yashsingh1/xdaforums huggingface dataset:
[Nexus 9 Original Android Development] ode_:
Can't understand why this worked, but yes it works now when using US on system language.

Now have to dig out where is file what contains paper size settings and fork it to A4..
[Nexus 9 Original Android Development] NYCHitman1:
It's because the UK English language doesn't contain updated translations. We only focus on US English. The rest are reliant upon contributions from users, etc..
[Nexus 9 Original Android Development] ode_:
Understandable thing.

More than happy with current condition of ROM, more when understanding limits and more familiar with it, it just seems really robust ROM with really minor limitations.

You probably run some kernel audition app, like Trickster MOD or FauxClock etc, if yes could you tell what, 'coz probably best for me is something what author is using, then kernel setup is compatible for it.

I have tried both above auditors and found out at both are working fine, Faux has something magical touch on kernel, but it's but clumsy comparing to TM.

Exploring kernel/etc setup it made me wonder few things, ZRAM seems to be locked, or above auditors just can't handle changing it size (actual size is mystery to me on this point, maybe that 508mb?), also really big surprise was that Faux stated highest CPU clock as 2.5ghz.. I know at numbers can lie, a lot, and that's why asking what app you use for kernel audition.

Have to say, now after tweaking bit this v9.7 DU I'm well aware of risks making it vulnerable to fails or things caused by MY actions, and NO I'm not making any complains or bug reports from situations what might be caused from MY actions with ROM settings alteration(only if full clean situation is used, then). Probably next update to my ROM is on far far in to future when Marshmallow is breathing its last breaths, 'coz I don't need newest thing on earth, just stable and working - what this lollipop dirty unicorns is.

So big thanks to you for giving this DU to us!

Few pics from fiddling around: (2499000 - 382500mhz, swappines 10%, intelliactive cpu gov, 512fiops, entropy contribution off, low memory kill will be adjusted later)

Spoiler content hidden.
[Nexus 9 Original Android Development] NYCHitman1:
I use Kernel Adiutor. It's the most feature rich app we have for kernel tweaking.

As for settings, I use Interactive w/ 510-2091MHz. CFQ I/O w/ 2048 RA. That's about it for what I tweak.
[Nexus 9 Original Android Development] ode_:
I have tweaked lot more :)

Starting to be happy on efficiency of this ROM now, really like to have A4 paper size, but no easy solution. How hard it would be to copy US to UK but leave paper size and other metrics there on UK? This would be great for European users.

Here's my tweakings, it keeps tablet cool, won't shut every background app so aggressively ("better multitasking"), leaves snappy and smooth UI and gives around 10h hour SOT, doesn't matter are you watching Netflix or doing something basic, still ten hours is pretty close. Sharing if someone wants to breed something out from it.

Some minor tweaks might happen, but after reading kernel sources, if I have that much of interest, coz this feels just fine, minus letter paper size :)

Spoiler content hidden.

Edit: low CPU 408Mhz and 384kbRA on io, otherwise it bit cuffs on hd videos on YouTube, will see how this ends.

It utilizes dual core pretty well, won't stuck on high speeds on single core, calls help from other and drops speed, seems like power consumption guesses on clock speeds vs. Core amounts were going close.
[Nexus 9 Original Android Development] NYCHitman1:
CPU min was always intended to sit at 510MHz. Anything lower and you're essentially bottlenecking yourself.
[Nexus 9 Original Android Development] ode_:
you're right, I'm searching good balance of two core basic CPU load, like when running Netflix with 384 it goes on dual core both at 384 all time and hour consumption stays around 8.5% and zero cuffs. YouTube generates more load and there is small cuffing on 384, now testing what will help that, it cuffs bit even on 510, so searching more from timings, i/o etc, probably fiops just is too slow, 408mhz with 522kbRA fiops is reasonable choice, but not happy with it yet. Might have to change i/o governor to get more fluent read, coz rising above 512kb on fiops causes lag/cuffing.. Also generating nearly zero use entropy takes slot from CPU..

Well gonna play with settings and try to find some good balance for me.

Cuffing feels coming from somewhere else than CPU speed, similar cuffing seen on both governors it self, io and CPU. But searching :)

This is hard without real consumption graphs, would be nice if consumption graph pops from somewhere. My other devices are snapdragon based and those have consumption graphs available, easy to tweak inside those limits.
[Nexus 9 Original Android Development] NYCHitman1:
Switch I/O to CFQ or Zen and see if that performs better at all.
[Nexus 9 Original Android Development] ode_:
Cuffing on zen, not bad but noticeable when watching ie Blancpain races HD YouTube, CFQ kinda fine, concentrating on BFQ this moment, probably best flow on HD YouTube races(after quick tuning of idles, seeks etc.).

