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

This seems to be a recurring theme:

WLAlienEventDevice: WLAlienEventTouch::checkOffset time offset diverged by more than 100 millisecond (4294888701 ns), resetting offset to 2329793188515

4294888701 looks suspiciously close to UINT_MAX, maybe this is an integer underflow issue?

07-04 01:15:11.272   261   276 W WLAlienEventDevice: WLAlienEventTouch::checkOffset time offset diverged by more than 100 millisecond (4294888701 ns), resetting offset to 2329793188515
07-04 01:15:11.708   261   361 E WificondScannerImpl: Timed out waiting for scan result from wificond
07-04 01:15:13.523  1603  1755 I OkHttpWebSocketConnection: [normal:8157010] Sending keep alive...
07-04 01:15:13.524  1603  1755 I OkHttpWebSocketConnection: [unidentified:149135018] Sending keep alive...
07-04 01:15:13.527  1603  1755 D AlarmSleepTimer: Setting an exact alarm to wake up in 19999ms.
07-04 01:15:13.527  1603  1603 W AlarmSleepTimer: Waking up.
07-04 01:15:14.217  2803  2842 D GeckoIdleService: Get idle time: time since reset 3 msec
07-04 01:15:14.218  2803  2842 D GeckoIdleService: Idle timer callback: current idle time 3 msec
07-04 01:15:14.218  2803  2842 D GeckoIdleService: next timeout 4996 msec from now
07-04 01:15:14.218  2803  2842 D GeckoIdleService: SetTimerExpiryIfBefore: next timeout 4996 msec from now
07-04 01:15:14.218  2803  2842 D GeckoIdleService: reset timer expiry to 5006 msec from now
07-04 01:15:15.571   261   276 W WLAlienEventDevice: WLAlienEventTouch::checkOffset time offset diverged by more than 100 millisecond (4295483753 ns), resetting offset to 2334088672268
07-04 01:15:15.797   261   261 E Zygote  : System zygote died with exception
07-04 01:15:15.797   261   261 E Zygote  : java.lang.IllegalArgumentException: event time must not be in the future
07-04 01:15:15.797   261   261 E Zygote  :      at com.android.server.power.PowerManagerService$BinderService.userActivity(PowerManagerService.java:4976)
07-04 01:15:15.797   261   261 E Zygote  :      at android.os.PowerManager.userActivity(PowerManager.java:1190)
07-04 01:15:15.797   261   261 E Zygote  :      at android.os.PowerManager.userActivity(PowerManager.java:1155)
07-04 01:15:15.797   261   261 E Zygote  :      at com.android.server.accessibility.AccessibilityInputFilter.handleMotionEvent(AccessibilityInputFilter.java:315)
07-04 01:15:15.797   261   261 E Zygote  :      at com.android.server.accessibility.AccessibilityInputFilter.processMotionEvent(AccessibilityInputFilter.java:297)
07-04 01:15:15.797   261   261 E Zygote  :      at com.android.server.accessibility.AccessibilityInputFilter.onInputEvent(AccessibilityInputFilter.java:237)
07-04 01:15:15.797   261   261 E Zygote  :      at android.view.InputFilter$H.handleMessage(InputFilter.java:249)
07-04 01:15:15.797   261   261 E Zygote  :      at android.os.Handler.dispatchMessage(Handler.java:106)
07-04 01:15:15.797   261   261 E Zygote  :      at android.os.Looper.loop(Looper.java:223)
07-04 01:15:15.797   261   261 E Zygote  :      at com.android.server.SystemServer.run(SystemServer.java:652)
07-04 01:15:15.797   261   261 E Zygote  :      at com.android.server.SystemServer.main(SystemServer.java:434)
07-04 01:15:15.797   261   261 E Zygote  :      at java.lang.reflect.Method.invoke(Native Method)
07-04 01:15:15.797   261   261 E Zygote  :      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
07-04 01:15:15.797   261   261 E Zygote  :      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)
07-04 01:15:15.798   261   261 D AndroidRuntime: Shutting down VM
07-04 01:15:15.798   261   261 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main

I’m testing with firefox, that’s why you see gecko-related logs. Interacting with any android app for <15s is enough to reproduce this.

1 Like

Any news about this? I can’t really use my phone after upgrading to 4.6

EDIT: Discourse says that I can’t post any more replies to this topic, so editing this one.

Hey @jonico, thanks for your reply.

I found android settings – I need to tap “Android version 11” in Settings > Android AppSupport 5 times to launch it. But I can’t figure out how I’m supposed to “select the windows form factor”. It’s nice that it’s a 30 sec trick but it’s a challenge to keep the settings app up for 30 secs. Any way to update this setting via the command line?

You need to enter in android settings, to select the windows form factor. A 30 secs trick, and all will be fine :wink:

I experience the same with ice cream. Since licorice ice cream disappeared from Berlin there’s literally no use in cows or buildings anymore.

If I remember good: These are the settings to enable



Sorry, that doesn’t help. Took two days of trials for us to activate those two, but that didn’t help at all. Keeps crashing after a few taps.

Seems like a dead end here, doesn’t it? Has anybody tried a device reset? Honestly, I’m quite hesitant to give it try, dreading all the hassle that comes with it.
Is there any news from Jolla updating Android AppSupport?
Cheers!

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.