• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [LINARO] AWEstruck v1.04 12/14/14 | [3.4.107] v1.05b6 5/30/15

Did some research and reading and though its an older posting I think there's some relevant information. Hope its useful.
[PROJ] Overclocking the Adreno GPU on Snapdr… | Nexus One | XDA Forum

Also a MotoG kernel with alleged GPU over clocking and mp decision to intelidemand...there's a git may be worth a look...
[KERNEL][ANYKERNEL] pink kernel 20140728 | Moto G | XDA Forum


I saw that first post, there's actually not much of use in it. That MotoG kernel on the other hand will be very useful. Uses the similar code to [KERNEL][Z] DooMKernel (v22)[20140413] | Xperia Z | XDA Forum so hopefully it's a sound approach.

Thanks!
 
Thanks for the reply.
I appreciate the work you've put in! The last kernel I had would not stay locked in to 1.35 GHz; after a while it would jump up to 1.94 and stay there.

So far, this one has stuck and not jumped. Thanks.
 
I was woundering how to tell what oc kernal I'm running cpu says its running at 2.1 android runner days same thing it runs fast I mean really fast is there an app that give me the open and oc kernal?
 
I was woundering how to tell what oc kernal I'm running cpu says its running at 2.1 android runner days same thing it runs fast I mean really fast is there an app that give me the open and oc kernal?

About phone in the android settings will give you some information and the kernel tweaking apps will usually have a kernel info page that gives detailed information. Since you're running at 2.1 chances are you're running rbheromax's kernel. AWEstruck only runs at 1.7. Once I see rbheromax's stabilized code I'll port it, we've had some level of collaboration.
 
About phone in the android settings will give you some information and the kernel tweaking apps will usually have a kernel info page that gives detailed information. Since you're running at 2.1 chances are you're running rbheromax's kernel. AWEstruck only runs at 1.7. Once I see rbheromax's stabilized code I'll port it, we've had some level of collaboration.

thanks for the onfo
 
OK so I have been running the JB beta kernel since sunday. I have had no problems until today. I was playing ingress when suddenly the app froze and then the phone rebooted. This happened three time in a row all while playing ingress. Since I was away from home I had to restore to a previous install. My CPU was clocked from 472-1.72hz using interactive and my GPU at 400hz using ondemand.

A note. I previously have had my phone clocked as high as 1.92hz using the now defunct kernel that's was previously available and I also had no trouble with spocks staple release.
 
I'm going to install AWEstruck_JB_v1.04_beta_linaro4.9.1.zip, today and I'll report back any issues and non-issues as well.
 
Just wanted to report still no reboots and freqs stick with pac performace :) did u do any experimenting with the moto g code yet??
 
I recommend trial and error, different usage patterns will mean different settings work better than others.

Disabling it altogether should keep both cores active.
 
I had 2 reboots with the 1.04 kernel. 1.35GHz - 162 GHz Wheatley. Gpu was at 400. One reboot earlier and one a few minutes ago.
 
Back
Top Bottom