[PLANNING][WIP]Towards a new theme system - Omni Features Development

[PLANNING][WIP]Towards a new theme system - Omni Features Development

PLEASE - No generic "This is awesome" or "Thank you!" posts. In fact, unless you're a themer or ROM developer with technical questions about this project, please refrain from cluttering the thread for the time being. This is NOT ready for users yet and needs a lot of work before it will be.
So, it has come up multiple times that users want some way to theme their devices. The problem is that until recently, the only option for that was CyanogenMod's theme engine. Unfortunately, integrating this is problematic for many ROMs - while it's fine for cherry-pickers who don't care about understanding what they're throwing into their project, it's a big issue for someone who does not want to put 13,000 lines of code into their project in a single patch. (CMTE is 13,000 lines of changes in frameworks/base, which is the very core of Android.) Also, it has been known to have resource usage and performance issues.
Over the past year, Sony has worked on getting a runtime resource overlay (RRO) implementation merged into Android. Most of the implementation was in Android 5.0, and a few bugfixes were in AOSP master until Android 5.1 was released.
A few months ago, a few developers figured out how to use RRO for theming. This system was called Layers, and initially appeared to have a huge amount of potential. Unfortunately, for various reasons, the system stagnated. The original set of commits to implement Layers had a whole pile of issues and clearly had not gone through code review, and when attempts were made to fix these issues, the Layers team wanted to make no further changes. For Omni, a core requirement we have for any theme system is that it cannot affect the user experience when no theme is in use/installed. Layers fails this criteria. (For example, in AOSP, the text on the battery history graph is pure black with no transparency. In Layers, it is mapped to "exposed_primary_text_light" which is a shade of black that includes transparency. There is no way for an overlay to change the other graphical elements that reference this resource without also affecting the battery history graph text, and vice versa. There were numerous other cases of "colors redefined" and "multiple different colors mapped to a single resource".)
I've been talking with members of a few project (including Slim and LiquidSmooth) about taking the basic concept behind Layers and fleshing it out into a mature system that addresses the various issues with Layers. Also, there's a desire to try and implement as much compatibility with CyanogenMod themes as possible without making excessive sacrifices (bloat, major mangling of Sony's RRO approach to facilitate compatibility with legacy themes... Despite nearly all themes requiring a rearchitecture for Lollipop...) in order to make it easier for themers to support this new approach.

Proposed Roadmap and Status
Here's a proposed roadmap I discussed with some guys from Slim and LS in a discussion on G+. None of this is set in stone though.
1) Merge CM's resource exposure commits. While there are many aspects of CMTE I dislike, these are unambiguously superior to the Layers resource exposure commits and I find nothing objectionable to any of them I've looked at so far, although they have yet to go through full review. STATUS: Up on Gerrit, they seem good.
2) Write a Python script that handles translating the overlays of a CMTE theme to one compatible with the new system - STATUS: Semi-working, but requires item 4 and fails for any theme that uses the "common" resource overlay. Themes that don't use "common" (like Mono and FlatshadeUI) can be translated in 3-4 minutes. Well-formed themes that use "common" require typically 20-30 minutes to manually dereference any "common" references. Some themes rely on some hacks CM has to handle incomplete styles in overlays and thus won't be supportable without hacks that may be undesirable.
3) Implement support for loading overlays from somewhere on /data - STATUS: Not started yet. Needs some good security gurus/SELinux guys to do right.
4) Implement support for overlays being able to reference their own resources. CMTE has this, I haven't quite figured out how they implemented it as it's 13,000 lines of code changes to sift through. - STATUS: See the commit list, this is currently working, however it is "proof of concept" quality
5) Implement support for a "common" overlay - many CMTE themes use this and more are using it as time goes on - STATUS: Not started yet. This may not be possible without architectural mangling to a degree that is undesirable
6) Well, this is more in parallel with items 4/5, but implement an app for managing overlays - it has to be after 3 though. Someone who sucks less than I do at UI/UX stuff needs to do this. - STATUS: Obviously not started yet. I've had a few people express interest in this stuff.
7) Longterm goal - Implement support for parsing a CMTE theme in the manager app. Gives similar results to CMTE, except the big difference is putting the "heavy lifting" in an app instead of frameworks/base. This keeps the really nasty code separate from the core frameworks and thus more maintainable. - STATUS: Not even close to started. There are some components of CMTE that I really dislike and this may not be possible to do without those components. It's also far more likely to fail in ways that make a themer look bad for something not necessarily their fault.
Ideally it should be able to provide fairly high compatibility with CMTE but without the system bloat and performance impacts that CMTE seems to entail.

