Database Develop

DX/D2 Overclocker

Sorry for not posting this sooner everyone. But if you want to check out the first DX/D2 Overclocker to hit the market here are a few screens:
{
"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"
}
One of the key features this one carries is you can have as many presets as you want and as an integrated stress test feature to see if your settings are happy or not. There are also some new safety features coming today and something big I can't speak about tomorrow or Wednesday.
If you have any comments or ideas, let me know. I always want to improve things!
Thanks.

I can vouch for this product. Very nice layout and the settings work as advertised. I can't wait to see what you have up your sleeve!

Nice app! I like the presets. Gives you a good place to start from.

Nice app OP!

working for me so far, nice work. i was hoping i wouldnt have to go through the files like in the tutorials...
quadrant was like 1375 or so, now i hit 1485. not bad i think!

How can I test the overclock? I see always this bar graph on the forum but don't know what it is.
I have a blur X and was wondering if I could make it quicker without loading a custom ROM
Thanks
Ohh in the market in the app description make it in bold that it is only for the DX and D2 I think people are using it on other phones and that is why you are getting negative reviews. I'm thinking on getting it this week

Venc said:
How can I test the overclock? I see always this bar graph on the forum but don't know what it is.
I have a blur X and was wondering if I could make it quicker without loading a custom ROM
Thanks
Ohh in the market in the app description make it in bold that it is only for the DX and D2 I think people are using it on other phones and that is why you are getting negative reviews. I'm thinking on getting it this week
Click to expand...
Click to collapse
That bar graph you are most often seeing is people running the benchmark "Qaudrant". Go download it from the Market, it is free.

Real time CPU scaling and current speed are in 1.3.2 that just hit the Market. Enjoy.

I was wondering how the stress test works, everytime I use an OC setting and use the stress test and try to send a text it locks ups, no matter what speed im using. 1.45GHZ works but locks up after use without stress testing, and 1.40GHZ works fine until put under a lot of stress, but drains battery fast so ive been messing around wit the settings. Whats a great way to test my settings?

The Stress Test litterally just goes to town on your poor phone. It calculates PI to 800 decimal places over and over and over again until you tell it to stop. I don't recommend trying to do anything else while it is going. Just let it run and see if it craps out. Then be sure to stop it

gweedo767 said:
The Stress Test litterally just goes to town on your poor phone. It calculates PI to 800 decimal places over and over and over again until you tell it to stop. I don't recommend trying to do anything else while it is going. Just let it run and see if it craps out. Then be sure to stop it
Click to expand...
Click to collapse
Alright thanks, how long should I let it run?

AsaSpades said:
Alright thanks, how long should I let it run?
Click to expand...
Click to collapse
How long you let it run is up to you.
I typically start it then set it on my desk while I cook dinner/take a shower/do chores etc..
When I am done I check it out and see if it crapped out or not.
Also, I have tried all 3 methods currently available for OC'ing our X's and (in my opinion) this is the best out of them.
Nice user interface, some good starting points for OC'ing and with the latest build you get current/max/min clocks and battery temp.
Now, he just needs to add current voltage so I know what speed and voltage my X is pulling at that time.
OH, and some kind of log would be tits as well.
(Just thinking out loud)
D.

I keep getting the "oc in 90 seconds" pop up randomly even though I turned it off and applied settings...seems to be on anyway .. Many reboots and still getting the message

adammsu said:
I keep getting the "oc in 90 seconds" pop up randomly even though I turned it off and applied settings...seems to be on anyway .. Many reboots and still getting the message
Click to expand...
Click to collapse
Yep, I have noticed that as well.
I thought it might be memfree I was running, so I uninstalled it this morning and will see if that makes it go away.
If not, it is only a minor annoyance.
D.

debaucher said:
Yep, I have noticed that as well.
I thought it might be memfree I was running, so I uninstalled it this morning and will see if that makes it go away.
If not, it is only a minor annoyance.
D.
Click to expand...
Click to collapse
i agree, only minor, IF IN FACT that it really has been overclocked the whole time., and isn't dropping up and down all day.

I also have been having the same issues but I thought it was just me.
Sent from my DROIDX using XDA App

