Database Develop

reboot loop

I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman

Mine reboot when it overheats during charging. There are several overheating threads u should check out.
Sent from my Nexus One

Just be honest
houmi1 said:
I used to have random reboots on Nexus One, but after updating to Froyo 2.2 (before the official release), I had noticed the random reboots to get more (like 2-3 a day), but now the phone is totally useless, it does reboot constantly, and when it's connected to Power, it reboots couple of times, then gets stack at the Nexus logo.
I have put the stock firmware back, EPE54B, and it even detected 2.2 and Google pushed me the official release and still no go (yes, I did clear cache, etc)
I loaded up the log program and checked the logs after a reboot to see if it was some sort of kernel panic or something, but it does not show anything per say.
I even tried w/o SIM or w/o memory card and the results were not conclusive, it worked for some time, then started rebooting on its own. Sometimes I notice the phone is very hot, which makes me think that it might be faulty hardware (ram, etc)
Has anyone seen such an occurence, would HTC repair the device now the bootloader is unlocked or is this just a thin paper weight ? I think I read someplace that they still honor hardware repair...
Thanks,
Houman
Click to expand...
Click to collapse
From what I hear, if your honest and tell google that you unlocked your bootloader they will still repair your device, I don't know about replacing it if it can't be repaired. But before you go that route try troubleshooting. Make sure you have the correct radio, not all roms come with the correct radio. Non-compatible kernals can become a issue to, if you flashed a custom kernal. I get the bootloop problem if I flash a rom without wiping, which I never do, except when the instructions say no wipe required, and then I get the bootloop issue. So try a full wipe, data, dalvik & cache, ext, and then reflash your rom.

I had random reboots up the wazoo. My phone was unlocked/rooted/running FRF93. I downgraded to other versions of Froyo and even went back to 2.1/CM and it was still rebooting.
Turns out that HTC actually puts it through a reasonable testing procedure to determine if it was in fact the user that damaged the phone. So even if it is unlocked/rooted and the phone passes the test, you will get your repair free of charge just like me. I'm currently waiting for them to ship my phone back.
Although I have heard horror stories from HTC, so I really think it depends on the moon cycle...
Like a poster above said, BE HONEST. Let them know the truth that it's rooted/unlocked but currently running a standard ROM. If they give you the standard "if it's rooted, you're going to have to pay", tell them that you're heard of their testing procedure to determine if it's the user's fault. Go to a supervisor if you have to.

Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91

houmi1 said:
Hi,
Thank you all for the responses... so I decided to leave the battery out completely for one day, then put the battery in the phone, and I did quickly use the phone to wipe it as well as wiped the storage clean... so the phone should be back to regular day 1 status other than boot loader being unlocked. I guess by putting the PASSIMG.zip which has EPE54B files, I forgot, and it also flashed over the ramon recovery as well.
Then I turned off the phone but connected it to the charger and let it charge completely, this morning I turned on the phone and it has been on w/o reboots.
So this points to either heat, radio (wireless, 3g) -- it does not have a sim in it currently, but the good news is that it's not rebooting. I think I'll play with wireless first, then add 3g then we'll see where it takes me, but if it comes to returning it to HTC/Google, I'll be honest of course.
This has by the way:
Android Version: 2.2
Baseband: 32.36.00.28U_4.06.00.12_7
Kernel 2.6.32.9-27227-g3c98b0d
Build FRF91
Click to expand...
Click to collapse
Any updates? I have a similar issue

Yeah I basically think it's heat related and unrelated to the firmware, RAM, etc.... I had the phone at a very cool place and it works perfectly, and when I started using it, as it got hot, it started rebooting, and I noticed the back of the phone was very hot.
So I think nxt was right #2 in this thread.
Houman

The above observation would seem to make sense. My phone would reboot while trying to watch youtube videos sometimes, but ALWAYS within a few minutes of using it on the mains...
I have since had it sent back to HTC to have the phone repaired. I had rooted my phone just to get 2.2 however as it was a genuine hardware issue they replaced the main board and now not only does the phone not reboot anymore, the issues I had with no 3G (only Edge) have disappeared too. Happy
BANE

