yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] pvkiniyan95:
I m gonna use flashify to flash recovery no fastboot anymore hope it doesn't mess up

---------- Post added at 03:30 PM ---------- Previous post was at 03:26 PM ----------

Changed my mind I'll wait for results from u guys, coz if something is messed up then my gnex is pretty much bricked....oh god what have I done when things are coming together so well
[Samsung Galaxy Nexus] bsmitty83:
Proof like its needed ....
[Samsung Galaxy Nexus] ILA:
Correct me if I'm wrong, but if I format the partitions to f2fs and were to flash ext4 ROM (i.e. anything other than the included ROM) would my phone turn into a thermonuclear bomb or would it just bootloop (with no damage)?

And the process for reverting to ext4 would be to flash the regular TWRP/CWM via fastboot and format the partitions and then business as usual, right?
[Samsung Galaxy Nexus] dezful:
Yaay.. finally my maguro is booting with f2fs after struggling with ADB sideload. Damn Windows 8.1! lol

anw, how to check f2fs partition using terminal similar to this one? :)
[Samsung Galaxy Nexus] clnzx2:
Oh it works...and works well. Stayed up half the night testing. So far no problems
[Samsung Galaxy Nexus] bsmitty83:
Su , cat proc/mounts

Hack The Tuna
[Samsung Galaxy Nexus] bsmitty83:
Nothing will happen , also no need to reflash a recovery . the twrp we using can switch back and forth . go under advanced menu , there's a button f2fs/ext4 click it and there's all your options to format in ext or f2fs , on all 3 partitions

Hack The Tuna
[Samsung Galaxy Nexus] ILA:
Wicked! Love you guys! :D
[Samsung Galaxy Nexus] chongns:
How you make the sideload working in w 8.1? mind just hang.
[Samsung Galaxy Nexus] dezful:
Praise the Almighty Android, Google, Maguro, [MENTION=4608636]bsmitty83[/MENTION] [MENTION=2838735]aosp[/MENTION] and people who made this happen .. lol.. now I'm running maguro f2fs mode!

here's my first impression on f2fs:

1. adb push ROM (commotio) took 35s (f2fs) vs 59s (ext4) :D

2. adb push pa gapps micro (85mb) took 20s (f2fs) vs 37s (ext4)

3. first boot is much faster on f2fs (not placebo effect) lol
[Samsung Galaxy Nexus] michierusama:
Commotio ROM is vanir right?
[Samsung Galaxy Nexus] bsmitty83:
Don't side load . use adb push .

Hack The Tuna
[Samsung Galaxy Nexus] bsmitty83:
Right now no other kernel or ROMs support f2fs , this is the beginning . I'm sure most will follow soon

Hack The Tuna
[Samsung Galaxy Nexus] dezful:
adb push I mean.. lol

somehow, my windows 8.1 only gave me one shot of "adb usb" (only with advanced startup). One "adb kill-server" will result in device not found and then I must do advanced startup the windows again. Also, It's not working on normal startup, which always results in device not found. I don't know why.
[Samsung Galaxy Nexus] bsmitty83:
After adb kill-server try adb start-server , if that don't work , get that crap windows off your rig and use Linux lol

Hack The Tuna
[Samsung Galaxy Nexus] Nephilim:
**ANNOUNCEMENT * *

I would just like to let everyone know that I finally got my PS3 controller to work with Legend of Zelda: The Skyward Sword on Dolphin Emulator! Now I can finally play the only Zelda title I haven't gotten to try out yet.

P.S. It looks stunning in 1080p with 16x antisotropic filtering.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] michierusama:
Holly S***t :D way to go. What are your pc specs?
[Samsung Galaxy Nexus] Nephilim:
My primary PC is in pieces right now because I'm doing some upgrading so the one I am using is my old PC, that one is running just a duo-core pentium oc'd to 3.2ghz with a Nvidia GeForce 9600GT video card. It's running on 4gb of ram on a 64bit version of Windows 8.1 though so that along with some tweaking of certain settings on the Dolphin emulator allows for a pretty excellent experience. I might add that I am using a 42" 1080p LCD Television via HDMI at 1920x1280 resolution for my monitor. ;)

