[V][Optimise]Knutselmaasters tips&tricks collection - Sony Xperia T, TL, TX, V

Hello all.
After several requests I finally decided to make this topic.
I'm not a developer, not even a phone specialist, but just a general technician that loves to tweak to get the best out of all things I get my hands on.
I have my V since about 20 months and I've tried all sorts of roms, mods, settings and apps.
Please share your experiences here, and if you use the things proposed here, post some feedback to give something back to this community in return.
Also l politely ask people that have more knowledge than me, to correct me if I'm wrong and to help me add precisions.
I devided the information over the following posts.
The second post talks about apps, the third post is all about kernel settings, the fourth post is about android settings.
I reserved some posts underneath for possible expansions.
Of course I don't take any responsibility for what happens to your phone after using any of the tips below if it makes you unhappy, and I take all credit if you do like it..... :angel:

Applications
These apps will do good to almost every rom.
I don't add general apps to prevent needless discussions, only apps that solve problems or raise the phone's quality.
Please tell if you know apps that you think are better, or that should also be listed here, and tell us why.
*************************************************************************************/
SoundAbout
If you have a non-Sony headphone there is a big chance that you have troubles getting them to work.
SoundAbout can force output to the headphone if the phone doesn't recognise it automatically, amongst a lot of other sound output related options.
*************************************************************************************/
Viper4android
Gives your phone an enormous boost in sound quality.
It can also force the sound enhancements for headphone to work on the loudspeaker and to headphones that are enabled with the abovementioned SoundAbout app.
*************************************************************************************/
Faster GPS
Lets you set the GPS server to your locality, giving a big speed up and better precision.
Also it lets you force A-GPS and much more.
*************************************************************************************/
Greenify
Get better battery life by stopping needless background processes.
*************************************************************************************/
Seeder
Makes the dalvik runtime work much smoother when multitasking and in demanding apps.
*************************************************************************************/
Xposed framework
Can change almost every single aspect of the phone with seperate dowloadable modules.
A must have if you're on dalvik.
*************************************************************************************/

