BlissRoms/Bliss OS 14 now available

Hello everyone! Our latest BlissRoms/Bliss OS release based on Android 11, BlissRoms/Bliss OS 14, is now available to the general public.

Here is the list of currently supported devices for BlissRoms:

  • Samsung Galaxy S9 (starlte)
  • Samsung Galaxy S9+ (star2lte)
  • Samsung Galaxy Note 9 (crownlte)
  • Redmi Note 7 Pro (violet)
  • Realme XT (RMX1921)
  • OnePlus 3/3T (oneplus3)
  • Redmi Note 4 (mido)
  • OnePlus 6 (enchilada)
  • Redmi Note 5 (India) / Redmi 5 Plus (Global) (vince)

We also support x86/x86_64 devices over at Bliss OS.

Support for more devices is coming in the future, so stay tuned!

Maintainer applications now open!

Note: this post is for developers and maintainers looking to join Team Bliss. Users can disregard this post.

We’re looking for potential maintainers for our next version of BlissRoms, BlissRoms 14!

For this year, we are tightening up our maintainer application process and imposing certain requirements for new maintainers. All new maintainers must meet the following criteria to be accepted, barring any special circumstances. If you do not meet the requirements but believe you have a unique reason to be accepted, please reach out to the administrators at Team Bliss.

  1. You need to understand English. Many of our internal documentation and tools are written in English. In the past we’ve had some unfortunate instances where maintainers did not understand our directives and caused problems. Therefore, all maintainers must have a reasonable comprehension of English in order to be accepted.
  2. Your device must be buildable. Please do not apply in the hopes of getting your device maintained by us. That’s not what this program is for.
  3. Build artifacts must be flashable as-is, without any modification. Unzipping and swapping out the kernel image, editing system files to force certain features to work, etc., are not allowed. Build artifacts should retain their original file name.
  4. You should be able to use Linux, git, and Gerrit. In addition, you may have to run Python scripts on machines you are building ROMs on to upload your builds.
  5. You must have a commit history on GitHub for at least 1 year.
  6. All device trees (including kernel and vendor) must be public at the time of application, barring any legal problems like DMCA takedown requests. Particularly, if your vendor repository is prone to DMCA takedowns, please reach out to an admin before applying. There are no exceptions for device/kernel trees. Dependencies of the device tree (such as supporting libraries) must be public as well.
  7. You must release builds every two weeks, minimum. Please set aside enough time for maintaining your device.

Also, this year we are dropping the requirement for XDA threads. If you hate interacting with entitled users then you don’t have to! We are also dropping the requirement for support groups on Telegram.

All maintainers and developers of Team Bliss must abide by our ToC. These are really basic conditions, so don’t worry about signing away your soul or anything. These terms mainly deal with common decency to others and regulations like the above to agree to.

If you understand everything above, you may sign up for maintainership here:

Sign ups for Q now closing

Note: this post is for developers and maintainers looking to join Team Bliss. Users can disregard this post.

Hello! As part of our move to Android 11, we will be closing new sign-ups for the Android 10 (Q) BlissRoms maintainer application. We will come back with a new maintainer program for Android 11, so check back here often and we will announce details once we have them!

Updates (September 2020)

Hey everyone! Exciting time of the year. iOS 14 is coming out soon, right?

…I’m kidding! I know you guys are itching for the Android 11 builds, so before we start this month’s worth of announcements, I want to briefly touch on these points below.

When will Android 11 come out?

Android 11 came out a couple of days ago, so obviously we should have a build ready to go for everyone, right?

Well, no. That’s not how this works. The bring-up for Android 11 will be a tedious and long process and it will definitely need help, in the form of people spamming our chats asking for the latest and greatest Android 11 BlissRoms build.

…I’m obviously being sarcastic. Don’t do this. Please!

Asking for ETAs is a big no-no in the Android community, and if you don’t know this already just try going to the forum on XDA-Developers and ask when a custom Android 11 build will be out. You’ll be banned before you can finish asking “ETA?!”