AsaSpades said:
I was wondering how the stress test works, everytime I use an OC setting and use the stress test and try to send a text it locks ups, no matter what speed im using. 1.45GHZ works but locks up after use without stress testing, and 1.40GHZ works fine until put under a lot of stress, but drains battery fast so ive been messing around wit the settings. Whats a great way to test my settings?
Click to expand...
Click to collapse
I think the problem here is the 1.45 ghz. To increase the Frequency that drastically, you also need to increase voltage. With a voltage setting too low you will lock your phone. The closer you get to a stable VSEL value the more you will be able to do before it locks up. That is why the stress test is so powerful a test to determine if the voltage is appropriate. When at 1.40 ghz your voltage must be close to stable if you can use under lite usage, but if you can only use it lightly, why OC so drastically?
Another App in the market, Droid x/2 Overclock, gives an advised list of frequencies and the VSEL value, and for 1.45 ghz, it advises 82 VSEL as the starting point. which is about 33% more power than it uses at stock frequency (62 VSEL). This is why you said you are tearing through your battery much quicker.
To alleviate the added draw, what I do, is run 2 settings, I leave it undervolted and clocked down to 750 mhz for every day use (barely notice a difference from stock performance) which increases my battery life to 35 hrs + and have a second setting for things like Emulators clocked up to 1.45 ghz running 78 VSEL very stable, never locks up. The added step is worthwhile to me since it both saves the added strain on the processor, Less Heat, and drastically Increases Battery Life.
If you insist on leaving it full blazing 1.45 ghz, get SetCPU (also in the market) and set profiles that can down control power, ie when my screen is off, the CPU is capped at 300 mhz. For the most part the Android OS already controls this pretty decent, but I like to be able to manually control it myself.

I would really like to see the application stop the service after it does it sets the clock after 90seconds.
As it stands now, I force stop it every boot.

Suckerpunch #50 not running at 1.4ghz??? *RESOLVED*!!!!

Ok. i have refraind from asking questions for quite some time. I have lurked, and read and read and read. i learned how to flash roms and kernels and most otherthings i want to do without bothering anyone with noob questions...up until now.
I flashed the suckerpuch #50 kernel in attempts to try out 1.4ghz, but unless im completely missing something my phone dosnt ever seem to go above 1 ghz on this kernel. im not positive this is the case, but heres what leads me to beleive it:
cpu usage widget on my screen never shows above 1ghz, while a different 1.2ghz OC i tired shows it peaking up to 1.2 right after boot, and if i exit quadrant it shows 1.2 for a sec before dropping back down, same with any 3d game, when i quickly close it and look at the widget, it will show running at 1.2. Yet suckerpuch never shows above 1.0 UNLESS i run CPUsetting and set it to "performace" which it then appears to be running at 1.4 AT ALL TIMES, and the phone isnt stable so thats a no go.
am i missing some key piece of information here? did i flash it wrong? is there some other type of modification i need to do to get it to actually run at 1.4?
ive read through the suckerpunch #50 opening posts multiple times and i believe it tells me i need to modify some file or other, possibly, but im not understanding.
any info/help would be much appreciated!
P.S. this forum, the devs, and all the things supplied to make my phone awesome are absolutley great.

I believe SuckerPunch is set to 1Ghz as default unless you change the setting with Voltage Control (or SetCPU). Mind you that 1.4Ghz is not run well on a lot of devices and may cause freezing. And I'm glad some people take up reading before asking questions

p.p.s- im aware not to use set CPU.
honestly i cant see the point of it with any kernel. dosnt seem to do anything.

koreancanuck said:
I believe SuckerPunch is set to 1Ghz as default unless you change the setting with Voltage Control (or SetCPU). Mind you that 1.4Ghz is not run well on a lot of devices and may cause freezing. And I'm glad some people take up reading before asking questions
Click to expand...
Click to collapse
yeah im using voltage control- minus 125 on all and the phone seems to work well.
i just find it weird that the kernel peaks at 1ghz, where as another peaks at 1.2ghz (both without use of setCPU, and WITH use of Voltage control)
when i was using setCPU and putting it on performance, i could see it was running at 1.4, pretty much at ALL TIMES. MOST things ont he phone worked well, ultra fast. the problems i noticed is that neocore would freeze (which i understand to be a sign of instability) and speedtest would either give me REALY slow speeds, or force close every time. were as set on conservative it would work perfectly and neocore wouldnt freeze.

