My mogul randomly stops charging when Im on the phone or on the internet for awhile (connection sharing via wifi) . After seeing a blurb in the manual about how the battery will stop charging I decided to try something crazy (stupid actually,so dont do this yourself of mosture could damage your phone). I sprayed some cold spray on the battery. The phone suddenly started charging again. After 10 minutes,it stopped again. More coldspray and it charged again. Its pretty clear that the battery is overheating. I have a replacement coming this week,hopefully it will be better. Is anyone else having this problem?
It appears on further examination that this happens mostly when Im running wifi with the power setting set for max range and sharing the internet connection. It helps if I open the keyboard (seems to improve cooling). It seems to run pretty cool when Im just sharing over the cable with no programs running. I have also noticed the problem when playing games or running programs while talking on the phone. I see alot of people looked but no one else reports having this problem. Ill post some further information when I get the new phone monday.
Ditto
I have two Moguls in the family. Both had the same intermittent symptoms. We came to the same conclusion. Turn off Wifi when not in use and close background apps when not in use. This seems to be the fix so far. Will a ROM update help this situation?
JeromeOz said:
I have two Moguls in the family. Both had the same intermittent symptoms. We came to the same conclusion. Turn off Wifi when not in use and close background apps when not in use. This seems to be the fix so far. Will a ROM update help this situation?
Click to expand...
Click to collapse
I doubt it,unless sprint or htc decides to cripple the performance to reduce power. =( Seems it may in fact be a defect in the design. It helps to open the keyboard when your running wifi. I also found it helps if you turn wifi power down to minimum. (optimize for battery vs performance/range) and turn off bluetooth,as well as close all running programs and turn the display off. If and when we have an overclocking util available it may also help to turn down the speed of the cpu,at least if it has enough speed not to impact the network throughput.
Where to begin....
I have had my wiz for about a year now (maybe longer) and everything was running fine. Nothing special installed really. I've Sim and CID unlocked, flashed to 1.1 and then flashed again to Mr. Frazzz's XDA Mobile 6 (awesome btw) and had been running that for quite some time with battery status as the only other thing I've really added.
One night I was out and managed to hit my touch screen on a table and it shattered. Things ran fine for a while (could still see considering the touch is seperate from the LCD) and managed to use it as a phone using shortcut keys. Then i started getting problems like slowing down etc and I figured it was partially due to the duress of a cracked touch screen making the phone think it was having a part of the screen pushed (or not there) so i finally had the screen, both the touch and lcd, replaced. Shortly after, I noticed the phone would freeze up randomly. (this is also about the time i switched from t-mobile to at&t prepaid) Sometimes it would do it 3 or 4 times a day and the only remedy is removing the battery. Sometimes it will go for over a week without any issues. Any ideas? Im ready to melt it.
Here's what I've done thus far with no results:
Reflashed to official t-mobile 2.26 and then flashed to Mr. Frazzz's WM6. I've re-installed battery status and then came across a thread stating that the latest version of which might be causing hangups....so i gimped it at first, using only settings I had known to work before with no issues and later uninstalled the whole thing. Still having the same problems.
I have the WM6 radio fix for cingular and 2.69.11 radio as well.
One thing I do notice is that, everytime i make a call and receive the system message stating what that call had cost me, it can cause weird things to happen if I was in the process of doing something else. Not sure that's part of the issue though considering the phone will just be sitting in my pocket when it does randomly freeze.
Is it possible that my mem card is just being jostled and causing issues? or that somehow the powerbutton is being adversely affected inside my pocket if the phone gets flipped upside down? Anyone and everyone's imput would be greatly appreciated, especially if Mr. Frazzz has any input. BTW, this has happened using both WM6r3 and r5 by Mr. Frazzz. I upgraded to r5 this last time i reinstalled WM6.
I'm guessing battery status is doing it. Same thing happended to me, did a hard reset, installed all my programs again excluding battery status and everything is fine.
Is there something else I can install that will overclock for me when the phone is active and kick down the speed when idle?
I also used battery status for the disable proxy thingie when wiFi is on.
Well...Overclocking is never safe and the manufacture of a cpu has clocked a cpu at a set speed. Why, because it is more stable. So anything past the stable speed will bound to be unstable. I overclock mine to 260 and still do not notice a boost so either you leave it at 195 and run smoothly or make it "faster" and have more issues. Your call.
Hello,
I am owner of HTC P3600 from last 12 months and i used custom roms too all was working fine and before 2 days i found that whenever i leave the HTC for few hours it hangs and when i press the standby button to wake it up nothing appears on the screen and i have to reset it to start it again.
Updates:
Ok i re flash the Hard SPL, Radio and Rom and until now (in last 24 hours) it don't hangs.....
Update 2: I think the battery is the problem as the battery time is decreased from 3 days to just 1 and a half day and it freeze now while charging....
Any solution? anyone experience the same problem?
Help please with your views...............
I have a similar problem. My HTC started crashing after a rom update. However, i think it is not crashing due to software...
Well, the software is more CPU demanding, so it heats more than before. Also, i started using backlight properties set to high (i need to set to low again), which again highly heats the PDA. Finally, when charging the battery tends to get very hot. All this put together causes the CPU to overheat and crashing.
At least, from my experience, when it crashes it is always very hot.
razpowa said:
I have a similar problem. My HTC started crashing after a rom update. However, i think it is not crashing due to software...
Well, the software is more CPU demanding, so it heats more than before. Also, i started using backlight properties set to high (i need to set to low again), which again highly heats the PDA. Finally, when charging the battery tends to get very hot. All this put together causes the CPU to overheat and crashing.
At least, from my experience, when it crashes it is always very hot.
Click to expand...
Click to collapse
Sounds like a radio rom problem. Try to reflash radio.
Thanks for the advice!
I will reflash the radio rom.
If it solves the problem i will update my post here so everyone else knows how to solve this kind of problem.
it helped ? reflashing the radio rom ?
lol you ****up your phone hahahahahahahha
No, it did not helped. Probably it is an hardware problem.
The pda was intensively used connected to the computer, because it was used for software developing.
I think it is broken, hehe.
DOWNGRADING TO LOLLIPOP:: --- B151 from B331
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
----
THX @skeppley
THX @Demian3112
----
Figured the above was an important surprise for some of you... OP still valid
Hello Everyone! Im new to the whole Honor 5x thing, coming from an m8 now, and before that a nexus 6, and before that a z3 then before that an S4 and before that an HTC Evo 4G LTE... Along with some minors, LG Risio, Moto E, S5...
Im just happy to say that so far I really enjoy this phone! Within the first few days of using it on Lolipop, i was getting 1d 15h type battery life which if youve looked at the phones ive mentioned so far... Really..really..wasnt what I was used to. A Day? For sure, the htc would be at 18% getting back on the charger... and it would die at 10%... with how long id had it. But... A Day was doable.
Ive been looking for a phone for SOOooOOO long now that had good enough battery to last a day at max brightness... Tweaking kernels, and Installing various ROMS (all of them per device)... Crack Flashing, as some would say. It just became a hobby... Ive noticed many weird things about the community, to those reading... let me list them now...
1. People all of the sudden(within the last 2 years?) prefer stock android over anything, regardless of what additional features are being added... Such as battery life improvements, Multitasking improvements, theme improvements, usability improvements... People like stock android... hmmm?
2. People want to be nexus so bad they will theme other UI's to death, just to make it look like stock, generic android... hmm..
3. Battery life, while a common complaint, seems to be indifferent to how frequently people update their phones.. (note: Marshmellow EMUI has a multi core battery bug, listed on XDA under mods..) or what ROM they choose (note the most popular rom being one with significantly worse battery life than stock)
4. Security improvements are completely unnecessary to the community (note the most popular rom being one that hardly supports the fingerprint sensor)
5. No matter how many bugs (even those listed in OP) people will always flock to the latest update of android. And then subtly complain to the developer about the bugs they already know about..
Such a strange mixture of people...to be sure.
However what ive noticed here, is a complete lack of readily available information, so i am hoping some of you might be able to assist me.
TL;DR
So I succeeded in downgrading my phone from MM to LP, as the battery life thing is a legit problem for me, as much as it may not be for other people. However the fingerprint sensor has been disabled, and no longer exists in the settings list... nor is it part of the startup. (confusing to be sure, you would think it would be there, and just FC when clicking on it were there to be a bug, or if the OS didnt detect the sensor or something... it should still be there yeah? If i understand how it works...
Also I cant seem to flash a B151 rom at all, being on B33...3? <- marshmellow... and im assuming at this point that means i wasnt supposed to be able to downgrade... (oops)
So i got TWRP installed (whats up with all the random errors twrp is throwing? Assuming thats normal...?) and am awaiting a BMarshmellow rom to finish... Which leads me to...
Where are the Emui ROMS? Unless its closed... but if this rom maker can do it... ?
and also, is the fix to the battery life on marshmello noticable to those of you who also care about battery life at all?
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Demian3112 said:
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Click to expand...
Click to collapse
Well there is a fix for it in the mods section that fixes battery. Finally got this phone back to functional lol..
Anyway, the fix for the moment anyway looks like it works, just has to be redone every reboot but really isn't that hard. After applying mincores mincpu 0 the big cores only light up when necessary. So far its helping a lot with battery life at least noticeably. Listented to music the whole way to work this morning and was still at 97% when I got there (I have an hour drive) , and that's using Youtube Music over 4g.. Not too shabby.
Yesterday I got to work doing the same thing on marshmallow at about 85-90 so it is doing something, and watching Kernel Auditor shows the big cores turning off when not in use. Worth checking out, applying the settings that are mentioned there don't do much im afraid, as I cant get them to stick through a reboot yet.
Currently writing an init.d script to make that happen every boot.
For now to my knowledge though it is working. Though I think lollipop was for sure better apps on screen off actually worked properly -_-; which im noticing more and more it doesn't anymore. Its more like a Doze control which is annoying because Doze is not near as good as stock lollipop control. I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know!
TL;DR
I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know! Id much rather downgrade than continue to fix marshmallow.
Though for those of you wondering, Viper|Atmos//Sony Beats the audio mod works perfectly on this phone
Just finished Init.d for Mincpus to fix the whole Big Little problem Super good stuff. Phone now booting in the big little mode you were talking about. super easy stuff.
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
skeppley said:
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
Click to expand...
Click to collapse
U need the firmware had same.. revert though dload
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
You should try CyanogenMod 13: excellent battery life, USB OTG and gyro working, much better CPU & RAM management...
FP reader is working, but you must upgrade to MM first (to update trust zone and radio firmwares).
igotlostintampa said:
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
Click to expand...
Click to collapse
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
Demian3112 said:
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Click to expand...
Click to collapse
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on your bed at night? And then never again?
As for CM13, im fairly apathetic to the topic... Not to be annoying, or rude, but ive heard the excellent battery life claim a million times about stock android, and while ive noticed its improvements over something like...say, Sense, or Touchwiz... Ive never seen it beat the z3's battery saving tool (before marshmallow), or as of the day I got this phone, Huaweis non-debloated lollipop.
Ive never seen a phone still be at 30-40%, at the end of work, the day after the day I charged. Until this phone. The Z3 would make it a little past lunch if I barely used it on day 2, but this phone played pokemon go for 2 hours the day I charged it, I spent the day listening to streaming music, browsing for various small things, watching a few youtube videos, a little navigation... And it had 40% when I left work the next day lol at 100% auto brightness. Id love to see some screen on vs idle drain comparisons between this phones CM13 and Stock, at that point, ill believe a battery claim.
It played pokemon go at 60fps and the game is a known battery/gpu hog (s7 plays slower than this phone, likely due to lack of gyroscope?)
other than some various laggy UI glitches, the phone was pretty much what id been looking for (I Prefer Miui over stock android, this phone is similar)
igotlostintampa said:
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on yuur bed at night? And then never again?
Click to expand...
Click to collapse
What buildnumber and Custom version/Cust do you have? Might be able to link you the right firmware.. twrp backup doesnt backup firmware that explains that you dont have a finger print, is the H from Honor at boot logo Red also?
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
skeppley said:
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
Click to expand...
Click to collapse
Your Reply has been added to the OP for those concerned with Downgrading. Figured it might be nice to stumble upon the directions that, after reading many posts throughout the various roms, many people might actually be looking for. Will likely try this tonight when I get home, battery is much better with the battery fix, but not as good as lolipop
Great.
Hope to help others that were stuck the same way
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Demian3112 said:
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Click to expand...
Click to collapse
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
igotlostintampa said:
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
Click to expand...
Click to collapse
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Demian3112 said:
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Click to expand...
Click to collapse
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
igotlostintampa said:
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
Click to expand...
Click to collapse
Im using Force doze app.. U can whitelist apps and as soon as you turnoff your screen it starts doze... You wont get notifications from apps you didnt whitelist until you turn it back on
Hello,
Forever pretty much I've been experiencing issues with my nexus 6p. I got it second hand but it seemed fine when I got it. Now, however, after a little inactivity, I find that unlock my phone will cause it to crash or reboot instantly. Its right after it unlocks that it does this. It's not every time but it happens a lot. It also sometimes happens a little bit after unlocking the phone after inactivity. Its like when it needs to drain more power from the battery than its used to it will just crash on me.
The only real thing that prevents this is keeping the phone on charge. Then again, it has happened before where it will still die on me. I've replaced pretty much everything on the phone with the exception of the charging board and the main board. So stuff like the screen and battery have been replaced (+more). Not sure what is causing it. I've had this issue before on stock android but at the moment I'm running the final version of Resurrection Remix on Nougat.
How would I go about troubleshooting this?
Nexus Radical said:
Hello,
Forever pretty much I've been experiencing issues with my nexus 6p. I got it second hand but it seemed fine when I got it. Now, however, after a little inactivity, I find that unlock my phone will cause it to crash or reboot instantly. Its right after it unlocks that it does this. It's not every time but it happens a lot. It also sometimes happens a little bit after unlocking the phone after inactivity. Its like when it needs to drain more power from the battery than its used to it will just crash on me.
The only real thing that prevents this is keeping the phone on charge. Then again, it has happened before where it will still die on me. I've replaced pretty much everything on the phone with the exception of the charging board and the main board. So stuff like the screen and battery have been replaced (+more). Not sure what is causing it. I've had this issue before on stock android but at the moment I'm running the final version of Resurrection Remix on Nougat.
How would I go about troubleshooting this?
Click to expand...
Click to collapse
Good observation. It is true that the reboot happens because of higher performance. It is caused by the four higher performance cores of the CPU starting to work. There is a fix.
What it does is to shutdown those four cores and you will be able to use only four of the lower performance but power efficient cores.
Follow the link :
https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279
Sorry for my late reply...
Thanks for the solution, but it seems like a very drastic trade-off for a fix. Is there nothing I can try to fix this like a system or boot.img patch that does something other than disable cores?
Either way, thank you.
Nexus Radical said:
Hello,
Forever pretty much I've been experiencing issues with my nexus 6p. I got it second hand but it seemed fine when I got it. Now, however, after a little inactivity, I find that unlock my phone will cause it to crash or reboot instantly. Its right after it unlocks that it does this. It's not every time but it happens a lot. It also sometimes happens a little bit after unlocking the phone after inactivity. Its like when it needs to drain more power from the battery than its used to it will just crash on me.
The only real thing that prevents this is keeping the phone on charge. Then again, it has happened before where it will still die on me. I've replaced pretty much everything on the phone with the exception of the charging board and the main board. So stuff like the screen and battery have been replaced (+more). Not sure what is causing it. I've had this issue before on stock android but at the moment I'm running the final version of Resurrection Remix on Nougat.
How would I go about troubleshooting this?
Click to expand...
Click to collapse
My 6p just recently encountered the same symptoms as yours. Only way to keep it from rebooting is keeping it plugged in. I've found something that has worked for me so far, maybe it will work for you too. It seems like disabling the Doze feature has fixed this problem for me. I'm not rooted, so I used adb command to do so. Here is a link for the instructions. Hope this helps you too. In the instructions,
it show you how to enable, but can be used to disable with one simple change.
https://windroidwiz.wordpress.com/2017/06/02/android-noroot-force-enable-doze-to-extend-battery-life-of-your-phone/