I haven't tried ICS yet.
Is bluetooth any more functional on ICS than GB?
On GB, I can't get BT to "auto connect" like my blackberry used to.
-Thanks!
I've tried quite a few roms... the bluetooth on ICS is almost up to GB. It is still garbled for me during the first few seconds of a call. Afterwards it only clicks once in a while. A2DP works perfectly, however.
I have no issues with bluetooth on any of the 3 devices I use.
I stream music to my bt headphones all day with no isssues, and autoconnect works great if you can stay on 1 rom
Mine automatically connects to my car when I turn it on with AOKP.
Related
on the edge of updating to froyo at the moment but might wait a week or two for the little problems to get ironed out..
just wondered though if they have improved the Bluetooth on the phone ?
I have heard a few people having problems with the HTC implementation of it and have myself a device with pairs but does not connect
thanks
mitch
hi mitch,
bluetooth issues are still there after official htc 2.2 froyo update.
I have a Logitech diNovoMini keyboard that can pair but not connect to my desire.
htc broke the damn thing...
Bluetooth woes
I have just bought a Linx B-Tube. It should function as a bluetooth headset (only it has a speaker). I was hoping to pair it with my Desire which was running Cyanogenmod RC1. I couldn't get it to pair so I decided to make the leap to the nightly to see if it made any difference....nope!
I can see the device and I am prompted for a passcode for connecting. When I enter the code it just goes back to the original screen and doesn't pair.
I have also tried pairing to my MacBook pro with the same result..
Any solutions would be much appreciated
I have a Vodafone unbranded HTC Desire running Froyo, and I have a similar bluetooth problem. It really sucks. My Plantronic bluetooth headset can pair and connect with the phone without any problem. The connection is fine and will automatically be re-established if the headset is in range. However, occasionally, yes, occasionally, the headset will be detected and connected, but can NOT be used. I can see the icon that shows that the bluetooth headset is connected. However, clearly the phone voice output is for whatever reason NOT routed to the bluetooth headset, and hence I can't talk using the headset. I found that once I got this issue, the only way to solve it is to unpair and re-pair the bluetooth headset.
Very annoying. These days software quality control is very poor.
Hi my problem is different. both with Android 2.1 and 2.2 my bluetooth headset (Blueant Q1) works fine except when the Wifi Connects to a new hotspot. When this happens teh bluetooth headset discoinnects and then reconnects : (
Maybe I should be happy it works most of the time listening to previous posters !
So a friend of mine bought me a TuneLink (for Android) for my birthday. I've been running CM7 Nightlies for quite a long time, and I'm currently using N93. The tunelink is great for the car, if it worked.
I've worked back and forth with support from NewPotato, the makers of the tunelink, and they are stumped. They have sent me multiple devices, thinking it was maybe a hardware issue, but nothing seems to work. At first, the device will pair and connect, and music will start playing, but after about 10 minutes, my phone becomes very slow and will eventually reboot itself. After this, the phone will connect but not pair to the tunelink. No matter what I do after the reboot, the phone refuses its connection.
I also have a Jabra Clipper that works perfectly all the time, without problems, and I haven't seen anyone else complain about the CM7 Bluetooth stack.
Anyone else witnessing any problems with any bluetooth device while running CM7?
bump bump bump
Using 7.1-RC1 on an Incredible:
Also having issues with the TuneLink. Worked perfectly on stock ROM, when I switched to CM7 the device will work for about 5 minutes before the BT signal fades out and then I pick up nothing but interference when I play audio. Eventually the device just disconnects from the phone. Then the Bluetooth radio will not reconnect unless I pull the device and then let it sit for awhile.
This is a deal-breaking issue for me now that my iPod Touch is broken. I have to be able to listen to my podcasts in the car. I really don't want to go back to stock.
I should also add that my Bluetooth headphones work just fine with CM7.
Since there are issues with Bluetooth Audio of ICS 4.0.3 is there a way to port the all the Bluetooth associated files for Galaxy S2 in ICS 4.0.3 from the GB rom 2.3.6 or 2.3.9 MIUI. Its is very frustrating when the Bluetooth audio skips at connect.
My problem is the Bluetooth audio connects and everything is fine but when you start playing music it skips at first until you pause the song for few seconds and then press play again. But I cannot do that when using GPS as it cuts the Voice guidance all teh time. The problem is with the Bluetooth AVCRP and associated file.
So I was wondering if it can be ported from GB 2.3.6 or MIUI GB2.3.9? Or is there any other solution to this other then Buying a Nokia or any other phone.
similar problem
I'm interested, too. With 2.3.5 everything fine.
With 4.0.3 occasional bt not connecting, I have to disable and reenable. Also when disabling
Flight mode, bt doesn't return on automatically like wifi.
Omia28000 said:
Since there are issues with Bluetooth Audio of ICS 4.0.3 is there a way to port the all the Bluetooth associated files for Galaxy S2 in ICS 4.0.3 from the GB rom 2.3.6 or 2.3.9 MIUI. Its is very frustrating when the Bluetooth audio skips at connect.
My problem is the Bluetooth audio connects and everything is fine but when you start playing music it skips at first until you pause the song for few seconds and then press play again. But I cannot do that when using GPS as it cuts the Voice guidance all teh time. The problem is with the Bluetooth AVCRP and associated file.
So I was wondering if it can be ported from GB 2.3.6 or MIUI GB2.3.9? Or is there any other solution to this other then Buying a Nokia or any other phone.
Click to expand...
Click to collapse
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
A week or so again I tried hooking up my A2DP bluetooth speaker with my S4, running a 4.2.2 ROM. This bluetooth speaker works great with iphones, my HP Touchpad running CM, and my Galaxy Nexus running 4.1.2. I tried it also with a friend's Note 2, running 4.1.2, and it works fine for him too.
The speaker is this one: http://www.amazon.com/Spracht-Portable-Wireless-Bluetooth-Connectivity/dp/B0023B1364
Though I've owned my S4 for 6 months, it may have been the first time I tried pairing it. It paired fine. However, any music streaming attempts fail horribly. It spurts out a few seconds of sound, then goes silent. Intermittently a few more seconds of sound may pop through. If I hit some of the buttons on the speaker (stereo widening, bass boost), a few more seconds pop through, and then nothing.
This is a bit different than some of the other complaints with 'poor quality' streaming. In this case, it doesn't truly stream much. I reverted back to complete stock and had the same problem.
I remember hearing that with 4.2, there were widespread reports of poor a2dp quality, supposedly fixed with the next version (4.2.1? I forget).
Thinking something might be wrong with the bluetooth on my phone specifically, I obtained warranty service and obtained another brand-new/refurbished S4. Right out of the box same problem. This new phone was also on 4.2.2, stock.
I simultaneously obtained a bluetooth adapter for my car, which is also apt-x capable, and it works great. Maybe the apt-x protocol supersedes the a2dp, I don't know.
Anyone else with an older a2dp (only) bluetooth speaker/headset with similar issues, running 4.2.2?