Kobo Start Menu

[NiLuJe]

Okay, updated the FBGrab package, it should *hopefully* now handle the Kobos properly .

[tshering]

Originally Posted by NiLuJe

Okay, updated the FBGrab package, it should *hopefully* now handle the Kobos properly .

Works perfectly! Thank you!

[NiLuJe]

@tshering: Awesome, thanks for checking, and the test dumps .

[embryo]

Well, after I used my -android flavored- Glo last month just for reading, I realized that I don't 'play' with it that much when I'm away from home (apart from searching the tags for what to read next).
So I thought I'll give dual boot a try.
It worked OK, but I did miss the Kobo Start Menu that I had on my Nickel only system.

For that I was prepared to do some experimenting.
The plan was to:
- Patch Glo with the necessary files to dualboot.
- Copy the files of the system partition as 'Files 1'
- Install KSM
- Copy the files of the system partition as 'Files 2'
- Find what the differences were.
- Create scripts to copy the needed files to boot from KSM to Android and vice-versa.

But after the KSM installation, lo and behold!
Both boot options worked perfect!

So now I can have everything in one reader.
I'm using 3.4.1 (since 3.5.0 is reported slower with the epubs) and I keep my books (3.5k+) in a .Books folder.
Using koreader 2014.04-401 and pbchess-1.2.6.41

@Tshering
- I uploaded the files that got copied to the system with the Dual boot patching to tell me, if you can, if there are dangerous for the reader's stability.
- I can't get 'kobomenuFontsize' to work.
This is the setting for the font size of the main menu, right?
'kobomenuMenuBarFontsize' works OK.
- ksmImageWidthPortrait for my Glo is 724 (no scrollbars)
- Is the last version KBStartMenu_04.zip with the KBStartMenu_04_update01a.zip?
- When I use USB Support to connect to Calibre, it says that the device is Kobo Touch. Is this changeable?
- I get many freezes with KoReader and some with the KSM, but its the beginning, I have to read more...

I'll keep you posted.

[tshering]

@embryo
Wow, this sounds exciting!

Originally Posted by embryo

- I uploaded the files that got copied to the system with the Dual boot patching to tell me, if you can, if there are dangerous for the reader's stability.

Unfortunately, I do not know.

Originally Posted by embryo

- I can't get 'kobomenuFontsize' to work.
This is the setting for the font size of the main menu, right?

Yes this is the font size for the list entries. Maybe there is a problem with the byte order mark? You can try to leave the first line in usersettings.txt blank.

Originally Posted by embryo

- ksmImageWidthPortrait for my Glo is 724 (no scrollbars)

Thank you for the information. By the way, I think I will give up this approach and will handle images differently in future.

Originally Posted by embryo

- Is the last version KBStartMenu_04.zip with the KBStartMenu_04_update01a.zip?

Yes, it is.

Originally Posted by embryo

- When I use USB Support to connect to Calibre, it says that the device is Kobo Touch. Is this changeable?

Change in .kobo\kbmenu\usb\usb_enable.sh the product id to 0x4183. Now there is
"PRODUCT_ID=0x4163".
For general information:

• 0x4163=Touch
• 0x4173=Glo
• 0x4183=Mini
• 0x4193=AuraHD
• 0x4203=Aura
• 0x4213=?

I will set the value dynamically in future versions.

Originally Posted by embryo

- I get many freezes with KoReader and some with the KSM, but its the beginning, I have to read more...

Might not be related, but maybe you can have a look at this post.

[embryo]

Originally Posted by tshering

Yes this is the font size for the list entries. Maybe there is a problem with the byte order mark? You can try to leave the first line in usersettings.txt blank.

You're right!

Change in .kobo\kbmenu\usb\usb_enable.sh the product id to 0x4183. Now there is
"PRODUCT_ID=0x4163".
For general information:

• 0x4163=Touch
• 0x4173=Glo
• 0x4183=Mini
• 0x4193=AuraHD
• 0x4203=Aura
• 0x4213=?

Right again!

