Database Users

[Q] How to overclock my HTC HD2 with Android ?

Hi !
It's my first thread, i hope you can find the solutions to solve my problem.
In first time, i'm sorry to my bad english. So, my problem is:
I have a HTC HD2 and i know to install Android on that. My new challenge is to overclock my device, with SetCPU or other. I have already followed some tutorials to do a few profiles... I did it, the maximum value i selected is 998 MHZ. It's Ok i think, i cross "Set on boot" and "enbale" so when i use Quadrant Standard Edition, i check 1024 Mhz. But when i see the device of XDA's devs i can see like rafpigna's nand 3024 MHZ ! Here : http://forum.xda-developers.com/showthread.php?t=908528
My questions are:
1. How can i do it ?
2. Can i accelerate my N64's roms (with N64oid) if i succeed to solve this problem ?
Thx for all.

MAMiiX said:
Hi !
It's my first thread, i hope you can find the solutions to solve my problem.
In first time, i'm sorry to my bad english. So, my problem is:
I have a HTC HD2 and i know to install Android on that. My new challenge is to overclock my device, with SetCPU or other. I have already followed some tutorials to do a few profiles... I did it, the maximum value i selected is 998 MHZ. It's Ok i think, i cross "Set on boot" and "enbale" so when i use Quadrant Standard Edition, i check 1024 Mhz. But when i see the device of XDA's devs i can see like rafpigna's nand 3024 MHZ ! Here : http://forum.xda-developers.com/showthread.php?t=908528
My questions are:
1. How can i do it ?
2. Can i accelerate my N64's roms (with N64oid) if i succeed to solve this problem ?
Thx for all.
Click to expand...
Click to collapse
Same question here... but, we really need to use setcpu????

I hope some people can answer us

MAMiiX said:
Hi !
It's my first thread, i hope you can find the solutions to solve my problem.
In first time, i'm sorry to my bad english. So, my problem is:
I have a HTC HD2 and i know to install Android on that. My new challenge is to overclock my device, with SetCPU or other. I have already followed some tutorials to do a few profiles... I did it, the maximum value i selected is 998 MHZ. It's Ok i think, i cross "Set on boot" and "enbale" so when i use Quadrant Standard Edition, i check 1024 Mhz. But when i see the device of XDA's devs i can see like rafpigna's nand 3024 MHZ ! Here : http://forum.xda-developers.com/showthread.php?t=908528
My questions are:
1. How can i do it ?
2. Can i accelerate my N64's roms (with N64oid) if i succeed to solve this problem ?
Thx for all.
Click to expand...
Click to collapse
This is totally dependent on the Kernel supporting overclock.
This question cannot be answered completely due to the fact there are several Android ROMs with different configurations and preset Set-CPU profiles.
Also it appears you've mistaken the Quadrant score to be the frequency of the CPU? The CPU was not 3024MHz, that is the Quadrant score. The CPU was 1.5Ghz.
I believe 998MHz is the standard highest processor speed of the HD2, unless you have a Kernel which supports overclocking you can do whatever you want in Set-CPU and it won't change a thing.
I'm afraid I cannot answer your question regarding the emulator but I believe it would not have a massive effect, maybe fix some lag if you have any.

Thanks you very much. So if i install the Rapigna's buil i can have this quadrant's score ? Really ? Because it's HIS Kernel which he can does this ?

Isnt it also the case the overclocking will only work when the phone is running with the charger plugged in?
I have not seen any overclocking working on battery (although i imagine it would kill the battery!).

geekyhawkes said:
Isnt it also the case the overclocking will only work when the phone is running with the charger plugged in?
I have not seen any overclocking working on battery (although i imagine it would kill the battery!).
Click to expand...
Click to collapse
No.
There are a multitude of threads from users moaning about overclocking depleting the battery far quicker than the standard clock settings. That on its own is enough to conclude the phone doesn't have to be plugged in to allow the overclock to work.

MAMiiX said:
Thanks you very much. So if i install the Rapigna's buil i can have this quadrant's score ? Really ? Because it's HIS Kernel which he can does this ?
Click to expand...
Click to collapse
You may receive comparable results although Quadrant scores have been criticised because of what they are based upon. You may receive lower scores. Running your phone in an overclocked state is an effective way of shortening the life of your phone, if you want to play games so much I would suggest maybe a PSP or Nintendo DS?

Overclocking depends on the kernel that is used. Kernel like tytung's kernels supports max speeds of up to 1190mhz. Rapigna's kernel supports up to 1.5ghz.
Based on this, if you use these kernels, use it alongside setcpu to control your overclocking.
However, I strongly advise against overclocking + charging at the same time unless if you are in an air conditioned room. There has been some speculation that overheating might be related to the recent outburst of touchscreens failing "mysteriously". Another technique to avoid this is to use a battery temp profile in SET CPU to give you a warning when your battery has reached dangerous levels.

Thanks for all !

1190mhz is the best and safest over clock speed

