Database Users

Which builds currently have Bluetooth working?

I did a search in here but there are so many results...
I have been playing with the 1.5 build DZO posted on his page. Bluetooth seems to work, but I am having a hard time synching my contacts. Anyone know other builds with functional Bluetooth?

have u tried to
is ur data the problem or is it just ur contacts?

I actually got the contacts synched after a bit of tinkering. Still, I am wondering what other builds have the working bluetooth. I am assuming this is a different beast than the xROMs of a few months ago as it was taken directly from DZO's site.
Does that mean limited bluetooth drivers have been developed for the touch? I was playing around with mine tonight and it was working. If I can have bluetooth on say a 1.6 or a 2.x version of Android, then I may really give up win-mo for good.

yea
I dont believe there is a working 1.6 or 2 with bluetooth.. for now at least. Ur best bet is that build. Its also one of the fastest (if not the fastest) and stable around.

lgevo said:
I dont believe there is a working 1.6 or 2 with bluetooth.. for now at least. Ur best bet is that build. Its also one of the fastest (if not the fastest) and stable around.
Click to expand...
Click to collapse
I'm pretty sure a 1.6 build (like Donut AOSP by plemen) flashed on NAND with dzo's latest kernel will have bluetooth enabled...along with GPS and usb headset audio

[Q] Bluetooth issues with Froyo

So I flashed to a froyo ROM over the weekend and have found someone posted a fix for the gps issues, but I'm having BT issues as well. Has anyone else experienced this: I can pair certain BT accessories but not others, and even when paired the devices cannot connect without multiple connection requests.
My specific issue is that I have motorola rockr bt earbuds, and a Jabra car kit, and they both pair with the phone (after a few trys) but neither will automatically connect to the phone once they're turned on. With the earbuds I have to manually try to connect 6 or 7 times in a row before they'll connect, and even then they may only connect with the phone audio only. This wasn't an issue with the stock ROM so I'm assuming its the bt radio library for Froyo thats the problem?
I'm not new to development, but I'm kinda new to development on Android. I've been trying to learn more about the radios and how they're configured within the OS but I haven't found a lot of good documentation on it. I'd be happy to work this out for myself and post any improved radio to the forum but it would be helpful if someone could send me a link to some learning material? If someone has an improved Epic Froyo BT radio to flash that would be helpful as well

yes bluetooth issues as well, but different in that only when i turn bluetooth on it foreclose's. the bluetooth is otherwise not affeceted. only on the initial start up.

I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!

Delta1Fox said:
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Click to expand...
Click to collapse
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.

revjtanton said:
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
Click to expand...
Click to collapse
I noticed that too with the stock 2.1. However, Bluetooth voice dialing is a feature built into 2.2. I've read that some people having it work great, but other's like myself, are not having it work at all. Oh well. I'll live for now. Hopefully if it isn't fixed beforehand then it'll be fixed with the "official" release. LOL.

now that you mention it, i had this problem too doing some bluetooth file transfers between my buddy and I's phones last night. it struggled to connect multiple times but after the first successful transfer it seemed to stop having problems for a little. I'm moving back to 2.1 until we get some non-beta custom roms for froyo because i use bluetooth and gps everyday. just out of curiosity though, for those who are having problems, which rom and modem are you using?

I put the DI18 modern on there and that has seemed to fix the gps more or less. I think I'm going to go back as well. Maybe I didn't flush data enough times but layar can't find the camera, neither can the bar code scanner...it's close, but Froyo just isn't ready for the Epic yet.
Sent from my SPH-D700 using XDA App

Still having Bluetooth problems with official Froyo release on Epic 4G
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...

I am using the new official Froyo release from Samsung/Sprint. having the same buggy issues I had with the old leaked version.

donkeysauce said:
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
Click to expand...
Click to collapse
I can confirm these issues still exist in the official release.

I'm having the same problem, but when I use bluetooth in my car, it insists on transmitting sounds to my car's bluetooth, even when I repeatedly uncheck Use for media audio. I don't have an option in my car to disable A2DP. My only complaint with Eclair, other than speed (I'm using Bonsai4All, and previously, Syndicate) was that I was running out of space for software (was using EpicExperience). Sometimes, bluetooth won't connect at all, necessitating a phone reboot, or going into airplane moe and then back out. So I'm gathering that this is across the board, regardless of Froyo build? Syndicate didn't work at all with my car.

[Q] Bluetooth keyboard problems

I bought the Mini Bluetooth Keyboard direct from Chinavision. It works OK in WInMo, but nothing will make it work in Android. I would post the link, but posting rules don't allow it.
Has anyone else bought a similar keyboard (I believe they sell a similar one on Amazon) and got it to work? If so, how?
I can pair it OK, but nothing will make it work. I tried the supplied Android driver, but that won't install properly. I tried the various BlueInput apps, but none will connect at all.
Chinavision themselves are not at all co-operative, so I thought I'd ask here.
Thanks in advance,
--
Pete

