yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] temasek:
Actually I'm very certain system partition is safe from user disaster.

As for kernels, there are hybrid f2fs support and full f2fs support.

Hybrid f2fs only supports data and cache

Full f2fs supports system, data and cache.

Ask your kernel dev on this info.

Converting data to f2fs which u probably did actually wipes your internal sdcard because internal sdcard = /data/media which actually is part of your /data partition.

But system is different. System partition is independent from other partitions and also free from your users related data as it's always on Read only mode when booted up.

I'm pretty sure when u last did something related to f2fs, u are either relating to data partition or maybe accidentally enabled data partition to be wiped.
[ONE Android Development] efattal:
Thanks for your detailed explanations. You're probably right. As soon as [MENTION=3814731]katinatez[/MENTION] will upload his build, I will retry. Thanks again.
[ONE Android Development] dev0lver:
Ok, basically I got the answer

System partition is not linked with data partition for formating, so we can freely convert it to f2fs without fear of losing data, but as usual, backup is welcome for the - you never know situation

By me, that is only thing left to do for full f2fa conversion, since I have f2fs on data and cache, with ak kernel (which supports f2fs), so when next update lands and when I will have time, probably tomorrow because of work, will format system and flash the rom to enjoy full phone on f2fs

Let's see how will that work wh n the update lands for download :)

Thnx to all the developers who made this, and gave us opportunity to use f2fson this ROM, now I am liking it even more than before :)
[ONE Android Development] martinoff:
It's time to unsubscribe from this thread and never come back

Sorry [MENTION=3814731]katinatez[/MENTION] I really like your work

Keep going and have fun
[ONE Android Development] hassan_1000:
How did you manage to rezip into a flashable zip with es file explorer?
[ONE Android Development] kecinzer:
I still can't understand what is wrong with it. If anyone take you source and build ROM with it and take care of all user requests. If you don't want this, just close your source ;).
[ONE Android Development] temasek:
Thanks for your comments.

I'll not clog [MENTION=3814731]katinatez[/MENTION] thread with more such nonsense.

Have a good day.
[ONE Android Development] kecinzer:
I don't wanna be unrespectfull I realy appreciate your work. I just don't understeand this policy.
[ONE Android Development] Deadpool253:
I disagree [MENTION=525305]kecinzer[/MENTION] , there's already too many CM12 clones out there as it is and it's just fragmenting development with a base that is currently still in alpha as it is. I could see your point if you're building from source but that's not the case. It's basically just taking someone else's name and rom and using it to get downloads to a kang that has stuff tacked on to it. That's never ok unless the original dev signs off on it which apparently was done without asking for permission first. It's a rule on XDA for a reason.
[ONE Android Development] erad1:
I think it's called "intellectual domain" and though there's no real inherent laws or policies, we should respect the individuals (domain provider) wishes just the same. It's just common courtesy really. See it's kind of like the NFL's policy, they broadcast free OTA programming but have a statement about no re-use without express written consent.
[ONE Android Development] Snottierwhale:
Wait why? This isn't the thread temasek is talking about having no permission
[ONE Android Development] nicholaschum:
Yeah that's the problem with the OPO forums, people Kang each others work with no granted permissions, and release it as a side project.

I remember when there were 2 Mahdi Roms that differed ever so slightly, and now there's two Temaseks. I honestly prefer the original temasek rom, with support from you, instead of a lurcher on XDA that quietly posts a modified build based on your builds with no explicit request to do so.

---------- Post added at 07:08 PM ---------- Previous post was at 07:06 PM ----------

Source is open source, yes. But using your name after reposting the Rom, with no explicit permission, is like having your brand stolen, under non supervised conditions. Hence, he can destroy the reputation of the Rom if the kanger wants to do so.
[ONE Android Development] damage98:
Thanks for the new build. Much appreciated!
[ONE Android Development] pogi1100:
The other ROM is just the F2FS version of this one... So that others don't actually have to manually modify the contents of the zip themselves (and perhaps screwing up in the process). I don't see what's wrong with it.

I mean... I guess the author of the other thread could have just used this one to post the modified F2FS version and kat could have just linked to them in the OP... Either way, the only difference is that the other is in a separate thread...
[ONE Android Development] nicholaschum:
You don't see zephiK posting a Mahdi with Smooth Scrolling Mod built in, at most he would post the patch ON the Mahdi thread when people want to do so.

