I'd like to give F2FS a try on my N10 but I'm not sure where to start. I know I need both a ROM and kernel that's compatible with F2FS but not much beyond that, so if anyone can help point me in the right direction that would be great. Thanks!
Hello. Only the kernel needs f2fs drivers. So you can use any ROM you want. My kernel includes latest f2fs sources. You may use it. Now by answering to you I think it'might be a nice idea to offer stock kernel with f2fs...
Envoyé de mon Nexus 10 en utilisant Tapatalk
Related
Hello
I have a problem with the modification LGSystemUI, namely I wanted to add a center clock.
I've done all kinds of combinations known to me in statusbar.xml unfortunately unsuccessfully.
I know you can do it using Xposed, but I would prefer to avoid.
Please hints
Yours.
Sorry for my poor English: p
Same question for me, I've it with Xposed module but I prefer to have it cleanly in the framework...
Thx to help us
Envoyé de mon LG-D802 en utilisant Tapatalk
Hi S3V3N, I think in your G3 ROM you solved the issue. Can you give us a hint?
If there aren't any, how can I convert a 6.0.x EXT4 ROM into a F2FS one? I found some guides but only kitkat is mentioned there.
Thank you.
Pure Nexus Project:
http://forum.xda-developers.com/nexus-4/development/rom-pure-nexus-project-layers-t3237366
Chroma:
http://forum.xda-developers.com/nexus-4/development/rom-chroma-03-31-2015-layers-t3069936
The Roms are F2FS compatible, but with the stock kernel included, you'll get a nice and shinny bootloop. For that, you need a custom kernel that supports F2FS. "Taurus kernel" and "Quanta kernel" work perfectly with the new file system. I suggest "Taurus" cause it's got more features and it has almost the same battery and performance as Quanta. And I also suggest "Pure Nexus Project" as ROM, cause it's got pretty much every feature you want, it's "polished", no bugs, and overall it gives you a very nice and smooth experience.
Taurus kernel:
http://forum.xda-developers.com/nexus-4/general/kernel-taurus-mr1-r13-t3145519 (choose AOSP when you download it)
Quanta:
http://forum.xda-developers.com/nexus-4/development/kernel-sabermod-franco-kernel-r211-t2858561
You should migrate to F2FS only the "cache" and "data" partitions, cause only those are used the most. Formatting the "system" to f2fs won't give any improvements except for maybe a bootloop if you're "lucky".
Follow this tutorial:
http://forum.xda-developers.com/nexus-4/help/guide-detailed-f2fs-manual-format-guide-t3264185
Thank you, but the first ROM you linked has cast function broken, as I see in the comments. I'll try Chroma with Taurus!
I'm still not able to understand why I couldn't find by myself that f2fs guide you linked
Also, how can you tell that those two ROMs are F2FS compatible? I didn't find any information in their topics. For example: is MinimalOS compatible too?
http://forum.xda-developers.com/nexus-4/help/guide-detailed-f2fs-manual-format-guide-t3264185 take a look
ROMs just work and don't ask for password on first boot.
Yeah, I read that. I mean how to know if a ROM is compatible before flashing it and realizing it asks for a password or whatever.
I guess, you just ask the developer. It's the simplest way to know whether the ROM supports f2fs or not. A "mention" (eg: @TheArt. ) should draw his attention and you could get an answer quicker than you'd expect.
Cheers !
Hi all,
Can someone point out a tutorial or share some thoughts on building CM13?
Problem: it took around ~6 hours to build CyanogenMod yesterday because of the kernel compilation (i3 processor on an Asus laptop running Linux Mint Debian Edition).
I want't to be able to use specific repositories but don't want to compile the kernel everytime I "brunch bacon".
I hear it is possible to point out a specific boot.img (previsously built), include it while building, thus preventing the compilation of the kernel, which is very time consuming and doesnt make any sense, unless something changed.
But couldn't find any tutorial on this and the Cyanogenmod documentation is a bit confusing.
I bet this isn't new to some of few, so, could you please point me in the right direction here?
Regards,
- aurocha
aurocha said:
Hi all,
Can someone point out a tutorial or share some thoughts on building CM13?
Problem: it took around ~6 hours to build CyanogenMod yesterday because of the kernel compilation (i3 processor on an Asus laptop running Linux Mint Debian Edition).
I want't to be able to use specific repositories but don't want to compile the kernel everytime I "brunch bacon".
I hear it is possible to point out a specific boot.img (previsously built), include it while building, thus preventing the compilation of the kernel, which is very time consuming and doesnt make any sense, unless something changed.
But couldn't find any tutorial on this and the Cyanogenmod documentation is a bit confusing.
I bet this isn't new to some of few, so, could you please point me in the right direction here?
Regards,
- aurocha
Click to expand...
Click to collapse
just run "make bootimage" after lunching device
But that would build the kernel, right?
Enviado do meu A0001 através de Tapatalk
Hi,
I want to update my Mi A1 on Android 7.1.2 to Android 8.0 but I'm root with Magisk and I didn't flash TWRP. Usually, on my OP5 I just download the full zip and flash with twrp, but here, is the same method or not ?
Thanks
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
Hi,
I had the december version of android 7 (i think it was 7.1.2) and was also rooted with magisk, of couse without twrp installed.
What i did was to remove all modules from magisk and activate 'magisk hide' and 'magisk core only mode' (in settings). I don't know if it makes any difference but I had 'preserve force encryption' and 'preserve AVB 2.0/dm-verity' checked (in the main screen). After this rebooted, checked safetyNet (was all ok) and followed the instructions from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips (devices with a/b partitions).
I have to say I had no problems with the update. After this I installed some magisk modules and everything is ok.
However I was a little afraid to proceed as I read lots of posts from people with bootloops (probably from uncompatible magisk modules) and so on. I decided to take the risk as I'm not nearly an expert on this.
Resuming, IT'S UP TO YOU TO TAKE THAT RISK..... or you can wait for some other opinions.
regards and good luck
I'll try soon, when the OTA update was ready for me, Thanks a lot
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
Hello to al. first let say me, excuse my bad english. Currently from Argentina and got this new phone. I Really like it and because i'm a real careful-guy with cellphones, i like yo transform it to f2fs filesystem...
My early cellphones, an S1 and S4 Mini deaths by emmc problems. really use them and i think that ext4 FS killed them...
well. thanks a lot already
Don't try it. Flashing stock rom over F2FS file system may result in hard brick. The rom may not support F2FS.
hope anyone reseased it.. f2fs is more faster responsive but also more experimental
since arter97 has fixed GC performance issue i would have f2fs on my mi a1