Show me the Code! (Patches)
THESE PATCHES ARE A PROOF-OF-CONCEPT/WORK IN PROGRESS. DO NOT MERGE THESE INTO ANY PROJECT. I will NOT work with anyone who merges these before they are ready!
You can submit them to your own Gerrit for review, but DON'T merge them.
Resource exposure patches
These are similar to the patches that make up "Type 2 Layers" - but to maximize compatibility with CM themes, we're using CM's resource naming. In fact, all of these patches are cherry-picks from CM
https://gerrit.omnirom.org/#/c/13292/
https://gerrit.omnirom.org/#/c/13293/
https://gerrit.omnirom.org/#/c/13294/
https://gerrit.omnirom.org/#/c/13295/
Allowing overlays to reference their own resources
A major limitation of the vanilla RRO implementation is that an overlay cannot reference its own resources. Sometimes this is annoying, in other cases (such as windowBackground attributes - see http://developer.android.com/guide/topics/ui/themes.html ), it makes doing certain things impossible. One of my main goals has been to find the minimum amount of change to allow this. Currently, the patches below are also all extracted from CMTE's frameworks/base megacommit. If this architecture is preserved I'm going to fix authorship of these commits, but right now I'm hoping to use these to gain ideas for a better way to do this and in the process rewrite them. These commits in their current implementation have some serious architectural limitations.
https://gerrit.omnirom.org/#/c/13346/ - The core implementation. This allows overlays to use their own resources. I'm in the process of analyzing this to determine if there's a way to do this without the current limitations it has. Specifically, if you attempt to use a "standard" overlay with package ID 0x7f, the overlay will completely fail and cause severe issues.
https://gerrit.omnirom.org/13347/ - Treat a few other PackageIDs as being "static" packages. I'm still in the process of reading through Android's code to figure out the differences between static and dynamic references. Overlays must be one of these packageIDs or they will fail.
https://gerrit.omnirom.org/13350/ - Allow aapt to override the packageID by specifying it as an argument to -x - this is needed to produce overlays that don't bork the system
Overlay best-fit hacks
https://gerrit.omnirom.org/#/c/13324/ - With standard RRO, if an overlay only has one resolution of resource, and the overlaid package has a resource that is a better fit (for example, overlay only has xxhdpi and device is xhdpi), the overlaid package's resource would get used. The end result in Layers is that some overlays would behave inconsistently on some devices. (For example, I've never seen a Layers overlay for Hangouts properly theme chat bubbles on any of my devices...)
Misc other fixes
https://gerrit.omnirom.org/#/c/13356/ - Quick settings tiles have a hardcoded AnimatedVectorDrawable class. This doesn't need to be hardcoded and can be a generic Drawable - for example, some themers want to use a RippleDrawable here. This commit is from Steve Kondik

Frequently Asked Questions
Q: What is this sytem's name?
A: To be determined. Names I've thought of so far are Light Weight Theme System (LWTS) and Phoenix (rising from the layers of ash) - I'm personally leaning towards LWTS because it's very neutral and I also hate flashy names.
Q: How is this different from AOSP/Sony RRO?
A: It is RRO with some small changes to address limitations in the current AOSP/Sony implementation, such as inability of overlays to reference their own resources.
Q: How is this different from Layers?
A: Any patch that is part of this system will go through code review with stakeholders from multiple projects invited to participate. Also, a core requirement of this system is that it does not change the behavior/look of the system when a theme is not installed.
Q: How is this different from CyanogenMod's Theme Engine?
A: While the current state of this is almost entirely cherry-picks of subcomponents of CMTE, it is only 150-200 total lines of code vs. CMTE's 13,000 in frameworks/base alone. There are some components of CMTE that we either don't want or will require too much invasive code to implement. So far one architectural difference is that like Layers, the current plan is for most of the "heavy lifting" (AAPT) to be done on a themer's PC, not on-device. Also, like Layers, this approach currently DOES support multiple overlays for a given package target. (This is most commonly used by Layers themers to change navbar icons independently of whatever other theme is installed for the rest of SystemUI)
Q: If this is intended to be a multi-ROM collaborative project, why is it in the Omni forum?
A: Most of the existing "generic" forums have a lot of clutter. One of the things I want to discuss with people is a better location for this. Same goes for the current usage of Omni's Gerrit.
Q: Needing a hacked AAPT sucks! I hate this!
A: I don't like it either. Trying to find a better solution is a work in progress.
Q: What about fonts?
A: Something I'd like to support, but not implemented yet.
Q: What about icon-packs?
A: Something I'd like to support, but not implemented yet. CM's approach depends on some of their massive architectural changes to RRO. Also, most launchers have built-in support for icon packs. (CMTE also allows a method for themes to include icon packs that will work with any launcher.)
Q: What about bootanimations?
A: Something I'd like to support, but not implemented yet. Should not be hard
Q: What about wallpapers?
A: Someone should probably work on this. I personally hated any theme that overwrote my nice wallpapers from InterfaceLIFT... So someone else will need to work on it. This NEEDS the ability for a user to disable by default.
Q: What about applying themes/overlays without reboot?
A: Unlikely, this capability of CMTE is the root of many of their massive architectural changes to RRO, and is responsible for many of the other tentacles it has throughout frameworks/base unrelated to resource lookup. Implementing this is almost guaranteed bloat.
Where are the Dialer/InCallUI resource exposure commits?
I need to take a look at these, CMTE doesn't have any - it may be that they are unnecessary when combined with the ability for overlays to self-reference resources. For example, looking at https://gerrit.omnirom.org/#/c/11674/2 there is no need to modify anything in res/drawable with CMTE or this approach, as the items in res/drawable can simply be overlaid. I have not yet looked at the other items.

Porting CMTE Themes
*Documentation on how to port a CMTE theme to the new system goes here*

More leftovers
Original leftovers is going to be the porting guide

Why not just call it Overlays Theme Engine?

skynet11 said:
Why not just call it Overlays Theme Engine?
Click to expand...
Click to collapse
Hmm, maybe... It's more likely to get confused with Layers though. It's already bad enough that so many users confuse Layers with vanilla RRO.

Just want to say 2 things:
1) Icon packs are actually possible to make, I made for "educational purpose" a port of a little part of Moonshine Icon Pack, GemFlat theme icons and some icons I personally made.
There are some advantages compared to CM: you don't have to insert app activity in any XML file, but just overlay the icon using a layer that target the app you want to theme.
2) I didn't understand well a thing about portings: do you actually mean on Layers or on this new type of theme engine?

Just a quick heads up.
Let's please read the OP before posting. If your post is not going to contribute to a technical discussion of the situation, please do not post it here. If your post mysteriously disappears with no warning, it is because such was not heeded.
Thanks.

SPAstef said:
Just want to say 2 things:
1) Icon packs are actually possible to make, I made for "educational purpose" a port of a little part of Moonshine Icon Pack, GemFlat theme icons and some icons I personally made.
There are some advantages compared to CM: you don't have to insert app activity in any XML file, but just overlay the icon using a layer that target the app you want to theme.
2) I didn't understand well a thing about portings: do you actually mean on Layers or on this new type of theme engine?
Click to expand...
Click to collapse
I believe this new way.
LiquidSmooth maintainer for d2usc/vzw & p600

SPAstef said:
Just want to say 2 things:
1) Icon packs are actually possible to make, I made for "educational purpose" a port of a little part of Moonshine Icon Pack, GemFlat theme icons and some icons I personally made.
There are some advantages compared to CM: you don't have to insert app activity in any XML file, but just overlay the icon using a layer that target the app you want to theme.
2) I didn't understand well a thing about portings: do you actually mean on Layers or on this new type of theme engine?
Click to expand...
Click to collapse
1) Well, right now, icon packs can be loaded by launchers that are "icon pack" aware. CMTE allows any launcher to load an icon pack from the theme itself by altering the icon resource of the app itself. Right now "system icon packs" are pretty low priority since MOST popular launchers support loading icon packs themselves, unless someone can state a good use case for them other than "supports any launcher".
2) Since CMTE is the most common theming system with a LOT of themers behind it, it's ideal to try and make the transition from CMTE to any other system as painless as possible for a themer. A theme engine without themes is pretty useless. Layers attracted a lot of themers unhappy with CMTE mainly due to how Cyngn ran some of their theme contests, but many of those themers were still supporting CMTE. If you want someone to support more than one theme engine, and you're NOT the biggest one out there, you've got to make their life as easy as possible. (Strangely, one member of the Layers team said that everything he did was "for the themers" - but the majority of what he did made things harder for themers AND ROM developers, especially themers coming from CMTE.)
Also, just one request to moderators: Try to go light on the moderation unless things go bad. It's a long story, but one of my issues with the Layers team was going overboard on the moderation. That said, the post deleted was just a link to the Layers community with no other comments other than saying "don't reply to me"...

