Help for OC and UV!!! - HTC Incredible S

hey i needed some help on overclocking and changing some voltages on my device!!
1.i have read threads and guides on other forums before which explain how to OC and what are governers and schedulers etc.
2. most threads on this topic are from different devices' forums
so i thought their frequencies voltages must vary as they have different CPUs and hence started a new thread!!
3. What i want to know is, what voltages should i choose at different frequencies??
or it is completely not important to set voltages??
4. Earlier i used setCPU but it doesnt stick to frequencies i set and resets default 1024 after reboot.
how do i avoid this??
Currently i am using AnTuTu CPU master PRO for doing all this
please guide me if possible provide specific values on which htc incS performs good!!!
my system details are in my signature
any help is appreciated!!

prunzzz said:
hey i needed some help on overclocking and changing some voltages on my device!!
1.i have read threads and guides on other forums before which explain how to OC and what are governers and schedulers etc.
2. most threads on this topic are from different devices' forums
so i thought their frequencies voltages must vary as they have different CPUs and hence started a new thread!!
3. What i want to know is, what voltages should i choose at different frequencies??
or it is completely not important to set voltages??
4. Earlier i used setCPU but it doesnt stick to frequencies i set and resets default 1024 after reboot.
how do i avoid this??
Currently i am using AnTuTu CPU master PRO for doing all this
please guide me if possible provide specific values on which htc incS performs good!!!
my system details are in my signature
any help is appreciated!!
Click to expand...
Click to collapse
+1
Sent from my HTC Incredible S using Tapatalk 4 Beta

I've commented on this 100 times before but I can't search on mobile. So there are a few threads out there explaining this in this forum. If you can search and find them they'll go into a little more detail than I'm about to.
OK so the OC controller you're using I'm unfamiliar with however they all do the same thing. What you should do is find out which governers your kernel supports and than use Google to figure out what their perimeters are. Generally speaking you're going to want to have different profiles set up for "screen on"and "screen off" for your basic set up. Later once you understand why you're doing you can set the governers for gaming, charging etc.
Set your screen off for around 200 min and 400 max. This will keep your phone from running high frequencies that will drain your battery while you are not using your phone. Set the governer to smart ass or on demand, read about them and see what's best for you.
Screen on set to max 1200 - 1400 if you want high performance and the low to whatever you like just not above 400 as it will not allow your CPU to idle. Set governer to smartass. You don't really need to be running above 1100 for most I stances however you will notice it is a bit peppier. While running at higher freqs you will notice your phone heating up... I have never heard of an incs over heating and frying in every case your phone will shut itself off or freeze. If you're afraid of overheating there's a profile for that too to change your freqs at certain temps.
Do NOT choose "set at boot" until you are certain that your set freqs will not hang your phone, doing this will cause your phone to freeze as soon as your ROM boots up causing a boot loop and you will have to revert to a backup to fix the situation.
As for uv'ing the premise of this is to save battery life, running at lower freqs than intended. I recommend not bothering but if you do want to try and save battery I generally suggest -10 for all values. Be aware it is very common for this to hang your phone. You have to tinker with it to get it right for your ROM.
Hope this helps any other questions just ask.
Sent from my Incredible S using xda premium

itsbeertimenow said:
I've commented on this 100 times before but I can't search on mobile. So there are a few threads out there explaining this in this forum. If you can search and find them they'll go into a little more detail than I'm about to.
OK so the OC controller you're using I'm unfamiliar with however they all do the same thing. What you should do is find out which governers your kernel supports and than use Google to figure out what their perimeters are. Generally speaking you're going to want to have different profiles set up for "screen on"and "screen off" for your basic set up. Later once you understand why you're doing you can set the governers for gaming, charging etc.
Set your screen off for around 200 min and 400 max. This will keep your phone from running high frequencies that will drain your battery while you are not using your phone. Set the governer to smart ass or on demand, read about them and see what's best for you.
Screen on set to max 1200 - 1400 if you want high performance and the low to whatever you like just not above 400 as it will not allow your CPU to idle. Set governer to smartass. You don't really need to be running above 1100 for most I stances however you will notice it is a bit peppier. While running at higher freqs you will notice your phone heating up... I have never heard of an incs over heating and frying in every case your phone will shut itself off or freeze. If you're afraid of overheating there's a profile for that too to change your freqs at certain temps.
Do NOT choose "set at boot" until you are certain that your set freqs will not hang your phone, doing this will cause your phone to freeze as soon as your ROM boots up causing a boot loop and you will have to revert to a backup to fix the situation.
As for uv'ing the premise of this is to save battery life, running at lower freqs than intended. I recommend not bothering but if you do want to try and save battery I generally suggest -10 for all values. Be aware it is very common for this to hang your phone. You have to tinker with it to get it right for your ROM.
Hope this helps any other questions just ask.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
thanks a lot