[REF][SuperFriendly] Explanation of Governors, I/O Schedulers and Kernels [23-Nov]

Introduction
"It takes few hours to make a thread but it doesn't even take few seconds to say Thanks"- arpith.fbi
Click to expand...
Click to collapse
Code:
Don't be afraid to ask me anything.
I won't bite, but I might lick you.
Just thank me for this super brief thread.
Give credits to this thread by linking it if you're using any of my info.
Thank you to you too
Have you unlocked your bootloader of your current device ? If so, read it ! If not, learn the benifits ! :victory:
What is this thread about ? It is a very brief explanation of every governors and schedulers to let you find the best combo for your device.
I've been searching a lot about informations about Kernels, Governors, I/O Schedulers and also Android Optimization Tips. No matter its Google or XDA or other android forums. I will go into it and try the best I can to find these infos. So I thought of sharing it to here for the XPlay users.
My main reason to share this is to benefit users for better knowledge about Kernels, Governors, I/O Schedulers and Tips on Android Optimization. I'm not aware of whether where this should be posted, its related to kernels, governors and schedulers so I think it would be best if I share it to here. Yes, I wrote it word by word with references.Happy learning. :angel:
After months on XDA, no matter its in a development forum or Off Topic forum. Users kept on asking what's this what's that. And I'm sure that not all members will understand what is it until they bump into my thread
FAQs regarding on :-
-I/O Schedulers
-Kernel Governers
-Better RAM
-Better Battery
-FAQs
*Will add more when I found something useful.
Click to expand...
Click to collapse
I do a lot of asking by PM, to learn, it doesn't matter whether its a stupid one. (People who know me understands)
With my experience and lots of asking. I managed to find a lot of infos that we can use to optimize our phone.
I will try to explain as clear as I can.
Governors :-
-Smoothass
-Smartass
-SmartassV2
-SavagedZen
-Interactivex
-Lagfree
-Minmax
-Ondemand
-Conservative
-Brazilianwax
-Userspacce
-Powersave
-Performance
-Scary
-Lulzactive *
-Intellidemand *
-Badass *
-Lionheart *
-Lionheartx *
-Virtuous *
* Haven't gathered much needed information. Will add it later.
Explanation
OnDemand
Brief
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, OnDemand will rapidly scale the CPU up to meet the demand, then gradually scale the CPU down when it isn't needed.
Click to expand...
Click to collapse
Review
Brief says all. By a simple explantion, OnDemand scales up to the required frequency to undergo the action you are doing and rapidly scales down after use.
Conservative
Brief
It is similar to the OnDemand governor, but will scale the CPU up more gradually to better fit demand. Conservative governor provides a less responsive experience than OnDemand, but it does save batter
Click to expand...
Click to collapse
Review
Conservative is the opposite of Interactive; it will slowly ramp up the frequency, then quickly drops the frequency once the CPU is no longer under a certain usage.
Interactive
Brief
Available in latest kernels, it is the default scaling option in some stock kernels. Interactive governor is similar to the OnDemand governor with an even greater focus on responsiveness.
Click to expand...
Click to collapse
Review
Interactive is the opposite of Conservative; it quickly scales up to the maximum allowed frequency, then slowly drops the frequency once no longer in use.
Performance
Brief
Performance governer locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task. After that it returns the CPU to extremely efficient low-power state.
Click to expand...
Click to collapse
Review
Good at gaming, Really good. Disadvantages are it may damage your phone if too much usage.
Powersave
Brief
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
Click to expand...
Click to collapse
Review
Set it to your desired minimum frequency and you won't have to look for your charger for once in a while.
Scary
Brief
A new governor wrote based on Conservative with some Smartass features, it scales accordingly to Conservative's way. It will start from the bottom. It spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as Conservative right now.
Click to expand...
Click to collapse
Review
Hmm.. Overall I don't see any difference. After I understand its main objective. I was very curious and decided to use it again. Results are the same.. No difference. Report to me if anyone has tested this.
Userspace
Brief
Userspace is not a governor pre-set, but instead allows for non-kernel daemons or apps with root permissions to control the frequency. Commonly seen as a redundant and not useful since SetCPU and NoFrills exist.
Click to expand...
Click to collapse
Review
Highly not recommended for use.
Smartass
Brief
It is based on the concept of the Interactive governor.
Smartass is a complete rewrite of the code of Interactive. Performance is on par with the “old” minmax and Smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Click to expand...
Click to collapse
Review
Smartass is rather the governer that will save your battery and make use of your processor for daily use. Like the brief explantion said " Smartass will spend much more time on lower frequencies." So logically you don't need for sleep profiles anymore.
SmartassV2
Brief
Theoretically a merge of the best properties of Interactive and OnDemand; automatically reduces the maximum CPU frequency when phone is idle or asleep, and attempts to balance performance with efficiency by focusing on an "ideal" frequency.
Click to expand...
Click to collapse
Review
This is a much favourite to everybody. I believe almost everyone here is using SmartassV2. Yes, it is better than Smartass because of its speed no scaling frequencies from min to max at a short period of time.
Smoothass
Brief
A much more aggressive version of Smartass that is very quick to ramp up and down, and keeps the idle/asleep maximum frequency even lower.
Click to expand...
Click to collapse
Review
In my personal experience, this is really useful for daily use. And yes, I'm using it all the time. It may decrease your battery life. I saw it OC itself to 1.4 gHz when I set it to 1.2. Good use. Recommended.
Brazilianwax
Brief
Similar to SmartassV2. More aggressive scaling, so more performance, but less battery.
Click to expand...
Click to collapse
Review
Based on SmartassV2. But its advantage is a much more performance wise governor.
SavagedZen
Brief
Another SmartassV2 based governor. Achieves good balance between performance & battery as compared to Brazilianwax.
Click to expand...
Click to collapse
Review
Not much difference compared to SmartassV2. But it is a optimized version of it.
Lagfree
Brief
Again, similar to Smartass but based on Conservative rather than Interactive, instantly jumps to a certain CPU frequency after the device wakes, then operates similar to Conservative. However, it has been noted as being very slow when down-scaling, taking up to a second to switch frequencies.
Click to expand...
Click to collapse
Review
Used it before. Like the name of the governor, I didn't experience any lag whatsoever. Another governor based on performance, but not battery efficient.
MinMax
Brief
MinMax is just a normal governor. No scaling intermediate frequency scaling is used.
Click to expand...
Click to collapse
Review
Well.. it's too normal that I can't really say anything about it..
Interactivex
Brief
InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to optimize the balance of battery vs performance. InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
Click to expand...
Click to collapse
Review
A better understanding from the brief to you users, this is an Interactive governor with a wake profile. More battery friendly than Interactive.
Due to current kernels doesn't have these governors. I will be delaying the explanation, its very interesting. If you want it ASAP, post below
-Lulzactive *
-Intellidemand *
-Badass *
-Lionheart *
-Lionheartx *
-Virtuous *
**********************************************************************************************************************************************************************
I/O Schedulers(thanks to droidphile)
Deadline
Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.
Advantages:
Nearly a real time scheduler.
Excels in reducing latency of any given single I/O.
Best scheduler for database access and queries.
Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
Like noop, a good scheduler for solid state/flash drives.
Disadvantages:
When system is overloaded, set of processes that may miss deadline is largely unpredictable.
Click to expand...
Click to collapse
Noop
Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data. Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.
Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance.
Click to expand...
Click to collapse
Anticipatory
Based on two facts
i) Disk seeks are really slow.
ii) Write operations can happen whenever, but there is always some process waiting for read operation.
So anticipatory prioritize read operations over write. It anticipates synchronous read operations.
Advantages:
Read requests from processes are never starved.
As good as noop for read-performance on flash drives.
Disadvantages:
'Guess works' might not be always reliable.
Reduced write-performance on high performance disks.
Click to expand...
Click to collapse
BFQ
nstead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it's behavior.
Advantages:
Believed to be very good for usb data transfer rate.
Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)
Considered an accurate i/o scheduler.
Achieves about 30% more throughput than CFQ on most workloads.
Disadvantages:
Not the best scheduler for benchmarking.
Higher budget assigned to a process can affect interactivity and increased latency.
Click to expand...
Click to collapse
CFQ
Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.
Advantages:
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
Disadvantages:
Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.
Click to expand...
Click to collapse
SIO
Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.
Advantages:
Simple, so reliable.
Minimized starvation of requests.
Disadvantages:
Slow random-read speeds on flash drives, compared to other schedulers.
Sequential-read speeds on flash drives also not so good.
Click to expand...
Click to collapse
VR
Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.
Advantages:
May be best for benchmarking because at the peak of it's 'form' VR performs best.
Disadvantages:
Performance fluctuation results in below-average performance at times.
Least reliable/most unstable.
Click to expand...
Click to collapse
Credits
-droidphile
-kokzhanjia

