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

[spock1104]

can someone provide their aboot.img for me? friendly in need of a bootloader

pull it from my B07 image N800_B07_FULL.zip - 390.98 MB

Hey spock mind if I use the kernel in my rom bro? Have not given it a try yet so I'm going to have to read the thread good so I can get the most out of it. Anything you recommend for stock use?

By all means. 1.05 beta 3 is probably the best to go with for now. I'm in the middle of what's turning out to be a substantial rewrite, and I have no idea if it's going to work or when it'll be ready.

 

[dragonhart6505]

pull it from my B07 image N800_B07_FULL.zip - 390.98 MB



By all means. 1.05 beta 3 is probably the best to go with for now. I'm in the middle of what's turning out to be a substantial rewrite, and I have no idea if it's going to work or when it'll be ready.

Looking forward to it.
One thing id like to point out. Graphics performance is greatly improved in your kernel opposed to the one in CM11. However for some reason a few tracks in Real Racing 3 crash the app when using your kernel, not in the included CM11 kernel. I also had a few flicker issues in some apps (Chrome, Facebook and a couple of games). Just thought id point out something to look into

 

[spock1104]

Looking forward to it.
One thing id like to point out. Graphics performance is greatly improved in your kernel opposed to the one in CM11. However for some reason a few tracks in Real Racing 3 crash the app when using your kernel, not in the included CM11 kernel. I also had a few flicker issues in some apps (Chrome, Facebook and a couple of games). Just thought id point out something to look into

With any luck the rewrite will address some of that, but can you grab a logcat after one of the crashes for me?

 

[dragonhart6505]

With any luck the rewrite will address some of that, but can you grab a logcat after one of the crashes for me?

Would love to. Except inexplicably beta3 decided to crash just about everything...including logcat extreme. Also now I can't mount /data in twrp? After restoring my backup all works fine again...peculiar

 

[Curtis1973]

Works like a charm bro. Have added it to rom,will leave to users what tweaking app that wish to use and point to this thread for info on how to use the kernel and what precautions they need to be aware of. Thanks man.

 

[spock1104]

https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2012637

 

[rbheromax]

https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2012637

I can't seem to view it....

 

[spock1104]

Yeah, doesn't work for me either when I click on it... this should though. I was trying to direct link to the internal shots of the N800. Clicking details on this page will bring you to a list with the internal photos as one of them.

https://apps.fcc.gov/oetcf/eas/repo...me=N&application_id=851872&fcc_id=SRQ-ZTEN800

 

[dvdavid888]

Has anybody been experiencing a reboot when toggling wifi off I have been experiencing issue when I'm using wifi for long periods of time then toggle wifi off as soon as I toggle wifi off my phone reboots this is not happen every time just once in a while but other than that when your latest kernel has been smooth nice work spock

 

[dragonhart6505]

Has anybody been experiencing a reboot when toggling wifi off I have been experiencing issue when I'm using wifi for long periods of time then toggle wifi off as soon as I toggle wifi off my phone reboots this is not happen every time just once in a while but other than that when your latest kernel has been smooth nice work spock

Had one instance of this, right after toggling wifi from the notification bar, though I was testing screen recording and had a game open in the background and attributed it to low ram.
Ive since gone back to stock CM11 kernel for better battery life so I can't EXACTLY confirm the instance

 

[spock1104]

Has anybody been experiencing a reboot when toggling wifi off I have been experiencing issue when I'm using wifi for long periods of time then toggle wifi off as soon as I toggle wifi off my phone reboots this is not happen every time just once in a while but other than that when your latest kernel has been smooth nice work spock

Please upload /proc/last_kmsg

 

[spock1104]

Had one instance of this, right after toggling wifi from the notification bar, though I was testing screen recording and had a game open in the background and attributed it to low ram.
Ive since gone back to stock CM11 kernel for better battery life so I can't EXACTLY confirm the instance

I'd be interested in seeing the better battery stats logs for stock kernel vs AWEstruck. At least in theory AWEstruck should be providing better life, but you could have found a case where the kernel is getting hung up on something and not letting the phone sleep. I have some detail on this in post #2.

 

[dvdavid888]

At work right now will upload later I believe it was a out of memory issue

 

[dragonhart6505]

I'd be interested in seeing the better battery stats logs for stock kernel vs AWEstruck. At least in theory AWEstruck should be providing better life, but you could have found a case where the kernel is getting hung up on something and not letting the phone sleep. I have some detail on this in post #2.

I use wheatley gov and have both Startup Manager and Greenify doing their thing, so literally almost NOTHING is running in the background at any time, so wake-lock shouldnt be happening on my phone for any reason and nothing runs while my screen is off. However on your kernel ill come to find almost double the battery drain with mild use. But remember, i do always have the Max clock speed as high as it will allow me (1.89 on yours, 1.72 on stock.) On stock CM11, i can go without charging nearly all day even with some gaming for an hour or two. Also as I said I was testing my recording apps (Rec. and SCR and Shou...SCR at the time) and had Modern Combat 5 running at the same time. I was also using Performance gov at the time and both apps draw significant resources

 

[spock1104]

