I know I know, I am very late to the party.
But anyway, I finally installed the ICS update a few hours ago.... and my phone won't stop rebooting now.
Its not a boot loop, because it does get into Sense UI and I can use it, but eventually after a few minutes, it will reboot all on it's own with no warning. I assume its loading my (rather large) list of apps from the SD card since I have never seen it reboot until it finally wakes up, realizes a SD card is indeed mounted, and starts populating my app list. I never saw that process finish from the few times I bothered to watch it.
I tried removing the SD card and now its no longer rebooting, so unless taking out the battery did something, I assume its likely the SD card.
Is there any way to tell what is causing it without reformatting my phone? I REALLY don't want to wipe out everything.
After some testing, I have found two issues with the update:
1. It seems that it is not any one specific app, but the NUMBER of apps on my SD-card causing the reboot. I have somewhere around 200-250 apps installed on it. So far I can put about 80 or so of them in .androud_secure and it will work fine, I do not know exactly what the braking point it, but I know that having around 140 apps causes it to reboot every 5 minutes, regardless of which apps are on there.
2. I can't load my text messages anymore. Any contact who I have had a long history of texting with, it just gets stuck saying "loading". I can still receieve messages, but since I can't actually open the message list anymore, I can't reply!
I would really like to avoid doing a factory reset if possible, is there anything I can do about this?
I was consideing just doing a SMS-backup and then flashing a custom rom, but I like the 3D feature and it seems like there is not a SINGLE custom rom out there that supports 3D, and many don't support 4G either.
Please, does anyone have any advice?
Hi,
I'm a owner of a Samsung Galaxy S Plus (I9001). I have the CyanogenMod 10 installed and also a second partition on my SD Card.
So far so good, I restart my phone everything goes well, even with the second partition. The phone is not particularly fast but I can't blame it as I have lots of apps installed.
What I really don't understand it's when it stays on for some time, without any explanation or visible error my anti-virus starts to restart itself again and again (Avast anti-virus) then everything on my status bar starts to restart itself (Juice Defender and Accuweather). The other issue is the keyboard starts and the closes restarting itself again and again, I can't write anything.
I tried several task killers to see if any app was causing this issue but nothing worked. The only thing that stops this behaviour is restarting the phone, then everything starts working well and for some hours (5-6) then the restarting begins again.
I find myself restarting the phone two or three times per day because of this. And also by restarting the battery looses a lot of it's power.
Any ideas to solve this?
Cheers
I had the same problem. Try uninstalling Avast, reboot your phone, then reinstall it. Worked for me but as for the other apps doing it, I'm not sure.
Ofhrysto its
Kriptik210 said:
I had the same problem. Try uninstalling Avast, reboot your phone, then reinstall it. Worked for me but as for the other apps doing it, I'm not sure.
Click to expand...
Click to collapse
I already tried to uninstall and install again. I even changed to Kaspersky a couple of times...same result. This probably has nothing to do with Avast.
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
Recently, my GS4 started having occasional freezes where the screen will still come on when I press any of the buttons, but it will not respond to any touching of the screen, or responds incredibly slowly. The only way to solve this is to pull the battery and reboot. To try to solve this, I did a factory reset from my phone settings menu, re-rooted, and restored my apps from a Titanium backup, but the issue has re-occurred in the past few days. Is there any way to avoid this? Having to pull my battery multiple times each day is not ideal.
Uninstalling both Cydia Substrate and Xposed seems to have solved the problem. I uninstalled both at once, so I'm not sure which it was, but if anyone else runs into a similar problem, you could try that.
I honestly don't know where to post this so I'm going to post it under "General" in hopes that someone far smarter than me can help (!)!...
ScreenShot:
https://drive.google.com/open?id=0Bx8wdr_asZMFZXE1dGFWSnZ2NmM
I've had the following issue for the past 30 days (at first I thought it was some glitch that caused the UI to crash when phoning-home to Cyanogenmod for updates). It SEEMS to have happened right when I first started screwing around with TitaniumBU... that may be a total coincidence, also...
The phone works just fine but will suddenly start showing things in Landscape instead of Portrait (and vise-versa). After I reboot the phone boots to a black screen with just the status bar at the top (showing the time, wifi, etc...) with absolutely NOTHING ELSE except for what appears to be a "back" arrow at the bottom of the screen (that does nothing when pressed).
WTH?! Please. Because I've tried everything (to include wiping internal and ext-SD). :crying: I have, of course, searched other forums but "Android UI Crashing" returns a ton of unrelated results...
:cyclops:I'm still having this issue so I'm gonna bump this thread... Any help is much-appreciated!:cyclops:
I'd wipe the whole internal storage (including ROM) and reinstall the ROM.
Dude - WAY ahead of ya - already did. To the extent that I accidentally soft-bricked the stupid phone!
We all know, as engineers and troubleshooters, that the first step to solving a problem is duplicating it.... and I cannot seem to consistently duplicate the problem! And the crux of it is that this started at the end of December when I was bored around the holidays and playing with my phone (making several different changes).
Obviously I'm not restoring anything from a previous backup... I've even blown away my backed-up App settings in my google account... Formatted Internal and External... Installed latest OS and GApps...
Gun to my head; if I had to guess I'd say that it has something to do with the "System Profiles" feature... I started using it to disable my Lock Screen whenever it detected my home wifi, and to return to the System Default (with the Lock Screen enabled) whenever it no longer detected my home wifi... Because I swear that the crashed-phone looks the same as the screen where you enter your PIN with the addition of the status bar at the top...
The issue has to do with System Profiles to use wifi-detection for toggling the lock screen. Not sure what it is about this that causes the issue, but that was the cause.