I have been working on grouper recently and I felt that there was a certain lack of a stock based kernel with only useful stuff and not custom features. There might be some users like me who haven't been able to customize their tablets much because of schedule and lego kernel hasn't been updated much recently. So I have made a kernel for Lollipop with only required stuff.
Some points to note(they can't be called features)-
Compiled using latest Linraro 4.9 optimized for Cortex A9
Kexec support
All-F2FS support
GPU overclock(franco's method)
Optimized ARM RWSEM algorithm
Entropy tweaks
Agnostic kernel flasher
SuperSU compatible
Download- http://forum.xda-developers.com/devdb/project/?id=6701#downloads for boot.img
and http://d-h.st/2bYP for agnostic kernel flasher zip
Note- boot.img is only for All-F2FS partition users while zip can be used for all partition types(ext4, data-F2FS, all-F2FS).
XDA:DevDB Information
Phantom Kernel, Kernel for the Nexus 7
Contributors
Shivam Kuchhal
Source Code: https://github.com/shivamk11/android_kernel_asus_grouper
Kernel Special Features:
Version Information
Status: Stable
Created 2014-11-17
Last Updated 2015-05-03
Reserved
Reserved
nice!...will check it out and report back....
d
**wow, just installed latest Lollipop image (LRX21P) after converting to ALL-F2FS and it boots just fine!...
Im impressed with Lollipop setup!
Awesome, I'm gonna give this a try!
For GPU overclock is it set higher already or do I need an external app or additional files to affect it?
Sweet, now all i need is some advanced power button options and my tablet is set :3
dareino said:
nice!...will check it out and report back....
d
**wow, just installed latest Lollipop image (LRX21P) after converting to ALL-F2FS and it boots just fine!...
Im impressed with Lollipop setup!
Click to expand...
Click to collapse
What steps did you follow? I tried the same and got stuck at boot.
Which root way did you follow? Chainfire or permissive?
I am running rooted factory image on ext4. I flashed the zip, got positive feedback of the boot.img installing, rebooted, saw one app optimizing on boot. But when I go to settings.device the kernel still reports the stock name and in trickster I see the same with no evidence of any new gpu customizability. Thanks.
javivalle said:
What steps did you follow? I tried the same and got stuck at boot.
Click to expand...
Click to collapse
I didnt do anything differently when I convert a ROM to ALL-F2FS..I know it takes a good 5 mins once it hits the swirling balls....
I dont have root tho....
d
**just updated SuperSU and im rooted...**
dareino said:
I didnt do anything differently when I convert a ROM to ALL-F2FS..I know it takes a good 5 mins once it hits the swirling balls....
I dont have root tho....
d
**just updated SuperSU and im rooted...**
Click to expand...
Click to collapse
any guides available... ive tried some of the stuff but did not convert....
MattSkeet said:
any guides available... ive tried some of the stuff but did not convert....
Click to expand...
Click to collapse
PM me and ill send u my copy
dareino said:
PM me and ill send u my copy
Click to expand...
Click to collapse
PM sent thanks
I am also wondering, how did you convert a Lollipop ROM to All-F2FS? With the 'Convert To F2FS' App from the Play Store? Does it work with 5.0?
Or is all i need flashing a Lollipop ROM on my F2FS device and then this kernel and it will boot?
also can i use this kernel on tilapia? I know i can't use grouper ROMs but never bothered with Kernels until now.
punshkin said:
I am also wondering, how did you convert a Lollipop ROM to All-F2FS? With the 'Convert To F2FS' App from the Play Store? Does it work with 5.0?
Or is all i need flashing a Lollipop ROM on my F2FS device and then this kernel and it will boot?
also can i use this kernel on tilapia? I know i can't use grouper ROMs but never bothered with Kernels until now.
Click to expand...
Click to collapse
Actually if you flash a grouper version of twrp you can use grouper ROMs on a tilapia. You just lose 3g.
Sent from my Nexus 7 (build by kayioulis.com) using XDA Free mobile app
this was the best kernel for falcon, i can't wait to try it for the nexus 7 :good:
GtrCraft said:
Which root way did you follow? Chainfire or permissive?
Click to expand...
Click to collapse
Chainfire
buffal0b1ll said:
I am running rooted factory image on ext4. I flashed the zip, got positive feedback of the boot.img installing, rebooted, saw one app optimizing on boot. But when I go to settings.device the kernel still reports the stock name and in trickster I see the same with no evidence of any new gpu customizability. Thanks.
Click to expand...
Click to collapse
That's weird, might be some issue in agnostic flasher. Anybody else can confirm?
punshkin said:
I am also wondering, how did you convert a Lollipop ROM to All-F2FS? With the 'Convert To F2FS' App from the Play Store? Does it work with 5.0?
Or is all i need flashing a Lollipop ROM on my F2FS device and then this kernel and it will boot?
also can i use this kernel on tilapia? I know i can't use grouper ROMs but never bothered with Kernels until now.
Click to expand...
Click to collapse
There's an All-F2FS zip available in android dev.
dustcollector69 said:
this was the best kernel for falcon, i can't wait to try it for the nexus 7 :good:
Click to expand...
Click to collapse
Thanks!
I'll try this.
Anything, ANYTHING is better than the stock kernel on the OG N7.
Shivam Kuchhal said:
There's an All-F2FS zip available in android dev.
Click to expand...
Click to collapse
Care to share that zip and the steps you took to achieve f2fs?
Related
TWRP-2.7.0.0 with "All-F2FS" support​
I have modified the standard TWRP recovery to work with F2FS partitions.
This is different from the previous recoveries that i published.
This is for "All-F2FS" that mean that /system, /cache and /data are formatted with F2FS.
Keep in mind that this can work only with a compatible kernel and ROM.
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Download:
FormatPartitions.zip: Here
TWRP-recovery img: Here
Chagelogs:
- 11/03/14: Initial release
Here are some explanations. Read them
Recovery has the usual red back key to remember you that you are using a F2FS-recovery.
If wiping /system and /cache and making a factory reset from Wipe menu doesn't work, use FormatPartitions.zip. (<- READ THIS)
Instead wiping /data is fine within the wipe menu.
To switch your /system, /cache and /data partitions to F2FS follow instructions:
Keep in mind that you will lose all the files on the memory of your N7.
You need:
- Two files you can download above (img and FormatPartitions.zip)
- A ROM with "All-F2FS" support (Like my SlimKat version)
(Or Make your ROM with Convert To F2FS)
- GApps (i think you want PlayStore.) Usual GApps. Slim AiO work well.
Copy a ROM with "All-F2FS" support to your N7
Copy GApps to your N7
Copy FormatPartitions.zip to your N7
Reboot in bootloader
Flash this recovery with Fastboot (Maybe Flashify works too)
Reboot in new recovery
Flash FormatPartitions.zip
Reboot recovery (It's needed for some reasons..)
Flash ROM
Flash GApps
Go to Wipe Menu and Format Data (Not a simple wipe)
Reboot
Done.
It's easier than it seems
To restore partitions to stock:
- Download a standard TWRP
- Download RestorePartitions.zip
Flash RestorePartitions.zip (Untested)
Flash standard Recovery
Format Data in Wipe Menu
Hope i dind't any errors writing this down. I personally tested this procedure.
Enjoy.
This is Awesome thxs for your hard work. And a few people where talking about have a Twrp that had all the partitions in f2fs and bam here it is.
Awesome work legolas!
So if I understand correctly, just having an f2fs-supported kernel isn't enough to run f2fs on all partitions? We need a modified ROM as well?
Also, are you going to make a modified TWRP 2.7 with MultiROM support?
Curious about which ROM has "All F2FS" support? Lego, did you modify one as such?
Sent from my Nexus 7 using Tapatalk
farmerbb said:
Awesome work legolas!
So if I understand correctly, just having an f2fs-supported kernel isn't enough to run f2fs on all partitions? We need a modified ROM as well?
Also, are you going to make a modified TWRP 2.7 with MultiROM support?
Click to expand...
Click to collapse
Yes. You need a modified ROM too.
Yes when i have some free time! As now this doesn't support MultiROM for the reason writed in OP.
adomol said:
Curious about which ROM has "All F2FS" support? Lego, did you modify one as such?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes . My SlimKat version is ready.
legolas93 said:
Yes. You need a modified ROM too.
Yes when i have some free time! As now this doesn't support MultiROM for the reason writed in OP.
Yes . My SlimKat version is ready.
Click to expand...
Click to collapse
I should have noticed your post with the ROM... Thanks!
Oh boy, legolas you have been mighty busy lately lol... Thanks for this hard work of yours.
Can non-devs manage to modify their ROM of choice or is this something only the ROM devs can manage?
Sent from my Nexus 7 using Tapatalk
I can verify that everything is working as advertised... Installed your modified files and am now up and running with F2FS.
I'll post if I run into anything odd.
[EDIT] Finished restoring all my apps and data. And it's blazing! Ran an ANTUTU benchmark test and scored a
14829 vs. 12726 of a stock Nexus 7!!!
And the here are the numbers for the Quadrant benchmark: 5748 vs. 3517 for stock... nice!!
Thanks again legolas!
Does the standard omni ROM will work with this? If not then where can I find a modified omni ROM? And where can we find modified gapps?
Sent from my Nexus 7 using Tapatalk
bhu1 said:
Does the standard omni ROM will work with this? If not then where can I find a modified omni ROM? And where can we find modified gapps?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I believe users will have to ask their devs to provide a modified version of their ROM of choice. I'm going to give SlimKat a try with M-kernel here soon I think, just because legolas seems to be the only dev taking F2FS support seriously. I like that about him.
What is meant by "Normal Gapps"? I wasn't aware there was a Gapps considered not normal. There are only different versions of it. Can someone provide a link to "Normal Gapps" please? OP says in the play store but I do not find anything in the play store called normal gapps, or even gapps (although I did find something called Gapps Manager, hmmm). I normally use PA gapps or the latest CM gapps. Thank you
EDIT: Never mind, I just found that SlimROM's has their own version of Gapps, which seems to me to be the best choice if I am going to try SlimKat. lol
Sent from my Nexus 7 using Tapatalk
adomol said:
I can verify that everything is working as advertised... Installed your modified files and am now up and running with F2FS.
I'll post if I run into anything odd.
[EDIT] Finished restoring all my apps and data. And it's blazing! Ran an ANTUTU benchmark test and scored a
14829 vs. 12726 of a stock Nexus 7!!!
And the here are the numbers for the Quadrant benchmark: 5748 vs. 3517 for stock... nice!!
Thanks again legolas!
Click to expand...
Click to collapse
Glad you like this
SkOrPn said:
I believe users will have to ask their devs to provide a modified version of their ROM of choice. I'm going to give SlimKat a try with M-kernel here soon I think, just because legolas seems to be the only dev taking F2FS support seriously. I like that about him.
What is meant by "Normal Gapps"? I wasn't aware there was a Gapps considered not normal. There are only different versions of it. Can someone provide a link to "Normal Gapps" please? OP says in the play store but I do not find anything in the play store called normal gapps, or even gapps (although I did find something called Gapps Manager, hmmm). I normally use PA gapps or the latest CM gapps. Thank you
EDIT: Never mind, I just found that SlimROM's has their own version of Gapps, which seems to me to be the best choice if I am going to try SlimKat. lol
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
With "Normal" i mean the usual GApps you used (There are no need for some sort of special GApps..). Maybe "normal" can be a bit confusing.. :silly:
legolas93 said:
Glad you like this
With "Normal" i mean the usual GApps you used (There are no need for some sort of special GApps..). Maybe "normal" can be a bit confusing.. :silly:
Click to expand...
Click to collapse
Ok, yeah that is a bit confusing, or at least the way you typed it is. Kinda made it seem like there was a different version I needed to look for, lol. So, normal is just what ever Gapps package you prefer to use? In other words, they should all work? Cool, thanks legolas... :good:
adomol said:
I can verify that everything is working as advertised... Installed your modified files and am now up and running with F2FS.
I'll post if I run into anything odd.
[EDIT] Finished restoring all my apps and data. And it's blazing! Ran an ANTUTU benchmark test and scored a
14829 vs. 12726 of a stock Nexus 7!!!
And the here are the numbers for the Quadrant benchmark: 5748 vs. 3517 for stock... nice!!
Thanks again legolas!
Click to expand...
Click to collapse
only got 13840 on my cm11 nexus 7 on antutu. looking forward to more f2fs development!
brclho said:
only got 13840 on my cm11 nexus 7 on antutu. looking forward to more f2fs development!
Click to expand...
Click to collapse
Did you modify CM11 yourself to work with All-F2FS?
SkOrPn said:
Did you modify CM11 yourself to work with All-F2FS?
Click to expand...
Click to collapse
nope, normal cm11. just wanted to post a comparison to f2fs.
brclho said:
nope, normal cm11. just wanted to post a comparison to f2fs.
Click to expand...
Click to collapse
so that's the difference when all (system & data & cache) is in F2FS : 14k+ in antutu ? And a rom with just the data partition in F2FS got 13k+ ?
TarteMan said:
so that's the difference when all (system & data & cache) is in F2FS : 14k+ in antutu ? And a rom with just the data partition in F2FS got 13k+ ?
Click to expand...
Click to collapse
sorry i will clarify. i have not done f2fs conversion yet. this is stock file system (whatever it is) with cm11 antutu score.
brclho said:
sorry i will clarify. i have not done f2fs conversion yet. this is stock file system (whatever it is) with cm11 antutu score.
Click to expand...
Click to collapse
okay
but anyone can compare antutu or quadrant score between All-F2FS rom and Data-F2FS Rom ?
TarteMan said:
so that's the difference when all (system & data & cache) is in F2FS : 14k+ in antutu ? And a rom with just the data partition in F2FS got 13k+ ?
Click to expand...
Click to collapse
In real world terms, that is all the difference you need. The only other way to get your OS's file system any faster is to replace it with a real ssd. Its simple really, F2FS was made for NAND, and EXT4 was not.
Ok, before I start all over can someone tell me how long the Google logo is supposed to stay on the screen please?Its been about 20 minutes now, so I am wondering if its upgrading android in the background but just not displaying it. lol
EDIT: Ok, 45 minutes later, I am giving up. Going to do it all a second time now.
EDIT2: 1 hour later. Got it working second time around. I guess this recovery does not like flashing all kinds of things at once. Just flashed Rom and Gapps and its booting apparently. Will flash the 3rd party kernel and MoAB later.
this backup Korean firmware for twrp 2.6.3.0, first make all wipe, then restore the system folder. Now dear friends left to adjust the kernel to work memory. Who can rabotat kernel we are waiting for your help.
Downloads: https://yadi.sk/d/9llrwW9ZSAPAM
sew this boot for camera operation https://docs.google.com/file/d/0B1e6YcHvyda_UEZBNjFSdno4TFU/edit
Many thanks Paulicat for the kernel
ananasic said:
this backup Korean firmware for twrp 2.6.3.0, first make all wipe, then restore the system folder, and then the boot folder. Now dear friends left to adjust the kernel to work the camera and memory. Who can rabotat kernel we are waiting for your help.
Downloads: https://yadi.sk/d/3-3klCFfRA2Fa
Click to expand...
Click to collapse
Did you try flashing a stock JB kernel afterwords for the E970?
johnwayne007 said:
Did you try flashing a stock JB kernel afterwords for the E970?
Click to expand...
Click to collapse
does not work
ananasic said:
does not work
Click to expand...
Click to collapse
Huh, well sadly I am no good at all with kernel anything. Do you know if the kernel source was released for the Korean variant?
We will have to wait for someone to get us a modified kernel or wait for an official KK rom for E970 , because of the difference b/w other variants. "Camera/SDCard"
But thanks a lot for getting a rom though.
There's apparently enough changes between JB and KK stock kernels, and the AOSP kernel source, that we can't get working camera or SD until LG releases the kernel source.
Dont mind my inquisitiveness , but Can't we get the camera codes ported from nexus 4 ? They share the same hardware when it comes to camera module ?
I am very skeptical about any KK release for our variant. AT&T has already given the release for G Pro , if our device were to get any update at least there would have been some word about it from ATT.
Sent from my LG-E970 using Tapatalk
Rishi. said:
Dont mind my inquisitiveness , but Can't we get the camera codes ported from nexus 4 ? They share the same hardware when it comes to camera module ?
I am very skeptical about any KK release for our variant. AT&T has already given the release for G Pro , if our device were to get any update at least there would have been some word about it from ATT.
Sent from my LG-E970 using Tapatalk
Click to expand...
Click to collapse
All we need is the F180 kitkat kernel source and we'll be fine.
LG is good at releasing their sources, just give it some time.
Thanks a lot mannn, for the ROM. We will wait for the kernel modification.
KK BELIEVE THE KOREA APPEARS ON OpenSource Code Distribution
ONLY THE G IS THE PRO
https://www.lg.com/global/support/o...tegoryId=CAT00000001&osCategoryId=CAT00000002
ananasic said:
this backup Korean firmware for twrp 2.6.3.0, first make all wipe, then restore the system folder, and then the boot folder. Now dear friends left to adjust the kernel to work the camera and memory. Who can rabotat kernel we are waiting for your help.
Downloads: https://yadi.sk/d/3-3klCFfRA2Fa
Click to expand...
Click to collapse
Restoring fails on twrp 2.7.0 ... is this specific for 2.6.3.0 ??
PUT THAT ON PAGE BELOW FOUND SEVERAL THINGS TO CARRY AS A MANUAL FROM THE RON'S ROM KERNEL BUT NOT UNDERSTAND WHY THIS WELL IN RUSSIAN AND CHROME DO NOT TRANSLATE TO 100% OF SOMETHING I HOPE TO SERVE IN DEVELOPMENT
http://4pda.ru/forum/index.php?showtopic=502205
Nobody port to E970? =(
dark_nobody said:
Nobody port to E970? =(
Click to expand...
Click to collapse
Nobody read the threads? =(
Sent from my LG-GEEB using Tapatalk
already released from the kernel f180s f180k and LG
* https://www.lg.com/global/support/o...tegoryId=CAT00000001&osCategoryId=CAT00000002
LG OpenSource Code Distribution
TOTAL WEIGHT OF THE KERNEL 118 MB
WHO CAN CHANGE THE MAGIC OF THE KERNEL?
lbertking said:
already released from the kernel f180s f180k and LG
* https://www.lg.com/global/support/o...tegoryId=CAT00000001&osCategoryId=CAT00000002
LG OpenSource Code Distribution
TOTAL WEIGHT OF THE KERNEL 118 MB
WHO CAN CHANGE THE MAGIC OF THE KERNEL?
Click to expand...
Click to collapse
Kernel is badly packaged.
I emailed them to correct it.
Doesn't compile.
Paulicat said:
Kernel is badly packaged.
I emailed them to correct it.
Doesn't compile.
Click to expand...
Click to collapse
Yeah, I think JB was like that too for E970 as well, I can't remember
nygfan760 said:
Yeah, I think JB was like that too for E970 as well, I can't remember
Click to expand...
Click to collapse
JB for E971 is ok now, not sure upon initial release so you could be right.
Hopefully they fix it soon.
Hello OP,
Can you please post a link to the back up image of the boot only. My internet connection is too slow to download 1.5gb. Currently i am working on a zip. but boot looping. want to try with your kernel
Thanks in advance.:good:
could carry without the kernel or modify a kernel cm 11 for that fence watching the adjustments needed as recovery, translations of app, screen size, and go compacting the rom image of more?
porting this ROM would be easier? belongs to a f220k optimus gk
https://docs.google.com/file/d/0B57NNNkITzpjQkFOMjU4ZUhLNDQ/edit (rom)
https://docs.google.com/file/d/0B3dApvWjgNoKQWRtXzRSWW5SZlE/edit (recovery)
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=f220 (lg)
Greetings EARTHLINGS,
Thought Id have a play with the latest CM11s with F2FS with AK kernel. Works brilliantly and the whole rom feels much smoother. ART working real good (I dont suppose it will with xposed).
You need to format system, to f2fs to flash this rom as follows:
- philz recovery make this easiest
- format to f2fs system, then cache, then data and data/media
Because it easy and he always does an excellent job I used Calkulin's Stock Rooted XNPH44S as the base for this.
Anyhow, its nice to share so here it is.
here - AK75 or
here - AK77
No support, and in the event of problems its not my fault.
Have fun. and thanks ak and Calkulin for your usual brilliance.
The bad news - Please note coverting to F2FS will destroy your data, so make a full backup and copy it to your PC first.
The good news - If you are already using 44R on ext4 format
- make a full TWRP backup and copy to your PC.
- install this and any other scripts you want after you have reformatted to F2FS, philz is easiest for this step.
- copy your nandroid back to your phone
- restore your ext4 data (select only the data) to your new f2fs rom with TWRP.
HINT ABOUT RECOVERIES- I find using philz is good for the initial format, but TWRP is better for making and restoring backups. I use TWRP multirom as my daily now my OPO is converted to f2fs.
Please also note that any OTA will not work as the stock ROM is ext4. I will however update the ROM when an OTA occurs.
So this is a rom in that you put AK kernel there?
furrycurry said:
So this is a rom in that you put AK kernel there?
Click to expand...
Click to collapse
This is a rom because you flash it and your phone works
Yes it has AK075 kernel, and it uses F2FS file system.
Why not ak77?
Sent from my A0001 using XDA Premium 4 mobile app
Setting.Out said:
Why not ak77?
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1. AK75 is almost week old...
Ozonep said:
+1. AK75 is almost week old...
Click to expand...
Click to collapse
My god! A week old! Shocking!
furrycurry said:
So this is a rom in that you put AK kernel there?
Click to expand...
Click to collapse
Setting.Out said:
Why not ak77?
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Because when I did the rom, AK77 didnt exist. I have included AK 77 version now. Thanks for the heads up.
PS you can always flash AK77 over the first rom anyhow.
Mr Woolf said:
My god! A week old! Shocking!
Click to expand...
Click to collapse
It sounds more impressive when calculated in minutes.
Sent from my A0001 using XDA Premium 4 mobile app
Ozonep said:
+1. AK75 is almost week old...
Click to expand...
Click to collapse
What a strange way of looking at it. AK 075 was current yesterday I recall, less than 24 hours ago. Today its been updated to AK77. You guys should think of a career in politics.
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Can you flash this ROM without changing the file system?
Sent from my A0001 using XDA Free mobile app
rahditzz said:
Can you flash this ROM without changing the file system?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
No, Its modified version for f2fs only. And this is the only difference between this and stock C11S.
Once you go to f2fs are we able to go back and use our ext4 backups and not lose anything really want to try but want to make sure I can go back to ext4 much alohas
rahditzz said:
Can you flash this ROM without changing the file system?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
No. You have to convert to f2fs first.
otisman said:
Once you go to f2fs are we able to go back and use our ext4 backups and not lose anything really want to try but want to make sure I can go back to ext4 much alohas
Click to expand...
Click to collapse
see added content in op
Hasan_bd said:
No, Its modified version for f2fs only. And this is the only difference between this and stock C11S.
Click to expand...
Click to collapse
Sorry not correct. This has a modified boot, incorporating AK77 and the necessary changes to make it work with F2FS, so its not stock. Functionally, its the same as stock.
Also true stock is not available as a flashable rom (yet), so rather than re-invent the wheel, I used Calkulin's 44R flashable rom as a base. As I understand it, this is stock apart from the necessary changes to make it a flashable version, along with SU being provided and not installing stock recovery.
zaphodbeeb said:
Sorry not correct. This has a modified boot, incorporating AK77 and the necessary changes to make it work with F2FS, so its not stock. Functionally, its the same as stock.
Also true stock is not available as a flashable rom (yet), so rather than re-invent the wheel, I used Calkulin's 44R flashable rom as a base. As I understand it, this is stock apart from the necessary changes to make it a flashable version, along with SU being provided and not installing stock recovery.
Click to expand...
Click to collapse
Yeah..I understand, actually I am also a fan of f2fs system and using CrDroid in f2fs system with tyr kernel. But the thing is apart from kernel and updater script, there is no visible difference in both roms and technical terms make someone really difficult to understand whats going on.
Anyway, keep up the good work. I faced some problems with AK Kernel while incorporating with CrDroid f2fs but now I will give another try :laugh:
Hasan_bd said:
Yeah..I understand, actually I am also a fan of f2fs system and using CrDroid in f2fs system with tyr kernel. But the thing is apart from kernel and updater script, there is no visible difference in both roms and technical terms make someone really difficult to understand whats going on.
Anyway, keep up the good work. I faced some problems with AK Kernel while incorporating with CrDroid f2fs but now I will give another try :laugh:
Click to expand...
Click to collapse
Cool,
Let me know when you have done it and Ill help test it. Multirom is a marvellous thing, and what the heck, one more rom isnt going to make any difference. Im permanently connected to my OPO and PC anyhow.
Flashed it yesterday. Working great so far.
Thanks a lot!
I flashed today, works everything except I haven't root. I have to flash supersu in recovery?
EDIT: yes, flashing through recovery works.
I have made a kernel for stock Cyanogen OS12 with the touchscreen firmware fix and the hardboot patch (So you can use the stock rom as primary rom in multirom)
I have attached 2 file types.
The .img files to flash it with fastboot or an kernel flasher app.
The .zip files to flash it with a custom recovery
Here is a Video from savadam How to install the kernel in the recovery.
In the youtube video description you will also find howto unlock the bootloader and install a custom recovery
Update:
Kernel V2 is attached with a modified Ramdisk to fix the not working Settings-display
Update2:
The touchsreen fix is causing an 30mA higher battery drain if double tap to wake is enabled. I can life with it, but if for you the drain is to high you should disable double tap to wake in settings-display.
As soon as a new fix is finish I will provide a new kernel
Update3:
Kernel V3 with the new fix which seems to fix the touchscreen problems without causing an higher battery drain http://review.cyanogenmod.org/#/c/99607/
Update4:
Kernel V4 with fixed Sunlight Enhancement
Update5:
Kernel for CM11s XNPH05Q added
Update6:
Kernel for CM11 M11 Snapshot/Nightly added
Sources: https://github.com/bauner/android_kernel_oneplus_msm8974
Anyone tried this and can confirm it is working?
Sent from my A0001 using XDA Free mobile app
nitramcek said:
Anyone tried this and can confirm it is working?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I would not post it here if it would not work...
I use this kernel since a few weeks on the stock cos12 and since friday with the touchscreen fix.
Hardboot/Multirom support is also tested and working
Kernel V2 is attached in the first post with a modified Ramdisk to fix the not working Settings-display
@bauner it works great, I thought I had no issues, now I can touch even lighter
dev_freak said:
@bauner it works great, I thought I had no issues, now I can touch even lighter
Click to expand...
Click to collapse
Since end of december
bauner said:
Since end of december
Click to expand...
Click to collapse
Nice, I love this phone and I had touch issues, which I didn't knew, now I can touch my screen very light.
confirmed that its working perfectly and my phone is flying
does it work on stock cm12s
chiujiewei said:
does it work on stock cm12s
Click to expand...
Click to collapse
It is made for the stock cyanogen os 12
i already have cm12s as my primary rom and miui6 as my scondary rom in multirom.
will flashing the boot zip for my cm12s conflict multirom?
What about the battery life? Any experience? I flashed FC which fixed the touchscreen issue, but worsened the battery life.
ovanitas said:
What about the battery life? Any experience? I flashed FC which fixed the touchscreen issue, but worsened the battery life.
Click to expand...
Click to collapse
Kernel is stock m8 as described in the topic its been compiled from latest cm stock sources so its the same as stock cm12s.
chiujiewei said:
i already have cm12s as my primary rom and miui6 as my scondary rom in multirom.
will flashing the boot zip for my cm12s conflict multirom?
Click to expand...
Click to collapse
No it will not conflict. just boot into recovery and go to install-choose the kernel and make sure that Inject MultiRom after installation is checked
bauner said:
No it will not conflict. just boot into recovery and go to install-choose the kernel and make sure that Inject MultiRom after installation is checked
Click to expand...
Click to collapse
is kernel same version as 12s?
tsimitsangaz said:
is kernel same version as 12s?
Click to expand...
Click to collapse
It is built from the latest cm12.0 sources with the stock cos12.0 YNG1TAS17L ramdisk
bauner said:
It is built from the latest cm12.0 sources with the stock cos12.0 YNG1TAS17L ramdisk
Click to expand...
Click to collapse
is it possible to compile the same kernel with the touchscreen driver and without MultiRom support?
tsimitsangaz said:
is it possible to compile the same kernel with the touchscreen driver and without MultiRom support?
Click to expand...
Click to collapse
It would be possible but it will not make any differences, because the hardboot patch does nothing if you don't have multirom installed
Video based on this Thread
For those who are interested, here some videos regarding this beautiful rom,
Thank me if i helped you.
Lmao I feel bad for bauner. So many posts asking the same thing pretty much. [emoji12] [emoji32]
Sent from my A0001 using Tapatalk
Just for fun, I compiled an optimized version of stock kernel for Marshmallow 6.0
It works with stock ROM for Moto X Pure XT1575, not tested with anything else.
Current features:
Compiled with O3
Uber toolchain
misc gcc optimization flags
KCAL
TCP congestions
Source code:
https://github.com/vadimtk/moto-x-kernel-6.0
Based on source
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-MPH24.49-18
Download link
V5:
Changes:
Updated to Kernel 3.10.94, thanks to https://github.com/Nimrodsv
XT1575:
https://www.androidfilehost.com/?fid=24345424848487596
XT1572:
https://www.androidfilehost.com/?fid=24345424848487595
V3:
Changes:
Couple SSD/flash related optimizations
XT1575:
https://www.androidfilehost.com/?fid=24343351889232014
XT1572:
https://www.androidfilehost.com/?fid=24343351889232056
V2:
https://www.androidfilehost.com/?fid=24341993505161414
How to use:
1. Download and unpack
2. Reboot to bootloader:
Code:
adb reboot bootloader
3. Boot temporary with new kernel (active till next reboot):
Code:
fastboot boot v4tk-opt-V2.img
or flash permanently:
Code:
fastboot flash boot v4tk-opt-V2.img
XDA:DevDB Information
V4TK Kernel, Kernel for the Moto X Style (Pure)
Contributors
VadimTk
Kernel Special Features:
Version Information
Status: Beta
Created 2015-12-24
Last Updated 2015-12-23
Damn that was fast okay I'm installing it now. I'll be the test dummy for TruPureX users. Thanks for your hardwork its very appreciated
also OT. woot 123 posts
---------- Post added at 02:09 AM ---------- Previous post was at 02:02 AM ----------
Works great on TruPureX it's just very bare bones at the moment. Still great job! I can not wait to see more from you tanks again for being awesome
Thank you for this!
sweet! vadim is back will flash later
patt2k said:
sweet! vadim is back will flash later
Click to expand...
Click to collapse
If your running TruPureX your going to be happy by the speed up
I tried flashing this in TWRP and get a failed message. md5 checks out. Any suggestions?
btafoya said:
I tried flashing this in TWRP and get a failed message. md5 checks out. Any suggestions?
Click to expand...
Click to collapse
Its not a flashable zip. You need to extract it before flashing. Flash as an image file in TWRP and select boot
^^^ yes, and/or try using flashify or rashr after unzipping
I have the traditional root using rooted boot and super SU in system. Is this boot.img pre rooted?
countryfolk07 said:
I have the traditional root using rooted boot and super SU in system. Is this boot.img pre rooted?
Click to expand...
Click to collapse
the boot.img does not control root. The only thing that would effect this for would maybe be the SR build as that hooks into the kernal. traditional dosent hook into the kernal. He is reverting to traditional soon.
WelcomeToTheSkye said:
If your running TruPureX your going to be happy by the speed up
Click to expand...
Click to collapse
I had it,using Sabissimos rom and so far so good.
Sent from my XT1575 using Tapatalk
I flashed this on a rooted, deodoxed 6.0 and dang.. My phone is so snappy now. Thank you!
WelcomeToTheSkye said:
the boot.img does not control root. The only thing that would effect this for would maybe be the SR build as that hooks into the kernal. traditional dosent hook into the kernal. He is reverting to traditional soon.
Click to expand...
Click to collapse
If the boot partition isn't flashed as rooted you will bootloop if superSU is installed. When I first took OTA I had to flash a rooted boot.img to get root without bootlooping. I can remember off hand who created the image, but this is why I ask.
VadimTk said:
Source code:
https://github.com/vadimtk/moto-x-kernel-6.0
Click to expand...
Click to collapse
Very nice Vadim
Please remove the "http://" on the url part for this link.
Might be a good idea to note that in the OP @VadimTk. Thanks!
Sent from my XT1575 using Tapatalk
Sir can i install this kernel on non rooted pure style
@VadimTk
please make an xt1572 version compatible, this version don't work on style, every app FC at start.
thanks
happy xmas
fdc77 said:
@VadimTk
please make an xt1572 version compatible, this version don't work on style, every app FC at start.
thanks
happy xmas
Click to expand...
Click to collapse
Did you wipe dalvik/cache?if it truly didn't work on the xt1572 either WiFi or RIL would be broken.
yes, wiped cache and dalvik but no luck, wifi and ril seems to be broken but i don't know for certain because phone was unusable
fdc77 said:
yes, wiped cache and dalvik but no luck, wifi and ril seems to be broken but i don't know for certain because phone was unusable
Click to expand...
Click to collapse
Ah okay then yes it is incompatible lol sorry for doubting