I was running fine all last week but yesterday and today I have picked my phone several times and it has been frozen. Black screen of death I guess you could say.
Has anyone else seen these issues after appying update.zip or completely flashing? I cleared my cache and applied update.zip but if no one else is having the issue after flashing I will probably just do that to make sure it is super clean. I just hate losing all my apps/config.
Thanks.
Related
I'm running DamageControl 2.07.
I happened to be up in the middle of the night, and I caught my phone randomly restarting. I've seen it happen before but didn't pay it any mind before, but now this is starting to bother me.
Is anyone else experiencing this?
I have this too. Running DC 2.07.2 and when I'm doing something normal (tweeting on Touiteur, texting, etc.) and the phone doesn't actually reboot, it just..... shuts off. This happens at any battery level from 100 to 0. I turn it on and it's fine, but.... it's really annoying.
Yep i experienced this with all the new Rom base on DC. i dont really know how to fix but changing to an other Rom will fix it. The problem is almost all the new 2.1 Roms that came out are base on Dc so i flashed DarchLegend 5.0.5 and its been 3 days and my phone hasn't done that yet
noticed this too when running regaws mod. flashing darch now with the darchstar theme, gunna give it a go.
anyone know of a white taskbar(with 3g) for darchs latest rom?
I've had this happen to me even with stock 1.5, lol.
I don't know what causes it, it's a pain in the ass. It happened a few times after I rooted too. Lately I haven't had this problem anymore.
my phone rebooted on its own last night, second time thats happened. there was talk of this about 2 weeks ago and the thought is this is a battery issue, apparently a couple people bought new batteries and the rebooting didn't happen after.
Alright this is starting to really bother me now. It's rebooting like 3 times a day now. I keep thinking my phone is hacked.
It's happened to me before on 1.5... I was going to charge my phone overnight while I slept, and no matter what I did, I couldn't keep the damn thing to stay off. Everytime I kept plugging it in, it would just turn on again. Eventually I just pulled the battery, put it back in, and plugged it in and stayed off.
this is the first thread i read upon my return from being banned for 7 days. this sh*t scared the living f*ck outta my a**
ahem
sorry
it happened to me right after i installed the latest regawmod
i simple wipe and fresh flash fixed the issue immediatly
i also pulled my battery, and my nandroid was corrupted
i was scared. i was like damn, 7 says and i come back to this?!
Okay; so last night I unplugged my phone at 100% right as I went to sleep. I do this on a regular basis so nothing new.
I wake up this morning to my phone being turned off/dead. I attempt to turn it on after plugging it into the wall..and it got stuck on the boot logo and would vibrate in short bursts.
Weird; because I haven't flashed anything in a few weeks and everything seemed stable.
I pull the battery and reboot the phone..seems to work.
But as the phone powers on; the screen to log in to my account pops up to restore my data etc etc..
And guess what happens next? Force closes for every app I have install..no structural fc's.. just happens when I try opening ANY app installed.
I did try running Dolphin Browser through the phone's cache and moving the cache to my SD Card. Didn't work with it in the phone; but moving it to SD card allowed it to work for a bit then it crashed.
I fixed it by re-flashing the current rom i was running. I am running ext4; was posting to see if anyone has come across this?
What rom were you on?
Sent from my Evo Killer!
I haven't seen or heard of this before but I would suggest a fresh install. Odin back to stock dk28 and redoing everything the manual way. It's a ***** but dollars to donuts it fixes your problems.
Sent from my ext4 Epic 4G running Bonsai4all 1.1.3!
Been running midnight 2.2 for a while now. And it supports ext4; before you shoot that down
@kenvan I already fixed the issue; I was just seeing if anyone else ran into this..and to try and find out what caused it. Wish I was home so I could of gotten a logcat :/
This morning I noticed my phone getting very hot in my pocket. A quick check of gSam showed the phone temp at 105°. Battery had dropped from 100% to 60% in under two hours with no use. When I checked app usage mm-camera-daemon was running at 89% usage. I booted to recovery and wiped cache and that stopped it. Did a Google search and found that this was a bug with 4.4.2 and was fixed with 4.4.4. Now there are lots of posts on various forums about people having this problem with 5.0. It is the process that runs the camera and it apparently gets stuck running after using the camera or if any camera related apps are used. Clearing the cache fixes it, but I'm reading in different places that it may start again within a few hours. Just wondering if anyone else here has experienced this yet.
newmanx4 said:
This morning I noticed my phone getting very hot in my pocket. A quick check of gSam showed the phone temp at 105°. Battery had dropped from 100% to 60% in under two hours with no use. When I checked app usage mm-camera-daemon was running at 89% usage. I booted to recovery and wiped cache and that stopped it. Did a Google search and found that this was a bug with 4.4.2 and was fixed with 4.4.4. Now there are lots of posts on various forums about people having this problem with 5.0. It is the process that runs the camera and it apparently gets stuck running after using the camera or if any camera related apps are used. Clearing the cache fixes it, but I'm reading in different places that it may start again within a few hours. Just wondering if anyone else here has experienced this yet.
Click to expand...
Click to collapse
I would suggest checking to make sure you have Smart Stay turned off; it's not a complete solution but it eliminates a way the camera can turn on without you having directly initiated it. Since Smart Stay uses the camera to check if you are still looking at the phone before turning the screen off, it can cause the daemon to start even without a person realizing it leading to the overheating and power drain.
The morning this happened I booted to recovery and wiped the cache partition then left the phone off until it cooled down. I have not had this happen again since.
This is now happening 9 out of 10 times I open the camera or the gallery. With the original Lollipop update it was sporadic, but since OC4 it has become a regular problem for me. Is anyone else experiencing this?
newmanx4 said:
This is now happening 9 out of 10 times I open the camera or the gallery. With the original Lollipop update it was sporadic, but since OC4 it has become a regular problem for me. Is anyone else experiencing this?
Click to expand...
Click to collapse
It isn't just a lollipop problem. I'm on 4.4.4 NI2 and it happened to me. I deleted apps and still couldn't get it fixed. I had to go back to an earlier backup to get rid of it. Never figured it out.
Strange I never experienced this on KK. A cache wipe always fixes it but it's very annoying.
Probable Solution!
I had same problem on towelrooted 4.4.2 NE9 stock ROM. You can try this. I removed skype, rebooted and re-installed it again. And I never had this battery drain issue because of this again.
I've been having a pretty bizarre issue with my Nexus 10 for the last two months, and I'm curious if I'm the only one. At some point, my touchscreen will stop responding to input, and it will stay that way. Even after restart, the touchscreen will work for a few seconds, and then suddenly freeze again. If I factory reset, it will seem to work again, but at some point (sometimes hours, sometimes days), it will happen again, just as I described. This only seems to occur in 5.0+ roms, but it happens no matter what rom I'm using -- I've tried Cyanogen, Lineage, Remix OS, and even stock, with and without root, with the same result. This issue doesn't occur with KitKat roms (I've been running stock 4.4 just to keep my tablet functional), and it also doesn't occur in TWRP. The behavior seems like a driver issue, but the fact that nobody else seems to have it and it didn't occur at all for me until a few months ago makes that somewhat unlikely. Any ideas?
Am I seriously the only person who is having this problem?
I swear, it's just bizarre. This is the first time I've ever had a tech problem and found absolutely nothing about it on the internet.
I did finally get this resolved, and I thought I'd come back and document the solution in case anyone has anything similar happen and is as dumbfounded as I was.
What I ended up doing was completely wiping the system, cache, and data partitions, and then restoring the original factory ROM using the Nexus Root Toolkit. Once I did that, I no longer encountered the freeze-ups. Never did find the root cause, but the tablet is working again, so I'm fine with that.
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
waqar747 said:
Hey, I had been stuck with the issues as mentioned shortly after I upgraded to Nougat via ODIN (SM-G935F/probably Netherlands, Unlocked, no root, no mods). The phone would work fine and then suddenly start overheating and resultant bootloops and black screens when in certain standard apps like Google photos and Facebook. This would happen with no fixed pattern, sometimes everyday, sometimes once a month). I did cache clears and full resets but the problem would reappear. Phone stopped getting OTAs as well, although it got a few in the beginning. Security patches. Recovery typically showed updating and didn't progress.
Finally I decided to flash another latest stock ROM via ODIN. Now a few days have gone by without a sign of the previous troubles (God, I hope it stays like this).
My question after this long story, is this possibly a hardware problem, in which case I'll sell it off before it reappears. Or could it just be a software glitch solved by the new ROM, in which case I'd like to keep the phone. Which is more likely, I really want to keep the phone as the S8 upgrade is not worth the money for me, in my opinion.
Click to expand...
Click to collapse
Sounds like a bad flash. The new flash removed the issues, so you're good to go.
Guess what guys, the problem returned after about 3-4 weeks. Appeared randomly while using FB. Phone went into bootloop and overheating again, and even when it restarted properly, it would go into the same cycle when I started using apps like messaging, whatsapp and facebook.
I booted in recovery and cleared the cache after about 25 reboots. One thing I noted was that recovery initially showed an update running, which got stuck first, and then completed after another reboot and entering into recovery. Has been stable for the past 24 hours now, like it never happened. I can't figure out what the issue could be, since now I can do whatever I want and it won't overheat like before or reboot.
Feels like a software issue since it disappears like it was never there. Hardware rarely does that. Is there a possibility that storage of some sort is bad at some point, and when data is written over that point, the problem appears. I'm shooting in the dark but can't figure it out otherwise.
Yup.
Seems you have memory issues.
Go to Samsung service and replace memory chip.