Kobo Start Menu 09

[rogerty]

Hello,

I've installed the latest version of KSM (9, 2018.01.05) + koreader+plato+vlasovsoft (licensed) + patch for being able to copy files (new epub, i.e.) trough wifi from ftp, without having to connect to pc with a usb.

But after I copy the file, I need to simulate plug and unplug usb in order to inform nickel I've updated files.

The problem is that on the forums I see that I have to use the "simulate_usb_connection.png" to do this, but:

1- I don't have this file in my installation ... why ?!
2- If i'd have it, from where should I 'execute' that image ?

I'm very confused about it, please give me detailed instructions about how to fix it; I think the docs should be updated

Thanks in advance,

Roger

[tshering]

Originally Posted by rogerty

The problem is that on the forums I see that I have to use the "simulate_usb_connection.png" to do this, but:

1- I don't have this file in my installation ... why ?!
2- If i'd have it, from where should I 'execute' that image ?

I'm very confused about it, please give me detailed instructions about how to fix it; I think the docs should be updated

Since the script can do harm when used carelessly (and it maybe not work very reliably), I did remove the concerning png (simulate_usb_connection.png) from KSM 09. You can take any png file and rename it to simulate_usb_connection.png. You can also take the file attached to this post.
Initiate the function:

• connect the Kobo to the PC
• copy simulate_usb_connection.png into the folder kbmenupngs
• eject safely and disconnect
• check simulate_usb_connection.png is listed in the library and its thumbnail are displayed there. Open it, so that it appear at least once as tile on the home screen.
• exit nickel and launch it again

How to use it:

• the device must NOT be connected via USB
• (in nickel) open simulate_usb_connection.png as if it were a book
• there should now appear the usb connect pop up. Select quickly "connect" (this is time critical, it is important that select without waiting)
• wait until the pop up closes, the "connected and charging" message appears, and disappears, ...

I do not recommend to use this function. It might not work on some newer Kobo models!

[edlu]

Hi
After last update on KA1 - 4.18.13737, KSM 09 not working, installed it all over again several times. It is there, but Nickel is taking over. It boots with KSM 09 msg quickly then goes into Nickel with three dots and boots into Nickel.
The only way to go to Koreader is when I click at koreader image, then it boots into Koreader, which I find a little bit pain.
Hope there is a fix, or I might need to roll back Kobo OS to earlier edition to make KSM 09 work.
help is much appreciated.

[edlu]

Originally Posted by edlu

Hi
After last update on KA1 - 4.18.13737, KSM 09 not working, installed it all over again several times. It is there, but Nickel is taking over. It boots with KSM 09 msg quickly then goes into Nickel with three dots and boots into Nickel.
The only way to go to Koreader is when I click at koreader image, then it boots into Koreader, which I find a little bit pain.
Hope there is a fix, or I might need to roll back Kobo OS to earlier edition to make KSM 09 work.
help is much appreciated.

After several tries it worked. Not sure what changed though.

[Bolognie1]

I really just cbf with this. I got a H2O libra, and now it's just fkd up. I can't use the menu and the orientation is fixed. It just bugs out and I just want to uninstall it, but I can't access the menu anyway. How do I connect via web interface to uninstall?

[Frenzie]

http://{The ip of your device}:8087/rmc_test.html

[ben4ever]

Did someone already create a patch to fix the fact that SD card is mounted read-only when launching Plato and hence ebook metadata cannot be written?

Here the instructions from the Plato maintainer what needs to be done in KSM to fix this.

I would appreciate if someone could provide a patch for this, please. That would be great .

[ben4ever]

Originally Posted by ben4ever

Did someone already create a patch to fix the fact that SD card is mounted read-only when launching Plato and hence ebook metadata cannot be written?

Here the instructions from the Plato maintainer what needs to be done in KSM to fix this.

I would appreciate if someone could provide a patch for this, please. That would be great .

Never mind, got it working. I've created a patch now which updates adds/kbmenu/onstart/start_plato.sh by adding the line

mount -o remount,rw /mnt/sd

before starting Plato.

Download the attached patch if you want to do the same. Simply extract KoboRoot.tgz from the zip file, copy it into .kobo, and install it by clicking on handle update on KSM home screen.

[rtiangha]

