yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] smint86:
Waiting for v5.3, but while waiting - anybody flashed 2P (or even 3P) version with [MENTION=3814731]katinatez[/MENTION] new unofficial TWRP 2.8.4.0 (from here)?
[ONE Android Development] M5devil:
I went back to 4.7 as it seems to be most stable atm
[ONE Android Development] krxz:
Hey guys, how can I go back to ext4? I am trying to get my phone to work since couple of hours and I am tired of it atm. PLease help me.

thanks, krxz!.
[ONE Android Development] Kernel Klink:
I restored 2P F2FS v4.7 using it after trying to install a different ROM with TWRP 2.8.1.0 (just updated from this older one- I had problems booting into recovery with 2.8.3.0 and went back to 2.8.1.0)...
[ONE Android Development] phermey:
i like the idea. no reason for you to go through the extra trouble... and we get something stable. it's a win win.
[ONE Android Development] tobitege:
+1 ...and since [MENTION=3874152]zaphodbeeb[/MENTION] created great tutorials on how to do it, anyone should try it for themselves if it were so urgent :)
[ONE Android Development] TeChNoC4AzY:
I wonder if I have my system as f2fs... Will it be stable?
[ONE Android Development] zaphodbeeb:
As stable as the ext4 version is.
[ONE Android Development] zaphodbeeb:
Linaro 5.4 version with themes stable & essential firmware upgrade

Hi all,

I have been running with this version since this morning , and it seems stable enough so Ill make f2fs versions for this tonight. Please note that it is essential to upgrade your firmware to this. This is derived from the latest cm12 nightly, so is just a once off change to firmware. Its essential as without it you may have an increased risk of your device bricking. Just flash the attached once, and thats it.
[ONE Android Development] smint86:
So, thanks again for your explanation how to make a ROM f2fs flashable on your own. I'm running Temasek v5.5 linaro on my f2fs mixed bacon together with AK v0.90 - it's perfect. Maybe (I hope that's okay for you [MENTION=3874152]zaphodbeeb[/MENTION]) someone is interested to download the version I changed for my personal usage.

It's ready for f2fs mixed devices (/system ext4, /data & /cache f2fs) and not for multirom (only primary). You can get it here: https://www.androidfilehost.com/?fid=95897840722644812. If not done already, flash the most up to date firmware (from 01/16 nightly) before you flash the ROM.

I created the ROM step by step from the instruction, besides using the above mentioned change for the tool. I flashed it on my device without problems. I'll take the link down immediately, if someone has a problem with it. Just pm or answer to this post.
[ONE Android Development] TeChNoC4AzY:
Hmm.. Is there an advantage of having the system f2fs? Faster boots and all? I know I definitely see an increase of speed in my data/cache partition in f2fs, faster app loading time for sure.
[ONE Android Development] smint86:
From OP:

Also I read, that ext4 is better for handling large amount of small files (what happens in /system partition). I can't find the post atm, but was by a dev iirc. In the end you could try on your own and do some benchmarks, would be interesting ;). I'm running mixed as recommend by op and am perfectly fine with it.
[ONE Android Development] TeChNoC4AzY:
Then that's where I will stay, thanks!
[ONE Android Development] nico53laval:
Why do you recommend flashing the firmware update? Dirty flash?
[ONE Android Development] zaphodbeeb:
Hi,

sorry only just got around to your posts.

- No I dont mind you publishing your roms.

- I think the problem you had was because you deleted the folder/files. The script is a little cumbersome in places, and one of its problems is cleaning up after iteself. I found its best not to manually delete anything in the ramdisk folders etc, but to give the script a command without the boot file data it needs to work. It seems to clean itself very well if you do that, but produces some ugly error messages. Just ignore the error messages. The folders will be cleaned after you use bash unpackimg.sh (without the boot.img bit). Then do a bash unpackimg.sh boot.img again and the folders are freshly popuated. I also used the alternate script you found but that has some funny ways also. It was just a lttle easier to use the one in my post for the instruction.

Pleased you worked it out.:good:
[ONE Android Development] zaphodbeeb:
No problem with you posting a rom at all.

The reason for the firmware upgrade is basically that Katinatez's rom uses cm12 as a base, and so it may not work correctly without the latest firmware from cm. CM also had problems with the firmware and had to do some reverts, and also canned some of their changes this week because of this, so I suspect that in changing the firmware they are also fixing actual (and some potential) problems. It seems to have mproved radio on my device anyhow (or is it a placebo effect). Rom developers dont usually update firmware because its too risky. They leave this to the device maintainer, and thats largely CM's job at present.

Pleased the instructions worked.:good:

I got 5.5 working f2fs style also on my device, but Ive been working on other projects also so havnt published it yet. I am working on a kernel of my own based on CM12 and Sabermod toolchain, but its more security focussed and wont be ready for distribution for some time yet. 5.5 is looking really good though.
[ONE Android Development] zaphodbeeb:
For the job that the system partition does ext4 is better (or so the theory goes). Antutu does show this with Temaseks rom. Another advantage to this is that f2fs uses more memory and preallocates a larger space for itsself. This isnt always good on some devices/roms. Its not really a problem for the OPO however but it makes a difference on other devices.

F2FS is a relatively new tech, and there are more developments yet to come from samsung and others I guess with f2fs.

Try out a comparison of ext4 and f2fs with Antutu (there are also other tools). Its just a little faster on ext4 when have tested it. In real life, we dont all just use Antutu, so I expect some processes on system do suffer a little by using ext4, but generally I do think that its better for the system partitions workload.
[ONE Android Development] zaphodbeeb:
Just as a general point on this, you will notice that "performance" does go down sometimes with some releases, as the devs introduce new commits from cm and add their own. A little like running up a down escalator. Hopefully making progress upwards, overall! Lollipop has/is developing at the fastest rate of any other android release in my experience. Consider that we dont even have a officially "stable" CM version yet.
[ONE Android Development] TeChNoC4AzY:
I'm still scoring 50k+ with latest version 5.4 on antutu :) I'm loving teamasek and AK kernel. I've never seen anything work so smoothly and bug free.
[ONE Android Development] zaphodbeeb:
5.2 was a bit of a disaster. There were re-releases of it, and the rom I produced was from the first release of it which didnt contain this fix. Apologies. I just run out of time to re do it all again for the second release. Looking at the main thread I wasnt actually that sure that the problems were going to be resolved in the second iteration of 5.2, so I decided to wait to see what 5.3 brought.;)
[ONE Android Development] steijn0:
Hi,,