Related

[Q] Constant overclocking safe?

Setcpu determines that 1704mhz can be achieved, would it be safe running the GNote at that constantly does anyone know?
Hmm...
I would say, this is depending on more than only the frequency,
if you set the voltages for 1704mhz on e.g. 1650mV u'll get a very hot phone and a hot accu... this will not be good for ur phone, if you're doing this constantly.
But if u find a good compromise between voltage and frequncy, u can do this constantly.
Also you could make profiles in SetCPU so that for example if you're gaming it will set voltage and frequency to 1704mhz and if your screen is off, it setz frequency to 800mhz.
So you have to decide if u'll want to take the risk...
I hope i could help u and sorry for my bad english,
Schnizel.
Aside from benchmarks theres no real benefit from running at 1.7ghz. Most of the time thebphone stays at 200 to 1200mhz
safe?
thought overclocking is always a risk. think nobody here will tell go do it its safe is there ?
and why would you overclock a 1,4ghz dual core in a mobile ?
Thanks, i've seen in a different thread that the voltage would need to be lowered so overheating isnt too bad.
SetCPU gives information on what frequencies are used by percentage and mine is either minimum or max so it suggested its topping out while doing stuff....
1.7ghz is too much for a constant setting.
I had my phone at 1.7 and while watching Netflix on 3G, it would get TOO HOT. and i mean TOO HOT.

[Q] Kernel for CM7.2 Stable that allows OC and governor change

I have just updated to Cyanogenmod 7.2 stable on my P990 Optimus 2x (Fido Canadian version).
When I go to the CPU settings I cannot change the min/max frequencies or select a CPU governor.
I have done some research and found kernels like Vork and FauxDS, but they are for 7.1 nightlies so I am not sure if it is a good idea to flash them.
What I am most afraid about is the possibility of getting the black screen of death while my phone sleeps (it happened once already but it stopped after I changed to a different charger and reflashed CM7.2).
The reason why I want to change the settings is that there tends to be scrolling lag (my old HTC Desire Z was faster!) and there is also a bit of lag waking up the phone (lockscreen does not appear instantly when pressing power button).
Does anyone know what is the best kernel I can flash to enable frequency/governor changes in CM7.2 stable? I would prefer not to change the ROM if possible as I am kinda nooby in comparison to the XDA community in general. Thanks for any help.
I suggest you try Etana kernel. It has the things you need. Also use CPU master to set profiles and minimum CPU frequencies. I used something like min freq 352 MHz when asleep (don't worry doesn't drain battery) and I had no lag whatsoever.
heavencanwait said:
I suggest you try Etana kernel. It has the things you need. Also use CPU master to set profiles and minimum CPU frequencies. I used something like min freq 352 MHz when asleep (don't worry doesn't drain battery) and I had no lag whatsoever.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1427646 ?
If so, do I just flash the zip off the sd card using ClockworkMod? And what are the differences between lite and DS?
Thanks.
All right, after reading, I determined I don't need LOC/HOC/DS as I don't intend to raise the max frequency, I just want to raise min frequency.
Installed the Etana kernel via CWM and it works. I can raise minimum frequency, though I still cannot see a governor option! Any idea how to get my governor setting back?
You can use CPU master and set some profiles. It's not exactly the same as governors but it's as close as it gets and it gets the job done pretty well. As far as I remember there were two governors for O2X - powersave and performance. I've always used performance and I can't tell if there's a HUGE difference in battery usage. I guess performance utilizes higher CPU frequencies when the device is asleep and somehow scales faster to even higher frequencies when needed to. But this might be complete crap as I am not too much into how CPUs work...
And please use the THANKS button (right below the user name), it kind of forum etiquette and it keeps people motivated to help others. Thank the Etana developer too.
heavencanwait said:
You can use CPU master and set some profiles. It's not exactly the same as governors but it's as close as it gets and it gets the job done pretty well. As far as I remember there were two governors for O2X - powersave and performance. I've always used performance and I can't tell if there's a HUGE difference in battery usage. I guess performance utilizes higher CPU frequencies when the device is asleep and somehow scales faster to even higher frequencies when needed to. But this might be complete crap as I am not too much into how CPUs work...
And please use the THANKS button (right below the user name), it kind of forum etiquette and it keeps people motivated to help others. Thank the Etana developer too.
Click to expand...
Click to collapse
Thanks for letting me know, I didn't realize there was a thanks button at first haha.
Fixed!
As for now CPU Master in his profiles let's you choose governor. We have only 2. Power save nd Performance.
Sent from LG 2X using Tapatalk 2 Elite

