element-hq
The app crashes under certain conditions.
Steps to reproduce
- Make sure the app can receive notifications and calls, and allow the app to run in the background;
- Start the app and put it in the background;
- Lock the screen and turn it off;
- Use another device to call the device;
- Observe the screen changes.
Outcome
What did you expect?
n/a
What happened instead?
Although the screen shows the incoming call screen, it disappears instantly (and then automatically returns to the lock screen). Sometimes it may be displayed twice. After that, unlock the phone and enter the app, you will find that the app prompts that it has crashed.
This problem has appeared since the update from 1.6.22 to 1.6.24. I tested 3 Different phones: OnePlus MT2110 (Pixel OS, based on Android 14): Successfully reproduced the problem Mi 9T (MIUI 12.5, based on Android 11): Successfully reproduced the problem Nokia TA-1054 (based on Andorid 8.1): Not 100% reproducible, behaves normally most of the time, occasionally behaves the same as the other 2 phones.
When the screen is unlocked (in the launcher or elsewhere), clicking on the system notification banner to open the incoming call screen will not crash the app.
OnePlus MT2110 Tried to log out and log in again (including reinstalling the app), failed to resolve the issue.
Logs have been sent via Rageshake.
Your phone model
See description above.
Operating system version
See description above.
Application version and app store
Element Android 1.6.24
Homeserver
Synapse 1.119.0
Will you send logs?
Yes
Are you willing to provide a PR?
No
This has been occurring on all the devices within our org running the updated version of element. (Pixel 7a, 7 pro, 8 pro, Samsung Note 20, S21, Tab S7, Tab S8 & Tab S9). This is made even more frustrating by the fact that if a call is placed by one party while the other does the same thing, the call just keeps ringing for both until it either times out or you cut the call.
I have the same problem, crashlog below.
Generated by AppErrorsTracking 1.3(6) Project URL: https://github.com/KitsunePie/AppErrorsTracking
[Device Model]: Pixel 8 [Display]: AP2A.240905.003 [Android Version]: 14 [Android API Level]: 34 [System Locale]: de_DE [Process ID]: 26817 [User ID]: 0 [CPU ABI]: arm64-v8a [Package Name]: im.vector.app [Version Name]: 1.6.24 [Version Code]: 40106242 [Target SDK]: 34 [Min SDK]: 21 [Error Type]: JVM [Crash Time]: 2024-12-13T19:37:51.945 [Stack Trace]: android.app.RemoteServiceException$ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{f3183a2 u0 im.vector.app/.features.call.audio.MicrophoneAccessService c:im.vector.app} at android.app.ActivityThread.generateForegroundServiceDidNotStartInTimeException(ActivityThread.java:2243) at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:2214) at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException(Unknown Source:0) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2520) at android.os.Handler.dispatchMessage(Handler.java:107) at android.os.Looper.loopOnce(Looper.java:232) at android.os.Looper.loop(Looper.java:317) at android.app.ActivityThread.main(ActivityThread.java:8592) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:878)
Confirmed that it is happening on version 1.6.24 from F-Droid. App crashes when a screen locked phone is called from another phone. Please see: https://github.com/element-hq/element-android/issues/8964
Just a note from me, I tried the Element X and the calls there do either not ring at all (only a notification about missed call arrives) or the same crash happens, i don't remember because it is a while ago, but at all case, calls are not working normally on Element X as well.
same here, this happens on both of my Android 15 and 13 phones, fixed by downgrading to 1.6.18