Also when Mahdi was made into an F2FS version, it was posted INSIDE the Mahdi thread and not a whole entirely new thread for it.

EDIT: BTW [MENTION=3814731]katinatez[/MENTION], time to update title to reflect 5.0.1 instead of 5.0? :)
[ONE Android Development] fjsferreira:
There are dozens of cm ROMS, built by different people, no one complains. Two temaseks and everyone loses their minds?

Sent from my OnePlus One
[ONE Android Development] pogi1100:
Yes, I could see the argument for this. But is it really that big of an issue though? It saves kat some work and keeps the F2FS versions' problems in a separate thread... Which I suppose has both upsides and downsides. Anyways, I'm fine with either outcome...
[ONE Android Development] nicholaschum:
There isn't much issue, as you can see.

However, a simple "Hey Temasek, I would like to create an F2FS version of this amazing ROM for you, so that people can have the F2FS version easily since I will maintain it".

A simple gesture like this, is much better than going his own way, making a new thread about it, disrupting Katinatez and Temasek's download stats on AFH, and then tema found out after 7 pages of "development" over there. That simple one line gesture, respects the developer, and lets him know that his work should be respected and not a Kang for free ROM.

Also, the original developer should be informed before this happened. I would hate for my boot animations to be reposted in a different style, disrupting the true ethos of my work, reposted under the same name, and not even told about it at the first place. Now the original developer is not approving of this method, should you respect his wishes?
[ONE Android Development] katinatez:
Yes, will be updating op and title tonight, taking the night off.
[ONE Android Development] ek69:
Using es file explorer I had to unzip, replace, then rezip

Using zarchiver u can delete the file from inside zip directly, then place the updated file inside zip directly as well :)

Sent From Bacon
[ONE Android Development] pogi1100:
Finally back home. Here is the v2.1 modified framework.jar for faster scrolling (scrolling cache disabled).

Push to /system/framework/framework.jar
[ONE Android Development] chachin:
i can use do adb push framwork.jar /system/framwork//framwork.jar right or what would be best command?
[ONE Android Development] latenightchameleon:
Yup, just mount system and adb push framework.jar /system/framework/

You might have to chmod 644 or something as well
[ONE Android Development] temasek:
If u flash custom kernel on top of the rom, ensure the custom kernel has full f2fs support first before converting system to f2fs.

If using katinatez, read his next post before deciding.
[ONE Android Development] dev0lver:
As far as I know, ak kernel has full f2fs support
[ONE Android Development] temasek:
Then u have no worries.

V16.2 will be able to detect existing system partition filesystem and format it accordingly. Those on EXT4 or F2FS are safe.

Official CM atm cannot perform such without modifying manually the flashing script.
[ONE Android Development] Jole7:
Great Temasek thank you for the support.
[ONE Android Development] johnb380:
I can't wait for this new build! If everything builds as planned we will finally have a completely bug free lollipop ROM no thanx to Google. But thanx to the community!

This Rom is everything I need ever on my bacon thanks to [MENTION=2332422]temasek[/MENTION] and [MENTION=3814731]katinatez[/MENTION]

You guys r truly the best developers on XDA and the world in my opinion!
[ONE Android Development] johnb380:
You are the mother...in man [MENTION=3814731]katinatez[/MENTION] !

I love you! No homo!

You to [MENTION=2332422]temasek[/MENTION]
[ONE Android Development] Jole7:
Does the rom uses uber toolchain?? Thanks in advance.
[ONE Android Development] dennis96411:
Wait, so that means I can flash it with F2FS system partition now?
[ONE Android Development] dev0lver:
Let me say it like this - IT'S ALIVE, IT'S ALIVEEE :D

Data, system and cache formated to f2fs

Then wiped system, dalvik and cache for semi clean flash like usual

Flashed rom , gapps, ak 303, all booted up normally, phone works normally

I didn't lose any of my personal data or apps :D

So feels free to convert to f2fs without fear of losing data :)

By me, all works like before, without any tiny problem :)

Thnx to all who are developing this :D

Edit:

