• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Bluetooth Fix for AOSP ROMs?

WA_Bob

Android Expert
Hi all!

I've seen here and on the Rootz forums that I'm not the only one who seems to be having problems with my Bluetooth earpiece working with my TB. For some reason CM7.1.1, Shift Theory, and Liquid all leave me with no connection to the phone or really crappy audio if it does connect. I've had no problems connecting on various Sense ROMs or before now on AOSP ones so I have to assume it isn't the phone or the earpiece. But I also know this isn't happening to a large number of TB owners or there'd be more questions out there.

Does anyone know of a fix for this or are there too few of us with this issue for it to be of great concern?
 
Hi all!

I've seen here and on the Rootz forums that I'm not the only one who seems to be having problems with my Bluetooth earpiece working with my TB. For some reason CM7.1.1, Shift Theory, and Liquid all leave me with no connection to the phone or really crappy audio if it does connect. I've had no problems connecting on various Sense ROMs or before now on AOSP ones so I have to assume it isn't the phone or the earpiece. But I also know this isn't happening to a large number of TB owners or there'd be more questions out there.

Does anyone know of a fix for this or are there too few of us with this issue for it to be of great concern?

Hi,
I too have run aosp roms and get poor quality on bluetooth phone calls people sound over modulated. I have been able to narrow down that this occurs with cell calls, if a landline person calls np?
I wonder if cell calls are amplified more and that's why we get bad sound on bluetooth.
I have been able to reduce some of the problem by running the app that is part of the aosp roms called DSPManager.
I have these settings : in app choose bluetooth device , enable compression, select effect strength to extreme, then enable equalizer, select preset vocal booster, that's it.
I have no other options selected and this has helped :-)
Do this when not on a call it will take effect on the next call you make on bluetooth!

Hopefully this will be ironed out with the leak of the new verizon ota release the bluetooth section can be used.

I wonder if we could take the Bluetooth.apk from the Verizon release and replace the one in the AOSP rom? Like was done with the location problem we had...

Thanks,
Bryan
 
Yeah, that sounds like mine when it will connect. Thanks - I'll give that a try later this afternoon after work.

And I couldn't pull out the bluetooth.apk myself so I'll wait for someone smarter than I to tackle it! :D
 
Yeah, that sounds like mine when it will connect. Thanks - I'll give that a try later this afternoon after work.

And I couldn't pull out the bluetooth.apk myself so I'll wait for someone smarter than I to tackle it! :D

Hope it helps you out :-)
Is there a way to pull out the apk from the image without having to install it and then copying it out to the sdcard?

Thanks,
Bryan
 
Well, changed the DSP settings and it worked for the audio. As for connection, that's still a crapshoot but 1 out of 2 is an improvement at least. Thanks for the advice!

Now to wait for someone to fix it for real.
 
I pulled this Bluetooth.apk from an older version of CM7 (1.6.1 to be exact). Either of you want to try it? Just use root explorer and got to system/app. Find your current bluetooth.apk and long press>permissions. Remember what they are and now rename the file to bluetooth.apk.bak. This will render the app useless while you test the new one.

Now, move the new bluetooth.apk from your SD card to system/app. Make sure the permissions are the same, or change them to what the permission on the other bluetooth.apk were.

Reboot and test. If for some reason it doesn't work, just delete the new bluetooth.apk and rename the old one back to bluetooth.apk and reboot again.

If you want to be extra cautious, which isn't a bad thing, take 5 minutes and make a nandroid before testing this. I don't use bluetooth so I can't test it for you guys personally. Let me know how it goes. Just remember, I'm not responsible if your phone blows up ;)
 

Attachments

Thanks Worm! I'll give it a shot today. And if it blows up my phone, I'll just blame my parents for not loving me enough. :D
 
i havent had any prollem with bluetooth for several versions of cm7 now. my phone conects right away,connects and reconnects if i get out of range for a minute,and i can hear fine on it.

maybe something to do with the earpiece itself?

i talk on my BT for 3-4 hours a day,so its a pretty important aspect of a rom that im considering useing. ;)