Basically while tooling around with my old computer I saw my old Dolphin Emulator in my taskbar and so that got me to look to see if the wiimote was able to be emulated on a controller yet, sure enough it was so now I am enjoying the latest in my very favorite childhood/teenage video game franchise. :D
[Samsung Galaxy Nexus] michierusama:
That Game is awesome. I played it. You will enjoy it.
[Samsung Galaxy Nexus] thagringo:
cool, thanks !

have yet to try this, 2 questions :

- can we have a separate thread for this in order to have everything in one place pls. ?

- does anyone know what would have to be done to modify any rom to get it working with f2fs ? I have found an convertor app that apparently does just that ( but is not available for the gnex) and all i have found so far implies building your own rom with a few basic patches.

I remember reading instructions to modify any rom but cant find them anymore ...

TIA guys !
[Samsung Galaxy Nexus] bsmitty83:
A separate thread will be made as soon as I have time .

As for other ROMs I use vanir , not to be rude but I really don't care about other ROMs lol

Hack The Tuna
[Samsung Galaxy Nexus] aosp:
LOL Team DirtyVanir is in the building but I'm working on the patches for [MENTION=4328678]metalspring[/MENTION] & [MENTION=3390093]MWisBest[/MENTION] as I type then I will help other VanirAOSP devs with other devices but as for other roms supporting f2fs on the GNeX I guess that all depends on the devs running the circus but who knows call me maybe ✌
[Samsung Galaxy Nexus] michierusama:
Let the games begin.
[Samsung Galaxy Nexus] sagara.sandaru:
f2fs Liquid Smooth please!!! ;)
[Samsung Galaxy Nexus] jhonnyx:
I'd say: let's test the waters first. Then you can ask the Liquid Devs to work into the rom.
[Samsung Galaxy Nexus] aosp:
[Phoronix] Samsung Keeps Tuning F2FS File-System Performance - http://goo.gl/iKPBIK

[Phoronix] F2FS Gets Improved Read/Write Performance - http://goo.gl/va8NWV

[Phoronix] F2FS On Phoronix - http://goo.gl/33TNGS
[Samsung Galaxy Nexus] winamp26:
f2fs vanir pealse

Sent from NEXUS³ Vanir AOSP05/25/14
[Samsung Galaxy Nexus] drmxmyt:
it is already vanir, isnt it?
[Samsung Galaxy Nexus] michierusama:
It is. Lol.
[Samsung Galaxy Nexus] bsmitty83:
Really???

Hack The Tuna
[Samsung Galaxy Nexus] michierusama:
Well people should start to be patient. I see a lot of whining... For god sake. Its done and working and we only have to wait for it to be released to the masses. Thanks.
[Samsung Galaxy Nexus] winamp26:
please create new thread and telling into how to change (is it bad idea?) or give me a link how
[Samsung Galaxy Nexus] chongns:
The link or go back 4 pages back and start to reading until reach back here.

[emoji106]

http://xdaforums.com/showthread.php?p=53005551
[Samsung Galaxy Nexus] winamp26:
if i change it, can i back to ext4 or not?

and possible brick my phone?
[Samsung Galaxy Nexus] osm0sis:
Bro. Read back. You've already been told you need to and your questions have already been answered.
[Samsung Galaxy Nexus] bsmitty83:
For real dude all this has been answered , if you don't have the patients to read , maybe you shouldn't worry about this right now

Hack The Tuna
[Samsung Galaxy Nexus] pattyboi:):
you guys are the best :good:
[Samsung Galaxy Nexus] winamp26:
last question:)

after flash TWRP-TUNA-F2FSALL.img

flash B66-Commotio-MAGURO-F2FSALL-FIXED.zip and then rom and gapps?

