Hi guys, I just wanted to know what undervolt values you guys use, right now im getting semi decent battery life but in comparison to others battery life its terrible, I get about 3 hrs on screen time (screen brightness at 25%) and overall 14 hrs battery life (100 - 0%) with average amount of use (browsing the web, text messaging and whatsapping)
Whether I'm on blur (Darkside/Aura) or CM7, I'm using Faux's latest 1.0GHz kernel. Unless I'm gaming, I leave my CPU capped at 750MHz, with a profile for screen off with max 216MHz (priority 100). I've attached my Voltages. Be careful with the set at boot option. Make sure to do a nandroid backup before messing with any of this. Remember that the max difference between steps of voltage settings is +/- 100; if you break that, then the settings are automatically inert (this is a Tegra restriction). Not all silicon is created equal, so your best undervolting might be less (or more) than mine. Good luck!
-omni
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
omni_angel7 said:
Whether I'm on blur (Darkside/Aura) or CM7, I'm using Faux's latest 1.0GHz kernel. Unless I'm gaming, I leave my CPU capped at 750MHz, with a profile for screen off with max 216MHz (priority 100). I've attached my Voltages. Be careful with the set at boot option. Make sure to do a nandroid backup before messing with any of this. Remember that the max difference between steps of voltage settings is +/- 100; if you break that, then the settings are automatically inert (this is a Tegra restriction). Not all silicon is created equal, so your best undervolting might be less (or more) than mine. Good luck!
-omni
Click to expand...
Click to collapse
i read somewhere in these forums that the voltage values on either side cannot have step-wise differences greater than 100mV... if that is true, that would mean that your voltages from 216mHz to 608mHz are not functional. i dont have much personal experience with UV, so couldnt say first-hand one way or the other, but from what i've gathered here, that is my understanding.
i would suggest starting small (-25 on all clocks) and adjusting them upwards, one at a time. as long as you dont check "set on boot", you can do this until your phone reboots, and then just wind it down to where it was stable.
fischwrap said:
i read somewhere in these forums that the voltage values on either side cannot have step-wise differences greater than 100mV... if that is true, that would mean that your voltages from 216mHz to 608mHz are not functional. i dont have much personal experience with UV, so couldnt say first-hand one way or the other, but from what i've gathered here, that is my understanding.
i would suggest starting small (-25 on all clocks) and adjusting them upwards, one at a time. as long as you dont check "set on boot", you can do this until your phone reboots, and then just wind it down to where it was stable.
Click to expand...
Click to collapse
The 100mv max difference between frequencies is a built in Tegra limitation. It applies to the final mV values at each frequencey (i.e. left side). So as long as each step does not exceed 100 from the preceding one, you should be good to go. Fischwrap is correct, 216 to 608 are being ignored.
See these 2 posts from faux's thread, they get into some more detail:
July 13
July 24
*Edit* After re-reading the second link I posted I wanted to correct the above. Steps greater than 100 are not ignored, they are automatically adjusted to be within 100mV of the preceding step.
can i ask, how come your scaling drop down box has a option called powersave, and mine is greyed out and I can't select an "option"?
thanks
On CM7 (any build, but currently on weekly #2) with Faux's 1.0GHz stopgap kernel I can get up to 40 hours with light to heavy use using the following UV values:
I use Optimize Toolbox to prevent unwanted autostarts, have WiFi turned off 50% of the time, have data turned on all the time, and rarely play games or watch videos.
on cm7, weekly build #2, faux's 1.45 stop ext4 kernel.....loving cm7, and the atrix. with minimal use (work long days during the week, I'm a mechanic) getting roughly 3 days. Still doing some texting, phone calling, web browsing, email during occasional times. also using uv values of -100 for each
Sorry for deviating from the OP. I would like to maximise my phone's battery life too. For some strange reason, i cant load Faux's enhanced 1 Ghz kernel on any of the ROMs, be it CWM or the usual gingerbread ones. Overclocked and stock kernels work fine though. I have checked and then cross-checked every step required to flash a kernel. What might be the issue?
Being new to XDA, i cant post directly in the development section, else i would have asked the same in Faux's kernel thread. Sorry again!
Related
With talk of late about smooth scrolling and step time between frequencies I got to thinking. What draw backs are there to running at 500mhz with the performance governor?
I know that means it's forcing 500mhz when it could be 200mhz. And while ideally the processor should be as low as possible, 500mhz is pretty low.
But the phone has really felt so smooth! Scrolling is near jitter free and things seem to open much quicker, average smaller things, not intense games obviously.
With screen off deep sleep should be no problem. And how many times does the phone drop down to 200mhz while in use? If I'm not using my phone the screen is off. Seems the the extra battery spent would be made back up by it not going over 500mhz.
So I guess my questions are: Has anybody tried this for am extended period of time? And/or is there really that much processor strain by forcing 500mhz during use?
Sent from my páhhōniē
Huh? Performance governor fundamentally fixes the clock at maximum stock speed (1.2 GHz).
Do you mean setting the minimum for ondemand/conservative to 500 MHz when the screen is on? I do this on my device. When the screen is on, the power consumption difference between 200 MHz and 500 MHz is very small, especially thanks to cpuidle, which gates the clock when the CPU is not loaded, eliminating most of the usual linear contribution of clock frequency to power consumption.
Processor is set to 500mhz max 200mhz min with screen on.
The governor set to performance to keep it at 500mhz while screen is on.
If power difference between 200 and 500 is not that big, then that's how I'm going to leave it for now. Everything has been very stable. No slow downs on normal phone operations, no force closes, no sod's, or soft reboots.
Sent from my páhhōniē
Performance governor fixes the CPU at 1.2 GHz... Not sure what you're talking about.
Not sure why you would want to downclock your device so much.
If you move the max slider in setcpu to 500mhz and set the governor to performance, it pins the CPU at 500mhz, not 1.2ghz
Sent from my GT-P7510 using Tapatalk
K Rich said:
If you move the max slider in setcpu to 500mhz and set the governor to performance, it pins the CPU at 500mhz, not 1.2ghz
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Yahtzee!...er, correct
And so far everything had been great. Stable, no freezes. I did undervolt it pretty low @ 500mhz (dropped it 75mv) and it got choppy. But upped the voltage 25mv and been silky smooth ever since. Battery life hasn't seemed to be effected much. I was hoping for more but aiming to break even. I'm ok with same battery life.
Turkbey rom / latest entropy512's dd
Sent from my páhhōniē
I'm running miui, at 500max on performance I see skyrocket class jittery performance. Maybe its miui vs stock based that's giving that difference. My phone spends most of its time at 500 when not charging or deep sleep, according to CPU spy. So the difference in battery should be minimal, but to me the difference in performance is very noticible. YMMV.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy S II (i777)
Hehe, you're doing the exact opposite of me - I have things set to conservative with 500 MHz minimum when screen is on.
(Why? Because the diff. betwen 200 and 500 in terms of power consumption is far less than the baseline power consumption of the screen.)
Entropy512 said:
Hehe, you're doing the exact opposite of me - I have things set to conservative with 500 MHz minimum when screen is on.
(Why? Because the diff. betwen 200 and 500 in terms of power consumption is far less than the baseline power consumption of the screen.)
Click to expand...
Click to collapse
Same set up here.
Sent from Wernicke's Area
500mhz starting giving me issues. Switched to 800mhz.
Had the phone heat up pretty hot one time. I'm guessing the cpu limit somehow didn't kick in. So instead of performance governor keeping the phone at 800mhz, I set the high cpu limit to 800mhz and the low cpu limit to 800mhz. Since that is now keeping it at the speed I want, the governor can be set to conservative, or whatever you want other than performance, and I don't have to worry about overheating or excessive battery drainage if something goes wrong again.
So far it's been working great. Haven't noticed a change in battery life.
Sent from my páhhōniē
Hi friends,
I wanted to ask that does overclocking damage the mobile processor and decrease its life in any way. I want to use a Megatron rom but i am afraid to do so, kindly help me out.
Another question i wanted to ask is how to check if my mobile is running baseband or new baseband.
I have LG Optimus One Android version 2.3.3 default rom.
Regards,
Pravin
If you installed GB via official update,then you have new baseband.
About overclocking:
Every processor support a max frequency.Mine supports about 710 mhz.But,I overclocked it to 806,put the phone on "set on boot" and it kept rebooting for 5+ times.However,this didn't affected my processor.I don't think that overclock can damage your phone in any way.Also,until 729 mHz you'll get the same battery performances as at 600 mHz.Just OC until 691 mhz first time and play smth for 5 minutes.If it doesn't reboot( also know as KP = kERNEL pANIC) , then go on until 710,729,748,etc.Until you get KP.After,select the last working value and enjoy.
pravin_pran said:
Hi friends,
I wanted to ask that does overclocking damage the mobile processor and decrease its life in any way. I want to use a Megatron rom but i am afraid to do so, kindly help me out.
Another question i wanted to ask is how to check if my mobile is running baseband or new baseband.
I have LG Optimus One Android version 2.3.3 default rom.
Regards,
Pravin
Click to expand...
Click to collapse
I dont think the overclocking can damage the phone, in the worst case it can heat up the phone slightly (which i experienced on stock ROM using franco's kernal)
The worst thing that can happen is that the phone will heat up after 1-2 hours like galaxy s and s2 do in 10 mins...
Sent from my LG-P500
Problems of Overclocking:
1.Decrease in battery life because we are increasing the voltage output.
2.Overclocking causes heating which can lead to damage to other hardware components and again damage to battery.
But since these effects are very minimal and are hardly noticeable(and in with most kernels, processor usage is controlled by good governors) in our phones there is no serious harm in overclocking and will only improve performance.
rishabh22 said:
Problems of Overclocking:
1.Decrease in battery life because we are increasing the voltage output.
2.Overclocking causes heating which can lead to damage to other hardware components and again damage to battery.
But since these effects are very minimal and are hardly noticeable(and in with most kernels, processor usage is controlled by good governors) in our phones there is no serious harm in overclocking and will only improve performance.
Click to expand...
Click to collapse
Heating is not that bad, unless you are a sick gamer or surfer...
Our device uses same voltage for 122-480 and 600-864, so the battery taken is not that bad...
Edit: the phone NEVER gets over 40°C unless there are 35° air temperature, you hold it very hard in your hand or it has a protection...
Sent from my LG-P500
Once I broke my phone with KDZ and took it to Service Center...
When I got it back, they said that also motherboard was damaged. I tried to look like a fool and acted that I'm surprised.
I'm pretty sure this is because of OC. Don't use higher than 787mhz.
Edit: Oh, and before this problem, I got GPS lock in 1.5 minutes. Now it's in about 10 seconds.
vlt96 said:
Heating is not that bad, unless you are a sick gamer or surfer...
Our device uses same voltage for 122-480 and 600-864, so the battery taken is not that bad...
Edit: the phone NEVER gets over 40°C unless there are 35° air temperature, you hold it very hard in your hand or it has a protection...
Sent from my LG-P500
Click to expand...
Click to collapse
Yeah thats why i said the effect is very minimal. And higher the processor usage obviously more the battery usage. So with kernels like the original lg one which does not have a very good governor(as far as i know) the processor tends to stay towards the max frequency range and hence higher voltage.
Yes,overclocking 'too much' can damage CPU and battery life.
Sent from my LG-P500 using Tapatalk
rishabh22 said:
Yeah thats why i said the effect is very minimal. And higher the processor usage obviously more the battery usage. So with kernels like the original lg one which does not have a very good governor(as far as i know) the processor tends to stay towards the max frequency range and hence higher voltage.
Click to expand...
Click to collapse
Conservative is the best stock governor... it looks like interactive actually is much more battery saver than ondemand... which ALWAYS keeps at Max..(this is odd)
I love conservative, I am using it because it takes a minute to get Max performance, but then you have maximum performance... but when you do a short usage and keep minimum frequency at 122, there is a chance you will have no higher than 480...
Also, one thing I recommend is using maximum at 480 when idle and listening to music... phone tends to keep it at maximum always when awake and music in background... and 480 is smooth for small tasks... and really battery save!
Sent from my LG-P500
That's what i think too .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OK lets put it this way..
Computers.. desktop for example.. are well known to be overclock..
CPU problems would be.. HEAT. it causes the processor to malfunction, reboots and worst to be cooked..
since are device is to small and 806mhz heats it up not much to burn.. its ok
but? it malfunction.
and overclocking SHORTENs your processor LIFE. that is true
Bad if too much
We are actually pushing the limits of our phone.
Too much of everything is bad..especially HEAT.
Beat the heat...
Battery drain is not a problem just as "vlt96" says.
It can decrease life of your mobile's processor as maufacturers claim.
729 Mhz or 748 Mhz should be sufficient for medium use.
i m using cm7 stable rom on my p500........with overclocking min 480/max729 ,governor-performance,scheduler-cfg.....
is there any effect of overclocking on battery life or performance on mobile?
more performance but lower battery life.
Mmm ok I have some questions, what is a normal overclock to improve battery life but without sacrificing a lot of performance.
And the other way around, an overclock that improves some performance without sacrificing too much battery.
What are the "optimal" values of an overclock (Without making the phone unstable)
I would just overclock until you get phone instability or you go as far as you can for the current kernel (I'm on AOKP 4.0.4 and it's 787 max which is what I'm at).
Battery life doesn't get affected that much because it's mostly drain when playing games where it ramps up to the max clock speed, at which point you're draining a lot of battery anyways.
Koraboros said:
I would just overclock until you get phone instability or you go as far as you can for the current kernel (I'm on AOKP 4.0.4 and it's 787 max which is what I'm at).
Battery life doesn't get affected that much because it's mostly drain when playing games where it ramps up to the max clock speed, at which point you're draining a lot of battery anyways.
Click to expand...
Click to collapse
Thanks, I also have AOKP so I'm going to work around it a bit, how can I test stability?
Go to Rom Control.. Performance.
Remember to UNCHECK " Set at boot" option.. so that if anything happens.. it can return to default value after a reboot.
If random reboots or white screen appears or phone hangs.. its not stable.
I'll rephrase my question, what type of test can I do to ensure I have a stable overclock. I don't want to find my phone turned off out of the blue and maybe missed an alarm or what not. Thanks anyhow for the tips
Just do general usage. If it works fine for 2 weeks at a specific clock, it's likely to be okay.
kibaruk said:
I'll rephrase my question, what type of test can I do to ensure I have a stable overclock. I don't want to find my phone turned off out of the blue and maybe missed an alarm or what not. Thanks anyhow for the tips
Click to expand...
Click to collapse
You will only know by using. The CPU manufacturers label a chip ancertain speed because it fails a test at the next level. That means that some chips can handle faster than others. They are guaranteed to be stable at the rated speed.
There is no formula
Sent from my LG-P500 using xda app-developers app
Thank you everyone who helped me in here
Overclocking kills lifespan of processor...
Dwars said:
Overclocking kills lifespan of processor...
Click to expand...
Click to collapse
Not necessarily. Voltage and heat are usually what kills electrical components. Since our device can't change voltage for the CPU, that point is irrelevant. However, heat is a factor but AFAIK the heat from overclocking doesn't increase that much for this device, unlike something like PC CPUs so that's fine as well.
Koraboros said:
Not necessarily. Voltage and heat are usually what kills electrical components. Since our device can't change voltage for the CPU, that point is irrelevant. However, heat is a factor but AFAIK the heat from overclocking doesn't increase that much for this device, unlike something like PC CPUs so that's fine as well.
Click to expand...
Click to collapse
No, you can damage it. If it heats up, then:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is unfortunate, it is not even hot so I don't know what's up.
Sent from my LG-E970 using xda premium
There is the temp as says setCPU
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Tim4 said:
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Click to expand...
Click to collapse
I am unsure if this is just over caution on their part of if this is something we need to be worried about... honesty even yours at 39c is not that hot 102 F which for a computer is whatever... but I thought this chip was supposed to run cooler and everything being the new architecture.
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
gafalas said:
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
Click to expand...
Click to collapse
You are right on point. I have seen it drop (I believe to 1180) when running a bunch of benchmarks. The manufacturer sets the heat threshold at a very safe level. Kernel devs are usually able to safely bump that up another 10 to 15 degrees. I am one of the lucky ones that got the variant 3 of the international One X. Variant 3 was the strongest version and I ran all 4 cores at 1600 with 51 minimum. Faux usually figures out how to uncap and raise the throttle temperature... but he's on a N4. I am going to keep an eye on the kernel threads there and see how far they push things. Chainfire's "PerfMod" app is perfect to watch this while running different apps
Sent from my LG-E970 using Xparent ICS Tapatalk 2
Well since I love getting into technical results with this Rezound since I got it, I'm pretty much really late to the game with this phone. My Thunderbolt took a crap on me during deployment and I've been spending the last 2-3 weeks working on it here and there to make it the best battery life for my OWN personal usage.
People may say *Oh dur turn on 4G* I know 4G eats battery, but where I'm at, I get very very spotty signal, Most I use is 3G sending MMS. I keep data off all day since I just text.
Since I get spotty signal, obvious answer is my phone will use more battery for itself. I'm am well aware of this. I have most of the stuff memorized I have done to this phone, rom wise, build.prop, Kernel Tweaker etc. So if you have any questions about what I've done just ask me. It's hard enough to search through a ton of threads and get VERY VERY vague answers. Seems like it's been like this since I jumped on the HTC Inc back in the day
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did take these with my camera because screenshot didn't wanna work properly with me so I just grabbed my camera and shot the pics off. If anyone wants me to post my usuage from yesterday via battery_stats I can.
EclipticRez 5.2.1
Funky v2.3, S2W disabled.
The best results I've found in regards to battery life is with using Kernel Tuner and giving each processor core a different governor (cpu0 Badass, cpu1 Conservative) and underclocking and tweaking some settings in MPdecision. Also, turn off auto-brightness. Take it to around 35-40% and just leave it there.
I also leave LTE on at all times, but I also use WiFi wherever available.
Granted, I don't have my extended battery (yet - just ordered one earlier in the week), but I finished yesterday with 17 hours and 2 hours and a few minutes of screen on time. That's just with the standard 1620 mAh battery.
liqwidzero said:
The best results I've found in regards to battery life is with using Kernel Tuner and giving each processor core a different governor (cpu0 Badass, cpu1 Conservative) and underclocking and tweaking some settings in MPdecision. Also, turn off auto-brightness. Take it to around 35-40% and just leave it there.
I also leave LTE on at all times, but I also use WiFi wherever available.
Granted, I don't have my extended battery (yet - just ordered one earlier in the week), but I finished yesterday with 17 hours and 2 hours and a few minutes of screen on time. That's just with the standard 1620 mAh battery.
Click to expand...
Click to collapse
Well I will defiantly try that out, I was also using auto the whole day since I was constantly inside/outside when the sun was blaring.
What are your current MPDecisions in Kernel Tweaker?
Also in Kernel Tweaker, does it not sometimes load your settings for the CPU? I heard it was kernel related and not ROM related. Sometimes my CPU0 would stay at 1080MHz where I set it at but CPU1 would reset to 1.5Ghz
savagebunny said:
What are your current MPDecisions in Kernel Tweaker?
Also in Kernel Tweaker, does it not sometimes load your settings for the CPU? I heard it was kernel related and not ROM related. Sometimes my CPU0 would stay at 1080MHz where I set it at but CPU1 would reset to 1.5Ghz
Click to expand...
Click to collapse
Mine jumps back up to 1.5 on CPU1 as well, but that's a non-issue. Set it to Conservative. Make sure that the minimum is set at 384 MHz for each core. Otherwise it will just start jumping around (at least, that's what happens to me). I don't know if it's exactly kernel related, though. I was able to run Funky 2.4 on a Sense 4 ROM (Newt's OneXxX 6.0.2, I think) and cpu1 stick, though.
MPdecision:
Service Start Delay: 10000 ms
Pause: 10000 ms
Threshold Up - Load: 40 ms
Threshold Up - Time: 450 ms
Threshold Down - Load: 5 ms
Threshold Down -Time: 250 ms
Idle Frequency: 192
liqwidzero said:
Mine jumps back up to 1.5 on CPU1 as well, but that's a non-issue. Set it to Conservative. Make sure that the minimum is set at 384 MHz for each core. Otherwise it will just start jumping around (at least, that's what happens to me).
MPdecision:
Service Start Delay: 10000 ms
Pause: 10000 ms
Threshold Up - Load: 40 ms
Threshold Up - Time: 450 ms
Threshold Down - Load: 5 ms
Threshold Down -Time: 250 ms
Idle Frequency: 192
Click to expand...
Click to collapse
Thanks. Ya that's what I just set it too. I was using dancedance on both cores when I posted up the screen shots. Will see how it goes for the most of the day. Yesterday I sent out almost 300 texts maybe or more so that was a majority of screen time with 3 different people to say the least.
Oh and another anomaly I can't quite figure out. Some days my phone only pulls less than -100mA and then only ~-20mA on average in screen off sleep. Now today instead of doing the same thing yesterday, todays average has been more near ~ -280mA+ with screen off sleep
I have changed nothing on the phone. Did a restart, no change. Shut phone down completely, pull battery and reboot and still the same result. And even when people ask me what my wakelocks are, I post them and then no one knows what they are nor can I find documentation on the software itself.
did u tried to check it with gsam battery to see what drain or what waking up the phone ?
Try uninstalling some memory intensive apps and reinstall them. Sometimes restored files, for me, just need to be reinstalled.
Also, I just received my extended battery and I'll see how far I can go with it.
How has your phone been doing since the new settings?
Sent from my ADR6425LVW using xda app-developers app