yashsingh1/xdaforums huggingface dataset:
[Nexus 9 General] Annita:
I just got a Nexus 9 WiFi and first thing I did is a full factory reset to volantis-mmb29k-factory-c25ba34c and had the "usual" errors about f2fs ("File system type f2fs not supported." and "Formatting is not supported for filesystem with type 'f2fs'.") but got over them and succesfully install TWRP and CM13 (cm-13.0-20151229-NIGHTLY-flounder).

I tried to upgrade today to cm-13.0-20160101-NIGHTLY-flounder and despite the fact that when loading into recovery TWRP is quite slow to load, I noticed that flashing a new CM takes a veeeeeeeeeeeeeery long time (talking about >10 minutes waiting) and as it felt too much time, I reset the device and obviusly, the CM13 version was not upgraded. Did not even get to the "Patching system image unconditionally" message...

Now I just did a new clean Factory Reset and installed today's cm-13.0-20160101-NIGHTLY-flounder and worked fine. I'm used to flash ROMs on my Nexus 4 & Nexus 5 and doesn't seem right this amount of time on the Nexus 9, so I was wondering if it's normal? How long does it take you to load a new nightly using TWRP?

Thanks!
[Nexus 9 General] whowatchlist:
[MENTION=373247]Annita[/MENTION] the boot time is unusual long, especially when it encrypts data again. My s4 is much faster even though it's a few years old. [MENTION=7179167]Raphafluffa[/MENTION] instead of adb push try using a file explorer to push files. If not try using fastboot to go to stock. As for elementalx you need to unencrypt after installing it. The your device is corrupt message happens before the first encryption. You need to reboot recovery if you don't find a file after pushing it.
[Nexus 9 General] Raphafluffa:
Thank you very much for your help!

The problem is that adb push does work (I double checked that the CM file is on the SD with the es explorer and additionaly downloaded it directly with the tablet) but as soon as I try to access any file with the recovery do I only find empty system folders (0 mb on the sd card). However, the recovery does find all my files on my usb stick connected via otb cable.

I went back to stock (6.0.1) via fastboot and don't get the error (device is corrupt) anymore but my pc still only sees the device but it's able to copy anything to it.

At this point I'm not certain how to proceed but maybe something like this :

Stay on 6.0.1, flash recovery, wipe device, set the data format to f2fs, push cm on it, reboot recover, flash cm, flash the anti encryption i found somewhere here, flash pico 64 gapps, reboot, don't get stucked at logo and vi error schissel, profit and be happy

Pls correct me in case ?

The stock system is cancer, really need cm ?

Thx a lot for your help!
[Nexus 9 General] whowatchlist:
What do you mean set the file system to f2fs? I didn't do anything like that
[Nexus 9 General] Raphafluffa:
Not exactly sure, but i think it's the format for files on the "hard drive". I saw somewhere in the comments that the recover wiping automatically changes the file format and it should be changed back after to f2fs.
[Nexus 9 General] madbat99:
No, data should not be f2fs. Leave that alone. Maybe format cache to f2fs if you want, but not data.

Make sure you have the most recent twrp, 2.8.7.1 , then it will see files. Do not format data to f2fs. All the issues you have are usually related to old builds of twrp, encryption, or data format.
[Nexus 9 General] schickel:
I have a problem with the CM13 eMail app.

It shows one mail twice (see screenshot). Did someone else have this issue also?

In the Gmail app it is alright and the only reason I don't want to use the Gmail app is, that it doesn't support push for private mail addresses. The CM13 mail app support it and this is an important feature for me.

View attachment 3598926

Gesendet von meinem Nexus 9 mit Tapatalk
[Nexus 9 General] dmantilal:
I thought stock Marshmallow used F2FS on /data by default.

Anyway, I use F2FS /data partition with Marshmallow, encrypted or decrypted, with no problems. Why do you discourage F2FS /data?

IIRC, F2FS /cache is not supported, so I would be careful advocating it (bootloop?). My /cache only has TWRP logs, so it seems that /cache is not used like it once was. The dalvik-cache is on /data, so F2FS makes even more sense on /data.
[Nexus 9 General] schickel:
Vendor Fix for CM13

Hi,

after booting CM13 I got: "there's an internal problem with your device. contact your manufacturer for details"

A quick search here on XDA say, that there is a vendor fix missing (it modify the vendor build.prop to match the system build.prop). The vendor.img is in the factory image and must be flashed in fastboot. For 5.1.1 exists a flashable vendor fix. Till now I didn't find a flashable for 6.0.1 and CM13.

