Database Develop

Kernel Help, UV and Improve I/O performance

Ok, I'm working on building my own kernel. Now I got how to do the overclock and such, thats easy. What I want to know is what is going on with what Barak/Eugene does and what Team Whiskey does to the kernel to improve the I/O. Also wanting to know what JAC/Team Whiskey set their voltages to?

Good luck I have been trying to get voltage out of simbionix all night. For some reason, its like their kryptonite, no one wants to talk about it.
ECOTOX said:
Ok, I'm working on building my own kernel. Now I got how to do the overclock and such, thats easy. What I want to know is what is going on with what Barak/Eugene does and what Team Whiskey does to the kernel to improve the I/O. Also wanting to know what JAC/Team Whiskey set their voltages to?
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

PaiPiePia said:
Good luck I have been trying to get voltage out of simbionix all night. For some reason, its like their kryptonite, no one wants to talk about it.
Click to expand...
Click to collapse
Voltage table
{1200000, 1350, 1100, 0},
{800000, 1200, 1100, 1},
{400000, 1050, 1100, 2},
{200000, 900, 1100, 4},
{100000, 900, 1000, 5},
Its not kryptonite, just been busy

Viralblack said:
Voltage table
{1200000, 1350, 1100, 0},
{800000, 1200, 1100, 1},
{400000, 1050, 1100, 2},
{200000, 900, 1100, 4},
{100000, 900, 1000, 5},
Its not kryptonite, just been busy
Click to expand...
Click to collapse
Will you guys release a source for the kernel? I'd like to compile one for stock speeds to work with my phone as my CPU cannot stand an overclock.

Viralblack said:
Voltage table
{1200000, 1350, 1100, 0},
{800000, 1200, 1100, 1},
{400000, 1050, 1100, 2},
{200000, 900, 1100, 4},
{100000, 900, 1000, 5},
Its not kryptonite, just been busy
Click to expand...
Click to collapse
Wow, Thank you very much Viral!
Is this for Project Core? and what is the stock voltage table looks like?
Thanks again!

richan90 said:
Will you guys release a source for the kernel? I'd like to compile one for stock speeds to work with my phone as my CPU cannot stand an overclock.
Click to expand...
Click to collapse
Please, post it if you ever get to create that kernel. I bet many of us with the Vibrants that can't be OCed will appreciate it.

PaiPiePia said:
Wow, Thank you very much Viral!
Is this for Project Core? and what is the stock voltage table looks like?
Thanks again!
Click to expand...
Click to collapse
For the stock voltages it should be in the Samsung source. You should download it since your gonna need it. I cant remember them exactly but if you like I can post them.
And BTW thanks alot Viral =) that was alot of help

ECOTOX said:
For the stock voltages it should be in the Samsung source. You should download it since your gonna need it. I cant remember them exactly but if you like I can post them.
And BTW thanks alot Viral =) that was alot of help
Click to expand...
Click to collapse
Thanks! uh, I just wanted the voltage table for the Project Core because I want to see how much Team Whisky overvolted the CPU at 1.2 Ghz.
I looked at a captivate post and it stated that stock voltage for 1.0 Ghz is 1.275 v (?) so, Core has a good .075 voltage increase at the highest clock.
P.S. I can't figure out what the 3rd number column of that table indicates, if you know please enlighten me.

PaiPiePia said:
Thanks! uh, I just wanted the voltage table for the Project Core because I want to see how much Team Whisky overvolted the CPU at 1.2 Ghz.
I looked at a captivate post and it stated that stock voltage for 1.0 Ghz is 1.275 v (?) so, Core has a good .075 voltage increase at the highest clock.
P.S. I can't figure out what the 3rd number column of that table indicates, if you know please enlighten me.
Click to expand...
Click to collapse
honestly, not completely sure myself XD i wouldn't mess with it though, just change the first 2 and you should be fine

oh, and btw, does anyone know if the image file created in the /arch/arm/boot folder is the initramfs? or am I going to have to rip it from another zimage?

Viralblack said:
Voltage table
{1200000, 1350, 1100, 0},
{800000, 1200, 1100, 1},
{400000, 1050, 1100, 2},
{200000, 900, 1100, 4},
{100000, 900, 1000, 5},
Its not kryptonite, just been busy
Click to expand...
Click to collapse
you are pushing it above vdd_arm max voltage level. for those that care to read the spec, vdd_arm max is 1.31v. so overvolt at your own disgression

Viralblack said:
Voltage table
{1200000, 1350, 1100, 0},
{800000, 1200, 1100, 1},
{400000, 1050, 1100, 2},
{200000, 900, 1100, 4},
{100000, 900, 1000, 5},
Its not kryptonite, just been busy
Click to expand...
Click to collapse
you are pushing it above vdd_arm max voltage level. for those that care to read the spec, vdd_arm max is 1.31v.

raspdeep said:
you are pushing it above vdd_arm max voltage level. for those that care to read the spec, vdd_arm max is 1.31v.
Click to expand...
Click to collapse
Was just thinking the same thing
P.S.
Thanks again for everything!

Some how I'm thinking {1200000, 1350, 1100, 0} 1350! This is a abit of overcooking for me.
This is getting just a little to quick to compile " a new and improved kernel ". No ill meant but just thinking out loud..
Not trying to flame anything or anyone. I guess it all good.

Overclocking pros and cons???

I want to know wat r d pros and cons of overclocking..
As far as i know pros are better performance..
Con: reduced battery life..
Plzz add ur suggestions in d list..
And does overclocking processor reduce d lifespan of device?
Sent from my HTC Incredible S using XDA App

