I've tried all the froyo and gingerbread rooms for my GT540 but none seen to have Bluetooth headsets working. As I use the phone for work and have a long drive coming up it looks like I'm going to have to go back to stock 2.1 so I can drive hands free.
I would have through that due to the legal implications in some countries Bluetooth headsets would be a high priority.
Anyone working on a 2.2+ rom with Bluetooth headset working?
Why don't you try 2.1 ROM soft-modded by MMXTREM ? I found it very fast for a 2.1 ROM (some things like opening the SMS are faster on 2.3 ROMs) and almost 100% stable (Elegance 2.1 ROM had some problems with stability and force closing apps), and with Link2SD you have more than enough space for applications. Also, battery life is double the time on 2.2/2.3 (4-5 days for me, use it mostly for calls and some SMS, wifi 10mins a day).
I run it because of EAP protected wireless networks (2.2 and 2.3 ROMs have some problems with them) and after trying almost all ROMs, had it for the longest time on my phone.
EDIT:
DL for Recovery:
http://fileshare.in.ua/4169544
Thanks would try it if I could get it to download from the link
OK got it from Murz shared folder, Bluetooth works.
Will use this one while I wait for a 2.2 or 2.3 gets sorted
Thanks
Related
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
So I having a recurring problem with all of the non-Sense builds that I've tried here on the forum. The bluetooth would pair and connect perfectly in all the cases. However, the problem arises when I tried to make a call. The phone would freeze up or come to crawling halt. The dialing screen would go black, and then I would get the android.phone.process force close error. And I would need to pull the battery and reboot.
The issue has happened every single time with any of the non-sense builds I've tried so far: NexusHD2-FRG83, HyperDroid v1.6, Bangsters v1.5, and shubCRAFT v1.5.
I've tried with the included kernels with each build, and also with different combinations of kernels with the above builds as well, hasparin r4.1, r7.2, r7.4, r7.5 and michyprima r11. And still the same issue.
I'm certain there are other people with this same exact problem. So there has to be something going on with these non-Sense builds.
I have two bluetooth headsets, Plantronics 925 and 975. Same problems on both.
I don't like Sense, but I have to use a Sense build because bluetooth calling is very important to me. I hope some of you developers can come up with something to fix this.
Hi. I had exactly same problem.
Try to push play&pause music ,start&stop voice action
before start use bt.
Another solution is push bt call button immediate after make call
Sent from my Nexus One using XDA App
That didn't work for me.
I had the same problem as the OP and thats why i switch to a sense build also
Did you try this before?
http://forum.xda-developers.com/showthread.php?p=8348326
zoftdev said:
http://forum.xda-developers.com/showthread.php?p=8348326
Click to expand...
Click to collapse
Yes, I've tried that. But those files are for sense builds, and when I transfer them to a non-sense build, BT wouldn't even turn on.
See the FAQ in my signature. Some of the builders have BT working on CM6 with the EVO kernel so you should soon see builds that support it.
Sent from my HTC HD2
hastarin said:
See the FAQ in my signature. Some of the builders have BT working on CM6 with the EVO kernel so you should soon see builds that support it.
Sent from my HTC HD2
Click to expand...
Click to collapse
Wow! That's superb news.
BT Works
raysacr said:
So I having a recurring problem with all of the non-Sense builds that I've tried here on the forum. The bluetooth would pair and connect perfectly in all the cases. However, the problem arises when I tried to make a call. The phone would freeze up or come to crawling halt. The dialing screen would go black, and then I would get the android.phone.process force close error. And I would need to pull the battery and reboot.
The issue has happened every single time with any of the non-sense builds I've tried so far: NexusHD2-FRG83, HyperDroid v1.6, Bangsters v1.5, and shubCRAFT v1.5.
I've tried with the included kernels with each build, and also with different combinations of kernels with the above builds as well, hasparin r4.1, r7.2, r7.4, r7.5 and michyprima r11. And still the same issue.
I'm certain there are other people with this same exact problem. So there has to be something going on with these non-Sense builds.
I have two bluetooth headsets, Plantronics 925 and 975. Same problems on both.
I don't like Sense, but I have to use a Sense build because bluetooth calling is very important to me. I hope some of you developers can come up with something to fix this.
Click to expand...
Click to collapse
I have been running with BT on several builds for a couple of months now including the NexusHD2-FRG83 builds mentioned above. In fact if a build does not have working BT I skip it. I have found that the first time you install the build and try to use handsfree you need to do the trick of selecting/de-selecting and then selecting BT in the call screen before the actual connection. I use my phone constantly for work with speaker phone (Motorola EQ7) and my headset (BlueAnt T1). No problems making or receiving calls. I use the BT in both phone audio and media audio modes without any issues.
jinharry said:
I have been running with BT on several builds for a couple of months now including the NexusHD2-FRG83 builds mentioned above. In fact if a build does not have working BT I skip it. I have found that the first time you install the build and try to use handsfree you need to do the trick of selecting/de-selecting and then selecting BT in the call screen before the actual connection. I use my phone constantly for work with speaker phone (Motorola EQ7) and my headset (BlueAnt T1). No problems making or receiving calls. I use the BT in both phone audio and media audio modes without any issues.
Click to expand...
Click to collapse
before it's only supported on RMNET or non evo kernel.. the NEW NexusHD2 that was just released now supports BT on all currently available kernels... you don't even have to do the on, off, on trick anymore for the bluetooth to work.. i think it's the closest to being the perfect android build for our HD2.. everything just works including the MMS which i'm having problem with all the sense builds (low res image)..
I will load NexusHD2 1.5 tonight and see what I find
Finally a non-sense build with working bluetooth. I was able to bluetooth music and make a call using my car stereo. I just had to post this. http://forum.xda-developers.com/showthread.php?t=804210
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.
I have tried many cooked ROMS, Darkys, DOC for example and several others. They are all great and fast, a few bugs here and there, but in general I'm a fan, but.
Everyone of them breaks the bluetooth rSAP profile and makes my phone pretty unusable in my Audi.
Symptoms are dropping connection, no phonebook (or intermittent) transfer. No connection at all after it drops until phone is rebooted. Similar problems are with HFP bluetooth profile as well. This is with any cooked ROM.
My only solution to the issues was to install a stock gingerbread 2.3 JVK ROM with no mods.
I have posted a few times on the developers threads but nobody seems interested.
So just a message to developers, what could it possibly be that you are all doing that breaks the bluetooth so badly?
Maybe try a cooked rom but using stock kernel. Don't even root it. If it doesn't than probably it has something to do with the kernel.
Possibly, but most cooked ROMs come pre-rooted with tweaked kernels.
I guess I could build one in the DOC's kitchen without any tweaks.
You only talking about 2.3.3 ROMS? Or does Darky's V9.5 do it as well? If 2.2.1 works fine on a custom ROM, that would be more important to me than having a non-stable gingerbread ROM until Samsung release an official update? V9.5 is pretty unreal so I see no reason to bother with 2.3.3 yet That is if you rely on bluetooth working in your car more than 2.3.3 ^_^
craigyb said:
I have tried many cooked ROMS, Darkys, DOC for example and several others. They are all great and fast, a few bugs here and there, but in general I'm a fan, but.
Everyone of them breaks the bluetooth rSAP profile and makes my phone pretty unusable in my Audi.
Symptoms are dropping connection, no phonebook (or intermittent) transfer. No connection at all after it drops until phone is rebooted. Similar problems are with HFP bluetooth profile as well. This is with any cooked ROM.
My only solution to the issues was to install a stock gingerbread 2.3 JVK ROM with no mods.
I have posted a few times on the developers threads but nobody seems interested.
So just a message to developers, what could it possibly be that you are all doing that breaks the bluetooth so badly?
Click to expand...
Click to collapse
I had same problem... I've changed the kernel to Supercurio kernel and since then not even single problem, else I use to have same problems as u having and were happening several times in a day. Cook a rom in romkitchen with SC kernel and see if that help
It has happened since around 8.0 of Darkys ROM, I must admit I have always used Voodoo Kernels with lagfix, so maybe an SC kernel will fix the issues.
I just installed the stock gingerbread 2.3.3 yesterday afternoon and I've had no issues since, before that the highest release I used was JS8 with the latest ginger modem JVK?
I was on 2.2.1 Ultimate and there wasnt any issues with BT headset stereo using headphone and media profile. It was also working fine with my MB car connections.
Now I'm on Criskelo GB and besides the crappy sound of gingerbread, bt still not an issues with MB car or headset. Criskelo is based on DaminGTO kernel.
It was also working on the Pioneer BT Audio receiver, xplod series.
I never had those problems with using Stock FW.
Now iam on JVK erveryting is fine.
Iam on rSAP with a Mercedes Comand NTG1 + V2 BT Module.
One thing never worked, is the PBAP Phonebook Access Profile,
so only the sim contacts are visible in the comand!
Ok, stock JVK is ok and a cooked JVK ROM from the kitchen with a supercurio kernel is ok as well.
Full phonebook/dialled/missed/received transfer in rSAP mode to my Audi A7 with MMI 4G.
So it seems the issue is Voodoo kernels.
* wifi not working
* bluetooth not working
* no calendar / timer / stopwatch like stock rom
why ?
tested and running on e15i
Wifi and calendar work fine for me, I haven't tried BT, but it should work fine as well. As for the timer/stopwatch you can always download one if you need it, DX probably doesn't use it, so he didn't include it in the FB to make this ROM lighter
sorry my bad wifi works....bluetooth works but at very ver slow rate...
p.s usb connection also takes time to connect, should I switch back to 2.1 stock rom ?
Wifi is Working Fine to me since v005.
Bluetooth is great been using it with my Liveview, 0-2 disconnections for 8hrs
even on my MW600 everything except for the hiccups that occurs at rare times while playing music or watching video's
FroyoBread comes light, so if you need some apps like timer/stopwatch you can download that in market lots of apps there for you and free.