yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] lcrponte:
User problem, not a ROM problem. Flash latest img and repeat the steps on the installation instructions.
[Nexus 9 Original Android Development] briand.mooreg:
I use the nano, without problems. Make sure you download the 64 bit gapps.
[Nexus 9 Original Android Development] ipilcher:
Get rid of corrupted device warning?

Has anyone figured out a way to run this ROM (or any custom ROM) without the nasty "Your device is corrupt ...." (and Santa Claus won't bring you any presents) warning on every boot?

(I feel like this must be an FAQ, but I can't find it in this thread or the CM 12.1 thread, so ...)
[Nexus 9 Original Android Development] ss12108:
I don't get that message, but I don't know what I did that is different. Elementalx kernel maybe?
[Nexus 9 Original Android Development] dictionary:
Flash the latest bootloader.img and vendor.IMG with fastboot.
[Nexus 9 Original Android Development] lcrponte:
People still can't follow simple instructions.
[Nexus 9 Original Android Development] dictionary:
It's literally the first instruction lol
[Nexus 9 Original Android Development] ipilcher:
As it happens, I'm coming from MMB29K, so I fail to see what instructions I've failed to follow.
[Nexus 9 Original Android Development] lcrponte:
You might wanna check what happened in between because as you can see, you're the only one with that problem so far. You might wanna mention [MENTION=4619263]sheffzor[/MENTION] to debug your problem though.
[Nexus 9 Original Android Development] sheffzor:
Just paste here the result of the following command via adb shell:

cat /vendor/build.prop
[Nexus 9 Original Android Development] ajeevlal:
does this rom can be flashed on non LTE version?
[Nexus 9 Original Android Development] lcrponte:
You have an official non-LTE CM version, why would you want to do that? :)

Enviado do meu Nexus 5 CAF através de Tapatalk
[Nexus 9 Original Android Development] thechicgeak:
Did that and the connectivity issues persist. On stock firmware it connects to LTE with no issues and so does my Nexus 6.

After extensive experimentation, on CM13 my Nexus 9 sometimes connects to 3G after maybe 10 minutes or so (it seems like forcing 3G makes this happen). After switching to LTE once 3G is connected it usually connects to LTE (maybe another 10 minutes).

All diagnostics that I have done point to a firmware issue.
[Nexus 9 Original Android Development] lcrponte:
Okay, I've done some tests and I can replicate that behaviour sometimes. I'll ask [MENTION=4619263]sheffzor[/MENTION] to take a look into it to see if we can come up with a solution, meanwhile if you can provide some more details, don't hesitate.

Funny thing is that my Nexus 5 sometimes is doing some weird stuff too.
[Nexus 9 Original Android Development] mattspew:
Is this thread going to cover the Wifi ROM? I can't find anything on CM13 for Wifi Nexus.
[Nexus 9 Original Android Development] lcrponte:
I wanted it to since the devices are the same (except the LTE part ofc), but the device maintainers didn't agree to have a unified thread.

One of the maintainers stated that there were people that were going to mistakenly flash flounder ROM on flounder_lte and flounder_lte ROM on flounder... It's arguable but I can understand the point.

If you want to report a bug for the wifi variant, go ahead. (I'm gonna get my throat trashed by a maintainer for sure for saying this.)
[Nexus 9 Original Android Development] JayDream:
On that note, there is something that has been bothering me with current cm 13 rom for the N9 wifi version. A weird message pops up after every reboot, another user posted the same problem on the wifi thread but I dont think it was resolved http://xdaforums.com/showpost.php?p=64781366&postcount=530 Did I do something wrong?
[Nexus 9 Original Android Development] buttie:
Did you flash the newest (MMB29S) vendor image? CM still requires version MMB29K. If so, you have three options:

1. Flash vendor.img matching the one in build.prop

2. Change value ro.build.fingerprint in build.prop to

ro.build.fingerprint=google/volantis/flounder:6.0.1/MMB29S/2489379:user/release-keys

(not recommended, you'll have to do it after every CM update).

3. Simply just don't care.

Although if you have other vendor.img flashed - from MM 6.0.0 or older - you should upgrade.
[Nexus 9 Original Android Development] lcrponte:
What kind of trouble?
[Nexus 9 Original Android Development] ankn:
I can confirm that in the past days/builds, sometimes it stopped to rotate in any app. After a reboot the correct behavior was restored.
[Nexus 9 Original Android Development] ankn:
Only if the home settings says this.
[Nexus 9 Original Android Development] JayDream:
Oh ok, Its a compatibility issue with the vendor image? Usually when its the bootloader that isn't compatible, it wont even flash the rom in recovery. It kinda threw me off because everything else seemed to be working fine. Thanks for clearing that up :D I wouldve known better but the wifi thread doesnt specify which vendor image to use for cm 13, so i figured just flash the latest.
[Nexus 9 Original Android Development] Micromind:
I need some help, since I can't install CM13 on my Nexus 9 LTE.

I'm on MMB29K, bootloader is unlocker, hboot 3.48.0.0135, recovery is TWRP 2.8.7.1 ... vendor is from MMB29K.

When I try to install cm 13 flounder_lte (one of the latest night buils) I get this error:

Can't install this package on top of incompatible data.. Please try another package or run a factory reset.

What can I try? What's is wrong with my procedure?

Thanks for help.

cat /vendor/build.prop

ro.vendor.build.date=Wed Nov 11 23:32:26 UTC 2015

ro.vendor.build.date.utc=1447284746

ro.vendor.build.fingerprint=google/volantis/flounder:6.0.1/MMB29K/2419427:user/release-keys
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] elherr:
Turn off LiveDisplay when watching Netflix. That was the fix for me.
[Nexus 9 Original Android Development] sinik420:
I love you
[Nexus 9 Original Android Development] maelfilk:
Anyone using supersu? Does latest supersu 2.66 or 2.67 work with cm?
[Nexus 9 Original Android Development] simonsickle:
You'll have to use system-less superSU due to sepolicy
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] Leader2light:
From locksceen smart cover will not bring up camera when corner is folded back.

Works fine once tablet is unlocked.
[Nexus 9 Original Android Development] simonsickle:
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.
[Nexus 9 Original Android Development] blastagator:
Is anyone running f2fs /data with the encryption on? Trying to troubleshoot a different device.

Thanks,
[Nexus 9 Original Android Development] fence:
Flashed stock gapps, same story, OK google works but option to use anywhere is still greyed out.
[Nexus 9 Original Android Development] buttie:
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.
[Nexus 9 Original Android Development] 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 ?
[Nexus 9 Original Android Development] simonsickle:
I dont maintain the LTE version, only the wifi version. Ill try to look at the issue though
[Nexus 9 Original Android Development] nigelhealy:
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.
[Nexus 9 Original Android Development] lcrponte:
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.
[Nexus 9 Original Android Development] 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
[Nexus 9 Original Android Development] sheffzor:
Should be fixed on next nigthly.
[Nexus 9 Original Android Development] 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.
[Nexus 9 Original Android Development] 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.

:)
[Nexus 9 Original Android Development] kacang87:
sorry for dumb question..how to dirty flash..did it need flash gapps?
[Nexus 9 Original Android Development] Logix:
Here is some clarification for ya good people!