Small concern about battery drain with these, probably just nothing to worry.(I'm targeting under 10% / hour drain, preferring near 8.5%)

And yes both were better/smoother than fiops.

Current testing point with BFQ using 2048kbRA, 459Mhz CPU min(also difference from earlier post I'm having Entropy r512/w1024):

Most choices are familiar, but then there is also values what I don't know exactly, and tuned those from feedback feels, if you (or someone else) see something stupid here please let me know.

I'm having feeling of too much drain with this, above 10%/h(not much), testing load is HD YouTube videos, YouTube is a really thirsty b...h.
[Nexus 9 Original Android Development] NYCHitman1:
I don't see any stutters on YouTube or Netflix at all. Never have.
[Nexus 9 Original Android Development] ode_:
Netflix no, but on YouTube there is minor. When watching race videos, car driving, simulator driving, it makes small "drops" on fps, like missing few frames on constant flow. That's not biggest thing on world, but when you have capability to avoid those why not. Most people aren't noticing those or just let them be as it's normal on internet video quality, I don't like to let those be, I'm taking all frames. I'm kinda perfectionist :)

That BFQ now (as posted) keeps pretty nice stable flow even on 1080p60.
[Nexus 9 Original Android Development] NYCHitman1:
The latest stable build is now in the OP. Enjoy!

Side note: This will be our final Lollipop build. Stay tuned for delicious Marshmallow goodness! :highfive:
[Nexus 9 Original Android Development] cerj:
Thank you, and looking forward to the goodness
[Nexus 9 Original Android Development] oblivianz:
Does this ROM come with a modified/tweaked kernel? And also are most people on this ROM running the default kernel?
[Nexus 9 Original Android Development] NYCHitman1:
Yes, it does.
[Nexus 9 Original Android Development] muhsli:
Josh, I just have to ask because I recently swapped out my 7 year old DIR-655 and finally got myself some 5Ghz WiFi.

Are the N9 capable of connecting to the DFS channels at all? At what level are they locked down?

I'm asking because I'm currently on the 6.0 test build, and so I don't know if it is as easy as that you've enabled it in the lollipop builds (but not yet in the M test) or if it's locked down in the hardware in some way.

I've tried some googling about it, and there seems at least some people on stock ROM have been having some troubles with the N9 and DFS.
[Nexus 9 Original Android Development] NYCHitman1:
I'd have to look into it, tbh. It's kernel related.
[Nexus 9 Original Android Development] muhsli:
Thank you that would be very nice, good thing it's in the kernel so you know where to look.

furthermore, I really appreciate yours and your fellow developers work! This device wouldn't have been the same without DU.
[Nexus 9 Original Android Development] cancertoast05:
I have a stock 6.0 root, using Elemental X(I forgot to backup my og kernel - Flashify may be able to help?). If I wanted to use DU, is that possible? Is there anything I need to watch out for, when going from 6 > 5.1.1 ? I only ask because I know that encryption is a big thing for 6.0, not so much for 5.
[Nexus 9 Original Android Development] NYCHitman1:
If you're encrypted on 6.0, you'll remain encrypted on 5.1.1. Not really much of an issue otherwise outside of having the proper vendor.img
[Nexus 9 Original Android Development] cancertoast05:
proper vendor img? Sorry, I am still rather new to rooting/roms. I haven't dabbled in quite a long time, I just recently acquired a Nexus 9. According to my knowledge, I would just need the DU img for my volantis, then just full wipe and then flash.
[Nexus 9 Original Android Development] gravin:
Hello I have this error "application keyboard Android (AOSP) is locked abnormally"

My rom is the Dirty Unicorns 5.1.1 (DU_flounder_5.1.1_20151106-2023.v9.8-OFFICIAL)

There is a solution? thank you
[Nexus 9 Original Android Development] NYCHitman1:
Hasn't happened to me. Did you clean flash?
[Nexus 9 Original Android Development] NYCHitman1:
You need to use the Lollipop vendor.img for Lollipop and the Marshmallow vendor.img for Marshmallow.

For specifics, please do some research on the side.
[Nexus 9 Original Android Development] gravin:
Yes I've done all wipe

---------- Post added at 08:31 PM ---------- Previous post was at 08:28 PM ----------

Another question, you can disable encryption ?? Thank you, you're so kind
[Nexus 9 Original Android Development] NYCHitman1:
Encryption isn't forced. You have to decrypt on your own. The ROM doesn't do that for you.
[Nexus 9 Original Android Development] lmulli:
I've noticed on G+ a few devices getting sneak previews of Marshmallow roms, any chance something in the pipeline for this device? Ta.
[Nexus 9 Original Android Development] cancertoast05:
Flashed 9.8, with gapps, and fix. TWRP install went smoothly. I rebooted and it is sitting on the Google logo. It has been about 2 minutes. How long should I wait? I did a full wipe (except for sdstorage.)

ed: Ok... So I got myself back to recovery, thankfully. I think I will have to restore and then get the vendor image from the lollipop image or should I take the one from the latest marshmallow? (I am coming from a marshmallow install, MRA58K.)
[Nexus 9 Original Android Development] NYCHitman1:
Take the one from the latest lollipop image and fastboot flash it.
[Nexus 9 Original Android Development] cancertoast05:
Can it been done through TWRP as well? or does it have to done through adb command?
[Nexus 9 Original Android Development] D-m-x:
Actually it is, I'm using 6.0 on my N9 as we speak. Links can be found if you're searching for them.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 9 Original Android Development] DanteGR:
Flash it from fastboot. Not TWRP