mandeep294 said:
I want to know wat r d pros and cons of overclocking..
As far as i know pros are better performance..
Con: reduced battery life..
Plzz add ur suggestions in d list..
And does overclocking processor reduce d lifespan of device?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Overclocking will reduce the lifetime of the CPU, but honestly I don't think that you'll really notice it.
If you lower the voltage you'll also get the same or even better battery time even though you overclock it.
If you overclock too much your phone will most likely start to freeze or just shut down.
Can't really think of any major things that might happen.
And pros; games will run more smoothly, you can have more applications running in the background without lag because of the CPU. If you're running out of RAM an overclocked CPU won't help you.
That's all I can think of right now, and hopefully I haven't mixed up anything
*edit*
http://www.tested.com/news/the-risks-and-rewards-of-overclocking-android-phones/444/
Maybe you should read that
*hopes that it doesn't say the exact opposit of what I just wrote here*

If you're undervolting, the processor shouldn't overheat therefore less battery loss and less chance of any damage.
You can overclock our phone processor ~300mhz without seeing any overheating or bad battery drain. I just wouldn't recommend over that for very long periods.

scoobysnacks said:
If you're undervolting, the processor shouldn't overheat therefore less battery loss and less chance of any damage.
You can overclock our phone processor ~300mhz without seeing any overheating or bad battery drain. I just wouldn't recommend over that for very long periods.
Click to expand...
Click to collapse
But, there might actually be some phones that will start freezing just by overclocking 300MHz too
Forgot to mention, in my previous post, that how far you can go with overclocking is really device specific, it can differ a lot from two different Incredible S. I remember from the community for my old phone that some people couldn't even overclock 100MHz. CPU's for phones aren't really made to be overclocked, so do it with caution.
And to find out how much you can overclock your CPU, in your phone, just take it easy and go like 50MHz/time and perform some sort of a stresstest of the CPU, when it start to freeze and/or turn off you've gone beyond the limit of what your CPU can take. And don't set the frequency to as close to the limit you can, set it like _MAX_ 50MHz from the limit, I'd go for at least 100MHz below the limit.
Hopefully someone appreciates this post, and if anyone want to point out something I've gotten wrong... please do.

Splux said:
But, there might actually be some phones that will start freezing just by overclocking 300MHz too
Forgot to mention, in my previous post, that how far you can go with overclocking is really device specific, it can differ a lot from two different Incredible S. I remember from the community for my old phone that some people couldn't even overclock 100MHz. CPU's for phones aren't really made to be overclocked, so do it with caution.
And to find out how much you can overclock your CPU, in your phone, just take it easy and go like 50MHz/time and perform some sort of a stresstest of the CPU, when it start to freeze and/or turn off you've gone beyond the limit of what your CPU can take. And don't set the frequency to as close to the limit you can, set it like _MAX_ 50MHz from the limit, I'd go for at least 100MHz below the limit.
Hopefully someone appreciates this post, and if anyone want to point out something I've gotten wrong... please do.
Click to expand...
Click to collapse
I'm going by this chips specific tolerance, fyi I'm an electronics engineer.
I strongly doubt anyone's phone would not be able to overclock at all.
You just have to watch the heat really. Overall, 200 to 300MHz is very safe.
This generation snapdragon has high tolerances.
I have gotten mine up to 2ghz.
Freezing generally won't occur until after about 1.6ghz, or if the undervolting is too severe.
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
Any chip can overclock, it is certain undervolt levels that cause most to freeze.

How about hot countries like Egypt ??? And pocket kept phones.
Would that fry the cpu ??? If overclocked I mean

josephedward said:
How about hot countries like Egypt ??? And pocket kept phones.
Would that fry the cpu ??? If overclocked I mean
Click to expand...
Click to collapse
There is thermal overload protection built, the phone resets when the CPU reaches the temperature threshold. So a moderate overclock should create no problems. If the phone is rebooting though you should think about scaling back.

Sorry for bumbing old thread
Biggest issue I've came across with overclocking are the voltages. Took me half a year to adjust CPU voltages even till this point where I can overclock 100mhz. Since not all devs share their acpu table, its impossible to know how severe the undervolting is in particular ROM.
Every CPU is different, and mine needed 100mV(?) higher voltages than the ARHD native voltages to even stay at 1152mhz without insta freeze :/
Sent from my HTC Incredible S using XDA

CPU overclocking does have pros and cons, and I think the cons tends to outweight the pro's but it all depends on the type of user each person is. The only pros means you save a few seconds doing something, or get a better benchmark score - for what reason? I will explain below.
Overclocking can give you that 0-40% more boost. This can show from our stock IncS @ 1.0GHz = 3000 antutu score, overclocked becomes 3600 or 4000. That is a benchmark score, it's just numbers and don't mean real world performance.
How about when you are gaming? This doesn't translate immediately that you will get like 50+% more speed, it's more like in a shooter game your FPS jumps from from 18FPS > ~22 FPS, with a 30% overclock. it's just a measly 3-5 FPS. Often times, this also comes with instability causing freezes, reboots, or a hot phone, and extreme battery drain.
Whether you can tell the difference or need that extra power is up to you and each person, but personally I find that it's a gamble to take that has little gains other than telling others "hey I got this benchmark score"! Good for them.
Now, underclocking is a different story. While in theory it shouldn't cause any problems to the CPU, the purpose is 99% of the time to prolong the battery. This is what voltage controls in kernels are all about.
inSaN1Ty_X said:
Sorry for bumbing old thread
Biggest issue I've came across with overclocking are the voltages. Took me half a year to adjust CPU voltages even till this point where I can overclock 100mhz. Since not all devs share their acpu table, its impossible to know how severe the undervolting is in particular ROM.
Every CPU is different, and mine needed 100mV(?) higher voltages than the ARHD native voltages to even stay at 1152mhz without insta freeze :/
Click to expand...
Click to collapse
The GPL requires whatever kernel that is distributed becomes open source. If you find a developer that doesn't share with you the kernel source they are using, you can complain about it. They are violating the policy that makes android/linux, the OS it is. Most developers tend to take someone else's kernel and bundle it in their rom, but the original creators of the kernel should usually have a source up.

