Hi all,
I have a killer problem with CM7 - my bluetooth headset (stereo earphones) is frequently disconnecting and connecting. This happens at irregular intervals, sometimes during calls and music playing - and has put me in embarrassing situations already.
I have looked around a lot, trying editing the audio.conf file, changing radios (just in case) and tweaking otherwise and nothing helped.
Please help me solve this!
I like CM very much, but I can't continue with it if BT isn't working - is there any other ROM without this kind of problem (MIUI? CM9? Stock? )
Thanks for any help and good will
Ophilar
PS I've seen this issue many times, without any clear solution. I think it would be good to solve it once and for all. I'd be happy to debug/post log if it helps. Cheers
Solved on ICS (CM9)
Update: Switched to CM9 nightly and everything works like a charm, including Bluetooth.
If you don't have a critical app which doesn't work on Ice Cream Sandwich, I recommend the switch
Related
Hi, I do know that there been reported quite a few problems with Galaxies bluetooth.
I have Motorolla HT820 headset. It connects without any problems. Starts playing music. However, every odd 30 (sometimes more) seconds it stops playing music for some 0.5-1 seconds.
Checked that headset works okay with other phones, so its problem in phone.
Anyone has similar problems, or it works for them without problem (eg. maybe other variants of galaxy s work better)?
Turn off WIFI. It is a common Android problem.
mirox3m said:
Turn off WIFI. It is a common Android problem.
Click to expand...
Click to collapse
Seriously? Thats it? I spent god knows how long trying to fix it, used different firmwares, searched in google quite a lot (obviously not good enough, as I thought its a galaxy only issue)... God android sux in some things...
Thanks, mate!
PS. Topic can be closed.
EDIT: After testing a few minutes it appears thats it is enough to just switch off - switch on WiFi to fix it (I assume for the duration of one session).
Hey there fellows,
I have a Samsung Galaxy S I9000 that I've been using since Froyo. As an accesory, I've always used the Motorola S9-HD A2DP headset to listen to music and take calls wireless.
The thing is that ever since I've started flashing GingerBread ROMs (stock), it started to mess up.
Let's begin to enumerate the issues:
1) After having the device paired, simple turning the headset on wouldn't connect to the phone (as it worked before 100%)
2) With the headset turned on, if I go to the Bluetooth menu on the phone and "click" to connect, it would say connecting and one of this things would happen:
- "Connecting..." would display forever until I shut the BT radio off
- It would connect and immediately disconnect, even sometimes the headset shuts down too!
- It would connect to one of the profiles: the audio one or the headset one, but not both
- 1 out of 50 times it would connect to the audio profile online and finally be able to play music through them
3) While the headset is playing music (i.e. connected), I turn it off, and sometimes Android keeps showing the icon as connected, for like 10 minutes, until it eventually times out
As you might guess, I've been searching since this arised for a solution, comment, similar behavior reported from other users, etc, without luck; neither here at XDA, Google or other related forums. I've found some *similar* stuff like car audios disconnecting but finally they fixed them or were some issues with the car app or something, unrelated to this.
This started happening ever since the first GingerBread I've flashed; now I'm on stock JVS and the same thing still goes on. I've tried before flashing any kernels (as stock as it gets) and this happens too. I've tried after flashing pretty much every kernel (to see if they somehow fixed this) and the problem persisted.
Let me be clear the the headset works great; if I use it with another phone (Nokia) it doesn't present any of these issues; neither did here before GingerBread!
So far, the only remotely possibility to use it fine and that works 95% of the times is:
1) Erase the headset memory of paired devices
2) Erase the phone memory of paired devices
3) Pair the device
As you can imagine too, doing this EVERY TIME I want to use the headset is an awful lot of pain!
Well, thanks for your time and for reading so far... any kind of pointer, advices, consolation that you can provide would be more than thanked for!
Best regards,
Anyone?
sorry no solutions from me.....but I did incur a similar situation when I flash jvq stock (music player would stop playing music and make bootanimation sounds)before flashing over to re by darky.....since being on darkys the problem has gone.maybe try a custom rom!!!
Sent from my GT-I9000 using xda premium
urban bumpkin said:
sorry no solutions from me.....but I did incur a similar situation when I flash jvq stock (music player would stop playing music and make bootanimation sounds)before flashing over to re by darky.....since being on darkys the problem has gone.maybe try a custom rom!!!
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
That's a good thing I didn't try! I refrained from flashing a Darky because all the "extra" steps involved besides directly flashing the files from Odin and also the auto voodoo lagfix kernel that converts unless you put the files to NOT to on some directory... plus the "bloated" experience over a stock ROM.
I think I should try one though, and also think that the BT should work OK in stock too! First I'd like to confirm if it's a "known" issue with the Ginger ROMs or not...
Anyway, thanks for your advice, might flash Darky soon!
its amazingly easy to do...just follow the guides to the word.....
Sent from my GT-I9000 using xda premium
Hi all,
Got a really weird bug... was interested to see if anyone else has the problem. I've tried 4 different ROMS with very very very clean installs so I know it's common, but it's obviously rare as I'm not seeing it coming up here.
In short 4.1.2 - Slimbean, Asylum etc Bluetooth to my car for hands free calls works fine.
10.1 or 4.2.1 - Asylum, Revolt, Utacka Paranoid etc don't work with my car, but they do work with a headset..??? WTF..?
So I can hear the phone ring, then once the call comes in sound is not transmitted in either direction.
I'd appreciate any suggestions on things I can do to troubleshoot or fix the problem.
Matt
I have the same problem in my car. I can't hear the phone ringing or anyone else picking up on the other line. If I can't get this working soon I may have to go back to the stock ROM.
I've tried Paranoid Android, PACMAN and AOKP with the same issue on all three. Also I flashed the bootloader to the latest version of SuperSlim.
Hey guys, ive been running CM9 on my touchpad for ages but want to move to a JB rom. Im going to be using my Touchpad as a media device for outdoor speakers i have in my patio so i can walk around and change music as need be (instead of having to go inside where the receiver is to change music then go back outside). I was looking for improved roms with better battery life maybe and especially working bluetooth with A2DP. Are there are any JB roms that fit the bill? Some googling turns up Jscullins roms, but i was reading he was only doing it as an experiment and figured his BT fixes would be included in more (and possibly better) roms. Something stable with decent battery life and working BT with A2DP is what im after. Any suggestions? Thanks folks.
also, if there is nothing that fits the bill what would be the best CM9 ROM that does? I have noticed that my current CM9 build has an annoying issue with the touchscreen where if im scrolling around and let go, sometimes it registers that as a tap/click. My girlfriend hates it. A smooth CM9 build with good battery life, good working A2DP BT for music streaming, touch issues fixed (which i heard of for CM9 builds so thats why i mention it), and stable would be awesome.
Well I am running JC Sullins 0808 CM10.1 (4.2.2) ROM, and this is working well with BT keyboard and mouse. I did sync it to the car for BT Audio and that worked fine on the 5-10 minutes I used it, not tested audio over BT for any longer than that.
Generally the ROM has been stable, and am happy with it. I hope his fixes make it back into the dailies/weeklies, but we'll see, been a while now.
I did a complete wipe and start again on the device to get it working, and so far very happy with 10.1. I also am starting to use BT Audio more and more, so BT is important to me.
Hi everyone, thanks for taking the time to look at this.
I'm having an issue where if I run any CM based rom I get "com.bluetooth.android has stopped responding" when connecting to my Mazda car stereo or my jawbone speakers. I've had this issue on every version of CM that has been out since November. If I use a stock based rom, everything works fine and I don't have any issues. It doesn't matter if I'm using 4.4.2 or 4.4.4, the previous scenario still holds true.
Any ideas what I can try in order to solve the issue or at least narrow it down further?
I really like flashing different roms and checking out the awesome features everyone has added, but I unfortunately need my bluetooth to work properly.
Thanks in advance for all the help!
nuggetfn22004 said:
Hi everyone, thanks for taking the time to look at this.
I'm having an issue where if I run any CM based rom I get "com.bluetooth.android has stopped responding" when connecting to my Mazda car stereo or my jawbone speakers. I've had this issue on every version of CM that has been out since November. If I use a stock based rom, everything works fine and I don't have any issues. It doesn't matter if I'm using 4.4.2 or 4.4.4, the previous scenario still holds true.
Any ideas what I can try in order to solve the issue or at least narrow it down further?
I really like flashing different roms and checking out the awesome features everyone has added, but I unfortunately need my bluetooth to work properly.
Thanks in advance for all the help!
Click to expand...
Click to collapse
Ha. I have the exact opposite problem. I have a 2013 Subaru Outback and every AOSP rom works perfectly and any stock rom has issues. Calls work fine on both stock and AOSP based roms, but media playback has always presented a problem for me on stock roms. On AOSP roms I can play Netflix, Youtube, music, etc through my car speakers but I can only get Play Music to work on stock roms. Sometimes on a stock rom, Youtube will play for 2 seconds but then cutoff the audio. The video will continue to play, but the audio is lost. Very strange.
I've searched around a bunch, and it looks like i's not an uncommon issue, but it doesn't look like there's a systematic solution. I assume there are too many variables (car makes, models, years, stereo upgrades, Nav options, etc) to be able to isolate an issue. You just have to keep trying different iterations.
Keep me posted if you find a solution.