yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] sketchman16:
Anybody else's camera not working with latest nightlies?

Also, I tried the last snapshot, and I get the same issue. Also present in Dirty Unicorns. However if I flash the Google images the camera works fine. Going to try to flash another 3rd party again, and see if it magically works there too now.
[Nexus 9 Original Android Development] zawata:
i know the device configs and settings are there but im not sure it needs to be build seperately or not(i was under the impressiong that it was)

let me look in my device tree real quick and get back to you

EDIT: hmm, i dont see why it wouldnt...

theoretically it should work i think

if anyone running the LTE model wants to risk it and try to flash this then be my guest and please let me know what works and what doesnt (namely the radio) However i will not be responsible for what happens to you device should you choose to take this advice
[Nexus 9 Original Android Development] inffy:
Well atleast the device tree looks pretty same as it is on Slimlp. I will test tomorrow.
[Nexus 9 Original Android Development] Max128:
Hi,

For a little while .. my tablet is slow for charged. I have three chargers and is the same thing, I also saw that I was not alone. So if someone have fix it this problem or have a ideas ?
[Nexus 9 Original Android Development] EnginEAR:
Thanks!

Just installed it on my new Nexus 9.

Went smoothly.

Thanks for all your hard work. It is very much appreciated.
[Nexus 9 Original Android Development] inffy:
[MENTION=5285997]zawata[/MENTION] did you have to modify your CM source someway to get this built?

I tried with CM source + your kernel and device tree but the build fails in the middle part. Will need to investigate more...
[Nexus 9 Original Android Development] zawata:
Yes I did

This commit needs to be cherry picked or else it fails saying that memchr is an undefined reference

http://review.cyanogenmod.org/#/c/83064/

That will fix those errors and you shouldn't have any more
[Nexus 9 Original Android Development] millamic:
Volantis

Is there any way to include volantis as an acceptable device type? I had to unzip, remove the assert from updater script, then rezip. It works, but isn't ideal. But THANK YOU so much for getting this out to us. Much appreciated!
[Nexus 9 Original Android Development] Max128:
Yay is the old method, update your recovery to last version ( 2.6.4.0 ) and is fine.
[Nexus 9 Original Android Development] Makkos26:
You made me **** in my pants!!! :D

Can you tell us a small range? (in a week/month/quarter?) Or is it a secret? :D

I'm so excited.... :D XD
[Nexus 9 Original Android Development] SwoRNLeaDejZ:
It may be a situation where all you need to do is flash, and then enter APN info manually. Make a backup of you APNs, do a clean install, and then restore your APNs. Report back if it works. I am sure that is something that [MENTION=5285997]zawata[/MENTION] would like to include in his OP ;) ("LTE Supported: APNs need to be entered manually")
[Nexus 9 Original Android Development] Yourgodtim:
had similar issue.

try flashing a bootloader that doesnt force encrypt... mine the roms boot and when you reboot it never comes back.

check into it in the right thread and that may help you in the right direction.
[Nexus 9 Original Android Development] zawata:
Im assuming you mean in the recovery, in which case update you're recovery to the latest twrp(2.8.4.0) which already has fixed that issue.

dont get too excited, i should be getting in contact with the CM devs tonight(more like emailing them) but the process of getting official builds could take a while(upwards of a month)

hopefully since its a nexus device(and it isnt very hard to build) the process will be sped up a little

As i dont typically work on devices with service so i will look into getting those APN's included by default but if i cant I'll include detailed directions on how to do that...provided thats actually the problem. Has anyone confirmed it runs on the LTE version? it would be nice info

EDIT: Found where the APN's are stored and how to include them, not difficult but i need to find an efficient/correct way to do it or else our wifi tablets will crash because their GSM/CDMA connectivity is broken haha

also theyre not inlcuded by default so that is very likely a problem

EDIT2: they might be included by default but a different version so ve got no idea because i havent studied into it too much...waaay too much homework. Ill see if i can look at it tomorrow while im at work...juuust for you guys

the kernel force encrypts not the boot loader

and be careful because i nearly bricked my devive doing that
[Nexus 9 Original Android Development] zawata:
Firgured out how to support LTE, next version will support LTE tabs
[Nexus 9 Original Android Development] zawata:
well it seems my CM12 isnt as popular as inffy's is but ill continue to update this anyways

currently working on getting official builds, going about the process ith the rest of my team

can say for sure

new build is up, got things like new QS tiles, a boot animation, and new setup wizard

