Hi everyone so recently my bluetooth has been really unstable. It is extremely frustrating as it will stutter, stop, unpair, turn off and on and right now it won't let me turn it back on. This is preventing smooth music playback. I have done literally everything, clearing cache to factory resseting and to no avail nothing has worked and I'm at the end of the line with ideas and frustration. If anyone can help at all it would be much appreciated. I'm attaching an image of what it looks like when I try to turn bluetooth on and it won't turn on. It greys out and nothing happens, won't turn on, search for devices or anything.
That certainly sounds awful. The last thing I'd try is doing a reflash of your firmware, to see if that helps (maybe something got corrupted along the way, and this should solve that). If that doesn't work, then you might just have a hardware issue. If you're rooted, you could investigate further... I'd start by looking at the logs in the phone to see what's erroring out...
Yeah I have tried refreshing the firmware so I'm guessing it is a hardware issue... but it's happening with the pixel line of phones. But how would I check the logs? Thank you so much for your input!!! I really appreciate it
Refreshing the firmware (or factory reset) is different from reFLASHing the firmware... I just want to make sure you tried the reFLASH.
Wait, is the issue with the Pixel phones, or the Samsung (this forum is for Samsungs).
Also, is it possible that the bluetooth device could be the issue? Does the device work reliably with other phones? For example, my company had many issues with Toyota bluetooth on the company cars and Android phones... this was a few years ago. It's because Toyota didn't follow the standard properly. Other people had issues with Nissans. Again, these were older cars, but the point is that the device was the problem, not the phone...
No the device is fine it's just the phone, I know this because another device works fine with it and even with a car pairing or another BT speaker have the same issues.
Have definitely tried to reFLASH the firmware and I was just saying this problem also seems to be common on the pixel line as well.
Would you recommend to check system logs to see if it's a hardware issue?
Checking logs (like dmsg) is one place to look... to see if there are any warnings and errors in there. I don't have any specific guidance on how to do this or what to look for, but that's where I'd start. I don't know if you can find dmsg logs without root (I tinkered with that in my previous phone which was rooted, but I didn't use it much so I don't have much guidance to offer... you will likely need to read up on what these logs have, etc).
Related
my diamond is playing up, there are no sound at all from earpiece, ringer or loud speaker after every 30mins to 1hour,
once you restart the phone and its works again, then gone within 1hour, have to keep restart the phone
here what i have done:
i run this RUU_Diamond_HTC_WWE-ME_1.93.456.2_Radio_Signed_Diamond_52.29.25.12_1.0 0.25.05_Ship
Still not fix
then this
SwiftBL-WWE-Diamond-ROM-v5.6
still not fix,
i dismantle the phone have a look is anything simple loose connection and such, but there is no sign of that or no sign of any water damage.
please if you have any idea to share here will be much appreciated
thanks
Same problem here...
looks like still fresh this Diamond phone, no one have idea yet to rectify this issue
still waiting.............
if it is fine to begin with, and then it goes after a little while, i would say it is not a hardware problem, but a software one.
especially as you have tried it on more than one ROM, it suggests that you may have installed something else on to the device which may be influencing it.
Hard reset and sycn your contacts etc back to the device, but do not install anything else, or do any tweaks at all.
let it run out of the box without any changes for a 24 hour period.
does it still happen?
if yes, send it back.
if no, start putting everything back on one by one until the problem re-occurs, trying the device for a couple of hours after each install. when it fails again, you have your suspect which is the last thing you installed or did before it failed again.
course, it could be a dodgy device, but make sure before you go through the hassle of sending it back, cos it could just be some software that doesn't like wm6.1.
I have been having problems with rotation. I am beginning to think I have a problem with my hardware, but here is the problem:
First off, I am experiencing this with multiple ROMS: Cognition, Perception, and Assonance, various versions on all.
ALWAYS...when I first flash, it works fine. Within a few days it may quit, and it may start back up. But ultimately seems to stay off.
The problem is, that I am thinking that when I call for AT&T to report it, they will tell me to do a hard reset, and it will work again. (I actually don't know for sure if hardwar reset seems to fix it or not).
Anyone else fighting this? Any thoughts?
[EDIT]
I just did a hard reset, and yes, rotation came back. It must not be hardward, but I can't imagine what is killing it. Quite frustrating.
ewingr said:
I have been having problems with rotation. I am beginning to think I have a problem with my hardware, but here is the problem:
First off, I am experiencing this with multiple ROMS: Cognition, Perception, and Assonance, various versions on all.
ALWAYS...when I first flash, it works fine. Within a few days it may quit, and it may start back up. But ultimately seems to stay off.
The problem is, that I am thinking that when I call for AT&T to report it, they will tell me to do a hard reset, and it will work again. (I actually don't know for sure if hardwar reset seems to fix it or not).
Anyone else fighting this? Any thoughts?
[EDIT]
I just did a hard reset, and yes, rotation came back. It must not be hardward, but I can't imagine what is killing it. Quite frustrating.
Click to expand...
Click to collapse
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
LibertyMarine said:
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Click to expand...
Click to collapse
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
anibjoshi said:
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
Click to expand...
Click to collapse
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
Try flashing a Sense ROM, like ARHD or MaximusHD?
Enviado de meu HTC One usando Tapatalk
LibertyMarine said:
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
Click to expand...
Click to collapse
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
IINexusII said:
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
Click to expand...
Click to collapse
No I rooted the device but did not install any root apps...i unrooted the device to install the GPE Rom(not necessary i know, but it seemed like a proper way) and found that it started giving problems immediately. Can non-root regular apps also cause such problems? I had installed only a limited number of apps anyway, updated the pre installed apps, facebook, twitter, whatsapp, some games..thats it..nothing wierd..
Might be a Screen-Off max. frequency issue. Like the phone gets only 500Mhz in sleep mode at maximum. Which is to low for an incoming call. Could you install a app like Android Tuner or Trickster Mod to check your Screen-Off Max frequency. If it`s that low, set it to ~1000Mhz.
anibjoshi said:
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
Click to expand...
Click to collapse
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Yup try installing kernel and custom rom.
Remove the case and try ( i know this is stupid thing but can give it a try)
Jvov said:
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
Click to expand...
Click to collapse
Thanks for your help buddy! I really appreciate it!
anibjoshi said:
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Click to expand...
Click to collapse
Thanks ! That's awesome and gives so much motivation! If you find out that you have a hardware defect and that you have to send it to HTC, I'll give you some information how to deal with those guys that you get your warranty.
I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?
It's not a stock rom.
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Without getting a logcat there is nothing anyone can do except guess what the issues is.
donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.
zelendel said:
Without getting a logcat there is nothing anyone can do except guess what the issues is.
Click to expand...
Click to collapse
I was hoping someone who had the same problem might chime in. What should I look for in the logcat?
johninor said:
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.
Click to expand...
Click to collapse
I just clean flashed the latest version of the Lite ROM and it did not fix my problem.
donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
I tried a clean flash of the Lite ROM. That didn't solve the problem. I then flashed the latest factory image (MOB30W). I did not restore anything or install any apps except Google Play Music and Podcast Addict, which I am using to reproduce the problem. I still have the same problem. Bluetooth media audio is working indoors, but as soon as I step outside it breaks up and goes out completely for 20 or more seconds at a time.
I think that rules out the Lite ROM as the problem. Anyone have any ideas for me?
I googled looking for bluetooth audio breakup issues and I found a few things that were suggested to fix it. They were turning off the WiFi and and turning off GPS. I tried both and they did not help my problem. I didn't expect them to because they were fixes for people reporting general bluetooth breakup on specific devices, while I am seeing the breakup on Media Audio, but not Phone Audio.
If anyone knows of a better place to ask my question, please let me know. I've been searching and can't find an answer or a better place to ask the question.
After some research here may be a fix...
johninor said:
I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?
Click to expand...
Click to collapse
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
donnyutx said:
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
Thank you. I hadn't found that thread when I searched. I tried the several suggestions in that thread. One was clearing caches, which, of course, I had already done as a result of testing clean installs of the ROM I use and the latest stock ROM. So that didn't solve the problem. The other suggestion was turning off bluetooth scanning in location settings. I hadn't even known that was a thing. I tried turning off bluetooth scanning and wifi scanning this morning and used my phone all day as usual. It didn't solve my problem - no change at all. I had in an earlier test turned off the GPS and that hadn't helped either.
The second link, I believe is just a different way of installing ROMS and managing related stuff. I don't think that tool is going to do anything that I didn't do by installing the latest stock ROM with the flashall.bat script.
Love the device, but this one is going in for an exchange. Not sure if it will resolve the issues I had, but my phone was behaving badly. I unlocked and rooted it about 10 minutes after I got it, using the Chainfire method here..
1) WiFi reception is awesome, except it drops the connection constantly! I have an entry level commercial AP (Unifi) and the thing is awesome. All kinds of devices connected to it, but this Moto can't stay connected. From the logs on the controller, it appears to be switching channels constantly. Wifi goes from all bars to bars with x to off.
2) Reboot results in bootloop. On more than one occasion, I had to reset the device multiple times to get it to boot. This morning, I could not get it to complete a boot at all. I've since reflashed the Tmo stock ROM.
3) Lookout randomly comes back! Froze it with TiBu, stop and disable in app manager... nothing kills it! Reason 1 for root!
The WiFi issue is a killer. Again, I am going to take this one in and exchange it for another and hopefully the WiFi issue is gone. I think I'll need to restrain myself from rooting until I pass the exchange date.
I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now
forty9er said:
I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now
Click to expand...
Click to collapse
Thanks! I will give that a shot before I take it in.
I've been back on stock with unlocked bootloader for a day and change, and I still get WiFi drops. It seems to happen more with BT on, but they certainly haven't gone away. I've changed a bunch of things on my AP to try and eliminate them too, but it hasn't helped much. I may try disabling the A/C radio (which fixes it for some), but that's hardly an answer. I am starting to think that this is a Nougat or a Qualcomm issue.
Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Sent from my Moto Z (2) using Tapatalk
Tidbits said:
Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Click to expand...
Click to collapse
Well, it seems I'm not the only one.
https://forums.lenovo.com/t5/Moto-Z...terprise-type-5Ghz-band-802-11AC/td-p/3816198
I actually have this issue with another device too , so I think it's either an Android, AP or a Qualcomm thing. Some have said turning off the A/C/N radio helps, but that's not a "solution."