yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] n76:
I assume you have ADB available, if so then you can check the mounts on your phone's OS:

$ adb shell
root@maguro:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,seclabel,relatime,user_xattr,barrier=1 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,nomblk_io_submit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-0 /data f2fs rw,seclabel,nosuid,nodev,noatime,background_gc=on,discard,user_xattr,inline_xattr,active_logs=6 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

I happened to have done a "adb root" earlier but I don't think you need root permission to run the mount command. Note that /data is listed as f2fs. But now that I look at it, it appears that I did not get /cache reformatted as it is showing up as ext4.
[Samsung Galaxy Nexus] Ziyan:
Help this dude get new maguro! We work together behind the scenes - did I mention that he was the who named this ROM? Haha, I suck at naming stuff, so he came up with this awesome one :)

While he can't build stuff (for various reasons), he continuously supports the gnex development - he plays an important role at keeping this device alive as well :)
[Samsung Galaxy Nexus] casaprocida:
It is hardware related. I change 2 time the USB/microphone circuit. It cost around 5 dollar on China market and it is easy to change with the help of ifixit.
[Samsung Galaxy Nexus] mb_3000:
Thanks for your reply! I'm not really sure what happened, but I did a full wipe and flashed everything again, and all of the sudden the usb port is working again. probably something to do with the kernel settings I messed up? or maybe the port is just failing. hope it works for a few more years :D
[Samsung Galaxy Nexus] phaleg:
It looks a bit hard for my level... is there any other way I can check it?

Maybe from recovery (latest TWRP) or from oS (Slimkat 4.4.4 r2)?
[Samsung Galaxy Nexus] Jagoflax:
Hi, you can install the app called DiskInfo from the Play Store and check it there

Enviado desde mi Nexus 7 WiFi mediante Tapatalk
[Samsung Galaxy Nexus] bamtan2:
I have donated my $10 to help fund [MENTION=2838735]aosp[/MENTION]'s development and testing efforts for Galaxy Nexus. And I know other readers have too! GALAXY NEXUS FOR PRESIDENT 2020!

IMO ZMOD performs as well as stock 5.1.1 on Nexus 5. The only problem is an important one: ZMOD has 1/4 the free RAM of Nexus 5 5.1.1. With various methods (Recently app, LMK/OOM whitelist, disabling services, uninstalling apps) I manually force just a few applications to stay open. Otherwise I find apps are constantly being killed.
[Samsung Galaxy Nexus] alagga:
(Post of the G2 Forum)

I get excatly the same problem. Cant swich to f2fs everytime i boot up i get ext4 again. Any solution for this?
[Samsung Galaxy Nexus] phaleg:
As far as I know, you can format only the 2 cache partitions to f2fs, not data...
[Samsung Galaxy Nexus] n76:
My /data seems to be formatted for f2fs:

$ adb shell
root@maguro:/ # mount
.
.
.
/dev/block/dm-0 /data f2fs rw,seclabel,nosuid,nodev,noatime,background_gc=on,discard,user_xattr,inline_xattr,active_logs=6 0 0
.
.
.
root@maguro:/ #
[Samsung Galaxy Nexus] huyphuco:
As I remember, almost lollipop rom doesn't support /system formatted to f2fs. Others can be in f2fs.
[Samsung Galaxy Nexus] alagga:
I think its a Problem with twrp itself. The G2 Users just got a fix with flashing a special kernel before formating to f2fs.

Is there a possibility to Format to f2fs via adb vor another recovery?
[Samsung Galaxy Nexus] sanjed:
=Antiallergiker;61551461]I think its a Problem with twrp itself. The G2 Users just got a fix with flashing a special kernel before formating to f2fs.

Is there a possibility to Format to f2fs via adb vor another recovery?[/QUOTE]

I was not able to get f2fs to work with twrp 2.8.6.0 so I flashed 2.8.5.0 instead and it worked straight away. Give it a go.
[Samsung Galaxy Nexus] alagga:
Thanks :) where u downloaded the 2.8.5.0 with f2fs support?
[Samsung Galaxy Nexus] sanjed:
Page 59 of this thread, post 584.
[Samsung Galaxy Nexus] Pee_kee:
Is there anyway to change bootanimation..??
[Samsung Galaxy Nexus] musical_chairs:
The problem is recovery's kernel; see below.

Some do, some don't. I'm not sure about ZMod, but since the gains with f2fs are in writing operations (/system is read-only during normal operation), there's not much point and it costs precious /system space to format it to f2fs.

