@USBhost I know, it's stupid question,but.. For CM user there isn't need to flash SupeSu? Is it right?
Yep no need@USBhost I know, it's stupid question,but.. For CM user there isn't need to flash SupeSu? Is it right?
Doesn't work on N dp3, supersu doesn't detect the binary. Tried both 2.74 and 2.72, flashed on top of stock kernel and then flashed FI, no luck. What am I missing?flash SuperSU v2.74 first because if you dont SuperSU v2.74 will error out on some backup error.
if you dont flash SuperSU then your fine.
I'm on NDP3 with SuperSU...Doesn't work on N dp3, supersu doesn't detect the binary. Tried both 2.74 and 2.72, flashed on top of stock kernel and then flashed FI, no luck. What am I missing?
Does this mean that FI kernel now has SELinux enabled by default? Will this be a problem installing over K10.2.4, since all the contexts have been wiped out?K10.2.5
-| SELinux can now be set to enforcing after boot
yes it will work on DUI think I'm missing something but I'm not sure. I have serious battery drain issues with my Nexus. I've tried a couple of ROMs and it didn't make any difference so I read about this kernel and figured I'd try it.
I tried the Pure version because of the battery problem but now I'm getting messages that I don't have root. I'm getting ready to wipe it and start fresh but I'd like to know if the kernel is compatible with the Dirty Unicorns ROM or just the Pure Nexus ROM.
The standard Fire-Ice kernel works but I didn't notice a lot of battery life improvement.
Sorry for what might be a dumb question but I just can't find the answer I'm looking for.
Sent from my Venom powered M8 using TapaTalk
SELinux is still disabled by default except on user ROM builds || stock ROM.Does this mean that FI kernel now has SELinux enabled by default? Will this be a problem installing over K10.2.4, since all the contexts have been wiped out?
--- edit ---
Hmmm... on second thought, maybe the contexts aren't wiped out. I just took another look in the root folder, and the context files appear to be intact.
init.flounder64.usb.rc
init.recovery.flounder.rc
init.recovery.flounder64.rc
init.zygote32.rc
ueventd.flounder64.rc
fstab.flounder64
init.flounder64.rc
So only this version?@USBhost Unfortunately I have the same problems with dead freezes again. Even on CM. But I can't return to stock kernel 'cause I get crashes when I flash CM without your kernel. Do I need full wipe or there is another way?
Awesome thanks! And sorry for being AFXDA / away from XDA@USBhost past ones too. The next time ,sure, I'll add logs if it would be helpful, thx)
UPDT:unfortunately ain't can get logs
/sys/fs/pstore/ is empty
UPD2: after yet one force reboot, there is /sys/fs/pstore/console-ramoops-0
The reason why is because FIRE-ICE needs the full recovery environment to work.I don't think this kernel n version can flash with flashfire, I've tried twice but nothing's changed
I know official twrp has some boot loops problem with n, is your recovery fix that?The reason why is because FIRE-ICE needs the full recovery environment to work.
Twrp will boot just give it time.I know official twrp has some boot loops problem with n, is your recovery fix that?
PN is about 2 months old but I don't think thats the problem.I tried searching through the thread, but couldn't find anything. Maybe it was poor searching. Anyway, my tablet is getting VERY hot. I read somewhere else about a problem with the wifi but supposedly google patched it. I'm wondering if I'm missing something or doing something incorrect.
Running this kernel and pure nexus.
Thanks! I'll search and figure out how to do that. It has been a while.PN is about 2 months old but I don't think thats the problem.
FIRE-ICE OC's the CPU to 2.5ghz by default
so lovering that should fix your heating problem.