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

First android app after boot failes to start [answered]

asked 2019-04-28 18:58:15 +0300

dirksche gravatar image

updated 2019-04-29 13:50:18 +0300

yajo gravatar image

After booting my Xperia X the first android app I start via app icon fails. I got the small window on home screen, it circles, but after 10 seconds the window disappears, the app does not start. Android support runs, I got a status message from Conversations (android) that the app is connected with the server. If I press this status message the app starts as usual. Do I try to open with app icon it fails. But just the first time after boot. If I press the icon the second time the app opens as usual. Any ideas? This behaviour starts before updating to

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by pawel
close date 2019-04-29 20:24:10.502790



Having the same with several android apps and Xperia X on &

Spark ( 2019-04-28 19:08:34 +0300 )edit

i would assume that if.you start.android support manually.beforehand it will not.crash on first run. to me.it seems like android.support takes too.long.to start. on the second.trial it is already running, thus no crash

pawel ( 2019-04-28 19:28:50 +0300 )edit

Thats definitely not the reason. Like I wrote, android support is running.

dirksche ( 2019-04-28 20:05:47 +0300 )edit

Xperia XA2, / EA

I can confirm. Androiddalvik is already running longer time and Conversations and Threema are running in the background. The same behavior occurs even after 30 minutes of waiting time and that should be enough time to start Android.

The first start with the app icon fails, the start over the notification works.

Jolla 1 works as expected.

4carlos ( 2019-04-29 06:35:36 +0300 )edit

i.did.recheck and i think it happens when.autostart is enabled. usually.i start android.supoort.manually and dont have this issue

pawel ( 2019-04-29 07:41:16 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2019-04-29 19:30:58 +0300

Spark gravatar image

I checked a few things and I am halfway sure that this behavior is caused by @coderus "Aliendalvik Control". If it is installed and the phone is rebooted, the issue occurs. If it is deinstalled and phone is rebooted, it doesn't occur and Android apps start at first try.

Side note: I also had connectivity issues with threema (red warning symbol and error messages when trying to send) and they are also gone now. But they are not really as reproducible as the issue above...

edit flag offensive delete publish link more


Yeah. You are totally right. Great investigation. When I remove Aliendalvik Control everything works fine again. Do I install it again, the bug is back. Thanks.

Edit: Just posted a comment on Storeman.

dirksche ( 2019-04-29 19:55:30 +0300 )edit

I removed Aliendalvik Control because of this because of the hint that it probably could cure connectivity problems. What I now have is a constantly crashing Aliendalvik: It always works for some minutes and then just crashes and is being restarted regardless of I was using it or not. My battery now only lasts about half a day (I mean approx. 6 hours). Reinstalling didn't help.

Help! Aaaah!

Yo ( 2019-05-01 19:56:44 +0300 )edit

This is really strange. Aliendalvik Control is an additional app. SFOS and Aliendalvik are made to live without it. Just install it again. Nobody said anything about "connectivity problems".

dirksche ( 2019-05-01 20:48:21 +0300 )edit

Hi @dirksche - I already installed it again but it did not help.

'Spark' wrote in his answer above as a side note that his connectivity issues are gone after he uninstalled aliendalvik control. So I hoped mine would go away as well...

Yo ( 2019-05-01 23:23:13 +0300 )edit

Hups. I see. Sorry. Did you try to reinstall Android Support itself? Please don't remove. All your android apps will be removed, too!!! Just overwrite with devel-su pkcon install aliendalvik No warranty. This way works on my Xperia X. (But didn't solve the bug

dirksche ( 2019-05-02 08:43:35 +0300 )edit

Question tools



Asked: 2019-04-28 18:58:15 +0300

Seen: 278 times

Last updated: Apr 29 '19