The official TWRP builds can format to f2fs. The problem is, their tuna kernel code does not have f2fs support, so they can't mount, read, or write any f2fs partitions. You could format /data and /cache to f2fs, then re-boot your ROM and it will work just fine (I've done this). Of course you won't be able to back up or restore with TWRP then, and that's not a place you want to be. So you'll need a custom build of TWRP with f2fs enabled in the kernel, not the official TWRP builds, if you want to use f2fs.
[Samsung Galaxy Nexus] alagga:
[MENTION=5840086]zyian[/MENTION] could you put these recoverys in the Download section or as a litttle note in the thread?

As the 2.8.6.0 doesnt work properly. With 2.8.5.0 no problems :) :good:
[Samsung Galaxy Nexus] n76:
I used the TWRP 2.8.6.0 with f2fs that is in the download area of this thread to format /data to f2fs so it seems fine in that regard. My only issue with it is that it has encryption broken.
[Samsung Galaxy Nexus] phaleg:
There is a TWRP suitable for f2fs (*.img) ... can you flash it in recovery?

Once it is done, how should you set that the right partition will be f2fs?

Should the rom as well support f2fs?

I am a n00b, trying to understand how it works
[Samsung Galaxy Nexus] bamtan2:
I'm a newbie but I think the recovery needs to support f2fs to format it that way, the kernel needs to support f2fs to read it, and the ROM distribution needs to support f2fs to work with it. So yeah that'd mean everything needs support :)

ZMOD and the TWRP builds mentioned here all support f2fs, but there are bugs with TWRP, as you can see. People who have one bug will switch to a different version to hopefully bypass that bug.

If you format to f2fs, note that "internal storage"/"sdcard" is a virtual partition on the /data partition. When people say TWRP "wipes /data" they usually mean "deletes everything on /data except the sdcard data", which is kind of confusing for some of us. So when they go to format the /data partition to be f2fs, they don't realize that this will actually destroy EVERYTHING, including the virtual /sdcard. So EVERYTHING you want to keep needs to be backed up, because all of it will disappear when you FORMAT these partitions.

What is the best or easiest way to backup the whole device? That I do not know. In theory it should be easy to do a nandroid backup of all the data stored in the system and store it on the /sdcard, then backup the whole sdcard by USB cable to your computer, then you could reverse this process to put the device back to the way it was. But I have never found an easy way to do this. I've tried some different tools, but they errored before copying all the files. I don't know of any "gparted" for android that will just make disk images that you can easily move and work with.
[Samsung Galaxy Nexus] osm0sis:
My adbsync sdcard backup script for Windows is an easy way to do so.
[Samsung Galaxy Nexus] aosp:
Thanks alot dude now if only other gnex users cared about the time and effort that goes into these free ROMs as much as you do ?
[Samsung Galaxy Nexus] n76:
Your "Donate to me" button goes to a 404 page for me and even if it worked, it looks like the URL is for Google Wallet which I don't do. Do you have a PayPal account I can send my donation to? Thanks!
[Samsung Galaxy Nexus] bamtan2:
Fix your donate link or link to ziyan because this post will only get more and more buried over time :) http://xdaforums.com/showpost.php?p=61529688&postcount=1017
[Samsung Galaxy Nexus] siealex:
https://play.google.com/store/apps/details?id=eu.chainfire.liveboot

Install it, open, agree to install the script. You won't need any bootanimation...
[Samsung Galaxy Nexus] n_petr:
Hello. Have all spontaneous reboots been fixed in recent [ROM] [5.1.1] ZMoD and [ROM] [5.1.1] CyanogenMod 12.1 Beta builds?
[Samsung Galaxy Nexus] aosp:
jaraidaniel@gmail.com
[Samsung Galaxy Nexus] n76:
Thanks!

“Check is in the mail” :)

(Actually, it is via PayPal and you should receive it, or notification of it very quickly.)
[Samsung Galaxy Nexus] robocop2000:
Can you please give me a link for xposed download for our device (also gravitybox). I didn't find it!

Thank you in advance!
[Samsung Galaxy Nexus] aosp:
Last zMoD maguro build [MENTION=2633638]Ziyan[/MENTION] uploaded has almost 3000 downloads already? :eek:

So far only [MENTION=4545566]bamtan2[/MENTION] and you care enough to help me out but hope is still alive cause of gnex users like you guys thanks alot ;)
[Samsung Galaxy Nexus] n76:
It won't mount my encrypted f2fs /data partition.

