Okay, so, I'm using CM 11 M12 on my Galaxy S3 and recently I decided to be a daredevil (like an idiot) and flash Boeffla Kernel on my phone. I flashed it and messed around with some settings, I'll post what settings I changed to what.
CPU: zzmove governor, profile - optimal. Set the max CPU frequency to 1200 MHz.
Enabled zRam, set it to 4 partitions at 800 MB each with swappiness set to 95.
Enabled Boeffla tweaks.
After that, I noticed that the phone would sometimes freeze for a short period of time, which was okay at first, but then the freezes got more annoying so I decided to restore my nandroid backup and use my stock kernel. Well, that didn't fix my problem, in fact, it made them even worse.
My phone now freezes randomly while doing anything (browsing, playing games, opening apps, etc) for 30 seconds to a minute. And during that time period, the phone is pretty much frozen. Can't turn off the screen, can't toggle anything, I can only restart it by holding the power button for 10 seconds after which the phone still continues its weird behavior.
There are some odd things I noticed though:
1. I cannot transfer files to my phone using a USB cable. It stops at about 1/3 of the progress and the phone freezes (can't power up the screen, open apps, etc). I can only reboot it and stop the file transfer process. However, transfering files to my SD Card works, albeit it very, very slowly.
2. At first, the currently open app freezes but not other parts of the system. Let's say I'm using Chrome, i'm browsing and then Chrome freezes. I can still open the notification bar or the power menu, but the app itself doesn't respond anymore. After a few more seconds, the entire system goes unresponsive.
3. Restoring and making backups takes extremely long (using TWRP 2.8.5.0). While restoring a backup, the process sometimes stops for half a minute and then continue which leads me to believe that the CPU is under heavy load all the time.
4. During the freezes, the phone won't reboot itself automatically, but certain aspects of the phone will crash with an error message (like the Settings menu, lockscreen, the wallpaper will change to the default one, etc)
I also tried doing a complete wipe (data, dalvik and cache) and booting up CM 11 again. Right after I selected the language in the "Welcome" screen, the phone went unresponsive and very sluggish. Animations would freeze, get stuck and it was impossible to continue. I decided to restart the phone again by holding the power button after which I got into a bootloop. The only thing I could do is restore my nandroid backup again.
Does anyone know what the problem could be? Do I need to delete certain kernel files left over from Boeffla kernel? Is it a hardware problem? I seriously hope that this is something that can be solved by wiping data (i'm even willing to wipe /data/media) or by deleting certain system files.
Thanks in advance and sorry if this post is in the wrong forum or if it doesn't follow certain guidelines set by XDA.
Emmc nand damage caused by messing with partition, try reading the freezing thread in general forum.
There is no cure, only a partial workaround to teach the operating system to avoid the damaged areas.
Related
I have upgraded my SGS2 to ICS (PDA I9100DXLP7) (rooted with CF-ROOT). All was fine the first weeks, then I started having occasional phone crazyness often when the battery was lower than 30%. Phone would reboot, gets very hot and keeps reboot until battery totally flat within minutes.
I noticed an additional problem which is auto-update was giving many errors such as : package invalid, not enough storage to install app (well got 300MB free for apps, 3GB on internal sd and 4GB on external...)... but manual install/upgrade always succeeds.
Then I started having issue of loss of mobile data connectivity... rebooting the phone would solve the problem..except that now almost everytime I reboot the phone, the cpu usage is at 100%, phone soft reboot (not full reboot) after a while (from 1 to 5 minutes). battery is being sucked at the rate of ~1% per minute!!! Usually it takes about 30 to 50 minutes of loop reboot before the phone can work... once it works and cpu is not 100% all is fine. Even plugged in the charger the phone barely maintains it's battery level, if plugged in usb, battery keeps going down!
cpu usage is caused by system server (100% cpu on both cores). I tried adb debug console, all I see is that the phone gets stuck for a while, then all processes are being killed and the phone soft-reboot.
I tried clear the dalvik cache and reformat the cache partition, didn't really seem to help. I tried disabling media scanner too, with no luck.
I now notice that most of the time the phone is stuck in that auto-reboot loop, the auto-update process is in progress... not sure if it means anything.
Anyone got any idea on what is wrong? is a full wipe/reinstall my only solution?
Thanks,
David.
Have you tried using Better Battery Stats to see what process is running to make your phone do that?
Hi,
It's mentionned in my post, the culprit is the process "system_server"
Wipe phone and reinstall firmware from a different download .
jje
Last night I was reading Twitter before going to bed when I noticed that my GPS kept ticking on and off after I'd posted an update (I let my Twitter app access GPS to assign my location to tweets). Thinking that odd, I rebooted.
Talk about the reboot from hell.
Approximately 30 seconds after booting back up, the phone locked: I could tap buttons and feel haptic feedback, but no changes to the screen occurred. I eventually got the bright idea to lock it and unlock it; pressing the lock key blacked the screen, but pressing it again did not bring the screen back. Scared, I eventually pulled the battery and started up again.
It happened again. And again. In the midst of all this, I slowly learned a few things: it wasn't tied to any of the new apps I'd installed (I had enough "functional time" each boot to uninstall a couple of things), it wasn't tied to internet connectivity or GPS (I had time to turn both off), and the SGS3 has a dev option to monitor CPU usage of various apps/threads. That little HUD, which overlayed everything else, would remain updating through a lockup, and I found that a process named "df" was starting up and immediately sucking up the entire CPU and not letting go.
I eventually found that it worked the processor so hard that the phone would overheat if left alone and "soft reboot" (OS restarts, but no Verizon/Samsung loading screens), so I was able to at least stop pulling the battery!
Finally, I turned it off and let it cool down for a few hours whilst Googling: no results anywhere for a similar problem or regarding the "df" process. Turning the phone back on after its reset didn't help at all. The lockup time was so quick that I couldn't even initiate a factory reset--it would lock up in the midst of preparing to perform it!
I eventually restarted it into the bootloader (meant to go for recovery, oops) to poke around and got a really scary image: a "Custom" screen before the bootloader starts that the devs are saying means that system apps/files have been modified. Now, since I don't have root yet (no hacking/voiding warranty JUST yet), I am not ABLE to modify system apps, which means that something got tweaked all by its lonesome, and THAT isn't supposed to happen. It was probably what was causing the lock, though--some driver somewhere that's supposed to say "Processor, don't try to calculate pi to infinity" got hosed or whatever.
I eventually got into stock recovery and was able to initiate the factory reset from there without the use of the actual OS (thus avoiding the hard lock). The phone rebooted fine, let me sign into Google, and spent the rest of the night redownloading apps. It's fine now.
EXTREMELY worrisome. Possibly a hardware fault with the EMMC chips holding my OS or something--there's not a lot that can knock out system files on a non-rooted device. At least it doesn't appear common, insofar as all my Googling leads to no results at all.
Any ideas as to what the heck happened?
Apologies in advance for the potentially vague description, but I also cannot find a solution elsewhere on the forum.
Earlier today, I was watching a YouTube video and then I locked my phone and left it to charge whilst I went downstairs (as I often do). When I returned roughly an hour later, I found the screen on, which I only ever do if I've left Draw Something open, or some similar app - but it was on the lock screen.
(none of that is necessarily important, I just wanted to clear up the "what did you do to make it start rebooting" question)
Anyway, after unlocking the phone, the screen went to black and the phone restarted.
However, it wasn't a "real" reboot, because the boot screen didn't come up, etc. It's just like just the UI is restarted. I can usually use the phone for about 30 seconds at a time. This seems extended when I have flight mode on, and is even longer still when I have the phone locked.
I've uninstalled some potentially-offending apps, removed the SD card, cleared some apps' data, but to no avail.
I'm using default 4.0.4 from Samsung. The only issues I'd had with it until now were that some apps crashed occasionally, but I attributed that mainly to the apps themselves.
The most annoying thing for me is that is seems like it's an issue that can be fixed quite simply, without having to uninstall every app or factory reset the phone.
Anyone have any other ideas as to what I could do? Thanks!
RobHannay said:
Apologies in advance for the potentially vague description, but I also cannot find a solution elsewhere on the forum.
Earlier today, I was watching a YouTube video and then I locked my phone and left it to charge whilst I went downstairs (as I often do). When I returned roughly an hour later, I found the screen on, which I only ever do if I've left Draw Something open, or some similar app - but it was on the lock screen.
(none of that is necessarily important, I just wanted to clear up the "what did you do to make it start rebooting" question)
Anyway, after unlocking the phone, the screen went to black and the phone restarted.
However, it wasn't a "real" reboot, because the boot screen didn't come up, etc. It's just like just the UI is restarted. I can usually use the phone for about 30 seconds at a time. This seems extended when I have flight mode on, and is even longer still when I have the phone locked.
I've uninstalled some potentially-offending apps, removed the SD card, cleared some apps' data, but to no avail.
I'm using default 4.0.4 from Samsung. The only issues I'd had with it until now were that some apps crashed occasionally, but I attributed that mainly to the apps themselves.
The most annoying thing for me is that is seems like it's an issue that can be fixed quite simply, without having to uninstall every app or factory reset the phone.
Anyone have any other ideas as to what I could do? Thanks!
Click to expand...
Click to collapse
just go to recovery mode and fix permissions
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
Hello guys, I have a Samsung Galaxy A10 and since today that I'm having an issue with it. Every 3 seconds there's a lag spike in the operating system only. In apps its completely normal no lags at all. For example if I continually flick the notification bar up and down i get a lag spike every 3 seconds every time. It happens the same with the navigation buttons on the bottom, keyboard, basically anything related to the os. But in apps I dont have this issue. I think it all started when I plugged in the charger and i got a warning that was water on it, but there wasnt any water that warning sometimes pops up when the cable slips a little bit and gets halfway attached. I restarted the phone multiple times, it seems fine on boot but quickly goes to the same problem. The phone is not rooted, it's original firmware and all. Can anyone help me out here?
@crazyon3
Try this
Uninstall apps which haven't used in last 30 days. No need to worry, you can always install back when required.
Delete all images and videos of WhatsApp and similar which are just forwards. It will be a big chunk usually.
Move all personal pics and videos to cloud (Google Drive). Enable auto backup. Delete device copies for > 1 week old files.
Run SDmaid app. Uninstall it after that.