sorry guys:(
[Samsung Galaxy Nexus] jhonnyx:
Read a few pages back please, I'm sure your question is answered there.
[Samsung Galaxy Nexus] metalspring:
Anyone run any benchmarks to test f2fs yet?
[Samsung Galaxy Nexus] AbhishekS:
A question for f2fs users.

How is the lag while installing/updating an app from the Play Store?
[Samsung Galaxy Nexus] bsmitty83:
Its not as bad IMHO , still a little there but a definite improvement

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
That's been shown to be a Play Store bug, not so much to do with our storage. If you go back and flash Ice Cream Sandwich you'll see that the old Android Market installs apps without so much as a hiccup. ;)
[Samsung Galaxy Nexus] drmxmyt:
running f2fs, did several tests with a1sdbench, didnt change much. ~30mb read, ~13mb write speed average. did a quick test. long test doesnt change that much neither. can someone also make it with ext4 for comparison.
[Samsung Galaxy Nexus] BestBrd:
More RAM,android kitkat,omap improvements,f2fs support and (probably) 3.4 kernel were added since google has released the gnex...gnex has been tuned a bit i think ahahahahah
[Samsung Galaxy Nexus] ILA:
Ok, looks like I've screwed something up... I can't install anything form the PlayStore... It errors out of the instalation and says ".. (Error retrieving information from server. [RPC:S-3])" (No FC tho :) ). I've flashed Banks gapps (standard)...

Is the PlayStore server down? Have I messed up or did this happen to anyone else?

Thx in advance! :)

Edit: Because it can't install anything, none of my apps have been restored ofc :eek:
[Samsung Galaxy Nexus] michierusama:
I tried to install the rom but I couldnt see the files on the SD after pushing them with ADB. Recovery flashed fine, formatting was fine, but the final step was a total failure in my case. Windows 8.1, all good but thats where I am stuck. I will wait for the ''oficial thread'' LOL.
[Samsung Galaxy Nexus] bsmitty83:
Reboot the recovery , then try again it should show up , if not after a reboot , push it again

Hack The Tuna
[Samsung Galaxy Nexus] bsmitty83:
Yay , now that f2fs is done , I can build new kernels lol

Hack The Tuna
[Samsung Galaxy Nexus] ILA:
Yup, adb isn't working for me as well on this recovery. Worked fine on the original TWRP...
[Samsung Galaxy Nexus] michierusama:
Bad luck for us... Ill try later.
[Samsung Galaxy Nexus] jhonnyx:
Wait a little bit. ADB under windows on that recovery is a bit of a problem, but not that much, If waiting a little bit does not work, go to mount menu then try pushing.

That worked for me ;)
[Samsung Galaxy Nexus] metalspring:
Might be just an issue with what was included in the TWRP recovery source that was used
[Samsung Galaxy Nexus] michierusama:
I will try later tonight. I was kinda in a hurry this afternoon. But Ill wait for the thread too...
[Samsung Galaxy Nexus] osm0sis:
[MENTION=3390093]MWisBest[/MENTION] had some adb fixes for TWRP/his ROM that might help.
[Samsung Galaxy Nexus] bsmitty83:
Adb works fine on this recovery , TRUST ME , I've used it more than enough . we probably tested a hundred rom zips getting f2fs to work .

If you can adb shell you can adb push , if not kill the server then restart it . still not working ? Use a Linux distro lol
[Samsung Galaxy Nexus] ashclepdia:
didn't I say something similar would happen? lmfao
[Samsung Galaxy Nexus] cujo6801:
Oh sure now that I've gone through a full detox you want to get me hooked again...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] bsmitty83:
Everything a good pusher is supposed to do ...... Lol , hey at least this $h¡t is free [emoji39]
[Samsung Galaxy Nexus] michierusama:
Trust me I tried lots of times. I just wanna do it. But that will be later. :D
[Samsung Galaxy Nexus] jhonnyx:
On linux adb push works like a charm, on Win, sucks, that's all I'll say ;) +1 Smitty
[Samsung Galaxy Nexus] MWisBest:
The problems aren't with the recovery, it's actually with the ROM. It does not matter what OS you are on, if the ROM has the bug it has the bug. The problem was that some ROMs were trying to overwrite the default init.recovery.rc, which is the wrong way to do things... instead a init.recovery.tuna.rc should be used instead, ala: https://github.com/MWisBest/android_device_samsung_tuna/blob/omni-4.4/init.recovery.tuna.rc