cm7 even works better for me,as on stock roms,if i get a text message or other notification,it knocks out my connection on every stock 2.3.4 based rom ive tried :mad: ill have to shut every thing off and repair it to get it working again.

the ONLY prollem i have,is that if i stay out of range for long enuff,my BT will only connect to media audio when im back in range. ill have to turn the earpiece off,toggle BT off then on,and turn the ear piece back on to fix it. this however,seems to be a particular issue with my particular earpiece(platronics voyager) as it does this on EVERY rom ive run,on every phone ive had :eek: ;)

how did you install cm7? rom manager? recovery? did you "update" or clean install? a fresh,clean install may help if you did use rom manager,or flsahed over a previous version. also,do not try and backup up BT settings,etc. with titanium,manually re-pair it on each new install.

good luck :)
 
I'm on CM7.1 been installing and managing through TWRP 1.1.1 recently. It doesn't seem to matter if I wiped it clean and re installed after wiping my phone "clean" or flashing a recovery - still have heck getting it to work. I had been trying to restore bluetooth connections via Titanium and I can stop that. But if it's my earpiece, I don't understand why it would work fine on Sense ROMs and not on AOSP ones. :confused:

BTW:I've never had the text message problem you mention and my connection has always restored like yours if I drift in and out of range.

I'll just got done setting up Worm's file and I'll see what happens with it. All-in-all, just very confusing
 
Hey! It worked! All's right in my Bluetooth world again. Thanks again Worm! I still don't know what happened, but this fix will work until then next update of CM7 and others hopefully fix it on their own.
 
Hi,
Well I didn't have any problems with bluetooth connecting...
My issues only seems to be when I talk to someone they are very overmodulated. I seem to notice that when it happens they are on a cell phone np problem with landline calls ok its weird but consistent.

I should of preface this to say that I am using Liquid 3.0

So I tried worms file (bluetooth.apk) from cm1.6 (thanks worm).
Found it didnt help had same trouble so sad...
Then had a thought we just had a verizon/htc gb leak maybe that will work?
Got the leak pulled out of the zip the bluetooth.apk and did the same replace procedure..
Only problem is will have to wait till tomorrow to test this out since I hook up to bluetooth in the car where the problem happens.
I am using imo 4.0 kernel. if this doesn't work thinking of going to 4.1 I do have to say I had the same issue with roms stock kernel (tiamet).
Oh by the way didn't have a problem with car until rooted and flashed...
I also disabled using the dspmanager since that reduces it a bit but would like to find the root cause and fix... and didnt want it to confuse the tests.
Might retest this with a sense kernel to see how it is with that.

Ouch my head hurts :eek:

Thanks for reading to this point any suggestions or advice appreciated.
 
So I have been hunting for this sort of thing far longer then I like to admit. I signed up with this forum just to talk on this subject.

The reason I am looking for the cyanogenmod 7 Bluetooth stack, is because the rest of the Thunderbolt ROMs don't seem to work with the PS3 or WII remotes. only the cyanogenmod 7 ROM works. As I have read and seen the cyanogenmod 7 ROM is entirely compatible with my lovely Thunderbolt.

Now currently I am running Killasense 3.7.19, Literally just installed it and must fix a couple things before I proceed. I guess I am wondering if this will work for what I am trying to do.

Will I be able to apply this Bluetooth stack to my current Killasense rom and have it work with my ps3 controller.

Will update my kernel to fix the camcorder issue then will push this bluetooth.

WISH ME LUCK!
 
I have an Acer liquid metal, (S120) have recently installed "[ROM] HOLO-CM7 the really CM10 experience on Metal! (22/04/2013)" it's CM7.2 Base: CM7 Nightly build date 01/03/2013. Have been looking for a solution / work around for a few days now, I heard apparently the bluetooth apk file from earlier versions of CM7 work ok? I liked worms suggestion of the bluetooth APK file but I tried that method but couldn't find it in ES file explorer. perhaps it's phone specific?? Any ideas would be great, sorry for replying on an old thread. Cheers, Dani.
 
Back
Top Bottom