also a possible fix for LTE
[Nexus 9 Original Android Development] inffy:
Cm has already thei own kernel (still empty) and device trees for flounder
[Nexus 9 Original Android Development] rpolito73:
Link doesn't take me to new build. Last build is 1.23
[Nexus 9 Original Android Development] zawata:
Found that this morning...like what the hell?
[Nexus 9 Original Android Development] inffy:
They were private. I think they have been working with them for a while now.
[Nexus 9 Original Android Development] zawata:
Nope only 2 weeks I was working before that

But it doesn't matter they're pretty experienced and know way more than I do, a few of our commits are similar but that's because we think the same

I'm going to be working with him getting this official so I can still help out

Looks like the official date is going to be coming a lot faster thoigh

The code is under review by the CM head devs and everything is speeding along nicely
[Nexus 9 Original Android Development] zawata:
uploaded wrong rom to wrong folder

should be fixed in about 10 minutes
[Nexus 9 Original Android Development] carlofabyss:
So I couldn't find much information regarding this except for devices with stock roms whose batteries actually didn't respond to any charger. Basically my issue is I flashed the latest nightly, flashed the appropriate vendor.img and everything seemed to work fine at first. But then I noticed that using the stock charger simply didnt work. It'll charge when plugged in to my computer (or at least the battery indicator says so) and it will charge with my nexus 5 charger oddly enough, but it simply will not charge with the stock charger on this build. Even stranger, the stable build seems to work fine with the charger as well. I understand these are nightlies and they are not meant to be stable but I was just wondering if this was a known issue. Thanks
[Nexus 9 Original Android Development] razorloves:
Starting with the Jun 13 nightly, you'll want the new MOB30M vendor.img. http://review.cyanogenmod.org/#/c/149002/

I extracted it from the MOB30M factory image if you want it https://www.androidfilehost.com/?fid=24588232905719876

As usual, you can flash it to the vendor partition with twrp or with fastboot.
[Nexus 9 Original Android Development] stephanb1:
Flashed the 1606 nightly and now have the problem that the device is not powering off anymore.

It's just stuck at the Power Off popup, the circle stops turning and I have to reboot it by holding the power button.

Vendor image was updated to MOB30M.

Any ideas?
[Nexus 9 Original Android Development] razorloves:
which rom did you come from? Does the 1506 nightly working fine?

I see someone else has reported the same problem with the lte nightlies, here http://xdaforums.com/showpost.php?p=67348751&postcount=123

have you tried 1706 nightly? It just came out couple hours ago.

.
[Nexus 9 Original Android Development] stephanb1:
Thank you for the link. Good to see that I'm not alone with my problem.

Came from another CM13 nightly about a month old which didn't have the problem.

Downloading 1706 right now. Let's see what happens.
[Nexus 9 Original Android Development] stephanb1:
After trying this and that, I ended up in a full clean install. My Nexus is shutting down fine but now I got another problem.

