[ROM][CM12.0] UNOFFICIAL CM12.0 for Tilapia

nygooz

Member
Oct 16, 2010
43
5
0
I figured out some extra steps that helped me to get F2FS working with this ROM. Although some people may not have had issues, here's a full list of steps I took so there's no confusion:

1. Install the latest TWRP. Only v2.8.4.1 or later allows you to convert partitions to F2FS with Tilapia. Grouper was catered to earlier, as always :rolleyes:.

2. Back up the Internal storage in addition to using something like Titanium Backup to back up App Data if you need to.

3a. If you do not wish to modify the CM 12.0 ROM archive in any way, thus simplifying the process by converting only the Data partition to F2FS, in the Advanced Wipe menu of TWRP, check the Data partition and select "Repair or Change File System". Choose F2FS and start the process, then reboot recovery. Now please skip to step 5.

3b. If you wish to go "Full F2FS", that would include the System, Data and Cache partitions and ensure performance is optimal. In the Advanced Wipe menu, check each of those partitions and select "Repair or Change File System". Choose F2FS and start the process, then reboot recovery. Now please continue at step 4.

4. If you have opted to go "Full F2FS", you will need to extract the "updater-script" file from the ROM archive.zip\META-INF\com\google and modify several lines of script in a text editor the way Aneto described earlier in the thread:



You will then need to repack and replace the modified "updater-script" file back in the same location of the original within the ROM archive.zip using WinRAR or whatever works. This step will need to be repeated each time you wish to update the ROM. Now please continue at step 5.

5. Install your ROM, followed by a kernel which supports F2FS, such as M-Kernel (version a73 or greater for Lollipop). You may need to reinstall the kernel each time you update the ROM. Now reboot system and allow the OS to load fully, then reboot recovery.

6. Install Google Apps for Lollipop, reboot system again and allow apps to be optimized and the OS to finish loading.

7. You're now good to use your tablet, but if you wish to free up space in the System partition, you can use something like Titanium Backup to move apps from System to Data. Moving or uninstalling the Google apps "Hangouts" and "Google+" frees up quite a lot of space. You may also want to install SuperSU in recovery prior to tinkering with apps that request root access.
Can you help me with my updater script? I found only three of four mentioned lines. I updated only those which I found and during system flash partiotion was reconverted to EXT4 from F2FS.

Here's what I found in todays version of nigtly. Can somebody edit it in proper way and send back to me?
View attachment updater-script.txt
 

amd1361

Member
Feb 14, 2013
27
4
0
f2fs

Hi
Can I use the app "convert to f2fs" to convert the rom to an f2fs ROM?
I have already used that program and installed CyanogenMod 11 (I converted cache , system and data to f2fs using multirom twrp recovery) and it works really well.
Thanks
 

daniello8

Senior Member
Sep 13, 2008
1,170
122
93
Berlin
Flashed this rom over CM11 and I am not sure I did well. Recovery complains about not having enough space to install gapps. When I look at TiBu first screen I see System-ROM: 670 MB (273 MB available) .. which seems to be a little small.
The other partition "Internal+Media" looks ok 29.5 GB (15.4 GB available).

Do you have the same layout .. or would this have required a full wipe?

Edit (a pity nobody jumped in btw): I really appreciate that this rom is proviced but I do find the current builds to be quite chewy/slow. If anyone has found a switch to remedy .. please post.
 
Last edited:

nygooz

Member
Oct 16, 2010
43
5
0
Can anyone paste updater sript with F2FS ?
What's your method to merge it to the ROM zip then? I need to make this operation on tablet.
 
Last edited:

MxFadzil92

Senior Member
Apr 29, 2011
418
56
0
28
Singapore
Flashed this rom over CM11 and I am not sure I did well. Recovery complains about not having enough space to install gapps. When I look at TiBu first screen I see System-ROM: 670 MB (273 MB available) .. which seems to be a little small.
The other partition "Internal+Media" looks ok 29.5 GB (15.4 GB available).

Do you have the same layout .. or would this have required a full wipe?

Edit (a pity nobody jumped in btw): I really appreciate that this rom is proviced but I do find the current builds to be quite chewy/slow. If anyone has found a switch to remedy .. please post.
you do have to clean install everything. meaning full wipe.
 

RevMike

Member
Dec 11, 2009
38
21
0
Performance problems and workaround

I have been running this for a few days and it is generally functioning fine, but at times I have had tremendous lag. I would sometimes press the power button and the device would take 20s or so to wake up. Button presses would be ignored for long periods of time, etc. A reboot would help for a few hours, but then it would come back.

I recalled that I had similar problems with CM on other devices. On my Verizon Samsung Galaxy Note II, for example, I used to have an issue where I couldn't answer an incoming call because it would ring, but refuse to wake up enough to accept the call. The workaround was easy enough. I eventually discovered that if I went to the performance settings and set the Minimum CPU Frequency higher, the problems went away.

I tried this with my Nexus 7. In Settings->Performance->Processor I increased the Minimum CPU Frequency from 102MHz to 340MHz. (I turned on the "Set on boot" setting as well.) It is working almost flawlessly now and the lag is gone.

I suspect that the core issue is that the CPU governor is not increasing the frequency quickly enough. Adjusting that may work as well. I did not try the 204MHz setting, but that may be enough too.

Of course YMMV. The apps I have running might put a higher background load on my device than yours, and so yours might be fine at the default.

I'm currently running the 2015-01-26 nightly and I dirty flashed from CM11 without issue. I am using my Nexus 7 with T-Mobile in the United States.