Related
Hey guys
recently i bought a Bluetooth speaker and connected it to my A3 (300FU), but now when i check the battery stats to see what is eating my battery it only shows Bluetooth (not even screen, wifi etc) [ see screenshots]
i deleted dumpstat/logcat and also wiped cache partition but it didn't help.... is there an obvious solution or am i missing something here?
*running stock Marshmellow ROM
Any help would be appreciated
i think a few users have it confirmed, Bluetooth seems to be a major drain in MM for A3FU.
i can only advise to update to a newer build. what build are you btw? do a screenshot of About in Settings
i didn't have a problem until recently, when i paired my device with the bluetooth speaker.
should i reset network settings?
I've attached the screenshot.
all users who reported BT issues came from first BT pairing, just like you. and they were all on PH3.
It's a rom bug that you can only hope they notice and fix, and then it's up to you to try the new builds and see if there is any change.
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Bffn45 said:
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Click to expand...
Click to collapse
Quite sure bluetooth is being the idiot here.
I do not own this device but I had this issue on my other A series device and it's because of the Nearby Device Scanning in Other Connection Settings.
This feature is included after updating to Mashmallow and it causes your Bluetooth to be always ON if the feature is ON(By default its ON so go and turn it off).
BTW, how did you get the battery graph on Mashmallow? Didn't Samsung removed it since Lollipop? I can't access it on my device, my sister's J7 and my mom's S7 edge
conanDO98 said:
I do not own this device but I had this issue on my other A series device and it's because of the Nearby Device Scanning in Other Connection Settings.
This feature is included after updating to Mashmallow and it causes your Bluetooth to be always ON if the feature is ON(By default its ON so go and turn it off).
BTW, how did you get the battery graph on Mashmallow? Didn't Samsung removed it since Lollipop? I can't access it on my device, my sister's J7 and my mom's S7 edge
Click to expand...
Click to collapse
Nearby device scanning is turned to off, should i reset network settings? maybe that way it will correct the readings
For the Battery stats --> Settings -->at the System section search for Battery--> Battery usage, or maybe just use S finder
I've got the same issue. Untill I switch Bluetooth on, normal battery stats, as soon as I do, everything is reported as Bluetooth - no screen use, now Android System use. "Nearby Device scanning " option seems to have no effect.
I also had this issue when I upgraded to MM (build CPI1)... even tried factory reset, but problem persisted.
I think it's a bug in the Samsung ROM, no way to get rid of it without a software upgrade.
Same "bug" with my A300FU.
Tried everything...
Installed earlier firmware (rom) with odin (in which I did not have the exaggerated Bluetooth usage)
Installed latest firmware again
Full wipe
Install latest firmware
After installing each rim I have the high Bluetooth usage from the start without installing any app
My colleague with identical A300FU did have the same with the previous 6.0.1 rom, bit after OTA update it dissappeared on his device
So it has to do something with my setup....
According to the battery gauge Bluetooth is using approx 4mAh PER SECOND
Also explored the option to modify the power profile.xml in the framework-res.apk but to no avail (keep getting bootloop)
*frustrated*
Anyone an idea?
Flashing cm12 or cm13 and then reverting to stock 6.0.1 is also not a solution to this issue......
My Wife's Galaxy A5 (2015) also has this bug. All 6.0 firmwares - even latest from January. So stupid - I can't belive that they can't see this bug. There is no battery drain - only bad statistics. But its very anoying because You cant check how long screen was used etc. Scaning of near devices is disabled too - didnt help. Dammed.
Have You find any solution?
I never looked at that screen before, but I recently noticed this too and it freaked me out at first. After testing it tho, I was gonna post and ask other peoples' experience, but then I found this thread.
What I get is that initially my batterystats are recorded normally, but then when i turn on bluetooth, even if it's for 1 second, all stats disappear and bluetooth appears in that list with what appears to be a huge (and impossible) drain.
Bffn45 said:
But is this a bug only in the battery stats or is bluetooth actually draining the battery even if its turned off ?
Click to expand...
Click to collapse
PlutoDelic said:
Quite sure bluetooth is being the idiot here.
Click to expand...
Click to collapse
I normally have bluetooth on, and I don't actually notice my battery draining any faster than when it's off. Also, if the computed battery usage on this was accurate on my phone, I would run out of power in a matter of seconds. So it's definately a bug in the battery stats.
aerogenes said:
After installing each rim I have the high Bluetooth usage from the start without installing any app
My colleague with identical A300FU did have the same with the previous 6.0.1 rom, bit after OTA update it dissappeared on his device
So it has to do something with my setup....
Click to expand...
Click to collapse
I beg to differ! I flashed lollypop and the problem disappears then, but it's there on both marshmallow builds for our country, even when starting fresh after a data wipe.
Which roms have you tried? And what rom is your colleague on after the OTA that fixed it? Buildnumbers would really help
For me: U1CPH3 and S1CPL1 both have this issue
It seems, for me at least, that after the December OTA security update the bug dissappear and i am now getting normal battery readings.
Bffn45 said:
It seems, for me at least, that after the December OTA security update the bug dissappear and i am now getting normal battery readings.
Click to expand...
Click to collapse
Al right, thanks! Latest rom/update for my country is from december too, but i still have it.
So i'll try downloading a jan 2017 rom for a different country and see what happens
Update:
Installed the S1CQA2 firmware, which should be the latest, and the bug is still there. Just with less unbelievable numbers and it takes a little while longer for it to make all other stats disappear.
Update2:
Looked into the powerprofiles.xml too, but the marshmallow one (which has this issue) is identical to the lollipop one (that doesn't have this issue). Also all there is to edit in there is the amperage usage for actual A2DP, but according to this https://source.android.com/devices/tech/power/values.html a lot of battery usage is just pushed to the batterystats service by the controller.
Now wondering what files are associated to the bluetooth controller. Simply replacing the bluetooth.apk from a different rom where this is working does not solve it either.
After some more digging, and succesfully porting the S5 bluetooth files to my phone, i found out that the samsung S5 suffers from this issue as well andthus the issue was still not fixed
Also, judging from other posts in other forums it appears the Note 4 has it too.
Therefore I think it is a touchwiz bug, and I am clueless on what to try anymore.
This is my third post in this thread in a row but editing my previous posts here might make the new info go unnoticed...
So this is just a heads up that the italian A300FU1CQC2 firmware has finally fixed this bug for me! :victory:
I have had bluetooth on (idle) all day now and it doesn't show up in battery stats at all.
great effort mate, really love it when people monitor the release stream .
Carpe-Dimi said:
So this is just a heads up that the italian A300FU1CQC2 firmware has finally fixed this bug for me! :victory:
I have had bluetooth on (idle) all day now and it doesn't show up in battery stats at all.
Click to expand...
Click to collapse
Thanks for the heads up... I've just flashed the update, and I can confirm that also for me this new firmware solves the BT issue. :good:
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
steveindajeep said:
I thought it might be a driver issue by searching for "moto x pure display driver". My phone looks exactly like the one pictured in the first link in the search. Android authority is a pretty decent site and after reading through the comments section it does seem common enough.
Im going to try to reflash via fastboot as you suggested but im afraid i think youre right as it doesnt show on a screenshot. Its worth a try i suppose. Just dont have the $ for a phone right now.
thanks for the reply btw.
Click to expand...
Click to collapse
I haven't heard of any display issues in this regard since the X's initial release, and that was fixed pretty quickly with an OTA. None sense then... The "display driver" is built into the kernel, and if this was an issue I'm sure we would have heard more about it.
Sorry to hear, but this sure sounds like a hardware problem.
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
_arxn said:
Okay so my issue was similar just that instead of the bottom half, it was happening for the full screen and it seems to have fixed itself after having the screen on full brightness overnight. It was a mistake actually. It all started when I was replacing my old battery cus it got so weak. I had no heat gun or anything or that sort around so I figured I could heat the phone up internally. Started running clash royale as it got the phone hotter whenever I played and changed the sleep period to 30 minutes because those are the things that make my phone heat up. So I did that. Replaced the battery yada yada, it works perfectly now. So I forgot to set the sleep period back and went to bed with the screen on. Somehow it just continued to stay on all the way till morning (or I believe so). Woke up to the phone hot, screen brightness on full. It was under my pillow too so the heat just kept building up. Needles to say, when I realised I closed the apps running, turned the brightness all the way down and locked the screen. I put it aside to cool off because I had just gotten up, wasn't in the mood. But seeing as I can't keep my hands always from my phone I picked it up like 3 minutes later. I'm writing this an hour after and the brightness is on the lowest setting. No ghosting, no lines being drawn up anywhere, no lagging, nothing. It's currently working like brand new. I should mention that the phone was plugged in the whole time. And mobile network was on. WiFi was off.
I'll keep monitoring the issue and I'll post and changes if any. Hopefully there won't be any.
Click to expand...
Click to collapse
Later on the same day: So I fell asleep for about 4 hours with brightness on low. (damn I sleep a lot) woke up and the issue returned. But I had the brightness on full for a while and it seems to have resolved again when I put it back to low brightness.
That's all so far. Still monitoring
I'm glad someone else noticed that when you slide the brightness bar it effects the way this display issue behaves. I was starting to think I was alone on this. Now this is just my experience on my phone of course. It seems to be around 2/3 way to full bright that it starts to flash the white lines on and off and then 3/4 + it is pretty much acts as it should, they go away! So I took a screenshot as acejavelin suggested and the screenshot was clear. So this would explain why updates don't seem to change anything since it does seem to be a certain batch with bad hardware. Can this hardware be solder changed? Guess I will keep an eye out for sale of xpure with busted digitizer/good lcd to test and possible mb swap.
Yes 1575 definitely has a display driver issue, i've noticed this too. I don't think there is a way to fix this, unless it would be fixed in Nougat.
But how sure are you that it's a driver issue and not hardware? That's why I'm waiting for nougat. If it doesn't fix the issue then I'm just going to have to retire the phone.
Sorry bro
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Mine has the same issues now and then but a restart fixes it always.
Bill720 said:
If you're encountering a display problem in aftermarket roms and even on the bootloader and recovery menus, then it's most definitely not a "display driver" issue. As @acejavelin already pointed out, it's not a known software problem unless you're running the shipped Lollipop software release.
Click to expand...
Click to collapse
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
But the Op!
onupirat said:
that's the point, problems are only in the stock rom. I've tried many custom roms and none of them have this issue, but unfortunately they have many other issues so i have to use the stock version.
Click to expand...
Click to collapse
steveindajeep said:
I've already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
Click to expand...
Click to collapse
Oh. I just read this and assumed that we were all talking about the same thing. In your case, I'd perform some experimentation to make absolute certain that your findings aren't just coincidence.
Question re: hardware vs software
acejavelin said:
What makes you think this is a driver issue? If you do a screen shot when this is occuring does it look normal or messed up? If it is a software issue, the screen shot will look messed up, if it looks normal then the hardware is at fault. That would give you about a 80% accurate answer.
There are no "known issues" with the display drivers in the Moto X S/P, so if it's software, best would be to reflash stock via fastboot and retest. If the issue recurs it is likely hardware.
Click to expand...
Click to collapse
Hi ~ just read your msg, and tried your "screenshot test." The grayish area on my screen (which over time, comes & goes - haven't detected a pattern as to why/when) DOES show up on the screenshot.
If I understand correctly, that would tend to indicate that I am experiencing a software issue? (Not hardware)
I did do a Factory Data Reset, and am experiencing the same issue. I had not added any apps for an extended period of time, prior to this gray-area occuring. I did, however, drop the phone. I don't recall for certain, but I don't think the problem occurred immediately, rather, it started very shortly thereafter (1 -3 days).
And I am waiting for delivery of a battery, since that's shot (runs down very quickly, & shuts down with anywhere from 30% - 60%+ battery level).
Any suggestions for resolving this? I hope this post makes sense... And thank you for any ideas or assistance you can offer!
Hello everybody. I have the same problem.
And who ever changed the display? Do you want to understand this is the problem of the display, motherboard or drivers?
I think it's a software problem, a hardware will not stop glitches when you flash a different software until and unless you fix it. In my experience, after my phone break because of downgrade to marshmallow stock firmware, and with an unlock bootloader i update my phone using OTA update, suddenly it stop working. blank screen and i tried try to recovery it with xt1575 IMG file to boot it again, mine it was xt1572(India) then I start facing a lot of problem, glitches, can go back to marshmallow stock firmware so and so... Now I'm trying to find a solution !!!! Custom ROM, CM13 work better and no glitches till now... I will Report soon
Moto x style/pure display problem
steveindajeep said:
My phone seems to have developed a display driver issue where part of the screen ghosts images, turns 50 shades of gray, etc. Apparently this is a common problem at one time one if one searches "fix moto x pure display driver" on google but cant find a fix for it.
Does anyone know how to fix this? Did motorola address this issue with a fix? Perhaps reflash the driver? Ive already tried wiping the phone and flashing to Nougat ([7.1.2] AICP for clark). Neither made a difference. It shows in twrp as well btw.
running out of ideas here. Hate to have to retire the old girl.
any ideas on a replacement for verizon networks...i need an sd card slot for additional storage and of course the phone needs to be rootable. Maybe a moto G?
Click to expand...
Click to collapse
I think maybe due to brightness control problem, could be the software or hardware problem
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?
My Moto G4 suddenly restarts at any time if I am using the phone, most of the time it happens when I receive a call.
I have tried various ROMS, even stock firmware, still facing the same issue.
I have the XT1643.
Anyone else facing such an issue?
[email protected] said:
My Moto G4 suddenly restarts at any time if I am using the phone, most of the time it happens when I receive a call.
I have tried various ROMS, even stock firmware, still facing the same issue.
I have the XT1643.
Anyone else facing such an issue?
Click to expand...
Click to collapse
Which baseband do you have? Do you tried without 3rd party apps on stock rom too?
strongst said:
Which baseband do you have? Do you tried without 3rd party apps on stock rom too?
Click to expand...
Click to collapse
I have the 'M8952_70030.25.03.62R' baseband.
I have tried without any third party apps installed, facing the same issue.
If in case it was a baseband issue, I would be interested in flashing the latest baseband.
Would you be kind enough to point me the right direction?
[email protected] said:
My Moto G4 suddenly restarts at any time if I am using the phone, most of the time it happens when I receive a call.
I have tried various ROMS, even stock firmware, still facing the same issue.
I have the XT1643.
Anyone else facing such an issue?
Click to expand...
Click to collapse
Same here.
I tried every rom. The problem still presists.
The problem is noticeable when battery is below 70 and while receiving calls.
Device XT1643
[email protected] said:
I have the 'M8952_70030.25.03.62R' baseband.
I have tried without any third party apps installed, facing the same issue.
If in case it was a baseband issue, I would be interested in flashing the latest baseband.
Would you be kind enough to point me the right direction?
Click to expand...
Click to collapse
You do have latest baseband version.
This issue happens when phone gets heats up and battery stops responding (power cut) to lower the heat radiated.
If im right according to your telling ill suggest you to take the phone to service centre. It is more a hardware problem then the roms itself.
How do i know?
Simple, experience.
My friends g4 plus suffers from same issue(not on calls but heat issue) and service centre guy told us this reason.
Well i may be wrong as information is incomplete.
Fill in this :
Battery temperature.
Background activities.
Mostly with calls and other than that (if happened).
You told all/most roms, may you name some with build date and what/how issue existed in all of then.
Also battery supply voltage(use my device app).
Try the same issue like this :
Plug in your phone charge it and play heavy games.
If device reboots you got your solution, if not then recreate the scenario and tell us exactly what happened.
Saksham Thapaliya said:
Same here.
I tried every rom. The problem still presists.
The problem is noticeable when battery is below 70 and while receiving calls.
Device XT1643
Click to expand...
Click to collapse
DgnrtnX said:
You do have latest baseband version.
This issue happens when phone gets heats up and battery stops responding (power cut) to lower the heat radiated.
If im right according to your telling ill suggest you to take the phone to service centre. It is more a hardware problem then the roms itself.
How do i know?
Simple, experience.
My friends g4 plus suffers from same issue(not on calls but heat issue) and service centre guy told us this reason.
Well i may be wrong as information is incomplete.
Fill in this :
Battery temperature.
Background activities.
Mostly with calls and other than that (if happened).
You told all/most roms, may you name some with build date and what/how issue existed in all of then.
Also battery supply voltage(use my device app).
Try the same issue like this :
Plug in your phone charge it and play heavy games.
If device reboots you got your solution, if not then recreate the scenario and tell us exactly what happened.
Click to expand...
Click to collapse
Thank you for the suggestion, I guess I will take it to the service centre, seems more of a hardware issue.
Anyways, my phone is still in the warranty period, but I have flashed it.
Will they service it for free if I flash stock firmware and relock the bootloader?
[email protected] said:
Thank you for the suggestion, I guess I will take it to the service centre, seems more of a hardware issue.
Anyways, my phone is still in the warranty period, but I have flashed it.
Will they service it for free if I flash stock firmware and relock the bootloader?
Click to expand...
Click to collapse
No,
Once you unlock your bootloader the warranty is compromised.
Saksham Thapaliya said:
No,
Once you unlock your bootloader the warranty is compromised.
Click to expand...
Click to collapse
Well, will they still service my phone if I pay them?
[email protected] said:
Well, will they still service my phone if I pay them?
Click to expand...
Click to collapse
Yes, they will take your phone and money from your pocket and will repair it.
If you can now, try to flash the stock rom with build no. NPJS25.93-14-8.
I also had similar issue(it shut down on receiving notifications) with build no. NPJS25.93-14-4 (even on custom roms I flashed over it) which got fixed in the NPJS25.93-14-8 update.
Now again the issue reappeared on NPJS25.93-14-10 version.
Hence I flashed the complete NPJS25.93-14-8 using fastboot and now it's working fine(both on stock and custom roms). Maybe it had something to do with modem version or bootloader(unlikely).
Tell me if it worked.
saranshkmr.in said:
If you can now, try to flash the stock rom with build no. NPJS25.93-14-8.
I also had similar issue(it shut down on receiving notifications) with build no. NPJS25.93-14-4 (even on custom roms I flashed over it) which got fixed in the NPJS25.93-14-8 update.
Now again the issue reappeared on NPJS25.93-14-10 version.
Hence I flashed the complete NPJS25.93-14-8 using fastboot and now it's working fine(both on stock and custom roms). Maybe it had something to do with modem version or bootloader(unlikely).
Tell me if it worked.
Click to expand...
Click to collapse
My phone shuts down while playing something through speakers( like while playing music, ringtones etc.).
It doesn't powet on itself but i have to turn on the device by myself. Is it a hardware issue?
Also my camera flash isn't working fine. While capturing only yellow led blinks. But while using torch both the led's are workung fine. What the crap this device is??
ADITYA_KUMAR said:
My phone shuts down while playing something through speakers( like while playing music, ringtones etc.).
It doesn't powet on itself but i have to turn on the device by myself. Is it a hardware issue?
Also my camera flash isn't working fine. While capturing only yellow led blinks. But while using torch both the led's are workung fine. What the crap this device is
Click to expand...
Click to collapse
If you haven't tried clean flash, do that. Flash the NPJS25.93-14-8 version.
Else it highly seems a Hardware issue.
And yes, this device is a crap. Heating issue, lag when recording video, random shutdowns, etc. But development work for this device is great.
I also have my earphone jack not working which apparently required to change the whole motherboard to fix as claimed by service center guy. And unlocked bootloader void my warranty so it's been this way for long time.
I had the same problem and I did everything. change rom, from kernel I did everything possible with software based speech and searching in forums I found that it is a battery failure, check if you still have the warranty. otherwise you need to buy a new battery only this way the problem is solved
I hope you solve your problem
I just solved it today and it goes great, greetings:good:
saranshkmr.in said:
If you haven't tried clean flash, do that. Flash the NPJS25.93-14-8 version.
Else it highly seems a Hardware issue.
And yes, this device is a crap. Heating issue, lag when recording video, random shutdowns, etc. But development work for this device is great.
I also have my earphone jack not working which apparently required to change the whole motherboard to fix as claimed by service center guy. And unlocked bootloader void my warranty so it's been this way for long time.
Click to expand...
Click to collapse
When i was on 14-8v , i started having these problems. Therefore i flashed lineage os 14.1. but problems are still.
While playing music it's not necessary that my device is going to be turned off, but sometimes it suddenly turns off by itself.
And my both leds are working fine while using torch, but at the time of capturing shots the white led does not blink, only yellow led blink. If anyone knows plzz let me know the solution.
Same here
I am using latest Android update provided by Moto. No root and nothing else..
Just got this today and it's great besides being a bit smaller than my g6 and because of front camera design only being technically 5.5in screen for most apps especially games.
However since I have had it, it has randomly rebooted itself twice for no real apparent reason. Is this a known issue or something anyone else has experienced? I want to try to get a bit more information on it before contacting the eBay seller. It is a refurbished.
I have never experienced a random reboot. You might want to try factory resetting your phone and then setting it up with the fresh start option instead of restoring from a Google cloud backup. Was your phone on Nougat or Oreo when you received it? Were there any major software updates?
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Nickvanexel said:
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Click to expand...
Click to collapse
Must be rogue app, had mine 3 months and never had a glitch or reboot.
Sent from my PH-1 using Tapatalk
If you are still having the random reboots you might want to boot your phone into safe mode to verify that a third party app isn't causing the problem. Since your phone was refurbished it's also possible that it was damaged by the previous owner or returned for the same issue you are experiencing. I did read that some early PH-1 buyers had to return their phones because of hardware issues like overheating.
Just did it again while using chrome. Just froze up for a few seconds and restarted. Doesn't seem to be overheating and the first time it happened before I installed anything I think. Guess I'll try a reset and go from there.
Factory reset twice now. No 3rd party apps installed. Updated all apps on Google play. The default phone apps.
Now the phone is freezing and rebooting itself constantly. Out of control. I am in safe mode right now and hasn't frozen yet. I don't know what the hell is going on.
Would love to be able to fix this issue myself without having to do return shipping. I have contacted the seller already though.
If it doesn't freeze or reboot at all in safe mode that usually means an app that you downloaded is causing the problem. The normal thing to try would be to factory reset the phone, download one app and see if there are problems. If the phone seems to be fine download a second app and use the phone long enough to see if the phone is stable. If it seems fine download a third app and do the same.
That's obviously very time consuming and if you were running a phone with heavily modded code like OnePlus with Oxygen it would probably be worth the investment of time. But this phone runs stock Android. Unless you are installing something unusual that might cause stability issues what you are describing sounds like a hardware problem. You might have bad memory for example and not enough is going on when the phone is in safe mode to trigger the unstable behavior.
I think returning or exchanging the phone you bought is definitely your best course of action. I really like this phone but it sounds like yours is defective or damaged.
The only other thing that comes to mind is that sometimes if you own more than one phone the Play Store will show apps that aren't compatible with the phone you are actually using. Dialers, messaging apps, camera apps and music players made for a specific phone brand aren't usually compatible with other brands because they need modded framework to function properly. Some apps that definitely are not compatible with this phone do show up in my Play Store Library available for download. Is it possible you are downloading an incompatible app?
I factory reset and haven't installed a single app. Just updated everything that was stock with the phone after reset. I was thinking faulty ram too, seems like it is.
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Grab a BTS zip from the back to stock thread... And flash that...
I'll bet however it was updated had some yuck in it...
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Someone in the Essential stock ROM dump thread just described the exact same behavior that you are experiencing. He hopes reflashing stock will fix it but since it's identical to what's happening with your phone I think he's going to end up disappointed. You might want to check out his post and see if he has any luck. It was the latest post in the thread so it should be easy to find.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page41
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Nickvanexel said:
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Click to expand...
Click to collapse
Sorry I didn't notice that. I haven't done any flashing on this phone but I know I read that people with the Sprint phones were flashing the regular stock image to get rid of the Sprint apps and get updates from Essential rather than Sprint. But if you don't want to unlock your bootloader you can download official factory images from the Essential website and sideload using a computer. Flashing instructions are on the download site.
https://www.essential.com/developer/current-builds
Alright I reflashed the latest firmware from essential page via adb sideload. I highly dout it worked but I'll see.
What would I need to do from here to do a complete fresh reflash completely overrighting any trace of the old os? I still want to keep it stock but doesn't matter if I need to unlock the bootloader. Just want a complete wipe of the old os and fresh reflash to be sure any traces of corruption are removed to be sure if it's a hardware issue.
That's easy on single partition phones but much more difficult on phones with an A & B partition like the PH-1. You definitely need to unlock the bootloader. On my Pixel XL you needed to flash the factory image separately to partitions A & B to ensure there was nothing left from before but the procedure might be different on this phone. I went through the flashing instructions when I got this phone and think if you flash the full restore stock image it supposedly returns both partitions to stock automatically but that definitely didn't happen on the Pixel. Considering that this phone is supposed to be easy to hard brick (which was virtually impossible on the Pixel) I wouldn't chance it unless you can't return or exchange the phone from the seller.
Well side loading the ota from essential website didn't work. I'd say it's already hard bricked. Still crashing after a while of using it. Last night I loaded as many apps at one time as I could. Got maybe 10 opened at once before it crashed. Seems like faulty ram to me.
Wife just had it happen on her new White one twice today while playing Pokemon GO.
She says she also had her podcast app and hangouts open but minimized and not being actively used in the background.
She's on a fresh install of Oreo 8.1 with the Gcam mod by MGC_5.1.018_Urikill_vXXII.apk using the settings suggested by aer0zer0
Anyhow I hope its just a completely random fluke and not a serious issue as I have a new black one from Amazon in the mail and would really hate to have to return these otherwise wonderful devices.
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Nickvanexel said:
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Click to expand...
Click to collapse
Ouch okay that most certainly sounds like a bad hardware issue as you suspected earlier.
Thankfully in her case the reboots were well apart from one another and the phone was fine after the reboot. Even let her play PKGO.
I mostly came in to comment to hopefully help by voicing that it had happened and the circumstances in which it did for her with the idea it might pinpoint some flaw in the overall system if there was one.