Reserved for kernel infos
Sent from my WT19i

Yes, we do have kernels with Lionheart, lulzactive and intellidemand.
Nice reference cheers.
Sent from Xperia Play (R800a) with Tapatalk

CosmicDan said:
Yes, we do have kernels with Lionheart, lulzactive and intellidemand.
Nice reference cheers.
Sent from Xperia Play (R800a) with Tapatalk
Click to expand...
Click to collapse
Really ? Okay will add it in later
Sent from my WT19i

kokzhanjia said:
Really ? Okay will add it in later
Sent from my WT19i
Click to expand...
Click to collapse
Yeah LuPuS has Lulzactive, Virtuous, Intellidemand, Lazy, Ondemandx, Lionheart and Badass added (but no mention of LionheartX).
Turbo kernel also has intellidemand but the parameters have been modified quite a bit (by me) to suit our snapdragon SOC's better. I think wedgess also put these changes into LuPuS too (at least one of the ICS/JB kernels he builds he said he did). The browser mode still has no effect AFAIK but in my experience it's more battery-friendly and better performance than on-demand (thanks mainly to dbus_input ramping). But many users have reported slightly better gaming experience with SmartAssv2.

Great reference, this will be of much help to new comers, thanks for the hard work you put into this.

CosmicDan said:
Yeah LuPuS has Lulzactive, Virtuous, Intellidemand, Lazy, Ondemandx, Lionheart and Badass added (but no mention of LionheartX).
Turbo kernel also has intellidemand but the parameters have been modified quite a bit (by me) to suit our snapdragon SOC's better. I think wedgess also put these changes into LuPuS too (at least one of the ICS/JB kernels he builds he said he did). The browser mode still has no effect AFAIK but in my experience it's more battery-friendly and better performance than on-demand (thanks mainly to dbus_input ramping). But many users have reported slightly better gaming experience with SmartAssv2.
Click to expand...
Click to collapse
Yeah. Saw your work Nice one.. anymore in depth infos about kernels at here ? I want to add a bonus one for this..
paragroth said:
Great reference, this will be of much help to new comers, thanks for the hard work you put into this.
Click to expand...
Click to collapse
Thanks
Coloured signatures are nice

