Develop Bugs

[Q] M7VZW Died twice, after installing cm11. Over heating and battery draining fast.

Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!

ccarr313 said:
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
Click to expand...
Click to collapse
Are you using the stock charger?
Try a different charger on the next phone. Many people have flashed CM11 and don't have those issues so it appears to be your charger that's killing the phones.

Don't think it's the charger. I am seeing more and more threads of people running cm11 a d getting this overheat issues then phone dying. I think it's best that people leaves cm11 alone until it can be fixed. As I have never seen any other Rom act like this.
Sent from my HTC6500LVW using Tapatalk

The only thing i can think of, after resting on it, is that i turned on the DSP manager EQ shortly before it happened each time. Not going to customize the one I am getting today. Just thankful I know enough that I managed to get them both back to s-on / locked / stock RUU before sending them back.....so my warranty will cover them.
And yes, i was using the stock HTC charger that came with the device. Wish i had a meter.

This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.

peteschlabar said:
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
Click to expand...
Click to collapse
Both phones are dead. Will not charge, will not turn on. They only worked for a few hours after the over heating issue started. Battery continued to drain even after being turned off, and after it was drained it would not charge at all. It was lucky i could even get them back to s-on / locked / stock. And the issue continued after going back to stock. Hardware damaged for sure. So no more testing on those. lol

On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.

Fu5ion said:
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Click to expand...
Click to collapse
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao

ccarr313 said:
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
Click to expand...
Click to collapse
They'll let you send as many as you want as long as its under warranty haha. I remember I had to send in the droid bionic 4 times and the droid RAZR twice, both times without any hassle from them. I just had awful luck with those phones, mostly screen-lifting.

Haha. Good to hear. Because I have 10 months of warranty left, and I am a computer modder at heart.....and that has turned me into a custom rom loving phone crazy person. :laugh:

Yeah you've got nothing to worry about there. Just make sure its back to stock. They honestly probably wouldn't say anything if it weren't, but we don't want to give them even more reasons to lock us down more.

I'm having the same issues. I'm on my 4th phone now.
This happened to me on several ROMs. SlimBean 4.3, SlimKat 4.4 now.. and I flashed back to stock while I had a phone that wasn't dead yet.. but it's still happening.
I'm not sure what the deal is. Just happens without rhyme or reason out of the blue one day.
Can anyone recommend flashing anything that might help?
What's responsible for the battery management even if there's no ROM installed? HBoot? Should I re-flash an HBoot to attempt to fix? It's not the ROM, I don't think. If it is, it's something that permanently screws up the phone. I've completely wiped my phone and went to stock. Same issue.

I got my new phone, and s-off'ed / unlocked / flashed cwm recovery, then updated it to 4.3 ota, no issues so far. Scared to put any custom rom after what happened to the last two. But having no issues yet with it, with only a custom recovery and s-off. Have rom manager loaded also, and made a back up since it seems to be running fine now. If anyone isolates this problem and can get a fix going, would make me very happy.

I've noticed that trickster and some of the other CPU performance apps are locking the min CPU speed at the max speed so the phone always stays at top speed. If it stays like that for an extended period of time it will damage the phone. The heat can cause the battery to drain really fast and damage the CPU. If you are on any ROM with a custom kernel I would be on the lookout for this.
Sent from my HTC6500LVW using Tapatalk

I was running CM11 on my nexus Galaxy and I thought my battery was bad. My phone would die after a few hours. I got a new battery and it did the same. I installed slim ROM and now I am getting 10+ hours no problem. Also my phone does not feel like it is going to melt.

Do I keep it or switch it? Need advice

Just bought the G4 on 8/6. I'm going in to return it tomorrow. It gets terribly hot and the finding location icon is constantly flashing. I don't know if I should just swap it for a new G4 or get something else. I know there is a root method but I've heard of it working and causing issues for others. I saw a thread where the My Verizon app was asking for root access. I know you can just freeze it. It stinks that the phone is locked. I'm torn between this phone and the Nexus 6. What would you do?

I'd try finding out what's causing it to get hot; Probably some apps running in the background that don't need to.
Getting root isn't an issue as long as there is a compatible image. What you do with root access could cause issues.
You can disable some of the built-in apps with root (you can do it within FX Explorer + root addon). That should improve performance/increase battery life/reduce heat.

