[Kernel] [FIRE-ICE] [06/01] [Android 7.x 6.x]

[buffal0b1ll]

Thanks for the report....
yea that way it would work. The problem was if FIRE-ICE was flashed first before "complie enable overlays".
The problem that I seen was that substratum could not mount system/could not push aapt.

I never touched getenforce/setenforce...

Just to be clear, disabling/enabling overlays is working fine on 10.5.2 with phh259 now. The first go at enabling overlays was on EX 5.05 with phh259, then I flashed stock ROM boot.img, 10.5.3, and phh259 and booted and tested things, lastly flashed 10.5.2 and phh259 which is where I'm parked now.

 

[USBhost]

Last test

this is the last test.

If Substratum does not work then do this.
Note: make sure mount namespace is off in supersu.

/system/etc/FI.d/lib/busybox mount -o rw,remount /system
/system/etc/FI.d/lib/busybox mount -o rw,remount /vendor

Also Note: Substratum's way of checking systemless mode is bad!
i dont understand it.... it seems if mount is modified substratum would fail.

Good News! the regression from K10.5 is now fixed!!! cheers!
overall performance should be improved now.

 

[wantowan2]

Woot!

Haha, I just had too many apps opened and froze. So I came over to look for an update....perfect!

 

[USBhost]

Here's the late patch notes lol
K10.5.3
-| FI.d: v55
-| latest: from google
-| some: f2fs updates
-| some: cleanups from past merges
-| dropped: disabled selinux (it will stay permissive)
-| back to cortex a57 (a72 did not seem to help)
-| attempt to fix Substratum (it seemed to work for me)

Note's:

Substratum
In this update i stopped replacing stock mount with busybox's version.
In my attempt to fix substratum (im not happy with substratum btw).

SELinux
I decided to drop having selinux disabled it just became to problematic to keep,
and it made a lot of problems for users to switch kernels. so permissive it shall be...
goodbye clean kernel logs :crying:. i will find a way to make you clean again!

EDIT: i forgot to add i will be gone for the next 4 days on a cruise (NO INTERNET)
so i wish everyone safe journeys!

 

[wantowan2]

Hey cool, will give this a shot. Was having some freezing when going from one open web app to another with recents. Hard reset required. It would start there but would still get haptic feedback for a few taps before it would stop. During this time hardware buttons would still work. Could blank and unblank display, open power options but not be able to select anything. Synapse wouldn't be there. Work around was to keep recents simple and/or minimize everything before starting something new.

Oh ya it was the GNU version of the N version that I was using.
And you were right. The last update did do away with A LOT of the old MM lag issues, wicked!!!

 

[wantowan2]

Hey, pulled a driver log. It seems to have some interesting stuff in there. Maybe a good source for some fixes?
http://pastebin.com/RLrXSfbY

Hope this helps. ?

 

[henderjr]

Hi. I'm a fairly new owner of this device purchased second hand from eBay. Definitely not a noob in the root/flashing/android world though. So I am running the latest 7.1 release rooted (or maybe it's 7.1.1? whatever the absolute latest beta is). I thought I'd give this kernel a try last night. I flashed it with FlashFire and everything seems fine. I just cannot, for the life of me, figure out how to change the brightness. I have terminal emulator installed (and am familiar with it) but can't get any sort of BL (or bl) command to be recognized. Generally I just tried bl -r but kept getting the same error (command not recognized or something similar). I also tried giving SU access first by entering in su and then the bl -r command after I get root access. What am I missing? I didn't find any help in the search but sorry if I missed something. I tend to spend the majority of my time reading on my N9 at night in bed and it was wayyyy too bright last night. Thanks for any help!

 

[Choochter]

Hi. I'm a fairly new owner of this device purchased second hand from eBay. Definitely not a noob in the root/flashing/android world though. So I am running the latest 7.1 release rooted (or maybe it's 7.1.1? whatever the absolute latest beta is). I thought I'd give this kernel a try last night. I flashed it with FlashFire and everything seems fine. I just cannot, for the life of me, figure out how to change the brightness. I have terminal emulator installed (and am familiar with it) but can't get any sort of BL (or bl) command to be recognized. Generally I just tried bl -r but kept getting the same error (command not recognized or something similar). I also tried giving SU access first by entering in su and then the bl -r command after I get root access. What am I missing? I didn't find any help in the search but sorry if I missed something. I tend to spend the majority of my time reading on my N9 at night in bed and it was wayyyy too bright last night. Thanks for any help!

As a stopgap you might want to try f.lux from the Play store, helps a lot with nighttime reading

 

[Bryanx86]