Nah that's pretty much it
Sent from Xperia Play (R800a) with Tapatalk

Throughout my experience(mainly from observing CPU speeds during music playback), I found that:
Scary:
Ramps up to max after reaching a threshold (50/60% CPU load) then slow scales down to match as 50-80% CPU Load @ X MHz. After a while if load lowers (30-40%), it will clock down to match the 50-80% load. You will see a lot of 100% @ low MHz with this governor.
SavagedZen:
It maintains a 80-90% CPU Load @ X MHz for a fairly constant load. This one also scales based on the Max CPU Freq. settings. So the lower your Max CPU Freq, the better it is at maintaining the CPU Load/MHz balance (for music playback at least).
I didn't look at the source, so these are just from observations only. So I might be talking out of my ass.
Also, having good CPU Load at appropriate CPU Speeds may or may not contribute to battery life. No experiments showed that yet iirc.
Monitoring done via "Diagnosis - System Information" an app that generates an overlay with whatever information your want ie cpu load, speed, memory free, used, disk io, network io, etc.
Refresh rate kept at 5 seconds to keep CPU Load interference minimal (lower than ICS/JB CPU Info overlay from Development, Settings tab).

Great thread, this should be sticky!

jabberwocky_one said:
Throughout my experience(mainly from observing CPU speeds during music playback), I found that:
Scary:
Ramps up to max after reaching a threshold (50/60% CPU load) then slow scales down to match as 50-80% CPU Load @ X MHz. After a while if load lowers (30-40%), it will clock down to match the 50-80% load. You will see a lot of 100% @ low MHz with this governor.
SavagedZen:
It maintains a 80-90% CPU Load @ X MHz for a fairly constant load. This one also scales based on the Max CPU Freq. settings. So the lower your Max CPU Freq, the better it is at maintaining the CPU Load/MHz balance (for music playback at least).
I didn't look at the source, so these are just from observations only. So I might be talking out of my ass.
Also, having good CPU Load at appropriate CPU Speeds may or may not contribute to battery life. No experiments showed that yet iirc.
Monitoring done via "Diagnosis - System Information" an app that generates an overlay with whatever information your want ie cpu load, speed, memory free, used, disk io, network io, etc.
Refresh rate kept at 5 seconds to keep CPU Load interference minimal (lower than ICS/JB CPU Info overlay from Development, Settings tab).
Click to expand...
Click to collapse
Nono you are right. I read these before and your observation is just about it, thanks for the info
chabbe11 said:
Great thread, this should be sticky!
Click to expand...
Click to collapse
Thank you
Sent from my WT19i with Real Xperia r1

Am I setting it up the right way?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I prefer using that minimum and maximum.
And would this screen off profile work, even if I have configured the main minimum? The 100mhz for screen off really saves a lot of my battery.
Sent from my R800i using Tapatalk 2

Gr8 helped me a lot in understanding alll of this .....

bhavei said:
Am I setting it up the right way?
I prefer using that minimum and maximum.
And would this screen off profile work, even if I have configured the main minimum? The 100mhz for screen off really saves a lot of my battery.
Sent from my R800i using Tapatalk 2
Click to expand...
Click to collapse
Yes it is right. I didnt really tried the other way that you mentioned, because i have No-Frills pre-installed in my settings..but i see it worked. Of course it will save battery.. Nice
piku2008 said:
Gr8 helped me a lot in understanding alll of this .....
Click to expand...
Click to collapse
Will add more soon About kernels, Is there any BFS kernels around here ? Most kernels are CFS..
Sent from my WT19i with Real Xperia r1

