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.
Related
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.
Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.
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.
Hi guys,
My f400l has been experiencing issues for a while now. One morning, I woke up to find an unresponsive device. Took out battery and turned it on again to find that the device had partially reset itself (ie. going back to stock launcher and layout, missing apps). Device was still rooted so I tried to restore apps and settings via titanium backup. However, phone kept freezing throughout restore process.
Next, I decided to flash back to stock. This is when i noticed that wifi would remain at 'wifi turning on' but never actually turn on. Additionally, bluetooth could not be turned on. I then upgraded to lollipop via normal firmware update from lg software on my pc. Phone then would freeze after every 2 mins.
After trialing many rooms, I am now on cloudyg3 2.1 but wifi/bluetooth are still not working and phone still freezes occasionally (usually at the beginning of the day).
Really at a loss here, can anyone suggest what seems to be happening and what I can do about it?
Thanks everyone!
smarikoe said:
Hi guys,
My f400l has been experiencing issues for a while now. One morning, I woke up to find an unresponsive device. Took out battery and turned it on again to find that the device had partially reset itself (ie. going back to stock launcher and layout, missing apps). Device was still rooted so I tried to restore apps and settings via titanium backup. However, phone kept freezing throughout restore process.
Next, I decided to flash back to stock. This is when i noticed that wifi would remain at 'wifi turning on' but never actually turn on. Additionally, bluetooth could not be turned on. I then upgraded to lollipop via normal firmware update from lg software on my pc. Phone then would freeze after every 2 mins.
After trialing many rooms, I am now on cloudyg3 2.1 but wifi/bluetooth are still not working and phone still freezes occasionally (usually at the beginning of the day).
Really at a loss here, can anyone suggest what seems to be happening and what I can do about it?
Thanks everyone!
Click to expand...
Click to collapse
reflash the modem and kernel and you should be set
suljo94 said:
reflash the modem and kernel and you should be set
Click to expand...
Click to collapse
sounds simple enough.
Would these be the right links?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-rin-kernel-1-0-t2847581
http://forum.xda-developers.com/showthread.php?t=2784501
If flashing the modem, wouldn't I need to first revert back to stock kitkat?
smarikoe said:
sounds simple enough.
Would these be the right links?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-rin-kernel-1-0-t2847581
http://forum.xda-developers.com/showthread.php?t=2784501
If flashing the modem, wouldn't I need to first revert back to stock kitkat?
Click to expand...
Click to collapse
flash the correct one
https://www.androidfilehost.com/?w=files&flid=22640
suljo94 said:
flash the correct one
Click to expand...
Click to collapse
Argh! So i tried flashing and upon reboot, phone came up with a security error. Currently reverting back to stock via download mode. I couldn't get back into recovery. Did I do something wrong? Thanks for the help so far tho!
EDIT: ahhh just realized i flashed a kitkat kernel, woops! Will see how things pan out for now
So i went back to stock and flashed a kernel but that didn't seem to help. Can't seem to find a zip file for kitkat baseband so I'm a bit lost as to how to flash a modem.
One thing I also noticed is that fact that i cannot access recovery via hardware buttons? I use power and volume down but the combo doesn't work. It just boots normally?
So I can't connect my phone to the car bluetooth connection in my car. It's ONLY a custom ROM problem. If I use FreedomOS or stock it works fine. I have changed to literally every firmware in existence, still no fix. I can connect to some devices, but I also have problems with Android Wear.
This is a big deal as I bought this phone for a custom ROM. Anybody know what's the fix?
I have read more threads about this, but nobody ever seems to have an answer that isn't "flash xyz firmware ZIP in TWRP" which I've already tried. Please, anybody willing to help, please do!
So you can't pair your phone i assume?. If so I had the same problem.
It was a real issue in earlier aosp roms but now alls I do is clean flash the rom, set up and connect my BT and then if using a theme it goes on last!!!!.
No, it pairs fine, but then never connects as a phone. Only media works. I never dirty flash roms, so that's not the issue at all.
I will try this, then report back. Haven't tried this yet.
Which option in the toolkit should I use? There seems to be no options to revert stock specifically. You mean the OP3 Unified Toolkit, or is there specifically a "unbrick tool"?
Tried it. Not fixed. Used 4.1.3 zip after the reflash of stock using the Qualcomm tool. Should I try a 6.0.1 zip like 3.2.8 OOS or something?
I have built several custom ROMs with a BT fix that gets rid of the "no phone" issue. This sounds like the same issue I had so this should work.