Just wondering whether the Sauna release note that “Scrolling in Firefox (and in some other apps relying on timestamps) is smoother” might bear any solution to our issue.
The error message is quite clear, we need advice from the sailfish team to proceed.
Right, then let’s hope they find the time to fix it.
Please, do not touch/change the Android settings. Doing so could cause unexpected phenomena.
Let AppSupport do its job.
In the APPS section of the Android settings, only one item,
“Force activities to be resizeable”,
should be enabled.This is the default after flashing Sailfish and installing AppSupport.
1 Like
A new revision of this document is available now.
A couple of problems were observed with the removal of AppSupport on 4.6.0.
1 Like
This issue popped up last week for me. Any Android App crashes shortly after launch.
The update to Sauna went fine (worked fine for a week). This issue started the moment after I’ve updated a few apps with the Aurora Store as I always do. Right after the update no android app works anymore.
Xperia 10 III, MicroG
I have uninstalled Android AppSupport from the Jolla Store. I have not rebooted or done anything else after this. So far my apps stopped crashing.
The question is in what kind of state am I?
I did not reinstall Android AppSupport and on the store it says I can install it.
You say your apps stopped crashing, but how can you run Android apps without AppSupport? Or do your Jolla apps crash too, like I have observed my Sailfish browser do on several occasions?
1 Like
That is what I do not know. The phone rebooted in my pocket and AppSupport was gone.
Reinstalled > Apps are crashing again. Cannot reproduce my earlier state by uninstalling AppSupport 
I wonder if anyone at Jolla is listening here.
1 Like
It’s so tragic, when I come to think of it. Next week, when our summer holidays end and our new school year begins, I’ll be needing my Android apps, so I had no choice but to order a Samsung Galaxy S9+ to install /e/OS on it in order to have a fully functioning phone. That’s me saying goodbye to Sailfish, I guess. Pity!
3 Likes
Any news on the issue? Also waiting for a solution
2 Likes
There is a fix for the crashing Android apps in the upcoming 4.6.0 release. It will probably not prevent the crashes of all apps but hopefully most of them.
For example, I have the ING Banking app, and opening it from the app grid works fine. I have no account so I cannot properly test the app, however, it stays up at the “Let’s get started” view and in the next couple of pages.
5 Likes
Any news about this?
3 Likes
Unfortunately latest update 4.6.0.15, doesn’t fix these issues.
My Xperia 10II with only App Support keeps also crashing all Android Apps, since update to 4.6.0.13.
…so I could only start certain Android apps with the help of the exec command via qCommand or via store start.
With 4.6.0.15, these apps now start without the detours. However, they still do not start as they did before 4.6.0.13 - but they do start. So that’s a success, at least for me.
Confirm. Same issues are here.
The last 4.6.0 release should have fixed the event timing issue above, but I suspect there are other causes for crashing. It would be very helpful if someone else experiencing this problem could gather some logcat logs or more as Android is crashing, especially around the FATAL EXCEPTION bit as it often takes a while to completely collapse with lots of other things crashing on the way.
1 Like
The output of that command is “No AppSupport instances running.”
I had Homeassistant running in the background. Used it for 20s before it crashed.
1 Like
build 5.0.0.61 device adaptation 1.0.1.38 xperia 10 iii
02-24 17:20:58.825 262 262 E Zygote : System zygote died with exception
02-24 17:20:58.825 262 262 E Zygote : java.lang.IllegalArgumentException: event time must not be in the future
02-24 17:20:58.825 262 262 E Zygote : at com.android.server.power.PowerManagerService$BinderService.userActivity(PowerManagerService.java:4976)
02-24 17:20:58.825 262 262 E Zygote : at android.os.PowerManager.userActivity(PowerManager.java:1190)
02-24 17:20:58.825 262 262 E Zygote : at android.os.PowerManager.userActivity(PowerManager.java:1155)
02-24 17:20:58.825 262 262 E Zygote : at com.android.server.accessibility.AccessibilityInputFilter.handleMotionEvent(AccessibilityInputFilter.java:315)
02-24 17:20:58.825 262 262 E Zygote : at com.android.server.accessibility.AccessibilityInputFilter.processMotionEvent(AccessibilityInputFilter.java:297)
02-24 17:20:58.825 262 262 E Zygote : at com.android.server.accessibility.AccessibilityInputFilter.onInputEvent(AccessibilityInputFilter.java:237)
02-24 17:20:58.825 262 262 E Zygote : at android.view.InputFilter$H.handleMessage(InputFilter.java:249)
02-24 17:20:58.825 262 262 E Zygote : at android.os.Handler.dispatchMessage(Handler.java:106)
02-24 17:20:58.825 262 262 E Zygote : at android.os.Looper.loop(Looper.java:223)
02-24 17:20:58.825 262 262 E Zygote : at com.android.server.SystemServer.run(SystemServer.java:630)
02-24 17:20:58.825 262 262 E Zygote : at com.android.server.SystemServer.main(SystemServer.java:424)
02-24 17:20:58.825 262 262 E Zygote : at java.lang.reflect.Method.invoke(Native Method)
02-24 17:20:58.825 262 262 E Zygote : at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
02-24 17:20:58.825 262 262 E Zygote : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)
02-24 17:20:58.825 262 262 D AndroidRuntime: Shutting down VM
02-24 17:20:58.825 262 262 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
02-24 17:20:58.825 262 262 E AndroidRuntime: java.lang.IllegalArgumentException: event time must not be in the future
02-24 17:20:58.825 262 262 E AndroidRuntime: at com.android.server.power.PowerManagerService$BinderService.userActivity(PowerManagerService.java:4976)
02-24 17:20:58.825 262 262 E AndroidRuntime: at android.os.PowerManager.userActivity(PowerManager.java:1190)
02-24 17:20:58.825 262 262 E AndroidRuntime: at android.os.PowerManager.userActivity(PowerManager.java:1155)
02-24 17:20:58.825 262 262 E AndroidRuntime: at com.android.server.accessibility.AccessibilityInputFilter.handleMotionEvent(AccessibilityInputFilter.java:315)
02-24 17:20:58.825 262 262 E AndroidRuntime: at com.android.server.accessibility.AccessibilityInputFilter.processMotionEvent(AccessibilityInputFilter.java:297)
02-24 17:20:58.825 262 262 E AndroidRuntime: at com.android.server.accessibility.AccessibilityInputFilter.onInputEvent(AccessibilityInputFilter.java:237)
02-24 17:20:58.825 262 262 E AndroidRuntime: at android.view.InputFilter$H.handleMessage(InputFilter.java:249)
02-24 17:20:58.825 262 262 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
02-24 17:20:58.825 262 262 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
02-24 17:20:58.825 262 262 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:630)
02-24 17:20:58.825 262 262 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:424)
02-24 17:20:58.825 262 262 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
02-24 17:20:58.825 262 262 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
02-24 17:20:58.825 262 262 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)
02-24 17:20:58.826 262 262 I AlienCrashLogger: Crash logs disabled, not dumping
02-24 17:20:58.827 262 262 I DropBoxManagerService: add tag=system_server_crash isTagEnabled=true flags=0x2
02-24 17:20:58.834 262 262 I Process : Sending signal. PID: 262 SIG: 9
02-24 17:20:58.909 682 682 E DisplayEventDispatcher: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.909 1553 2424 E DisplayEventDispatcher: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.909 675 675 E DisplayEventDispatcher: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.909 682 772 E OpenGLRenderer: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.910 1553 1553 E DisplayEventDispatcher: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.910 1553 2379 E OpenGLRenderer: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.910 413 578 E OpenGLRenderer: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.910 413 413 E DisplayEventDispatcher: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.910 413 413 E DisplayEventDispatcher: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.910 53 53 I lowmemorykiller: lmkd data connection dropped
02-24 17:20:58.911 675 2428 E OpenGLRenderer: Display event receiver pipe was closed or an error occurred. events=0x9
02-24 17:20:58.911 53 53 I lowmemorykiller: closing lmkd data connection
… omitted log noise showing the jvm is being shut down