Database Develop

Overclocking App available in the market!

Hey everyone, there is an overclocking app in the market, anyone care to give it a try?
Edit: So I downloaded it lol. Here are some screenshots. BTW, is there anyway I can verify that the cpu freq is actually being adjusted?
*Just for fun I ran neocore to see if it would raise my FPS. lol.

just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz

Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
For example, atrackdog would take me at least 20-30 seconds to load my full app list (184 apps)
After installing overclock, it loaded in under 5 seconds.
i'll run other programs, and post my results.
I ran droidgear (game gear emulator) before and after, and I can honestly say it was faster (not a placebo affect).
-Before: droidgear would take over 4 minutes just to get to the menu screen
-After: i was actually able to load a game in under 1 and a half minutes, I even let it sit to run the demo, and it is the fastest ive ever seen an emulator run on this device (compared to NesEmu, and GB emu)
It would probably actually be playable if tweaks were made to the application codebase, and android Open GL stack.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.

well, i was too, and then i downloaded it and said "aahh, what the hell, if i break mine, ill just take my wifes haha..." probably not the best of plans but i installed it anyway
sooo i havnt burnt up my phone yet, but here is my issue with the app, does the app only work untill you reboot your phone?
because when i reboot my phone, it goes back to the default speed according to the app
also, my phone tends to hang up (stuck on the apps screen, no buttons work, screen wont rotate, power button wont shut screen off) when using the 528MHz
so far, i havnt found a reason to pay a dollar for it, but ill keep testing
[UPDATE]
resolution for all below tests is 320 x 480
i tried neocore like posted above, using the mid level setting, and i actually did raise my fps from
DEFAULT CPU (248 MHz): 20.5 (with sound off)
384 MHz: 25.0! (with sound off)
DEFAULT CPU (248 MHz): 14.5 (with sound on)
384 MHz: 20.8 (with sound on)
still havnt gotten the fast speed to work yet, but im still trying to figure that out, on another note, sweeter home does seem to load a little faster
[UPDATE]
Incase you didnt see my sig, im not running on a ADP1 phone, so that might by why the fastest setting doesnt work for me, but so far 384MHz is making a noticeable difference with NEOCORE and SWEETER HOME
andonnguyen said:
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
Click to expand...
Click to collapse
i use snap photo, which used to take FOREVER to load up on my g1 using the camera button, its significantly faster using the 384MHz setting, good observation
Ok, so so far here is a list of things ive noticed (using 384MHz vs 248MHz):
-FPS in NEOCORE increased on adverage 5 to 6 fps
-Sweeter Home doesnt lag NEARLY as much as it used to (ALOT less force closes)
-Snap Photo doesnt take a month to load using the camera button
-G1 Wakes up properly which was a issue my g1 (and others on this forum) had
-Even though the app says it will "kill" the battery, using 384MHz during normal use of the phone isnt "killing" my battery, however, doom (while runs better (even with sound on)) seems to be dropping my battery level faster, but the game is running faster, which is the trade off id expect when running these apps together

At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.

speoples20 said:
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
Click to expand...
Click to collapse
all of our battery life sucks unless you have the extended battery, im not getting THAT big of a battery drain according to the system monitor app, and it DOES make a difference on g1's that have lag issues (running tons of apps like i do)
in other threads, people have complained about the g1 not waking up quickly sometimes, ive yet to have that issue since ive clocked mine up to the 384MHz setting

@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
The program installs a script on your sd card called ocx_tmp.sh and adjusts it that way, it'll write to /system as -rw (from what I've discussed with someone) would probably cause instability.
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Try it before and after setting the cpu freq in overclock and you'll see what I mean =)

I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?

Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
andonnguyen said:
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
Click to expand...
Click to collapse
im not as familiar with clocking/overclocking so i wasnt sure if i was clocking it to 384, overclocking it to 384, or what, so what would be the proper thing to put in my sig? lol because according to my first quote, true overclocking wouldnt be untill i went beyond 528, so from the view of my first quote, im not OVERclocking, im clocking, wheras your saying im overclocked

andonnguyen said:
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Click to expand...
Click to collapse
so is it infact the program thats changing the cpu freq or is it the phone? if its the program, is this to avoid overworking the cpu without the demand?