Maybe it's placebo, but phone is snappy as hell :D
[ONE Android Development] zagzag99:
So what's your storage at? Still ext4?

You've formatted /data to f2fs without touching the personal storage?

I find it hard to believe.

can you actually sense the i/o difference?
[ONE Android Development] katinatez:
Yes

No Google stock toolchain 4.8 on Rom & Kernel. I did this because there are many custom kernels to choose from with different flavor of toolchains.
[ONE Android Development] Jole7:
Thanks man great update!!!!
[ONE Android Development] dev0lver:
My system partition is on f2fs, not ext4

Ext4 is past time on mine phone :D

I had formated data partition on mine phone to f2fs long time ago, and that format wiped my phone completely, here I was doing format to f2fs on SYSTEM partition only, since I had data and cache on f2fs done long time ago

Here is a proof that formating system partition does not mess with internal storage, while changing the file system for DATA partition WILL wipe your phone to bare bones

:)
[ONE Android Development] zagzag99:
Okay, so that's explain the no loss of personal data. You've already converted the storage filesystem to f2fs.

Otherwise one need to backup all 64gb to external storage before formatting data partition. And the return stuff via adb sideload or mtp in recovery mode, so to get back even the zip for flashing.
[ONE Android Development] dev0lver:
Exactly

Once you convert data partition to f2fs, you lose all your data

So you need to sideload zip of rom and gapps to be able to revert the phone in working condition

Then once the phone has booted up, you can normally transfer the files to the phone, no needs for sideloading pictures and other stuff :)
[ONE Android Development] johnb380:
New ROM is amaaaazing! Thanks [MENTION=3814731]katinatez[/MENTION] and [MENTION=2332422]temasek[/MENTION]
[ONE Android Development] Aduck79:
Even with ext4 the new ROM feels snappy ?
[ONE Android Development] uudruid74:
Another option is to use a USB OTG cable with external USB storage. I like that option best and TWRP will flash from OTG USB storage
[ONE Android Development] jasonsaw96:
Does anyone have issues with systemUI crashing while playing songs screen off?
[ONE Android Development] katinatez:
Both twrp and philz recovery have this option.
[ONE Android Development] temasek:
[MENTION=3814731]katinatez[/MENTION]

In your fstab, swap f2fs and ext4 making f2fs first line then ext4 2nd line for all related partitions. This will speed up flashing process.
[ONE Android Development] wollax:
Yes a few times with different players, I am using Neutron, Cyano Music Player, and playerPro, all the same crash, but not so often...
[ONE Android Development] temasek:
Possibly your visualizer? Maybe try turning it off?
[ONE Android Development] johnb380:
I have the issue too. Weird.

Edit: it is the visualizer! Turn it off! Everything is good now.
[ONE Android Development] gogib:
Hi all today i install the new update on f2fs for the first time i format the system and cashe with philz recovery, everything working great but when i tried to install stock tk gapps I had an error 70 not enough space and i forced to install mini tk gapps. Is that normal ?
[ONE Android Development] LiquidSolstice:
It's the visualizer. Several other ROMs I've tried have this issue. The moment you turn off the Lockscreen visualizer, it's fine. No idea who broke it.
[ONE Android Development] temasek:
My own device hlte doesn't have this issue.

AFAIK when initial visualizer commit, there were some issues with certain devices. This visualizer updated several times already.

Edit : If anyone can provide me a logcat to have a look at the crash for bacon with regards to visualizer would be good.
[ONE Android Development] Ejvyas:
Can anyone provide me steps to go from 16.1 to 16.2 latest including converting all partitions to f2fs and without losing data ? I'm bit scared as I don't know what this is but hearing good things since last 3-4 pages

I don't know much about partitions but I usually flash dirty from the ota
[ONE Android Development] dev0lver:
Backup internal storage to pc

Then enter recovery, select wipe, advanced, then check system, data and cache one at the time and select option to change file system

Then you should see screen with info of which file system is currently on

Then select f2fs, swipe to format and change file system and that's it

Repeat for other partitions (system, data, cache) the same proces, and you should be ready for flashing

The same way you can check if you formated successfully, because once you change feel system, it should say f2fs under partition properties

Then after format, sideload rom and gapps zip to the phone to flash it and get the phone back to the working state :)