I use Greenify to kill off wakelocks as well, and see 0.8%/h drain overnight. In this case though I'm interested in the kernel wakelocks, not the partial wakelocks. example, over the course of 48 hours i usually see about a half hour of bam_dmux_wakelock, which is the kernel accessing the radio. If one of the kernel wakelocks has gone out of control that would explain the extra drain and I may be able to fix it, otherwise it's just a matter of how often you're using it at max clock and how conservative your governor is being. Ideally if you check the frequency times you'll see a lot of time spent at 162MHz on CPU 0. CPU 1 won't get proper stats since it's being shut off by kernel mpdecision.

Also keep in mind that PhenomX4 is still using my bugged CPU table, so if you're going to compare 1.72 on his you have to go against 1.62 on the latest AWEstruck.

 

[dragonhart6505]

I use Greenify to kill off wakelocks as well, and see 0.8%/h drain overnight. In this case though I'm interested in the kernel wakelocks, not the partial wakelocks. example, over the course of 48 hours i usually see about a half hour of bam_dmux_wakelock, which is the kernel accessing the radio. If one of the kernel wakelocks has gone out of control that would explain the extra drain and I may be able to fix it, otherwise it's just a matter of how often you're using it at max clock and how conservative your governor is being. Ideally if you check the frequency times you'll see a lot of time spent at 162MHz on CPU 0. CPU 1 won't get proper stats since it's being shut off by kernel mpdecision.

Also keep in mind that PhenomX4 is still using my bugged CPU table, so if you're going to compare 1.72 on his you have to go against 1.62 on the latest AWEstruck.

Ahhh OK that's helpful information. I also have radio turned off because my phones disconnected and I know having it on uses battery. Basically I'm all about keeping my phone running as long as possible, which is the goal for anyone.
My G/F won't let me root her S4 to help her awful battery drain despite showing her how badass life I've been getting on my Awe. Angers me so >_<

 

[dragonhart6505]

Heads up on JB beta 3
Installed on stock rom. Unstable above stock frequencies. Would randomly freeze the system after about 10 minutes of use needing a battery pull. Highest freq I was able to get was 1.83, anything higher would initiate msm-dcvs at 384mhz. Also tries to boot at 2.05ghz? Is pretty fast though. Looking forward to and waiting patiently for the next revisions

 

[roadkill42]

Heads up on JB beta 3
Installed on stock rom. Unstable above stock frequencies. Would randomly freeze the system after about 10 minutes of use needing a battery pull. Highest freq I was able to get was 1.83, anything higher would initiate msm-dcvs at 384mhz. Also tries to boot at 2.05ghz? Is pretty fast though. Looking forward to and waiting patiently for the next revisions

b nice if can get 1.0 boot

 

[dragonhart6505]

b nice if can get 1.0 boot

Tried b3 yet? Would be helpful to the dev to get more info

 

[roadkill42]

Tried b3 yet? Would be helpful to the dev to get more info

I'm on kk

 

[dragonhart6505]

I'm on kk

Beta 3 has a kk version on page 26 in this thread. It DOES boot, youll have to ignore the black screen where the boot ani should be, it just doesnt show up. Give it like a minute or 2. Its pretty quick but I had some battery drain issues compared to CM11 stock. Also HID BT doesnt work but spock said hes sure he knows where it went wrong.
If you can could you grab some info with Better Battery Stats for him? Also could you compare a Quadrant to mine on the previous page? Top clock I could get was 1.89ghz, ymmv.
Anybody else would like to help would be greatly appreciated.

 

[roadkill42]

Beta 3 has a kk version on page 26 in this thread. It DOES boot, youll have to ignore the black screen where the boot ani should be, it just doesnt show up. Give it like a minute or 2. Its pretty quick but I had some battery drain issues compared to CM11 stock. Also HID BT doesnt work but spock said hes sure he knows where it went wrong.
If you can could you grab some info with Better Battery Stats for him? Also could you compare a Quadrant to mine on the previous page? Top clock I could get was 1.89ghz, ymmv.
Anybody else would like to help would be greatly appreciated.

I did try it bat was good I got the same clock u did

 

[dragonhart6505]

I did try it bat was good I got the same clock u did

Ah...well then...

 

[spock1104]

Heads up on JB beta 3
Installed on stock rom. Unstable above stock frequencies. Would randomly freeze the system after about 10 minutes of use needing a battery pull. Highest freq I was able to get was 1.83, anything higher would initiate msm-dcvs at 384mhz. Also tries to boot at 2.05ghz? Is pretty fast though. Looking forward to and waiting patiently for the next revisions

Which app told you it booted at 2.05? 3c Tuner has been showing 1.18 in the cpu times. I want to check which is lying and if there's something to fix.

 

[dragonhart6505]

Which app told you it booted at 2.05? 3c Tuner has been showing 1.18 in the cpu times. I want to check which is lying and if there's something to fix.

Ah, 3c is the new Android Tuner ain't it? I never updated it to 3c

Update: got rid of AT/3c for Trickstermod and no, its not booting at 2.05ghz. Its normal. Also found a stabler-ish frequency at 1.67ghz/wheatley. Hasnt froze yet and performance is still pretty good