Kobo Start Menu 08

[tshering]

I just tried FW 4.2.8283 on a C Touch. When exiting from nickel to KSM, there are screen distortions each time the screen is refreshed. I am back on 4.2.8110, and everything is back to normal.

[davidfor]

Originally Posted by tshering

I just tried FW 4.2.8283 on a C Touch. When exiting from nickel to KSM, there are screen distortions each time the screen is refreshed. I am back on 4.2.8110, and everything is back to normal.

I have just posted in the FW 4.2.8283. There are kernel changes for 32bpp support. The kernels for the other devices will need to be updated before the newer KoboRoot.tgz can be used.

[tshering]

Originally Posted by davidfor

I have just posted in the FW 4.2.8283. There are kernel changes for 32bpp support. The kernels for the other devices will need to be updated before the newer KoboRoot.tgz can be used.

Thank you for this information!

For users who configured KSM so that it automatically calls KOReader (or anything else but nickel) after boot, it might be a good idea to go back to the original settings (autostart of nickel after 20 seconds or so), before they install a complete update package (KoboRoot.tgz plus the other stuff) newer than 4.2.8110. At least until we have information of people who have already tried.

Did any KSM users already install a complete FW 4.2.8283 on an Aura One or Aura Edition 2? Where there any problems with KSM?

[trekk]

Originally Posted by tshering

Did any KSM users already install a complete FW 4.2.8283 on an Aura One or Aura Edition 2? Where there any problems with KSM?

I downloaded and installed FW 4.2.8283 on my Aura One via KSM. The installation process went fine.

From the KSM menu I was able to start the vlasovsoftlauncher, but when pressing "start koreader" nothing seems to happen. After a reboot I was able to start Koreader.

Now every time I start nickel and then exit to KSM, Koreader won't start without doing a manual reboot of the device. Vlasovsoftlauncher however starts without rebooting.

[tshering]

Originally Posted by trekk

I downloaded and installed FW 4.2.8283 on my Aura One via KSM. The installation process went fine.

From the KSM menu I was able to start the vlasovsoftlauncher, but when pressing "start koreader" nothing seems to happen. After a reboot I was able to start Koreader.

Now every time I start nickel and then exit to KSM, Koreader won't start without doing a manual reboot of the device. Vlasovsoftlauncher however starts without rebooting.

Thank you for the report. I understand that you did not install the emergency poweroff for Koreader. Right? I am just asking to eliminate possibilities. Did you look whether there was a crash log in the koreader folder?

[trekk]

Originally Posted by tshering

I understand that you did not install the emergency poweroff for Koreader. Right?

You are right. Emergency poweroff was not installed on this particular device.

Originally Posted by tshering

Did you look whether there was a crash log in the koreader folder?

Yes, this is the correlating excerpt:

01/18/17-11:20:53 ERROR cannot open translation file: l10n/en_US/koreader.po
./luajit: ./ffi/framebuffer_linux.lua:60: unknown bpp value for the eink driver
stack traceback:
	[C]: in function 'error'
	./ffi/framebuffer_linux.lua:60: in function 'init'
	./ffi/framebuffer_mxcfb.lua:290: in function 'init'
	./ffi/framebuffer.lua:59: in function 'new'
	frontend/device/kobo/device.lua:127: in function 'init'
	frontend/device.lua:39: in main chunk
	[C]: in function 'require'
	frontend/ui/uimanager.lua:1: in main chunk
	[C]: in function 'require'
	./reader.lua:93: in main chunk
	[C]: at 0x00013e85

[tshering]

Originally Posted by trekk

You are right. Emergency poweroff was not installed on this particular device.



Yes, this is the correlating excerpt:

01/18/17-11:20:53 ERROR cannot open translation file: l10n/en_US/koreader.po
./luajit: ./ffi/framebuffer_linux.lua:60: unknown bpp value for the eink driver
stack traceback:
	[C]: in function 'error'
	./ffi/framebuffer_linux.lua:60: in function 'init'
	./ffi/framebuffer_mxcfb.lua:290: in function 'init'
	./ffi/framebuffer.lua:59: in function 'new'
	frontend/device/kobo/device.lua:127: in function 'init'
	frontend/device.lua:39: in main chunk
	[C]: in function 'require'
	frontend/ui/uimanager.lua:1: in main chunk
	[C]: in function 'require'
	./reader.lua:93: in main chunk
	[C]: at 0x00013e85

Thank you again. Maybe reading the fbset values before and after starting nickel can help to find an easy solution.

BTW: I thought it is difficult to test the emergency power off without using telnet. But here is your chance.

[trekk]

Originally Posted by tshering

BTW: I thought it is difficult to test the emergency power off without using telnet. But here is your chance.

So true, chance taken

When I exit nickel and start Koreader via KSM the "KOReader exited irregularly" message comes up immediately.