If you get stuck, just Google a little bit, and you will find your answer easily :)
[ONE Android Development] tavito05:
I know I shouldn't make requests but this is pretty interesting. Maybe a bit ambitious but it'd be cool.

Lg has the knock unlock.

The fast few days I realized that even if you double tap the capacitive buttons of our OPO the screen comes on as if we were doing the double tap. Is there any way that we can tap to unlock , like LGs knock code, but using our capacitive buttons ?
[ONE Android Development] LiquidSolstice:
I can't seem to find a response for this.

When I try using the stock TK-GApps package with F2FS formatted partitions (all), I get an insufficient space warning. Is this expected? I've used this package before.

EDIT: Also, why are you sideloading the zip after formatting? MTP works inside TWRP, you just plug in and mount on your computer like you would when booted into Android.
[ONE Android Development] Mark5:
Here you go... I *think* this is a log for when I was using Spotify. Crashes and even my wallpaper changed!
[ONE Android Development] drjat:
Also: Do we need to reflash firmware after changing all the partitions to f2fs?
[ONE Android Development] dev0lver:
Bok

I didn't have any problems with flashing gapps and messages of insufficient space, so I can't help o that part

I am sideloading because, I have never used mtp, only sideload, so for me it's easier :)

And also, I am feeling more secure when I am flashing file directly from the phone, then doing mount on pc, because you never know when or why your connection with pa can break :)
[ONE Android Development] uudruid74:
My visualizer works fine. However, adding a large number of media files to the queue will cause problems, after flipping through songs, the interface will stop responding, the queue may appear empty, basically it gets weird until I reboot. The number of files this requires will vary but 2000+ seems to clog things up in a couple seconds.
[ONE Android Development] johnb380:
I think it's the visualizer when you have trds or a theme enabled is the problem.
[ONE Android Development] uudruid74:
My TWRP MTP doesn't work, but maybe the MultiROM extensions have broken MTP somehow.

---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------

Anyone know what happened to the alarm clock gestures? They disappeared awhile ago. I used to be able to shake the phone to snooze and flip it over to turn off the alarm
[ONE Android Development] temasek:
I'm on TRDS and visualizer works fine. But I'm on hlte. I'll check the log soon.

It's not affecting all. So far I heard bacon.
[ONE Android Development] johnb380:
Here's my log of it... To replicate turn on music visualizer then play a song then turn off screen then turn on screen then try to swipe to unlock then the system ui with restart only when you turn off music system ui will restart one more time then you can unlock the screen without a system ui restart!

https://drive.google.com/file/d/0BzHb7D14yxhqWWRlQnR4NHNyVlU/view?usp=docslist_api

Also trds has no effect on it. It does it with or without it on!

Edit 2:

Here's an error only log

https://drive.google.com/file/d/0BzHb7D14yxhqc0JnNngzd0xhZWM/view?usp=docslist_api

---------- Post added at 10:59 AM ---------- Previous post was at 10:44 AM ----------

What mode is best for logs when posted for debug reasons for the developer?
[ONE Android Development] zagzag99:
With 16.2 or with f2fs we're bound to permissive selinux?
[ONE Android Development] Ejvyas:
Thanks for your help!!

To be very specific and in simple words can I do following :

TiBu backup

Copy backup to external storage

Format to f2fs: data cache system

Install firmware using recovery

Install ROM using recovery

Install tk gapps using recovery

Reboot to ROM

Restore TiBu backup

I don't want to be stuck with unstable phone in the middle of weekdays. Also this is the first time I m formatting partitions.
[ONE Android Development] drjat:
As long as you know how to use sideload.
[ONE Android Development] temasek:
08-30 10:50:06.642 E/AndroidRuntime(2470): java.lang.NullPointerException: Attempt to invoke virtual method 'int android.media.audiofx.Visualizer.setEnabled(boolean)' on a null object reference

packages/SystemUI/src/com/android/systemui/statusbar/VisualizerView.java

New commit from cm as below

SystemUI: use new visualizer from Eleven

https://github.com/temasek/android_...ndroid/systemui/statusbar/VisualizerView.java

I'll check further why u have NPE

