Was not doing much with my G6 today except webbrowsing and I walked over to my phone to find this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Links to this page: https://support.google.com/nexus/an...6698467256067-2151825810&p=verified_boot&rd=1
Eventually it said the system was corrupt and could not be started. Contact customer service.
I managed to get the phone to reboot and it started up fine. Have never seen this error so wondering if someone could explain?
Is it related to Secure start-up? Or maybe malware? There's not really anything installed on my phone that I wouldn't trust.
Will call T-mobile today.
Well this is unnerving to see....
this is the screen you see after you unlock the bootloader... shows on my phone as well and everytime you boot the phone. on my ZTE 7 it's slightly different, but message is the same. did your phone reboot on it's on? maybe after installing the latest update?
cortez.i said:
this is the screen you see after you unlock the bootloader... shows on my phone as well and everytime you boot the phone. on my ZTE 7 it's slightly different, but message is the same. Did your phone reboot on it's on? maybe after installing the latest update?
Click to expand...
Click to collapse
I'm assuming it restarted itself since I was out of the room when it happened. It looked like it tried restarting a few times. It refreshed that screen a few times, then it said that the system is corrupt and it could not be started, etc and to call customer service... then it turned off.
I did read about software modifications from that help link but haven't installed anything questionable. Pretty much only big apps like Twitter, Instagram. No games, no utilities since I am just testing what came with the phone. I haven't touched the bootloader since I'm still technically testing the phone. The most I've done is enable Developer mode but I haven't tweaked any settings.
I didn't accept any software updates and I didn't see any notifications. Unless it updates itself?
I attached the screen that the phone gives using Power + Vol Dwn
Again, it's still working. It just had to be rebooted. Just not sure what triggered the message... unless enabling Developer Options is all that it takes.
I'm trying to find the screen it gave me after the one I posted above. It didn't stay on long enough for me to take a picture.
Same thing happened to me just a little while ago - it's been running fine since I received it otherwise. It eventually restarts itself and seems ok, but then I got that error a second time within about 15 minutes.
The only change I had made today was installing the XDA Labs app. It seems shortly after that is when this started. I've since removed that app to see if the error returns.
bren924 said:
Same thing happened to me just a little while ago - it's been running fine since I received it otherwise. It eventually restarts itself and seems ok, but then I got that error a second time within about 15 minutes.
The only change I had made today was installing the XDA Labs app. It seems shortly after that is when this started. I've since removed that app to see if the error returns.
Click to expand...
Click to collapse
Uh oh. Keeping an eye on this
Sent from my Nexus 6P using Tapatalk
bren924 said:
Same thing happened to me just a little while ago - it's been running fine since I received it otherwise. It eventually restarts itself and seems ok, but then I got that error a second time within about 15 minutes.
The only change I had made today was installing the XDA Labs app. It seems shortly after that is when this started. I've since removed that app to see if the error returns.
Click to expand...
Click to collapse
FWIW I installed the app yesterday and haven't seen this crash.
bren924 said:
Same thing happened to me just a little while ago - it's been running fine since I received it otherwise. It eventually restarts itself and seems ok, but then I got that error a second time within about 15 minutes.
The only change I had made today was installing the XDA Labs app. It seems shortly after that is when this started. I've since removed that app to see if the error returns.
Click to expand...
Click to collapse
Try factory resetting my phone. I did it to mine with Power Btn + Volume Down when starting. You gave to take finger off power button when LG logo comes up and then holding power btn down again quickly. It flashes it incredibly quick.
When I googled the issue, I read it has something to do with "verified boot". So far the only phones I've read that have it are Nexus, but the text on the LG is a little bit different. There is a second screen that says something about customer support... if you see this screen, if possible have a camera on hand to screen shot it. It looks like some kind of bug with the OS. Doesn't look like it will effect the function of the phone. But the message is frightening...
This is the Google official page about it:
Understand warning about operating system safety
https://support.google.com/nexus/an...6698467256067-2151825810&p=verified_boot&rd=1
What is Strictly Enforced Verified Boot in Android 7.0 Nougat?
http://thehackernews.com/2016/07/android-verified-boot.html
Pasted above from the second link in the above post. Seems like it could possibly apply to this issue...
What is Strictly Enforced Verified Boot in Android 7.0 Nougat?
http://thehackernews.com/2016/07/android-verified-boot.html
As far as security is concerned, Google is going very strict with the newest version of its mobile operating system.
Until now, Google has not done more than just alerting you of the potential threats when your Android device runs the check as part of the boot process.
Android Marshmallow 6.0 does nothing more than just warning you that your device has been compromised, though it continues to let your device boot up.
1. Android Nougat 7.0 Getting Strictly Enforced 'Verified Boot'
In
Android Nougat, Google has taken the security of its Android operating system to the next level by strictly enforcing verified boot on devices.
Among multiple layers of security protection, Android uses verified boot - since Android version 4.4 KitKat - that improves its device's security by using cryptographic integrity checking to detect if your device has been tampered with.
Now, Android Nougat will strictly enforce the boot check, giving you far more than just a warning.
2. Android 7.0 Verified Boot Protects Device from Rootkits and Malware
Enforcing verified boot on a device is a good idea.
If any Android malware or rootkit made its way onto your Android device and made deep system changes to critical kernel files, your device will either start in a limited-use mode (presumably similar to safe mode) or refuse to start at all, protecting your data.
In addition to strict verified boot, Android Nougat also features forward error correction that is capable of repairing some errors on devices without any user input.
And, of course, Nexus devices will be the first to get these features.
This will prevent your Android device from becoming a playground for malware and viruses, at least after you restart it.
That sounds really great. Right?
3. If Modified, Corrupt or Tampered, It won't let your phone Boot
For most users the strict verified boot would be helpful, however, for some, it's bad news. According to Google, some non-malicious corruption of data could cause Android devices to fail to boot up because verified boot process runs into issues that it can not correct.
This data corruption could be the result of some software flaws or hardware issues.
Here's what the Android Developer blog explains: "This means that a device with a corrupt boot image or verified partition will not boot or will boot in a limited capacity with user consent. Such strict checking, though, means that non-malicious data corruption, which previously would be less visible, could now start affecting process functionality more."Since corrupted data may not always be malicious, even a single-byte error could prevent the device from booting.
However, Android Nougat brings additional code designed to protect against data corruption.
"In the changes we made to dm-verity for Android 7.0, we used a technique called interleaving to allow us to recover not only from a loss of an entire 4 KiB source block, reads the blog, "but several consecutive blocks, while significantly reducing the space overhead required to achieve usable error correction capabilities compared to the naive implementation." 4. Verified Boot Has Made It Harder to Root Android 7.0 Nougat
Like I said, data corruption could not always be due to malicious reasons.
Strictly enforcing verified boot could also make it tougher for you to tweak your Android Operating System (especially with locked bootloader) using custom ROMs, mods, and kernels.
Since this involves circumventing the locked bootloader, verified boot process will detect any changes, making it harder for users to play with their devices when Nougat rolls around.
The bottom line:
Enforcing strict verified boot in Android Nougat is a good idea, because most users root their devices with custom firmware but forget to take important security measures, which leaves their devices open to malicious software and rootkits.
What do you think of the additional security Google provides to the boot process in Android Nougat?
Let us know your views in the comments below!
Click to expand...
Click to collapse
Interesting it mentions it tries to fix the error. I noticed this when mine was "crashing". Flashed the first screen a few times before it "failed". Unfortunately can't find an example of this screen anywhere.
Man. This happened to me on LG v20. No explanation since I didn't root my phone. Lucky T-Mobile sent me replacement .
Sent from my LG-H872 using Tapatalk
Is this limited to t mobile devices so far? Sounds like they have an app Google sides not like.
This has happened to me twice about 4 days apart. I have AT&T LG G6 US variant. I have also seen on Reddit this happened to Verizon customers.
I don't root/unlock and I only install well known apps from the playstore.
I did find one thing in common was that both times it happened relatively soon after turning OFF the always on display. Was this the same for anyone else?
for those affected by this "issue", have you reported this to T-Mobile/ATT? if yes, what was their respective response(s)? thanks.
cortez.i said:
for those affected by this "issue", have you reported this to T-Mobile/ATT? if yes, what was their respective response(s)? thanks.
Click to expand...
Click to collapse
They were more interested in talking about malware tbh. Thinking of reporting it to LG. Especially if I get a shot of the second screen... that one reads like it's bricked.
For what it's worth, this hasn't happened again since I removed the XDA Labs app. May just be coincidence. I'm planning on putting that app back on to see if the issue resumes.
cortez.i said:
for those affected by this "issue", have you reported this to T-Mobile/ATT? if yes, what was their respective response(s)? thanks.
Click to expand...
Click to collapse
The ATT rep said looks like a software bug and reset the phone and said if it happens again to go through the exchange/return process.
It has happened a second time already I just really don't want to return this phone if it's a software issue that could be fixed with an update. But I'm starting to think maybe I should.
Dcpeiffer said:
The ATT rep said looks like a software bug and reset the phone and said if it happens again to go through the exchange/return process.
It has happened a second time already I just really don't want to return this phone if it's a software issue that could be fixed with an update. But I'm starting to think maybe I should.
Click to expand...
Click to collapse
UPDATE: I talked with AT&T and they said that a phone update that went live is actually what's causing the faulty bootloader message. Apparently a factory reset is fixing the issue most of the time but I can exchange the phone for up to a year if the issue persists.
Glad to say since I've factory reset my phone, I've had 0 issues. I'm thinking it is a bug tbh and not something to be too concerned with.
Dcpeiffer said:
UPDATE: I talked with AT&T and they said that a phone update that went live is actually what's causing the faulty bootloader message. Apparently a factory reset is fixing the issue most of the time but I can exchange the phone for up to a year if the issue persists.
Click to expand...
Click to collapse
Glad AT&T is taking responsibility and giving you a nice window for exchange. All T-mobile was willing to give me was the normal 20 days, then it would have to be within the warranty period...
Related
I'm trying to get to the bottom of this freezing issue affecting many users where the NS will not wake up from standby and requires a battery pull to rectify. As samsung or Google seem reluctant to do anything about this (or even acknowledge the problem) I wonder if we can narrow it down to what is causing the issue? If you are affected by this you will know what I am referring to without the need for further explanation.
If your NS is freezing, please copy and paste the following with your answers:
Length of ownership:
How long ago did freezing start:
Current software version:
Did you notice freezing before update:
Update method (Manual / OTA):
i9020 (SAMOLED) or i9023 (SCLCD):
Hopefully a colleciton of responses to the above might start to show a pattern so if as many of you can replay with your answers as possible we stand a better chance of narrowing this down.
note to mods: please don't move this to Q&A as with my other thread on the matter as this is not a question, more an attempt to gain more info. Thanks
stock ROM
ownership: since it came out in december
freezing: what freeze?
Did not notice any freeze, not before, not after
method OTA
i9020
same answer for custom ROMs, except for the OTA part
Length of Ownership: Since Feb 25, 2011
Freezing: yes, at random times have not pinpointed what/why (necessitating a battery pull every single time )
Version: 2.3.1 OTA
Noticed it shortly after the update (at least twice a week) but NOT before (the OTA update)
Edit: Stock
SAMOLED
Sent from either my Nexus S, N1 or telepathically using two tin cans and some string.
AllGamer are you on 2.3.3 or something else?
I'm hearing the issue effects all 2.3.x versions ... was there anything before this or is that what the NS released with - I can't recall from when I had mine at launch?
Hi,
My responses inline.
Length of ownership: 2 months
How long ago did freezing start: 1hr
Current software version: 233
Did you notice freezing before update: no
Update method (Manual / OTA): manual, on custom rom now
i9020 (SAMOLED) or i9023 (SCLCD): i9020
1 thing I noticed is that my freezing was not rectified even after puling the battery out, the only thing it responded was changing the sim card, then it took me phone registration screen and phone was fine after this even with old sim. Never encountered this problem after that.
Sent from my Nexus S using XDA App
Length of ownership: Jan 2011
How long ago did freezing start: Since Jan 2011 randomly
Current software version: 2.3.3 Cyanogen 7.0 RC4 with netarchy 1.3.0.1 CFS
Did you notice freezing before update: Yes
Update method (Manual / OTA): Manual , using custom roms
i9020 (SAMOLED) or i9023 (SCLCD): i9020
Additional comments : Personally, I think it has to do with both BLN and noLED apps and how the kernels are responding to them. BLN pro caused me more problems with the freezing as opposed to noLED so i moved back to noLED.
For me, the freezing is about once every 2-3 days and usually if i flash a non-netarchy CFS kernel. Once i'm on netarchy, it freezes less frequently. Maybe once a week and only if i overclock to 1.3 and charging at the same time. (Possible overheating problem?)
Hope my comments helps in your research. Thanks for doing this
xspyda said:
AllGamer are you on 2.3.3 or something else?
I'm hearing the issue effects all 2.3.x versions ... was there anything before this or is that what the NS released with - I can't recall from when I had mine at launch?
Click to expand...
Click to collapse
yes 2.3.3
have you guys tried wipe data + wipe cache?
AllGamer said:
yes 2.3.3
have you guys tried wipe data + wipe cache?
Click to expand...
Click to collapse
I'm pretty sure that has been tried by many experiencing the problem to no avail. Seems that whatever causes the issue results in a hardware fault that neither Google or Samsung are willing to acknowledge.
I'd LOVE to hear of someone having actually fixed this problem.
Length of ownership: 4 months
How long ago did freezing start: after 6 weeks
Current software version: 2.3|2.3.1|2.3.2|
Did you notice freezing before update: not sure
Update method (Manual / OTA): OTA
i9020 (SAMOLED) or i9023 (SCLCD): i9020
I bought my phone on 12/31/2010 with FW 2.3. The phone worked fine for about 6 weeks, maybe a bit less. At first I've noticed random reboot or freeze, but very very few of them. then it gradually escalated to unusable phone.
Quick summary of Samsung's service.
1.) I've send the phone for the 1st time - Samsung claims no issues found, restores phone to FW 2.3 and mails the phone back. I open a package a week later and cannot boot up the phone, the phone only displayed the while "Google" writing and a lock-pad on the bottom of the screen. After many and many retries I was able to boot up the phone but then it froze again.
2.) I've send the phone for the 2nd time - Samsung keeps the phone for a week and claims no issues found, restores phone to FW 2.3 and mails the phone back. I pick up my phone, put in my battery and the phone freezes within 5-10 minutes. So I mail it back again.
3.) I've send the phone for the 3rd time - They are evaluating I guess. I've called and some woman picked up (2nd level support here in US as i requested) very unfriendly and basically said to my face "we're evaluating your phone and you'll get your phone when you'll get it" and that she cannot do anything about this.
i will never buy a Samsung phone again.
They always reset to FW 2.3 which the phone still freezes on. Some Google guy claimed for a while that they are working on this but it seems doubtful.
here is the link:
http://www.google.com/support/forum/p/Google+Mobile/thread?hl=en&tid=44db6d8e31129d4c
Wow, nasty experience with Samsung by the sound of it and from what. I've read this is all too common.
I'd personally be quite satisfied with the Nexus S but I don't think I could use one daily knowing that I could run into this problem at any time with no way to resolve and be at the mercy of Samsung who seemingly don't give a damn.
From the content of this thread I'm not seeeing any pattern as I'd hoped to. Shame, I really thought we might just learn something from this and sadly the only thing I am learning is to steer clear of Samsung.
Of course this issue doesn't affect every NS owner out there but is seems those tthat are unlucky enough to experience issues are left out in the cold.
Still interested to hear of other users' experiences. Thanks to all that have contributed so far, keep your reports coming guys.
Length of ownership: Since the week of the US release
How long ago did freezing start: Roughly 2-3 weeks ago.
Current software version: 2.3.3
Did you notice freezing before update: No
Update method (Manual / OTA): OTA
i9020 (SAMOLED) or i9023 (SCLCD): i9020
I first noticed my phone randomly crash, reboot and then go to the recovery screen with the exclamation mark in the triangle. It was just sitting there when I saw it happen. Pulled the battery and booted fine.
The next day it crashed, rebooted and went into safe mode... which I had never even seen or used before. In safe mode it crashed again and rebooted and went into a crash > safe mode boot loop until I pulled the battery. Worked fine for a while and then the freezes started happening. I would go to power on the screen and nothing would happen. Pulled the batter and then it worked.
Sometimes it would freeze and the screen was just very dimly lit... sometimes I would see just the menu "buttons" lit. either way a battery pull was the only solution. Started happening more frequently... though again not if I was plugged in.
Tried full wipes a couple times including storage... even with just the standard apps installed it still would eventually freeze.
So using my Nexus One for now... I'm really not in a hurry to deal with Samsung so I've been putting off calling them. But I miss my NS in my hands...
bought in USA Bestbuy
Length of ownership: since January 2011, 4 months
How long ago did freezing start: since end of February after OTA update
Current software version: 2.3.1
Did you notice freezing before update: NO, Nexus S was working for 2 months without freezing
Update method (Manual / OTA): OTA from 2.3 to 2.3.1
i9020 (SAMOLED) or i9023 (SCLCD): i9020
My phone randomly crashed, reboot and then went to the recovery screen with the exclamation mark in the triangle.
I've tried factory reset, clear cache, format SDcard,
I've tried flash 2.3.1, 2.3.3 with Odin
I've tried nandroid recovery 2.3.3 , 2.3.1
no idea why and how to solve it
----
I just want to add that I didn't install any software and I didn't change any settings. I've just let the phone in default setting after flashing or recovering (nandroid recovery). I didn't set any google account or set wifi. And also I didn't insert any SIM card and and bootloader is locked. Still is freezing.
xspyda: yes, I tested without SIM card. Right now I haven't been using Nexus S for 2 months it is not possible to use him.
-----
edit2:
I played with this phone again, I did nandroid recovery 2.3.1 ( It is pity that we don't have nandroid backup of 2.3 ) maybe could help.
And after 3-6 restarts he got stuck in this screen and only remove battery helped.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe it helps to move forward this issue.
pphmmr said:
I've tried factory reset, clear cache, format SDcard,
I've tried flash 2.3.1, 2.3.3 with Odin
I've tried nandroid recovery 2.3.3 , 2.3.1
no idea why and how to solve it
Click to expand...
Click to collapse
This may be clutching at straws but have you tried remving the sim card also? In fact, does the freezing still occur without a sim card inserted - anyone?
I could be wrong but it appears to me that the majority of people experiencing freezing issues are doing so only after performing an update, whether that be manual or OTA. Could there be something wrong with the way Google are pushing out these updates I wonder?
I think we need more reports like these already collected and then we need to look at the possibility of passing this information on to the relevant area for investigation (I know, it's a long shot).
Thanks for all reports so far, would be great if we can keep this thead going / updated and gather as many instances of this as possible.
Mods: Any chance of making this a sticky so as to collect as much info as possible?
Please keep your reports coming!
Length of ownership: since january
How long ago did freezing start: about a month or so ago
Current software version: 2.3.2 with voodoo kernel stock rom
Did you notice freezing before update: nope
Update method (Manual / OTA): manual
i9020 (SAMOLED) or i9023 (SCLCD): i9020
Sent from my Nexus S using XDA App
Lately my phone freezes randomly. Yesterday I got a phone call, went to plug in the head set and the phone wouldn't wake up for me to turn off speaker phone, and then it just rebooted. I'm considering just wiping my phone and starting fresh. I'm starting to lose my patience with this crap
Sent from my Nexus S using XDA App
Thanks for the edit / update pphmmr. From what have learned so far there is no way for us to fix this when the freezing occurs.
mylexon20s - are you talking about the same freezing issue that is described in this thread, the known issue affecting many? If so, can you please fill in the template at the beginning as other users have so we can continue to seek a pattern to this fault please?
There is new update 2.3.4 out. Does it help to solve our problem? Has anyone tried?
pphmmr said:
There is new update 2.3.4 out. Does it help to solve our problem? Has anyone tried?
Click to expand...
Click to collapse
Interested to know this too. Anyone with the problem tried the update yet?
Perfect. Done. Now it is my nexus s OK. finally.
I've just updated to 2.3.4.
I was testing it for 3 hours and still ok.
edit1:
still I can wake SNS up after 8 hours and also after 24 hrs. still OK.
How to solve the problem:
I upgraded to GRI49 ver. 2.3.3 by this zip
I copied zip file into SNS sdcard and follow next steps:
1. turn off
1. turn on + hold volume up
3. select RECOVERY
4. if you see exclamation mark in the triangle press and hold power button and after 2 sec. press volume up as well
5, choose update from sdcard
6. find zip file
then I updated again but to ver. 2.3.4 by this zip with same procedure
And then I did factory reset and I wiped cache as well.
If you have 2.3.3 GrI40 you can skip 1st procedure and just update to 2.3.4 directly.
Great, keep us posted please...
My phone has turned off on its own once our twice a day in the 4 days since
I got it. Now I have to do that fake lock for the bootloader that basically just removes the message. Anything else I should know?
Sent from my MB860 using XDA App
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Couldnt help myself. But for real, you could help us help you help us all by giving more information.. What message are you talking about removing? What, if anything, have you tried to resolve the random reboot (im assuming) issue? And what is a fake lock for the bl, if there is such a thing I missed it. Have you done a wipe + fresh flash.?
zeropants said:
My phone has turned off on its own once our twice a day in the 4 days since
I got it. Now I have to do that fake lock for the bootloader that basically just removes the message. Anything else I should know?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You live in Bloomington, it IS more than likely Aliens.
umm, I think you're implying you're trying to hide the fact that your phone's been rooted and bootloader unlocked, so you can safely return it? Are you returning to Asurion or AT&T?
Or are you implying something else??
Sorry, I didn't realize how vague that was until after I re-read it.
There's a process so the the unlocked message doesn't show. Then, I was planning on reloading the stock 2.3.4 rom through RSD. I bought the phone at a Best Buy Mobile so I was just going to turn it in for another Atrix...possibly something else. I was warned off the phone when I went in to buy it because of the number that get returned but I liked it anyway.
I don't know if it's necessarily shutting off so much as becoming unresponsive. The problem occurs after playing a game for a little while, or something similar that would make the phone a little warm. Whenever I finish, and I lock the screen, it won't unlock and the power button literally does nothing. I have to pull the battery, then I hit the power button and it boots right up.
I've been on 3 roms all with clean wipes, and they all do it.
Thats what we call "the sleep of death". Its unfortunate thats been happening, i have had that prob on the Captivate but not on the Atrix *knock on wood*. Are you using a custom kernel, OC/UV, SetCPU or a similar voltage control app? Those types of things was what had caused the SoD for me..
Edit: in this thread somebody is reporting he had the issue only when WiFi was always on, and Green Power fixed it, a similar app is Juice Defender. Those apps periodically turn the wifi on to save power (instead of having it on constantly). Another user said putting his phone in "performance mode" resolved the issue, thats in settings under battery.
I can confirm I have my wifi set to always on. I was using CM7's powersave governor but I just changed it over to performance. If this is not happening to everyone's Atrix I still think it would be worth me taking it back in to get a different one. We'll see what happens with the governor change.
---------- Post added at 01:26 AM ---------- Previous post was at 12:58 AM ----------
zeropants said:
I can confirm I have my wifi set to always on. I was using CM7's powersave governor but I just changed it over to performance. If this is not happening to everyone's Atrix I still think it would be worth me taking it back in to get a different one. We'll see what happens with the governor change.
Click to expand...
Click to collapse
After changing to performance the phone reboots itself a few minutes after the game is over instead of just freezing. I think this is pure hardware defect.
It could be a hardware defect. I have always used performance mode. When I was on Froyo I had a bunch of random reboots but since gb I dont see many anymore. Every now and then I get a reboot but never a sleep of death (maybe because
Ive never used powersave?). There are many other threads about the reboots and I agree with what I read once that instead of an actual reboot it is a graphical shell crash. The reason I agree with this is because once during a call I experience one of these reboot/ graphic shell crashes and was able to continue my conversation the whole time the phone was "booting", my call never disconnected.
WiredPirate said:
It could be a hardware defect. I have always used performance mode. When I was on Froyo I had a bunch of random reboots but since gb I dont see many anymore. Every now and then I get a reboot but never a sleep of death (maybe because
Ive never used powersave?). There are many other threads about the reboots and I agree with what I read once that instead of an actual reboot it is a graphical shell crash. The reason I agree with this is because once during a call I experience one of these reboot/ graphic shell crashes and was able to continue my conversation the whole time the phone was "booting", my call never disconnected.
Click to expand...
Click to collapse
I'll be taking it back in either today or tomorrow depending on how much time I get. I wouldn't mind dealing with this periodically, but I can pretty much count on freezing or a reboot after running a game for longer than 5 minutes.
I cleared everything off and ran the official firmware off RSD, now the phone just boots the AT&T logo splash screen and starts over.
zeropants said:
I cleared everything off and ran the official firmware off RSD, now the phone just boots the AT&T logo splash screen and starts over.
Click to expand...
Click to collapse
If you have the option, I'd recommend the Inspire4G, if you're sticking with AT&T.
It's like the Atrix but . . . well, it has a bigger screen Not as easy to root though.
rynosaur said:
If you have the option, I'd recommend the Inspire4G, if you're sticking with AT&T.
It's like the Atrix but . . . well, it has a bigger screen Not as easy to root though.
Click to expand...
Click to collapse
I was looking at that one, almost exactly like my Thunderbolt. I don't think it has the horespower the Atrix does though. We'll see what happens. The screen no longer says unlocked, so I should be OK.
I went into Android Recovery off of boot up but I don't get the factory reset options or anything. No buttons or any touch area on the screen bring up options on the recovery menu.
I was finally able to get a recovery done from the boot menu after finding out Motorola's instructions are crap. Since the recovery, the phone hasn't done a boot loop or shut off/restarted. Hopefully we're all good now.
My Atrix does the sleep of death on average 2 times a day. That being said sometimes it doesn't happen for a day, but the next has 4 sod's. My phone has exhibited this behavior since day one. Stock, unlocked, and multiple kernel and radio combinations all result in sod's. Took it to ATT and was told the phone just does that and any replacement will likely do the same thing.
zibrah3ed said:
My Atrix does the sleep of death on average 2 times a day. That being said sometimes it doesn't happen for a day, but the next has 4 sod's. My phone has exhibited this behavior since day one. Stock, unlocked, and multiple kernel and radio combinations all result in sod's. Took it to ATT and was told the phone just does that and any replacement will likely do the same thing.
Click to expand...
Click to collapse
my phone has never done the sleep of death, and i'm sure a lot of people here have never experienced it either.
you got a crappy customer service rep who just didn't feel like replacing your phone.
I still have my fingers crossed, but in the 30 or so hours since I had the full reset done at the boot menu the phone is not getting as hot, and it's not doing the sleep of death. I played a few games, watched vides, etc, and it's coming out of sleep like it should. The good news is BB Mobile has a 30 day return policy on their phones instead of AT&T's 14, so if I continue to have trouble I can take it in.
zeropants said:
I was finally able to get a recovery done from the boot menu after finding out Motorola's instructions are crap. Since the recovery, the phone hasn't done a boot loop or shut off/restarted. Hopefully we're all good now.
Click to expand...
Click to collapse
Can this be done on an unrooted stock gingerbread? I've tapped all over the screen while it was in Android Recovery, especially just above/around the Search button.
Tubboi said:
Can this be done on an unrooted stock gingerbread? I've tapped all over the screen while it was in Android Recovery, especially just above/around the Search button.
Click to expand...
Click to collapse
I'm not at the menu now, but I believe the options are actually brought up by holding in volume up and volume down at the same time (I don't remember if the power button was involved...
The Motorola instructions call for tapping the screen but that didn't do it, thus my comment than that their instructions were ****.
Also, as an update, still no sleep of death since the reset.
zeropants said:
I'm not at the menu now, but I believe the options are actually brought up by holding in volume up and volume down at the same time (I don't remember if the power button was involved...
The Motorola instructions call for tapping the screen but that didn't do it, thus my comment than that their instructions were ****.
Also, as an update, still no sleep of death since the reset.
Click to expand...
Click to collapse
Keep us updated...I had the same problem...Depending on how you go I will do a complete restore with RSD lite...Thank you
rynosaur said:
If you have the option, I'd recommend the Inspire4G, if you're sticking with AT&T.
It's like the Atrix but . . . well, it has a bigger screen Not as easy to root though.
Click to expand...
Click to collapse
IMO, if I was going to keep my oversized and battery limited, inspire 4g, I would of gotten a HTC hd7s lol.
Sent from my MB860 using Tapatalk
kba712 said:
Keep us updated...I had the same problem...Depending on how you go I will do a complete restore with RSD lite...Thank you
Click to expand...
Click to collapse
If you are on the original rom you can do the reset with the boot mode. If you're not you need to restore through RSD, then do the reset.
I've gone 2 straight days without any issues.
Hello everyone, my Nexus 7 (32gb Wi-Fi Model) has been randomly rebooting itself. I have unlocked the boot loader on it, but I have not installed any custom ROMs yet. I've mainly noticed it rebooting when I'm watching YouTube or using Google Chrome. Any idea on how to fix it? Thanks.
Just a test.
same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?
Best app to help figure this out. Go into the options and check the top 3.LINK
Might be a shot in the dark but I had experienced reboots that was caused by HD Widgets (was acknowledged by them) and possibly Beautiful Widgets. uninstalling them cured my nexus 7 rebooting syndrome.
gokart2 said:
Best app to help figure this out. Go into the options and check the top 3.LINK
Click to expand...
Click to collapse
Currently giving this app a try. Hopefully this will shed some light on the situation. Thanks.
Jomari29 said:
same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?
Click to expand...
Click to collapse
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.
Infobits said:
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.
Click to expand...
Click to collapse
Awesome! Thanks for the tip! I spent the last week slowly removing apps and re-installing them and I think I've solved the problem.
I've been following this forum re 32.3.A.0.376. There are many users commenting on sound issues, etc. However, many have rooted their phones and done modifications. I use my phone unmodified and would like to know if the various issues exist on the standard phone. Thanks.
rebecker said:
I've been following this forum re 32.3.A.0.376. There are many users commenting on sound issues, etc. However, many have rooted their phones and done modifications. I use my phone unmodified and would like to know if the various issues exist on the standard phone. Thanks.
Click to expand...
Click to collapse
I haven't tried re-locking my bootloader so I do not know whether a locked bootloader would yield higher external sound volume. My *guess* is it won't.
I have however tried both with unmodified kernel and modified (RootKernel 5.20 with DRM fix) kernel and in both cases I experience a significantly lower volume from both Spotify and YouTube compared to Marshmallow.
I have been running unmodified stock since launch for the first time on an android, and flashed AU .376 this weekend, with thoughts that if it did not fix this sluggish poor-batteried clump, I would switch to something else like Huaweii.
So far on day 2.5 I experience a much more smooth phone with prolonged battery life, albeit not as much as it had on MM. I've not experienced the sound bugs with low volume, although when I sitting down to switch the various notification sounds while wearing earplugs, it suddenly started playing from the phone speaker.
So far I am happy enough that I will keep the phone for now, with no plans of rooting or unlocking it as of now.
Is the AU .376 legit to donwload? I mean, would my warranty be void if i download it before the official release?
non-root user
AndreasElia said:
Is the AU .376 legit to donwload? I mean, would my warranty be void if i download it before the official release?
non-root user
Click to expand...
Click to collapse
It might void the warranty, ref http://talk.sonymobile.com/t5/Android-development/using-flashtool-void-warranty/td-p/924234. Although for me in Norway this might fall in a gray zone as we have some good consumer protection laws in norway.
I might reflash it without any wipe when the proper release is out just in case I am to sell it at any point.
Been using the new build stock since yesterday and noticed better battery life. I'm using a US stock E5803 on 32.3.A.0.376 Malaysia and I've disabled a bunch of extra apps. Here are a few pros/cons that I've seen so far.
Pros: Better battery life, improved camera post processing (white/colour balancing, sharpening), improved camera speed with video recording/photos, Improved ram management, LTE does not drop anymore, phone heats up a tiny bit less than before, fingerprint scanner works with no issues, better stamina mode options, and phone sleeps like a baby with no noticeable battery drain.
Cons: Lower volume on 3rd party apps using phone speaker (spotify, etc) and no issues so far with Anker bluetooth speaker.
Untested: Bluetooth with car stereo, call quality.
Im using Nougat since last week and im downloading MM back again. Im not satisfied with nougat. In my opinion the performance is worse than on previous release.
I installed the previous release (.372) via OTA, so far it's good but battery is a bit less.
My question here is, if .376 will be pushed to my phone via OTA or I will have to flash it manually.
Currently I'm waiting for OTA update and checking daily, so fsr no luck :/
Sent from my E5803 using Tapatalk
Way better than any Marshmallow firmware I ever used on my phone. ZERO PROBLEMS! No sound issues, no notification issues. I'm using .376 w/o root to test if battery life is longer than when using root. Anybody noticed differences in battery life between root and non-root?
Cerhio said:
Way better than any Marshmallow firmware I ever used on my phone. ZERO PROBLEMS! No sound issues, no notification issues. I'm using .376 w/o root to test if battery life is longer than when using root. Anybody noticed differences in battery life between root and non-root?
Click to expand...
Click to collapse
How did you install it without root? Tried to do it with Xperia Flash and it give me a locked phone notification.
Also, is there a way to back up the current firmware before installing .376?
Thanks
AndreasElia said:
How did you install it without root? Tried to do it with Xperia Flash and it give me a locked phone notification.
Also, is there a way to back up the current firmware before installing .376?
Thanks
Click to expand...
Click to collapse
Install the same way like with root. Use latest version of Flashtool to download and install new firmware.
I assume you have a locked bootloader which means no nandroid backup via TWRP, right?
You could try to backup via adb. Google for adb backup. You can also use a GUI called Holo for it if you not familiar with command prompts.
However from what i heard it's not as good as a nandroid backup and a few things can be missed in the backup.
But if you don't like nougat, you can also just flash back an old firmware via flashtool.
So, I woke up today to see OTA notification for .376 update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It was only 85mb download, so I downloaded it via mobile data and installed it. I took screenshots of before and after update, take a look.
Currently running with no issues, and will post update for battery time and performance.
Sent from my E5803 using Tapatalk
Just updated it to Nougat, no root, no unlocked bootloader. Everything is fine, volume is ok I guess (seems high both with music and with ringtones) very fluid. Camera is maybe a bit improved (quality is almost the same) but apart from the countdown before the selfie shooting, there is the possibility to set the Iso up to 3200 when using 20/23 mpx in manual mode (don't remember if it was in MM too); seems a little faster when taking the picture. Still no control over shutter speed in the stock camera, STILL limited to 1/10 in the manual camera app (damn), S T I L L no capability to shoot Raw. Overheating is still there, but not much a problem (at least in winter )
Good update, not really different after all but little improvements are there (damn Sony is too lazy on the camera though)
Gewiz said:
Install the same way like with root. Use latest version of Flashtool to download and install new firmware.
I assume you have a locked bootloader which means no nandroid backup via TWRP, right?
You could try to backup via adb. Google for adb backup. You can also use a GUI called Holo for it if you not familiar with command prompts.
However from what i heard it's not as good as a nandroid backup and a few things can be missed in the backup.
But if you don't like nougat, you can also just flash back an old firmware via flashtool.
Click to expand...
Click to collapse
Good morning
Did everything you suggested without any trouble - used Android Studio for the back up and then download Xperia flashtool (Emma).
Unfortunately when reaching the point that i had to flash my mob with the new system, 'Emma' cannot proceed due to my phone been locked. Knew that it was too easy to finish everything fast and successfully Guess i ll have to wait
Anyone here with a nougat update in UK?
AndreasElia said:
Good morning
Did everything you suggested without any trouble - used Android Studio for the back up and then download Xperia flashtool (Emma).
Unfortunately when reaching the point that i had to flash my mob with the new system, 'Emma' cannot proceed due to my phone been locked. Knew that it was too easy to finish everything fast and successfully Guess i ll have to wait
Click to expand...
Click to collapse
Nearly pal, i don't know if it should work with latest version of emma to. Never used before. Usually if flashtool is mentioned here, we mean another tool. Try it with this one(latest version):
http://www.flashtool.net/downloads.php
I updated to the Vodafone UK firmware through Flashtool (I live in Norway) and I noticed they've fixed the white noise issues with sound through mini jack, which is amazing
However, it seems that my unlocked bootloader is causing some issues with the fingerprint scanner, Youtube, mobile connections etc. Think I'm gonna root, as the thermal engine still seems to be kind of meh :/. Also, no stutters so far, even when using Chrome and Word at the same time plus Messenger bubbles
It's been about 27 hours since the update and I'm loving it. No volume issues at all and battery life seems at least comparable to MM (my use was abnormal for the past day, so I'll report back if I notice drastically different battery life over time). Only thing I did after updating was cleared the cache. One small warning, though: my update took a LONG time... nearly an hour. I didn't expect that, and it had me worried that something went wrong, but it was fine.
jackpotbox said:
Anyone here with a nougat update in UK?
Click to expand...
Click to collapse
Yes, got mine on O2. Not convinced on battery life is better but overall looking it
Sent from my E5823 using Tapatalk
Gewiz said:
Nearly pal, i don't know if it should work with latest version of emma to. Never used before. Usually if flashtool is mentioned here, we mean another tool. Try it with this one(latest version):
http://www.flashtool.net/downloads.php
Click to expand...
Click to collapse
Tried again last night, installing eveything right from the beginning. this time is seemed to be much easier and faster and at last updated to Nougat successfully! Only thing noticed until now is the smoother fingerprint sensor and i really enjoy the clear all and window switch commands.
Thanks for all the help, have a nice day
Andreas
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.