yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] MegaDJPlay:
Hey mate, how is progress? Seems like ak CAF kernel is F2FS compatible.

Enviado do meu A0001 através de Tapatalk

---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------

Is the v20 stock cpu values or underclocked?

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] ksigit:
CPU is at stock value..
[ONE Android Development] lemon07r:
Time for an update I guess.

I've began testing on a render kernel version of the rom, so far not usable yet. Shot [MENTION=5438598]RenderBroken[/MENTION] a few questions, was told that he is going to release his next revision of the kernel soon to be inline with the newer commits from [MENTION=4800121]Sultanxda[/MENTION]'s kernel, which should fix my current issues.

Sounds like AK kernel is working on f2fs now. So I will give this a shot too. However I was at work all day today, and didn't have much free time to work on this project. I am at work all day tomorrow too, so you guys might need to wait till wednesday or thursday before any stable release.
[ONE Android Development] ale_cas:
This rom supports power off alarm in quick mode?
[ONE Android Development] ksigit:
What's that? How to enable? I'm happy to check..
[ONE Android Development] ale_cas:
Go to Settings>Developer Options>Enable Quickboot

Then set up your alarm to 20 minutes and power off your phone. The phone will wake up and the alarm will ring.
[ONE Android Development] RenderBroken:
I have pushed my source. Also Updated F2FS. Let me know how it works for you. Also note that if it still doesnt boot, it's most likely because of the missing DTB file that needs to be coupled with my zImage. The one that works with Tyr will not work for mine.
[ONE Android Development] ksigit:
Yes, it is working..[emoji6]

---------- Post added at 10:49 ---------- Previous post was at 10:19 ----------

Just fyi, flashed R6 version: it doesn't boot, stuck in android logo..
[ONE Android Development] RenderBroken:
Thanks!
[ONE Android Development] RenderBroken:
Just FYI, I was able to fix F2FS and Updated it as well. Here is a link if interested:

HERE
[ONE Android Development] zeus_hunt:
Sorry for the silli question.

How do I update the unofficial_twrp_2.8.6.1-bacon-dark.zip on the One Plus One.

I know how to update using fastboot using adb. But that process uses .img file

I am not sure if I should be pushing .zip file or extract the .img file from the .zip file and update the recover ?
[ONE Android Development] lemon07r:
Awesome! I will take a look once I get back from work.

The zip file you would flash from recovery like you would gapps or a rom. You can't flash the zip from fastboot, and the image file in the zip can't be flashed from fastboot too (I've tried before lol). I believe the latest official twrp version can format to f2fs as well, if you really want to flash via fast boot you can use the official twrp.
[ONE Android Development] zeus_hunt:
Thats the confusion I have..

The new twrp does not support flashing the modem firmware, hence this particular version 2.8.6.1
[ONE Android Development] ksigit:
Booting OK, currently testing it.. Multirom still doesn't work though.
[ONE Android Development] lemon07r:
Oh im so sorry! That was a typo! Sorry I wrote that right after waking up, meant to write you cant flash zips from fastboot!
[ONE Android Development] zeus_hunt:
Didn't think one could flash recovery image using the recovery image.

Anyway, just installed the unofficial_twrp_2.8.6.1-bacon-dark.zip using the previous twrp and its working fine.
[ONE Android Development] PlusOne3k:
Same problem here.

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] ksigit:
All kernels I tried (AK, Renderbroken, Tyr) giving same behaviour. I suspect problem in multirom side, f2fs support is somehow broken..
[ONE Android Development] lemon07r:
Ah right I meant to make a post about this, I asked [MENTION=4804871]DerRomtester[/MENTION] about this, the problem is KEXEC support is not implemented in his kernel because it breaks encryption. I believe [MENTION=5438598]RenderBroken[/MENTION]'s kernel does have KEXEC support so sit tight and wait for me to release a render kernel derivative if you want to use multirom. I have only an hour before work and am working all day today, but I will try and release the render kernel derivative before I leave.

K Ive finished and tested it, I don't have enough time to update the master post, let me know how this works on multirom!:

http://d-h.st/h1ZO Devhost download (android filehost is down at this time)