kokzhanjia said:
About kernels, Is there any BFS kernels around here ? Most kernels are CFS..
Click to expand...
Click to collapse
There was, I ported it over a few months ago. But I removed it because it was causing priority issues. The latest BFS patch for our kernel has some critical bugs, so I ditched it. When I get ext# fixed in .60 kernel up and going I will probably take another crack at it, backporting one of the more recent 3.x BFS versions.
One of the LuPuS kernels might still have na laternative BFS version, but I think wedgess stopped building it for the same reason as me.

CosmicDan said:
There was, I ported it over a few months ago. But I removed it because it was causing priority issues. The latest BFS patch for our kernel has some critical bugs, so I ditched it. When I get ext# fixed in .60 kernel up and going I will probably take another crack at it, backporting one of the more recent 3.x BFS versions.
One of the LuPuS kernels might still have na laternative BFS version, but I think wedgess stopped building it for the same reason as me.
Click to expand...
Click to collapse
I see, there are really few BFS based kernels out there. BFS is better in my opinion so i would like to elaborate more about BFS to attract more users.
Btw, one guy in Xperia Mini, Mini Pro and Active forums had already successfully making it up and running for stock and CM ROMs. Its already hitted version 2.3
Maybe you could get some help from him ? Name is Mesa Kernel.
Sent from my WT19i with Real Xperia r1

kokzhanjia said:
I see, there are really few BFS based kernels out there. BFS is better in my opinion so i would like to elaborate more about BFS to attract more users.
Btw, one guy in Xperia Mini, Mini Pro and Active forums had already successfully making it up and running for stock and CM ROMs. Its already hitted version 2.3
Maybe you could get some help from him ? Name is Mesa Kernel.
Sent from my WT19i with Real Xperia r1
Click to expand...
Click to collapse
I was using v0.313 of BFS, it wasn't that hard - just had to adapt the patch for the Xperia's stupid kernel. That version is so unstable and buggy, in fact all 2.6.x BFS patches were so problematic that the official page has removed them.
I'll check it out, if he back-ported BFS for Linux kernel 3.0 and has them on GitHub, otherwise it would be easier just to do it myself. But I have other more important concerns for Zeus development right now, BFS doesn't really bring any significant performance boost (which is why it is continually rejected from AOSP inclusion).

CosmicDan said:
I was using v0.313 of BFS, it wasn't that hard - just had to adapt the patch for the Xperia's stupid kernel. That version is so unstable and buggy, in fact all 2.6.x BFS patches were so problematic that the official page has removed them.
I'll check it out, if he back-ported BFS for Linux kernel 3.0 and has them on GitHub, otherwise it would be easier just to do it myself. But I have other more important concerns for Zeus development right now, BFS doesn't really bring any significant performance boost (which is why it is continually rejected from AOSP inclusion).
Click to expand...
Click to collapse
Oh... i didnt know that.. anyway, I don't think he has his github set up. I didnt saw a link to his github on his thread. And isnt BFS aimed for forward looking(like only performing on a task that is given without any concerns) ? I read about it at google docs about it. And i don't really know how to explain it clearly..
Good luck in your development my frirend. And this thread has been moved to General section. Hope you can find it and Nice to have another friend
Sent from my WT19i with Real Xperia r1

This is nice info,
Thanks

Thanks man. This is awesome. Much appreciated

TricksterMod replacement

Do you know any good alternatives for TricksterMod that support OC and undervolting? I'm running latest ParanoidAndroid with M-kernel. Help much appreciated!

Why do you want to use another app? If you read OP of M-Kernel, you will see that only trickster is supported to change parameters. Extract from the OP: "The only app supported for changing any kernel parameters and settings is TricksterMod".

Odp: TricksterMod replacement
I want to try another one, because when I downclock to 1,2 Ghz, there seems to be no direct voltage change option for that frequency, closest is 1170 and 1230 Mhz. So I have no idea which one should I change.

That's the way the nexus 7 gets frequencies. Instead of using specific voltages, it uses an incremental table.
Sent from my Nexus 7 using xda app-developers app

Yep, i've read that tegra uses the table as a reference... Even if there the kernel has clock speeds that directly relate to the one you are going to use, -50mv does not mean a direct -50mv sent to the core. Also, tegra does auto 'cold zone' undervolt when it's capable. Hence, the voltage set contrasted to the frequence set in any software is relative to tegra but not 100% definitive...

Odp: TricksterMod replacement
Thanks, seems like undervolting my Nexus won't be as easy as I thought.

Dont worry too much about it. It's just like your local speed limit, if 40mph/kph you wont stay exactly at 40 all the time, neither always below or always above. It will be a reference and realtime decisions are made based on road conditions. Somewhat simillar here.
Im lucky to have a good chip, able to run at 1.6G with voltages meant for 1.2 stock... Able to push it lower but it starts locking up once in a while. It might take a few days so have fun! Remember to backup anything important just in case =>

Underclocking CPU Gives Better Benchmark Scores?