Try using the Cooler app from playstore.

Knowbody42 said:
I'd try finding out what's causing it to get hot; Probably some apps running in the background that don't need to.
Getting root isn't an issue as long as there is a compatible image. What you do with root access could cause issues.
You can disable some of the built-in apps with root (you can do it within FX Explorer + root addon)
Click to expand...
Click to collapse
Well honestly, I don't mind that there is no recovery yet. I use root to backup with Titanium, use adblock, and freeze all the Verizon nonsense.
FreedomUser said:
Try using the Cooler app from playstore.
Click to expand...
Click to collapse
Is this the app you're talking about? There's a few of them.
https://play.google.com/store/apps/details?id=com.easyx.coolermaster
On a side note, I keep leaning towards the G4. I loved the G2. I'm on Verizon and would pick up the VS986. It comes with 10B I think and then it updates to 11A. If I decide to stay with the G4, should I try rooting before upgrading? I'm almost certain that out of the box, it needs a software update.

Fridge.
Sent from my A0001

sefirosu0522 said:
Is this the app you're talking about? There's a few of them.
https://play.google.com/store/apps/details?id=com.easyx.coolermaster
Click to expand...
Click to collapse
Yes that's the app i'm talking about, but you can use others too, they are same.

sefirosu0522 said:
On a side note, I keep leaning towards the G4. I loved the G2. I'm on Verizon and would pick up the VS986. It comes with 10B I think and then it updates to 11A. If I decide to stay with the G4, should I try rooting before upgrading? I'm almost certain that out of the box, it needs a software update.
Click to expand...
Click to collapse
It will likely come with 610B, so there is definitely an update available.
The first root image released for Verizon was 611A. But I'm pretty sure someone has since released a rooted image for 610B, so you might not need to update.
But I could not get some features (Advanced Calling) working on 610B, until I updated to 611A. So it's possible you would want to update to 611A anyhow.

Honestly, id wait for the nexus and the note 5 coming out. The touch issues along with lg not wanting to unlock bootloader has made everyone frustrated.