Entropy512 said:
1) Well, right now, icon packs can be loaded by launchers that are "icon pack" aware. CMTE allows any launcher to load an icon pack from the theme itself by altering the icon resource of the app itself. Right now "system icon packs" are pretty low priority since MOST popular launchers support loading icon packs themselves, unless someone can state a good use case for them other than "supports any launcher".
2) Since CMTE is the most common theming system with a LOT of themers behind it, it's ideal to try and make the transition from CMTE to any other system as painless as possible for a themer. A theme engine without themes is pretty useless. Layers attracted a lot of themers unhappy with CMTE mainly due to how Cyngn ran some of their theme contests, but many of those themers were still supporting CMTE. If you want someone to support more than one theme engine, and you're NOT the biggest one out there, you've got to make their life as easy as possible. (Strangely, one member of the Layers team said that everything he did was "for the themers" - but the majority of what he did made things harder for themers AND ROM developers, especially themers coming from CMTE.)
Also, just one request to moderators: Try to go light on the moderation unless things go bad. It's a long story, but one of my issues with the Layers team was going overboard on the moderation. That said, the post deleted was just a link to the Layers community with no other comments other than saying "don't reply to me"...
Click to expand...
Click to collapse
I am a themer of both CM and Layers. Now, CM has many features that Layers hasn't (such as fonts, wallpapers, boot animations...) But talking about app themes only I like very much more Layers because of exposed colors. In new "Layers 2.1" various errors that have been made during first exposing were fixed (as did @atl4ntis alone in his ROM), and you don't have to struggle with styles.xml for most of the things (so it's more noob friendly). Obviously there have been many situations where I missed thee possibility to link something to something other in the overlay.
So I think that layers isn't confusing very much. I found more confusing cm. I think that someone who never made themes would prefer layers to cmte. This is my opinion BTW

SPAstef said:
I am a themer of both CM and Layers. Now, CM has many features that Layers hasn't (such as fonts, wallpapers, boot animations...) But talking about app themes only I like very much more Layers because of exposed colors. In new "Layers 2.1" various errors that have been made during first exposing were fixed (as did @atl4ntis alone in his ROM), and you don't have to struggle with styles.xml for most of the things (so it's more noob friendly). Obviously there have been many situations where I missed thee possibility to link something to something other in the overlay.
So I think that layers isn't confusing very much. I found more confusing cm. I think that someone who never made themes would prefer layers to cmte. This is my opinion BTW
Click to expand...
Click to collapse
I think the whole thing about whether is easy or hard can easily be fixed by creating templates just like in the CMTE where a "noob" can just git clone that and start off with that.......
If the template is done right with comments and all, it shouldn't be an issue. Then you have support threads which can be made after things are set and done where people can help each other and get things going.
Nothing is ever going to be "noob proof". Just take a look around at all the guides and everything for the most simple things. As easy as it is to flash a ROM, there's actually videos and guides for that and people STILL find themselves with that deer in the headlight look

SPAstef said:
I am a themer of both CM and Layers. Now, CM has many features that Layers hasn't (such as fonts, wallpapers, boot animations...) But talking about app themes only I like very much more Layers because of exposed colors. In new "Layers 2.1" various errors that have been made during first exposing were fixed (as did @atl4ntis alone in his ROM), and you don't have to struggle with styles.xml for most of the things (so it's more noob friendly). Obviously there have been many situations where I missed thee possibility to link something to something other in the overlay.
So I think that layers isn't confusing very much. I found more confusing cm. I think that someone who never made themes would prefer layers to cmte. This is my opinion BTW
Click to expand...
Click to collapse
Well, CMTE exposes colors too - can you provide a specific example of something that was easier in Layers than CMTE due to not being exposed?
I'm guessing probably something in Dialer or InCallUI, since the resource exposure commits in the rest of CMTE are pretty similar to Layers with a few exceptions. I'm willing to consider some "laziness commits" that expose resources as long as they don't conflict with existing ways of doing things.
Other themers I've spoken to preferred CMTE over Layers by a long shot. I think the learning curve of Layers for basic theming might be a bit shorter, however CMTE allows a themer to do much more. I've seen piles of things in Mono, Coalfield, and FlatshadeUI that would be an utter nightmare to do on Layers, if even possible. (As evidenced by the fact that some guy has been trying to port Coalfield to Layers for 2-3 weeks now - I had Coalfield working about 20-30 minutes after I started working on getting it to work with the new system.)
I looked into these fixes you claim they made... They're the fixes I fought for two months to get people to agree on, it appears that after I gave up and said "I've had enough", they squashed the fixup commits into the original ones and changed authorship (In addition to removing the post with my proposal from their community). For reference - the original fixup commits that I put forward for Layers 2.1 are at https://gerrit.omnirom.org/#/q/status:open+topic:rro2p1 and were originally written in late February. Similarly, any CMTE resource naming convention compatibility in Layers was proposed by myself for Layers 3 (WIP at https://gerrit.omnirom.org/#/c/12323/2) and rejected along with the Layers 2.1 fixes - it appears they pulled THIS in too and called the whole thing 2.1. (You'd think that a naming convention change would merit a major version number bump...)

Mazda said:
I think the whole thing about whether is easy or hard can easily be fixed by creating templates just like in the CMTE where a "noob" can just git clone that and start off with that.......
If the template is done right with comments and all, it shouldn't be an issue. Then you have support threads which can be made after things are set and done where people can help each other and get things going.
Nothing is ever going to be "noob proof". Just take a look around at all the guides and everything for the most simple things. As easy as it is to flash a ROM, there's actually videos and guides for that and people STILL find themselves with that deer in the headlight look
Click to expand...
Click to collapse
One thing I want to do is to try and write some convenience tools for themers... This may be necessary to handle the "common" nightmare as I might need to preprocess "common" resources.
Of course, there are a lot of tradeoffs here... Sometimes making things TOO easy prompts a flood of some really awful stuff. Theme DIY was a great idea but it's led to a bunch of really horrible paid themes on the Play Store (despite the TDIY author stating that the tool was not to be used for paid themes), making people more reluctant to actually buy paid themes that ARE good.
Which is why I'm still torn on one feature of CMTE that handles cases where an overlay has an incomplete style that is missing attributes - Now, this makes a themer's life easier, but in general, the themes where lack of this feature has been a problem were ones of poor quality... One of the stated reasons for the patch was handling cases where an app updated causing the overlay to crash. The problem in this case is that it's better for something to be obviously wrong than for it to fail in subtle weird ways. Look at Facebook for example - at some point they made a MASSIVE overhaul of their styles. Some themes overlaid the "old" styles - as a result of the changes, they crashed with this engine, but caused strange graphical glitches in CMTE. (In fact, I need to check, but I think one themer removed all of his style overlays for Facebook from a theme because of this - at least he was considering it.)
I want to make themer's lives easier BUT I also don't want to encourage bad practices... There are some tough tradeoffs here.

I agree with you.
If also users with no theming capacity starts making paid themes this will be a pain for good themers.
Another question, do you have any ETA to complete this? (Or at least first points)

SPAstef said:
I agree with you.
If also users with no theming capacity starts making paid themes this will be a pain for good themers.
Another question, do you have any ETA to complete this? (Or at least first points)
Click to expand...
Click to collapse
As far as ETAs - there are a lot of unknowns here. Also, I need to finish up some core Omni stuff that I let slide for... WAY too long because I was spending time on theming and Layers. There's a gigantic CAF ifdef effort I need to finish so we can start nightlies.
Also, if I recall correctly, you were working with the guy behind Carbon UI? (Elixium Dark is the Layers form of Carbon UI???) - https://play.google.com/store/apps/details?id=com.zyxxeil.carbon.ui
That was a pretty easy port since he only used common for some of the keyboard drawables.
MilosUI took about ten minutes (mostly, again, handling "common" in the keyboard).
I think I'm gonna pop back over to FlatshadeUI for a while though.

Entropy512 said:
As far as ETAs - there are a lot of unknowns here. Also, I need to finish up some core Omni stuff that I let slide for... WAY too long because I was spending time on theming and Layers. There's a gigantic CAF ifdef effort I need to finish so we can start nightlies.
Also, if I recall correctly, you were working with the guy behind Carbon UI? (Elixium Dark is the Layers form of Carbon UI???) - https://play.google.com/store/apps/details?id=com.zyxxeil.carbon.ui
That was a pretty easy port since he only used common for some of the keyboard drawables.
MilosUI took about ten minutes (mostly, again, handling "common" in the keyboard).
I think I'm gonna pop back over to FlatshadeUI for a while though.
Click to expand...
Click to collapse
I didn't port it. We did it together (actually Elixium Dark was out 2 weeks before Carbon), so there was no problems into porting, because they are 2 different themes. With that project we showed that it's possible to make very good themes with both CM and Layers.
Milos is a port (but with some changes), yeah it was quite quick to port it.
Mainly the "hard work" is with common and with framework, systemUI and settings, as they are quite different to theme between the 2 platforms

I look forward to adding this to my comparison between Layers and the CyanogenMod Theme Engine when I publish it

Related

[IDEA] HTML-based layout launcher

I've searched for this, and it doesn't seem to exist; I'm surprised.
In case the premise is not clear: in much the way that (for example, SSlauncher) some launchers can have heavily customized setups / themes which can then be saved / backed up, why is there no launcher in which the theme / layout would be html-defined? The primary missing element would be a tag to launch an app, but I imagine such could be implemented, <a href=app://com.somedev.whateverapp>foobar</a> etc...
It would have the mild advantage that many users are already familiar with the markup, and it would allow for simplified sharing (and previews!) of themes... As well as device-resolution agnostic themes, etc.

I completely agree with you. Just finished googling it and came up with nothing. Right now i use a text only launcher, but would enjoy a HTML one much better

Another good thing would be that you could easily make themes for both phones AND tablets! I'd make a bunch of designs for sure!

[BitSyko] Official Layers and BitSyko Apps [RRO]

BitSyko is a group project mainly consisting of 3 Apps. Layers, Showcase and RomMate with a view to simplify things that are complicated and give an average user more control over his/her rooted lollipop and Marshmallow device.
Let's get the to the main app and straight to the point.
What is Layers?
What is Layers?
Layers is a extension of runtime resource overlay.
RRO is a framework created by sony for use as a way for them to create xperia themes but also for internal quick prototyping.
Why is root needed?
We use root to do this to provide a way for the android community can use regardless if they are on aosp or touchwiz or any other skin to provide versatility.
RRO was created for OEM use by making changes for them to create theme ecosystem that they could control, by using a location intended for pre-themed by OEMS, we are able to tap into the use of this system.
Why were changes needed on lollipop?
Our ability to theme resources were quite limited in lollipop since a lot of android linked back to the frameworks which we could not overlay with RRO so we had to make changes in AOSP source to provide a way to theme more.
Thankfully Google saw this inability also and has made changes in M so there will need to be less that needs to be modified for theming and better support natively.
By the nature of how RRO works, most resources are actually protected from malicious changes by RRO
Why does the community say Layers or RRO or RRO/Layers?
When we started the project, we didn't have a name for this system and we just called it how we were using it and it stuck.
RRO is the basic overlaying of resources
Layers is what can't be done with just RRO without resource changes
So what is a Layer?
A layer is what we call our themes. A Layers theme is a collection of overlays
Where are layers stored to be loaded?
Since RRO was developed for OEM use, we use a location of system/vendor/overlay to place our theme apks.
The package manager sees these apk at boots and verifies them and then uses a tool called idmap to link it into the system resource table
Is layers a theme engine
No, there is no engine in place with Layers, it uses native android code to work while theme engine was just naming by T-Mobile to market their theming system back on gingerbread phones.
Cyanogenmod has stuck with that naming and are way closer to it then what Layers is
So how does it work?
What a overlay does is that it looks for a string in the the resources and replaces it during loading into the system.
For a way better and more in depth explanation see sony's blog post about how rro works
http://developer.sonymobile.com/201...ce-overlay-framework-to-android-code-example/
Why is a reboot needed?
Since RRO hooks into the resource look up framework of android, the system only looks at these resources upon intial start of a process, service or app so a restart of it is needed which is why a reboot of something that changes the framework or system ui needs to be retarted to remove or load a new resource.
Is RRO insecure
When sony says this in their blog, it is greatly exaggerated.
Just like how Layers had to make changes in the source just to move the resources to locations that can be overlaid with RRO, the actual limits of overlaying a running system come into play. Not that many files can actually be overlaid because they make calls back to other resources that are not present in a overlay.
Trying to overlay these files will end up in a bootloop upon booting because it will not be able to link the resource.
Rumours of this insecurity have been greatly exaggerated by others yet never showed any actual proof of this happening in the actual OS or apps out there.
In Sony's case, their example app was coded in exactly a way to show off how it could work but not how it does in existing apps out there in practice
So reading sony's blog says that it is more then theming?
It absolutely is just for more then theming and the usage of just for theming means that it has been left untapped for other uses.
Theming is just the large market demand in the android community so that is what the primary focus has been.
I was planning to use it for different purpose before it was realized for it's use for theming.
There were also limits everywhere that I tried to change with RRO that would require lot of changes in the source code to do much beyond theming.
Why can't cmte and Layers co-exist?
While they both use RRO as the base of how they theme, CM takes the code of RRO and repurposes it for the cmte for system apps creating a conflict of use.
Cmte works towards providing a whole complete package with everything running through the asset manager.
Layers sticks as close to the stock RRO and only changes what needs to be changed to provide a function yet still be used in stock android or other skins with minimal modifications to just resources
How long as RRO existed?
RRO has been in android* and open source since the gingerbread days.
It was a fancy symlinking system back in those days and evolved over the next few years to what we use today for better performance.
The ability of being able to overlay* apps outside of the framework and multiple apps has existed since 2012 in unmerged commits on the aosp gerrit.
So why did nobody think of using this before for theming?
Cm realized it and rebased to it (did not realize this before because of giant squashed commits) but beyond sony and recently a few other oems, nobody even noticed it before or saw potential in it.
Why is there no boot animations, ringtones, wallpapers, fonts with rro like cmte?
These are going to be in a separate app called RomMate that is in current development because they do not use RRO as their method of use.
Why is there no icon packs for layers?
This is in current development
What is the future for layers?
We are currently at the beginning of overhauling our system to provide maximum capapbility with all oem roms for marshmallow.
We are also working on providing a new way to provide large modularity in themes to provide a plethora of options for the user while making it easier on the themer/designer.
Why are you writing this now?
Tired of a outdated post with inaccurate info by me because I did not dive deep enough into cmte's code being posted everywhere when someone asks what layers is plus so people can link to it.
How do i get started with Layers?
First you need to be sure if your ROM supports Layers, It does? Okay.
1) You can join the BitSyko Development Community.
3) Download the https://play.google.com/store/apps/details?id=com.lovejoy777.rroandlayersmanager Layers app on to your device.
4) Open the Layers app so it can initialize and create the required folders.
5) Check out and find a layer you want on the community or use the Showcase app to find new themes
Fixing bootloops caused by a incompatible/bad layer from TWRP.
Step 1: Go to Advanced.
Step 2: Go to file manager.
Step 3: Go to /system/vendor/overlay/ and remove the bad overlay apk.
GitHub :- https://github.com/BitSyko
XDA:DevDB Information
BitSyko, App for all devices (see above for details)
Contributors
sykopompos, bitstra, CallMeAldy, @bgill55
Version Information
Status: Beta
Beta Release Date: 2015-01-24
Created 2015-01-25
Last Updated 2015-08-22
#WhiteUiMustDie

