Android 6: broken commands, crashes, caching issues(?)
See original GitHub issueThe following issues seem significantly different in nature, but also exclusive to my Android 6 Marshmello tablet, and can’t be reproduced on Android 7 or 11, so I’m bundling them here.
Specific actions that stand out:
- Every command produces the Error message
Command error Unrecognized command: /
Screenshot of command error
- Using
[enter]
on a physical keyboard (to send a message)instantly crashes the application, bringing you back to the application homescreen with the error report prompt, and even though the app updates, it can't be interacted with (like most of te OS) because of a System message "Unfortunately, Element has stopped", which will kill the app once interacted withIncidentally, you can use a command just fine by pressingScreenshots
[enter]
on a physical keyboard, which also alleviates the crash until app restart. - At some point pictures and videos in messages will stop rendering, clicking them will just display nothingness. At a later point they will stop taking additional space on the screen. They're still clickable, but the app redirects you do a gallery app, where the images are still viewable. Clearing the cache from system settings resolves the problem for a while.
- The application can start being really slow, shortly followed by a crash seemingly out of nowhere.
- Generally the application is very sluggish compared to almost any other app, though I can't tell if this is simply the technology Element is based on.
- Sometimes the rooms sidebar registers the clicks but does not redirect to any room, behavior resets when a room is opened manually
- Clicking a notification only opens the homescreen. Earlier I would also get something along the lines of
Error: malformed link
- Notifications are not automatically cleared unless all of the according rooms were visited
The tablet is rooted (but not really modified) and I can use adb if that helps to identify the issues.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Known issues with Android Studio and Android Gradle Plugin
This issue is a sticky problem that continues to happen even if you stop and restart the debugger. To fix this problem, delete...
Read more >App crashes after exiting with a "signal 6 (SIGABRT)" in ...
Android bug report: After reproducing the issue, navigate to developer settings, ensure 'USB debugging' is enabled, then enable 'Bug report ...
Read more >Fix an Android device that freezes or won't respond
Try the following steps if your phone: Freezes Stops responding Is stuck with the screen on After each step, restart your phone to...
Read more >Top 6 Methods to Fix Apps Keep Crashing on Android
3. Clearing App Cache · Open Settings on your phone · Navigate and find Apps section in your settings and tap on it...
Read more >334366 - Crashes on x86 emulator - chromium - Monorail
I am repeatedly seeing latest master Chrome crash on Android x86 ... which should do a cache lookup then call ShaderProgram::Setup().
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Would it make sense if I reproduced it in a VM?
thanks for the info, I’ve labelled this Minor/Uncommon due to the issues occurring on Android 6 but not other versions/devices
will upgrade if we get more reports or if the issues are reproducible on other android versions