Thread: Firmware 4.31.19086
View Single Post
Old 04-16-2022, 10:21 PM   #772
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 Laen View Post
No Problems with 64gb (had ist half of a year in it) and 128gb intern or 64gb extern.
The Problems are now away after factory reset.
the Problems was only the 4 last read books on the home screen and die cover in stand by mode.
all other worked fine.
with database corrupt all would be not working.

there was other users on the web that had 128gb intern.
Are you sure those users where using a 128GB card in a Glo? I have seen that it works in a Clara HD and probably a Glo HD. But, the Glo was around a long time before these larger cards and might not have full hardware support for it. As I said, people had issues with some 32GB cards in the Glo. And as you are having problems, and you have made this change, it is something you need to check.

I can state that my Glo is working with all of the recent firmware versions. It only has a 2GB card in it. That is not the original as that failed some time ago. I only use it for testing, but, it is working correctly.

As to a corrupt database, the symptoms you describe are symptoms of a corrupt database. What happens when the database becomes corrupt depends on exactly how it is corrupt. The device can run for a long time with a corrupt database, it just can't save changes such as reading position. These will be lost either when the device is restarted or as more books are opened.
davidfor is offline   Reply With Quote