I will upload to mirrors after work!
[ONE Android Development] ksigit:
No dice, multirom still broken.. I'm starting to believe this is multirom side of problem. From kmsg I can see it couldn't mount /data and /cache at some point, expecting ext4 type of partition and thinking it was encrypted somehow.
[ONE Android Development] f41lbl0g:
Although I am not using this kernel (using ak caf), multirom appears to work, but the multiRom menu is completely black. This might also be the case with render. After the oneplus logo, the screen stays black for a couple seconds, which is actually the multirom menu. If you click on the approximate location of your secondary roms in the black menu, it should boot into it. That is, if your screen stays black for a couple seconds after the oneplus logo as I have with ak.
[ONE Android Development] ksigit:
Yes, multirom menu also problem, but even if I set secondary ROM as default, it won't boot into it, always comeback to primary ROM. Booting secondary ROM via multirom also does not work. As I said before, seems like multirom expecting ext4 partition on /data and /cache, which is not the case.
[ONE Android Development] f41lbl0g:
Based on my pervious experience with f2fs and multirom, the secondary rom must have f2fs support on the secondary kernel, else it will not boot. Multirom can automatically boot the format of the secondary rom in f2fs, even without having an f2fs compatible rom. This means that it should detect your partitions if they are f2fs or ext4, however I'm not sure why it is trying to mount as ext4 (maybe no f2fs support on secondary?).

Caf roms on primary are already glitchy enough on ext4, adding f2fs to the mix makes it even harder for multirom.
[ONE Android Development] ksigit:
That's what's I thought as well, so I tried this ROM as secondary, but problem still persists.

Currently I'm confused on who's at fault: CAF, multirom or f2fs..
[ONE Android Development] zjxpot:
All can someone explain the procedure to return to ext4? pls.

thanks in advance
[ONE Android Development] renaltosonylevi:
The same as what you did to go to f2fs but you select ext4 in twrp instead. And yes internal storage gets cleared.

Personally I recommend a USB otg cable and flash drive as the easy way to backup and restore as long as we are not dealing with huge amounts of media.
[ONE Android Development] Miksel12:
Will there be an update to the latest build from Sultan?
[ONE Android Development] PlusOne3k:
Good question, today I got an ota notification - but I am not sure if I can flash without struggling in problems with F2FS.

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] mrkele:
I just tried and I got stuck at boot logo. trying to revert back to the old one. I wish I did backup :D
[ONE Android Development] ksigit:
Just flash f2fs ready kernel after OTA update, preferably renderbroken R7 CAF kernel. It should work.
[ONE Android Development] sychim:
Will not work. The update-script has to be modified to include f2fs for data partition. After that flashing f2fs ready kernel will do.
[ONE Android Development] Miksel12:
Tried that with sultans rom from the 14th but it didnt boot.
[ONE Android Development] Guest00936:
I think this is not for f2fs support. Its for the other sultan rom the caf one only.
[ONE Android Development] IonutP:
A new update would be nice, this is by far the best ROM that I used.
[ONE Android Development] GirishSharma:
My multirom twrp supports F2F2 (MultiROM TWRP 2015-08-03 (v2.8.7)). So, I if I flashes cm12.1-20150914-lemon07r_f2fs-sultan_tyrv15.zip, will I need to flash TyrV15.zip also i.e. if I take steps like this :

1.Format F2F2 Data and cache

2.Since you said this will format whole sdcard then, how do I flash the rom,ukm,open gapps(i am fan of open gapps). Can you please elaborate more.

3.In your OP you said : PS - This can take up to a couple minutes, do not be alarmed if you are on "patching unconditionally" for a bit. So, what does it mean.
[ONE Android Development] ksigit:
- You don't need to flash tyrv15.zip, it's included in the ROM.

- You can copy all necessary zip files via usb-otg or mtp connection after you format /data. So make sure all files available on usb-otg or pc.

- ROM installation using block-based method, which includes 'patching system unconditionally' instead of traditional installation by copying files. Just don't be alarmed if it takes a bit of time.
[ONE Android Development] GirishSharma:
Thanks for reply.

Currently I have downloaded all zips in computer. If I formats the sdcard then after formatting how will I copy the zips to device i.e.

1.Format data, cache by F2FS.

2.Should I also have to format Internal storage too? In OPO there is no sdcard, so I think I have to format internal storage too, right?

3. Ok, now how should I proceed for rom installation.

Seems, I am asking noob question, but I think its always good to ask, if you have doubt.
[ONE Android Development] ksigit:
-No need to format internal storage. Just format data and cache, nothing else. This will erase your phone contents, so please backup your data to external media beforehand (usb-otg, pc)!

