yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yotvb531:
Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.

https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1

https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1

MD5 Sum: e6c265c57e00b4949362d6ff53c9a799
[Samsung Galaxy Nexus] musical_chairs:
Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.
[Samsung Galaxy Nexus] SpideyTheMan:
As always thanks for the new build! And thanks for all you do! Using Trickster MOD I can clearly see that 384Mhz is the kernel default in battery mode Power Save and Balanced. The GPU jumps to 512Mhz max in Performance. In any mode the GPU will drop back to 153Mhz within 3 seconds when it is no longer needed. So it seems likely that something about the GPU dropping back to 153Mhz that might be the culprit causing the kernel crash. Based on the following article which quotes a Google developer on why they choose a 307Mhz GPU clock in their original Tuna kernel builds it appears that the 512Mhz OC yields little relative performance increase for all the additional power consumption and 384Mhz was even not seen by Google as begin worth the battery life. At 153Mhz the clock will not drop any more so I may try this slower clock rate to see if this helps with the GPU crash. http://techie-buzz.com/android/why-is-the-gpu-inside-the-galaxy-nexus-clocked-at-308mhz-instead-of-380mhz.html
[Samsung Galaxy Nexus] musical_chairs:
I'll have to look into this. I thought Ziyan had them working on his ROMs (with the newer power control driver), so I dropped the config change I had put in there to use the old ones.
[Samsung Galaxy Nexus] elbi14:
thanks for respond. :o

all working great. with all partitions ext4 . :highfive:
[Samsung Galaxy Nexus] SpideyTheMan:
I've noticed that with the latest builds I'm no longer seeing issues with phone crashing/rebooting due to PowerVR SGX GPU issues. This is even without using Trickster MOD to modify the clock of the PowerVR SGX GPU chip from kernel defaults. I typically run in battery mode Balanced which runs the GPU at 384Mhz and it drops back to 153Mhz after 3 seconds of decreased demand. So this problem doesn't seem to be an issue any more. Maybe it was the power management settings after all. Overclocking the GPU doesn't happen unless you run in battery mode Performance and I typically don't do this so I think I'm good there.

I am still noticing audio hal issues with occasional pops and clicks but it seems to be a better. Haven't tried f2fs but might queue that up for later. No LTE in any build lollipop for Galaxy Nexus to date but 3G is working well.

Thank again!
[Samsung Galaxy Nexus] musical_chairs:
I believe the issue was that without this open commit: http://review.cyanogenmod.org/#/c/97042/ the GPU would scale up to 512MHz no matter what the performance mode was set to. And while that works just fine on my phones, yours apparently doesn't like being overclocked that much. With that commit, though, the performance mode can change the max GPU frequency, so in Balanced mode it tops out at 384 MHz. Glad to hear that the reboots seem to be gone.
[Samsung Galaxy Nexus] SpideyTheMan:
Thanks for the explanation. The phone is working well. Very much appreciated.
[Samsung Galaxy Nexus] musical_chairs:
New build up. 1080p videos play smoothly now (fixed by Ziyan).

I will be working on another (non-android) project for the next three weeks or so. So unless there are major bugs with this build, there won't be any new ones for a bit. Don't worry, I'll be back. :)
[Samsung Galaxy Nexus] SpideyTheMan:
Thanks for the new build! I'll give it a go this afternoon! Would you mind clarifying support for f2fs in the prior 5/12 build? I've attempted to convert /cache to f2fs using TWRP 2.8.6.0 with a copy of mkfs.f2fs I placed into /sbin. Formatting /cache as f2fs worked fine but TWRP then begins to complain that it cannot mount /cache after the conversion to f2fs. So does this mean that kernel support for f2fs is missing or did I happen to skip a required step in the process of converting to f2fs? Any recommendations would be appreciated... Thank you!
[Samsung Galaxy Nexus] musical_chairs:
Do you have a f2fs-enabled recovery? I don't think the official TWRP builds support f2fs. So you probably are right that kernel support isn't there for f2fs, but it's TWRP kernel support that's lacking, not ROM kernel support. I don't know if anyone has put up a f2fs-enabled TWRP for toroplus or not.
[Samsung Galaxy Nexus] SpideyTheMan:
Thanks for the pointers! Yes, you were correct. I had been using the standard TWRP builds and was unable to locate TWRP with F2FS specifically for the toroplus. I've modified the instructions below to use musical_chairs TWRP build with F2FS for toroplus devices. Here is twrp-2.8.6.0-toroplus-f2fs.img which I was able to successfully use to switch to F2FS for the /cache and /data partitions.

