Best matrix client for Sailfish? (Element android app seems bust after last appstore update)

I use Element. It is essential.

It works fine on my XA2 Plus, on 4.4 and 4.5. From Aptoide store.

After eight months waiting (!) i finally got mobile data on my 10iii.
Element app from Aptoide/Fdroid (no idea which) was working fine on SFOS 4.4.
Updated to SFOS 4.5 and it was still working fine.
Decided to update my apps on the 10iii - including Element - and all of a sudden the app won’t open properly.

Behaviour:

  1. press Element icon
  2. app opens full screen with loading symbol
  3. app then minimises to the system tray
  4. clicking on the system tray mini-window tries to full screen, but bounces back to minimised
  5. rinse and repeat.
    Uninstalled and reinstalled from both Aptoide and Fdroid, same behaviour; no working element app.

Now scared to update the Element app on my old XA2 in case that borks it on that handset too!

Questions:
a) is this known behaviour, and if so is there an easy(!) fix?
b) is a a less hastle(!) matrix client that is fully compliant with Element server/chatrooms/E2E?

I’m on an emotional rollercoaster with SFOS at the moment, and I’m getting pretty tired of the experience. I simply can’t investing this much time and energy trying to get a phone to do basic phone things like talk to people…

Have you tried hydrogen? I’m not sure what is supported, tough. I use sailtrix on the phone, but I don’t use the telephony stuff. just chat.

Chat would do it.

Would you recommend it?

Thanks.

i have installed hydrogen and logged in, but it is our course doing nothing until i have verified the device via one of my other logged in devices.

element detects a new device, and offers to send a verification request, but hydrogen seems mutely indifferent to the offer.

i have also installed sailtrix and logged in, but it is our course doing nothing until i have verified the device via one of my other logged in devices.

element detects a new device, and offers to send a verification request, but sailtrix likewise seems mutely indifferent to the offer.

Even though you can’t verify the device, E2EE does work properly with Sailtrix.
Also, Sailtrix doesn’t fetch all previous messages, so you’ll receive all new messages, as long as Never send encrypted messages to unverified sessions from this session is disabled on your accounts Security & Privacy settings.

1 Like

I use hydrogen and I’m quite satisfied with it. It might miss some bells and whistles but it does what I need.

how do you open up encrypted chats in hydrogen without device verification?

You can verify hydrogen manually from your other client.

1 Like

I have just installed hydrogen and sailtrix to try and neither of them asked me for any verification,

Btw, can’t you just validate the thing via your pc?

You can export your encryption key and add it in the settings in hydrogen, afterwards, hydrogen will show as verified.
hydrogen does not support the “normal” verification methods so far.

i probably do have the same issue with element: Android app element crashes on start (4.5 ea)

using fluffychat from fdroid currently

1 Like

On one server I verified sailtrix with gomuks on a linux machine. I haven’t tried with hydrogen, but as @thigg says, you can import the keys exported from another client, like element/riot.im

1 Like

I just installed Sailfish on a new 10III. Element doesn’t work, but FluffyChat does. Both from F-Droid.

Element crashes like this:

