Bluetooth issues - One (M8) Q&A, Help & Troubleshooting

Hi,
i'm hoping someone could help me with an issue that has happening since i flashed a ROM onto my one M8.
Before i flashed a rom, the bluetooth audio connection worked perfectly with the radio in my Skoda (a Kenwood DNX525 DAB), ever since I flashed a rom, i have had problems with the audio cutting out, or stuttering every 30 seconds or so. If i unpair and delete the connection from both devices, then re-pair the devices, it might work without problems for one journey, then after restarting the car the stuttering is back.
The first rom i flashed was Mikes Android revolution HD 45, then flashed 53.1, and i am now running LeeDroid V8.2.1 and all have had the same problems.
As far as i can tell i am doing all the clean caches, and formatting i need to, but i would really like to get this working without having to resort to going back to a stock ROM.
If anyone has any ideas how to fix this, or trouble shooting i could try myself, please let me know.
Thanks in advance for any help.

Try seeing if your head unit has some setting option (might be pretty buried in a sub-menu) to "re-initialize" the system. This will wipe any settings you've made (to factory defaults, I believe).
Hopefully, this will help your BT connection issue. I had a similar issue on my Subaru head unit (which I understand Kenwood supplies - at least for my 2012 model) where the phone would not properly auto-reconnect, after flashing a ROM. Unpairing, and re-pairing didn't help. But re-initializing fixed it right up. If so, you may have to do this with every new ROM flash. Although, backing up Bluetooth Pairings with Titanium Backup, and restoring after a ROM flash, also seems to work okay for me.
If you were on a Sense ROM originally (when BT connection was working well) I wouldn't think there would be much (if any) difference in Bluetooth stacks. So I'm guessing and hoping that re-initializing the head unit, and re-pairing will solve the issue.

Related

[Q] Please help!!! MIC is breaked after Update...

Hi ll,
I really out of ideas here .
I was running Pays 1.9 Bravesoul ROM without any issues for about 4 months on my unbranded Desire(HBOOT 0.75)!
Today I decided to update to Froyo.
I used Rom Manager to upgrade to OpenDesire 3.03 and Radio 32.43.00.32U_5.09.00.20.
Every thing went well, except that I noticed that the MIC doesn't work at all.
Not when I make or receive a call, Not if I try to Mute/Unmute it, Not if i try to Record sound, or Video or WHATEVER!!! The only way the other side can hear me is trough my BT headset.
So I tried to use the LeeDroid 1.7a ROM but same result. Also tried to use different Radio - 32.42.00.32U_5.09.00.08.
I then Nandroid restore to my 1.9 Pays rom (Wiping Data+Cach+ext), but still doesn't work. I tried different Radios:
32.37.00.32U_4.06.00.16_2
32.36.00.28U_4.06.00.02_2
32.26.00.24U_4.04.00.03_2
same thing...
I finally Unrooed my Desire to v1.15.4 Radio 32.30.00.28U_4.05.00.11 without any luck!
So I'm pretty hopeless Please if someone also have / had this issue, Please share!
Thanks!
sounds to me like it's broken mate
i know it's coincidence that it broke as you changed ROM but if it doesn't work on anything there's no explanation
have you tried a hard reset + clearing caches?
if you have then unroot your phone, put it back to your original RUU for warranty purposes and sent it back for repair
by what do you mean Hard Reset?
I wiped all data, I've changed roms.
Currently It's unrooted...
Is it possible for the Radio update to do this? (all the updates went without a hitch)
Or maybe the OpenDesire ROM (I see that v3.03 is removed, do you know why?) did this?
There is no way it a coincidence. I making phone calls all the time, The update took me about 15 min, after which I tried the Video camera and noticed there was no sound...
Thanks!
well, I noticed that the mic works, but extremely week! I really need to shout in order to hear a whisper... I do this in recording...
I'm starting to believe that maybe it's the mimbrein (Or the piezzo) that is ruined inside the mic...
Is it possible to control the gain in software? (Is there still a chance that the S.W upgrade caused this?)

[Q] Radio Update Killed Handset Speaker Audio