andonnguyen said:
.
The program will reset the cpu freq back down to 384mHz after the phone sleeps.
Click to expand...
Click to collapse
by sleep do you mean turning the screen off using the power button? because i saw no change in my cpu freq when doing so using your commands

ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
dont know, but i found this over at the android community:
Technical Features
Supports WCDMA/HSUPA and EGPRS networks
Multimedia Broadcasting Multicast Service (MBMS)
Integrated ARM11™ applications processor and ARM9™ modem
QDSP4000™ and QDSP5000™ high-performance digital signal processors (DSP)
528 MHz ARM11 Jazelle™ Java® hardware acceleration
Support for BREW® and Java applications
Qcamera™: Up to 6.0 megapixel digital images
Qtv™: Playback up to 30 fps VGA
Qcamcorder™: Record up to 24 fps QVGA
Up to 4 million triangles per second, and 133 million depth-tested, textured 3D pixels per second fill rate
gpsOne® position-location assisted-GPS (A-GPS) solution
Support for third-party operating systems
Digital audio support for MP3, aacPlus™ and Enhanced aacPlus
Integrated Mobile Digital Display Interface (MDDI), Bluetooth® 1.2 baseband processor and Wi-Fi® support
maybe that info will help? if not sorry

I remember reading somewhere by someone that it runs at 384 by default, and I think the post above confirms that...

ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
gui fluidity is definitely increased, and sluggishness between app switches and when the translucent app drawer opens up is gone. i like it, but to the average person there probably is no need to do it.
keep in mind this is also not overclocking the cpu, it's clocking it to its default spec. as it is an embedded arm, it is designed to run hot, so i guarantee you are in no danger of hurting your phone.
also, do not listen to people that claim there could be no gain from overclocking, just because the bus speed is slower than the cpu speed does NOT mean there will be no improvement in system performance. if that were the case, there'd be no use for 4ghz desktop processors.
cache still runs full speed, and common execution paths stay in cache meaning no prefetch from system memory, meaning BIG improvement in many cases. (that's why cache exists.)

damnoregonian said:
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
gui fluidity and responsiveness is greatly improved. sluggishness if app switching and the translucent app drawer are completely gone.
for many i imagine this means there isn't really any reason to clock the cpu up to its stock speed, but to each their own.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
Click to expand...
Click to collapse
care to write up a how-to for getting the 582 consistantly and changing the idle loop?

Holy crap. Used this @528MHz with Haykuro's version 4.5 apps to sd ROM and the osk works SO MUCH BETTER!!!! Also I got 25.6 fps on neocore... very smooth

wootroot said:
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Click to expand...
Click to collapse
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.

A modded version of JF's ROM would ROM.
I DO notice the sluggishness and it bugs the heck out of me. (I switched from a WING with a 200MHz CPU, and although it IS faster than the wing, it doesn't seem significantly faster and seems to much slower when I open up the camera...

damnoregonian said:
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
Click to expand...
Click to collapse
that involved eh?
thanks for this post though, now i understand more about the idle loop and why the cpu freq resets with each reboot
maybe someone can take this stuff further like he said, that kind of stuff would be worth the dollar, imo more than a dollar

well... i don't mind providing basic procedure and source, i just don't want to get dragged into level 1 support of the procedure.
i'll go ahead and package up some source, prebuilt boot images based on JF's RC33 (which is what i run) and a basic procedure.

[Q] dynamic overclocking

.
..

I use setcpu to do this.
Look into the governors, choose one.
Then choose the appropriate thresholds (in the advanced menu) for what you do.
It doesn't allow you to tweak per app, but tells the cpu governor at what %of cpu to move to the next cpu speed (up or down).
I set mine very low, as i care more about battery than performance. So my up threshold is like 95% or something.
But my down threshold is a lot more agressive.
But you do the opposite.
MuF123 said:
Hello,
my question is regarding dynamic overclocking. I've used the ones that raise the speed when under a load - but my question is -
Is there a way to return to stock clocks after certain time?
Explanation:
situation1: I want to check new single mail or open new single IM or check university's website for some news, I want the device to be FAST as possible, nevermind the battery.
situation2: I want to use maps/navigation/IM/games/web browsing for longer period of time (hours?) with the screen on. I don't need all the power when I play solitaire, text on IM or browse not-so-important news websites.
I think when I've seen the realtime clock displayed on my phone it jumped to max clock right after I've clicked almost anything on the screen. I want the speed-up, but after certain period of time to stop doing this in favor of the battery life-time.
Any ideas how to do this? Thanks!
Click to expand...
Click to collapse
Sent from my Milestone using Tapatalk

Yes, just throttle the cpu to give you more power when you are sluggish. That could work for you.
Me? I have my droid do 110 when screen is off (works quite well!), and then I FORCE the unit to 1000 when plugged in. Besides that i throttle the cpu based on battery power: more cpu power with more battery life. Makes my droid last longer.
I might want to add a throttle up when sluggish and not in my personal battery red zone and a throttle down when the cpu gets too hot period.
Any cpu frequencies that you all would suggest?

..

MuF123 said:
Thanks for the reply, but - think about this, I will start a 3D game, it will use 100% of the cpu so it would always stay at the highest possible frequency (+highest voltage). I don't want that.
Click to expand...
Click to collapse
I dont get it?
You dont want max speed in game? Why do you overclock?
If the game requires 100%, the it will (and should) clock up.
As soon as the game doesnt, it will clock down (depends on your threshold).
The only other i could see, is to change the max clock rate in setcpu before you play the game. This will ensure it doesnt clock higher than your choice, but requires a manual step.
But seriously, if your cpu is pegged at 100, why would you not want it to step up the higher speed?
Sent from my Milestone using Tapatalk

..

MuF123 said:
exactly - I don't want minimum battery in game, that's why I don't want to overclock.
actually from the nature of 3d rendering I think every game will run at 100%, but the situation when the game hits the frame limiter (not likely on milestone).
I want snappy performance while doing few quick tasks:
e.g.: new IM comes, I want to unlock, load the application, get to the IM, reply, lock. (40seconds)
or
taking phone from cradle - I want the phone to load homescreen fast, rotate the screen, open phone app, to look at last missed call and call back (20seconds).
Battery life won't be affected by 40 or 20seconds of ~1100mhz, okay.
And then I start a game for a prolonged time. It will run smoothly even on 550MHz, the additional frames I see are just waste of battery = I don't want that.
So now I have two options - either run at max speed and it will be always fast and it will drain my battery when I decide to play for an hour.
OR
I can use default speeds for longer battery life for everything and I will wait an hour to rotate the screen in browser or IM app.
Click to expand...
Click to collapse
You could compromise and find a max speed that you could undervolt to make it drain battery like stock. My 800mhz vsel is less than the default vsel @550. So the battery drain is less...
It requires some trial and error, but most "slight" overclocks (700,800; depends on the phone) can be configured to drain less than stock.
Of course, if you feel you need 1000 or 1100, this wont work as it requires increasing the vsel (or at least not decreasing it).
Sent from my Milestone using Tapatalk

[INFO][GUIDE] Overclocking information, governors, profiles, problems, solutions, FAQ

Updated As Of 30/06/2013
Code:
#include
*
* Your warranty is now void.
*By you using my Mods, Roms etc...
* I am not responsible for bricked devices, or dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Hello existing members, and new comers, this is a thread dedicated to people's temperatures and clock speeds on this phone. Doing this we can learn how the Desire C handles heat in certain circumstances, and if it is indeed the reason why people cannot overclock as high as others.
However I would like to state to anyone who tries any of these tips and tricks mentioned by both me and other members, we are NOT LIABLE for any damage you may cause to your device. I guessing most of you guys are aware of this, but I thought to make to clear to anyone who doesn't know these things.
To the existing fellow Desire C overclockers I have wrote some notes of which can improve the experience with your phone, they are as follows:
Use different frequencies instead of a solid one, for example:
In certain CPU management applications you can change how the CPU behaves when the phone is in a certain state, this meaning things such as; charging, low battery, sleep etc...
These adjustments are known in the android community as "profiles" there is currently one one CPU program of which I know about what can do these "profiles" and that's setCPU. (if you guys know any others pm me, or post in this thread and I will make a list of apps available)
When you use your phone for music especially files with a high bit rate (320kbps) when you lock the phone the music may stutter, or "lag" let's put it. Now I have found a way to greatly reduce this "lag" this is to go to where it states the lowest CPU frequency and turn it up from 122mhz to 2xxmhz. This fixes lag because when the clock speed is at such a low state, functions and background services such as music, sync etc... are preformed much slower, hence the "lag".
One of my main points is about the phones CPU "governor" this basically controls how android will handle your phones cores, and resources currently there are many available in the current kernels, however, as more kernels come there may be more "governors" available on our devices these include:
SmartassV2
Interactive
Lagfree
Conservative
Loinheart
Ondemand
Preformance
All of these governor's will make a slight or more noticeable change to the performance of your phone there will be some screenies of my setup below the main post.
The overclocking application I use is called SetCPU thus is available here on xda for free, but is also paid for on both the android market and the amazon market place. If you wish to get it from xda, for now search it because I will add the thread link to this post soon.
As mentioned before if you have issues regarding overclock your phone be sure to post and I and other will be glad to help out, remember no question is stupid.
The kind of information of which will be posted and discussed in this thread is:
Temperatures of devices cores.
Screenies of peoples "profiles"
Selected governors
Questions regarding overclocking
Solutions to problems for users having issues
The five posts after this one are as follows:
CPU profiles, examples and what they do.
Thermal throttling, what it is and also what concerns it.
Governor, recommended ones and more in-depth of what they do.
How to flash New kernels for new users.
Questions and answers (FAQ).
So let's fill this thread with useful information and questions regarding all this overclocking business
But please do not spam this thread with useless information because we do not want this locked, as I could be a resource, also if you guys want this post sticked please say so and I'll see if it can be done.

Overclocking profiles
Okay as mentioned before in the above post I will post some screenies of my current profiles, of which I prefer. However you can use my settings as a reference and create your own, if you do make a screenie of your setup and post it to give others more options, or more understanding of what these are, and what they are about.
A little more indepth about CPU profiles is that let's say if you wanted to conserve more battery during the night for example, you could create a profile saying what clock speeds to run at, at particular times this meaning from 12AM-8AM with a clock speed of 122mhz-386mhz this configuration will save more power than 122mhz-600mhz or 767mhz or even 806mhz in an overclockers case.
For example my clock speeds are:
122mhz-3xxmhz in sleep mode
806mhz-806mhz when charging
122mhz-4xxmhz from 2.00AM to 8.00AM
2xxmhz-806mhz when doing tasks in sleep mode such as titanium backup.
Update: It appears with some configurations, that if music is playing the lag may be present when waking the device.

Potential thermal throttling
Just like any other computer weather it is a desktop, laptop, phone or even a tablet, and no not the ones you eat lol
All have thermal limits, also known as thermal throttling which is the CPUs thermal limit, when this reached the system may become unstable,reboot,or turn off entirely depending on what the device is coded to do in these situations.
I have a theory of why some people's phones can overclock higher than others without issues, or really high core temperatures. I think it is down to the environmental variables which include:
Humidity, the more humid the environment is the harder it is to cool a device, due to a higher density of water being in the air unable to transfer heat effectively.
Heat, this is a big problem for computers what are overclocked, more speed means mote heat! Unlike a gaming computer, where there is a whacking heatsink to cool the CPU efficient enough to prevent overheating
However, for any android phones, tablets it is a different story, the cooling system inside these devices is known as static cooling, meaning there is mire heating being trapped inside the system and isn't being moved my fans etc...
Now I believe if the people having issues with overclocking should post their temperatures of their CPU to see if there is a difference between devices which can overclock far, and the ones that can't.
To get more information on temperatures I think anyone who is overclocked should post their temps both idle, and after playing some games etc...
For example, using the setCPU application widget on my home scene I can read my temps of my CPU on the fly, if you can't provide a screenshot of this for what ever reason then post you information like below:
IDLE: @122mhz-806mhz is around 18-22 degrees.
AFTER WORK (GAMES,APPS ETC...) @122mhz-806mhz is around 32-39 degrees
If people post these figures then we will know if there is much of a temperature difference between devices.
Let's get some boss results and figures to help figure out potential crashes,reboots etc... Some users have experienced.
Remember, that thermal throttling, slows down the CPU, so it doesn't cause damage to it

CPU governors what are they?
In the brief explanation in the first post a Cpu governor basically tells android how to access the hardware, in this case the CPU. Basically each governor has a set amount of variables of how long processes can use a thread on the CPU, or how the system handles simple requests, the governor controlles all of the things android puts through our hardware.
Intact a CPU governor is so low level it is actually inside the android linux kernel, meaning that the kernel compiler needs to code these into the kernel to make them available.
There are many governors available, of which can be used under certain circumstances for example:
Conservative, this governor will try to cut the amount of clock cycles the phone will process data with, hence the name conservative meaning it will save power where possible, but resulting in lower performance.
Preformance, this governor is used to squeeze every little bit of performance out of your system possible, great for gaming but not so great for battery life.
I will list other governor functions later on.
Currently the governor I recommend is based solely on use, I mostly use Lagfree which is both good battery life and gaming performance.
If you guys use any others governors post it with why you think it is the best config for you, including your temps, clock speeds etc...
Remember this thread is about gathering information about the thermal relation between phones what can overclock far, and ones that can't.
Recommended Governors and schedulers​

Flashing a Boot.img
Recently I have had messages from new users who are confused about installing this rom, Well i'm here to help! So I have written a short guide on how to flash the rom, kernel etc... In short simple steps:
Copy the newest nameless to your sd card
Install the rom as normal
When it says reboot after installation is finished, uncheck that box and go back into recovery
Then on the main recovery screen there will be a reboot into fastboot, click that. Note: have your computer plugged into your phone before this, because it will connect better.
Next on your computer find the nameless rom package open it and find a folder called, "Kernel_boot_img"
My advice is to try the 767mhz kernel first, see if your phone boots if it does try the 806mhz after, if it also boots you have a high over clocked phone
You will need to flash the boot.img as normal (fastboot flash boot boot.img), whatever kernel it is (767, or 806mhz) And don't forget the wipe the cache after installing the new kernel as this could cause problems to fix this use this command, "Fastboot wipe cache" then followed by "fastboot reboot" then your phone should reboot.
TO CLEAR ANY CONFUSION:
Don't flash both kernels at one time, it will not work like that try one at a time to see if it boot with success.
If it doesn't boot with one of the kernels, then try the other one most phone work with the 767mhz kernel, while others work with the 806mhz
If nothing else work message me and I will try to help, however your phone should work and boot with success with these step, be sure to follow them closely.
Good luck, I hope this helps any new comers having problems.

Y U NO Work? FAQ
Y U NO WORK! Is often said by people who are angry your phone isn't working with some kernels, I am going to list some of the most asked questions new users have sent me regarding this subject:
Q: My phone won't boot, instead it is stuck at the green and white "HTC" screen.
A: All I can say my friend is try the other kernels available on the nameless thread there are currently two of which are 768mhz and 806mhz if you have tried both you unfortunately have a phone what doesn't like extra heat.

Screenshots
Screenshots coming soon

Reminders about thread, Kernel history, Member temps etc...
If other users require extra help please post a question below, me and other members will be glad to help you out and get you on your way. However, remember that this thread needs to remain clean! No spam posts, and no flaming arguments!
This thread is a home to share the following things,as mentioned above, and try to resolve potential issues regarding overclocking these include:
Phone CPU temputures
What kernels work, which ones don't
The highest temputures you have, compared to other who cannot overclock
Screenshots of profile settings and temps
XDA Kernel history​XDA member reported temperatures and clock speeds​
Neoyoli
767 oc kernel - performance/deadline
IDLE: @767mhz-767mhz is around 27-31 degrees.
AFTER GAMING, ANTUTU: @767mhz-767mhz is around 35 degrees
nikhil16242​I use 722mhz max - 320mhz min lagfree-deadline
Temps:
Idle : 28-30 'C
Charging : 34-35 'C
Charging + Playing a heavy game like shadowgun : 40-41 'C​
einstein.frat
I leave it at 722max 320min it is 30'c 87'f I use smartass2 and sio
Whoamigriffiths
normal temps quite high 32-35 after antututututututuutututu 37.2 @806mhz, performance governor ​

Wow its War and Peace!
Awsome work , thankyou. I'll sort out my temps etc later tonight as I have to go out now . and I'll hit you up with some much deserved thanks . For some reason my counter says I've used 8 already and I've not used it yet

Thanks Richard . I'm trying my best to resolve issues other members are having. I'm soon going to make another thread to help out with issues on roms, cache errors etc... So look out for that one.
Hopefully this thread can be stickied, so all new and existing members can see it without creating new threads with the same questions, as it is a waste of space.

okay, here I go: me and my phone live in London, today the weather turned to nice lol.
767 oc kernel - performance/deadline
IDLE: @767mhz-767mhz is around 27-31 degrees.
AFTER GAMING, ANTUTU: @767mhz-767mhz is around 35 degrees
And, strangely since I'm using either V6 SuperCharger (it has a kernel panic tweak) or the performance/deadline combo, the phone did not reboot on 767, previously I had to downclock to 722 to make it stable, because it rebooted under heavy usage like gaming.
I will try different combos and report back if it stayed stable.
But I was wondering if the issue with the 806mhz kernel was due to heat, the phone would still boot up, isn't it?

Re: Overclocking information, governors, profiles, problems, solutions and FAQ
I leave it at 722max 320min it is 30'c 87'f I use smartass2 and sio.
What's good configuration anyone know?
I know old settings that are good are
Ondemand-noop
Ondemand-deadline
Lionheart-sio
Lagfree-sio
Smartass2-sio

Hmm that might not be strictly true, a CPU can get hot after first boot up very quickly just like any Computer, I have some other ideas why some peoples phones don't boot too, i'll post them in my thread and update it.

I use 722mhz max - 320mhz min lagfree-deadline .
None of the 800mhz OC kernel works for me.Doesnt even get to boot animation
Temps:
Idle : 28-30 'C
Charging : 34-35 'C
Charging + Playing a heavy game like shadowgun : 40-41 'C
I really dont think its due to high temperature (but one can never be sure about these things) as even at 41 'C the phone doesnt actually reboot.It only reboots on setting a higher OC like 767mhz

Interesting, nikhil16242 I will try to get shadow gun and use the same clock speed as you and compare my temps to yours, see if there is a difference between them.
I have another idea what it could be, and i think it is related to what frequencies each phone supports maybe einstein.frat could try something slightly under 806mhz and see if it works. But i think it is how to frequencies are counted on the kernel, maybe if einstein.frat can change some of the values, to lower variables it may work I need to look this up any input about how kernels work would be helpful.

have any of you guys tried to flash the 806mhz kernel WITHOUT wiping the cache through fastboot?

Re: Overclocking information, governors, profiles, problems, solutions and FAQ
Yes .
Tried all possible combinations like flashing the rom cleanly and flashing kernel,flashing kernel with and w/o wiping cache .
Sent from my HTC Desire C using xda app-developers app

Did the first overclock kernel work for you, by zeroprobe?

Re: Overclocking information, governors, profiles, problems, solutions and FAQ
Yeah, oc kernel by zerophobe did boot for me, but I think it used "fake" overclocking since benchmark scores where more or less the same as stock kernel .
Sent from my HTC Desire C using xda app-developers app

Well i think figures should be changed inside the kernel, I don't know what maybe some of us can experiment with unstable kernels. It is two things heat, or how the kernel is coded, which ever way we need to find out, hopefully overtime we will.

Overclock CM11

Hi there,
really sorry if this has already been around, but i've been searching this forum up and down and didn't find a thing.
Anyways, i was wondering how i could enable overclocking under cm11 nightly? Could anyone point me towards a solution? Thanks

Well ...
http://forum.xda-developers.com/droid-4/development/5-0-custom-oc-kernel-t3041512
It should work (in the past it works)
Install it on your Cyanogenmod Rom
Fervi

ferviverus said:
Well ...
http://forum.xda-developers.com/droid-4/development/5-0-custom-oc-kernel-t3041512
It should work (in the past it works)
Install it on your Cyanogenmod Rom
Fervi
Click to expand...
Click to collapse
There's a guy who said that that kernel doesnt work on cm11...it work's for you in the past?

For CM11 and other AOSP 4.4 ROMS, the most fully-featured and overclockable kernel is JBX. You can use the one intended for the RAZR.
Joojoobee's is good, and certainly the best for Lollipop, but due to its extra voltage management stuff the JBX kernel has a higher overclock ceiling.
Use the newest kernel from here.
Boot into Safestrap, make a backup in case something goes horribly wrong, then flash the package to start up the installer. In the installer, don't install any of the tweaks, at least a couple of them cause instability for our phone, and don't bother with the init.d stuff. Just install the kernel itself and Trickster Mod. Trickster, FYI, is probably the best app for managing JBX, but other apps can as well.
Done. Reboot phone, hopefully it won't bootloop, once back up increase speed until it starts freezing when you try to use it, bump voltage 10-20mv, find ceiling again. I think the JBX thread has better/more detailed instructions, but that's about the gist of it.
Maximum advised voltage is 1490mv iirc, don't try to even approach that unless you want to cook eggs on the back of your phone.

Thanks a bunch!
After messing around with both solutions, Jojobee's solution gave me a bootloop but the other one worked.
However i can't seem to get past 1300mhz when overclocking, that seems to be the limit. I was aiming to try to reach 1400, any idea how i could go about that? I can't seem to find an option to set the max frequency higher than 1300.

Well i was playing a little with JBX kernel..these are my conclusions:
- Kernel install/works fine if you don't install 10% battery mode..otherwise you are goingo to have android crashes
- Kernel performance it's below than current cm11 m13 stock kernel...i believe is due to full scale freq that it has...cpu spend a lot time switching from one freq to another...if you overclocked you will have almost the same performance than NON-OC stock kernel..that's why stargo applied and later reverted full scale on stock months ago...meaby if JBX kernell would have support to boost driver (like cm12 OC kernel) it would be better...but it hasnt...
So my conclusions...dont waste time on JBX kernel...sorry my 4 my english
Enviado desde mi XT894 mediante Tapatalk

Milp said:
However i can't seem to get past 1300mhz when overclocking, that seems to be the limit. I was aiming to try to reach 1400, any idea how i could go about that? I can't seem to find an option to set the max frequency higher than 1300.
Click to expand...
Click to collapse
I don't think you can set the CPU higher than 1.3ghz, at least not in the way you're thinking.
In the case of the JBX kernel, you overclock the Main Processor Unit (MPU) speed. I don't remember what tab it's under in Trickster, but it should be the same one as the voltage settings. I couldn't even begin to guess where it'd be as far as other apps.
The default is 100mhz. This is multiplied by each frequency step; e.g. 1.3ghz is actually a 13x multiplier of the base 100mhz.
So to obtain 1.4ghz(ish), simply increase the MPU clock from 100mhz to 108mhz, since 108*13=1404.
If you're lucky, you'll be be able to do this without needing to touch the voltage, if not...read the FAQ in the JBX post, because I don't remember offhand exactly how to set voltages :v
Once you know how, I would think a 5-10mv bump would be all that'd be needed to stabilize most CPUs for 1.4ghz.
fyi, ignore if you already have stuff for these:
Antutu is a decent app for both testing stability and checking to make sure you're not hitting the heat throttle.
Cooltool isn't a bad thing to use either, if configured to show CPU speeds, since it'll show you if the CPU has been forcefully throttled back (if the CPU gets too hot, it'll forcefully change the maximum multiplier to 10x/11x to protect itself from baking; if it does, back your voltage off and be happy with whatever speed you've attained).

Thermal Settings

I have noticed the Xiaomi Mix has some persistent software thermal throttling after a short period of time.
I ran the same test on a OnePlus 3T and noticed this throttling issue is not present.
It's possible the temps to start throttling are too low on the Mix.
Is there any way to modify or increase these throttle limits?
I know this has been done before but I cannot load the Thermal conf file in /system/ etc / thermal-engine.conf
Can we replace the file with something else ?
The OnePlus forum members released several versions of the file with different throttling temps. Can we use these files or make our own.
https://forums.oneplus.net/threads/oneplus2-how-to-fix-thermal-throttling.417108/

Did you ever get any further with this? My phone idles at ~35C. I read a review that said throttling begins at ~40C so I get throttled when I do virtually anything.
I've only had this thing 2 days and the performance has been worse than my old Nexus 6 because the cores keep getting capped very low. I was copying some backed up files over WiFi from my PC. It was lots of small files so it was running for 20 mins or so. When I was trying to do other stuff in the meantime it started to get really sluggish. I used to do exactly the same thing on my N6 and I could never tell that file copying was running in the background. I checked Kernel Auditor and it was showing temps ~50C and the cores were all being capped around 5-600MHz.
I've tried the stock ROM (stable and beta) and EPIC, and Lineage/RR. It seems to be a bit worse on the latter two (Antutu won't go above 100k, but it's like 140k on the MIUI ones) for some reason, but it's an issue on all of them.

gavin19 said:
Did you ever get any further with this? My phone idles at ~35C. I read a review that said throttling begins at ~40C so I get throttled when I do virtually anything.
I've only had this thing 2 days and the performance has been worse than my old Nexus 6 because the cores keep getting capped very low. I was copying some backed up files over WiFi from my PC. It was lots of small files so it was running for 20 mins or so. When I was trying to do other stuff in the meantime it started to get really sluggish. I used to do exactly the same thing on my N6 and I could never tell that file copying was running in the background. I checked Kernel Auditor and it was showing temps ~50C and the cores were all being capped around 5-600MHz.
I've tried the stock ROM (stable and beta) and EPIC, and Lineage/RR. It seems to be a bit worse on the latter two (Antutu won't go above 100k, but it's like 140k on the MIUI ones) for some reason, but it's an issue on all of them.
Click to expand...
Click to collapse
I have absolutely gotten further here I have managed to get throttling completely disabled actually.
The highest temp the CPU got to was 42 degrees Celsius after running Dolphin for 2 hours straight.
There is no need for thermal throttling on this device at all, hardware does a good enough job clearing the heat.
To stop the thermal throttling you need root access.
Use ES File Explorer from the play store and enable root access
Navigate to root and look for Folder system/etc and find file called thermal*******.*** ( I don't remember what it's called )
Cut this file from this location and paste it into another directory. I moved it to the sdcard for easy access. This way you can move it back if you do not like the results.
I have not experienced any overheating with this, also the battery doesn't drain like crazy. Performance is greatly improved with speed matching the Snapdragon 835 in a few scenarios.
Oh yeah restart the phone after you move the file so it can register the changes. Clock the cores appropriately with Kernal Auditor to make sure it can run at full blast when it needs to. On demand is way faster than interactive.

Cheers. I actually read the links you posted and renamed the conf file. After a reboot it was flying. The problem isn't so much the throttling, it's that mine idles at ~35C already, so it was getting capped when I did virtually anything. If I run Antutu 2-3 times in a row and check the temps in Kernel Auditor it can be in the low 60s. Using other temp apps (CPUTemp) it only shows about 45C tops.
It definitely does feel pretty damn warm since I don't use a case. but I'd love to know what the 'real' temp was. I tend to believe the lower one since I got the 45C warning when using EPIC and that's exactly what the app said. it was.
My Antutu scores increased substantially too. I was sometimes dipping down to 80-90k but I regularly get ~140k now, even 160k once. I know not to go by those scores but when I could never even get above 100k it was a concern.

gavin19 said:
Cheers. I actually read the links you posted and renamed the conf file. After a reboot it was flying. The problem isn't so much the throttling, it's that mine idles at ~35C already, so it was getting capped when I did virtually anything. If I run Antutu 2-3 times in a row and check the temps in Kernel Auditor it can be in the low 60s. Using other temp apps (CPUTemp) it only shows about 45C tops.
It definitely does feel pretty damn warm since I don't use a case. but I'd love to know what the 'real' temp was. I tend to believe the lower one since I got the 45C warning when using EPIC and that's exactly what the app said. it was.
My Antutu scores increased substantially too. I was sometimes dipping down to 80-90k but I regularly get ~140k now, even 160k once. I know not to go by those scores but when I could never even get above 100k it was a concern.
Click to expand...
Click to collapse
Yeah I'm thinking Xiaomi severely limits the thermal threshold to improve battery performance.
It's kinda all they care about in Japan for some reason.
Makes for some great performance improvements without the thermal settings being active.
This setting change is almost necessary of you need some heavy work done.
Glad you were able to get this changed.

i remove thermal_8896_blabla.conf...
Honestly device become too hot for me.... backplate change during my game (Battle Bay), very different sensation... reinstall immediatly *.conf... Finally i have decent perf and cold phone and very good battery life... no more...
My opinion !

lesscro said:
i remove thermal_8896_blabla.conf...
Honestly device become too hot for me.... backplate change during my game (Battle Bay), very different sensation... reinstall immediatly *.conf... Finally i have decent perf and cold phone and very good battery life... no more...
My opinion !
Click to expand...
Click to collapse
I think our best solution would be a modified .conf file that increases the thermal threshold as opposed to completely removing it.
Until this solution is available then this is our only choice.

i agree... i think with a ROM kitchen mayve this fil can be readable... anyway @ this point, we can only hope somebody dectypt this file to support various cool modification available over XDA...
Edit /
it seems HTC make same stuff... here it is a guideline ot example...
https://forum.xda-developers.com/showthread.php?t=2455596

lesscro said:
i remove thermal_8896_blabla.conf...
Honestly device become too hot for me.... backplate change during my game (Battle Bay), very different sensation... reinstall immediatly *.conf... Finally i have decent perf and cold phone and very good battery life... no more...
My opinion !
Click to expand...
Click to collapse
I had the same issue. I was getting 165k+ in Antutu but the phone would get uncomfortably warm when doing multiple passes, or gaming for extended periods.
In the Thermal section of Kernel Auditor, I enabled the Core Control and Temperature Throttle options and the phone still gets warm, but only as warm as you'd expect. I still get ~155k in Antutu consistently and the performance in general is still very smooth. I have the CPU governor set to ondemand, and the GPU governor to simple_ondemand. All other KA settings are default.
One other thing I always do is to reduce the Window Animation, Transition Animation and Animator duration scales to .5x (1x by default). It just makes the phone feel snappier in general. Settings > Additional settings > Developer options (MIUI-based).
I'm using the latest EPIC ROM. Using RR/LOS I couldn't replicate the same high Antutu scores consistently for some reason. I quite like MIUI after years of using CM and CM-like ROMS anyway.

already reduce animation x0.5... MIUI use a lot of this animation with complex and (very long calcul) then reduce this number make device seems much faster... anyway, u right...
A custom kernel for miui base... based on Dragon XIA exist in MI5 thread... only need to play a bit to make universal... with all source we can make somthing, but no have time to play with all tutorial available on XDA or Youtube...
Only way to make device much smoother and battery friendly or Perf/Warm destructor...