Is the 5.4 2p linaro build done uploading?
[ONE Android Development] tobitege:
Yes, just check the download folders.
[ONE Android Development] TeChNoC4AzY:
It is
[ONE Android Development] steijn0:
Thanks fellas I was just wondering whether it would show up in the folders while incomplete
[ONE Android Development] tobitege:
Little OT: I'm primarily using Firefox, installed "Download Status Bar" plugin, showing download progress at bottom.

But the neat feature is, once a download is finished, hover with the mouse over the entry and it calculates the MD5 for it and I can immediately compare that with the MD5 displayed on the download page. :)
[ONE Android Development] krxz:
Hi,

I flashed v5.4 and got some force closes with launcher and synapse. Isn't it possible to dirty flash the version?
[ONE Android Development] tobitege:
Have you tried to re-install synapse and drivers?
[ONE Android Development] krxz:
I reinstalled both but got an fc when restoring my profile. That's normal I know but after that I couldn't restart synapse. Normally there shouldn't be a problem dirty flashing new versions. In recovery I get "result was [/system]" after flashing 5.4
[ONE Android Development] zaphodbeeb:
Dirty flashed ok for me. The [/system] result is normal. Very unlikely to be anything to do with f2fs specifically. Try deleting cache and dalvik using philz. If that doesnt work try searching the Temasek thread.
[ONE Android Development] azsl1326:
No worries. I appreciate all your hard work and time in converting the ROMs.
[ONE Android Development] krxz:
So I reflashed rom and I think I foubd the culprit. It seems that betterbatterystats widget causes nova launcher fc. I dunno why but when I add the widget to screen it crashes. But I couldn't think of a reason for this which can be rom related. Maybe it's just random who knows. Anyway I am now running 5.4 without bbs widget :D
[ONE Android Development] MrPhilo:
v5.5 I can't seem to boot into system, gets stuck on AK boot logo
[ONE Android Development] tobitege:
Flash ak .87 instead for the time being.
[ONE Android Development] phermey:
psa: i updated to the 5.5 rom posted. it wasn't nearly as quick as the 4.6 special edition i have been on. so i rolled back. Big Mistake. the new firmare kept things from working. now i am back on 5.5 and i no longer have root.
[ONE Android Development] TeChNoC4AzY:
Has 5.5 been tested? I'm hearing form a friend that his antutu score has decreased as low as 44k from 50k+ he would get with 4.6 and I am on 5.4 now with 50k + aswell, not sure if I should upgrade.
[ONE Android Development] smint86:
v5.5 f2fs-mixed with AK v0.90 (interactive, cpu-boost, bricked hotplug with min 2 cores on) runs buttery smooth and simply perfect for me :). I don't care about benchmark but real life performance couldn't be better. Nothing to complain about.
[ONE Android Development] TeChNoC4AzY:
How can I use the bricked hotplug? And can you run antutu with performance, and 2.88 oc just so I can see.
[ONE Android Development] krxz:
No problems here. This is what I did:

1) Wipe Cache/Dalvik/ARTA

2) Flashed 5.5

3) Flashed UKM SE

4) flashed AK 090

Reflash SuperSU BETA 2.44 in recovery
[ONE Android Development] smint86:
bricked hotplug = msm_mpdecision

About Antutu, I'll update this post later if I find some more time this evening.
[ONE Android Development] TeChNoC4AzY:
Okay thanks, and is msm_mpdecision the gpu gov or cpu?
[ONE Android Development] DerRomtester:
It is a hotplug and not a governor.
[ONE Android Development] phermey:
I will give it a shot tonight when I get back home, but root checker says no root. SuperSU would not update binaries etc.
[ONE Android Development] tobitege:
It might just take a couple of reboots or even reflashes, happened to me on different roms on different devices, but it figured it out by itself eventually. :)
[ONE Android Development] TeChNoC4AzY:
How to enable?
[ONE Android Development] phermey:
I saw somewhere the other day, probably on android police or /r/android, that there is an app in the play store that has been updated to root the one plus. So luckilly it is not going o be that big of a deal if it does not come back by tonight... It's just a pain in the neck. I need to get tibu working.
[ONE Android Development] smint86:
Please, stop spamming the thread. Write a PM or better inform yourself in the kernel thread. You have everything you need in the first three posts. This is a development thread concerning f2fs related topics, not Q&A and spoonfeeding. Thanks.
[ONE Android Development] TeChNoC4AzY:
How about you just help me instead of pushing me away? Oh and hmm I think the point of this ROM is for F2fs CORRECT?! I don't see the dev having an issue with my questions, or anyone else for that matter, as a MATTER A FACT, the dev types very long paragraphs for a one sentence question. Which I definitely like. So once again, do a favor and try to help people instead or telling them what to do, the more you help the less questions people will have!
[ONE Android Development] DerRomtester:
Maybe this helps understanding how hotplugging works.

http://bamboopuppy.com/how-to-do-a-cpu-hotplug-in-android/
[ONE Android Development] TeChNoC4AzY:
Thank you for helping me! :)
[ONE Android Development] zaphodbeeb:
f2fs lovein..

Hey people, lets just be nice and enjoy the f2fs love.

The problems people are experiencing are a bit strange, but I suspect that they are down to not wiping dalvik and cache. Always a safe bet to do this when dirty flashing.

The performance (according to the world of Antutu) of this rom has dropped a little, but thats just the way it goes. When a dev implements something new, it may not be as efficient as it could be from day 1. There has been quite a lot of new recently (firmware, themes, kernel changes etc) so Im not surprised.

However this rom still goes like s&*t off a shiney shovel, and Im 110% confident that the devs will be doing everything they can to make it faster/more efficient/feature rich. Life on the edge eh.. Like running up a down escalator sometimes.

I personally am amazed that a rom can be changed so much, so frequently, and still be good enough for a top performing daily.

If you really need every feature to be 100% all the time then I would recommend going back to 4.4 really as the whole lollipop thing is still very young and it will be a little bumpy occasionally.

This is on "out of the box" standard linaro 5.5 with no tweaks on Antutu (3rd run)
[ONE Android Development] phermey:
that worked. thanks a ton.
[ONE Android Development] TeChNoC4AzY:
When I flash a new version I format system, install latest rom, then the gapps, kernel, UKM, and reboot, is this considered dirty flash?
[ONE Android Development] zaphodbeeb:
Sorry made a mess of that. Corrected below.

Hi, For a full flash.

1. wipe dalvik and cache

2. wipe/reformat

3. Flash the rom

4. Flash Gapps

5. Flash SU

6. boot and reboot

7. restore (from nandroid or other)

8. Flash UKM and anything else

For a dirty flash

1. wipe Dalvik and cache.

2. flash rom

3. boot and reboot

4. flash UKM

