yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gautam_nexus:
I am currently using all f2fs. I would like to use System as ext4 and the rest as f2fs. How shall I proceed forward?

1. Do I need a special recovery or the one that I have will do?

2. Do I need to convert ROM to f2fs or Ext4 rom will do?

3. Do I need a special Kernel?

Thanks!
[Samsung Galaxy Nexus] rajputrajat:
In TWRP f2fs recovery -> Advanced -> F2FS switch..

select system -> ext4

other with f2fs..

and you are good :)
[Samsung Galaxy Nexus] DR3W5K1:
Yea what he said. Also no need to convert the ROM and you can use a non f2fs kernel if you like.
[Samsung Galaxy Nexus] AgentSmith:
How is a non f2fs kernel going to read an f2fs data partition then?
[Samsung Galaxy Nexus] rajputrajat:
AFAIK, you need f2fs kernel to use f2fs partition...

good thing is most of our good kernels are already f2fs supported...
[Samsung Galaxy Nexus] DR3W5K1:
: HomerSimpsonDOUGHmeme:

Didn't feel like Google searching a meme this early

Alright I guess you need a f2fs kernel then.
[Samsung Galaxy Nexus] poo706:
As far as the kernel, you should make sure it's capable of mixing and matching ext4 and f2fs instead of just being all one or the other. Also, watch out for Slimkat and a few other ROMs that mount data as ext4 during installation. You'll get a non-booter if it's f2fs.

[poo]
[Samsung Galaxy Nexus] osm0sis:
Yeah basically ours is the only right now that can mix and match on pretty much any ROM because of Unified v2. FML's stock kernel can also do it, but only for FML or ROMs that use the Motorola fallback fstab (very few).
[Samsung Galaxy Nexus] poo706:
I believe I saw that the latest Fancy can mix and match too.

[poo]
[Samsung Galaxy Nexus] osm0sis:
Correct. Good to see! Looks like he just added my Unified v2 changes (he was already using v1) as of today. :D

[MENTION=4608636]bsmitty83[/MENTION] boype's done some nice 3.4 backports you might want to check out:

https://github.com/boype/kernel_tuna_kk44/commits/4.4
[Samsung Galaxy Nexus] JuanG:
General changelog for version 8.12.14?
[Samsung Galaxy Nexus] osm0sis:
The general changelog can be inferred from the last few pages (Unified v2, boype's backports, Google Camera fix, another attempt at fixing the boot logo loop).

Definitively, always check the commits: https://github.com/bsmitty83/DirtyV_tuna/commits/DirtyV-f2fs

Edit: Ah! There you go, Smitty explained too! :)
[Samsung Galaxy Nexus] bsmitty83:
Basically

Added zzmove to both dirtyV and "-SR builds . all the tunables are available through synapse ( trickster doesn't recognize them ) , I haven't really messed with it yet .

Added back 1mb ram on DirtyV-SR to allow Google camera to function .

Reverted a few commits to try to stop the bootloops on reboot issue

Using [MENTION=4544860]osm0sis[/MENTION] ' v2 ramdisk , any partition can be either f2fs or ext4 . mix n match .

Added a few other under the hood commits , check github if you really wanna know . [emoji6]
[Samsung Galaxy Nexus] szale9001:
Installed latest SR version. Good so far and the 720p recording seems to work fine now on google cam. However, my camera shows 1080p as an option for video and is set to that by default. When selected, it (predictably) crashes the camera until you clear data and reset. I only tested this it to make sure there wasn't a OP labeling error or that I downloaded the wrong one by accident. It seems I didn't and the 1080p option is mistakenly showing up?

Is 1080p still showing for anyone else on SR?
[Samsung Galaxy Nexus] osm0sis:
Not showing 1080p on SR here (which is correct), but the memory Carbon reports in Settings | About phone is still at 757 mb and Google Camera still crashes. :confused:
[Samsung Galaxy Nexus] bsmitty83:
Not sure , only option I get is 720p or below , everything working correctly on my phone with SR.
[Samsung Galaxy Nexus] osm0sis:
Definitely still broken here. Presumably that's since the ROM-reported RAM is the same number as with 7.17.