The steps required to switch to f2fs on toroplus are as follows:

1. Flash recovery with musical_chair's TWRP 2.8.6.0 with F2FS for toroplus.

2. Backup data partition using TWRP recovery.

3. Copy the current TWRP data backup to a PC so that the data isn't wiped when you format the data partition. Also backup sdcard data to preserve any important pictures/videos/etc on the internal sdcard since it will be wiped when you format the data partition.

4. Wipe cache using the appropriate menu in TWRP and select the option to change filesystem to F2FS.

5. Wipe data using the appropriate menu in TWRP and select the option to change filesystem to F2FS.

6. Reboot TWRP into recovery so that you can mount the data partition again. If you have any problems using writing to sdcard after rebooting reboot into recovery again. If the problem persists after 2nd reboot re-format data as ext4 and then format data again as f2fs. Reboot into recovery and you should be good.

7. Copy TWRP data backup from your PC onto your toroplus.

8. Before restoring TWRP data backup go into TWRP settings and enable the option "Use rm -rf instead of formatting" to prevent the restore from reformatting the data partition as ext4.

9. Restore your data backup using TWRP restore.

10. Reboot and be amazed.
[Samsung Galaxy Nexus] SuperGoober:
Thanks for the directions Spidey but let me ask you a question . Are you just formatting data and not touching internal storage or does it get wiped as well ?
[Samsung Galaxy Nexus] ClintE1956:
I've read that f2fs is not as reliable as ext4, and that it also takes up a lot more room on a partition than ext4. Also, after crashes (more frequent on f2fs according to reports), files left open are supposedly not able to be written to or deleted, requiring wipe/format of affected partition.

Granted, I've never tried f2fs, and there are a lot of people who love this file system that seems to be optimized for flash systems.

Thoughts / opinions ?
[Samsung Galaxy Nexus] SpideyTheMan:
I believe that on the Galaxy Nexus, the data partition is shared by both the data and sdcard filesystems. So you should backup anything important from the sdcard before formatting the data partition as f2fs. I do know for certain that once you format the data partition as f2fs you that your sdcard data is also wiped and sdcard cannot be mounted again without a reboot of TWRP. I have two (2) toroplus devices and the first one wiped the data partition cleanly but on the second device I had to format data as f2fs, reboot into recovery, and then I couldn't use sdcard so I formated data again as ext4, rebooted into recovery, and formatted data as f2fs again, then rebooted into recovery. This time sdcard was usable again and I could copy the TWRP backup onto the phone and restore.

---------- Post added at 06:31 PM ---------- Previous post was at 06:18 PM ----------

I don't have that much practical experience with f2fs but from reading up the f2fs filesystem design paper by the Samsung developers it's obvious that a lot of thought went into the design and how a new filesystem was needed to leverage the unique characteristics of flash memory. As far as I can tell there is no inherent design problem with f2fs that would make it less stable for storage but only time will tell. Just make good backups and give it a try if you are interested. One paper is available F2FS: A New File System for Flash Storage. Another f2fs overview that is a good read is also available as F2FS: A New File System Designed for Flash Storage in Mobile.
[Samsung Galaxy Nexus] ClintE1956:
I will be doing some tests with f2fs on the toroplus soon, as that phone is now a backup device.

I'm going to attempt this scenario:

1. Full TWRP backup

2. Copy sdcard to computer

3. Wipe everything