-After formatting, reboot to recovery

-Connect your phone to pc via USB cable. Makes sure your phone storage shown on pc. If not, toggles the mount -> disable/enable MTP button.

-Copy all installation files to phone.

-Flash ROM and then gapps, supersu (optional, for root access)

-Reboot system
[ONE Android Development] GirishSharma:
This is how I proceeded :

Reboot to recovery

1.Wipe

2.Advance Wipe

3.Select data

4.Repair or Change File System

5.Change File System

6.Select F2F2

7.Swipe to Change

Back

Back button of the menu

Back button of the menu

8.Select cache

9.Repair or Change File System

10.Change File System

11.Select F2F2

12.Swipe to Change

Back

Back button of the menu

Back button of the menu

Back button of the menu

Advanced Wipe

Select System,data,cache

Swipe to Wipe

System wiped with ext4, while data and cache with f2fs.

-Connect your phone to pc via USB cable. Makes sure your phone storage shown on pc. If not, toggles the mount -> disable/enable MTP button.

Created a folder "New Folder" by computer windows browser. I saw an icon "one" in the windows browser.

In this New folder I pasted required zips and Installed them (/sdcard/NewFolder)

Android is starting...

Optimizing app (N) of 124.

So, here are my phone details :

Device model : A0001

CyanogenMod version : 12.1-YOG4P-20150914-STABLE-Sultan-bacon

Android version : 5.1.1

Baseband version : DI.3.0.c6-00230-M8974AAAAANAZM-1

Kernel version : 3.4.0-Tyr-CAF DerRomtester@kernel#15 Fri Sep 11 15:49:36 CEST 2015

Build date: Sun Sep 13 17:53:08 PDT 2015

Build number : LMY48B test-keys

Recovery : MultiROM TWRP 2015-08-03 (v2.8.7)

Gapps : open_gapps-arm-5.1-stock-20150910

So, at this time my data and cache are F2F2 while system partition is ext4. Is this correct please?
[ONE Android Development] Guest00936:
+1
[ONE Android Development] sychim:
I modified the latest Sultan's ROM from 20150925 to support F2FS data and cache with OP's 'updater-script' and 'boot.img' files and wanted to share it with you. I dirty flashed it over 20150914 version, and then installed Render Kernel CAF-R7. Please use this link to download it.
[ONE Android Development] Guest00936:
It boots perfectly on dirty flash, works like a charm. Still observing it.
[ONE Android Development] sychim:
I updated the newest Sultan's ROM from 20150927 to have F2FS support for data and cache. Dirty flashing it over 20150925 works OK. Please get it from this link.
[ONE Android Development] Guest00936:
Thanks for your effort for this community the version of 20150925 is very stable. How do you do this editing into f2fs format?
[ONE Android Development] sychim:
I changed the 'updater-script' to include support for F2FS and replaced the boot.img file with F2FS compatible kernel. There are many references here at xda-developers on ROM conversion. I started using F2FS since Nexus 4 and found it to be really helpful. There is an app at the playstore to convert ROMs to F2FS format but unfortunately it's only for Nexus 4, 5, and 7.

Here's a good guide: xdaforums.com/showthread.php?t=2694201
[ONE Android Development] ksigit:
There is a guide how to do it: http://xdaforums.com/showpost.php?p=57921263&postcount=453
[ONE Android Development] IonutP:
Guys, what is your SOT? I never had more than 3-3.5 hours on every rom I tried, and I tried all of them. it's very annoying seeing so manny people with 5+ hours of SOT. I even tried some synapse profiles, still the same. I'm not using so many apps, just facebook, fb messenger, whatsapp, 9gag, and some cm12 themes.
[ONE Android Development] otonieru:
can you help to upload the Render-CAF kernel? His server got an issue that causing the downloaded zip can't be flashed. Apparently all MD5 is messed up

---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------

Get greenify and amplify... will fix your SOT for good
[ONE Android Development] lemon07r:
Sorry guys, I have been busy with work and haven't had any days off, also having financial issues (student life too hard) so what little free time I have has been devoted to picking up web design so I can make some freelance money as well. The last build I released is still perfectly stable, so I'm in no rush to update. Once sultan releases his next major update I will probably update this project then.

