[dpaine88]

So as of 3.2 the default GPU is 307? But before that it was 384?

Sent from my Galaxy Nexus

[Exostenza]

Came over frame Franco kernel about a month ago and I mist say I like how you keep this kernel so up to date with the latest sources. It is smooth with good battery life and since I can flash through Franco kernel updated it is a winner! You guys both are great devs and I love having the option at anytime to have either an up to date lean kernel or a heavily modded kernel.

Great job!

Sent from my Galaxy Nexus using Tapatalk 2

[ThehulKK]

I was getting the same problem after raising the GPU OC to 512. After rebooting everything seems better. Here is the output
app_36@android:/ $ export PATH=/data/local/bin:$PATH
app_36@android:/ $ su
app_36@android:/ # dmesg | grep gpu
[ 40.029724] [imoseyon] gpu top speed changed from 307200000 to 512000000 (0,0)
app_36@android:/ #

Sent from my Galaxy Nexus using RootzWiki

[abqnm]

mozy420, on 12 April 2012 - 09:46 AM, said:

awesome, IMO! I'll give it go today. Some cpu utilities allow for screen-off profiles. Is the 'so' script similar in that regard? Also, I did notice governor(Interactive) would stay essentially pinned at 700mhz if min was set to 700mhz in earlier kernels. I think that was resolved in 3.1 exp2 though.

As far as off-screen behavior goes, is there an easy way to force it not to go below the minimum - unless it's sleeping. The only benefit 'could' be some of the tethering / mobile data disconnects people are experiencing with the release of 4.0.4 imm76.

Thanks again!

The kernel by default limits the screen off speed to a max of 700. The script just turns that off so it can scale the full range when the screen is off and the phone is awake.

dpaine88, on 12 April 2012 - 09:48 AM, said:

So as of 3.2 the default GPU is 307? But before that it was 384?

Sent from my Galaxy Nexus

Yes it defaults to 307 to help with some reboot issues on some devices. You can increase it if you wish but personally the only thing that I have found to be impacted by increasing it is nenamark2 scores. Nothing I have seen performance-wise has been impacted. Not even other benchmarks seem to be affected.

[Mr. Steve]

I'm getting an md5sum check failure while trying to update from 3.1.0exp2-230 to the 3.2.0exp1-230 using lkflash.

[KaosMcRage]

Arvylas, on 12 April 2012 - 08:29 AM, said:

Nope! 1200mhz and 1350mhz definitely don't drain the same. battery consumption depends on the voltage, current and frequency so a higher freq will drain more because of the additional current AND the higher freq.

Metallice, on 12 April 2012 - 08:30 AM, said:

I'm pretty sure actual drain is calculated by multiplying MHz and mv and capacitance or resistance or something like that. So 1350 at 1220mv with consume more power than 1200 at 1220mv. Also "race to idle" depends on the bottleneck. Its often not the CPU. Writing files to /data or /sdcard should take just as long at 350mhz than at 1200mhz.

Sent from my Galaxy Nexus using RootzWiki

Huh, my mistake then. I could have sworn I read otherwise multiple times in various threads. Maybe just misinformation creep.

Thanks.

[rusty815]

hmm, I type in "oc gpu 2" and it says that the gpu clock has been set to 384mhz instead of 512mhz, any idea why?

[imoseyon (OP)]

Mr. Steve, on 12 April 2012 - 09:57 AM, said:

I'm getting an md5sum check failure while trying to update from 3.1.0exp2-230 to the 3.2.0exp1-230 using lkflash.

sorry fixed now i think.

rusty815, on 12 April 2012 - 10:10 AM, said:

hmm, I type in "oc gpu 2" and it says that the gpu clock has been set to 384mhz instead of 512mhz, any idea why?

haha that's because there's a typo in my script! It does set the frequency correctly to 512mhz but reports incorrectly. You can double-check using "checkt". You can also use lean tweaks which has been tested more thoroughly.

[Mr. Steve]

imoseyon, on 12 April 2012 - 10:14 AM, said:

sorry fixed now i think.



haha that's because there's a typo in my script! It does set the frequency correctly to 512mhz but reports incorrectly. You can double-check using "checkt". You can also use lean tweaks which has been tested more thoroughly.

Just checked and the md5sum check went through perfectly. Thanks!

[Mr. Steve]

So how much will overclocking the gpu from 384mHz to 512mHz affect battery life?