4. Format relevant partitions as f2fs

5. Restore TWRP backup

6. Copy sdcard from computer back to phone

Is this possible? Or would it be better to just do the full wipe/format then fresh install CM12.1 (or whatever) and apps?
[Samsung Galaxy Nexus] SpideyTheMan:
Yes, that should work. I'm not sure how portable data is between major Android versions so mileage may vary. When I first switched to CM 12.x I wiped everything to get a fresh start. I've been using musical_chairs's builds of CM 12.x for toroplus as my daily driver for quite some time. I have three (3) toroplus devices with one (1) running stock and two (2) running CM 12.1. Works great... very usable....
[Samsung Galaxy Nexus] SuperGoober:
Nandroid Restore Problem

Unrelated to the above f2s question I wondered if anyone has run into the issue of nandroid restore with system over 628 megs failing , I had 2 nandroids made this morning . It would restore system fine until it reached 628 megs and it's like it runs out of system space and fails , If I don't install all my apps and keep the system size down around 600 megs then its fine . It's rendered any nandroid I made useless and impossible to restore where the system size happened to exceed 628 . The problem with this is if i backup my perfectly working device with a system size of say 630 megs then that nandroid is destined to be useless . Why will my nexus allow me to install that much system data , backup to nandroid succesfully and balk at letting me restore that much data ? I don't know if the problem is with twrp ( newest and next to newest versions ) or if its the device or some other bug . Can somebody load their phone up with plenty of apps and do a nandroid with over 628 megs system space, and confirm if you can restore the nandroid sucessfully ?. Try about 650 megs maybe . It's like it hits a brick wall at 628 . Anyone have an idea about this ? thanks
[Samsung Galaxy Nexus] SpideyTheMan:
According to the XDA developers wiki on the Samsung Galaxy Nexus you should have sufficient filesystem space to perform the restore even after formatting. Look at the restore log file and maybe it may provide a hint as to why the restore is failing.
[Samsung Galaxy Nexus] SuperGoober:
Yeah but thats a straight nexus . I've never not been able to restore nandroids . If I create one that's 627 megs it's fine . Thats why I'm hoping someone else will try and confirm whether or not they can restore larger than 628 or whether we've picked up a bug with twrp or something else . You love testing , give it a shot and lets find out . Remember we're on a very non stock layout using android L that's not really supported by CM , out on a limb so to speak .
[Samsung Galaxy Nexus] elbi14:
My step to switch from ext4 to f2fs :

* Backup data (all) to PC

* Use FML TWRP 2.7.1.0

* Format system(ext4). then flash ROM/Gapss or other system files what u need to flash

* Format/change data and cache to f2fs

* Reboot devices.

after boot copy your data back up on pc to phone again.

CMIIW . :P

its worked always on kitkat rom.

I have not tried it on lollipop rom
[Samsung Galaxy Nexus] ClintE1956:
Is it true that the latest build of CM12.1 for toroplus will not install using the maguro recovery? That recovery flashed ok and seems to create backup properly, but when I go to install toroplus CM12.1 it gives me error:

This package is for device: toroplus; this device is maguro

Recovery seems to think it's a maguro device since I flashed the f2fs-supporting 2.8.6.0 maguro version of TWRP.

Is there a workaround for this?

Thanks
[Samsung Galaxy Nexus] SpideyTheMan:
Not good. I only used the maguro recovery to convert cache and data to f2fs, not to flash a new rom. It's not surprising that it wouldn't let you. At this point we may need to keep a few recovery images available until we have an toroplus TWRP with f2fs ... :o)
[Samsung Galaxy Nexus] SuperGoober:
You might want to edit your instructions to include the step of changing the recovery back . I haven't done this yet but I would have done the same thing he did . I was assuming the maguru recovery was compatible period until I read his post .
[Samsung Galaxy Nexus] SpideyTheMan:
After a bit of research it seems that things aren't as bad as they look. There is an acceptable workaround. Until someone comes up with an official toroplus TWRP with f2fs we'll need to continue to borrow from the maguro community. The workaround is as follows...

