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
Related
I have been having a terrible time with battery of my hd.
I tried several rom, dutty,miri,lost in asia,engery, and last one was black pearl.
With every rom, there was one or the other problem, so had to shift to new one.
My only concern of any rom,was that it should provide a good battery life.
Currently with black pearl, the batter drains like anything.
I dnt have much apps installed or running.
Apps:
PocketShield (running)
Advance Cconfiguration
Touch in call
Advance system task bar
I checked the cpu usage and wanted to figure out, why the battery drains so fast.
The phone is in suspend mode.(wifi,3g,dataconnection, BT, AS,...everything is disable).
Still it will loose like 30% battery in almost 10hrs.
The cpu usage shows,
Idle 81.40
taskmgr 18.40
the above two kinda stays constant,
but the below processes jumps with cpu usage, frequently.
Asynckiller0.10
shell32 2.21
qwertmememory0.10
Can anyone explain me, wat this process are doing and is the idle process being so high normal.
If not what can I do to resolve this.
I did search the forum, but I found something to clear RAM, not sure, if that is the solution.
any help will be highly appreciated.
I am using Dutty's 3.9 at the moment and very happy about it I love it
It is fast and after soft rest only 34% memory is in use
Phone is always on internet checking email every 2 hour, regular talk and text and of course iGO8
It goes for me about 1 and half day
Idle 79
taskmgr 20
And only tmail.exe is keep in changing but always less than 0.20
Some of process doesn’t use any CPU usage unless one or more events occur like you touch screen or even changing signal bar
about the idle process, it's normal that it shows such a high cpu usage. dont ask me why but this is how windows monitors cpu inactivity. for example on your windows PC try to launch task manager and you will see there is a similar process, called System Idle Process, that uses all the cpu power that's needed to reach 100%. (EG ffox.exe uses 2%, explorer.exe 3%, system idle will use 95%.)
it does not mean your cpu is always used 100%, it means your cpu is 80% (or whatever) idle.
My experience with the battery life problems is this: Radio ROM matters most.
Also I must admit that nueDynamicClock (version 1.0 not the latest version) helps a lot.
Currently my battery lasts for 2 days if I do not use wifi a lot, and if I do not play NFS for hours.
I am currently using onkologs Super Lite 6.5 ROM with radio ROM 1.13.25.24, and I have the following Processor (nueDynamicClock) settings:
-default speed: 528 MHz
-after system is idle for 5000 ms: 122.88 MHz
-on backlight off: 122.88 MHz
-on suspend: 19.20 MHz
I hope this helps...
Idle means how much of the cpu is not being used, so you want that as high as possible and 80% sounds normal. That means that 20% of the cpu is needed to run the taskmanager and there is 80% idle (not doing anything). It's there so that in case you want to know how much of your cpu is not being used, you can simply look at that, instead of having to have to add up all the processes that are using the cpu.
Hello,
I find things very funny on my phone let me describe. This happens on both opendesire 4.0.25 and defrost 4.9 . I am downloading defrost 4.7 now to see if the problem solves. This is it, my phone clock speed is always at 998MHZ and the CPU usage is always at 100% . I realised that is why my phone always got hot and the battery drains fast. I hope someone could give me a solution, or is it the new kernal that is giving the problems?
Thank you.
On Defrost you can try a different kernel directly from the Defrost setup.
I am now using HAVS 1113and the phone works great and the battery life has increased significally
Thank you for your reply
but that is not the problem. This is, my CPU usage is always at 100% (checked with many apps) also the CPU setting is ondemand which means my usage being at 100%, makes the clockspeed always at 998. The process that took up 76% of the CPU was named android.process.media or something like that. Anyone knows what it means and what I am supposed to do now? How am I to disable the process and what process is that? How can I disable it?
Thank you and I'm hoping for more replys its quite upsetting to have your processor running high all the time
Sounds like a background app is stopping the Desire going into a sleep state...you might have to reset the phone and add 1 app at a time to see what it is...
install Android System Info on your Desire and take a look at the tasks list.
There press the menu button to sort the list by CPU load.
The total CPU load should be around 10%, which gets consumed by the Android System Info process itself, and a small amount by Android System Info.
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).
I'm on stock, rooted, s-off
my device is getting extremely hot during normal use.(i dont play games at all, just whatsapp, facebook, news etc..)
sync is off, auto brightness.no google location reporting and history, no google now or history.
and using bbs to see what is going on ,i have no wakelocks and looking at battery screen, screen on time and awake time are almost identical.so nothing is keeping my device awake.
but for some reason, when the device is idle, the cpu goes nuts!
i installed cpu status bar xposed module so i could monitor cpu on real time, and i see the device jumping allot from 300mhz to 960 and 1000+ for no reason.(without touching it, and no apps running).when i touch the screen it scales to maximum.
it drives me crazy because i dont understand why the cpu behave like that.there is no logical reason for cpu going to max when i'm typing text.
its unbearable, cause its getting really hot while i hold it.
i have tried various kernels(elementalx, skydragon, faux, ionx, hacker kernel, but all of them shows that behavior.
on my old i9100, i never got that behavior, ondemand governor was perfect and i could reach 4 hours of screen on time.with the m8, i can barley pass it , going for 4-5 hours, because its draing too fast.
any suggestions?
*EDIT*
tried a factory reset, and i just installed xposed with cpufreq status bar module, and the device is still going nuts.WTF?
Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.
thebobmannh said:
Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.
Click to expand...
Click to collapse
i know there are background process and apps, and i don't except the device to stay at 300mhz all the time, but its quite annoying to hold on to a device and feel its temperature rising to insane levels without doing anything fancy with it.just texting.and every touch ramp the cpu to the max frequency, its weird.and unnecessary.
i don't know if its normal behavior, as i mentioned, my old i9100(galaxy s2) would not act like this. and i could get 4 hours of screen on time, and here, i get 4-5 hours max.it dose not seem logical.
I'm not using lte of nfc or BT.my reception is full(both wifi and cell).
i just want to know if this a normal behavior? anyone else having this heat buildup on light use?
I have a similar problem there on M8S. I killed half the background tasks, disabled syncing, auto backups, and then I open FBreader(or any other app) at 30% brightness and all the cpu cores go to 50 degrees C, heat up my battery to 43 degrees C. It results in loss of 40% of battery charge in just an hour. With screen off my device usually consumes 1-2% an hour. Whatever I do, I have never seen at least one core sleeping, they always work at 600-900MHz.
I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius
bucs9115 said:
I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius
Click to expand...
Click to collapse
Okay, so I got rid of my Note 4 so this is off of memory (full-disclosure). My Note 4 always ran pretty hot when it had to do anything. When flashing ROMs I'd be lucky if the CPU was below 70 C and any time I'd be playing a GPU intensive game it would get too hot to touch. I never had a lot of issues with the battery temp being too high though despite this.
As far as solutions go:
1) Screen res might help.....but I would try my other suggestions first
2) I wouldn't recommend disabling cores, it just makes the other two have to work harder to accomplish the same tasks and may be worse overall.
3) Kernel adiutor will allow you to do two things: adjust thermal throttling and adjust max GPU/CPU frequencies. I always reduced the max GPU frequency on this phone to lower the temps and adjusted thermal throttling to 55 C. The only CPU adjustments I did were to make sure the CPU wasn't overclocked.
4) I know you said it wasn't a rouge app, but get a task viewer (this is a good one) just to make sure (I had Nova taking 25% CPU usage in the background because I restored it from TiBu).
I saw your post in the NSeven thread and decided to respond, but please in the future try not to post errors in other threads unless you have the issue in that ROM. It sounds like you might have the same issue in that ROM as well, but you didn't say so in your post.
Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?
bucs9115 said:
Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?
Click to expand...
Click to collapse
You're welcome, and no worries for the post . As for your third point it would be really helpful if you tell me what you're running.
Could you list: kernel, ROM, root method, Android version, and any kernel mods (govtuner, skynet, etc)?
Also, does the same thing happen when you set a GPU max frequency? Have you tried having the settings run on boot and then reboot the phone?
Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol
bucs9115 said:
Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol
Click to expand...
Click to collapse
Since you're replying to both threads I'll keep my responses to your other Q&A thread to make life easier .