Kernel Settings
Scheduler
The scheduler settings can have quite some impact on the system.
I've tested all of the commonly available and as a general find I can say that for all of them, the cache size gives the best results around 1mb (1024kb).
Furthermore, choosing the cfq scheduler helps enormously to stop the annoying sound glitches that I've witnessed on all of the newest roms during audio playback.
*************************************************************************************/
Governor
To keep things simple, the Ondemand and Interactive governors both have their advantages and inconveniences, but these are certainly the two that have the best compromise between performance and battery life.
There are a lot of governor parameters we can change, with the right app.
Because of the availability of a special setting regarding the sound bug, I have been forced to use ondemand, even if I would prefer using the interactive because it gives me a smoother system and better battery life.
The scheduler setting seems very related to the sound bug, system smoothness and lags, so I looked for other possible IO related settings that might be helpful.
The ondemand governor has a setting called io_is_busy (true or false)
I googled what that does, and found out that it is preventing the CPU to clock down if the system is waiting for IO operations when set to 1 (true)
This setting does miracles for me, I get a lot more responsive system and it helps a lot for the sound bug.
I tried it with deadline scheduler (fastest for me) and it almost solves the sound bug, but with CFQ it works best.
The default setting is 0 (false).
It does have a small negative impact on battery because it keeps clocks high now and then, but it certainly isn't a lot.
I was forced to use Ondemand governor now, so I read about it and tried some settings to make it behave more like the interactive governor which gave me a better battery life and smoother system.
The ones that are quite effective are:
Powersave_bias it sets a percentage of "effort" the system does to use lower clocks.
It is quite effective on battery stamina and the phone isn't really loosing a lot of "bite" or responsiveness when the setting remains around or under 10% (set to 100 for 10%, as it is a 0 to 1000 scale)
The default setting is 0 (disabled) so basically just a low percentage will activate the function and be unnoticeable.
I've set mine to 36.
Up-threshold is the percentage of charge on the core before it goes up one notch in clockspeed.
Default is 90.
This setting helps a lot to get the processor go up in speed gradually, and remain in 80% region clockspeeds when more isn't needed.
Above 93 it becomes noticeable, but in a pleasant way as the UI doesn't spike from very slow to full speed, but it ramps up gradually.
It is good for battery and pleasant to the eye.
I have set mine to 95.
Sampling_down_factor is the number of clock cycles the core remains at the same clockspeed when there is no more demand, before clocking down.
Default is 4.
I have searched all over the net but haven't found any reason why this is set to 4 clocks.
I set this to 1 and got better battery and less heat without noticing any difference what soever besides that.
I'm really happy with these settings, and I haven't had any problems playing around with them, no fc no bugs.
Just remember to change 1 parameter at the time and test it , and change with very small steps!
*************************************************************************************/
Voltages
After the screen brightness, changing the voltages has the biggest impact on battery life.
It can also influence system performance, because with the extra heat generated by using too high voltages the thermal throttling will lower clockspeeds sooner and more often.
Attention! Raising voltages (too much) may permanently damage your phone!
Attention! Lowering voltages can only make your phone crash and restart without harm, BUT be sure to test voltage settings before making them automatically applied on boot to prevent that the system gets too unstable to change back the setting.
You would need to reflash to get it at the default setting.
Attention! There are three different versions of processor on our phones, each has a different voltage table.
Be sure to use the right one, that corresponds to your phone !
You can check what version you've got by comparing your default voltages with the table below.
Default Voltages as used in all roms including stock, except some specific @WhiteNeo kernels.
These voltages don't allow any overclocking and cause heat problems when playing games in the sun etc.
"Slow Processor"
384mhz -=- 950mV
432mhz -=- 975mV
486mhz -=- 975mV
540mhz -=- 1000mV
594mhz -=- 1000mV
648mhz -=- 1025mV
702mhz -=- 1025mV
756mhz -=- 1075mV
810mhz -=- 1075mV
864mhz -=- 1100mV
918mhz -=- 1100mV
972mhz -=- 1125mV
1026mhz -=- 1125mV
1080mhz -=- 1175mV
1134mhz -=- 1175mV
1188mhz -=- 1200mV
1242mhz -=- 1200mV
1296mhz -=- 1225mV
1350mhz -=- 1225mV
1404mhz -=- 1237,5mV
1458mhz -=- 1237,5mV
1512mhz -=- 1250mV
"Nominal Processor"
384mhz -=- 900mV
432mhz -=- 925mV
486mhz -=- 925mV
540mhz -=- 950mV
594mhz -=- 950mV
648mhz -=- 975mV
702mhz -=- 975mV
756mhz -=- 1025mV
810mhz -=- 1025mV
864mhz -=- 1050mV
918mhz -=- 1050mV
972mhz -=- 1075mV
1026mhz -=- 1075mV
1080mhz -=- 1125mV
1134mhz -=- 1125mV
1188mhz -=- 1150mV
1242mhz -=- 1150mV
1296mhz -=- 1175mV
1350mhz -=- 1175mV
1404mhz -=- 1187,5mV
1458mhz -=- 1187,5mV
1512mhz -=- 1200mV
"Fast Processor"
384mhz -=- 850mV
432mhz -=- 875mV
486mhz -=- 875mV
540mhz -=- 900mV
594mhz -=- 900mV
648mhz -=- 925mV
702mhz -=- 925mV
756mhz -=- 975mV
810mhz -=- 975mV
864mhz -=- 1000mV
918mhz -=- 1000mV
972mhz -=- 1025mV
1026mhz -=- 1025mV
1080mhz -=- 1075mV
1134mhz -=- 1075mV
1188mhz -=- 1100mV
1242mhz -=- 1100mV
1296mhz -=- 1125mV
1350mhz -=- 1125mV
1404mhz -=- 1137,5mV
1458mhz -=- 1137,5mV
1512mhz -=- 1150mV
@WhiteNeo Voltages are lower than the stock values and give very good results.
As his kernels also support overclocking, i will add the voltages for 1620mhz too.
Some reports of phones rebooting at sleep with these voltages are reported and can normally be solved by raising the voltages on the lowest clockspeed(s) a bit. Never go higher than the stock values!
These voltages let me run the second core overclocked without any problems, but if I overclock the first core or both, my phone gets too hot.
"Slow Processor"
384mhz -=- 950mV
486mhz -=- 975mV
594mhz -=- 1000mV
702mhz -=- 1025mV
810mhz -=- 1050mV
918mhz -=- 1075mV
1026mhz -=- 1100mV
1134mhz -=- 1125mV
1242mhz -=- 1150mV
1350mhz -=- 1175mV
1458mhz -=- 1200mV
1512mhz -=- 1225mV
1620mhz -=- 1250mV
"Nominal Processor"
384mhz -=- 900mV
486mhz -=- 925mV
594mhz -=- 950mV
702mhz -=- 975mV
810mhz -=- 1000mV
918mhz -=- 1025mV
1026mhz -=- 1050mV
1134mhz -=- 1075mV
1242mhz -=- 1100mV
1350mhz -=- 1125mV
1458mhz -=- 1150mV
1512mhz -=- 1175mV
1620mhz -=- 1200mV
"Fast Processor"
384mhz -=- 850mV
486mhz -=- 875mV
594mhz -=- 900mV
702mhz -=- 925mV
810mhz -=- 950mV
918mhz -=- 975mV
1026mhz -=- 1000mV
1134mhz -=- 1025mV
1242mhz -=- 1050mV
1350mhz -=- 1075mV
1458mhz -=- 1100mV
1512mhz -=- 1125mV
1620mhz -=- 1150mV
@Knutselmaaster Voltages
I've spent a lot of time testing downvolting.
The following settings have been tested on my phone only, quite thoroughly, and should run good on every LT25i.
My phone is the "Nominal" version, and i translated values for the other versions by using the same logic as in the stock and @WhiteNeo ones.
Please give me feedback so that i can validate my results.
These voltages let me run both cores overclocked without any problem
"Slow Processor"
384mhz -=- 912.5mV
486mhz -=- 937.5mV
594mhz -=- 962.5mV
702mhz -=- 975mV
810mhz -=- 1025mV
918mhz -=- 1025mV
1026mhz -=- 1050mV
1134mhz -=- 1062.5mV
1242mhz -=- 1087.5mV
1350mhz -=- 1112.5mV
1458mhz -=- 1137.5mV
1512mhz -=- 1162.5mV
1620mhz -=- 1187.5mV
"Nominal Processor"
384mhz -=- 862.5mV
486mhz -=- 887.5mV
594mhz -=- 912.5mV
702mhz -=- 925mV
810mhz -=- 975mV
918mhz -=- 975mV
1026mhz -=- 1000mV
1134mhz -=- 1012.5mV
1242mhz -=- 1037.5mV
1350mhz -=- 1062.5mV
1458mhz -=- 1087.5mV
1512mhz -=- 1112.5mV
1620mhz -=- 1137.5mV
"Fast Processor"
384mhz -=- 812.5mV
486mhz -=- 837.5mV
594mhz -=- 862.5mV
702mhz -=- 875mV
810mhz -=- 925mV
918mhz -=- 925mV
1026mhz -=- 950mV
1134mhz -=- 962.5mV
1242mhz -=- 987.5mV
1350mhz -=- 1012.5mV
1458mhz -=- 1037.5mV
1512mhz -=- 1062.5mV
1620mhz -=- 1087.5mV
If the voltages are too low, the phone will tell you.
If the phone crashes in sleep, the voltages on low speeds are too low.
If the phone freezes in demanding apps like games, the voltages on the high speeds are too low.
If the system seems to freeze just shortly once in a while, the voltage in the mid-speeds is too low.
With some patience you can easily find the minimal voltages for your phone
*************************************************************************************/
Clockspeeds
Attention when overclocking, it generates exta heat that might damage your phone! Normally thermal protection will save you by lowering the maximum speed but there's no guarantees here!
Depending on a few factors, the V can be overclocked.
This can be done with only a few kernels and you need some luck as each processor is different.
On my phone, I can only overclock when I set the lowest stable voltages possible and I think I would have to disable it in extreme situations like playing Ingress in the full summer sun with my external battery plugged in.
If you're one of the lucky ones that has the "fast" processor (see voltages) then it should even be better.
Note that I also altered my governor settings to make my phone go up in clockspeed less quickly (see Up-threshold)
What is more interesting is downclocking at screen off.
My findings are that it is possible to use only the lowest clockspeed, without any bugs.
Music playback works as good as with the screen on and open applications will continue as they should.
The only thing is that it takes a bit more time for the phone to properly wake up when you unlock the phone.
That is why I set mine to max 486mhz, it is not much more but it totally solves the slowdown.
I think it is because using one single speed for min and max disables some process that regulates the acceleration or something like that....
Downclocking at idle really extends battery life but of course only when you don't use your phone often.
*************************************************************************************/
Memory
1gb of ram is not much.
That is why the minfree settings are quite important.
To prevent memory filling too much (witch really makes the phone lag as crazy) the preset used needs to be at least aggressive and for better behaviour of open apps i advice to "de-agress" the first two values for foreground apps to the level of the light preset. (sorry, phone broke and i don't remember the exact values)
*************************************************************************************/

Android Settings
As options and settings differ on all roms, I won't precise how to reach these.
Some might be available on the rom you use, some won't.
Please share your setting that helps make performance, user experience or battery life better, and supply some feedback on the settings proposed here.
Automatic Display Brightness
Most new roms have this setting, where we can adjust the steps of the automatic brightness levels.
For some reason, this never corresponds to the sensor of my V.
Check it out by opening the settings popup, and keeping the sensor in a bright light.
The sensor on my phone measures a little bit over 9100 lux as maximum value.
The maximum brightness in the settings at default is 2000 lux.
This makes the auto setting unusable for battery stamina and your eyes.
If you adapt the settings to your personal taste, using the whole 0-9000 range, it is comfortable for the eyes and it gives an enormous boost in battery stamina.
I post my settings here, but i repeat that the best way is to take the time to adapt the settings to your personal taste.
Lower brightness is always better for the battery but you should at least be able to read what is on the screen in all circumstances.
The way I use to find the right settings is by finding primarily the two extremes, and set them.
So, into a total dark place and set the 0 lux and go in maximum sun for the brightest setting.
Note that to change the maximum setting, you need to alter the before-last setting, for instance if you want the maximum lux reading to be 9000, change the lux of the second brightest to 8999 lux, the last will automatically be 1 more, thus 9000 lux.
The min and max set, go to some intermediate places, with different light conditions and in each one set the setting so that you can still read comfortably.
The sensor value goes down in quite a non linear way so think about how to divide the steps.
These are my settings:
0 lux = 10
50 lux = 30
100 lux = 40
200 lux = 50
500 lux = 75
1001 lux = 100
8800 lux = 175
8950 lux = 220
9100+ lux = 255
(can someone confirm the default max lux value please)
*************************************************************************************/
Runtime
I use ART instead of Dalvik, and I'm really satisfied.
It means no xposed for the moment, but with the right rom you won't miss that
*************************************************************************************/
Notification LED
I found my notification LED to stop the charge indicator LED from working after changing ROM.
Each time I received a notification during charge, my charge led would not turn on again, untill I restarted my phone.
Reflashing the same and other roms did not help, very weird.
The solution I found was in the notification LED settings.
It was set to "custom", while there was no custom setting available.
Just setting the "custom" to any other setting solved the problem for me.
*************************************************************************************/

Hardware
Some hardware tips:
-Don't touch the black rubber seals of the ports with your fingers, the natural acid of your body deteriorates them much quicker.
-If you change the port covers, use a very small screwdriver (or a paperclip that you flattened with a hammer) and push it carefully in the hole where the lid is attached to guide it out, thus preventing the small hook to keep it in place.
-Don't take off the "Sony" labeled screen protection, it really makes the screen very sensible to cracks (*sic*)

There, I finally had some time to add stuff.
I received a brand new battery yesterday, so I will be able to give results that should correspond to a "new" phone.
I will add my famous voltages soon, in the kernel settings post, but I'm taking the time to search reliable info and test results.

Thanks for your thread, I also recommend to put thread link in your signature.
By the way, beside those apps I also use Seeder with all three options checked and light RNG service profile.
It has no effect on battery life but kills almost every lag when multitasking and also in some games.

I wanted to try seeder lately but apparently it doesn't work on ART.
I will add it to the list.
The voltages are underway, I'm trying to find a reliable way to benchmark different settings, battery wise.

Voltages added.
I'm letting my new battery settle for a while before benching the different voltages as it seems to get better at every charge for the moment.

Thank you for the time and effort of writing this thread..i wanted to ask you, whatever ROM i am on except stock based gives me SoD..no matter what i do i just cant get a day without a custom rom dying on me..i ordered a new battery and replaced it successfully but it still dies on me..Do you think it has something to do with the voltage from the battery? if so what do you suggest i should do??? i have the XPERIA T.

Well, I'm surely not an expert on the sleep of death matter and never had my hands on a T, but maybe I can help anyway.
Let's try
As I'm a technician, I'm used to find the source of problems by eliminating possibilities.
You say you've changed the battery and that hasn't solved the problem so changing it again shouldn't help.
Sleep of death logically happens when the phone is idle (doing nothing).
When the phone is idle, it runs at low clock speed.
You never have freezes or reboots when you're using the phone?
In that case I would try to get the phone run a little bit faster in idle state, just to see if it still happens.
Assuming there is a unlocked kernel available for the T, I would flash that, and use an app like system tuner to set minimum speed @ screen off one or two steps higher and see if it survives the night.
You could even set min and max speeds to the same to find the clockspeed(s) that are not stable.
Once you've found the unstable speed(s), you can
- Just keep the setting that disables that clock, but assuming it is the lowest clockspeed, your phone will use more battery in idle state.
or
- Raise the voltage with 1 step (12.5mV) for the clockspeeds that are instable amd see if it helps.
Attention be careful, don't raise too much! If it isn't better with 25mV more, then more volts are not likely to do better and raising too much will cause heat problems (on low clockspeeds it is quite safe as the voltages are much lower than at full speed)
I joined some screens of system tuner so that you can see what I mean with "settings for screen off", the first are my own actual settings and the second is what I would try on your phone (assuming that the T has the same clockspeeds as the V of course)

Knutselmaaster said:
Well, I'm surely not an expert on the sleep of death matter and never had my hands on a T, but maybe I can help anyway.
Let's try
As I'm a technician, I'm used to find the source of problems by eliminating possibilities.
You say you've changed the battery and that hasn't solved the problem so changing it again shouldn't help.
Sleep of death logically happens when the phone is idle (doing nothing).
When the phone is idle, it runs at low clock speed.
You never have freezes or reboots when you're using the phone?
In that case I would try to get the phone run a little bit faster in idle state, just to see if it still happens.
Assuming there is a unlocked kernel available for the T, I would flash that, and use an app like system tuner to set minimum speed @ screen off one or two steps higher and see if it survives the night.
You could even set min and max speeds to the same to find the clockspeed(s) that are not stable.
Once you've found the unstable speed(s), you can
- Just keep the setting that disables that clock, but assuming it is the lowest clockspeed, your phone will use more battery in idle state.
or
- Raise the voltage with 1 step (12.5mV) for the clockspeeds that are instable amd see if it helps.
Attention be careful, don't raise too much! If it isn't better with 25mV more, then more volts are not likely to do better and raising too much will cause heat problems (on low clockspeeds it is quite safe as the voltages are much lower than at full speed)
I joined some screens of system tuner so that you can see what I mean with "settings for screen off", the first are my own actual settings and the second is what I would try on your phone (assuming that the T has the same clockspeeds as the V of course)
Click to expand...
Click to collapse
Ok thank you very much!! i will begin my testing and let you know

Good luck!
Be patient and try one setting at a time
I've added some text on clockspeeds under the kernel section, more will come.

For automatic brightness I suggest Lux Lite app (or its full version). It has some more features than rom's brightness setting. And actually I used this app all the time just because I don't know how to set hightest lux value, but now I know it. Thank you!

Knutselmaaster said:
Good luck!
Be patient and try one setting at a time
I've added some text on clockspeeds under the kernel section, more will come.
Click to expand...
Click to collapse
Ok here is an update! i have been testing since we last spoke and all i did was set the lowest frequency of the cpu to one notch higher than the lowest available and also applied the settings you suggested..i flashed neowave..and where other times i would always see a SoD within a couple of hours or overnight...I have not seen one yet so im guessing (and hoping) that was the problem..thank you so much for your help!

That is great news!
I had a much worse experience, my screen has broken.
The phone is useless now, image is ok but it doesn't react to touch any more.
So i'm in doubt, get it repaired or get another phone.
And i just installed a new battery

Knutselmaaster said:
That is great news!
I had a much worse experience, my screen has broken.
The phone is useless now, image is ok but it doesn't react to touch any more.
So i'm in doubt, get it repaired or get another phone.
And i just installed a new battery
Click to expand...
Click to collapse
Sorry to hear that mate! to be honest if someone manages to port a working version of lollipop for the T then trust me i would not even consider changing it for anything, im sure a genius will make it work so in my opinion get it fixed because it will be worth it

I ordered a brand new Z2.
At €340 it has an unbeatable value/quality that I couldn't resist.
The repair costs for the V are almost the same as a new one, and if I buy a new phone anyway, it might as well be a bit better.
I hope that the info i posted so far can help others in the future.
I will take some time to "finalise" this topic and add all I know, if it isn't already there, but as y'all can understand, I won't add info after that.
With very mixed feelings I say goodbye to my beloved V and it's community.
Special thanks and goodbye to @Aria.A97, @Alx31TLse and @WhiteNeo

Knutselmaaster said:
I ordered a brand new Z2.
At €340 it has an unbeatable value/quality that I couldn't resist.
The repair costs for the V are almost the same as a new one, and if I buy a new phone anyway, it might as well be a bit better.
I hope that the info i posted so far can help others in the future.
I will take some time to "finalise" this topic and add all I know, if it isn't already there, but as y'all can understand, I won't add info after that.
With very mixed feelings I say goodbye to my beloved V and it's community.
Special thanks and goodbye to @Aria.A97, @Alx31TLse and @WhiteNeo
Click to expand...
Click to collapse
Sorry to hear that, thanks for every byte of info you shared You were one best owners of Xperia V.
I planned to get a Z3 or Z3 compact, but I decided to wait for next x64 generation of phones, something like Z4 or Galaxy S 6

Knutselmaaster said:
I ordered a brand new Z2.
At €340 it has an unbeatable value/quality that I couldn't resist.
The repair costs for the V are almost the same as a new one, and if I buy a new phone anyway, it might as well be a bit better.
I hope that the info i posted so far can help others in the future.
I will take some time to "finalise" this topic and add all I know, if it isn't already there, but as y'all can understand, I won't add info after that.
With very mixed feelings I say goodbye to my beloved V and it's community.
Special thanks and goodbye to @Aria.A97, @Alx31TLse and @WhiteNeo
Click to expand...
Click to collapse
Thanks for your support and everything. Hope to see you again in some device's forum one day.

Related

Tegra OC/UV Voltage

Hello, I'm tried, with the OC and UV of my terminal, I managed to get these results:
- 1200MHz 1025mV
- 1000MHz 925mV
- 900MHz 875mV
- 750MHz 800mV
- 650MHz 775mV
- 500MHz 725mV
- 300Mhz 675mV
My terminal is stable, tested after 500 sec of stress cpu, but also comes to 63° in the test, what is the maximum temperature stability for Tegra?
What do you think? I should remove the OC and just leave the UV?
Default Voltage and Clock:
- 1000MHz 1000mV
- 900MHz 950mV
- 750MHz 875mV
- 650MHz 850mV
- 500MHz 800mV
- 300Mhz 750mV
How do you undervolt the unit? Thanks.
ppsun said:
How do you undervolt the unit? Thanks.
Click to expand...
Click to collapse
With Pimp My CPU and EternityProject Kernel 1.4
Sent from my LG-P990 using Tapatalk

Tegra OC/UV Voltage

Hello, I'm tried, with the OC and UV of my terminal, I managed to get these results:
- 1200MHz 1025mV
- 1000MHz 925mV
- 900MHz 875mV
- 750MHz 800mV
- 650MHz 775mV
- 500MHz 725mV
- 300Mhz 675mV
My terminal is stable, tested after 500 sec of stress cpu, but also comes to 63° in the test, what is the maximum temperature stability for Tegra?
What do you think? what comes to your terminal?
Default Voltage and Clock:
- 1000MHz 1000mV
- 900MHz 950mV
- 750MHz 875mV
- 650MHz 850mV
- 500MHz 800mV
- 300Mhz 750mV
PS: I have already started a topic in general optimus 2x forum, but I think here is on the proper
Hell_97 said:
Hello, I'm tried, with the OC and UV of my terminal, I managed to get these results:
- 1200MHz 1025mV
- 1000MHz 925mV
- 900MHz 875mV
- 750MHz 800mV
- 650MHz 775mV
- 500MHz 725mV
- 300Mhz 675mV
My terminal is stable, tested after 500 sec of stress cpu, but also comes to 63° in the test, what is the maximum temperature stability for Tegra?
What do you think? what comes to your terminal?
Default Voltage and Clock:
- 1000MHz 1000mV
- 900MHz 950mV
- 750MHz 875mV
- 650MHz 850mV
- 500MHz 800mV
- 300Mhz 750mV
PS: I have already started a topic in general optimus 2x forum, but I think here is on the proper
Click to expand...
Click to collapse
I read somewhere the min. voltage is something like 750, so your uv at the low range has no effect.
Hi!
This is my stable config:
- 1200MHz 1050mV
- 1000MHz 975mV
- 900MHz 900mV
- 750MHz 800mV
- 650MHz 700mV
- 500MHz 600mV
- 300Mhz 500mV
kernel eternity 1.4
The chip in our beloved LG O2X cannot output voltages lower than 770 mV.. So assigning any UV-values below 770 mV is useless.
I myself am using Benee's VorkKernel:
1200 MHz - 1075 mV
1100 MHz - 1025 mV
1000 MHz - 925 mV
800 MHz - 825 mV
500 MHz - 775 mV
300 MHz - 770 mV
xgeneralex said:
Hi!
This is my stable config:
- 1200MHz 1050mV
- 1000MHz 975mV
- 900MHz 900mV
- 750MHz 800mV
- 650MHz 700mV
- 500MHz 600mV
- 300Mhz 500mV
kernel eternity 1.4
Click to expand...
Click to collapse
oh yeah!, you have inspired me, here's my new configuration:
- 1200MHz 1025mV
- 1000MHz 925mV
- 900MHz 875mV
- 750MHz 800mV
- 650MHz 700mV
- 500MHz 600mV
- 300Mhz 500mV
Stable after 1000 sec of stress test
wgspoelstra said:
The chip in our beloved LG O2X cannot output voltages lower than 770 mV.. So assigning any UV-values below 770 mV is useless.
I myself am using Benee's VorkKernel:
1200 MHz - 1075 mV
1100 MHz - 1025 mV
1000 MHz - 925 mV
800 MHz - 825 mV
500 MHz - 775 mV
300 MHz - 770 mV
Click to expand...
Click to collapse
oh, really?
lol
1400Mhz - 1100mv
1300MHz - 1050mv
1200Mhz - 1000mv
1100Mhz - 975mv
1000Mhz - 925mv
800Mhz - 825mv
500Mhz - 725mv
300Mhz - 675mv
stable
matinha said:
lol
1400mhz - 1100mv
1300mhz - 1050mv
1200mhz - 1000mv
1100mhz - 975mv
1000mhz - 925mv
800mhz - 825mv
500mhz - 725mv
300mhz - 675mv
stable:d
Click to expand...
Click to collapse
Great! you are lucky!
Hell_97 said:
Great! you are lucky!
Click to expand...
Click to collapse
1400Mhz stress test gives me 49º
matinha said:
1400Mhz stress test gives me 49º
Click to expand...
Click to collapse
Sorry but can you proof it?! Nearly all of us got more than 60°C with 1300MHz so I can't really believe it.
Hitchi said:
Sorry but can you proof it?! Nearly all of us got more than 60°C with 1300MHz so I can't really believe it.
Click to expand...
Click to collapse
you will believe
here is a video with my temps with 1400mhz : http://www.youtube.com/watch?v=H5zOYXK3CoE
the cpu temp started at 47ºC
Running max 1.2ghz on 1050Mv
Its stable and cpu temp is between 40 and 50 degrees.
Sent from my LG-P990 using XDA App
K.D.M. said:
Running max 1.2ghz on 1050Mv
Its stable and cpu temp is between 40 and 50 degrees.
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
try 1.2ghz at 1000mv
matinha said:
try 1.2ghz at 1000mv
Click to expand...
Click to collapse
Ive used your readings now. Lets see how it does
Sent from my LG-P990 using XDA App
Hell_97 said:
oh, really?
Click to expand...
Click to collapse
Yah, really. Source: http://www.android-hilfe.de/1328175-post4.html
Sent from my Optimus 2X using XDA Premium App
matinha said:
you will believe
here is a video with my temps with 1400mhz : http://www.youtube.com/watch?v=H5zOYXK3CoE
the cpu temp started at 47ºC
Click to expand...
Click to collapse
Weird 1.4ghz 80secs stressing max 53degrees
Pretty good
Sent from my LG-P990 using XDA App
matinha said:
try 1.2ghz at 1000mv
Click to expand...
Click to collapse
My phone crashes at this voltage, the maximum for me is 1200MHz 1025mV.
Hell_97 said:
My phone crashes at this voltage, the maximum for me is 1200MHz 1025mV.
Click to expand...
Click to collapse
Same here but 1100Mv @ 1.4ghz works good. Quadrent score of 4205
Sent from my LG-P990 using XDA App
55° max at 1400mhz 1100mv
Hi,
I'm not an Optimus 2x owner, but a Motorola Xoom owner.
Luckily I'm one of them with a tegra 2 running stable on 1700mhz.
Now I'm playing around to get a lower voltage profile. My first try was interesting successful running [email protected]
so here I'll post my voltage table while trying around(so do not try it):
below 760 mhz removed, because of the same voltage
Freq @ Voltage @ Temp @ MFLOPS
0760mhz @ 0800mv @ 35.2°C @ 047.100 = stress stable (1.5 min)
0816mhz @ 0825mv @ 35.2°C @ 053.342 = stress stable (1.5 min)
0912mhz @ 0825mv @ 35.0°C @ 057.743 = stress stable (1.5 min)
1000mhz @ 0850mv @ 36.1°C @ 065.375 = stress stable (1.5 min)
1200mhz @ 0975mv @ 37.1°C @ 075.500 = stress stable (1.5 min)
1400mhz @ 1075mv @ 37.1°C @ 089.006 = stress stable (1.5 min)
1504mhz @ 1125mv @ 37.0°C @ 093.912 = stress stable (10 min)
1600mhz @ 1225mv @ 37.6°C @ 098.062 = stress stable (10 min)
1700mhz @ 1275mv @ 00.0°C @ 102.750 = stress unstable
legend:
death = caused a reboot
linpack stable = linpack gets max 1 inconsistent in 5 runs
stress (un)stable = stress tested + temp check
For the stresstests I'm using StabilityTest.
it is interesting, that linpack gets the best results when the cpu is running at the lower voltage limit.
but the most stable settings are the default settings, there also 1700mhz are working in the stress test stable
Regards
Ralph

OC/UV settings

What are your OC/UV settings?
Thank's for the info!
Sent from my GT-P1000 using Tapatalk
Currently at:
Min: 100mhz
Max: 1200mhz
Cpu Govenor: Conservative
I/O: V(R)
Works great for me, no lags everything runs smoothly
I'm currently running:
Minimum: 100 Mhz
Maximum: 1300MHz
with the ondemand scheduler
and the sio I/O scheduler
All this is on Overcome Jupiter and I find it gives me enough power to keep things running smoothly but the battery is still great.
At the moment, I'm not Undervolting but I used to run it in a cascading scheme where at 1300 I would undervolt 125 and drop 25 each frequency step until at 800 MHz it was back at standard voltages. This improved my battery a bit but led to the occasional glitch etc.
Performance case:
Minimum: 200 Mhz (200 mhz -75mV, 400-1000mhz -50mV, 1200mhz -25mV, 1300-1500mV untouched)
Maximum: 1600MHz (overvolt +50mV)
ondemand\performance cpu governor
deadline I/O scheduler (looks pretty faster than sio)
Battery saving case:
Minimum: 100 Mhz (100-600mhz -75mV)
Maximum: 1000MHz (800-1000mhz -50mV)
with the powersave cpu governor
noop I/O scheduler
those settings are best as for me.
also if i need extreme speed i lock CPU @ 1600mhz or cut its scaling up to 1400-1600mhz (beacuse overheatings suck badly)
using modded Overcome 3.1.0
I used the performance settings above and so far so good. I'll post back if battery performance is any better.
Sent from my PC36100 using XDA App
5 days with moderate usage
Sent from Sprint Galaxy Tab
2.5 days with heavy heavy usage.
Sent from Sprint Galaxy Tab

[Q] cpu speed?

what are the best settings for
1)overclocking: which governer should i use and what should i set as min. and max. cpu frequency to overclock
SAFELY.
2)same for underclocking.
also suppose i wish to set cpu frequency at 700Mhz max. can i also set 700 as min.?or is there a problem with that?
spam bot said:
what are the best settings for
1)overclocking: which governer should i use and what should i set as min. and max. cpu frequency to overclock
SAFELY.
2)same for underclocking.
also suppose i wish to set cpu frequency at 700Mhz max. can i also set 700 as min.?or is there a problem with that?
Click to expand...
Click to collapse
1) max- 729mhz, min- 320mhz, smartassV2, sio.
2) max- 480mhz,min- 245mhz, ondemand, deadline.
No, you can't because mini's processor's default max is 600mhz and keeping (forcing) it to min. 701mhz will probably ruin your processor so stay away from high min. frequencies.... Happy OC....
Sent from my Galaxy mini using Tapatalk 2
ashu.bigsmoke said:
1) max- 729mhz, min- 320mhz, smartassV2, sio.
2) max- 480mhz,min- 245mhz, ondemand, deadline.
No, you can't because mini's processor's default max is 600mhz and keeping (forcing) it to min. 701mhz will probably ruin your processor so stay away from high min. frequencies.... Happy OC....
Sent from my Galaxy mini using Tapatalk 2
Click to expand...
Click to collapse
so basically my min freq should not go above 600mhz...?
min frequency should not go above 200mhz
if you will set min frequency as 700 your mobile may reboot
and you can't oc stock rom, you will need to have custom rom like emanon
If you OC a lot then the camera might not work also.
just check all the things before doing OC
Press the thanks button
Sent from my Nexus⁴

