Author: Alex Cruz

Weeklies have started and some news…

For those not familiar with Weeklies, these are incremental builds that are posted between official builds. These builds are meant to be as solid as the official but can contain work in progress mods/tweaks from time to time. These builds are built off what’s already merged to Github so what’s in them is tested by the team and other contributors.

Weeklies are signed with the same keys that Official builds are signed with, release keys. If you’re wanting to try out the weeklies and are not on an Official build, you will have to do a full wipe before trying them. If you are already on the Official build, you may dirty flash them with no problems.

If you run into any issues, as always we recommend you visit our JIRA and report these issues there. If you’re wanting to discuss issues with other users or even the maintainer before reporting it to JIRA, you may head over to our Discord server and do so there.

So what’s the news?

A lot of our developers to include myself have been doing this custom ROM thing for a while now. Some of us as early as the ICS days. The leadership in DU has decided that it time to call it quits. We have been doing this for a while now and have nothing to prove. Our Android P builds are as good as they’re going to be, as you can tell and we figured we end things on a high note. Things are going very well but is time to move on. At the end of Android P, the project you’ve all come to love or maybe hate lol will dissolve. Our developers are free to do what they want to do but I suspect most will continue to kick ass and take names elsewhere for other projects.

For myself, I will pursue making a name for myself over on Twitch. Is something that I’ve wanted to do for a while now but just never had a whole lot of time or even space on my computer to do so. With DU in the rear view mirror, I believe I can give it my all. If nothing else, I can have some fun with that πŸ™‚

Our Github organization will stay up as a reference for any developers that would like to carry on a similar project and/or port any of our work forward to future versions. However, our Discord server, Twitter account and other accounts that we used to communicate with our base will be shut down at the end of P.

We like to take this opportunity to thank all our contributors throughout the years. Is definitely been a good experience and we wouldn’t have done it any other way because we did it our way! Thank you again!

#StayDirty

DU13 is here!

Today is the day! After a few months since the release of Android P in AOSP, we’re finally ready to release our first official build. In doing so, we’re starting weeklies as well.

The list of DU 13 supported devices include

Pixel XL (Marlin)
Pixel 2XL (Taimen)
Pixel 3/3XL (Blueline/Crosshatch)
Pixel C (Dragon)
Nexus 6 (Shamu)
OnePlus 3/3T (Fruitcake)
OnePlus 5/5T (Cheeseburger/Dumpling)
Moto G5 Plus (Potter)

Some devices (Nash, OP6 and OP6T) did not make the cut for DU13 but will hopefully join the line up for weeklies next month. This was mainly due to device specific issues that have yet to be worked out on those devices. Hopefully you can understand.

For those unaware of how weeklies work, let me explain. First of all, weeklies are done once a week (Thanks captain obvious) on Friday’s. This is with just 1 expectation. The week of a security update there will be no weekly but another official build. This means that if a security update is released in AOSP on a Monday, that following Friday an official build will be released since of a weekly.

Also, weeklies and official builds are signed with private keys. This means that you can notΒ dirty flash these builds on top of anything else but builds signed with the same keys. So today if you want to try out the official build and you’re using an RC or an unofficial build you compiled yourself, you will have to do a full wipe in TWRP. That said, if you stay on this official build and next week you want to try the weekly, you can go ahead and dirty flash it with no problems or a full wipe.

If you run into any issues, please report them using JIRA. If you’re new to JIRA, simply create an account and follow the instructions on the site to create a bug report. The same applies if you would like to submit a feature request.

//jira.dirtyunicorns.com

Last but not least, if you’re an unofficial builder and would like to join our team as a maintainer, simply follow the instructions in our ‘Notices’ Github repo. Developers that don’t want to maintain a device but would like to contribute as part of the DU team are also welcomed to apply.

//github.com/DirtyUnicorns/Notices

We would like to thank all our contributors, past and present, who has helped this project to what it is today! Thank you!


#StayDirty

Join us…