Hi,
I don't know if these benchmark applications are valid, but I downloaded AnTuTu Benchmark and messed around with my CPU frequency. At first, I maxed out the core clock speed to 1.3 GHz. Next, I set the maximum clock speed to 475 MHz. When I set it to 475 MHz, I get a better CPU score.
Something does not seem right. Any thoughts?

...and now you know why folks don't trust benchmarks.

There is a thermal CPU control. By overclocking, you are overheating, and it's underclocking to prevent itself overheating...

CrazyPeter said:
There is a thermal CPU control. By overclocking, you are overheating, and it's underclocking to prevent itself overheating...
Click to expand...
Click to collapse
That was funny to read.
By overclocking, your in fact under clocking or so it seems.

Yes that can happen. If it gets too hot it will probably start throttling each core back which gives worse and worse scores.
Right now I have mine up at 1600Mhz and I get better scores than 1300Mhz but as well I'm running nearly the same voltages that 1300Mhz is.

Nice!

Interesting guys,
I guess I'll just leave it at default settings

Too bad I can't root my device .......

STXInnovation said:
Interesting guys,
I guess I'll just leave it at default settings
Click to expand...
Click to collapse
I made a bunch of (repeated) measurements with a CM10.1 nightly kernel (at various Fmax settings) and the results were quite squirrelly. When I get a little time, I'll make some more tests and post up the data.
BTW - if you were using TricksterMod are you sure you actually applied the changes? You didn't provide any numbers (your results) and it is not uncommon for Antutu to produce 10% different results in that benchmark from run to run (and much much worse at different Fmax values!!) - so is it possible you just mistook a random variation for a "change for the worse"?

bftb0 said:
I made a bunch of (repeated) measurements with a CM10.1 nightly kernel (at various Fmax settings) and the results were quite squirrelly. When I get a little time, I'll make some more tests and post up the data.
BTW - if you were using TricksterMod are you sure you actually applied the changes? You didn't provide any numbers (your results) and it is not uncommon for Antutu to produce 10% different results in that benchmark from run to run (and much much worse at different Fmax values!!) - so is it possible you just mistook a random variation for a "change for the worse"?
Click to expand...
Click to collapse
Yeah would have to agree here. Between voltage and clocks you can really affect any benchmark score. I knits I've been playing with it. Though a swing of 10% in AuTutu is pretty big. I've had maybe a few hundred points at most.
Sent from my Nexus 7 using xda app-developers app

Abandoned

abandoned.

Can this apply on mi 11?

huycoixvb said:
Can this apply on mi 11?
Click to expand...
Click to collapse
Not exactly.
This chart is for the sd865.
Mi11 has a sd888, so the voltage levels will be different.
The basic idea is the same. But it requires testing and proofing.

Do you have source of konabess app? If possibility, send me pls :3

Thanks really useful