Enybody have a hint for this?
[Nexus 9 General] Kubens1pl:
Is is possible to use Trebuchet on Nexus 9 ? How can i set it as my default launcher?
[Nexus 9 General] wieman01:
I am updating from CM12.1, but did a full wipe before I installed the latest CM13 image. Also installed latest Opengapps Nano package, however, I cannot get past the Setup Wizard because Google Play keeps crashing and generating error messages ("Unfortunately, Google Play Services has stopped...").

Any idea what I need to do apart from a full wipe? Read that I may need to install the Google factory image first before I update to CM13. Clearly that isn't an option and I was hoping I could upgrade from CM12.1 without resetting the device anyway.

Any insight would be appreciated.

P.S.: I did flash Gapps immediately after I flashed the CM13 recovery. Also TWRP is the latest version.
[Nexus 9 General] tibere86:
You are going to need to flash via fastboot the new Android 6.0.1 vendor image for the Nexus 9. Or, just flash the latest Google Factory Image using the included script, fastboot flash TWRP, reboot into TWRP, wipe all and flash CM13 + Gapps.
[Nexus 9 General] schickel:
I'm on cm-13.0-20160105-NIGHTLY-flounder, clean fresh install and the message comes again...

From where you've got the vendor fix?

Gesendet von meinem Nexus 9 mit Tapatalk
[Nexus 9 General] alose:
https://developers.google.com/android/nexus/images?hl=en
[Nexus 9 General] gladiac:
Hey [MENTION=1673056]schickel[/MENTION],

just make sure you have a current vendor partition (like the one from the latest 6.0.1 image) flashed from the google factory images. However, the message will still appear. After flashing the vendor-partition you can use my vendor build prop patch to get rid of the error message. It works for any device on any current android version. There are no checks in the flashable zip.

I hope I could help,

glad
[Nexus 9 General] Annita:
I also got the message after flashing vendor.img and cm-13.0-20160105-NIGHTLY-flounder.

The issue is that you (probably) did a factory reset with the new volantis-mmb29s-factory-80118d3a and installed the latest nightly but Nightly 20160105

does not

have the latest Update Security String included, so the message is showing. The code was approved (http://review.cyanogenmod.org/#/c/126582/) and will be available in next nightly...
[Nexus 9 General] schickel:
Servus! ;)

Thank you for the fix. It works now. I've flashed the vendor.img and as you say the message still appears. After flashing yout fix the message is gone.

One question: The fix must be flashed after every new CM-version?
[Nexus 9 General] Annita:
See my previous message. You just hide the message, but the "error" still there and would be fixed after the new nightly, so no worries!!!
[Nexus 9 General] wieman01:
Thank you, understood. Just for clarification: What is the difference between "Android 6.01 Vendor Image" and "Google Factory Image"? And with the device being encrypted would you have a guide or something that helps me through this? I am asking because I bricked a device once because of the bloody encryption. Pardon my French...
[Nexus 9 General] maelfilk:
Has anyone successfully rooted cm13 with supersu? I know cm already has superuser but supersu is still better. I tried different versions of supersu but no luck so far.
[Nexus 9 General] Annita:
Flashed today's nightly cm-13.0-20160107-NIGHTLY-flounder and vendor.img, but still get the error message (Android System: There's an internal problem with your device. Contact your manufacturer for details.) after restarting the Nexus 9...

Any ideas???
[Nexus 9 General] dmantilal:
What apps do not work with CM's su?
[Nexus 9 General] 1031982:
I'm thinking of flashing this to my tablet, however I would like to know the fallowing when compared to stock :

1 : battery life

2 : performance in some games. Specifically, Simpsons Tapped Out and Need For Speed No Limits. Also, my 9 starts to get real warm/hot in the Simpsons.

3 : recommended build date. I really want stability and will only use one app at a time.
[Nexus 9 General] schickel:
I'm on the 08 nightly without flashing the vendor and the message is not appear. But after flashing the nightly I've flashed the fix to not encrypt the device. The vendor fix I've flashed only once after fresh install with the 05

Gesendet von meinem Nexus 9 mit Tapatalk
[Nexus 9 General] tibere86:
Delete
[Nexus 9 General] ectodroid:
Delete
[Nexus 9 General] dmantilal:
With the 01-21 nightly, Chrome tabs constantly crashed. Switching to my 01-20 nandroid backup fixed the problem.

Let me know what I can do to trouble-shoot.
[Nexus 9 General] nigelhealy:
Any video comparisons stock vs CM13?

My N9, side-by-side with N7, both current stock, the N7 is instantly responding but the N9 is laggy, e.g. press home button and wait 1-2 seconds on N9.

