Android App Support does not start

[kan_ibal]

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:

@kan_ibal

Additional information:

[root@Xperia10II system]# systemctl --failed
  UNIT                         LOAD   ACTIVE SUB    DESCRIPTION              
● aliendalvik.service          loaded failed failed Alien Dalvik             
● lxc@multi-user.service       loaded failed failed LXC Container: multi-user
● systemd-modules-load.service loaded failed failed Load Kernel Modules      

[root@Xperia10II system]# systemctl status systemd-modules-load
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2023-12-26 11:54:25 CET; 13min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 27908 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 27908 (code=exited, status=1/FAILURE)

Dec 26 11:54:25 Xperia10II systemd-modules-load[27908]: Failed to lookup alias 'veth': Function not implemented
Dec 26 11:54:25 Xperia10II systemd-modules-load[27908]: Failed to lookup alias 'xt_CHECKSUM': Function not implemented
Dec 26 11:54:25 Xperia10II systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Dec 26 11:54:25 Xperia10II systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Dec 26 11:54:25 Xperia10II systemd[1]: Failed to start Load Kernel Modules.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

[root@Xperia10II system]# systemctl status aliendalvik.service
● aliendalvik.service - Alien Dalvik
   Loaded: loaded (/usr/lib/systemd/system/aliendalvik.service; enabled; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/aliendalvik.service.d
           └─01-prevent-start.conf, 01-user.conf
   Active: failed (Result: protocol) since Tue 2023-12-26 11:59:21 CET; 8min ago
  Process: 29130 ExecStopPost=/usr/libexec/appsupport/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
  Process: 29081 ExecStart=/usr/libexec/appsupport/start-aliendalvik.sh (code=exited, status=0/SUCCESS)
  Process: 29067 ExecStartPre=/bin/sh -c while ! systemctl-user is-active lipstick.service 1>/dev/null; do sleep 1; done (code=exited, status=0/SUCCESS)
 Main PID: 29081 (code=exited, status=0/SUCCESS)

Dec 26 11:59:20 Xperia10II start-aliendalvik.sh[29081]: lxc-start: aliendalvik: start.c: do_start: 1291 Failed to setup container "aliendalvik"
Dec 26 11:59:20 Xperia10II start-aliendalvik.sh[29081]: lxc-start: aliendalvik: sync.c: sync_wait: 36 An error occurred in another process (expected sequence number 3)
Dec 26 11:59:20 Xperia10II start-aliendalvik.sh[29081]: lxc-start: aliendalvik: start.c: __lxc_start: 2053 Failed to spawn container "aliendalvik"
Dec 26 11:59:20 Xperia10II start-aliendalvik.sh[29081]: lxc-start: aliendalvik: tools/lxc_start.c: main: 308 The container failed to start
Dec 26 11:59:20 Xperia10II start-aliendalvik.sh[29081]: lxc-start: aliendalvik: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options
Dec 26 11:59:20 Xperia10II start-aliendalvik.sh[29081]: cat: can't open '/home/.android/data/alien_boot_completed': No such file or directory
Dec 26 11:59:20 Xperia10II stop-aliendalvik.sh[29130]: lxc-attach: aliendalvik: attach.c: get_attach_context: 403 Failed to get init pid
Dec 26 11:59:20 Xperia10II stop-aliendalvik.sh[29130]: lxc-attach: aliendalvik: attach.c: lxc_attach: 1430 Failed to get attach context
Dec 26 11:59:21 Xperia10II systemd[1]: aliendalvik.service: Failed with result 'protocol'.
Dec 26 11:59:21 Xperia10II systemd[1]: Stopped Alien Dalvik.

[root@Xperia10II system]# systemctl status lxc@multi-user.service
● lxc@multi-user.service - LXC Container: multi-user
   Loaded: loaded (/usr/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2023-12-26 10:24:51 CET; 1h 42min ago
     Docs: man:lxc-start
           man:lxc
  Process: 5852 ExecStart=/usr/bin/lxc-start -F -n multi-user (code=exited, status=1/FAILURE)
 Main PID: 5852 (code=exited, status=1/FAILURE)

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

@kan_ibal

lxc-start: aliendalvik: utils.c: lxc_can_use_pidfd: 1772 Kernel does not support pidfds
lxc-start: aliendalvik: utils.c: safe_mount: 1198 Device or resource busy - Failed to mount “proc” onto “/usr/lib64/lxc/rootfs/proc”
lxc-start: aliendalvik: conf.c: lxc_mount_auto_mounts: 801 Device or resource busy - Failed to mount “proc” on “/usr/lib64/lxc/rootfs/proc” with flags 14
lxc-start: aliendalvik: conf.c: lxc_setup: 4094 Failed to setup first automatic mounts
lxc-start: aliendalvik: start.c: do_start: 1291 Failed to setup container “aliendalvik”
lxc-start: aliendalvik: sync.c: sync_wait: 36 An error occurred in another process (expected sequence number 3)
lxc-start: aliendalvik: start.c: __lxc_start: 2053 Failed to spawn container “aliendalvik”
lxc-start: aliendalvik: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: aliendalvik: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options
cat: can’t open ‘/home/.android/data/alien_boot_completed’: No such file or directory

[abranson]

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.

[jollajo]

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