-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuttering audio #6
Comments
I used an iPhone 15 (non-Pro) in my vehicle with EHU32 and tested it extensively since I knew that the underlying library for handling A2DP audio has had problems with iOS devices in the past but never had any issues. Found something else here with a suggested fix: SOLVED Poor quality audio from IOS devices. #582 Made a build of EHU32 v0.9.3 with the data out pin changed for you to test (also compiled with updated libraries). Can't really test it on my hardware. Also please describe your board, is it the type-C version? What's written on the metal shielding? What USB-UART chip is on the board, is it the CP2102 or WCH something or other? |
I’ll try out this version and report back, I can’t tell what is written anymore because the esp32 is glued into a box and is upside down. I do remember the UART chip being an obvious clone though. Safe to say the rest of the board is likely chinesium. I have to say though, amazing work, I hate aftermarket radios and this is just perfect, almost jumped out of my chair when I found this. |
Got myself an older iPhone for testing but I would appreciate it very much if you could take the time to describe/photograph the board in detail, I've got many variants in my collection but testing each one of them is not feasible, so I want to narrow it down to the problematic ones and work out a fix (mainly for other people attempting to put this together). I'm in similar boat here since this project is partially a product of my disdain for aftermarket headunits which look out of place and don't integrate with the car like the stock headunits do. Also, how often do you see Aux displayed? I'm still in the process of refining the display blocking/overwriting logic but you're the first person with anything other than CD30 sharing feedback so I'd like to ask. I do most of the development on CD30MP3 with GID and EHU32 works seamlessly with that but each time I test new code with CD70 there's always something that doesn't work exactly right, still getting Aux to show up here and there (probably RDS and navi data getting through and messing with my logic). Not to mention that debugging is difficult when you've got to focus on driving. Hope you understand my frustration here. |
Aux does randomly pop up yeah, I haven’t noticed a pattern though. Sometimes it doesn’t pop up for a long time, sometimes the text goes blank for half a second and goes back to normal. Aside from that, having steering wheel control on bluetooth is amazing, I should be able to provide you with pictures of the ESP tomorrow. I also tried an iPhone 11 but it exhibited the same audio issue. Looked 100% like a Bluetooth issue, I muted the iPhone but audio was still playing. |
I might try to extend the buffer data to support up to 512 chars in some later versions. As for ÿ showing up that's rather strange, unfortunately I don't have a CID on hand to investigate.
In the next release I'll be moving away from reading data from ECC and read all the data (including voltage) from the display. Hopefully that will work better across different models
That's actually proper behavior since I have forced the audio receiver to NOT apply any volume control and iOS respects that, unfortunately android's behavior varies with manufacturer and once it detects no volume control it applies the volume correction locally before sending the data off to the bluetooth receiver. Not only does that reduce the audio quality (lower dynamic range) but also can result in clipping (as you have observed with your Nokia smartphone). Not much to be done about that other than setting the volume to 50% and hope no correction is applied. |
Thanks for the photos, tried the same album/title/artist (from apple music) with GID but it works fine here but gets cut off earlier. Can you tell me what's the GM part number for that display? I vaguely remember that some vectras and signums had an early CID model (siemens vdo too) that only has two lines of data on the vehicle tab (the rightmost one), is it that one? |
Hi, swapped the pin and flashed the software, no change in iOS but Android now plays fine upto like 80% volume. Display is 24461297. EDIT: not sure if it’s due to the source volume change, but the dynamic range? (idk how to call it, the quality is much better when there is a lot of different sounds going on) is much better on the software you sent. |
Right, thanks for trying it out and all the feedback, I'll do some testing with the iPhone and different ESP32 boards over the upcoming weekend. Also, if you have some spare time and any other ESP32 boards at your disposal you might wanna try testing with them. |
I do have more boards, unfortunately they’re from the same batch and identical to the one I’m using, doubt they’re going to make a difference. |
Do you happen to have an aliexpress listing for that board? The exact one you got these ESPs from. One of the boards is from WeAct, others are random (ESP-WROOM-32, ESP32-WROOM-32D, ESP32-WROOM-32UE, ESP32-WROOM-32U). Note that your ESP32-WROOM-32D module visually differs from mine, it's likely that one of them is a clone (or both are clones). |
I do not have a listing anymore, the boards were boght over a year ago. |
Hi,
So I’m having the same issue as the person on #1 , the audio on an iPhone 15 Pro running iOS 18.3 is crackling, stuttering and jumping. Meanwhile a Nokia 8 on Android 12 (PixelExperience 12.1) is playing almost flawlessly (have to keep audio down on the phone down otherwise clipping happens). I don’t know what codec or sampling rate the iPhone is using, but the Android connects using SBC and 48KHz.
Forgot to add: car is a Signum with a DVD90 + CID (both Siemens/VDO)
The text was updated successfully, but these errors were encountered: