yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Android Development] joshndroid:
as per temasek's twitter he is working on cm12.1 due to it now coming out of the staging branch and into the big time.... he states it will probably take atleast 1 -2 weeks before we even see anything.

i may get another release out for cm12.0 tomorrow, see how i go for time. in saying that it will probably be the last release.

in saying that i have been trying to prep my stuff for cm12.1 as there is a cyanogenmod branch - i have started one basically with all my merges from cm12, for now..... very early days have not even attempted to sync/build yet.... will set up and begin the big sync for my sources tomorrow.... (thankfully i just received double internet quota the other day :good:)
[Nexus 9 Android Development] D-m-x:
I just hope 5.1 will make this Tablet usable finally. I mean I really like it, but Multitasking is just horrible. Laggs, stuttering and freezes especially when playing music. I even gave up to use it that way.
[Nexus 9 Android Development] joshndroid:
Never had this issue when I took it on holidays for 3 weeks... Used it daily for these things and never let me down... If 5.1 is better bring it on
[Nexus 9 Android Development] cerj:
Im streaming movies/listening to music and texting on hangouts/surfing XDA and Ive nevr had an issue.. I can say that at one time i had 4 launchers installed ( I was checking to see how my theme was looking on all 4 launchers ) and i got some bad lag, but Im sure all of them were competing for memory.. Since ive uninstalled two and made one the default, and tapped aggresive in Nova i have not had any issues..
[Nexus 9 Android Development] SwoRNLeaDejZ:
I clean flash every time, and just use my Google account to reinstall my apps, and TiBU to restore app data on the ones I care about (from a backup obviously), and I've never had a single issue flashing anything on this device.

---------- Post added at 08:02 PM ---------- Previous post was at 07:58 PM ----------

I don't get how people are having these issues... I listen to music, and do about ten other things at once, almost all the time, and it moves between apps quickly, animations are perfect and lag free, and I have zero performance issues at all. I can't imagine what anyone is doing to render this device "unusable". That seems crazy to me...
[Nexus 9 Android Development] micmars:
Agreed...best tablet I've owned and one of the finest roms for which we could've hoped for this device...stable, fast, and handles music, video and other tasks simultaneously, and with aplomb.
[Nexus 9 Android Development] D-m-x:
If you look around there are a lot of people having those issues. Maybe you don't realize it or its different for you but it's also the little things sometimes.
[Nexus 9 Android Development] joshndroid:
Been working on my cm12.1 ROMs today, have not started with flounder but have 2 cm12.1 stock ROMs from my device trees for my other devices which is a good sign at the ease at which this 5.1 update is accepted for 'legacy' support
[Nexus 9 Android Development] El Nino1977:
Don't have any issues bud, early day rom problems and just expressed the time consuming part with flashing ROMs on a N9. I bet I can download a ROM, full wipe, flash multiple zips, boot and restore everything on my N6 before a simple dirty flashed ROM installation procedure on a N9 has completed and booted up.

The lag on simple operations and the closure of apps in background is definitely android lollipop issue, the CPU is a beast and under no circumstances under perform but it does. Arm64 on android has got a long way to go yet, let's all see if 5.1 irons out some niggles.

Apart from that, I love the device and the whole concept of it. Probably my 3rd best Nexus device I've owned. This is now my 6th Nexus [emoji41]
[Nexus 9 Android Development] SwoRNLeaDejZ:
I wish I was on this ROM so I could say whether or not the issues are CM specific, because I don't use this ROM (not going to start cheerleading for the ROM I use, but I think if you look closely enough, you'll be able to determine what it is) but with my current setup, my performance is incredible, and lag is the last thing I notice. Initial bootup, after flashing, takes about 8-12 minutes re-encrypt storage, but every boot after that is no slower than either of my N7s.

With screen off, tablet idle, I am getting ~21 days of standby on a single full charge. With use, ~2 days with about 7 hours of screen on time, and performance is rock solid. Should be noted, I am already on 5.1, but I don't remember having any issues on 5.0.2 either. (and don't mention the "memory leak" because AFAIC that "bug" doesn't exist)
[Nexus 9 Android Development] siraltus:
I'm on the Nexus 9 LTE and on the 3-29 build, GPS is not present at all. Flashed back to stock, GPS works great. Flashed the 3-29 build again, no GPS. Oh well.
[Nexus 9 Android Development] D-m-x:
Works fine for me on 29/3.
[Nexus 9 Android Development] House.m.d:
I cannot install,"File Corrupt", latest Version. I m on TWRP R7
[Nexus 9 Android Development] taronas:
GPS works on the LTE device?
[Nexus 9 Android Development] D-m-x:
Don't know that, on WiFi it's fine though.
[Nexus 9 Android Development] House.m.d:
I downloaded 4 times, but not able to flash. TWRP says ZIP file is corrupt.

Gesendet von meinem A0001 mit Tapatalk
[Nexus 9 Android Development] siraltus:
GPS is not working on the LTE variant. I went back to the stock ROM.

---------- Post added at 09:28 AM ---------- Previous post was at 09:28 AM ----------

You're on the WiFi variant. I'm using the LTE variant and there's no GPS.
[Nexus 9 Android Development] joshndroid:
What browser are you using?
[Nexus 9 Android Development] House.m.d:
Boat Browser on Android and Firefox on Windows 8.1.
[Nexus 9 Android Development] joshndroid:
feeling like my n9 has been a little neglected. Temasek version is now 9.5 (cm12.1) i managed to get builds off with my other 2 devices which were always going to be a bit easier, so with my day off today i will hopefully get us up to speed. Starting relatively from scratch with our device again (mainly because i am going to be unsure of what build errors may crop up from the difference between the cm12 and the cm12.1 builds, so i am starting with a fresh local manifests and will run builds and re-add my changes where necessary. will report back.
[Nexus 9 Android Development] MotoFlasher:
I can wait ... U2?

[MENTION=4144316]joshndroid[/MENTION]

THX for Info

Thank you all who work on this project/device! :highfive:
[Nexus 9 Android Development] maikinho10:
Hi,

i see your conversation with temasek on twitter, think you found the build issue right:)?

Looking forward for a new awesome update.

Many thanks [MENTION=4144316]joshndroid[/MENTION] [MENTION=2332422]temasek[/MENTION]

Greets Maik
[Nexus 9 Android Development] joshndroid:
Yeah don't know what may be causing it... Kind of over my head atm lol

i can't get a build out from cm12.1 so it potentially be a cm problem at this time
[Nexus 9 Android Development] micmars:
Get that miscreant partner in crime on this, the slacker should stop kvetching about light bleed and just blind build. I thought this was supposed to be APascual does all of the boring stuff.

Sent from my Nexus 9
[Nexus 9 Android Development] joshndroid:
Nope he no longer has the device.

Plus this is a device tree issue or an actual cm issue at present as stock cm won't build either
[Nexus 9 Android Development] micmars:
There's no reason to imbue reality into the situation...so he keeps returning the thing over supposed light bleed, just make him fix stuff, or just blame him even when not needed.

He's a really terrific dude, and I just think that shouldn't be tolerated.
[Nexus 9 Android Development] joshndroid:
thanks to [MENTION=2649771]dcrin3[/MENTION] in the cm12.1 thread, i have been able to cherry pick a commit that fixes the error i highlighted above. currently experiencing other build issues with temasek rom (not related to just flounder) at the moment so running a stock cm12 flounder build myself to see if any other errors crop up for me. once i can rebuild temasek i will conduct further work on this rom. At present i have been able to keep a lot of the arter optimizations this time round by looking better into the commits for optimizations that i originally removed in the cm12.0 based rom, so in theory, it should be better optimized as well as being cm12.1. I havnt been able to spend as much time as i like working on it as i would like due to work commitments at present.
[Nexus 9 Android Development] cerj:
Im running temasek v10, which is CM12.1 on my Note 3 and it is a treat.. Im sure you will work out the kinks and if you need any help testing, micmars will be happy to help.. He not only talks the talk but he walks the walk.. ;)
[Nexus 9 Android Development] joshndroid:
i have been able to get a successful build out. had to change a few things unfortunately which means i have lost a few of the optimizations at this time.. about to test and see how it goes
[Nexus 9 Android Development] Dunka:
Thanks for all your work on this and also for keeping us updated :good:
[Nexus 9 Android Development] joshndroid:
uploading currently to romhut will have further instructions soon. :good:

i would suggest downloading your 5.1 gapps - i recommend the 64 bit gapps by craigacgomez (linked in second post)
[Nexus 9 Android Development] joshndroid:
Okay so here is the release for Temasek cm-12.1 v10.0

Firstly, you should be recieving an update notification for those who are on a previous version from the OTAupdater, or you can do a manual refresh/check and it should pop up. For those new or coming from another rom just head to the link from the second post and download away.