Might not be related, but maybe you can have a look at this post.

... and again!!!! (its getting ridiculous ;o)

Thank you.

[davidfor]

Originally Posted by tshering

Change in .kobo\kbmenu\usb\usb_enable.sh the product id to 0x4183. Now there is
"PRODUCT_ID=0x4163".
For general information:

• 0x4163=Touch
• 0x4173=Glo
• 0x4183=Mini
• 0x4193=AuraHD
• 0x4203=Aura
• 0x4213=?

Where did you get the last id from? Or is it just a guess for the next product?

[tshering]

Originally Posted by davidfor

Where did you get the last id from? Or is it just a guess for the next product?

0x4213 is already included in the list of versions in libnickel.so.1.0.0 of FW 3.5.0. And E606G has been added to the PCB list.

[davidfor]

Originally Posted by tshering

0x4213 is already included in the list of versions in libnickel.so.1.0.0 of FW 3.5.0. And E606G has been added to the PCB list.

I hadn't looked through libnickel for ids. But, I had seen E606G in kobo_config.sh. That returns "dragon" which suggests whatever device for id 0x4213 will be the same size and resolution as the Aura HD.

[tshering]

Originally Posted by davidfor

I hadn't looked through libnickel for ids. But, I had seen E606G in kobo_config.sh. That returns "dragon" which suggests whatever device for id 0x4213 will be the same size and resolution as the Aura HD.

My quoting E606G in this context might be misleading.

In libnickel.so.1.0.0 of FW 3.4.1 we find, a little bit off from the lists:

E60QB\x00\x00\x0000000000-0000-0000-0000-000000000370\x00\x00\x00\x000x4213

If the three values belong together, they would hint at a Glo. For additional information: E606G is in the PCB list.

But would this data from libnickel.so.1.0.0 of FW 3.1.1 mean

00000000-0000-0000-0000-000000000370\x00\x00\x00\x000x4303\x00\x00E60QB\x00\x00

if they belonged together? Additional information: E606G nowhere to find.

[davidfor]

Originally Posted by tshering

My quoting E606G in this context might be misleading.

In libnickel.so.1.0.0 of FW 3.4.1 we find, a little bit off from the lists:

E60QB\x00\x00\x0000000000-0000-0000-0000-000000000370\x00\x00\x00\x000x4213

If the three values belong together, they would hint at a Glo. For additional information: E606G is in the PCB list.

But would this data from libnickel.so.1.0.0 of FW 3.1.1 mean

00000000-0000-0000-0000-000000000370\x00\x00\x00\x000x4303\x00\x00E60QB\x00\x00

if they belonged together? Additional information: E606G nowhere to find.

Looking at 3.5.0, it has changed again. the "00000000-0000-0000-0000-000000000370" is at the end of the list of these ids. "E60QB" is still separate. I wonder this is an id used for an emulator or some sort of test bed.

Anyway, from the evidence, I'm betting on an update for the Aura HD. Or at least a device with the same size screen and resolution.

[tshering]

Originally Posted by davidfor

Looking at 3.5.0, it has changed again. the "00000000-0000-0000-0000-000000000370" is at the end of the list of these ids. "E60QB" is still separate. I wonder this is an id used for an emulator or some sort of test bed.

According to the usual pattern (cf. this), it should be the id of the next Kobo reader. Or did you refer to "E60QB"?

[davidfor]

Originally Posted by tshering

According to the usual pattern (cf. this), it should be the id of the next Kobo reader. Or did you refer to "E60QB"?

Yes, "...370" should be the id used for the next device. But, I was referring to "E60QB". It is in a separate area and has had different of the other ids associated with it. That made me wonder if it had a special purpose such as a test bed.

[tshering]

I am planning to bundle the KSM version of KBStartMenu_04.zip together with the updates and to add some improvements into a new package.
I would like to preset the font size for the menu depending on the device type. If users could provide me with the values that they think best, I will use them.
For instance, for the Touch my preferred font size is:

kobomenuFontsize=35

[embryo]

For my Glo I think 50 is Ok with me...