OTA 25 - call history and SMS db gone
-
OK, the problem is probably solved. It seems that the problem is related to the size of history database. It probably just coincided with OTA-25 install and subsequent reboot. In my case, I have kept the history database from the very start of Ubuntu Touch.. When moving to newer phone I have always copied the call and SMS history. I use to prune the SMS history but not the call history.. Now the database probably grew to such big size that the history-daemon failed to parse the db in time (which is probably hardcoded somewhere) and timeouted. After pruning the call history using sqlite3 tool both dialer and messaging app work with the history again.
Volla
Fairphone 2
BQ Aquaris M10 FHD -
@daha said in OTA 25 - call history and SMS db gone:
Anybody knows if there are any limits imposed to history size?
There is no limit afaik, but bigger db means slower queries. But still should'nt freeze the app.
Meanwhile, after a backup you can remove the database to avoid that freeze -
@lduboeuf It did not freeze the apps. Both apps started - though after longer delay (there must be timeout hardcoded somewhere). But the history was not available (i.e. was shown empty).
-
@daha said in OTA 25 - call history and SMS db gone:
OK, the problem is probably solved. It seems that the problem is related to the size of history database. It probably just coincided with OTA-25 install and subsequent reboot. In my case, I have kept the history database from the very start of Ubuntu Touch.. When moving to newer phone I have always copied the call and SMS history. I use to prune the SMS history but not the call history.. Now the database probably grew to such big size that the history-daemon failed to parse the db in time (which is probably hardcoded somewhere) and timeouted. After pruning the call history using sqlite3 tool both dialer and messaging app work with the history again.
Just for curiosity, what the output of:
sqlite3 /home/phablet/.local/share/history-service/history.sqlite "SELECT COUNT(*) FROM text_events;" -
@lduboeuf Same here: no calls history, no sms history after the update. The result output of the above command: 16595. And from voice_events: 25868. And history-daemon is using 100% of one of the cpus.
-
This post is deleted! -
Before pruning the voice_events table:
dave@salsero:~$ sqlite3 history.sqlite.ota24
SQLite version 3.22.0 2018-01-22 18:45:57
sqlite> select count() from voice_events;
16478
sqlite> select count() from text_events;
4254 -
@daha said in OTA 25 - call history and SMS db gone:
Before pruning the voice_events table:
dave@salsero:~$ sqlite3 history.sqlite.ota24
SQLite version 3.22.0 2018-01-22 18:45:57
sqlite> select count() from voice_events;
16478
sqlite> select count() from text_events;
4254Ok, it is not so big database. Already tested with more than that without issue iirc.
-
@lduboeuf I deleted the first (oldest) 10000 records from voice_events and then restarted the phone and now I have again calls and texts history.
-
@mihael said in OTA 25 - call history and SMS db gone:
@lduboeuf I deleted the first (oldest) 10000 records from voice_events and then restarted the phone and now I have again calls and texts history.
interesting, so we have an issue when voice history is getting too big.
That is why i've done a way to clean them in the UI meanwhile.
But we could launch a clean process each time we reboot the phone to avoid that
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login