Related
Hi there,
I'd like to overclock my IncS to 1,3 Ghz...
But I don't know the right settings.
Can you please tell me the right setting for best performance (e.g. oc to 1,3ghz) and best battery life?
thanks
does anybody know?
Set max to your desired, min to the lowest it will go and scaling to smartass.
I'm OCd to over 1.4 and no issues... UCd to 192 with smartassv2 governor
Sent from my Incredible S using XDA App
the best performance I have experienced in my INC is when I put oc / uv beater to the following:
wake gov: ondemand
wake mins: 245000
wake max: 1228800
Sleep gov: Conservative
my sleep: 245000
Sleep max: 691200
when I take a test in antutu nenchmark for I the following result.
score: 2729
If I clocked lower or higher, the result is lower
Overclocking depends entirely on your chip.
You should use whatever governor suits your needs.
I personally use ondemandx which speeds up on demand (as the name implies), conservative tries to keep the frequency as low as possible, interactive uses max frequency if min isn't enough, smartass is an improvement of interactive that keeps performance high while improving battery life (meaning there's little reason to use interactive).
You can find it in more detail here.
So basically, smartass if you want performance, conservative if you want battery life, ondemand if you want something in between. In reality though, I don't think you'll see much difference between them and I've seen no difference in idle power draws, so if you don't use your phone all that much, they won't be that different.
Once you've picked a governor, you should set min speed to 122000 (no reason to use any higher) and max to whatever you want. Your phone will probably crash or suffer from bad performance if you go over 1.5 GHz, but it varies a lot. Might happen even earlier.
Once you've found your desired performance level, you should start tweaking your voltages. You can do that under the UV profile. In there, you can adjust voltages at different speeds and the phone will automatically use them at whatever speed it's at. You should undervolt to increase battery life, so start by reducing all by 25 or 50 and then temp apply. Use it like that for a couple of hours and if it doesn't freeze, you're probably stable. You can either stop here or spend many hours tweaking it further, but that'll take many hours to get right.
This is my setting
Sent from my HTC Incredible S using xda premium
Which would be the best O/C program out there ?! I have SetCPU, Daemon but I'm sure there is better in the market...... just need to know the name so I can get it Thanks!
I'm currently 230MIN/1150MAX
Me4oKyX said:
Which would be the best O/C program out there ?! I have SetCPU, Daemon but I'm sure there is better in the market...... just need to know the name so I can get it Thanks!
I'm currently 230MIN/1150MAX
Click to expand...
Click to collapse
In my opinion, and I'm sure many others', Virtuous daemon is the best by far.
It comes standard in a lot of roms, and using the OC/UV beater
http://forum.xda-developers.com/showthread.php?t=1207546
it would have the best performance. I've set mine similar to yours and with this method, you can set the phone to underclock when battery reaches a low level
Ever since I flashed the 213 leak, battery life has been a bit disappointing. To help things along, I downloaded SetCPU (haven't used it since my good ole OG Droid) and let it autodetect settings. To my surprise the governor was set to 'interactive' instead of hotplug like it was on stock GB.
My understanding is that hotplug allows the phone to disable unneeded cores during periods of low utilization, while interactive does not (although both cores can be disabled when the phone is sleeping). Do you think switching to hotplug from interactive will improve battery life?
My battery life is much better since switching, but I also disabled 4G (on WiFi most of the time) and added screen off and low battery profiles (600mhz and 800mhz max respectively) which muddy the waters a bit. I thought I would mention it on here for those of you who feel the same, it might be an easy way to improve battery life on the leak.
That's interesting. I've been using the .213 leak and my battery life has been quite good. I haven't noticed any particular drop in battery life, and I keep 4G on all the time. If I don't use my phone much, it's not uncommon for me to have 60% left at the end of the day.
Do you use anything like SetCPU? I am wondering whether I can confirm that the default governor of the leak does not shut off one of the CPUs when it is idle. If nobody can confirm I'll get around to checking it myself this weekend :laugh:
Sorry, I haven't messed with my cpu settings.
I have just updated to Cyanogenmod 7.2 stable on my P990 Optimus 2x (Fido Canadian version).
When I go to the CPU settings I cannot change the min/max frequencies or select a CPU governor.
I have done some research and found kernels like Vork and FauxDS, but they are for 7.1 nightlies so I am not sure if it is a good idea to flash them.
What I am most afraid about is the possibility of getting the black screen of death while my phone sleeps (it happened once already but it stopped after I changed to a different charger and reflashed CM7.2).
The reason why I want to change the settings is that there tends to be scrolling lag (my old HTC Desire Z was faster!) and there is also a bit of lag waking up the phone (lockscreen does not appear instantly when pressing power button).
Does anyone know what is the best kernel I can flash to enable frequency/governor changes in CM7.2 stable? I would prefer not to change the ROM if possible as I am kinda nooby in comparison to the XDA community in general. Thanks for any help.
I suggest you try Etana kernel. It has the things you need. Also use CPU master to set profiles and minimum CPU frequencies. I used something like min freq 352 MHz when asleep (don't worry doesn't drain battery) and I had no lag whatsoever.
heavencanwait said:
I suggest you try Etana kernel. It has the things you need. Also use CPU master to set profiles and minimum CPU frequencies. I used something like min freq 352 MHz when asleep (don't worry doesn't drain battery) and I had no lag whatsoever.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1427646 ?
If so, do I just flash the zip off the sd card using ClockworkMod? And what are the differences between lite and DS?
Thanks.
All right, after reading, I determined I don't need LOC/HOC/DS as I don't intend to raise the max frequency, I just want to raise min frequency.
Installed the Etana kernel via CWM and it works. I can raise minimum frequency, though I still cannot see a governor option! Any idea how to get my governor setting back?
You can use CPU master and set some profiles. It's not exactly the same as governors but it's as close as it gets and it gets the job done pretty well. As far as I remember there were two governors for O2X - powersave and performance. I've always used performance and I can't tell if there's a HUGE difference in battery usage. I guess performance utilizes higher CPU frequencies when the device is asleep and somehow scales faster to even higher frequencies when needed to. But this might be complete crap as I am not too much into how CPUs work...
And please use the THANKS button (right below the user name), it kind of forum etiquette and it keeps people motivated to help others. Thank the Etana developer too.
heavencanwait said:
You can use CPU master and set some profiles. It's not exactly the same as governors but it's as close as it gets and it gets the job done pretty well. As far as I remember there were two governors for O2X - powersave and performance. I've always used performance and I can't tell if there's a HUGE difference in battery usage. I guess performance utilizes higher CPU frequencies when the device is asleep and somehow scales faster to even higher frequencies when needed to. But this might be complete crap as I am not too much into how CPUs work...
And please use the THANKS button (right below the user name), it kind of forum etiquette and it keeps people motivated to help others. Thank the Etana developer too.
Click to expand...
Click to collapse
Thanks for letting me know, I didn't realize there was a thanks button at first haha.
Fixed!
As for now CPU Master in his profiles let's you choose governor. We have only 2. Power save nd Performance.
Sent from LG 2X using Tapatalk 2 Elite
{
"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"
}
TEAM INSOMNIA PRESENTS THE SPEEDY GONZALEZ KERNEL
DISCLAIMER: WE DO NOT TAKE ANY RESPONSIBILITY TO WHAT HAPPENS TO YOUR DEVICE. FLASH AT YOUR OWN RISK
CHANGELOG 12/10/2012 V1.5.5
-REMOVED SMARTASS2 SINCE IT WAS CAUSING PROBLEMS
-UPDATED SPLASH SCREEN IMAGE THANKS TO MRAZNDEAD
CHANGELOG 12/09/2012 V1.5
-ADDED MORE OC FRENQUENCIES
-ADDED VOLTAGE CONTROL (I SUGGEST USING SYSTEM TUNER)
-OVERALL A LOT OF CLEANING UP
CHANGELOG 12/02/2012 V1.4
-INCREASE VOLTAGES FOR OC FREQUENCIES
-FIXED USB CHARGING
-MORE SPEED TWEAKS
-OVERALL MORE STABILITY ACCORDING TO TESTERS
CHANGELOG 11/22/2012 V1.3
-INCREASE VOLTAGES FOR OC FREQUENCIES
-MAY OR MAY NOT HAVE FIXED USB CHARGING
-MORE SPEED TWEAKS
DOWNLOAD: SpeedyGonzalez-v1.5.5
DOWNLOAD: SpeedyGonzalez-v1.5
DOWNLOAD: SpeedyGonzalez-v1.4
DOWNLOAD: SpeedyGonzalez-v1.3
DOWNLOAD: SpeedyGonzalez-v1.2
CM9 DOWNLOADS
DOWNLOAD: SpeedyGonzalez-CM9-v1.2
DOWNLOAD: SpeedyGonzalez-CM9-v1
FEATURES:
-OC UP TO 2.0
-ADDED SMOOTHASS, LULZACTIVE GOVERNORS
-UPED VOLTAGE A LIL BIT
-MISC SPEED AND BOOT TWEAKS
-MISC SD SPEED TWEAKS
-BUILT WITH LINARO TOOLCHAIN 4.6
FOR MORE FEATURES CHECK OUT MY GITHUB
HOW TO FLASH:
DOWNLOAD
PUT ON SD CARD
BOOT INTO RECOVERY
WIPE CACHE
FLASH KERNEL
FIX PERMISSIONS
REBOOT
Source- github.com/smartguy044
OK GUYS HERE IT IS THE INITIAL FIRST PREVIEW FOR KERNEL 3.0.XX FOLLOW THE FLASH DIRECTIONS IN THE OP*
DOWNLOAD: HERE
*VERY VERY IMPORTANT PLEASE READ BEFORE YOU FLASH OR REPORT ANY PROBLEMS*
OK GUYS I HAVE DONE A LOT OF RESEARCH ON OUR CHIPSET AND PHONE. FROM WHAT I HAVE COLLECTED OUR CPU IS ONLY OVERCLOCKABLE UP TO 1.45. WITH THAT SAID YES A LOT OF PEOPLE HAVE OC TO 1.6+ WITHOUT ANY ISSUE INCLUDING MYSELF. *IMPORTANT* DO NOT COMPLAIN OR SAY THE KERNEL IS BAD IF YOU EXCEED THIS NUMBER AND GET BUGS. ALL CHIPS ARE NOT THE SAME SOME CAN GO TO 2.0 SOME CAN ONLY GO TO 1.2. ALSO IF YOU ARE RUNNING ANY TWEAKS OTHER THEN THE KERNEL (PMR ETC.) DO NOT COMPLAIN ABOUT BUGS UNTIL ALL TWEAKS HAVE BEEN REMOVED AND KERNEL TESTED AGAIN. I TEST EACH KERNEL ON MY PHONE AND WITH MY SETUP. I DO NOT USE ANY OTHER TWEAKS OTHER THEN THEN THE KERNEL ITSELF AND IT RUNS FINE FOR ME. THANKS HAVE A GREAT DAY
OK GUYS SO I BROWSED AROUND AND FOUND THIS GUIDE FOR UV/OC SO THANKS TO Klathmon FOR PUTTING IT OUT
It seems alot of people dont know the proper way to undervolt their phones, so I'm gonna try to help out! This is my first attempt at a guide, and i tend to ramble so just tell me if it makes no ****-for-sense
Undervolting is great, it allows us to change the voltage in our phones while we use it! this can really increase battery life and reduce heat in the phone. but if its not done right, it causes many more problems than it fixes.
When you are following this guide you WILL have issues! This is not a generic disclaimer, it is the TRUTH! the goal here is to find out where your phone stops working, and you cant do that without causing it to STOP WORKING.
once again: THIS WILL MAKE YOUR PHONE FREEZE, IT WILL HAVE AWFUL BATTERY LIFE, AND IT WILL MAKE BAD THINGS HAPPEN
But after its all done it should work much better
To start off, too much or too little voltage in the phone causes any number of things including:
Reboots (Screen Off and Screen On)
Lagging
Phone Overheating (Hot to the touch)
Reduced Battery Life (this includes the phone using more power, as well as reducing the battery's ability to hold a charge)
'Strange' issues with things shutting off/not working (WIFI, Bluetooth, your favorite app, ect...)
Many other 'weird' things
If you are having any of the above issues, and you are using a custom kernel, they may be caused by inproper undervolting.
THIS CAN BE THE CASE EVEN IF YOU HAVE NOT DONE ANY UNDERVOLTING YOURSELF!!!
Most custom kernels have undervolting build into them, and even 'stock voltage' versions allow overclocking, and those frequencies have no 'safe' voltage associated with them.
How to Properly Undervolt your Phone:
*this assumes you have no idea where to start, if you have some past experience, USE IT!!!*
First, Undervolting a phone the right way is not a quick job, like most things in life the more time you put into it the better your end result will be. For me i like to take an ENTIRE WEEK OR MORE to get all my settings down right. whenever you decide to do this, expect any and all of the issues i listed above to happen while you are trying to find the right settings.
Step 1: Starting Fresh
Disable all overclocking, undervolting, AND PROFILES on the ROM, you need to get the stock speeds working before you try to push the phone to its limit.
This will be your baseline. Use the phone like you normally do, text, call, surf the web, even let it sit in your pocket for a while. Do this for as long as you need to to be sure that everything is stable.
If you have any issues during this stage. STOP! add +25mv to every frequency across the board and start over. Do this up to 3 times if necessary, if after you have added +75mv to your stock voltage and you are still having issues, it is most likely something else in the rom causing the issue (rogue app, wrong kernel version, phone was dropped in the toilet too many times...) try to fix that first, or just try to ignore the issue, its up to you.
Otherwise, if everything is stable, Continue to step 2!
Step 2: Start Lowering Voltages
Lower all of the voltages by -25mv across the board. (If your phone needed any voltage added over stock to be stable, skip this step.)
This is where you begin testing the waters. Once again use the phone like normal, including some screen off time, as well as some CPU intensive tasks (playing music while websurfing, gaming, ect.)
If your phone is still stable after a good amount of time, then do it again. Your looking for the moment when things start to go wrong.
When you notice your first random reboot, or you start to feel the phone getting hot, or not responding STOP! you found the limit of your phone. Go back to the last working voltages you have and use them for step 3.
The more time you spend at this step the better your overall result will be! if you dont get any symptoms in an hour, they might show up later in the day, or overnight. Just take your time and have some patience.
Step 3: Lowering Voltages Independently
Now that you have a stable working phone. you can start lowering voltages one by one!
Starting with the lowest frequency, lower the voltage by -25mv.
Run this for a while, until you feel it is stable. Then move to the next highest voltage and do the same.
*If you have any issues, undo ONLY that frequency!!! Write down that frequency somewhere. you are done with it! you know that frequency is stable, and you shouldn't need to touch it again!!!
Keep doing this till you get to your stock maximum frequency, then continue to step 4!
*NOTE:* if any 2 voltages have more than a 100mv difference (125mv difference on Morfic's Kernels) between them, you need to raise the others around it to be equal or less than that. For exampe:
if at 1ghz, the phone is at 1000mv and at 1.2ghz the phone is at 1150mv. the higher one needs to be lowered (set 1.2ghz to 1125mv). if that is not stable for you then you must raise the lower one higher (set 1ghz to 1025mv).
Step 4: OVERCLOCKING!
At this point you should have a completely stable phone with no overclocking, grats! Now you get to start raising the frequency.
starting with the next highest frequency, set it to its stock voltage. if this is more than 100mv (125mv for Morfic's kernels) more than the previous frequency, set it to 100mv (125 for morfic) more than that.
run this until it is stable, and keep reducing it as much as you feel until you find instability. set it one step higher and move on to the next highest frequency.
if, after setting the voltage to 100mv (or 125mv) more than the last one, it is not stable, you need to raise the lower frequency's voltage up. sometimes this can cause a chain reaction that makes you raise 3, 4, or even all of the other frequencies up, if this happens you need to decide if that frequency is worth it to raise all the other frequencies to the next level.
If all is running good, proceed to step 5!
Step 5: The part where you hate me
(this step is optional, its just something i do to help with stability)
Now that you have a fully overclocked phone that is running as low of a frequency as it can safely, raise all of the voltages up by +25mv!
yes yes, i know, it sounds retarted to just undo that hard work and all that time you just put into finding the perfect voltages, but just hear me out.
Even if you spent a week on each step, did everything perfectly and tested everything you ever do on your phone and it is all completely stable. one day you are going to do something that will push the phone, which is running at its limit. so by adding 25mv to everything you are giving yourself some insurance. you may loose some battery life (i honestly don't ever notice a change with only 25mv) but when your phone alarm goes off in the morning to get you up for class, or you get that call you got that job you wanted, just be happy its not frozen on the table, or black screened in your pocket.
There you go! you should now have a stable phone with great battery life, and now you can stop bugging the devs about 'that strange reboot that is still there' or 'how every time you use his kernel you get black screens'
Click to expand...
Click to collapse
Android CPU governors explained
Credits!!!!
Deedii for taking the time to compile all this!
Click to expand...
Click to collapse
Android CPU governors explained
1: OnDemand
2: OndemandX
3: Performance
4: Powersave
5: Conservative
6: Userspace
7: Min Max
8: Interactive
9: InteractiveX
10: Smartass
11: SmartassV2
12: Scary
13: Lagfree
14: Smoothass
15: Brazilianwax
16: SavagedZen
17: Lazy
18: Lionheart
19: LionheartX
20: Intellidemand
21: Hotplug
1: OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.
OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.
This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.
2: OndemandX:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.
3: Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
4: Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
5:Conservative Governor:
This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.
The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.
6: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.
7: Min Max
well this governor makes use of only min & maximum frequency based on workload... no intermediate frequencies are used.
8: Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.
9: InteractiveX Governor:
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
10: Smartass
Is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
11: SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.
12: Scary
A new governor wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
13: Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.
14: Smoothass:
The same as the Smartass “governor” But MUCH more aggressive & across the board this one has a better battery life that is about a third better than stock KERNEL
15: Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery
16: SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.
17: Lazy:
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.
18: Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source.
The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.
19: LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.
20: Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors)
To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.
21: Hotplug Governor:
The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."
Obviously, this governor is only available on multi-core devices.
Click to expand...
Click to collapse
Awesome, thanks man
Sent from my 1.8GHz Linaro optimized Nexus 7
no problem im gonna try and do a lot more with it but this is a great improvement over stock
This is EPIC!!!! :laugh:
Great work dude!!!!
Phone locks up at 1804
Sent from my 1.8GHz Linaro optimized Nexus 7
no problem guys now if we can fix the camera issue for cm10 roms this will be a device worth keeping
IRX120 said:
Phone locks up at 1804
Sent from my 1.8GHz Linaro optimized Nexus 7
Click to expand...
Click to collapse
haha i havent went above 1.6 thats plent smooth for me :silly:
smartguy044 said:
haha i havent went above 1.6 thats plent smooth for me :silly:
Click to expand...
Click to collapse
I'll run a bunch of different tests and benchmarks either tonight or tomorrow to try to find the "sweet spot"
It's hard to say what everyone else's sweet spot will be though, as every chip is different. I think I'll be happy as long as I can get 1.4 without any adverse effects.
yea i ran 1.4 for a couple days then tried 1.6 and its fine....this is the best experience i have had with an oc kernel on any device i have owned
1.6 is fine, 1.8 locks up.
On my nexus 7, if I go above 2ghz it locks up, these CPUs aren't designed to go that high
Sent from my 1.8GHz Linaro optimized Nexus 7
yea its only a single core cpu so dont wanna strain it to hard
Freezing in 1.6 guess my phone is overheating on boot
Sent from my 1.8GHz Linaro optimized Nexus 7
thats no good ive been running 1.6 since yest with no problems
smartguy044 said:
thats no good ive been running 1.6 since yest with no problems
Click to expand...
Click to collapse
I was running benchmarks. Let my phone cool down and its fine now.
Great work
Sent from my SGH-T679 using xda app-developers app
Thanks man.....once we figure out camera I'll do some more work on kernel but it took me about 4 days non stop to get it to this
Sent from my SGH-T679 using xda premium
I'm going to try this with CM7, will report back.
Sent from my SGH-T679 using Tapatalk 2
Did you fix the USB problem?
Sent from my SGH-T679 using xda app-developers app
yes sir thats what i have been waiting on before releasing it
Q&A for [KERNEL][D5803&D5833] AndroPlusKernel
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][D5803&D5833] AndroPlusKernel. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
Very nice kernel, fast and smooth - great work and port.
Anyone knows if it's possible to use any third party kernel app to boost the headset volume?
Working
Hi this is my first post, infact I joined so I could report my findings.
I would just like to confirm so far that V5 working on my Z3C using the .93 firmware. I didn't need to wipe cache/dalvik/data partitions either.
For purposes of settings configuration, I'll be using TricksterMod
For stress testing purposes I'll be using Stability Test 2.7
Overclocking
Overclocking seems to work, I'll stress test and report back with the results.
I was wrong, it is unstable when overclocking and stress testing, with the phone force rebooting 1-5 seconds in to the stability test which loaded all 4 cores. Tried 2899Mhz and 2880Mhz (were both unstable and didn't try 2.72, 2.75, 2.57 either - I might try stability testing them.) Was completely stable at 2.47GHz, and it actually stuck there, no throttling in place! I stopped the stress test when the CPU temp was around 77-80C as my hand was getting burnt! The battery temp reached about 46C. It took 10 mins of stress testing for this to be reached. When the stock kernel was in place it would begin throttling after about 1-20 seconds under full load. First 2.2GHz, then 2 then 1.7 then 1.5 and eventually 1.25 after about 2-4mins.
I couldn't do a single core test though. I suspect as most games use single core or dual cores it wouldn't get overly hot.
My opinion is that fast clocked phones should be marketed with 2 speeds. The highest it'll reach under a boost mode (turbo for Intel's i5 and i7 series), and a slower speed that it'll average out at under thermal pressure. The Z3Cs would be turbo: 2.5GHz and normal: 1.5GHz.
Governors
These are quick tests I'm performing here to provide a quick look at responsiveness and potential unnecessary CPU jump ups.
Wheatley - most of the time it's hovering at top speed when approx CPU usage is 9%, it'll occasionally hunt down to 300Mhz but then right back up to 2899MHz. This one is speedy though. Governor tunables available.
Lagfree - idles at 300MHz - 960MHz then hunts up to 2.2-2.9Ghz when needed and turns on the second core. It seems to slow back down to idle. This one seems to have fast scrolling, sliding notifications pane quickly). No governor tunables.
SmartassV2 - idles at 300Mhz, speeds up to 422-960 on core 0, and turns on core 1 at 1.2-1.5GHz for a few seconds under fast scrolling and notification pane opening. Seems quite responsive. Probably good for battery life hopefully with the responsiveness of Interactive. No governor tunables.
Lionheart - Idles at 960 MHz for a few seconds then slows down to 300MHz with the odd increase to 729MHz. Core 0 and Core 1 reaches 1.26GHz under scrolling, notification pane opening. As fast as the others. Governor tunables available.
Hotplugging
Intelliplug appears to work better than MP-Decision - now only one core is on during idle, instead of 2.
MP-Decision was disabled to avoid conflicts.
Undervolting
I've only undervolted 300MHz to 675MHz from 775MHz as of writing this post.
Tried quickly undervolting in trickstermod by setting them all about -75mV, stability tested it, appears stable. I'll tweak the voltages a bit better when I do a scaling stability test.
Issues I've experienced
Sound Control is the only thing so far that causes a reboot. However music still plays over the speakers and headphones. Equaliser works too.
Upon rebooting, the CPU top speed will set itself to 2.2GHz, despite being set higher and saved at a higher speed in Trickstermod. Certainly trivial though.
Strange thing I've noticed: On the undervolt part I've noticed that there is a freq called 3033MHz, but no 2899MHz freq. Just an observation.
Misc
Force Fast Charge confirmed working! Before flashing new kernel charge went up 5% in about half an hour. It's now up another 5% in a matter of 5-10mins. This is when plugged to my PC.
Vibrator strength - set to 20 from 31, much quieter on table and can still feel it.
I'd like to say a huge thank you to DooMLoRD and AndroPlus for developing this stable kernel. Now my Z3C is worth the £28 a month I'm paying for again. Since this silly lad decided to bork the camera, Bravia functionality etc by rooting it on the first day. I'll report back and edit the post with my findings.
Max won't go beyond 2.266 GHz, Min won't change.
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
pjmanalo said:
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
Click to expand...
Click to collapse
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
DBCJoey said:
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
Click to expand...
Click to collapse
Thanks! That did the trick!
Odd that my usual app for the job across 4 other phones - SetCPU - doesn't work on what should essentially be the same job. [emoji55]
Please make sound_control drivers work so its possible to boost headphone volume on the Xperia Z3 Compact... Thanks
Nice work, a lot of updates I like it!
Is it possible to add a change log?
Thanks!
kernel for d5803 with the .93 but not .105
i search a kernel for the d5803 with the last .93 french version of phone
.5.77
Works great! Thanks a lot
Link for Z3C_D5803_AndroPlusKernel_v10.zip is dead
Pls upload in another location.
Yay sound control is working, thank you so much you're the best!
How to make this?
Hi AndroPlus,
I'm trying to figure out how one would go about building this boot.img that you've created.
What platform and compiler are you using?
Where are you getting sources the for the kernel? This file?
c9af6fc647060fb85dd646798453ec8f 23.0.A.2.105.tar.bz2
How do you construct boot.img from zImage + recovery?
Sorry if these are dumb questions.
Edit: never mind, I figured this out.
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/ contains most of the information I needed.
The arm version of gcc that ships with Ubuntu 14.04 worked fine - arm-none-eabi-gcc (4.8.2-14ubuntu1+6) - no need to track down any mystery binaries. I did have to make several modifications to the kernel source to get it to build. Interestingly, some of the cpufreq stuff contained code that was incorrect. Someone at Samsung needs to go look up what "sequence point" means.
The hardest part was figuring out how to turn the zImage + ramdisk into something I could boot.
This: https://github.com/sonyxperiadev/mkqcdtbootimg was the correct tool to use - again, no need to track down any mystery mkbootimg or dtbTool binaries.
Hope this is helpful to someone. As someone new to Xperia dev, I found most of the information out there worse than useless.