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 ?
Related
I cannot pair my vehicle's headunit to a CM-powered device, starting with CM6 RC2. (RC1 worked as expected).
I would like to build the stock Android Bluetooth stack and replace that portion of CM with it, in an effort to see if it resolves this problem for me. I'm also curious how the new Bluetooth stack in Gingerbread will behave, as it's apparently received an overhaul.
Ultimately, I'd like provide a package so that CM users could easily "flash" a new BT stack if they're having problems with CM's modified version.
I'm a junior developer, and I have Ubuntu on my machine, as well as AOSP Gingerbread and CM6/7, all building correctly. However, I lack the knowledge (or even a starting point) on what I need to do to accomplish this.
Anyone willing to offer some advice?
Additionally, if anyone else out there is having problems, please post here--once I get this working, I'll need test candidates to see if it helps resolve their issues as well.
EDIT: Starting here. http://source.android.com/porting/bluetooth.html
Never had an issue with bluetooth and my vehicle or a couple of others while running CM 6.x or any of the nightly builds of cm6. Sometimes a kernal I flashed would break it, but otherwise it worked fine. I done this one both a alpine blue tooth module and factory ones.
What are you syncing to?
aduljr, the type of headunit I have is called "BlueConnect", and is built-in to my 2009 model year Hyundai Elantra. This is the manufacturer's website: http://www.autointelligence.com/
Like I said, it worked with CM6.0.0 RC1, but stopped working starting with RC2 and hasn't worked since.
So far I've started reading about the BlueZ stack, but haven't made more progress than simply reviewing some make files.
As always, if anyone has any pointers (or if anyone is also having BT-related problems), please post.
Thanks.
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
timwoj said:
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
Click to expand...
Click to collapse
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Shidell said:
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
have you tried updating to cm6.1 and trying with a stock kernel?
jsseidel1 said:
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
Click to expand...
Click to collapse
Interesting, and appreciated. I'll look into a Google Group, although for now I'll work out of this thread unless this grows into a large project.
BrianDigital said:
have you tried updating to cm6.1 and trying with a stock kernel?
Click to expand...
Click to collapse
I have tried 6.1 with an alternative kernel (Kings) to no avail. Do you have a kernel you'd suggest I pair with 6.1 for testing purposes? I'm more than willing to do so for testing purposes.
Shidell said:
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
Basically, I'd like to be able to tether my phone over BT. The Evo doesn't provide a DUN or PAN service that OS X can see (never tried windows), so things like Android-Wifi-Tether don't work in bluetooth mode.
does you phone work with any other bluetooth device?
aduljr said:
does you phone work with any other bluetooth device?
Click to expand...
Click to collapse
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
BuddaBelly said:
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
Click to expand...
Click to collapse
+1 I have this same problem. CM has a much weaker bluetooth connection than Sense ROMs. I would love to be able to flash something over CM7 to increase bluetooth reliability, even if it hurts battery life (you could always turn bluetooth off when you need to save battery).
Shidell said:
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
Click to expand...
Click to collapse
ill try this as i have the cutting out issue as well
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
allroy1975 said:
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
my wifi is never on. and even when it is it doesnt do it on sense roms.
zikronix said:
my wifi is never on. and even when it is it doesnt do it on sense roms.
Click to expand...
Click to collapse
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
BuddaBelly said:
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, wouldn't it be easier to look back into the git commits for the CM repository. And see what changed in the bluetooth files after 6.0.0? That way you should be able to drop in the older bluetooth stuff, and have it work. Then you can try to convert that stuff to work in CM7?
timwoj said:
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
Click to expand...
Click to collapse
If you use AWT and set it to Bluetooth mode and then turn it on, the PAN service will magically be created, but only while tethering is turned on. However, I still wasn't able to get Bluetooth tether to work because of some kind of IP address error in AWT. I think AWT wasn't able to set an IP address for the Bluetooth PAN adapter. My computer was able to see the Bluetooth PAN but wasn't able to pull an IP address to fully complete the connection.
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
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:
Hello, guys,
I currently am on ProBAM, which is a nice ROM, but car bluetooth is very buggy. The sound quality is quite low, and sometimes I have to press the green button many times before it actually answers - and at times it doesn't at all.
What I'd like to know is how good does this feature work on your ROM, so that I can decide which one to flash.
Thank you in advance.
Pkmns said:
Hello, guys,
I currently am on ProBAM, which is a nice ROM, but car bluetooth is very buggy. The sound quality is quite low, and sometimes I have to press the green button many times before it actually answers - and at times it doesn't at all.
What I'd like to know is how good does this feature work on your ROM, so that I can decide which one to flash.
Thank you in advance.
Click to expand...
Click to collapse
you can try liquidsmooth alpha9. works like charm..
maxs8007 said:
you can try liquidsmooth alpha9. works like charm..
Click to expand...
Click to collapse
i have tried almost all variety of ROMS, the latest 4.3.3 or any of the custom ROMs have issues with car bluetooth. the most stablest i have found is DDLF2 or stock gingerbread or FlyGB.
also i have noticed when the car wants to download the contacts, if you accept it, the bluetooth connections gets buggy, hence suggest not to accept to download contacts.
regards
venky
Have you triedthis?
http://forum.xda-developers.com/showpost.php?p=45643437&postcount=33
well cyanogenmod 11 resumes cm11 for our phone :angel:
cm-11-20141027-EXPERIMENTAL-taoshan.zip
Is stable ?
davidhor21 said:
Is stable ?
Click to expand...
Click to collapse
same issue with FXP 343 no signal (blinking signal icon)
well i played the ROM a bit some bugs are fixed like front camera (video mode)
well i reverted back my old ROM
ehehe its nice to see cyanogemod continue CM11
waiting tomorrow for nightly release.. i hoped signal is fix.
thats nice.
@varun.chitre15 is this coming from you? or just CM it self?
Pleasee!!
which bugs have this android version ?? and if someone could tell me out into a stable version for the Xperia l ?
Milleto05 said:
which bugs have this android version ?? and if someone could tell me out into a stable version for the Xperia l ?
Click to expand...
Click to collapse
try it by yourself
Joel16 said:
@varun.chitre15 is this coming from you? or just CM it self?
Click to expand...
Click to collapse
It's an experimental build triggered by me.
There is one more coming in few hours, I need you all to test that new one and check if the recently introduced 'No signal' problem is fixed.
It's working for me. Poland, both 3g and 2g.
Sent from my C2105 using XDA Free mobile app
cm
Hello, haw can i make incoming call glowdots background transparent?
varun.chitre15 said:
It's an experimental build triggered by me.
There is one more coming in few hours, I need you all to test that new one and check if the recently introduced 'No signal' problem is fixed.
Click to expand...
Click to collapse
I understand that you had been busy with android One devices and recently Xiaomi Mi3 device. I am not sure congrats be enough for I believe that it needs more recognition !
I checked them all out and that's greatest work but sadly couldn't test it due to unavailability of Android One in Europe.
I understand how much effort and work is required and one single mistake in code can increase errors by many folds. I know it's already a tough job to code and with all the nagging and hate you got for some xperia L users must be very disheartening.
Even if you discarded Xperia L out of further development, I wouldn't have blamed you for all many greedy users did to you.
With all that going on, it's very good to see your support and love for the Xperia L once again which obviously has kept me & many others away from the thought of selling it away.
I hope you continue to work for Android projects as a whole and wish you every luck to make all your work to further success.
P.S: Xperia L Users
Never ask for ETA or when any bug would be fixed and whine like a bit**. He got a life and he does everything for free. You do owe him for using his works but he doesn't owe you at all even if you make a donation.
He gives you time from a lot of his hobbies, family, friends and I'm sure a lot more to bring you his ROMs. He is as human as you , maybe more if you can't see that he has cutting his time from his life and giving it to you to make some Roms and kernel for you.
Instead of being thankful and grateful, don't be a **** to trouble him.
He deserves every support and thank for his each work and you shouldn't take that away from him.
I hope this comes to you as some insight how hard it is to be in his shoes and you should respect that regardless of if he decides to quit development for Xperia L or any device.
@varun.chitre15, Thank you very much for your hard work on our Taoshan.
Long life to the development Taoshan. !!
varun.chitre15 said:
It's an experimental build triggered by me.
There is one more coming in few hours, I need you all to test that new one and check if the recently introduced 'No signal' problem is fixed.
Click to expand...
Click to collapse
Thanks, will try this one ASAP
Ok phone 2g/3g works
varun.chitre15 said:
It's an experimental build triggered by me.
There is one more coming in few hours, I need you all to test that new one and check if the recently introduced 'No signal' problem is fixed.
Click to expand...
Click to collapse
Dirty flashed cm-11-20141028-EXPERIMENTAL-RIL-taoshan over FXP341, also flashed Thunderzap. Data connection works correctly (E, 3G and H+ tested).
Sent from my C2105 using Tapatalk
I tested EXPERIMENTAL-RIL, and everything works perfectly for me
Meanwhile, is there any updates to hwcomposer? those graphical bugs are annoying
any nightly updates ?
I am using the nightly for three months now and I am satisfied.... The experimental is going to be nightly soon? or stable perhaps?
Sent from my C2105 using XDA Free mobile app
maa chuda