The check for the device type is not being performed by TWRP -- it's being performed by the ROM updater script so all you need to do is change the ROM updater to allow it to install on a 'maguro'. To do this open the desired ROM in 7-Zip, navigate to META-INF\com\google\android and edit the file 'updater-script'. Change any references in the script from 'toroplus' to 'maguro' and then save the updated script to the ZIP. Upload this modified ROM to your device and you can then flash the ROM without being stopped by the 'maguro' conflict trying to install a 'toroplus' ROM. I found this idea in the 1+OnePlus forums and will give credit for the idea to the guys at this link.

---------- Post added at 05:29 AM ---------- Previous post was at 05:24 AM ----------

Changing the recovery back doesn't work either. As soon as you change the recovery back to a recovery without f2fs you no longer have access to the data partition so data and sdcard are inaccessible. So that makes flashing a new ROM a challenge to say the least. But after a bit of research I did come up with a workaround that allows us to use the 'maguro' recovery with f2fs on our toroplus devices and still flash a toroplus ROM. It's was really pretty simple. Just modify the ROM as described and replace any references for 'toroplus' and change them to 'maguro' in the updater-script. You can then flash any 'toroplus' ROM on a 'maguro' recovery. Problem solved.

---------- Post added at 05:52 AM ---------- Previous post was at 05:29 AM ----------

From what I hear FML TWRP 2.7.1.0 is another maguro recovery with f2fs support, so in theory it should work but you'll probably need to modify the toroplus ROM to install on a 'maguro' recovery...
[Samsung Galaxy Nexus] SpideyTheMan:
This is well documented in this thread now so you should be good. Reference this post if you would like the details on switching to f2fs on toroplus.
[Samsung Galaxy Nexus] ClintE1956:
After returning to investigate the toroplus last night for a few minutes, I came to some of the same conclusions everyone else did. Either edit the rom (preferable) or switch back and forth between recoveries; not a big deal to switch back and forth, but not as simple as edit rom. Good to know it probably won't work flashing recovery(s).

Only issue is, after flashing maguro, can't access data partition from computer while in recovery (to grab backup created with maguro recovery). Probably need to erase/reload driver on computer.

Thanks to all
[Samsung Galaxy Nexus] SpideyTheMan:
The maguro recovery should not affect your ability to access the data partition. It didn't for me. I could still access the sdcard without issue. Make sure that MTP is enabled and that your data partition is mounted. Lastly simply unplug and re-plug the USB cable or reboot your PC and do the same USB cable dance. Make sure that you see the device in device manager and that it doesn't come up as an 'unknown device'....
[Samsung Galaxy Nexus] funka81:
Good ROM,thank you !
[Samsung Galaxy Nexus] SuperGoober:
I don't do f2s but I do know a guy with limited skills did a twrp for the s3 in about an hour that worked . Perhaps you could ask the guy that did the maguro twrp to fix the one for toroplus ? He would probably jump on it and fix it in no time . Do you know if anyone has done a twrp for the toro ?

[MENTION=4531957]musical_chairs[/MENTION] Rom runs fantastic !!! You have done a great job man . Thanks so much !
[Samsung Galaxy Nexus] musical_chairs:
Thanks guys for helping each other out, and glad you are enjoying the ROM. I can look into doing a TWRP build for toroplus once I come back online. I already have the ZMod source tree on my computer so it shouldn't be too hard.
[Samsung Galaxy Nexus] elbi14:
New Hope. :highfive:
[Samsung Galaxy Nexus] musical_chairs:
Your hoping can now end - in fulfilment:

https://www.androidfilehost.com/?fid=23991606952615221

F2fs-enabled TWRP built from the ZMod repos, for toroplus.