I'm hoping tshering doesn't mind (I couldn't figure out what KSM09 is licensed under), but in an attempt to try to tidy up KSM09 development a bit to make maintenance easier, I'm trying to recreate the development timeline on GitHub in order to use Git's versioning functions to see the differences between all these different versions.

The repository is here:
https://github.com/rtiangha/kobo-start-menu-09

This is what I've done:

Using KSM09 plus update001 as the base, I added the nightmode mod.

Now, according to CH23, this combination is good enough to support the Clara HD.

Next, I incorporated the redux3 icons and added the modifications needed to support Plato 0.7.9 and external sd cards.

From here, based on Elim Garek's post, I created a new branch just for the Forma and merged his changes. According to the diff, it looks like it's mostly binaries.

Finally, based on gilali's post, I created a new branch for just for the Libra and merged in the one line modification.

Which brings us to the present, but I still have a few questions:

1. What is the status of Aura H20 Version 2 support and if it works, what are the modifications that need to be made?
2. Are there any other devices missing that needed modifications in order to work? If so, which devices and what modifications?
3. I'm not sure where update002 fits into all of this in 2019. I made a test branch merging it in after everything else, and according to the diff, it looks like most of update002 has been incorporated in other patches. So how much of update002 is still relevant and can be merged in, and knowing the diffs of the newer Mark 7 devices, how much of update002 can be ported to those other branches?
4. Now that there's a bit more clarity on all the different versions and how they differ from one another, how much of this stuff can be combined to create a single KSM09 version that supports all devices? I assume that outside of binary drivers (which could be shunted to a separate package or packages depending on device if that makes things easier), most of the functionality in the scripts could be dealt with conditionals dependent on the device?

I might be missing a few other modifications so let me know if there's anything major yet to be added (it's a long thread, lol), but I hope this work helps a bit. I love KSM and whenever I get around to getting a new device, I hope it'll still run on it. It's been a good exercise for me to learn Git/GitHub too.

[tshering]

Originally Posted by rtiangha

I'm hoping tshering doesn't mind

I don't mind at all. I am glad somebody takes care of the stuff.

I am not sure whether this can help you, but have a look at this post.

Originally Posted by rtiangha

[*]Now that there's a bit more clarity on all the different versions and how they differ from one another, how much of this stuff can be combined to create a single KSM09 version that supports all devices? I assume that outside of binary drivers (which could be shunted to a separate package or packages depending on device if that makes things easier), most of the functionality in the scripts could be dealt with conditionals dependent on the device?[/LIST]

I think it would be preferable to have one package for all models. The binary files that are borrowed from vlasovsoft should be updated to the most recent version. Currently the standard KSM 09 version comes with two different touch/mouse drivers (libKoboTS.so and libKoboTS_h2o2.so) on the user partition; based on the device model, KSM copies the appropriate driver to the system partition. This part should be modified to include also libKoboTS_h2o.so so that all models can use the correct driver (See also this post.) The rcS file should also export the device names that vlasovsoft expects (cf. kobomenu_test.sh in the package that is available here.) As for the screen orientation, I guess one should follow how vlasovsoft handles it.

Best,
Tshering

[rtiangha]

Originally Posted by tshering

I don't mind at all. I am glad somebody takes care of the stuff.

I am not sure whether this can help you, but have a look at this post.

Oh wow, that's super helpful! Can't believe I missed it. So I guess that implies that the Forma version would be the best to rebase on.

OK, I've created a new unifed dev branch based on the Forma version to work on stuff until everything is caught up (then you could do a KSM09 2019-12 update roll up release or something), but added in the usb version from CH23's Clara package. I'm not a strong programmer, but if I did it right, I also added a conditional to ksmhome.sh with gilali's modification to support the Libra H20. So in theory, I think that's all that needs to be done for Forma and Libra devices?

My struggle is knowing if the files in the repository are the absolute latest, and if not, where to get them. Off the top of your head, like the example of that usb file, can you think of any others? For example, I'm no longer certain which version of start_plato.sh is the latest to add in baskerville's suggested modification; the one in the repository right now is my best guess.

I think it would be preferable to have one package for all models. The binary files that are borrowed from vlasovsoft should be updated to the most recent version. Currently the standard KSM 09 version comes with two different touch/mouse drivers (libKoboTS.so and libKoboTS_h2o2.so) on the user partition; based on the device model, KSM copies the appropriate driver to the system partition. This part should be modified to include also libKoboTS_h2o.so so that all models can use the correct driver (See also this post.)

OK, sounds easy enough. For the "case $MODEL_NUMBER in ..." block, I'm looking at what geek1011 has posted in terms of device information and it looks like there are a few missing devices. However, how do you find out which models use which driver? (Edit: Oh, I see. That's the entire point of ksm_helper).