Is CM13 going to be any faster than stock?

I don't need CM13 otherwise.

I have the LTE version and there's little custom ROM support for N9 LTE, seems CM13 is it?
[Nexus 9 General] 1031982:
How well have games played on CM13? Has it run any cooler?

I'm on stock and it gets hot when playing The Simpsons Tapped Out.
[Nexus 9 General] nigelhealy:
What you come from? I'm on current stock
[Nexus 9 General] 1031982:
Thanks for the reply.
[Nexus 9 General] nigelhealy:
On stock, I put in a lot of effort to disable encryption, but it doesn't seem to have noticeably helped. I also worked to keep f2fs.

With cm13, is it worthwhile to keep off encryption or let it encrypt, is f2fs worthwhile or let it do ext4?

How does this sound:

Full wipe

Cm13 ROM

Switch data to f2fs

Gapps

Fed_patcher

ElementalX
[Nexus 9 General] nigelhealy:
So I've flashed CM13. Apart from a vendor.img message, which can be either ignored or flash an older vendor.img to match cm13, I have mine as /data fs2fs, no encryption, elementalx, no zRAM, fsync disabled - i.e. all the options for speed.

You are correct, the lagginess, like my hardware has a fault, has gone! Nippy fast. I have no idea what specifically CM13 is doing better/different to stock but it works.

The odd thing is I think what is wrong with stock is somehow specific to the N9, as my N7 doesn't need anything other than stock to be nippy. Some setting/tweak ???

Anyhow, I'm converted, so far so good seems working but it will take a while, hours/days to see if any bugs affecting me.
[Nexus 9 General] nigelhealy:
Would be good for all to know, because if Google would just do the same then all N9 owners would be better.

Hitting the CM13 bugs. Sigh. Screen auto rotate gone, horrible loud onscreen key clicks I can't seem to find setting to disable (I find but doesn't work). Stock is better apart from speed.
[Nexus 9 General] Raphafluffa:
Thanks guys!

Thank you all very much for your help! Everything is running smoothly and fast now :)

Even though I might repeating other posts this is how I did it finally:

Update the stock rom to the latest – Factory reset it – Open bootloader – flash recovery – flash CM – don’t reboot directly but flash gapps + fed patcher – flash elementalx – flash the error fix

Last but not least did my home screen not rotate even though it was enabled in the normal setting and working in my apps and lock screen. Thx to Djonni DK I figured that you have to enable it extra in the home screen settings: touch screen for 2 sec – click those 3 tiny dots above the widget icon to get into the home screen settings – allow rotation

Thx guys, I love this :)
[Nexus 9 General] Markyiptw:
The loud clicks is because the system sound volume is linked to ringtone volume, and we cannot set ringtone volume on cm (the volume panel only control notification volume).

我從使用 Tapatalk 的 Nexus 9 發送
[Nexus 9 General] Marky__Mark:
Is anyone having problems clearing history in the browser?
[Nexus 9 General] nigelhealy:
Thanks for the tip of the rotation, I could not find it and used Nova Launcher.

Are you aware of cyandelta?

This has two useful features in this context we both share of needing to do some flashing after the ROM before booting. Install cyandelta, then add your current installed ROM to its settings. Then add zips to install post ROM install. I add fed_patcher to keep encryption disabled, SuperSU as I had one app doesn't work with CM root, xposed, elementx. Then let cyandelta do the CM update check for you, it downloads just the delta, so saving bandwidth and then merges in the ROM delta then it boots into recovery, flash the new ROM then the other zips in your sequence, then boots. Works for me.
[Nexus 9 General] Raphafluffa:
I’m happy I could help!

I’m definitely getting Cyandelta, didn’t know about it but it looks perfect for my needs, thank you kind Sir! Furthermore, checking out Xposed and what I can use it for.

Setting up this stuff and playing around with CM is almost more fun to me than using the tab itself :D

Cheers

Edit:

Thx a lot! Cyandelta works perfect for me! Easy and fast updates, yay!

An additional information:

In the process of figuring out how to install a custom rom and some mistakes I made during that process, did my PC not recognize the SD card of my Nexus 9, I could see the Tablet in the Windows file explorer but not the content of the card nor could I copy anything on it.

The solution (temporary): enable development settings – scroll down to “Select USB Configuration” – select PTP (Picture Transfer Protocol) just for the moment being – now your PC should be able to recognize the cam folders – select the USB config again and switch back to MTP (Media Transfer Protocol) --- However this only works as long as the tab is connected to the PC and I have to repeat the process as soon as I unplug/plug it back again.

