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

[buttie]

Are you using the Google or GCC version?

I'm using GCC and on AICP 12.1 (Android 7.1) I'm almost up to 48 hours without freeze.

 

[chancex]

i don't why lose the wifi? any idea?

 

[USBhost]

i don't why lose the wifi? any idea?

If I understood you
you are saying that you have no wifi?

If so update your vendor

 

[chancex]

If I understood you
you are saying that you have no wifi?

If so update your vendor

Thanks support
let me list the software version
OS: cm-13.0-20161030-NIGHTLY-flounder.zip
Kernel: FIRE-ICE K10.5.1 10-24-2016.zip (2 type GCC most try it)
Xposed: xposed-v86-sdk23-arm64.zip
Other: vendor-build-prop-fix-signed.zip
Flashtool: TWRP 3.0.2
after flash and boot, login system can't connect the wifi and can't find any wifi ap(just scan).

need help!

 

[USBhost]

Thanks support
let me list the software version
OS: cm-13.0-20161030-NIGHTLY-flounder.zip
Kernel: FIRE-ICE K10.5.1 10-24-2016.zip (2 type GCC most try it)
Xposed: xposed-v86-sdk23-arm64.zip
Other: vendor-build-prop-fix-signed.zip
Flashtool: TWRP 3.0.2
after flash and boot, login system can't connect the wifi and can't find any wifi ap(just scan).

need help!

Flash the latest vendor.img for your device
That should fix it.

Latest Marshmallow one

 

[chancex]

Flash the latest vendor.img for your device
That should fix it.

Latest Marshmallow one

Same...
maybe try other way

thanks a lot

 

[buttie]

Same...
maybe try other way

thanks a lot

Are you sure you've installed latest vendor for MM (version MOB30W)?

Pro-tip: don't use vendor-build-prop-fix then you'll always know if you have correct vendor version for your current ROM.

 

[chancex]

Are you sure you've installed latest vendor for MM (version MOB30W)?

Pro-tip: don't use vendor-build-prop-fix then you'll always know if you have correct vendor version for your current ROM.

Im use the CM ROM.

 

[buttie]

Im use the CM ROM.

Doesn't matter, CM 13 is a Marshmallow ROM, you need latest vendor from Marshmallow, that means version MOB30W.
If you unpack your ROM zip directory system you can find file build.prop, if you open this file in Notepad those two lines will always show you correct vendor for your ROM:

ro.build.description=volantis-user 6.0.1 MOB30W 3031100 release-keys
ro.build.fingerprint=google/volantis/flounder:6.0.1/MOB30W/3031100:user/release-k

Anyway, we are way off-topic, further help you should seek in CM thread.

 

[chancex]

Doesn't matter, CM 13 is a Marshmallow ROM, you need latest vendor from Marshmallow, that means version MOB30W.
If you unpack your ROM zip directory system you can find file build.prop, if you open this file in Notepad those two lines will always show you correct vendor for your ROM:

ro.build.description=volantis-user 6.0.1 MOB30W 3031100 release-keys
ro.build.fingerprint=google/volantis/flounder:6.0.1/MOB30W/3031100:user/release-k

Anyway, we are way off-topic, further help you should seek in CM thread.

thanks
but i flash to factory image, thanks again

 

[cunningstunts_1]

At the weekend, I installed the last available version of Purenexus with the latest FireIce kernel. I have to say, this is the best my Nexus 9 has ever been. I've been using Purenexus and FireIce since the start of the year and have always suffered with freezes. It seems like this is now resolved, so congratulations dev, you seem to perfected the kernel. Thanks for your work.

Sent from my Nexus 9 using Tapatalk

 

[USBhost]

K10.5.2 is up

K10.5.2
-| FI.d: v54
-| latest: from google
-| some: swap updates
-| some: ksm updates
-| fixed: some lag because of zram
not a big update.....

i will work on fixing substratum in the next update!
thanks @davall


Today is my 2 year anniversary of this kernel!!! :fingers-crossed::victory::highfive:
Thank you all for the support!

it's amazing how much i have learned in just the past two years...
I was a noob back then... well im still one now lol...
but hey i know so much more now than what i did back then!
I could not have done it without you guys! Thank you!

 

[Bryanx86]

K10.5.2
-| FI.d: v54
-| latest: from google
-| some: swap updates
-| some: ksm updates
-| fixed: some lag because of zram
not a big update.....