Flashing UKM before the phone has booted has caused me problems prevously so I do this. Also reflashing supersu shouldnt be necessary but I always flash it anyhow. I use Philz as my day to day as I have found this to be a little less problematical. I do install multirom and full TWRP (Katinatez of course) for testing purposes.
[ONE Android Development] MrPhilo:
Depends which version you are using. Im using 3P.
[ONE Android Development] krxz:
I'm sorry I forgot to mention I'm using 2P
[ONE Android Development] zaphodbeeb:
If Im doing a clean flash I reformat all partitions regardsless of if they are ext4 or f2fs. Its easy enough to backup/restore any folders and nandroids to and from a pc. With a clean flash I generally sideload rhe flashed components until the phone is booted. Then I copy across folders containing the remaining items/backups back to the phone for onboard flashing.
[ONE Android Development] steijn0:
Is the 5.9 build on its way? It seems quiet down here^^
[ONE Android Development] phermey:
Yeah I am thinking that as soon as I get done with making his watch band for the 360... I am going to break out the desktop and use those guides he posted back on pg 16. I have been wanting to learn how to do it for a while now.
[ONE Android Development] steijn0:
Yeah same here I'm in a bit short on time ATM though:p
[ONE Android Development] smint86:
I'm short on time as well, but beeing a flashaholic forces me to at least produce the f2fs-mixed (2P) version for my needs. You can grab it here or from my sig: https://www.androidfilehost.com/?w=files&flid=24579

It's f2fs-mixed (/data & /cache f2fs), 2P version, Temasek 5.9 linaro. I'll try to always produce this version as soon as it releases, at least when I'm at home. Already flashed it on my device together with AK v094. Need to keep it up2date and it's really not so hard to convert it on your own (takes ~5 minutes).
[ONE Android Development] phermey:
thanks smint.
[ONE Android Development] steijn0:
would it be possible to just extract the boot.img from a flashable.zip?
[ONE Android Development] smint86:
Yeah, just extract it using zarchiver (on the phone), or any tool that can handle zip files on your desktop. Select the boot.img and extract it, as easy as that. In fact, it's written in the guide ;)
[ONE Android Development] steijn0:
i just tried to convert 5.9sm into f2fs but I can't seem to figure it out...:(
[ONE Android Development] smint86:
If you gave more information, someone could try to help you with troubleshooting ;). Where exactly are your problems? Did you follow the guide step by step? Do you get any errors? Try to be more exactly, it's not easy to help without information.
[ONE Android Development] steijn0:
well yeah I followed the guide step by step, and after I completed it, I flashed it but it turned out to be bootlooping, lemme try again and iĺl get back to you!

---------- Post added at 09:16 PM ---------- Previous post was at 08:56 PM ----------

This is what I ended up getting, I'm gonna flash it in a minute,

---------- Post added at 09:24 PM ---------- Previous post was at 09:16 PM ----------

Fixed it:)
[ONE Android Development] shnaow:
Link for the last build 2P please!

smint86: the last build that you posted at 08h01 AM bootloop. Can you fixed it and repost please? Thx
[ONE Android Development] smint86:
It definetly doesn't bootloop, as a flashed it on my own and tested it prior uploading ;). I bet you didn't flash the most up to date firmware before flashing the ROM, did you? :)
[ONE Android Development] shnaow:
You're right smint86! I had forgotten to flash the most up to date firmware! Thanks for your help and have a nice day.
[ONE Android Development] smint86:
Next time, just press the thanks button below a post of a user who helped you, saves place in the thread and makes me happy as well ;). Good that it works now, you're welcome.
[ONE Android Development] zaphodbeeb:
Yes, all you need is a boot.IMG. If its from a ROM, or flashable kernel. I've been working on a few changes here but still have some updater-script bits to work out. Hopefully it should mean a single ROM version that will work on any partition mix. I.e f2fs-all, f2fs-mixed, all-ext4.
[ONE Android Development] zaphodbeeb:
Yes I'll get 5.9 out in the morning. Maybe with a new installer.
[ONE Android Development] TeChNoC4AzY:
Will v5.9 be up soon?
[ONE Android Development] zaphodbeeb:
Hang fire until tomorrow. I'll be updating at least the fstab stuff, hopefully the updater-script also.
[ONE Android Development] TeChNoC4AzY:
Sent a pm

---------- Post added at 12:58 AM ---------- Previous post was at 12:40 AM ----------

What will this new installer do?
[ONE Android Development] raja_mastana:
Hi zaphodbeeb, i have been following your guide successfully for converting temaseks rom to f2fs-all

It was working till 5.5

on 5.9, the first boot did not complete even after 15 mins

Is there something else we need to change for this particular version?