Reserved
Developers
Basically there are two types of supports, you'll have to include in your ROMS on lollipop to have full layers support working without any issues.
RRO basic and layers type 2.1 for lollipop and type 3 for marshmallow
RRO basic is what you can do with stock while layers is the extension of that
Rom commits from a aosp base.
https://github.com/The-Ancile-Project/platform_manifest/blob/frank-mutant-test-1/README.md
Commit not added to that list yet
https://github.com/MinimalOS/androi...mmit/8681610df588647bdfa464b316895d33f78c3f9e
Huge thanks to Sony and Google for RRO
http://developer.sonymobile.com/201...ce-overlay-framework-to-android-code-example/

Reserved

reserved

reserved 2

Reserved

reserved

Reserved 2

1st one... Thanks for opening an xda thread!!!

Reserved

Damn another thread to religiously follow.... Shaking my fist

Excellent! Subscribed.

I'm curious...and slightly drunk. Cheers to you guys!

Yes! Really looking forward to seeing where this goes! Layers for everyone!

Nice work team! Have been waiting for this thread to open
Sent from my Nexu5

Not a qualified plastic surgeon but I'm trying to give the OP a makeover. Lmao

Thank you guys for bringing Layers (RRO) to the table, subscribed to the thread. Great explanation of what Layers is too!