i will work on fixing substratum in the next update!
thanks @davall


Today is my 2 year anniversary of this kernel!!! :fingers-crossed::victory::highfive:
Thank you all for the support!

it's amazing how much i have learned in just the past two years...
I was a noob back then... well im still one now lol...
but hey i know so much more now than what i did back then!
I could not have done it without you guys!Thank you!

I was curious your input on what might happen were I to flash your kernel after having already applied a substratum overlay that I'm going to stay with? Do you think it would cause a bootloop? @USBhost

 

[USBhost]

I was curious your input on what might happen were I to flash your kernel after having already applied a substratum overlay that I'm going to stay with? Do you think it would cause a bootloop? @USBhost

off hand i dont know much about substratum.
someone told me of if it was already applied it would work.
but if it was not the overlay won't apply.

 

[wantowan2]

off hand i dont know much about substratum.
someone told me of if it was already applied it would work.
but if it was not the overlay won't apply.

Hi!

I don't use it much but I think all you have to do is open the them you used in "overlays", then " rebuild"?? At worst you would select all/uninstall selected. Reboot then do it over again the way you like it.


DEV!!! I don't know if I should call you USB or Mr. Host....

Well, well, well. I have been distracted but now I have N on my N9 I came back looking for a kernel. It seems this horrible lag has followed us into N. It was even in Slim. As I know the device maintainer for slim personally and was surprised.
I wish I had the time to really dig into this device again to see what is going on.. . I just wanted to say that I can see how much work you have put into this kernel. Original functionality has definitely started coming back! Haha I can multitask, open multiple web based apps and everything.
As it is still early for N its a bit hard to know where any of the remaining little items are (front or back end). Keep it up man, its really working out.


Thanks!

 

[USBhost]

News Update....

I'm getting some progress with substratum
I think i found the problem...

It seems aapt is not being copied to /system/bin/

Edit: one workaround is to do
adb root
adb remount

Then apply

Edit 2: it seems to be more there problem than mine....
substratum does not like busybox's mount....

Edit 3: i seem to have fixed it. substratum is working fine in my testing
but note you will have to flash your ROM again

 

[Bryanx86]

I'm getting some progress with substratum
I think i found the problem...

It seems aapt is not being copied to /system/bin/

Edit: one workaround is to do
adb root
adb remount

Then apply

Edit 2: it seems to be more there problem than mine....
substratum does not like busybox's mount....

Edit 3: i seem to have fixed it. substratum is working fine in my testing
but note you will have to flash your ROM again

So need to reflash rom then kernel, what if substratum is already applied? I've not installed any busy box other than one in line with rom

Sent from my flounder using XDA Labs

 

[USBhost]

So need to reflash rom then kernel, what if substratum is already applied? I've not installed any busy box other than one in line with rom

Sent from my flounder using XDA Labs

If it's already applied your fine. No need to reflash.

If it's not applied you will have to reflash.

 

[buffal0b1ll]

Not sure what the problem people are having with Substratum is. I'm having no issues enabling/disabling overlays with Substratum at all on:
FIREICE N 10.5.2 Google GCC (no tweaks)
phh superuser 259
Subs 490
Masq 15
Android 7.0 with 11/5 security updates

I should also disclose that I was originally on EX 5.05 on Substratum's first launch, grant Susbs/Masq root, complie enable overlays. Then I gave the 10.5.3 build a whirl and Substratum did enable/disable overlays OK. But I had weird SE Linux issues on 10.5.3 like Terminal Emulator not able to getenforce or setenforce, and AdAway not able to apply hosts file whether permissive or enforcing. I've since switched to FIREICE 10.5.2 and all is working as expected.

 

[USBhost]

Not sure what the problem people are having with Substratum is. I'm having no issues enabling/disabling overlays with Substratum at all on:
FIREICE N 10.5.2 Google GCC (no tweaks)
phh superuser 259
Subs 490
Masq 15
Android 7.0 with 11/5 security updates

I should also disclose that I was originally on EX 5.05 on Substratum's first launch, grant Susbs/Masq root, complie enable overlays. Then I gave the 10.5.3 build a whirl and Substratum did enable/disable overlays OK. But I had weird SE Linux issues on 10.5.3 like Terminal Emulator not able to getenforce or setenforce, and AdAway not able to apply hosts file whether permissive or enforcing. I've since switched to FIREICE 10.5.2 and all is working as expected.

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...