So don’t ask us.

That being said, we have a general timeline set for beta releases in a couple of months, and general releases after that. This is not a concrete timeline and it is subject to change at any time. So please don’t message us and say that we lied when we don’t ship builds in a couple of months. We didn’t. You just didn’t read our announcement fully.

Will my device be supported in Android 11?

Right now, we cannot be sure. So please don’t ask about this, too.

Oh, speaking of device support…

Unofficial builds are unofficial builds

We are happy to see that members of the community are adding support for devices that are not on the official roster, by building unofficial builds. However, we would like to remind you that as much as we are grateful to developers and maintainers helping to create a better ROM community, we cannot endorse these builds in any capacity.

This has particularly become an issue as some unofficial maintainers have begun to launch builds to “compete” with official builds, claiming more functionality and bug fixes. We have even received a number of abuse reports from maintainers, claiming that unofficial maintainers are encouraging users to threaten or harass the official maintainer, sometimes doing it themselves. We never condone this type of behavior and we are really saddened to see how abusive some members of the community have become. Please do not support this behavior yourself and steer clear of builds built by these toxic members of the community.

Another issue with unofficial builds is support. We cannot support devices we don’t own. We just can’t do it. Period. This means whatever bug or snag you run across while running an unofficial build should be forwarded to the unofficial builder, not us. Our public community chat on Telegram is only focused on providing support for official builds, and not unofficial builds. We just don’t have the capacity to do it. Sorry.

If you, as a developer, would like to build official builds, then please consider applying to our maintainer program at Team Bliss. We have instructions on how to do just that on our community chat.

Oh, right. Regarding the community chat…

Spam moderation in community chat

In the past month we’ve seen an uptick in spam, particularly threatening and abusive messages from trolls. We are trying our best to filter them out, however we cannot be available 24/7 and some of these messages may slip through the cracks.

If you notice any bad messages on our community chat, use the /report flag while replying to the offending message to report the message to admins. Also, right click on the message and select “Report Message,” then select the appropriate abuse reason. This will alert the Telegram team to the abuse and they will be able to shut the spammer down.

We appreciate everyone’s patience and are working towards a solution that will preemptively block spammers before they even join. Further details will be announced soon. Thanks!

Updated OTA announcement

We recently overhauled our downloads infrastructure and that caused some of our server API URLs to change. As a result, the old OTA app bundled with old builds of BlissRoms will no longer work.

To check if you have the old OTA app:

  • If your BlissRoms build was released after August 23rd, then no need to worry! You already have the patched OTA app.
  • If your BlissRoms build won’t update even if there is a new version listed online it’s possible your build does not have the patched OTA app.

If you are on a build before August 23rd, please update manually by downloading and flashing a new build .zip. You only need to do this once!

In the future, we are looking at OTA-OTA solutions (sounds weird, right?) so that users do not have to repeat this. We’re sorry for the inconvenience!

Great, so let’s see what changed this month for BlissRoms!

Feature additions

  • The September security patch has been merged! Thanks to @jackeagle for the merge πŸ™‚
  • Added toggle for carrier group visibility
  • Added support for MiSound FX and DiracSound FX
  • Improved lockscreen nav Pulse
  • Added music card in volume panel
  • Improved FOD
  • Added centered R-style notification headers
  • Added ambient screen Pulse
  • Improved SystemUI
  • Added volume plugins
  • Added toggle for gradient background in QS panel
  • Added setting to add minimum auto brightness value
  • Face authentication now automatically blocks when the device is in a pocket
  • Clicking on the QS data usage toggle now opens the data panel
  • Aligned music card vertically to volume panel
  • Added option to force custom Doze brightness
  • Made ringer icon optional in volume panel
  • Asus Longshot is now the default screenshot system!
  • Moved Dark Mode to Blissify Settings
  • Added dependencies to system themes