[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.

Clocking problems

Hi,
first, I want to apologize for my bad english.
I have a problem with the clockingspeed of my HTC One.
I was impressed by how bad the battery life of the One is.
I found out, that the CPU is always clocking at 1,7Ghz, both values (Min AND Max) are set to 1.7 Ghz.
If I turn on the battery-safe option, it clocks at 1Ghz, but again on both values.
So, I have downloaded some CPU apps, which should let me change the clocking speed of the CPU.
Well, it works, but if I turn on "Set on boot", and reboot, the values are gone.
I thought, this would be caused by the stock ROM, so I have flashed the "InsertCoin" ROM, but no changes.
Has someone the same problem, or does someone has a solution for me?
regards.
The clock speed is dynamically controlled. When the phone is not in use, it should reduce the clock speed.
It sounds like you have an app that is preventing it from sleeping.
Install betterbatterystats and look for partial wakelocks. Feel free to leave a screenshot here.
Hi,
even if there is an app which would prevent my phone from clocking down, the MIN-value should be at 300/400mhz, and not be the same as the max-value ..
regards.
No idea..?
what hes saying is theres a rogue app mostly likely in the background thats pushing your phone that it thinks it should ramp up the speed of your phone. so even if you have it set to 384/1.7 the phone is detecting "oh **** *so and so* app is beastly bump the speed to max 1.7. bad analogy but you get the idea. i would start by wiping the phone install a brand new rom and DONT install anything just the mhz reader. then check. if your on a fully clean flash and still holding at max value all the time. then next is to check the CPU governor. it may have been set to performance at some point "accidentally" the performance governor forces the phone to hold at max speed. mostly only used for synthetic benchmarks.
Nope nope nope.
Nope.
I just had to S-Off my phone ..

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

Q&A for [KERNEL][D5803&D5833] AndroPlusKernel
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][D5803&D5833] AndroPlusKernel. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
Very nice kernel, fast and smooth - great work and port.
Anyone knows if it's possible to use any third party kernel app to boost the headset volume?
Working
Hi this is my first post, infact I joined so I could report my findings.
I would just like to confirm so far that V5 working on my Z3C using the .93 firmware. I didn't need to wipe cache/dalvik/data partitions either.
For purposes of settings configuration, I'll be using TricksterMod
For stress testing purposes I'll be using Stability Test 2.7
Overclocking
Overclocking seems to work, I'll stress test and report back with the results.
I was wrong, it is unstable when overclocking and stress testing, with the phone force rebooting 1-5 seconds in to the stability test which loaded all 4 cores. Tried 2899Mhz and 2880Mhz (were both unstable and didn't try 2.72, 2.75, 2.57 either - I might try stability testing them.) Was completely stable at 2.47GHz, and it actually stuck there, no throttling in place! I stopped the stress test when the CPU temp was around 77-80C as my hand was getting burnt! The battery temp reached about 46C. It took 10 mins of stress testing for this to be reached. When the stock kernel was in place it would begin throttling after about 1-20 seconds under full load. First 2.2GHz, then 2 then 1.7 then 1.5 and eventually 1.25 after about 2-4mins.
I couldn't do a single core test though. I suspect as most games use single core or dual cores it wouldn't get overly hot.
My opinion is that fast clocked phones should be marketed with 2 speeds. The highest it'll reach under a boost mode (turbo for Intel's i5 and i7 series), and a slower speed that it'll average out at under thermal pressure. The Z3Cs would be turbo: 2.5GHz and normal: 1.5GHz.
Governors
These are quick tests I'm performing here to provide a quick look at responsiveness and potential unnecessary CPU jump ups.
Wheatley - most of the time it's hovering at top speed when approx CPU usage is 9%, it'll occasionally hunt down to 300Mhz but then right back up to 2899MHz. This one is speedy though. Governor tunables available.
Lagfree - idles at 300MHz - 960MHz then hunts up to 2.2-2.9Ghz when needed and turns on the second core. It seems to slow back down to idle. This one seems to have fast scrolling, sliding notifications pane quickly). No governor tunables.
SmartassV2 - idles at 300Mhz, speeds up to 422-960 on core 0, and turns on core 1 at 1.2-1.5GHz for a few seconds under fast scrolling and notification pane opening. Seems quite responsive. Probably good for battery life hopefully with the responsiveness of Interactive. No governor tunables.
Lionheart - Idles at 960 MHz for a few seconds then slows down to 300MHz with the odd increase to 729MHz. Core 0 and Core 1 reaches 1.26GHz under scrolling, notification pane opening. As fast as the others. Governor tunables available.
Hotplugging
Intelliplug appears to work better than MP-Decision - now only one core is on during idle, instead of 2.
MP-Decision was disabled to avoid conflicts.
Undervolting
I've only undervolted 300MHz to 675MHz from 775MHz as of writing this post.
Tried quickly undervolting in trickstermod by setting them all about -75mV, stability tested it, appears stable. I'll tweak the voltages a bit better when I do a scaling stability test.
Issues I've experienced
Sound Control is the only thing so far that causes a reboot. However music still plays over the speakers and headphones. Equaliser works too.
Upon rebooting, the CPU top speed will set itself to 2.2GHz, despite being set higher and saved at a higher speed in Trickstermod. Certainly trivial though.
Strange thing I've noticed: On the undervolt part I've noticed that there is a freq called 3033MHz, but no 2899MHz freq. Just an observation.
Misc
Force Fast Charge confirmed working! Before flashing new kernel charge went up 5% in about half an hour. It's now up another 5% in a matter of 5-10mins. This is when plugged to my PC.
Vibrator strength - set to 20 from 31, much quieter on table and can still feel it.
I'd like to say a huge thank you to DooMLoRD and AndroPlus for developing this stable kernel. Now my Z3C is worth the £28 a month I'm paying for again. Since this silly lad decided to bork the camera, Bravia functionality etc by rooting it on the first day. I'll report back and edit the post with my findings.
Max won't go beyond 2.266 GHz, Min won't change.
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
pjmanalo said:
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
Click to expand...
Click to collapse
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
DBCJoey said:
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
Click to expand...
Click to collapse
Thanks! That did the trick!
Odd that my usual app for the job across 4 other phones - SetCPU - doesn't work on what should essentially be the same job. [emoji55]
Please make sound_control drivers work so its possible to boost headphone volume on the Xperia Z3 Compact... Thanks
Nice work, a lot of updates I like it!
Is it possible to add a change log?
Thanks!
kernel for d5803 with the .93 but not .105
i search a kernel for the d5803 with the last .93 french version of phone
.5.77
Works great! Thanks a lot
Link for Z3C_D5803_AndroPlusKernel_v10.zip is dead
Pls upload in another location.
Yay sound control is working, thank you so much you're the best!
How to make this?
Hi AndroPlus,
I'm trying to figure out how one would go about building this boot.img that you've created.
What platform and compiler are you using?
Where are you getting sources the for the kernel? This file?
c9af6fc647060fb85dd646798453ec8f 23.0.A.2.105.tar.bz2
How do you construct boot.img from zImage + recovery?
Sorry if these are dumb questions.
Edit: never mind, I figured this out.
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/ contains most of the information I needed.
The arm version of gcc that ships with Ubuntu 14.04 worked fine - arm-none-eabi-gcc (4.8.2-14ubuntu1+6) - no need to track down any mystery binaries. I did have to make several modifications to the kernel source to get it to build. Interestingly, some of the cpufreq stuff contained code that was incorrect. Someone at Samsung needs to go look up what "sequence point" means.
The hardest part was figuring out how to turn the zImage + ramdisk into something I could boot.
This: https://github.com/sonyxperiadev/mkqcdtbootimg was the correct tool to use - again, no need to track down any mystery mkbootimg or dtbTool binaries.
Hope this is helpful to someone. As someone new to Xperia dev, I found most of the information out there worse than useless.

Categories

Resources