Kobo Start Menu

[Cyphox]

sorry, dont have the touch anymore, forgot to edit my profile.

its always like this (tested it five times now):
- power on the device, do something with it or not (reading etc), doesnt matter.
- as soon as you/re (back) in kobo start menu (or any submenu), leave the device alone for about 2-3min and get back to it, its frozen and you cant do anything but a reset (or forced power down).

as long as you're "doing" something in start menu everything's fine. same goes for using apps llike coolreader, no problems at all.

its almost like it enters some automatic sleep mode from which it cant be waked up.

[tshering]

Originally Posted by Cyphox

its almost like it enters some automatic sleep mode from which it cant be waked up.

Actually, I once implemented an auto-sleep function in the Kobo Start Menu. However, I removed it. At least I thought so. I cannot exclude that it slipped into the code again, and I cannot check now, since I am on a trip and don't have the code with me. Anyway, if the device falls asleep, you should be able to wake it up with the power slider. But who knows!
We could make a little experiment, if you like, Add in .kobo/kbmenu/usersettings.txt the line

export kobomenuShowClock=true

Use a unix-style editor for editing. After rebooting, the menu will display a running clock. This way we can maybe get some information, whether the device is sleeping or the application is dead (clock does not run), or on the other hand whether it is awake/alive (clock does run) and for some reason does not register the touch imput. I don't know how much the clock increases the power consumption, but since your tests will not need more than some minutes each, we don't have to worry about it.

[tshering]

I am providing here the script file checkbatteryautorefresh.sh. Extract it from the archive and copy it to .kobo/kbmenu/scripts/test/. Run it by selecting "scripts" > "tests" > "checkbatteryautorefresh.sh." Basically, it does the same as checkbattery.sh, namely displaying some information on the current state of the battery. The difference is, that the new script updates the information every 60 seconds. You can use this for instance to get information on the progress of the charging process.

[Ken Maltby]

Originally Posted by tshering

I am providing here the script file checkbatteryautorefresh.sh. Extract it from the archive and copy it to .kobo/kbmenu/scripts/test/. Run it by selecting "scripts" > "tests" > "checkbatteryautorefresh.sh." Basically, it does the same as checkbattery.sh, namely displaying some information on the current state of the battery. The difference is, that the new script updates the information every 60 seconds. You can use this for instance to get information on the progress of the charging process.

Thanks, this should pretty much eliminate any need (for me) to ever use Nickel again.

Luck;
Ken

Works well, all that I could ask for.

[Cyphox]

Originally Posted by tshering

export kobomenuShowClock=true

interesting, looks like the freezes do not occur when the clock is running.

nice workaround.

[tshering]

Originally Posted by Cyphox

interesting, looks like the freezes do not occur when the clock is running.

nice workaround.

That would be great! I was hoping for this, but did not really believe that ic could work. Of course, it could be just some kind of coincidence, since we don't know what triggers the freeze. Counting each second seems of course to be an overkill. I was planning to introduce an option to count only hours and minutes with the next larger upgrade anyway. But maybe an interval of one minute is to long to keep the application/the system alive.

Funny, just some minutes ago my Touch froze after some time of not using it. See the next post.

[tshering]

Originally Posted by Ken Maltby

Thanks, this should pretty much eliminate any need (for me) to ever use Nickel again.

Luck;
Ken

Maybe it is to early for a celebration. I just charged my mark 3 Touch. It started by 62 percent, and froze on 93 percent.

[Ken Maltby]

Originally Posted by tshering

Maybe it is to early for a celebration. I just charged my mark 3 Touch. It started by 62 percent, and froze on 93 percent.

Mine seems to be topping out at 96. I know that the charging will slow as it nears full charge. OK, it just jumped to reading 100 "Status Not charging"

Looking good so far on my AuraHD 3.2.0.

Luck;
Ken

[Markismus]

Originally Posted by tshering

Have a look at post 17!

Ah, the post crossed. Will try.

[WS64]

Is there any way to get rid of the two front light entries on my Kobo Mini? Obviously I can't use them...

[tshering]

@WS64
Thank you for telling. This was an oversight.

• copy KoboRoot.tgz from the archive to .kobo
• in the home menu select "handle update" > "install update" (rather then "install partial update")

[WS64]

Thx, they are gone now!

[roger64]

Hi

I stopped updating my Kobo Glo about last July with a comfortable 2.8.1 and 0.0.7. patcher, plus some fonts and dictionaries.

I had been curious to try Koreader since it did not interfere with my current settings. I did that today:
- startmenu was easily installed. I think the icons take a lot of screen real estate...
- koreader was easily installed too (stable version from April).

As I did not read about control gestures for Koreader, I was quickly stuck with one book and had to do a pinhole reset. After reading some needed information, everything now seems to be working fine. Koreader is very responsive, the boldening of the font very pleasant.

It's another choice with pluses and very few minuses. Thanks very much for your contributions.

[Markismus]

@Tshering On github pazos asked whether we could use Start Menu for fast switching between koreader and Nickel.

Would it be possible to make a script which exits koreader and enters Nickel and a script which exits Nickel and enters koreader? Together with the normal exit script from Nickel to break the loop, we would have a real fast switcher.

As a point of interest. We had to reboot the device in the past after killing Nickel to reenter Nickel. Did you do rather smart scripting to alleviate that problem or does it also depend on the compiled code that is installed as part of Start Menu?

[Ken Maltby]

I wonder if you could:

From nickel to koreader :

killall -STOP nickel
-----------------
killall adobehost
killall dbus-daemon
killall Hindenburg
(or not depending on why you are going back and forth)
------------------

killall -CONT reader
(not running/found errors to:

# finally call reader
./reader.lua 1> koreader.log.`date +%s` 2>&1
(Or wherever you want it to start.)



From koreader back to nickel:

killall -STOP reader

killall -CONT nickel

.

Otherwise there will be dancing boxes.

Luck;
Ken

Perhaps we just need exit options for koreader?

Or... A Start Menu selection that starts Nickel then killall -STOP nickel and starts Koreader; then killall -STOP reader.lua; then killall -CONT nickel. A PNG would be added to -STOP nickel and -CONT reader. for jumping back to koreader.