Bug fixes

  • Fixed “Edit QS panel” icon touch issue
  • Fixed battery QS tile icon not changing. The detail for it was also removed.
  • Fixed “remove lockscreen default shortcuts”

And that’s it for this month! Have a good one and see you in the next update post!

Android-Generic Project Blog – 09.05.20

For the longest time, the Android-x86 world has been plagued with not having a proper recovery toolset packaged with the OS. There have been a few attempts at such a solution in the past, but nothing that was able to coincide with the main Android system and work together. Until Gearlock came into play. It started as a toolkit to do many of the underlying troubleshooting within a basic UI for Phoenix-OS, Remix-OS, etc. And by working together with the lead developer, Axon, we were able to work out a solution for all Android-x86 based projects. Just clone vendor-gearlock into your AOSP based project, run one command, and it’s ready to go. The result is a recovery/tweaking solution that can be run along side system, and also acts as a pre-bootloader for the main OS, so you can in fact choose to boot into Recovery first if you desire.

Here’s a little preview I tweeted, giving a quick glance of some of the options available.

We’ve also been further integrating more and more ROMs into Android-Generic Project, Lineage OS 17.1 being the latest. And boringdroid developer, @utzcoz (Also the newest member of Team Bliss!!!) has also been hard at work in the Android Desktop UI development world, so we’ve been mostly testing all the changes under the hood there with the recent Lineage OS test builds, but have plans on continuing the ROM bringup game soon.

Again, if you are interested in learning more about Android-Generic Project or Android-x86 development in general, be sure to check out our project readme. It has quite a few learning resources as well as plenty of documentation on the process.

And as a gauge of interest, we would like to know how many of you out there would be interested in watching the entire bring up process for a ROM, maybe streamed on Twitch someplace we could interact with those watching, and if so, what ROM would you all like to see added? Let us know in the comments below.

Thanks again

Updates (W3, August 2020)


BlissRoms v12.11 is out! Here are all the new changes this week:

Bug fixes

  • Fixed padding for quick QS brightness slider (top and bottom)
    Earlier, it was too close to the quick QS tiles. This has been fixed.
  • Aligned Omni weather to different clocks properly
  • Fixed QS detail background bug
  • Fixed no ringtone on some devices on first boot
  • Fixed sound settings crashing with some GApps
  • Re-added media picker for ringtone and other sound options
  • Fixed a couple of issues with system themes on settings background
  • Fixed statusbar ticker layout
  • Fixed QS panel header background not being rounded
  • Fixed current formatting on lockscreen for devices that report directly in amperes

Feature additions

  • Added lockscreen clock colors
  • Added option for color picker or accent color
  • Improved persistent settings icon toggle, can now switch between:
    • Disable
    • Show in expanded panel
    • Show always (also in quick QS panel)
  • Added OOS compact VoLTE and VoWiFi icon
  • Added smart pixels tile
  • Added the option to hide pixel animation on navbar
  • Added OnePlus dashboard icons
  • Added option to change navbar handle thickness
  • Added clipboard service
  • Added new look to QS drag handle
  • Added toggle for QS data usage location:
    • QS panel
    • Quick statusbar
  • Added QS header styles:
    • Black
    • Grey
    • Light grey
    • Transparent
    • Accent
  • Brought back option to move QS battery to quick statusbar
  • Added an option for QS clock size:
    • Static (default)
    • Dynamic (same as statusbar clock, can be changed)
  • Moved carrier group to QS panel (inspired by Oxygen OS)
  • Added a vertical layout to QS data usage and clock
  • Added a vertical layout to right side of QS header (battery, logo, and network traffic)
  • Moved statusbar weather image to QS panel, next to date, from quick statusbar
  • Added more QS tile styles
    • JustIcons
    • Hexagon
    • Diamond
    • Star
    • Gear
    • Badge
    • Badge two
  • Added VOOC charging display on lockscreen charging (for supported devices)
  • Added more QS headers:
    • One-piece anime pack
    • One-piece
    • Hunter x Hunter headers
    • Shingeki no Kyojin headers
    • Kimetsu no Yaiba headers
    • My Hero Academia headers
    • Naruto headers
  • Improved clipboard access
  • Improved color picker
  • Added full proc/version information for kernel (enable or disable by tapping)
  • Settings changes
    • Replaced animations with new ones
      Credits to our designer, Roger Truttmann, for the amazing animations!
    • Improved Blissify settings:
      • Decluttered Blissify > QS options
      • Added categories for more items
      • Improved overall UI
      • Added hints and redirections from one setting to another
        (Please suggest ideas if you think there can be more!)

