Thread: Aura HD Changes in Kobo Desktop 3.17
View Single Post
Old 08-28-2015, 10:46 PM   #9
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 MacEachaidh View Post
No, never said they were items in the Settings menus. But if they weren't happening before, and now they are, on the same level of firmware, then they're obviously settings of some kind on the device.
The only "setting" that has changed is the "last time recommendations" were sent to the device. The recommendations tile was already in the list of things that could be displayed. The sync from the desktop app simply updated the data and hence it was displayed.
Quote:
I doubt the database is corrupt. That's like something Customer Care would say.
Well, Customer Care would tell you to do a factory reset. And unfortunately, sometimes a reset, rebooting your computer or restarting the modem is the only way to fix things. Until whatever is the real cause gets fixed.

In this case, you described a behaviour. That behaviour is unexpected. It is not seen by most other users. When it has been reported and we looked into it, the database was corrupted. It is possible it is just the table that is used for the tiles, but, I would be very surprised if this is not the cause of the problem.
davidfor is offline   Reply With Quote