I would STRONGLY recommend doing a clean flash, I did.

Use the rom, linked 5.1 64 bit gapps and latest version of supersu

The boot up time for the first boot will take a while, as usual. Do not be discouraged, throw it on charge and give it a bit of time.

On actual boot you will get a pop up complaining about internal device error check with manufaturer. This error can be disregarded. It is an error with chekcing the vendor image fingerprint as per craigacgomez. I have also ran the rom for a while and it had not affected performance. There is a fix in his thread however I have not flashed it. Those coming from his rom may not even get the error pop up.

Everything else should be business as usual. I know the changelog is broken due to the build tools at the moment, I had to revert to cyanogenmod's version to get it to build (the changelog is in the otapp and on romhut as usual though). I will work on this one in the mean time. There may be some other bugs, etc as this is a dirty out release. Next version i will nuke my out directory and build fresh. This was just really to get a release out to you all.

cheers

edit: i know audioFX is still force closing. I imported the source fix however the required lib was not being pulled from the device. I should have it fixed for next release.
[Nexus 9 Android Development] joshndroid:
I know i'm spamming my own thread, however some people don't look at the edits and only await for new posts

I have added a fix for the audioFX, a flashable zip to the addons section of romhut - see here - https://romhut.com/roms/temasek-flounder

download and flash it with your usual flash routine. It will only really be needed for v10.0 i will have it fixed for future
[Nexus 9 Android Development] joshndroid:
Next build audiofx fixed no need for fix zip, changelogs fixed as well as build optimizations due to fixing up optimized temasek build tools. Trying to import back optimized bionic but receiving fair few errors will attempt again another time
[Nexus 9 Android Development] D-m-x:
Thx for all your work man, I'm going to wait for your fixed release and do a clean install (wipe eveything). I'm really excited how CM 12.1 is going to perform.
[Nexus 9 Android Development] House.m.d:
No matter what Rom i flash, there is always the same message after a Reboot.
[Nexus 9 Android Development] oby2:
I pulled this from the rastapop thread, fixed my problem

You just need to make sure "ro.build.fingerprint" in /system/build.prop matches "ro.build.fingerprint" in /vendor/build.prop for that dialog to go.
[Nexus 9 Android Development] MotoFlasher:
Really thank you for your efforts!

Flashed and excited again! Runs without problems. :good:

And because of the error >> the vendorfix zip-file had not helped me, and I had to edit the build.prop myself.

As oby2 writes I have it also from the Rastapop thread.

BTW

Both kernel (zen & fire-ice) run gorgeous! See Screenshots...
[Nexus 9 Android Development] House.m.d:
Ok, thanks. Had edited build.prob manually and .... fixed!
[Nexus 9 Android Development] Dunka:
Wow, it flashes must faster than 5.02 did.

So far no issues, other than the known vendor fix.

Thanks again
[Nexus 9 Android Development] joshndroid:
I did mention the vendor fingerprint 'internal storage' issue and a potential fix but anywho, thinking of making something more eloquent but the necessity for it may only be a one time thing so maybe not
[Nexus 9 Android Development] dictionary:
Flashed this ROM and didn't flash the vendor fix. I've previously flashed it for other ROMs. Never got the internal message, so might be something that only needs to be done once. Will have to investigate further, but really, it's pretty easy to flash after every new ROM if need be. Thanks for a nice release. :)
[Nexus 9 Android Development] joshndroid:
Okay will take a quick look after work again will do another release as well hopefully, just need to install new fan setup in my desktop get rid of some heat ? first. May go a water cooler setup soon instead of the Cryorig ultimate Cooler to overclock
[Nexus 9 Android Development] vogemic:
Great rom! Only problem that I have is GPS is not working. Maybe you could fix this? Thanks for all your work!
[Nexus 9 Android Development] taronas:
GPS on LTE seems to be broken at the core of CM. It does not work in any CM based rom so far, 5.0.x and 5.1

If you need GPS go with an AOSP build like http://xdaforums.com/nexus-9/development/rom-pure-aosp-12-6-14-t2964737
[Nexus 9 Android Development] joshndroid:
probably the required files are not there.

going to be running a new build soon, just going through the motions as usual :good:

side note; Just Frankenstein'd my desktop.. now a total of 4 x 200mm fans and 3 x 120mm and a Cryorig Ultimate Universal fan:good: some serious cooling power now. thinking of watercooling cpu now for OC for more power when building :cool: (should have got an 8-core :p )
[Nexus 9 Android Development] djkinetic:
clean flash of 4-21 build causes camera not to connect.
[Nexus 9 Android Development] joshndroid:
Hmm didn't get to try the camera myself. Got a log?
[Nexus 9 Android Development] D-m-x:
Just had a few minutes before I had to go. But I think the camera didn't even show up for me in the launcher. I will however look at this later when I get home and get you a logcat if no one else got you one first.
[Nexus 9 Android Development] joshndroid:
Did u check your apps package sometimes I find I need to install Google camera from market, bizarre but yeah
[Nexus 9 Android Development] D-m-x:
Nah, haven't had time but that could very well be. Although Craigs Gapps should include everything as far as I remember. But i will check it later and get back to you.
[Nexus 9 Android Development] MotoFlasher:
Several times tried clean flash (new OTA zip) with the new Craig Gapps but after update had a permanent play service FC.

Then tried OTA & Craig Gapps from 03/13 and a lot of different FCs. :eek:

I do not get what's wrong with me or the n9 :silly: ... never had such problems.

Something like an "mind-edit" ;) >>

When writing the post I thought to myself - try it again. Clean flash with new Craig Gapps and tadaaa works. Although had 2 FC (settings and play services) but after confirming they were gone.

To the Google camera problem >> It does not work. Have uninstalled the existing version with tibu and reinstalled from the store.

Camera has an FC.

And ...Um... in the store it looked (Existing app, before the uninstall.) >>

Tried to catch a log - maybe it will help.

Log´s >>

https://drive.google.com/file/d/0BxBzjtoD04QfdkI5VnVfSW0yVFE/view?usp=sharing

https://drive.google.com/file/d/0BxBzjtoD04QfWUtocmd0dXlMYk0/view?usp=sharing

I tried the app "Camera FV-5" and these are the error message >> Camera driver could not be loaded.
[Nexus 9 Android Development] D-m-x:
Again just had I few minutes to test but I can confirm what MotoFlasher says. Deleted the camera folder via Root Explorer and installed it again. Camera Fc's immediately.

Edit: I will also upload a Logcat later today.
[Nexus 9 Android Development] joshndroid:
Does someone who has flashed the vendor fingerprint fix have a broken camera?

edit - just trying it myself hold up7
[Nexus 9 Android Development] Dunka:
I had an icon on my dock that when pressed said gallery has stopped but that icon wasn't in my app drawer, my camera does work once I found the (AOSP) camera in my app drawer.

Flashed the Gapps from the OP
[Nexus 9 Android Development] joshndroid:
alright so the vendor fix from the other thread will notget rid of the error, however, I did make my own which got rid of the error. Need to think of a better way to do it automatically lol

fixing that error did not fix the camera (as i was hoping due to what was looking for in the log) - i had to do one thing to get rid of an error on building last release which may have been the thing to cause the camera to break so i will try that out.
[Nexus 9 Android Development] joshndroid:
going to full nuke everything tomorrow, update all source to 5.1.1 r1 - ran out of time today due to work. ran a fews builds camera still fails to connect, may have to revert a few things me thinks
[Nexus 9 Android Development] D-m-x:
Maybe a good thing, I'm also unable to play any Video. Doesn't matter if it's YouTube or Twitch. There's sound for roughly 1 second and then just Black Screen without Buffering.

Thought i messed something up an clean installed again (Rom, Gapps, SuperSU) but that didn't change anything.
[Nexus 9 Android Development] joshndroid:
Okay it's sounding more like a change I had to make to remove errors in frameworks av, seems like it may be more important than just disregarding the error
[Nexus 9 Android Development] D-m-x:
If you need any logs just say the word.
[Nexus 9 Android Development] joshndroid:
Frameworks av looks after codecs and the like. Break one of them potentially break camera, video playback, etc because the codec that handles it is broken... Have a few ideas just takes time is all... All else fails I have a last ditch solution lol ?
[Nexus 9 Android Development] jaxbierley:
Question for understanding:

Since you say you be merging 5.1.1 into the builds, that's because the source available. Now, since it nor 5.1 have actually been released for the 9, is it truly fixing issues or what. How exactly does that work?