And that’s it for this week’s worth of changes! As always, the developer changelog is available here.

Have a great weekend!

Updates (W1, August 2020)

Welcome to the fast ring of BlissRoms “Updates” posts! This will be the first of many weekly update posts for BlissRoms. If you want to know which week it is, then check the W1, W2 tags in the title!

And with that out of the way, let’s get into this week’s worth of updates!


Bug fixes

  • Launcher fixes:
    • Fixed weird recent transition animation on swiping from navbar
    • Fixed no Google app in app drawer
    • Removed prediction row toggle
    • Fixed quick-switch padding in Recent apps
    • Removed column/row options (enable grid in launcher settings)
    • Fixed icon pack value not showing in settings
    • Fixed many miscellaneous things
  • Fixed QS tint style issues (see example here)
  • Fixed emergency button on power menu on first boot
  • Improved Settings > Privacy UI for GApps users
  • Fixed no permission bar chart for inbuilt GApps devices
  • Improved handling no icon preferences
  • Fixed maintainer name showing unofficial maintainer on other languages
  • Set eleven as default music player
  • Enabled media picker for ringtones
  • Set default Dialer and no in call-UI on first boot
  • Fixed button tint in SetupWizard
  • Disabled Bliss clear primary overlay (use clear system theme)
  • Removed similar packages (like Gallery, Calendar) for inbuilt GApps devices
    (if installing GApps externally, use scripts to override, if they do not override by default)
  • Fixed navigation bar toggle showing for devices with no hardware keys

Feature additions

  • Launcher:
    • Add scroll to remember position in app drawer.
  • The following themes were added:
    • Clear theme (this was requested a lot! Finally added :D)
    • PitchBlack
    • Dark grey
    • Solarised dark
    • Material Ocean
  • Aug Security Patch
  • Added iOS-like clipboard toast notification. See if apps are spying on your clipboard!
  • Added option to show/hide rotation button on navbar and gestural mode
  • Added partial screenshot to HW keys actions and edge swipe action
  • Added backgrounds wallpaper app and Calculator (for non-GApps users)
  • Optimized touch
  • Added support for Boost Framework
  • Added same NFC icon for statusbar as QS tile
  • Added Linotte font
  • Improved Settings > Wi-Fi animation
  • Added a brand new animation for connected devices
  • Added new animation for Settings > System
  • Added battery health options (this needs to be enabled by your maintainer! But please don’t bug them to… they will do it if the device supports it.)
  • Added a new Face Settings video
  • Brought back SettingsIntelligenceGoogle
  • Added default tiles on first boot
  • Added wifi-ext (device-dependent)

Also, thanks to everybody translating on our translation page, we have more languages for everyone to enjoy!

If you would like to see the full developer commit changelog, you can find that here.

And that’s it! If you have any comments or questions, feel free to comment down below!

Updates (July 2020)

This will probably be our last monthly update post! Starting from August we will transition to weekly updates as needs arise.

New lock screen clocks

New, OnePlus-inspired lock screen clocks have been added! Go check out the full-quality video over at our Twitter.

Changes in BlissRoms

The following are new changes in BlissRoms 12.9 and 12.10:

Bug fixes:

  • When the brightness slider position was set to QQS, and when the dark mode tile was toggled, sometimes there would be two brightness sliders. This has been fixed.
  • Fixed force close for some devices (Realme XT) on lock screen charging info.
  • Fixed padding between battery and signal icon
  • Fixed force close for Wi-Fi only devices
  • Fixed external adaptive Settings dashboard icons not theming
  • Fixed no brightness slider and Quick Settings panel when rotated to landscape mode
  • Fixed various network traffic issues
  • Fixed Edge Lighting sometimes showing up on home screen
  • Fixed various screen stabilization problems
  • Updates and fixes to notch-city display cutout mode
  • Fixed OnePlus switch disabled thumb color
  • Fixed accent preset summary and selected value in “Blissify > Themes”
  • Fixed slim recent switch not showing the enabled state properly
  • Fixed status bar header’s buggy layout when the single image option is selected, but there is no image selected yet
  • Fixed showing unlock screen directly bug
  • Fixed network traffic visibility on status bar
  • Improve DT2W (double tap to wake) on AOD (always-on display)
  • Improved FOD (fingerprint-on-display) views
  • Fixes and updates to lockscreen shortcuts

UI changes:

  • Unified options in “Blissify > Statusbar”, everything can be found in one place now
  • Reordered some stuff in “Blissify > QS” depending on their importance

Added features:

  • Add 5 new OnePlus-inspired lockscreen clocks (see above!)
    Thanks to @Roger_T for the designs!
    • OnePlus Numbers
    • Minimalism
    • OnePlus Roman dial
    • OnePlus analog
    • OnePlus minimal
  • QS “DISCO” mode has been added, thanks to the POSP team!
  • Random accent mode has been added, thanks to the msm extended team!
  • Navbar pulse has been added, thanks to the DU team for porting it to Android 10!
  • Added random accent to tile label
  • Added support for per app network isolation
  • Added option to enable full screen for all apps. This is different option from the “long apps” feature, which is for old, legacy apps.
  • Improved aspects of volume panel (Notification row among other changes)
  • Brought back brightness slider in expanded QS panel when QQS (top) and QQS (bottom) are selected.
  • Added Ethereal primary theme.
  • A lot of improvements to Notch city, thanks to POSP and crdroid team!
  • Update QS data usage more frequently
  • Improved QS data handling some more
  • Increased size of all analog clocks
  • Fixed accent and gradient mode for QS tiles
  • Improved QS tint modes
  • Added SBC HD Bluetooth codec
  • Added Bluetooth dual channel mode
  • Added option to select SBC HD by default
  • Added A2DP codec priority option (preferred codec)
  • More Bluetooth updates
  • More SQLite improvements
  • Enabled Zygote pre-forking (USAP pool). This will make apps launch faster!
  • Added VoWi-Fi icons. This is disabled by default, so ask your maintainer to enable it only if your device supports the function.
  • Added notification counters (shows number of notifications in status bar)
  • Added back button for free-form windows
  • Update heads up QS tile icon
  • Add R style icon shapes
  • Transparent QS background (not yet added, depending on device releases may vary)
  • About Phone animations have been removed and changed to Lottie animations like other sections, as requested by many users.
    Thanks to our lead designer, Roger Truttmann, for adding these animations!
  • Added transparent status bar QS background
  • Removed search bar in launcher
  • Added ability to disable glance widget in launcher
  • Added stock navbar layouts (compact, right leaning, left leaning, etc.)
  • Launcher additions below:
    Thanks to all contributors and the AICP team!
    • Change row and column count
    • Clear all recents with swipe down
    • Toggle app labels
    • Hide top apps prediction row in app drawer
    • Icon size setting
    • Icon support


  • Navbar pulse will be hidden if navbar is hidden, or IME space is hidden when navbar is set to gesture mode. This is not a bug.
  • For transparent statusbar background, QS background opacity has to be reduced to see the effect!

We’ve also added more translations, thanks to contributors on our Crowdin. Go translate BlissRoms for your device here!

Dropped devices

