yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] bhu1:
Guys I need some help, it is a bit off topic I guess -

I have a full HD LG led TV which does not have WiFi support so no miracast, I wanna play some shows and movies which are in 1080p 5.1 level profile format but they don't play cause of 5.1 level restriction like with the ps3.

Is there any way I can play those videos on my nexus 7 and mirror them onto the TV using USB connection?

If that's not possible then (this gets more off topic from here) anybody knows if I can play the videos on the nexus 7 and miracast them onto the TV through mirroring on the ps3? Like I connect tablet and ps3 through miracast and ps3 is connected to the TV and I play video on tablet and it plays on TV through miracast on ps3.
[Nexus 7 Original Development] michael_ch:
CM11 with F2FS on /data

I just want to give feedback that I have successfully installed CM11 with F2FS on my Nexus 7 (2012). So far I'm using F2FS for /data only, but the speed improvement is already enormeous. It really feels like I'm using a new device again!

As it took me some time to find out about it, I am sharing the info for others to try out.

Most important is that the current CM11 kernel for the Nexus 7 does not (or not entirely) support F2FS yet. So you will need to install a separate kernel to mount these partitions.

Requirements:

Recovery with F2FS support: TWRP 2.7.1.1 from http://www.teamw.in/project/twrp2/103

CyanogenMod 11 M8 release: cm-11-20140708-SNAPSHOT-M8-grouper.zip from http://download.cyanogenmod.org/?device=grouper (or any later release)

Kernel with F2FS support: M-Kernel from http://xdaforums.com/showthread.php?t=2168787

Flash the recovery, then format /data. Use the advanced settings to specify F2FS as filesystem, otherwise Ext4 will be used again.