When an app is asking for a new permission, I can`t click on allow, only the deny button is clickable. But in settings - apps all permissions can be granted.

Already re-flashed 1706 on top but without success.

Gesendet von meinem Nexus 9 mit Tapatalk

Edit: Problem solved. Issue was caused by the app Set Orientation when the display orientation was set to landscape.
[Nexus 9 Original Android Development] lolwatpear:
Why am I stuck on the cm 13 logo? I flashed that latest vendor IMG that razorloves uploaded, flashed the latest nightly, and then x64 arm gapps.
[Nexus 9 Original Android Development] USBhost:
Does CM add support for Hardware x265?
[Nexus 9 Original Android Development] razorloves:
maybe you forgot to factory reset? just a guess. would need a lot more details of what you did. exactly how you did it and what rom you came from.
[Nexus 9 Original Android Development] lolwatpear:
got it working. i just reflashed the entire stock img and then twrp. only difference from what I remember was not changing cache to f2fs, but i've always changed cache and data to f2fs with cm13 on other devices.
[Nexus 9 Original Android Development] rbulbow:
Hi everyone,

Did any of you guys try to use Skype on your Nexus 9?!

I was able to use it just fine on stock Android, however, after I installed CM13, I keep getting a message to 'Select SIM card' and I can't get rid of the message nor use the app.

A screenshot is attached for your reference.

I have the wifi only version of the Nexus 9, just for the record.

Any help is more than welcome.

Thanks,

Ron
[Nexus 9 Original Android Development] Dariovsky:
Hi, is this forum active? Is there another forum for flounder?

Am I the only one facing Wi-Fi issues on today's (8th June) nightly? The tablet just can't find any network at all! I rebooted and wipe cache and dalvik several times and nothing.

Please give me some orientation, thanks in advance!
[Nexus 9 Original Android Development] razorloves:
flash the newest vendor.img from MOB30P update that came out 2 days ago.

should fix that.

https://wiki.cyanogenmod.org/w/Install_CM_for_flounder#Updating_the_vendor.img
[Nexus 9 Original Android Development] Dariovsky:
Thanks [MENTION=614507]razorloves[/MENTION] , I'm downloading it right now.

If anyone has interest on the latest vendor.img you can find here: https://www.androidfilehost.com/?fid=24588212152304738
[Nexus 9 Original Android Development] razorloves:
You're welcome. After you flash the new vendor.img the build id will not match, so you'll see the "internal problem message", but it's safe to ignore in this instance.

I have submitted change for that and it will be in next nightly (9 July).
[Nexus 9 Original Android Development] mr.Eiger:
Today I flashed latest nightly build. Had some problems with gapps, but they were fixed with dalvik/cache cleanup.

The only thing that stopped me from using this ROM were slightly blurry UI elements (looked like low resolution display). Icons in stock and Nava launchers (in Nova after playing with settings they became ok), fonts, and mostly noticeable - wallpapers. They looked like overcompressed images. Thought that the problem with icons could be caused by dpi settings. Changed them with no luck. What is causing wallpaper and fonts blurr cant even imagine.

Did someone faced something like that on their devices? Searched about that problem with no results. Perhaps I'm describing it with wrong terms?

Really liked functionallity and speed of CyanogenMod on my N9, but overall picture hurts my eyes, so by now reverted to stock.
[Nexus 9 Original Android Development] razorloves:
really? that sounds strange. complete opposite for me. everything's very sharp and high res. just like stock rom.

are you sure you're up to date with everything? vendor, bootloader, etc.

you factory reset?

which gapps did u install?
[Nexus 9 Original Android Development] mr.Eiger:
Yes for me it is strange too. Never had such problems with custom ROMs. Yes everything was up to date. Am not sure if the bootloader was updated, I'll recheck it. Used OpenGapps.

UPDATE: added screenshots for more visualization. In archive to be not compressed by XDA forum engine.
[Nexus 9 Original Android Development] gh0st125:
can anyone provide me a link for the latest vendor.img for the Nexus 9 LTE? The vendor.img posted above works, but now i have no cellular connectivity.
[Nexus 9 Original Android Development] razorloves:
https://wiki.cyanogenmod.org/w/Install_CM_for_flounder_lte#Updating_the_vendor.img
[Nexus 9 Original Android Development] gh0st125:
Thanks, I flashed it using TWRP, but now it's asking me for a password to start Android... which password do I have to type in? I don't have a lockscreen password.

edit: I typed in my google password, I then got an error saying the password was correct but my data is corrupt and I have to do a factory reset... I reflashed vendor.img for Nexus 9 WiFi and now it works again (but again no cellular connectivity).
[Nexus 9 Original Android Development] gh0st125:
/bump.

Any idea how i can get LTE working again?
[Nexus 9 Original Android Development] maelfilk:
Actually there are separate versions for WiFi and LTE models

http://xdaforums.com/nexus-9/orig-development/rom-cyanogenmod-13-nexus-9-lte-t3273566
[Nexus 9 Original Android Development] iNaruX:
Hello,

I just wanted to report a bug I found and ask how to fix it.

I flashed the latest nightly today and my lockscreen is behaving strangely. Luckily I am able to reproduce and record it. Here's a Youtube Link:

https://www.youtube.com/watch?v=V7KjAisUeEo

As you can see: If I have lockscreen on "swipe" it works normally (albeit only in portrait mode*), I use it only at home so I tend to have the lockscreen off completely. In this setting, I cannot access the corners and homebutton, because the device is confused between lock and unlock.

Greetings
[Nexus 9 Original Android Development] razorloves:
it's a problem on all cm nightlies right now. bugreport is already on jira
[Nexus 9 Original Android Development] dragonballz2k:
so If want to use latest snapshot I have to use the vendor image MMB29V I can't use the newer ones right?
[Nexus 9 Original Android Development] razorloves:
Right
[Nexus 9 Original Android Development] gh0st125:
thanks! I flashed latest vendor.img from Nexus 9 LTE Factory Image (https://developers.google.com/android/nexus/images) and it works now.
[Nexus 9 Original Android Development] Bastlwastl2010:
It seems there is a problem since yesterday with 64 bit Versions of CM

They are compile ist, you see the download for 1 or 2 ours, then they delete it....
[Nexus 9 Original Android Development] dumdum2:
I've installed the last snapshot (2016-08-16), and was unable to scan Wifi networks.

I did a clean install(Wipe data, cache, d.cache and system).

Does anyone has the same problem and is there a solution for it?
[Nexus 9 Original Android Development] razorloves:
You have to update your vendor img to newest

https://wiki.cyanogenmod.org/w/Install_CM_for_flounder#Updating_the_vendor.img
[Nexus 9 Original Android Development] dumdum2:
Oh I just applied the vendor-build-prop-fix.zip. I will flash the vendor img.

Thanks
[Nexus 9 Original Android Development] dumdum2:
It worked, thanks :)
[Nexus 9 Original Android Development] placebo_domingo:
CMTE got an update today.
[Nexus 9 Original Android Development] mattspew:
Volume control bug?

Not sure when this started, but when I press the hardware volume keys the volume control shows on screen but I can't control the volume.

If I press volume button, up or down, then use the screen to charged the volume, I can then use the hardware keys again.

It's like the hardware keys trigger the volume screen, but then lose focus; the volume slider isn't highlighted in blue until I press it in the screen. See screenshots.

Running the 20160820 snapshot. Tried a reinstall and clearing cache/dalvik.

Running the same snapshot on my N5 without issue.
[Nexus 9 Original Android Development] razorloves:
same here on sep 12 nightly :(
[Nexus 9 Original Android Development] Ysalamiri:
Ok, now is there a CLEAR list somewhere about what vendor.img version you need for what CM version?

Because I installed the latest Release ( cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J1-flounder.zip ) with the vendor.img version as specified in the OP (MMB29S) but my Wifi is not working, so I can't even get past the initial setup.

Flashing any other vendor.img version, and my device fails to boot (stuck on the Google screen).

Edit: nvm, found it in the build.prop file
[Nexus 9 Original Android Development] Bastlwastl2010:
This was B.S.
[Nexus 9 Original Android Development] michael_ch:
Take a look at BUILD_ID in https://github.com/CyanogenMod/android_device_htc_flounder/blob/cm-13.0/cm.mk.
[Nexus 9 Original Android Development] razorloves:
That's some weird behavior that I think is affecting all wifi only tablets with cm13.

There is a setting that corrects it.

Settings - Buttons - Control ringtone volume. Turn that off.
[Nexus 9 Original Android Development] mattspew:
Sure, but then how do we control the ringer/notification volume easily? ;)
[Nexus 9 Original Android Development] razorloves:
oh, i see now. it's still screwy.

Looks like a problem with cm framework.

There's no dialer or phone app so i'm thinking there shouldn't even be a ringer volume control.

The icons it shows for ringer, alarm, notification, media, in the sound settings doesn't even match the icons in the volume control popup that shows when you press volume button.

Is this reported on jira? Needs to be if it's not.
[Nexus 9 Original Android Development] mattspew:
I haven't logged it, was about to ask where we even log issues.

Point me in the right direction and I'm happy to log it.
[Nexus 9 Original Android Development] razorloves:
https://jira.cyanogenmod.org/projects/CYAN
[Nexus 9 Original Android Development] mattspew:
Done, thanks.

https://jira.cyanogenmod.org/browse/CYAN-8112
[Nexus 9 Original Android Development] mattspew:
They want a logcat for the issue, can someone with a logging app please provide one. I've never had success playing with logs.
[Nexus 9 Original Android Development] placebo_domingo:
I will give this a shot this weekend. I've been wanting the bug squashed for some time.
[Nexus 9 Original Android Development] placebo_domingo:
Logcat

[MENTION=614507]razorloves[/MENTION] [MENTION=4207616]mattspew[/MENTION] Pressed volume up several times. Here is the output.
[Nexus 9 Original Android Development] mattspew:
Thanks for the logs. I'd really like to see this fixed, it's really annoying.
[Nexus 9 Original Android Development] kak4rot:
What about CM 14.1 Official? I see there isn't a lot of activity here :_(
[Nexus 9 Original Android Development] fleischbanane:
[MENTION=5868649]kak4rot[/MENTION]

It could be official in a few days:

http://xdaforums.com/nexus-9/orig-development/unofficial-cm14-1-nexus-9-t3512713
[Nexus 9 Original Android Development] mattspew:
This thread may be dead soon, but..... Just noticed a new snapshot has arrived and am wondering which vendor image I need; latest Android 6 or the latest?
[Nexus 9 Original Android Development] fleischbanane:
I am pretty sure you need the latest Android 6 ones. The latest are for android 7.1.1.
[Nexus 9 Original Android Development] razorloves:
yep, as fleischbanane stated. https://github.com/CyanogenMod/android_device_htc_flounder/blob/stable/cm-13.0-ZNH5Y/cm.mk#L48
[Nexus 9 Original Android Development] mattspew:
I'm getting wifi dropout every 5 or so mins with the 20161222 snapshot. Gone back the August snapshot and all is fine again. Think I'll just wait for stable CM14 .
[Nexus 9 Original Android Development] razorloves:
lineage 14.1 nightlies have started. :good: https://xdaforums.com/nexus-9/orig-development/rom-lineageos-14-1-nexus-9-flounder-t3617907
[Nexus 9 Original Android Development] René Hitz:
cm - 12-20150131 - UNOFFICIAL - flounder will not boot

The current ROM " cm - 12-20150131 - UNOFFICIAL - flounder " fresh install will not boot , it stops at the word " Google" . " cm - 12-20150123 - UNOFFICIAL - flounder " starts . I am trying to do an update on " cm - 12-20150131 - UNOFFICIAL - flounder " . The tablet will not boot again and stops at "Google" .
[Nexus 9 Original Android Development] dom2684:
Same here , had to do a full wipe and still wouldn't boot, I went back to the previous build.
[Nexus 9 Original Android Development] zawata:
Damn really?

I'll take a look at it
[Nexus 9 Original Android Development] dom2684:
Yeah I thought maybe it would take some time so I left it , while I got ready for work . Came back 30 min later still at the google screen
[Nexus 9 Original Android Development] René Hitz:
I have the ROM left a good 20 minutes . I am now back to the previous version.
[Nexus 9 Original Android Development] zawata:
Yeah, that's hopefully because I didn't make clean before building it to save time.

I started another build before going to class and I'll check it in a few hours when I'm off work

yep, fixed uploading now
[Nexus 9 Original Android Development] René Hitz:
I installed the new ROM . After the restart, there were various error messages from crashing apps. The Google Play Store and other Google apps were no longer present . I re-flashed the Gapps . After the restart, and some updates the ROM is now running.

I am very satisfied with the ROM so far as only the charge time is unacceptable. It takes about 3 times longer than with stock ROM.
[Nexus 9 Original Android Development] zawata:
Unfortunately thats not on my end, and while i know how to fix it, im technically not allowed

The best advice i can give is too install fire-ice kernel from usbhost as it seems to do a lot better than stock
[Nexus 9 Original Android Development] inffy:
Umm why wouldn't you be allowed?
[Nexus 9 Original Android Development] René Hitz:
Installed fire-ice kernel. Testing...
[Nexus 9 Original Android Development] zawata:
well i just looked up the rules for doing this but while i am allowed, i dont have the knowledge

the CM guidelines state that all kernel values that need not be changed, should not be changed and thats on of them

while i am aloed to provide a settings for increasing charge speed in the performance menu, im dont know how too so ill leave it at stock and reccomend people too fire-ice kernel
[Nexus 9 Original Android Development] zawata:
new build will be up in a few minutes
[Nexus 9 Original Android Development] dragonballz2k:
I was wondering for people that want faster charging, but want stock kernel what about init.d using scripts? I don't think you would break guidelines since you could provide it separately.
[Nexus 9 Original Android Development] zawata:
I dont know anything about init.d scripts but if someone else wants to take thr tome then by all means
[Nexus 9 Original Android Development] inffy:
Why would unofficial rom even care about CM guidelines, its not like this is controlled by CM. That is the reason why there is source available and you are free to change it as much as you like. Those guidelines are for official CM roms, unofficials don't have to care about them
[Nexus 9 Original Android Development] zawata:
No they dont have to care, they dont care about me at all, i could pretty much do whatever i want but I'm not going too because i built this to be stock CM not "my take on CM"

I know its a problem and frankly i could probably get USB-host to tell me how to fix it but thats not what i want. I want to deliver to people the experience of having CM on their devices which means I'm following just about every rule i can.

If you want to do it in your version be my guest but I'm not going too
[Nexus 9 Original Android Development] Makkos26:
Go on just like that! :)

We love you and appreciate your hard work! :)

The pure CM what you provide us is awesome!!! And hope you will be able to get in the official line with your ROM! :)