I guess it's that device difference stuff? Might need to add another mb back so all the varied devices are happy? :confused:
[Samsung Galaxy Nexus] osm0sis:
Does 8.12 fix it on your device?
[Samsung Galaxy Nexus] sergialess:
Now I've fallen in love with Fancy r54, my heart is divided ;)

I've just done a test with new SR: It almost works. It records video and also it is played ok, but suddlenly, when I navigate back, the camera app gives FC, and then you can't access again to the camera hw (you have to reboot).

Second test: record first video (just 5 seconds). Record second video: error (black screen, no access to camera).

Thank you very much for your effort and consideration.

I'm using latest Google Camera app, and CarbonRom.
[Samsung Galaxy Nexus] JuanG:
Thaks! Great job!
[Samsung Galaxy Nexus] osm0sis:
Mine still doesn't even begin to record once. I'm seeing we're both on Carbon though.. Hmm..

ASRAM definitely works, so there must be something about SR's memory grabbing still at fault on our devices/setups.
[Samsung Galaxy Nexus] sergialess:
Excuse me, but what is ASRAM?.

I'm pretty sure you will get it working very soon.

And yes, Carbon is a fantastic rom, imho.
[Samsung Galaxy Nexus] osm0sis:
Just the technical name for it. :)

ASRAM = Additional Safe RAM, ~738. DirtyV uses this.

SRAM = Super RAM, ~757. DirtyV-SR uses this.
[Samsung Galaxy Nexus] sergialess:
I'm wondering if it is worth fighting so hard for 19MB... :confused:
[Samsung Galaxy Nexus] pkgnex:
That would be a matter of opinion.

Mine = No. I'd rather keep a functioning camera and 1080p playback, which is why I personally stopped using -SR kernels long ago. I haven't ever missed the small amount of extra RAM, either, and I'm a big proponent of increasing free RAM...

I honestly can't believe that bsmitty83 has gone to the trouble of maintaining separate versions for a 2.5% increase in RAM, but more power to him for his efforts to keep everyone happy!
[Samsung Galaxy Nexus] pattyboi:):
i only go SR cause we cant even play back 1080p,our screen is 720p,so screw it

(just my opinion of course :P )
[Samsung Galaxy Nexus] DR3W5K1:
+1

Also every now and then that ±15MB can make a difference when having three apps in ram versus one of those three having to be reloaded.
[Samsung Galaxy Nexus] Reinvented:
Everything is running perfectly over here.

No complaints whatsoever.
[Samsung Galaxy Nexus] DR3W5K1:
Yea i bet the N5 runs like a dream. :p
[Samsung Galaxy Nexus] Reinvented:
Hahaha, it honestly does.

I'm underclocked to 300MHz min / 1.4GHz max, and I've never had a slowdown before. It's astonishing.

It's sort of a shame I'm still with Verizon and have to stick with my Toro, haha
[Samsung Galaxy Nexus] osm0sis:
Haha I'm with Patty and Drew on this one, so I'm glad Smitty is still building SR. :)

Good news is Smitty sent me a test build with 5mb put back into the ION tiler and it fixed Google Camera's rear 720p video recording 100%. So now we're just narrowing down the limit again, and that should likely work for everyone where the 1mb back didn't. :highfive:
[Samsung Galaxy Nexus] KreNtal:
Everything is perfect now except for rebooting on restart :(
[Samsung Galaxy Nexus] bsmitty83:
I give up on that , I've only had it happen once to me . ever . I've rebooted fine at least a hundred times at various times , battery level , plugged in , not plugged in etc , and I cannot get it to happen again . I still believe it could be somehow voltage related , but at this point I waive the white flag on it .
[Samsung Galaxy Nexus] Jar3112:
Sooooo... Would you mind giving a look at the usb not being recognised by recovery? :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] krweby:
Is there a difference in voltages from the 4/19 build and now?
[Samsung Galaxy Nexus] osm0sis:
They're stock now, they weren't then, but that was a more recent change so wouldn't explain it. If it's voltage, or even not, I feel like it's something low-level like those LPDDR timings.

krewby have you tried it with just your ROM stock ramdisk to see if you can still reproduce the loop? I don't feel like we've fully ruled out CM's stupid SELinux files that broke backwards compatibility if you downgrade again.