oFUNGUSo said:
yeah im using voltage control- minus 125 on all and the phone seems to work well.
i just find it weird that the kernel peaks at 1ghz, where as another peaks at 1.2ghz (both without use of setCPU, and WITH use of Voltage control)
when i was using setCPU and putting it on performance, i could see it was running at 1.4, pretty much at ALL TIMES. MOST things ont he phone worked well, ultra fast. the problems i noticed is that neocore would freeze (which i understand to be a sign of instability) and speedtest would either give me REALY slow speeds, or force close every time. were as set on conservative it would work perfectly and neocore wouldnt freeze.
Click to expand...
Click to collapse
I guarantee you you cannot run -125 at 1.4GHz, unless you have some kind of wonder-phone.
In Voltage Control, you're set to 1.4GHz, correct?
If you are, have you made sure to enable the 1.4GHz state in Voltage Control via the bottom menu as well? If you don't, even though you're set at 1.4GHz it will not run at that.

Auridran said:
I guarantee you you cannot run -125 at 1.4GHz, unless you have some kind of wonder-phone.
In Voltage Control, you're set to 1.4GHz, correct?
If you are, have you made sure to enable the 1.4GHz state in Voltage Control via the bottom menu as well? If you don't, even though you're set at 1.4GHz it will not run at that.
Click to expand...
Click to collapse
my bad, im running -125 on i think its the gb 1.2ghx kernel. thats working fine.
im going to reflash #50 and try what you said.....though im pretty sure i already had it set. i know i was setting the mv from 100 up to 1400

ok i flahsed back to #50, and went into voltage control. it DID cap my freq at 1000, i changed it and set 100 through 1400 to -75mv.
i ran stress test for about 30 seconds and exited, and my CPU widget shows 99% usegage at 1ghz
hmm
i flashed back to gb reorient 1.2ghz and during boot up as soon as the CPU widget loaded it shows 1.2ghz. ran stress test again and exited in the middle of it, widget showed 99% usage at 1.2ghz.
i realyl dont know what im missing here, but it does seem as thought the suckerpunch #50 is not running above 1ghz for me.
comparing all forms of benchmark type tests between the two kernels, everything EXPCEPT necore is scoreing better on the 1.2 kernel. neocore onthe 1.3 kernel is giving me 55.4 fps, whereas on the 1.4 kernel its giving me 65 and some change fps. i know benchmark scores arent that meaningfull in some cases, and on the #50 thread it even states that some may be lower on that kernel.......but i swear ive done something wrong because i dont see how it can be running at 1.4

oFUNGUSo said:
ok i flahsed back to #50, and went into voltage control. it DID cap my freq at 1000, i changed it and set 100 through 1400 to -75mv.
i ran stress test for about 30 seconds and exited, and my CPU widget shows 99% usegage at 1ghz
hmm
i flashed back to gb reorient 1.2ghz and during boot up as soon as the CPU widget loaded it shows 1.2ghz. ran stress test again and exited in the middle of it, widget showed 99% usage at 1.2ghz.
i realyl dont know what im missing here, but it does seem as thought the suckerpunch #50 is not running above 1ghz for me.
comparing all forms of benchmark type tests between the two kernels, everything EXPCEPT necore is scoreing better on the 1.2 kernel. neocore onthe 1.3 kernel is giving me 55.4 fps, whereas on the 1.4 kernel its giving me 65 and some change fps. i know benchmark scores arent that meaningfull in some cases, and on the #50 thread it even states that some may be lower on that kernel.......but i swear ive done something wrong because i dont see how it can be running at 1.4
Click to expand...
Click to collapse
Like I said in my previous post, are you actually enabling the frequencies or just selecting 1.4GHz as the max in Voltage Control?
You have to enable 1.4GHz in the "states" menu of Voltage Control for it to work, as well as set 1.4GHz as the max in Voltage Control. SuckerPunch does not overclock by default because a lot of phones do not play nicely with 1.4GHz.

Auridran said:
Like I said in my previous post, are you actually enabling the frequencies or just selecting 1.4GHz as the max in Voltage Control?
You have to enable 1.4GHz in the "states" menu of Voltage Control for it to work, as well as set 1.4GHz as the max in Voltage Control. SuckerPunch does not overclock by default because a lot of phones do not play nicely with 1.4GHz.
Click to expand...
Click to collapse
ha. this had me confused......there was no "states" menu. that got me pokeing around and then i realized i didnt have the newest version of voltage control(had 2.0 instead of 3.0). i do NOW. and i see the option to select the states. so, i selected 7 states up to 1400. and selected the max frequency of 1400. set a voltage for all, and applied.
still the same result. lol. its not running over 1ghz according to cpu stats. it SAYS it frequency range is from 100 to 1400. but it aint going over 1000.
*sigh* there has to be something else im missing

For suckerpunch's new builds, it's set to startup at 1ghz. After like 15mins. you can run some tests and it should be at max clock.

YESSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ITS WORKING! and dayum i see and improvement in stats! benchmarks look fantasitc, neocore isnt freezeing, phone isnt freezing on lockscreen.....will have to run stress test for a while to see for sure but it appears stable!
1400 -50
1300 -50
1200 -75
1120 -75
1000-75
800- 100
600-100
400-100
i really cant figure out the right way to do that, but it seems to be working so far
for one, i needed the newest version of voltage control.....for two, im thinking that i was supposed to wipe the davik cache before install, because it did a different song and dance when i did that. for three.....for whatever reson the 1000hz version didnt seem to want to work for me....and finally....waiting for a while after the phone booted up i did see the CPU start to jump up to 1.4.
thanks guys!

[Q] Phone not sleeping

Hey all, recently rooted my Hero to CM7 RC4 and I've noticed that it doesn't actually sleep, even when the screen is off. If I turn the screen off (to "sleep" it) for a minute, the up-time (in Status) also goes up by a minute. My battery life is also very poor and is likely a result of the phone never spooling down. Poking around the web, some people thought this was from the default SMS app, but this happened before I had ever sent a text (only received one.) I even installed handcent and used it for a bit, but the phone still doesn't sleep properly. Any ideas?

Have you gone into Spare Parts and checked Partial Wake?

stayclean said:
Have you gone into Spare Parts and checked Partial Wake?
Click to expand...
Click to collapse
I did, but it said the only appreciable lock was 3m 25s for Android System (all time.) Dialer was 4s all time. There are no stats for 'time since last boot' or 'time since last unplugged'; I recently rebooted and have the phone currently plugged in.

Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.

gaan kak said:
Hey all, recently rooted my Hero to CM7 RC4 and I've noticed that it doesn't actually sleep, even when the screen is off. If I turn the screen off (to "sleep" it) for a minute, the up-time (in Status) also goes up by a minute. My battery life is also very poor and is likely a result of the phone never spooling down. Poking around the web, some people thought this was from the default SMS app, but this happened before I had ever sent a text (only received one.) I even installed handcent and used it for a bit, but the phone still doesn't sleep properly. Any ideas?
Click to expand...
Click to collapse
You do have the End button Behaviour to sleep right?
its in sparepatrss?

stayclean said:
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
Click to expand...
Click to collapse
Right now I have wi-fi off, with generally average phone service on 3G. Sometimes it dips down to 1 bar or reaches 4, but is usually 2-3.
I have the governor set to 'ondemand', with a min of ~176 and a max of ~714. The brightness is set to auto. I don't know if I have much stuff auto-syncing, is there a way to check if I do? I don't have very many apps installed - I just rooted this afternoon, and this is my first android phone so I'm trying to take it slow.

davidevan said:
You do have the End button Behaviour to sleep right?
its in sparepatrss?
Click to expand...
Click to collapse
Pretty sure in Android, the end button defaults to sleep anyway, so I don't think that really accomplishes much. Maybe try turning off 3G when not using the phone actively? That will drain the battery a bit.

stayclean said:
Do you use wi-fi, or 3G? Bad or good phone service? Stuff auto-syncing on a regular basis? By the way, pretty sure up-time just displays how long the device has been on, nothing to do with sleep time or anything.
Click to expand...
Click to collapse
Yeah, you're right...uptime has nothing to do with sleeping.
To the OP...reboot the phone then let the phone run for about 1.5 - 2 hours or so without using it. Then go to Menu - Settings - About phone - Battery use. Then tap the graph at the top where it shows your time and compare your Awake time bar to your screen on time bar. They should be similar, with a bit more in the awake time depending on wat is set to sync.

To be honest, there is no fix to be honest. I've had this problem on many occasions and it fixes itself automatically whenever it wants to.
Sent from my HERO200 using Tapatalk

What radio are you using??? What kernel are you using??? Also try unckecking auto brightness. Also I think I read the ondemad governor has no sleep frequency,so if your clocked at 748 then your still at 748 when you hit the end button to sleep. Also there's no need to have the end button set to sleep in spare parts the rom should sleep on its on. lm not sure but I don't think the phone will sleep being on that governor. Try smartass or conservative and see if it sleeps then. Also make sure you have compatibility unchecked in spare parts. Also in settings under accounts&sync uncheck mobile data. That will need to be rechecked again to use your data services. Having it on all the time drains big time. Hope some of this helps. If not just post here or pm me and if I can help I will good luck
Yea it's Me Again With the
Modified Hero