"A step forward for the Android Open Source world

There's a hidden gem in Nexus 9, which was announced by a short sentence in the middle of a reply in a long mailing-list thread:

"No proprietary binaries are needed for Volantis. The proprietary vendor binaries are on a separate 'vendor' partition."

Until now, in Android devices, the proprietary device-specific files that live underneath Android itself were stored in the same /system partition as the Android files."

https://plus.google.com/+JeanBaptisteQueru/posts/akHWypRNEn3

vendor is exactly that, but its stored on its own partition which dosent get wiped as part of a a clean wipe you should only have to install them when the build gets updated and requires them like bootloader or modem ( allot of XDA nexus devs are lazy and dont include which one is current in the op which is kinda the problem here (or its outdated) )

imma make a repo for you guys like beanstown did for us on the 6p of the vendor images so u dont gotta download the whole factory image.

just a fyi to all the most recent upstream nightly builds fail with google play store /service and or setup wizard has stopped settings have stopped latest gapps can anyone confirm
[Nexus 9 Original Android Development] helderm14:
Hi.

This is my first post on XDA (although I have been reading it for some years) and so I am sorry if i'm not complying with any rule.

I use this ROM as my daily ROM, and I would like to report a bug I have found some time ago and checked now it still exists on the latest snapshot.

I travel a lot by train, and I have a nice data plan on my phone and so I share internet with my Nexus 9. However, instead of using Wireless AP, I use Bluetooth tethering (I am not sure but I think it consumes less battery from my phone). Everything works just fine until at the end I disconnect the tablet (turn off Bluetooth) and my tablet freezes and reboots.

