[ROM] [6.0.1] [MARSHMALLOW] CyanogenMod 13 for Nexus 9 LTE

[sinik420]

Getting all black screen on Netflix playing after flashing latest update. Updated vendor and bootloader as well to no avail, any ideas? Page 1 says to use the latest image but links to mmb29k but latest is 29s, I stayed on 29k per the advice above.

 

[elherr]

Getting all black screen on Netflix playing after flashing latest update. Updated vendor and bootloader as well to no avail, any ideas? Page 1 says to use the latest image but links to mmb29k but latest is 29s, I stayed on 29k per the advice above.

Turn off LiveDisplay when watching Netflix. That was the fix for me.

 

[sinik420]

Turn off LiveDisplay when watching Netflix. That was the fix for me.

I love you

 

[maelfilk]

Anyone using supersu? Does latest supersu 2.66 or 2.67 work with cm?

 

[simonsickle]

Anyone using supersu? Does latest supersu 2.66 or 2.67 work with cm?

You'll have to use system-less superSU due to sepolicy

 

[fence]

Having an issue with OK Google anywhere option being greyed out.
Using the 20160206 mini opengapps and cm build. Does anyone else have this issue? There is a user in the official opengapps xda thread with the same problem but no solutions.
Cheers.

 

[Leader2light]

From locksceen smart cover will not bring up camera when corner is folded back.

Works fine once tablet is unlocked.

 

[simonsickle]

Having an issue with OK Google anywhere option being greyed out.

Using the 20160206 mini opengapps and cm build. Does anyone else have this issue? There is a user in the official opengapps xda thread with the same problem but no solutions.

Cheers.

I'm fairly certain only the stock gapps package will support ok Google. No promises though. Check out the site link, it describes everything.

From locksceen smart cover will not bring up camera when corner is folded back.

Works fine once tablet is unlocked.

I am 90% sure this is a cm security feature. Cyanogen mod does have specific support for smart cases (dot view on m8 for example). Extra programming may be required.


Sent from my iPhone using Tapatalk

 

[blastagator]

Is anyone running f2fs /data with the encryption on? Trying to troubleshoot a different device.

Thanks,

 

[fence]

I'm fairly certain only the stock gapps package will support ok Google. No promises though. Check out the site link, it describes everything.





I am 90% sure this is a cm security feature. Cyanogen mod does have specific support for smart cases (dot view on m8 for example). Extra programming may be required.


Sent from my iPhone using Tapatalk

Flashed stock gapps, same story, OK google works but option to use anywhere is still greyed out.

 

[buttie]

Flashed stock gapps, same story, OK google works but option to use anywhere is still greyed out.

I think it's a device specific bug. I've got this problem on CM with stock gapps, now I'm on AOSP based rom (Pure Nexus to be exact) and "anywhere" options is still greyed out. I didn't find a solution so far.

 

[nigelhealy]

I have the current stock ROM (MMB29R) and done a clean flash of today's CM13, and I got the vendor incompatibility message.

Am I meant to flash an earlier vendor or reflash the current vendor.img ?

 

[simonsickle]

I have the current stock ROM (MMB29R) and done a clean flash of today's CM13, and I got the vendor incompatibility message.

Am I meant to flash an earlier vendor or reflash the current vendor.img ?

I dont maintain the LTE version, only the wifi version. Ill try to look at the issue though

 

[nigelhealy]

I dont maintain the LTE version, only the wifi version. Ill try to look at the issue though

I have a problem arisen, trying to figure it now if user error. I flashed a build.prop ignoring message zip in recovery, rebooted and then lost Internet over cellular (no LTE, etc). Coincidence?

I'm now doing a full wipe fresh install, but before I start I fastboot flash vendor the vendor.img from volantisg-mmb29k, to avoid any error messages.

One other thing not specific to the ROM but if I flash Xposed before ElementalX then ElementalX works better than if I do the opposite. Weird.

[Update]

Yep that fixed it. There is another thread which has a fixer.zip to make the "incompatible" message disappear. Do not use it. Best to follow this thread's OP and either ignore the message, or before you start flash the volantisg-mmb29k vendor.img to be the same as the one in current CM13.

 

[lcrponte]

I have a problem arisen, trying to figure it now if user error. I flashed a build.prop ignoring message zip in recovery, rebooted and then lost Internet over cellular (no LTE, etc). Coincidence?

I'm now doing a full wipe fresh install, but before I start I fastboot flash vendor the vendor.img from volantisg-mmb29k, to avoid any error messages.

One other thing not specific to the ROM but if I flash Xposed before ElementalX then ElementalX works better than if I do the opposite. Weird.

[Update]

Yep that fixed it. There is another thread which has a fixer.zip to make the "incompatible" message disappear. Do not use it. Best to follow this thread's OP and either ignore the message, or before you start flash the volantisg-mmb29k vendor.img to be the same as the one in current CM13.

No LTE is a known bug that pops up every time that you reboot the device. You have to change to something else that is not LTE and then change to LTE again and it's bypassed till the next reboot.

 

[oo0]

vendor img

Mismatched fingerprints; system reported google/volantisg/flounder_lte:6.0.1/MMB29K/2419427:user/release-keys but vendor reported google/volantisg/flounder_lte:6.0.1/MMB29R/2482564:user/release-keys

 

[sheffzor]

Mismatched fingerprints; system reported google/volantisg/flounder_lte:6.0.1/MMB29K/2419427:user/release-keys but vendor reported google/volantisg/flounder_lte:6.0.1/MMB29R/2482564:user/release-keys

Should be fixed on next nigthly.

 

[kyleastley]

So I went on to install this on my Nexus 9 and what a difference no lag better battery, why can't Google just get things right.

 

[Need4Sneed]

Just a quick FYI for everyone:

Although the latest nightly (cm-13.0-20160309-NIGHTLY-flounder_lte) is identified as a MMB29V build, the matching factory vendor image does not work 100% with the system build yet, so stick with the MMB29R vendor image for the moment.

After I flashed the most recent nightly (cm-13.0-20160309-NIGHTLY-flounder_lte), I checked the build number and noticed that it was a MMB29V system build, so I went ahead and flashed the MMB29V vendor image, but I got the warning saying that there was something wrong with the hardware of the device, so I reflashed the factory MMB29R vendor image and everything is back to normal.

If anyone here is aware of when we're suppose to flash the updated vendor image to match a specific nightly dirty flash, please let us know. Up to now it's been kind of a trial-and-error thing.

 

[cam30era]

..