Starting today we are accepting applications for new maintainers and developers. Before I explain any details on how to go about applying for either position, let me explain the differences (at least for us) for those unaware of the two.

Maintainer
A maintainer is a developer who maintains a device. A developer who takes on the day to day responsibilities of ensuring that the device they’re maintaining is not only tested against the latest changes in source but that the device is living up to our standards of stability, performance and reliability. They are responsible for the upkeep of their device and fixing any device related issues that may or may not occur over time.

Developer
A developer is someone that takes on the day to day responsibilities of the development process. Whether that’s testing commits, writing new features, adding on to existing features or just fixing any issues that may or may not occur, the developer is responsible for these things.

To apply for either position, just check our Notices GitHub repo.

There you’ll see a list of requirements for both positions. Once you meet those requirements, contact the recruiting committee and they’ll interview you and forward it on to Josh Chasky for a final decision.

DO NOT contact the recruiting committee unless you have a question about one of the requirements or you have met these requirements.

//github.com/DirtyUnicorns/Notices

Good luck and #StayDirty

RC builds today and what you need to know

RC builds will be released today at different intervals by our maintainers. Here’s what you need to know before you flash any of these builds on your devices.
1. These builds are not to be considered our official build.
There’s still a lot of work ahead of us before we can go ahead and release our official builds. These builds are merely for us to gather feedback on where we’re at right now. Our hopes are that enough feedback is given to us properly that we can improve our builds.
2. Weeklies will not start next week.
Again, these builds are not to be considered our official build. Weeklies usually follow our official build. The official build has not been posted and so weeklies will not be posted any time soon.
3. All builds will be posted in our Discord server.
If you have any issues, head into the respective channel and report your issue there. Be prepared to provide logs if you do report any issues. If you’re wanting to make a feature request, you may also do so via Discord. Just keep in mind that we will not add in everything and anything. Just because ABC and XYZ added it or we had a feature in the past, does not mean that we’re in any way obligated to add it.
4. Unofficial devices can be posted starting today.
If you’re an unofficial builder, we welcome you to post your build in our Discord server to make it easier for our users to find it. We also want to ask that you not give into the need to ask for donations for our work. We don’t ask for donations and never will, you shouldn’t either. Any questions about unofficial builds becoming official can be answered by reviewing our Notices repo on Github.

5. Thanks for the support!
As always, we want to remember where we came from and the folks that 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!


#StayDirty

DU 12.5 is here!

Full changelog:

– Merged in latest tag for AOSP security updates
– Fix NullPointerException in BatteryUtils
– Fix NPE in AutoSyncWorkDataPreferenceController
– Fix the format of wifi_carrier_content string
– Fix NPE crash in AppInfoBase
– Fix for OOM caused by looper leak in settings
– Fix the crash caused by show DialogFragment after it state already saved
– Fix for NPE caused by missing argument in setResult for ChooseLockGeneric
– Fix for battery item summary that disappears
– Fix can’t enter bluetooth device preference under settings
– Fix dev settings crash when no OEM unlock service
– Fix settings force close
– Fix ripple effect in Dirty Tweaks preferences
– Fix issue with scrcpy (mirroring desktop app) and adb reverse
– Fix FC with mediaprovider in cases with MTP and β€˜optimizing’ download provider
– Launcher3 fixes from AOSP and β€˜Rootless pixel launcher’
– Ensure power menu aligns properly per stock behavior
– Ensure we load the section corresponding to what build the user is on in the updater
– Ensure we get the correct fingerprint position during setup
– Avoid NullPointerException when updating preference intents
– Expand on to swipe down gesture in Launcher3
– Expose the main style in MusicFX for themers
– Remove force show system bars in splitscreen mode to avoid issues with expanded desktop
– Change deskclock analog widget background with system theme
– Added haptic feedback to double tap gestures in Launcher3
– Added ripple effect for brightness slider icons
– Added some haptic and visual feedback to download button in the updater
– Added new devices to changelog filter
– Added back Demo mode because designers wanted it
– Added translations
– Check gerrit/github for device specific changes.