We are discontinuing support for the following devices:

  • Realme 5 Pro (RMX1971)
  • Asus Zenfone Max Pro M1 (X00T)

We would like to thank the maintainers that maintained these devices up to this date. If you wish to maintain for any of the devices above, or apply to maintain for a new device, submit a maintainer application here.

And that’s it for this month! Leave a comment down below on your thoughts!

Let’s Try And Change The Game

We would like to announce a change to Bliss OS (our PC/x86/x86_64 builds) that we’ve been working on. Recently, the development on Bliss OS has taken a different turn towards something that can better benefit the entire community.

We’ve taken the concept of our Android-PC project, and started to rework the scripts to make things a whole lot smarter and easier to use. This allowed us to evolve Android-PC project into a toolkit that could also build multiple versions of a Bliss OS, along with AOSP. So seeing the potential there, we started working on the scripts, more and more. Adding the ability to create a PC .iso for just about any ROM out there, not just Bliss. After that we then boiled it all down to one vendor repo to clone into the AOSP or ROM source.

With that main groundwork laid out, we then added the treble (GSI) scripts based off the same PHH-Treble concept we started using in Android Pie, and updated those with all the new functionality added for the PC side of things. Making this project now require a new name, Android-Generic.

Next step was to make it smarter. So with multiple ROMs applying the same set of generic patches, we quickly figured out that we will need to split things up for the patches. So the process for both GSI & PC patches all start with a pre-patch phase to allow for any reverts or other preparation a ROM source might need, then after that we apply a generic patchset (usually the base set that applies straight to AOSP), then after that we have a second ROM specific patch set to add any conflict resolutions that occur from the initial process of configuring for you ROM. Then after that is all set, we also have a Customization patch set type. Think AOSP vs. AOSP-EX, or Lineage vs Lineage-EX. In this phase of patching, it will look for any rom add-ons, added patches for customizations, features, etc, on top of what the ROM has currently.

After that we set out to make the whole thing work more efficiently, adding the ability for new patch conflicts in one ROM to seek out other potential conflict resolutions on its own from the resolutions other ROMs have in the AG repo, so the more ROMs included in the main Android-Generic repo, the more ROMs that will be able to use it out of the box, benefiting the entire community.

Now for GSI, some may be thinking that PHH-Treble already uses a patching system and scripts, why would this be used? Since we are indeed using his work for the generic GSI patches, we don’t want to replace his work at all, we want to take the value-added approach and provide the community an easy to use system that incorporates his work and uses everyone’s solutions on top of it to grow and benefit everyone exponentially. 

For the PC side of things, this doesn’t mean the end of Bliss OS at all, in fact, Bliss OS is now part of all the PC ROMs that are built through AG. We will still be uploading Bliss OS builds too, but they will also be accompanied with  various other PC builds of different Android ROMs, and AOSP combinations.

This is where we need the Android community to start showing their support and try using the toolset. We’re not afraid of constructive criticism and are consistently working towards automating the entire process if possible. Help us help the community and git checkout Android-Generic today!

git clone vendor/android-generic

A notice on bug reporting

Hello everyone! This is a quick notice on what’s going on behind the scenes, regarding bug reporting for our ROMs and firmware.

Right now we have a repository set up on GitHub for bug reporting. However after using it for a couple of months we realized a couple of things:

  • People really, really want unified bug reporting
  • Device bug reports are hard to handle
  • Source bug reports must be separate but it’s hard to distinguish in the sheer volume of bug reports

That’s why we’re moving over our bug reporting system to Atlassian’s Jira. With the transition, we just want to let you guys know of a couple of things:

  • Starting from today (June 13) we will no longer be accepting new bug reports at the aforementioned bug reporting repository.
  • In the future we will open access to Jira for the public and allow everyone to submit bug reports. No date has been set yet.
  • Jira will handle all bug reports, including BlissRoms and Bliss OS bug reports, device-specific bug reports, and more.

We hope this clarifies a couple of things. Thank you for using Team Bliss’s software!