Android App Support will not load

asked 2020-01-24 16:59:41 +0300

1428 ●27 ●32 ●43

http://www.justpurefact.c...

updated 2020-01-25 19:30:21 +0300

This suddenly happened. I restarted my phone as the Android App (Waze) wasn't getting a connection. The shutdown locked up and I had to hard reboot. Afterwards Android App Layer won't work. Start/Stop buttons both are disabled in the Settings menu, and every time I try to start an Android app, its says starting App Layer, and spins for a while with the App showing the loading animation and then crashed. Sony XA2 Plus 3.2.1.20

Things I've tried: Rebooting, Shutting Off and On, Uninstalling/Reinstalling Android Layer, Airplane mode and starting an app (still does not work). I've also tried multiple apps, Aptoide, Waze, Here, etc. Native Apps work just fine.

edit retag flag offensive close delete

Comments

Confirmed service isn't running using systemctl.

Ran script /usr/bin/start-aliendalvik.sh and it says "info systemd again..." repeatedly and then "Couldn't deliver notify message to systemd".

SValmont ( 2020-01-24 23:30:40 +0300 )edit

1

I already had this phenomenon on my Sony Xperia 10 Dual.
But I think this is the normal first loading time of the android system. If I wait it will start always. Often start then also the apps they I try to start allown. I think that depends on wich kind of real restart you make.
A deep restart or only a soft restarts e.g. restart lipstick.
Maybe with a deep restart added the time for entering the pins and you may not notice it ...
If you have install patchmanager yo have also a restart of the lipstick and have to wait some minutes of android suport.

Ralf ( 2020-01-25 13:35:18 +0300 )edit

2

answered 2020-01-29 08:25:21 +0300

0xe4524ffe
173 ●3 ●5 ●10

Also had this problem on XA2 Plus, Sailfish OS 3.2.1.20.

TLDR: Probably CPU doesn't have enough power on device startup, and services reaching timeout

The problem solved itself, after I edited \vendor\etc\rqbalance.config to set minimum online cpu cores to 8, essentialy disabling cpu core hotplugging(It causes weird bugs and hotplugging actually is disabled on stock sony android), and set cpu frequency scaling governor to ondemand, with io_is_busy enabled by editing \vendor\etc\init\init.nile.pwr.rc. And also fixed some other things in init files and \vendor\etc\thermalmanager.xml(There's a lot of wrong settings, 'cause those are from AOSP, not Sony(though sony f's up pretty frequently too), plus some things needed tweaking after I changed governor). Haven't had that problem ever since.

It seemed like the problem was that there were not enough cpu power on device startup, and Android app support was crashing, or most likely some services were exceeding timeout value, and their start was aborted. I don't remember seeing anything in logs, though, so I can't say for sure what was the actual source of the problem.

PS: Had to read a lot of kernel source code, while trying to do that. There is almost no mention of these systems on the internet. Honestly, It would be much easier if Jolla set up community wiki pages(like, real ones, not on forum).

edit flag offensive delete publish link

Comments

Did you set the balanced min cpus to 8? There was performance, battery save, balanced, etc.

SValmont ( 2020-01-29 16:49:03 +0300 )edit

Also I'm assuming io_is_busy 1 = enabled?

SValmont ( 2020-01-29 19:27:35 +0300 )edit

I did try the changes you outlined and that didn't fix it. Any ideas on what else to try look for? That the message comes up telling me android is loading seems to be telling, as I haven't seen that before in the UI (at least for a prolonged period of time). But you are right it appears to be timing out with the service not being started.

SValmont ( 2020-01-29 19:31:00 +0300 )edit

1

Yes, io_is_busy=1. I set it to min 8 cpus in all profiles. Here's how those files look on my XA2 Plus now: rqbalance_config.xml, init.nile.pwr.rc and thermanager.xml. You can try to look in android logd or to get status of systemd services, systemctl usually also shows service log in addition to status. I assume you already looked at dmesg output.

0xe4524ffe ( 2020-01-30 06:53:01 +0300 )edit

Just went through all of this. Only thing else I can do is go line by line. Still the aliendalvik.service fails.

SValmont ( 2020-01-30 23:13:38 +0300 )edit

0

answered 2020-01-25 21:23:05 +0300

ksandom
341 ●5 ●8 ●10

This has happened to me as well. My apps magically all started the moment I started wifi and got a wifi connection.

On previous versions, my methods of getting the apps to work were more convelouted. For a previous version, people narrowed it down to Aliendalvek control. Removing that worked for most people, but not others.I don't think that is relevant this time. But it hasn't happened many times to me yet.

edit flag offensive delete publish link

Comments

What are the convuluted methods? Wifi didn't work.

SValmont ( 2020-01-26 00:20:56 +0300 )edit

My gut feeling is that this isn't going to help you, but here goes. I stopped needing this from 3.2.0.

After a fresh reboot, I'd wait a few minutes. Nothing would work before that.
Some apps could be the first to be started, while others couldn't. I used Facebook messenger. Once that successfully loaded, other apps like whatsapp or firefox could be started.

All of this is voodoo talk, but what I think was going on is that there was too much to load at once and apps that took too long to load where hitting a timeout before they could finish starting.

Another possibility is memory pressure.

But like I say, I don't think these "observations" are still relevant on 3.2.1.20. But maybe they lead to something.

ksandom ( 2020-01-26 01:30:09 +0300 )edit

Also tried removing androiddalvek package with the terminal.

SValmont ( 2020-01-28 08:24:03 +0300 )edit

Android App Support will not load

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

Android App Support will not load

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions