• 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

As u can c in my screen of same app u use min is incorrectly set kernel side as I have removed min from script
ehatesuj.jpg

I'm open to suggestions on how to approach this, I can't produce this on my phone and so can't even begin to look for a cause yet.
 
What good will removing the stock frequencies from the table do other than remove options that may be valuable to some (including me)?
 
udadevem.jpg
no ur not being rude, im running the script updated per jimsmith80 I can give u a trickster screen it shows same I'm running b2
 
Sorry I mean an app that will overload the phone for a sustained time and cause it to jump frequency. Though I don't think there's anything that can be done about that, pretty sure that's just the governors acting up. Most intensive app I have is Monopoly.
 
Sorry I mean an app that will overload the phone for a sustained time and cause it to jump frequency. Though I don't think there's anything that can be done about that, pretty sure that's just the governors acting up. Most intensive app I have is Monopoly.

I would suggest "solar system 3d" I know its pretty heavy on hardware, its free and about 50mb. https://play.google.com/store/apps/...m_medium=organic&utm_term=3d+solar+system+app
Might do the trick for you.
 
Sorry I mean an app that will overload the phone for a sustained time and cause it to jump frequency. Though I don't think there's anything that can be done about that, pretty sure that's just the governors acting up. Most intensive app I have is Monopoly.

Quadrant standard does it, also I play templerun 2 and Baja or bust
 
Ugh I should have thought of quadrant. Using cool tool to overlay the frequency I can see the CPU jump to 1.35 which I have to believe is because of the scaling settings. Once it goes past 1.18 it doesn't seem to return to using 1.18 as the max (I think this explains your observation of the frequency not sticking). I'll set all of the scaling values back to 1 tonight.
 
Or not... I reset the frequencies with android tuner and the setting sticks, it won't go past 1.18. We may have to add the initial frequencies back to the post boot script.
 
Or not... I reset the frequencies with android tuner and the setting sticks, it won't go past 1.18. We may have to add the initial frequencies back to the post boot script.

All the script does is what the app does which is echo a min max, the kernel should abide by this. Instead it takes over and over clocks as it sees fit depending on load, android tuner may keep echoing as the kernel tries override the setting
 
All the script does is what the app does which is echo a min max, the kernel should abide by this. Instead it takes over and over clocks as it sees fit depending on load, android tuner may keep echoing as the kernel tries override the setting

Script didn't fix it. It looks like a cpufreq or governor bug. Making every frequency a scale frequency will only hide the underlying issue. I need to find where it looks at the available scale frequencies when ramping up and add an if statement to shield going past the specified max. I expect this will be a few days. Will also look at GPU. Thanks for your patience while I tried to wrap my mind around it.
 
Script didn't fix it. It looks like a cpufreq or governor bug. Making every frequency a scale frequency will only hide the underlying issue. I need to find where it looks at the available scale frequencies when ramping up and add an if statement to shield going past the specified max. I expect this will be a few days. Will also look at GPU. Thanks for your patience while I tried to wrap my mind around it.

No problem thanks for even making a fairly stabile oc:)
 
Here is a workaround that is working on my phone right now. Set your max frequency to 1.134, 1.35, 1.458, 1.512, 1.674, or 1.728 and it should stick.
 
Just wanted to put out there I have still had no overloads heats or crashes. My settings have stayed locked and even the hz have not gone beyond their designation. Using trickstermod, 1.03 kernel at 1.5 GHz interactive. Wish I had one of the devices that have issues, but I'm not complaining lol.

Modern Combat 4, Nova 3, Ravensword...everything is smooth and slick. Even bumped up the graphics with 4xAA and Nvida Shield settings with GlTools. Makes em look great and still smooth as a beast.
 
Just wanted to put out there I have still had no overloads heats or crashes. My settings have stayed locked and even the hz have not gone beyond their designation. Using trickstermod, 1.03 kernel at 1.5 GHz interactive. Wish I had one of the devices that have issues, but I'm not complaining lol.

Modern Combat 4, Nova 3, Ravensword...everything is smooth and slick. Even bumped up the graphics with 4xAA and Nvida Shield settings with GlTools. Makes em look great and still smooth as a beast.

1.5 is one of the frequencies that will lock, not very surprising. Glad it's working well.
 
Back
Top Bottom