Thread: Kobo Start Menu
View Single Post
Old 07-29-2014, 09:19 AM   #431
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by tshering View Post
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.
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.
davidfor is offline   Reply With Quote