Hi
So I got my phone back from htc, they basically fixed it and even locked the bootloader so all is well
Just FYI
Houman

Help diagnosing freezes and random reboots

I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?

Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.

I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.

Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much

studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)

stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.

stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues

Another AOSP Brick

So My phone is most certainly bricked this morning. I saw a few posts on the topic, as well as one that was locked. Seems that there a re more than 5 of us, can a mod by chance merge the posts, so we can start troubleshooting the issue, and keep it from happening in the future. I will describe what I have done, and maybe it will help someone come up with an idea of what binds us all to our bricks.
Once upon a time in a galaxy far far away I was a flashoholic:
So I get my black one in the mail, and start playing in the forums, seeing what's what, and I go about trying to moonshine, firmware doesn't match so it doesn't work, get her rooted, s-off with revone, and flash a few sense based roms. No problems. Try the cm rom listed in the first post of the 10.1 link, no gps, weak signal, back to sense. Finally get a few of the threads completely read, and find rc2 of 10.1 flash(using twrp 2.6.1.0, and I do all the wipes and format data, and factory reset before sideloading my roms) get it up and running, gps works, find the build.prop line to edit to get it to stick to sprint to work, and away we go, rom is good, problems are small, phone working exactly llike it's supposed to. I did play with trickster mod here and there, but didn't much care for the program. So was playing in original development, and saw that the twrp forum had new input, so I go into it, and see a new twrp available (2.6.3.0) dl, flash the .img, reboot recovery, wipe everything, sideload 10.1 rc2 again and gapps. Almost immediately noticed the temp on the phone was very warm, almost hot, and that was without being on the charger. It was bedtime, so plugged phone in, go to bed, get up look at phone, and its at 50 percent on the dot, and no red light. Houston we have a problem. So I start researching how to ruu back to stock, and just to see if it was the recovery, I flashed cwm, didn't like it, and then reflashed the older twrp, problem persists, well I really didn't want my phone to reach 0 percent battery, so the race was on, set phone on ac vent and charge it, take it off charger, it would drop 20 to 30 percent in five to ten minutes. Get ruu downloaded, can't get it to run, troubleshooting that, my battery plugged in is down to 6 percent and the speakers are hissing at me, when I see the problem, plug it in to the laptop, run ruu, watching phone, watching progress, complete!!! yes reboot phone, log in to gmail, get message about phone using more power than it's receiving (plugged in to wall again) and boom shutdown. So now I'm thinking to myself hrmm good or bad, red light says charging, go smoke a few cigs comeback in phone boots, and is charging, no errors, everything is running like it is supposed to, everything works. It's still very warm though for not running much of nothing, leave it in the cold air, and she charges up to 100% (albeit slowly took most of the day) unplug her, go to sleep, and about 3 hours later I heard the low battery warning, and woke up to my nice black brick. No red light, no pressing buttons for x amount of time, she is most certainly dead.
Hopefully this can help us figure out what is causing the bricks.
And only 3 more hours to the sprint store opens :victory: that's bound to be fun

I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.

phatmanxxl said:
I'm willing to bet your phone had a bad battery. Too bad we can't check for ourselves.
I was running slim rom and after a few days i lost all sound on my phone, even with headphones plugged in. Flashed a Stock rooted sprint ROM, still no sound. I then decided flash the hexed fastboot menu to mask the S-off, "tampered flags" and splash screen, RUU'ed back to stock and returned the phone. I'm hesitant to flash another asop rom, I'll just flash sense Roms from now on. Still waiting on that 4.3.
Click to expand...
Click to collapse
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.

raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
I don't know, I love Slim ROMs but if it happens again Sprint will start asking questions and might investigate the phone, plus I got the last red phone in stock

raptoro07 said:
Yeah, I agee. There is nothing in your story that makes me think the problem was an AOSP ROM.
Click to expand...
Click to collapse
How many brick threads have you seen in here on Sense roms?

n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
Including folks that flashed gsm roms? Zero

n1gh7m4r3 said:
How many brick threads have you seen in here on Sense roms?
Click to expand...
Click to collapse
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....

