Develop Bugs

Overheating?

I seem to be having an issue with my phone overheating and rebooting. It seems to happen consistently when using navigation or when playing games (I'm hooked on Gem Miner). Always at an inopportune time. To me this seems like a result of bad hardware or something but is it possible that rooting and installing ROMs like CM7 or Kingdom Stock Sense?
I bought my phone at Best Buy and ended up getting the warranty, so assuming I can revert the phone back to stock, I should be able to get this covered under warranty. Right?

My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible

Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.

TheWhiteBandito said:
My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible
Click to expand...
Click to collapse
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...

k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Hot enough that it's shutting down. I couldn't tell ya specifically.

k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Its higher than 119F. Mine hit 122F the other day and didn't reboot, unless the safety shut off didn't kick in on mine. Don't think it is much higher than that though before it does.

I had heard it shuts down at 119 but my phone hasn't ever gotten that hot. I've only managed to get it up to about 114, that was multitasking and charging, overclocked to 1113.

When it reboots, do you get 5 vibrations and then the indicator flashes green until you pull the battery? If so, you are starting to have serious problems.
This thread helped me recover my Incredible..
http://forum.xda-developers.com/showthread.php?t=982454

I had mine at 120F the other day loading a new rom and no shut off
Sent from my Incredible using XDA Premium App

Mine gets hot when using wireless tether.

jetsaredim said:
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...
Click to expand...
Click to collapse
I'm leaning toward a hardware issue. The reason I say that is because I'm using CM7.0.3 and Chad's Incredikernal and when I use navigation I also connect my car charger and have never had a heat issue nor any reboots. I drove from SC to FL back in Feb and had navigation running the whole time.

Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?

jetsaredim said:
Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?
Click to expand...
Click to collapse
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.

fLaWx said:
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.
Click to expand...
Click to collapse
I assume you're not completely an expert in this matter, but let me see if I get this right... I have to go back to having CWM on my phone so I can apply the S-ON zip and then re-run the stock recovery to get back to complete 100% stock. Sound right? I wouldn't even consider it if I didn't think there was a slight chance that I'd get flagged on the warranty review for having S-OFF set. I don't want them to have any reason to deny my getting a new phone.

Hi - long time lurker, barely ever post, but I'm gonna chime in here.
My DInc also reboots, and it is warm to the touch when it does happen. Don't know how hot though sry. I've been rooted since November, but haven't installed a Custom Rom, just removed bloat, and added some other useful tools. The biggest change I've made was changing the fonts. I don't over/under clock either (it runs just fine for me). My reboots seem to be increasing in number. At first it would be once a month, then a few times a week, and now a couple times a day.
Sometimes, my phone will reboot just once, and then continue to work. Sometimes 2-3x in a row, and then continue to work or not. Sometimes, it just vibrates 5x quickly, and then is locked (LED flashes), and the only way to recover is to pull the battery and start over.
Seems to happen MOSTLY around certain times of day - 4:30-6pm when I'm on my way home from work (no, not using my phone, but it happens anyway), and around lunchtime (again, not using it, or if I am it's barely). Other times it happens too - but really randomly. I'm ruling out different apps that might be triggering it, but don't think that's the issue.
QUESTION - if it is heat related, and the phone is supposed to go into shut-down mode at 119*, but seems to be different temps for everybody, could it be the thermostat? Could it be registering a false temp reading and think it needs to shut down? Has anyone explored this?
I'm not an engineer, or even a programmer, but I like to play one on TV. Thx

Oh - I forgot to add this:
There have been times when it would reboot, and I've placed my phone and battery (removed from phone) on the vents of an airconditioner, or even sitting on a frozen ice pack (the kind for a cooler) and it would still happen afterwards. To the touch, my phone would be cold, not freezing, but cold. Seriously lower temp than what it was when it was very warm to the touch...

I'm definitely with you on the first scenario. I just brought it to my local Best Buy where I bought it (with warranty) and they sent it off and gave me a loaner DInc to use till mine's repaired. They said, if they can't repair it, they'll give me a DInc2 as a replacement since the Dinc1 is "backordered" (aka not being carried).

