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.
Related
Trying to find some feedback from anyone using the BlueAnt V1 bluetooth headset with the EVO.
I'm having problems with the headset not answering calls maybe 85-90% of the time. It announces there is a call, but will not answer via voice command or hitting the button. I can answer via the phone but when I do it doesn't transfer voice to the headset. The headset thinks it is connected because when the call is ended it tells me.
Have done two factory resets on the phone and resets on the headset with no change. Also spoken to Blueant tech support and they weren't much help. All they said is they haven't heard of it having problems with the EVO and should be compatible with all Android devices. Their suggestion was to try it with another EVO and see if the problem still exists. Well, I don't have another to test it on so that does me no good. This headset worked great on both my Blackberry phones before I got the EVO and has the latest updates installed.
BTW...I'm running Myn's RLS4 w/ #17.
Thanks.
Well I don't think it is the Bluetooth , it is the Rom. I have problems with myns #4 with the sync in my email. I have a blue ant also and it does the same thing . I have tried other roms including virus and it works on them , try that .
sent from the phone that is EVO
Pretty sure I tried this headset when the phone was stock and with some other Sense and non-Sense roms. It has never worked properly.
Not sure if it has something to do with the lockscreen or not. The first time it is connected to the phone it works fine. But every time after that, it doesn't connect the call.
I haven't had any problems running anything on Myn's. But just to make sure, when I switch a rom again I will reset and try the headset.
yeah mine does the same thing, it works if i answer w/ voice command but if i press answer button most of the time the audio is route to phone speaker......Lame!
has anybody with a blueant tried it with cyanogenmod? i wonder if the different bluetooth stack yields different results. I'd like to see an app update for the blueant software too (had a cheaper headset that stayed connected way better)
When I pair the headset, it connects and works great the first call I get whether using voice command or button to answer. Then every time after that, it won't connect the call.
Maybe it has something to do with the lockscreen or the phone going to sleep. I will have to do some trial and error.
Currently I am trying out the headset with MikFroyo 4.2 (Sense rom) to see if it makes any difference. This rom is really close to stock so maybe it will work?
I will post back with my conclusion.
My headset works fine now. I have found there is a coding issue that exists in certain roms such as Myn's and CM that prevent proper operation. CM seems to have put together a fix for it. Myn's still does not work at this time. It has been requested as a fix for RLS5 final.
Running eVoKINGS Black Titanium with Mik's 4.2 base and my headset works good.
hey where is the fix for CM or is it just in some of the versions? cause i just flashed CM7 and some of the features i loved about the Blue Ant before are not working like it will not play my audio like it did before i use to be able to listen to my music and what not through the blue tooth. if there is a fix for it i would love to get that working again.
jbrazee said:
hey where is the fix for CM or is it just in some of the versions? cause i just flashed CM7 and some of the features i loved about the Blue Ant before are not working like it will not play my audio like it did before i use to be able to listen to my music and what not through the blue tooth. if there is a fix for it i would love to get that working again.
Click to expand...
Click to collapse
Sorry...it's been a while and can't remember where I read about the fix. If I run across again will let you know. Might try downloading "BT mono" from the Market to see if that helps. Not sure if it is effective on AOSP or not but worth a look.
I can't get any sound from my speaker at all. Anybody having this issue or am I the lucky winner.
Running EC05- rooted
Sent from my SPH-D700 using XDA Premium App
LAELOW615 said:
I can't get any sound from my speaker at all. Anybody having this issue or am I the lucky winner.
Running EC05- rooted
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I can't answer such a generic question without more information. First, I'm going to assume you mean the earpiece, not the external. Next, I'm going to assume it's STOCK EC05 rooted. So based on that assumption, you likely don't believe you've done anything to your Epic that would cause this kind of error. Then I'm going to take it that, either your question is rhetorical and you believe you have a hardware issue, or you believe that either EC05 or rooting is the cause and you're asking if anyone has had any similar problem with EC05.
I can say that I don't know of any similar problem with rooting or EC05. But seeing as you don't mention whether you're even stock or custom, or whether this problem arrived before or after you rooted, no one will be able to compare their situation to yours. Please enclose better information. The following are my generic solutions:
1. Download Sound Manager and attempt to tweak hidden sound settings.
2. Flash or re-flash a ROM (as I don't know if you're custom or not to begin with).
3. Odin to stock or stock-rooted EB13.
4. Head to your nearest Sprint repair store.
You can find links to everything you need for a fresh start in my signature.
LAELOW615 said:
I can't get any sound from my speaker at all. Anybody having this issue or am I the lucky winner.
Running EC05- rooted
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Same issue
All notification sounds and ringtones play through the earpiece instead of the speaker
I had the issue on stock rom figured rooting would fix it.
It did for a couple days and then everything went back to playing through the earpieces as if I was on the phone.
I use a bluetooth car kit often and Im wondering if that has anything to do with it
There may be a simple fix for you. This has happened to me a few times when I have plugged up my Epic to wired headphones. Something about disconnecting can sometimes cause the phone to think it is still outputting sound to the headphones, so you cannot hear sound anymore . . . even with a restart. A simple fix is just to plug in a headphone jack again and remove again. This has fixed this issue for me numerous times.
Lost my sound today
Took the above advise and plugged in a wired headset then unplugged. Worked like a charm...for about 2 hours...then happened again. No matter what I try now, cant get sound again.
B4 u ask:
Been CleanGB/BML w/o any mods or themes for long time.
Havent installed any new apps in days.
No OC/UV
Sounds are fine in wired headset
BT works.
Cleared DV cache and reboot > no fix
ODIN'ed stock EC05 > no fix
---this tells me its not the os, but why did it work after plug/unplug headset?
Yes, Sprint store just down the street, but I love a challenge Anyone?
Same problem. Works fine if I plug in an audio out. But did ring for instant messages for about a day. So speaker does work. Wonder if I should go with the kernel that was orginally flashed with cm9?
Sent from my SPH-D700 using XDA
There are two different issues being reported here.
One being, sounds come out of the ear piece and not the speaker (e.g. ring tone during incoming call can be heard with phone up to your head).
The other being no sound at all, unless you connect to the headphone jack.
The latter I would suspect to be a HW problem (loose internal speaker connection maybe?).
The former would be an audio routing issue I've experienced myself (usually related to BT, speaker-phone, etc).
A simple reboot should fix the routing issue (has for me a few times).
=]
If u Odin back to stock and it still doesn't work then its probly hardware. I tried everything thinking it was sw but ended up replacing the speaker.
Sent from my HERO200 using XDA
I have the exact same issue, if I plug in headphones it will work through speaker, nothing connected it thinks headphones are connected. I have to jam a eyelet from my shoes in there, and connect it to bluetooth to hear audio...
So I ain't the only one...
Went back to stock, same difference, nothing I know will correct it...
saramon said:
I have the exact same issue, if I plug in headphones it will work through speaker, nothing connected it thinks headphones are connected. I have to jam a eyelet from my shoes in there, and connect it to bluetooth to hear audio...
So I ain't the only one...
Went back to stock, same difference, nothing I know will correct it...
Click to expand...
Click to collapse
This is a known phenomenon I've seen a thread here before where the headphones are reversed... like it think the headphones are plugged in when they aren't.... dunno what causes it but its certainly not too abnormal.
Sent from my SPH-D700 using xda premium
samsung galaxy s2 epic 4g
hi i win a samsung galaxy s2 epic 4g i live in the bahamas and i factory unlock it to use on my carriers but i can't hear incoming calls or out going calls i have reset the phone,root the phone and nothing work can somebody help me..i email the seller to ask him if he'd sold me the phone like that but he told me it was working fine before he sold it to me skype , works on incoming calls and outgoing calls and magic jack works i don't no what to do .....!!!! help thanks
keno24 said:
hi i win a samsung galaxy s2 epic 4g i live in the bahamas and i factory unlock it to use on my carriers but i can't hear incoming calls or out going calls i have reset the phone,root the phone and nothing work can somebody help me..i email the seller to ask him if he'd sold me the phone like that but he told me it was working fine before he sold it to me skype , works on incoming calls and outgoing calls and magic jack works i don't no what to do .....!!!! help thanks
Click to expand...
Click to collapse
Wrong forum, this is galaxy s1 epic 4g with keyboard.
I have experienced poor Bluetooth call audio on my galaxy nexus. The audio is crackly, and very unclear. I have tired 4 different bluetooth headsets that were first tested on known working lg revolution.
Call audio is fine with the phone to my ear, and the strange part is, bluetooth music streaming couldn't be clearer. I have factory reset twice and tried volume +
Is this normal or should I get a replacement phone? very frustrated, it's so bad I can't understand anyone.
Sent from my Galaxy Nexus using XDA
bump
I have the same problem as you, I recently updated OTA to:
Jellybean 4.1.1
Baseband: XXLF1
And i'm experiencing horrendous bluetooth quality (I'm using a Jabra Extreme2 bluetooth headset).
The calls are perfectly crisp and clear when I use the phone to my ear, but when I switch over to the headset it seems as if they are underwater and everything is mumbled (they say the same about when I speak to them and how much better it is when I don't use the bluetooth)
I didn't face this problem before, and I've noticed there were Verizon users with the issue as well when going from 4.02 to 4.04
(google search : Support Terrible Bluetooth sound quality since 4.0.4 )
as it wont let me post links yet
Now, I am in Canada using Fido/Rogers - so do you guys think it would be okay to flash back the baseband to UGKL1 or UGKK7 ? (Apparently it was a fix for a few of the Verizon users)..
Hi everyone,
The bluetooth on my GSIII has been a complete failure. You can follow the saga here (http://www.benzworld.org/forums/w245-b-class/1662643-2009-w245-samsung-galaxy-s-iii.html), but basically it connects to my car and has no sound with the stock ROM and refuses to connect to the car at all with the AOKP JB build. It suggests an android problem, so I'm wondering if the bluetooth stack can be reloaded to reflashed with something different. If anyone has any ideas, I'm all ears. Thank you!
I have a problem with one of my Bluetooth devices dropping and reconnecting. Not sure why is just one. It works fine on an iPhone. I'm guessing your GS3 isn't the international version?
Sent from my SGH-I747M using xda premium
Nope not international, SGH-I747M from Bell.
I'm trying this. Will report back.
evilmonkey1987 said:
I'm trying this. Will report back.
Click to expand...
Click to collapse
Sweet! please let us know!
I'm having a different issue. it connects and stays connected, plays music but it doesn't list the song/artist info on my eclipse screen but the SG2 will..
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
evilmonkey1987 said:
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
Click to expand...
Click to collapse
Try CM9. Bluetooth works much better with it. CM10 should have it fixed as well in a day or two.
Here's a 'six months later' update. My phone went through various android updates and I'm now on Android 4.1.1 (up from 4.0.4). The problem was still not solved, but instead of no audio, I now have one way audio, where people hear me but I don't hear them through bluetooth. I have also gone through a number of custom ROMs and kernels for my phone (including CM9/10 and AOKP) and nothing helped with the issue.
A couple of days ago, my girlfriend's HTC One X (finally!) got its Android update, also from 4.0.4 to 4.1.1. Her phone now works like a charm with the in-car bluetooth.
The solution I ended up with was a car cradle and a couple of NFC tags to control my phone in the car. My NFC tag that's stuck to my car cradle turns off WiFi, starts car mode, starts a car home app and turns my volume to max. All I have to do after that is connect the 3.5mm audio cable and I use my phone in place of the car's infotainment system. That way the phone integrates into the car as well and the only thing I lose are the steering wheel controls (they still work for volume).
My less technologically inclined girlfriend now has everything work auto-magicallly with bluetooth. So I guess all's well that ends well, but to anyone considering a US-spec Galaxy S III, watch out: the bluetooth issue is still not fixed. If bluetooth is critical, consider the HTC One X (but be warned: it has awful battery life!)
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
colbynmeghan said:
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
luncht1me said:
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
Click to expand...
Click to collapse
What's wrong with stock? I have no major issues with streaming BT from my phone to my Mazda 3 head unit, or to my Sony MW600 earphones. Even track titles work (the only thing that doesn't work is time display). In my experience, Bluetooth works best on the stock ROM.
Stock Rogers ROM (DLK4 - JB 4.1.1), rooted
KT747 (1/9/2013) kernel
CWM Recovery 6.0.2.3
PlayerPro Music Player
On my old Xperia X10, I had CM7 and had no end of issues with BT:
- Sometimes it would connect and there would be no sound
- Sometimes it wouldn't connect at all
- Sometimes it would cut out after switching songs
- It would stutter a lot whenever Wi-Fi was enabled (but I think that was a problem with the Xperia).
When I tried CM10.0 on my S3 I had similar connection issues, just not as bad. Also, the volume gain over BT was much lower, so I had to turn the car speakers way up. Stock 4.1.1 doesn't have any of these problems. The only problem I had was the audio switching over to speaker after turning off the car, but I fixed it.
Also, BT is apparently broken in 4.2.1 in general, not just CM10.1. Google confirmed a BT patch that works on the Nexus 7, due for release with 4.2.2: http://www.expertreviews.co.uk/smar...confirms-android-4-2-bluetooth-streaming-flaw
TIP: Don't forget to turn up the volume on your phone. I don't know how many times I accidentally turned down the volume and thought that it wasn't working. Now I have Tasker do it for me whenever I connect. :good:
4.1.2 has Bluetooth working use it everyday. (Stock and ROM.) Can't tell u which combo I use at a time. I flash a different ROM everyday. As 4.2.1bluetooth is broken expect for task's AOKP. He has it workingish.
Now as connecting to a car. Depends on what it connects as. And I've learned going to and from ROMs when u connect a source hit the volume up 9/10 times it works
Sent from my SGH-I747 using Tapatalk 2
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