Does anyone have any ideas how to find why my phone is rebooting randomly? I'll check it periodically and then it will have a bar stating it's starting. Then my launcher loads and no icons and I need to wait a minute. I don't know exactly what's going on. It appears the phone is randomly rebooting.
Have you tried a factory reset? Are you rooted?
I just factory resetted it and rooted it a few days ago. I got to thinking I think the rebooting started after I throttled the cpu trying to save battery. I just changed the cpu governor fro ondemand to scheduled. So far it seems to run faster but I'm sure the battery will be worse but we'll see if the crashing ceases.
Crashed and rebooted 15 minutes ago. So, changing cpu back didn't fix.
Flash the 100% stock image and try leaving it that way. If the problem doesn't occur, it's something you're doing/flashing/changing that's the cause of the issue.
Obviously I know it's not a hardware issue.... so I know a 100% stock would fix it. I'm trying to figure out how to fix it without putting it to stock.
dorlow said:
Obviously I know it's not a hardware issue.... so I know a 100% stock would fix it. I'm trying to figure out how to fix it without putting it to stock.
Click to expand...
Click to collapse
Just so you know, mine started freezing/rebooting after the May update on stock everything. I think that update has issues.
rft183 said:
Just so you know, mine started freezing/rebooting after the May update on stock everything. I think that update has issues.
Click to expand...
Click to collapse
never had freezing/rebooting issue with mine.
mngdew said:
never had freezing/rebooting issue with mine.
Click to expand...
Click to collapse
I seem to be seeing a lot of people complaining about the issue. It's been an issue with the Pixel since the beginning, apparently, but it seems to have gotten worse with the May update.
With that said, I did make another change around the same time... I had switched from Project Fi to a Verizon MVNO, and so I flashed the Verizon system image (from the Google Factory images page) rather than the standard one, since it supposedly had some Verizon-specific fixes.
rft183 said:
I seem to be seeing a lot of people complaining about the issue. It's been an issue with the Pixel since the beginning, apparently, but it seems to have gotten worse with the May update.
With that said, I did make another change around the same time... I had switched from Project Fi to a Verizon MVNO, and so I flashed the Verizon system image (from the Google Factory images page) rather than the standard one, since it supposedly had some Verizon-specific fixes.
Click to expand...
Click to collapse
Is this freezing/rebooting Verizon specific issue?
mngdew said:
Is this freezing/rebooting Verizon specific issue?
Click to expand...
Click to collapse
I don't know. That was the only change that I'd made at the time, though. It's gotten really annoying, so I've flash PureNexus with ElementalX to see if that would make a difference. I haven't been using it long enough to say one way or the other.
rft183 said:
I don't know. That was the only change that I'd made at the time, though. It's gotten really annoying, so I've flash PureNexus with ElementalX to see if that would make a difference. I haven't been using it long enough to say one way or the other.
Click to expand...
Click to collapse
I'm also on Elemental X kernel with slightly overclocked cpu. Does the freezing/rebooting take place while in idle?
mngdew said:
I'm also on Elemental X kernel with slightly overclocked cpu. Does the freezing/rebooting take place while in idle?
Click to expand...
Click to collapse
I flashed PureNexus on Friday and used its default kernel over the weekend without any troubles. I've only now flashed Elemental X this morning. Time will tell, I guess!
Edited to add: When I was on the stock rom and kernel, it was freezing while I was using it, requiring me to restart the phone. I would also go to use it after it had been asleep for a while, only to have it do the "Android is Starting" thing. So yes, it was restarting at idle as well as when I was using it.
rft183 said:
I flashed PureNexus on Friday and used its default kernel over the weekend without any troubles. I've only now flashed Elemental X this morning. Time will tell, I guess!
Edited to add: When I was on the stock rom and kernel, it was freezing while I was using it, requiring me to restart the phone. I would also go to use it after it had been asleep for a while, only to have it do the "Android is Starting" thing. So yes, it was restarting at idle as well as when I was using it.
Click to expand...
Click to collapse
Well, I guess the problem with my phone was unrelated. It completely died yesterday afternoon. I'm doing the RMA thing with Google now.
I started having this issue with Android O
I have unlocked version.maybe an app, I'm going to do a reset
rft183 said:
I seem to be seeing a lot of people complaining about the issue. It's been an issue with the Pixel since the beginning, apparently, but it seems to have gotten worse with the May update.
With that said, I did make another change around the same time... I had switched from Project Fi to a Verizon MVNO, and so I flashed the Verizon system image (from the Google Factory images page) rather than the standard one, since it supposedly had some Verizon-specific fixes.
Click to expand...
Click to collapse
Well, after getting the phone back reloading the stock image and re-rooting it, I went into developer options and turned off ota updates. So, hopefully I don't get that update... even though root doesn't allow to update. Just causes annoying update prompts.
Related
I'm on the verge of buying a Nexus S but I am now reading about many freezing issues where the phone loses all responsiveness after the backlight goes out on occasion - the only solution being to pull the battery and reboot, only to have it happen again.
This thread shows that some people are returning their phones to Samsung and are seeing a fault diagnosis of 'bad BGA' and a fix of 'PBA replaced'
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
BAD BGA COMPONENT
WARRANTY, REPLACE PART
Solution:
Replaced PBA
Passed All Functional Testing
Just how wide a problem is this, is it something that will affect pretty much everyone at some point or are these cases failry isolated?
edit: I am buying from someone who has this phone on contract so I am wondering also if I will be able to get support from Samsung should I run into this problem. Are warranty issues dealt with by Samsung direct or are they passed through the carrier when originally obtained on contract?
Any thoughts?
never experienced any of these problems. you have a 30 day return policy (maybe less now)
zephiK said:
never experienced any of these problems. you have a 30 day return policy (maybe less now)
Click to expand...
Click to collapse
Unfortunately not, see my edit above.
Also, it seems users are running into this problem after owning the device for a while, taking them beyond their 28 day / 30 day return
i've had mine since it was first available and never had any problem like this.
I've also never seen this.
milkham said:
i've had mine since it was first available and never had any problem like this.
Click to expand...
Click to collapse
same. ive had it maybe like a 1.5 week after release date
It happens to me if i mess around with custom kernels and o/c speed but so far if i use netarchy's stable CFS, it'll be fine. No freezing and having to pull my batt.
It happens if i use hornity or some BFS kernels. Haven't tried Jame Bond yet to test it out.
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
AllGamer said:
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
Click to expand...
Click to collapse
the thread the OP linked is Nexus S
only time that has happened to me is when i overclock to 1.4 ghz and the phone can not handle it
Ok, it's encouraging that this isn't affecting everyone but still a bit worrying.
AllGamer said:
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
Click to expand...
Click to collapse
Wrong - as zephiK has pointed out, the link is to a whole load of people having issued with the Nexus S, NOT the Galaxy S.
I believe the most problems with smartphones are in software, not hardware. And software could/should be patched/updated.
and this is one of the reasons that preventing me from walking into cpw and buying it tomorrow.
I am Having this exact issue with my phone. it is unusable the phone freezes every 20 minutes. Hope Samsung finds a fix for this soon.
I just got my nexus s the other day but I haven't had any freezing either I hope those with the issue get it sorted out though
loading another ROM would help, or perhaps it might be a hardware issue, in which case, take it back for an exchange
AllGamer said:
loading another ROM would help, or perhaps it might be a hardware issue, in which case, take it back for an exchange
Click to expand...
Click to collapse
Happens in stock rom, and many other custom roms too. So I dun think its the rom problem
oh dear, this is exactly what I'm concerned about. Any pattern as to which are affected by this, ie just slcd or just samoled? Only a thought.
I shall soon receive my second nexus s and I really don't want to have this problem!
I'm using the i9023 if that info helps.
Yes thanks but it's not what I wanted to hear as the chances are that this is the one I will receive.
I've heard of people reporting successfully fixing this with a full reflash, others say it's a hardware issue.
Keep us posted.
My wifes Moto G occaisionally crashes and reboots. It hasnt happened very often but I would like to know if it is happening to anyone else and if they know the cause? Maybe it's a bug that will be sorted with a future software upgrade?
The same is happening to me right now, I'm running 4.3. Sometimes it becomes very annoying; I already contacted Motorola through, they're supposed to call me later today...
I hope that KitKat solves this issue because I don't want to root yet.
vrsk said:
The same is happening to me right now, I'm running 4.3. Sometimes it becomes very annoying; I already contacted Motorola through, they're supposed to call me later today...
I hope that KitKat solves this issue because I don't want to root yet.
Click to expand...
Click to collapse
Ah so it's not just us then. I hope that an update will cure it as I doubt that my wife would let me root her phone. Will be interesing to see what Motorola say.
ahardie said:
Ah so it's not just us then. I hope that an update will cure it as I doubt that my wife would let me root her phone. Will be interesing to see what Motorola say.
Click to expand...
Click to collapse
Mine even reboots during the start-up animation, it has become so annoying. A shame since it is a great device
I'll report with the results later.
vrsk said:
Mine even reboots during the start-up animation, it has become so annoying. A shame since it is a great device
Click to expand...
Click to collapse
That must be really annoying. Luckily ours isn't that bad.
vrsk said:
I'll report with the results later.
Click to expand...
Click to collapse
Cheers.
Same issue here. Got the device, (US GSM) on Dec. 14th, and had it happen a couple of times. I didn't think anything of it, because this phone is for my son, and I was trying out parental control stuff on it. I wrapped it, and it sat under the tree till the 25th, which is when I updated it to 4.4, and the crashing has gotten worse. I get random app crashes, and more reboots now than ever. I cleared the partition cache, which didn't work. I am going to try a factory wipe and see if that fixes it, but I honestly doubt it. Moto chat told me to call in the morning to talk to a level 2 tech.
So, there seem to be a few of us, but I didn't see anything on their support forums....
llyenn said:
Same issue here. Got the device, (US GSM) on Dec. 14th, and had it happen a couple of times. I didn't think anything of it, because this phone is for my son, and I was trying out parental control stuff on it. I wrapped it, and it sat under the tree till the 25th, which is when I updated it to 4.4, and the crashing has gotten worse. I get random app crashes, and more reboots now than ever. I cleared the partition cache, which didn't work. I am going to try a factory wipe and see if that fixes it, but I honestly doubt it. Moto chat told me to call in the morning to talk to a level 2 tech.
So, there seem to be a few of us, but I didn't see anything on their support forums....
Click to expand...
Click to collapse
So far I've had a single instant reboot in the camera app. Hope it doesn't get worse.
The phone is still rebooting sometimes. Is there any way I can check why it is happening like something that will create an error log? Or does anyone have any tips for stopping it happening? It is a very minor nuisance at the moment but I'm afraid it might get worse. Especially if it is a problem with the hardware rather than the software.
I have a UK moto g and it hasn't rebooted on me yet the past week I have had it
Sent from my XT1032 using xda app-developers app
I've got the International 8 GB version from Koodo and it hasn't rebooted since I started using it full time on Dec 28. It remains powered up 24/7.
Often these reboots and crashes are user app related, it may be a good idea to data factory reset the phone and see if the issue remains.
Undervolting the cpu may cause these issues too if you undervolt too much.
I have 120 apps installed and had no crash/reboot so far in the 3 weeks i had the phone.
I have same trouble. My device is crashing and rebooting sometimes at day. Is there any solution??
Moto g purchased in mexico, telcel.
Guys, return it to your phone dealer if you can. Waiting for a fix(that may or may not come) will just increase your pain. If the service center spots the restart, they should definitely repair/replace your phone.
gee2012 said:
Often these reboots and crashes are user app related, it may be a good idea to data factory reset the phone and see if the issue remains.
Undervolting the cpu may cause these issues too if you undervolt too much.
I have 120 apps installed and had no crash/reboot so far in the 3 weeks i had the phone.
Click to expand...
Click to collapse
Yes it could be but I think it's most likely Android OS or Motorola's own certain app that's causing this. My device resets so frequently that's it become impossible to use, unbelievably it reboots every 5-10min, even when I leave the phone on standby I see it rebooting it self.
It's no just specific app that I use, it has rebooted while I'm browsing (Google Chrome), in Gallery app, on Play Store and also when I was transferring images from pc to the device!
Motorola Chat support are useless, they just game me links to Moto UK Support contact, that's it. Not much of advice.
So I will be taking it back to Phone4u store and possibly get it replaced if they can.
Kit kat seems to have fixed problem.
dankerk said:
Yes it could be but I think it's most likely Android OS or Motorola's own certain app that's causing this. My device resets so frequently that's it become impossible to use, unbelievably it reboots every 5-10min, even when I leave the phone on standby I see it rebooting it self.
It's no just specific app that I use, it has rebooted while I'm browsing (Google Chrome), in Gallery app, on Play Store and also when I was transferring images from pc to the device!
Motorola Chat support are useless, they just game me links to Moto UK Support contact, that's it. Not much of advice.
So I will be taking it back to Phone4u store and possibly get it replaced if they can.
Click to expand...
Click to collapse
My wifes phone seemed to be getting worse. It rebooted four times the day before yesterday. It always seemed to be worst when we were travelling.
Yesterday morning the Kit Kat update became available. The phone hasn't rebooted since. Hope I'm not speaking too soon but fingers crossed it seems to be fixed.
We got 2 Moto G's in our family (one for me, one for my father), both ordered from Amazon.de as 8gb version (XT1032)
I haven't seen any reboots on one of these devices. They both got updated to 4.4.2 yesterday and also no crashes.
Has anyone found out what is causing the crashes? Is it maybe even a hardware failure?
creambyemute said:
We got 2 Moto G's in our family (one for me, one for my father), both ordered from Amazon.de as 8gb version (XT1032)
I haven't seen any reboots on one of these devices. They both got updated to 4.4.2 yesterday and also no crashes.
Has anyone found out what is causing the crashes? Is it maybe even a hardware failure?
Click to expand...
Click to collapse
If the Kit kat upgrade has cured the problem on my wifes phone then it must have been software related. Possibly an app I had downloaded was causing it. It's worth pointing out as well that most people didn't seem to have this issue.
BTW I spoke to Motorola chat a few days ago using the help app. on the phone. They told me it was probably an app I had downloaded causing it and a factory reset would sort it. Installing the upgrade seems to have done the same thing though.
Happy to hear it's not something hardware related.
I even had reboots with my nexus 5, 4 on random basis (not often). Must be some sort of app I've had installed on all my devices
I received mine in december (from Amazon [Retail.FR]) and experienced some crashes (almost every day).
I installed KitKat on it and did two factor resets to be sure it was not software related issues. Since then, a week ago, I experienced a crash every day and half (screenshot). Crash happened without any reason or specific context.
My serial number is: TA8900B6##
I decided to return my Moto G to Amazon and buy a new one.
I'm experiencing the same and I decided to try to run a constant logcat in the background to see what's going on. Also is there any way to have a constant recording with dmesg? I'm no linux commands expert.
For logcat (in terminal emulator) I used logcat > sdcard/logcat.txt which is growing in size as far as I can see. Hopefully this brings some news.
Good luck everyone.
Cheers
Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
starslab said:
Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
Click to expand...
Click to collapse
Try without encryption. It's hardly useful and only causes issues on Android.
Lethargy said:
Try without encryption. It's hardly useful and only causes issues on Android.
Click to expand...
Click to collapse
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
starslab said:
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
Click to expand...
Click to collapse
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Lethargy said:
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Click to expand...
Click to collapse
CyanogenMod has Privacy Guard, which is another feature I'm using, mostly with the aforementioned WhatsApp!, which has a list of permissions longer than my arm. I don't like it, but I need it for work.
I'll grant that the custom Recovery and ROM may slightly weaken the encryption (specifically an attacker could alter the ROM from Recovery), but even so having the encryption makes the phone a million times more resistant to data theft and tampering than not having it. It's worth noting that tweaking the ROM is the _worst_ an attacker could do. If I suspected such a thing had happened I could re-unlock the bootloader (which would wipe my data), and re-flash a known good Recovery and ROM. I'd lose my data, but even if the attacker had dumped the partition they still wouldn't have my key, and my data would still be private.
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
its more then likely the encryption. Disable it, re-flash and see what happens
No encryption. Wiped and trimmed the phone yesterday, now 4 crashes.
Try another ROM, see if it crashes. If it still does, flash factory images and see if it still does.
If so, RMA.
Nothing but trouble for me since upgrading to m9. I have been using the various M builds since March with no problems. M8 was fine. No device encryption for me. I tried turning it on and instead got stuck redoing the whole phone.
Now I get frequent crashing. I switched to the most recent nightly yesterday. Apps stopped crashing. However the os itself still crashes. Several times the screen wouldn't turn on after removing it from my pocket. The light was blinking so it definitely didn't just turn off. It also has stayed black after a few (but not all) phone calls. I've had to hard reset every time to recover.
Thinking about reverting to m8 backup. Willing to give it a few more nightie and see if it works out.
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Got it from the OTA update. Unfortunately I'm not experienced enough to know how to debug it or use proper logs. It could be that its an app I'm using combined with the most recent update...
Im using M9 snapshot too and i have not had 1 problem its been excellent
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
+1. I installed another kernel (Chaos) for that reason and it's way faster.
OP: Maybe a bad flash? I would download M8 latest stable snapshot, and do OTA upgrade to M9. That's how I got mine.
C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
Thanks for the suggestion. I actually have been using elemental and forgot to install it after the OTA. Will put that on now and see if it helps.
starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
simms22 said:
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
Click to expand...
Click to collapse
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Sent from Tapatalk on Nexus 5
last four hours have been fine since adding elemental. Hopefully works in the long run. 8/18 nightly.
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Click to expand...
Click to collapse
What roms do you think are more stable than CM at this time?
trobbs said:
What roms do you think are more stable than CM at this time?
Click to expand...
Click to collapse
Just about any
So since about 2 days ago the phone just start freezing. Sometimes it just restarted randomly, but mainly freezing at least every 5 minutes. The power button alone wouldn't turn it off no matter how long I held it. Always have to use Pwr+Vol Down to reboot.
I put up with it because I've been busy, but finally tried wiping cache - no profit. Tried safe mode - no profit. Factory reset- negative profit. After the reset it just seems to restart a bit more often but in general it freezes less, making the timing seem even more random.
This happened when I first got it (used). It was restarting due to the fresh 7.0 update. So a factory reset fixed it and it was smooth sailing for like 3 months or something. I know there was a minor system update a few days ago but those dont usually call for a factory reset. I tried it anyway and it just didnt work. I had actually even tried uninstalling all the app updates from the night before it started happening. but safe mode couldn't even fix the problem so I guess that was moot.
Software version: G920VVRS4DQE1
Stock everything - I dont hack my daily drivers at all
Android 7.0
Mainly I'd like to know if Im alone. A fix would be great but I'm hoping it's not specific to my device. If it's a hardware issue I'm gonna give it a swift toss down the stairs and maybe deliver a nasty curb stomp to it right afterward.
Any advice?
I'm running into the same exact issue. Same build, and am running out of ideas.
Lathorus said:
I'm running into the same exact issue. Same build, and am running out of ideas.
Click to expand...
Click to collapse
Good to know its not just me. Did it start after a recent update for you also? That would give me hope that its not faulty hardware. Maybe just a bad update.
sawyerbenjamin said:
Good to know its not just me. Did it start after a recent update for you also? That would give me hope that its not faulty hardware. Maybe just a bad update.
Click to expand...
Click to collapse
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Lathorus said:
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Click to expand...
Click to collapse
Same for Verizon. I guess I'll just hold out, using a backup phone, until a new update hopefully fixes it.
Lathorus said:
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Click to expand...
Click to collapse
Gonna go ahead and revive this. It seems to work fine when the sim card is out. I recommend you see if it's the same with you. I've charged it up before work multiple times before work days and come home from to see that it never restarted. I was able to test this using the fingerprint feature; it isn't asking me to use pattern like it does after boot.
No one else is chiming in but, since we're both on Verizon, I'm having a feeling that it's directly related to the SIM/carrier.
Like the title says, about 2 times a day when I let my phone sit without being used it will turn completely off and only will turn on when I hold the power and volume buttons and it goes into fast boot mode and I can start it up that way and then everything is fine.
Rooted magisk
Edposed framework
Elementalx kernel
Stock oos rom
twrp
Rboard
Joneplus tools
Adaway
Ifont
Gravitybox
And no crazy settings besides keeping elementalx set on performance mode all the time
Any ideas as to what is wrong here?
I've had this same issue. I'm not rooted. The phone will be in my pocket and just randomly shut down. When I pull it out to turn it on, it won't turn on the normal way. I have to hold volume up and power for 15 seconds to get it on. It's happened 3 or 4 times to me in the last week. I've had the phone since day 1 and had no issues until about a week ago. Plugging in the charger doesn't seem to fix it. And it's happened to me in the morning when the phone has been fully charging all night. I just uninstalled a bunch of apps to see if something wonky was going on. Could be an issue with the latest system update?
spart0n said:
Like the title says, about 2 times a day when I let my phone sit without being used it will turn completely off and only will turn on when I hold the power and volume buttons and it goes into fast boot mode and I can start it up that way and then everything is fine.
Rooted magisk
Edposed framework
Elementalx kernel
Stock oos rom
twrp
Rboard
Joneplus tools
Adaway
Ifont
Gravitybox
And no crazy settings besides keeping elementalx set on performance mode all the time
Any ideas as to what is wrong here?
Click to expand...
Click to collapse
I think kernel is the culprit
RISHI RAJ said:
I think kernel is the culprit
Click to expand...
Click to collapse
Ok so completely remove it or change settings what should I do?
RISHI RAJ said:
I think kernel is the culprit
Click to expand...
Click to collapse
I flashed Smurf kernel and I'll see what happens.
Elementalx was my first kernel, there was an app to manage it, does Smurf have that? I can't find it
if u look at post2 this person is not rooted
so i dont think that he has custom kernel either
an his phone also turns off
so maybe its software
I don't think its software, Maybe
A hardware issue, It'll be more clear when Op will post results
I had been experiencing the sleep-of-death issue on a daily basis some time after I converted my TMobile unit to International. I suspect it to be software related so 2 days ago, I went back to OOS 9.5.3 via the MSM tool and did not root or unlock bootloader. I have not had the SOD issue since so today, I went ahead and updated to 9.5.8 via OTA and will leave it as is for another 2 days. If all is well, I will do each root process step every 2 days in hoping to narrow down what exactly is causing the issue.
I have same setup as u accept xposed and gravity ..... Elemental is and has been running great
So far with Smurf kernel I've had zero sleep of deaths. The only difference I've noticed with Smurf vs elementalx is the phone gets much hotter under intense loads and doesn't thermal throttle as much but when the load stops it cools off rather fast
I had my first sleep of death with Smurf 1.7.2
Crazy as it is very balanced. Replaced ElementalIX recently.
Se7eN43 said:
I had been experiencing the sleep-of-death issue on a daily basis some time after I converted my TMobile unit to International. I suspect it to be software related so 2 days ago, I went back to OOS 9.5.3 via the MSM tool and did not root or unlock bootloader. I have not had the SOD issue since so today, I went ahead and updated to 9.5.8 via OTA and will leave it as is for another 2 days. If all is well, I will do each root process step every 2 days in hoping to narrow down what exactly is causing the issue.
Click to expand...
Click to collapse
I will be posting updates in the thread linked below. This issue started being discussed a while back with rooted and non rooted users reporting their SOD experiences.
https://forum.xda-developers.com/oneplus-7-pro/how-to/poll-phone-randomly-powered-off-t3940427/page8
I've had NO sleeps of deaths or any unexpected restarts for several days now after switching to Smurf kernel
I just saw an Article on AndroidPolice that OnePlus is aware of the issue and will be fixing it soon.
https://www.androidpolice.com/2019/...cting-some-oneplus-7-pros-will-soon-be-fixed/
I am using ElementalIX kernel and met this problem two times. Waiting solutions.
einverne said:
I am using ElementalIX kernel and met this problem two times. Waiting solutions.
Click to expand...
Click to collapse
Try using a different kernel. I think that was my issue. I was going to change/uninstall 1 thing at a time and I started with my kernel and then it never happened again so I think it was my kernel
Currently facing this issue. Often. Switched to a different kernel. Nothing same.
Pvt WhoOkid said:
Currently facing this issue. Often. Switched to a different kernel. Nothing same.
Click to expand...
Click to collapse
Revert back to stock kernel until OnePlus addresses the issue.
Se7eN43 said:
Revert back to stock kernel until OnePlus addresses the issue.
Click to expand...
Click to collapse
I see their rolling out 9.5.10 hopefully it solves this.