I recently spent a week in another state and the kompakt was the only device brought. It spent a lot of time in offline+ mode and unused. On the plane flight back, I put it into offline+ mode as I had done many times before on the trip, and just opened my music app. Was listening to music fine until I went to change it, and upon unlocking saw an error message saying that the app “System UI” had crashed, with the option to close the app. When I did, the screen just froze black for a few seconds, then went back to the lock screen and was fine for a bit after unlocking. However, this issue repeated itself the entire flight. It didn’t interrupt music playback so it was still usable, but it was a hassle whenever I wanted to change what was playing. At one point the phone seemed to have had enough, and while one of these errors was on screen, it just crashed and restarted, while music was still playing.
The UI crashes seemed to go away after that, so I decided to forget it, however just today it happened again twice, once in the same music app while I was driving, and another time when I was using Discord (offline+ was off in both cases). I’m aware that third party apps are technically not supported, but it’s not these apps that are crashing, it’s the literal UI. The fact that this issue has happened again today makes me worried that something is wrong with the phone.
The only thing I can think of that changed over the trip is that it went to high elevation, was stored in a decently cold room, and was dropped ~1 ft onto some gravel when I was getting out of a car (no damage, cosmetic or otherwise). Any support for this would be appreciated!
As an aside, I also noticed that there seems to be a weird ear protection feature when it comes to media playback? I was trying to listen to a song with a particularly loud section, and it kept auto pausing at exactly the same spot, in both my usual music app and Mudita’s own music app (using the exact same audio file). I realized that this happened only if the volume was on max, if I turned it one notch down it stopped happening. I was not damaging my ears with it being on max, because it was playing through my car stereo and therefore the volume the phone was set to is irrelevant. Is this an intended feature?
1 Like
@noah.p.mannion Thank you for reaching out & I am so sorry that you’re experiencing issues. Let me ask our team if there is anything you can do on your end, or if the solution is to contact our customer service for other options.
Just to confirm: you are using this Tempus music app (not Mudita’s native’s music player) when this happens?
Yes, the crashes occured both on that app and on the Discord app installed from Aurora store (play store). However they could well have occured on a mudita app too, I just don’t use any mudita apps for extended periods of time.
1 Like
@noah.p.mannion I’ve talked to the team & they said that this behavior is indicative that Kompakt might not have enough ram for whatever the sideloaded app is doing.
Would you be able to provide us with adb bugreport command output and perhaps open the report and probably see the reason.
This is very likely a combination of both, but the sideloaded apps are the primary trigger.
The symptoms strongly point to a resource/memory pressure issue caused by sideloaded apps that Kompakt’s System UI can’t gracefully handle.
This is the reason that sideloaded apps are the primary suspect:
“Tempus” + Discord are not lightweight apps. Discord in particular is a resource-heavy app with persistent background services, WebSocket connections, and notification handling. Running it on Kompakt’s constrained hardware (e-ink, limited RAM) is likely pushing the system beyond its design limits.
The fact that music continues playing while the UI crashes suggests the audio stream is handled at a lower system level, but the UI rendering layer (SystemUI/Launcher) is running out of resources or hitting an unhandled exception.
@noah.p.mannion Our team also got back to me about the audio issue that you experienced when you played the song on max. Our team says that it’s probably a hardware protection so speaker will not blow. If it is Bluetooth - it can be on headphones - and headphones send a signal to pause music.
This info could all be in the logs, if you can send those over to our support. Without adb bugreport, it’s really difficult to pinpoint.
Our support team can send you instructions on how to get these logs/bug report to us. So, please reach out to them. Their email is [email protected]
It would also help if we can get this specific music file to debug.
Please let me know if you need any more help.
@noah.p.mannion I deleted the post where you publicly linked your bug report, for security reasons. I did pass on the logs to our team & one of our tech looked over them & has this analysis:
From Kompakt side - The logs show the device’s SurfaceFlinger (the system’s screen compositor) is struggling immensely, reporting over 22,500 missed GPU frames. This indicates that the system is under heavy rendering stress when trying to display the interface.
The bug report confirms that Tempus (com.eddyizm.degoogled.tempus) is actively running and hooked into the system’s MediaDataManager. It is pushing custom playback actions and an album art bitmap (426x426) to the system interface.
If Tempus is passing bad data or causing a memory leak when the screen wakes up to render the media widget, it will crash the System UI.
Additionally, there’s a high probability - This music app bypasses Kompakt battery power-saving security
PLUS, we have to take into consideration that TEMPUS, is not simple music app - it is streaming from home server. We can see that stream caching size is 256mb which is super high, even for a traditional smartphone.
That said, the app has multiple issues reported and author is active on github: Issues · eddyizm/tempus · GitHub (121)
Thanks for the analysis, I don’t think it’s the streaming that’s causing it (cause it happened in offline+), but I’ll definitely try to find a more lightweight alternative.
1 Like
@noah.p.mannion Additionally, please reach out directly to our tech support with this if you still run into this problem. Their email is [email protected]