Logging looks the same as with the f2fs TWRP 2.8.6.0 that Ziyan put in the downloads area so maybe it will work with an unencrypted f2fs mount. If anyone has that it might be nice to verify that the normal builds of TWRP for Maguro support f2fs.
[Samsung Galaxy Nexus] tlwhitec:
Another $10 heading to Zyian's PayPal. Although I don't own a maguro anymore, it still stayed in the family. Thanks for your efforts! I really appreciate it.
[Samsung Galaxy Nexus] alagga:
So i took the time to make a short tutorial how to formate to f2fs :

(- Backup apps,etc. with Titanium Backup)

- Backup all data from internal sd-card (via OTG/ADB*/MTP)

INTERNAL SD-CARD GETS WIPED!!!

- download latest Zmod + Gapps to your PC

- download TWRP with f2fs support (2.8.6.0 making problems on some devices)

2.8.6.0 -download-section

2.8.4.0: http://xdaforums.com/show...postcount=1817

2.8.5.0: http://xdaforums.com/show...postcount=1847

-flash TWRP (for example with flashify)

- reboot to recovery

- Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS

- Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS

- Reboot recovery

- Pull the Zmod + Gapps to your phone (via OTG/ADB/MTP)

- Flash Zmod + Gapps

- reboot to system

- now you can copy the saved sd-card Content back to the phone (via OTG/ADB*/MTP)

(- Restore Apps with Titanium Backup)

- be happy with your f2fs Device :D

*Howto Backup+Restore with adb:

- pull files from device to PC: adb pull /data/media sd_backup

- Copy the saved SD card content back to device: adb push sd_backup /data/media/0/

Thanks to Obihoernchen.net and bamtan2
[Samsung Galaxy Nexus] sergialess:
I was a f2fs enthusiast, but I went back to ext4 for compatibility reason.

Do you think it is worth to give f2fs a second chance?

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] AgentSmith:
Personally I don't understand the whole fuss about f2fs. It's not (yet?) fully supported in Linux and there isn't even a noticeable performance boost, on my GN at least. So yes I tried it but I believe I know better now which is simply to stay away and stick to ext4.
[Samsung Galaxy Nexus] n76:
Just curious. . . On my GN when running CM10 or CM11 it would start to lag after a week or so and I'd have to do a fstrim operation on /data and /cache to "fix" it. In theory the fstrim should have happened automatically on a periodic basis but I found no evidence that it was. Have you had any issues with needing fstrim to be run periodically when using ZMoD?

Running ZMoD with f2fs on /data feels quicker and more responsive than CM11 and it is staying responsive, not bogging down over a period of a week or more. How much is due to it being ZMoD rather than CM, or being Lollipop rather than KitKat or f2fs rather than ext4 I don't know. But so far the ZMoD on f2fs has been really solid and responsive for me.
[Samsung Galaxy Nexus] siealex:
F2FS damages our flash chips several times faster than ext4.
[Samsung Galaxy Nexus] n76:
References or link please. . . My quick web search did not turn up that as an issue.

Thanks!
[Samsung Galaxy Nexus] AgentSmith:
Zmod lags heavily with ext4 after a month or so. Unfortunately fstrim doesn't solve the issue so I doubt f2fs would make a difference. It's simply ROM related. In my case I'll just wipe data one day and start over.

That seems highly doubtful. F2fs is made with flash chips in mind. Then again I am no expert so you won't hear me falsify such a claim either. I wouldn't worry about it though.
[Samsung Galaxy Nexus] Säschu:
Feedback to ZMoD-20150617-maguro build

Hell - after two days of use I can only say the ZMOD build is a hammer package - thanks Ziyan !

Why is this thing flying so fast ? I use the mentioned build with LuckyK-V.2.5_AK2 Kernel (was somewhere in this long thread a recommendation of someone) and tk_gapps-modular-pico-5.1.1-20150620-signed as daily driver. The phone is also encrypted and unrooted (company policy). The phone is even blazing fast and smooth after encryption. I came from CM11 and afterwards omnirom Kitkat. No comparison...can't believe. Rock stable and fast as hell.

So well done.

Only few things I want to mention:

- Still have (as I also had with all CM and omni) once all 1-2 days a crash report - but phone still works as usual.

- While use (display on) the device gets little hotter on camera lens than other roms...is this ROM/Kernel somehow little overclocked ? However...nothing I am worry about...

- Sometimes wireless stops working (can not activate) and requires reboot of the device

- Battery usage is slightly worse compared to the kitkat roms. Anything I can do here ? Greenify without root and xposed is no help.

So far everything else seems to work well, BT is OK, Mail (Exchange and IMAP) works perfect, camera works, and it's faaaaaast - did I already mention that ? ;)

