Heyhey, I have several audio-related issues in 7.4-20260315-FP6 & I heard this forum is a good place to post about that I am wondering if others have these problems too?
Rotating the screen while having sendspin playing music in the music assistant webapp results in audio-dropouts.
A bluetooth-connection to a PC resulted in broken audio (50% silence, 40% normal playback & 10% short bursts with audio-garbage).
A bluetooth-connection to a Renault Twingo head unit resulted in no audio.
An Android Auto (WLAN) connection to the same unit resulted in “jumpy” audio, it was okay sometimes but mostly glitchy garbage.
The stock music app in Android Auto is constantly closing/crashing on launch in the cars head-unit but continues playing.
I did not have those issues with /e/OS (A15).
EDIT: Things have changed a bit, check this post for the current state.
I started with LOS 23.2 based iodeOS release/beta afaik.
If there is a way to make a full OS Backup (like backing up system- & data-partitions, etc.) I wouldn’t mind to test LOS. But because I need my phone regularly I can’t spend a lot of time switching OS and setting it all up again. So if anyone knows a way, please let me know.
It is weird that no one seems to run into this issue. I also noticed that some bugs I thought are fixed already reappeared: In almost all scenarios, rotating the screen Interrupts audio-playback for a split second. I noticed it in Youtube, Sendspin, Bandcamp, GrayJay, LOS music app and more. But sometimes it’s gone, mostly, only affecting very few apps.
I am about to update to iode-7.4-20260321-FP6, I will report if anything changed.
I updated to iode-7.4-20260321-FP6 but no changes.
I made a little cut to demonstrate the issue with the screen rotation audio-dropouts, interestingly it only happens when rotated from certain positions to certain positions.
I also created a video demonstrating 2 issues: 1. the music-app is counting up the time twice as fast as reality, causing the bar to be at the end of the song, when actually being in the middle of the song. But more importantly, the horrible bluetooth issues (audio was recorded on the receiver aka my PC).
And here is the videos waveform, the dropouts look somewhat rhythmic.
I managed to get the playback via BT to my PC working properly, it turns out it was an issue with Gnome Desktop, constantly searching for new devices while playing music, overwhelming the BT-Device. It still has a few hiccups here and there but I blame that on the rather dated BT device of my PC.
But the other issues I couldn’t solve yet. I Tried the latest iode version with Android Auto and audio is still a jumpy mess sometimes.
I don’t have an “Android Auto” capable car, so occasionally have to steal a friend’s car to do some occasional checking. There are a lot of variables in the car manufacturer and year, their implementation, etc. but I do know that some others report less than ideal experiences with wireless AA.
Wondering if your car allows testing of BT only audio connection apart from AA?
I don’t own a car but use car sharing (the Twingo is cheap ). So I use AA and Bluetooth with all kinds of cars, whenever I have another opportunity I will do tests on other vehicles and report back.
I already tried that and it did not work at all:
I should also test another music-app, iode’s stock app is extremely quirky, sometimes choking my entire system, disabling touch-control and causing heavy screen-distortion, it’s rare but pretty crazy when it happens. But maybe it’s the audio-drivers after all and that’s what messes with the music-app.
Sooo, today I connected the phone via bluetooth to the headunit of a Opel Combo and the connection seems fine, with the exception of one single 4 seconds long dropout.
However, that is when I realized the stock music-app is behaving extremely weird, with and without a bluetooth-connection about 50% of the songs just wouldn’t load. It will show the right tags but the cover-art of the last playable song, with a nonstop circling loading bar.
But that’s not even the weirdest part… I was about to screenrecord the behavior to report it but as soon as I hit record… all songs play perfectly fine suddenly. As soon as I stop the recording, it goes back to not being able to load these files.
This app is so extremely broken, I am starting to believe that it was the app the whole time that breaks bluetooth & Android Auto.
I will switch to Auxio now, see if I run into the same issues again at any point & report if anything worth mentioning happens.
I installed AA-DHU on my PC for easy Android Auto testing. I tried the stock music-app and Auxio. For some reason, both work perfectly fine, maybe a recent iode update fixed some things. But I will try to test the Twingo again asap (the car I had most issues with).
Interestingly, the issue where songs aren’t loading in the stock music-app, is gone too if Android Auto is connected and it breaks as soon as I disconnect.
btw, I tried AA with USB & WLAN but it seems like I can’t use bluetooth in this test-environment.
When all tests are done, I will summarize which issues still exist and make an updated post.
After a lot of testing, here is the current state of things:
Whats working:
Bluetooth: I tested Bluetooth with the Twingo again and realized that you have to go into a sub-sub-sub-menu where you can switch the source to Bluetooth. Really annoying but yea, it was not the phone’s fault. Same with the PC, Gnome-Desktop messed with the Bluetooth-connection as mentioned before.
Android Auto: I think that must have been fixed by an update, because I tried it with the Twingo (again), an Opel Corsa & AA-DHU (USB & wireless), everything is working fine now, doesn’t matter which music app I use.
Stock music-app (in Android Auto): I noticed the issue with the crashing AA-app has been reported at aa4mg’s git (A magisk-module that implements AA into MicroG based Systems). I don’t use it and the person who reported it doesn’t use iodeOS, so I guess that was yet another bug with the stock music app that is now fixed?
What ins’t working:
Stock music-app (visuals): I looked up the git of this app and found this bug-report & this bug-report. The visual indicators for the playback progress are tied to the animation-speed that is set within Android-settings. Since mine is set 0.5, for each passed second the indicators move 2 seconds. This was reported over a year ago and hasn’t been fixed yet, pretty disappointing tbh.
Stock music-app (playback): Some songs still don’t playback unless I start a screen-recording (for whatever reason). Instead I get a infinitely circling loading bar, no meta-data gets shown and no playback is happening.
Rotating screen: Rotating the screen still causes audio-dropouts. Not a big issue but an issue nevertheless.
I am wondering if others have these problems too?