Hi. I'm a fairly new owner of this device purchased second hand from eBay. Definitely not a noob in the root/flashing/android world though. So I am running the latest 7.1 release rooted (or maybe it's 7.1.1? whatever the absolute latest beta is). I thought I'd give this kernel a try last night. I flashed it with FlashFire and everything seems fine. I just cannot, for the life of me, figure out how to change the brightness. I have terminal emulator installed (and am familiar with it) but can't get any sort of BL (or bl) command to be recognized. Generally I just tried bl -r but kept getting the same error (command not recognized or something similar). I also tried giving SU access first by entering in su and then the bl -r command after I get root access. What am I missing? I didn't find any help in the search but sorry if I missed something. I tend to spend the majority of my time reading on my N9 at night in bed and it was wayyyy too bright last night. Thanks for any help!

C.f.lumen by chain fire is an app that can adjust your brightness and screen tint

Sent from my flounder using XDA Labs

 

[USBhost]

Hi. I'm a fairly new owner of this device purchased second hand from eBay. Definitely not a noob in the root/flashing/android world though. So I am running the latest 7.1 release rooted (or maybe it's 7.1.1? whatever the absolute latest beta is). I thought I'd give this kernel a try last night. I flashed it with FlashFire and everything seems fine. I just cannot, for the life of me, figure out how to change the brightness. I have terminal emulator installed (and am familiar with it) but can't get any sort of BL (or bl) command to be recognized. Generally I just tried bl -r but kept getting the same error (command not recognized or something similar). I also tried giving SU access first by entering in su and then the bl -r command after I get root access. What am I missing? I didn't find any help in the search but sorry if I missed something. I tend to spend the majority of my time reading on my N9 at night in bed and it was wayyyy too bright last night. Thanks for any help!

My kernel needs to be flashed from recovery for bl to work.

 

[USBhost]

K10.5.4 is up

K10.5.4
-| updated: to N 7.1.1 kernel source
-| slight: cleanup of the K10.5 full system freeze fix


Happy Holidays!

 

[USBhost]

Thanks everyone for testing.
K10.5.5 will be up today.

 

[buttie]

ok guys im testing a hunch.....
let me know if something happens at what uptime.

Test 1 and 2 froze while watching video, test 1 on YouTube and test 2 on Amazon Video to be exact. Uptime varies but is not longer than 3h. Didn't check 3 yet.

BTW: did you change anything in recovery kernel in test 1 or 2? TWRP rebooted on me once in a while on idle and every time when I tried to flash ROM. Problem disappeared after flashing test 3.

 

[USBhost]

Test 1 and 2 froze while watching video, test 1 on YouTube and test 2 on Amazon Video to be exact. Uptime varies but is not longer than 3h. Didn't check 3 yet.

BTW: did you change anything in recovery kernel in test 1 or 2? TWRP rebooted on me once in a while on idle and every time when I tried to flash ROM. Problem disappeared after flashing test 3.

only the kernel.
what im testing is what causing the freeze i had on K10.5.4(K10.5.3 i had an uptime of 3days+).
1.2.3 all had freezing. im trying to make sure this was really the problem.
PS. test 4 is up if you want to try.

 

[buttie]

only the kernel.
what im testing is what causing the freeze i had on K10.5.4(K10.5.3 i had an uptime of 3days+).
1.2.3 all had freezing. im trying to make sure this was really the problem.
PS. test 4 is up if you want to try.

I've clocked almost 4 days on 10.5.3 with ResurrectionRemix, it froze eventually but for this dreadful tablet it's still exceptional result.
Although I've had video freezes on Netflix, other video apps (Amazon Video, BBC iPlayer, SeeSo) run smoothly.

On test 3 I'm on hour 9, but didn't use tablet very intensely, will check test 4.

 

[blackbuffalo]

ok guys im testing a hunch.....
let me know if something happens at what uptime.

edit: test 2
edit: test 3
edit: test 4

Good news. I'm on Test 4 and when play video on youtube, it not freeze :good:

PS:
1. I updated to 7.1.1 and get random freeze with test 4. Back to 5.3 version and will test with test 6

 

[buttie]

Test 4 is better than 1, 2 and 3, but still far from stable. Although, freeze on test 4 is not permanent like before, after a minute or three tablet unfreeze itself so now I'm on 24h of uptime even though it froze on me at least 4 times.

 

[USBhost]

K10.5.5 is up

K10.5.5
-| latest: from google
-| reverted: "slight: cleanup of the K10.5 full system freeze fix" because the freezes came back

edit: man i must be sleepy lol fixed

 

[oldseddie]

10.5.5 fixed a problem I had with Tecarta Bible not scrolling. So far looks like a keeper. Thanks for you work!

 

[buttie]

Sadly problem with Netflix is back on 10.5.5 and 10.5.6.