As for the "case $PRODUCT in ..." block, where does one find the coordinate data for the various missing devices?

The rcS file should also export the device names that vlasovsoft expects (cf. kobomenu_test.sh in the package that is available here.) As for the screen orientation, I guess one should follow how vlasovsoft handles it.

Not sure what vlasovsoft expects for the newer devices and it looks like that pbchess package hasn't been updated since February. Not sure how to do this part, but the above should be enough for now unless other people are willing to chip in (feel free to send pull requests!).

[tshering]

Originally Posted by rtiangha

I'm no longer certain which version of start_plato.sh is the latest to add in baskerville's suggested modification; the one in the repository right now is my best guess.

Me seems that KBStartMenu_09_plato_6.1.zip from this post was the latest version.

[rtiangha]

Originally Posted by tshering

Me seems that KBStartMenu_09_plato_6.1.zip from this post was the latest version.

Got it. That's what I thought. I was trying to figure out where the rotation code came from, but I just found the message asking to remove it so it must have been that an older version got mixed in somehow. OK, I'll update the file.

[rtiangha]

OK, I modified rcS to add in the Aura H2O driver (I think; I don't have the device so I can't test it to see if it works).

Based on user reports, it looks like the Clara, Forma and Libra work with the H2O2 driver, so there's nothing left to be changed on that front.

The only device I'm unsure about is the Aura Edition 2 v2 currently being sold by Walmart (I think). Same code name as the v1 (star) but has an ID of 379 and is classified as a Mark 7 device. So it's missing, but from what I can tell, it's the only one left in their supported product line. Not sure if we should assume it uses the same driver as the v1 (libKoboTS.so) or the same one as the other Mark 7 devices (libKoboTS_h2o2.so, in which case, I think no change would be needed and it should just work by default with this newer version of KSM09). It'd be nice for someone with access to that device to test and confirm.

(Edit: And I have no idea why line 174 reads

export export QWS_MOUSE_PROTO=KoboTS

so I deleted that extra export; let me know if that is actually needed).

As for the other 'Add Forma and Libra data to the "case $PRODUCT in ..." block' task, currently, that section in KSM09 looks like this:

Spoiler:

    case $PRODUCT in
      kraken|phoenix|star)
        export COORDINATES="80 870 70 70 200 870 70 70";;
      snow)
        export COORDINATES="180 -1200 100 100 320 -1200 100 100";;
      dragon|dahlia|alyssum|nova)
        export COORDINATES="120 1220 100 100 280 1220 100 100";;
      daylight)
        export COORDINATES="100 1640 200 200 300 1640 200 200";;
      *)
        export COORDINATES="55 685 60 60 150 685 60 60";
    esac

while in firmware 4.18.13737, it looks like this:

Spoiler:

	case $PRODUCT in
		kraken|phoenix)
			export COORDINATES="200 740 350 150";;
		snow)
			export COORDINATES="250 -1050 570 150";;
		star)
			export COORDINATES="160 740 400 150";;
		dragon|dahlia)
			export COORDINATES="260 1070 540 130";;
		alyssum)
			export COORDINATES="240 1070 550 150";;
		daylight)
			export COORDINATES="320 1400 730 170";;
		nova)
			export COORDINATES="250 1070 600 150";;
		frost)
			export COORDINATES="350 1400 750 200";;
		storm)
			export COORDINATES="325 1240 610 150";;
		*)
			export COORDINATES="140 600 300 70";;
		
	esac

Is it good enough to just copy/paste that section in? I'm assuming that if that's done, then KSM09 will no longer work on older firmwares (which probably wouldn't be an issue to worry about because newer hardware won't run on older firmware anyways so no need to support that), correct? Or is there a reason why the KSM09 version looks so different?

[NiLuJe]

Yes, the H2O²r1 (Mk. 6) behaves in a completely different way than the H2O²r2 (Mk. 7).

I'd recommend looking at how Plato handles that, that's probably the most concise approach. Or you can read my rants about that scattered across the FBInk codebase, with the caveat that I only care about minor parts of the quirks, and that I'm not sure the uglier stuff (input) actually behaves since I don't have access to those devices.

And, yeah, pickel was recently updated (basically since the new spinner, so, 4.17 or something) with a new, simpler coordinates syntax. Which means I would *assume* it doesn't support the old syntax anymore, and older versions won't handle the new syntax.
Newer pickel variants also expect the various PLATFORM & co env vars to be set properly (which the default rcS does just fine, so that's only a concern if you use pickel on its own without a proper env setup), which wasn't always the case in (much) older FW versions.