When I start Koreader after a manual reboot of the device, Koreader will start und function normally. After exiting Koreader the "KOReader exited irregularly" message comes up again.

Edit: If you wait to long before choosing one of the options ("power off", "continue"), the device will freeze, but come back to life after a power off/on.

Edit 2: I can't find any log file. Maybe you can point me to the path.

[tshering]

Originally Posted by trekk

When I start Koreader after a manual reboot of the device, Koreader will start und function normally. After exiting the device the "KOReader exited irregularly" message comes up again.

Sorry, I am not able to understand exactly at which point the message comes up.

Originally Posted by trekk

Edit: If you wait to long before choosing one of the options ("power off", "continue"), the device will freeze, but come back to life after a power off/on.

Did you try to select "power off" from this point (when you can choosee between power off and continue)? Did it work? Or does this too lead to freezing?

Originally Posted by trekk

Edit 2: I can't find any log file. Maybe you can point me to the path.

I do not have my kobo with me. Therefore, I might give some inaccurate information. If I remember correctly, there are several ways to go there:
1) explore > kbmenu.msh > log > koreader_exit_log.txt
2) explore > adds > kbmenu > log > koreader_exit_log.txt
Do not expect to much. Only the exit time is logged.

[trekk]

Originally Posted by tshering

Sorry, I am not able to understand exactly at which point the message comes up.

Sorry, I was unconcentrated, because my neighbor brought me some delicious food.

I meant, that after exiting Koreader the "KOReader exited irregularly" message comes up again. I corrected my post above.

Originally Posted by tshering

Did you try to select "power off" from this point (when you can choosee between power off and continue)? Did it work? Or does this too lead to freezing?

Both, "power off" and "continue", work as they should, but if you wait too long before tapping on the screen, neither of them will do anything and the screen freezes.

I found the log file, thank you. It was option 1) and, yes, date and time of the spontaneously Koreader exit is shown.

[tshering]

Originally Posted by trekk

Sorry, I was unconcentrated, because my neighbor brought me some delicious food.

Good for you!

Originally Posted by trekk

I meant, that after exiting Koreader the "KOReader exited irregularly" message comes up again. I corrected my post above.

This is bad. I cannot remember that I changed something in the script after testing and before uploading. What is happening here?

Originally Posted by trekk

Both, "power off" and "continue", work as they should, but if you wait too long before tapping on the screen, neither of them will do anything and the screen freezes.

This is bad. I cannot remember that I changed something in the script after testing and before uploading. What is happening here? Did I repeat myself? Anyway, I hope the device does nonetheless power off (even though you cannot know by looking at the screen).

Thank you again for reporting.

EDIT: I have tested it again several times on my reader and everything works as expected. Right now I do not know how to continue at this point.

[tshering]

I have KSM (and KOReader) running on Kobo Touch under FW 4.2.8283. Could owners of other models please install the uploaded patch* (the archive contains a KoboRoot.tgz file), and confirm whether it works? The problem was that after running nickel and returning to KSM, the screen of KSM had distortions, and KOReader did not run.

* I do not want to talk anybody into installing FW 4.2.8283. Be aware that there is a warning against "manually applying 4.2.8283 if it's not available via the Kobo servers" by george.talusan (link). From the information spread in this forum the greatest risk is for mark 5 devices (Aura 6", H2O).
Edit: I have tested FW 4.2.8283 on a Kobo Glo (after applying KSM_patch_4.2.8283). KSM and KOReader are working, but nickel does not (heavy screen distortions):

If you have installed the package KSM08_ext_aura_one_03b from here, then there is no need to install KSM_patch_4.2.8283, since it is already included there.

I have removed the archive from this post and included this patch (with further improvements) in KSM08_ext_aura_one_03c from here. KSM08_ext_aura_one_03c is not limited to Aura One and Aura Edition 2.

[JFeole]

Tshering,

I just updated to 4.2.8283 on my KA1, and did notice the KOReader behaviour. I started KOreader after reboot, started fine, then exited ok, no screen issues or hangs.

Then I started Nickel, checked, and exited and attempted to then reload KOReader, which would NOT load, jus non-responsive, no hang.

Lastly, i added this patch you just posted and retested and seems to work fine
after installing patch.

Thanks,
John Feole

[tshering]

Originally Posted by nook_nerd

Tshering,

I just updated to 4.2.8283 on my KA1, and did notice the KOReader behaviour. I started KOreader after reboot, started fine, then exited ok, no screen issues or hangs.

Then I started Nickel, checked, and exited and attempted to then reload KOReader, which would NOT load, jus non-responsive, no hang.

Lastly, i added this patch you just posted and retested and seems to work fine
after installing patch.

Thanks,
John Feole

Thank you for reporting!

[trekk]

I applied the KSM_patch_4.2.8283. After exiting Nickel Koreader starts fine now, but when closed, the "KOReader exited irregularly" message appears again.