A permanent solution would be cool :)
[Nexus 9 General] nigelhealy:
My only use of xposed is YouTube adaway
[Nexus 9 General] Annita:
Had (and still have) an issue with my Nexus 9 with TWRP 3.0.0 and CM13 (latest nightly 20160214). The issue is that I tried to lock via pattern the access to the tablet with a 4x4 pattern code, and it was working fine while the tablet was on; but as soon as I rebooted it (and had enabled the ask for pattern at start up), the pattern was only 3x3 and did not have the option to choose a 4x4 pattern (as I have on the Nexus 5X)...

Also, the data partition was inaccessible from TWRP when trying to recover the data via TWRP, so in the end had to format data and loose all the information there... It works fine with a 3x3 code, but it doesn't with a 4x4 pattern. Do you know if this is a known issue?
[Nexus 9 General] 1031982:
I put CM 13 on my nexus 9. Almost a night and day compression.

I'm about to update to the 2-16-2016 nightly.

Once there is a snapshot or milestone for the N9, there is a good chance I'll stay on that.
[Nexus 9 General] hdtvpower:
I failed.

I was on Nexus 9 LTE encrypted with start pin., then unlocked, wiped, flashed twrp, latest CM13. Ended with the two corrupted messages.

Went back to stock. All ok. Twrp again. Cm13 again. Then factory reset before boot. No message at boot but still after boot. flashed prop_fix zip. Now message before boot but none after boot.

Back to stock, all ok. Flashed twrp, Cm13 and no_encrypt boot. Ended in bootloop.

No back on stock again. All ok. Is anybody running Cm13 without at least one of the 2 corrupt messages?

Besides that formatting user data always fails because of unsupported file system f2s2.

Help please?
[Nexus 9 General] Raphafluffa:
A wise man/woman told me when I had the same troubles: read the comments! :)

Alright, so as far as I understand is the first error message connected to the enforced encryption and the second one (once booted) to the vendor image.

Here is how I did it:

1. Be on the latest stock rom 6.0.1 before flashing CM. You can either Flash the stock rom or update it from "inside" the tablet

2. Download the adb driver package from here

3. Follow this guide to unlock the fastboot, install the latest twrp custom recovery and last but not least the CM.

4. After the CM has been installed out of twrp, don't reboot! Instead flash fed-patcher to avoid the ForceEncrypt.

5. No need to reboot, flash the vendor build prop.

6. Flash the latest CyanogenMod 13 (Android 6.0) open GApps - ARM 64 - Andriod 6.0 - eg. pico (most basic version)

7. Flash Kernel ElementalX

8. Finnaly reboot

Notes:

I didn't change the filesystem after the full wipe, not sure what that is good for as well. I used "adb push filename.zip /sdcard/" to get the zip files onto the sd card, however this only works in faastboot (?). I use CyanDelta for easy updating the lastest CM and Titanium Backup for backing up my apps. The Home screen can rotate as well, its not a bug.

Hope this helped, please correct me or add information.
[Nexus 9 General] madbat99:
You have to select USB for storage every time in marshmallow. When you plug in to pc, Just pull down notification shade. Tap USB options, tap USB for storage.
[Nexus 9 General] hdtvpower:
Thanks, worked almost,

after the elementalx update i rebootet. The Google apps were gone.! I redid the whole process and did

cm13

gapps

Fed

prop

reboot

This worked out well.

Thank You so much for your help!!

best regards

HDTVpower

---------- Post added at 03:38 PM ---------- Previous post was at 03:12 PM ----------

just did an update to the latest NIGHTY through Cyandelta. Both messages back. Back to zero :(

---------- Post added at 04:00 PM ---------- Previous post was at 03:38 PM ----------

just realizing, elementalx is a boot.img meaning the fed does not make any sense here, right?
[Nexus 9 General] hdtvpower:
difficult

There is no way around. Whenever I do a CM13 Nightly update, i will kill the boot.img and elementalx will be gone. Encryption will start again and the messages are back.

This is very cumbersome. If want to have an easy life either have to ignore the messages or pray that a dev at CM will modify the buildprop and the encrypt_enforcement. Otherwise if I need security updates i have to go through a manual flash every month.

Thanks for helping so far.

hdtvpower
[Nexus 9 General] Raphafluffa:
Haha schissel, that is nice! It totally works :D

Thanks!

---------- Post added at 09:08 PM ---------- Previous post was at 08:54 PM ----------

Hang in there buddy!

Regarding the problem you had with ElementalX and the GApps am I not sure what happened. I could flash both after each other and had no problem, I doubt that ElementalX is deleting the GApps but than again do not know what caused that error.

Regarding CyanDelta:

You can add additional zip files to be installed automatically after the CM. Open the CyanDelta - "click" the 3 dots in the top right corner - Settings - Install additional zip after rom 1 (choose open gaps) - Instal Zip rom 2 (fed patcher) - Instal zip rom 3 (vendor prop fix) - Instal rom 4 ( ElementalX) - ??? - Profit

However, after CyanDelta has installed all zips you have to choose the settings for ElementalX again. But this goes relatively fast and maybe can be done with the Elex app? Anyway, this wont even delete your apps, no error messages, no encryption, easy updates :)
[Nexus 9 General] hdtvpower:
Got it working . will install fed and buildfix after each update before boot.

