Android App Support does not start

REPRODUCIBILITY: always
OS VERSION: 4.5.0.25
HARDWARE: xqau52 / Xperia 10 II Dual SIM
UI LANGUAGE: en_GB
REGRESSION: yes

DESCRIPTION:

Android App Support stopped working and does not work since then.
What I have done to make it work:

  1. I have increased free space on / up to 1,2 GB
  2. I have AAS reinstalled

PRECONDITIONS:

The only activity I have done when it stopped working was to boot a SailfishOS recovery image via fastboot boot in attempt to increase root filesystem and run fsck. After booting normal OS the AAS dosn not start anymore.

STEPS TO REPRODUCE:

  1. It is hard to tell because it is still in fault state.

EXPECTED RESULT:

Android App Support does start again.

ACTUAL RESULT:

Android App Support does not start.

MODIFICATIONS:

Waydroid but both with AAS were working alternatively.

ADDITIONAL INFORMATION:

 lxc-start --rcfile=/tmp/appsupport/aliendalvik/config --lxcpath=/tmp/appsupport -n aliendalvik -F

This really looks like an lxc failure. Maybe getting more logging out of that as suggested in the last log might give more pointers. If it really was caused by filesystem resizing, then that would indicate that some filesystem corruption occurred. You could also try forcing reinstallation of the appsupport packages.

It’s really difficult to discount bad interactions between waydroid and appsupport though. That systemd-modules-load failure looks like all sorts of trouble.

1 Like

It’s the same for my phone, try to start App Support manually from Settings, this works for me.

Intermittently I’m able to get X10III App Support into a state where Start button fails to start it, and only full reboot helps.

Trying to find something other than aliendalvik.service to restart to avoid rebooting.

Are you at a long uptime ( > 25 days)? Look here.

1 Like

Tyvm, that thread is indeed exactly what I’m seeing happen.

I have removed /etc/modules-load.d/waydroid.conf file and now systemd-modules-load loads without failure but it doesn’t change a thing regarding main issue.

For me, the last time AAS didn’t start was because /home/ was too full (instead of / ).

1 Like

Please try with 4.6.0.11. It is available now for the Early Access subscribers.

1 Like

I’m going to. I’ve been waiting for this update for several months :slight_smile: but as long as it is my daily driver I will wait for official release and then report.