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

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.

1 Like

…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

1 Like

Since yesterday, I have this Android crash problem (exception event time must not be in the future) in my Xperia 10 V :slightly_frowning_face:

all,

the following error still keeps happening on 5.0.68. can you please at least help me debug it?

10-16 16:52:39.108   263   263 E Zygote  : System zygote died with exception
10-16 16:52:39.108   263   263 E Zygote  : java.lang.IllegalArgumentException: event time must not be in the future
10-16 16:52:39.108   263   263 E Zygote  :      at com.android.server.power.PowerManagerService$BinderService.userActivity(PowerManagerService.java:4976)
10-16 16:52:39.108   263   263 E Zygote  :      at android.os.PowerManager.userActivity(PowerManager.java:1190)
10-16 16:52:39.108   263   263 E Zygote  :      at android.os.PowerManager.userActivity(PowerManager.java:1155)
10-16 16:52:39.108   263   263 E Zygote  :      at com.android.server.accessibility.AccessibilityInputFilter.handleMotionEvent(AccessibilityInputFilter.java:315)
10-16 16:52:39.108   263   263 E Zygote  :      at com.android.server.accessibility.AccessibilityInputFilter.processMotionEvent(AccessibilityInputFilter.java:297)
10-16 16:52:39.108   263   263 E Zygote  :      at com.android.server.accessibility.AccessibilityInputFilter.onInputEvent(AccessibilityInputFilter.java:237)
10-16 16:52:39.108   263   263 E Zygote  :      at android.view.InputFilter$H.handleMessage(InputFilter.java:249)
10-16 16:52:39.108   263   263 E Zygote  :      at android.os.Handler.dispatchMessage(Handler.java:106)
10-16 16:52:39.108   263   263 E Zygote  :      at android.os.Looper.loop(Looper.java:223)
10-16 16:52:39.108   263   263 E Zygote  :      at com.android.server.SystemServer.run(SystemServer.java:630)
10-16 16:52:39.108   263   263 E Zygote  :      at com.android.server.SystemServer.main(SystemServer.java:424)
10-16 16:52:39.108   263   263 E Zygote  :      at java.lang.reflect.Method.invoke(Native Method)
10-16 16:52:39.108   263   263 E Zygote  :      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
10-16 16:52:39.108   263   263 E Zygote  :      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)
10-16 16:52:39.108   263   263 D AndroidRuntime: Shutting down VM
10-16 16:52:39.109   263   263 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
10-16 16:52:39.109   263   263 E AndroidRuntime: java.lang.IllegalArgumentException: event time must not be in the future
10-16 16:52:39.109   263   263 E AndroidRuntime:        at com.android.server.power.PowerManagerService$BinderService.userActivity(PowerManagerService.java:4976)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at android.os.PowerManager.userActivity(PowerManager.java:1190)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at android.os.PowerManager.userActivity(PowerManager.java:1155)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at com.android.server.accessibility.AccessibilityInputFilter.handleMotionEvent(AccessibilityInputFilter.java:315)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at com.android.server.accessibility.AccessibilityInputFilter.processMotionEvent(AccessibilityInputFilter.java:297)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at com.android.server.accessibility.AccessibilityInputFilter.onInputEvent(AccessibilityInputFilter.java:237)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at android.view.InputFilter$H.handleMessage(InputFilter.java:249)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:223)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at com.android.server.SystemServer.run(SystemServer.java:630)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at com.android.server.SystemServer.main(SystemServer.java:424)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
10-16 16:52:39.109   263   263 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)
10-16 16:52:39.109   263   263 I AlienCrashLogger: Crash logs disabled, not dumping

1 Like

I had the same problem recently, and reading your logs, @burak, I think you have a similar cause.

The Android apps randomly die on touch input, especially press-and-hold or scrolling. Singular short touches seem to be okay.

Looking at the stack trace I now remember that the way I ended up in this situation is by registering KDE Connect as an accessibility app. Disabling its accessibility options fixed the issue (Settings → AppSupport → tap on Android version → Accessibility → KDE Connect → Use KDE Connect).

The problem is that the settings app dies before it saves the disabled state.
So the alternative option is to enable the KDE Connect shortcut on the same settings page. An icon appears at the bottom right of the screen next to the Back button. Now AppSupport dies but the icon stays. So start AppSupport and click that.

Hope this helps. @jolla staff: is it supported to have an Android app registered as an accessibility helper? if not, do you want to improve the experience by avoiding the crash? I bet this is either some clock skew or not initializing a timestamp value.

Hey everyone,

I haven’t been following the discussion lately, as I have switched to /e/ os on a Samsung Galaxy, which works like a charm. But I’m still a fan of Sailfish, of course, and will grab my phone, charge it and give it another shot, just out of curiosity. Thanks for you replies and support, very much appreciated!

Unfortunately, I can’t access Android settings. Whenever I try to scroll down to Accessibility, Android App Support crashes, hence KDE Connect is inaccessible on my phone.

@Arusekk Thanks for your hint anyway. Maybe it helps other users.