kaijura said:
The GPL requires whatever kernel that is distributed becomes open source. If you find a developer that doesn't share with you the kernel source they are using, you can complain about it. They are violating the policy that makes android/linux, the OS it is. Most developers tend to take someone else's kernel and bundle it in their rom, but the original creators of the kernel should usually have a source up.
Click to expand...
Click to collapse
Meaning: DEVs usually just share a link to github. It's pretty frustrating for "newb" user to even find the kernel source code from there. Seen one ROM where MDJ actually posted the acpu table and it was easy to see the voltages and adjust them to be alike with another ROM/(Kernel) that had trouble with O/C.
As for the Overcloking generally, I only find I usefull if kernel supports governor like smoothass, which really boosts the smoothness and I can truly see the difference.

inSaN1Ty_X said:
Meaning: DEVs usually just share a link to github. It's pretty frustrating for "newb" user to even find the kernel source code from there. Seen one ROM where MDJ actually posted the acpu table and it was easy to see the voltages and adjust them to be alike with another ROM/(Kernel) that had trouble with O/C.
Click to expand...
Click to collapse
well, just ask them where it is then. I'm sure most would tell you to look at that acpuclock source unless they were just not cool with you for some reason.

kaijura said:
well, just ask them where it is then. I'm sure most would tell you to look at that acpuclock source unless they were just not cool with you for some reason.
Click to expand...
Click to collapse
I see. Well for starters, could you provide something like guidence where to find IceColdSandwitch's acpu table? I Would be really really happy.
Sent from my HTC Incredible S using XDA