i wont even flash an aosp rom on this phone i have seen a few people brick while on aosp.. and the dude i got my one from he bricked his first one running an aosp rom.. he said he rooted it flash an aosp rom.. was fine for a week or so the while listing to music on the phone it died brick.. im not saying its deff aosp roms but i have seen and heard enough where im not going to try it... lol im good with my sense:good:

I wonder what's the difference between GE ones and Sense ones.

raptoro07 said:
So in summary: you flashed an aosp Rom decided to go back to a sense Rom decided to go back to aosp messed around flashing recoveries, ruu'd back to stock and then it died. You got a lot going on there is what I'm saying.
but it's ok to eat fish cause they don't have feelings.....
Click to expand...
Click to collapse
I guess you could summarize it like that, but I thought that I stated I knew it was going to die, shortly after I upgraded my recovery. All flashing after that was an attempt to troubleshoot/save the beast if at all possible.

Well I know what's causing the bricks.
So i figured out in part at least what is indeed causing the bricks. It was my first guess, but I messaged a couple of kernel devs, and the information they gave me led me to believe my first assumption was wrong. Apparently it was not. i am not sure if it's an aosp thing, a twrp (was using 2.6.1.0) when I found out, or just a really nice user error experienced by a handful of people. But regardless, either the kernel, and or some of it's settings are not being wiped in twrp to include an advanced wipe of all check boxes besides usbotg, a format data, and then a factory reset wipe. So when kernel or settings interact with new kernel/rom that you install and they don't play nice together, you get your nice little brick. Oh but how do I come across such preposterous conclusions you ask yourself? So I payed my 50 bucks, got my new phone, put my go to rom on it, and play away; lo and behold a stable 10.1 cm comes out. Can't resist, must flash, disapointing to see in the stable release the first thing I have to do is edit build prop to get sprint signal(it is a sprint rom yes?) Still liking the rom for what it is, probably my favorite, except Trebuchet is laggy as S**t(ping pongs kernels alleviate this, but his kernels are for 10.2). So in an attempt to fig the lag, i play with different settings and whatnot that I found laying around xda here and there. nothing is helping with the stutter I see on the home screen. So I go to the main One thread, and look around for kernels, I find one, don't figure it will work, but figure I'll just wipe if it does bad things to my phone; and it did. 8 boot loops later what do I do? Wipe everything as mentioned above, and sideload 10.1 stable, guess what happens on reboot? That's right bootloops. So some how the kernel or some of it or its settings at least are not going away as they should on a clean install, and that I'm sure is what is causing the bricks.
Ty,
I'll be here all night

You sure do keep a really good attitude through it all though. We've all been there but you are purposely putting yourself and wallet through it over and over to find the culprit. I for one appreciate it.
D

Freezing and bootloops.

Anybody else having these problems? 2nd day to have it and it would freeze up and bootloop. At one point it was off for 2-3 hours and I couldn't get to fastboot. Finally I got it to factory reset twice and its doing fine for now. Unfortunately I'm on shift for 24 hours or I'd make Verizon give me a new one.
Sent from my XT1254 using XDA Free mobile app

Aarongauntt said:
Anybody else having these problems? 2nd day to have it and it would freeze up and bootloop. At one point it was off for 2-3 hours and I couldn't get to fastboot. Finally I got it to factory reset twice and its doing fine for now. Unfortunately I'm on shift for 24 hours or I'd make Verizon give me a new one.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Could it be some app that you installed? Haven't had any problems myself with it.

Have you switched from dalvik to art?

I've had zero issues with bootloops so far.

Haven't switched to art and I doubt any nonroot app would cause bootloops. Who knows.
Sent from my XT1254 using XDA Free mobile app

No issues so far here

none here

Had one this morning. Phone froze during a phone call, and then got stuck at the boot screen before the animation. Rebooted it by holding the volume and power button and it's worked since.

No problems here, have played games for several hours straight with no issues and have been playing with it all day.

Mine was solid for about 4 hours and its starting back up again. Maybe I have a lemon.
Sent from my XT1254 using XDA Free mobile app