Flash your ROM's boot.img with fastboot flash boot boot.img, then grab one of the zImages from GitHub and fastboot flash zimage zImage should do the trick.

https://github.com/bsmitty83/DirtyV_tuna/commits/DirtyV-f2fs

They're in the commits named for each build (SmittyV, DirtyV, DirtyV-SR).

Anyone who's still getting the loops please try this.
[Samsung Galaxy Nexus] danielstar13:
Guys how do you install this kernel on your f2fs rom? I really want to try this kernel..
[Samsung Galaxy Nexus] ktetreault14:
I'm sorry but can i use this on Verizon?
[Samsung Galaxy Nexus] osm0sis:
Flash. ;)

Kernels are for all variants of the GN. tuna=maguro,toro,toroplus. Sushi! :)
[Samsung Galaxy Nexus] bsmitty83:
Sure
[Samsung Galaxy Nexus] krweby:
Yep tried it with the zImage that was provided before. Still the same issue.
[Samsung Galaxy Nexus] osm0sis:
Cool. I guess that rules out ramdisk for good (which I was fairly confident about since it's never been a problem on franco.Kernel, but it's nice to be sure). :good:
[Samsung Galaxy Nexus] KreNtal:
Now problem man, I can deal with it. It's worth it
[Samsung Galaxy Nexus] d0ge01:
As always

I really want to try new version of this kernel

but it won't boot on encrypted device ( Carbon ROM KK )
[Samsung Galaxy Nexus] osm0sis:
That's shi*ty news! :( :p

ext4 encrypted or f2fs encrypted? I had definitely fixed ext4 encryption with [MENTION=4834554]Oehr[/MENTION] on Unified v1, but I suppose it's possible the same fix doesn't work on v2 for some reason. :confused:
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] Updated bootscript tweaks are pushed to GitHub! (Credit [MENTION=4615478]boype[/MENTION]/Fancy, as with the previous ones!) :D

I noticed our vfs_cache_pressure is set to 120, and boype has it at 55. The default is 100, right? What are your thoughts on that?

The other cool thing I was working on today was with boype and the Fancy crew. We were trying to get AnyKernel2+Unified v2 support to go all the way back to Jelly Bean 4.2, and if we're not there yet we're definitely close. :cool:

Edit: Just got confirmation it works! :victory: :)

Pushed as well: https://github.com/bsmitty83/DirtyV_tuna/commit/ebdc76117d8571a7b80e33e4a188fe78b121e7f1
[Samsung Galaxy Nexus] cujo6801:
And your reward

Sent from the "DOG" pound
[Samsung Galaxy Nexus] osm0sis:
Can I keep it? :laugh:
[Samsung Galaxy Nexus] d0ge01:
Nope, i have both system and data ext4 , with data encrypted, UR won't boot but the strange things is fancy kernel have the same problem , but i had used anykernel version ....

Idk why this happen, it's more like a bootloop ( before ask encryption password )
[Samsung Galaxy Nexus] danielstar13:
Yes, however, when I flash it on my phone with PA F2FS, it freezes in bootanimation.
[Samsung Galaxy Nexus] osm0sis:
Yup. Definitely shi*ty news. Sounds like Unified v2 breaks ext4 encryption again.. You willing to help test?

Setup, logs, anything? I'm running Carbon with both data and cache f2fs with no issues.
[Samsung Galaxy Nexus] cujo6801:
Halle Berry at 48

Sent from the "DOG" pound
[Samsung Galaxy Nexus] AbhishekS:
Probably not the right thread to ask, but certainly the most appropriate one as most people having knowledge of kernels are always here.

What's the status of kernel 3.4 for the Galaxy Nexus?
[Samsung Galaxy Nexus] DR3W5K1:
AFAIK it's still being worked on by ice.

Hashcode got a new job or something so he's not helping anymore.
[Samsung Galaxy Nexus] Rushead:
Halle....lujah
[Samsung Galaxy Nexus] bsmitty83:
op updated -all 3 versions

mainly for the SR version , added back 5mb to ion tiler to make google camera work

