Hello, I have tried using CM10 numerous times over the last few months (nightly builds) but always had to switch to back to a stock based rom. The reason being that when I use any CM10 variant anybody I call in my car (using handsfree bluetooth) complains of loud road noise. I was hoping since CM10 went stable for the Hercules this problem would be solved. I installed the stable rom last night but today had the same complaints.
I went digging in the settings and found the phone setting for noise cancellation (unchecked by default) and checked it, but that did not help.
This is not a problem on stock based roms. Is there any other settings I can tweak to try to fix this before switching back ?
Related
Hi guys,
Because of this problem I get almost sorry that I had taken a Galaxy Nexus.
I can pair Nexus with my carkit (parrot) and I can play audio through the speakers.
My problem is: When I call or receive a call I can hear almost nothing. Sound is so low that I can not even notice that the sound from the speakers or coming from the phone. I am using Volume+ too but nothing helps!!
It's look like that Nexus somehow even loses the connection, without any reason.
It's a rooted Nexus and running on AOKP.
Is there a better ROM for my bluetooth issue or do you guys have any suggestions?
Thanks in advance..
No one??
Has nobody has an idea or experince with this??
The market description for Volume+ says:
A Cyanogen Mod 7 or MIUI ROM is HIGHLY recommended. Running this app on a Stock ROM/Kernel may result in it not working, being far too quiet, or getting even quieter. PLEASE don't comment or rate badly if you are on a Stock ROM as this is most likely the problem.
Click to expand...
Click to collapse
The feature list for AOKP says it uses the "Unsecure boot.img (stock AOSP kernel)."
You might want to try uninstalling the application to see if that fixes your sound issues over bluetooth.
I am using a stock (unrooted) GSM Galaxy Nexus. It pairs just fine with my Jawbone Era bluetooth headset and do not have an issue when making/receiving calls with volume. Where I notice the volume is quite low is the voice dialer prompt only (the actually call is fine). Apart from that, no issues.
miui..
Hi guys,
Thanks for your replies.
I flashed the rom of miui and it's seems to work till now. So this rom dealing better with bluetooth.
New so can't comment in the IceColdSandwich thread.
When I connect my inspire Bluetooth to the car It works fine. Issue is after I turn off Bluetooth I only hear sound from the ear speaker not the back speaker.
Ringing, notifications, everything uses the ear speaker from that point until I shutdown and restart the phone.
I worked fine in the previous icecoldsandwich version but just updated to 8.1.1. This is the only issue I have had so far.
Have you tried to switch rom? on my opinion its the rom issue.
Go back to the ROM that was working. Keep in mind that any custom ROM is going to have a bug, so always remember to have a version that satisfies all your needs.
I noticed last night that the headphone icon was MIA.
The headphones work fine, but, depending on what ROM I'm using (all cm10 based - all different versions: nightlies, AOKP, blackjb, etc.) I don't always here the phone ring.
I know I've seen it. Thoughts?
My Samsung T989, which was running Cyanogen 10.1.3, recently starting having the problem where I wasn't getting any sound from the earpiece during calls.
Speaker phone works, headphones work and the person on the other end can hear me (so microphone works). But nothing from the earpiece.
I've tried every setting but nothing. I've also tried Cyanogen 11 just to see if perhaps it was a bug that has been fixed, but still no sound, so I assume that this is a hardware problem.
Is there any way of diagnosing this better as either hardware or software? Any known fixes?
WTF is the deal with AOKP 10.1 MR2 and Sound
bosth said:
My Samsung T989, which was running Cyanogen 10.1.3, recently starting having the problem where I wasn't getting any sound from the earpiece during calls.
Speaker phone works, headphones work and the person on the other end can hear me (so microphone works). But nothing from the earpiece.
I've tried every setting but nothing. I've also tried Cyanogen 11 just to see if perhaps it was a bug that has been fixed, but still no sound, so I assume that this is a hardware problem.
Is there any way of diagnosing this better as either hardware or software? Any known fixes?
Click to expand...
Click to collapse
You are not the only one. Mine the sound other than calls is GONE! I am trying to figure this out. Tried to Flash the ROM from a clean flash with reset to factory and the works and went directly to AOKP ROM Directly with the latest Gapps. No dice. The phone ear piece works but speaker phone and any thing else via the speaker does not work any longer. I am dead in the water here and need a fully functional phone.
This is not my first rodeo. I have flashed many Andriod devices, Cliq+, Nexus S, Nook Color, Acer 500 etc... and the Galaxy S II.
Heck I am also now having issues with the CWM Recovery as well. I can not flash it current. The CWM ROM Manager says flashing and never completes. It has Root privileges. Really has me beside myself at the moment and it is my primary driver so it is interfering with WORK now and really has been ANGRY!
Maybe try out different radios or make sure you using the required version of TWRP?
I'm using UVMC6
Having an issue with no sound emitting from any audio output on the phone, but sound will play through Bluetooth-connected device. No sound from front speaker (phone calls, dial pad), no sound from rear speaker (notifications, ringer, alarm, media) and no sound from wired earpiece/headphones. Seems like it's stuck in Bluetooth/headset mode, but turning off Bluetooth doesn't restore sound. Problem is intermittent, haven't determined pattern to the behavior.
Phone was rooted long ago but kept stock ROM. Flashed Paranoid Android 3.99 RC2 about a month ago, and problem seems to have started shortly thereafter, but not sure if related. Haven't tried to reflash.
Any suggestions? Tried searches, but didn't locate this specific issue.
SGH-T999 (US/T-Mobile Galaxy S3)
Is it a T999 or a T959? And flash back to stock.using Odin. If it still is a problem it's likely hardware related.
Sent from my SGH-T999 using Tapatalk
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
yardsale said:
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
Click to expand...
Click to collapse
Did some more investigating last weekend before flashing ROM (never did the reflash).....seems that often, not always, if I turn off the car ('13 VW) while still connected to phone Bluetooth, the phone's sound quits working (all sound). Rebooting phone and turning off Bluetooth does not restore sound. The only solution I've found is to reconnect to car's Bluetooth, then turn Bluetooth off before shutting down car, and that only works about half the time, but sound is instantly restored. My estimation is that this wouldn't be hardware related, is that a fair assumption?
I also have a Tasker profile set up on phone to disable PIN lock when phone is connected to Bluetooth device (enables Sena Bluetooth headset used with motorcycle helmet to function properly), could that be causing the problem? Anyone else experience this issue?
Please try another Rom. Some of the Custom Roms may not be uptodate with CM Checkins. This issue was reported a bit back. There were CM Code Fixes that may not have been incorporated in that rom.
I am using Slimbean 2.0 (Android 4.3.1) and have seriously tested its bluetooth capabilities.
its also been reported thst msny car manufacturers did not bother to put any time or money into their BT capable systems. they just threw it together so they could add to feature lists.
Lots of peopke have problems with BT in the car, especially on cm roms. but those are notorious for BT issues to begin with.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Thanks for the replies. I flashed to Paranoid Android 3.99.1 RC1 but the problem still exists. I never had this issue with any of our vehicles, until switching to PA from stock ROM. If problem becomes unbearable, may go back to stock. Thanks again.
@yardsale
I should have mentioned in the previously. Please read this post of mine. Yes its a different Rom. However, here primarily the issue is that of hardware antenna of the T999 talking to the Car's antenna. Doc is 100 % correct, the manufacturers do use substandard Antenna. On that thread, someone else reported issues with two '13 VW for themselves and their brother's.