jetsaredim - I was able to get a replacement DInc sent to me overnight (free!). My first replacement had a faulty USB port, so I couldn't charge my phone. I have 'another' DInc being sent to me now. Other than the faulty USB port, I haven't had any overheating issues so far (knock on wood).
First phone manufactured in June 2010
First replacement phone, manufactured in April 2010, and remanufactured June 2011 (via ##7764726)

I just got my replacement Incredible today. I just tested my original phone again by watching 15 minutes of video on youtube and BANG!!!!!!!!!! It rebooted as usual. Screen and battery get very warm. The reboots seem to happen when watching videos online or offline, playing games for 10 to 15 minutes, browsing the web for 15 to 20 minutes, using Google Maps with or without charging at the same time, and charging and talking on the phone at the same time. Well, I'm sending back the original and hoping that the replacement doesn't fail me. Glad that I swapped it just before the manufacturer warranty was up.

Have had the Dinc since week one. 100% stock - have not rooted (yet) and stock battery - in the past month it has 'overheated" and rebooted twice. Never happened before. Both times while using navigation and charging. Could it simply be the battery? It's not holding a charge like it used to too which also makes me wonder about the battery.

Do we has unlocked bootloader?

After root came out for G4 i never heard that unlocked bootloader came out. Im looking through the threads, but most are old or got off topic, so to keep it simple
Is there unlocked bootloader for VZ G4 yet?

No

We don't even have a fully working phone..People with 12a has broken WiFi notifications and people without it have touch screen issues.

^^ So much this. It's depressing.

Read somewhere that a lot of first batch phones have faulty circuit boards, that's what is causing the issues. I'm still on 10b and wanted to hold out for the bootloader unlock, but it doesn't look like it's gonna happen anytime soon. Might bite the bullet and try to do a warranty replacement through LG so I get a new phone vs a certified pre owned from Verizon...
Sent from my VS986 using Tapatalk

Not everybody with pre 12a have touchscreen issues. I'm on 11a and I have absolutely no touchscreen issues. It's smooth, fast, and responsive.

chubbrock said:
Read somewhere that a lot of first batch phones have faulty circuit boards, that's what is causing the issues. I'm still on 10b and wanted to hold out for the bootloader unlock, but it doesn't look like it's gonna happen anytime soon. Might bite the bullet and try to do a warranty replacement through LG so I get a new phone vs a certified pre owned from Verizon...
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Please let me know how that turns out. It's so pathetic that I can't even use the phone. I need to get it replaced/fixed or ...... the wall is where it might end up with.

Spookymyo said:
Not everybody with pre 12a have touchscreen issues. I'm on 11a and I have absolutely no touchscreen issues. It's smooth, fast, and responsive.
Click to expand...
Click to collapse
X2 mine is perfectly fine, and is also on 11a rooted and with a lot of stuff freezed / uninstalled.

This made me laugh pretty good man

Thank you for your answer, straight to the point mate.

CyberManiaK said:
X2 mine is perfectly fine, and is also on 11a rooted and with a lot of stuff freezed / uninstalled.
Click to expand...
Click to collapse
X's three, mine seems to be doing fine but when I download an app from xposed and reboot it, it takes hours to load when I reboot. I don't know if I can attribute that toward this issue.

1NOLASaints1 said:
X's three, mine seems to be doing fine but when I download an app from xposed and reboot it, it takes hours to load when I reboot. I don't know if I can attribute that toward this issue.
Click to expand...
Click to collapse
How are you rebooting -- selecting reboot from the power menu? My reboot lag was resolved once I stopped selecting reboot and just shut down the phone entirely then used the power button to turn it back on. No idea why that worked, but it worked for someone else here at XDA too, so it's worth a shot.

How to bypass unlocked bootloader 30 second wait on the bootup screen?

Seriously, google. Is it really necessary to make us wait 30 seconds if we have an unlocked bootloader?
How do I stop this nonsense without locking the bootloader again?

sorry but you cant.....
what i dont understand is why it needs to beep in such a high pitch sound each time.....

Yea it's pretty annoying, it's a Chromebook thing. My HP Pavilion would do it too but at least you could speed it up and continue by pressing spacebar, Cheep5k8 said that we could drop it down to 2 seconds BUT you have to remove the screen and flip the dev switch in order to do so.
Sent from my Pixel C using Tapatalk

bummer. the tablet boots super fast otherwise.
if only i were a jedi. i'd flip that switch by force.

Still the same answer to this question?
On older devices I know folks smarter than me figured out a way to remove it. I no longer remember those methods.

That beep makes me jump every time!

m+a+r+k said:
That beep makes me jump every time!
Click to expand...
Click to collapse
Scares the **** out of our dogs. They go and hide if I forget to cover the speakers each reboot!

WTH, I swear to dog I just went around and replaced all the damned batteries in the smoke detectors in the house because of that chirp. It's been driving me nuts!
It's a sad statement that I was hearing it so often at random times, just shows how unstable it is [emoji53]

There must be some hack to avoid this by replacing bootloader or some other partition, doesn't it?

Is there still no solution to the dreaded 30 second delay and beep? It's the only thing preventing this tablet from being 100% awesome with LineageOS.

It's annoying but as I only reset about once a month when a new update comes out I can live with it.

Not tested at the moment, but I was wondering...
If it's that annonying (and I find it too) it should be possible to relock the bootloader while keeping root. Of course, it implies that when you will need to unlock it again, it will wipe your device (no problem if like me, you install each rom from scratch)

DarkAdrien said:
Not tested at the moment, but I was wondering...
If it's that annonying (and I find it too) it should be possible to relock the bootloader while keeping root. Of course, it implies that when you will need to unlock it again, it will wipe your device (no problem if like me, you install each rom from scratch)
Click to expand...
Click to collapse
If I recall correctly, this bricks the device. May be wrong though, would not recommend at all regardless.

Oh sorry, forgot to give my feedback here. I tested relocking the bootloader : unfortunately it wipes your tablet. So at the moment you cannot disable the 30s wait while keeping root and/or unlocked bootloader

DarkAdrien said:
Oh sorry, forgot to give my feedback here. I tested relocking the bootloader : unfortunately it wipes your tablet. So at the moment you cannot disable the 30s wait while keeping root and/or unlocked bootloader
Click to expand...
Click to collapse
What if you're not bothered about losing root? I flashed PixelExperience/Pie 9.0 by followmsi, which is great. All I wanted is pie, I'm not bothered about root. If I re-lock the bootloader, I don't mind losing root or wiping the device; I'm just worried it will brick the tablet! Anyone know what may happen?

downgrading to kitkat

hi guys. I wanted to downgrade back to kitkat because of the constant rebooting problem and I stumbled upon this warning message. is this true? please peruse the attachment.

You can downgrade back. Ive done it before. But why downgrade when MM is coming? Have you tried disconnecting and reconnecting battery? Or even resoldiering it?

Downgrading to KitKat works just fine. I've done it many times. I wouldn't worry too much about MM coming out soon. I mean, we've only had ONE article saying it's coming soon, but it still technically isn't an official source. A reliable one, but not official. KitKat is easier to deal with than Lollipop though in regards to Xposed and viper4android. The UI looks, and IS, better for the OLED display.

thank you friends. what was the deal with that screenshot of that warning anyway? is it outdated info?

NightShadow02 said:
thank you friends. what was the deal with that screenshot of that warning anyway? is it outdated info?
Click to expand...
Click to collapse
I think it's more of a warning that something could go wrong if you don't know what you're doing. That's the first I've seen any kind of message like that though.
Sent from my SM-T700 using Tapatalk

noxarcana said:
I think it's more of a warning that something could go wrong if you don't know what you're doing. That's the first I've seen any kind of message like that though.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
cool cool. got my tab s back to stock kit kat. oh so stable. what ROM are you currently running on your device noxarcana?

NightShadow02 said:
cool cool. got my tab s back to stock kit kat. oh so stable. what ROM are you currently running on your device noxarcana?
Click to expand...
Click to collapse
I'm on Lollipop right now waiting for Marshmallow. If MM isn't released by the end of August, I'll be going back to KitKat. KitKat is very stable in all ways! For me, viper4android works without issue, Xposed doesn't require you to be deodexed, and it just looks better.
Sent from my SM-T700 using Tapatalk

noxarcana said:
I'm on Lollipop right now waiting for Marshmallow. If MM isn't released by the end of August, I'll be going back to KitKat. KitKat is very stable in all ways! For me, viper4android works without issue, Xposed doesn't require you to be deodexed, and it just looks better.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
is lollipop giving you the random flickering screen then reboot problem? because i'm a sufferer of said problem ever since I updated.

NightShadow02 said:
is lollipop giving you the random flickering screen then reboot problem? because i'm a sufferer of said problem ever since I updated.
Click to expand...
Click to collapse
Only when my battery drops below 50% and it becomes more and more frequent the lower it gets. It becomes unbearable around 30%. Flickers with a green light, random reboots, and false power offs. The false power offs are when the screen goes black but the device is still on and reacts to volume buttons and home button. Pushing the power button would seem to do nothing but it's actually locking the device but you wouldn't know that because the device seems to be off. Pushing the power button again unlocks the device and the screen comes back on but will turn off again randomly within a few minutes.
I'm on my second Tab S right now. The display on my first got a hairline fracture in the digitizer so the screen had this temporary, at first, green/yellow tint which could be temporarily "fixed" by holding the corners and bending inward. Not the best fix as you can imagine. Everything else on it worked just fine but it was going to cost the same price as a new one just to fix the screen so I gave it to a friend and bought myself a new one. I had for just over a year.
Sent from my SM-T700 using Tapatalk

noxarcana said:
Only when my battery drops below 50% and it becomes more and more frequent the lower it gets. It becomes unbearable around 30%. Flickers with a green light, random reboots, and false power offs. The false power offs are when the screen goes black but the device is still on and reacts to volume buttons and home button. Pushing the power button would seem to do nothing but it's actually locking the device but you wouldn't know that because the device seems to be off. Pushing the power button again unlocks the device and the screen comes back on but will turn off again randomly within a few minutes.
I'm on my second Tab S right now. The display on my first got a hairline fracture in the digitizer so the screen had this temporary, at first, green/yellow tint which could be temporarily "fixed" by holding the corners and bending inward. Not the best fix as you can imagine. Everything else on it worked just fine but it was going to cost the same price as a new one just to fix the screen so I gave it to a friend and bought myself a new one. I had for just over a year.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
yes same symptoms! i can't use a tablet which goes crazy when below 50%. I tried an AOSP rom once which limited the CPU to about 400mhz and the flickering and shutdowns are minimized. but. what can you do with such a slowpokey device these days haha. when I was still on stock lollipop, enabling power saving mode helped a bit as well.
people keep saying it is a battery connector issue or something but I've replaced the battery and it still does the same thing. doesn't seem to happen on kitkat so far. so I hope the rumored marshmallow update will get that issue fixed. and I'm surprised samsung didn't develop a patch for this widely reported shutting down issue.
does your second tab S work like a charm on lollipop though? perhaps it's a different batch with a different motherboard or something.

I never believed it to be the battery connector. I'll admit I'm not electrical engineer or anything like that, but I've been playing around with devices since I was 5 by taking them apart and a battery connector just doesn't make sense to me. I think it's a OS and device (a certain batch or something) issue. None of these issues were on KitKat. My first Tab S had NONE of these issues whatsoever! Only this current Tab has shown these issues. It "works like a charm"....as long as I stay above 50%.
Sent from my SM-T700 using Tapatalk

noxarcana said:
Downgrading to KitKat works just fine. I've done it many times. I wouldn't worry too much about MM coming out soon. I mean, we've only had ONE article saying it's coming soon, but it still technically isn't an official source. A reliable one, but not official. KitKat is easier to deal with than Lollipop though in regards to Xposed and viper4android. The UI looks, and IS, better for the OLED display.
Click to expand...
Click to collapse
Do you have to unlock the bootloader to install any custom/stock room?
i'm kinda new with this

IsaacXDA said:
Do you have to unlock the bootloader to install any custom/stock room?
i'm kinda new with this
Click to expand...
Click to collapse
I know nothing of bootloaders. I have a WiFi only device and don't have to deal with a bootloader.

No Charge Without Re-Boot [Un-Solved - It's Baaack]

I've noticed recently (~3 times in last couple weeks), my Pixel XL will not start charging unless I re-boot, from 25%-35% charge. I've swapped chargers (Nexus 5X vs Pixel XL) and USB-C cables without success.
A simple reboot fixes the issue, but is a bit of a pain.
Pixel XL 128
7.1.1, Jan Update
Rooted
TWRP
Verizon SIM
Anyone else seeing this oddity? Any suggestions to correct??
Edit: 1/15 Replacement Device received, unlocked & rooted. The issue returns after just one day! Reboot needed to re-charge.

I have this same problem! I have had it since getting the pixel with root, custom kernel. Thought it was the kernel but the device swears it has nothing to do with it.
I haven't had TWRP very long but it happens still. It's random, and a reboot always fixes.
I wish I knew the cause, but too annoying to run full stock unrooted to test lol.

I've had this issue as well even with stock. Completely random. I've since flashed Pure Nexus since it's release and haven't had the issue anymore.

Happened again this morning. Gah, no overnight charge.

Chatting with Brian at Google.
He jumped to "Sending a Replacement Phone" after about 2 mins of very basic discussion. Seems odd, but whatever. Seemed a pretty quick surrender...
I did inquire if this was a known issue. He said, No, probably just a rare scenario.
I'll probably run stock for a while on the new phone to see if this recurs. Then I'll return to root and monitor.

markp99 said:
Chatting with Brian at Google.
He jumped to "Sending a Replacement Phone" after about 2 mins of very basic discussion. Seems odd, but whatever. Seemed a pretty quick surrender...
I did inquire if this was a known issue. He said, No, probably just a rare scenario.
I'll probably run stock for a while on the new phone to see if this recurs. Then I'll return to root and monitor.
Click to expand...
Click to collapse
Interesting. I don't feel like getting it replaced, because I have a dbrand skin on it that would not transfer.
JagXK8 said:
I've had this issue as well even with stock. Completely random. I've since flashed Pure Nexus since it's release and haven't had the issue anymore.
Click to expand...
Click to collapse
Hmm, how long have you been running on PureNexus? Sounds promising.

xocomaox said:
Interesting. I don't feel like getting it replaced, because I have a dbrand skin on it that would not transfer.
Hmm, how long have you been running on PureNexus? Sounds promising.
Click to expand...
Click to collapse
Since 1/6. I've actually had 3 problems with my pixel. Randomly not charging, volume buttons not working and times call quality. But so far haven't had any issues after flashing pure nexus. I did chat with support but wasn't a quick surrender.
Sent from my Pixel XL using Tapatalk

JagXK8 said:
Since 1/6. I've actually had 3 problems with my pixel. Randomly not charging, volume buttons not working and times call quality. But so far haven't had any issues after flashing pure nexus. I did chat with support but wasn't a quick surrender.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I am almost certain it is a software issue. I am going to flash Dirty Unicorns soon I think which will hopefully fix the problem.

xocomaox said:
I am almost certain it is a software issue. I am going to flash Dirty Unicorns soon I think which will hopefully fix the problem.
Click to expand...
Click to collapse
I am inclined to agree its a software issue, which is why I was surprised "Brian" offered a hardware replacement so quickly. I did very recently do a Factory Reset to address my "Double-Tap-To-Wake" issue (reset fixed it), so maybe this was his queue to not try yet another reset...

markp99 said:
I am inclined to agree its a software issue, which is why I was surprised "Brian" offered a hardware replacement so quickly. I did very recently do a Factory Reset to address my "Double-Tap-To-Wake" issue (reset fixed it), so maybe this was his queue to not try yet another reset...
Click to expand...
Click to collapse
I think Google offering to replace units quickly isn't terribly surprising.
The cost for them to replace a unit is very low. They are probably shipping out a refurb, and are only paying for shipping costs. The unit that will be returned is surely fixable with ease and can be re-deployed to another user. This is a super low cost way of providing what appears to be excellent customer service to the end-user. Apple and other companies have done this for years and have been very successful.
EDIT: I am now on DU so I will let this thread know if I have any more charging issues.

Woke up this morning to charge my phone, didn't start charging. Rebooted to fix. Made a call and the call quality was like I was in a poor reception area. Oh well still happens at random. Think I'm ready for a replacement.
Sent from my Pixel XL using Tapatalk

JagXK8 said:
Woke up this morning to charge my phone, didn't start charging. Rebooted to fix. Made a call and the call quality was like I was in a poor reception area. Oh well still happens at random. Think I'm ready for a replacement.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Well it happened to me last night on DU. I think I might be able to use this as a free replacement card down the road to get a refreshed unit. It's crazy that without touching the phone I can reboot it and it will work.

My replacement devices arrived last night - Pixel XL, 128GB, Black.
They are probably shipping out a refurb...
Click to expand...
Click to collapse
Especially with all the shipping delays, I fully expected this replacement would have been a refurb. By all appearances this replacement is new or at least a pristine refurb. Packaging and accessories were clearly new (that part is easy), but the phone's back, corners, edges and glass are all 100% flawless.
The phone appears to be playing well. Ran it on Daydream for 2:27 last night to watch a NextVR basketball game - no overheating, possibly sightly less drift than my old device.
Edit: My plan to hold-off rooting failed - I am unlocked & rooted, but kept the stock recovery vs TWRP (in anticipation of FlashFire).

Replacement Device received, unlocked & rooted. The issue returns after just one day! Reboot needed to re-charge. Blargh!
I should have used a little more discipline and not rooted right away - for science.
I am doubtful I'll revert to stock to test some more, but who knows.

Odd. Given that not everyone who is rooted has this issue perhaps sharing a list of mods/root apps and other apps that you installed on the new device could help to shed some light on where things to sour.

I seem to have had this issue ever since I rooted and installed ElementalX kernel. So it would appear that either I have a bad device, it's root, it's the elex kernel, or both root+kernel causes this.
I've modded emoji's but only once or twice, definitely had the issue on a fresh DU and PureNexus install with only root and kernel.
I am still questioning the charger, but not much because I also use the USB-a to USB-c cable connected to a cheap 1a chsrger at work with the same problem. So very unlikely it is the cable.

xocomaox said:
I seem to have had this issue ever since I rooted and installed ElementalX kernel. So it would appear that either I have a bad device, it's root, it's the elex kernel, or both root+kernel causes this.
I've modded emoji's but only once or twice, definitely had the issue on a fresh DU and PureNexus install with only root and kernel.
I am still questioning the charger, but not much because I also use the USB-a to USB-c cable connected to a cheap 1a chsrger at work with the same problem. So very unlikely it is the cable.
Click to expand...
Click to collapse
For me, still a most basic configuration:
- rooted (supersu 2.79-sr2)
- stock recovery
- stock kernel
- stock launcher
- no roms
At the moment, the only root-apps that possibly raise a flag as not fully stock. Nothing odd in this list as far as I can see:
- adaway (modified hosts file)
- titanium
- flashfire (not in use)
- rootchecker
- quickreboot
- tasker & autolocation
Next instance of no-charge, I'll try the brand new charger & cable from the replacement packaging.

markp99 said:
For me, still a most basic configuration:
- rooted (supersu 2.79-sr2)
- stock recovery
- stock kernel
- stock launcher
- no roms
At the moment, the only root-apps that possibly raise a flag as not fully stock. Nothing odd in this list as far as I can see:
- adaway (modified hosts file)
- titanium
- flashfire (not in use)
- rootchecker
- quickreboot
- tasker & autolocation
Next instance of no-charge, I'll try the brand new charger & cable from the replacement packaging.
Click to expand...
Click to collapse
It's strange if it is root causing it, why has nobody else mentioned anything? I'm glad you get it on the stock kernel, so that rules that out.

xocomaox said:
It's strange if it is root causing it, why has nobody else mentioned anything? I'm glad you get it on the stock kernel, so that rules that out.
Click to expand...
Click to collapse
I'm not rooted and my bootloader is not unlocked and still have this issue from time to time. So pretty sure it has nothing to do with root. Trying to use some usb-c headphones once (they didn't work) did trigger it immediately. It's likely going to be related to the usb-c port in some way, possibly a firmware issue?

I also randomly encounter this problem. I already returned 1 pixel xl that quit charging, completely stock, a reboot did not fix it. On my second device and still occurs occasionally seems like it takes a week or so and a reboot fixes, so not sure what the problem is. Still completely stock.