So thanks guys for that hammer rom and kernel. If you get that battery "draining" and temperature issue solved this may become a perfect Lollipop for our old Maguros.

This combo is definately worth a donation...will search later for the donation link(s) :fingers-crossed:
[Samsung Galaxy Nexus] siealex:
But why did tens of people here burn out their flash chips in 1..3 days after switching to F2FS?
[Samsung Galaxy Nexus] alagga:
I dont think it'll burn our flashchips, as it is the stock format on some devices.

But the difference of f2fs and ext4 is not really much noticable. Seems a bit faster (after a few days use).
[Samsung Galaxy Nexus] jhonnyx:
Highly doubt that's F2FS related. It's more related to layer 8.
[Samsung Galaxy Nexus] Nautilus74:
I stay in f2fs on my GNEX since you can do it..... my GNEX has undergone at least 500 flash to date.

It is still perfect and does not slow down even when I leave only 2 GB of free memory.....

....at least until today...:p
[Samsung Galaxy Nexus] AgentSmith:
Talking about lag... Yesterday I tried uploading a 500 MB file to my Google Drive over WiFi. Nothing happened. It didn't even show up in the app's upload queue. An hour later I forgot about it. But last night it turned out it had finally started uploading, except now it ate away half my data package as it lost WiFi connection before the upload. I uninstalled Google Drive for now, just to be safe. Lag or what?

I'll wipe data very soon. :)
[Samsung Galaxy Nexus] axbl:
Is it possible to let the softkeys on all the time ?

They dissapear after a few seconds....
[Samsung Galaxy Nexus] bamtan2:
For what it's worth, I've been running ext4 ZMOD and FullAuto kernel from May, about 1.5 month ago, and the device is still working well. But because 5.x has less memory available than 4.x, I need to hack at this problem manually to make it all work.

I have uninstalled/disabled apps to save memory. I have been using Opera Mini browser because it seems to use the least memory in my testing. Also, I have enabled Nova Launcher's "Advanced" priority-raising feature to keep the launcher open more often.

I also find the LMK settings are not effective with the apps I use, so I have set my LMK settings to be slightly unusual. I did this because I used "Auto Memory Manager" to look at the types of app in each LMK/OOM lifecycle category, and I noticed the category memory levels and process OOM priorities did not align with my interests. For example: Google Play services are higher priority than real apps I use. It is a waste for my favorite apps (including the launcher and keyboard) to be closed just to keep unused services open.

But because I don't know how to permanently change process priorities, I have cheated and made "Background Process" the same OOM/LMK priority as all the services. This serves to bring their priorities slightly closer together. Then I have installed the "Recently" app by [MENTION=631273]Chainfire[/MENTION] to help me manually manage the Background Process. It doesn't always work to remove closed apps from the Recents menu, but it helps. I manually manage the Recents list to keep only 2-4 apps open at once.

Foreground Application: 50MB
Visible Application, Secondary Server, Hidden Application, Content Provider: 100MB
Empty Process: 250MB

I chose 100MB as the common memory limit here because 100MB is about how much is necessary to launch the biggest applications I use, directly into memory, without doing paging to disk every time something new is run.

So, by using as little memory as possible (uninstalling apps, closing apps...) and keeping 100MB available at all times, the speed of ZMOD still seems good after 1.5 months used.
[Samsung Galaxy Nexus] sergialess:
[MENTION=4545566]bamtan2[/MENTION], you make me flash Zmod again and tweak it as you did. Thanks.
[Samsung Galaxy Nexus] osm0sis:
That's the launcher/apps crashing and restarting; what you both describe are the ongoing memory management issues present in Lollipop for the GN. :(
[Samsung Galaxy Nexus] AgentSmith:
Well I wiped data and things improved noticeably. At least now when I press the home button the phone responds within a second. ;)

Just to be clear, I still absolutely love this ROM! I can live with the phone's shortcomings and age. Devs here have already performed miracles so who knows what's still in store for us. :)
[Samsung Galaxy Nexus] n76:
Really, really minor points and more questions than problems. . .

1. Comparing the UI on my GNex Maguro running ZMoD 5.1.1 with my spouse's Moto E LTE running stock 5.1 from Motorola (purchased direct and not through a cellular provider). I notice that the carrier name is on the top left of the Moto screen. Its there on the lock screen on ZMoD but not once unlocked. I don't see a setting for changing that.

2. On ZMoD there is a slight color band on the bottom on the bottom of the lock screen. And once unlocked there is also a band on the top of the screen. None of that on the Moto E which makes the Moto E look a bit cleaner. Again, I don't see a setting for changing that.