The hardest part about building this was figuring out that I needed to check out the remoteproc-f2fs branch of the kernel in my ZMod tree (it's not pulled by default in the ZMod manifest). For the longest time I couldn't figure out why it could format to f2fs (successfully, too, because the ROM booted and had no problems mounting data), but it couldn't mount data or cache unless they were ext4. Anyway, it's all good now, and my backup toroplus (the one that eats battery and has broken glass) is flying on f2fs.
[Samsung Galaxy Nexus] JerichoKru:
Surely you mean 2.8.6.0?
[Samsung Galaxy Nexus] musical_chairs:
:o It doesn't say that anymore...
[Samsung Galaxy Nexus] musical_chairs:
Those instructions are good, I followed them. Or I tried to...on my first attempt I got stuck at step 6 because my first build of TWRP wouldn't mount /data, but that's fixed now. And then I forgot to go back to the guide after that, and so I missed step 8 completely. Data stayed on f2fs, it did not get re-formatted back to ext4. I don't think /data ever gets formatted on the GNex unless you explicitly select that, as formatting /data wipes /sdcard too (which is why all that backing-up is necessary when switching file system types). But selecting the 'rm -rf' setting won't hurt anything either, since you have already just formatted /data. I would de-select it again after you are all done, so /system will get formatted on normal installs and restores.
[Samsung Galaxy Nexus] musical_chairs:
A new build is up. Interesting changes are:

- Video recording should work in many more apps now. Snapshots during video are also working. Unfortunately, a small purple line has reappeared on the videos. So, recording with the stock app is slightly less perfect than it was in the 5-21 build.

- CyanogenMod seems to have a new 'vertical' app drawer that will be selected by default. You can still choose the old horizontal one.

Have fun!
[Samsung Galaxy Nexus] SpideyTheMan:
Awesome! Thanks for the toroplus TWRP with f2fs. It's great to have an official TWRP for toroplus! Appreciate your work on this. I also installed your latest build of CM12.1 and all is well on my two phones running with f2fs /cache and /data. Smooth and running great!
[Samsung Galaxy Nexus] SuperGoober:
f2s questions

Ok I understand these intructions fairly well but I'm not sure about a couple of the steps.

When I copy the nandroid back over am I suppose to be in twrp , fastboot mode or what ? Am I suppose to use odin ? My pc is not seeing the phone in either fastboot mode or twrp . The instructions say to copy the nandroid back over but not how I'm suppose to do that . Can anyone shed some light on the steps ? Thanks
[Samsung Galaxy Nexus] musical_chairs:
No, not odin, nor fastboot. You want to copy it over in TWRP, using MTP. MTP should be enabled by default, but if it's not, you can enable it under the 'mount' menu. If it is already enabled, try disabling MTP then re-enabling it. You can also push the files to your phone (while booted in TWRP) using adb, but that shouldn't be necessary. On my toro, I used somebody else's build of TWRP and I couldn't get MTP to work on that, so I pushed the files with adb. But MTP is working fine for me on my TWRP builds.
[Samsung Galaxy Nexus] SpideyTheMan:
If you aren't familiar with the process of copying files while booted into TWRP recovery using MTP there are a lot of good tutorials online. Maybe this will help:

1. Download and install the Android SDK Tools.

2. When installing select the following components: Android SDK Tools, Android SDK Platform-tools, Android Support Library and Google USB Driver.

3. After you boot the phone into TWRP recovery and plug it in look in Device Manager on your PC to verify there are no "unknown device" listed. If there is update the device and install the generic Google driver found in "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver" which was downloaded as part of the Android SDK Tools.

4. Once everything is working you should see the phone listed as a drive in your system. This drive can be used to copy files to and from the phone's sdcard filesystem.

5. Now that you have the Android SDK Tools installed if all else fails you can use ADB from an elevated command-line prompt to pull or push files from/to the phone. You'll find ADB in "C:\Program Files (x86)\Android\android-sdk\platform-tools" and Google's list of ADB commands should help you. Look for tutorials on using ADB if needed.

6. If you still can't get everything working and need more specific recommendations follow the detailed tutorial which shows you how to get MTP working with USB debugging enabled.