sounds like a defective unit or something.
i'd do a wipe, dont install any apps, see if it works fine or not. if it does, probably an app issiue. if you are getting problems even after the reset, its the phone.

Same issue here. Kept randomly rebooting, but only occasionally. Did a few factory resets, installing only essential apps each time thinking it was one of my apps that didn't play nice with Turbo (even though they played just fine with my Razr Maxx and Galaxy S5) to no avail. Last night, did a factory reset, didn't install any apps (nor did I update any of the pre-installed ones) and this morning, endless bootloop. I can't get it to stop. I'm really starting to hate this startup sound. LOL!

My phone locks up occasionally. Always restarts itself. I'm not sure what has been causing my phone to lock up but I haven't been able to pinpoint an action that is specifically creating the issue.
Sent from my XT1254

So I couldn't figure out a way to just power it down (all the usual button combinations just kept rebooting it, which then continued the bootloop) so I just figured I'd let it bootloop until the battery ran out. After about 3 hours of bootlooping, it just finally booted. I didn't touch anything. Weird. Maybe it's like a 4 year old temper tantrum, just let them get it out of their system and all will be better in a couple hours. Hahaha!

I have a phone that it's going this as well. I can get into recovery and reset but that didn't work. If I try to wipe cache the phone reboots and freezes which seems abnormal. I never had a phone reboot after wiping cache. I loaded the phone into fastboot and using RSD Lite I flashed the original software into the phone to no help. I did notice though that in the fastboot option that my baseband is blank. Might just be a bad device.? Does anyone know where I can find stock firmware 21.44 (that has the VoLTE option)?

I've had 4 turbos, latest one with almost no apps, and been waiting on Motorola for near 3 weeks for another device... Just about to sell the next turbo they send out... I've also had the same issues plus WiFi drops BT drops freezing lagging, and lately unable to receive voice calls and voice mail

polish23 said:
I've had 4 turbos, latest one with almost no apps, and been waiting on Motorola for near 3 weeks for another device... Just about to sell the next turbo they send out... I've also had the same issues plus WiFi drops BT drops freezing lagging, and lately unable to receive voice calls and voice mail
Click to expand...
Click to collapse
With four turbos there seems to be more of a user error than system. you either disabled a needed apk, installed an apk that doesn't play nice, or you took an ota and havent completed an FDR. Its recommended and has been posted on here multiple times throughout this site/forum that always, always do a FDR with an update.

the_rooter said:
With four turbos there seems to be more of a user error than system. you either disabled a needed apk, installed an apk that doesn't play nice, or you took an ota and havent completed an FDR. Its recommended and has been posted on here multiple times throughout this site/forum that always, always do a FDR with an update.
Click to expand...
Click to collapse
I'm not running any additional apks at this point and haven't since the second replacement device. Apparently, I just have good luck with this phone, that I now despise, and wish I could get rid of. I followed all the disable guides for what was safe, and I'm not sure what an FDR is, but if you tell me I'll give it a shot. Last replacement came updated as well. At this point this current model doesn't even receive phone calls, because it just doesn't work correctly.

polish23 said:
I'm not running any additional apks at this point and haven't since the second replacement device. Apparently, I just have good luck with this phone, that I now despise, and wish I could get rid of. I followed all the disable guides for what was safe, and I'm not sure what an FDR is, but if you tell me I'll give it a shot. Last replacement came updated as well. At this point this current model doesn't even receive phone calls, because it just doesn't work correctly.
Click to expand...
Click to collapse
Factory Data Reset.

the_rooter said:
With four turbos there seems to be more of a user error than system. you either disabled a needed apk, installed an apk that doesn't play nice, or you took an ota and havent completed an FDR. Its recommended and has been posted on here multiple times throughout this site/forum that always, always do a FDR with an update.
Click to expand...
Click to collapse
the_rooter said:
Factory Data Reset.
Click to expand...
Click to collapse
OK, so I have done that with each of the devices. Unfortunately, I just have horrible issues/luck with this phone.

Some issues I've had (2 days in)

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."