3. I've set the same background image on both phones and on the GNex is looks a bit color shifted. But when I open the image in the gallery app on the GNex the color is fine. So I don't think the issue is the image or the GNex screen but maybe something to do with handling background screen images. Again, I don't see a control for playing with that.

As I noted, these are really minor things. This ROM rocks! But it would be nice if I could tweak the above. :)
[Samsung Galaxy Nexus] alagga:
With this Rom the Galaxy Nexus is really fast and stable.

The only Problem (with Lolliop/this Rom) is that you cant keep more than one app open at the same time.

Every app-switch reloads the app.

Gesendet von meinem Galaxy Nexus mit Hilfe von XDA Forums
[Samsung Galaxy Nexus] eternal70:
Try this minfree settings. Yeah it help a bit, because we can't do anything about our 1 gb ram
[Samsung Galaxy Nexus] siealex:
1. The position of the carrier name is exactly as in stock Android.

2. This band is a hardware problem in one of two versions of Maguro displays.
[Samsung Galaxy Nexus] nikodr:
Rhe minfree settings from nephelim i use on r20 with zmod on are

50

70

116

130

165

370
[Samsung Galaxy Nexus] alagga:
Yeah with nephelim settings the overall seems smoother, but you have no real Multitasking -.-

With the other settings you get more lag

Gesendet von meinem Galaxy Nexus mit Hilfe von XDA Forums
[Samsung Galaxy Nexus] Fenix46:
which kernel uses?
[Samsung Galaxy Nexus] alagga:
stock kernel, as i got lags with the last versions of LuckyK
[Samsung Galaxy Nexus] Fenix46:
with stock kernel, is not convenient to change the minifree, because it is designed to work well without touching anything. if you have lag try doing a wipe data. for the lucky, strange that have lagged, and perhaps the governor, but I personally tried the kernel of zmod with ondemand and that's great, but not for everyone and so :)
[Samsung Galaxy Nexus] AgusL:
I can confirm that last lucky version and previous one are slower than 2.3. I am having a lot of lag when pressing the app switcher button and perfomance un general is slower. v2.3 was the best one. Maybe I should try doing a clean ROM + kernel flash.
[Samsung Galaxy Nexus] Fenix46:
sometimes you have to do a wipe with toolkit, because the recovery is not always cleaned well. I did one yesterday because I could not try the slim, even a stock kernel, and also with zmod I had a bit of lag... :)
[Samsung Galaxy Nexus] AgentSmith:
Do you mean TWRP doesn't always do a full data wipe? I wiped data yesterday and I still have a lot of lag. With older Zmod builds my phone was a lot more responsive.
[Samsung Galaxy Nexus] Fenix46:
Yes... But normal wipe, with recovery, or full wipe with toolkit or fastboot??
[Samsung Galaxy Nexus] AgentSmith:
Wipe data with TWRP, leaving /data/media intact. Basically the standard wipe option, without using the advanced options.
[Samsung Galaxy Nexus] Fenix46:
As I think, the wipe from twpr are not always good, sometimes you have to do a total wipe with toolkit, clean all the memory and start from scratch, so the device resumes normal operation
[Samsung Galaxy Nexus] ykom:
It's a great kernel, but headset controls never work, right?

Sent from my G Nexus
[Samsung Galaxy Nexus] Ziyan:
A line gone from the kernel caused it to break again, will fix it in the following new release.
[Samsung Galaxy Nexus] robocop2000:
Ziyan, are you working for a desktop extended feature in the new release? It's more important for our device have this function! As you know there are some problems with a stamp image on screen! :(
[Samsung Galaxy Nexus] Ziyan:
Yes, I'm considering some new features for the new builds. :)
[Samsung Galaxy Nexus] ptmax13:
I vote for "ram optimizations" first, and then for new features...

:p
[Samsung Galaxy Nexus] siealex:
Downgrade to ICS or JB 4.1 and stay on it, there are no other ways.
[Samsung Galaxy Nexus] WilliamVig:
Hello I`m new to the XDA world and I`d like to know how do I install/flash/activate F2FS, I keep hearing about it and I heard that it`s supposed to be good.
[Samsung Galaxy Nexus] bamtan2:
I believe this is the short answer:

1. Flash TWRP (only some custom builds of TWRP support F2FS)

2. Format /data and /cache to F2FS using TWRP (this destroys ALL your data)

3. Flash android ROM using TWRP (only new ROMs support F2FS, but some older ones can be converted manually with a tool found on the forum)

:)