And yeah there are a lot of good guides for converting roms to f2fs, only issue is each guide does it a different way, and they dont work with all roms! These guides are usually based on cm nightlies, usually what you would have to do is take what you learn and try and get things to work through trial and error.
[ONE Android Development] lemon07r:
Finished testing and uploading my 3 latest builds, inline with sultanxda's updated rom and 3 kernel variants, ranging from ak, render to tyr kernel. I found all of them score near the same in antutu so just pick whichever you prefer! PS Tyr kernel doesn't have multirom support for security reasons, if you want multirom I believe render kernel supports it.

The unsplit boot.img contains the kernel as well as the modified fstab, so you should be able to use the interchangeably with the other variants so as long as they are using the same rom build number/date. So in case if I ever disappear again feel free to play around, I've attached the modified fstab and updater-script if you wish to do so. So far these are tried and true (took a lot of trial and error before I got it right lol). If any of you see any improvements that can be made feel free to let me know :).

Yeah I heard about that, luckily I had a good copy which I downloaded a while ago and used to make a test variant of sultans rom. I've uploaded it for you to 3 mirrors.

https://www.androidfilehost.com/?fid=24052804347824907

http://d-h.st/YizA

https://mega.nz/#!uJcVAZoK!lip4_CYE-2cGmPlUgqEJHhI7DoJGkVyHN3pGJv2LPFk
[ONE Android Development] Miksel12:
Awesome update!

You say that the caf version of the renderkernel supports linux 3.4.108, but isn't that for the normal version? I thought caf was only supported on 3.4.0...
[ONE Android Development] otonieru:
Can i flash it directly over my current kernel?

or should i re-dirty flash the rom first?

Thank you for this btw!
[ONE Android Development] IonutP:
Silly question. Can i use an ext4 rom with multirom?
[ONE Android Development] DerRomtester:
I have noticed some mistales you have made. You dont use the ramdisk tweaks of the kernels. e.g. if i flash Tyr f2fs Rom the default scheduler is is deadline AMD not bfq or two hotplugs are active mpdecision and cpuquiet. This can cause weird behavior. I suggest flashing the kernel again so than anykernel ramdisk can apply all tweaks.

---------- Post added at 10:39 AM ---------- Previous post was at 10:36 AM ----------

No.
[ONE Android Development] dwaipayanray95:
Why can't we format the system partition to f2fs? Formatting the system partition to f2fs would result in faster boot up times and faster system app executions?
[ONE Android Development] lemon07r:
Well if it installs for you without an error I will be shocked cause I wrote the updater script to only take system in ext4.

Also formatting system to f2fs is what most call "3p" cause you have 3 partitions formatted to f2fs (/system /data and /cache), I am using 2p because it has been proven to have much better performance and because 3p has a lot of problems. There was a really good post in one of [MENTION=3874152]zaphodbeeb[/MENTION]'s threads. I can't find it right now, but just a quick search of "3p" in one of his f2fs rom threads will turn up a couple of posts with relevant information

http://xdaforums.com/search.php?searchid=387834414

One post specifically mentions a 1500 point difference in antutu when using 2p vs 3p, (however I am not a big believer of benchmarks so I wanted to find a better post for you but couldn't remember where I saw them).

I knew I was missing something, I will take a look at this when I get back from work. Hopefully I will have properly merged relative kernel tweaks to their respective roms by the time the next build is released.
[ONE Android Development] jark99:
I'm thinking about trying this out and doing a full F2FS conversion from Ext4!my question is how would this affect my ability in a month to flash the Android M update? Would I need to reformat everything and lose all my files again?
[ONE Android Development] lemon07r:
This is not full F2FS! This is only 2 part F2FS, and you only want two part because this is what has been proven to perform fastest and with the least issues.

As for Android M, Android M will probably not be available for the One officially either right away or at all, OnePlus is notorious for slow updates and late promises. You will probably see android M roms developed by our peers not long after android M gets it's release, meaning if you are updating to a F2FS supported android M rom you should be fine, however chances are with the android M update it won't matter what rom you are now, as you will probably have wipe everything for stability's sake instead of dirty flashing anyways. Simple answer is, you will only need to reformat if you switch back to ext4, a large portion of the big roms innately supports F2FS anyways, off the top of my head I know temaseks cyanogenmod rom supports F2FS. However will you lose your data? Idk, that's a android M question, all I can tell you is that you won't lose your data because of formatting if you stick to f2fs.
[ONE Android Development] Tromzy:
Hi, I switched from official CM12.1 nightlies yesterday to this ROM and I'm pretty satisfied with the overall performance. :) The only question I have (but maybe I should post it in Sultanxda's ROM topic ?) : I cannot set my alarm ringbell volume on "progressive" (or whatever it is called in english ; the option that make the ringbell volume start low and then get louder). The option is not there. Is it normal ?

