We have moved to a new Sailfish OS Forum. Please start new discussions there.
2

Android still unusable (Android, XA2) [3.1.0]

asked 2019-07-20 13:05:15 +0300

ElderOrb gravatar image

updated 2019-07-23 16:21:59 +0300

jovirkku gravatar image

Update didn't improve android support at all for me. I can't launch a single android application after fresh reboot (well, from 3-4 attempt I can but then it works pretty unstable), in rare cases when I succeed applications gets killed after a few minutes of idle state. I feel like there is something completely wrong in my setup, I mean it just can't be that bad.... What can I do to troubleshoot? Is it just me or everybody experiencing behavior like this?

edit retag flag offensive close delete

Comments

1

It shouldn't work like that at all. I get an occasional Android app shutdown, but on the whole it works more or less ok.

You could go to Terminal and see what the logs show to actually happen when the expected things fail to happen. Usable commands are listed here (run with devel-su):

https://together.jolla.com/question/204859/how-to-help-debug-android-support/?answer=204871#post-id-204871

Also, the native Crest and Lighthouse apps might tell you if you're running out of memory or something and what processes may be the culprit.

teemu ( 2019-07-20 14:07:05 +0300 )edit

should work mostly but google calendar not (not yet ;) )

danfin ( 2019-07-20 14:33:54 +0300 )edit

It sounds bad as you described. Usually in these cases the most effective way is to fresh install the Android support to your device. I think there are plenty of threads with similar huge issues and re-installing has fixed it in many cases

Sakke ( 2019-07-20 14:47:41 +0300 )edit
1

Have you tried completely removing any native google accounts? Also check the size of your contacts.db. 100s of megabytes is not normal. I had this issue for the first few months, but managed to sort it out. There is a thread on it here somewhere.

attah ( 2019-07-20 16:38:47 +0300 )edit

2 Answers

Sort by » oldest newest most voted
2

answered 2019-07-21 14:54:51 +0300

ElderOrb gravatar image

Thanks a lot guys! Reinstalling android support AND recreating google account magically improved situation! I keep my fingers crossed in hope that's the end of the story.

edit flag offensive delete publish link more
0

answered 2019-07-21 15:47:37 +0300

ElderOrb gravatar image

updated 2019-07-21 16:03:29 +0300

After reboot it broken again :(

@teemu thanks for the idea with lighthouse - I feel like I know the root cause for such a behaviour: just lack of memory. What is interesting, memory seems to be consumed by contactsd. Need to dig more...

edit flag offensive delete publish link more

Comments

Oh my...

-rw-r--r-- 1 nemo privileged 777318400 Jul 21 16:03 contacts.db

773 Megabytes (which most likely memory mapped due to using WAL mode for SQLIte) for just contacts! There is something really wrong here...

ElderOrb ( 2019-07-21 16:07:16 +0300 )edit

I deleted 700 Mb contacts.db (which is completely different issue) and turned google account content sync into manual mode in hope that contacts.db will stop its growth. So contactsd stopped being memory consumer number one (lighthouse shows negative memory consumption, lol). It made android applications launching a bit more predictable, but I'm still experiencing weird issues - like android applications freeze, so I'm unable to type any text into input fields on click buttons. Not sure if this is related, but I'm observing huge CPU spikes from system_server (what is that?). I feel like I'm descending into never-ending rat hole... :(

ElderOrb ( 2019-07-21 17:06:46 +0300 )edit

Now funny part - I deleted google account completely and this made android support a period more stable (and eliminated CPU spikes from system_server). Weird.

ElderOrb ( 2019-07-21 17:23:11 +0300 )edit

Maybe something similar like this? https://together.jolla.com/question/206914/xa2-plus-carddav-and-android/

Yo ( 2019-07-21 17:27:18 +0300 )edit

You probably also need to clean up broken contacts from google.com/contacts. Until i did the problem kept coming back. The contacts.db is very much related.

attah ( 2019-07-21 18:02:55 +0300 )edit
Login/Signup to Answer

Question tools

Follow
3 followers

Stats

Asked: 2019-07-20 13:05:15 +0300

Seen: 676 times

Last updated: Jul 21 '19