Week in review – 16 March 2018

Short changelog:

– Made necessary changes to ship User builds
– Fixed changelog not loading after SSL certification
– Fixed smartbar media arrows not showing sometimes
– Fixed potential Smartbar FC for buttons custom application
– Fixed Pulse disappearing sometimes after skipping tracks
– Fixed Miracast on all our devices
– Slim Recents fixes
– Expanded Desktop fixes
– Fruity Pebbles fixes/changes (built-in themes)
– Added pinch-in gesture on tasks to Clear All to AOSP recents
– Added prompt for location permission in Gallery2
– Added back the ticker scroll
– Added QS pulldown with one swipe on FP sensor for devices that support it
– Added roaming indicator switch
– Added a one time QS dialog for the theme tile
– Added QS tile titles visibility mod
– Added translations
– Check gerrit/github for a full changelog and/or device specific changes.

Important notes:

– User builds

All our supported devices with the exception of the Nexus 6 (shamu) and HP touchpad (tenderloin) will now ship user builds instead of userdebug.

The main difference between user and userdebug is that userdebug builds are intended for debugging purposes, where user builds included none are better suited for production. For more information, feel free to read this and also this.

This change also removes the SU implementation found in AOSP and will ensure those devices that ship user builds will pass safety net without the use of Magisk or any tricks.

Is worth to mention that some of our users that compile their own personal builds have reported that they were able to pass safety net prior to this change while running userdebug builds and without the use of magisk. While we don’t know exactly how this was achieved, we also found that this was not the case across all our devices.

– Font manager

Our font manager is still being worked on. A lot of progress has been made by Randall Rushing. We hope to have it set and ready for next week but there are no guarantees.

– Crowdin

Crowdin will be set up this week and hope to have it ready for more translators to contribute. Keep an eye out for an announcement if you would like to contribute in translating.

– Reminders

Weeklies and official builds are signed with private keys. This means that if you’re on the official build, you can dirty flash this weekly. If you’re on anything other than that and want to use this weekly you MUST perform a full wipe in recovery. If you decide to disregard this and flash this weekly or the official build on top of anything, you will not be able to boot. Have fun looking at a black screen :p

If you run into any issues, please use JIRA to report your issues.


As always, we want to remember where we came from and who got us where we’re at! We wouldn’t be where we’re at without the help and support of all our contributors, past and present! Every developer, designer, translator and supporter, thank you for everything you’ve done for our project!


Android O planning

Android O will be here before we know it! The hype train has been put in high gear and it seems like that’s all everyone is talking about these days! Part of this is because there’s not a whole lot to really do Android wise. This time of year is always like this. People go into maintenance mode and just fix bugs, tweak little things here and there and that’s pretty much what you’ve seen out of ROMs lately. The other part is the unknown. Most people just don’t know what to expect with a new release. This may be because they’re new to the Android custom ROM scene or they just don’t want to go on assumptions.

Read More

Tell me how you really feel

So about a month ago we (Josh Chasky and I) wanted to do something for April fools day! We started to think and we came up with a decent plan.

Given that Shreesha Murthy is a popular maintainer with a huge following for his work on devices like the OnePlus 2 and Oneplus 3/3T, we decided to use him as the target for our prank. We figured more people falling for this, the better!

Read More

Android O and some plans

Android O was announced not long ago and it’ll be here before we know it. They already got a developer preview and is scheduled for late August or early September. We’re ready and have a lot of neat ideas to expand certain features and create a few new ones. We won’t jump the gun on our plans for features just yet because until we get a change to evaluate the source, is just hot air. Google is Google and what that means these days is that Google might throw a curve ball at us and plans might change.

Read More

Options are good

About 4 months ago we talked about SuperSU and the conspiracy that had taken a life of its own in the community. While we still believe that there’s NOTHING to worry about with SuperSU, we have gone ahead and changed our mind about one thing. We will no longer ship with root. We can’t stress enough how this change has nothing to do with SuperSU. There’s been no evidence of wrong doing when it comes to Chainfire and SuperSU, this is a fact.

Read More

Theme decision 2016

It was almost a month ago that we made a post telling you that we were still undecided on which theme engine/outlet we would include in DU and that we would wait and see. A lot of people said what they had to say but we wanted to discuss it as a team, take it slow and just look at the code because really that’s what makes it go round. We wanted to really just think about which one would be a better fit for us not just for this version of Android but for future versions. A project of this size can’t just think 1-2 steps ahead, we need to think 5-10 steps ahead and not really jump but be ready to jump.

Read More

SuperSU, the fear and the plan

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.

Read More