Thread: Kobo Start Menu
View Single Post
Old 07-29-2014, 08:13 AM   #430
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by davidfor View Post
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:
Code:
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
Code:
00000000-0000-0000-0000-000000000370\x00\x00\x00\x000x4303\x00\x00E60QB\x00\x00
if they belonged together? Additional information: E606G nowhere to find.

Last edited by tshering; 07-29-2014 at 08:20 AM.
tshering is offline   Reply With Quote