I am running faux's newest kernel on my att atrix, Allen build 4. I've noticed that upon cold reboot, the frequency scales correctly. after a while however, the phone stays at the max frequency. I've tried stopping running archives that I thought might be causing this, hit it doesn't help. Is it the kernel?
Sent from my MB860 using xda premium
You have a misbehaving process
turl1 said:
You have a misbehaving process
Click to expand...
Click to collapse
That's what I thought originally, but after killing all the apps that were running, it still stayed at the frequency.
I have a hypothesis, and i'm going to test it in a second. I think that when I plug my phone into my laptop dock, it for some reason locks the frequency at max.
EDIT: It's the webtop mode. If I plug the phone into my laptop dock, and open the laptop, the frequency is locked at maximum frequency. I'm going to flash the stock kernel again, and see what happens next.
EDIT2: So it's definitely faux's newest kernel. It might just be me, but it definitely is locking to max frequency. Stock does not have this problem.
Sent from my MB860 using xda premium
paravorheim said:
That's what I thought originally, but after killing all the apps that were running, it still stayed at the frequency.
I have a hypothesis, and i'm going to test it in a second. I think that when I plug my phone into my laptop dock, it for some reason locks the frequency at max.
EDIT: It's the webtop mode. If I plug the phone into my laptop dock, and open the laptop, the frequency is locked at maximum frequency. I'm going to flash the stock kernel again, and see what happens next.
EDIT2: So it's definitely faux's newest kernel. It might just be me, but it definitely is locking to max frequency. Stock does not have this problem.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I have seen the same behaviour. Just got my HD Dock yesterday. When I pulled it out it was warm/hot. I thought it was just the clock/screen using power or whatever. Then I opened SetCPU while in the dock and it showed a constant 1000Mhz. When I unplug it still shows that frequency. Too bad
use the auto detect button again#
Sent from my MB860 using xda premium
ltdanno360 said:
use the auto detect button again#
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks, I'll try it out in the morning, and report back.
Sent from my MB860 using xda premium
I think this is a known issue with faux's new kernel. When you place the phone into a laptop dock it clocks the CPU at max until a reset. I guess the same thing happens with any dock
Sent from my MB860 using xda premium
i have recently made a decision to delete the set cpu and install cpu masters from the market ,i think so for after 24 hours i think it does make a difference um
i notice lower temps even after an hour of useing the webtop or just an average temp overall i am useing the faux 2.0 kernal 1.3 oc but its set at 1.2
my profiles are screen off 456 max-216-min
the rest are 1200max 216-min
Sent from my MB860 using xda premium
I don't have a dock but I just installed _unknown's hdmi/webtop mod while running faux's enhanced stock 0.2.0. Noticed my phone was really hot after trying it out, even with the screen off and noticed a constant 1000 max. in setCPU.
Cleared my cache & dalvik, reinstalled kernel, jugg's battery fix, cleared my battery stats, rebooted into recovery (figured it wouldn't hurt since it defaulted to that option), then fixed permissions and restarted. Everything seems to be back to normal.
Will see what happens when I run the webtop again and report back later. Currently CPU is showing 36C and battery is at 32C. Are these acceptable temps?
Related
Every mornin after charging all night, my phone decides it wants to go black.. and ironically enough, not come back.
I have to pull the battery and reboot. It happens 4-5x in the morning, then doesn't happen the rest of the day. What would cause this?
- Nebula Lemon Slice ROM
- DK28
- SetCPU running @ 100-1000 conservative (only reason I mention this is it always seems to happen shortly, not immediately, after installing)
If you need any more info just ask.
Sent from my SPH-D700 using XDA App
Still no resolution for this issue. Returning my Epic today.
Try odining back to stck and then flashing dk8 again and the nebula rom see if that fixes it and try to format your sdcard to.
Sent from my SPH-D700 using XDA App
I have the same problem. It only occurs after I activate set cpu and it goes to sleep. If I turn set cpu off (after a battery pull) then it's fine. I just figured that set cpu doesn't support the epic that well yet.
Sent from my SPH-D700 using XDA App
Currently at 102.2F as reported by setcpu widget while plugged in and using it for the past half hour or so. Seems kinda high to me, what's everyone elses experience?
Sent from my DROID2 using XDA App
Well when its plugged in it will be warmer than normal. Right now my phone has been on with constant texting and random other usage all day long and I am at 80.6 degrees
My phone stays in the mid 90s and early 100s with regular use. It only gets in the 80s if I leave it completely alone for an hour or so.
Sent from my DROID2 using XDA App
I stay mostly in the 80s and can get into the 90s with heavy use. Don't think I've ever passed 100, but there's a chance something like psx4droid could have pushed me up. I average about 86F.
Sent from my DROID2 using Tapatalk
aeidian said:
Currently at 102.2F as reported by setcpu widget while plugged in and using it for the past half hour or so. Seems kinda high to me, what's everyone elses experience?
Do you use the SetCPU profiles? You could set one to underclock the processor while charging.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Sent from my DROID2 using XDA App
Redneck Trash said:
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
I do, its set to 800mhz when charging. 600mhz if it gets above 104F regardless of charging or not. Leaving it alone on the charger for the last half hour the temp shows 92F. Just firing up Xda app and typing this out the temp has jumped to 98F in about a min of use.
Sent from my DROID2 using XDA App
Are you guys using SetCPU for profiles and overclocking, or are you just using it for checking temps and current speed?
These are the droids you are looking for.
vagely said:
Are you guys using SetCPU for profiles and overclocking, or are you just using it for checking temps and current speed?
These are the droids you are looking for.
Click to expand...
Click to collapse
I was using it to check temps for this but I use 2 profiles, which may help my temps (def helps my batt). The default profile is 1000 max, 300 min, on demand. The other is when my screen is shut off, 300 max, 300 min. I've found this has saved me a pretty sizeable chunk of battery. I tend to listed to music 7-8 hours a day and while it doesnt need full CPU it will use it if it gets the chance. Restricting the proc to 300 off has never caused any issues and I can get from 8am - 4 or 5pm staying over 70% battery I have the unstable apps overclock and used it for a while, but kinda came to the conclusion that I can't really justify needing to overclock yet as I never see any lag. I guess if I run into any lag at some point I'll prob clock back up to 1.3 or so.
vagely said:
Are you guys using SetCPU for profiles and overclocking, or are you just using it for checking temps and current speed?
These are the droids you are looking for.
Click to expand...
Click to collapse
I did overclock, but it ran way too hot, like 107F during normal use and didnt get below 100 dormant. 1gig is high enough to me. I have it set to underclock when charging or when below 50% battery or when above 104F.
Sent from my DROID2 using XDA App
aeidian said:
I do, its set to 800mhz when charging. 600mhz if it gets above 104F regardless of charging or not. Leaving it alone on the charger for the last half hour the temp shows 92F. Just firing up Xda app and typing this out the temp has jumped to 98F in about a min of use.
Only other idea I have is downloading Droid Overclock and try running at low or ultra low voltage. Make sure to make a backup first. And try low before ultra low. Individual devices can be picky about a lower voltage and can go into a bootloop if it can't run on a lower voltage. Droid Overclock has profiles like SetCPU.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Sent from my DROID2 using XDA App
Am I doing something wrong? No matter what I do. I cannot get setcpu to cap at 1200Ghz, it always resets to 1300Ghz. No matter what rom I use it wont stay set. It always resets
Sent from my MB860 using xda premium
Do you have the "set at boot" box checked off?
If so, under Settings > CyanogenMod Settings > Performance do you have the CPU set at 1200 and have set at boot checked off?
DK
I hope someone corrects me if I'm wrong, but I believe there may be a bug with SetCPU. You can try CPU Tuner or that other app which does the same thing to confirm.
In any event, you may be able to circumvent it by setting up a profile. Just an idea. Let us know how it goes!
Maybe a bad version of setcpu or oc kernel. I haven't had any issues but I'm on HomeBase and have setcpu limits on screen off 216/456 and battery <50 1000. Been working superb I must say.
I use CPU Master and haven't had any issues at all.
Sent from CM7 Pre-Beta 4 on Atrix 4G.
No problems with setCPU. Just check off "apply at boot"
Hmm,i have the same issue with stock 2.3.4, setCpu and both faux or kholks kernel,very weird, i will try profiles, later today.
Same here, I have mentioned it many times and actuallly thought I was the only one.
Sent from my Tab using a pigeon.
Ok, i just tried the profiles and still to no avail. Very weird and rather annoying
I've also mentioned this a few times and have since moved back to 0.1.7
Try wiping setCPU's data from the manage applications menu.
Nope, same thing happens. The interesting thing is that if I cap it at 800 MHz, it tops up at that. Any step higher and the cap doesn't work.
Sent from my MB860 using Tapatalk
drdino said:
Nope, same thing happens. The interesting thing is that if I cap it at 800 MHz, it tops up at that. Any step higher and the cap doesn't work.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Very odd. You could also try wiping cache and dalvik if you haven't already.
Have you had this issue with any other ROMs?
I am more or less having the same issue. The annoying thing is that sometimes it would work but sooner or later, after a reboot, or changing the settings, it would go off again.
One thing that seeme to help is to set both slides to the min setting then just move one slide at a time, one click at a time and wait a few seconds between changes, till you get the settings you want... did not always work but it did more often then not.
I am going to try cpu master see if that does work for me.
Yeah it's weird. Whether it sticks or not seems totally random.
Hi, I'm on stock 2.3.4 and tried using CPU Tuner, it seems the kernel still won't act accordingly to the max cap I set.
Just like when I use SetCPU, even with the slider set max to 1000 and "Set on boot" ticked, it still jumps to 1300 sometimes.
So the problem could be with kernel, but I don't really know
bapaogoreng said:
Hi, I'm on stock 2.3.4 and tried using CPU Tuner, it seems the kernel still won't act accordingly to the max cap I set.
Just like when I use SetCPU, even with the slider set max to 1000 and "Set on boot" ticked, it still jumps to 1300 sometimes.
So the problem could be with kernel, but I don't really know
Click to expand...
Click to collapse
That's what I figure. I've tried everything.
Sent from my Atrix using XDA Premium
amwbt said:
That's what I figure. I've tried everything.
Sent from my Atrix using XDA Premium
Click to expand...
Click to collapse
Here's the good news:
http://forum.xda-developers.com/showthread.php?p=17575166#post17575166
drdino said:
Nope, same thing happens. The interesting thing is that if I cap it at 800 MHz, it tops up at that. Any step higher and the cap doesn't work.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Had the same problem with my atrix when I had one, prevented me from using any oc kernel.
Sent from my GT-I9100 using xda premium
bapaogoreng said:
Here's the good news:
http://forum.xda-developers.com/showthread.php?p=17575166#post17575166
Click to expand...
Click to collapse
Very good info. Thanks for posting! Greatly appreciated.
Sent from my SGH-I897 using xda premium
After calibrating, draining and recharging and wiping stats a thousand times, this is what I get:
https://lh5.googleusercontent.com/-...9zLfSiSGJ_Q/s512/screenshot-1321359229108.png
Wtf is that crap?
Sent from my PocketDock
Rouge app, or bad battery
Sent from AT&T SGS2
Viamonte said:
After calibrating, draining and recharging and wiping stats a thousand times, this is what I get:
https://lh5.googleusercontent.com/-...9zLfSiSGJ_Q/s512/screenshot-1321359229108.png
Wtf is that crap?
Sent from my PocketDock
Click to expand...
Click to collapse
2 hours of screen time there, that seems about normal to me. I'm lucky if I squeeze out 3 hours of screen time throughout the day.
Sent from my MB860 using Tapatalk
It depends entirely on what you are doing. 2 hours of screen time (even in ideal conditions) will most likely get through half of your battery.
What screen brightness settings do you use?
What were you doing with the "screen on"? (i.e. gaming, video etc).
What kernel do you use? Try the Faux 1.0 Ghz kernel (if not already) and consider undervolting.
I imagine with the combo of Faux's stock kernel, undervolting and perhaps reducing screen brightness will see 5ish hours of screen time.
It was on around 85% brightness due to being under direct sunlight.
My kernel is faux's 1.45 for CM
Over 80% of the time the clock was around 200, 400MHZ as stated by SetCPU, and both those clocks are undervolted by 50.
I was browsing the whole time.
Viamonte said:
It was on around 85% brightness due to being under direct sunlight.
My kernel is faux's 1.45 for CM
Over 80% of the time the clock was around 200, 400MHZ as stated by SetCPU, and both those clocks are undervolted by 50.
I was browsing the whole time.
Click to expand...
Click to collapse
Wow no wonder. Roaming for 2 hours with brightness nearly on full will definitely drain your battery.v Plus the 1.45 Ghz kernel overclocks the RAM and GPU also. You might want to get an anti glare screen-protector and flash the 1.3 Ghz kernel and use wifi.
I'm on the nightlie 18
Sent from my MB860 using xda premium
rog1121 said:
Wow no wonder. Roaming for 2 hours with brightness nearly on full will definitely drain your battery.v Plus the 1.45 Ghz kernel overclocks the RAM and GPU also. You might want to get an anti glare screen-protector and flash the 1.3 Ghz kernel and use wifi.
Click to expand...
Click to collapse
Umm... wifi wasn't an option back there, and I don't use screen protectors. BUT I didn't know that bit of fact from faux's kernel, I'll put in the 1.3
BTW, Green power pro does help a ****load on keeping battery alive.
ps: anyway to control RAM and GPU clocks the way we do with SetCPU with the... well... cpu?
msd24200 said:
I'm on the nightlie 18
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Why don't u go to a stable version and see if the battery drain continues there also ? You can always create backups to restore right ..
Sent from my MB860 using Tapatalk
Welcome to cm7. I'm lucky to get 10 hours light usage with faux 1ghz kernel undervolted with a screen off profile of 216-216mhz.
Sent from my MB860 using XDA Premium App
jimmer411 said:
Welcome to cm7. I'm lucky to get 10 hours light usage with faux 1ghz kernel undervolted with a screen off profile of 216-216mhz.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Have you tried installing better battery stats and CPU spy to see if you have a rogue app? You should be getting significantly better battery life. How is your cell signal?
Sent from my GT-P7310 using Tapatalk
anupash said:
Why don't u go to a stable version and see if the battery drain continues there also ? You can always create backups to restore right ..
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Lol it is stable and my battery life is great
Sent from my MB860 using xda premium
I don't believe setcpu functions correctly for dual core devices, I remember reading, albeit a while ago, setcpu only effects 1 core, leaving the second untamed.
Please correct me if I'm wrong. Stock cm kernel has plenty of ass behind it, no ones playing bf3 on their handsets....yet...
Sent from my MB860 using xda premium
In all actuality, android isn't optimized for dual core devices either. ICS will be.
Sent from my MB860 using xda premium
termleech said:
Have you tried installing better battery stats and CPU spy to see if you have a rogue app? You should be getting significantly better battery life. How is your cell signal?
Sent from my GT-P7310 using Tapatalk
Click to expand...
Click to collapse
Watchdog shows the suspend process and android media process taking up about 30% usage constantly. Signal is strong when I'm at work, constant 4-5 bars H+
Even after a full wipe and clean install of CM7 those same processes throw up alerts immediately, I will get al alert for the suspend process every few mins.
Background data off, no email syncing or anything. I'm lucky to get 3 hours screen on time or pandora streaming. I bought a new Motorola battery about a month ago and I don't use GPS or wifi.
Running stock, aura or homebase and the drain is gone... they aren't any good IMO tho.
For now I'm carrying a spare charger everywhere I go till the nexus prime is released.
Sent from my MB860 using XDA Premium App
JaronBang said:
In all actuality, android isn't optimized for dual core devices either. ICS will be.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
ICS is still android lol
I know what you meant though. Just saying
Now that we have a new way to overclock in v14 there are near unlimited variables to overclocking with this kernel. I've found a good balance of performance with 1300ghz step and live OC value of 121%. Let us know what has worked for you. You may include voltages as well.
I'm using reborn90's settings
200-1000; 110% live oc arm volt; 800/950/1100/1175 int volt; 1000/1000/1000/1025
Seems rather steady, I also recommend turning save on boot in settings of nstools before applying these settings just in case xD
Sent from my SCH-I500 using xda premium
I am on 100-1300 with 116% Live OC, haven't played with voltage yet but everything runs great.
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
mleonm5 said:
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Do you UV first then live oc? Or is it just stock voltages?
Sent from my SCH-I500 using xda premium
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
mleonm5 said:
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
it depends on how far you phone can go, some can oc more then others but some less then others, I usually never go passed 1.2ghz ,I'd rather save battery.
Sent from my SCH-I500 using xda premium
Just my opinion, but since Android 4.0 relies so heavily on the hardware rendering capabilities of the phone you'd be better off to UNDERCLOCK the CPU to 800mHz, and apply the Live OC to say 125% and have an effective CPU speed of 1000mHz while increasing the GPU clock by the same amount. I've tried it and it works very well but I didn't stick with it long enough to see how it affected battery life. You will need to modify your voltages though. I was at 1250mV on the 800mHz step.
If anyone is interested in just using stock settings, i found this thread interesting:
http://forum.xda-developers.com/showthread.php?t=1424064
100-800 mhz, 125% live oc.
So how much of a change have you noticed from Stock kernel to Glitch. I tried OCing once.. and it froze.. and phone died.. and ended up having to wipe / re-flash. Probably user error though
Just wanted to say I accidentally OC'd to 1.4ghz with 110% LOC and man did this thing fly and didn't even crash.
Sent from my ICS Mesmerize
I noticed I'm able to achieve higher stable oc (over 1500) using low leakage voltage and live oc of 116 or less. Without low leakage i can barely acheive 1400 oc at anything over 110 live oc. Never noticed this much difference in internal voltage stability in previous kernel version. I wonder what's changed?