Bluetooth problem - need help
Here is my situation. I have a EVO 4G Rooted with rooted 3.29.651.5.
My phone's bluetooth paired perfectly with my car for several months.
Then I installed Vlingo and my bluetooth stopped working with my car. I uninstalled Vlingo and the bluetooth worked only sporadically. Since then I have tried almost everything I can and have searched for weeks to get this to work.
I have tried:
* complete wipe and reinstall of ota rooted rom
* reinstalled Vlingo tested, then unistalled again
* deleted and then restored backups of BrcmBlueToothServices 1.0 and Bluetooth Share 2.2
* deleted BrcmBlueToothServices 1.0 and Bluetooth Share 2.2 then flashed rooted ota rom to get clean copies back again (I hope)
* Unpaired my Evo from my car then paired them again.
* Upgraded to rooted 3.30.651.2n.
* Flashed a new King's Kernel #11 (2.6.32.24-king-hav-OcUv)
I know it is not my car as my wife as the same phone I have. I rooted it and except for the recent kernel change on my phone the only real difference is that I never put Vlingo on her phone. I can pair her phone perfectly with my car and it works great just like mine did before Vlingo.
I'm not an expert, my learning curve was huge to get to root and I have done a lot of reading to try to figure this out.
ANY help would be appreciated! I need my phone to work with my car as I'm on the phone a lot.
The kernels will break bluetooth on the CM builds.
The CM framework has been redone and there are few compatable kernels. Yes kings kernel will work, but not everything. Currently, there is no custom kernel (beside the stock CM kernel in each build) that will work and keep bluetooth working on CM roms
kthejoker20 said:
The kernels will break bluetooth on the CM builds.
The CM framework has been redone and there are few comparable kernels. Yes kings kernel will work, but not everything. Currently, there is no custom kernel (beside the stock CM kernel in each build) that will work and keep bluetooth working on CM roms
Click to expand...
Click to collapse
Thanks You very much for your response. Since my technical level is a little limited let me see if I understand. You are saying that my rooted stock ROM is a Cyanogen Mod Build. That ROMS made using this with stock kernels should work with Bluetooth, but if you use a custom kernel there could be a problem.
If this a correct understanding, the only problem is that I was using the stock kernel that came with the ROM and it was working fine for weeks. Then I installed Vlingo and the problem arose. I then unistalled Vlingo and the problem still persisted. Days later I then switched kernels in an attempt to fix the problem. I have the same problem regardless of which kernel I use.
Do you have a suggestion for a solution? Again, thank you.
bluetooth
nykbob said:
Thanks You very much for your response. Since my technical level is a little limited let me see if I understand. You are saying that my rooted stock ROM is a Cyanogen Mod Build. That ROMS made using this with stock kernels should work with Bluetooth, but if you use a custom kernel there could be a problem.
If this a correct understanding, the only problem is that I was using the stock kernel that came with the ROM and it was working fine for weeks. Then I installed Vlingo and the problem arose. I then unistalled Vlingo and the problem still persisted. Days later I then switched kernels in an attempt to fix the problem. I have the same problem regardless of which kernel I use.
Do you have a suggestion for a solution? Again, thank you.
Click to expand...
Click to collapse
i have the same problem did everything mentioned above, rooted my wife evo and mine my Bluetooth doesn't work on mine hers does, maybe the devs could make a backup flashable zip for Bluetooth and htc syn that would be great
Using rooted file manager, I can get to the bluetooth.apk and BrcmBluetoothServices.apk files. When I click on either one of them I get a message that asks:
"Replace Application
This is a system application. Do you still want to replace it?
All previous user data will be saved."
Question, If I say "OK" what does it replace with? Maybe replacing these two files will change things for me so I can get my BLuetooth function back again.
Any comments?
Nothing I have done has gotten my bluetooth function back again. I'm desperate. Anyone have any ideas. What is frustrating is that my wife's Evo will work just fine in my car, but mine has not ever since I tried Vlingo.
There must be a way to reinstall bluetooth without having to do a factory reset and start all over again. (And I'm not sure that would do it anyway.)
Anyone with suggestions?
Update: I just flashed the updated stock ROM (New_RUU_Supersonic_3.30.651.3_Deodexed_signed - http://www.4shared.com/file/yLaxLUnJ...RUU_Super.html) from http://forum.xda-developers.com/showthread.php?t=836728.
"So Far - So Good" as my bluetooth suddenly worked again. I have flashed the previous stock 3.30.651.2 ROM and nothing changed. This also comes with a updates stock kernel. So who knows, may be this update fixed the problem. I'm keeping my fingers crossed.
BTW, I forgot to wipe anything when I did this update. All good so far.
Later: It works better but not consistent. I still have problems where after a phone call I have to turn the bluetooth off, then on again to make or receive additional phone calls.
I think i fixed my bluetooth !!!!!!
I THINK I FIXED IT !!!!!!
Wow after over 2 months of searching, learning, and trying everything I could think of (other than unrooting and going stock) I stumbled upon what seems to be a solution.
Here is what I did:
Using ASTRO file manager I opened up the "system" folder then opened the "app" folder. From there I scrolled down to the "BrcmBluetoothServices" file and long clicked it until the "File Options" appeared. Then I selected "Edit" and on the next pop-up I selected "Delete". (I was desperate and was going to delete it and reinstall from scratch).
When I selected Delete, a confirmation box appeared that said something that caught my eye like, "Are you sure you want to delete the update as this will return the file to stock?" (or something like that). WOW, when I heard delete the update I figured that Vlingo may have updated this file causing the problems. So I said yes. The update was deleted.
The BrcmBluetoothServices file remained but evidently it reverted to its original stock format. I noticed that my Evo no longer showed a pairing with my car. So I went to my car and deleted that pairing as well and then re-paired my car and phone.
Success! I have been using it for a day and so far so good. My Evo instantly connects with my car when I turn the car on, and I can make and receive phone calls normally. It has only been one day, but it looks good so far!!!
This did fix the problem. Working now for 2 weeks.
Related
Hello. I have a problem with sound in my kaiser with Android. I tried 2 systems [Cynanogen mod 6 (Froyo) and Myn's Warm Donut], 4 radios (from 1.71 to 1.65) and 2 kernels. Sound never appeared. Why?
what zimage or nbh you using if you are using a older one it might have problems
Did you mean kernel? the newest from this page:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
it may be that you have muted the media volume in settings.
No. I don't have any sound. Not only media. When someone calls to me, I cannot hear him too and this person cant hear me too.
Audio issue
I have the same problem. I tried different builds and nothing helps. Any suggestions??
Just a thought, but have you tried flashing a stock rom, then flashing to nand again? Flashing a stock rom clears the entire nand, leaving no possibility of stray bits of data left from custom roms.
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
<refresh>.
Mu_aawiyah said:
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
Click to expand...
Click to collapse
Yeah, flashed it back to a the most recent stock rom, and then back to andriod.. how works perfectly. Sorry i didnt tell you guys earlier.
I think it was to do with the radio thingy-ma-jig. I flashed it with winmo 6.1 from htc website, and then back again.
Now i'm runnying frayo.
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Wagierek said:
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Click to expand...
Click to collapse
That is most likely because you didnt flash it right. take the .nhb from it, plug it into your sd card and flash it from sd. try that.
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Wagierek said:
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Click to expand...
Click to collapse
Well, with regards to how I got it fixed (the detailed explanation), i flashed it with a custom winmob rom initially, but surprisingly, the same problem i had with android was happening with the winmob. I could make a call after reboot, but after that call, the sound completely died, and the camera did not work. So i tried to flash with the latest stock rom. I've uploaded the actual roms i used on my public drop box folder here => "i tried posting the link, but because i'm new, it wouldnt allow me...pm me"
I am not a professional on flashing, rather i am a beginner. My tytn 2 is a european T-mobile version. I tried to flash it, it did it half way...then stopped! I tried to do it again, but then it just said "...loading..." and would not go past it. But when i booted to my custom rom, it was still there, but the problems had gone. I guessed that it flashed the radio, and nothing else.
When i then went to android, it worked perfectly.
That was my journey.
I hope that helped... maybe.
Unfortunately, it didn't help.
Any other ideas?
I solved mine by changing radio ROM,but i lost sound and camera in windows,any ROM that fit both android and windows???
What version did you flash?
1.65.14.06
Me too!
I flahsed froyo last night and didn't test after makng calls. I'm having the same issue (lose sound after a phone call). I followed the sticky guide and sim unlocked the radio before flashing (which I think I had already done before). I will try changing radios when I get home to see if this resolves the issue and post my results.
Update: I flashed 1.71.09.01 on my ATT Tilt and this fixed the issue. Now sound and camera work great. Phone runs faster also!
Hey everyone,
So I have been having problems connecting my evo to my bluetooth fm transmitter for my car (I can't post links yet, but it is on amazon, the gogroove flexsmart x2) ever since I switched from cm6.1.2 to miui 12.31. The transmitter was working perfectly, and my phone would pair and connect to it flawlessly, however, when I switched to miui, it didn't work at all. It would just not connect, no matter what I did. So I tried switching kernels around, and none of them worked (I tried about 3 kernels on cyanogen before I switched to miui, and switching didn't cause any issues). So I decided to go back to cyanogen, yet my bluetooth didn't work when I restored to a nandroid backup. Bluetooth still wasn't working. So then I went into clockwork and wiped my data/cache and installed the latest cm6 and bluetooth worked. Excited, I installed all of my applications, got my settings right, and installed a different kernel. When I switched kernels to try out a savage one, my bluetooth wouldn't connect. Nothing would work to bring that back, so I deleted my data/cache again and got it to work. Everything worked fine, but I wanted a different kernel, so I tried putting on snap 7.6, and it won't work anymore. I am not entirely sure what to do. I can re-install cm6 by clearing my data/cache, but I want to know why I can't use any other kernels that worked previously. Any suggestions?
Recently, I posted on cyanogen forums, and someone said to use Calkulin's format all zip as well as clear davlik cache. That didn't wok. I also tried going onto a sense rom and installing a sense kernel which didn't work either. I'm not entirely sure what to do. The thing that bothers me the most, not that I can't be on a different kernel than the stock cm6 one, it is that I don't have the option to change, but I did before.
Thanks so much for any help!
Almost sounds like it may be a hardware problem. Most of the software fixes I would suggest you've already tried with no luck. Keep in mind hardware can fail.
spiicytuna said:
Almost sounds like it may be a hardware problem. Most of the software fixes I would suggest you've already tried with no luck. Keep in mind hardware can fail.
Click to expand...
Click to collapse
I would think that it is a hardware problem, but I am lead to believe it is something dealing with the kernel because when I am on a stock cm6 kernel, it works, but when I change the kernel, it fails.
EDIT: Also, would you recommend maybe unrooting my phone and completely resetting it?
This is a question regarding Twa_Priv's 4.1.2 10/13 updated ROM.
1,) Does a TRRS headset (headphones with mic) work now? I know that lots of devs were working on getting the mic to work with jellybean, I just don't know if it has gotten around to working on the newly updated ROM
3.) I have had trouble with Amazon appstore not recognizing my KF as a kindle since the last ROM where I clean installed from scratch, so it won't let me install kindle-specific apps. Has anyone had this problem, and does anyone know a way to get around this?
4.) One more issue. I think that this is just a personal problem somehow. I have been having trouble restoring backups. I use Twrp 2.2.2.1 and it seems to create backups fine, it just wont restore them. I haven't tested out if it works with the last 3 builds, because then I have to start from scratch again if it doesn't work, and that takes a lot of time... I had twrp originally then switched to CWM because I thought I had to for an app, then discovered that I REALLY like TWRP better, so reflashed it, and it hasn't worked since then. Any pointers?
thanks
So I just rooted my Samsung sgh t-989 the tmobile one. I put TWRP 2.5 and have Cygenmod 10.1 running. I was all excited because I have notdone this kind of stuff since middle school.
But The problem is my Bluetooth is "disabled" When i try to turn it on it just goes right off, I have no idea where to start to fix this problem. I already tried google and searching the forums but no solutions.
Which date of cm10.1 did you flash? You need to give more details. Flash a custom kernel? What's your radio you're using?
Denta87 said:
So I just rooted my Samsung sgh t-989 the tmobile one. I put TWRP 2.5 and have Cygenmod 10.1 running. I was all excited because I have notdone this kind of stuff since middle school.
But The problem is my Bluetooth is "disabled" When i try to turn it on it just goes right off, I have no idea where to start to fix this problem. I already tried google and searching the forums but no solutions.
Click to expand...
Click to collapse
I've had exactly the same problem, using the CM 10.1 RC5a.
Bluetooth will do as you described - be disabled, when clicked on, will jump to off again.
Restarting always fixes it momentarily.
If BT is on, and successfully connects to my car, and I'm able to place a call, first no one can hear me, the call is dropped, and BT shuts off to remain permanently disabled til I reboot the system.
After a reboot, its usually ok for a couple hours.
Lots of other users are having the same problem....
Denta87 said:
So I just rooted my Samsung sgh t-989 the tmobile one. I put TWRP 2.5 and have Cygenmod 10.1 running. I was all excited because I have notdone this kind of stuff since middle school.
But The problem is my Bluetooth is "disabled" When i try to turn it on it just goes right off, I have no idea where to start to fix this problem. I already tried google and searching the forums but no solutions.
Click to expand...
Click to collapse
Also, flashing this fix now, will report back:
http://forum.xda-developers.com/showthread.php?t=2174100
I wiped dalvik/cache, flashed the BT fix, fix permissions, then rebooted.
Just CM 10.1 RC5a, UVMC6 radio, I upgraded firmware using the UVMC6.aio.tar.md5 file made by Mikeyman
Hope it works - really tired of having to reboot every time i want to make a call over BT car audio...
HISTORY oforoub
aaronchili said:
Also, flashing this fix now, will report back:
http://forum.xda-developers.com/showthread.php?t=2174100
I wiped dalvik/cache, flashed the BT fix, fix permissions, then rebooted.
Just CM 10.1 RC5a, UVMC6 radio, I upgraded firmware using the UVMC6.aio.tar.md5 file made by Mikeyman
Hope it works - really tired of having to reboot every time i want to make a call over BT car audio...
Click to expand...
Click to collapse
36 hours on this and no BT crashes!
Faster connection to car audio, and call stability is much better.
Also remember after reboot to delete all devices, and re-add them.
I have searched all over and couldn't find any answers, so hopefully this isn't a repeat thread.
I just purchased the HTC desire 816 and upgraded to it. I activated it, and set everything up, Saturday. Sunday after trying to load xposed onto it, it froze on the boot screen.
I managed to restore it from fastboot, and got it updated to lollipop.
Now for the problem, and what I have tried:
The phone will not see bluetooth devices at all.
First I tried simply a factory reset, which allowed it to see my smart watch and start to connect to it. Part way through the setup of my watch, it lost it's connection.
Next I tried a wipe and restore to full stock, this did not allow me to see any bluetooth devices.
Then I tried rooting, cwm, and putting kitkat back on the phone. I still couldn't see bluetooth, and now I am trying to upgrade back to lollipop.
I am at a loss as to what may be the problem, but I need it to work with bluetooth.
I have tested it with both my LG G smartwatch, and a gemline bluetooth speaker.
OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.
tenchu98 said:
OK, so a little update here. I did a full stock & root flash last night.
The wifi began working, and Bluetooth was connected to my smartwatch.
This morning, wifi is still working and bluetooth can't see any devices.
On a side note, I am trying to figure out what version of xposed to install on my phone.
Click to expand...
Click to collapse
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811
thoctor said:
If you're on 5.0 lollipop then 21. If you're on CM 12.1 (5.1) then 22. I have this same device and carrier and haven't had any issues like you're describing other than a few Bluetooth dropouts every once in a while. Good luck.
http://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.
tenchu98 said:
I went back to full stock, and relocked the bootloader, because HTC said that it was an issue with the bootloader being unlocked. I doubted them, and it turns out I was right to doubt. The issue isn't fixed, and I seem to have narrowed it down to the searching function. My HTC can't see any discoverable items.
I have a gemline speaker, which has NFC to pair Bluetooth built-in, and my phone is unable to see it when I try to use NFC enabled pairing.
Click to expand...
Click to collapse
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
I am suspicious that somewhere along the lines the bluetooth files became corrupted in system. I have been trying to find a way to put the original ones back on, but haven't been able to find a way. I really want to get this working, and remove root.
Why do I not want root, because my kids enjoy pokemon go and it won't run on root anymore.
Click to expand...
Click to collapse
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.
thoctor said:
Yeah, that's a load of crap so you were right to question that. My bootloader stays unlocked and I don't have any Bluetooth issues other than the ones noted for running CM custom roms and the headset dropouts. I have 3 different Bluetooth devices linked to my phone and no issues pairing any others either.
You could find and flash back your stock recovery and then find either the stock RUU file or the stock Rom.zip file and flash back to stock. I understand about root. It's getting to the point my next device will probably stay stock but I'm having my fun now.
Click to expand...
Click to collapse
I did this once already, I am thinking that my next step will be to manually copy the bluetooth related files from the system image into system using root
then flash unsupersu.zip
So I hav replace every bluetooth related file I can think of, and even deleted some file suggested online, and my phone still doesn't see other devices. When I put my phone on my NFc enabled speaker it acts like it is going to pair, but then says "unable to pair gemline speaker".
I am beginning to become frustrated.