I had previously posted an issue I have had with my phone randomly shutting down when it was in sleep mode. The only way to get it back on was to pull the battery. It was not ROM specific, and was driving me crazy!. I Odined back to stock, formatted my sd card, rerooted, put a ROM on my phone and the problem seemed to go away. I just installed Launcher Pro, to see if It will happen again, so far working fine. I think Titanium backup may have something to do with this issue, because last time it started happening, I had done a restore with titanium. It might also have something to do with the SD card. I am going to play with this more over the next few days, and If I can figure it out, I will update this post. Any comments will be very appreciated.
Related
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 :/
I posted this in the Atrix Development forum under Gingerblur since that's what's currently on it, but it may just be a general Android issue so I'm reposting it here as well just in case:
OK I had something weird happen to my gf's phone yesterday. I don't know if this is Gingerblur related, but that's what's on it so I'm putting it here.
AT&T Atrix w/ Gingerblur 4.0 (Just haven't got around to going to 4.5)
So I put Gingerblur on it 2-3 months ago and it's been working great for her. So yesterday I was with her and we were going to install this market app (I can't remember what it was), but she hit Install on the market app, it changed to the OK button, but when she clicked OK, the button just flashed and just sat there and did nothing. i found that odd. So I had her see if she could sideload an app (not the same one) -so I downloaded it to the phone and clicked it to install it. I accepted it and it just said "Installing...." forever. So I told her OK the phone got out of whack or something let's just reboot it.
So we reboot it, and she complains that a lot of her apps show the default android icon for them (instead of their respective icon pics) and she can't run them. From what we noticed, these were all the apps that were moved with app2sd. Also, nothing will install from the market - you can get there, but you get the same symptoms as above. You can click "Install" on the app but when you click "OK" it doesn't do anything.
Under Settings/Manage Applications it shows all her apps installed so the phone still thinks all the apps are there. So I tell her to pick an app that she doesn't really care about and Uninstall it. She said that works, but trying to install it through the Market fails.
So she's freaking out. I tell her to let me at least back up what I can off the phone. So I try plugging the phone into my computer with the USB. I can't get the phone to be seen at all by the computer. I put the USB into Mass Storage mode/Nothing/etc, and even turn off/on USB Debugging - I just can't get this thing to be seen. So now I'm starting to worry.
We have an external SD card in the phone so I was able to start copying what I could under Setting/Files over to the SDcard.
Now all I'm thinking about is getting this phone working again so I'm starting to read how to recover the phone back to stock using this thread:
http://forum.xda-developers.com/showthread.php?t=991072
So I'm able to get it into the recovery state. So as I'm downloading the SBF, I notice it says to remove the SIM card too. So I shut it down, and remove the SIM. I boot up the phone regularly and I notice everything is working now as it should (minus the phone since the SIM is out), but all apps are there and working correctly and the market works as it should.
So immediately I nab Titanium Backup from the market and start backing things up. I tell her to go through the list and start backing up what she thought was important. So I'm thinking this thing fixed itself, but when I put the SIM card back in, we're back to the broken state again.
So.. does anyone know what's going on here? It seems like the phone doesn't like her SIM card anymore, but she can still make calls with it aside from the rest of the phone issues with it in.
If we need to take this back to stock, I will - especially now that I was able to back things up with TB.
Hi
I updated swype yesterday, which went fine in itself. I restarted the phone couple hours later, and the phone got stuck on the Samsung logo. Tried restarting, pulling out the battery, nothing did the trick.
Clearing the cache's helped, but only to some extend. Immiedietly after going into homescreen, apps started to crash, starting from Nova Launcher.
Loading the nandroid backup that I did in june helped, so much so, that I pinpointed that swype was the one app that messes things up. I loaded the nandroid backup of broken OS that I did, and tried to uninstall swype from adb which went fine, but the problem did not go away, which makes me believe something is deeply broken over here.
Anybody had similar expieriences in the past, and could point me out to how to fix the problem? I really would hate to re-do all the things I did on the phone since june.
lukair1983 said:
Hi
I updated swype yesterday, which went fine in itself. I restarted the phone couple hours later, and the phone got stuck on the Samsung logo. Tried restarting, pulling out the battery, nothing did the trick.
Clearing the cache's helped, but only to some extend. Immiedietly after going into homescreen, apps started to crash, starting from Nova Launcher.
Loading the nandroid backup that I did in june helped, so much so, that I pinpointed that swype was the one app that messes things up. I loaded the nandroid backup of broken OS that I did, and tried to uninstall swype from adb which went fine, but the problem did not go away, which makes me believe something is deeply broken over here.
Anybody had similar expieriences in the past, and could point me out to how to fix the problem? I really would hate to re-do all the things I did on the phone since june.
Click to expand...
Click to collapse
so, let me try and understand this, if you don't update swype, there is nothing wrong with your phone?
Correct. For now I'm on my june nandroid backup and everything works as expected.
Solved
It turned out this update made swype be disabled in the OS keyboard settings, and combined with the fact I froze native keyboard apk, it made unnexpected results after every boot.
Once I restored the native keyboard apk in my june image, swype update went fine, and everything is back to normal.
Topic can be closed.
In the last few days my S5 has started just locking up briefly and then rebooting. It doesn't do it from a particular app, only when using the camera, or any other specific symptom I can find. It will even lock up and reboot during a reboot sometimes. It's happened running various unrelated apps that don't have anything (apparent) in common, when running no apps, when closing apps, and when sitting all by its lonesome next to me while I'm doing something else entirely.
When it started I was running Safestrap with AllianceROM 1.1 installed on the boot partition. I wiped and installed AllianceROM 2.0 and it still does it. The only change I can think of that happened anywhere around the time the problem developed is I replaced a broken charging port cover (can't imagine how that would have messed anything up.)
One common symptom that may or may not be helpful: during the short unresponsive time during the crash before it reboots, one or two lines of "static" a few pixels tall running horizontally across the display will often (but not always) appear. It's happened when using the phone, when not using the phone, and during reboot from a previous crash. It's crashed while rebooting prior to the Safestrap screen displaying. It crashes and reboots with and without the SD card installed.
At this point I'm thinking the phone is just plain broken (still under warranty) and a replacement is in order. So my questions are:
1. Anyone seen this before and know a fix?
2. Is there anything I'm overlooking and should test before pursing warranty replacement?
3. Is there any reason to avoid a replacement unit (ie. would a new phone resist root/safestrap/etc)?
Thanks.
Sounds like you've covered everything but one.
Try returning the phone to stock and see if the problem persist. If it does then phone is ready to be exchanged.
If not, you'll know it is something other than a hardware issue.
c4manceph said:
Sounds like you've covered everything but one.
Try returning the phone to stock and see if the problem persist. If it does then phone is ready to be exchanged.
If not, you'll know it is something other than a hardware issue.
Click to expand...
Click to collapse
Yeah, I suppose I ought to do that just to be sure. But to be absolutely certain that would require Odin'ing back to stock to get rid of the root, Safestrap, and all the trimmings, right?
So I need a nandroid backup of my current image so I can resurrect that if it doesn't work so I have a phone that only annoys me intermittently while I wait for the replacement. While if that does solve the problem I need my Titanium Backup files so I can gradually restore my apps/settings after redoing all the root, Safestrap, and custom ROM work.
Am I missing anything?
This is the method I would use to return to stock:
http://forum.xda-developers.com/showthread.php?t=2784880
Sounds like you've got it covered.
Thanks. That link mentions repartitioning as being optional... under what conditions would it be advantageous? Is it just one of those "if you wanna be absolutely sure" things or are there cases where the partitioning has been changed and needs to be reset?
New symptom: twice now the phone has rebooted into Odin mode with the message "Could not do normal boot, mmc_read failed".
Doesn't look good... at least I've been able to reboot the phone to the OS each time. Once it even did it itself.
Sounds like internal memory failure. Do your best to ODIN back to 100% stock & do a warranty return.
I've been back to stock for a day without any spontaneous reboots.
I figure the next step is to root, install Safestrap, and then flash the AllianceROM and not restore my Titanium backups except those that are absolutely necessary (and taking a nandroid backup before doing any of those). Let it run for a day or two like that, see if the reboots stay gone and then slowly restore the backups a few at a time to see if one of them causes the problem to return.
Thanks for the update, I wondered if you were having any luck.
I'll keep this updated just in case anyone else has the same problem, so they can have a better idea how to resolve it.
Currently I've been running AllianceROM 2 for about 10 straight hours with no misbehavior. From stock I installed towelroot, Safestrap, then flashed the ROM according to instructions. Once that was loaded and the Play store done downloading everything I shut down, backed up via nandroid, and then used Titanium Backup to restore some key apps and data. Actually I restored more than a few, but not close to all. With the backup if the problem returns I have a clean restore point to use for a more conservative approach.
My plan going forward is that if nothing else goes wrong, I'll restore a few more backups as I need the related app, and after a week or so if things don't fall apart I'll go through and delete the entire contents of the Titanium Backup folder and re-backup the apps as they are in a stable state. Whatever was causing the problem seems to have died in the repartition/odin-to-stock/root-and-return-to-custom, or it's lurking in one of the unrestored backups.
Fingers crossed.
Aaaaand just had a spontaneous reboot. Second time it's done it while scrolling the newsfeed in Facebook. (First time was pre-wipe to stock.) It's possible I just didn't have the restored stock version running long enough since this took over a day to happen.
So I'm restoring the backup and not restoring any of the Titanium Backup stuff. If it still reboots on its own after this, I'm considering it hardware and pursuing a replacement.
There's been another spontaneous reboot. At this point I'm pretty comfortable calling it a hardware failure. I believe the absence of reboots while the phone was Odin'd back to stock was a fluke and, had I given it enough time, I'd have seen a spontaneous reboot there as well. I'm going to forego testing this theory to expedite a resolution to the problem.
So my next step is to call Verizon and start the ball rolling on a warranty replacement. I'll Odin the phone back to stock just before turning it in, until then I'll let it run (as much as it does) the way it is.
The warranty replacement was easy. Went over the steps I'd taken (leaving out all the bits about root, custom Roms, and so on since it's none of their business) after spending about a half hour on hold between the initial customer support person and the actual phone tech guy. He kept saying, as I was telling him what I'd done, "yeah, that's what I was going to recommend next". Set me up for a replacement, next day air, and that's what I'm running now.
Wiped the old phone back to stock via Odin, set up the new one and restored every backup I wanted from Titanium backup. So far, no problems.
It's kinda neat how they send the replacement phones. No back cover, no battery, nada. You take all the stuff out/off of your old phone, use it to finish up the new one, and you're done. Put the old one back in the package, slap the return label over the previous label, and send it on its way. (Be sure to go to a FedEx store or something where you can get a receipt and so on to PROVE you sent it in case it gets lost, or you're paying for a new phone.)
It's clearly not a new new phone, it's a refurb, but aside from some minor scratches on the screen that a screen protector would make invisible, it's essentially new.
Still no sign of a spontaneous reboot, looks like this is fixed.
All of the sudden my phone refuses to go into deep sleep, it stays at 300mhz according to cpu spy. Not even if I switch to airplane mode the deep sleep works. This has happened a few times in the last week. A reboot fixes it for a while. Do you think it's an app that is misbehaving? Has someone else seen the same thing on their phone?
jocke_lulle said:
All of the sudden my phone refuses to go into deep sleep, it stays at 300mhz according to cpu spy. Not even if I switch to airplane mode the deep sleep works. This has happened a few times in the last week. A reboot fixes it for a while. Do you think it's an app that is misbehaving? Has someone else seen the same thing on their phone?
Click to expand...
Click to collapse
I had the same thing once I got my Note 4. Turned out that it was my micro SD card, which I popped straight into my new phone from my old phone (an LG). It may or may not be your cause too.
I ended up reformatting it through Android (after copying all my files to my pc). After that, I put all my data back on it. It's been about a month now with my phone always deep sleeping.
If you have a micro SD card in your phone, then remove it for a while to see if the phone sleeps. If so, then backup any wanted files from it, pop it into the phone, and reformat it. Afterwards, you can put your data back on it.
If this isn't your problem, then yeah, it could be an app.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk
spexwood said:
I had the same thing once I got my Note 4. Turned out that it was my micro SD card, which I popped straight into my new phone from my old phone (an LG). It may or may not be your cause too.
I ended up reformatting it through Android (after copying all my files to my pc). After that, I put all my data back on it. It's been about a month now with my phone always deep sleeping.
If you have a micro SD card in your phone, then remove it for a while to see if the phone sleeps. If so, then backup any wanted files from it, pop it into the phone, and reformat it. Afterwards, you can put your data back on it.
If this isn't your problem, then yeah, it could be an app.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk
Click to expand...
Click to collapse
I don't have any SDcard. Hopefully it is an app that is causing the problem. Right now I have uninstalled all the apps that I have installed lately. Let's hope this helps.
The problem seems to start after I charge the phone and pull if off the charger. But as I said, it started last week. I haven't had the problem before and I bought the phone in early November.
jocke_lulle said:
I don't have any SDcard. Hopefully it is an app that is causing the problem. Right now I have uninstalled all the apps that I have installed lately. Let's hope this helps.
The problem seems to start after I charge the phone and pull if off the charger. But as I said, it started last week. I haven't had the problem before and I bought the phone in early November.
Click to expand...
Click to collapse
If it didn't do it before, then it shouldnt be a hardware problem unless something just randomly broke. As long as the phone isnt getting real hot or anything weird like that, then that shouldnt be it.
I think it may be an app. If uninstalling everything fixes it, then you can reinstall the apps one by one until it happens again. Wait like a day inbetween reinstalls.
If that doesnt help though, then do a factory reset (last resort).
GOOD LUCK!
spexwood said:
If it didn't do it before, then it shouldnt be a hardware problem unless something just randomly broke. As long as the phone isnt getting real hot or anything weird like that, then that shouldnt be it.
I think it may be an app. If uninstalling everything fixes it, then you can reinstall the apps one by one until it happens again. Wait like a day inbetween reinstalls.
If that doesnt help though, then do a factory reset (last resort).
GOOD LUCK!
Click to expand...
Click to collapse
My problem seems to be fixed now. I did uninstall some apps but that didn't seem to help. I then turned off the phone, pulled the battery for some minutes, put it back again, booted to recovery, wiped cache and then restarted. Since then it's been OK. I have an uptime at 350h right now. It must has been something that had got stuck before. Hopefully it doesn't happen again! Now I'm waiting for lollipop