• 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

DsyMnapTic said:
Maybe stability is an ongoing process of testing to see if this or that works and then adding something that breaks something else.... More features are probably all "in between" types of things, to give people more options while in fact the subtle stability tweaks and bug squashing is a continuous process that goes on behind the scenes.... Weren't all the attempts and constant kernel releases, about getting things to operate stably in the first place?
Click to expand...
Yes they were but its the "its good enough mentality" u get when u point out an issue... For example i take into consideration every issue ppl see with my rom release i dont respond saying "the app ur using doesnt work correctly" like i got from u and spock... If it was an app issue the stock kernel would have issues
 
For me PowerControl works fine and especially after the last update. This is based off the AOKP power control from source. I find no issues with settings sticking with the stock kernel, not to mention the plethora of tools and tweaks the app offers. Don't get me wrong about this kernel its a work in progress and its coming along. I, like many others love bleeding edge and find it cool for a time but when it comes down to it in the end stability supersedes cool every time. Spock will get it sorted eventually I'm sure. :)
 
I have also never had a freezboot yet. Sometimes my phone gets hot on high frequencies if I'm playing with it too much and it stops charging but let it cool down and its good again.
Remember folks, the chip in our phones reacts differently under various conditions and the quality of the overall chip you have. We have had this discussion more than once. For one reason or another some phones work great while others dont work at all.
I too cant use performance control because it won't stick settings and has caused my phone to wig out. Trickstermod and Android Tuner have been great to me and have the most amount of options available when things are added down the line. It comes down to the point of have you taken one app out and tried the other for an elongated time? TM/AT dont work for you? I'm sure theres an alternative that does but remember these are the highest regarded tuning apps available and have been for quite some time. Saying "well I dont use it" for one reason or another is personal preference, but if you havent given it time to see if your issues are still prevalent then thats your problem.
If you keep backtracking to make one thing stable, you dont get ahead of the game. Without testing new releases with new features, you won't have any idea if what was added broke something else and how/why/where that bug exists. Thats why we have log cat. By adding new stuff well see more and more differences in how people will use the kernel and can then conclude if its gone far enough...and you can never go too far IMO
Spock youve done great and I have no complaints over stability on my end. However you wish to proceed is up to you.

...it is your kernel after all
 
So what is the news with this kernel? Is it 4.4.4 compatible now? I went to download it and it shows it was last updated in June.
 
stolikat said:
So what is the news with this kernel? Is it 4.4.4 compatible now? I went to download it and it shows it was last updated in June.
Click to expand...

I tried making a compatible kernel a couple of weeks ago but testers reported issues. I will try again soon.
 
brittnearl said:
Gotcha... So ur improving it;)
Click to expand...

I'd like to characterize it as "unifying." I've got it so that the same source code will compile either the KitKat kernel or the JB Kernel, just need to select the correct defconfig. I've applied PhenomX4's architectural changes on top of what I already have, so new kernels will be a superset for the most part.

I'll see about testing the KitKat side of things on my phone, but here's a test version of the unified JB kernel.

AWEstruck_v1.04_beta_unified.zip - 8.77 MB
 
DsyMnapTic said:
I've never gotten random freeze reboots with it, however I have figured out a method to keep both cores running and doing what I want.... In the mp decision control settings I just set min_CPUs and max_CPUs both to 2 and now they run fine.

Do you know what scroff_single_core is though?
Click to expand...

screen off single core. if it's enabled, only cpu 0 will run while your phone's screen is off. Because really, you only need one core running when you're not using it. More modern processors have a big.LITTLE configuration where they can switch to a slower/more power efficient core, but we don't have that option so this is the best we get.
 
the problem with KitKat:

E/dalvikvm( 6754): JNI posting fatal error: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...
 
spock1104 said:
I'd like to characterize it as "unifying." I've got it so that the same source code will compile either the KitKat kernel or the JB Kernel, just need to select the correct defconfig. I've applied PhenomX4's architectural changes on top of what I already have, so new kernels will be a superset for the most part.

I'll see about testing the KitKat side of things on my phone, but here's a test version of the unified JB kernel.

AWEstruck_v1.04_beta_unified.zip - 8.77 MB
Click to expand...
Still get freeze reboot on 2 different devices :confused: also y no gpu oc??
https://www.dropbox.com/s/7eiwfhfqnf6a7i4/last_kmsg.txt
 
And confirmed that the function that was being used to update the frequencies was removed by PhenomX4. I'll restore and hope it doesn't break KitKat.
 
Will it still switch to single core with screen off, if I have the minimum cores set to 2...I mean seems like it would since it still allows that option to be on.
 
DsyMnapTic said:
Will it still switch to single core with screen off, if I have the minimum cores set to 2...I mean seems like it would since it still allows that option to be on.
Click to expand...

I don't know, but in the name of science you can find out.

adb shell
cat /proc/kmsg | grep 'MPDEC'
 
You must log in or register to reply here.
Back
Top Bottom