Hello good people of XDA, I am having a bit of an annoying issue with my Cyanogenmod 7.1 "stable" install on my Evo 4G. Tiamat 4.1.0 SBC+ Kernel.
When I run a gps related application like Ulysse speedometer, Google Maps and Navigation, after a seemingly random amount of time the phone crashes and reboots itself. The time that I can use the app may be a few seconds to a few minutes and I havent noticed anything that would help determine the timing issue.
I have been doing a little testing and while running logcat on my PC via ADB, I have pulled the last events that occur immediately before the crash. It seems to me that the issue is more/only likely to occur when the phone is also not connected to a wifi network. Everything works fine when using GPS while connected over wifi.
Is anybody interested in reading through the end of my log file? How should I post it?
Please, any help at all?
sntmods said:
Please, any help at all?
Click to expand...
Click to collapse
I've been having the same problem as you and I think I've figured out a fix for it. I'm on Deck's 1.3 stable (which is essentially CM7.1) with Tiamat 4.1.0 SBC, using the smartass governor (the original one) with a CPU frequency range from 128 MHz to 768 MHz, and undervolted by 100 mV.
I've only encountered the issue sporadically and it's only occurred when using Google Maps or Navigation. I would be using Maps and moving the map around a lot, rotating it, or zooming in and out and all of a sudden the screen would freeze and the phone would reboot after 10 seconds or so. I figured out that I could reproduce the problem by opening up a bunch of apps to get the free memory (RAM) down to about 100 MB, open up Google Music and start streaming a song on the handset speaker, then open up Maps and just move around the map a lot; after less than a minute of doing this, the screen would freeze and the phone would reboot.
I tried uninstalling and reinstalling Maps; wiping the cache, dalvik cache, and fixing permissions; reverting to an older version of Maps (5.10); reversing the undervolting; changing governors; and changing the CPU frequency range; but none of these things fixed the problem.
I noticed that if I tried the Music and Maps crash technique when there was more free RAM (say 150 - 250 MB free), it wouldn't work, so I figured the problem probably had to do with the apps in use not having enough available RAM to operate properly and the default values that Android uses to kill idle apps was set too low. Fortunately, I remembered about Autokiller Memory Optimizer, which allows you to set those values, so that you always have above a certain level of free RAM. First, I tried the “Aggressive” preset (82, 90, 98), which didn’t fix the problem, so I then tried the “Extreme” preset (150, 160, 170) and that fixed it (for a full explanation of what the numbers mean and how the app works, see the Autokiller Memory Optimizer). I tried several different combinations of values between the Aggressive and Extreme presets and finally settled on Hidden app: 110, Content provider: 120, Empty app: 130. I was able to use lower values and still prevent the crash/reboot issue, but I figured I should leave a little buffer room to be safe and the 110, 120, 130 combo seemed low enough to prevent idle apps from being unnecessarily killed.
So, I’m not exactly sure what the root cause of the problem is, but Autokiller Memory Optimizer seems to be a nice workaround to fix the problem.
Well after testing this workaround for some time now, I can say that it doesn't prevent the reboots completely, but it does seem to have decreased their frequency, such that it's only happened one or two times since I started using it. I tried changing the cutoff values for when certain types of apps are killed, but eventually returned to the original levels I went with (Hidden app: 110, Content provider: 120, Empty app: 130) as they seemed to work the best (the one or two reboots that did happened, occurred when I was experimenting with the values).
Related
hi all
ive been having major difficulties controlling batt drain and 100% cpu usage after rooting and then flashing a custom firmware.
it usually...almost always..in fact- happens when i switch on wifi together with auto-sync data.
so i thought it must be one of the sync accounts, plus I'd read a bit about htc sync accounts sucking batt. So I disabled most...and there was improvement. but then it still does happen once in a while..once or twice in the middle of the night, meaning i woke to a dead phone in the morning. every time it gets so bad that I just have to reboot the phone.
when the slow down happens, i open up osmonitor, watched Android's own process log or the HTC launcher's log and i'd usually see a million of these:
gc_for_malloc freed xxxx objects / xxxx bytes in xxx ms
but am unable to troubleshoot further because it seems to be nothing meaningful.
anyone got any ideas?
yellowchilli said:
hi all
ive been having major difficulties controlling batt drain and 100% cpu usage after rooting and then flashing a custom firmware.
it usually...almost always..in fact- happens when i switch on wifi together with auto-sync data.
so i thought it must be one of the sync accounts, plus I'd read a bit about htc sync accounts sucking batt. So I disabled most...and there was improvement. but then it still does happen once in a while..once or twice in the middle of the night, meaning i woke to a dead phone in the morning. every time it gets so bad that I just have to reboot the phone.
when the slow down happens, i open up osmonitor, watched Android's own process log or the HTC launcher's log and i'd usually see a million of these:
gc_for_malloc freed xxxx objects / xxxx bytes in xxx ms
but am unable to troubleshoot further because it seems to be nothing meaningful.
anyone got any ideas?
Click to expand...
Click to collapse
I have the same problem just like yours!
I don't know how it happens?
But I founded a way to solve it temply.
when you saw the CPU load are 100% and system runs lagging.
First, launch the "set CPU" if you had installed.
Than you'll see the frq. Goes to 245 Mhz if you're set profile to "ondemand"
don't need doing anything, At least, you can see that CPU load are back to 5%~15%
As normalized. I don't know how it works? But it works everytime.
I'm using coredroid v3.2 and O/C 1.2G Hz, desire hd.
Can anyone who can tell us how it happend?
I've read that this is a common problem with many custom ROMs. If I remember correctly it had something to do with a file being constantly read. So you have to set permissions for that file which forbid reading. The trouble is that the system changes permissions again, and you have to constantly change the permissions using a sheduled script. It works but doesn't really solve the problem. The solution is to flash a custom ROM which has this fixed. Android Revolution HD 3.2 is one of them. With 3.1 I had this issue, now with 3.2 it's gone for good.
haha i don't know how you managed to get to setcpu..
mine is a near-freeze most of the time and would probably take forever to get there
but if i do get the chance i'll give it a try, thanks.
thanks, am indeed running on 3.0 so i'll give 3.2 a try.
just wondering if any of you guys experienced the same problem.
i just had this issue after upgrading to 2.2 tmobile us 34.4.9.
this usually happens when playing games and that in the middle of the game there will be a huge lag/screen freezes and this continue even after killing the program. it goes away after reboot and you can see a 100% cpu warning on top.
-vsel set at 20/300, 36/700, 49/1000 at 86%
-watchdog didnt report any misbehaving apps
-memory booster free memory around 35-40%
-apps not in sd
sometimes this happens, sometimes not. any ideas how this thing happens and how to avoid it.
thanks
try upgrading vsel set to 30/300 50/800 60/1000 and the treshold to what you want.
That should leave the phone smooothe~
Bug in froyo. Enable usb debugging for workaround. See:
http://forum.xda-developers.com/showthread.php?t=826507
thanks will try both.
in my case, I solved it by changing the trueshold SetVsel to 88%
definately up your Vsel 49 is too low for 1000Mhz try atleast 52 or 53 Most people suggest 56-58. Also I disagree with having vsel2 at 800, but thats just my opinion I keep mine at 600
800 just seems a little much IMO
I am running Jedi ROM, and have tried several different Kernels but they all have the same issue:
The CPU frequency is always stuck at the max frequency.
I have tried adjusting the CPU using both Antutu and Rom Toolbox, but there is no difference.
I need some advice and guidance as to how to fix this.
Some digging around seems to indicate that its an issue with android.process.media from source /system/app/SecMediaProvider.apk
for the first 10 minutes of boot, this goes crazy, and uses insane resources.
Tried killing the task, and after a little bit it turns back on again! AHH
Found the problem. My efforts to FULLY maximize the usage of my note 2, I had installed external high-res textures for n64oid. There are over 7000 files at a size of just under 900mb. It takes a while to go through those.
Option A: deal with it so i can use external textures
Option B: remove the external textures
Option C: go with either A or B and work to find a solution that will make the media scanner totally ignore the folder and all subfolders (.nomedia only applies to the folder it is in, not the subdirectories)
From last few months, I've been noticing a major slow down in my device. It lags a lot freezes while opening almost any app making the phone almost unusable for daily basis. I don't know what's causing the slow down.
Here's what I've already tried with no positive results:
- Completely formatting SD card + Internal storage and Flashing stock ROM
- Completely formatting SD card + Internal storage and Flashing CM ROM with all android versions (4.1, 4.2, 4.3, 4.4, 5.0, 6.0)
- Frequently cleaning cache partition and wiping all application's cache.
I also have very few apps installed on my phone and there are no major load on the RAM as well.
I am wondering what can cause such slow down?
As far as I remember, this device wasn't that much slower when I first got it about 2 years back.
Does Google services are causing incompatibility with this device causing freezes or this is a hardware issue? (If it is, then which part of hardware could it be?).
Also do you also experience such slow downs, lags and freezing?
You can try to change your kernel and modify a few things. I really suggest using Wild Kernel and downloading the Trickster MOD app on Playstore and change your settings. I usually set my Governor to "ondemand" and it's worked pretty well. I used to have this problem too back when I had the phone on "batterysaver" and it was a mess.
I agree with the kernel tweaks. I"ve noticed that this device does NOT like to go below about 250mb free ram. I've set my LMK settings very aggressively. Accept for foreground applications, I've set everything to 3x normal.
I too am using On demand, tweaked.
I/O set to BFQ
I also like to run Chainfire's Recently (check the playstore) and I set it to max 6 apps with a limit of 6 hours. I only allow 2 Google search instances, no settings screens and I set it to remove each apps documents as well.
With the above, I experience very few slowdowns any more. I should add, that I am using MM roms.
Model: Galaxy Note 4
Android: 6.01
Rooted: No
My phone once again is almost impossible to use due to constant lag and slowness. After using one of many apps to identify what was consuming all my CPU I discovered it was the Android OS process and then I drilled down using top command (Elixir 2 app) to identify sub-process system_server. The system_server process was constantly utilizing >40% CPU and when this is coupled with user processes, my CPU was pegged in the 95-100% all the time. This made my phone just about impossible to use.
I encountered this issue approx. 3mo ago and I tried everything to resolve, but ended up doing a factory reset to resolve it. after the same thing a few months ago. Doing a factory reset was the only resolution unfortunately at the time. Now that it the issue has returned, I have tried just about everything to fix it without doing a factory reset, here are some of the trouble-shooting:
Toggled bluetooth on/off
Disabled improve location accuracy options for both BT and WiFi
Removed and re-added my 2 Google accounts
Disabled Google account sync of Gmail, and selective options.
Toggled from Global/GSM to LTE mobile network mode
What did clear the system_server CPU usage issue was putting my phone in Airplane Mode. All this tells me it is radio related....
My phone has been extremely slow and hanging as a result the past three days to a point where it was FRUSTRATING the hell out me, at one point I almost threw it!!! After searching high and low on the web, I couldn't deal with it any long----so I too the plunge and performed another factory reset---which fixed the problem. Since this was the second time in 4 months, I'd like help identifying what is causing this to avoid it in the future.
Thank you in advance everyone!
Bump; 24 views and no replies yet.... I cannot be the only one who experienced this issue. Can we start a dialog on possible causes and fixes other than a full factory reset?
Thank you in advance,
i have the same issue just installed https://forum.xda-developers.com/no...-noble-rom-t3392289/post68300761#post68300761 and system_server consumes ~15% along with zygote ~6%. did you resolve problem?
guruleenyc said:
Model: Galaxy Note 4
Android: 6.01
Rooted: No
My phone once again is almost impossible to use due to constant lag and slowness. After using one of many apps to identify what was consuming all my CPU I discovered it was the Android OS process and then I drilled down using top command (Elixir 2 app) to identify sub-process system_server. The system_server process was constantly utilizing >40% CPU and when this is coupled with user processes, my CPU was pegged in the 95-100% all the time. This made my phone just about impossible to use.
I encountered this issue approx. 3mo ago and I tried everything to resolve, but ended up doing a factory reset to resolve it. after the same thing a few months ago. Doing a factory reset was the only resolution unfortunately at the time. Now that it the issue has returned, I have tried just about everything to fix it without doing a factory reset, here are some of the trouble-shooting:
Toggled bluetooth on/off
Disabled improve location accuracy options for both BT and WiFi
Removed and re-added my 2 Google accounts
Disabled Google account sync of Gmail, and selective options.
Toggled from Global/GSM to LTE mobile network mode
What did clear the system_server CPU usage issue was putting my phone in Airplane Mode. All this tells me it is radio related....
My phone has been extremely slow and hanging as a result the past three days to a point where it was FRUSTRATING the hell out me, at one point I almost threw it!!! After searching high and low on the web, I couldn't deal with it any long----so I too the plunge and performed another factory reset---which fixed the problem. Since this was the second time in 4 months, I'd like help identifying what is causing this to avoid it in the future.
Thank you in advance everyone!
Click to expand...
Click to collapse
I can see why you arrived at that conclusion but I'd caution a second look . I think its your wakelocks bud which is radio connected . until I disabled the lame google one my phone would get ridiculously hot and I mean physically hot as in to the touch turns out my problem was all the damn services the play store is attempting to use. It$ rediculous 1 app has twice almost 3 times as many service request as the rest of the phone . makes me wish play games was Foss compatible so bad I threw in on the bounty for it. But yeah try a wakelock sheriff specifically on play services and its stupid 22 (I think was what mine was) connected services and see if that helps
We are watching you
It looks like removing the screen pattern/password stops bumping system_server +110%, and it runs ≃ 1% CPU and 6% RAM.
Accordingly, CPU frequency is also lower. (1,4GHZ to 1Ghz).