Important notes:

– Last Oreo release

As we said last week, this will be the last Oreo release for us. With the release of Android P and the source being pushed on the same day, we have started to work on that. Now this isn’t to say that you won’t get any more builds from us. We are planning to push out monthly security updates just as long as Google does their part. We will not back port any security updates.
For more information on this, we recommend you read this here.

– In before we shut down..

The Nexus 7 (Flo) is making an appearance on the list of supported devices this time around. Too bad is our final Oreo release but better late than never, right?

– Social

If you folks would like to stay up-to-date with what’s going on with this project or just want to share some stories, screenshots or shoot the shit, I’ve provided some links below!
Be advised that these channels/groups for which we communicate on are not support channels/groups.
If you have an issue, we highly recommend you still use JIRA. Not only because JIRA is awesome but because is the quickest way to get eyes on your issue(s).
Twitter
Twitter build status bot
Google plus
Telegram channel
Telegram group (not for support)

– Reminders

Weeklies and official builds are signed with private keys. This means that if you’re on any official/weekly build or just last week’s weekly, you can dirty flash this official build. If you’re on anything other than that and want to use this build you MUST perform a full wipe in recovery. If you decide to disregard this and flash this build or a weekly 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.
//jira.dirtyunicorns.com

Thanks:

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!


#StayDirty

Pumpkin pie is the best!

In case you don’t know yet, Android P was released about 30 minutes ago. The source is slowly making its way to AOSP. We originally thought it was going to be on the 20th of this month like all the blogs were predicting but obviously we’re happy to get it early too. So now that Android P is out, we want to outline some things that will take place in the coming days and weeks.
DU 12.5 is still being released this Friday
This release will probably be the final release for Oreo. We will continue to do security updates for Oreo but nothing else.
Following the release of DU 12.5, we will start working on Android P
Last week we had our end of cycle meeting and it was very productive. Aside from just hanging out and shooting the shit, we got to discussed Android P as well as issues that we’ve faced with Oreo and things that we would like to do come P. I think we have a really good game plan and we hope to put it to action very soon. Obviously we were not expecting the release this early but we’ll manage.
JIRA will be set to private after the release of 12.5
We have no plans on working on Oreo beyond just merging in AOSP security updates and kernel upstream moving forward. We have a lot of work ahead of us with Android P so we hope you understand.
P Wen Sur?
We don’t have an ETA for anyone, even for people that could get one if we had one. Our focus is just to get it right the first time around. We would like to avoid from making the same mistakes we’ve made and get it right. Just know that when we do release our first set of builds for P, you can expect the same level of quality and attention to detail that you’ve come to expect from us.
AOSP security updates
As said above, these will continue on beyond DU 12.5 but just as long as Google still pushes them out for 8.1. We will not back port security updates.
I think that’s all we have for now. If there’s anything else, we’ll post it over our official channels (Telegram, Twitter and Google+)
#StayDirty

Week in review – 3 August 2018

Short changelog:

– Ensure power menu aligns properly per stock behavior
– Added new devices to changelog filter
– Added back Demo mode because designers wanted it
– Added translations
– Check gerrit/github for a full changelog and/or device specific changes.

Important notes:

– Is that time of year

As you guys can notice by the changelog, there’s not a whole lot going on lately. Is that time of year where we’re just fixing small things, merging in security updates only, tweaking this and tweaking that because we’re all just sitting around waiting for the next version of Android to drop. The rumors have it set for the end of the month, so we’ll see what happens. Later on this week, we’ll make a separate post outlining out plans for Android P and what happens to weeklies, security updates and our project in general once Android P drops to AOSP.

– New maintainers

If you’re building DU for an unofficial device and would like to make it official, contact us! Check out the link below for more information about the requirements for both you and your device.

We will also like to add that if you’re wanting to become a maintainer and are serious, show it. Start reviewing commits in gerrit. Submit your support patches for your device(s) via gerrit. Push out some builds via our G+ community. Make yourself known.
//github.com/DirtyUnicorns/Notices

