• 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

spock1104 said:
I was actually considering that to isolate if the issue is the driver or the infrastructure i backported. Gonna be a few days though, little to no dev time available to me until Friday.
Click to expand...
Sounds like me lol real life comes first, wish i could do this for a living:) i have some work to do with the new walmart update lol needs integrated :eek:
 
OP kernel is working great for me so far. Set to 162-1350mhz on boot, WiFi is working with no drops yet. Nintendo DS emulation is smoother when running 2x speed, and battery is better.
 
brittnearl said:
Our stock rom is aosp based as is all roms if im not mistaking?? Just coded over with manufacturer specific code
Click to expand...

Don't mean to call you out on it, but you might be mistaken. If all ROMs were built on aosp, I wouldn't need specific kernels for different ROMs on my other devices...
AOSP, AOKP, stock are incompatible between each other. Maybe this is device specific, but I've not found anything to support otherwise.
Again, your knowledge outweighs mine, I only been flashing, testing, researching as little as necessary to do this stuff 6-7 years and don't completely understand the system, so feel free to correct me by all means
 
dragonhart6505 said:
Don't mean to call you out on it, but you might be mistaken. If all ROMs were built on aosp, I wouldn't need specific kernels for different ROMs on my other devices...
AOSP, AOKP, stock are incompatible between each other. Maybe this is device specific, but I've not found anything to support otherwise.
Again, your knowledge outweighs mine, I only been flashing, testing, researching as little as necessary to do this stuff 6-7 years and don't completely understand the system, so feel free to correct me by all means
Click to expand...
The reason different roms have different kernels is code is different from rom to rom, eg: boot class paths and driver setups, i actually got cm 10.1 to boot by modding stock kernel but everything was broke due to incorrect drivers, hals, etc...
 
brittnearl said:
The reason different roms have different kernels is code is different from rom to rom, eg: boot class paths and driver setups, i actually got cm 10.1 to boot by modding stock kernel but everything was broke due to incorrect drivers, hals, etc...
Click to expand...

I don't think that's right, the HAL is supposed to hide driver differences from the OS. Features may have been missing but so far as I know cm10.1 should be capable of booting with our kernel. More likely is something was incorrect in the machine definition or you didn't have the correct set of blobs.
 
brittnearl said:
Scratch that just had a freeze reboot https://www.dropbox.com/s/7eiwfhfqnf6a7i4/last_kmsg.txt
Click to expand...

Any more reboots? There is a wifi message toward the end but it looks innocuous. What sticks out to me is there was an emergency remount of your filesystem and immediate shutdown precipitated by:

[07-05 14:08:09.451] [1][1: init]init: sys_prop: permission denied uid:10032 name:sys.media.vdec.sw

which looks related to control of the video rendering between software and hardware
 
spock1104 said:
Any more reboots? There is a wifi message toward the end but it looks innocuous. What sticks out to me is there was an emergency remount of your filesystem and immediate shutdown precipitated by:

[07-05 14:08:09.451] [1][1: init]init: sys_prop: permission denied uid:10032 name:sys.media.vdec.sw

which looks related to control of the video rendering between software and hardware
Click to expand...
I switched bk to stock and have yet to have a random freeze or reboot, i had a couple freeze reboots on ur kernel... Although b4 u added bk mp decision i just got wifi disconnects on long operations
 
brittnearl said:
I switched bk to stock and have yet to have a random freeze or reboot, i had a couple freeze reboots on ur kernel... Although b4 u added bk mp decision i just got wifi disconnects on long operations
Click to expand...

If you go back to AWEstruck, try turning on the 10 second delay in MPDecision through trickster or android tuner, or shut it off altogether.

Anyone else out there try the latest?
 
Hey. I love your kernel. But Ive had my phone shut down and not power up until I remove and reinsert my battery several times. I've tried this at all CPU speeds. I get red messages in my logs stating that a CPU is going offline. With the MP decision, will that fix these problems? I want your kernel but am tired of my phone shutting down on me. I have reverted back to the stock kernel and just using andoid tuner to force the second core online. Thanks in advance for any advice. :)
 
stolikat said:
So with this kernel should I use android tuner or trickster or both for overclocking?
Click to expand...

Best to pick one or the other, depends on how many options you want. Android tuner is like a swiss army knife.

If you use both at the same time you risk accidentally having both apply differing settings and create a race condition, so you won't know what really got set on startup.
 
vestalpaul said:
Hey. I love your kernel. But Ive had my phone shut down and not power up until I remove and reinsert my battery several times. I've tried this at all CPU speeds. I get red messages in my logs stating that a CPU is going offline. With the MP decision, will that fix these problems? I want your kernel but am tired of my phone shutting down on me. I have reverted back to the stock kernel and just using andoid tuner to force the second core online. Thanks in advance for any advice. :)
Click to expand...

If you upload the logs I can have a look and try to figure out what happened. But it sounds like for some reason the phone thought the battery died. The battery pull would reset this.
 
vestalpaul said:
How would I get those logs via Android tuner? Last boot log?
Click to expand...

easiest thing to do is hook to the computer and do an "adb pull /proc/last_kmsg"

or, apparently the ability was recently added to android tuner (yay!). on the fourth tab select "system and kernel logs", then the manage button, and "last reboot", then click manage again and share.

Thanks for the help!
 
OK so I installed the moonshine ROMan along with your Kernel. Currently have it set at 1.45ghz on the wheatly governor. And 627mgz on demand with the GPU. Minimum cores=2.
I now have an option in Android tuner to save settings as initd script. What exactly does that mean?
 
You must log in or register to reply here.
Back
Top Bottom