only 2 problems left:

No pairing with Nexus 9 keyboard via Bluetooth . keyboard useless.

Cannot change volume of key klick.

Any ideas for this?

Great Forum!
[Nexus 9 General] 1031982:
Overall, this has been great. I was about to send in my N9 for repair because it kept getting hot playing the Simpsons tapped out. On CM13, that no longer happens at all.

The only things I would like are the fallowing :

1 - The ability to disable app icons on toast notifications.

2 - Remove the phone volume option, (it's not a phone and doesn't need it).

3 - The ability to force the keyboard open. Some pages have typing boxes, but when selecting them the keyboard doesn't open.

4 - Allow the quick settings drawer to mirror stock. (I know this isn't likely, but it's my list.)

If there are mods that do any of this, please let me know.
[Nexus 9 General] madbat99:
Try a different rom. There are many roms that are bleeding edge and feature packed. CM is more stability oriented. Solid, reliable, and more customization than stock Android.

For more features (including the ones you mention) aicp is a good choice. And it uses cm as a base.

Or stick with CM and add xposed framework and a few modules.
[Nexus 9 General] spacecase-25:
Gapps crash, completely beyond frustrated. Haven't been able to find a fix anywhere. Any ideas?

Running the latest cm nightly and latest opengapps.
[Nexus 9 General] 1031982:
Right now I need stability over features. I'll stick with CM and if I see any modules that will do what I want, I'll try them out.
[Nexus 9 General] wieman01:
This happened to me when I upgraded from CM12 to CM13 without a full wipe. I had to reinstall Android stock and then CM13 to make the crashes go away. Sounds silly, but was a reality.
[Nexus 9 General] Masteryates:
I got sick of the crappy stock performance and took the plunge into CM13 last night on the latest snapshot. :highfive:

The tablet feels around twice as fast as stock. :victory:

I've had a few crashes on Google app but apart from that, it seems stable. :angel:

Have any of you guys had an issue where, "OK Google," refuses to work when the screen is off? I've trained the voice model and things are fine with the screen on.
[Nexus 9 General] wieman01:
Well, a new install is always faster and the gap will be less conspicuous once you have been using it for a while. Personally I find the performance differences to be minimal.
[Nexus 9 General] michael64142:
Hi guys!

So I installed the stable version of CM13, and I love it so far!

Only 3 things;

- I get a message my device is corrupt before the Google logo shows up. Is there a way to get that message away? (except for flashing to Stock)

- When I try to use the Do Not Disturb function through the quick toggle menu, 'Settings' crashes.

- Changed the boot animation through 'Themes', but even though it says it already has been applied, it still shows the regular blue CM animation (already tried a few different animations).
[Nexus 9 General] whowatchlist:
Might not be the first one to say this but have you tried the Pico package? All the other ones crashed me.
[Nexus 9 General] malikadnanm:
can't flash

hi. i just got a nexus 9 and i can't install gapps for this rom or any other. Whenever I install any GAPPS package (i've tried, mini, micro, and pico) I keep getting "setup wizard has stopped working" on bootup and can't get past that. Without gapps the roms boot fine. I've flashed the newest Vendor img and the patch as well but nothing works. Am I doing something wrong? These are the steps i did -

1. flash full stock images

2. TWRP

3. flash vendor

4. CM13

5. Gapps

6. Vendor Patch

i've tried different ordering of those steps as well and nothing works, still get the wizard stopped working message. any help would be greatly appreciated thanks.
[Nexus 9 General] kacang87:
before flash rom,try wipe system, data and cache..and then flash cm13 with opengapps pico 64bit..dont flash any vendor patch except you got message there are problem after boot your tab.
[Nexus 9 General] Masteryates:
With only a few things open, you are right in saying the difference is minimal. Open a ton of things though, and stock would freeze lag and stutter. CM13 seems to handle tight situations much better. :)