EDIT: Added a check so hopefully helps your device. Not a fix but a band-aid. Untested.
[ONE Android Development] johnb380:
You know what could it be the I use V4A? I read somewhere that viper causes issues with visualizer. Maybe that's the reason. But I tried music visualizer on eleven it doesn't fc system ui but I don't see a difference with it on or off tho. I.don't even know what is it supposed to look like with it on?

Edit!

Actually I had V4a installed the apk but no the drivers so I guess that wasn't the issue either.
[ONE Android Development] temasek:
I use V4A too and I'm perfectly fine.

When your next build comes about by [MENTION=3814731]katinatez[/MENTION] , feedback to me the results of this again.
[ONE Android Development] johnb380:
OK thanx for your help friend! I will let you know how it works out on next build.
[ONE Android Development] Ejvyas:
Now I understand what you mean by installing ROM via sideloading which I have never done

But can't I adb push and then just install from recovery ?
[ONE Android Development] johnb380:
Yes u can also u can just hook it up to a pc and install drivers and go to my computer and find ur phones storage and drag and drop into data/media folder and then go to there in twrp and flash. That's how I did it when I accidentally wiped my internal memory!
[ONE Android Development] Ejvyas:
Thanks a lot !! I am more comfortable with ADB so I ll try that.
[ONE Android Development] zagzag99:
Did someone with f2fs managed to change selinux to enforcing?

My phone goes dead if I try to.

Used to be fine on ext4.
[ONE Android Development] Ejvyas:
Formatted and reinstalled

On f2fs now :D
[ONE Android Development] uudruid74:
I verified this is not a ROM problem unless its also in Cyanogen. Anyone know a good non Cyanogen ROM should try to verify this is something on my phone?

I have formatted data recently and system repeatedly. Music player is fine at the moment, but I know if I start swiping or tapping to advance to the next song, it will die quickly.
[ONE Android Development] LiquidSolstice:
It's because you're letting your TK-GApps package overwrite the default clock app with the Google one.

Make a text file, and on the first line, put the word "Exclude". On the second line, put the word "GoogleClock".

Save this file as gapps-config.txt, and put it in the same directory as where your TK-Gapps is stored. TK-Gapps will stop replacing the stock Clock with Google's clock going forward. This option will be respected for all future TK-GApps releases, as long as that text file is in the same directory as the gapps zip.
[ONE Android Development] uudruid74:
Awesome. Thank You! Would flashing the ROM over again fix this as well? Will make the file anyway. I've been wondering about this forever!
[ONE Android Development] LiquidSolstice:
You don't need to use "sideload". You can use MTP from recovery or use ADB provided you create the folder you're going to push to first (formatting data as F2FS will wipe out everything on internal).

To everyone suggesting it, let's stop telling people the only way to get files on the phone either before/after F2FS conversion is to use adb sideload. Sideload is a really annoying an unneeded step that doesn't accomplish anything that MTP or even regular ADB push doesn't.
[ONE Android Development] LiquidSolstice:
Seeing as TK-GApps automatically removes all already-installed GApps when you flash (if it finds any), yes, I think in your case, reflashing the ROM dirty, and then flashing the GApps package over again would do just fine. (Of course, back up to be sure).

I used to always wonder this about the Clock app as well, because I hated having a persistent alarm icon in my status bar. I don't even use the stock clock app (I use AlarmPad), but the stock clock app disables the icon for all apps.

Anyways, BEFORE you do what you're about to do, I strongly suggest you take a look at the TK-GApps config file guide. If there are google apps in the package you're flashing that you routinely find yourself removing when you boot into the ROM for the first time (Like Play Newsstand is totally useless to me), you can use the config file to stop ANY of them from being installed in the first place. A lot of people think TK-GApps (and previous PA-GApps) are just a zip collection of apps, but they are so, so much more intelligent than that.

Take a look at the configuration post here: http://xdaforums.com/showpost.php?p=60944096&postcount=4

MAKE SURE TO ADD THE WORD "TEST" TO YOUR FILE WHILE YOU TRY IT. If you do this, instead of actually flashing, when you flash TK-GApps in TWRP, it will emulate what it would have done, and then output that to a text file on your storage, so you can see what got copied, what got ignored, what got deleted, etc.

It takes 5 minutes to figure this out and once you do, you'll have your own custom GApps setup any time you flash any TK-GApps package in the future.

Good luck!