Just ordered something simular on ebay and waiting for delivery.
I noticed it said that it wouldn't work in Android v2.2 so I guess it will be a bit of a challenge to get it working.

I tried again today. I installed BlueInput v1.8 and had some results, but nothing useful. A click sound comes from the HD2 every time a key is pressed, as per the settings, but no text.
So, something is happening ...
I'm running darkstone SuperRAM Froyo 1.5 on SD.
--
Pete

use cm7. cm implemented support for bluetooth hids.

lolmensch said:
use cm7. cm implemented support for bluetooth hids.
Click to expand...
Click to collapse
cm7?
---
Pete

PeteMy said:
cm7?
---
Pete
Click to expand...
Click to collapse
cyanogen mod 7. it is a popular custom rom. (cyaongen mod 6 will also work but there are almost no roms around here anymore.)

seriously?

even after the 4.2.2 update bluetooth is still not fully working?
Does anyone here use blueput droid ? Basically turns your phone into a touchpad and keyboard for other devices.. but on every rom, i get "bluetooth stack not supported try a rom like cyanogen" but even on cm10.1 i get this -__-
any help?

I get a different issue. If Bluetooth is enabled the Wi-Fi cuts out on certain streaming apps like Skype, groove ip, and even Google + when scrolling quickly through the feed.
Sent from my Nexus 4 using xda app-developers app

brolic925t said:
even after the 4.2.2 update bluetooth is still not fully working?
Does anyone here use blueput droid ? Basically turns your phone into a touchpad and keyboard for other devices.. but on every rom, i get "bluetooth stack not supported try a rom like cyanogen" but even on cm10.1 i get this -__-
any help?
Click to expand...
Click to collapse
I'm not perfectly clear on the exact reasons, but what I've heard is the BT is wonky because Google switched from a closed source, more compatible BT source to a less reliable open source to be more compliant with the open standard that Android is trying to promote. In doing so, it broke some of the functions. They're trying to fix it and did part-way with 4.2.2. Maybe they'll get there eventually, but not in the near-future, I don't think.
Other manufacturers have a second BT stack that they use that is closed source that makes it more compatible with BT devices.
At least that's what I've heard and what I remember. Maybe I'm completely wrong, but thought I'd like to spread the info. It's not the fault of the devs, it's Google.

[Q] Bluetooth woes ,, opinions needed

Have a stock unrooted N4 running the new 4,4,3.
Updated to 4,4,3 solely in the hope it would solve the bluetooth disconnects experienced. Note I did not have 'stuttering' or the like, just solid disconnects which would then auto reconnect in 30-60 sec unfortunately stopping my music app which would then need to be restarted and since I primarily use the BT on my bike or motorcycle it is obviously a pain ....
!!!!!!!!!!!! the update not only has not stopped the disconnects it has now introduced stuttering on occasion (not all the time) ....
Here's where I am at:
1. Live with it until Google finally realizes IT'S A PHONE not a camera or whatever and solves the BT problem or gets the BT folks to do it. (really can't believe they can't solve this or is it just an N4 problem?)
2. Root the phone, install TiBU, backup, wipe and install 4.4.3 factory images, reroot and recover stuff from TiBU ... all this in the hope the BT problem goes away ... chances of this?????
3. Give up and install CM which people say does not have this BT problem ... true??????
Thanks in advance to all for your help and opinions ..........

Could it be
Could it be the BT device itself? Does it work like a charm with other devices?

Electrospaz said:
Could it be the BT device itself? Does it work like a charm with other devices?
Click to expand...
Click to collapse
That's a great question and I am sorry I did not include the info in my original post ... the problem is evident with several different BT devices and these same BT devices work fine connected to other things ..... but not with the N4

zdrifter said:
That's a great question and I am sorry I did not include the info in my original post ... the problem is evident with several different BT devices and these same BT devices work fine connected to other things ..... but not with the N4
Click to expand...
Click to collapse
Has it always been stock? Perhaps your BT adapter in the device is faulty itself. I've ran two different headsets off of mine in the past year as well as connected to my PC and other phones with no issues at all. I've been rooted running beanstock right from day 1 though..

Electrospaz said:
Has it always been stock? Perhaps your BT adapter in the device is faulty itself. I've ran two different headsets off of mine in the past year as well as connected to my PC and other phones with no issues at all. I've been rooted running beanstock right from day 1 though..
Click to expand...
Click to collapse
Yup ... always stock ... when new on whatever version was current then (can't remember) did not have this problem and BT worked fine ........ when they went to the 'low power' BT solution it started.

Was really hoping this update would solve the disconnect problem.