– Reminders

Weeklies and official builds are signed with private keys. This means that if you’re on last’s week’s build or on any official/weekly build, you can dirty flash this weekly. Weeklies and Official builds can be dirty flashed on top of each other. 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 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.
//jira.dirtyunicorns.com

Thanks:

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!

#StayDirty

Week in review – 27 July 2018

Short changelog:

– Fix issue with scrcpy (mirroring desktop app) and adb reverse
– Fix FC with mediaprovider in cases with MTP and ‘optimizing’ download provider
– Launcher3 fixes from AOSP and ‘Rootless pixel launcher’
– Remove force show system bars in splitscreen mode to avoid issues with expanded desktop
– Change deskclock analog widget background with system theme
– Added some haptic and visual feedback to download button in the updater
– Added translations
– Check gerrit/github for a full changelog and/or device specific changes.

Important notes:

– New maintainers

If you’re building DU for an unofficial device and would like to make it official, contact us! Check out the link below for more information about the requirements for both you and your device.

We will also like to add that if you’re wanting to become a maintainer and are serious, show it. Start reviewing commits in gerrit. Submit your support patches for your device(s) via gerrit. Push out some builds via our G+ community. Make yourself known.
//github.com/DirtyUnicorns/Notices

– Reminders

Weeklies and official builds are signed with private keys. This means that if you’re on last’s week’s build or on any official/weekly build, you can dirty flash this weekly. Weeklies and Official builds can be dirty flashed on top of each other. 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 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.
//jira.dirtyunicorns.com

Thanks:

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!

#StayDirty

Week in review – 20 July 2018

Short changelog:

– Fix NullPointerException in BatteryUtils
– Fix NPE in AutoSyncWorkDataPreferenceController
– Fix the format of wifi_carrier_content string
– Fix NPE crash in AppInfoBase
– Fix for OOM caused by looper leak in settings
– Fix the crash caused by show DialogFragment after it state already saved
– Fix for NPE caused by missing argument in setResult for ChooseLockGeneric
– Fix for battery item summary that disappears
– Fix can’t enter bluetooth device preference under settings
– Fix dev settings crash when no OEM unlock service
– Fix settings force close
– Fix ripple effect in Dirty Tweaks preferences
– Avoid NullPointerException when updating preference intents
– Expand on to swipe down gesture in Launcher3
– Expose the main style in MusicFX for themers
– Added haptic feedback to double tap gestures in Launcher3
– Added ripple effect for brightness slider icons
– Added translations
– Check gerrit/github for a full changelog and/or device specific changes.

Important notes:

– Nexus 7 (flo)

As many of you saw on our social media accounts, the Nexus 7 (flo) has been added to our lineup. Like most new devices, it will have to wait before it sees a weekly because it needs to get an official build first. This will happen on August 10th if everything goes as planned.

– New maintainers

If you’re building DU for an unofficial device and would like to make it official, contact us! Check out the link below for more information about the requirements for both you and your device.

We will also like to add that if you’re wanting to become a maintainer and are serious, show it. Start reviewing commits in gerrit. Submit your support patches for your device(s) via gerrit. Push out some builds via our G+ community. Make yourself known.
//github.com/DirtyUnicorns/Notices

– Reminders

Weeklies and official builds are signed with private keys. This means that if you’re on last’s week’s build or on any official/weekly build, you can dirty flash this weekly. Weeklies and Official builds can be dirty flashed on top of each other. 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 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.
//jira.dirtyunicorns.com

Thanks:

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!

#StayDirty

DU 12.4 is here!

Full changelog:

– Merged in latest tag for AOSP security updates
– Fix DUI settings custom action dialog lag
– Fix bootanimation build warnings / size
– Fix memory leak of page “Languages & input”
– Fix crash issue when user uses multi-window mode on WifiCallingSettings
– Fix NPE in SettingsPreferenceFragment
– Fix broadcast receiver leak issue
– Fix window transformation related issue
– Fix Phone info FC related to Eab provisioned on some devices
– Fix CustomTile NPE in handleRefreshState
– Fix tabs in the udpater with no files showing previous fragment
– Fix left clock glitch on landscape and cleanup code
– Fix ContentService JNI leaks
– Fix slow-app ANR dumping
– Fix socket leaks in various android.net.Network methods
– Fix doFadingAnimationLocked in sanitized builds
– General theme fixes
– Media Provider fixes
– Analog deskclock widget changes
– Improve lockscreen ambient analog clock design
– Improve compatibility with LMT and other apps that don’t preload recents
– Ensure that locked recents apps are respected
– Don’t update if HeadsUp is disabled
– Hide freeform task header icon
– Lock rotation on SetupWizard to avoid issues
– Make scramble PIN layout Multi-User friendly
– Split calendar click action from clock in qs footer
– Remove janky fonts
– RTL changes to doze/gesture packages
– Ensure our AOSP security dialog respects RTL
– Ensure bluetooth icon is transparent when disconnected
– Include WallpaperPicker for all builds
– Add special captive portal servers for chinese
– Add Square style battery
– Add ability to allow to add custom clocks as analog clock overlays
– Add ability to keep pressing on SmartBar ime arrows to move kb cursor
– Add bigger recents icons, dynamic mediaplaying and alarm clock infos
– Add ability to allow single tap on app icon to show app info overlay
– Add DU and deep night clock
– Add dt2sleep to Launcher 3
– Add flashlight gesture & group it with the sleep one to Launcher3
– Add onLongClick functions to calendar/clock in qs footer
– Add ripple effect to the power menu items
– Add ripple effect for alarm and date
– Add option to show battery percentage when charging
– Add permission whitelist for EmergencyInfo app
– Allow to kill any app from recents panel in a safe way
– Allow details view for Cellular tile when tile title is disabled
– Allow for a more robust way to reset DUI options
– Added translations
– Check gerrit/github for device specific changes.

Important notes:

– Marlin and Shamu

A couple of weeks ago the Marlin joined the lineup. Many were happy but were curious why no builds were released. The answer is simple! For all new devices, we wait until the device has got an official build before feeding it weeklies. We don’t get in the habit of just adding in a device mid month, so we have to wait. Once the device gets the official build, it gets added on to the weeklies rotation. This is what’s happening today! The Marlin is now part of the crew officially and will get weeklies from here on out.
The Shamu has been part of our lineup for a very very long time and unfortunately is not doing so well. Relax folks! This isn’t the ‘is not you, is me’ speech. We’re not dropping the Shamu, at least not this cycle! There are just some major issues that we feel like should get addressed first before releasing 12.4 out for this device. Our Shamu maintainer is hard at work on it and as soon as the issues are resolved, it will be compiled and pushed out to you folks! Please have some patience πŸ™‚

– New maintainers

If you’re building DU for an unofficial device and would like to make it official, contact us! Check out the link below for more information about the requirements for both you and your device.

We will also like to add that if you’re wanting to become a maintainer and are serious, show it. Start reviewing commits in gerrit. Submit your support patches for your device(s) via gerrit. Push out some builds via our G+ community. Make yourself known.

– Social

If you folks would like to stay up-to-date with what’s going on with this project or just want to share some stories, screenshots or shoot the shit, I’ve provided some links below!
Be advised that these channels/groups for which we communicate on are not support channels/groups.
If you have an issue, we highly recommend you still use JIRA. Not only because JIRA is awesome but because is the quickest way to get eyes on your issue(s).
Twitter
Twitter build status bot
Google plus
Telegram channel
Telegram group (not for support)

– Reminders

Weeklies and official builds are signed with private keys. This means that if you’re on any official/weekly build or just last week’s weekly, you can dirty flash this official build. If you’re on anything other than that and want to use this build you MUST perform a full wipe in recovery. If you decide to disregard this and flash this build or a weekly 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.
//jira.dirtyunicorns.com

Thanks:

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!


#StayDirty