This is awesome! Can't wait for the template to come out so we can theme the whole rom with one app XD
Sent from my Nexus 5 using Tapatalk

Nice. It's officially here. lol Guess it's time for me to finally join this G+ thing.:good:

Still trying to figure out how to make overlays, I won't give up. Maybe I'll succeed in a couple of years :silly:
If someone will push some tut out :angel:

MBTD - G7 Premium Themes. Feedback, communication

Rain
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

This is Rain, an LG Home+ theme for your LG G7 running Android 9. This theme is a premium quality theme like no other Home theme+. What you see is what you get and that is quality and attention to details! Rain is a dark theme with some bright gradient accents throughout. The Dark Notifications compliment the ui and battery life! The app icons have a slight gradient to them, with some more noticeable than others. This theme does not support adaptive icons as some of the key features of this theme are blocked by enabling the adaptive icons. If you'd prefer adaptive you will need to use a third party launcher like Hyperion or Nova.
No need to run a third party theme system any more, just use the system theme chooser and you can enjoy all the benefits of an advanced theme system.
To apply the theme simply go into settings/display and select themes. From there select Rain, and push apply! then reboot and then reapply the theme again. It's a bit more in depth than other themes but given the complexity of this premium theme it is required for all elements to be themed properly.
That's it! Simple, easy and quick.
This theme is also meant to run at the highest resolution, with the lowest stock setting for the actual display size. Larger sizes may cause some elements to look slightly off. If this happens please lower the display sizes of the iconography.
Also for the power menu to be themed you have to reboot and reapply the theme. Sometimes you may have to reapply it more than once. This is something with LG's software and not within my control.
If you run into any issues please send me an email directly instead of leaving a poor rating. Often I am very quick to reply and great to solve any issues. The review system is not meant to be a support channel!
Thank you so much for your support and I hope you enjoy this theme. I've worked extremely hard on this and by far it was the most challenging and time consuming project I've ever made!
Now for the stuff people actually care about.... Screenshots!!!