Thank you for the amazing ROM
[Nexus 9 Original Android Development] osiedacz:
Which Vendor.img

Hey all, just wanted to say thank you first of all for working on this ROM. Second, I have a question about the vendor.img file. I just flashed this ROM today and all seems fine, except the warning following:

Android System

There's an internal problem with your device. Contact your manufacturer for details.

Is this the error I would get for not having the correct vendor.img flashed? I started off with the latest version from MMB29V. Then I took the OPs advice and tried the MMB29K, but still get the same error at system boot.

Any advice for me? Or am I chasing up the wrong tree? Thank you.
[Nexus 9 Original Android Development] osiedacz:
Alright, replying to myself here. I figured out it isn't either of the options I chose, but the one that works is the MMB29R. This one eliminates the error.

So to go along with a previous question someone else asked, how do we know when to change our vendor.img file?

---------- Post added at 02:31 PM ---------- Previous post was at 01:43 PM ----------

Just an FYI for anyone coming to this ROM on AT&T, you'll need to update the APN in order to connect to data. Select the Broadband choice and modify it to read the settings form this page:

http://www.att.com/esupport/article.html#!/wireless/KM1062162
[Nexus 9 Original Android Development] osiedacz:
Slow Cellular Data Connection

I was wondering if anyone else using this ROM has noticed it takes at least a minute or two for the cellular data connection to connect when shutting off WiFi? My APN settings are correct for AT&T.

If I am on a WiFi connection or airplane mode and I switch to cellular data, the tablet connects to the cellular line quickly, but the actual data connection takes a while.
[Nexus 9 Original Android Development] kacang87:
there are no problem here..data connect as soon as on the celular..
[Nexus 9 Original Android Development] fence:
Is there any way to combine the ringer and notification volumes? CM has the option on my N5 but it appears to be missing on the N9.

Also the NFC quicksetting toggle has been refusing to appear in the quicksettings pulldown for weeks of nightlies.
[Nexus 9 Original Android Development] maelfilk:
How can i disable lockscreen media cover art? Apart from using xposed?
[Nexus 9 Original Android Development] SkyperGER:
Hello togehter,

Today I have installed the newest Cyanogenmod flounder_lte and the newest OpenGAPPS on a totally wiped Nexus 9 LTE.

Following problems I have:

-no dialer app is visible

-no camera app is visible

-when I try to start the camera from the lockscreen the app crashes with "No conection to camera possible"