Best governor,sheduler etc

Hello guys..Now how we have a lot of new kernel, in yours opinion which is best setup for performance,battery in governor, sheduler ,min&max Cpu,Gpu etc for our MI3 ? For now I use interactive,noop ,min 300 MHz and max 1,2 MHz..Gpu max 462MHz.. And that's seems ok for me..and franco kernel by audahadi
Nightmare + tripndroid 1.2-1.5Ghz, gpu 330Mhz
pgqta said:
Nightmare + tripndroid 1.2-1.5Ghz, gpu 330Mhz
Click to expand...
Click to collapse
Min cpu frequency 1.2 Ghz?? Why?
are you into gaming?
This is my current setup on XenonHD with Stuxnet+ kernel
(with regard to stats posted HERE)
HEIS3NBERG said:
4 hours of SoT with 50% ? How did you do that ? I'm reaching the 4hours of SoT sometimes but with 0% of battery :crying:
What is the other saving stuff you talking plz ?
Click to expand...
Click to collapse
damnthomas said:
wt setting is best for batter besides cpu set to governor and uc uv skills by Dark Knight
Click to expand...
Click to collapse
(I'm going to go tab by tab in Kernel Adiutor)
CPU:
CPU Max Freq- 1497MHz
CPU Min Freq- 300MHz
CPU Governor- conservative
Multicore Power Saving- Aggressive
Sync Threshold- 1190Mhz
Input Boost Freq- 960MHz
CPU Voltage:
300MHz- 700mV
422MHz- 705mV
499MHz- 705mV
576MHz- 710mV
653MHz- 710mV
729MHz- 715mV
883MHz- 725mV
CPU Hotplug:
MPDecision- ON (Stuxnet has no other hotplugs yet, and disabling hotplugs allows you to manually control which cores are active by checking boxes in CPU tab. But I didn't want to permanently switch off some cores, as it would probably affect smoothness, so decided to let MPDecision take care of it)
That's about all the Power-saving changes I made. :good:
The Dork Knight Rises said:
This is my current setup on XenonHD with Stuxnet+ kernel
(with regard to stats posted HERE)
(I'm going to go tab by tab in Kernel Adiutor)
CPU:
CPU Max Freq- 1497MHz
CPU Min Freq- 300MHz
CPU Governor- conservative
Multicore Power Saving- Aggressive
Sync Threshold- 1190Mhz
Input Boost Freq- 960MHz
CPU Voltage:
300MHz- 700mV
422MHz- 705mV
499MHz- 705mV
576MHz- 710mV
653MHz- 710mV
729MHz- 715mV
883MHz- 725mV
CPU Hotplug:
MPDecision- ON (Stuxnet has no other hotplugs yet, and disabling hotplugs allows you to manually control which cores are active by checking boxes in CPU tab. But I didn't want to permanently switch off some cores, as it would probably affect smoothness, so decided to let MPDecision take care of it)
That's about all the Power-saving changes I made. :good:
Click to expand...
Click to collapse
Can you explain why have you set your Sync Threshold to 1190Mhz
shabtab said:
Can you explain why have you set your Sync Threshold to 1190Mhz
Click to expand...
Click to collapse
Actually I can't...cuz I have no idea!
If you read the original post I linked, my aim was to increase battery life, so I just reduced all clock speeds while maintaining the default order
MaxFreq>SyncThreshold>InputFreq>MinFreq
But it gave me awesome results (again, check the link in prev post) without causing any lags, and ppl were asking for my setup, so I shared it with you guys.
Hope it helps you too :good:
The Dork Knight Rises said:
This is my current setup on XenonHD with Stuxnet+ kernel
(with regard to stats posted HERE)
(I'm going to go tab by tab in Kernel Adiutor)
CPU:
CPU Max Freq- 1497MHz
CPU Min Freq- 300MHz
CPU Governor- conservative
Multicore Power Saving- Aggressive
Sync Threshold- 1190Mhz
Input Boost Freq- 960MHz
CPU Voltage:
300MHz- 700mV
422MHz- 705mV
499MHz- 705mV
576MHz- 710mV
653MHz- 710mV
729MHz- 715mV
883MHz- 725mV
CPU Hotplug:
MPDecision- ON (Stuxnet has no other hotplugs yet, and disabling hotplugs allows you to manually control which cores are active by checking boxes in CPU tab. But I didn't want to permanently switch off some cores, as it would probably affect smoothness, so decided to let MPDecision take care of it)
That's about all the Power-saving changes I made. :good:
Click to expand...
Click to collapse
Mine is quite same and with Stuxnet on RR ROM, 1 Hours SOT per 10%; quite impressive.
The Dork Knight Rises said:
Actually I can't...cuz I have no idea!
If you read the original post I linked, my aim was to increase battery life, so I just reduced all clock speeds while maintaining the default order
MaxFreq>SyncThreshold>InputFreq>MinFreq
But it gave me awesome results (again, check the link in prev post) without causing any lags, and ppl were asking for my setup, so I shared it with you guys.
Hope it helps you too :good:
Click to expand...
Click to collapse
okay let me explain then it used to increase the max cpu clock speed if needed, like if you've clocked your cpu at 1.5 and the cpu gets exhausted with 100% usage then the cpu will be increased to given SyncThreshold value for sometime to lower the pressure on cpu,, in simple words it should not be lower than the max cpu Freq. and preferably disabling it is a better option.. and btw your settings are just awesome phone is not over heating also and thanks.
shabtab said:
okay let me explain then it used to increase the max cpu clock speed if needed, like if you've clocked your cpu at 1.5 and the cpu gets exhausted with 100% usage then the cpu will be increased to given SyncThreshold value for sometime to lower the pressure on cpu,, in simple words it should not be lower than the max cpu Freq. and preferably disabling it is a better option.. and btw your settings are just awesome phone is not over heating also and thanks.
Click to expand...
Click to collapse
Ah that makes a lot of sense. Thanks.
EDIT: But then why was SyncThreshold less than Max by default?
EDIT2: Also, same thing's been done by this awesome guy @nicholaschum (Google searched 'CPU Sync Threshold' LOL):
http://forum.xda-developers.com/showpost.php?p=56974252&postcount=363
The Dork Knight Rises said:
Ah that makes a lot of sense. Thanks.
EDIT: But then why was SyncThreshold less than Max by default?
EDIT2: Also, same thing's been done by this awesome guy @nicholaschum (Google searched 'CPU Sync Threshold' LOL):
http://forum.xda-developers.com/showpost.php?p=56974252&postcount=363
Click to expand...
Click to collapse
I am also wondering why people are keeping it less than default it just makes no sense.
@Gnome You are a pro kernel dev, right? Can you please explain to us (noobs :laugh what is up with the SyncThreshold value and what exactly it does?
The Dork Knight Rises said:
This is my current setup on XenonHD with Stuxnet+ kernel
That's about all the Power-saving changes I made. :good:
Click to expand...
Click to collapse
Your guides are always that helpful. Hope to see more guides from you! Pressed the thanks button.
Which is the best kernel for you?
mipo007 said:
Which is the best kernel for you?
Click to expand...
Click to collapse
Kernel by Gnome :thumbup:
Sent from my MI 3W using XDA Free mobile app

Categories

Resources