If I'm not mistaken, I believe you are correct looking at this commit. I'm assuming it works similarly to Windows 10 fast startup.That's odd. I think you may be correct. It reverted back to my original mac address from before I flashed the previous kernel I was using. I saw it from an old entry in my router's config page.
By the way. Did you do something to make the device boot faster or am I just experiencing a placebo effect of sorts?
I don't recall having done anything for faster boot.That's odd. I think you may be correct. It reverted back to my original mac address from before I flashed the previous kernel I was using. I saw it from an old entry in my router's config page.
By the way. Did you do something to make the device boot faster or am I just experiencing a placebo effect of sorts?
Makes sense. I wonder how one can force a hard restart?If I'm not mistaken, I believe you are correct looking at this commit. I'm assuming it works similarly to Windows 10 fast startup.![]()
Placebo effect it is. Well, I did a complete uninstall and reinstall of Magisk as well so that may have helped. Thanks for the Kernel!I don't recall having done anything for faster boot.
You don't need to switch to system_b... also flash Magisk before flashing FK.Sir @franciscofranco I had a bootloop upon flashing your kernel. Here are my steps:
1. Dirty flash fastboot rom using V9.5.9.0.ODHMIFA (Android O) from http://en.miui.com/download-333.html via MiFlash (save user data).
2. Boot to bootloader, fastboot oem unlock
3. Boot latest twrp recovery, fastboot boot recovery-3.2.1-2-oreo.img
4. Switch to system_b, then boot again to recovery.
5. Flash franco Kernel.
6. Flash latest Magisk beta, 16.3.
Am I doing it wrong? Thanks sir.
You shoul flash magisk first before the kernel....Sir @franciscofranco I had a bootloop upon flashing your kernel. Here are my steps:
1. Dirty flash fastboot rom using V9.5.9.0.ODHMIFA (Android O) from http://en.miui.com/download-333.html via MiFlash (save user data).
2. Boot to bootloader, fastboot oem unlock
3. Boot latest twrp recovery, fastboot boot recovery-3.2.1-2-oreo.img
4. Switch to system_b, then boot again to recovery.
5. Flash franco Kernel.
6. Flash latest Magisk beta, 16.3.
Am I doing it wrong? Thanks sir.
Yes... I thought we were all past that already this late at the game...so dirty flash with miflash ? how about dirty flasb with twrp can it be ?
Ok, thanks a lot. It works fine now when flashed on system_a. Thanks for this awesome kernel sir.You don't need to switch to system_b... also flash Magisk before flashing FK.
so if dirty flash with twrp can not?Yes... I thought we were all past that already this late at the game...
Not supported by stock so it's unlikely.Goodnight @franciscofranco.
I have not seen in the first and second post that the kernel contains to wake up the screen with double tap.
It contains it?
If not, will it be implemented?
Thank you very much for the work you do.
As long as the dirty flash involves flashing boot, system and modem, it should be okay.so if dirty flash with twrp can not?
I would flash it like so:Great work! How to flash this kernel if on any other custom kernel??
First of all thank you The Great Franco for supporting MIA1.Not supported by stock so it's unlikely.
1. Why use a custom kernel if you won't root it to set tweaks/changes to the kernel itself? What's the point?1. Do we really need to flash Magisk, I dont want to root my phone... Just want use your Kernel
2. Why many custom roms also want to flash Magisk (Compulsory) . Can anyone explain?
That's not the Stock Mi A1 kernel. That's a custom kernel called MetaPhoenix.First of all thank you The Great Franco for supporting MIA1.
Bro for stock kernel it dpes support double tap to wake . You can find the commit and source of implementation here it will be great if you can spare some time for this implementation
Link below of stock kernel having double tap to wake implement and working well..
https://github.com/ghpranav/MetaPhoenix_tissot