Either way, love the ROM, just curious is all.
[Nexus 9 Android Development] joshndroid:
N9 is a little different to others in that binaries are held in a separate partition. Further just because Google hasn't released a build for it doesn't mean that it a) can't run it or b) have things fixed by devs in the mod community. There are some very knowledgeable people out there that have fixed stuff that Google has screwed up in source. 5.1.1 is the next evolution of the source for many things and it would be silly not to implement them when alot of it easily will be. The underlying (base) hasn't necessarily changed its more fixes etc just like devs do their their roms. I'm not a dev I'm giving it a crack but I'm just learning through this all myself
[Nexus 9 Android Development] tcleary73:
hey, first off thank you for all your hard work. been running your ROM since early march and never had an issue until the latest build. when I boot up from a powered off state I get this message...it has no effect on performance and I had never seen it until I upgraded to 5.1...any ideas?
[Nexus 9 Android Development] D-m-x:
Yeah, read the Posts in this Topic especially those written bei [MENTION=4144316]joshndroid[/MENTION]
[Nexus 9 Android Development] joshndroid:
I will make a zip for the internal device space error
[Nexus 9 Android Development] joshndroid:
So I have been building n9 roms all afternoon firstly I will say I got one build that was blisteringly fast unfortunately the camera was broken... Something imported as per temasek build is breaking it and the Av frameworks fix I tried did not fix the underlying problem it just either turned the error off or disregarded the error message... So essentially I am going to revert back to cyanogemod and track my own from scratch and import bits and pieces until I either find the culprit that breaks it or atleast have a good solid Base for 64 bit. It doesn't effect the build as a whole as within I might just create a separate branch for releases and one for me to tinker with to keep builds in the meantime
[Nexus 9 Android Development] D-m-x:
Just the Camera? Would you mind releasing that Version, maybe just in an external Link so I could flash that.

At least I could flash and use that build if Video Playback works. For now my Tablet is just lying in the corner otherwise ^^
[Nexus 9 Android Development] joshndroid:
Camera test is what I was testing as video codec fail.. Remove the error and it won't build so that one had to go... Will crack out a build tomorrow with the 5.1.1 source its too late her atm
[Nexus 9 Android Development] joshndroid:
have been cherry picking optimizations from tema branch, running a build hopefully all goes smooth and will have a release for you guys by this afternoon =]
[Nexus 9 Android Development] D-m-x:
Can't wait, did you get everything to work :D?

Also a good thing that your Afternoon is my Morning :D
[Nexus 9 Android Development] joshndroid:
Getting build errors at the moment temasek is busy so I have logged the errors.. Once it is fixed I will continue building
[Nexus 9 Android Development] temasek:
Derpy temasek :(

There are some stuffs, probably imports or what's not from CM silent mode commit. I'll fix when back home.
[Nexus 9 Android Development] joshndroid:
No problem temasek it is all good.. We all have a life
[Nexus 9 Android Development] joshndroid:
new 5.1.1 build is up... have a feeling lte is going to be broken due to many things being removed in the device tree for volantis.... so i haev taken the name out of the thread.... also ther eis a build fingerprint fix in the addons section. cheers.
[Nexus 9 Android Development] vogemic:
Thanks! For me LTE is working. Did dirty flash. Wiped dalvik cache, system & cache.

Did clean install LTE still working. GPS no go.
[Nexus 9 Android Development] cerj:
Thank you tema, your roms are my favorite across devices
[Nexus 9 Android Development] D-m-x:
Finally got around to install the new Build. Great work [MENTION=4144316]joshndroid[/MENTION]

Very smooth with ElementalX and I also haven't encountered any Bugs. Xposed x64 works also on 5.1.1!
[Nexus 9 Android Development] wingdo:
I've been running AICP but gave Tema a second chance Friday night. Insanely stable, and fast. I love that it works with Elemental X as well as Xposed. Very pleased to have moved over.
[Nexus 9 Android Development] D-m-x:
Anyone got a clue why my Tablet is draining battery like hell. 10% per Hour, better Battery stats, Wakelock Detector and internal Battery stats show nothing unusual. Doesn't seem to be awake the whole time.

Maybe Custom Kernel or something?
[Nexus 9 Android Development] wingdo:
If you are using a custom kernel like Fire and Ice or ElementalX, try switching the CPU gov. to Interactive and away from ElementalX if EX is the gov used.
[Nexus 9 Android Development] D-m-x:
Just done that, thanks. Will report if it helped tomorrow [emoji1]
[Nexus 9 Android Development] wingdo:
It should help. The EX gov is performance geared, basically as soon as you touch the screen it jumps up to max freq. Great when gaming, but it kills the battery for me.
[Nexus 9 Android Development] joshndroid:
Fresh build will be out asap thinking Tuesday, have one at the moment don't have time to upload