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?
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?
1 Like
You need to enter in android settings, to select the windows form factor. A 30 secs trick, and all will be fine 
1 Like
I experience the same with ice cream. Since licorice ice cream disappeared from Berlin there’s literally no use in cows or buildings anymore.
2 Likes
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.
1 Like
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!
1 Like
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.