(If you don't want to loose your data, you can copy it away using an external USB drive and tar (to preserve permissions and ownerships) or using rsync with tcp forwarding (rsync uses port 873) through adb. If anyone has an easier idea for how to achieve this, let me know. If anyone needs more details about it, I can explain it in a separate post...)

Note that the boot screen stalls for a long time after every reboot. I don't know exactly why this happens, but it seems to help if you tap on the screen. Did not investigate this further yet...

Side note: I also tried to use F2FS for /system but then failed to install CM11 + gapps because the partition went full. It seems that F2FS requires more disk space, which seems to be too much for /system currently...

---------- Post added at 08:33 PM ---------- Previous post was at 08:32 PM ----------

Btw. can someone finally update the thread title? M5 is pretty outdated meanwhile...
[Nexus 7 Original Development] SkOrPn:
Looks like you could be a great candidate for trying out Chromecast. It will bring Wifi to your TV and allow you to cast just about anything from your N7 to your TV. We use a Roku 3, but I rarely try casting something to the TV. We are strictly Netflix, Hulu and Plex users here which the Roku 3 excels at.
[Nexus 7 Original Development] jrk190:
I have a Chromecast, love it. Best investment you could make, just hoping we get screen mirroring with Android L.
[Nexus 7 Original Development] aney1:
I tried it too a while ago, but i couldn't restore my data partition.

How did you copy the data back? With aroma file manager?
[Nexus 7 Original Development] michael_ch:
I wouldn't recommend to copy the data when the system is running. Better do that in the recovery, where /data is not accessed.

So I think it would be the easiest way to boot into the recovery, mount a USB drive and write the data to the stick using rsync.

If you use rsync (mount /system to find the binary in /system/xbin/rsync) then make sure that the USB drive is formatted with ext4, otherwise format it.

I did not use a USB drive, instead I started rsync as daemon on the phone. This worked very good, but the setup is much more complicated...
[Nexus 7 Original Development] :
M8 won't let me access my settings, it crashes every time I try to open them. Does that happen to anyone else?
[Nexus 7 Original Development] aromig:
Yep, did a fully clean install and now it's working like a charm. Sometimes big changes from version to version make a dirty flash problematic.

Sent from my GS3 running CM11, via FapDaCock
[Nexus 7 Original Development] hochoch:
Check the cyanogenmod blog. They said it would happen, just wipe data settings in app manager.
[Nexus 7 Original Development] Domino5:
Anyone noticed that navbar is too big? (Since 2/7 nightly I guess) It should be 48dpi but looks like 55 or more
[Nexus 7 Original Development] corumuk:
Ok so i tried using f2fs and when it reboots it repeatedly asks for a password to decrypt storage. Have had to reformat the data partition to ext4 to get it to boot. Using twrp 2711, latest snapshot and mkernal a69.
[Nexus 7 Original Development] ironmaskusa:
Yea, I didn't search to read for a solution to the same problem. I just restarted from scratch on m8. Everything works good so far.
[Nexus 7 Original Development] michael_ch:
This problem happens when one of the partitions could not be mounted. Are you sure you flashed the M-Kernel? This is necessary for F2FS support.

See the two following posts which refer to a very similar problem:

- http://xdaforums.com/showthread.php?p=50711676

- http://xdaforums.com/showthread.php?p=51074778
[Nexus 7 Original Development] corumuk:
yeah i flashed a69 then rebooted and checked in the device info page and it was showing as mkernel.

i can see the decrypt storage problem has been around for a while, may give it another go later.

thanks for the info.

update.

ok, so tried again.

using twrp 2711 i flashed mkernel a69, the latest 'alpha' version, over the current cyanogenmod snapshot. then selected wipe, data, change file system, f2fs, which was successful. then rebooted. then had password screen again to decrypt data partition.

will read up a bit more later maybe, or just wait till it works without hours of faffing about.
[Nexus 7 Original Development] :
You have to FORMAT the data partition! A wipe is not enough. You can check by rebooting to recovery -> wipe -> change or repair filesystem -> which fs is shown?
[Nexus 7 Original Development] SkOrPn:
All partitions are to be formatted first, no wiping involved. After the partitions are formatted, then you flash a F2FS ROM that was "pre-converted" to support F2FS (should be done via OTG). I use "Convert to F2FS" from the play store and have flashed 20 roms and never once had a problem. From how you typed it, it seems you are wiping or formatting last, or trying to convert partitions after a ROM flash? Of course you will get that decrypt message after destroying the work your ROM and TWRP did. lol Converting to (formatting) F2FS completely erases your Data partition and everything that was on it.

After formatting (not wiping) to F2FS, you need to have the files in question, at least the F2FS ROM on a flash drive or on your computer, because Formatting Data removes EVERYTHING. I use OTG of course but maybe you need to push from the PC, I do not know how you plan on doing it. But it seems you are simply wiping, lol and that will obviously not work.
[Nexus 7 Original Development] :
I flashed the latest nightly. That somehow fixed it too.

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

Ah, I just noticed that some guy posted a solution to this on the page before.
[Nexus 7 Original Development] corumuk:
Mmm i thought the method posted earlier on this thread is to just convert the data partition to f2fs, the other partitions remain unchanged whereas the system you are using is for all f2fs maybe (hence formatting all partitions). I assumed (probably incorrectly) that when i flashed mkernel over the latest snapshot that it would reside on the system partition and that the system partition would be unaffected when i converted (which includes formatting) the data partition to f2fs using twrp. Formatting data is after all not much different than a factory reset i guess so my thinking was that the rom (inc mkernel) remain untouched, but from what you are saying there is something critical that the rom/kernel needs to boot that sits on the data partition.
[Nexus 7 Original Development] SkOrPn:
Yes, if you convert only your DATA partition, you are formatting it to F2FS. There is no "convert" and keep files intact though. You can do formats on all hard drives, SSD's and NAND chips, they all support different file systems on the same media device. However, when you convert to F2FS you are in essence doing a FULL format of that partition or nand chip. Doing this erases everything that lies inside the data partition which includes your SDCARD and 100% of all user stored data. Until you accomplish this task at least once, you can not use F2FS without losing everything. However, once it is done, it is done forever, or until you have a reason to go back to ext4. This is why I bought a OTG cable, because it makes life so much easier when playing around with android. TWRP can natively see files on a fat32 formatted flash drive, so I keep all my ROM and kernels on the PC ready to copy over to a flash drive in a pinch.
[Nexus 7 Original Development] corumuk:
Ok cool. I copied everything from the data partition to my pc before i converted. Still not sure why it didn't work though. It converted successfully and that included formatting the data partition to f2fs but leaving the system partition intact. Maybe i'll have better luck downloading an all f2fs rom and trying that at some point.
[Nexus 7 Original Development] SkOrPn:
To be absolutely honest, I think converting only the data partition is a complete waste of someones time. Either go full f2fs or nothing at all. Either way the user has to lose everything on the device at least once. If this was a desktop computer, I would say lets wait a bit longer for F2FS to mature before using it, but on these Android devices it just does not matter and F2FS is obviously better suited for a mobile device anyway. The process is not an easy one so do it all at one time and forever be done with it :good:
[Nexus 7 Original Development] corumuk:
Agreed. I'm now fully f2fs and life is good. Didn't take long, nails are a bit shorter though lol.:good:
[Nexus 7 Original Development] SkOrPn:
LOL, and wow that was fast. Took me much longer back when we were first trying to figure all this out in March. Glad you got it done though. Now just remember, every ROM you flash from here on out will not care whether it is f2fs or not (they natively expect ext4), but you need to make sure they are either converted to support f2fs, or do it yourself.

I made life easier by simply purchasing Legolas's conversion app. Once every other week I convert a new rom and flash it regardless if I need to or not, lol...
[Nexus 7 Original Development] wurstel:
hey guys, i encountered something weird with the new cm11 m8 ony my nexus 7: the lockscreen wallpaper always stays the same, no matter what i do. i changed the wallpaper in settings, but the lockscreen wallpaper is always the cyanogenmod one (the blue one with the circle). am i missing something? can i change the lockscreen wallpaper independently somewere? i thought they removed that feature, but somehow it seems present in the lates milestone????
[Nexus 7 Original Development] michael_ch:
As I mentioned before, I had the problem that CM11 + gapps (gapps-kk-20140606-signed.zip) did not fit onto a F2FS formatted /system partition. That's why I left it running as ext4.

The performance improvement with only /data on F2FS is still enormeous. I'm very happy with my Nexus 7 right now even if the speed gain may be even bigger when also /cache and /system will run on F2FS...
[Nexus 7 Original Development] todivefor:
Flashed TWRP 2.7.1.1, but do not see the f2fs setting in advanced settings.
[Nexus 7 Original Development] michael_ch:
I just checked again to be sure:

Wipe => Advanced Wipe => [Select Partion] => Repair or Change File System => Change File System

Hope this helps.
[Nexus 7 Original Development] underwaterjr:
I convert cm to full f2fs and use banks' standard gapps. No problems with it all fitting.
[Nexus 7 Original Development] todivefor:
That worked fine. I was looking at format and not wipe. I kept getting "partition invalid." I guess you have to do one partition at a time. Thank you. Just getting my ducks in a row.

FYI. I used TWRP manager to install TWRP. I was at 2.6.3.1. It installed 2.2 something. Had to install 2.7.1.1 manually. Piece of crap!
[Nexus 7 Original Development] corumuk:
The PA gapps here (micro version) are the ones that worked for me http://highonandroid.com/android-apps/download-android-4-4-4-gapps/

After installing a converted snapshot and the above gapps the nexus has 62.9mb free in the system partition, as reported by titanium backup.

TBH i'm not noticing a significant speed increase, although I never felt it was particularly slow before.
[Nexus 7 Original Development] r-l:
Anyone having issues with the themes on the latest nightly ?

The change in the settings don't stick {rest of the ROM does changes) it changesn back tot holo theme
[Nexus 7 Original Development] todivefor:
I converted everything also. Used banks' standard gapps and had no problem and have plenty of system space available also. The only problem (or non-problem) I had was converting the three partitions to f2fs. Each time TWRP reported success, but when I went back each partition was reported to be EXT4. I repeated several times with same results. I think I backed out to TWRP home and then they were reported as f2fs.

I also do not see much change in speed.

One question. If I do a nandroid restore of an EXT4 backup, will that revert to EXT4, keep f2fs, not work, or brick?
[Nexus 7 Original Development] Keitaro:
A nandroid backup (whether it's from Twrp, Cwm etc) is an exact copy of that partition and so it backs up the format of the partition is as well. So, restoring that backup will revert it to EXT4.

Also, after you have formatted a partition to f2fs you should reboot into recovery again. I'm not sure of the technical reasons why it's just that I see it mentioned in almost every f2fs guide that I've seen.

I'm on CM nightly + minimal banks gapps + mkernel with all 3 partitions f2fs (confirmed via the diskinfo app) :)
[Nexus 7 Original Development] todivefor:
Since I had had trouble formatting f2fs, I installed diskinfo to check. Data and cache are f2fs and system is ext4. SOB! I formatted system f2fs and rebooted to recovery, it said system was f2fs. I reinstalled without wiping data. It got to cyanogenmod boot animation, but never went further. I tried a clean install thinking I could restore data. Same result. Never got past cyanogenmod boot animation. Any ideas?
[Nexus 7 Original Development] Buggster:
Did you try an other kernel yet. The M kernel seems to help getting past the boot stage.
[Nexus 7 Original Development] Keitaro:
I had the exact same experience a few days ago and even flashing m-kernel after rom + gapps didn't solve it either. It stayed on the CM boot logo animation as you saw as well.

At the time, I was in the middle of making a post here about it but then I heard about the Convert To F2FS app..

https://play.google.com/store/apps/details?id=com.runnerway.converttof2fs&hl=en_GB

I ran a CM nightly through it and came out with a ready to flash zip. I then went into recovery and manually formatted the system partition to f2fs again and rebooted into recovery again. I then flashed the zip from the app above, then minimal gapps and then started the rom. Checking in Diskinfo confirmed that the system partition had this time remained at f2fs.

I then decided to compare the updater-script file from both the original nightly zip and also the modified one as output from the Convert To F2FS app. This script is found in the following folder inside each zip archive...

\META-INF\com\google\android

Lines 10 and 11 of the script format and mount the system partition as EXT4 and so this is why you, and I, saw that it had changed from F2FS back to EXT4 after the first attempt.

format("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");

The updater-script in the modified zip output by the app has these commands to format the system partition and mount it as F2FS instead...

run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
run_program("/sbin/busybox", "mount", "/system");

Now whenever I decide to update to another nightly, I manually change the updater-script to changes line 10 and 11 to those above and everything (rom + gapps + m-kernel) flashes and boots without issue. I don't use the Convert To F2FS app anymore.
[Nexus 7 Original Development] Buggster:
M kernel Solved it for me after converting to f2fs didn't work. I had to eventually revert to ext4 stock, then to ext4 cm11

and the m kernel to get it working. Just found out that converting to f2fs can be an serious drag

if you don't get it right the first time

ending up with an no OS situation and forgetting you need to flash over fastboot..

I just wonder why nobody isn't posting an converted f2fs cm11 version of this rom?
[Nexus 7 Original Development] todivefor:
Keitaro, thank you this worked for me. It probably cost me an unnecessary $1.65 for Convert F2FS app, but that was my stupidity.

I re-formatted system as F2FS and rebooted to recovery as you suggested. I modified the updater script as you suggested, but the install failed. I was trying to save myself from having to re-setup the ROM so did a dirty install. Thought I had screwed up in the updater script, so bought the app. Ran it, and then tried dirty installing it. It also failed. Neither failure provided any reason. I then did factory reset and tried again. It installed no problem. I restored data from my nandroid backup and I am back in business. Diskinfo shows all three partitions as F2FS.

If you use the conversion app, is it still necessary to run with m-kernel (I am)? I am using Banks' standard gapps. Have about 49.6MB of system left as reported by diskinfo. When formatted as EXT4, I had a lot more space available.

It's actually pretty simple, once you have done it and have had the help provided by Keitaro.

edit: in rethinking, I believe the answer to m-kernel is yes, needed.
[Nexus 7 Original Development] Keitaro:
I'm glad I could help :)

The Convert To F2FS app replaces what ever kernel is in the input rom with this F2FS one...

http://xdaforums.com/showthread.php?t=2664392

...which is from February this year. So, you don't need to install m-kernel but I do since Feb is somewhat "old" for a kernel, especially when m-kernel gets updated more frequently. M-kernel also has a few more options to play around with in Trickster.

As for free space in the system partition, with Banks -> 7-2_GApps_Minimal_4.4.4_signed.zip I have 142 MB free in the system partition according to Diskinfo.
[Nexus 7 Original Development] qx876:
Hey,

I am having minor bluetooth troubles since months and lots of nightlies and m versions.

Trying to activate bluetooth from the quicksettings to connect to my speaker is a hit and miss, sometimes it works sometimes not.
[Nexus 7 Original Development] Yeti12:
There's an app which does it for you, its not free, but not expensive LINK
[Nexus 7 Original Development] cdrom1028:
I did the same thing, PA is cool but CM is more satisfying for me.
[Nexus 7 Original Development] cub0ne:
havent noticed any problems yet. running of 2312 build. everything is working properly. maybe i play lot reason why im not noticing any bugs lol..
[Nexus 7 Original Development] krazeecracker:
Exactly I've been running cm since the cm7beta days
[Nexus 7 Original Development] sNoxious:
Does CM have Tablet UI option like PA has?

Sent from my Samsung Galaxy S III
[Nexus 7 Original Development] im.nick.hello:
Hybrid mode is all pa
[Nexus 7 Original Development] DemosZevasa:
Nope, cause its stock based with no hybrid engine.
[Nexus 7 Original Development] lynx2k50:
But can I force the tabletUI with CM?
[Nexus 7 Original Development] DemosZevasa:
4.2 has no "tablet ui"
[Nexus 7 Original Development] LuffyPSP:
Guys what does the quick pulldown do? I tried testing anything part of my screen and no change has happened at all.
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
So now that I have my N7 I can be more specific about my problem. I can add new toggle tiles but when I try to rearrange them they don't rearrange in the way that I want and I can't get rid odd the ones that are there by default.

Edit: see attached picture

I actually am able to get rid of tiles, but the Bluetooth one likes to stay where it is even when the layout screen has no tiles present and rearranging is a mess.

Sent from my Nexus 7
[Nexus 7 Original Development] littleguevara:
Same problem here, but for the battery life I'll deal with it loll

Sent from my Nexus 7
[Nexus 7 Original Development] JeremyNT:
The option seems bugged on my nexus 7 at the moment. It is supposed to allow you to get the settings panel when you pull down the menu in a certain spot. On my n7 though I always get that menu on the right hand side no matter what I try changing the option to.

On my gnexus the option works. I leave the setting set to 'off' and pulling down anywhere with two fingers gets the settings panel on that device.
[Nexus 7 Original Development] gianptune:
You're a big fan of those sexy quintets?
[Nexus 7 Original Development] christianlr25:
You can try Apex Launcher, it has a tablet UI option.
[Nexus 7 Original Development] bjo12:
Finally got it working.. the battery was low on my controller.. haha.. was to excited never thought about that.. :p

Btw my controller is genuine.. thanks :thumbup:
[Nexus 7 Original Development] shaggyskunk:
Looks like Grouper, won't be on the menu today either :(
[Nexus 7 Original Development] HamsterHam:
Does Franco kernel work with this rom?
[Nexus 7 Original Development] alahkel:
I'm sorry for the noob question but: have these nightlies the usb otg mode for fat/ntfs sticks/harddisks implemented or not? I'm running last nightly (12_23) but my grouper isn't able to read natively my ntfs stick drive (need stickmount app)
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
I may be wrong, but I thought stickmount was the only way you could do this anyway and that OTG was just for keyboards, nice, etc.

Sent from my Nexus 7
[Nexus 7 Original Development] Harley25:
Delete all toggles and add your toggles in the way that you want.
[Nexus 7 Original Development] GFXi0N:
Hi! I just bought my Nexus 7, after years on cyanogenmod with my Nexus 4, and the first thing I did was to install cyanogenmod. One weird issue I experience is, whenever I open a full screen app, after the "swipe down to exit full screen" message, swiping down won't take the full screen mode off. I have to press power, and then exit the app. Am I doing something wrong? It's quite weird. Happened already on games like dead trigger 2 or the walking dead ones, for example. Also on cbr comics readers.
[Nexus 7 Original Development] Reptilez_DK:
Works fine for me, with Beach Buggy Blitz. It can be a little tricky though. Sometimes a *very* slow swipe from the top, is necessary.

These typos came from my maguro.
[Nexus 7 Original Development] GFXi0N:
Nope, I'm sure it's some kind of weird bug, since it does not work until you restart the device. Once you do, it works for some time. After a while, it stops working. I just disabled heads up notifications. It's the only thing I can think of that could mess with the swipe down function..... And it's getting on my nerves
[Nexus 7 Original Development] sancho_panzer:
Don't have this problem, could be related to your launcher. Trebuchet had huge bugs on latest releases, I'm using Apex.

http://xdaforums.com/showthread.php?t=1452663