After installing Radio 2.05.00.06.11 (dinc_ota.zip), my handset speaker audio disappears. Speakerphone and bluetooth work fine, but no luck with the internal speaker.
Heres the kicker:
Once I restore the 1.0 Radio, the internal speaker starts working again.
After lots of searching, this seems to be a very intermittent problem. I've only found two other people experiencing the same issue. Unfortunately I have not found a solution.
Does anybody have any idea as to what my next step should be to try and solve this?
Thanks!
I have the same problem...
heega1 said:
After installing Radio 2.05.00.06.11 (dinc_ota.zip), my handset speaker audio disappears. Speakerphone and bluetooth work fine, but no luck with the internal speaker.
Heres the kicker:
Once I restore the 1.0 Radio, the internal speaker starts working again.
After lots of searching, this seems to be a very intermittent problem. I've only found two other people experiencing the same issue. Unfortunately I have not found a solution.
Does anybody have any idea as to what my next step should be to try and solve this?
Thanks!
Click to expand...
Click to collapse
Try downloading a fresh copy of the update and running it again?
It's working just fine for too many people for it to be a problem with the update itself.
douger1957 said:
Try downloading a fresh copy of the update and running it again?
It's working just fine for too many people for it to be a problem with the update itself.
Click to expand...
Click to collapse
updating the radio twice will brick the phone! same one that is.
zeke1988 said:
updating the radio twice will brick the phone! same one that is.
Click to expand...
Click to collapse
not exactly. but, this radio isnt a image, its a patch. and a double patch is not the same thing... there is no error checking. dont do it!
I've tried re-installing the update 3 times from three sources. At first I thought it was the Froyo update so I went back to my nand backup and that didn't help, but once I downgraded the baseband it magically started working again.
So I tried it again. Re-downloading all the tools and packages. Only for it to happen again right after the Radio update. So I reverted back, cleared everything to factory, did a fresh install, then did the upgrade once more.... Still same problem.
Since it is such an intermittent issue, I'm thinking that maybe the hardware is to blame. The particular handset that I have is a warranty replacement from Verizon (blown speakers on first one). Maybe that has something to do with it.
Anyone have any other theories?
Thanks!
So I'm stumped. It's a pretty straightforward process, and I can't see where I'm going wrong.
Next Step: Warranty Replacement. We'll see if that helps. I'll be sure to record the serial number and other details of the phone before I send it back. Maybe we can find a pattern.
It will be a couple days before the new phone arrives. If you have something I can try, please suggest away!
Thanks!
I am having the exact same problem. I have tried both 2.x radios and both have the same effect. I want to use froyo but the only way to is to use speakerphone or a plugged in headset. I tried to take it in yesterday but the tech at verizonwireless told me to wait it out until 2.2 comes out to see if that fixes my problems. ( went in stock told them I was having the problem on stock radio) final problem being is when official does come out and it kills my headset speaker is it going to be too late to root my phone knowing the replacement I get will already be loaded with the new software.
Chicken and Egg
Unfortunately, unrEVOked has not developed a S-ON patch. This means that you will either have to take stock 2.2 which will be unrootable -or- you will patch forever, have S-OFF, get stock 2.2 and not be able to return the phone if the problem doesn't clear up.
Please keep that in mind when making your decision.
The replacement phone worked...
Not sure what the problem was, but it confirms my method for installing 2.2 wasn't flawed..
Thanks for all your help!
-j
I am trying to get verizon to send me a new one. They are not being very helpful right now. They said the audio issue is a software issue that should be fixed with the new update but might send me a new phone due to number of dropped calls. I have to stop in store tomorrow

Bluetooth problem - need help

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.

[Q] Bluetooth connectivity

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?

Bluetooth problem

Hi, I've an annoying problem with the Bluetooth: when it's turned on, it turns off randomly and after few seconds it turns on.
It's impossibile to keep connection with other devices.
I've the last firmware version.
Please help me!
Try a factory reset to see if it is a problem with the software or an app.
If it still keeps dropping it might be a broken Bluetooth module which has to be repaired...
I have root and recovery. Can I reflash the firmware I have with root and dualrecovery included? If yes, what I lost?
Thanks
I have a similar problem with various CM12 and CM12.1 builds ... Bluetooth just can't be turned on, after turning it on, it turns itself off after a few seconds.
Originally I thought, it maybe a hardware defect, but when going back to a previous version of CM (restoring a nandroid backup), Bluetooth worked flawlessly. As I didn't want to stay with a build from November, I kept updating the ROM, but Bluetooth stayed offline.
Until today when I made the suggested factory reset. Now Bluetooth works without problems, even after reinstalling all the apps I had installed before. So thanks for your advice, Schlengge

Categories

Resources