Kobo Start Menu 07

[tshering]

Originally Posted by Markismus

EDIT: Rotation issue remains, so I'll accept your invitation, too. The script logs were generated on a Kobo Aura H2O.

Could you please tell me in which situations you see this issue on H2O apart from poweroff_test.sh and poweroff.sh?

[Markismus]

Originally Posted by tshering

Could you please tell me in which situations you see this issue on H2O apart from poweroff_test.sh and poweroff.sh?

Today I've touched all menu items available: no rotation anywhere.

I have no idea why the previous KSM7.4 started rotating. No idea why the newly installed rotated yesterday. No idea why after installing your log-scripts yesterday and checking for rotation today there is no rotation to be seen: Not even when powering off.

I wouldn't mind either, but for the possiblity that it al starts rotation again.

So yesterday: while pressing koreader item and usb and koreader submenu items. Didn't went around looking whether other menu's rotated, too.
Today: none.

[KoboNewbie]

Hello tshering, I downloaded again the pbchess2015-5.zip file from Sergey's page and just copied the vlasovsoftlauncher folder, like you suggested, and now it's working fine on both Glo and Aura HD with KSM 07 Update 4! No unsupported messages! Thanks! I also installed the nightmode patch on both devices (thank you for saving me from my ignorance, otherwise I'd keep trying to make the toggle_nightmode.png work without the patch until kingdom come, lol), and it's working fine on the Aura HD; the Glo has a few glitches (sometimes I have to hold the light button very long to turn off the light, also the light simply turns on by itself randomly and drains the battery when the reader is just sitting there, and auto-sleep [via the nickel settings menu] doesn't work), but the Glo was already behaving like that with nickel 3.5.0 (and that was the reason I decided to update, which led me to find out about KSM).

Please don't hate me, but I also noticed a serious battery drainage problem on the Glo after I updated to 3.15.0 and installed KSM 07, even when it's asleep on Nickel (I already set preventfreeze to false, BTW, but that didn't help). Before the update and KSM, the battery lasted for days (like two weeks) even when I occasionally forgot it not sleeping overnight, so I never even had to turn it off. Now the battery dies in two days, sometimes less, even when it sleeps all the time. The curious thing is, I did the same things on the Aura HD (updated to 3.15.0 and installed KSM 07) and its battery life didn't change at all (still lasts for weeks even with the device always on). I noticed that other people posted here about short battery life problems on Glo, so this is why I'm tellilng you this. Maybe it's something in the model that doesn't agree well with KSM 07, I don't know. Anyway, if the problem persists, I'm thinking about uninstalling KSM 07 from the Glo, since I can still enjoy it on the Aura HD, where it works fine. Overall, I prefer the Aura HD anyway, I think it works better and I love the bigger screen, I'd buy a 9.7-inch model if there was one on the market here.

Once again, thanks for all the patience and support.

[tshering]

Originally Posted by Markismus

Today I've touched all menu items available: no rotation anywhere.

I have no idea why the previous KSM7.4 started rotating. No idea why the newly installed rotated yesterday. No idea why after installing your log-scripts yesterday and checking for rotation today there is no rotation to be seen: Not even when powering off.

I wouldn't mind either, but for the possiblity that it al starts rotation again.

So yesterday: while pressing koreader item and usb and koreader submenu items. Didn't went around looking whether other menu's rotated, too.
Today: none.

Really strange!

[tshering]

Originally Posted by KoboNewbie

the Glo has a few glitches (sometimes I have to hold the light button very long to turn off the light, also the light simply turns on by itself randomly and drains the battery when the reader is just sitting there, and auto-sleep [via the nickel settings menu] doesn't work), but the Glo was already behaving like that with nickel 3.5.0 (and that was the reason I decided to update, which led me to find out about KSM).

Something is definitely wrong with your device. Is it hardware ore software related? Did you already try to factory reset your device?

Originally Posted by KoboNewbie

Please don't hate me, but I also noticed a serious battery drainage problem on the Glo after I updated to 3.15.0 and installed KSM 07, even when it's asleep on Nickel (I already set preventfreeze to false, BTW, but that didn't help). Before the update and KSM, the battery lasted for days (like two weeks) even when I occasionally forgot it not sleeping overnight, so I never even had to turn it off. Now the battery dies in two days, sometimes less, even when it sleeps all the time. The curious thing is, I did the same things on the Aura HD (updated to 3.15.0 and installed KSM 07) and its battery life didn't change at all (still lasts for weeks even with the device always on). I noticed that other people posted here about short battery life problems on Glo, so this is why I'm tellilng you this. Maybe it's something in the model that doesn't agree well with KSM 07, I don't know.

I am not sure whether this is model based, since I have a Glo myself without power issues. However I never let it sleep over night.

[KoboNewbie]

Originally Posted by tshering

Something is definitely wrong with your device. Is it hardware ore software related? Did you already try to factory reset your device?

I really don't know whether it's hardware or software related; I'm beginning to suspect maybe the light button is busted somehow. Haven't tried the factory reset yet, I'm still working up the courage to do that :-P

Originally Posted by tshering

I am not sure whether this is model based, since I have a Glo myself without power issues. However I never let it sleep over night.

I think I was just spoiled, because at first the battery discharged very slowly while sleeping, and maybe now battery consumption is a little higher and its battery is also a little older, and that compounded to produce a very short charge duration. But it still seems waaaay too short. For instance, it was charged to 100% yesterday until morning, I even turned it off for a few hours since, but tonight it's back in feed-me-please mode. That's very annoying. The Aura HD, on the other hand, was charged to 100% yesterday, I don't think I even turned it off, but it still has more than 80% charge tonight. Maybe the Aura HD has a bigger battery as well. I think I'm gonna check how much both devices consume in sleep and reading mode, both in nickel and koreader, over a period of, say, two hours, and post the results here, just for the heck of it.

Thank you for your always useful advice.

[xor_]

I know the question of suspend and power consumption has been discussed before. But I haven't really seen much in the way of conclusive answers. And I'm a bit unhappy with the battery life of my Glo HD outside of nickel. Sorry if these are trivial questions.

I noticed both KSM and koreader use suspend to RAM in their suspend scripts. What is the reason for not using suspend to disk?

And when I send my device to sleep through the magnet cover mechanism, who handles that? Is that the suspend script in koreader / KSM, or something else?

[tshering]

Originally Posted by xor_

I noticed both KSM and koreader use suspend to RAM in their suspend scripts. What is the reason for not using suspend to disk?

KSM just used the same calls as nickel did at that time. Suspending to disk would heve been more time consuming. And in the case of KSM, where there is no point in saving its state for an extended period of time, simply powering off would be preferable to suspending to disk.

Originally Posted by xor_

And when I send my device to sleep through the magnet cover mechanism, who handles that? Is that the suspend script in koreader / KSM, or something else?

In KSM, the suspend script is still existent, but it is never called. You would have to make some effort to call it manually.

As I see it, the power consumption during suspend (when you the script from KSM, and I guess it would be the same with koreader) is as it should be, namely close to none. The problem however is that something finishes the suspend state untimely. See this post and especially the log in the spoiler.

[xor_]

Thanks. I'm not quite sure that's what happens under koreader. In fact I'm trying to understand what it does in the first place. If I put a debug line like

date >> /mnt/onboard/mydate.txt

into koreader's suspend.sh, that file doesn't get written. So I'm suspecting that script isn't being executed. Not sure whether it's supposed to, but I guess that's a question I should ask in the koreader thread.

Anyway, the bottom line for me is, I easily get 30 percentage point charge drops per day, with my Glo HD sitting still being "suspended" by the cover. And that just seems too much. I used to think the device just wakes up occasionally when I move it around during the day in my bag. But I get those drops even when I make sure it just sits still all day.

[gyAndy]

Hi.
I installed KSM07 on my Kobo Glo HD (firmware 3.16.0) .
I'd like to uninstall KSM but in "KBStartMenu_07_uninstall.zip" is not referenced the uninstaller for the firmware 3.16.0 .
Can I use th uninstaller for the version last version (3.13.1)?

Thank you.
Andy

[tshering]

Originally Posted by gyAndy

Hi.
I installed KSM07 on my Kobo Glo HD (firmware 3.16.0) .
I'd like to uninstall KSM but in "KBStartMenu_07_uninstall.zip" is not referenced the uninstaller for the firmware 3.16.0 .
Can I use th uninstaller for the version last version (3.13.1)?

Thank you.
Andy

Yes, you can use the 3.13.1 version.

[Ken Maltby]

Originally Posted by xor_

Thanks. I'm not quite sure that's what happens under koreader. In fact I'm trying to understand what it does in the first place. If I put a debug line like

date >> /mnt/onboard/mydate.txt

into koreader's suspend.sh, that file doesn't get written. So I'm suspecting that script isn't being executed. Not sure whether it's supposed to, but I guess that's a question I should ask in the koreader thread.

Anyway, the bottom line for me is, I easily get 30 percentage point charge drops per day, with my Glo HD sitting still being "suspended" by the cover. And that just seems too much. I used to think the device just wakes up occasionally when I move it around during the day in my bag. But I get those drops even when I make sure it just sits still all day.

The Freescale iMX507 used by Kobo communicates with a MC34708 power management chip over an SPI/I2C bus. Freescale had some documentation on a Linux bus interface.

Luck;
Ken

[chipro12]

HI, I have a question. I kind of messed around with nickel and then I lost all of the png files. Also, when i reboot and select nickel, I had to go through the whole setup thing with kobo. Then, I put in my kobo account. The nickel home screen is normal and all png files are back but they cant be used. So, i am sort of confused by this. What causes this problem? How can i retrieve these functionality of these png files?
btw, i am using a kobo h2o
Edit: Now my KSM screen doesn't have handle update option?

[Ebri]

Almost sure, that your database is corrupt, if you can log out from menu (sometimes after database corruption I was unable to), then log in, a new database will be created, and books will be re-read again.

If you made backups with calibre, you should copy it back to .kobo directory. (kobo utilities plugin can do it).

You can also try to repair it by any sqlite handling database software, but for me it usually didn't succedd at this stage.

[chipro12]

Thanks for your reply. Now what makes me really worried is that I can't find the option of "handle update" on KSM? :<
Edit: Vlasovsoft is gone too :<