-a few minor commits , figured if i was gonna update one version , might as well do all 3
[Samsung Galaxy Nexus] Reinvented:
On behalf of all of us, thank you!
[Samsung Galaxy Nexus] osm0sis:
Aww we gave up? Haha I was still curious whether +3mb or +4mb would also work. :p

Please remember to adjust your configs to remove "androidboot.selinux=permissive" from CONFIG_CMDLINE next time you're updating them, then add it to your mkbootimg script (with --cmdline androidboot.selinux=permissive) instead, that way our AnyKernel2 zip can support Android 4.2+. Making the other commit for that now, thanks to [MENTION=4615478]boype[/MENTION] for noticing that I'd missed it in my recent back compatibility commit. :)
[Samsung Galaxy Nexus] danielstar13:
I'm using TWRP 2.7.0.0 F2FS and I converted the PA ROM using the F2FS Conversion tool.
[Samsung Galaxy Nexus] Reinvented:
She's aged well!

I'm also 29 years younger than her, hahaha
[Samsung Galaxy Nexus] piterdemon:
We are in the same age :)

Wytapatano z Galaxy Nexus PA 4.5 beta2 [MENTION=280772]Dirty[/MENTION]Vkernel
[Samsung Galaxy Nexus] Reinvented:
Smitty and friends, I wrote a little interactive script for pulling GitHub changlogs, which allows you to quickly enter a command and itll put out a changelog in a text file, inside of a folder for that days date. Figured it could maybe come in handy for future releases?

It's my first script of this calibre, so I'm sorta proud of it.

Link to the repo:

https://github.com/I-am-Reinvented/Changelogger

Link to the commit with included instructions just in case:

https://github.com/I-am-Reinvented/Changelogger/commit/db4031f154827e99dd3ddafd5219d97a76ff498c

Hope you don't mind me posting it here
[Samsung Galaxy Nexus] osm0sis:
So I'm inferring here that you're doing F2FS-all? You still didn't say, but you used the converter so it's a safe assumption.

I'd like to suggest you switch to the latest FML-TWRP over in the FML ROM thread, convert /system back to ext4 and flash PA ROM regularly (download it again and don't convert it to f2fs).

Let me know if that fixes anything.
[Samsung Galaxy Nexus] GilGameshn1:
Thanks [MENTION=4608636]bsmitty83[/MENTION] and [MENTION=4544860]osm0sis[/MENTION]
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION] Can you create a anykernel2 zip with the latest SmittyV for me please
[Samsung Galaxy Nexus] osm0sis:
Smitty commits all the zImages and I keep the committed AnyKernel2 zip up-to-date so that people can easily do this themselves. :)

Grab the zImage from the latest SmittyV commit here: https://github.com/bsmitty83/DirtyV_tuna/commit/16c941876a1a9700d8d6106d1482e62819901320

And add it to the current AK2 zip here: https://github.com/bsmitty83/DirtyV_tuna/blob/DirtyV-f2fs/AnyKernel2/UPDATE-AnyKernel2.zip

Easy peasy! ;)
[Samsung Galaxy Nexus] osm0sis:
Oh f*ck, it just occurred to me likely why encryption rebroke in Unified v2..

Encryption is a fallback, meaning the device only knows that /data's encrypted when it fails to mount it normally. That probably means it doesn't so much look like ext4 or f2fs per se and blkid might not recognize it, so the fstab entry is probably getting swapped with nothing (i.e. removed), hence hung boot.

I have a few ideas how to fix it but I'll need someone to test. [MENTION=4834554]Oehr[/MENTION] [MENTION=5250929]d0ge01[/MENTION] or any other security junkies willing to help?
[Samsung Galaxy Nexus] danielstar13:
Thank you!!

But then I'll be getting an ext4 PA if I do your instructions, correct? What I want to get is DirtyV on F2FS PA..
[Samsung Galaxy Nexus] Ashtrix:
Can i know what's the difference b/w the FML TWRP and the 2.7.1.1 one posted on DirtyV :confused: ?

thanks !!
[Samsung Galaxy Nexus] Punkiderma:
2.7.1.1 is multirom and the f2fs/ext4 switch is inside settings,so is different from original TWRP and this cause problem with themes,because they will hide these different options.

