Let me start off by saying that we are grateful for everything that Chainfire has done for the community. From Mobile ODIN to SuperSU to FlashFire, the guy is a beast and has help the Android community more than anyone. That’s a fact. Thank you for everything you’ve done for us Chainfire!
We started using SuperSU at the beginning of 2014 and it still performs great! Chainfire has even work together with our very own Josh Chasky in getting our Pixel C (dragon) working with SuperSU. We love SuperSU! Back in September of 2015 the news broke out that Chainfire was selling SuperSU to a company named CCMT. We like everyone else had questions. Part of it was that was the unknown. We’re humans and is in our nature to get curious about the unknown. Back then we didn’t know much but that Chainfire had sold it to a company own by an individual or group of individuals that supposedly own other root apps and that it was a new company. A lot of rumors started to circulate. Everything from Chinese hackers to the owner of XDA to even Google. It got crazy and stayed crazy for a while but like all things, it died down. The community went back to using SuperSU and that was the end of it, at least until now.
A week or so ago, this conspiracy surfaced up again. Same demands, same arguments, just different usernames and more people shouting at the computer screen. We won’t take part in the mudslinging but we have to address this issue because Dirty Unicorns is a large AOSP project with many users and we do ship SuperSU with our builds as of right now. So allow me to put out the facts first.
1. We trust Chainfire. He’s a great contributor and developer and the community would not be the same without him.
2. CCMT has been pushing out updates for over a year now so if they were going to steal our soul here, they would of done it already.
4. There’s been ZERO reports of anyone falling victim to identity theft that points back to SuperSU.
Here’s our plan!
We will continue to use SuperSU until there is something to talk about other than rumors and conspiracies. If SuperSU does stop working or there’s an issue that can’t be address by Chainfire or by us, we will move forward and use Koush’s open source alternative, Superuser.
Superuser is what we were using back in 2014 when we switched to SuperSU. We’ve gone ahead and tested Superuser with our N builds (no ETA’s) and it performs good. We haven’t noticed any hiccups with any known root apps. I’ve had a few testers take it and try to make it crash or find issues and nothing.
So to wrap this up, please just know that we are prepared. If something does go wrong we will put this plan into motion but as of right now, we rather not jump to conclusions. Chainfire is a trustworthy developer and this company has been pushing updates for a year now so again, until there’s solid evidence of any wrong doing is business as usual!
So many of you know that Android N is being rolled out today. I was a bit surprised to see this considering the new Nexus devices have yet to be announced. History told us that this would never happen but it did (where’s that crow at). Google seems to have lost their mind but we’re ready for the cluster ahead.
The point of this post is to give our users some insight on where we’re at and where we plan to be in the coming months. I’ll start off by saying that is been great working on Android M. We’ve all learned a lot and really enjoyed ourselves along the way. For us we gained new talent and saw “old talent” step up and really it was great seeing people come together on a common goal. We had a lot of pieces, some didn’t work but in the end I think we’re happy where things ended up at. We made some mistakes but we’ve learned from them and hopefully don’t make the same ones twice.
Right now we’re waiting on security updates to roll out on Monday September 5th (2 weeks from now). Security updates will be merge as soon as we can into our source and we will release v10.6 on Friday September 9th. Version 10.6 will be our final M release. Weeklies will come to a stop Friday September 2nd. DU builds based off Android N will be label DU11.
While waiting for security updates to drop, we will go ahead and get a manifest for Android N going as soon Google pushes the source to AOSP. Don’t get too excited yet because we won’t be adding anything or releasing anything just yet. We will evaluate the source for about a week and see exactly what we have. We expect the worst out of Google and so we want to see what’s broken first before adding in a ton of things on top of it.
After we evaluate the source, we will try our best to fix any issues that we may find and really get a solid base. We have a cabinet full of unique features and want to make sure you enjoy them without any hiccups.
This cycle will catch those that like the kitchen sink ROMs by surprise. We will be focusing on less. People say less is more and that’s becoming more true than you guys can imagine. We’ve started to really see that a lot of mods were just there and that really nobody used them. We came to this conclusion by looking at our community. This doesn’t mean that we’re going for a vanilla look and we’re going to hype up a battery icon and a new wallpaper, that’s not that we mean. What we do mean is that you won’t see a lot of things in DU that are not used by us. Things like ‘gesture anywhere’, ‘app circlebar’ and a few other mods will be a thing of the past. You want to use those mods, don’t bother using DU because you won’t see it in future builds. We will focus on expanding even more on what we have and in turn provide more original work.
Do you plan on sticking with the CMTE?
Yes, we will go forward with the CMTE minus the CMSDK and everything we’ve done to it so far. Since the start of M, we’ve made significant changes to the CMTE and we’re curious where things lead. The CMTE for us provides a lot of flexibility for not just the user but for developers. Proof of this flexibility can be seen with the work we’ve done so far. Things like our themes tile, headers integration and the ability to continue to make use of features such as instant patching in apps like Arcus without the use of the CMSDK.
Are you guys still going to support the same devices?
I would love to tell you that we are and that your 3 year old device will keep going strong but that’s very unlikely. I’ve heard whispers from maintainers that they will drop devices because either is becoming too much of a pain to deal with hacks or they just really want to use something newer. As of right now, we can’t say for sure and provide you all with a list. You will for sure see a few devices swap out maintainers. Some maintainers are planning on getting newer devices and other maintainers are picking up those devices left behind. If your device does get drop from official support, don’t be surprised. Maintainers lose interest all the time or the device just gets too old or sometimes life hits and life is really unexpected.
So when can we expect DU11?
Like last year we don’t plan taking part in the annual ‘I’m first’ race. We’re not hungry for donations and we don’t have anything to prove. We’ll evaluate our source and very carefully move forward. We’re learning from past mistakes and rather just take our time. We’re constantly innovating and pushing out unique features. Really just pushing the bar, setting the standard and making the community better! Up until now, google has had a rough 8 month window between the time they release the source for the next Android version and the time they announce the next Nexus. For us that’s a long time to make sure we get things right so you won’t see builds from us for a while.
If anything changes, we will update via our G+ community so please keep an eye on there for teasers and updates!
So as many of you now know, we have a new logo via a community contest! The winning logo selected by a team vote was made by Rajath Ranganath. This logo was legitimate and many users loved it, but we needed something that spoke to our brand and so we changed our mind. We went with John Xionidis‘ logo who btw got the second most votes in this contest and have not looked back. The community has taken it and run with it!
Known designers like JayRod, Paul Clark, Simon Schürrle and many more (I could of listed more folks) have shown their love for the DU community once more by creating absolutely amazing wallpapers! There’s even been talk of DU edition themes by both JayRod and Jacek Malinowski! We could not be happier!
A little bit because as founder of this project, known trouble maker, and on a rare occasion — the voice of reason, it’s always good for me to look back and see where we started. It helps me see where we’re at and paint a picture in my head for where we’re going. I do this with the help of good friends on the team so don’t be fooled either, this is not a one man show. 🙂
Just keep in mind that when I started this project, it was just me, a can of red bull, and a used EVO 3D. I didn’t really see this becoming as big as it is right now. Especially not with the gerrit, website, crowdin, tons of features, etc. I really didn’t see any of this happening. I honestly figured it would just be something to pass the time, which maybe would have resulted in getting the attention of AOKP and potentially maintaining the EVO 3D for them.
With all that said, I started to look at other areas that need a makeover, a touch up in terms of design. The default wallpaper stands out as something requiring an update. It stands out because it doesn’t stand out, if that makes sense. The default wallpaper created by Jesus Partida (who also created our boot animation in both LP and M), was designed to do just that. It was supposed to blend in and not take away from anything. Times have changed. We now want something that can be used and enjoyed by users and not end up as something they quickly replace on first boot.
Below are some of the requirements we’re looking for:
– Clean and original I can’t stress this enough. It has to be 100 percent original for the exception of using John Xionidis‘ logo if you wish to add that into the wallpaper
– Must fit all supported resolutions This one is a bit difficult to explain but some wallpapers look great on say the Nexus 6P but you put that same wallpaper on say the Nexus 7, it looks like a hot mess. The wallpaper begins to lose quality and/or might be stretched out or cut down. Remember that we support multiple devices with different resolutions so if you have to, make multiple versions
– Must use the team colors Designers you know what to do with these
#980800 #FFFFFF #161616
Oh and yeah, there’s a prize too!!!
When John Xionidis‘ logo was selected, we offered him the prize just like we did the original winner, but he refused. I was like WTF, but he refused. He said that for us to make another contest and just put it towards that so thank him for this. That was incredibly classy on his part.
The winner will receive a $25 USD prize via PayPal. Be immortalized by many DU users, and get to see their wallpaper on thousands (if not more) of devices around the world!
We would of gone with a Google Play gift card, but we underestimated things, and didn’t know that we have users in countries where Google does not play ball. With that said, a gift card might not be a fitting reward for them due to country restrictions and/or they might just want a pizza instead.
The contest ends in exactly one month from today on Tuesday August 23rd. We will announce the winner that Friday inline with that weeks weekly build!
If you enter the contest, make sure that you can use PayPal. If you cannot use Paypal, please do not enter the contest. I can’t stress this enough. If you don’t know whether there’s restrictions for your country, Google it. DO NOT ENTER if you can’t redeem the prize.
How do I enter?
Simply use the hashtag #NewDUwallpaper and post to Google+. It does not have to be in the DU G+ community, just anywhere on G+. When we get ready to select the winner, we will use that hashtag to find the entries. If you don’t use the hashtag then you’re SOL.
Thank you for all the support and all contributions!
By now, you know how DU came to be and a lot of you have been there by us through the process and is been a fun one no doubt! Over the years, we’ve gone through quite a few different logos and even talked about changing the name. Some logos were original and some quite not.
Although we feel like our current logo is one of the most recognized logos in the Android custom ROM community; second to only CM’s cid, we feel is time for a reboot. Some fresh flair to branding is always good. Many organizations, companies, groups, etc do it from time to time and I think we’ve reached that point as well.
Here’s some of the logos we’ve used in the past few years.
What we’re looking for in the new logo is something original, clean and that still says DU when you look at it.
By original we mean nothing based off existing work. Nothing that includes copyrighted logos or a mashup of clip art. If you need any more clarification, please contact us in our G+ community and we’ll be more than happy to explain.
We want it done in the highest quality you can do it in so we can use it for years to come. This logo will be used in our Gerrit, JIRA, G+ community, website, github, our apps, all our XDA threads and any where you see DU. It will be seen by thousands of users and we hope that it will become as recognizable as the one we have now.
We want something that can be be used with a transparent background. What we developers have learned about logos is that while some logos look great with a certain background, there are certain backgrounds where the logo looks like total crap. If you already know this then that’s great, if you don’t please keep this in mind.
Please wow us! Seriously, make us say “That’s the one!! That’s it!!”. Bring your best!
Did I mention this is a contest?
Yes, we want to reward the winner for their work!
Not only by including their name in the DU About app under credits and XDA threads but also a 25 dollar Google Play gift card!
If the winner does not use Google play or simply would like to spend the money on pizza, is also payable via paypal.
The contest will end on July 16, 2016 (one month exactly) and the winner will be announced via our G+ community that following Monday, July 18.
Once the winner is announced, we will expect a PSD, Ai, vector, etc to be given to us. After all, we want to continue to use the logo and in the highest quality possible!
Please submit all entries on G+ using the hashtag #NewDUlogo
Theme “jank” by our definition is having a theme installed and getting a FC while you go turn on WiFi/Bt or enter one of the many setting screens we got. You go into Dirty Tweaks and is like you’ve stepped into another theme. You had a dark theme installed but Dirty Tweaks now has a white background and the icons are green while the theme had them set to red. You pull down the quick settings and you see some tiles themed while others are still stock. You ask yourself “what was all the hype about”.
We’ve all been there and it sucks.
Some people hyped up this theme, you go install it and while it looks good in the play store screenshots, that’s not the case for you. It makes the entire experience a bad one. Most themers use CM as a base which makes sense since it is their theme engine but that shouldn’t mean that other ROMs should be left behind. Our money is just as good as CM users, am I right? Things like quick settings tiles, Smartbar, Fling, etc should all be themed.
Bryan Owens of Team Blackout was the first to show DU some theme love and make his theme as pretty as it was in CM for DU. For this I will always be grateful. He started it and a few other themers have followed his footsteps and shown us love. Unfortunately not all themers feel this way and so we STILL have some jank when installing certain themes with DU.
This is where DU Certified comes into play. Instead of chasing these guys around and begging and this and that, we decided to celebrate what we have! Give these themers that have taken their time to show us love, the recognition they deserve while at the same time, saving our users the hassle of browsing and downloading 100-200 themes. Sure the play store description gives you some of this info BUT not everyone does and sometimes you miss a gem or you buy a theme that advertises support and find out that what they call support is not really support.
So a few months back we launched DU Certified and it was a success for the most part. Many themers gravitated to it and for that we are grateful. The problem came with updating the app. It was a pain to do so because in order to update the themes, we had to update the actual app. This was bad from the go and I blame myself for poor planning and I take full responsibility for that.
Tomorrow we move on beyond that and get ready to launch a more efficient way of updating our themes from within DU Certified. The user won’t ever have to update the app unless the code itself changes which that’s normal for any app. Improvements are always welcomed but you should not have to update because of the content.
That said if the app is going to hold any weight, we need to be consistent and not add themes just because we’re cool with said themer. We have to be fair and put any fanboyism aside and just be true to our criteria. So prior to launching, we’ve gone ahead and removed some themes that may have been certified and met our criteria once upon a time but that’s no longer the case. Again, this is not done because we don’t like that themer or his or her work, it just means that we’re being consistent and want to truly give our users what we set out to give them. Please try to understand this if you see your theme is not in there.
Themers can submit or in the case above, re-submit their themes when they feel they’ve met our criteria and we’re MORE than happy to check it out! If the theme does meet our requirements, we’ll add them ASAP to DU Certified. You can contact Edwin Rivera, Randall Rushing or myself via our G+ community
Here’s our criteria for DU Certified :
– Settings to include Dirty Tweaks must be fully themed.
– No FC’s or any kind caused by your theme, we’ve talked about this above.
– No black text on black background, white text on white background, etc
– The quick settings area must be fully themed. This include all tiles, heads up button, task manager, etc
– SmartBar either needs to be left alone or themed. If you have the basic ‘back/home/recents’ themed then you will have to theme the rest. This looks tacky if you do 3 and the rest are stock.
– Keep your theme updated. Once you get certified, that shouldn’t be the end of it. Please continue!
So as some of you might of noticed with either gerrit activity or picked up on the hints, tomorrow we will release 10.3 along with the new DU Certified. Official and weeklies will also change some.
The week of the official build, weeklies will not be compiled. After some discussion, we came to agreement that it doesn’t make sense to do so. We’re just wasting resources because essentially they were both the same, just different names.
If you’re on a test build or another ROM, we advice you do a FULL WIPE for a great user experience. If you fail to so, please stay away from JIRA and reporting any issues in our XDA threads. If you’re on a weekly or official build, you can dirty flash but please be advice that if you run into an issue, we will ask you to do a FULL WIPE and make an attempt at duplicate said bug prior to reporting it.
I want to go ahead and thank all translators, themers, contributors and all who support us! Thank you 🙂
When we first started Dirty Unicorns nearly 4 years ago, we didn’t have to worry about translations. Our users back then were mainly English speaking and we had no complaints, life was simple.
A lot has changed since and today we have all types of users. From French to German to Polish, we have them all. The DU team has also changed and nearly 30 percent of the team speaks English as a second language.
That said, we have brought back Crowdin and is ready for all translators that are willing to help out 🙂
We’ve enjoyed it and in DU fashion learned a thing or two from it. It has truly been fun reading all the comments on XDA, Google+, Telegram and even made it’s way to Twitter and the famous Reddit. We even managed to get an article about us leaving to work for some Russian company in the middle of no where.
Sorry Jeff, hope we didn’t get you in trouble but you know, we had to get our laughs hahaha
Several close friends also got reeled in and we enjoyed every second of it hahaha Whether they like to admit it or not, they did 🙂
People like Nate Benis of Pure Nexus, Brian Koluch (who the fuck is bdogg) of Resurrection Remix, our friends over at Evervolv and even the great Andrew Dodd of Omni ROM were quick to dismiss our prank because it really had some holes in it but after talking to them in hangouts, they too were a believer. Truly fun times! haha
What we did learn from our prank was that a lot of people had our back! Many users, themers and developers from around the community were quick to get in touch with us and offer help whether with hosting, maintaining devices or just give us advice as some had gone through similar situations. Some people we knew of and some were new faces but all were ready to do what they had to do to get us back on track! While it was fun to play this prank, it was also heart warming to know that people genuinely cared and wanted to help. To those people we would like to say THANK YOU and we are very honor to call you our friends!
Other side of the prank, we had some folks that saw this as a chance to kick us while we were supposedly down. They were too caught up in the moment to see that it was a joke and were gloating on social media, saying things that were clearly BS and claiming that it was “karma” that did this. We just laughed at that because it really takes some real bitchassness (Josh Chasky’s word) to say things when someone is down and not do it when we’re in the position to do something.
To those people we say FUCKKKKKKKKKKKKKK YOOOOOOOOUUUUUUU!!
When I started this project nearly 4 years ago it was not my intention to ever make any money off it. This is why from day 1 I had a policy to never accept nor ask for donations. This has work well and all members, former and active have always respected this policy.
That said, bills have to be paid. Student loans have to be paid and money does not grow on trees.
So it kills me to say that today we are losing several vital members of the team.
Randall Rushing, Anders Nielsen, Andrzej Ressel, Susan McCombs and James Taylor have all accepted offers to work on a new project for Russian based smartphone manufacturer Highscreen.
We all are very happy for them and wish them the absolute best in their new opportunities.
So what does this mean for us?
You will see things start to slow down as far as bug fixes until we can get some new talent added to the team. Some devices will be dropped as of right now to include the Angler and M8. Gerrit, JIRA, this website and many things that we’ve taken for some what granted will soon be shut down and we will have to regroup and find alternatives.
For right now, we are looking into using Android File Host or maybe Google Drive.
Last week we released our first builds based off Marshmallow and it felt pretty damn good! Not so much the hype or the onslaught of n00bs that followed but the fact that we can now focus on bigger things. Yes, this is not a one and done.
Those that have been here before the wagon got full, know that after every major release we kick off weeklies. Weeklies in the past were released every Monday unless otherwise posted. This time around, things will change a bit and they will be released on Friday’s.
Because it makes sense. End of the work week, you have more time to throw a few back, flash some builds and test features while providing feedback to us.
Be adviced that weeklies are not to be considered stable. Although 9/10 times they’re as stable as the official build, they may include code from time to time that does not make it into the next release. This is all part of the development process.
– Only devices with OFFICIAL XDA threads will receive weeklies
– DO NOT ask for us to include unofficial devices to the weeklies
You can download weeklies one of two ways, via our updater that all OFFICIAL builds include or via our download site.
If coming from the v10.0 release, you can dirty flash it on top of it by just wiping cache afterwards. Be advice that if you do experience any bugs, is recommended that you do a FULL WIPE to rule out any issues that may come from dirty flashing. Please provide logcats and useful information when reporting issues.
If coming from anything else, is recommended that you do a FULL WIPE. This means wiping everything but internal storage. If you’re coming from a ROM that includes Layers, is also recommended that you delete the ‘overlays’ folder. Please refer to the FAQ in our G+ community of any official XDA thread.
Android M was released back in October; and we’ve been busy hacking away at things; writing new features; and trying to fix what El Google has screwed up. It has truly been an exciting couple of months and we’re finally ready to release our first Marshmallow build to the public.
Although it seems like every ROM under the sun has released 100 builds before us; we wanted to make sure we got it right. We didn’t want the “ME FIRST” award. With the help of many testers in the G+ community; I think we can say that we’ve done a great job!
With this release, we’ve also started to flex our muscles a bit and show the community what we really have. We’ve adopted an approach of not just adding features just to add it, but also moving things forward. We look at feature XYZ and see what we can do with it; and if we are able to make it better. This has been the best thing to happen to DU!
We’ve also written some very unique features and we want to talk about them while we have your attention.
“Fling”, who doesn’t love “Fling”?
“Fling” is a gesture based navigation feature; like nothing else you’ve seen in Android. You are able to assign gestures to everything. From an application (chrome, youtube, angry birds, etc); to an app’s activity; to contacts; a settings shortcut; or to many custom actions that we have provided.
These custom actions include ‘back, bluetooth, expanded desktop, force close an app (aka kill-all), Google Now on Tap, home, last app, menu, notification panel, overview (aka recents), power menu, screen record, screenshot, setting panel, turn off screen, voice search, wifi or no action at all.
BUT WAIT, there’s more!! The fun doesn’t stop there as you can assign short swipes, long swipes, single tap, double tap and longpress in either left or right direction.
You don’t like the “Fling” logo? You can get rid of the “Fling” logo and still have the same functionality!
If you decide to leave the “Fling” logo in place, by default the animation is a circlular motion. If you decide this is not for you; the logo can be turned off. You are also able to use the color changer to pick the default color.
The trail that you see when you start to use “Fling” can also be customized. You can turn the trail off and still keep it’s functionality. Even the color of the trail can be changed to match your favorite themes.
“SmartBar”, in case “Fling” didn’t already win you over!
“SmartBar” is a one of kind navigation feature. You can assign up to 7 targets on phones and up to 10 on tablets. By default, “SmartBar” looks and feels the same as the AOSP navigation bar. If you don’t add targets or change any of the settings, you won’t notice any difference.
With “SmartBar”, you can assign targets in the same way as “Fling”. Whether that’s with a application, or a preset custom action. You can also use your favorite icon packs to change the default icon on any target. This is all done without touching the CM theme engine; for those that want to keep the stock look.
Like “Fling”, you can also assign single tap, double tap, and longpress actions to your targets. This allows for true customization. Where your home button may take you back to your homescreen, but double tapping it takes you to Google+, or turns on the flashlight. Long pressing could take you to the last app, or turn off your screen; without the need to use the power button. The possibilities are endless!
BUT WAIT, there’s more!! You can change the touch animation on your targets. You can set them to have a spring-like action, or if that’s not your cup of tea; you can go back to the stock animation. Changing the layout of context buttons and keyboard arrows is also included in “SmartBar”!
With both “SmartBar” and “Fling” the bar size can be adjusted and still use “Pulse”!
“Pulse”, YEAH….we didn’t just bring sexy back, we made it sexier!
While playing music with “Pulse” enabled; you get a one of a kind; brilliant; bar-style equalizer. You are able to toggle “Pulse” on and off; as it’s not everyone’s cup of tea. “Pulse” can be used with the default setting where it looks like a lava lamp. The “Pulse” color is even customiziable.
“Pulse” will not render visualizations under certain circumstances. This is a limitation of the Android API / media stack. It is not a bug. I will explain a bit further.
Android uses an output “sink” called remote submix. In submix; audio may pass through for operations like downsampling (a2dp compliance etc), pre and post processing (fx) and other things including passing track data through the visualizer library. Most output destinations like bluetooth, headphones, music, and Chromecast; Android intercepts the audio track automatically and routes it through remote submix. The visualizer library gets the track data and we have “Pulse”. Device speaker output does not require remote submix operations. Often in cases where the track is streamed with DRM protection; remote submix is bypassed; and “Pulse” will not work. I’m exploring options to force remote submix on speaker output. Such a task will be rather difficult and complicated.
Besides these three landmark features; we have also added in an awesome “Themes Tile”. The “Themes Tile” does not work as just a shortcut to the themes engine; it allows the user to change themes on the fly.
“Long Pressing” the “Themes Tile” changes the theme on a per-app basics. Some of you have seen this similar feature on Cyanogen OS, but previously you had to use the prebuilt apk taken from that ROM. While this proved to be an OK workaround; it took away the default theme engine, and at times, was hit or miss.
Our “Themes Tile” is functional and is open sourced. It will continue to get better via the help of the community!
We could be here all day explaining every feature we’ve written, or implemented from other ROMs, but I’ll end with a short list of the features we think are important to you 🙂
– CAF Task Manager
– Double tap to sleep (statusbar/lockscreen)
– Selinux Switch
– LCD Density Changer
– Mid screen shortcuts
– Bottom L/R shortcuts
– Lockscreen wallpaper changer
– Lockscreen notifications customization
– Weather options (lockscreen/extended statusbar)
– Lockscreen colors/fonts customization
– Statusbar customization (battery, clock, traffic indicator, etc)
– Quick settings customization
– App circle bar
– Geature Anywhere
– OmniSwitch (standalone app / use for recents)
– Slim Recents and AOSP recents customization
– Heads up customization
– Animations (system/list and toast)
– Expanded Desktop customization
– Power Menu options
– Built-in system app remover
– Wakelock blocker
– Built-in ad blocker
– CM Theme Engine
– Dashboard customization (columns, dividers, title view)
On top of this; we’ve added support for some new devices and dropped a few:
– HTC Droid DNA (dlx)
– Nexus 6P (angler)
– Nexus 5X (bullhead)
– Moto X Pure (clark)
– Nvidia Shield K1 (shield tablet)
– Oppo R7 Plus
– HTC EVO LTE (jewel)
– Samsung Galaxy Note 3 (HLTE)
– Sony Xperia Z (yuga)
Official builds will start to roll shortly. Please have patience and try to keep from asking for ETA’s.
ROM developers, source for SmartBar/Fling/Pulse will be fully release within 30 days 🙂
Keep an eye at our github for updates https://github.com/DirtyUnicorns for the #Kangbang