I've bought the european version H81510C and the video are plagued with all major side-effects of the rolling shutter. Wobble, skew and warping effects, all around, literally a jello cam very similar to the after effect warp stabilizator, just lot's more unpolished. The top of the phone reach very high temperature by random or just by calling someone and if you launch an app in GL ES 2.0|3.0 ( OPEN GL ES 3.1 + AEP doesn't seems to correctly "work" on this device (missing support of most texture extension:lightmap and such) will try Arm64 build later and/or texture compression), you'll burn your palm. The G4 seems also to discharge or doing something unattended trough the Qi wireless charging antenna tho, cause I feel mine arms becoming insensitive ( physical harm ) after holding it for a while under normal usage (insulating the 2 pin on the backcover does help a little, but, still unpleasant to keep in hand). If I were are able to find the XT1250|XT1225 for less then 350 I would swap it immediatly, nonetheless I'm also debated to return it and wait till september for a replacement, anyhow the NEXUS is a better choice, except for the camera, even a new ZenFone2 updated to the last avaiable version along it's propretary APP is better of this 600 EURO data collector.
update:
By updating to lastest version (or by NOT keeping it in the hands), the overheating issue seems somewhat under control.
About the unpleasant feeling | electric field > magnetic constriction = discharge , I found out mine shell ( backcover + wireless charging antenna ) the white one ( simil-ceramic ) is made by acrylonitrile butadiene styrene (ABS) "reinforced" with 10% of glass fiber.
About the LG G4 OPENGL ES 3.1 - it's very slow, it doesn't even make a third of a frame in one second ( other device reach 25-44 FPS ), will try in ASTC..and its better by not much.
--
That's mine experience with LG and I call it night- refund under way, will check the PRO version if one avaiable this year.

The G4 is fine. If it is overheating then there is a rogue app or process killing it. My coworkers Samsung G 5 was chewing through batteries and Exchange services was taking up most of the resources. We default the Email app and setup it up and all is right now.
When I first got my G4 and set it up, initially it got hot as hell downloading apps and settings. I did a factory reset and it has been fine since. It never gets hot anymore. I use GPS and QC 2.0 fast charge while on the phone (I travel for work) and it is fine. The only time I had an issue with heat was when I left it out in the sun while streaming pandora.
I think the issue is something to do with setup. I noticed I had bought mine at a brick and mortar store and the sales guy quickly ran through the setup and skipped a bunch of stuff. I think something was stuck in the background trying to do something. Once I factory reset it and set it up properly, I never had a problem. My friend also ordered a G4 online and had it shipped and she never had a problem.
Just my thoughts.

player911 said:
The G4 is fine. If it is overheating then there is a rogue app or process killing it. My coworkers Samsung G 5 was chewing through batteries and Exchange services was taking up most of the resources. We default the Email app and setup it up and all is right now.
When I first got my G4 and set it up, initially it got hot as hell downloading apps and settings. I did a factory reset and it has been fine since. It never gets hot anymore. I use GPS and QC 2.0 fast charge while on the phone (I travel for work) and it is fine. The only time I had an issue with heat was when I left it out in the sun while streaming pandora.
I think the issue is something to do with setup. I noticed I had bought mine at a brick and mortar store and the sales guy quickly ran through the setup and skipped a bunch of stuff. I think something was stuck in the background trying to do something. Once I factory reset it and set it up properly, I never had a problem. My friend also ordered a G4 online and had it shipped and she never had a problem.
Just my thoughts.
Click to expand...
Click to collapse
had same problem with mine ,first day it ran hot as hell but after first day, it has not got hotter than any other fone i have owned.

player911 said:
The G4 is fine. If it is overheating then there is a rogue app or process killing it. My coworkers Samsung G 5 was chewing through batteries and Exchange services was taking up most of the resources. We default the Email app and setup it up and all is right now.
When I first got my G4 and set it up, initially it got hot as hell downloading apps and settings. I did a factory reset and it has been fine since. It never gets hot anymore. I use GPS and QC 2.0 fast charge while on the phone (I travel for work) and it is fine. The only time I had an issue with heat was when I left it out in the sun while streaming pandora.
I think the issue is something to do with setup. I noticed I had bought mine at a brick and mortar store and the sales guy quickly ran through the setup and skipped a bunch of stuff. I think something was stuck in the background trying to do something. Once I factory reset it and set it up properly, I never had a problem. My friend also ordered a G4 online and had it shipped and she never had a problem.
Just my thoughts.
Click to expand...
Click to collapse
Thanks for the input. I ended up getting a new phone becasue I was within the 14 days and it has been running fine.
Thanks for the replies everyone.

sefirosu0522 said:
Thanks for the input. I ended up getting a new phone becasue I was within the 14 days and it has been running fine.
Thanks for the replies everyone.
Click to expand...
Click to collapse
Glad it worked out.

Pixel suddenly dying with 15-30% battery left

Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?

l2yangop said:
The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
I had it happen once with an unrooted phone near the end of December.

I guess I'm going to send it in... but don't want to bother flashing back to stock if I dont have to. thoughts?

l2yangop said:
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
Was the phone cold? There is extensive conversation about this on the Nexus 6P forum, and it is much worse when the phone is cold. I had it happen cold and warm, but it happened often when it was below 30 degress F.

thacounty said:
Was the phone cold? There is extensive conversation about this on the Nexus 6P forum, and it is much worse when the phone is cold. I had it happen cold and warm, but it happened often when it was below 30 degress F.
Click to expand...
Click to collapse
no, i live in FL haha

l2yangop said:
no, i live in FL haha
Click to expand...
Click to collapse
Haha. I've been in FL when it was 35!
I was just wondering if it was the same scenario. Not that it would be acceptable.

l2yangop said:
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
You could try flashing February stock rom, then doing factory reset, in case anything is out of kilter in software causing this.

l2yangop said:
Is anyone else running into this? I did a quick search, and didn't see any hits in the the Q&A section or the PureNexus ROM forum which I'm running. I think it is a somewhat common problem. The first thing google support chat asked me was if I was rooted. I said no, but is this only happening to rooted phones?
Click to expand...
Click to collapse
This is now widely reported and seems to be major problem affecting lot of pixel phones. Check out the number of entries in the product support page and in the android code tracker.
https://productforums.google.com/fo...!msg/phone-by-google/QiGBJRx9oxg/Xy5_pkJZDAAJ
https://code.google.com/p/android/issues/detail?id=230806 - Google has marked it as fixed and status is updated as future release which means that it is a software bug.
I also had this issue but i dont have it right now. Mine got resolved by using a non-stock and non-quick charger to charge the phone. I havent faced this issue for the past couple of weeks now. Some people had success doing it and some did not. So its more of a hit and a miss. My guess is that this is a software bug caused by the battery reporting percentage

I have this bug at the moment too. Some users are reporting that a factory reset solved it for them so I have done one yesterday. Can't say yet if it fixed the problem for me too.
You can read more here:
https://forum.xda-developers.com/showthread.php?t=3530040
Gesendet von meinem Pixel XL mit Tapatalk

lalit79 said:
This is now widely reported and seems to be major problem affecting lot of pixel phones. Check out the number of entries in the product support page and in the android code tracker.
https://productforums.google.com/fo...!msg/phone-by-google/QiGBJRx9oxg/Xy5_pkJZDAAJ
https://code.google.com/p/android/issues/detail?id=230806 - Google has marked it as fixed and status is updated as future release which means that it is a software bug.
I also had this issue but i dont have it right now. Mine got resolved by using a non-stock and non-quick charger to charge the phone. I havent faced this issue for the past couple of weeks now. Some people had success doing it and some did not. So its more of a hit and a miss. My guess is that this is a software bug caused by the battery reporting percentage
Click to expand...
Click to collapse
Thanks for you reply. I have seen reports of people sending their phone (usually the 6p but even a couple pixels) back for repair under warranty . If its a software bug and we're on the latest version of software, what could they be doing to fix it when they send it back I wonder? Make me think its hardware.

This could be indicative of a malfunctioning battery. Flashing back to bone stock would be the best troubleshooting method.

[email protected] said:
I have this bug at the moment too. Some users are reporting that a factory reset solved it for them so I have done one yesterday. Can't say yet if it fixed the problem for me too.
You can read more here:
https://forum.xda-developers.com/showthread.php?t=3530040
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Factory reset on stock? I'm running Pure nexus and elemental x

l2yangop said:
Factory reset on stock? I'm running Pure nexus and elemental x
Click to expand...
Click to collapse
yes, on stock rom. But I think it's not rom related.
Edit, you can try 7.1.2 beta, someone wrote there should a fix in it for that problem
Gesendet von meinem Pixel XL mit Tapatalk

Had this start the last couple of days at 30%. Very annoying. Completely stock as well.

I had this problem and attempted the trouble shooting tips from Google without success. I managed to get a replacement and not had any issues since.

firephoenixctk said:
I had this problem and attempted the trouble shooting tips from Google without success. I managed to get a replacement and not had any issues since.
Click to expand...
Click to collapse
Was the replacement directly from Google? Or from your service provider.
Apparently google made a fix to this issue in upcoming updates.

AznRico said:
Was the replacement directly from Google? Or from your service provider.
Apparently google made a fix to this issue in upcoming updates.
Click to expand...
Click to collapse
The replacement was directly from Google.

Coming up to 30% soon so I'll see if it does it again. Apparently it's still happening in 7.1.2 so god knows what update it's fixed in.

I have been reporting in the Pixel community and bug report. My phone was purchased in November from the Google Store, has never been rooted, and always use the OEM charger. My phone ran great until the February patch and then began encountering the abrupt power off around 30% battery.
Android OS, Android System, and Google Play Services are always the top battery consumers. Turning off various things has had no impact. I finally contacted Google and they are giving me the run around about a replacement. The Support staff did confirm they are aware and are replacing some phones but working on a fix, which implies it is software as noted above.
I am still pushing for a replacement and will see what happens.

jonathon1289 said:
I have been reporting in the Pixel community and bug report. My phone was purchased in November from the Google Store, has never been rooted, and always use the OEM charger. My phone ran great until the February patch and then began encountering the abrupt power off around 30% battery.
Android OS, Android System, and Google Play Services are always the top battery consumers. Turning off various things has had no impact. I finally contacted Google and they are giving me the run around about a replacement. The Support staff did confirm they are aware and are replacing some phones but working on a fix, which implies it is software as noted above.
I am still pushing for a replacement and will see what happens.
Click to expand...
Click to collapse
If its happening continuously this is probably something wrong with the battery. I have two Pixel XLs and had this happen once at around 35%! I left it powered off and recharged and this seemed to do the trick. Its clearly a software problem in that instance. So this could be two distinct issues IMO.

Google Pixel XL Lags sometimes

What's up guys.
I'm facing occasional lags on my Pixel. Every now and then the launcher and UI overall become unresponsive. It happens with the stock rom and LineageOS. I think it could be caused by an app or something but I haven't had any luck finding the culprit.
I tried disabling Digital Wellbeing, and even though it seems to work at first the lag comes back time after.
How are your Pixels standing up? Do you have any lag on yours?
I have a Verizon Pixel XL with the bootloader unlocked, do you think unlocking the bootloader may cause this issue?
Hope to heard from you, my experienced comrades.

I suppose a fresh flash is needed. However, as you said you are on LOS, so you have already done a fresh installation. In that case I am not sure. Maybe something hardware breaking as the device is old or something? I certainly wish not.

ithehappy said:
I suppose a fresh flash is needed. However, as you said you are on LOS, so you have already done a fresh installation. In that case I am not sure. Maybe something hardware breaking as the device is old or something? I certainly wish not.
Click to expand...
Click to collapse
Hmm, this is my 2nd Pixel. I recently purchased 2 for some friends, I also had a 32gb version before, all of them have the same issue. I just happen to think is caused by Android P.

liriolebron said:
Hmm, this is my 2nd Pixel. I recently purchased 2 for some friends, I also had a 32gb version before, all of them have the same issue. I just happen to think is caused by Android P.
Click to expand...
Click to collapse
I happen to have a stuck-for-few-seconds problem way back when the phone was new, on Nougat. It drove me crazy. Sold the first pixel for that reason alone and moved to the dark side. But then when I came back to another Marlin after couple of months I found that the problem was gone! Sometimes this type of problem happens on some specific Pixel devices I suppose, its not reported as it happens to a very few Pixels I guess! Either wait for an upcoming update to see whether it fixes stuffs, or maybe move to some other device. But I feel you, I remember quite well how that problem made me go total bonkers, probably you will find my threads on it as well. Good luck.

Wi-Fi and Bluetooth randomly won't turn on

I've had this phone for awhile now. Came from Taimen. S8+ before that..... Never had any issues until about 4 weeks ago. I thought it was the ROM I was on so I went Stock.....no good....then.....I tried Beta. Back to Stock no root/hacks. Keeps happening, intermittently. I'll come home from work, go to turn my Wi-Fi on and it won't turn on. Then I'll go to turn my Bluetooth on and it'll then just keep crashing. Sometimes it fixes with a reboot. Tonight it did not. I'm clueless. Never had an issue like this before that I couldn't fix myself. I've been on every ROM in the Forum trying to fix this last few weeks. No luck.
If at any time throughout the day I turn my Wi-Fi off I risk not being able to turn it back on. I did notice it seems to have a higher chance of working when mostly charged, but that may just be coincidence.
Any ideas?

most likely hardware issue, you're not the only one, contact pixel support.

Stock kernel? I have had the issue (no WiFi after kernel flash) with DU and EX for about the last month (worked fine before then). Have to flash my magisk_patched to revert the kernel to (in my case) Unicorn Blood.

sliding_billy said:
Stock kernel? I have had the issue (no WiFi after kernel flash) with DU and EX for about the last month (worked fine before then). Have to flash my magisk_patched to revert the kernel to (in my case) Unicorn Blood.
Click to expand...
Click to collapse
Yea. Stock kernel. I thought it was a DU issue when it started. That was the 1st thing I bailed off of to try and fix it. I remember being surprised I was having an issue with DU on my device, which I had never experienced. I bought the device, problem free, off of Swappa last year in April. I don't have any kind of Warranty protections or anything that I'm aware of.

djcrystals said:
Yea. Stock kernel. I thought it was a DU issue when it started. That was the 1st thing I bailed off of to try and fix it. I remember being surprised I was having an issue with DU on my device, which I had never experienced. I bought the device, problem free, off of Swappa last year in April. I don't have any kind of Warranty protections or anything that I'm aware of.
Click to expand...
Click to collapse
That is the only issue I have with DU, and since it is not the stock DU kernel it is hard to say where the compatibility issue lies. It started a few personal builds ago, and then before I installed another one I flashed EX even though I hadn't tried it on that build. It worked, and worked again on my next build. Then it failed on the next two, so I am just sticking with Unicorn Blood for the time being.
As for your issue, I do wonder if you don't still have some residual issues from your initial switch back to stock. After returning to stock, have you ben flashing OTA or doing flash-all? I would try a flash-all with -w intact. Change slots, and do it again. Then at least for a couple of times on and off your Wi-Fi leave the install base pretty lite to see if you have any conflicts without reinstalling a bunch of stuff. Sure sounds one of the image files (vendor or radio maybe) is bad.

sliding_billy said:
That is the only issue I have with DU, and since it is not the stock DU kernel it is hard to say where the compatibility issue lies. It started a few personal builds ago, and then before I installed another one I flashed EX even though I hadn't tried it on that build. It worked, and worked again on my next build. Then it failed on the next two, so I am just sticking with Unicorn Blood for the time being.
As for your issue, I do wonder if you don't still have some residual issues from your initial switch back to stock. After returning to stock, have you ben flashing OTA or doing flash-all? I would try a flash-all with -w intact. Change slots, and do it again. Then at least for a couple of times on and off your Wi-Fi leave the install base pretty lite to see if you have any conflicts without reinstalling a bunch of stuff. Sure sounds one of the image files (vendor or radio maybe) is bad.
Click to expand...
Click to collapse
So since DU, I've been on BETA.....clean....flashed to both slots....then to to July Stock 10, Clean both Slots.....Tried the two newest ROMs in the Forum.....now I'm on straight-up stock, clean flash-all, both slots, stock kernel.....My gut is telling me it's hardware but a part of me is in denial. My phone is still in Mint condition so it's hard for me to imagine it's broke but Uncle Google's been making some mistakes in the manufacturing of things lately so......I might be sh1t outta luck. I have unlimited data....it's the Bluetooth thing..... that's REALLY REALLY annoying.

I'd be in denial too. My last thing to check would be the Wi-Fi itself. Maybe some sort of compatibility issue with the phone of another issue. Do you have any other remembered networks that you get onto after being off Wi-Fi and returning to range? Same possibility with BT. Unfortunately, it is common with all BT connections to occasionally miss a reconnect.

sliding_billy said:
I'd be in denial too. My last thing to check would be the Wi-Fi itself. Maybe some sort of compatibility issue with the phone of another issue. Do you have any other remembered networks that you get onto after being off Wi-Fi and returning to range? Same possibility with BT. Unfortunately, it is common with all BT connections to occasionally miss a reconnect.
Click to expand...
Click to collapse
I'm doing some digging on this issue. It does appear to be a community wide issue as stated by the user a few posts up, unfortunately.
https://support.google.com/pixelphone/thread/32828289?hl=en

djcrystals said:
I'm doing some digging on this issue. It does appear to be a community wide issue as stated by the user a few posts up, unfortunately.
https://support.google.com/pixelphone/thread/32828289?hl=en
Click to expand...
Click to collapse
Good luck.

sliding_billy said:
Good luck.
Click to expand...
Click to collapse
Lololol.....damn. So WiFi and BT works when it's charge is 85% or more.....so I juts gotta keep it charged all the time. These devices have great batteries. Piece of cake.
Thanks for chiming in fellas. Appreciate it.

djcrystals said:
Lololol.....damn. So WiFi and BT works when it's charge is 85% or more.....so I juts gotta keep it charged all the time. These devices have great batteries. Piece of cake.
Thanks for chiming in fellas. Appreciate it.
Click to expand...
Click to collapse
I am at a loss for words except "glad it is repeatable."

sliding_billy said:
I am at a loss for words except "glad it is repeatable."
Click to expand...
Click to collapse
Now that is effing funny!
Sent from my Pixel 3 XL using Tapatalk