Great guide, this post definitely deserves more views. Got one question: if my goal frequency is (let's say) 660MHz, isn't it better to set ddr7 and ddr8 max values to 11? Would it squeeze out more performance at max load, in your opinion?

Keppo2911 said:
Great guide, this post definitely deserves more views. Got one question: if my goal frequency is (let's say) 660MHz, isn't it better to set ddr7 and ddr8 max values to 11? Would it squeeze out more performance at max load, in your opinion?
Click to expand...
Click to collapse
Not really. The ddr timings are not really set for balanced performance.
Trottling happens alot, so finding a balance give overall better performance than burst performance thatxthen gives lower results due tocthe time to cool being longer than the time to heat up.
I was able to get a higher antutu score than stock at 670, with timings between 4-9
But its all based on user preference and work loads. These settings work excellently well for me.
The big difference though is the voltage table. Less electricity going in creates less heat.
The ram timings are just a minor tweak to add a bit more to the clock. Its the voltage that really changed big time for me. Lower volts, less heat, longer time at high clocks.

Patrick Morgan said:
Not really. The ddr timings are not really set for balanced performance.
Trottling happens alot, so finding a balance give overall better performance than burst performance thatxthen gives lower results due tocthe time to cool being longer than the time to heat up.
I was able to get a higher antutu score than stock at 670, with timings between 4-9
But its all based on user preference and work loads. These settings work excellently well for me.
The big difference though is the voltage table. Less electricity going in creates less heat.
The ram timings are just a minor tweak to add a bit more to the clock. Its the voltage that really changed big time for me. Lower volts, less heat, longer time at high clocks.
Click to expand...
Click to collapse
Loud n' clear, thanks alot!

How can I edit Votages is volts table ?

Can l do this in xiaomi mi 10t pro?

yeh with any smartphone with snapdragon from 855. Just root and install konabess from GitHub and overclock and undervolt

Patrick Morgan said:
abandoned.
Click to expand...
Click to collapse
Hi Patrick, sorry to ask but you abandoned for some reason?
I have a OnePlus 9R (SNAP 870) and it's hot, I'm looking for an undervolt on it but I can't find anything, could you give me some direction?

Use this table from this post in this video.
Max freq on Poco F3 is 683Mhz you have to try if can be overclock higher but Undervolt is still possible as all phones.
I recommend new version 0.15 on two lower freq retention and min_svs or low svs on third and do like in this table so 670 voltage SVS_L2.
I don't think that Snapdragon 870 is good choice for gaming better is to buy 865 and overclock to 950Mhz or 1ghz giving snapdragon 888 performance with lower temps than 870 and 888.
If you do root try to underclock CPU to 865+ 3ghz or 2.9ghz to lower temps performance difference isn't noticable.

vinyimp said:
Hi Patrick, sorry to ask but you abandoned for some reason?
I have a OnePlus 9R (SNAP 870) and it's hot, I'm looking for an undervolt on it but I can't find anything, could you give me some direction?
Click to expand...
Click to collapse
things just update faster than I have time to test.
my charts became old, even the one Dr.Brown is using on his video, its quite old missing voltage steps and have not been tested on the newer versions of Konabess.
my original thread here took about 3 months of my time testing every possible setting to make sure other users didnt brick or toast their devices.
I took everything down when I seen alot of new rom updates, and konabess updates were causing bugs in the settings I had here for many users.
I didn't have time to retest everything and update my charts, I also had to deal with people stealing my charts and claiming the work for them selves. which I had to open youtube reports, contact google with proof of my work contact admins here and a few other sites too, etc all because some people didn't want to add a credit of where they found my charts.
so after a good week of emailing and chatting on the phone with google fraud control i decided to not continue posting my work, that may actually cause damage if used wrongly was too much work to deal with.
I'm still just too busy. my phone is stock android non rooted now because some apps I use can't be hidden.
so, I have no time to update this thread. I have no desire to leave the information for others to brick their devices.
the chart on dr.browns video is older than my most up to date chart, but still even that is months behind the current app and rom version changes.
my best advice is, if your phone works the way you want it, dont mess with any of the clock speeds. just undervolt some steps that are commonly used and test those.
too many people have tried to overclock their phones GPUs above 900 and lost functionality (permanently) or just hard bricked the phone (where an unbrick tool wont recover it.)
many will say its harmless, but its about usage. if you game alot and want to game alot, overclocking will create more heat, even if you undervolt. the result will be a paperweight.
those many people are not you, and not your phone. so anything can happen.
be mindful and careful of the settings you use. and install a temperature monitor for CPU and GPU.
going over 70'c will risk the loss of your unit.

Patrick Morgan said:
things just update faster than I have time to test.
my charts became old, even the one Dr.Brown is using on his video, its quite old missing voltage steps and have not been tested on the newer versions of Konabess.
my original thread here took about 3 months of my time testing every possible setting to make sure other users didnt brick or toast their devices.
I took everything down when I seen alot of new rom updates, and konabess updates were causing bugs in the settings I had here for many users.
I didn't have time to retest everything and update my charts, I also had to deal with people stealing my charts and claiming the work for them selves. which I had to open youtube reports, contact google with proof of my work contact admins here and a few other sites too, etc all because some people didn't want to add a credit of where they found my charts.
so after a good week of emailing and chatting on the phone with google fraud control i decided to not continue posting my work, that may actually cause damage if used wrongly was too much work to deal with.
I'm still just too busy. my phone is stock android non rooted now because some apps I use can't be hidden.
so, I have no time to update this thread. I have no desire to leave the information for others to brick their devices.
the chart on dr.browns video is older than my most up to date chart, but still even that is months behind the current app and rom version changes.
my best advice is, if your phone works the way you want it, dont mess with any of the clock speeds. just undervolt some steps that are commonly used and test those.
too many people have tried to overclock their phones GPUs above 900 and lost functionality (permanently) or just hard bricked the phone (where an unbrick tool wont recover it.)
many will say its harmless, but its about usage. if you game alot and want to game alot, overclocking will create more heat, even if you undervolt. the result will be a paperweight.
those many people are not you, and not your phone. so anything can happen.
be mindful and careful of the settings you use. and install a temperature monitor for CPU and GPU.
going over 70'c will risk the loss of your unit.
Click to expand...
Click to collapse
Perfect understood Patrick, it's a shame all this happened, unfortunately people don't give value/recognition to people who help for free!
I'll enjoy and tell you my experience, my 9R is on OOS 11.2.6.6 (Stock) and with Kernel Stock as well (since there isn't much customization yet)
They ended up recommending the Dr. Brown video and I decided to do some tests, if the person copies the Overclock that he does in that video (905MHz) the device will not start, it will be necessary to flash the previous boot.img
This happened to me and I was able to reverse the situation (probably because the KERNEL does not support such clocks that would even be unnecessary)
But on his channel there is a more recent video teaching how to Underclock and so I took the clock's as a base and started to make my fine adjustments
Clocks follow this pattern; 512 - 490 - 455 - 445 - 305 - 295 - 195
Voltages as per your chart; SVS_L2 - SVS_L1 _ SVS_L0 - SVS_L0 - LOW_SVS - LOW_SVS - LOW_SVS
And the BUS frequencies I left original, so I found SWEET SPOT, the device is much cooler, stable, in games despite the Underclock holding well (80 FPS+ with graphics at maximum)
Hopefully there will soon be some app/kernel that can undervolt the CPU too, maybe just remove -25mv/-50mv and do some testing as most of the heat comes from it.
I'm quite satisfied and I'm grateful to you because without your charts in Dr. Brown's video, wouldn't know how to do!
I wish you all the best, success!

vinyimp said:
Perfect understood Patrick, it's a shame all this happened, unfortunately people don't give value/recognition to people who help for free!
I'll enjoy and tell you my experience, my 9R is on OOS 11.2.6.6 (Stock) and with Kernel Stock as well (since there isn't much customization yet)
They ended up recommending the Dr. Brown video and I decided to do some tests, if the person copies the Overclock that he does in that video (905MHz) the device will not start, it will be necessary to flash the previous boot.img
This happened to me and I was able to reverse the situation (probably because the KERNEL does not support such clocks that would even be unnecessary)
But on his channel there is a more recent video teaching how to Underclock and so I took the clock's as a base and started to make my fine adjustments
Clocks follow this pattern; 512 - 490 - 455 - 445 - 305 - 295 - 195
Voltages as per your chart; SVS_L2 - SVS_L1 _ SVS_L0 - SVS_L0 - LOW_SVS - LOW_SVS - LOW_SVS
And the BUS frequencies I left original, so I found SWEET SPOT, the device is much cooler, stable, in games despite the Underclock holding well (80 FPS+ with graphics at maximum)
Hopefully there will soon be some app/kernel that can undervolt the CPU too, maybe just remove -25mv/-50mv and do some testing as most of the heat comes from it.
I'm quite satisfied and I'm grateful to you because without your charts in Dr. Brown's video, wouldn't know how to do!
I wish you all the best, success!
Click to expand...
Click to collapse
I recommend Overclocking by your self to higher freq.
This config from video don't boot on any sn865 devices even Apollo but I can overclock to 940 MHz stable.
I know that Poco F3 has lock freq to 683 MHz after that doesn't boot.
I think your UV is too high 512 can get as low as SVS_L1 or SVS_L0

