[4.6.0.13] Android AppSupport crashes at any activity after upgrade to Sauna

REPRODUCIBILITY:
OS VERSION: 4.6.0.13
HARDWARE: Sony Xperia XA2 Ultra
UI LANGUAGE: English
REGRESSION:

DESCRIPTION:

Android AppSupport stops, crashing all open Android apps, after any kind of input within an open Android app after upgrade to Sauna 4.6.0.13. Andorid AppSupport Security patch level is 05/12/2023.

While the upgrade process itself ran smoothly, after the upgrade Android apps can no longer be used as any attempt to operate the app, be it scrolling, selecting, text input, etc., will cause Android AppSupport to crash. This behavior is inconsistant, as some input will be tolerated, while any further touch of the screen will then crash AppSupport.

Has anyone encountered similar issues after upgrade?

PRECONDITIONS: Android App Support must be running.

STEPS TO REPRODUCE:

  1. Open Android app
  2. Try to scroll on page or reply to a message (e.g. in Signal app)

EXPECTED RESULT:

App should stay open and execute command

ACTUAL RESULT:

App crashes after AppSupport shuts down, restarting immediately

MODIFICATIONS:

no modifications

ADDITIONAL INFORMATION:

4 Likes

Did your update go well?
Do you have anything like google services or microg installed?

1 Like

Thanks for your reply. Update went well, no issues there. And no, no google services installed. If I don’t touch an open Android app, it’ll just sit there. As soon as I try to scroll though, it’ll crash.

1 Like

For me is the same, sfos 4.6.0.13 with gapps on xperia 10Iii. Everything is very slow and app support crashes if I open any app.

1 Like

Maybe uninstalling and reinstalling Android Support might help. But this is just an idea.
You might want to backup some Android data before doing so, start with one app and successively reinstall backups and other apps.

2 Likes

Hi WT.Sane,
thanks for your suggestion to reinstall AppSupport. I had totally forgotten that it is not an integrated module of the OS. Unfortunately, reinstalling didn’t help, but on the other hand, my data stayed intact, so no need to reconfigure the Android apps on my phone.
It is beginning to dawn on me that resetting the device might be the only option, though, but I’m still pretty hesitant. Maybe someone will come up with a brilliant fix :smile:, so I’ll just wait a little longer and try my luck with exercising some patience.
Are shults and me the only two on the planet experiencing this frustrating issue?

1 Like

How much free space do you have in the root partition / overall?

As a last resort before reflashing the phone, you could try to delete Android App Support the brutal way (if you didn’t already), as described in the documentation:

1 Like


I tried freeing up as much space as I could. Here’s the result. I’ll try deleting app support the hard way once I’m back home from my class trip. Don’t want to fiddle too much as long as I need the phone here. I do appreciate your assistance very much. Thanks, I’ll let you know how it worked out.

1 Like

Good morning everyone,
I have the same problem too…
I did a total flash of Sauna just yesterday, on an Xperia 10 II dual sim.
In particular, I notice that WhatsApp crashes and Nextcloud Notes doesn’t keep the note I’m viewing open if I close the screen.
I have microG installed, I just removed it, let’s see if the situation improves…

1 Like

Hello everybody,
I have the same issue on my X10 dual sim. All Android Apps can be started but crash after any action within it. The app support seems to be restarted immediately.
I have microG installed and around 600 MB free space on System data about 25 GB on User data.

1 Like

I also have this problem, or very similar, (as I have mentioned in another thread) although it is much worse on my Xperia 10 iii than it is on my XA2 Plus. sometimes you have to try and start an Android app 5 or 6 times before it will open and work successfully.

1 Like

I have a similar problem on my xa2 plus, I did a reinstall due to the increase in memory, but sometimes when opening an application the App support message appears starting, before it happened only with here maps or google maps now it happens very frequently with any application

1 Like

We would appreciate getting some logs from the phones having problems reported in this thread.

Use the phone. As soon as you have seen the problem occur, run the following commands.
Please mention the date and time when this happened to make it easier to read the logs.

devel-su
/usr/libexec/droid-hybris/system/bin/logcat > sailfish-logs.txt
appsupport-attach /system/bin/logcat > android-logs.txt
appsupport-attach /system/bin/pm list packages | sort > android-packages.txt
rpm -qa | grep -E 'alien|apkd|appsupport' > appsupport-rpms.txt
journalctl -ab --no-pager > journal.txt

tar -cf appsupport.tar sailfish-logs.txt android-logs.txt android-packages.txt appsupport-rpms.txt journal.txt

If you do not want to publish your appsupport.tar here make a ticket at https://jolla.zendesk.com/hc/en-us/requests/new.

Thank you!

2 Likes

Hi,

Is this Collect Persistent Logs | Sailfish OS Documentation help article still relevant? I have been using it to collect logs.

1 Like

It is relevant and probably even better than those ^.

2 Likes

This is probably the most helpful part. This should be run before a crash, and should only return when AppSupport has shut down.

3 Likes

Thanks everyone for your support. Unfortunately, I haven’t succeeded generating log-entries. Is there anyone more tech-savvy out there with the same issue who could post a log after AppSupport crashes on their phone?

1 Like

