A Little History: :silly:
I have been running i9220ZCLP1...known bad kernel since whenever it was first available, April I think. Anyways, acquired that through flashing Rocketrom v5, according to the instructions provided at the time. Everything worked fine, other than contacts crashing and the wlan some times not enabling until reboot...common issues, as far as I've seen on these forums. One thing to note, is that unless the instructions at the time asked for a full wipe after flashing 5 (I'm almost certain they did not), then there has not been a full wipe performed while in this kernel.
The current issue:
The other day my phone froze on me...months after flashing and having used this kernel, waiting for something more solid to come out. After it froze...holding the power button turned it off, but the phone would not boot afterwards...to ics, to recovery, to download mode, nothing.
After some fiddling, I realized that it will charge and once it buzzes and the screen comes on showing a full battery, I can turn the phone on and it will boot...then freeze after getting past unlock screen. Or freeze and go black in download mode...didn't try recovery, wasn't interested in it at the time, but I'd imagine the same.
After removing the battery for a few days, then plugging it in til full charge notification, I was able to get it to boot again, where it froze at the boot screen, but went dark. After one more full charge...oddly, like a minute later, it booted to ICS fine and worked for 24 hours or so.
Now:
With a mind to flashing away from the bad kernel, I restarted the phone tonight from the menu in ics... it booted fine, so I left it plugged in to get a full charge and came back to a phone, screen still on, that shows same battery % as when I left it. And I'm back to where I started with this problem, powered off after holding power button a few seconds and now nothing.
Waiting for a full charge again, to see what happens...I'm guessing/hoping I'll be able to get it to boot again, with some more fiddling...
My question is whether this sounds like it's hardware (battery etc) or software (bad kernel etc) that is causing the problem.
If I can get it into download mode...plugged in, obviously, should I try OdinPC to a safe kernel?
Thoughts would be awesome. :fingers-crossed:
How about flashing stock GB via pc odin first and getting safe?
apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Sent from my GT-N7000 using xda premium
apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
OK, that's one vote for flash if I can get it running again. Thx, glad you read my post.
SpyderTracks said:
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Click to expand...
Click to collapse
Hmm, but how to get there...GB and all.
So now the vote is software. Any idea why this would happen much much later? No battery issues at all, just suddenly.
Maybe I'll buy a battery.
nebreprah said:
Hmm, but how to get there...GB and all.
Click to expand...
Click to collapse
A little searching would show you DrKentan's guide @ http://forum.xda-developers.com/showthread.php?t=1424997
I just transferred a movie on it two days ago. I have been on a road trip the past week and using a car adapter during that week (2.1 amp) and navigation. and navigation. Yesterday I was staying at someone else's house and kept losing signal in their house a lot and the battery went down fast. I plugged it into the way to charge like I have every night. When I went to bed I checked and it hadn't really charged at all. So I closed the location stuff that had destroyed the battery and went to bed. I woke up in the middle of the night to my phone vibrating from a reboot and it was ridiculously hot. It hadn't charged much. I used it for navigation on the way home and it charged in the car at a pretty normal speed. When I got home it won't connect to my computer.
I can't get adb to work, in the OS or recovery. Doesn't get recognized in the bootloader either. I tried multiple computers. It sometimes shows up as 'unknown device' and I uninstalled it once thinking i could re install it and it never showed up again.
I would go back to stock to try and fix it if I could, but I can't transfer anything to my phone.
studjuice said:
I just transferred a movie on it two days ago. I have been on a road trip the past week and using a car adapter during that week (2.1 amp) and navigation. and navigation. Yesterday I was staying at someone else's house and kept losing signal in their house a lot and the battery went down fast. I plugged it into the way to charge like I have every night. When I went to bed I checked and it hadn't really charged at all. So I closed the location stuff that had destroyed the battery and went to bed. I woke up in the middle of the night to my phone vibrating from a reboot and it was ridiculously hot. It hadn't charged much. I used it for navigation on the way home and it charged in the car at a pretty normal speed. When I got home it won't connect to my computer.
I can't get adb to work, in the OS or recovery. Doesn't get recognized in the bootloader either. I tried multiple computers. It sometimes shows up as 'unknown device' and I uninstalled it once thinking i could re install it and it never showed up again.
Click to expand...
Click to collapse
Same here. I am still searching for a workaround. I think it is a USB brick.
Download a ROM from XDA onto your phone and boot into recovery from the power button (assuming you have something like CM10.1 installed. I'm sure there are other apps that can boot into recovery also). Then you can wipe/flash from there and start fresh and see if the problem persists. No need for ADB here.
asawoszc said:
Download a ROM from XDA onto your phone and boot into recovery from the power button (assuming you have something like CM10.1 installed. I'm sure there are other apps that can boot into recovery also). Then you can wipe/flash from there and start fresh and see if the problem persists. No need for ADB here.
Click to expand...
Click to collapse
I installed almost every ROM and kernel there is, there's no connection via USB and the battery life is just terrible (around 6 hours until it's completely empty).
Read through some of your posts Ultraschorsch and I'm definitely in the same boat. I have airdroid to transfer files, but it's slow. I'm gonna try to go to the deodexed stock rom and kernel (but still rooted), and hope I get lucky.
I've already gone into recovery and wiped and reflashed in every combination I could think of and that hasn't helped. It's very frustrating.
I seems like it heated up so much that it destroyed the usb chip on it or something, and it wiped the info of what kind of device it's supposed to be or something. It was seriously so hot that I couldn't hold it in my hand (and that's with a case on it).
This is really a pain in the neck since we can't unroot it any more, so no RMA for us, I really hope there will be a solution to this problem. On the HTC Desire it was fixed through CWM but they need to find a workaround before. I am really a little hopeless...
I use dropbox to transfer files on my N4, I think it's faster than airdroid.
Ultraschorsch said:
This is really a pain in the neck since we can't unroot it any more, so no RMA for us, I really hope there will be a solution to this problem. On the HTC Desire it was fixed through CWM but they need to find a workaround before. I am really a little hopeless...
Click to expand...
Click to collapse
Can too! read here: http://forum.xda-developers.com/showpost.php?p=34749844&postcount=2
This is what I'm going to do and try to get an RMA tomorrow.
Also, I feel like the only solution would be to open the device. It seems like something actually broke when it overheated when this happened, so it needs to be replaced. whatever IT is.
Dude! If this works I really owe you! I'm going to try this tomorrow! Thanks in advance! :good:
If it works post back here so I (and future people with this problem) know!
So since the previous guide without usb has broken links here is what I did thanks to efrant's help:
Use BootUnlocker app from Play Market to LOCK the bootloader.
Flash this rom (odexed JOP40D - rooted)
https://docs.google.com/file/d/0B76WZ1xWiSuNSkN0Q01tdjhWdDA/edit
flash this boot image
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
flash this recovery
http://forum.xda-developers.com/showpost.php?p=36422317&postcount=207
Remove busybox and root following the steps posted in the above boot image post:
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
Hello,
Thanks for this tutorial, do i have to lock the bootloader first? I was thinking it was the last thing to do...
(I have to return the phone to google, so I need to restore everything)
studjuice said:
So since the previous guide without usb has broken links here is what I did thanks to efrant's help:
Use BootUnlocker app from Play Market to LOCK the bootloader.
Flash this rom (odexed JOP40D - rooted)
https://docs.google.com/file/d/0B76WZ1xWiSuNSkN0Q01tdjhWdDA/edit
flash this boot image
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
flash this recovery
http://forum.xda-developers.com/showpost.php?p=36422317&postcount=207
Remove busybox and root following the steps posted in the above boot image post:
http://forum.xda-developers.com/showpost.php?p=36534366&postcount=214
Click to expand...
Click to collapse
Hello all,
This is my first post in here and the reason why I'm here, is that I got the exact problem as mentioned in the opening post.
I've got my N4 last thursday, so 1 week ago. It worked like a charm and since I was busy finding out all the stuff and apps, I hadn't connect it to my PC before the weekend started.
Saturday in the morning I left for a trip and I navigated to the destination, using my car charger. The phone became extremely hot but it was the first time I tried the navigation, so I tought it was 'normal'.
That day and the days after (until today) my battery drained like hell, 6 hours standby with max. 45 minutes of active usage and it is empty.
So I started looking out for a custom ROM to solve it. But I never could connect it properly to my PC. Tried different PC's and different cables. Never a proper connection, only 'usb not recognized' or no connection at all!
Luckily I couldn't connect...because now it's still in the unlocked state as when I got it.
Today I'm going to call the company where I've bought it and ask for an RMA. Only problem is...they imported it from another country since the device isn't for sale in my country (Netherlands).
I'll keep you up to date.
any of you guys experience it? just long press the power button wouldn't help. I had to plug it to the charger and long pass the power button to reboot it. this is getting pretty frustrating... btw my n4 is 100% stock
jakkix said:
any of you guys experience it? just long press the power button wouldn't help. I had to plug it to the charger and long pass the power button to reboot it. this is getting pretty frustrating... btw my n4 is 100% stock
Click to expand...
Click to collapse
It has to be an app that`s causing that....
jakkix said:
any of you guys experience it? just long press the power button wouldn't help. I had to plug it to the charger and long pass the power button to reboot it. this is getting pretty frustrating... btw my n4 is 100% stock
Click to expand...
Click to collapse
Happens to me almost every time I connect it to my cars Bluetooth to listen to Pandora, and i'm on the latest CM 10.1 nightly.
SOD
I also happened yesterday and today, yesterday had cm 10.1 and in the evening I returned to stock 4.2.2 and happened again this morning. any suggestion?
My wife and I are both having this problem with our N4s. It's been happening on and off since about 2 weeks after we got them on January 7. I'm still debating whether or not to try an exchange under warranty. I'm not yet convinced that it would help, but it seems like it's only affecting a handful of us, so maybe it is hardware related?
Hmm hppnd with me too. Yst n today almost at same time. After playing with some apps or games.. Phone was hot..
Sent from my Nexus 4 using xda app-developers app
What rom/kernel if any are you guys on? I recently got the SOD. I am on the PA 3.1 and bundled kernel. Not sure what's causing it. My initial assumption was the themes in cm10. Now I think it's the launcher in question or lockscreen.
I am using Nova Launcher with slide/stock lockscreen. Nothing really has changed that I can tell within the last week. I uninstalled all my themes this morning to see if it was that causing the SOD.
Got the SOD this morning at work. Had to long press the power button a few times to boot it up. This time I uninstalled the Nova Launcher completely and reinstalled. Restored my widgets and seeing what that does later.
Happened twice. Once with unrooted stock, once with cm10.1. So i think this is an hw problem.
my battery screen looks exactly like this after SOD: https://code.google.com/p/android/issues/detail?id=35139
in my case long pressing to power button boots the device. no need to charger or button combo.
Forgot I posted here. I forgot to follow up. It turned out for me, there was a bad browser commit in the PA build in early March. I since reverted to a working nandroid and flashed the most recent rom. For others,I suggest to backup your apps and do a wipe. If that doesn't work, then maybe a factory reset?
i realized my SOD's occur at ~13:30 (1:30pm). Uninstalled a few apps(dash clock, rotation widget) and SOD's stopped. But today installed Onavo compression app than, bam!, SOD again(at 13:30 of course).
kpjimmy said:
Forgot I posted here. I forgot to follow up. It turned out for me, there was a bad browser commit in the PA build in early March. I since reverted to a working nandroid and flashed the most recent rom. For others,I suggest to backup your apps and do a wipe. If that doesn't work, then maybe a factory reset?
Click to expand...
Click to collapse
What do you mean bad browser commit?
Linsanity said:
What do you mean bad browser commit?
Click to expand...
Click to collapse
Basically the stock stuff was crashing the rom and causing the sleep of death. Have been fine ever since I reverted back to a working nandroid and dirty flashed the updated ones.
I am currently using the new version of pacman and it happened to me two nights ago.I reflashed and downloaded sleep of death fix app for charging. But I want to be 100% sure it won't happen again because I depend heavily on my nexus 4 for alarm. How can I be sure?
Sent from my Nexus 4 using xda premium
I just posted in the Android issue tracker this fix for nexus 4 SOD that worked for me :
It looks like there are different types of Nexus 4 freezing behaviour, all being lumped under the description: SOD.
My device (reliably) SODs after extendeded USB charging the very first time it sleeps; never happens while actually charging, just immediately upon disconnection; and it never happens in other circumstances.
However, I believe I now have a fix. If I only charge with a QI wireless charger OR if charging via USB, immediately sync with a QI charger upon disconnection, I never (it's been over a week now vs. every morning before) get a SOD.
Try this if you have the exact same problem I had. QI chargers are now available on eBay for less than £4 shipped.
NOTE: if you have a different sort of SOD issue, this may not work for you.
Hi Guys,
I have a big problem. I bought a Redmi 3s for a family member. It has the bloatware rom from Tinydeal so I installed the global developer version on it. I needed the dev version because my relative cannot speak english and that version has Hungarian support. So the phone seemingly works fine but in about every 2 day it just turns off. And it does not turn of properly because we need to push the power button for about 1 minute to turn on and last time we needed to push the power+volume button to turn on.
Just one additional note. I dont know if the phone is really turned off or it is just froze but it acts like it was turned off.
Does anyone has any idea what could be the problem? I hope it is not a hardware issue because sending back will not be quick...
I hope someone could help me. Thanks
mad.droid said:
Hi Guys,
I have a big problem. I bought a Redmi 3s for a family member. It has the bloatware rom from Tinydeal so I installed the global developer version on it. I needed the dev version because my relative cannot speak english and that version has Hungarian support. So the phone seemingly works fine but in about every 2 day it just turns off. And it does not turn of properly because we need to push the power button for about 1 minute to turn on and last time we needed to push the power+volume button to turn on.
Just one additional note. I dont know if the phone is really turned off or it is just froze but it acts like it was turned off.
Does anyone has any idea what could be the problem? I hope it is not a hardware issue because sending back will not be quick...
I hope someone could help me. Thanks
Click to expand...
Click to collapse
I have been facing this type of problem for almost two months. I was using xiaomi eu weekly rom. most of the time it shutdowns in pocket. I have searched in net about this problems and found no permanent solution. Later, I saw that someone told about proximity sensor issue. After deep sleep in whole night, it started the problems. So, he told to restart the phone after waking up in the morning. So, I did and it never shutdown in the whole day but did shutdown at night. I tried stable rom instead of dev rom. Seems like stable rom has less issue with it because i used stable rom more than 3 days and it never shutdowns during that period.
nafeesdipta said:
I have been facing this type of problem for almost two months. I was using xiaomi eu weekly rom. most of the time it shutdowns in pocket. I have searched in net about this problems and found no permanent solution. Later, I saw that someone told about proximity sensor issue. After deep sleep in whole night, it started the problems. So, he told to restart the phone after waking up in the morning. So, I did and it never shutdown in the whole day but did shutdown at night. I tried stable rom instead of dev rom. Seems like stable rom has less issue with it because i used stable rom more than 3 days and it never shutdowns during that period.
Click to expand...
Click to collapse
Hi. Thanks for your comment. Unfortunately I cannot user the global stable nor the eu rom as none of them the Hungarian language support my relative needs. I might try this restart everyday method...
mad.droid said:
Hi. Thanks for your comment. Unfortunately I cannot user the global stable nor the eu rom as none of them the Hungarian language support my relative needs. I might try this restart everyday method...
Click to expand...
Click to collapse
Restart or turn off your device for 2-3 minutes. And please tell us it works for you or not.
Looks like restart method every morning is not working. device shutdown mostly in pocket in beta eu & official rom. I used eu 8.0.5 stable rom for around 2-3 days without shutdown issue. now I flashed 8.0.6 eu stable rom and lets see how this thing go.
This happens only when I install any custom rom...the phone works fine with x720 5.8.018s version...anything apart from that device will shut down every 2-3 minutes ...very strange behaviour ...any one has any idea ?
any custom rom , android 6 or 7 , AOSP or stock based, it will boot fine and after initial setup , it will work for 3-4 minutes and then suddenly device shuts down. .. when i boot it up again , same thing happens, in one minute shuts down.
if i flash 5.8.018s stock rom , everything works fine....and it doesnt shut down...
After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?
marik1 said:
After device bugs, my phone finally was restored into x720 stock ROM (i have x720). On boot it worked below 1 minute and reboots. I had to do clean data. Also booting x720 ROM into x727 is not too good idea. Maybe you should try to do more wipes?
Click to expand...
Click to collapse
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.
Manan79 said:
I did all the wipes i could , cleaned all kinds of data... it was US version 5.8.018s originally and i tried to flash Omni ROm first , and other ROMS , all had same issues, so i thought going back to the stock US rom , but since US version of 018s is not available anywhere, i went to chinese version , and it works perfectly , no reboot/shutdown...... I have used number of phones and installed 100s of ROMS , i have never faced soemthing like this...i hve even used leeco pro 3 before, with all custom roms and no problems.
Click to expand...
Click to collapse
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP
Manan79 said:
Ok update...i downloaded x720 021S and 023S and updated using in build update option..(local update) , and it worked, 23S is working without any shut down...so i guess, it is problem only with roms flashed thru TWRP
Click to expand...
Click to collapse
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!
peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
That all happens with several ROMs - currently I'm on ResurrectionRemix 5.8.5. This is the most stable custom rom I have tested, but anyways the phone switches off in irregular periods. Sometimes the phone is about a day alive, sometimes only a few hours, sometimes below an hour. When I'm playing HQ games I think the phones switches off much faster, but not sure.
I'm also not sure - I do not have used the stock rom really long after I get this phone (was CN 5.8.018s I think) - but my feeling is, that the phone was definetely more stable with the stock rom.
Now after finding this thread, I will give the stock rom another try. Would you be so kind as to describe the process of going to the stock 023S a bit more in detail? First flashing the 5.9.021S for the x720 ROM throught TWRP and after that using the build in update option (rename file to update.zip into root folder)?
Thanks!
Click to expand...
Click to collapse
On my equipment too !!
Andresdsr said:
On my equipment too !!
Click to expand...
Click to collapse
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium
mchlbenner said:
You do not flash a 21s update twrp that may brick you.
You have to go stock and flash with stock recovery.
Their threads already on this.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...
Andresdsr said:
it was the same with the ROM that came from the factory.
I experienced 21s and 23s beta Tars, 23s original Chinese...
Click to expand...
Click to collapse
Does anyone completely solved the shutting down issue on x720? I remember the same issue with the stock rom when i was getting the phone (5.8.018). but this rom could have been a shop rom, cant remember.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.
Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
For me it seems that the issue happens more often whenever the phone uses more performance. Playing HQ games let the phone shut down after about 1-3min. doing nothing on the phone, it remains for about a day. Weird behaviour... will try to flash the stock recovery via fastboot and then a stock rom (no shop rom). hopefully it will improve the behaviour or even better solving the issue.
Click to expand...
Click to collapse
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.
sk8223 said:
Sounds like a hardware issue. As for me, I have a couple of screen issues--I usually have my LeEco Pro3 Elite connected to a charger, and I sometimes don't use it for long stretches of time (say, 8 hours) because I have another phone as well. Once in a while, during those times the screen refuses to turn on. Sometimes the fingerprint scanner wakes it up, other times I have to straight up reboot the phone using the power button (I have to keep it pressed for two whole minutes for it to wake up the phone). Pretty annoying, dunno why it's happening. Could be a loose screen cable.
Now, if your phone is shutting down every few minutes no matter what, it could be a battery issue. I say this because I had a similar issue with an old iPod Color from 2005. The iPod would shut off every few minutes even when plugged into a charger. I changed the battery and it stopped shutting down.
Hopefully it's not a motherboard issue because replacing a phone's motherboard is never easy.
I don't think gameplay should affect the phone negatively at all. Especially a phone with a Snapdragon 821, a 14nm processor with efficient cores, for crying out loud. I play Fate Grand Order, a pretty intense 2D online game with 1080p graphics for 5 hours straight on my LeEco Pro3 Elite (Snapdragon 820) without it heating up at all.
Again, seems like a hardware issue because no phone with a Snapdragon 821 or 820 should be doing that. Especially while gaming.
Click to expand...
Click to collapse
Thanks for the information.
Could be possible... If I'm shaking the phone like a cocktail-mixer, it feels something loose inside it and this could be the battery of course which could be not fixed correctly. But I am sure, that this issue has also something to do what is happening on the phone currently. Sometimes I am going to bed and the phone does not move for 8hrs, it simply lays on the table. In the morning, it is shutted down. Need to hold the power button for about 10sec to restart the phone (usually hold 2sec to power on). Sometimes (not really often) it warm-starts automatically.
I think this could be also a memory issue or internal storage. Yesterday I was playing a game (Bowling by Jason Belmonte) and after 3min, the phone hung up, display remains on, no reaction on pressing the hardware buttons, waiting 5min... nothing happens. So I pressed the power button 10sec, phone seems to reboot normally, but it take a bit more time in my oppinion. Now after entering the pin, some phone configurations were resetted to default, but not all. Playing this came, it sometimes happened, that the phone switches off (with one vibration). Rebooting with a 10sec press and it runs again normally. This time phone hung up and some configurations were resetted to default. WTF?
Today I have played Hmmsim 2. Phone hung up again, pressing the power button 10sec, phone begins to reboot, but rebooting never finished (waiting for about 1-2hrs). Long Press power button (10sec) to try to reboot again - same behaviour, never ending ROM loading screen. Wiped to factory via TWRP and the phone reboots again, but all configurations lost, like freshly installed rom. OK, whatever, using the google backup for apps and so on... when installing the apps in the background, the phone reboots about 3-4 times, app installations not finished. Cancelled and shutting the phone down to TWRP, where I am now...
What I will try to say is, that whenever the storage or memory is used to much or something like that, the phone begins with that behaviour.
And now I am thining about what to try next. I think I will try to flash the stock recovery via TOOL ALL IN ONE then flashing a stock rom like 5.9.023S.
I am still not sure of a hardware issue...
peed_neslo said:
I am still not sure of a hardware issue...
Click to expand...
Click to collapse
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.
sk8223 said:
The easiest way to tell is if the issues were occurring before you flashed TWRP. Were they? This is why you always wait a couple of months before modding your device. Otherwise you'll be stuck in a loop of doubts. By this I mean you'll be convinced that the issue has to do with your custom ROM or kernel rather than your device's hardware, but you have no way of knowing for sure because you never used the phone enough on stock firmware.
I was like you... my unmodified Zenfone 3 had a screen flicker issue and a headphone jack issue that I was convinced was a Nougat problem. I upgraded from Marshmallow to Nougat immediately after getting the phone. After a lot of research and posting threads on the Zenfone forums, I realized I had a hardware issue on my hands. The screen had to be replaced for the flickering to stop, and the headphone jack had been gimped to 0.3v by ASUS for some reason. I quickly sold the phone and got my LeEco.
Here's a thread I made on XDA about my screen flickering issue. It's a hardware issue: https://forum.xda-developers.com/zenfone-3/help/ze552kl-screen-flickering-lowest-t3660643
I've learned some important things from that experience: it's easy for your brain to trick you into thinking you've got an easy-to-solve software issue on your hands, when in reality you've got a hardware issue. You need to start making arrangements for a replacement device and get video evidence of your problems to show to the seller ASAP. Because that behaviour isn't normal. Now I hope you do have a software issue on your hands that the stock firmware will solve, but who knows. Be prepared for anything.
Click to expand...
Click to collapse
Thank you very much!
I am sure that the phone was doing the same on stock rom, but maybe fewer times. I have flashed a stock based rom now (Turbos mini 5.9.023s) and the issue still exists, but now the phone reboots normally more often than going into edl mode (emergency mode). I have found an old thread here on XDA and the issues described there sounds nearly the same. Finally the user in this thread also had hardware issue.
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.
peed_neslo said:
I believe also in a hardware issue, but I am still not sure. If I am looking to other threads regarding similar problems, there is always some regularity in the behaviour or the reported issues. In my case these rebootings (usual reboot or reboot to EDL mode) are definetely very unregular. On the TURBO Rom, these reboots happen definetely more often when the display is off and the phone sleeps. On the TURBO Rom, playing games seems to be helping lasting the phone a bit longer, the completely differnce to ResurrectionRemix Rom, where the phone was lasting longer when doing preferabely nothing. The issues are so inconsistant and this is making it hard to believe, that this is a hardware issue. Why the hell is the phone behaving different on every ROM - if it's a hardware issue, the occurred problems should have some regularity.
As I didn't have an OTA update option on the stock rom, I'd found out that this could be a "shop rom" (5.8.018), which is not the best choice nor for the first month(s).
Click to expand...
Click to collapse
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
I'm from Germany and I do not really want to return the phone to china or east asia for repairing (bought at banggood). This could take a very very long time. Changing to a new one could be also difficult because there are hardly any more devices out on the market and I need to return it for the change too.
But I am slowly at my wit's end and before these issues are making me more and more crazy, I will accept a problem with the hardware.
Click to expand...
Click to collapse
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Admittedly I'm not sure at all if this issue was already present after starting the phone for the first time. One of the first things I have done during the initial setup wizard was using the integrated data transfer app by LeEco (scanning a QR code with the old Xperia Z, downloading app to transfer data to the x720). This app establishes a Wifi direct connection between both phones to transfer the data like apps and other stuff. This transfer process takes at least 6-7 hours and during that process I am sure that the phone was not rebooting a single time. Maybe a specific app or background process of an app causes this irregular rebootings. I have not testet this. I have installed the most common of my apps also using different custom ROMs later.
On the current ROM (Turbos mini 5.19.023s) I have now looked into the last_kmsg.log file severel times after the phone was hard-rebooting (not to emergency mode - the phone is switching down to emergence mode really rarely since I have flashed the stock based ROM) to debug for a kernel problem and the power off reason seems to be ""Triggered from PS_HOLD (PS_HOLD/MSM controlled shutdown)". In the log file I could also find some "kernel panic" entries. So I have a little gleam of hope that the issue is not a hardware problem. I have to test a bit more with the stock recovery/ROMto gain a better knowledge of the issue. I think I will post this into the ROM topic to ask a developer.
sk8223 said:
If your issues were occurring from the moment you got the phone, you know it's a hardware problem. Your seller sent you a defective phone and you should at least try fighting for a partial refund. If you paid through PayPal, open a dispute. If you paid with a credit card, ask for a chargeback. Now, the shop you bought it from might ban you for initiating a chargeback, but it's probably worth it. Or you could just cut your losses and move on. Maybe donate your phone to a dev who wants to try something crazy. :good:
Oh snap, it's a Banggood phone? I bought my x722 from Banggood. No glaring issues other than the screen one so far, but this does worry me for the future. How long have you had it?
This is the problem with Chinaphones. They're cheap, they've got good specs, but you can't guarantee quality. Especially with now close-to-defunct brands like LeEco. If you're still okay with Chinaphones, get a Xiaomi next. Probably the most reliable Chinaphone brand out there, next to Huawei. And try to buy from an official source. I heard The Solution Shop in Europe sells Xiaomi phones for cheap (?). And always remember to record your unboxings and document all issues from now on.
Click to expand...
Click to collapse
Finally - I got it working without any problems now!
Happily it seems to be not a hardware issue. I have flashed the Grossoshop ROM and Recovery via a provided .bat file. This .bat file has flashed the recovery first via fastboot, then the ROM via fastboot. This Grossoshop ROM was based on 5.8.018s I think. Then I have updated TWRP Recovery to the latest version via TWRP itself (flashed the new image). Then I have flashed Mauro's 2.2 (which is based on 5.9.023s) and it is running great! Super performance, no extrem battery drain, no reboots, all is working (except the chinese design downloads as I cannot create a Leeco account from Germany). But now I'm satisfied. :good::laugh:
peed_neslo said:
Usefull information, thank you very much.
Nearly the same problem here: My X720 is only rebooting sometimes, but more often switching off directly (vibrates one time and switches off). While the phone is in that status, the battery is discharging. I can only reboot the phone by holding the power button for about 10sec or to TWRP. Two times I was rebooting the phone and some (not all) settings were restored to default - reflashed the rom... Another time rebooting the phone it hangs in the booting display, did not get it booted completely again - reflashed the rom.... Very strange behaviour and don't know why this happens.
But for about the last month, the phone is only switching off and I can reboot and use it for an unspecific time.
Thanks!
Click to expand...
Click to collapse
My x720 has done the same to me a couple of times now, Vibrates once and turns off and I have to hold the power button for a few seconds longer to turn it back on again which is odd.
The battery was charged over 50% % 70% at the times it happened and I wasn't even using the phone, It was just sat on the table in front of me.
I didn't have any problems at all until a few days ago when it first shut down.
I'm using Oreo - AICP 13.1 from here - https://forum.xda-developers.com/le-pro3/development/rom-aicp-13-0-pro3-aka-zl1-x727-x720-t3698058
The problem now is I don't know where to start troubleshooting When I get time I am planning on a clean wipe and fresh install of AICP again to see if that solves the problem
When using this ROM does your phone heat up a lot.
Sent from my LEX727 using xda premium
Did you manage to fix the problem somehow?