astronomy2021 said:
I recommend Overclocking by your self to higher freq.
This config from video don't boot on any sn865 devices even Apollo but I can overclock to 940 MHz stable.
I know that Poco F3 has lock freq to 683 MHz after that doesn't boot.
I think your UV is too high 512 can get as low as SVS_L1 or SVS_L0
Click to expand...
Click to collapse
Unfortunately on the OnePlus 9R (all stock) any clock higher than the original (670 MHz) the system doesn't boot (I don't know why, maybe some ROM limitation or KERNEL doesn't support it)
I ended up Underclocking to have a cooler device and in fact it is cooler without loss of performance in normal use and holding up well in games at maximum graphics
No artifacts, crashing or instability
As for the voltage on 512, it could really go with SVS_L1 - it goes between SVS_L2 and L1 on Patrick's Chart (525 - 512 - 490 MHz) I intend to do a test soon, for now it's stable and in games it doesn't get too hot!

vinyimp said:
Unfortunately on the OnePlus 9R (all stock) any clock higher than the original (670 MHz) the system doesn't boot (I don't know why, maybe some ROM limitation or KERNEL doesn't support it)
I ended up Underclocking to have a cooler device and in fact it is cooler without loss of performance in normal use and holding up well in games at maximum graphics
No artifacts, crashing or instability
As for the voltage on 512, it could really go with SVS_L1 - it goes between SVS_L2 and L1 on Patrick's Chart (525 - 512 - 490 MHz) I intend to do a test soon, for now it's stable and in games it doesn't get too hot!
Click to expand...
Click to collapse
No it is lock by Qualcomm to that freq so of doesn't boot it like 855+/860.
That why I buy Mi 10T with 865 and can be overclock to even 2ghz by someone.

astronomy2021 said:
No it is lock by Qualcomm to that freq so of doesn't boot it like 855+/860.
That why I buy Mi 10T with 865 and can be overclock to even 2ghz by someone.
Click to expand...
Click to collapse
Understood, a custom KERNEL doesn't unlock this lock by Qualcomm?
I had a OnePlus 8 with 865, today I just miss it

vinyimp said:
Understood, a custom KERNEL doesn't unlock this lock by Qualcomm?
I had a OnePlus 8 with 865, today I just miss it
Click to expand...
Click to collapse
Maybe can by i case of 855+ was lock on all phones from manufacturer process.
But early builds of F3 has unlock freq but after that they are block that why buying 865 is better if you want performance for gaming or emulation like switch. I now play Zelda breath of the wild on my Mi 10 t and after 168days will be Overclocking to 940Mhz giving me performance of 888.