View Single Post
Old 08-28-2017, 08:53 PM   #6
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 Kobo Touch is on the same FW version as yours and I do not see this problem. What difference might there be between our devices? My Touch is a C-model, and I have installed the complete FW (not only the KoboRoot.tgz).
Good point. The Touch I see the problem on is an N905. It has the full install of the firmware I am using. I've been seeing problems like this since the change to 32bpp. The N905C is slightly different hardware, so it might only be affecting the N905 and N905B.
davidfor is offline   Reply With Quote