FML(which I'm using now) is similar to original TWRP, f2fs switch is inside wipe menu so if you want to use a theme (for example holofied) everything should work(at least,for me is working and f2fs settings are supported). This one isn't multi rom
[Samsung Galaxy Nexus] Ashtrix:
Thnx bro...Just flashed the img, theming works finally :good: !!

Just one thing misses in all these twrp builds, it's the /efs backup option, though i had it backed up long time just in case ;).
[Samsung Galaxy Nexus] osm0sis:
Read back a few pages for the proper explanation, but f2fs on /system is pretty much pointless and will just waste space. /data and /cache are the only ones worth bothering with. :good:

It also keeps you from having to **** around with ROM zips, potentially breaking them by conversion, which is what I think happened in your case. :)

Yeah I don't like the font being smaller, but it's basically how TWRP does f2fs normally but enabled for our device (hopefully we'll get that officially in 2.7.1.1).
[Samsung Galaxy Nexus] danielstar13:
okay I got it! Thank you so much!!!! :D

btw, is my data (apps, music, photos) going to be deleted once I convert /system?
[Samsung Galaxy Nexus] osm0sis:
​

data is data. system is system. Don't do anything silly like Wipe all, or Factory reset and everything will be just fine. ;)
[Samsung Galaxy Nexus] danielstar13:
thank you so much!!!! :d
[Samsung Galaxy Nexus] osm0sis:
Well, fingers-crossed it fixes your issues. You still haven't given me much to go on (no logs, etc.), so I'm just taking guesses here for you. ;)
[Samsung Galaxy Nexus] Oehr:
just pm me with the kernel and i shall test it. fyi, im still on ext4. (see below why)

official one will hopefully also support encrypted devices, as the one in this thread (both multi and maguro) unfortunately fail to decrypt.

P.S. im a bit busy for the next few days, as my PC caught on fire...
[Samsung Galaxy Nexus] osm0sis:
Will do! Just making supper now then I'll script out my idea and send it your way.

FML-TWRP supports encyption if I recall correctly. MWisBest is a security fan himself, I believe! ;)

P.S. Holy ****! Stop trying to smoke up your PC? :eek:
[Samsung Galaxy Nexus] Oehr:
well, i tried the two TWRPs linked in the op ~3-4 weeks ago. both detect encryption and ask for a password - though neither accept the password, telling me its wrong. the official build (2.7.1.0) works just fine. And nope, I didnt typoed that pass. tried it thrice actually.

official 2.7.0.0 also had that issue. 2.6.x.x was fine and 2.7.1.0 fixed the regression. its not mentioned in the changelogs though

im off to bed now. 10h is a long drive home after all. gnight. looking forward to your kernel tomorrow

P.S. https://imgur.com/a/YasPa and https://imgur.com/a/pRHk1
[Samsung Galaxy Nexus] osm0sis:
FML-TWRP is in the FML ROM thread. It's different from the ones in the OP, and I know fixing encryption was one of the main things MWisBest listed as being different. :good:

Good that I've got til tomorrow, I got mired in getting static compiles working for xz and file binaries on AIK again, so I haven't gotten started yet! :p

Safe drive!

Edit: [MENTION=4834554]Oehr[/MENTION] alright, PM incoming. ;)
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION], [MENTION=4834554]Oehr[/MENTION] confirmed that my fixes got Unified v2 booting with encryption. Gotta love it when your first guess is the right one, eh? :D

https://github.com/bsmitty83/DirtyV_tuna/commit/2f2ab2e7c72c1e9f57caed6b6940009c5cf857c6

Here's the test version (running it myself), if anyone else wants it before Smitty makes a new release.

DirtyV-SR-8.15.14-Unified2:

http://v.ht/osmod -- http://d-h.st/users/osm0sis/osmod

If you don't want to flash the .img through a tweaking app like Synapse/Trickster or a flashing app like Flashify, and can't fastboot it, then use my recovery flashable Flashify Script zip!
[Samsung Galaxy Nexus] Oehr:
or just use the command line as superuser to do that:

dd if=/sdcard/boot-8.15.14-sr-unified2.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot

can be done in either recovery or while the system is live. requires a reboot to take effect ofc!

