• 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

I have yet to see anyone comment about the "frequency lock" option i have been mentioning in TricksterMod that worked for me on the previous build...
Would ANYONE like to input whether it helped them or not?
 
dragonhart6505 said:
I have yet to see anyone comment about the "frequency lock" option i have been mentioning in TricksterMod that worked for me on the previous build...
Would ANYONE like to input whether it helped them or not?
Click to expand...

Knowing what we know now, I think that makes perfect sense. It would have prevented thermald from entering frequency commands.
 
I'm always a few minutes too late... here's a full packaged beta 4 with the new kernel-based thermal settings added, ZTE frequency ramp removed, changes to post_boot for slightly more battery savings, and thermald gets deleted. fingers crossed on this one...

AWEstruck_v1.03b4.zip - 8.63 MB
 
evyna5aq.jpg


So far so good will do more testing
 
So far I have done 3 quadrants at different max and min freqs and all have stuck :), I'm using b4 will update later today after using on batt, I think default min max should b 162-1.5 :) or at least something on the scale so the scubbers show correct
 
brittnearl said:
Still get stuck in deep sleep. Have to pull batt, other than that all seems good
Click to expand...

I'll have to see if there's any extra logging I can turn on to get a cause, very stumped on that. I have had one reboot and no freezing since 1.01.

I snuck b4 on my wife's phone today, so she is now an unknowing tester.
 
spock1104 said:
I'll have to see if there's any extra logging I can turn on to get a cause, very stumped on that. I have had one reboot and no freezing since 1.01.

I snuck b4 on my wife's phone today, so she is now an unknowing tester.
Click to expand...
Im pretty sure its a sleep issues as with use and on charger all is fine, only happens if not used for a while
 
If you can flash freq7, that has the cpufreq debugs in it, which is the first thing i'd try anyways. We'll see if that gives anything interesting in last_kmsg and work from there.
 
My wife's phone and my phone simultaneously wouldn't come back from a lock. Last_kmsg cleared itself in both cases.

I want to re-enable kernel-based mpdecision for testing purposes, the extra control it has on the cores may resolve this.
 
spock1104 said:
My wife's phone and my phone simultaneously wouldn't come back from a lock. Last_kmsg cleared itself in both cases.

I want to re-enable kernel-based mpdecision for testing purposes, the extra control it has on the cores may resolve this.
Click to expand...
at least I know its not me lol
 
PhenomX4 didn't post a list of individual changes so I'd be guessing what needs to be done and unfortunately the time I have to do this is going to be constrained for the next few weeks. If someone can get me such a list so I can cherry-pick I would be happy to make a 4.4 version.
 
I did a test merge, doesn't look too bad actually. Most of the files are from WiFi, which my repo already has. If I can exclude those I might have a test build tomorrow.
 
I *think* I need to rework mpdecision for two cores before I can enable it again. That may explain why we saw a lot of hot plugging when it shouldn't have been.

In the mean time, I think I made a boo-boo on the post-boot script. I added power_collapse/idle_enabled to cpu1, but it looks like it should only be enabled for cpu0. You can either remove the line

Code: 
echo 1 > /sys/module/pm_8x60/modes/cpu1/power_collapse/idle_enabled
or flash 1.03a
 
You must log in or register to reply here.
Back
Top Bottom