02-26 23:49:36.462   261   299 I ALIEN   : alien processing window (de-)activation: 0. TARGET/SOURCE PKG: im.vector.app
02-26 23:49:36.463   261   299 I ALIEN   : alien relaunching app: im.vector.app
02-26 23:49:36.464   261   299 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10004000 pkg=im.vector.app cmp=im.vector.app/im.vector.application.features.Alias} from uid 1000
02-26 23:49:36.464   261   284 D EventSequenceValidator: Transition from INTENT_FAILED to INTENT_STARTED
02-26 23:49:36.475   413   413 D FakeHome: onPause
02-26 23:49:36.476   261   284 D CompatibilityChangeReporter: Compat change id reported: 135634846; UID 10040; state: DISABLED
02-26 23:49:36.476   261   284 D CompatibilityChangeReporter: Compat change id reported: 135754954; UID 10040; state: ENABLED
02-26 23:49:36.476   261   291 D CompatibilityChangeReporter: Compat change id reported: 143937733; UID 10040; state: ENABLED
02-26 23:49:36.477   261   284 D EventSequenceValidator: Transition from INTENT_STARTED to ACTIVITY_LAUNCHED
02-26 23:49:36.482   261   294 E libprocessgroup: set_timerslack_ns write failed: Operation not permitted
02-26 23:49:36.485   261   294 I chatty  : uid=1000(system) OomAdjuster identical 28 lines
02-26 23:49:36.485   261   294 E libprocessgroup: set_timerslack_ns write failed: Operation not permitted
02-26 23:49:36.493   261   276 I SurfaceFlinger: ALIEN: discarding frame without app/window (system process).
02-26 23:49:36.493    41    41 D Zygote  : Forked child process 3482
02-26 23:49:36.496   261   291 I ActivityManager: Start proc 3482:im.vector.app/u0a40 for pre-top-activity {im.vector.app/im.vector.application.features.Alias}
02-26 23:49:36.499  3482  3482 E libprocessgroup: Failed to make and chown /acct/uid_10040: Read-only file system
02-26 23:49:36.500  3482  3482 W Zygote  : createProcessGroup failed, kernel missing CONFIG_CGROUP_CPUACCT?
02-26 23:49:36.506  3482  3482 E im.vector.app: Not starting debugger since process cannot load the jdwp agent.
02-26 23:49:36.514   261   352 W OomAdjuster: Fallback pre-set sched group to default: not expected top priority
02-26 23:49:36.517   261   352 E AlienEventHub: Called isDeviceEnabled(2)
02-26 23:49:36.517   261   352 E AlienEventHub: Called isDeviceEnabled(1)
02-26 23:49:36.517   261   352 E AlienEventHub: Called isDeviceEnabled(3)
02-26 23:49:36.517   261   352 E AlienEventHub: Called isDeviceEnabled(0)
02-26 23:49:36.517   261   352 W AlienEventHub: ALIEN: getSwitchState is not supported
02-26 23:49:36.518   261   352 E AlienEventHub: Called isDeviceEnabled(2)
02-26 23:49:36.518   261   352 E AlienEventHub: Called isDeviceEnabled(1)
02-26 23:49:36.518   261   352 E AlienEventHub: Called isDeviceEnabled(3)
02-26 23:49:36.518   261   352 E AlienEventHub: Called isDeviceEnabled(0)
02-26 23:49:36.518   261   352 W AlienEventHub: ALIEN: getSwitchState is not supported
02-26 23:49:36.521   261   276 I SurfaceFlinger: ALIEN: discarding frame without app/window (system process).
02-26 23:49:36.524   261   294 E libprocessgroup: set_timerslack_ns write failed: Operation not permitted
02-26 23:49:36.525   261   294 I chatty  : uid=1000(system) OomAdjuster identical 12 lines
02-26 23:49:36.525   261   294 E libprocessgroup: set_timerslack_ns write failed: Operation not permitted
02-26 23:49:36.536  3482  3482 D NetworkSecurityConfig: Using Network Security Config from resource network_security_config debugBuild: false
02-26 23:49:36.537  3482  3482 D NetworkSecurityConfig: Using Network Security Config from resource network_security_config debugBuild: false
02-26 23:49:36.538  3482  3482 I MultiDex: VM with version 2.1.0 has multidex support
02-26 23:49:36.539  3482  3482 I MultiDex: Installing application
02-26 23:49:36.539  3482  3482 I MultiDex: VM has multidex support, MultiDex support library is disabled.
02-26 23:49:36.541  3482  3482 D org.jitsi.meet.sdk.JitsiInitializer: create
02-26 23:49:36.542  3482  3482 V fb-UnpackingSoSource: locked dso store /data/user/0/im.vector.app/lib-main
02-26 23:49:36.544  3482  3482 I fb-UnpackingSoSource: dso store is up-to-date: /data/user/0/im.vector.app/lib-main
02-26 23:49:36.544  3482  3482 V fb-UnpackingSoSource: releasing dso store lock for /data/user/0/im.vector.app/lib-main
02-26 23:49:36.548  3482  3482 D Sentry  : io.sentry.auto-init read: false
02-26 23:49:36.549  3482  3482 I Sentry  : Retrieving auto-init from AndroidManifest.xml
02-26 23:49:36.569   261   276 I SurfaceFlinger: ALIEN: new app: im.vector.app vs system
02-26 23:49:36.636  3482  3482 E REALM_JNI: jni: ThrowingException 7, No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107, .
02-26 23:49:36.636  3482  3482 E REALM_JNI: Exception has been thrown: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-26 23:49:36.636  3482  3482 D AndroidRuntime: Shutting down VM
02-26 23:49:36.637  3482  3482 E AndroidRuntime: FATAL EXCEPTION: main
02-26 23:49:36.637  3482  3482 E AndroidRuntime: Process: im.vector.app, PID: 3482
02-26 23:49:36.637  3482  3482 E AndroidRuntime: java.lang.RuntimeException: Unable to create application im.vector.app.VectorApplication: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6717)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at android.app.ActivityThread.access$1300(ActivityThread.java:237)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:106)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:223)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:7656)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
02-26 23:49:36.637  3482  3482 E AndroidRuntime: Caused by: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at io.realm.internal.OsSharedRealm.nativeGetSharedRealm(Native Method)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at io.realm.internal.OsSharedRealm.<init>(OsSharedRealm.java:11)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at io.realm.internal.OsSharedRealm.getInstance(OsSharedRealm.java:8)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at io.realm.BaseRealm.<init>(BaseRealm.java:19)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at io.realm.Realm.<init>(Realm.java:8)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at io.realm.Realm.getInstance(Realm.java:104)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at org.matrix.android.sdk.internal.auth.db.RealmPendingSessionStore.getPendingSessionData(RealmPendingSessionStore.kt:3)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at org.matrix.android.sdk.internal.auth.DefaultAuthenticationService.<init>(DefaultAuthenticationService.kt:32)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at org.matrix.android.sdk.api.Matrix.<init>(Matrix.kt:248)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl$SwitchingProvider.get(DaggerVectorApplication_HiltComponents_SingletonC.java:1696)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at dagger.internal.DoubleCheck.get(DoubleCheck.java:14)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl.injectVectorApplication(DaggerVectorApplication_HiltComponents_SingletonC.java:3)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at im.vector.app.Hilt_VectorApplication.onCreate(Hilt_VectorApplication.java:17)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at im.vector.app.VectorApplication.onCreate(VectorApplication.kt:1)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6712)
02-26 23:49:36.637  3482  3482 E AndroidRuntime:        ... 8 more
02-26 23:49:36.637  3482  3482 I AlienCrashLogger: Crash logs disabled, not dumping
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK: JitsiMeetUncaughtExceptionHandler FATAL ERROR
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK: java.lang.RuntimeException: Unable to create application im.vector.app.VectorApplication: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6717)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread.access$1300(ActivityThread.java:237)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.os.Handler.dispatchMessage(Handler.java:106)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.os.Looper.loop(Looper.java:223)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread.main(ActivityThread.java:7656)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at java.lang.reflect.Method.invoke(Native Method)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK: Caused by: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.internal.OsSharedRealm.nativeGetSharedRealm(Native Method)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.internal.OsSharedRealm.<init>(OsSharedRealm.java:11)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.internal.OsSharedRealm.getInstance(OsSharedRealm.java:8)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.BaseRealm.<init>(BaseRealm.java:19)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.Realm.<init>(Realm.java:8)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.Realm.getInstance(Realm.java:104)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at org.matrix.android.sdk.internal.auth.db.RealmPendingSessionStore.getPendingSessionData(RealmPendingSessionStore.kt:3)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at org.matrix.android.sdk.internal.auth.DefaultAuthenticationService.<init>(DefaultAuthenticationService.kt:32)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at org.matrix.android.sdk.api.Matrix.<init>(Matrix.kt:248)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl$SwitchingProvider.get(DaggerVectorApplication_HiltComponents_SingletonC.java:1696)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at dagger.internal.DoubleCheck.get(DoubleCheck.java:14)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl.injectVectorApplication(DaggerVectorApplication_HiltComponents_SingletonC.java:3)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at im.vector.app.Hilt_VectorApplication.onCreate(Hilt_VectorApplication.java:17)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at im.vector.app.VectorApplication.onCreate(VectorApplication.kt:1)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6712)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  ... 8 more
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK: 
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK: java.lang.RuntimeException: Unable to create application im.vector.app.VectorApplication: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6717)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread.access$1300(ActivityThread.java:237)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.os.Handler.dispatchMessage(Handler.java:106)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.os.Looper.loop(Looper.java:223)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread.main(ActivityThread.java:7656)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at java.lang.reflect.Method.invoke(Native Method)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK: Caused by: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.internal.OsSharedRealm.nativeGetSharedRealm(Native Method)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.internal.OsSharedRealm.<init>(OsSharedRealm.java:11)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.internal.OsSharedRealm.getInstance(OsSharedRealm.java:8)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.BaseRealm.<init>(BaseRealm.java:19)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.Realm.<init>(Realm.java:8)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at io.realm.Realm.getInstance(Realm.java:104)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at org.matrix.android.sdk.internal.auth.db.RealmPendingSessionStore.getPendingSessionData(RealmPendingSessionStore.kt:3)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at org.matrix.android.sdk.internal.auth.DefaultAuthenticationService.<init>(DefaultAuthenticationService.kt:32)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at org.matrix.android.sdk.api.Matrix.<init>(Matrix.kt:248)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl$SwitchingProvider.get(DaggerVectorApplication_HiltComponents_SingletonC.java:1696)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at dagger.internal.DoubleCheck.get(DoubleCheck.java:14)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl.injectVectorApplication(DaggerVectorApplication_HiltComponents_SingletonC.java:3)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at im.vector.app.Hilt_VectorApplication.onCreate(Hilt_VectorApplication.java:17)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at im.vector.app.VectorApplication.onCreate(VectorApplication.kt:1)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6712)
02-26 23:49:36.638  3482  3482 E JitsiMeetSDK:  ... 8 more
02-26 23:49:36.642   261  3509 I DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
02-26 23:49:36.642   261   351 W ActivityTaskManager:   Force finishing activity im.vector.app/im.vector.application.features.Alias
02-26 23:49:36.657   261   284 D EventSequenceValidator: Transition from ACTIVITY_LAUNCHED to ACTIVITY_CANCELLED
02-26 23:49:36.658  3482  3482 I Process : Sending signal. PID: 3482 SIG: 9
02-26 23:49:36.688   261  1421 I ActivityManager: Process im.vector.app (pid 3482) has died: fg  TOP 
02-26 23:49:36.688    41    41 I Zygote  : Process 3482 exited due to signal 9 (Killed)
02-26 23:49:36.689   261  1421 I ActivityTaskManager: notifySurfaceDiedIfNeeded: destroyingActivity = ActivityRecord{a54b27d u0 im.vector.app/im.vector.application.features.Alias t43 f}}
02-26 23:49:36.690   261   292 I libprocessgroup: Successfully killed process cgroup uid 10040 pid 3482 in 0ms
02-26 23:49:36.698   261  1421 E AlienEventHub: Called isDeviceEnabled(2)
02-26 23:49:36.698   261  1421 E AlienEventHub: Called isDeviceEnabled(1)
02-26 23:49:36.698   261  1421 E AlienEventHub: Called isDeviceEnabled(3)
02-26 23:49:36.698   261  1421 E AlienEventHub: Called isDeviceEnabled(0)
02-26 23:49:36.698   261  1421 W AlienEventHub: ALIEN: getSwitchState is not supported
02-26 23:49:36.699   261  1421 E AlienEventHub: Called isDeviceEnabled(2)
02-26 23:49:36.699   261  1421 E AlienEventHub: Called isDeviceEnabled(1)
02-26 23:49:36.699   261  1421 E AlienEventHub: Called isDeviceEnabled(3)
02-26 23:49:36.699   261  1421 E AlienEventHub: Called isDeviceEnabled(0)
02-26 23:49:36.699   261  1421 W AlienEventHub: ALIEN: getSwitchState is not supported
02-26 23:49:36.703   261   294 E libprocessgroup: set_timerslack_ns write failed: Operation not permitted
02-26 23:49:36.689   261  1421 I chatty  : uid=1000(system) Binder:261_B identical 1 line
02-26 23:49:36.690   261  1421 I ActivityTaskManager: notifySurfaceDiedIfNeeded: destroyingActivity = ActivityRecord{a54b27d u0 im.vector.app/im.vector.application.features.Alias t43 f}}
02-26 23:49:36.704   261   285 W WindowManager: Failed looking up window session=Session{551b695 261:1000} callers=com.android.server.wm.WindowManagerService.windowForClientLocked:5428 com.android.server.wm.WindowManagerService.removeWindow:1894 com.android.server.wm.Session.remove:193 
02-26 23:49:36.710   261   294 I chatty  : uid=1000(system) OomAdjuster identical 28 lines
02-26 23:49:36.710   261   294 E libprocessgroup: set_timerslack_ns write failed: Operation not permitted
02-26 23:49:36.711   261   276 I SurfaceFlinger: ALIEN: discarding frame without app/window (system process).
02-26 23:49:36.732   413   413 D FakeHome: onResume
02-26 23:49:36.754   261   272 W System  : A resource failed to call release. 
02-26 23:49:36.761   261   272 I chatty  : uid=1000(system) FinalizerDaemon identical 6 lines
02-26 23:49:36.761   261   272 W System  : A resource failed to call release. 
02-26 23:49:36.777   261   276 I SurfaceFlinger: ALIEN: discarding frame without app/window (system process).
02-26 23:49:37.144   261   284 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{a54b27d u0 im.vector.app/im.vector.application.features.Alias t-1 f}}
02-26 23:49:37.234   261   299 I ALIEN   : alien processing window (de-)activation: 1. TARGET/SOURCE PKG: com.jolla.home
02-26 23:49:37.235   261   299 I ALIEN   : alien moving home to foreground: com.android.systemui
02-26 23:49:37.236   261   299 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10240000 cmp=com.jolla.home/.FakeHome (has extras)} from uid 1000
02-26 23:49:36.785   261   276 I chatty  : uid=1000(system) SFThread identical 1 line
02-26 23:49:36.793   261   276 I SurfaceFlinger: ALIEN: discarding frame without app/window (system process).
02-26 23:49:37.238   261   284 D EventSequenceValidator: Transition from ACTIVITY_CANCELLED to INTENT_STARTED
02-26 23:49:37.238   413   413 D FakeHome: onPause
02-26 23:49:37.239   413   413 D FakeHome: onResume
02-26 23:49:37.241   261   284 D EventSequenceValidator: Transition from INTENT_STARTED to INTENT_FAILED
02-26 23:49:37.268   261   276 I SurfaceFlinger: ALIEN: discarding frame without app/window (system process).
02-26 23:49:37.740   261   299 I ALIEN   : already inactive

2 Likes

I could verify Sailtrix from linux desktop Element.
I fiddled a bit everywhere in Sailtrix and suddenly simplified icons showed up to validate verification.
Unfortunately, I don’t remember exactly what path I followed for that.
But fiddling a bit everywhere should be faisible for everyone ;–)

2 Likes

I used combination of Hydrogen (Jolla Store) and FluffyChat (F-Droid), then just FluffyChat, and now with 4.5.0.21 I’m back with Element (F-Droid) as it installs and runs fine again.

3 Likes

Thank you, I had the same journey.

1 Like

FluffyChat also supports multiple accounts!

Please open a bug report with your log from your posting above attached.