The init.recovery.rc stuff is responsible for bringing up the USB functions such as ADB.

These were the commits for my device tree that fixed it, applied to an OmniROM-based tree but reworkable for anything really:

https://github.com/MWisBest/android...mmit/0c63a68e19b1a26a804444206fc16244d5a2c7a3

https://github.com/MWisBest/android...mmit/55842146e4dc40a578582462c57f2d3a5f94c1d4

https://github.com/MWisBest/android...mmit/e509ac04b71fa48faffee5a0e4ecbc8288f14186

Those commits are independent of the recovery itself.

And for fixing /data encryption in 2.7.0.0+ TWRP, this did the trick, however this is an issue with the recovery and is not dependent on the ROM: https://github.com/MWisBest/android...mmit/8da3ea80edc3ddb9c84c58c8c953690fc0a188a1
[Samsung Galaxy Nexus] ILA:
Tried it. Killed the server and restarted it over and over and it just wouldn't recognize the device...

And so I tought that it was my Win8.1 causing the problem, but it was a bit strange since I adb pushed the ROM to the sdcard, which was nowhere to be found after I flashed it from the recovery...

...and this is where [MENTION=3390093]MWisBest[/MENTION] 's explanation fits perfectly... :)

I don't use adb that much since most of the things I use it for can be done form the phone, but I gave it a shot since I was doing a full backup. :)

EDIT: just an update to my PlayStore problem from the previous post. After a reboot I can instal apps, yay! :D The bad thing is that it didn't auto download my apps... :(
[Samsung Galaxy Nexus] apollo07:
[MENTION=4608636]bsmitty83[/MENTION] I was wondering if you could flash another kernel bc I need muh synapse!
[Samsung Galaxy Nexus] drmxmyt:
i also had problem with adb. older twrp doesnt have that problem but latest twrp with f2fs support most of the time doesnt work properly for adb. i simply couldnt make it work, luckily usb otg works now and could able to flash the rom with it.

note: i use win7 64bit, adb works perfectly with anything else.
[Samsung Galaxy Nexus] bsmitty83:
No not until I update the ramdisk of my kernel , or you could use [MENTION=4544860]osm0sis[/MENTION]' anykernel2 package with the latest smittyV zimage if you really need synapse . just extract the zimage from the boot image and add it to the anykernel2 package .

My ramdisk is still ext4 .

Hack The Tuna
[Samsung Galaxy Nexus] chongns:
ADB found no devices

A step need to take if ADB found no device.

If in the TWRP advance menu, just after formatting step, you cant push the file, the adb driver woundnt recognize the device.

you need to return back to main menu, than push the file.

I found this out after I full reflash the stock image 4 time.
[Samsung Galaxy Nexus] clnzx2:
For adb to work be on main menu and during testing I noticed windows would take as long as a few minutes to recognize the phone so be patient
[Samsung Galaxy Nexus] michierusama:
Ok, my issue its not that the phone wont get recognized, its about flashing the rom... When I push it with Nexus toolkit by wufresh, I cant find it on the system/folfer/etc/etc/etc.

Thats the only step Im stuck. Pushing the file and find it on the SD card.

---------- Post added at 10:09 PM ---------- Previous post was at 09:31 PM ----------

Did you flash the ROM. I cant..
[Samsung Galaxy Nexus] p34rp34r:
I hope I don't offend you with this question, but...you do know that "adb push" only moves files around right? You can specify the destination directory, but it doesn't actually install anything. You'll still need to flash the file you pushed. You can use "adb sideload" to push & install, but it sounds like sideload isn't working on the f2fs-modified TWRP.
[Samsung Galaxy Nexus] michierusama:
I know it moves the files from one destination to the one I set or the one its default. Thats when it happens, I cant find it. Its all blank. And I even try to install it via recovery but it does nothing. Bleh... I even put the recovery to the custom one they made and still boots into the ''original recovery''