Sent from my Nexus 9
[Nexus 9 Original Android Development] cancertoast05:
Will do, I did some more reading this morning before work. I will just flash the DU img, the gapps, and the fix, then reload to the boot menu, and fastboot the vendor.img that I will extract from the latest official lollipop release. And that should yield a fully functional DU install.
[Nexus 9 Original Android Development] NYCHitman1:
Vendor.img should be flashed first.
[Nexus 9 Original Android Development] cancertoast05:
So, to make sure I have this right.

I am going to put the DU img, the Gapps, and the fix onto the sdstorage of my Nexus 9. Reboot to bootloader menu, then use a cmd prompt in windows to run the adb commands and:

fastboot flash vendor vendor.img

Then I will load TWRP and do the images as I previously mentioned.

I am using this tutorial as a reference (http://www.rootjunky.com/learn-android/adb-and-fastboot-setup-commands/)
[Nexus 9 Original Android Development] NYCHitman1:
That is correct -- minus the fact that DU isn't an image lol.
[Nexus 9 Original Android Development] lmulli:
The DU 6 for the Nexus 9 must have slipped past me when I wasn't looking as I didn't see it mentioned in the G+ group! Will have a gander. Ta.
[Nexus 9 Original Android Development] 3's&7's:
You will so NOT be disappointed!
[Nexus 9 Original Android Development] DanteGR:
Guys no matter which gapps package I flash when dirty flashing / updating the rom, I end up with no play store and Google applications in general. What am I doing wrong?

Swiftkeyed from my 1+2 A2003
[Nexus 9 Original Android Development] cancertoast05:
Conversely, if I wanted to run the test DU 6.0, I wouldn't need to flash the 6.0 vendor.img since I already run 6? Thanks for all your help sir!
[Nexus 9 Original Android Development] dictionary:
Dirty flashing.
[Nexus 9 Original Android Development] cancertoast05:
Ok. I fastbooted the vendor.img then installed DU, gapps, and the fix. The tablet is now sitting on the DU lollipop boot logo, it is just spinning. How long should I wait?

edit: mission accomplished. Bonus, I now feel a lot more comfortable using fastboot and adb.

edit2:

I did just get a message stating google play has stopped. I installed the banks dynamic I believe (I cant see my sdstorage to confirm which one I put onto my tablets storage.... I can open play store. I cant download some things. I also am unable to see any USB connection.

edit3:

Rebooted and apps optimized, toggled usb debugging and I can now access USB menu. Everything seems to be working aside from I get an app closing every now and then and it says NO SERVICE on lockscreen (I have a non-LTE tablet.) I will update if I run into any serious issues.
[Nexus 9 Original Android Development] NYCHitman1:
I never get any apps FC on me, so it may be something on the app end causing issues. Regardless, acquire a logcat for assistance on that front.
[Nexus 9 Original Android Development] ode_:
Had also problems with that banks, zero problems with "64-bit mini gapps", you should try that.
[Nexus 9 Original Android Development] cancertoast05:
Did the Camera issue get resolved? I have looked around the forums and I see mentions of it working. I see that the camera app works. However, does camera functionality extend to video chat? So far I haven't had luck.
[Nexus 9 Original Android Development] NYCHitman1:
What camera functionality are you referring to? If just normal functionality (taking pics, etc..) -- that was fixed quite a few DU versions ago.

As far as video chatting is concerned, I've used Hangouts and Skype on numerous occasions to do video calls without issue. If you're having an issue, it's on your end.
[Nexus 9 Original Android Development] cardula:
I also had constant FCs from Google Play Services with Banks gapps. So far only had one FC using Open Gapps 64-bit nano during initial setup seconds after the Welcome screen appeared upon clean flash of v9.8, since then all has been well.

[MENTION=2489052]NYCHitman1[/MENTION] Thanks so much for this awesome ROM, night and day better than stock. Just got my N9 yesterday and nearly upgraded to MM but since I've heard so many great things about DU I just had to try it. Totally worth it, thanks again.
[Nexus 9 Original Android Development] NYCHitman1:
Well, we do have Marshmallow versions of DU for Nexus devices ready -- just not on XDA as we're still working on getting our CAF branch devices up and running. Check our G+ for more info.

Side note: Keep all test build conversations on G+ as well.
[Nexus 9 Original Android Development] TYMO68:
Hello NYCHitman1, I do hope this thread isn't dead yet but I have a new Nexus 9 wifi version that I just purchased and have already taken the full upgrade to the latest Marshmallow build. Reading in the thread that you do have Marshmallow versions of DU for Nexus devices ready -- just not on XDA yet due to you are still working out things. Can I simply flash your latest build from lollipop in this thread of DU over my current unlocked and rooted Marshmallow stock rom and it should install and function just fine or since I have already upgraded to Marshmallow will it cause a problem for me? Additionally, if ok to flash what is your recommended kernel or is it already baked in and no need to flash another? I really do appreciate your response and have always been a DU fan and supporter....Best Regards.
[Nexus 9 Original Android Development] Marky__Mark:
You need to install the lollipop vendor image.
[Nexus 9 Original Android Development] TYMO68:
Thks for that Marky_Mark. So now I'm pondering if it's worth the wait on DU Marshmallow or go ahead and enjoy some DU goodness now by reverting back to Lollipop until the update is released......arggh decisions, decisions!!!
[Nexus 9 Original Android Development] Marky__Mark:
Im on AICP. I took a backup including the vendor on 5.1.1 and on 6.0.1 so its easy to restore from one to the other.
[Nexus 9 Original Android Development] TYMO68:
I have a Nandroid already of stock Marshmallow 6.0.1. I'm thinking I'll just flash the 5.1.1 from the official Nexus Dev site then flash DU on top. I'm just trying to decide if it's worth it to go through or simply hold out a bit longer for DU to release their Marshmallow build. Is this latest build from DU stable, battery, and functionality worth the effort in your opinion? I mean you say that you are now on AICP so did DU not meet your satisfaction?
[Nexus 9 Original Android Development] NYCHitman1:
I'll try to answer your questions as best as I can.

First things first, we do not like to discuss test builds on XDA. They were solely meant to gauge interest and feedback on G+, not here. With that said, I've been using my (M) builds on for months w/o issue. You'll be fine as long as you're on the latest vendor.img and bootloader.

And to answer your question -- this project is not dead. It is very much alive while going faster, stronger, and better than it ever has in previous years.

If you want to see specifics, just check out our Gerrit or Github.
[Nexus 9 Original Android Development] Marky__Mark:
I wasnt aware DU had 6.0.1 test builds. Now Im interested! DU is AOSP and AICP is CM.based.
[Nexus 9 Original Android Development] NYCHitman1:
Don't make me send the goombas after you guys. :p

Check out G+ for more info! (link is in the OP)
[Nexus 9 Original Android Development] Luigi7744:
i tried installing version 9.8 of DU, but the installation aborts... i get a "error=7" . i looked up the fix for the error and it involves extracting the ROM and editing the code line assert in the updater-script in META-INF\com\google\android folder. i tried that but i could not find the text to edit.. it seems to be the only fix i could find for that error.. any suggestions?

currently on 5.1.1 n9
[Nexus 9 Original Android Development] NYCHitman1:
What TWRP recovery version are you on?
[Nexus 9 Original Android Development] jolinnard:
Hi [MENTION=2489052]NYCHitman1[/MENTION], nice job with DU for M. I have built my own packages for a week now and all seems to be stable. So far, I have only seen a CM theme that make some apps to crash, nothing to worry about.

There is only one thing that makes me crazy, with tablet sleeping (and doze activated) the music make some "pops"... really annoying. It happens with local mp3 and Google Music. It seems to stop when tab is awake. Do you notice that?
[Nexus 9 Original Android Development] jolinnard:
Ok... I think I had an old vendor image... Flashed latest from Google official package and now it seems fine.
[Nexus 9 Original Android Development] NYCHitman1:
Latest official build is now in the OP. Enjoy!! :good:
[Nexus 9 Original Android Development] nfremd:
This might be a stupid question, but is there any issue with dirty flashing the official build over the latest test build [MENTION=2489052]NYCHitman1[/MENTION]?
[Nexus 9 Original Android Development] NYCHitman1:
As always, feel free to try -- if you run into issues, clean flash before reporting anything.
[Nexus 9 Original Android Development] nfremd:
Coolio, I'll give it a try. Thank you for all of your hard work! I'm assuming that the vendor image notification is fixed in this build?
[Nexus 9 Original Android Development] NYCHitman1:
That won't be an issue if you're on the latest vendor image (MMB29S).

As time progresses and vendor.img's change -- I'll let you guys know when to upgrade in accordance to our builds.
[Nexus 9 Original Android Development] NYCHitman1:
Server should be back to normal now. Had some minor hiccups with DC config, but all is good now.
[Nexus 9 Original Android Development] Sn0wHookr:
Can anyone confirm if this works on the LTE model? I tried the test builds last month but got a no sim card error.
[Nexus 9 Original Android Development] NYCHitman1:
No, it will not work on LTE models. I removed that capability in Marshmallow.
[Nexus 9 Original Android Development] Marky__Mark:
Really diggin the new rom. No multiwindow. And i cant get the navbar arrows to work with the keyboard.
[Nexus 9 Original Android Development] NYCHitman1:
MultiWindow is there...
[Nexus 9 Original Android Development] Marky__Mark:
Cool. Thanks
[Nexus 9 Original Android Development] NYCHitman1:
Search in the Tweaks of Dirty and you shall find! :good:
[Nexus 9 Original Android Development] nfremd:
Ok, another stupid question about multi-window. I've enabled it, but I'm using Omni Switch. I can't seem to find a way to utilize multi-window with that. If I want to use multi-window do I have to go back to the default AOSP multitasking, or am I missing something?
[Nexus 9 Original Android Development] NYCHitman1:
Precisely. You'll need to use the AOSP Recents for Multi-Window functionality.
[Nexus 9 Original Android Development] nfremd:
That's what I thought. Thank you for the quick reply and confirming it.
[Nexus 9 Original Android Development] hirndurst:
I have DU 9.6 installed and enjoyed this ROM for several months. I would like to test the new DU 10 and have some questions about the flashing process:

1. Do I have to flash the latest MM Vendor and Boot stock images before flashing DU 10?

2. At the moment I'm without a PC. Is it possible to flash Vendor and Boot with FlashFire or any other android apps?

Thanks in advance!
[Nexus 9 Original Android Development] NYCHitman1:
You'll need to clean flash. That's first and foremost. Next, you will DEFINITELY require the MMB29S vendor.img -- but not a boot.img, that comes built into the ROM.

Also, no -- there's no other way to flash a vendor.img for Flounder right now besides using fastboot from a computer.
[Nexus 9 Original Android Development] schwaene33:
It is possible. You can flash the vendor.img with TWPR 3.0.0.0. I did it yesterday. So no Problem.
[Nexus 9 Original Android Development] NYCHitman1:
TeamWin added vendor image flashing to TWRP? Well, slap my ass and call me Sally. That's awesome!

I stand corrected [MENTION=2746294]hirndurst[/MENTION].
[Nexus 9 Original Android Development] schwaene33:
Yeah they did. But do not flash boot.img and radio.img. That is not cool in the moment.
[Nexus 9 Original Android Development] hirndurst:
Thank you for your fast response! I successfully flashed DU 10. Impressive work!

BTW I was able to flash vendor.img with FlashFire. Good to know, that it is also possible with TWRP.

While setting up DU 10 I noticed, amongst some other small quirks, that I was not able to set security pattern or pin in security settings (FC). Is this an already known bug in DU 10 or maybe Gapps related? I flashed the recommended 64 Bit Gapps.

Gesendet von meinem Aquaris M5 mit Tapatalk
[Nexus 9 Original Android Development] NYCHitman1:
No issues here. Are you using a theme?
[Nexus 9 Original Android Development] hirndurst:
No theme and no special apps installed (just some Google apps like Gmail, YT ...).

See log here: http://www.pastebin.com/UrAhjii5

Gesendet von meinem Aquaris M5 mit Tapatalk
[Nexus 9 Original Android Development] madbat99:
Anyone else having problems getting ad blocking to take effect? Tried in system ad block, as well as installing ad away.
[Nexus 9 Original Android Development] USBhost:
target /system/etc/hosts.og in adway

and say yes to symlink

and you should be good.