laie1472 said:
What radio are you using??? What kernel are you using??? Also try unckecking auto brightness. Also I think I read the ondemad governor has no sleep frequency,so if your clocked at 748 then your still at 748 when you hit the end button to sleep. Also there's no need to have the end button set to sleep in spare parts the rom should sleep on its on. lm not sure but I don't think the phone will sleep being on that governor. Try smartass or conservative and see if it sleeps then. Also make sure you have compatibility unchecked in spare parts. Also in settings under accounts&sync uncheck mobile data. That will need to be rechecked again to use your data services. Having it on all the time drains big time. Hope some of this helps. If not just post here or pm me and if I can help I will good luck
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I am merely speaking from experience with no programming or dev experience, but I think ondemand actually does sleep. I use it at 176/729 and my awake and screen on is always similar. See the screenie below and look at the broken blue line below the battery up time. If it wasn't sleeping that line would be solid. Again, this is just my personal experience using ondemand.
{
"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"
}

make it sleep=
just give it some nice warm hot cocoa with a dab of whisky, works like a charm

ranger61878 said:
I am merely speaking from experience with no programming or dev experience, but I think ondemand actually does sleep. I use it at 176/729 and my awake and screen on is always similar. See the screenie below and look at the broken blue line below the battery up time. If it wasn't sleeping that line would be solid. Again, this is just my personal experience using ondemand.
Click to expand...
Click to collapse
I mean you could be right, I'm no dev by far myself but
I'm using jm's kernel 806. Its based off of the same kernel as the aosp gb builds. If you check his kernel thread I asked this question and was given a different answer. Maybe I misunderstood him or didn't ask the question correctly. I'll send him a pm and see if he's in the mood to share some knowledge. I read that link you posted on aosp's thread, very helpful in understanding the kernels operations a bit better. But it didn't mention what those selected governors default to while sleeping. I mean how can I really know what frequency the kernel is currently at while its sleeping??? The min/max can be set with the default oc app. But not the off screen settings. Unless I'm missing something?? And that could be the case??
Yea it's Me Again With the
Modified Hero

I too am noticing lots of awake time on my battery graph with CM7 RC4. I rebooted about an hour ago, and haven't touched my phone until taking these screenshots. (Sorry for hosting them offsite, the network here blocks the xda uploader.)
http://img828.imageshack.us/slideshow/webplayer.php?id=sparepartspartialwakesil.png
One thing I found very interesting is that even though my phone shows nearly 50 minutes of 'awake' time, my battery still reads 100% even though it's been unplugged the entire time.
sleepy

laie1472 said:
I mean you could be right, I'm no dev by far myself but
I'm using jm's kernel 806. Its based off of the same kernel as the aosp gb builds. If you check his kernel thread I asked this question and was given a different answer. Maybe I misunderstood him or didn't ask the question correctly. I'll send him a pm and see if he's in the mood to share some knowledge. I read that link you posted on aosp's thread, very helpful in understanding the kernels operations a bit better. But it didn't mention what those selected governors default to while sleeping. I mean how can I really know what frequency the kernel is currently at while its sleeping??? The min/max can be set with the default oc app. But not the off screen settings. Unless I'm missing something?? And that could be the case??
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I haven't a clue...maybe JM can shed some light for us

the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.

il Duce said:
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
Click to expand...
Click to collapse
I have always used 176/729 ondemand and had no issues with music and get great battery life (and my phone sleeps ).

il Duce said:
the sleep would follow the governor design. Smartass caps at 352 and scales down to your min setting based on your input, interactive and ondemand scale differently... ondemand would scale down based on cpu load (app use) to your min, and interactive (input based) would scale down based on your input to your min. IMHO interactive and ondemand are the best. I use ondemand most of the time because I can set the min lower than interactive and still listen to music with the screen off, no choppiness. I do sometimes switch to 352 min interactive or 264 ondemand when I *think* my phone is being slow, lol.
Click to expand...
Click to collapse
But is there any way to accurately check or confirm the actual frequency??? Or follow the governor design???
Yea it's Me Again With the
Modified Hero

laie1472 said:
But is there any way to accurately check or confirm the actual frequency??? Or follow the governor design???
Yea it's Me Again With the
Modified Hero
Click to expand...
Click to collapse
I don't know that I understand you... The whole point is that they scale based on conditions, so the actual freq would be changing constantly (but only to your min setting). The smartass gov is the only one with screen off/on specific freq - it caps to 352 screen off, and min is 528 screen on... I suppose there's a way you could monitor it using adb, maybe ddms, but it would be changing based on your current load or input, so you wouldn't really get much from it. Does that help?