Edit : nevermind, my Alarm clock app was not up-to-date. Fixed now. :D
[ONE Android Development] jark99:
Thank you for the in depth and lengthy reply! Another question I have is, aside from read/write performances and overall stability, does F2fs offer better battery or is it just simply a way to streamline how android handles the file system?
[ONE Android Development] IonutP:
Can anybody help me with a step by step tutorial how to add multirom? I'm currently using this rom with Render kernel and Philz recovery. I tried to put the modified multirom recovery and after I added another rom, it keeps booting normally, without the multirom menu.
[ONE Android Development] PlusOne3k:
As i heard that should be fixed with the last update of multirom. You should use a kernel that is compiled with kexec support. Renderkernel is compiled with kexec support, if you got the latest update of multirom - it is still the same behavior CAF/Multirom no Menue at bootup.

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] IonutP:
Oh, I didn't knew that, thanks.
[ONE Android Development] lemon07r:
Well on paper, F2FS supposedly has better battery life, I forget where I saw this, it was in one of the older f2fs analysis' threads here in xda. BUT the difference is so small that it honestly doesn't matter, when I say small, I mean like a half minute difference from a full charge. Of course I could be wrong, however I can't find the relative posts that covered such topics as they were quite old.
[ONE Android Development] ksigit:
Been there, tried that. Seems like current multirom doesn't fully support f2fs (yet). Although it installed fine, it can't shows boot menu nor boot into secondary. Booting secondary via multirom app doesn't work either.

The only way to switch ROM is by swapping secondary into primary.
[ONE Android Development] Guest00936:
Yes, i think the current multirom doesn't properly supported yet the f2fs. It blocks the writes of firmware (ext4) on the f2fs data file system.
[ONE Android Development] PlusOne3k:
Anyone like to test smartmax_eps as kernel governor? Actually i am testing it, should be an battery extender at all.

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] dandwhelan:
I'm using the Tyr latest version and keep getting a weird bug were the screen seems to stay on with no back light, after they given screen on time. This only seems to happen when streaming Bluetooth audio in my car... Random!
[ONE Android Development] PlusOne3k:
Build version?

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] dandwhelan:
This rom is amazing
[ONE Android Development] lemon07r:
My oneplus one has had this issue for the past year.. on every rom. It is so very annoying, I think for me it's a hardware issue. For you idk, I would check out the respective master threads for sultanxda's rom and tyr kernel.
[ONE Android Development] sneakerspark:
New build is up. Can we expect an update soon? :D
[ONE Android Development] Holymartyr:
Can't wait for the latest builds! =D Loving the switch to f2fs so far! =)

Edit: Oh just found this guide from earlier in this thread (http://xdaforums.com/showpost.php?p=57921263&postcount=453), I compared the files of Sultans build vs yours, and found only the boot.img and updater-script changed. Is it literally as easy as changing the proper "ext4" sections to "f2fs" to make it work? O.o

Just downloaded the lastest sultan build and am currently trying it. Flashed just fine using the AK kernel, appears to be booting so far - will report back if everything has gone fine o.o

(P.S. I'M NERVOUS! lol)

Update: Finished booting, appears to be working? O.o? If it didn't work wouldn't it not get past boot? So I suppose I did it right >.<
[ONE Android Development] lemon07r:
For the updater script that's all you need to change yeah. The boot.IMG contains the modified fstab and zimage (kernel). I have yet to properly implement the kernel optimizitions in the ramdisk (not a big issue, you can flash the kernel again afterwards if you want them). So once the kernels have updated or if there's a big update of some sort I will get around to updating the ROMs, or I'll do it my next day off which should be Thursday. I don't remember what I did for the updater-script, but between that and the fstab one was easy and the other confusing and took a bit of testing. Honestly this work isn't too hard, its just annoying and takes forever to do the testing, especially since a lot of it is trial and error.