BTW I ended up formatting back to ext4 and the new version 5.9 works fine.
[ONE Android Development] smint86:
Please update your guide in that case as well. Already looking forward to it :).
[ONE Android Development] TeChNoC4AzY:
5.9 isn't even here yet.
[ONE Android Development] smint86:
You can grab v5.9 Linaro 2P from my signature. I'm currently uploading v5.9 Sabermod 2P for those who can't wait ;). In the end, you could just convert ROM of your choice to the format of your choice. It's pretty easy.

edit: Got your post now, as it was an answer to another user. No offense intented, but what I've written cares for everybody, anyway :D
[ONE Android Development] phermey:
bah. i just got done installing the linario not five minutes ago.
[ONE Android Development] smint86:
5 minutes to fast ;).

For 2P (f2fs-mixed) Temasek v5.9 Sabermod by katinatez: https://www.androidfilehost.com/?fid=95897840722648050

In about half an our, 3P versions will follow. I don't know if I will do this regularly, but I got time atm as I passed an exam :D.
[ONE Android Development] tobitege:
@smint86: congrats on your exam, I'd say! :) ...and thanks for sharing your builds+insight, appreciated!
[ONE Android Development] zaphodbeeb:
http://xdaforums.com/showpost.php?p=57921263&postcount=453 has now been updated with a new fstab option. Seems to work pretty well. So now you can use the new option and it is suitable for ext4, f2fs in any combnation. I am working on a new updater-script also which should "read" the partition format of the device and install as is appropriate. The advantage of this will be that different versions of the rom will not be necessary, as one will install correctly on any partition mix (including ext4). Just format your partitions as desired and install. Hopefully fnish producing the edify scripts and testing by tomorrow.
[ONE Android Development] krxz:
I tried to install 2p version and got stuck at ak boot logo. Flashed smint86s version and tried to convert to zaphodbeebs build but got stuck. I wiped cache/art, installed rom, ukm and ak kernel 094.
[ONE Android Development] tobitege:
@zaphodbeeb: do you plan on checking in with [MENTION=3814731]katinatez[/MENTION] if he'd be interested to use it in his build? The "catch it all" approach sounds veeery interesting.
[ONE Android Development] zaphodbeeb:
Yes I will. I think the fstab change should also work for full ext4 installs now, but I havnt tested this myself yet.
[ONE Android Development] steijn0:
Kinda regrettable building a script that will probably make this topic redundant:p
[ONE Android Development] tobitege:
I don't think so... no other thread deals with F2FS in depth like this one. It's a keeper! :)
[ONE Android Development] azsl1326:
Just d/l 5.9 2p Linaro and I am not able to get it to boot. It's stuck at the 1+ logo. Yes - I flashed the most recent firmware listed in the OP.

[UPDATE]

So, I went back and tried to flash v5.4 - which I was previously on and it would do a constant reboot to recovery. So, I went and reflashed the CM12_Update.zip (firmware) that I had flashed a few days ago and then tried v5.5 which is now booting. What exactly is the difference between the CM12_Update.zip from a few days ago and the one just posted in the OP along with v5.5?
[ONE Android Development] steijn0:
You're right i didn't exactly mean redundant I meant it is probably gonna be more of a general 'how-to-f2fs' instead of ROM specific
[ONE Android Development] tobitege:
IF you are using MultiRom, you must flash the firmware on primary rom, not from inside MultiRom roms. Or is it your only or primary rom anyway?
[ONE Android Development] azsl1326:
No MultiRom - only Primary Rom.
[ONE Android Development] tobitege:
Ok then, might have been a different firmware file you flashed at first?
[ONE Android Development] azsl1326:
Maybe, the file I flashed today before flashing 5.9 was, 'bacon_firmware_upgrade_cm12.zip'. When that didn't work, I took a gamble and (re)flashed the firmware file I previously flashed earlier in the week - CM12_Update.zip and it worked.
[ONE Android Development] tobitege:
Hmm... do you still have both available? If you peek inside, do they show the same number of files in the root of each zip? Just a hunch.
[ONE Android Development] azsl1326:
Yes, I have both. You might be right. They are the same size and it looks like they have the same files - at least the dates are the same of the files inside the zips.
[ONE Android Development] tobitege:
There should be at least 8 files in the ZIP's root. With the info at hand, I don't have an explanation for what happened (except extracting both and doing a binary file comparison; date/size are inconclusive).

Anyway, it now works for you, that's the good thing. :)
[ONE Android Development] azsl1326:
Yea, thanks. I am only on 5.5, though. I couldn't get 5.9 to boot
[ONE Android Development] zaphodbeeb:
Ak boot logo? Don't think that's been downloaded from this thread.