Pixel Experience
This is the Pixel Experience. For those who want to enjoy a lighter theme with minimal, subtle changes that want to be able to set it and forget it without having to worry about constant Google app updates and be able to enjoy the Pixel look. This is for you and you're gonna love it! Like Alpha this theme will be updated regularly and will continue to grow as time goes by. Enjoy the clean and refreshing look and experience the Pixel!!! #WhiteUiMustLive
Now you probably didn't bother to read that crap above so let's just post some screenshots shall we?

Pixel Experience (Legacy Theme)
So since not everyone digs using substratum I decided that Pixel Experience should be a regular (Or as I call them "Legacy" LG Theme). No computers, no additional apps in order to use it... You can just set it and forget it! You will get all the features from the Substratum version and then some.
Here's a pic of how this theme looks!

Pixel Experience Dark
Welcome to the dark side. This is Pixel Experience Dark! Including dark notifications! I'm really proud of this and how it turned out! Please take the time to read the app description as there is some important information in there for your benefit which will help you get the best experience out of this theme! Also in the description are optional patches which are theme specific!
So go get it and please drop me a quick rating and if you'd also be so kind to give this a quick share too that would be great!
Screenshots!!!
Since this theme pushes the boundaries of the LG Theme system it retains adaptive and dynamic icons on stock launcher. Due to this you will have to select your navbar color in settings, display, home touch buttons. By default it may show you have selected the dark option, but the navbar may still be white. Simply select the white and then select the dar one again and you should be set. It's a bit odd but that's just how it has to work. Unfortunately there is one app that does not show the navbar as being dark which is the LG Music app. it demands to stay white due to this. I realize some people may not like this so I've also made another patch for users who want it to match. This however will kill the adaptive and dynamic icons so decide which option you prefer because unfortunately due to system limitations you simply cannot have both. Like the previous patch just install it, reapply the theme and reboot. If you use a third party launcher this patch should most definitely be used. link to patch:
https://drive.google.com/file/d/1tDOIM4dKssw3oOMm6clEBROlGEoOgGt3/view?usp=sharing
I've also included a patch for Light notifications because some people mention that they're having difficulties with some apps like whatsapp or telegram where the user name is black on a dark background or that they have a light shadow around said text to make it somewhat readable. If you wish you can install the patch and the entire theme will remain as is but the notifications will be light and you won't have any issues at all.
How to install the patch: First update the theme to the latest version. Then download the following apks (link below). Next change to stock theme. Then install the apk patches. Then after you've installed them apply Pixel Experience Dark. Next reboot and you'll be all set. If you experience some force closes that is because you didn't revert to stock theme and installed the patches while using Pixel Experience Dark
Patch links 1 of 3:https://www.androidfilehost.com/?fid=1322778262904028399
2 of 3: https://www.androidfilehost.com/?fid=1322778262904028400
*3 of 3: https://www.androidfilehost.com/?fid=1322778262904028427

Twilight
See bottom of description for Quick Settings Add-on Patches!!!
This is Twilight an LG Home+ theme for your LG V40 or LG G7 running Oreo only (Pie is not yet available on my devices and therefore not yet supported!!!) This theme is a premium quality theme like no other Home theme+. What you see is what you get and that is quality and attention to details! Twilight is a dark theme with bright gradient accents throughout. The app icons have a slight gradient to them, with some more noticeable than others. This theme does not support adaptive icons as some of the key features of this theme are blocked by enabling the adaptive icons. If you'd prefer adaptive you will need to use a third party launcher like Hyperion or Nova.
No need to run a third party theme system any more, just use the system theme chooser and you can enjoy all the benefits of an advanced theme system.
***Third party Quick Settings Icons:
Some apps allow the user to add a shortcut activity to the quick settings panel. This is not supported by this theme whatsoever. If you decided to add any icons to your quick settings panel they will not show up. They will be 100% transparent. They cannot be added. If this bothers you then in a future update I will make an add-on quick settings patch that will add usability back for them, however it will sacrifice the creativity of the current structure of both styles of available quick settings icons. It will be more minimal and all the icons will be the same color like how most themes are. Due to the complexity and advanced nature of this theme this is something that I am aware of and have embraced 100%.
To apply the theme simply go into settings/display and select themes. From there select Twilight, and push apply!
That's it! Simple, easy and quick.
Please note that refunds will not be given for installations on non LG V40 or G7 Oreo Devices. As the title of the theme clearly indicates which device this is for and this app description does specify which OS version is supported..
This theme is also meant to run at the highest resolution, with the lowest stock setting for the actual display size. Larger sizes may cause some elements to look slightly off. If this happens please lower the display sizes of the iconography.
If you run into any issues please send me an email directly instead of leaving a poor rating. Often I am very quick to reply (unless I'm sleeping and you're in a different time zone) and great to solve any issues. The review system is not meant to be a support channel!
Quick tip... Search and install the app "Quick Shortcut Maker" on google play. Install, then long press on your home screen and select the 1x1 quick shortcut maker widget and drag it on your home screen. Then in the activities tab, scroll down to"wallpaper & themes" and expand it. touch 1st option at the top of the list that doesn't have and upwards arrow. Hit Create" button at the bottom and now you have a themes app shortcut you can place on your desktop!!!
Thank you for your support and enjoy theme!!!
This theme as you can see from the screen previews shows two different styles of Quick Settings icons. This is because I designed both styles and had a tough time deciding on which ones to go with so I decided to make them both. The minimal icons are default. However if you wish to change them simply download the corresponding patch to the style that you want. After you've downloaded the patch, apply the default LG theme. Then install the patch, reboot and reapply the theme then reboot again. You will now see a different style. If you wish to change back the original style you can repeat the above process using the other patch. I've uploaded and clearly labeled both patches. They can be found here: https://www.androidfilehost.com/?w=files&flid=288986
For dark notifications it takes 5 add-ons patches.

