Hi everyone. I ask you for help because I am a GOLF 5 owner with an Eonon GA5153F installed (which should be an MCTB) originally with Android 4.4.4 which I then brought to version 5.1 with a rom
The problem he has always had is related to the audio quality in calls. Until I used it, I used the hands-free phone and that's it, but now that my wife uses it, I prefer to be careful while driving and therefore call and do everything via the car radio. The problem is that the audio I get is really HORRIBLE. Practically whoever is on the other side of the phone hears nothing, hears 1 word every 5 and at a very low volume (I've already gone to the factory settings and turned up the bluetooth but nothing changes).
I've read that many of these Chinese have made hardware changes, removing the capacitor and resistor on the bluetooth module or similar, but I can't find anything about my car radio. Have any of you done this? Does anyone of you have photos, videos or something that tells me on mine which component I have to desolder, which track to open, or what to do?
Please because the quality that this car radio has on call is really a shameful thing!
Thanks a lot to everyone
P.S. Currently I have connected (in the back of the car stereo) an external microphone (the one that was inside the car stereo package)
Related
Hi All,
This morning I was listening to my favorite Podcast through the speaker of my SX66. I then headed out the door (still listening) and plugged the unit into my car stereo via the 2.5mm audio jack. I continued listening over the car stereo with no problems during my drive to work.
When I parked the car, I unplugged the SX66 expecting to have the audio switch back over to the speaker so I could hear the conclusion of the Podcast as I walked to the building. However, when I unplugged the unit there was complete silence. If I plugged it back in, the audio played normally through the car stereo again.
After playing around a bit, I found that except for the playing of ringtones for incoming calls, no sounds come from the speaker. The volume controls have no effect, and anytime I plug the headset in, I can hear all of the sounds normally through the headset (menu clicks, WMP, etc.).
I tried soft resets followed by more desparate hard resets. No effect. What in the world would cause the system and WMP sound to stop playing through the speaker only (headset OK), but ringtones for incoming calls play through fine? I'm confused. Is this a software or hardware problem? Anyone seen anything like this?
:?
Thanks for any suggestions,
Paul
Paul, it sounds like you have broken the audio jack socket on the unit, they have a switch type arangement in them to disable the speaker when on external sound, if a bit breaks off (which is what I suspect) then the removal of the jack plug will not re-make the connection for the audio to route back to the internal speaker - sorry to be the bearer of bad news - it needs a repair mate - Mike
Thanks for the suggestion, however it turns out this is a software problem. :lol: Specifically, it has to do with the BT patch that I was running (Cambridge Silicon Radio Ltd. BHCS, posted here: http://forum.xda-developers.com/viewtopic.php?t=36626&postdays=0&postorder=asc&start=75). It seems that if I add any BT device at all (even non-audio devices like a keyboard) and have the tray icon enabled (BTIcon.exe), then I have no sound. I'm not sure whether it's the patch, BTIcon, or a combination of both.
I removed the patch and took BTIcon.exe out of the Startup folder and everything went back to normal.
Paul
I have such problem
Sorry, I really tried to find something like this, but stuck.
Ican't solve it, and Removing BTtray - doesn't helps.
After update from
PH20B_0_B_WWE_E_BRIGH001_1.22.00_0_0_1.22.126_1.06.00_06.00
to
PH20B_0_B_WWE_E_BRIGH001_1.22.00_0_0_1.22.169_1.06.02_06.02
- same result.
Please - any ideas?
Thank you.
I am pretty new to Android and still trying to get all the grips on I need. As of now, there is one thing that really bugs me badly.
I use the device for Sat-Nav driving a lot, I have a semipermanent installetion in my car from my previous smartphones. Basically just a power feed and a 3,5mm Jack that come out of the dash panel where the device holder is mounted. I recharge plug in for recharge as needed. The audio jack goes into the device, from there to a so-called Fastmute box behind the dash which is connected to the stereo head unit (the loudspeaker output cables running away from the head unit to be specific. The Speaker lines are interrupted by the box and just pass through whatever audio is being played back by the stereo. However, once there is current on the 3,5 audio jack (i.e. speech from the SatNav) the music immediately goes mute and you can hear the turn instructions in perfect quality through the car speakers. Once the signal fromthe satnav dies down stereo music comes back.
For my taste this beats most commercial, fixed systems.
Now, since I am on Android weird stuff happens.
On a first testrun shortly after I gut the Desire (which was o2 branded stock 2.1 at that point) I noticed that I do not get any announcements through the fastmute. Checked the jack, opened the dash to check internal wiring, retried a mp3 player. It's all good on that side. The accouncements come through the device speaker, hard to hear, easy to miss a turn etc. I do not why or how, but it seems that the audio routing takes a route different from other audio. This had me pretty much meh!
Well few days later, now with a ModaCo R8 custom ROM and Froyo I was hoping for good luck and gave it another whirl. Of course, no dice. When I plug in the jack of the supplied headset (which I assume doubles as a handsfree) I get the symbol for that in the upper symbol bar. When I exchange that headset jack with the regular 3,5mm jack the symbol looks different, but still vaguel like a set of speakers.
But now here comes the completion of the mindfaq... I had the SatNav volume at about medium (so barely hearble with driving ambient noise) when the phone went and I took the call through the Bluetooth Handsfree instaalled in my car and was distracted by the call (the car came euipped with the BT Handsfree from factory, so the stereo goes to "pause" and the conversation is routed into the vehicle speakers.. A few minutes into the call I suddenly hear a perfectly well understandable, clear turn instruction hopping into the phone conservation. I was extremely intrigued and was hoping that I discovered that CoPilot can route instructions either into A2DP or more likely emulate a "call event" that results in routing the audio into the according BT profile.
However, after that singularity I tried reproducing this for a god part of an hour, driving a route that forces many instructions from the SatNav, all the while calling my own answering machine fo have an connection established.
Sorry for the lengty explanation. Questions:
1 Has anyone ran into this before? What was your solution? Bear with it, switch SatNav software, avoid listening to music in oder to not miss any turn directions?
2. Is there a hack, hidden configuration that would enable me to _force_ this audio routint into the direction of the BT Handsfree, making it think it is an incoming call?
As a fellow co-pilot user I share your frustration.
You will probably find that it's nothing as technical as it not routing to bluetooth or whatever.
Co-pilot has a nasty habit of messing with it's own volume setting when a headset is plugged in. It tends to reduce itself down to zero without notification or cause. You would try to reset the volume, but firstly, it wont go more than a third of the way up, and secondly, it will simply jump back down to zero again on it's own.
They know about this issue and their response is not to use it with a headphone jack!
It is rather annoying!!
Hey so I've tried searching other threads for my specific challenge and none of them seem to really touch on this so here goes.
I have a Samsung Fascinate, I'm rooted and I've flashed a bunch of kernels and ROMs no problem and as far as I can tell my Bluetooth works fine and audio works fine.
My issue is this: My car supports hands free calling via bluetooth and i've paired them with no issues and have made/received calls no problem. I've also used my phone to play music through the AUX cable no problem. I know that my car STEREO does not support Bluetooth and here is where i run into a problem.
I have my phone plugged in on my way to work singin along to my favorite tune when a call comes through. But (I think) when the AUX is plugged in, it interferes with the audio when connected to the bluetooth. Basically i can hear a call coming through on my car stereo and i can push the buttons on my steering wheel for functions on the phone but i can't hear and the other end can't hear me. So i have to end up unplugging the AUX cable out then the audio returns.
First off... is it just me? did I do something wrong along my journey of flashing all sorts of stuff? cuz i could've sworn at one point (i think before i went voodoo) it was all working fine together, but i could be wrong.
So if it's not something I did, is there a headset adapter out there with controls and possibly some kinda screen for like caller id or at least current track? like something that can connect to regular earphones that has an inline mic and controls.
Unless you fine folks have a better idea I would love to hear them. (I don't have a budget for this... just want to get it working... unless it's cheaper to buy a new car that can support it all)
Thanks
I think this is a fascinate specific or limited problem
http://forum.xda-developers.com/showthread.php?t=894452
Anyone have a solution for this one?
I have a 2008 car with factory installed Bluetooth phone interface. The Bluetooth is ONLY for the phone, not music. The car also has an aux in jack for the stereo. (Know where I'm going with this yet)?
Yesterday I was listening to music using the 3.5 mm jack on the phone, and it was also connected by Bluetooth to the car's phone interface. A call came in. The stereo automatically muted like it should but when I answered the phone I couldn't hear anybody there. After 30 seconds or so I hung up.
Then it dawned on me, with something plugged into the 3.5 mm jack, the phone audio may have been routed through that jack instead of Bluetooth. BUT the car assumes that when a call comes in you want the stereo muted so it kills audio from everywhere except Bluetooth. I suppose I could have reached over and unplugged the 3.5 mm jack, but that's inconvenient when I'm driving.
So, the question is, is there any way to set up the phone to always route phone call audio through Bluetooth when Bluetooth is connected?
I have the same issue.
I listen to music in my car via a cable from the headphone jack to my car stereo's aux in. If I get a call over bluetooth, I can't hear anything. If I unplug the cable on the phone side, I can hear the person on my car speakers, and the caller can hear me via the car's mic.
Are you using the stock firmware or a custom ROM? If it isn't a problem on a custom ROM then perhaps it can be fixed. It's very annoying -- my 3-year-old HTC Hero could do this, why can't the S3?
I was told by someone with a different version of the S3 (an international one) that this isn't an issue on their phone.
I'd love to find this out while I still have time to return the phone.
I'm going to try building a "car adapter cable" that feeds audio out the USB port to see if that works, Instructions are in this thread:
http://forum.xda-developers.com/showthread.php?t=1395173
That could be one option. Still seems pretty lame that we have to come up with workarounds for this pretty basic problem.
And I'd love to hear from someone running a custom ROM to try and figure out if it's a hardware or a software issue.
Anyone else having issues with connecting the 7T to their car and getting audio going out of it? My OG Pixel didn't have a problem, but I have to toggle off/toggle on Bluetooth and then manually tap the car's bluetooth listing to get it to actually 'connect' the audio portion.
Rather annoying, considering I'm only in the car for a few minutes at a time, this either eats into the time entirely, or makes me sit in my car for a couple minutes before even driving to fiddle with the bluetooth settings.
Car has stock headunit, 2015 Evo X. Like I said, original Pixel XL had no issues, but this is annoying. I've tried changing bluetooth versions to no avail. I can see it connecting and dropping the bluetooth connection fairly frequently while staring at it and trying to 'get it going'. But once it connects, it stays there.
My bluetooth headphones (Some knock off cheap Chinese ones for $20) don't seem to have an issue.
My connection to my aftermarket stereo is fine. Just seems a little quieter than my last phone. Connecting is kind of slow too when I start my car but it is automatic.
I don't have any issues with connecting to all 3 cars (2014 Honda Accord, 2009 Pontiac G8 Gt and a 2018 Honda Fit) but I do agree that the volume seems a little lower than my previous phone (Galaxy S8).
Sent from my [device_name] using XDA-Developers Legacy app
Hmm. Weird. Is there anyway I can check for logs to find out what exactly is happening? I haven't rooted, just don't know if it's something I can naturally pull from Android as a whole.
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
My bluetooth is quiet, but its also static-y. I never had any issues with my G6 and now I get static clipping every 10 or so seconds. Its unbearable.
jagadeesh16 said:
I had the same issue, but when I made the phone discoverable and initiated bt from the car stereo it seemed to work.
I also set a custom pin , not the default 0000
Click to expand...
Click to collapse
I'm not really having an issue pairing it, but it's just connecting after pairing is the problem.
I have changed the default pin. I can see it popping up and down the car stereo a few times in the bluetooth settings before it just gives up.
As for the other issues, I'm not having a problem at all with audio volume, nor popping/static when it finally does connect.
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Phreak411 said:
My volume is super low when connected to Android Auto and streaming music. Have to turn the radio up to max. However, I'm assuming that's an AA issue or Android issue, as it seems many others are having the same problem with different phones. Been thinking of adding an aftermarket amp to the car. Maybe I should pull the trigger. Lol
Click to expand...
Click to collapse
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Milkshakes00 said:
Be careful that a bugfix doesn't come and blow your eardrums out, lol.
Click to expand...
Click to collapse
LOL that would be my luck
.
My OnePlus 7t connects fine and phone works for calls on 2014 cts. The sound comes out of phone can change song on head unit but I can't get audio to play through car. Anyone else get this?
Yeah music stutters with car player... Only calls work. Music works on headphones etc. I couldn't find solution, did network reset, cleared cache. Nothing works.
Seriously!
I've wasted at least two hours already trying all the recommended steps: from flicking icons on and off to a full phone reset.
Still no connection to my Suzuki S-cross car. Multiple previous phones have connected effortlessly.
Even the $50 temporary five year old borrowed phone could handle it.
Anyone got any other suggestions? Yes, tried the AVRCP setting change from 1.4 to 1.6. That didn't work either...
Barebones system reset from scratch running O2 OS 10.0.6HD65AA
Any suggestions greatly appreciated.
I need to be able to talk and drive!
Reset the car radio and clear all pairing data if you can. Then try again.
autosurgeon said:
Reset the car radio and clear all pairing data if you can. Then try again.
Click to expand...
Click to collapse
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
mikefnz said:
Thanks for the suggestion.
Tried that.
Tried one other car - no problems.
Tried a tablet and a very old phone with the car and suprise - the car's bluetooth seems to be the problem.
I will try and find out if I can fix the car!
UPDATE: Morale of the story - read the car manual very very carefully and go though each tedious step = SUCCESS
Click to expand...
Click to collapse
Yep most have lots of tedious steps that are different model to model and if not followed exactly will cause this problem on occasion..
In my case music starts to be scrambled after 10 minutes or so of listening. When I take the phone (so the watch pops up) or turn on the screen it immediately works fine again, but when being put aside and the screen turns off, the issue starts again ..
Also in the early days of my previous 5t I had the same issues but some fix was delivered together with oxygen os update. And now the same story again
I have a different issue with Bluetooth:
- OP7T connects to car Bluetooth fine
- I can make/answer calls
- Bluetooth media works fine
The problem is with Google Assistant & car audio:
- it was working as intended until the latest update - 10.0.15 - I was pressing the button on the steering wheel the google assistant was answering questions through the car bluetooth, no need to switch to bluetooth media.
- after the latest update, when I press the button on the steering wheel, Google assistant pops on the phone , starts to answer question, but cuts off after 5 seconds. the command still goes through and Assistant still runs, but does not come up on the car audio.
- it looks like the Assistant is not connecting to the car as a hands free, but as to a bluetooth handsets.
Anyone experiencing this?