Also, I just switched to LiquidSmooth with F2FS (ran RR and EXT4 before): encryption seems to work, however it will not accept the decryption password - same goes for TWRP2 recovery... Not sure if LS is at fault here or the kernel...
[Samsung Galaxy Nexus] osm0sis:
Yeah I was never sure if f2fs encryption would work with Unified.. because I wasn't sure if there was a way for it to know which fstab entry to use because encryption could just look like nothing to blkid. I guess now we know!

It probably doesn't accept the password because the fstab entry is still ext4, so it's trying to decrypt to that instead of f2fs, or mount that after it decrypts or something. If anyone can think of a clever way to detect which fstype is being encrypted, I'm all ears!
[Samsung Galaxy Nexus] Oehr:
nope... seems like liquidsmooth is at fault here. encryption is just broken, even when i stick with ext4... tried the fixed unified kernel and whatever comes with LS: nothing works.

It encrypts just fine, and boots till i get to the enter pass screen. there, it just refuses the password. same goes for TWRP: neither are able to decrypt the partitions...

so f2fs might work with encryption. though it definitely wont with LS!
[Samsung Galaxy Nexus] osm0sis:
Any chance you could test f2fs encryption with a different ROM? Perhaps the one you were using ext4 encryption on, so it's known working with encryption in general?
[Samsung Galaxy Nexus] Oehr:
ill try!
[Samsung Galaxy Nexus] poo706:
If you guys narrow down the problem, I'll definitely try to fix it.

[poo]
[Samsung Galaxy Nexus] Oehr:
mhh, guess RR doesnt like F2FS for system. the conversion tool by poo709 manages to corrupt the zip and when i manually edit the updater-script, i get an error about the update-binary when trying to flash it... i dunno what to do about that, so i just skipped modifying the script, leaving system on ext4 as-is. i assume that doesnt really matter either, as system isnt affected by encryption - correct?

so once i installed the rom, i switched to the patched dirtyv kernel and made sure both cache and data is F2FS. the first boot was successful and I am now encrypting the F2FS partition. it should take another 30mins to complete!
[Samsung Galaxy Nexus] osm0sis:
Correct! Just use f2fs on data and cache, encryption is only for data anyway, and that'll keep it working for the majority of ROM zips with no conversion necessary. :)

That's how I've been running since I made Unified v2 and it's pretty sweet. :D

Fingers-crossed for f2fs encryption working. If not, I'll send you a test .img to flash that will export some debugging info for us. :good:
[Samsung Galaxy Nexus] Oehr:
encryption just finished. however, its refusing the pass, just like LS. though LS does that for both EXT4 and F2FS, so probably different issue...

i now redid RR(with dirtyv), EXT4 all the way, encrypted it, checked if it booted fine and accepted the pass (it did!), booted to TWRP, mounted encrypted partitions, formatted data to F2FS, rebooted and checked if it booted fine and accepted the pass: Pass refused :(

P.S. man that encrypting takes forever...
[Samsung Galaxy Nexus] osm0sis:
Thanks for taking the time!

Alright. Give me a few minutes to kick together a debugging info script. :)

Edit: [MENTION=4834554]Oehr[/MENTION] do you have a way to adb right now, what with your computer being a fiery ruin?
[Samsung Galaxy Nexus] Oehr:
i do. im on my laptop right now. otherwise, writing here and breaking my phone like this would have been impossible^^

though, im off to bed now, so ill see you in about 10h or so. or maybe more: gonna be a busy day.
[Samsung Galaxy Nexus] osm0sis:
Fair enough! Thanks again.

Here's the debug image when you're up for some more testing.

The device won't boot (on f2fs encrypted) but you should have adb access since I enabled it during boot, there might not be a shell since /system might not be mounted (I'm not sure where in the boot chain it'll get stuck when it can't decrypt), but adb pull continues to work so I have it spitting debug info out to /fsdebug.txt, so adb pull /fsdebug.txt for me please. :)

[ Attachment removed. ]
[Samsung Galaxy Nexus] Oehr:
nope, adb isnt available. shows no devices. "Google Galaxy Nexus ADB Interface" doesnt turn up in the device manager either.