Related
Undervolting and profiles.
I have tried a crap ton of different undervolting setting, but none work
Also the profiles in set cpu don't seem to work for me. I have a few of them set and it always sits on the top one I need some guidence with both please!
Another thing my xda premium app isn't pushing my notafications yes its set
Sent from my MB860 using xda premium
Undervolting is a delicate process. It takes time to find the max undervolt that is stable. With that being said, try undervolting everything by the lowest amount which is -25mv. Check to see if that is stable. If so proceed to go further. Remember lower freq will typically undervolt farther than higher frequencies.
As far as profiles go your probably not using the priority values right. The higher priority is what determines which profile setcpu uses. So for instance if you want a safeguard against overheating, you could set the profile for when the cpu goes above 55C to throttle the processor way down. If you set this profile to 100(max) it will overide all other profiles at 98, 99, 75, 50...etc. Also this may be obvious to some but be sure to tick(enable) the profiles button. If thats not ticked then it doesnt matter how many profiles you have set up. It simply wont use them.
jack_slapped said:
Undervolting is a delicate process. It takes time to find the max undervolt that is stable. With that being said, try undervolting everything by the lowest amount which is -25mv. Check to see if that is stable. If so proceed to go further. Remember lower freq will typically undervolt farther than higher frequencies.
As far as profiles go your probably not using the priority values right. The higher priority is what determines which profile setcpu uses. So for instance if you want a safeguard against overheating, you could set the profile for when the cpu goes above 55C to throttle the processor way down. If you set this profile to 100(max) it will overide all other profiles at 98, 99, 75, 50...etc. Also this may be obvious to some but be sure to tick(enable) the profiles button. If thats not ticked then it doesnt matter how many profiles you have set up. It simply wont use them.
Click to expand...
Click to collapse
When I was on alien rom, I tried 25 on all and it restarted after like a minute. What worked for me was 25 25,50,50,75,75,100 fromm bottom to top. I tried it with cm7 and total no go lol
Lemme tryi 25 on all and see what I get and I didn't know that. They all werent working, so I set them all to 100 lmao, I understand that now
Sent from my MB860 using xda premium
Aparently its been running 125,125,50,75,75,75,75bottom to top cm7 with 1.3 kernel.
It did restart a couple min ago randomly. Will keep posted
Sent from my MB860 using xda premium
Glad your getting some results. If it restarts even once it means at least one of your undervolted freq isn't stable. With your settings I would wager its in the uper freq considering your undervolt in the lower freq isn't too extreme. You might try decreasing the undervolt for your upper freq to -50 -50 -50 starting at the top. Might help to stabilize bc higher freq just require more voltage. If that proves to be stable continue trying to reduce the lower freq as much as possible. Mainly bc if you set your profiles right(screen off is the most important really) your phone will spend the majority of its time on the 200mhz freq. Thus the more undervolt on that freq should theoretically give the most benefit from undervolting. This is just all from personal experience. I'm no guru. Just spent way too much time adjusting voltages on phones . And of course having the upper freq undervolted as much as possible cant hurt either.
jack_slapped said:
Glad your getting some results. If it restarts even once it means at least one of your undervolted freq isn't stable. With your settings I would wager its in the uper freq considering your undervolt in the lower freq isn't too extreme. You might try decreasing the undervolt for your upper freq to -50 -50 -50 starting at the top. Might help to stabilize bc higher freq just require more voltage. If that proves to be stable continue trying to reduce the lower freq as much as possible. Mainly bc if you set your profiles right(screen off is the most important really) your phone will spend the majority of its time on the 200mhz freq. Thus the more undervolt on that freq should theoretically give the most benefit from undervolting. This is just all from personal experience. I'm no guru. Just spent way too much time adjusting voltages on phones . And of course having the upper freq undervolted as much as possible cant hurt either.
Click to expand...
Click to collapse
25,50,50,50,50,75,75
Still getting a reboot:'(
Only good thing about the reboot is it turns on instantly
PROFILES CONFIRMED WORKING trying to indwrvolt this thing
I think I'm gonna order another battery too bc this one isn't getting the 16 hours it was, I cant say much bc I'm screwing with the settings hardcore xD I will show.all settings in a sec
Sent from my MB860 using xda premium
Sent from my MB860 using xda premium
Blahhh
Put blah there so it would post lol. Also going to download a stress test or quadrent thing to test the stress and find maximum uv
Sent from my MB860 using xda premium
Undervolting COMPLETE=D
QUAD SCORE! OCED 1.3 CM7
Right now I'm thinking my battery life is going to be amazig and if I turned the data off when not using it... omg I would last like 2 straight days prolly=D
So pumped to test everything morrow!!
Side note:800mhz or above wont go past 75 >:/
Had really important question to ask you but forgot
Also tried putting 215 to 275 that was a no go lol. My question was is there a battery manager and info like the stock one for cm7?!!!
Sent from my MB860 using xda premium
Smittyzz said:
Undervolting COMPLETE=D
QUAD SCORE! OCED 1.3 CM7
Right now I'm thinking my battery life is going to be amazig and if I turned the data off when not using it... omg I would last like 2 straight days prolly=D
So pumped to test everything morrow!!
Side note:800mhz or above wont go past 75 >:/
Had really important question to ask you but forgot
Also tried putting 215 to 275 that was a no go lol. My question was is there a battery manager and info like the stock one for cm7?!!!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
well my battery was draining mad quick so I am not overclocking It anymore unless I want to show off or play games lol, lost 20% in one hour. Now its stable and undervolted
Sent from my MB860 using xda premium
First off, regarding SetCpu and over / undercloking, dev has said it'll only underclock/overclock ONE core at a time. It's a bug and he's working on it from what I understand. If both cores are needed to be in use at the same time, no over / underclocking will be applied. Secondly, profiles work as they should in SetCpu, so that's a problem on your end. Third, the undervolting can't be more than 100mv differnce between jumps. See screen shot.
http://www.multiupload.com/YUK0KPXZLJ
Phalanx7621 said:
First off, regarding SetCpu and over / undercloking, dev has said it'll only underclock/overclock ONE core at a time. It's a bug and he's working on it from what I understand. If both cores are needed to be in use at the same time, no over / underclocking will be applied. Secondly, profiles work as they should in SetCpu, so that's a problem on your end. Third, the undervolting can't be more than 100mv differnce between jumps. See screen shot.
http://www.multiupload.com/YUK0KPXZLJ
Click to expand...
Click to collapse
I understand the 100 thing and I got the undervolting and profiles done. I hope he gets both cores supported soon and thank you dmfor the reply
Sent from my MB860 using xda premium
Yea Im skeptical about not setcpu not having support for dual cores... Did some searching on the net and couldnt find anything to support that. As far as not the tegra 2 not being able to do over 100mv jumps. That's not true. My lowest frequency is 600mv (-150) and my next frequency is at 750mv. That's a 150mv difference right there... And I'm completely stable. Its entirely dependent on your processor. They are all different and respond differently to undervolting. You just have to find what works for you. Generally though the lesser the jumps in voltage will give you more stability.
a good kernal helps too im useing faux123 v2.0 0C1.3 its undervolts quite well
us/alienv4UL/OC1.3{webtop2sd{fixed}
So I'm interested in undervolting using the stock CPU freq's, and I'm going to be using setCPU (obvi).
So, first question: Even if I want to use the stock frequencies, do I have to be using the OC kernel (0.2.1/1.45ghz at the time)? And then adjust the max to 1000mhz?
Second, I started up SetCPU and whenever I go to the voltage tab it forcecloses. This happens with both the stock enhanced & OC kernel, and I've tried fixing permissions to no avail.
All I really understand so far is that the end result is a table of CPU frequencies and linked voltages. I've OCed the hell out of desktops, but I'm lost here.
I'd just like to know how to get from starting up setcpu to ultimately popping out that new voltage/freq table.
I do apologize if this seems kinda stupid, I'm just trying to exercise caution lest I demolish my phone's innards. I've done it with many an intel.
If you just want stock frequencies, then there's no need for a custom kernel. I guess in that case, you could just use SetCPU for undervolting & profiles.
However, if you want overclock, you'll need a custom kernel.
If you're going to be using a overclocked kernel (i.e. the new Faux 1.45 GHz), then you will need to set the max to 1.45 GHz, and make sure SetCPU is set to start on boot; other wise it will stay at the stock clock speed of 1 GHz... So i guess if you only wanted the OC at certain times, you could set the max speed manually, only when you want to, and not select to start on boot.
I haven't really had any success with undervolting yet... always crashes on me & reboots. The best thing to do is make sure "set to boot" is not selected, when testing your undervolting, other wise you could get stuck in a loop, with the phone crashing every time it boots and tries to apply you undervolting values. I'd start at -25 for each and work from there... stress testing each choice with a benchmark app to make sure you wont reboot... if it reboots, then you know your undervolt was to much. Also remember that you can not undervolt more than -100 between each frequency, otherwise the undervolting will not make any difference.
I really like the profile options in SetCPU... you can set the screen off frequencies to the lowest two, that way for whatever reason your phone isn't running at full strength while your not using it. Also, you can set frequency speeds at custom defined battery levels.
Hope this helps somewhat.
It's unclear to me why it force closes. This may be a rom incompatibility or a SuperUser issue? I assume you've tried uninstalling it and reinstalling it? Updating your SU app? Try flashing to the latest Aura rom?
A few quick words about SetCPU:
1. When you first get started, do not set to "Set on Boot" in case you've undervolted too much and it crashes when applied. You can always check it later once you know the voltages are stable.
2. Between each frequency step there is a maximum of 100mV step off. Anything greater than that it defaults to native voltage. I think this is a Tegra2 issue.
With that said, undervolting is simple: simply slide the little slider on SetCPU to negative values. How much you can under-volt largely depends on your particular hardware and it is inconsistent across all Atrix's. My voltage table is as belows:
1000mhz: -50
912: -50
750: -50
608: -75
456: -75
312: -100
216: -100
I, however, did not test the limits of my phone. Many people will slowly increment the voltage lower until they start to get resets, and then they'll move it back to find the lowest stable point.
It has, however, been well established that minor undervolting improves battery life and diminishes heat generation. Excessive undervolting may actually hurt battery life. You can look around on this forum regarding the data. However, reasonable undervolting will improve battery life.
Thanks fellas, this helps A LOT.
I was so afraid I'd get 17 responses of "You're such a noob. Stop cluttering the forums" etc etc
At this point, I think that the problem is, for whatever reason, the FC when I tap the voltages tab.
I'm on the newest Aura (1.2.2.1) newest enhanced stock kernel from Faux123 (0.2.1) and the newest SetCPU (2.4). I'll try updating my SU (though I believe I did that right after I flashed.
I'll reintall SetCPU and report back.
Until then, THANKS BUCKETS fellas. I really appreciate the info and advice.
UPDATE: May have found the problem. When it first boots up it prompts to autodetect freq's or choose them manually (or something like that). I was afraid this would actually alter my CPU clocks right then and there and so I hit manual detect, saw something that said Tegra2 etc and clicked it. I just now hit 'menu' and set it to autodetect, tried the voltages tab, and no FC, so I think that's solved.
Thanks again for all the info guys! I'll start experimenting and let you know HOW LOW I CAN GO (ha).
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
AdiNova said:
You guys get force closes due to kernel problems. You have to ask your developments. There might be something wrong with some of your cpu voltage drivers. So yeah that's why just a tip. Only overclock when you're playing some high end game. If not stick to normal. If not your phone might get overheated and damaged
Accidentally sent from my Ultra-speedy SG3 using Tapatalk
Click to expand...
Click to collapse
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
xyrovice said:
It's cool bro the problem was totally a user goof by me. I kind of agree with your OC philosophy though, primarily because 1ghz with this proc an RAM seems ample and I don't do much gaming.
Real quick:
When undervolting, should I do it one freq step at a time? Or can I do ALL of them at say -25, stress test, then adjust? Also, what's a good stress test that'll force the proc to hit all the different freqs instead of just the max clock and then the minimum when it's idling/the screen is off?
Click to expand...
Click to collapse
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Swiftks said:
Id start at -25 for all. Setcpu has a built in stress test under info, I think. Could also try a benchmark to test it. As general rule if thumb, then lower frequencies can be undervolted more, while the higher ones take some tweaking... I can't even do -25 on my 1000, b/c ill eventually get a reboot, maybe not right away, but eventually. Every device is unique when it comes to undervolting.... just remember to not set the undervolt part to auto on boot, until you get it somewhat stable.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
xyrovice said:
Got it. I figure that 'set on boot' checkbox is basically a wedding ring ha. Thanks for the advice and insight my friend.
Also (as I run my first stress test with -25 across the board) if I get reboots early on, should I assume it's the higher voltages and that I should back off on the fast end of the clocks?
Click to expand...
Click to collapse
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
ghost_og said:
When testing each frequency just set your min/max mHz to the level your testing i.e. min/max=1000. UV and stress test at that frequency and if it's stable, move to min/max=912 and so on.
FYI, my MHz might be different than yours, I'm on the stock enhanced.
Click to expand...
Click to collapse
That makes perfect sense- limiting the max during the stress test. Thanks for the tip bro I really appreciate it.
Disclaimer: I realize overclocking and tweaking is very much device specific and what works for one person won't necessarily work for another. That said, I've done a fair amount of reading on the subject but need some clarification on the finer points, along with some opinions on what's working for other people. Most of my questions pertain to the Devil kernel, as most of the settings aren't very well explained. I'm running AOKP M6 with Devil kernel and I've set a modest overclock with 200 minimum and 1200 max, which seems to be pretty smooth and stable. I haven't really felt the need to push it yet
1) What governor do you prefer? From what I read in this thread, SmartassV2 sounds the best and so far it seems to be working okay for me. Also, do the profiles matter (smooth, normal, powersave)?
2) Is it wise to mess with the memory settings in the Devil kernel (zRAM, etc) or should I just leave it alone? What about swap files? Worth the hassle or not?
3) What's the difference between using Live OC and the ROM settings to OC? I've left Live OC alone, and just used the AOKP overclocker to set my values.
4) I know that I've read Deep Idle doesn't work for our phones, but what's the Devil idle setting do?
5) Right now the Screen Off- Min/Max Freq setting is off, but should I set the values for that or does the SmartassV2 governor automatically handle it?
6) Any thoughts on I/O Schedulers? From what I was reading, SIO seems to be the best choice, but then again it seems to be all a matter of opinion.
Thanks for any input you might have on the subject
Alright well I think I'm getting a better handle on this since I've had a few days to mess around, and I'll post some of my thoughts in hopes it might help someone else who's trying to mess with OCing. Problem is that AOKP ICS is already so buttery smooth that overclocking really isn't that noticeable of a gain (at least for me).
As far as clock speeds I've been sticking with 200MHz min 1.2GHz max but might just drop back down to 1.0GHz to save some battery life (I don't really run cpu intense apps that often so I don't really see a huge need). I'm not really going to mess with Live OC now that I understand that it overclocks the bus too... I've screwed around enough with PC overclocking to know that it's going to seriously compromise stability which is a risk I'm not willing to take right now (not to mention it'll probably drain the battery a lot more than 'standard' OCing). I've also found that screen off 400MHz min and 800MHz max works well for me, because although 200MHz min will work too, it lags far too much coming back from standby for my liking.
2 things I still haven't messed with are the RAM settings and devil idle (which I assume doesn't work anyway). As far as the RAM I've never once ran into a low memory issue so I don't really think it's worth the trouble (due to reading this forum post I found).
I changed to SIO for the I/O scheduler but really can't notice any difference from just the default, but I'll keep it set there for good measure I guess.
Well that's it for now, if I notice anything else that might be helpful I'll post again, and if anyone wants to jump in with their experience or settings feel free.
Thanks
What settings are best for optimal performance and battery life? I don't have any experience with this, and I don't want to screw anything up. I just got tired of my games always lagging, but I don't want a battery drainer. I dont believe I have a custom ROM. Thanks for any and all help.
NLangan said:
What settings are best for optimal performance and battery life? I don't have any experience with this, and I don't want to screw anything up. I just got tired of my games always lagging, but I don't want a battery drainer. I dont believe I have a custom ROM. Thanks for any and all help.
Click to expand...
Click to collapse
SetCPU probably won't work very well unless you flash a custom KERNEL. You can mess around with it if you like and you'll probably won't mess things up. One thing I discovered before custom kernels came out is that you can enable the second core by enabling profiles in setcpu. YOu can see that in the menu option of setcpu for "cpu". That may help you in your games. If you set max at 1500 and min 192 initially, you'll see that next time you start setcpu, the max and min are both at 1500. I used another app like cpu monitor widget to see what was happening and low and behold the cpu was scaling 'properly', so I left the setting in setcpu at 1500 and 1500.
In the end...it doesn't work quite the way it was designed for and even with custom kernels we're seeing some issues with it, but mess with it, you may find that enabling the 2nd core will produce less laggy games. You'll have to judge the affect on battery.
topgun1953 said:
SetCPU probably won't work very well unless you flash a custom KERNEL. You can mess around with it if you like and you'll probably won't mess things up. One thing I discovered before custom kernels came out is that you can enable the second core by enabling profiles in setcpu. YOu can see that in the menu option of setcpu for "cpu". That may help you in your games. If you set max at 1500 and min 192 initially, you'll see that next time you start setcpu, the max and min are both at 1500. I used another app like cpu monitor widget to see what was happening and low and behold the cpu was scaling 'properly', so I left the setting in setcpu at 1500 and 1500.
In the end...it doesn't work quite the way it was designed for and even with custom kernels we're seeing some issues with it, but mess with it, you may find that enabling the 2nd core will produce less laggy games. You'll have to judge the affect on battery.
Click to expand...
Click to collapse
I appreciate the help! [Thanked]
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Quadrider10 said:
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Click to expand...
Click to collapse
anyone?
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
darkghost568 said:
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
Click to expand...
Click to collapse
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Quadrider10 said:
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Click to expand...
Click to collapse
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Snuzzo said:
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
Click to expand...
Click to collapse
Wheatley is epic.
Sent from my Rezound using Tapatalk 2
loonatik78 said:
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Click to expand...
Click to collapse
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
any ideas on how to fix tht?
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
No frills CPU in play store
Sent from my ADR6425LVW using Tapatalk 2
Quadrider10 said:
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
Click to expand...
Click to collapse
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
Yeah. Don't use DSB's kernel. I spent DAYS trying to figure out what his kernel is trying to do as far as governors. I'm not going to talk smack about the guy's work, but I will tell you what I know.
I doesn't appear any of the governors have been tweaked for his kernel. It looks like code was just tossed in there and left however someone else wrote it. For instance, smartassV2 has a sleep_wakup_freq of .998GHz, which is much slower than it should be. It SHOULD be near or equal to scaling_max_freq. Likewise, the max_cpu_load (which determines when the cpu should scale up) is 70, a fairly aggressive number, while the awake_ideal_freq and sleep_ideal_freq are pointlessly high. If I had to guess, these look like parameters for a Snapdragon S1 SoC, not the dual core S3 the Rezound has. No matter what governor you choose, it's only active on "cpu0". "cpu1" runs ondemand no matter what. The reason you have trouble making settings for the governor stick is because the sysfs location disappears and reappears for no obvious reason. It appears when things pop in and out (presumably when cpu1 goes on and off line), things are reset.
Cold hard reality is this: You're NEVER going to optimize any kernel out there to it's fullest potential. Either the options aren't there to tweak, or they behave in inexplicable ways. I can't tell you why DSB's kernel (not to single out a dev or his work, but I'm certain that's the kernel you're talking about) does what it does, but it's so far divorced from optimized on such basic levels you're better off not wasting your time.
As an aside:
After getting a rough feel for what some of these kernels are doing, I'm not at all surprised some kernels have had significant heat and battery drain issues. There are things that simply do not work right or work consistently. The devs shouldn't be blamed for this. These are probably the issues they're trying to work around that they inherited from the sources they're starting from and what makes tweaking them so difficult.
I acutely got everything to work. I'm just trying to overclock the GPU.