inSaN1Ty_X said:
I see. Well for starters, could you provide something like guidence where to find IceColdSandwitch's acpu table? I Would be really really happy.
Click to expand...
Click to collapse
You know you can also find a kernels' cpu VDD table using any app that lets you look at SVS values right?? It automatically pulls it for you.
This would probably be better asked in the IceColdSandwich thread as this topic is irrelevant to it since it means to cover all kernels, but here you go anyway:
Code:
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 24576, SRC_LPXO, 0, 0, 30720, 900, VDD_RAW(900) },
{ 61440, PLL_3, 5, 11, 61440, 900, VDD_RAW(900) },
{ 122880, PLL_3, 5, 5, 61440, 900, VDD_RAW(900) },
{ 184320, PLL_3, 5, 4, 61440, 900, VDD_RAW(900) },
{ MAX_AXI_KHZ, SRC_AXI, 1, 0, 61440000, 900, VDD_RAW(900) },
{ 192000, PLL_3, 5, 2, 122500, 900, VDD_RAW(900) },
{ 268800, PLL_3, 5, 1, 192000, 900, VDD_RAW(900) },
{ 345600, PLL_3, 5, 1, 192000, 925, VDD_RAW(925) },
{ 422400, PLL_1, 2, 0, 192000, 950, VDD_RAW(950) },
{ 499200, PLL_3, 5, 1, 192000, 950, VDD_RAW(950) },
{ 576000, PLL_3, 5, 1, 192000, 975, VDD_RAW(975) },
{ 652800, PLL_2, 3, 0, 192000, 1000, VDD_RAW(1000) },
{ 729600, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 806400, PLL_2, 3, 0, 192000, 1050, VDD_RAW(1050) },
{ 883200, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
{ 960000, PLL_2, 3, 0, 192000, 1100, VDD_RAW(1100) },
{ 1036800, PLL_2, 3, 0, 192000, 1150, VDD_RAW(1150) },
{ 1113600, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1190400, PLL_2, 3, 0, 192000, 1200, VDD_RAW(1200) },
{ 1267200, PLL_2, 3, 0, 192000, 1225, VDD_RAW(1225) },
{ 1344000, PLL_2, 3, 0, 192000, 1225, VDD_RAW(1225) },
{ 1420800, PLL_2, 3, 0, 192000, 1250, VDD_RAW(1250) },
{ 1497600, PLL_2, 3, 0, 192000, 1300, VDD_RAW(1300) },
{ 1574400, PLL_2, 3, 0, 192000, 1350, VDD_RAW(1350) },
{ 1612800, PLL_2, 3, 0, 192000, 1400, VDD_RAW(1400) },
{ 1728000, PLL_2, 3, 0, 192000, 1425, VDD_RAW(1425) },
{ 1804800, PLL_2, 3, 0, 192000, 1450, VDD_RAW(1450) },
{ 1881600, PLL_2, 3, 0, 192000, 1450, VDD_RAW(1450) },
{ 1958400, PLL_2, 3, 0, 192000, 1500, VDD_RAW(1500) },
{ 2035200, PLL_2, 3, 0, 192000, 1500, VDD_RAW(1500) },
If you need the direct source, it is available on my github: here
Edit: OP: this post is not meant to derail your thread, I'll hope you are okay with it.

kaijura said:
You know you can also find a kernels' cpu VDD table using any app that lets you look at SVS values right?? It automatically pulls it for you.
This would probably be better asked in the IceColdSandwich thread as this topic is irrelevant to it since it means to cover all kernels, but here you go anyway:
If you need the direct source, it is available on my github: here
Click to expand...
Click to collapse
[Hopefully it's okey to modify quotes like this on XDA..]
Thank you so so so much ! Yes I know that apps like incredicontrol can show it, but don't want to flash all the possible ROMs and their versions just to find out that when it could be available this easy. Also I can compare values more easily this way, rather than from the screen of my INC S.
But still thanks again! Oh and yea draftted slighlty from OP's question, hope he doesn't mind

Very cool i liked omg

Overclocking a phone's CPU is really an hit or miss. In Benchmarks you'll most likely won't see any improvement. On the other hand, GPU overclock seems to be much MUCH more worth It. It brings real benchmarks and gaming improvements.

i'm an experienced overclocker and i'd say that the cpu won't reduce life if the temperature and voltage aren't too high: less than 60°c under 1.6 volts for silicon (combined of both) and CPU is not afraid of continuous work in spite of high frequency (10GHz, 100GHz), as said it only shortens its life when the temperature and voltage are too high. silicon can withstand up to more than 2 volts but 1.6 on average. and unstable cpu overclock the main cause must be the temperature and the components around it like Ram, Motherboard, not the CPU itself. example an intel e6500 cpu has a base clock of 2.93 GHz is overclocked to over 9GHz with excellent temperatures and voltages and fully stable.

Tegra thermal throttling - throtling tabels and stuff.

Hi guys,
I've read about tegra thermal throttling on google and searched files responsible for it. On our O4X they're located in /d/tegra_thermal/ and /d/tegra throttle.
Official jellybean hasn't solved any of gaming problems, there is still no multicore usage with both GTA's and FPSE. And since users report that games have run ok on older firmwares ( before LG introduced agressive thermal throttling) my idea is that someone can post these files from before 10d ( I think, any input from different firmwares welcome ! ) .
Then we will be able to figure best values for files from /tegra_thermal and layout of tegra_table from /tegra_throttle
Files from tegra_thermal
passive delay
Code:
2000
tc1
Code:
0
tc2
Code:
1
temp_shutdown
Code:
90000
temp_throttle
Code:
71000
temp_throttle_skin
Code:
43000
temp_tj
Code:
34250
Now from /tegra_throttle
tegra_table0
Code:
[0] = 1000000 0 0 0
[1] = 760000 0 0 0
[2] = 760000 0 0 0
[3] = 620000 0 0 0
[4] = 620000 0 0 0
[5] = 620000 437000 0 0
[6] = 620000 352000 0 0
[7] = 475000 352000 0 0
[8] = 475000 352000 0 0
[9] = 475000 352000 250000 375000
[10] = 475000 352000 250000 375000
[11] = 475000 247000 204000 375000
[12] = 475000 247000 204000 375000
[13] = 475000 247000 204000 375000
tegra_table1
Code:
[0] = 1000000 0 0 0
[1] = 760000 0 0 0
[2] = 760000 0 0 0
[3] = 620000 0 0 0
[4] = 620000 0 0 0
[5] = 620000 437000 0 0
[6] = 620000 352000 0 0
[7] = 475000 352000 0 0
[8] = 475000 352000 0 0
[9] = 475000 352000 250000 375000
[10] = 475000 352000 250000 375000
[11] = 475000 247000 204000 375000
[12] = 475000 247000 204000 375000
[13] = 475000 247000 204000 375000
These tables seem interesting, there are four tabs of values ( for each core maybe ? ) and values from 0 to 13 in []. If we compare it to tables from previous firmwares we could learn something about them.
I haven't found any Nvidia docs about tegra thermal throttling, so if anyone of you have, please post them

hi, maybe you can find some more info / tweaks in the thread i've done?
http://forum.xda-developers.com/showthread.php?t=2187017
and
http://forum.xda-developers.com/showthread.php?t=2193578&page=9

L2Deliver said:
hi, maybe you can find some more info / tweaks in the thread i've done?
http://forum.xda-developers.com/showthread.php?t=2187017
and
http://forum.xda-developers.com/showthread.php?t=2193578&page=9
Click to expand...
Click to collapse
I read this threads carefully, and one is even started by me BTW: Great work about disabling thermal protection !
But I started this thread mainly to COMPARE values from different firmwares , and figure the structure of tegra_table 0 and 1. I haven't found about them anything anywhere and they look very interesting.
Having more info will only provide more undestanding of tegra throttling mechanism, so we will be able to fine tune it according to user needs.

FunkyRasta said:
I read this threads carefully, and one is even started by me BTW: Great work about disabling thermal protection !
But I started this thread mainly to COMPARE values from different firmwares , and figure the structure of tegra_table 0 and 1. I haven't found about them anything anywhere and they look very interesting.
Having more info will only provide more undestanding of tegra throttling mechanism, so we will be able to fine tune it according to user needs.
Click to expand...
Click to collapse
:laugh:
i didn't realise you were the OP of the thread:crying:. yes the tables you mentioned are pretty interesting. maybe we can get some insights from HOX since they uses tegra 3 too.
btw, Microsoft Surface has Tegra 3 chip also.

You guys are insane, really. First of all, we have to know maximum temperature on Tegra 3 in O4X. Then developers can do something and just watch. Maybe LG did thermal protection because off bad internal design. We must be careful, especially with our hands.

Don't worry Winudert, our phones won't explode in our hands. As far as we leave temp_shutdown intact nothing gonna happen. There's no maximum temperature, every SoC is different , but with default value in temp_shutdown, as I said there's nothing to worry about.
Devs are busy making other tasks like kernels and ROMs. You don't have to be a dev to edit some files, which is pretty straightforward. I won't sit still if I can do something usefull !
On topic: Waiting for someone to share their files, especially form v20B or v10D/v10H
EDIT: Downloading 1300 pages of tegra 3 technical manual, if I find something usefull , I'll post it here.
EDIT2: Manual is low-level, usefull to asm programmers and kernel developers, no word about linux on tegra , so obviously no explaination of it's config files. Our only hope is to compare files across different firmwares, so please upload.

FunkyRasta said:
Don't worry Winudert, our phones won't explode in our hands. As far as we leave temp_shutdown intact nothing gonna happen. There's no maximum temperature, every SoC is different , but with default value in temp_shutdown, as I said there's nothing to worry about.
Devs are busy making other tasks like kernels and ROMs. You don't have to be a dev to edit some files, which is pretty straightforward. I won't sit still if I can do something usefull !
On topic: Waiting for someone to share their files, especially form v20B or v10D/v10H
EDIT: Downloading 1300 pages of tegra 3 technical manual, if I find something usefull , I'll post it here.
Click to expand...
Click to collapse
But my O4X is kinda hot after 10 minutes playing Real Racing 3 at Medium settings (official V20A) with a little lag when I see more than three cars at one time. It's really upsetting , because my Nexus 7 can handle this game at High, also HTC One X member says the same, so I'm just waiting for custom kernels and ROMs. I definitely will buy next Nexus 7 if he will be faster than Tegra 3 powered first gen version, but I will skip this years high-end smartphones and will buy one next year, so I will stick with O4X.

Winudert said:
But my O4X is kinda hot after 10 minutes playing Real Racing 3 at Medium settings (official V20A) with a little lag when I see more than three cars at one time. It's really upsetting , because my Nexus 7 can handle this game at High, also HTC One X member says the same, so I'm just waiting for custom kernels and ROMs. I definitely will buy next Nexus 7 if he will be faster than Tegra 3 powered first gen version, but I will skip this years high-end smartphones and will buy one next year, so I will stick with O4X.
Click to expand...
Click to collapse
It is normal that it's hot. If it will become dangerously hot i will turn off. ( no matter if we delete temp_shutdown , as I read tegra3 has built in hardware protection). So to enable our LG to use more cores we have to tune thermal protection. Everything is in tegra_tables. There are four tabs for each core, and lower the number, more cores are shutdown, that's my prediction. But i won't do anything until someone share their files.

Winudert said:
You guys are insane, really. First of all, we have to know maximum temperature on Tegra 3 in O4X. Then developers can do something and just watch. Maybe LG did thermal protection because off bad internal design. We must be careful, especially with our hands.
Click to expand...
Click to collapse
Temp never rises above 64-ish celcius
Said by one who have tested multiple times
Sent from my LG-P880 using xda app-developers app
---------- Post added at 02:53 PM ---------- Previous post was at 02:48 PM ----------
FunkyRasta said:
It is normal that it's hot. If it will become dangerously hot i will turn off. ( no matter if we delete temp_shutdown , as I read tegra3 has built in hardware protection). So to enable our LG to use more cores we have to tune thermal protection. Everything is in tegra_tables. There are four tabs for each core, and lower the number, more cores are shutdown, that's my prediction. But i won't do anything until someone share their files.
Click to expand...
Click to collapse
My files
Temp_throttle 66000
Same for tj, and throttle_skin
Temp shutdown is 90000 (lol?)
Sent from my LG-P880 using xda app-developers app

Even if we find out exactly what to edit for performance, we need to automate editing values at boot because they reset themselves. I have v10d if you guys want any values from me
Sent from my rooted P880

@non4 said:
Even if we find out exactly what to edit for performance, we need to automate editing values at boot because they reset themselves. I have v10d if you guys want any values from me
Sent from my rooted P880
Click to expand...
Click to collapse
Okay, someone could write script to do this, even I will if I have enough time Sure, post it man

alekthefirst said:
Temp never rises above 64-ish celcius
Said by one who have tested multiple times
Sent from my LG-P880 using xda app-developers app
---------- Post added at 02:53 PM ---------- Previous post was at 02:48 PM ----------
My files
Temp_throttle 66000
Same for tj, and throttle_skin
Temp shutdown is 90000 (lol?)
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
What firmware you're on ? Do you play games ? If yes, how's the experience ?

FunkyRasta said:
Okay, someone could write script to do this, even I will if I have enough time Sure, post it man
Click to expand...
Click to collapse
What the throttle table?
Sent from my rooted P880

@non4 said:
What the throttle table?
Sent from my rooted P880
Click to expand...
Click to collapse
YES, and other files I mentioned earlier if you can

FunkyRasta said:
YES, and other files I mentioned earlier if you can
Click to expand...
Click to collapse
Probs be tomorrow cos I'm working till midnight but I'll see what I can do
Sent from my rooted P880

Values from v10a:
Tegra Thermal
Shutdown_temp_tj: 129000
Temp_tj: 57500
Throttle_temp_tj: 80000
Click to expand...
Click to collapse
Interestingly thats it in v10a, no throttle table, not that I can find anyway . Gamings pretty smooth to, gta runs like it would on my pc, spidermans pretty playable, NFS is so much better (but not lag free). The drawback is bad battery
Sent from my rooted P880

@non4 said:
Values from v10a:
Tegra Thermal
Interestingly thats it in v10a, no throttle table, not that I can find anyway . Gamings pretty smooth to, gta runs like it would on my pc, spidermans pretty playable, NFS is so much better (but not lag free). The drawback is bad battery
Sent from my rooted P880
Click to expand...
Click to collapse
You sure you looked in right directories ( all beggining with tegra_ in /d/ ) ? If yes, there's probably no throttling at all in v10A
But reverse enginering current firmwares to behave like v10A is beyond my reach So we need throttle tables from v20B and firmwares newer than v10A. Thanks for input though, it is very valuable !

FunkyRasta said:
You sure you looked in right directories ( all beggining with tegra_ in /d/ ) ? If yes, there's probably no throttling at all in v10A
But reverse enginering current firmwares to behave like v10A is beyond my reach So we need throttle tables from v20B and firmwares newer than v10A. Thanks for input though, it is very valuable !
Click to expand...
Click to collapse
Yep, checked again there is nothing in there, probably why its so smooth but battery is crap
Sent from my rooted P880

So there's no thermal throttling implemented at all in v10A. Which firmware solved heat issues everyone was complaining about ? We need files from it , and one previous firmware to compare it, it would be the best.
Sorry for not posting anything new, but I don't have time today to try editing values ( school) maybe tommorrow I will edit them and check performance. Hopefully someone till tommoro will upload his files

does the apk nvcplsv.apk has anything to do?
what's confirmed is that its nvidia's gaming profiles afaik. maybe we can meddle with that too to find out something.
ICS system/bin without odex (with tweaks telling people to move it to system/apk to save battery)
JB system/app with odex

[DEV][WIP][KERNEL-PATCH][MSM7x30/8x55 GPU OVERCLOCKING][2d-core done][3d-core][v0.7]

Finally after someone pm'd me I looked back into GPU Overclocking.
New thread created issues with old thread OP permissions (people seem to be asking the same questions over and over again all information will be kept in OP & DO READ THE THREAD, repetitive questions will now be ignored)
Benefits:
Smoother UI
Handle 2d & 3d core GPU intensive applications & games
Currently only 2D core has been overclocked working on 3D core OC
2D-core original value - 192mhz OC to 245mhz DONE achieved 25% performance boost grp_2d_clk outputs 245760000hz
3D-core original value - 245mhz OC to 300+mhz WIP hoping to achieve 40-50% performance boost
2D-core OC only Download: Coming soon...
Download Links for other devices coming soon...
Works for all HTC Sense/Cm9/Cm10 kernels (Just ask a kernel developer for your device to implement the source code)
Note: Don't have internet on PC so providing 3 main files that need replaced for 2D-core OC to work
Download link to source code: http://d-h.st/wbH
3D-CORE OC TESTS Download: Coming soon...
Do check under sys/kernel/debug/htc_clock/clks/ look for file with all clocks & look for GRP_clks (Graphics clock)

OK so basically today I've been thinking and I've come to the conclusion that I will release the 2D-core OC patch As Soon As Possible, 3D-core Core OC is NOT Impossible but for now I'll give it a break, I will attempt 3D-core OC If/When I can get a hold of a msm7x30/msm8x55 device, as it will make it much easier for both me & users.
So for now you can enjoy the 50mhz increase/bump up, perf boost 25% in 2D-core (will increase performance in both 2D/3D intensive appications as 2D-core is used for 3D AFAIK and increase User Interface performance (Note: This will not take a hit on battery life)), I will also release a couple of fixes on patchas kernel that shouldnt be there/set etc.
(Theres a device available in my area for roughly £90, if anyone wants to contribute towards getting that device or can donate a device , more than welcome and shoot me a PM so I can list you here.)
(This isnt a promise of 3D-Overclock if you donate, if you donate please do so expecting nothing I will only attempt 3D-overclock)
Working device list - all kernel 3.0+ msm7x30/msm8x55 soc devices.
Main thread is in Desire HD Android Development section: http://forum.xda-developers.com/show....php?t=2368497

Sound really great, do you have the commits on github? More easy to follow , will test it for Runnymede. Great job
Sent from my Find 5 using XDA Premium HD app

anders3408 said:
Sound really great, do you have the commits on github? More easy to follow , will test it for Runnymede. Great job
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
I have github but dont reqlly use it much, only have net on laptop so cannot push commits

Shaky156 said:
I have github but dont reqlly use it much, only have net on laptop so cannot push commits
Click to expand...
Click to collapse
Ahh okay. Will take a look at your patch. Did you run some benchmark on it? And how is battery with GPU oc vs no GPU oc?
Sent from my Find 5 using XDA Premium HD app

anders3408 said:
Ahh okay. Will take a look at your patch. Did you run some benchmark on it? And how is battery with GPU oc vs no GPU oc?
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
Benchmark are not really something that should be taken too seriously but yes antutu reported in 20-25% increase in performance not always accurate but 2d core clk results in 245mhz, user from desire hd reported going from in range of 2x fps to 4x fps and that is without the 3d-core overclock (2d-core is used in 3d graphics afaik)

anders3408 said:
Ahh okay. Will take a look at your patch. Did you run some benchmark on it? And how is battery with GPU oc vs no GPU oc?
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
diff patch to make life easier
diff --git a/arch/arm/mach-msm/clock-7x30.c b/arch/arm/mach-msm/clock-7x30.c
index 8e97664..5e9bc2e 100644
--- a/arch/arm/mach-msm/clock-7x30.c
+++ b/arch/arm/mach-msm/clock-7x30.c
@@ -2992,8 +2992,8 @@ static void __init msm7x30_clock_init(void)
clk_set_rate(&mdc_clk.c, 1);
/* Sync the LPA_CODEC clock to MI2S_CODEC_RX */
clk_set_rate(&lpa_codec_clk.c, 1);
- /* Sync the GRP2D clock to AXI */
- clk_set_rate(&grp_2d_clk.c, 1);
+ /* Set rate of 2D-core GPU Clock @245Mhz (OC of 53Mhz 25% perf boost by Shaky156) */
+ clk_set_rate(&grp_2d_clk.c, 245760000);
}
struct clock_init_data msm7x30_clock_init_data __initdata = {
diff --git a/arch/arm/mach-msm/devices-msm7x30.c b/arch/arm/mach-msm/devices-msm7x30.c
index d52db55..f428e57 100644
--- a/arch/arm/mach-msm/devices-msm7x30.c
+++ b/arch/arm/mach-msm/devices-msm7x30.c
@@ -1319,11 +1319,7 @@ struct resource kgsl_3d0_resources[] = {
static struct kgsl_device_platform_data kgsl_3d0_pdata = {
.pwrlevel = {
{
- .gpu_freq = 364800000,
- .bus_freq = 249600000,
- },
- {
- .gpu_freq = 245760000,
+ .gpu_freq = 245760000, /*Restore correct GPU frequency and bus frequency (Shaky156)*/
.bus_freq = 192000000,
},
{
@@ -1336,7 +1332,7 @@ static struct kgsl_device_platform_data kgsl_3d0_pdata = {
},
},
.init_level = 0,
- .num_levels = 4,
+ .num_levels = 3,
.set_grp_async = set_grp3d_async,
.idle_timeout = HZ/20,
.nap_allowed = true,
@@ -1372,14 +1368,13 @@ static struct resource kgsl_2d0_resources[] = {
static struct kgsl_device_platform_data kgsl_2d0_pdata = {
.pwrlevel = {
{
- .gpu_freq = 0,
+ .gpu_freq = 245760000, //Set 2D-core GPU Frequency @245mhz (Shaky156)
.bus_freq = 192000000,
},
},
.init_level = 0,
.num_levels = 1,
- /* HW workaround, run Z180 SYNC @ 192 MHZ */
- .set_grp_async = NULL,
+ .set_grp_async = set_grp2d_async, //Set the 2D-core Graphics Clock Asynchronous to the AXI clock (Shaky156)
.idle_timeout = HZ/10,
.nap_allowed = true,
.clk_map = KGSL_CLK_CORE | KGSL_CLK_IFACE,
diff --git a/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c b/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c
index e81b025..b8686c0 100644
--- a/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c
+++ b/drivers/gpu/msm_adreno205/kgsl_pwrctrl.c
@@ -488,10 +488,8 @@ int kgsl_pwrctrl_init(struct kgsl_device *device)
pwr->pwrlevels.io_fraction =
pdata->pwrlevel.io_fraction;
}
- /* Do not set_rate for targets in sync with AXI */
- if (pwr->pwrlevels[0].gpu_freq > 0)
- clk_set_rate(pwr->grp_clks[0], pwr->
- pwrlevels[pwr->num_pwrlevels - 1].gpu_freq);
+
+ /*Removed AXI Sync code (Shaky156)*/
pwr->gpu_reg = regulator_get(NULL, pwr->regulator_name);
if (IS_ERR(pwr->gpu_reg))

For now its an empty oc, meaning it doesn't work
Sent from my Find 5 using XDA Premium HD app

anders3408 said:
For now its an empty oc, meaning it doesn't work
Sent from my Find 5 using XDA Premium HD app
Click to expand...
Click to collapse
I was in IRC before you came on, talked to synergy, I've changed the OC code, removed mistake and set GPU OC a different way, guess what? tested on my sisters phone again and benchmark was improved, not majorly but on 2 of the draw tests, consistant results of improvement by 5-8fps and rest were by 1-2fps, but like I said lets see where 3d-gpu OC takes me, as that will definitely show if OC is working
What you guys got and what I got was different in benchmarks, which is weird, I got imrovements, you got the opposite. So can't call it an empty OC lol

Shaky156 said:
I was in IRC before you came on, talked to synergy, I've changed the OC code, removed mistake and set GPU OC a different way, guess what? tested on my sisters phone again and benchmark was improved, not majorly but on 2 of the draw tests, consistant results of improvement by 5-8fps and rest were by 1-2fps, but like I said lets see where 3d-gpu OC takes me, as that will definitely show if OC is working
What you guys got and what I got was different in benchmarks, which is weird, I got imrovements, you got the opposite. So can't call it an empty OC lol
Click to expand...
Click to collapse
your improvements here : 0xbench is very small, and should be higher if it is oc'ed , but yes its a plausble

Okay after looking @ GPU Overclock for 2 weeks, This is the news on GPU OC for MSM8x55/MSM7x30 socs.
My findings...
2D-core OC from 192mhz to 245mhz successful.
3D-core OC will not happen without me obtaining the datasheet (which is proprietary)
The clocks are protected, via Ownership/Permissions, and maybe an RCU/MPU
No Overclocking the CPU does NOT Overclock the GPU, thats the worst thing I've heard in my life lol.
The lowest the GPU can hit is 192mhz or lpxo freq
Bus is not overclockable, it always is 192mhz
EBI_2D_clk will and has always been 0mhz
Modifying kgsl platform data and/or the graphics table with random values or even calculated values from correct pll freqs will NOT OC the gpu
it's ashame the GPU clocks are protected.
IF anyone is looking to continuing this project and is on the right track you're more than welcome to get in contact with me, especially if you have the msm7x30 datasheet.
The QSD8x50 soc is more open than this soc, so I'm doing a few tests on the HD2
Also it is overclocked, wasted my time testing, measured the gpu frequency and output to dmesg tells me it is correct, if it wasnt setting then the dmesg would ouput it failing to set the gpu frequency. just like it does for 3d-core oc

it was said before and ill say it again, the gpu clock is relative to the cpu clock, you cant overclock the gpu, their all part of the soc "system on chip", you can increase the bus bandwidth etc, which is already present in my kernel, but performance increase? not any atall

onejay09 said:
it was said before and ill say it again, the gpu clock is relative to the cpu clock, you cant overclock the gpu, their all part of the soc "system on chip", you can increase the bus bandwidth etc, which is already present in my kernel, but performance increase? not any atall
Click to expand...
Click to collapse
GPU clocks on msm7x30 devices is hardcoded.
Sent from my Find 5 using XDA Premium HD app

Hi plz anyone help me my battery work just 5 and 7 hour I have cm10 plz help me how can I install this and how can I got more battery plz hellp
Sent from my Sensation XL using xda premium

Nexus 5 Voltage How Low Can You Go.

When I start my day with my phone my ultimate goal is to get the most out of my battery. I have a Nexus 5 which is great phone but one downside is that the battery which is 2300mah can barely get you through the day. One way to help this issue is to under volt your CPU, the nexus 5 has a snapdragon 800 CPU clocked at 2.26GHz which is power CPU but at times it can run a bit hot and use more juice than it needs. By Under Volting your CPU your device will run much cooler without losing performance. (Warning if you go too low with the voltages your device will freeze and randomly reboot. ). The voltages than the nexus 5 ships with are a bit high I've been able to under volt up to -75mah without losing any performance however your experience may be different. To under-volt your device you need to have a rooted phone with a custom kernel installed. Franco, ElementalX, and Codeblue are few a few of the many kernels you can use with the nexus 5. I've been using ElementalX as my kernel for a while now, although Franco is also a good one. I use the ElementalX kernel app to manage my voltages, its a paid app but its definitely worth it. you could also use the Kernel tweaker app to manager voltages as well. I've set the governer to elementalx and i set the max cpu freq to 1574MHz, and the max screen off frequency is set to 729MHz. Don't go to extremes take small steps. Please let us know your results here.
This is what i have so far.
300MHz = 650mV
422MHz = 650mV
652MHz = 700mV
729MHz = 720mV
883MHz = 740mV
960MHz = 750mV
1036MHz = 760mV
1190MHz = 780mV
1267MHz = 790mV
1497MHz = 830mV
1574MHz = 845mV
1728MHz = 875mV
1958MHz = 945mV
2265MHz = 1000mV
Edit:
my pvs is 2
300MHz = 650mV
422MHz = 650mV
652MHz = 700mV
729MHz = 710mV
883MHz = 730mV
960MHz = 740mV
1036MHz = 750mV
1190MHz = 770mV
1267MHz = 780mV
1497MHz = 835mV
1574MHz = 840mV
1728MHz = 875mV
1958MHz = 965mV
2265MHz = 975mV

I have franco kernel, I will try your settings, Report later !

Avg sot ?

doctor_droid said:
Avg sot ?
Click to expand...
Click to collapse
I can manage about 5-6 hours but Ive made other changes as well I haven't only undervolted

apatel321 said:
I can manage about 5-6 hours but Ive made other changes as well I haven't only undervolted
Click to expand...
Click to collapse
Anything above 5hrs sot is good

doctor_droid said:
Anything above 5hrs sot is good
Click to expand...
Click to collapse
I keep my brightness at the minimum with adaptive brightness enabled also my max CPU is set to 1190MHz, I do mostly web browsing I

cranknet said:
I have franco kernel, I will try your settings, Report later !
Click to expand...
Click to collapse
Just wondering which governor are you using with the Franco kernel.

apatel321 said:
I keep my brightness at the minimum with adaptive brightness enabled also my max CPU is set to 1190MHz, I do mostly web browsing I
Click to expand...
Click to collapse
That is sweet do you live in total dark and browsing html pages LOL

apatel321 said:
Just wondering which governor are you using with the Franco kernel.
Click to expand...
Click to collapse
I'm using Interactive.

nedooo said:
That is sweet do you live in total dark and browsing html pages LOL
Click to expand...
Click to collapse
Most of the time adaptive brightness keeps the brightness at the right level however I I do wish you could adjust the sensitivity of it

[update] I was experiencing some random reboots
It wasn't as stable as it should be

apatel321 said:
Most of the time adaptive brightness keeps the brightness at the right level however I I do wish you could adjust the sensitivity of it
Click to expand...
Click to collapse
Sorry for my sarcasm
BTW back to topic I use Code_Blue kernel and I lower voltage -35 wirh Synapse and my voltage is from 740mV for 300MHz to 990mV for 2265MHz

nedooo said:
Sorry for my sarcasm
BTW back to topic I use Code_Blue kernel and I lower voltage -35 wirh Synapse and my voltage is from 740mV for 300MHz to 990mV for 2265MHz
Click to expand...
Click to collapse
You should be able to go as low as 650mV for both 300MHz and 422MHz., without experience unstable behavior.

pvs bin?

varuntis1993 said:
pvs bin?
Click to expand...
Click to collapse
Mine showed 3 on synapse.

varuntis1993 said:
pvs bin?
Click to expand...
Click to collapse
its 2

Just remember in a couple weeks if you notice stability issues or your phone rebooting, it's probably because of these changes.
Personally I value 100% stability, and I'm already able to achieve the same battery lifeout of default clocks and voltages as well as stock ROM and kernel. Such as these 5-6 hour SoT examples using 40% Adaptive Brightness.
http://imgur.com/a/vQpoz
http://imgur.com/a/sdx3a
Also I think you'll find lowering the voltages by 5-10% doesn't make a noticeable difference in battery usage, thought it should run cooler and throttle less.

apatel321 said:
You should be able to go as low as 650mV for both 300MHz and 422MHz., without experience unstable behavior.
Click to expand...
Click to collapse
Going to give this a try. I've had good success undervolting other handsets.

With latest code blue and adiutor app cannot set 650mv for 300mhz and 422mhz, lowest i can go is 700mhz not sure why though. Thank you anyway, I'm trying this out.
Enviado desde mi Nexus 5

It's the kernel the lowest you can go with code blue is 700