I also have a similar problem. Since the update to “Sauna”, the last functioning banking app also crashes. As soon as I enter my PIN in the ING app, the program crashes.

I actually wanted to release another device for the move to another system. Now I have to wait for a release pin by post. Although I’ve been using Sailfish since Jolla 1, it just confirms to me that there’s no future in this. All the important functions that you unfortunately have to rely on today via smartphone don’t work.

2 Likes

You can succesfully launch the ING app from the terminal, see [4.6.0.11] App Support, app grid - ING Banking App and others are killed (closed) after entering PIN

In the terminal, you need to enter:

apkd-launcher de.ingdiba.bankingapp.apk de.ingdiba.bankingapp/com.ing.mobile.diba.startup.SplashActivity

Good luck!

2 Likes
07-04 00:29:45.046  2616  2654 D GeckoIdleService: Get idle time: time since reset 13 msec
07-04 00:29:45.046  2616  2654 D GeckoIdleService: Idle timer callback: current idle time 13 msec
07-04 00:29:45.046  2616  2654 D GeckoIdleService: next timeout 4987 msec from now
07-04 00:29:45.046  2616  2654 D GeckoIdleService: SetTimerExpiryIfBefore: next timeout 4987 msec from now
07-04 00:29:45.046  2616  2654 D GeckoIdleService: reset timer expiry to 4997 msec from now
07-04 00:29:46.027   260   260 E Zygote  : System zygote died with exception
07-04 00:29:46.027   260   260 E Zygote  : java.lang.IllegalArgumentException: event time must not be in the future
07-04 00:29:46.027   260   260 E Zygote  :      at com.android.server.power.PowerManagerService$BinderService.userActivity(PowerManagerService.java:4976)
07-04 00:29:46.027   260   260 E Zygote  :      at android.os.PowerManager.userActivity(PowerManager.java:1190)
07-04 00:29:46.027   260   260 E Zygote  :      at android.os.PowerManager.userActivity(PowerManager.java:1155)
07-04 00:29:46.027   260   260 E Zygote  :      at com.android.server.accessibility.AccessibilityInputFilter.handleMotionEvent(AccessibilityInputFilter.java:315)
07-04 00:29:46.027   260   260 E Zygote  :      at com.android.server.accessibility.AccessibilityInputFilter.processMotionEvent(AccessibilityInputFilter.java:297)
07-04 00:29:46.027   260   260 E Zygote  :      at com.android.server.accessibility.AccessibilityInputFilter.onInputEvent(AccessibilityInputFilter.java:237)
07-04 00:29:46.027   260   260 E Zygote  :      at android.view.InputFilter$H.handleMessage(InputFilter.java:249)
07-04 00:29:46.027   260   260 E Zygote  :      at android.os.Handler.dispatchMessage(Handler.java:106)
07-04 00:29:46.027   260   260 E Zygote  :      at android.os.Looper.loop(Looper.java:223)
07-04 00:29:46.027   260   260 E Zygote  :      at com.android.server.SystemServer.run(SystemServer.java:652)
07-04 00:29:46.027   260   260 E Zygote  :      at com.android.server.SystemServer.main(SystemServer.java:434)
07-04 00:29:46.027   260   260 E Zygote  :      at java.lang.reflect.Method.invoke(Native Method)
07-04 00:29:46.027   260   260 E Zygote  :      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
07-04 00:29:46.027   260   260 E Zygote  :      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)
07-04 00:29:46.027   260   260 D AndroidRuntime: Shutting down VM
07-04 00:29:46.029   260   260 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main

package list:

aliendalvik-configs-11.0.128-1.25.1.jolla.aarch64
feature-alien-0.4.2-1.2.3.jolla.aarch64
appsupport-configs-user-11.0.128-1.25.1.jolla.aarch64
apkd-plugin-notifications-fdo-ext-1.0.4-1.1.1.jolla.aarch64
alienaudioservice-plugin-sailfish-1.6.0-1.7.1.jolla.aarch64
apkd-plugin-geo-qtpositioning-1.0.0-1.1.3.jolla.aarch64
apkd8-android-settings-11.0.0.69.1-1.22.1.jolla.aarch64
appsupport-config-generator-1.10.10-1.10.1.jolla.aarch64
ofono-alien-binder-plugin-0.3.2-1.4.1.jolla.aarch64
appsupport11-system-unprivileged-11.0.0.74.46.3-1.7.1.jolla.aarch64
apkd-plugin-media-mpris-1.0.0-1.1.1.jolla.aarch64
aliendalvik-1.8.0-1.5.1.jolla.aarch64
apkd8-l10n-all-translations-1.85.1-1.11.1.jolla.noarch
libapkd-1.10.0-1.5.1.jolla.aarch64
alienkeyboardservice-0.12-1.2.4.jolla.aarch64
libalienaudioservice-1.24.1-1.10.1.jolla.aarch64
alienaudioservice-plugin-pulseaudio-1.24.0-1.11.1.jolla.aarch64
apkd8-11.0.0.69.1-1.22.1.jolla.aarch64
alienaudioservice-1.29.0-1.13.1.jolla.aarch64
apkd-plugin-permissions-sfos-1.2.0-1.3.1.jolla.aarch64

is this enough?