View Single Post
Old 09-12-2016, 09:17 AM   #4
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
I have an N905 Touch that is still running fine. It has had every firmware version on it with no problems. And I've just taken the screen from another N905 Touch that had a completely dead battery, and put it in an N905B Touch that had a broken screen. It seems to be working fine with 3.19.5761. I don't use either much, just enough to test firmware changes and so I can fiddle with them without losing anything important.

A possible problem is the kernel. Kobo didn't update the kernel in the Touch between firmware 2.6.1 and 3.16.0. There seemed to be some problems happen if you factory reset and went straight to one of the versions without the kernel. Factory resetting, installing 2.6.1 and then the later firmware seemed to be better.

Of course, there is still a problem. For a long time the firmware has had a bug in the code to install the kernel during the update. I can't remember if it affected the Mark 3 devices, but it meant the kernel didn't get installed. The code run after a factory reset did install the update. What that means is that it's possible the problem with 3.17 might be that the kernel was not updated and something in it is needed. A factory reset would fix this. And a factory reset does solve a lot of other weird problems as well.

Having said that...

My Glo started behaving like what you are describing. I eventually replaced the internal SD card with a spare I had, and it is almost like new. The card size won't matter much. I know people have used 16GB cards in the Touch, and I think 32GB cards are OK.
davidfor is offline   Reply With Quote