Kobo Start Menu 08

[tshering]

Originally Posted by geekraver

I also tried going to "tools" from KSM; that took me to the tools submenu but once again stopped responding to touch at that point and I had to power cycle.

New patch uploaded here.
I guess your device is still in the "safety mode," booting into KSM every second time, and every other time into nickel. When you copy the KoboRoot.tgz (of the new patch) to .kobo from within the nickel application in a session when the device had booted directly into nickel, it will automatically boot into KSM. At this point you should see a new entry in the main menu, namely "handle update." Select it and then select "install update." After the device has booted again into nickel, restart the device. Try whether you can now go into "tools" and back into the main menu (by "return" or "return home"). Try also to connect to the device to the pc:

• connect the device with the usb cable to the pc
• select "usb" "usb enable.sh" (this might take some seconds)
• from your pc you should now have access to the user partition of the device (same as from within nickel) (this might also take some time, since the pc installs the reader as a new device.)
• safely remove and eject the device
• (in KSM) select "usb_disable.sh" (this takes some seconds)
• disconnect the device from the pc (or leave it connected, if you want to charge the battery anyway, or for any other reason)

If everything worked (KSM being responsive to touch after booting; installing update from within KSM; navigating to "tools" and back to the home menu; connecting to pc via usb), you may do this:

• select "tools" > "activate" > "set runmenu settings.msh" > "always"

From then on the device will boot each time into KSM. This should make further testing more easy. But if anything of the aforementioned things did not work, or looked somehow suspicious, stay in the "safety mode."

[Frenzie]

Originally Posted by geekraver

@Frenzie, I applied your patch. Now from KSM selecting koreader launched and displayed the FileManager, but it was upside down and not responding to further touch events, and I had to power-cycle.

When you say FileManager, do you mean you tried an old release? Newer releases call it "KOReader File Browser". I would try this one (built a few hours ago) because it already includes the patch I gave you.

On newer firmwares it's must to use a build from no older than about half a year ago for native 32-bit support in KOReader. I believe KSM still sets it to 16-bit as a compatibility measure, which could be related to the screen turning you're seeing.

The most logical thing to try next is to look at what's different on the Kobo Aura One (i.e., add touch_probe_ev_epoch_time = true).

You could also try playing around with some other configs, like:

needsTouchScreenProbe = yes,
touch_switch_xy = false,

(See Kobo Touch.)

Btw, since you say the display is upside down it would be very useful to distinguish touch not responding at all from touch being mirrored or upside down.

[geekraver]

I’ll respond in more detail later but in general when I say “no longer responds to touch” I am trying various axes of symmetry as well as random areas all with no effect.

[CH23]

Is there a way to get out of the password/keyboard screen when trying to connect to a wireless access point?
Currently this screen shows a-z, A-Z, 0-9, which is of no use for any good password, but since there's no 'back' button, you end up getting stuck there.

[tshering]

Originally Posted by CH23

Is there a way to get out of the password/keyboard screen when trying to connect to a wireless access point?
Currently this screen shows a-z, A-Z, 0-9, which is of no use for any good password, but since there's no 'back' button, you end up getting stuck there.

Press enter!

[geekraver]

@tshering: I did not see a "Handle update" option. I could go into tools menu or scripts menu and then return home without a problem.

@frenzie: this time on launch I got a "KOReader Quickstart Guide". It was upside down and touch events stopped working.

I tried adding:

    needsTouchScreenProbe = yes,
    touch_switch_xy = false,

which resulted in a "Tap the lower right corner" screen but still no response to touch after that.

[gilali]

Hello
I'm new in the forum, It's my first post. I really appreciate your efforts to run alternative app on exotic hardware. Thank you everyone

Originally Posted by geekraver

@frenzie: this time on launch I got a "KOReader Quickstart Guide". It was upside down and touch events stopped working.

I confirm, the first time i got the "KOReader Quickstart Guide" and now i have the "KOReader File Browser". Still no touch responding.

Here was my very humble (very poor) contribution

Good luck !!

[Frenzie]

Thanks for testing, guys. (Maybe we should take it over to the KOReader forum to prevent littering the KSM thread?)

I haven't been able to glean from this topic so far if the touch stuff on H2O2 is the same as on a previous device? Someone would need to collect the debug output and such.

[sergeyvl12]

Originally Posted by Frenzie

Thanks for testing, guys. (Maybe we should take it over to the KOReader forum to prevent littering the KSM thread?)

I haven't been able to glean from this topic so far if the touch stuff on H2O2 is the same as on a previous device? Someone would need to collect the debug output and such.

May be this will help. My program asked user to tap on each of 5 points on the screen (totally 5 taps):

>>>> Point: 100,100
...
>>>> Point: 1340,100
...

Debug log is in the attachment

[Frenzie]

@sergeyvl12
Thanks! Looks sensible enough.

@geekraver
Did you try it without touch_phoenix_protocol already?

[tshering]

Originally Posted by geekraver

@tshering: I did not see a "Handle update" option. I could go into tools menu or scripts menu and then return home without a problem.

Thank you again. That you did not see the "handle update" option is no problem. If you were able to go into the tools menu and so on and return to home without problem, already after the first reboot, then the new patch was already installed at that point (and therefore no need for a "handle update" option). I guess my description on when exactly to copy the KoboRoot.tgz to the device was not very clear.

Did you try to connect to pc via usb? Cf. the description here.

[geekraver]

Originally Posted by Frenzie

@sergeyvl12
Thanks! Looks sensible enough.

@geekraver
Did you try it without touch_phoenix_protocol already?

Yes, makes no difference.

@tshering, what is the purpose of enabling usbnet? Killing unresponsive processes? I can edit files easily just mounting the Kobo as an external volume.

[Frenzie]

Originally Posted by geekraver

Yes, makes no difference.

Weird, I haven't had the time to compare it to other output (let alone remember where that stuff might be lying around in bug reports and forums), but it looks to me like you should at least be able to get some kind of behavior out of it.

See https://github.com/koreader/koreader/issues/2235 for the Kobo Aura One stuff.

@sergeyvl12 Do you happen to know how it compares to other devices?

[sergeyvl12]

Originally Posted by Frenzie

@sergeyvl12 Do you happen to know how it compares to other devices?

No... But I can try to get the same log (ask users on my forum) for other devices (e.g. Aura One, Glo HD).

[tshering]

Originally Posted by geekraver

Yes, makes no difference.

@tshering, what is the purpose of enabling usbnet? Killing unresponsive processes?

The usb menu offers two different things:
1) usb enable.sh
This lets you use your device as an external mass storage. This is useful if you want (or have) to copy files to the user partition without running nickel.
2) usbnet toggle.sh
This establishes a network connection between the kobo and your pc via the usb cable. With some further steps (see the first post of this thread.) you can use this connection to telnet into the kobo. That means you can execute linux commands from your pc (e.g., killing processes, deleting files, rebooting the device).

Originally Posted by geekraver

I can edit files easily just mounting the Kobo as an external volume.

Are you telling that you have tested KSM usb > usb enable.sh? Or are you talking about connecting from within nickel?