I was reading and the thing installed... dont know how I just hit reboot on the recovery and then the rom was booting... ok for now I have it but I dont even know how. I feel stupid LOL.
[Samsung Galaxy Nexus] jhonnyx:
PM if you have any questions. Where are you stuck right now?

You want to go stock?
[Samsung Galaxy Nexus] michierusama:
Read the post above... LOOOOOL! for real I dont know how it happened... but well it happened.
[Samsung Galaxy Nexus] metalspring:
Btw [MENTION=4608636]bsmitty83[/MENTION] [MENTION=2838735]aosp[/MENTION] what date was the f2fs version of vanir made? I just want to download the regular version of commotio for that day for a direct comparison
[Samsung Galaxy Nexus] chongns:
Make sure you are on f2fs, type mount in adb shell and check. Or it is just normal ext4
[Samsung Galaxy Nexus] bsmitty83:
5-27-14

Hack The Tuna
[Samsung Galaxy Nexus] winamp26:
finally i test it.

adb doesnt works in recovery (windows 7)and i flash it by USB-OTG.

1 question: commito is vanir build and can i flash vanir 25/05/14 with smity16/05/14?

thank you and excusme for many question
[Samsung Galaxy Nexus] bsmitty83:
No definitely not .

Hack The Tuna
[Samsung Galaxy Nexus] clnzx2:
Sideload works just fine
[Samsung Galaxy Nexus] dezful:
What OS do you use?

sent from Siemens C55
[Samsung Galaxy Nexus] metalspring:
FYI, adb sideload does seem to be broken in recovery, even on linux-

metalspring@metalspring-laptop:~/Downloads$ adb sideload ./B66-Commotio-TORO-F2FSALL-FIXED.zip

* failed to write data 'protocol fault (no status)' *
[Samsung Galaxy Nexus] Atento:
Exactly the same results here with ext4.
[Samsung Galaxy Nexus] DR3W5K1:
FWIW I've never been and to sideload using TWRP. ADB push/pull has always worked fine though.
[Samsung Galaxy Nexus] osm0sis:
Might need some different mount options for f2fs.

Good reading: https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt
[Samsung Galaxy Nexus] dezful:
Some parts of proc/mounts still show ext 4. I don't know what that mean. :D

sent from Siemens C55
[Samsung Galaxy Nexus] chongns:
F2fs only on system, cache and data.

Sdcard is FAT, right?
[Samsung Galaxy Nexus] bsmitty83:
What sdcard ?
[Samsung Galaxy Nexus] chongns:
Internal storage. Locate at /data/media/0
[Samsung Galaxy Nexus] bsmitty83:
Its an emulated partition , data is f2fs , data is userdata , ie "sdcard"

Hack The Tuna
[Samsung Galaxy Nexus] osm0sis:
Here's all the Moto X has in its fstab:

/data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr,errors=recover wait,nonremovable,encryptable=footer

They mount system and I think cache ext4 still.
[Samsung Galaxy Nexus] metalspring:
inline_xattr is the only f2fs specific one in there. however this sounds interesting-

flush_merge-

Merge concurrent cache_flush commands as much as possible to eliminate redundant command issues. If the underlying device handles the cache_flush command relatively slowly, recommend to enable this option.
[Samsung Galaxy Nexus] oman0123:
Loving this already. Market installs are so much smoother now. Only issues I had were all user error (isn't it always?) Took me all day and I'm still setting up but close to the finishing touches.

I sideloaded mine with almost no problems -- Other than having to download everything and start from scratch on my old win7 laptop. That was a pain.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] michierusama:
I got a systemui force close error on maguro ROM.
[Samsung Galaxy Nexus] pattyboi:):
Now,hear me out guys:

(Remember,I'm not the smartest person plus its 1 am so I'm real dumb right now)

But,maybe we are judging f2fs wrong..

Maybe we shouldnt judge it's performance ONLY on its write and read speed,sure its a filesystem upgrade which should theoretically increase read/write speeds

But,maybe f2fs could benefit the gnex in a wider spectrum

Think: f2fs is devolped specifically for nand flash card/MMC cards,unlike ext4

