Quote:
Originally Posted by HarryT
It's misbehaving again. I've emailed you the debug log.
|
I have looked over the debug log and it really appears that there is some background task running on your device from time to time. What I see is:
- Using 3.4.1: the database times to open the grouping drawer average around 6 seconds. There were not many of these samples in the debug log.
- Using 3.4.2 on the 9th: at noon, the average was around 6 seconds. At 17h there are several in excess of 25 seconds, then 4 with an average of 6 seconds. At 18:30 we jump up to an average of nearly 25 seconds, but several are at 6 seconds. At 19:30 there are several at 6 seconds, jumps up in excess of 20 seconds, then falls back to 6 seconds.
- On the 10th at noon we are back to 6 seconds. At 17:35 we are still at 6 seconds. At 17:40 we see 13 seconds and 21 seconds, with an average of around 18 seconds.
What this says is that a) V3.4.1 and V3.4.2 aren't that different, and b) the same version of CC is seeing wildly database access different times. The only reason I can see for this is that something else on your phone comes to life from time to time, consuming memory. Do you have any cloud sync programs or other background apps running?
It is possible, perhaps even probable, that the database created by an upgrade is not as efficient as one created from scratch. In particular, 3.4.1 added a column to the main database table, and I doubt that Android's database manager would do that operation in an optimal fashion. What I leading to is that it might be a good idea to uninstall CC, reinstall it, and then resend the books. This would create a database where all the storage for a given row is together. I totally understand why you might not want to do such an operation, but it might help.
Other than looking for background tasks and rebuilding the database, I don't have any suggestions. Sometimes CC database ops are fast(er) and sometimes they are not, and I am not sure what I can do about that.
Ahhh: one idea: if you are using user-defined sorts then sort by title, then author, then title. That will reinitialize the sorts to something basic, simplifying the database queries. If that helps then I have an idea of something I can do.