il Duce said:
I don't know that I understand you... The whole point is that they scale based on conditions, so the actual freq would be changing constantly (but only to your min setting). The smartass gov is the only one with screen off/on specific freq - it caps to 352 screen off, and min is 528 screen on... I suppose there's a way you could monitor it using adb, maybe ddms, but it would be changing based on your current load or input, so you wouldn't really get much from it. Does that help?
Click to expand...
Click to collapse
Here's what I'm getting at. If the frequency constantly changes due to the users demand or cpu load and maxes out at the selected frequency but doesn't go below the selected frequency either. Then lets say its in the middle of scaling up or down and the user hits the end button, then what frequency would the cpu be at??? Being that it's no way of telling if it hit the min or the max user defined choice. So if the user has a min of 352 and a max of 768 and this were to happen. Couldn't the kernel then be put to sleep at a frequency of 768 ??? After all its still in line with the user defined settings. With apps like over clock widget and set/cpu you could select the off screen clock settings but being as those apps conflict with the native app how can the user be sure of what the off screen frequency is set to if this were the case???
Yea it's Me Again With the
Modified Hero

OC and UV to perfection safely and easy guide !!!

READ EVERYTHING BEFORE ATTEMPTING ALSO DO SO AT YOUR OWN RISK.
Required. you must have an oc and voltage support kernel. jfbs stock roms have both oc and voltage. cars1189 stock rom does not but he provides link to kernels that do. Dont use exuv or uv kernels while doing this. well you can but if your new to this it is recommended to use regular oc kernel without uv/exuv. Also ram size does not matter.
What else do you need:
an app that allows you to change clock speed and voltages. if you dont already have one get performance control here (i use this thanks to jfbs for finding it).
*NOTE* never ever leave phone unintended when doing this until you find your chips sweet spot. YOU HAVE BEEN WARNED. otherwise if you listen and follow my advice you wont cause any major harm to your phone or any harm to your phone. Also do NOT have the settings apply at boot until you find all your settings. keep a pen or pencil and paper ready so you can remember workings settings.
1. remove case (if you have one on your phone) and battery cover. (this is just a safety precaution should your power button not work to pull that battery.
2. open up your overclocking app. (in my case performance control). set min and max frequency/speed to 245mhz
3. go to voltage settings and change the current voltage for 245760khz (really 245mhz) which is stock 900mV to 875mV (decrease by 0.25). close app out swipe around home screen and apps draw. open and close contacts list and see if phone freezes. we are not worried about phone running slow at this point until you reach 1ghz+ point of this. IF phone freezes/locks up hold power button to reboot phone or just pull battery and put it back in (personally i just use power button). if phone doesnt not freeze lower voltage again by 0.025 which should be 850mV. continue this process until phone DOES freeze so make sure you you wrote down last working voltage and as soon as phone freezes reboot or pull battery.
4. Once you found the lowest working voltage for 245mhz up the min and max frequency (speed) to 368mhz (368640khz)
5. Do the same thing as step 3 which is decrease the voltage by 0.025mV for the frequency for 365mhz. and repeat for each frequency up to 1ghz. Once you get to doing 1ghz voltage and above. The testing phone phase will be different but still flow the decrease by 0.025mV. for testing use any 3d game not candy crush type. and let it run for at least 10mins actually playing with phone plugged into charger. when you reach the spot where the phone freezes unplug both charger and force reboot/pull battery.
6. Once you find all of your working voltages for each frequency then you can set min back to 245mhz and your max to which ever you was able to hit. then set all of your volt settings in and save it for set on boot.
Note. 1.2ghz-1.4ghz seems to be a very good and safe battery to performance ratio. even more so if you followed my directions properly.
EDIT:
My settings for comparison.
Frequency Range: min.256mhz max 1401mhz(1.4Ghz)
Voltage scale:
122880KHZ - 700mV
245760KHZ - 700mV
368640KHZ - 700mV
768000KHZ - 925mV
806400KHZ - 950mV
902400KHZ - 975mV
1017600KHZ - 1000mV
1113600KHZ - 1050mV
1209600KHZ - 1100mV
1305600KHZ - 1150mV
1401600KHZ - 1200mV

pretty awesome you guys are still squeezing the juice out of the exhibit. XD

teerout said:
pretty awesome you guys are still squeezing the juice out of the exhibit. XD
Click to expand...
Click to collapse
i just got this phone only a year ago... also the guide should work for any phone that has oc and voltage control support. but thanks

my new phone, motorola droid, is not as developer friendly as the samsung. i should have done more research before getting it. motorola and verizon have it pretty locked down, no flashing and awesomeness. getting root privileges was a 15 step process.....oh for the days of flashing with the exhibit...i still have a red case and a green flowery case if anyone wants them.

teerout said:
my new phone, motorola droid, is not as developer friendly as the samsung. i should have done more research before getting it. motorola and verizon have it pretty locked down, no flashing and awesomeness. getting root privileges was a 15 step process.....oh for the days of flashing with the exhibit...i still have a red case and a green flowery case if anyone wants them.
Click to expand...
Click to collapse
any electronic can be overclocked and under/over volt. Over voltage is fine if electronic requires a outlet to run e.g pc. game consoles. while undervolt is best for battery operated devices as you would want to have long operation time between charging xD.
Updated OP with my personal settings for this phone.

Thanks for the guide, Will be giving this a try this weekend... Well this and possibly flashing that new Mahdi Rom for the exhibit

Thanks!
TripFX said:
READ EVERYTHING BEFORE ATTEMPTING ALSO DO SO AT YOUR OWN RISK.
Required. you must have an oc and voltage support kernel. jfbs stock roms have both oc and voltage. cars1189 stock rom does not but he provides link to kernels that do. Dont use exuv or uv kernels while doing this. well you can but if your new to this it is recommended to use regular oc kernel without uv/exuv. Also ram size does not matter.
What else do you need:
an app that allows you to change clock speed and voltages. if you dont already have one get performance control here (i use this thanks to jfbs for finding it).
*NOTE* never ever leave phone unintended when doing this until you find your chips sweet spot. YOU HAVE BEEN WARNED. otherwise if you listen and follow my advice you wont cause any major harm to your phone or any harm to your phone. Also do NOT have the settings apply at boot until you find all your settings. keep a pen or pencil and paper ready so you can remember workings settings.
1. remove case (if you have one on your phone) and battery cover. (this is just a safety precaution should your power button not work to pull that battery.
2. open up your overclocking app. (in my case performance control). set min and max frequency/speed to 245mhz
3. go to voltage settings and change the current voltage for 245760khz (really 245mhz) which is stock 900mV to 875mV (decrease by 0.25). close app out swipe around home screen and apps draw. open and close contacts list and see if phone freezes. we are not worried about phone running slow at this point until you reach 1ghz+ point of this. IF phone freezes/locks up hold power button to reboot phone or just pull battery and put it back in (personally i just use power button). if phone doesnt not freeze lower voltage again by 0.025 which should be 850mV. continue this process until phone DOES freeze so make sure you you wrote down last working voltage and as soon as phone freezes reboot or pull battery.
4. Once you found the lowest working voltage for 245mhz up the min and max frequency (speed) to 368mhz (368640khz)
5. Do the same thing as step 3 which is decrease the voltage by 0.025mV for the frequency for 365mhz. and repeat for each frequency up to 1ghz. Once you get to doing 1ghz voltage and above. The testing phone phase will be different but still flow the decrease by 0.025mV. for testing use any 3d game not candy crush type. and let it run for at least 10mins actually playing with phone plugged into charger. when you reach the spot where the phone freezes unplug both charger and force reboot/pull battery.
6. Once you find all of your working voltages for each frequency then you can set min back to 245mhz and your max to which ever you was able to hit. then set all of your volt settings in and save it for set on boot.
Note. 1.2ghz-1.4ghz seems to be a very good and safe battery to performance ratio. even more so if you followed my directions properly.
EDIT:
My settings for comparison.
Frequency Range: min.256mhz max 1401mhz(1.4Ghz)
Voltage scale:
122880KHZ - 700mV
245760KHZ - 700mV
368640KHZ - 700mV
768000KHZ - 925mV
806400KHZ - 950mV
902400KHZ - 975mV
1017600KHZ - 1000mV
1113600KHZ - 1050mV
1209600KHZ - 1100mV
1305600KHZ - 1150mV
1401600KHZ - 1200mV
Click to expand...
Click to collapse
Thanks a lot man! I still have this phone, and i am trying to squeeze out as much juice as possible. Going to be switching to the Oneplus one soon, or the nexus 5!

help
Hello i have an exhibit ii 4g running mahdi 4.4.4 kitkat can i just download the performance app and follow this instrccions or do i need to flash a kernel to overlock my phone?

Andresakapaco04 said:
Hello i have an exhibit ii 4g running mahdi 4.4.4 kitkat can i just download the performance app and follow this instrccions or do i need to flash a kernel to overlock my phone?
Click to expand...
Click to collapse
all of jfbs roms are overclockable by defualt so just download performance app and follow instructions. be save and watch temps if your overclocking keep it below 35c is possible or if battery gets really warm.

TripFX said:
all of jfbs roms are overclockable by defualt so just download performance app and follow instructions. be save and watch temps if your overclocking keep it below 35c is possible or if battery gets really warm.
Click to expand...
Click to collapse
Thanks for this response one more question what are the benefits of overlocking my phonr aside from more batery lifee??? ... i wana give this a try so i can keep using my exhibit

Thanks!
This will be helpful when undervolting my parents' phones.

undervolting will give you the better battery life while keeping the same performance
overvolting will drain the battery faster
underclocking will drop performance and save more battery life then just undervolting
overclocking will give you better performance
When it comes to any mobile device it is recommended to undervolt and overclock as you want as much battery life as you can while getting a performance boost or just to undervolt to save battery only.
Desktops are made to handle heat and voltage a lot better thus most ppl will overvolt and overclock to get the fast possible performance as you are always connected to a main power source.

@TripFX, thank you for the comprehensive OC & UV guide. I've been tinkering with the voltage settings for about a week via Performance Control and I think I've found a good spot for both my Exhibit devices.
Here are my settings (using cars1189 Christopher K^Kernel uv vhm 9-9-2014 build)...
EDIT: Updated voltage & CPU settings.
CPU Frequency:
Max. 1401 Mhz
Min. 368 Mhz
Voltage Settings:
122880KHZ - 750 mV
245760KHZ - 750 mV
368640KHZ - 800 mV
768000KHZ - 925 mV
806400KHZ - 950 mV
902400KHZ - 975 mV
1024000KHZ - 1000 mV
1113600KHZ - 1025 mV
1209600KHZ - 1050 mV
1305600KHZ - 1075 mV
1401600KHZ - 1125 mV
Btw, 750 mv is the lowest 122880KHZ, 245769KHZ, and 368640KHZ can be set to using the kernel mentioned above. If anyone wants to go lower, you'll need to try a different kernel or one of jfbs ROMs. cars1189's uv kernels seems to do okay (every device is different though, so be careful) but I would strongly advise against using exuv (both my devices couldn't handle exuv).
Also, device temp. has decreased by a couple degrees overall, couldn't be happier!

jajb said:
Here are my settings (using cars1189 Christopher K^Kernel uv vhm 9-9-2014 build)...
EDIT: Updated voltage & CPU settings.
CPU Frequency:
Max. 1401 Mhz
Min. 368 Mhz
Voltage Settings:
122880KHZ - 750 mV
245760KHZ - 750 mV
368640KHZ - 800 mV
768000KHZ - 925 mV
806400KHZ - 950 mV
902400KHZ - 975 mV
1024000KHZ - 1000 mV
1113600KHZ - 1025 mV
1209600KHZ - 1050 mV
1305600KHZ - 1075 mV
1401600KHZ - 1125 mV
Click to expand...
Click to collapse
I almost copied your exact settings for my T679 and it's running nice (I've set min/max to 245 MHz/1209 MHz)
However I was curious as to what you've set for Governor and IO Scheduler; I've just left it on default: ondemand and row. Any other special settings or tweaks?
I ask because temp has definitely lowered, but battery life *I think* seems to drain a bit faster (though I do have a bunch of communication apps that probably sync throughout the day).

ZHXS said:
I almost copied your exact settings for my T679 and it's running nice (I've set min/max to 245 MHz/1209 MHz)
However I was curious as to what you've set for Governor and IO Scheduler; I've just left it on default: ondemand and row. Any other special settings or tweaks?
I ask because temp has definitely lowered, but battery life *I think* seems to drain a bit faster (though I do have a bunch of communication apps that probably sync throughout the day).
Click to expand...
Click to collapse
as far as more tweaks to boost performance. if all the apps you use is art compatible then i'd suggest switching to art. massive cpu difference between davlik and art. least from my own experience. as far as battery drain i would recommend using an app such as greenify. for gov's and sched. mine i left ondemand but sched put it on sio. however i recommend reading over this as it will help you get a much better idea of what would work best for you. everyone uses the their phone differently so it should technically vary from person to person.

Just a heads up to anyone undervolting. Be careful undervolting below 750mv. I noticed on my phone that the battery started overheating at 725mv and below. 750 and above was fine.

[Q&A] [KERNEL][D5803&D5833] AndroPlusKernel

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.