Since the stagefright patch, I've been unable to connect with all of my BT devices automatically when leaving the BT radio on. This includes my car and my Android wear devices. I always have to cycle the BT radio on and off now. Anyone else have this issue and a potential fix? Tia.
Bump. Also finding that the BT just disconnects after being on for a while. Almost like it went to sleep. Also, trying to connect manually by selecting the device doesn't work as it just gives me a unable to connect message.
I'm at wits end and can only think of trying to hard reset at this point. Any ideas would be appreciated.
neoshi said:
Bump. Also finding that the BT just disconnects after being on for a while. Almost like it went to sleep. Also, trying to connect manually by selecting the device doesn't work as it just gives me a unable to connect message.
I'm at wits end and can only think of trying to hard reset at this point. Any ideas would be appreciated.
Click to expand...
Click to collapse
did you flash the full stagefirght patch?
if so you can simply flash the patch from VZW that has the 1 vulnerability left..
Flash the attachment.zip in recovery.
andybones said:
did you flash the full stagefirght patch?
if so you can simply flash the patch from VZW that has the 1 vulnerability left..
Flash the attachment.zip in recovery.
Click to expand...
Click to collapse
No unfortunately I'm all OTA bone stock on this one.
Wipe cache didnt work. Just going to try a hard reset next.
neoshi said:
No unfortunately I'm all OTA bone stock on this one.
Wipe cache didnt work. Just going to try a hard reset next.
Click to expand...
Click to collapse
If that doesn't work and it is the Stagefright Patch... the latest OTA was 4.17.605.9 (which patched Stagefright - as you already know) coming from 4.17.605.5, if it worked on 4.17.605.5 here is the stagefright.so library from that base... Should fix it for you.
I am uploading 3 files:
1 - with just the stagefright.so library
2 - with all the stagefright libraries - all may be needed and not just the one
3 - bringing you back to where you are now.
Test 1
Test 2
Back2Stock
Flash via Recovery
Thanks. A hard reset fixed it.
Kind of annoying that the last two OTAs I've had to hard reset to get the phone working normally.
neoshi said:
Since the stagefright patch, I've been unable to connect with all of my BT devices automatically when leaving the BT radio on. This includes my car and my Android wear devices. I always have to cycle the BT radio on and off now. Anyone else have this issue and a potential fix? Tia.
Click to expand...
Click to collapse
I did the full RUU , and had no issues, then I flashed the incremental firmware updates, and after that it was all wonky where I am not able to connect in my car unless i power cycle the BT.. I am going to try a few of the fixes Andy has, then going to RUU the latest firmware and see what happens.
Hopefully it works. Full wipe and redoing everything is always annoying!
I poked Mo on twitter about this but he didn't respond. I figure VZW messed something up along the way.
neoshi said:
Hopefully it works. Full wipe and redoing everything is always annoying!
I poked Mo on twitter about this but he didn't respond. I figure VZW messed something up along the way.
Click to expand...
Click to collapse
Actually it did not work I flashed the back2stock then I RUU the firmware here: https://www.androidfilehost.com/?fid=24052804347811415
Did not resolve. I was thinking of running dotdat's RUU, but found a TWRP from when it worked fine and just wiped and used that. I deleted the BT profile for my car, re-paired and then turned the car off, rebooted the device with BT on and after I started my car, the BT connected like a champ!
I would really like to know wtf caused that issue, it was so annoying. I as always appreciate anyone's input and feedback, suggestions, etc on such matters. I will go hit the thanks button even if it did not work as you all take the time to assist and try to understand things.
I will report back if it fails or not
Best Regards
carm01 said:
I did the full RUU , and had no issues, then I flashed the incremental firmware updates, and after that it was all wonky where I am not able to connect in my car unless i power cycle the BT.. I am going to try a few of the fixes Andy has, then going to RUU the latest firmware and see what happens.
Click to expand...
Click to collapse
This did not resolve this issue. this reared its ugly head again after once again doing the full all in one firmware upgrade again
Is anyone else having this issue still?
Mine is doing this again too after a full wipe. Not sure what to do at this point.
Related
Just flashed lollipop and everything works perfect except for Bluetooth. Phone simply says there are no other Bluetooth devices in range, and those devices can't see the nexus. I tried rebooting, factory reset, re-flashing stock lollipop using flash-all batch and even Wug toolkit just to cover all my options but still no work around. Anyone else experience this problem or can think of a way to fix it? Anything would help.
Wipe Cache
TheRoice said:
Just flashed lollipop and everything works perfect except for Bluetooth. Phone simply says there are no other Bluetooth devices in range, and those devices can't see the nexus. I tried rebooting, factory reset, re-flashing stock lollipop using flash-all batch and even Wug toolkit just to cover all my options but still no work around. Anyone else experience this problem or can think of a way to fix it? Anything would help.
Click to expand...
Click to collapse
Hi, one of my friend faced similar issue and wiping the cache from recovery helped solve the issue.
Try wiping cache and reboot.
pppp6071 said:
Hi, one of my friend faced similar issue and wiping the cache from recovery helped solve the issue.
Try wiping cache and reboot.
Click to expand...
Click to collapse
Just tried the wipe and reboot but the issue is still persistent. I'm still looking around for a solution but nothing has come up yet. Thanks for the input though!
lollipop im nexus5 bluetooth unstable
I just downloaded the lollipop today on my NX5 and i have a bluetooth SENA smh10 for my helmet and it was working very fine before the update, now its unstable, iv to start the music app first on phone while connecting the bluetooth inorder to be able to control it via the bluetooth device, also for calls, i recieved a call and i opened but no sound was there, i tried to call, same happened, so i had to disconnect the device, make the call and then i connected again..after a while it worked and i made a call... Theres some bug in the bluetooth i guess as my smh was working fine before. Also iv a problem in some wedges not responding like the data on off one. Oh yes..and battery empties SO Fast
TheRoice said:
Just tried the wipe and reboot but the issue is still persistent. I'm still looking around for a solution but nothing has come up yet. Thanks for the input though!
Click to expand...
Click to collapse
So I solved the issue. Re-flashed 5.0 to the device, rebooted, and wiped cache. It still didn't pick up bluetooth as of last night but it worked this morning. Also, for any android wear users (or at least moto 360) the phone wouldn't pick up the watch until I did factory reset on the watch and opened android wear on the phone itself in order to accept terms and conditions.
@TheRoice
thanks, has worked for me :good:
I apologize if this issue has already been addressed but Im beyond frustrated.
Since my OTA update to 5.1, my phone is completely crippled. It randomly powers off about 10 times a day (not a auto restart) and I have to power back up. It will also auto restart another 5 to 7 times a day, when it does this it will get stuck in a loop of trying to boot into the OS and restarting all over again. So it will display "Google" for about 2 seconds and then restart again. This is only stopped by holding down the power button. The best part about this happening is that the phone then thinks its the first time I have powered on since the 5.1 update and will initialize all of my apps, which takes about 5 to 10 min. I have had 5.1 for about a week or so and its been getting worse every day. More power off's and restarts each day.
I should note that I am with T-Mobile and my phone is not rooted. Bone stock
My phone is borderline unusable since the update. Please god somebody help me.........
Flash 5.1 factory images
beekay201 said:
Flash 5.1 factory images
Click to expand...
Click to collapse
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?
dafababa said:
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?
Click to expand...
Click to collapse
Basically something wierd went with the update, maybe a file got corrupt, some risidual 5.0 code is there. Who knows.
The best way out is probably to flash 5.1 again like said above although not really explained. This will ensure the entire phone is 5.1 and there isn't some 5.0 risidual code somewhere which is likely causing the problem.
It will flash your entire phone with stock 5.1, no root, custom recovery or kernel or anything, 100% stock. You will lose your data though, so if you can, back it up!
Download the 5.1 stock image here: https://developers.google.com/android/nexus/images#hammerhead
it will say 5.1 next to it, it'll be pretty clear.
Extract the contents after the download and run the flash-all script.
matt4321 said:
Basically something wierd went with the update, maybe a file got corrupt, some risidual 5.0 code is there. Who knows.
The best way out is probably to flash 5.1 again like said above although not really explained. This will ensure the entire phone is 5.1 and there isn't some 5.0 risidual code somewhere which is likely causing the problem.
It will flash your entire phone with stock 5.1, no root, custom recovery or kernel or anything, 100% stock. You will lose your data though, so if you can, back it up!
it will say 5.1 next to it, it'll be pretty clear.
Extract the contents after the download and run the flash-all script.
Click to expand...
Click to collapse
Before I do any of this I want to note that it appears there are many other people who are having the exact same issues as me. Is it possible that the update is just buggy??
dafababa said:
Before I do any of this I want to note that it appears there are many other people who are having the exact same issues as me. Is it possible that the update is just buggy??
Click to expand...
Click to collapse
there are people that are reporting a few issues, mainly the memory leak issue still being present. There are none or very little talking about 7 - 10 random power offs a day. This is very unusual and likely to be a specific issue to you not mainstream.
matt4321 said:
there are people that are reporting a few issues, mainly the memory leak issue still being present. There are none or very little talking about 7 - 10 random power offs a day. This is very unusual and likely to be a specific issue to you not mainstream.
Click to expand...
Click to collapse
Well I just finished flashing 5.1 build LMY47i and i can confirm the problem still exists for me. Im just gonna go back to 5.0.1
dafababa said:
Well I just finished flashing 5.1 build LMY47i and i can confirm the problem still exists for me. Im just gonna go back to 5.0.1
Click to expand...
Click to collapse
I htink you may have a loose power button or a loose contact. i had the same problem. Try to press it in really hard and it should fix the issue.
dafababa said:
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?
Click to expand...
Click to collapse
OTA update ain't the same as a factory image.
beekay201 said:
OTA update ain't the same as a factory image.
Click to expand...
Click to collapse
I've flashed back to 5.0.1 and still have the problems. I'm going to assume its a power button issue.
chaose said:
I htink you may have a loose power button or a loose contact. i had the same problem. Try to press it in really hard and it should fix the issue.
Click to expand...
Click to collapse
So like how hard?
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
So anyone else having random restart issues no matter what firmware you are running?
I am having this issue even after updating the firmware (yes I managed to get it updated lol didn't realize need to do it in increments rather straight to the latest).
I found a work around sort of but it requires having my hotspot on and another device connected at all times to keep the phone from restarting randomly.
Has anyone else ran into this issue and have a fix? Could it be a battery optimization setting?
Thanks
i got it when i update the rog 5 to latest version so i factory reset it then worked well
messhary said:
i got it when i update the rog 5 to latest version so i factory reset it then worked well
Click to expand...
Click to collapse
Ok thank you for replying, I just finished backing up with Migrate and going to do a factory wipe and then restore all my apps. Hopefully that solves my issues.
I have the same problem for last two firmware updates, for each update I need to do a full factory reset in order to let it work again!
Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys
Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs
creezalird said:
Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs
Click to expand...
Click to collapse
Restarted and also factory reseted
YassGo said:
Restarted and also factory reseted
Click to expand...
Click to collapse
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...
simplepinoi177 said:
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...
Click to expand...
Click to collapse
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success
YassGo said:
Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys
Click to expand...
Click to collapse
YassGo said:
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success
Click to expand...
Click to collapse
Mmmm...when you stated you "factory reset", it wasn't clear whether it was from the OS system setting or when flashing...
I don't think there is a "better clean" way to flash and/or reset the phone. If you're not flashing/sideloading OTA (which you aren't)...
It (reset network) was a very long shot, but worth exploring just in case it hadn't been tried yet...
I mean, I guess you can try Android Flash Tool and even go as far as to flash to both slots and relock bootloader to get a pure, stock status and see if the problem truly sticks that way. You've already wiped the phone, so I doubt this could hurt or you lose anything important at this point. But I can't imagine dirty flashing the latest March update (or even including disabling the verity stuff) wouldnt've addressed or reset things to set the issue straight...
If it's still there after relocking the bootloader and flashing to both slots, then it's warranty exchange time (if you ever want to resolve the issue)...
*most likely the flashing somehow wrecked the system board radio enough...
If/When this works, you'll need go through the trouble of unlocking the bootloader, and reflashing the Full Factory image with disabling the verity & validation stuff, before rooting again.
Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....
YassGo said:
Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....
Click to expand...
Click to collapse
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.
jaseman said:
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.
Click to expand...
Click to collapse
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?
YassGo said:
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?
Click to expand...
Click to collapse
I have had several OnePlus phones and they have all been great for me! However, I am having no problems with my 7 Pro either so....YMMV