G Theme 3
Click me for Video Promo
t's back!!! This is G Theme 3. Why G Theme you ask? Well I think you can figure that out when you use it what it's all about. This theme is a premium quality theme like no other Home theme+. What you see is what you get and that is quality and attention to details! G Theme 3 is a dark theme with beautiful colors and designs throughout it. The Dark Notifications compliment the ui and battery life! This theme supports adaptive icons and I recommended choosing circle which is unlocked as a feature and can be accessed from going into the settings application and then going into display, home and choose the icon shape. Due to this the music app does have a light overlay at the bottom which is a bug that LG should address!!! For real LG fix that will ya.
Now this is the important part. This theme is only for LG devices running UX 7, Android 9.0 pie. If you are running a different LG UX or android version this will not work and if you upgrade from the above this theme may not work properly. It is presented on an "as is basis". I do my best to try and update to allow for the theme to function on all devices as best I can and as soon as I can. However due to LG's interesting update cycle sometimes one device may update prior to others.
To apply the theme simply go into settings/display and select themes. From there select G Theme 3, and push apply! then reboot and then reapply the theme again. It's a bit more in depth than other themes but given the complexity of this premium theme it is required for all elements to be themed properly.
That's it! Simple, easy and quick.
The theme comes with a coral wallpaper but if you'd like to have it animated simply grab this add on and set it as a live wallpaper and you'll be all set. Since most Lg Devices don't support seamless wallpapers just download this and install it and set as your live wall and enjoy!
Live Wallpaper right Here!!!
Please note that refunds will not be given for installations on non LG G7, V35 UX 7 (running Pie) Devices. As the title of the theme clearly indicates which device this is for and this app description does specify which OS version is supported..
This theme is also meant to run at the highest resolution, with the lowest stock setting for the actual display size. Larger sizes may cause some elements to look slightly off. If this happens please lower the display sizes of the iconography.
If you run into any issues please send me an email directly instead of leaving a poor rating. Often I am very quick to reply and great to solve any issues. The review system is not meant to be a support channel!
Thank you so much for your support and I hope you enjoy this theme. I've worked extremely hard on this and by far it was the most challenging and time consuming project I've ever made!

[/CENTER]
Instructional video on how to apply Alpha, see below
You will need ADB installed on your pc: Right here
You will also need the substratum app as well as the Andromeda app and the Desktop client for Andromeda
This thread is for support and feedback for my LG Substratum themes and legacy LG themes. with the update to 8.0 Oreo substratum is now supported without rooting your device. Due to the capabilities with Substratum all previous LG themes will be referred to as "Legacy themes" and the primary focus has shifted to Substratum. Since substratum can provide everything that an LG theme can provide and more it makes the most sense to evolve and transcend into the more advanced theming system.
So this is my first theme "Alpha". It has a double meaning and I feel is appropriate for this theme. Let's stop with the chit chat and post a few screenshots and if you're looking for a way to pass the time then keep reading! I promise you the literature doesn't get any better, but have at it!

Oh hey everyone! Again, I didn't see ya there. You just snuck right up on me now didn't ya bud. Well it's that time again. Another new beautiful LG device is upon us and I had to get it. So it must mean it's time for another fun theme discussion and feedback thread. Now I must get this next bit out of the way to make it clear what the purpose of this thread is. 1: I am not here to sell my work whatsoever and that is not the purpose of this thread. Posts regarding updates, screenshots or other communication are strictly for the purposes of obtaining feedback on what I do. and to see if users are pleased with said changes. 2: I will never post a direct link to anything I make that is paid as that is not allowed and I expect that as users you will not post links either.
My V20, G6 and V30 threads are absolutely fantastic and I encourage you all to check it out at some point if you wish to see how I interact with people. I cannot thank you all enough who have supported me and given me feedback and interacted with me in any way to discuss things theme related. Don't be shy about commenting or giving suggestions or feedback provided it is constructive and is done in a mature and professional manner. Feel free to joke around a bit and have some fun. That's what it's all about anyway. It's a very positive and fairly active thread. Users often give me feedback which is incredibly valuable and also post pics of any bug fixes. That allows me to quickly address issues.
First things first to any mods who may be peeping it is important to note that I am complying with xda rules and there are zero paid direct links posted anywhere in this thread by me. So there are no rules being violated. Rule 11 states that I can use xda to get user feedback on paid applications and that is what this thread is for so I am well within rule 11 which can be found here:
11. Don?t post with the intention of selling something.
Don?t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and to offer support, but not to post with the intention of selling. This includes promoting sites similar / substantially similar to XDA-Developers.com.
Do not post press releases, announcements, links to trial software or commercial services, unless you?re posting an exclusive release for XDA-Developers.com.
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.
Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if both of the following conditions are met:
A) The site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership, who actively maintains an XDA-Developers support thread(s) / posts, related to the download.
B) The site is a relatively small, personal website without commercial advertising / links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
Be sure to follow me on google plus to stay up to date and get additional theme information regarding updates and other testing and feedback.
So this thread is for all those who are using any of my themes where we can come discuss things, give feedback and post screens etc of what I've been working on. I will continue to add new themes and post screens of my work here and interact with all of you. Remember, I ask that you be civil to myself and other members and keep any feedback constructive.

Reserved for theme 8

Reserved for theme 9

That's right... I'm taking the whole page!

Nice. Didn't think you'd have XDA action but sweet. Alpha purchased. It's gonna be a day or so before I can do the Andromeda thing but I'll report bugs, etc on here man. Nice work as always @MARK Bencze

Thanks! Installed and working great!!!

co.ag.2005 said:
Thanks! Installed and working great!!!
Click to expand...
Click to collapse
Looks like you need to sort out a few things still. That doesn't quite look right. Check the lg system resources option and settings overlays. Your icons are a bit off in settings. They should be centered
I have a feeling that when you get lg system resources that your 3 dot menu and search icon might have readability issues if you select the same accent color as the theme color. I'll check this too. If so I'll add it to a list and correct it. Normally the first version when adding a new device we find a few surprises so I'll probably wait a day or so and explore as well as get feedback from people here and then see what I can do.

markbencze said:
Looks like you need to sort out a few things still. That doesn't quite look right. Check the lg system resources option and settings overlays. Your icons are a bit off in settings. They should be centered
I have a feeling that when you get lg system resources that your 3 dot menu and search icon might have readability issues if you select the same accent color as the theme color. I'll check this too. If so I'll add it to a list and correct it. Normally the first version when adding a new device we find a few surprises so I'll probably wait a day or so and explore as well as get feedback from people here and then see what I can do.
Click to expand...
Click to collapse
Thanks. I didn't notice. I'll check out a few things on my end tomorrow when I have the chance.

