I have tried 4 ROMs but none of them support my bluetooth headset (plantronics backbeat 903+ )???
cm 10.1.2 jenkins was a nice ROM ...but when I connect mobile with bluetooth headset ...it says "Bluetooth pin request rejected by device " ???
There's a known bug for bluetooth a2dp on the CM 10.1.x builds. It's gonna take a while yet before it gets fixed, so if a2dp is really important to you, you should probably try a different rom for now.
____________________
Sent from the moon.
Bluetooth Loops using ROM CM10.2-20131228-Nightly-p500
Syd_M said:
There's a known bug for Bluetooth a2dp on the CM 10.1.x builds. It's gonna take a while yet before it gets fixed, so if a2dp is really important to you, you should probably try a different ROM for now.
____________________
Sent from the moon.
Click to expand...
Click to collapse
I am running ROM 10.2 latest nightly (build cm_p500-userdebug 4.3.1) titled and phone's Bluetooth is not synchronizing, goes into a fast loop (on/off/on/off/on/off/...), detections works on occasion then never completes. I consider Bluetooth availability a safety issue for driving. My question is, has this problem been addressed or does your recommendation to go to another ROM still stand? I like this ROM otherwise, but have to back-out to ROM v10.1 to get Bluetooth to work. thanks.
Also, being the New Year, I wish the team the best of success, health & strength, peace & happiness for the coming year.
o0snoopy0o said:
I am running ROM 10.2 latest nightly (build cm_p500-userdebug 4.3.1) titled and phone's Bluetooth is not synchronizing, goes into a fast loop (on/off/on/off/on/off/...), detections works on occasion then never completes. I consider Bluetooth availability a safety issue for driving. My question is, has this problem been addressed or does your recommendation to go to another ROM still stand? I like this ROM otherwise, but have to back-out to ROM v10.1 to get Bluetooth to work. thanks.
Also, being the New Year, I wish the team the best of success, health & strength, peace & happiness for the coming year.
Click to expand...
Click to collapse
I don't use bluetooth other than for file transfer, so I can't speak from experience. It's probably best to check the various ROM dev threads for more details regarding existing bugs and whatnot. IMHO, if you really want a completely bug-free experience, stick with GB or ICS roms. 10.+ roms are more or less still works in progress. If you're interested in trying out the latest cutting edge releases, though, you might want to give this pre-trimmed KitKat release a try. That, plus sweetnsour's version 13 kernel looks pretty good so far.
Bluetooth Loops using ROM CM10.2-20131228-Nightly-p500
Bluetooth is has been broken for a while then. Can you direct me to the Bluetooth code out of curiosity? Thanks for your reply, i'll take look at pre-trimmed KK. I like to live at the cutting edge so I am tracking KK/CM11 on Jenkins with anticipation and rooting for the team!:fingers-crossed:
Related
All,
Been on Synergy for the past 3 month and my flashing itch is coming back. I want to start trying 4.2.2...getting tired of TW. Has the 4.2.2 Roms gotten stable as a daily driver? I will predominantly using this for work so stability is key and driving, hence the bluetooth functionality.
I was roaming around the thread cyanogen, carbon and liquid and seem like they all have bluetooth issues?
Anybody on a current ROM that have both stability and working bluetooth?
Thanks for any opinion.
cant comment on bluetooth, but they are certainly stable and daily driver worthy.
hopefully someone else can chime in on the bluetooth specifically
Nutzzer said:
All,
Been on Synergy for the past 3 month and my flashing itch is coming back. I want to start trying 4.2.2...getting tired of TW. Has the 4.2.2 Roms gotten stable as a daily driver? I will predominantly using this for work so stability is key and driving, hence the bluetooth functionality.
I was roaming around the thread cyanogen, carbon and liquid and seem like they all have bluetooth issues?
Anybody on a current ROM that have both stability and working bluetooth?
Thanks for any opinion.
Click to expand...
Click to collapse
I use cyberon voice commander for BT voice dialing. I have found on all ASOP roms, it works but the volume is low and there is a delay of up to 5 second in acknowledging the voice command.
Bluetooth works fine for me on a Carbon nightly....really like this ROM.
Sent from my SCH-I535 using Tapatalk 2
LiquisSmooth 2.5 is very stable. Been using it as a DD since January. Bluetooth works fine when I use it, which isn't much.
I have CM 10.1 RC5, and it's the most stable release they have. I believe they fixed the bluetooth a while ago. I only use it for audio streaming to my car, so I can't really comment on headsets or whatever else you might use it for.
But to my knowledge, bluetooth works. :good:
I really like the new features of JB 4.2.2 based ROMs but i have one big issue:
NOWHERE the bluetooth Car Connection A2DB is working!!
I tried Vanilla Rootbox, Avatar, PAC and a few other 4.2.2 (CM10.1 based ) ROMs.
Streaming music to my car is working perfectly, i can sync my contacts to the car but a Phone call just makes "white noise".
I switched to Stock ICS 4.0.4 and here i can use the Car connection and audio is great - but Stock ICS this is abslutely not my taste.
For about 2 Weeks i'm searching for a solution now without any success
Anybody has any suggestion for a ROM, Hack or fix? <- PLEASE!
btw: Vanilla Rootbox 7 for Galaxy S is working - why not on Galaxy R??
Torpedro1978 said:
I really like the new features of JB 4.2.2 based ROMs but i have one big issue:
NOWHERE the bluetooth Car Connection A2DB is working!!
I tried Vanilla Rootbox, Avatar, PAC and a few other 4.2.2 (CM10.1 based ) ROMs.
Streaming music to my car is working perfectly, i can sync my contacts to the car but a Phone call just makes "white noise".
I switched to Stock ICS 4.0.4 and here i can use the Car connection and audio is great - but Stock ICS this is abslutely not my taste.
For about 2 Weeks i'm searching for a solution now without any success
Anybody has any suggestion for a ROM, Hack or fix? <- PLEASE!
btw: Vanilla Rootbox 7 for Galaxy S is working - why not on Galaxy R??
Click to expand...
Click to collapse
I think its known bug buddy. Let it be fixed.
Thin is a known bug since at least january!! I thought ast least one ROM could be there where this basic wefa
Don't get me wrong all the devs do a really great job here!!
But why is the priority if implementing the basic features so the ROM gets usable so extremely low??
Who do i have to donate to get this fixed?
I would be availabe as a tester for Car Bluetooth
Torpedro1978 said:
Thin is a known bug since at least january!! I thought ast least one ROM could be there where this basic wefa
Don't get me wrong all the devs do a really great job here!!
But why is the priority if implementing the basic features so the ROM gets usable so extremely low??
Who do i have to donate to get this fixed?
I would be availabe as a tester for Car Bluetooth
Click to expand...
Click to collapse
Who do i have to donate to get this fixed? - Buddy, Please elaborate this line.
Also, When Devs works over any project, then they fix Major problem, not the basic one.
So let Dev to handle this.
Devs r working on it..u just have to be patient n everyone knows dey can get it done..respect wat dey have done to our device which ll not be having 4.2.2 if dey wer not der..if ur desperate to use Bluetooth a2dp, den switch over to ics
Sent from my GT-I9103 using xda app-developers app
Disturbed™ said:
Who do i have to donate to get this fixed? - Buddy, Please elaborate this line.
Also, When Devs works over any project, then they fix Major problem, not the basic one.
So let Dev to handle this.
Click to expand...
Click to collapse
First thank you both for your answers!
I did not intend to offend somebody - sorry if it came over this way. I'm just telling my experiences and maybe i cannot write it in a polite enough manner (which is a known bug in my personal firmware).
I do respect all the devs! I already said they do a great job!
JB (CM10.1) based ROMs are great with battery life, usability, flexibility, features and everything works - except receiving calls an A2DB car hands free calling.
I tried serveral JB ROMs for a few months now, because i really like it - but my wife got crazy by now! She could almost never reach me, because the phone ignores incoming calls when it's in deep sleep or roaming - a known bug, i know. This one must be a lot harder to fix than a simple Bluetooth audio config which is 98% working anyway - thats way i just asked if there was a fix i didn't find.
On other Devices these features seem to be much easier than on the Galaxy R because both these issues are forking perfectly on our Galaxy S (1).
Regard Donation: Well, i thought the problem with this fix is that somebody might be missing a bluetooth headset to test it.
Since Media A2DB works but Hands free Calling does NOT i thought it might be just something VERY simple to fix and just the needed test-equipment is missing..
According to your recomendation i'm back to ICS Blueberry.
Thank you again!
I have the bluetooth handset.. And I know how to test Self... But no time...
Sent from my GT-I9103 using xda app-developers app
First of all, a big thank you to the CM team from a relative noob, for all their great work.
I checked the forums, and there was an issue reported on 9 July about BT randomly turning off, and only fix to turn it on being to reboot. I have experienced the same problem in CM 10.0 stable, 10.1 stable, and now 10.1.2. Not a major issue, but an annoyance - was wondering of there is a fix for that?
Thanks
Raj
Running on Samsung Galaxy SII Skyrocket on CM 10.1.2, radio UCMC1, Gapps
Not an official one, no, I have had the issue since the 4/24 build, but with some recent commits shortly after 10.1.1 it's been much better, but still not 100%. I know carvsdriver has identified the issue and just needs to get some time in to fix it, so it should be coming soon-ish to the latest nightlies. I don't know how likely it would be to get into a 'stable' release very soon, but for me, the nightlies are way better than the stable releases anyway.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
BT Problems - Getting better
rajb12 said:
First of all, a big thank you to the CM team from a relative noob, for all their great work.
I checked the forums, and there was an issue reported on 9 July about BT randomly turning off, and only fix to turn it on being to reboot. I have experienced the same problem in CM 10.0 stable, 10.1 stable, and now 10.1.2. Not a major issue, but an annoyance - was wondering of there is a fix for that?
Thanks
Raj
Running on Samsung Galaxy SII Skyrocket on CM 10.1.2, radio UCMC1, Gapps
Click to expand...
Click to collapse
I caught a fix for BT in the changelogs on the CM 10.1 nightlies. Just ran the latest nightly update a few nights ago and seems to be much better.
Of course your mileage may vary but if you need some better BT performance in CM10.1 on the Skyrocket, I can vouch that it is now better. For me on 10.1 Stable, BT would turn off if I screwed around a few times with it (pairing and unpairing devices) and would force me to have to reboot to use a new pairing. BT would actually turn off and stay off after enough BT actions. Reboot was only fix. Knock on wood, now I can use the BT settings without problems. I'm hoping nothing bad pops up but I think there are definite BT improvements with the latest nightlies...
SGH-i727
UCMC1 Radio
CM10.1 - 20130727 - Nightly Update
cejack said:
I caught a fix for BT in the changelogs on the CM 10.1 nightlies. Just ran the latest nightly update a few nights ago and seems to be much better.
Of course your mileage may vary but if you need some better BT performance in CM10.1 on the Skyrocket, I can vouch that it is now better. For me on 10.1 Stable, BT would turn off if I screwed around a few times with it (pairing and unpairing devices) and would force me to have to reboot to use a new pairing. BT would actually turn off and stay off after enough BT actions. Reboot was only fix. Knock on wood, now I can use the BT settings without problems. I'm hoping nothing bad pops up but I think there are definite BT improvements with the latest nightlies...
SGH-i727
UCMC1 Radio
CM10.1 - 20130727 - Nightly Update
Click to expand...
Click to collapse
I don't know that the commit was a complete fix, but it certainly helped. I saw a post on G+ about it (I think), and the developer mentioned that after 30 BT connections/re-connections, it would stop working, and that it would be hard to fix. It's definitely way better than it was.
Stereo Bluetooth works pretty well. Just listened to 3-4 hour podcast with Stereo Bluetooth P311 headphones.
Also used Motorola H500 bluetooth headset as well. No problem there. Also using 9XX Plantronics headset. No problem either.
All in all - can't complain about BT too much anymore after going from latest stable to more recent "nightly" releases.
If you run into problem.... you'll have to re-boot.
Thanks to all the developer of CM 10.1 for a great ROM which has become my DD. One question: Bluetooth still requires an occasional reboot in the latest nightlies. With CM 10.1 now in maintenance mode, is this the best we can expect or is there still ongoing work to fix the problem for good? I have just been rebooting once in the AM, so I don’t get a surprise when I try to use BT in my car, so it’s not a showstopper. Just curious.
chas101 said:
Thanks to all the developer of CM 10.1 for a great ROM which has become my DD. One question: Bluetooth still requires an occasional reboot in the latest nightlies. With CM 10.1 now in maintenance mode, is this the best we can expect or is there still ongoing work to fix the problem for good? I have just been rebooting once in the AM, so I don’t get a surprise when I try to use BT in my car, so it’s not a showstopper. Just curious.
Click to expand...
Click to collapse
All I can say is that with 4.3 (CM 10.2), in the past week I have only had to reboot once to fix bluetooth issues, that I can remember.
As many of you know, our device and 4.4 dont work together when calling someone via bluetooth.
I would like to offer anyone that can come up with a fix a (big) donation (via paypal?).
The fix, has to be in a flashable 4.4 rom as I can not compile roms myself to test this.
Regards,
DeKiesel
this is a great idea, I will donate to the programmer who creates it to solve the problem :good:
*push*
Good Morning Developer is nothing for you. A premium for your success
I will also donate to the developer that solves the issue with the Bluetooth.
With some positive mistake, on SlimKat for I9105P we got bluetooth headset working.
As i compiled with help from @LuK1337 we created that rom who is in beta now, and by mistake have working bt hd.
If someone want to donate for the bt hd fix, he needs to donate to Lukasz. Then we will talk about percent etc.
Thanks!
cicibanko101 said:
With some positive mistake, on SlimKat for I9105P we got bluetooth headset working.
As i compiled with help from @LuK1337 we created that rom who is in beta now, and by mistake have working bt hd.
If someone want to donate for the bt hd fix, he needs to donate to Lukasz. Then we will talk about percent etc.
Thanks!
Click to expand...
Click to collapse
Wow, thats awesome news! I will test it as soon as I can (after work)!.
Thanks!
For now, 3 users of SlimKat reported that BT HD is working via BT Headphones (sound is great) and via Earing BT device, sound is a little bit noisy.
Sent from Unicorn
Hello,
For me SlimKat Beta with the gapps included in the rom's topic doesn't work. it's the same as the other rom's. Loud noise and the call ends after 2 seconds. Two persons tested it (me in the morning, and me at lunch break ) I'll attach a log as soon as i get home.
If anyone has it working on a car system please let me know. I might do something wrong.
Thank you anyway for the nice ROM eventhou it needs some small touches to make it smooth and fast.
Best regards to you all !
YEAH GREAT NEWS :good::good:
I still have the same issues as with other roms :/
/edit: for the community: what changes did you make that made you think the bluetooth issue was resolved?
so the bluetooth works, or not ?
now I have installed CM11 and I do not want to change ROM, untill i have assured that BT working
It depends on what part of bluetooth. Streaming musik t.ex. is fine but calls via bt are not.
Same issue in all the roms, including CM11
exactly, I care about bt calls
I try to be up to date
recently few new roms shows
and unfortunately bt calls not work
I think it will never be corrected, sad, only few people needs it
BT call not work in all rom ?
happyrik said:
BT call not work in all rom ?
Click to expand...
Click to collapse
YES in all Rom with Source CM11 and this is for ALL Kit Kat Custom Roms for SG 2+
Ronytiger said:
YES in all Rom with Source CM11 and this is for ALL Kit Kat Custom Roms for SG 2+
Click to expand...
Click to collapse
*All not stock based roms.
So i testet CM11 M9 yesterday:
BT Freespeaking not Work
NFC not work with my Smartwatch
Problem was not fixed :crying:
is there any chance, that it will ever works ?
fipil said:
is there any chance, that it will ever works ?
Click to expand...
Click to collapse
no.
can you shortly explain why ?
I have read through several of the ROM threads and trying to determine which ROM and/or ROM+Kernel+Config combination works towards a stable bluetooth configuration.
I've had intermittent bluetooth connection drops on several of the CM 12 nightlies. In some cases, I've had audio issues as well.
If someone has a Lollipop based working configuration that enables a stable bluetooth, please share.
geeoat said:
I have read through several of the ROM threads and trying to determine which ROM and/or ROM+Kernel+Config combination works towards a stable bluetooth configuration.
I've had intermittent bluetooth connection drops on several of the CM 12 nightlies. In some cases, I've had audio issues as well.
If someone has a Lollipop based working configuration that enables a stable bluetooth, please share.
Click to expand...
Click to collapse
BlissPop worked great up until about a week ago with just the regular installation, no tweaks. CM then introduced some new commits regarding bluetooth, so as far as I can tell, all CM-based ROMs will have the same issue now (and I've tested over a half-dozen so far). DarkoBass is mostly AOSP, I believe, and it didn't seem to have any issues - made it through a few songs with no stutter - but I missed too many other features from BlissPop so I went back tweaking it with Boeffla to find a solution. ParanoidAndroid is mostly AOSP as well - I bet bluetooth on it would work fine, and they just released an alpha build today, I think. Might just give it a try myself...
How about veneer?
Sent from my A0001 using Tapatalk
cymbaline24 said:
BlissPop worked great up until about a week ago with just the regular installation, no tweaks. CM then introduced some new commits regarding bluetooth, so as far as I can tell, all CM-based ROMs will have the same issue now (and I've tested over a half-dozen so far). DarkoBass is mostly AOSP, I believe, and it didn't seem to have any issues - made it through a few songs with no stutter - but I missed too many other features from BlissPop so I went back tweaking it with Boeffla to find a solution. ParanoidAndroid is mostly AOSP as well - I bet bluetooth on it would work fine, and they just released an alpha build today, I think. Might just give it a try myself...
Click to expand...
Click to collapse
It's been glitchy for a while. Are they planning on fixing it or is it unfixable?
Demontooth said:
It's been glitchy for a while. Are they planning on fixing it or is it unfixable?
Click to expand...
Click to collapse
CM has been working on it; I believe they just pushed two new BT commits to try to fix some of the issues in the last day or so. I haven't tried out any updated ROMs to see if it helped yet. I reluctantly left BlissPop and tried out Slim Saber with AK kernel (someone somewhere said BT worked on it) and after a couple kernel tweaks I didn't have a single skip to or from work today. And it turns out it's a pretty damn good ROM too.
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
fireforhire said:
How about veneer?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Won't swear to it, but I'm pretty sure that's one of the ones I tried and it still skipped.
CM12 Nightlies are working fine for me with BT. It used to be terrible but it's great now.
cymbaline24 said:
BlissPop worked great up until about a week ago with just the regular installation, no tweaks. CM then introduced some new commits regarding bluetooth, so as far as I can tell, all CM-based ROMs will have the same issue now (and Ive tested over a half-dozen so far). DarkoBass is mostly AOSP, I believe, and it didnt seem to have any issues - made it through a few songs with no stutter - but I missed too many other features from BlissPop so I went back tweaking it with Boeffla to find a solution. ParanoidAndroid is mostly AOSP as well - I bet bluetooth on it would work fine, and they just released an alpha build today, I think. Might just give it a try myself...
Click to expand...
Click to collapse
Blisspop?The romer who copyed mokee,which is a rom based CM
BlakeSm said:
CM12 Nightlies are working fine for me with BT. It used to be terrible but it's great now.
Click to expand...
Click to collapse
It was a little better today.
geeoat said:
I have read through several of the ROM threads and trying to determine which ROM and/or ROM+Kernel+Config combination works towards a stable bluetooth configuration.
I've had intermittent bluetooth connection drops on several of the CM 12 nightlies. In some cases, I've had audio issues as well.
If someone has a Lollipop based working configuration that enables a stable bluetooth, please share.
Click to expand...
Click to collapse
BlissPop should work just fine.
No BT playback problems with Validus ROM
geeoat said:
I have read through several of the ROM threads and trying to determine which ROM and/or ROM+Kernel+Config combination works towards a stable bluetooth configuration.
I've had intermittent bluetooth connection drops on several of the CM 12 nightlies. In some cases, I've had audio issues as well.
If someone has a Lollipop based working configuration that enables a stable bluetooth, please share.
Click to expand...
Click to collapse
Had continuing problems with Temasek nightly. Switched to [ROM][5.0.2][02/04][OFFICIAL] GzRoms -Validus- [v7][Bacon] yesterday and have had zero BT music playback issues with Performance mode enabled. Couldn't be happier with this ROM.