Back story:
I bought a Moto X during the $100 off promotion and while I was waiting for it to be delivered, I read reviews and poked around online for interesting things about the phone. As an 8GB Nexus 7 owner, the one thing that caught my eye the most was this section of the Anandtech review discussing internal storage performance. Considering how badly my N7's storage performance degraded and how unbearably slow it has become, I felt like it could make good use of this "flash friendly file system." Some Googling revealed that the F2FS driver was developed by Samsung and actually contributed to the official kernel, where it was implemented somewhere around 3.8. I've done some development for an HTC phone in the past, but never for the Nexus 7, so I went and researched the kernel. Because Google's Tegra 3 kernel is based on 3.1, I had to start working on backporting the driver, when I discovered this repository of backports for F2FS. It provides patches for 3.0 and 3.2, but not for 3.1, so I manually applied appropriate changes from each. When I flashed the kernel and booted, it seemed to work, so I went ahead and injected the kernel into the latest TWRP image as well. I also modified the fstab for both the recovery and ROM and compiled Cyanogenmod's f2fs-tools for Android and statically linked them before injecting them into TWRP as well. I then booted into recovery, formatted /data (TWRP knew to use mkfs.f2fs), and booted back into Android. Success, it worked! I've been using my Nexus 7 like this since Friday evening and it's been so much more usable. Not perfectly "like-new" smooth, but it doesn't hang as often or as long.
I haven't seen anyone actually try this yet so I'm hoping my effort will be able to make a difference for N7 owners fed up with slow performance. Switching to f2fs is as easy as flashing a modified kernel and recovery, then doing a factory reset. Also, any interested developer is more than welcome to use anything I post here.
Basically, I took the official Tegra 3 kernel and did this:
KERNEL PATCH
Then modified the stock ROM's fstab like this:
FSTAB
Then I gave TWRP statically-linked f2fs-tools binaries:
F2FS-TOOLS
Then I reformatted /data and away it went:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm going to reboot into Linux and attach my boot/TWRP images for you guys to test out. Until then, I'd love to have some feedback.
What do you think about using f2fs on the Nexus 7?
Is it worth it?
What kind of impact on performance or battery life do you think this will have?
Did I do something seriously wrong with my kernel/fstab?
Am I absolutely insane and dangerous to everyone's Nexus 7 tablets and their puppies?
Image Downloads
Android File Host | Google Drive
Instructions:
WARNING: This process obviously will wipe your data. Make a NANDroid backup beforehand and save it to your computer. While I personally use this, I take no responsibility for damage done to your device.
Flash boot and recovery like usual:
Code:
$ fastboot flash boot boot-F2FS.img
$ fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper-F2FS.img
Format Data in TWRP
Reboot
Done!
Note that these are for the latest official 4.4.2 build KOT49H.
Let me know how your performance and battery life change after applying this. Storage performance should noticeably increase and battery life change should be negligible.
Excellent, hope you'll get around and do it for rest of the Nexus line too (greetings from Reddit). :]
This actually looks pretty interesting. Do you have any benchmark result?
I hope some of the kernel devs around here will pick up your idea.
The kernel devs can integrate the kernel patch and the fstab patch to some extent but definitely not the recovery patch. I'm going to try this tomorrow or the day after.
Great work.
Excellent idea - I'm highly interested in the results. My 2012 N7 is starting to look quite pokey alongside my N5, so if this provides an improvement I'm all over it.
madd0g said:
Excellent, hope you'll get around and do it for rest of the Nexus line too (greetings from Reddit). :]
Click to expand...
Click to collapse
Unless I get distracted, the plan is to do this for the Nexus 4. My goal is to expose this sort of thing to existing developers and let them handle the logistics. I've always been terrible about sticking to a project.
Erovia said:
This actually looks pretty interesting. Do you have any benchmark result?
Click to expand...
Click to collapse
Not yet. This is what I had to sat about benchmarks in the Reddit thread:
ss2man44 said:
The only problem is that the Nexus 7 performs at its worst after the media has been used for a while and filled with data. I'm hoping others will provide their experiences under these conditions, but if need be, I'll do some benchmarks of my own when I have time.
Click to expand...
Click to collapse
sgt. meow said:
The kernel devs can integrate the kernel patch and the fstab patch to some extent but definitely not the recovery patch. I'm going to try this tomorrow or the day after.
Great work.
Click to expand...
Click to collapse
This is exactly what I hoped for when I posted this. Kernel developers can merge this patch and if it gains enough attention, perhaps conventions could be established around specifying which filesystem a kernel/recovery is designed for. Built-from-source recoveries with F2FS support would be nice as well.
ss2man44 said:
Unless I get distracted, the plan is to do this for the Nexus 4. My goal is to expose this sort of thing to existing developers and let them handle the logistics. I've always been terrible about sticking to a project.
Not yet. This is what I had to sat about benchmarks in the Reddit thread:
This is exactly what I hoped for when I posted this. Kernel developers can merge this patch and if it gains enough attention, perhaps conventions could be established around specifying which filesystem a kernel/recovery is designed for. Built-from-source recoveries with F2FS support would be nice as well.
Click to expand...
Click to collapse
The patch applied cleanly (the second time I've ever seen a patch do that). Good job.
I'll compile and flash to see if it boots (there are issues with my kernels) and if all goes well I'll switch completely to F2FS.
sgt. meow said:
The patch applied cleanly (the second time I've ever seen a patch do that). Good job.
I'll compile and flash to see if it boots (there are issues with my kernels) and if all goes well I'll switch completely to F2FS.
Click to expand...
Click to collapse
Well it booted on one ROM that has no issues with SELinux and the other didn't boot although the same config without F2FS boots fine. Strange.
Sent from my Nexus 7 using Tapatalk
OMG
At first when I tried this I wasn't expecting this great deal of performance just by a file system change but boy was I wrong
The benchmark aren't higher but the the system performance is quite noticeable when using
This combines with FSync Off and nexus 7 will be flying
f2fs implementation on the note2 and s3 on all partitions: kernel & recovery and a compatible rom for the s3...perhaps you might get some help from those devs. using it on my s3 and the performance has been great. not entirely sold on benchmarks but on ext4 i was getting 14-15k on antutu. w/ f2fs on the same cpu/gpu speeds, i'm getting 18-19k. HTH
would really like to see this implementation on our beloved n7
maxq1 said:
f2fs implementation on the note2 and s3 on all partitions: kernel & recovery and a compatible rom for the s3...perhaps you might get some help from those devs. using it on my s3 and the performance has been great. not entirely sold on benchmarks but on ext4 i was getting 14-15k on antutu. w/ f2fs on the same cpu/gpu speeds, i'm getting 18-19k. HTH
would really like to see this implementation on our beloved n7
Click to expand...
Click to collapse
Using it on all partitions is very trivial and doesn't need any more kernel modifications. I just limited it to /data/ because that's what Motorola did and it seems to work very well for them. I also didn't know whether or not it would cause any problems in the long run.
Feedback
1. What do you think about using f2fs on the Nexus 7?
2. Is it worth it?
3. What kind of impact on performance or battery life do you think this will have?
4. Did I do something seriously wrong with my kernel/fstab?
5. Am I absolutely insane and dangerous to everyone's Nexus 7 tablets and their puppies?
Click to expand...
Click to collapse
1. It's about time I ditch ext4!
2. it doesn't matter, you're learning new stuff:highfive:
3. Only the benchmark wil tell the troth
4. why did you add discard? doesn't android automaticlly trim partitions?
alifa said:
1. It's about time I ditch ext4!
2. it doesn't matter, you're learning new stuff:highfive:
3. Only the benchmark wil tell the troth
4. why did you add discard? doesn't android automaticlly trim partitions?
Click to expand...
Click to collapse
Bro benchmarks show no real world performance only the raw power of the device.
buggatti said:
OMG
At first when I tried this I wasn't expecting this great deal of performance just by a file system change but boy was I wrong
The benchmark aren't higher but the the system performance is quite noticeable when using
This combines with FSync Off and nexus 7 will be flying
Click to expand...
Click to collapse
Do you mind sharing your results.. perhaps with a youtube video? I'm highly interested in trying _anything_ that might speed up my 2012 Nexus 7.
TWRP 2.7 has released. Any chance we could get a F2FS modified version of it please? Version 2.6.3.1 isn't working on my Nexus 7 and I downloaded it twice now. Just stays at the splash screen forever.
Next logical step is formatting system in F2FS format and see if its worth it.
Sent from my Nexus 4 using Tapatalk
Still planning to release this for nexus 4?
Can fstab be copied from a ROM that is already using f2fs to a rom that is not using f2fs? Or is this something that needs to be coded properly and built normally on a linux machine?
I just want to have /data formatted to f2fs (maybe even /cache). My /data partition is already f2fs, but the ROM I want does not support it, so I am sure it would not boot until I can modify fstab.
SkOrPn said:
Can fstab be copied from a ROM that is already using f2fs to a rom that is not using f2fs? Or is this something that needs to be coded properly and built normally on a linux machine?
I just want to have /data formatted to f2fs (maybe even /cache). My /data partition is already f2fs, but the ROM I want does not support it, so I am sure it would not boot until I can modify fstab.
Click to expand...
Click to collapse
fstab is part of the ramdisk in the boot.img. You would need the fstab file and a f2fs supported kernel for it to work with the other rom. Have you tried just flashing the boot.img-f2fs from OP?
HypoTurtle said:
fstab is part of the ramdisk in the boot.img. You would need the fstab file and a f2fs supported kernel for it to work with the other rom. Have you tried just flashing the boot.img-f2fs from OP?
Click to expand...
Click to collapse
Um no I haven't. I did try and use osmosis's kitchen and I swaped the fstab for the correct one. I was going to just edit it with my favorite notepad program but decided I wasn't sure I'd get it right.
It did not work. Not sure why.
Sent from my Nexus 7 using Tapatalk
Related
INTERACTIVE DATA2SD MOD
There are a lot of ways of moving /data to SD ext(2nd) partition. Here I'll show you an easy way to do it which is fully compatible with Optimus One(and possibly other devices as well). If you don't like the method used here, try other Data2SD/ext mod which may suit your needs, but please, don't hesitate to post your feedbacks/comments be it negative or positive (feedbacks/comments are highly appreciated).
The mod, as the title says, moves the whole /data partition to your SDcard's 2nd(ext) partition, which could give you virtually unlimited space to install apps and also boost quadrant scores. I have tested this with EXT2(and can get up to 900+ on quadrant with stagefright off or 2000 with stagefright on, OC'd to 787mhz with I/O score playing around 4000 - 5000+), so if you're using other FileSystems, please do post your feedbacks and possibly your I/O scores as well. I have also enforced an e2fsck on every boot which is useful for ext2 users as this will check and fix your 2nd partition for errors on every boot, if there's any.
Dalvik2cache temporarily unavailable with v4b5. A new version with the option to move dalvik-cache almost anywhere possible is coming up. If you still want to use the dalvik2ram mod, try v1.2(link at the bottom).
Why move dalvik-cache to RAM? Basically, the idea of moving the whole /data partition to SD ext partition is to primarily get more space for installing apps. And in this case, it does perform very well and combined with fast SD cards, it could even provide real-life performance boost. Now the downside to this, is that while most /data contents just get copied and read not that much often, dalvik-cache stores some info that needs to be read and updated very frequently. This results in a high I/O read/write frequency and thus results in shortening of the SD card life(in theory, the same could also be said when left internally but this time dealing damage to the nand disk instead). To counter this, the method I used is to move dalvik-cache to a virtual-disk like partition known as a tmpfs. tmpfs resides in RAM and has dynamic resizing structure which can allocate space depending on your needs. This way, dalvik-cache won't be using any physical disk and therefore causing damage to none. Almost too good to be true right? Well the drawback is, because tmpfs resides in RAM anything written onto it get's lost when rebooted or in-case of power loss thus resulting in loooong boot times(depending on the apps installed), as dalvik-cache contents are being rebuilt on every boot. Well I think that's enough of dalvik-cache and lets start with the mod.
WARNING
USING A NON-APP2SD ROM OR SIMPLY UNINSTALLING APP2SD IS STRICTLY RECOMMENDED
DO NOT EVEN TRY THIS MOD IF YOU HAVE ANY FORM OF APP2SD INSTALLED
ALWAYS PERFORM A BACKUP BEFORE TRYING OUT STUFF LIKE THESE
Disclaimer: I am not responsible for anything bad happening to the world blah blah, you know the drill!
INSTALLATION
An SD card with at least two partitions required.(First partition as FAT32 for regular SD use and second partition as EXT2(EXT3 and EXT4 will be supported on future builds)
1. Download Data2sd_v4b5.zip here!(latest stable build)
2. Flash via recovery
(testers WANTED, preferably using different ROMs.)
Test release can be found here!!!!!
QUADRANT TEST RESULT:
This mod is still on-going and still under development. Although it's already fully functional, some features or options may still be added later-on. Please post your feedbacks and give thanks if you can.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To disable DarkTremor's app2sd, just follow these steps
Ungaze_Data2sd_v1_2.zip(archive)
Code:
#Data2Sdext_Dalvik-cache2RAM
#
#By: Ungaze
#
#Credits:
#uncorrupted for original script for a wide variety of devices
#sibere and ownhere for additional resources
#pomka78 for dalvik-RAM script and Idea
#nervgaz, franciscofranco, andy572 and joesephmother for ideas and suggestions.
#all the testers and everyone who provided feedbacks on this mod. Thanks to you guys.
#
Can this be used with mik's CM7 beta6.1 rom ?
TIA
Very nice job! I will try it asap.
Attached the edify signed version (Clockworkmod 3 ). It installs just fine.
@hell1134: I think it should work on any rom that obeys the prerequisites and that are properly explained by ungaze (no apps2SD script installed or if it is something just uninstall in order to try this).
hell1134 said:
Can this be used with mik's CM7 beta6.1 rom ?
TIA
Click to expand...
Click to collapse
Should work with any non-app2SD Optimus One ROM on the fly. Make a backup first.
The script works fine. I tested it on Mik's beta 6.2. The only issue I have seen is with the themes. Even though a theme is selected, it defaults to the System one and since I could not find a way to do a hot reboot I couldn't properly apply my desired theme.
I have the other dalvik cache script running right now. You talk a lot about improving the life of the device/sd and saving space for apps. Is there no performance gains with doing this?
Sent from my LG-P500 using XDA Premium App
Momaro said:
I have the other dalvik cache script running right now. You talk a lot about improving the life of the device/sd and saving space for apps. Is there no performance gains with doing this?
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Personally, I don't find any huge/noticeable gain on any mod I have done with O1 this is because O1 is already super fast as it is, and it's a good thing. But if you're the kind of person who measures performance based on benchmark's, then data2sd will give you huge I/O performance gain(specially in quadrant). On the other hand, dalvik-cache2ram is purely for disk preservation only. Not much gain here.
regarding themes on miks CM7 6.2. I really don't have the slightest idea on what's happening with your themes. Maybe its in the way that CM implements themes? I reallt don't know as themes reside in the /system partition which should not be affected by the scripts that I have made.
I personally haven't seen any performance benefits. Anyway as I think about it the sdcard way is more preferably for me since I would never use one with a lesser class than 6.
@ungaze: Only the default themes (System, Androidian and Cyanbread) are in /system
marioemp2k7 said:
The script works fine. I tested it on Mik's beta 6.2. The only issue I have seen is with the themes. Even though a theme is selected, it defaults to the System one and since I could not find a way to do a hot reboot I couldn't properly apply my desired theme.
Click to expand...
Click to collapse
May be pasting your desired theme to system/app and removing the current default will help. Then even after reboot default will be your drsired theme.
Sent from my LG-P500 using Tapatalk
I don't think it will help me since the question is about T-Mobile Theme Manager settings. I don't know where these are saved but it is pretty obvious that there are not in the right place since everything defaults to the System theme.
Edit: I have managed to make Hot Reboot (Quick Boot Plus) work so now I have the themes working properly since I can restart only the UI.
I will stick to this for now.
one question :: is the phone really fast with data partition on sdcard's ext2 partition ??? anybody using it please give your inputs: Also How do i use this along with darktremor's a2sd ??? i just want data2sd not dlcache2ram
I haven't used ext2 partition but I can tell you about 3 and 4. Theoretically, performance wise ext2 should be as fast as ext4 the only major difference being that the latter is a journaled fs.
In practice you will not see too much difference between the 3 of them on this phone.
I have used mostly ext4 and I am happy with it. Once the phone boots it adds a little waiting time to actually be ready (5-10 secs for me).
For the second part, I don't think it's feasible to use both. Instead you can use the original script by pomka78 and disable darktremor's dalvik script from (a2sd nocache).
sarfaraz1989 said:
is the phone really fast with data partition on sdcard's ext2 partition ???
Click to expand...
Click to collapse
I'd tried app2sd with microSD Class 4 and now I can say that for scheme "[email protected], [email protected]" ext2 is faster than ext3, and ext4 is a waaay faster than ext3. This scheme is very useful and most of the time it is as fast, as "[email protected]" due to Dalvik cache is on nand. The scheme "(data&Dalvik)@Ext" with slow cards is almost useless because of the lags.
But of course it's better to use Class10
marioemp2k7 said:
I haven't used ext2 partition but I can tell you about 3 and 4. Theoretically, performance wise ext2 should be as fast as ext4 the only major difference being that the latter is a journaled fs.
In practice you will not see too much difference between the 3 of them on this phone.
I have used mostly ext4 and I am happy with it. Once the phone boots it adds a little waiting time to actually be ready (5-10 secs for me).
For the second part, I don't think it's feasible to use both. Instead you can use the original script by pomka78 and disable darktremor's dalvik script from (a2sd nocache).
Click to expand...
Click to collapse
Ext2 is the fastest one because of no journalism.
Anyway this script works awesomely good. With a class 4 card my phone flies like it never did and I don't understand how anyone can say that it lags.
how was the quadrant score, cant try it right now, i need to buy new sd card, any brand recomendation?
cmangalos said:
how was the quadrant score, cant try it right now, i need to buy new sd card, any brand recomendation?
Click to expand...
Click to collapse
I can push 2050 in Quadrant Advanced with 3650 for i/o.
Hi, I finally flash a rom with init.d enabled. Now I have franciscofranco scripts. But something went wrong when I flashed Data2SD + Dalvik-cache2RAM...
lerkin said:
Hi, I finally flash a rom with init.d enabled. Now I have franciscofranco scripts. But something went wrong when I flashed Data2SD + Dalvik-cache2RAM...
Click to expand...
Click to collapse
It's written in capital letters
Do you have A2SD script? You need a non-a2sd rom
kite86 said:
It's written in capital letters
Do you have A2SD script? You need a non-a2sd rom
Click to expand...
Click to collapse
Yes I have rom without it.
I installed franciscofranco first, and everything was fine.
After it I flashed that script, android was starting for 5 minutes and after that it hanged up, I removed battery, started again and there were constant force closes of titanium backup, launcherpro and some android processes.
I tried to install only that Data2SD + Dalvik-cache2RAM script on fresh rom. It started, when it hanged on "preparing SD", after restart everything was fine, there was about 400 mb of free rom.
Interesting... Are those two scripts compatible?
if im using darktremors a2sd i need to reflash my rom? do everything from beggining?
This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
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.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
Prerequisites
Code:
1. A Mako/Grouper
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[URL="http://forum.xda-developers.com/showthread.php?t=2678140"]http://forum.xda-developers.com/showthread.php?t=2678140[/URL]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Single script for both Nexus 4/ Nexus 7 ( 2012)
6. Error conditions at many places so a noob cant go wrong
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM
Instructions
Code:
1. Unpack the Zip file you downloaded from Link Below
2. Run F2FS Convertor.bat
3. Select your device
4.Place the Zip in the Extract /Input directory when prompted
5. The script will Unpack your ROM
6. Select option 11 for boot.img supplied with the script or option 12 for cm boot.img and 13 for any other F2FS compatible boot.img
7. Repack your ROM
8. Check NEW F2FS ROM directory for the Repacked ROM
9. Flash and Enjoy
10.Cleanup the working directory cleanup.bat
Download Links
1) English
2) German (Thanks to @mikaole)
Changelog
Code:
V1 : Initial Release
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work
Reserved
Lol where were you weeks ago when we needed you most? Thanks for this work, but I wish I had something to flash just to try it. Right now SlimKat is working wonderfully as is.
Thanks for doing this for the community. [emoji106]
Sent from my Nexus 7 using Tapatalk
SkOrPn said:
Lol where were you weeks ago when we needed you most? Thanks for this work, but I wish I had something to flash just to try it. Right now SlimKat is working wonderfully as is.
Thanks for doing this for the community. [emoji106]
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
All the best things, take time to come
SkOrPn said:
Lol where were you weeks ago when we needed you most? Thanks for this work, but I wish I had something to flash just to try it. Right now SlimKat is working wonderfully as is.
Thanks for doing this for the community. [emoji106]
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Its just 3 weeks ago things started to build up for f2fs for mako !! I created this script primararily for my Mako dont own a grouper !! Took me two weeks to polish the script !! Basically wanted to make kernels compatible too but after trying hard had to give it up !!
Do I get this right: I can use this script to convert the latest CM 11 nightly to F2FS compatibility? And what if the kernel changes in the nightly? Has the included kernel the fixes for the recently changed ram disk?
NABENDU1 said:
Its just 3 weeks ago things started to build up for f2fs for mako !! I created this script primararily for my Mako dont own a grouper !! Took me two weeks to polish the script !! Basically wanted to make kernels compatible too but after trying hard had to give it up !!
Click to expand...
Click to collapse
I was just poking fun at ya, nothing rude was intended. I am very happy to see something like this take place. Now we have something to do the next time our favorite ROM gets released.
We just need about 100 more devices to get supported and this may take off with the manufacturers themselves. Then I will consider all smart devices up to that point one large 10 year long beta test. Lmao
Sent from my Nexus 7 using Tapatalk
So this won't work on the Galaxy Note II ...... wish it would lol
master.peterm said:
So this won't work on the Galaxy Note II ...... wish it would lol
Click to expand...
Click to collapse
If you can link me to its thread which can make it fully f2fs compatible I'll be more than glad to help !!
SkOrPn said:
I was just poking fun at ya, nothing rude was intended. I am very happy to see something like this take place. Now we have something to do the next time our favorite ROM gets released.
We just need about 100 more devices to get supported and this may take off with the manufacturers themselves. Then I will consider all smart devices up to that point one large 10 year long beta test. Lmao
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I had no hard feelings or stuff on you or anybody !! Just that wanted to inform you about why my script was released so late !! And ya that's exactly my intention to make flashing Roms easy !! I mean changing manually isnt always gr8 especially when you flash on a daily basis like I do
edisso10018 said:
Do I get this right: I can use this script to convert the latest CM 11 nightly to F2FS compatibility? And what if the kernel changes in the nightly? Has the included kernel the fixes for the recently changed ram disk?
Click to expand...
Click to collapse
No idea I don't own a grouper so I don't test it at all !! @USBhost gave this boot.img to me and I included it in my script !! I think he could explain this better
Hey, I've been trying to troubleshoot for about 30 minutes but I simply cannot get the script to repack the ROM.
Here are the issues I'm running into:
1) When I am instructed to place the original ROM zip in EXTRACT/INPUT there is no INPUT subfolder.
That was easy enough though. I simply made one, placed the zip in, and everything seemed to move forward fine.
However:
2) During repacking, the script runs into a few errors. Rather than describing them here, I will post pictures of them below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The end result:
I can't find a repacked ROM in any of the folders or subfolders.
Any ideas about where I went wrong?
Note this does not convert the kernel to f2fs you have to flash a custom All-F2FS kernel
Oh, I thought it did that? Can we please have that included into this script? Just put your favorite f2fs kernel into a folder and let it include it into your new f2fs rom? That would be nice...
SkOrPn said:
Oh, I thought it did that? Can we please have that included into this script? Just put your favorite f2fs kernel into a folder and let it include it into your new f2fs rom? That would be nice...
Click to expand...
Click to collapse
If I get some time, I may try to put together a bat file to do this. Should be able to just extract both zips, merge the kernel library modules into the system folders in the ROM zip, and replacing the boot image. The whole system folder gets extracted recursively so the kernel files go with it, and zip it back up. This program fixes the updater-script.
Sent from my SCH-I545 using Tapatalk
icarianecho said:
Hey, I've been trying to troubleshoot for about 30 minutes but I simply cannot get the script to repack the ROM.
Here are the issues I'm running into:
1) When I am instructed to place the original ROM zip in EXTRACT/INPUT there is no INPUT subfolder.
That was easy enough though. I simply made one, placed the zip in, and everything seemed to move forward fine.
However:
2) During repacking, the script runs into a few errors. Rather than describing them here, I will post pictures of them below.
The end result:
I can't find a repacked ROM in any of the folders or subfolders.
Any ideas about where I went wrong?
Click to expand...
Click to collapse
Its not that you went wrong it's my script which is calling the wrong directories !! I had faced the same problem with my mako script in its early days but after changing a few things here and there it was gone !! Bdw I'll hook you up to a test script hopefully by today evening and I think you should be good to go
Edit : Others report it as working !! Might be you doing something wrong on your end ! Bdw you should extract all my folders in d F2FSROMCONVERTOR folder !! Name change or anything will effect the script to through errors
And ya the v3 test version is d same as the released version as far as I remember
NABENDU1 said:
Its not that you went wrong it's my script which is calling the wrong directories !! I had faced the same problem with my mako script in its early days but after changing a few things here and there it was gone !! Bdw I'll hook you up to a test script hopefully by today evening and I think you should be good to go
Click to expand...
Click to collapse
I tired a bit different method but was not working for me !! Tried android image kitchen to extract the boot.img made a compatible zImage of my kernel and copied the modied zImage to that of the unpacked boot.img from android image kitchen !! Then changed the fstab and repacked but the same still won't boot !!
If you can help me get this working with kernels I'll be much more happy
NABENDU1 said:
I tired a bit different method but was not working for me !! Tried android image kitchen to extract the boot.img made a compatible zImage of my kernel and copied the modied zImage to that of the unpacked boot.img from android image kitchen !! Then changed the fstab and repacked but the same still won't boot !!
If you can help me get this working with kernels I'll be much more happy
Click to expand...
Click to collapse
That's exactly what I tried
---------- Post added at 01:42 AM ---------- Previous post was at 01:32 AM ----------
I wonder if you just replaced the boot.IMG from the ROM with the kernel's boot.img
Would that boot
---------- Post added at 02:03 AM ---------- Previous post was at 01:42 AM ----------
It works!!! Cheer !!
Amazing tool lml
Enviado desde mi Nexus 7 mediante Tapatalk
Carbon ROM 4/24/2014 with the M-kernel
---------- Post added at 04:01 AM ---------- Previous post was at 03:29 AM ----------
icarianecho said:
Hey, I've been trying to troubleshoot for about 30 minutes but I simply cannot get the script to repack the ROM.
Here are the issues I'm running into:
1) When I am instructed to place the original ROM zip in EXTRACT/INPUT there is no INPUT subfolder.
That was easy enough though. I simply made one, placed the zip in, and everything seemed to move forward fine.
However:
2) During repacking, the script runs into a few errors. Rather than describing them here, I will post pictures of them below.
The end result:
I can't find a repacked ROM in any of the folders or subfolders.
Any ideas about where I went wrong?
Click to expand...
Click to collapse
F2FSROMConvetorV3
this one works for me
I tried using this tool to build a omni verison and a cyanogenmod version, both the latest nightly. On each build I get the message " Type Password to Decrypt ..."
Also the recovery provided does not boot up after flashing it using fastboot. The recovery from http://forum.xda-developers.com/nexus-4/orig-development/recovery-rom-kernel-f2fs-05-04-14-t2706825 is working
joefso said:
I tried using this tool to build a omni verison and a cyanogenmod version, both the latest nightly. On each build I get the message " Type Password to Decrypt ..."
Also the recovery provided does not boot up after flashing it using fastboot. The recovery from http://forum.xda-developers.com/nexus-4/orig-development/recovery-rom-kernel-f2fs-05-04-14-t2706825 is working
Click to expand...
Click to collapse
You flashed a MAKO recovery onto your Grouper? I did not know that would work
EDIT: Never mind me, I see that you have a mako and trying to convert your Omni to it.
F2FS FOR EVITA ANY AOSP ROM
F2FS for EVITA
AOSP only!
Current CM or most any of our AOSP ROMs around here that use a current CM based kernel.
THIS IS EXPERIMENTAL AND HAS POTENTIAL FOR DATA LOSS IF DONE IMPROPERLY. IF YOU ARE NOT COMFORTABLE WITH THAT PLEASE DO NOT ATTEMPT. I CANNOT BE AVAILABLE FOR 24/7 SUPPORT ON THIS.
These mods will provide the ability to format /data and /cache in F2FS format instead of EXT4. Use extreme caution. The will erase your entire /data partition just like a clean flash. I cannot and will not be held responsible for your failure to keep backups handy. F2FS is still considered experimental by Samsung and should be by you the user as well.
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
How to switch?
PLEASE READ INSTRUCTIONS CAREFULLY. IF NOT FOLLOWED YOU WILL LIKELY BOOTLOOP!!
F2FS capable TWRP Recovery 2.7.1.0 KK version
F2FS capable TWRP Recovery 2.8.5.0 KK versionThis is the same as the current official TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Kernel+fstab conversion zip Flash this after converting partitions to F2FS to install a CM kernel with F2FS support built in. This zip uses an anykernel installer so it should be comparable with most current ROMS. The zip will extract your current boot.img, unpack and replace your current fstab with a new fstab to indicate you current partition types, replace kernel with F2FS capable kernel , then repack and replace the boot.img
Fstab conversion zip For use only when you are already running a F2FS kernel and only need to update fstab after switching to/from F2FS/EXT4. This installer will only unpack, edit the fstab, and repack the boot.img. This will not replace the kernel, you must already be using an F2FS kernel or be returning to EXT4 only to make use of this zip.
DOWNLOADS NOW HOSTED @ CODEFI.RE
http://downloads.codefi.re/jrior001/Evita-f2fs
Procedure for fresh conversion including new Rom flashing:
1. Backup everthing you want to keep with titanium backup or whatever backup you choose.
2. Fastboot flash the new recovery img.
3. Run a twrp backup in case things get ugly!
4. Flash new ROM now if desired.
5. Still in recovery...Goto wipe -> hit Advanced wipe. Select data and hit change partition type. Convert to F2FS. Repeat for cache.
6. Flash the Kernel+fstab conversion zip.
7. Reboot and profit. Any partition app on market can confirm new format changes.
Procedure for nightly ROM updates after F2FS conversion:
1. Flaah nightly
2. Flash kernel+fstab conversion zip.
Procedure if you want to convert back and forth after initial conversion for testing purposes:
1. Change formats of data/cache as desired (only ext4 and f2fs supported).
2. Flash fstab conversion zip to update format types before attempting boot.
Code:
CHANGELOG
V1.0 - Initial release
V1.1 - added inline_data flag to F2FS mounts
V1.2 - updated to latest kernel/fstab as of 8/9
V2.0 - updated for cm-12.0
Source:
Kernel: https://github.com/jrior001/android_kernel_htc_msm8960/tree/cm-11.0-f2fs
Recovery tree: https://github.com/jrior001/twrp-htc-evita/tree/cm-12.0
Fstab scripts: https://github.com/jrior001/f2fs_fstab_convert_script
Devs, feel free to use or modify any of this for your own work just give thanks to where it came from. It was not all my original work, I must give thanks to Metallice and a few other devs in the grouper forum whose scripts I adapted for my own work.
XDA:DevDB Information
F2FS EVITA, Kernel for the AT&T HTC One X
Contributors
jrior001
Source Code: https://github.com/jrior001/f2fs_fstab_convert_script
Kernel Special Features: f2fs support
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2014-07-08
Created 2014-07-09
Last Updated 2015-02-26
Links and Instructions are now up. As promised, F2FS support is now possible for /data and /cache on Evita. For now there is no support for converting /system to F2FS as most have said it does not show significant gains because there is far less writing to /system partition. Also, as of now the only way to support converting /system would require specific ROMs built specifically for F2FS on system. As I have done it here we remain flexible to flash any regular nightly and still enjoy the gains of F2FS on /data and /cache. Follow instructions carefully and enjoy.
If we were building an AOSP ROM, how would we have F2FS already enabled? just wondering if there was a way to eliminate a few steps
pandasa123 said:
If we were building an AOSP ROM, how would we have F2FS already enabled? just wondering if there was a way to eliminate a few steps
Click to expand...
Click to collapse
I've been following some other devices trials and tribulations with f2fs. Most other places I'm seeing dev convert the partitions in the device trees fstab. This results in a fixed f2fs or fixed ext4 ROM. As a dev that means building 2 ROMs which is a time waster.
With these fstab scripts I modded from the grouper forums I was able to make basically any aosp ROM adaptable to f2fs or ext4 for data and cache. I have included this same script work and the needed f2fs tools into the torched installer as well as the f2fs conversion zips.
Pandasa123 I have posted all the source in the f2fs thread. You really only need the kernel commits and the f2fs capable recovery along with my scripts. You could also build a fixed f2fs ROM if you chose and I have commits on my github and on CM gerrit to use as examples for that as well. I have also pushed kernel commits to CM gerreit in hopes that intervigil will merge them to make this a lot simpler but I highly doubt that will happen.
@pandasa123, little more info...
If you look through my fstab zip scripts you'll find that they check the partitions for filesystem type, unpack the boot.img and the edit the fstab accordingly for f2fs or ext4 with all the proper mount flags and then repack the boot.img.
This seemed to me to be an easy way for any user to get their feet wet on f2fs and it takes the extra work away from the devs having to cook duplicate roms. Flash any current ROM, then flash the conversion zip to get your fstab proper based on whatever partition format you are currently on.
There is also a movement on liquid smooth to incorporate this type of conversion script into the ROM zip but its still a huge wip.
Great work, what an awesome parting gift. I have to say again, you've been such a fantastic asset to the Evita forum, easily one of the most significant and high quality contributors we've had the privilege to have here. Really wish I could get my hands on a OnePlus One now!
Sent from my Evita
timmaaa said:
Great work, what an awesome parting gift. I have to say again, you've been such a fantastic asset to the Evita forum, easily one of the most significant and high quality contributors we've had the privilege to have here. Really wish I could get my hands on a OnePlus One now!
Sent from my Evita
Click to expand...
Click to collapse
Did you try the f2fs yet? Curious for some feedback on how it feels to others. @cannondaleV2000 was helping me test this for a week or so until he bricked his ville then other day(unrelated, switching hboots failed him).
I haven't yet, I'm a stay at home dad to a seven week old little girl so I struggle to find the time to even flash a ROM recently. If I get some free time (that's a fairly big if) I'll definitely test it out. It's a real shame about his Ville, I think he got really unlucky and his PC thermalled and rebooted on him during the hboot change. Pretty sure he's getting it jtagged though.
Sent from my Evita
jrior001 said:
Did you try the f2fs yet? Curious for some feedback on how it feels to others. @cannondaleV2000 was helping me test this for a week or so until he bricked his ville then other day(unrelated, switching hboots failed him).
Click to expand...
Click to collapse
I will test and report back with benchmarks shortly.
EXT4 vs F2FS benchmarks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These were done on the same ROM (PA 4.42 stock kernel, then PA 4.42 F2FS evita kernel), followed instructions exactly, rebooted and re-ran the benchmark several times with approximately the same results. Benchmarks were performed on the /data partition. Not sure why SQLite performance took such a hit...
sephiroth2k said:
Click to expand...
Click to collapse
Generally similar to what numbers I had as well. Noticeable gains in both continuous and random write speeds.
jrior001 said:
Generally similar to what numbers I had as well. Noticeable gains in both continuous and random write speeds.
Click to expand...
Click to collapse
Yeah definitely, just curious as to why SQLite was slower with faster random write benchmarks? Seems counter-intuitive; faster writes should mean faster database writes. Also, across multiple runs Browser and Camcorder opened more quickly with F2FS but Camera was slower. IANA filesystem developer however. Thanks for this awesome contribution to the evita scene.
---------- Post added at 09:33 PM ---------- Previous post was at 09:13 PM ----------
Hey I googled a little and found this, suggested issue was "I suspect that you turned on CONFIG_DEBUG_MUTEXES in your .config." # CONFIG_DEBUG_MUTEXES is not set in ville_defconfig . Just throwing it out there
sephiroth2k said:
Yeah definitely, just curious as to why SQLite was slower with faster random write benchmarks? Seems counter-intuitive; faster writes should mean faster database writes. Also, across multiple runs Browser and Camcorder opened more quickly with F2FS but Camera was slower. IANA filesystem developer however. Thanks for this awesome contribution to the evita scene.
---------- Post added at 09:33 PM ---------- Previous post was at 09:13 PM ----------
Hey I googled a little and found this, suggested issue was "I suspect that you turned on CONFIG_DEBUG_MUTEXES in your .config." # CONFIG_DEBUG_MUTEXES is not set in ville_defconfig . Just throwing it out there
Click to expand...
Click to collapse
Its off in Evita source as well. Appreciate the effort and I will look more at that commit as well.
I decided to give the F2FS a try and so I went with the latest CarbonKat and your Torched kernel. I haven't run any benchmarks and I'm still getting all my stuff put back on here but I must say that almost everything seems faster so far. Most noticeable differences so far for me are bootup time is significantly shorter and my phone didn't slow down much at all while installing my apps from the Play Store. Before the switch to F2FS, I had noticed that my phone would lag (sometimes badly) as I would go through the My Apps list in the Play Store and continue choosing apps to install while others were still downloading/installing. Also for me most apps seem to open a little faster than before and work more smoothly.
I do have a question for you about the TWRP backup/restore process with F2FS. Specifically, lets say I backup CarbonKat with the F2FS partitions and then install something else without F2FS (or restore another backup that is not F2FS). If I want to switch back, can I then just restore my TWRP backup of CarbonKat with F2FS? If not, can you recommend a process for that? I'm probably not going to switch from this setup for a while but its hard to tell.
Also, about using the kernel+fstab zip vs just the fstab zip...I used the fstab only zip after flashing your kernel (which already has F2FS support) and that worked out fine for me. But, could I just always use the kernel+fstab zip even if the kernel I flash already has F2FS support?
Hope these questions are ok and thank you for all that you've done for our devices. This F2FS change is one of the most noticeable performance increases I've seen on my Evita and it's been my daily driver since AT&T released it back in 2012. Are there any benchmarks that you'd like me to run or any questions I might be able to answer for you on my usage/experience? If so, I may have to ask for detailed instructions if there's something I haven't needed to do before with android (still learning).
budroid said:
I decided to give the F2FS a try and so I went with the latest CarbonKat and your Torched kernel. I haven't run any benchmarks and I'm still getting all my stuff put back on here but I must say that almost everything seems faster so far. Most noticeable differences so far for me are bootup time is significantly shorter and my phone didn't slow down much at all while installing my apps from the Play Store. Before the switch to F2FS, I had noticed that my phone would lag (sometimes badly) as I would go through the My Apps list in the Play Store and continue choosing apps to install while others were still downloading/installing. Also for me most apps seem to open a little faster than before and work more smoothly.
Click to expand...
Click to collapse
That's bid difference I saw as well, apps install and load a bit quicker.
budroid said:
I do have a question for you about the TWRP backup/restore process with F2FS. Specifically, lets say I backup CarbonKat with the F2FS partitions and then install something else without F2FS (or restore another backup that is not F2FS). If I want to switch back, can I then just restore my TWRP backup of CarbonKat with F2FS? If not, can you recommend a process for that? I'm probably not going to switch from this setup for a while but its hard to tell.
Click to expand...
Click to collapse
If you ran a backup of your old ext4 /data partition and attempt to restore it, TWRP will restore it exactly as it was, in ext4. Lable your backups yo make it easier on yourself!! Twrp will restore in the same format as it was when backed up. Make sure you run the fstab script afterwards or you will bootloop while it fails to load /data.
budroid said:
Also, about using the kernel+fstab zip vs just the fstab zip...I used the fstab only zip after flashing your kernel (which already has F2FS support) and that worked out fine for me. But, could I just always use the kernel+fstab zip even if the kernel I flash already has F2FS support?
Click to expand...
Click to collapse
Yes but it will replace your kernel with a basic CM kernel w/f2fs support. If you want to run torched you made the right choice using the fstab only.
EDIT: Torched Installer includes the conversion script as well now.
budroid said:
Hope these questions are ok and thank you for all that you've done for our devices.
Click to expand...
Click to collapse
Great questions!! And your welcome, I've learned tons messing with this over the last 2 years
Flashed torched instead of Evita f2fs and speeds are much better.
sephiroth2k said:
Flashed torched instead of Evita f2fs and speeds are much better.
Click to expand...
Click to collapse
Could you please define "speeds"? Do you have any supportive data or is this just anecdotal?
Sent from my Evita
timmaaa said:
Could you please define "speeds"? Do you have any supportive data or is this just anecdotal?
Sent from my Evita
Click to expand...
Click to collapse
Torched F2FS is on the right in attached image. As you would say, read the thread - I've been posting benchmarks . I'm at work, didn't attach first try.
sephiroth2k said:
Torched F2FS is on the right in attached image. As you would say, read the thread - I've been posting benchmarks . I'm at work, didn't attach first try.
Click to expand...
Click to collapse
Yeah I've seen your earlier posts, was just wondering where the benchmarks were this time.
Sent from my Evita
timmaaa said:
Yeah I've seen your earlier posts, was just wondering where the benchmarks were this time.
Sent from my Evita
Click to expand...
Click to collapse
No problem - difference is incredible - apps install and open much faster, everything seems smoother (this is subjective of course). Thanks @jrior001 for breathing new life into my aging evita :highfive:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am NOT resposible for any damage done to your device, your neighbor, or any other things you like/hate.
Introduction:
Myself5 said:
@oshmoun and I were in need for a custom stock kernel to mess with. Since all the available Options were not fitting our needs, or gave us bad experience on some aspects, and we knew about Zombie Kernel from Tom, we decided to start working on that. So I brought up support for the Z5, we ported Kexec to it, updated it to 224 and added various things. Since the kernel gave us very good experiences, we decided to make it accessible to the public.
About:
This Kernel is based on @Tommy-Geenexus Zombie Kernel. He was ok with us continuing/porting his projects, so oshmoun, and me started to create the "oshmoun Myself5 Zombie Kernel" aka OM5Z Kernel.
Click to expand...
Click to collapse
After the v2.0 release, @Olivier, @a-st and I decided to make it for Z3+ single and dual SIM. We hope you'll enjoy it!
Features and Commit History:
Check 2nd Post!
Installation Instruction:
THIS DOES ONLY WORK ON UNLOCKED BOOTLOADER!
You can either flash the provided boot.img via fastboot, or flash the zip in recovery.
Additional Information:
The Kernel is underclocked by default. Both Cluster are underclocked to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements. However, due to public demand, V2 features the ability to disable the underclock (in case you need to make some baked Eggs real quick, whatever). All you need to do is run this code after boot (Kernel Adiutor has the abilty to execute scripts at startup, just a reminder).
Code:
echo "0:4294967295 1:4294967295 2:4294967295 3:4294967295 4:4294967295 5:4294967295 6:4294967295 7:4294967295" > /sys/module/msm_performance/parameters/max_cpu_freq
What it effectively does, is resetting the max clock limit for each core to the default (unset) values, allowing you to set whatever frequency (from the ones available ofc) you want.
Download:
OM5Z Kernel (Release Versions)
---> DevDB download section <---
boot_ivy_OM5Z_253.img
OM5Z-Kernel-V2.0-M-ivy.zip
boot_ivy_dsds_OM5Z_253.img
OM5Z-Kernel-V2.0-M-ivy_dsds.zip
Naturally, ivy_dsds files are for Dual SIM, ivy for Single SIM
Myself5 said:
Thanks/Credits:
Tommy-Geenexus - You can guess why
oshmoun - for obvious reasons
FreeXperia Team (especially Jerpelea) - for too many things!
CarbonRom Team - for too many things!
phaseburn - for being a good friend and helping me with almost everything !
infected_ - for help with SM!
My Big Brother Eric - for helping me keeping focused on Development!
My friend Silas - for letting me use his servers and being awesome!
If I forgot you, please tell me.
If you think we deserve a donation, I won't stop you
To Donate to Tommy-Geenexus:
To Donate to me:
To Donate to oshmoun:
PM Spam him to create a PayPal Donation system, he doens't have one yet
Thanks a lot to those who have donated!
Click to expand...
Click to collapse
Myself5 said:
Additional Information:
As you might have seen in my MultiROM Thread, some stock kernels require different Recovery Images than AOSP Kernels. We set an end too this, and fixed init_sony, rather than using some very outdated software which somehow works. This means, you might need to use a different recovery with this kernel if you're currently on a "stock" recovery. We're hoping that other stock kernel devs adapt our solution, so we can set an end to the old scripts.
Click to expand...
Click to collapse
XDA:DevDB Information
OM5Z Kernel, Kernel for the Sony Xperia Z4
Contributors
airlessproject, Olivier, a-st
Source Code: https://github.com/Myself5/android_kernel_sony_msm8994_OM5Z
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v2.0
Stable Release Date: 2016-07-19
Created 2016-07-19
Last Updated 2016-07-21
Latest Version: V2.0
Changelog:
Version 1:
Add kexec-hardboot
ramdisk: use init_sony, no outdated bootrec scripts
ramdisk: fix USB on Stock when using MultiROM
Remove broken Sony MHL driver
Update to 32.2.A.0.224
Merge caf/LA.BF64.1.2.2_rb4.40
Various CVE Fixes
Initial Z5 and Z5C bringup, based on Zombie Kernel with these features
Bug fixes for touchscreen / fingerprint / scheduler drivers
Stripped unnecessary debug nodes, legacy code and disabled KSM
Turquoise LED when EOC is reached (when battery is fully charged)
CPU-Speedbin visible in debugfs node (sys/kernel/debug/msm8994_cpuinfo/*Speedbin)
Calibrated JDI Novatek Panel to 6500K Color Temperature and 2.2 Gamma
Tomtom-Codec Digital Speaker-, Mic- and Cam-mic-Control
Underclocked both Cluster to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements
Version 2:
Ability to disable the underclock (added on public demand) See OP for instructions
Removed TomTom Audio
Update to 32.2.A.0.253
Update init_sony
include DRM Fix by @tobias.waldvogel
Add support for sumire_dsds (E6633 and E6683). Thanks to @tOrNadO™ for testing
For a detailed Changelog, check the Github Commit history:
https://github.com/Myself5/android_kernel_sony_msm8994_OM5Z/commits/
My E6533 got in bootloop.
Edit: waited for recovery to flash supersu and xposed. Since twrp wasn't there, so it bootlooped. Will try again. Error was on my end.
waseemakhtar said:
My E6533 got in bootloop.
Click to expand...
Click to collapse
- .253 stock ROM?
- where does it hang, kernel logo or bootanimation?
- which file did you flash?
- did you have xposed or supersu installed before? if yes, did you reinstall them after flashing the kernel?
Nice to have more options with another Kernel. Was waiting for a Kernel which is underclocked by default. Flashing Kernel+SuperSu 2.76+Systeless Xposed 85.7 went fine (E6553+.253). After that i had to flash twrp to "recovery" partition, FOTA-twrp doesnt boot. Looks really good for the first few minutes.
Trilliard said:
Nice to have more options with another Kernel. Was waiting for a Kernel which is underclocked by default. Flashing Kernel+SuperSu 2.76+Systeless Xposed 85.7 went fine (E6553+.253). After that i had to flash twrp to "recovery" partition, FOTA-twrp doesnt boot. Looks really good for the first few minutes.
Click to expand...
Click to collapse
hey buddy thanks for the nice words, I hope you'll enjoy the kernel.
btw the "recovery" partition is an alias for FOTAKernel afaik, so I don't quite get "FOTA-twrp doesnt boot", tho I must admit I don't know what's FOTA-twrp
I mean as you said, I too flashed twrp to recovery and it works with volume up on the purple led just as it should..
airlessproject said:
hey buddy thanks for the nice words, I hope you'll enjoy the kernel.
btw the "recovery" partition is an alias for FOTAKernel afaik, so I don't quite get "FOTA-twrp doesnt boot", tho I must admit I don't know what's FOTA-twrp
I mean as you said, I too flashed twrp to recovery and it works with volume up on the purple led just as it should..
Click to expand...
Click to collapse
Well i´m not that into recoverys with sony devices as this is my first and there seems to be a difference between flashing twrp from pc to "recovery" and flashing twrp to FOTA Kernel like this. I dont know if it is the same at the end, but some Kernels have twrp included, some not. If you change the Kernel you cant use twrp without flashing it new. I allways had htc devices before and you only flash twrp once and it´s there allways and forever xD. After flashing your Kernel it recognizes my TWRP in FOTAKernel, yellow led went on and changed to purple after pushing vol- but it doesnt boot, just purple led for two minutes after that i rebooted. As i said just flashed it to recovery and everything is working fine.
Trilliard said:
Well i´m not that into recoverys with sony devices as this is my first and there seems to be a difference between flashing twrp from pc to "recovery" and flashing twrp to FOTA Kernel like this. I dont know if it is the same at the end,
Click to expand...
Click to collapse
I think these two methods should have the exact same result at the end, but I may be mistaken
Trilliard said:
but some Kernels have twrp included, some not. If you change the Kernel you cant use twrp without flashing it new. I allways had htc devices before and you only flash twrp once and it´s there allways and forever xD. After flashing your Kernel it recognizes my TWRP in FOTAKernel, yellow led went on and changed to purple after pushing vol- but it doesnt boot, just purple led for two minutes after that i rebooted. As i said just flashed it to recovery and everything is working fine.
Click to expand...
Click to collapse
it should be vol+ I think, vol- is usually for the in-kernel recovery (from my experience with Xperia Z)..
anyway for me it worked after I reflashed the kernel for testing purposes, it entered twrp when I press vol+ (didn't try vol- tho)
also yes, this kernel doesn't include twrp in itself so you'd have to either use the one in FOTAKernel/"recovery"
just to be sure, this kernel supports root right? :angel:
could someone report performance, temprature, stability, lags, and such?
Thanks!
---------- Post added at 19:47 ---------- Previous post was at 19:36 ----------
Misanful said:
just to be sure, this kernel supports root right? :angel:
Click to expand...
Click to collapse
most probebly does why make a rom without root acces?
bjowol said:
could someone report performance, temprature, stability, lags, and such?
Thanks!
Click to expand...
Click to collapse
I think it´s too early to say something definitive but it looks really good, temperature is a little bit lower than with Stock or any other Kernel. I dont see any differences for the perfermance between this and Stock or AndroPlus, so far no laggs or bootloops or other problems.
Trilliard said:
I think it´s too early to say something definitive but it looks really good, temperature is a little bit lower than with Stock or any other Kernel. I dont see any differences for the perfermance between this and Stock or AndroPlus, so far no laggs or bootloops or other problems.
Click to expand...
Click to collapse
ok thanks, have u done any thermal throttling modifications?
bjowol said:
ok thanks, have u done any thermal throttling modifications?
Click to expand...
Click to collapse
No, just flashed kernel, su, xposed and twrp and thats it. But usually testing a new kernel takes a few days, thats all first impression.
Trilliard said:
No, just flashed kernel, su, xposed and twrp and thats it. But usually testing a new kernel takes a few days, thats all first impression.
Click to expand...
Click to collapse
Alright sure! but as you may know, i have an unusual hot device, and on stock configurations it reaches 60 degrees really quickly. and on stock config 60 degrees is the point when the device starts to throttle, and degrade performance. But thank you, i think ill try it out!
Misanful said:
just to be sure, this kernel supports root right? :angel:
Click to expand...
Click to collapse
Sure does. Just flash systemless SuperSU (last stable is always tested with the kernel).
bjowol said:
could someone report performance, temprature, stability, lags, and such? [emoji14]
Thanks!
---------- Post added at 19:47 ---------- Previous post was at 19:36 ----------
most probebly does why make a rom without root acces?
Click to expand...
Click to collapse
Performance should technically be a tad worse than other kernels, caused by the underclock. HOWEVER, due to the S810s hot nature, it wont run very long on its highest clock, and will underclock (even under our underclock limit) rather fast. So after all, you probably wouldnt see MUCH degradation especially not in real life situations, if at all you'd see them in Benchmarks. Temperature, should be way better than on stock thanks to the underclock (my Z5 is IMO cooler than my Z3 on Carbon LP and a performance optimised Kernel (M5 Kernel).
Lags: Helll naaahhh.
Stability: Using the kernel since release (that is Z5 release ofc) +1 Month. Had 3 reboots I am aware of. All while playing Pokemon Go. So, not sure if kernel or Game related at this point.
And Such: You won't see as much features in OM5Z as other competitiors provide. Thats because we focus on having a simple, basic daily usage kernel, with small and sensible additions here and there (e.g. kexec).
Hope that clears some stuff up.
Sent from my E6653 using Tapatalk
Testing it !
Hi,
12hr using, so far everything works well, no boot loop, no hangs, no lag,
For those who like me are not as expert as others a resume what i did:
* Download .253 from xperifirm (Custum DE)
* Remove fwinfo file from download
* Create flashable bundle (omit all .ta files) on flashtool (Answer no to script question)
* Backup (always backup )
* Flash bundle into the phone... I didn't wipe userdata but i can be done (Answer no to script question)
* Restart into system normally
* Flash vía terminal (cmd on windows) this kernel "boot_ivy_OM5Z_253.img" --- To get fastboot mode (Hold volume + while conecting usb cable until blue led flashes)
fastboot flash boot boot_ivy_OM5Z_253.img
* Flash twrp 3.0.2 for ivy
fastboot flash recovery twrp-3.0.2-0-ivy-20160606.img
* Restart on recovery twrp ( Power on phone, pres vol+ once while orange led flashes)
* Flash newest superSu stable (2.76 at this time) vía flash zip
* Wipe caches
* Restart to check root :good:
Enjoy this awesome work ... thaks
Your Kernel is working really good when using it as a "user" but something is a little bit wired with this Kernel. I dont get full access to the whole System. When using TWRP it doesnt show the temperature and it doesnt show severall partitions like oem an these small ones. When Android is booted i get access to all partitions using a root explorer, but cannot access all files on all partitions. All other Kernels have no problems with this, testet all there are for our device (stock,androplus,zach´s) and om5z is the only Kernel which produces this phenomenon. Would be wonderful if you can fix this, it´s a great kernel for daily usage.
Trilliard said:
Your Kernel is working really good when using it as a "user" but something is a little bit wired with this Kernel. I dont get full access to the whole System. When using TWRP it doesnt show the temperature and it doesnt show severall partitions like oem an these small ones. When Android is booted i get access to all partitions using a root explorer, but cannot access all files on all partitions. All other Kernels have no problems with this, testet all there are for our device (stock,androplus,zach´s) and om5z is the only Kernel which produces this phenomenon. Would be wonderful if you can fix this, it´s a great kernel for daily usage.
Click to expand...
Click to collapse
other kernels have twrp embedded in the boot.img, using rootkernel script. That one is modified to fix the cpu temp issue you mentioned, and also offers the ability to mount the other partitions.
OM5Z boots recovery from the FOTA/recovery partition, so as to try and seperate boot and recovery as much as possible. Those issues are basically recovery issues, not so much kernel issues.
About access to partitions on android, did you install supersu?
Trilliard said:
All other Kernels have no problems with this, testet all there are for our device (stock,androplus,zach´s)
Click to expand...
Click to collapse
did you actually use pure stock kernel from the firmware or you used the one repacked with the rootkernel script @oshmoun mentions?
also should be noted that you can use twrp with pure stock kernel only by fastboot boot, not by fastboot flash recovery because stock doesn't have init_sony and purple keycheck light
oshmoun said:
About access to partitions on android, did you install supersu?
Click to expand...
Click to collapse
I think he meant he has access to partitions inside the ROM, only not in recovery..
PS I had only 2% overnight drain in almost 7 hrs with wifi on and being logged in on several huge drainers like Facebook, Messenger, Viber etc.. whereas before I had always >1% per hour
That should say enough about this kernel's power savings... Simple stuff but pretty effective
I used Stock Kernel with rootkernel mod. And yes your declaration that this is related to the recovery itself makes sense. The Problem with access to some files when android is booted could also be relatet to latest systemless root (2.76) i dont know. I had access to all partitions when android was booted but not the rights to access some of the files (copy or delete files).
Well cause of the limitations of twrp which could be used with your Kernel, i cant use it for the Rom i´m actually working on, need access to all partitions hehe. Is there a way to integrate modified twrp into your Kernel?
The power savings are awsome, no other Kernel has such a good batery life.
Introduction
This is my port of LineageOS 17.0 for the UMIDIGI F1, with things mostly working as they are expected to. This ROM depends on the official vendor image, so please be sure you are on the latest official build before flashing this ROM onto your device. Also, since these MTK devices often come with some strange variants, please be aware that your lineage may vary.
Known Bugs
- VoLTE does not work (and probably won't work on any MTK device with custom ROMs any time soon) due to MTK's proprietary extensions.
- (Fixed since 20191230) Sometimes data connection can be randomly lost during reconnections. This can be fixed by either a reboot or `pkill phone` in a root shell (terminal).
Flashing Instructions
1. You MUST flash my TWRP port available here before trying to install the ROM
2. Reboot into TWRP, wipe data (no format needed), then install the ROM zip
3. Install anything else you would like (Magisk, OpenGAPPs, etc. OpenGAPPS beta for Android 10: https://sourceforge.net/projects/opengapps/files/arm64/beta/)
4. Reboot into system and enjoy.
Downloads
20191230-1: https://www.androidfilehost.com/?fid=4349826312261687930
20191105-1: https://www.androidfilehost.com/?fid=4349826312261619909
Source code
Device tree available at https://github.com/PeterCxy/android_device_umidigi_F1
Kernel source code is not available from UMIDIGI, unfortunately.
Screenshots (with OpenGAPPS beta)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What do you mean by "This ROM depends on the official vendor image" Do I need to flash the latest firmware from Umidigi, then flash Lineage?
Lolithetrolli said:
What do you mean by "This ROM depends on the official vendor image" Do I need to flash the latest firmware from Umidigi, then flash Lineage?
Click to expand...
Click to collapse
Actually I don't think there is much change in umidigi's firmware so you are probably fine with pretty much any vendor image. I am on the September vendor image which shows as 20190724
While I enjoy your effort for the port it's really rough around the edges. Settings randomly crash, NFC randomly crashes, there's no difference between default dark mode and black dark mode, it lacks accents other than default, after enabling developer settings numbers appear on the left hand side of the status bar, and GAPPS doesn't even have android 10 available yet. Again, thanks for the port, but it's not for me.
Lolithetrolli said:
While I enjoy your effort for the port it's really rough around the edges. Settings randomly crash, NFC randomly crashes, there's no difference between default dark mode and black dark mode, it lacks accents other than default, after enabling developer settings numbers appear on the left hand side of the status bar, and GAPPS doesn't even have android 10 available yet. Again, thanks for the port, but it's not for me.
Click to expand...
Click to collapse
Somehow I'm using it without any random crashes... Are you sure you have tested on the latest firmwares from umidigi? And are you sure you have wiped data properly? If those crashes only happen for you and not for me, then without logs it's simply impossible for me to fix anything.
And OpenGAPPS has beta version for Android 10, check it out at https://sourceforge.net/projects/opengapps/files/arm64/beta/
On the accent color thing, please wait until LineageOS 17 ports every feature over. For now having most things working is the primary focus.
Thanks for bringing a new life to an already awesome device! I was thinking on changing device due to lack of support, but now I'm surely sticking around! I have a couple of questions tho:
- Is it possible to add tweaks to this kernel? Like 2DTW, F2FS and maybe some more performance/battery gains? Or maybe upgrade it, like to 4.9?
- What about performance in games and/or more demanding tasks? I noticed this on all the GSI's that I tried, because they weren't optimized for the device, and it got hot easily.
Thanks once again for making this dream a reality! I Will test this along with your recovery when I can! Cheers!
SnapTheRipper said:
Thanks for bringing a new life to an already awesome device! I was thinking on changing device due to lack of support, but now I'm surely sticking around! I have a couple of questions tho:
- Is it possible to add tweaks to this kernel? Like 2DTW, F2FS and maybe some more performance/battery gains? Or maybe upgrade it, like to 4.9?
- What about performance in games and/or more demanding tasks? I noticed this on all the GSI's that I tried, because they weren't optimized for the device, and it got hot easily.
Thanks once again for making this dream a reality! I Will test this along with your recovery when I can! Cheers!
Click to expand...
Click to collapse
This seems to be built with stock kernel. As there is no kernel source released, the addition to kernel mods is not currently available.
mrmazak said:
This seems to be built with stock kernel. As there is no kernel source released, the addition to kernel mods is not currently available.
Click to expand...
Click to collapse
Well I found some P60 sources from Nokia, idk if it could be useful...
https://github.com/nokia-dev/android_kernel_nokia_mt6771
Amdroid Pie:
https://github.com/nokia-dev/android_kernel_nokia_mt6771/tree/android-9.0
SnapTheRipper said:
Thanks for bringing a new life to an already awesome device! I was thinking on changing device due to lack of support, but now I'm surely sticking around! I have a couple of questions tho:
- Is it possible to add tweaks to this kernel? Like 2DTW, F2FS and maybe some more performance/battery gains? Or maybe upgrade it, like to 4.9?
- What about performance in games and/or more demanding tasks? I noticed this on all the GSI's that I tried, because they weren't optimized for the device, and it got hot easily.
Thanks once again for making this dream a reality! I Will test this along with your recovery when I can! Cheers!
Click to expand...
Click to collapse
It is not technically impossible, but it would require a LOT of effort to reverse-engineer an entire kernel by piecing together open-source components from other manufacturers, and many of these vendors using MTK SoCs do not have open-source kernel just like Umidigi, though it's technically illegal to do so. I'm definitely not going to do this any time soon.
PeterCxy said:
It is not technically impossible, but it would require a LOT of effort to reverse-engineer an entire kernel by piecing together open-source components from other manufacturers, and many of these vendors using MTK SoCs do not have open-source kernel just like Umidigi, though it's technically illegal to do so. I'm definitely not going to do this any time soon.
Click to expand...
Click to collapse
Now I'm lost ? don't get me wrong, I didn't started yet to develop, but if Umidigi has an "open source" kernel, could it be decompiled somehow from the stock firmware?
SnapTheRipper said:
Now I'm lost ? don't get me wrong, I didn't started yet to develop, but if Umidigi has an "open source" kernel, could it be decompiled somehow from the stock firmware?
Click to expand...
Click to collapse
Linux being open-source doesn't mean any modification to it is easily reverse-engineerable. There is no such thing as "decompilation", only reverse-engineering, which is exactly what I referred to as "not totally impossible". However, if you hope someone to devote an enormous amount of effort just to "decompile" a kernel, you'd better off just sue the manufacturer for kernel source code (they are legally bound to do so by using the Linux kernel). It's far more plausible.
PeterCxy said:
Linux being open-source doesn't mean any modification to it is easily reverse-engineerable. There is no such thing as "decompilation", only reverse-engineering, which is exactly what I referred to as "not totally impossible". However, if you hope someone to devote an enormous amount of effort just to "decompile" a kernel, you'd better off just sue the manufacturer for kernel source code (they are legally bound to do so by using the Linux kernel). It's far more plausible.
Click to expand...
Click to collapse
Anyway
I tried the exact same steps but ended up in a splash screen loop. Any idea how to fix this (or how to grab a log of this, if needed)?
No service on two of the sim card. Phone shows carrier, but no network.
Edited: Never mind. Start from fresh umidigi system, and all good.
SnapTheRipper said:
Anyway
I tried the exact same steps but ended up in a splash screen loop. Any idea how to fix this (or how to grab a log of this, if needed)?
Click to expand...
Click to collapse
TWRP keep system read only, no more boot loop.
test on Umidigi F1 Play
I make Kernel Changes to make your rom work on umidigi f1 play and it booted but a lot of issues :
- sim card doesnt recognize in second reboot
- A lot of NFC Force closes
- Sound is deteriorated (i Think it because the besloudness in the stock rom)
- Rom has a lot of features that not working (example percentage of battery is not showed after i enable it)
this just a report of 15 minutes testing roms
It's possible to revert to stock? How?
sinergine said:
It's possible to revert to stock? How?
Click to expand...
Click to collapse
That would be easiest if you use twrp and make a backup , before flashing this. Same as with any rom, you should make backup first.
If you didn't do that, or the restore fails. Then use sp-flash tool and flash factory firmware.
Umidigi posts the firmware on there community web forum.
SnapTheRipper said:
Anyway
I tried the exact same steps but ended up in a splash screen loop. Any idea how to fix this (or how to grab a log of this, if needed)?
Click to expand...
Click to collapse
Same for me
hyibin said:
TWRP keep system read only, no more boot loop.
Click to expand...
Click to collapse
How to resolve?
sinergine said:
Same for me
How to resolve?
Click to expand...
Click to collapse
Resolved with reflash
hyibin said:
No service on two of the sim card. Phone shows carrier, but no network.
Edited: Never mind. Start from fresh umidigi system, and all good.
Click to expand...
Click to collapse
Now i've this problem.
Tried to restart all step from fresh system but no network
sinergine said:
Tried to restart all step from fresh system but no network
Click to expand...
Click to collapse
You have to put sim cards in before the initial boot. I gave up because too many bugs.