Related
need some help it just reboots randomly and is getting quite annoying :/
toxicpaulution said:
need some help it just reboots randomly and is getting quite annoying :/
Click to expand...
Click to collapse
With all the great info you provided I am sure someone will be able to help
well i read earlier that someone had problems with the android.process.media has stopped... thats the problem about after a minute of it pooping up my phone just resets. no need to be a **** about it
Without info you aren't going to get any good help. A rebooting phone could be caused by many issues. So far you have given us an error. This is still very little to go on. And now since you resorted to name calling I doubt you will get much help.
toxicpaulution said:
well i read earlier that someone had problems with the android.process.media has stopped... thats the problem about after a minute of it pooping up my phone just resets. no need to be a **** about it
Click to expand...
Click to collapse
That error could be cause by no less then 100 different things. Welcome to a development site. You have to provide all the needed info before we can help. With the info you gave me I would suggest to flash to a stock rom and stay there until you understand a little bit more about what your doing. I see no rom, radio, ril, mods, recovery, it flashing info at all.
zelendel said:
That error could be cause by no less then 100 different things. Welcome to a development site. You have to provide all the needed info before we can help. With the info you gave me I would suggest to flash to a stock rom and stay there until you understand a little bit more about what your doing. I see no rom, radio, ril, mods, recovery, it flashing info at all.
Click to expand...
Click to collapse
That's what i was thinking, but i was accused of flaming by a guy in the Captivate forums today, so i bit my tongue
i just flashed the absolution rom and it again crashed on me and i did wipe the cache and system before installing the custom rom.
and it reboots in the middle of typing or on standby >.< it is quite irritating to be honest
Rebooting
This is caused with a bad flash, radio/ril mismatch, and other programs that have been reinstalled from a backup. I would also suggest re-flashing to a stock rom, and see if it still does it, and if not I would look at getting a new rom. You also can reinstall the one you are running and then add the apps back one at a time to see if it is generated by them. Also I suggest going back to the dev thread and make sure you have the correct radio-ril combo. Search-Research and you will find the root cause.
toxicpaulution said:
and it reboots in the middle of typing or on standby >.< it is quite irritating to be honest
Click to expand...
Click to collapse
The absolution Rom was having some issues with battery and themes tweaks in the absolution tools. If you happened to change any of those that is probably the problem.
Random Reboot
well instead of starting a new thread I'll tap onto this one. I am also experiencing random reboots. My phone will reboot regardless if you are using it or not.The reboots can be as far apart as a couple of days or as frequent as 4 times a day. I am running a stock Gingerbread OS.(AT&T) The phone is not rooted. The phone is as stock as possible. The only apps on the phone are the ones that are pre-loaded by AT&T. I have changed the battery with a new OEM HTC battery. I replaced the SD card. I have also replaced the battery door.
Any ideas would be greatly appreciated.
Thanks
Its the battery. I had mine reboot at 96% and 48%. Replace the battery.
Sent from my Inspire 4G using xda premium
I changed the battery twice
My phone has an issue where it restarts about every five minutes. I have had a warranty replacement through my carrier, and I have done clean installs of the ROM through CWM every time I wipe the phone.
I had this same issue with Sabsa 4/4.1, and don't know yet if it's due to an app. I just did another clean install, and over the next several days I'm going to download non-vital apps (the vital apps *have* to go on there today, obviously, once the phone is wiped and redone) to see if it starts doing this again. In the meantime, since I couldn't find a similar issue anywhere on the forum nor in the dev thread, I wanted to ask here.
I install a pretty large number of apps, I will admit, and while this hasn't been Sabsa-specific, I think all the ROMs I have tried used the same or a similar kernel.
The apps I consider vital are:
imo
jorte
Google voice
avast
llama
SwiftKey (paid)
Dropbox
Skyvi
Before you respond, please do not tell me to try a battery pull, formatting my phone and reinstalling after a wipe, or wiping the cache/Dalvik/battery stats. These are all things I have done in varying orders. Has anyone else had this issue, and how did you resolve it? Is it one of my vital apps that I listed above? If it is that, please recommend a replacement.
ashlaye said:
My phone has an issue where it restarts about every five minutes. I have had a warranty replacement through my carrier, and I have done clean installs of the ROM through CWM every time I wipe the phone.
I had this same issue with Sabsa 4/4.1, and don't know yet if it's due to an app. I just did another clean install, and over the next several days I'm going to download non-vital apps (the vital apps *have* to go on there today, obviously, once the phone is wiped and redone) to see if it starts doing this again. In the meantime, since I couldn't find a similar issue anywhere on the forum nor in the dev thread, I wanted to ask here.
I install a pretty large number of apps, I will admit, and while this hasn't been Sabsa-specific, I think all the ROMs I have tried used the same or a similar kernel.
The apps I consider vital are:
imo
jorte
Google voice
avast
llama
SwiftKey (paid)
Dropbox
Skyvi
Before you respond, please do not tell me to try a battery pull, formatting my phone and reinstalling after a wipe, or wiping the cache/Dalvik/battery stats. These are all things I have done in varying orders. Has anyone else had this issue, and how did you resolve it? Is it one of my vital apps that I listed above? If it is that, please recommend a replacement.
Click to expand...
Click to collapse
Have you tried running the phone plugged into power without a battery? Is there any ROM on which the problem doesn't present itself? Are you overclocked?
bananagranola said:
Have you tried running the phone plugged into power without a battery? Is there any ROM on which the problem doesn't present itself? Are you overclocked?
Click to expand...
Click to collapse
1. No, I honestly didn't know it could do that. If it starts happening again I'll try that first.
2. Not that I've found. That said, I've only been using Sense 4 and 4a ROMs. The ones I've specifically tried so far are Sabsa (of course), ICESense, Black Impulse, and Virtuous.
3. No. I don't even overclock my computers. Too little gain for too much wear on the hardware.
Something else that I just thought of that I have seen other people tell users in the dev thread: Yes, I do have S-OFF.
ashlaye said:
1. No, I honestly didn't know it could do that. If it starts happening again I'll try that first.
2. Not that I've found. That said, I've only been using Sense 4 and 4a ROMs. The ones I've specifically tried so far are Sabsa (of course), ICESense, Black Impulse, and Virtuous.
3. No. I don't even overclock my computers. Too little gain for too much wear on the hardware.
Something else that I just thought of that I have seen other people tell users in the dev thread: Yes, I do have S-OFF.
Click to expand...
Click to collapse
For #2, give the latest (rooted) stock ROM a try if #1 fails. Obviously, Nandroid back up your current ROM first.
I never had a random reboot on ICS now on JB I'm having it at least once a week...not a lot, I know but still something is not right. The last time this happened I tried looking further into it and the only thing I see that may be causing the issue is signal loss. I am 100% stock and have maybe 25 downloaded apps, if that. Is there an app for STOCK that will backup some of my data? I really don't think a factory reset will help but I'll give it a shot. Any other ideas? I freaking love this phone and this is my only complaint....would love to fix the problem. Thanks.
Here's a shot of the signal before the reboot.
Is it worth trying a factory reset? I feel the chances of it doing any good are very slim. Switch to a different modem?
Sent from my SCH-I535 using xda premium
I'm having the same issue, and a reset did not help.
Sent from my SCH-I535 using xda app-developers app
Thanks for the reply. As long as it does not get worse it's not a huge deal. Maybe the next update will fix it?
Sent from my SCH-I535 using xda premium
Not sure what the right word is (hotboot?) but today my phone rebooted (not fully) while I was using it. No fc's or freeze ups, just the reboot. I'm currently on the no wipe leak which ended up being the official ota.... Since the no wipe was modified would it make any sense to install the full wipe version to see if the problem is resolved?
Sent from my SCH-I535 using xda premium
Flashed full wipe via Odin. In case anyone else has this problem I will post back with results in a week or so.
Sent from my SCH-I535 using xda premium
I'm having the same issue. It seems that something is causing JellyBean-enabled SGS3's to just jump into "interrupt heaven". It's always a quick boot, never resets the "Up time" counter, and only takes a few seconds to get back to normal, but it's a real pain in the arse!
Any ideas what the culprit is, guys? I'm running a newly replaced (ordered it on January 2nd and the first thing it does was download and upgrade to JellyBean "VRBLK3" before I could even start get it loaded, basically as soon as I activated the phone, it started to download the OTA before I could even get to anything else). I know in my case I have a couple of mods installed - maybe one or more of these is common amongst those of us having issues? I have the "4x5 scrolling" mod and the "BLK3 Logo fix" mod that removes the stupid VZW drum-beating and pulsating display on boot-up. Other than that, my phone is rooted (using method involving loading the older ICS bootchain so you can install the latest CWM recovery), has CWM Touch 6.0.2.3 and that's about it, other than your usual rooted toolkit programs. Anything common to the rest of you?
Oh, by the way - I've already tried reformatting the cache, blowing away the dalvik cache and even a complete factory reset, which seems to make it less jumpy, but it always comes back within a day or two if not just a few hours.
I had the same problem with mine rebooting when I had very bad signal. Last Friday I did a factory reset then Odin to 4.0.4 and let the phone update to 4.1.1 and the problem seems to have gone away. I am not willing to call it cured yet, but it hasn't rebooted since. This went from where I was rebooting constantly all day long at work and when on the road in bad signal areas.
So far so good.
By the way, I looked EVERYWHERE and couldn't find anyone complaining of this earlier so I figured it had to be a bad download of the update.
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Factory reset (and everything else) - it still reboots
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
ratledge said:
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
Click to expand...
Click to collapse
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Ryno77 said:
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
New SIM?
SlimSnoopOS said:
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
Click to expand...
Click to collapse
Well, unfortunately I've done that - twice in the past ten days, the latest one came Tuesday afternoon. No change, still just reboots while I'm not even using the phone, and it's not the phone, it's the software. I can't say for absolute certain that it is in the VRBLK3 / JB code, but I can say for sure it _is_ something I am running, but the fact that it does reboot in safe mode indicates it's not anything downloaded or added to the base system as shipped.
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
6 Pebble Blue 32MB phones in about 8 months
jaymattt said:
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
Click to expand...
Click to collapse
Heheh... Well, I got one on "day 1" by pre-ordering it from Verizon, after two months the power button fell off. They sent me a "CLN" one, it lasted ten days and started randomly rebooting (even if reloaded with 'virgin' unrooted OS), the third (another "CLN") was delivered with no power button and the volume rocker fell off while I was taking it out of the box. At that point, I got kind of pizzed and did the 'good customer for 10 years' and elevated it through three levels until I finally got them to ship me a brand new one. That one lasted two months until my wife left it on top of my car and I backed over it in my driveway. I used my Asurion (insurance) to get #5, which arrived rebooting from the moment I started it up. Within a few days after monkeying around with their tech support (they ain't the brightest bulbs - instructions include "remove the battery and dial yourself and hit the 'Send' key three times" - not kidding) I managed to get #6 shipped out, and it's first act of life was to suck down the VRBL3 (Jellybean) software update and I've mucked around with it for two weeks, tried loading it with various combinations of "No Wipe" and "Factory Reset" versions of VRBLK3, removed a bunch of programs I've had installed but never really used and it still just vibrates about once an hour (and it's totally random, sometimes lasts 6 hours, sometimes 6 minutes before rebooting), jumps to the "warm/quick start" and recycles without resetting the "time up" counter. I'm thinking it's something I fed it (i.e. a nasty program or interaction between programs) - but I've come up empty-handed so far as running it to ground.
Does anyone have any knowledge of known interactions or "bad programs" that just don't play well together under JB?
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, normally - I would agree. But this makes three phones that act exactly the same in a row. The first of which was my 2nd "New" GS3, updated OTA to Jellybean - which immediately started the rolling reboots. The problem with the "CLN" phones are that they were all defective in one way or another, or they wouldn't be recertified. I don't really think VZW does a good job recertifying these phones, there are just too many of them coming out every single day, and - lord knows Asurion probably is behind that curve. :silly:
All three phones have been identical in their behavior - "down to the letter" since VRBLK3 was released. :fingers-crossed:
Question: now that I've used my insurance, do I _have_ to go back to Asurion for replacement, or since I'm still in my first year, will VerizonWireless entertain sending me another? It seems like reading the information that comes with the Asurion phones, they are the ones that are now guaranteeing my phone for a full year from the time it was sent (that would be this past Monday).
The phone has an Asurion sticker inside it, not a VZW one...
And the winner is: battery replacement. Every single VZW marked battery causes it to reboot, but a plain old Samsung battery (made in Korea - I've noticed almost all the VZW branded SKUs are made in China) works 100% and gives me an average of 12 hours moderate usage. The batteries I had from previous phones, VZW and Asurion all have the Verizon markings on them, and every single one of them causes it to reboot. This new one I got today straight from Samsung does not.
Curious, huh? I have one out of five batteries with VZW markings, and it does the same as the other four "made in China" ones. You've gotta wonder...
Glad you found a fix. Is it possible the new battery is slightly larger? Wondering if the old batteries were maybe a bit loose.
Sent from my SCH-I535 using xda premium
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.