I will add then when I followed this instruction (in the play store description)
.....Then once all the overlay's are build go back and select them again and select "enable". I found 9 times out of 10 this is the best way to apply them and I experienced fewer issues. Do this from the "Themes" tab. The "Manager" tab really wasn't needed and caused me the most headaches......
Click to expand...
Click to collapse
it didn't quite "take" for me, so I enabled from the "Manager" tab, and all was right with the world.
fwiw, I also read through your instructions posted here too before doing anything:
https://plus.google.com/u/0/111385861061275979764/posts/hu6o6pop3w4?cfem=1
Nevertheless, awesome theme!!

Glad to see some mods coming along for the G7! I do have a question though: is it possible to change the statusbar icons to AOSP icons with your mod? I absolutely despise the fugly icons that Samsung/LG/every single OEM except for Google use on their devices. I also would love the option to be able to see p.m/a.m after the time on the statusbar too.
Sorry if the question sounds silly, I'm just not sure what you can do without root/unlocked bootloader on Android phones. Thank you!
Either way, thank you for your contributions

AhsanU said:
Glad to see some mods coming along for the G7! I do have a question though: is it possible to change the statusbar icons to AOSP icons with your mod? I absolutely despise the fugly icons that Samsung/LG/every single OEM except for Google use on their devices. I also would love the option to be able to see p.m/a.m after the time on the statusbar too.
Sorry if the question sounds silly, I'm just not sure what you can do without root/unlocked bootloader on Android phones. Thank you!
Either way, thank you for your contributions
Click to expand...
Click to collapse
I do have pixel status signal icons which are nice and clean and probably what you're looking for! I'm constantly adding new things.

co.ag.2005 said:
Thanks. I didn't notice. I'll check out a few things on my end tomorrow when I have the chance.
Click to expand...
Click to collapse
I re-applied everything and now the icons line up. Thanks again for the work. Excited to see the updates to this and future themes!
https://photos.app.goo.gl/SUc4G0q5XtdRwaIm1

dude, this theme works amazingly well. thank you so much for this. my eyeballs are in your debt!

markbencze said:
I do have pixel status signal icons which are nice and clean and probably what you're looking for! I'm constantly adding new things.
Click to expand...
Click to collapse
Sold! I've been able to get the nav bar and the status icon to stock Pixel and am loving it! Just need to figure out how to reverse the settings since it seems a bit buggy. Don't really need a "dark" theme but I'm sure some people do.

PAID PROJECT: Nougat or Oreo AOSP status bar signal and wifi icon colors and mods

I would like to hire the right developer for a personal project.
I absolutely dislike white statusbar icons. Most, if not all substratum
themes do not touch the status bar icon color, some use overlays to
change the background though. There is a substratum overlay for wifi icons but this seems overly
complex for such a simple icon swap, and there have been changes made by google
to prevent the signal icon from being changed, at least according to the developer.
In earlier versions of Android, SystemUI.apk could be extracted along with framework-res,apk, and the
resources swapped for icons of my choosing. I am going with an AOSP rom
based on Nougat (AICP, or Resurrection). I am not working with Sense roms. My understanding is that Oreo further limited
the ability to change statusbar icons, that would be my reason for going
with Nougat. I would rather stay with an Oreo build of AICP but that is not a must.
If you are interested, I would like an estimate of the time it would
take you to:
1. Tell me which files to pull and send to you
2. Determine where the resources and/or code must be decompiled/edited to make this
work, that is, signal, wifi, other icons of my choosing. I can provide the icon files.
3. Send me the edited files
4. I will test
5. Work with me to handle the bugs
6. Once we have a working setup, draft an outline of what you did which
would enable me to decompile/edit the appropriate apks or files so I can
do this myself later with different icons.
A bit about me:
I am tech savvy, familiar with the linux command line, adb, etc.
I am working with AOSP roms on a HTC M9. Rooted, S-OFF, it is a GSM
variant (himaul). But I am not a software developer.
I am not looking for an app to do this for me. But I am seeking out the expertise
to reverse engineer what I need to make this happen and do it manually.
In my hours of pouring over xda I read somewhere the inability to choose
the icons is a google policy. I can't stand the modern UI white, washed
out colors but themeing can take care of most of that. In case you ask,
I'm currently on 4.3 on a HTC M7 from 2014 and I have got to get going with a newer
device.
I realize your time is valuable and this will not be a trivial task (or expense)....I only ask you to reply having enough familiarity to dive in without too much OJT.
Please do include your hourly rate. I would have no problem if this work is made GPL and free to post here, if you like.
Thanks!!

Just noticed my favourite ROM was dead for more than a year. What to choose?

I just noticed the ROM I have installed on my phone (Bootleggers) most likely died (their website isn't up anymore, there's no new threads about it, their GitHub/Sourceforge didn't have any recent activity at all etc.). I chose this ROM because of some neat features it had. And, that's the reason I'm asking this question today.
The features I want to have might be stupid for others, but they make me choose a ROM over another one and since I don't really have the time I had before to go through every ROM I see with support for my phone, I am asking everyone for their personal preferences.
A ROM for me must have (from the most to the least important):
- Must be de-googled/have a de-googled variant
- Support for signature spoofing (this is needed because I will use microG to actually keep getting notifications on my phone)
- Include as little proprietary programs as possible (yeah, I know Bootleggers didn't really do that), preferably only include open source apps (I don't care if they're fully free software or something, they can be anything open source and a little bit more privacy-minded without tracking or anything than others, I am willing to make some small sacrifices but I want to use as many open source programs as possible)
- Over the air updates (I think all have that but I'll still specify)
- Must be the latest version of Android
- Work profile/Shelter support (but I think that absolutely everything nowadays has that)
And now come the least important things, but ones that will still make me choose a ROM which has them over one which doesn't:
- It would be nice if the default apps looked modern, and maybe also had consistent theming, preferably one that syncs to the theming you do in the Settings app
- Smart Pixels (turn off a certain percent of pixels to save some power/reduce brightness even further to some degree)
- Always on screen
- Changing colors, fonts, QS tile styling, theming in general, the more the better, and here come the things I really really want:
- The 'CRT' lock screen animation
- The 'Type' lock screen clock (the one where instead of showing 10:19 it writes 'It's Ten Nineteen')
So, yeah, I'll be glad to hear all of your suggestions! Or, if anyone still knows anything about what happened to Bootleggers I'll really want to know

You can try Dot OS with similar features. I am sure you will like it.

mm_rajesh said:
You can try Dot OS with similar features. I am sure you will like it.
Click to expand...
Click to collapse
Oh thanks! I used dotOS before, when it was some sort of Android 8 ROM trying to look like Android 9

Aicp rom, good and without google

Another Dot OS fan...

Database Info

welcome