Since f2fs is made for flash memory,wouldn't it cause less performance overhead since it would be less straining on the mmc card to make/write/read data and less straining would also mean less CPU cycles used as it wouldnt take as long to write/read data,less CPU cycles used during the read/writes means less power consumption,etc etc

Now I don't know if everting ties in like that,just my lil "conspiracy theory "

Anyway,the commotiono build is running great,no lag at all,responsiveness seems to be higher while things are downloading or installing ,great work Smitty,honestly your a f'ing amazing dev,same to you aosp,thank you guys for making this happen

(PS: to anyone having push problems with twrp,it worked for me after rebooting into twrp again and replugin my cable)
[Samsung Galaxy Nexus] p34rp34r:
All right...I've got this running on my toro now more or less. I'm running Windows 8.1, so all you naysayers, it CAN be done on Windows...

This is how I got there (standard "if-this-screws-up-your-phone-or-causes-thermonuclear-war-it-ain't-my-fault" disclaimer applies. bold means type as shown into command line, with the correct paths to the img/zips.) :

1. Backup

2. Copy backup to PC

3. Update ADB to latest (I'm using Android SDK, updated the platform-tools to 19.6.something. ADB says it is version 1.0.31)

4. adb reboot bootloader

5. fastboot flash recovery path/to/recovery/TWRP-TUNA-F2FSALL.img

6. fastboot reboot-bootloader

7. Use volume keys to reboot to recovery

8. In recovery, Advanced > f2fs/ext4 switch, change to f2fs, select all partitions, wipe <- this is why you backup :laugh:

9. Reboot to recovery again (I've had issues mounting partitions after wipes in the past)

10. In recovery, check adb devices to ensure device is connected (if not, open Windows Device Manager and scan for new devices)

11. adb push path/to/rom/B66-Commotio-TORO-F2FSALL-FIXED.zip /sdcard/

12. Wait until it says it's done

13. Install ROM, then adb push path/to/your/gapps

14. Install stock PA Gapps Apparently, stock and full-modular PA Gapps are too large for the /system partition? Installed mini. EDIT: Stock and full-modular can be force-installed by mucking w/ the updater-script and/or by using GApps Remover to make the install smaller. Be warned though, if you really don't have enough space, stuff might not work. I've been having Calendar Storage FC after doing this on my N7 and of course, Calendar isn't working right...

15. OPTIONAL: Flash [MENTION=4328678]metalspring[/MENTION]'s test kernel

16. Reboot

17. ????

18. PROFIT

Side note, I guess adb sideload does work, but at least for me, it required going to Windows Device Manager and refreshing. I think the issue [MENTION=4328678]metalspring[/MENTION] had was the reboot issue I mentioned in 9.

EDIT: PS, I really hope we can get the other Vanir (not Commotio/DHO's...appreciate the work, but I'm not a fan of some of the changes. I think the other one is nuclearmistake?) in f2fs.
[Samsung Galaxy Nexus] metalspring:
Adb push is not the same as adb sideload

Adb push simply pushes files to the device to whatever location you specify, then you have to flash it like any other zip, adb sideload sends the file to a temp directory on the device and then immediately flashes it for you. Adb push worked fine for me, its Adb sideload that didnt :P
[Samsung Galaxy Nexus] pvkiniyan95:
Did it...I did it....I ****in did it.....

As some of u know I messed my USB port a week ago so I couldn't connect to PC either in adb or fastboot and so decided to wait till I know everything works before doing anything...... Couldnt resist so flashed it and it works.....

Awwwyeaahhhhh....

BTW if u have problems with adb try what I did

1. Download and store required files in the phone (recovery and ROM,gapps)

2. Then I flashed the recovery with Flashify

3. Go to recovery and format /system and /cache alone to f2fs

4. Now using the file manager in TWRP recovery (pretty good)copy both the files (rom and gapps)to system or cache (I used cache)

5. Format data to f2fs

6. Now again move back those 2 files to /data from /cache or /system wherever u stored

7. Install them asusual...

8. Reboot....

Booooom I got it, hope it works for u guys too....

Of course take a backup before and tell me if it works :fingerscrossed: