Thread: Glo Android on Glo
View Single Post
Old 11-16-2013, 03:26 AM   #87
giorgio130
Time Waster
giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.
 
Posts: 422
Karma: 289160
Join Date: May 2011
Device: Kobo Glo and Aura HD
Quote:
Originally Posted by MarekGibek View Post
I don't see the "03" value supported in Tolino's kernel source code.
It's like:




Is it working on Aura HD but with wrong resolution? If yes, it is possible to fix it by merging video driver code from Aura HD's kernel.
I've taken the value from nxt_hwconfig.c:
Code:
const char * gszDisplayResolutionA[]={"800x600","1024x758","1024x768","1440x1080"};// Display resolution .
It doesn't work though, it just turns on the frontlight and hangs. Probably some changes at kernel level are needed, maybe more in HW Config. Where did you find that info about resolution?
giorgio130 is offline   Reply With Quote