How can I solve this problems? :(

Thank you in advance!

Regards,

Skyper
[Nexus 9 Original Android Development] maelfilk:
You can't make calls with N9, so there will be no dialer app, as for camera, try flashing latest vendor in recovery. Outdated vendor can cause such problems.
[Nexus 9 Original Android Development] SkyperGER:
Thank you maelfilk.

After updating the vendor image my camera is working. But I still can't see the camera app in the app overview. I've done a update and also cleared the Dalvik / Cache. The problem still remain. Do I need to reinstall or is the camera app invisible at this rom?
[Nexus 9 Original Android Development] maelfilk:
Does camera say "installed" in play store? I'd really recommend wipe and fresh install at this point or just re-flashing gapps (not sure if this won't cause problems).
[Nexus 9 Original Android Development] SkyperGER:
No the camera isn't installed in Play Store. I will wipe the N9 again and hope that its finally over :)
[Nexus 9 Original Android Development] chayjinn:
did u flash directly to cm13 from 5.1.1?

you need to flash the latest stock factory images then flash to latest cm13.
[Nexus 9 Original Android Development] 98bishopmal:
does this run faster then stock rom for the nexus 9?
[Nexus 9 Original Android Development] anurag_verma:
I was on 29k rom after installing latest snapshot release it said your device have internal error and it is not able to connect to wifi what should I do. Rest is within
[Nexus 9 Original Android Development] razorloves:
Your problems are caused by an outdated vendor img.

See here on how to update it to the newest MOB30W vendor img.

https://wiki.cyanogenmod.org/w/Install_CM_for_flounder_lte#Updating_the_vendor.img

You should also update your radio and bootloader while you're at it.
[Nexus 9 Original Android Development] anurag_verma:
Thank you for the help. It is working fine now
[Nexus 9 Original Android Development] razorloves:
The nexus 9 lte cm13 nightly has been updated to google's september update MOB31E.

http://review.cyanogenmod.org/161305

https://github.com/CyanogenMod/andr...mmit/983846bf94992acd7c85dd3b65825e9d0c187a5b

So, starting with 9 Sep nightly you will need the MOB31E vendor img.

Instructions are here: https://wiki.cyanogenmod.org/w/Install_CM_for_flounder_lte#Updating_the_vendor.img
[G3 Q&A, Help & Troubleshooting] gabito31:
Hey ya mates...I woke up today and checked the internet for the update to our phones...i searched for firmwares in lg firmwares site and found this:

Last Added

6SW/Switzerland	V0_1	LGD855	50

Is this android 6 update? Downloaded the kdz and i will flash it...If you have any news before i update the post comment!!! Good morning!
[G3 Q&A, Help & Troubleshooting] GamePat:
No, this is V21C

Look here:

http://xdaforums.com/lg-g3/general/news-lg-g3-mm-source-code-released-t3271176/page9#82
[G3 Q&A, Help & Troubleshooting] czito:
There isn't 6.0 update yet for anyone.
[G3 Q&A, Help & Troubleshooting] dornz:
Waa ?
[G3 Q&A, Help & Troubleshooting] padarnor:
When I want to install the new update I get this message.

The problem is that I have 4.57 Gb free.

Any idea?
[XDA Assist] Harshnil:
Cynogenmod 12.1 Wiko built for Miromax Canvas Fire 2

Disclaimer

I will not be responsible for bricked devices. Please follow correct instructions. Make a nandroid backup before flashing the rom.

Bugs

1080p video playback lags with stock player(use 3rd party apps)

Instruction:-

Flash philz recovery here

Reboot Into recovery

Wipe to clean install rom

Install n flash the rom

Flash Super Su

U need To flash gapps to enjoy play services properly

Reboot and Enjoy

Credits

@fire885for wiko built

@Prince Abhinav Gupta

@@whole cynogenmod devs team
[XDA Assist] v7:
Hi,

This isn't the right place to share this.Please read the stickies of this forum before posting.

If you have a build to share,share it in Miscellaneous Development

___

v7

XDA Assist
[HTC Desire 510] Keen16:
Does combination ##3424# work on Cricket?
[HTC Desire 510] MrMike2182:
What are you trying to do??
[Galaxy S6 Accessories] Tacoo:
I know certain cases like Lifeproof and Otterbox have pack in protectors that are cut specifically for the screen so the cases don't mess them up, and I'm looking for something like that that is sold by itself. I have a dbrand skin, and they don't have any from what I can tell, which is lame.
[Galaxy S6 Accessories] Illrigger:
I did a lot of searching and couldn't find one when I got my S6. I ended up going with this case:

http://www.amazon.com/gp/product/B00QU4PRP8?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00

It's not exactly what I wanted, but it offers good protection on all sides and works with skins without any problem.
[Galaxy S6 Accessories] ntorresla:
i like more fabolous..

http://www.amazon.com/Caseology®-Pr...50474152&sr=1-3&keywords=caseology+samsung+s6
[Galaxy S6 Accessories] DuckMcQUack:
I bought a chinese glass tempered glass screen protector that does just that. However i can't imagine how you can find the same one, just try Chinese stuff shops.
[Galaxy S6 Accessories] madnav:
I use Nilkin cp+ and it is the best thing I have used next to naked screen.
[Galaxy S6 Accessories] Denli:
Try Buff screen Protectors, they do what you want, from edge to edge, and it is not glass, it is thicker than normal screen protector
[Galaxy S III Q&A, Help & Troubleshooting] mango man:
Hi experts . I have this device i9300 . Before this was a i747 . But due to some reasons I changed the board and housing with i9300. Now it runs okay. But I have two problems.

1:- The battery charges just for 10 seconds. After that it stops charge indicator. But charges in background . At reaching 95 present it restarts atomticly. The second problem is

2:- it takes up to ten minuts to search signals.

Any help
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] tahmid_shahriar:
Can't the rom of Galaxy A5(2016 version) be ported to old version of A5(2014) ? Both of them almost have the same specs?
[Honor 7 Themes and Apps] mai55:
Hi.

I have made a new theme called "Tron". The main feature of the animated lock screen.

Installation: Install to the folder "Hw Themes" after opening the theme reboot

Download: https://mega.nz/#!49hHlQYA!vkwGUgN9Uw49wKgsNR4ii5eAWMuuOD6BImecQJub_ts
[Honor 7 Themes and Apps] sachin.george96:
This really sucks
[Honor 7 Themes and Apps] AmitJordy:
Good Theme

Good Theme, thanks
[Honor 7 Themes and Apps] the_white_fang:
Nice icons

Good looking icons, but the wallpapers are not as good.
[Android Q&A, Help & Troubleshooting] chnateag:
Hi guys,

I've got 60 phones to setup, and that's just the biginning. I looked for some solutions to mass deploy them, the fastest way possible. I of course already know titanium backup and applications like that, but i would prefer not to root phone...

I was pretty confident about a nandroid backup : flashing the recovery of the phone is really quick, and i would just have to backup on card or on usb on the go on the master phone, and to restore the backup on all the phone remaining. But it didn't worked as expected, it happens that on each phone, twrp is generating backup in a folder named something like "420khg66g6cca200" and which is different on each phone, and when you put the card in another phone, this one doesn't see the main backup.

I of course tried to sneak arround and generate a backup on the second phone, which i replaced with the content of the first one, but the phone doesn't even boot anymore.

I used twrp because i dind't find another recovery avaiable for the phone, which is by the way a samsung Xcover 3 also known as SM-G388F.

I tried to backup only system, system image, and data and to restore it and the phones is stuck on boot screens.

I tried to backup again with boot partition, same thing happen'd. There's something i don't understand tho, there's some warning about /system partition which can't be mounted when i look around on the recovery of the slave phone.

I'm on stock rom, no root. I looked for similar post (really), but there's mostly guys which make backup / restore on the same phone, and i didn't find my answer.

My questions are : is there someone's who did this before ? Why the phone doesn't boot anymore ? Is there something that's making the backup unrecoverable on another phone ?

In this case, is there anyway to bypass that ?

Thank you by advance.