Related
I am in the process of creating a theme and have thus far nearly completed the status bar. There are still a few icons/buttons that need to be updated and I will do so in the near future and post the updates.
Before I completely finish up the status bar and move on to another part of the theme, I wanted to get some feedback. I have posted a couple of screen shots and a MM download here.
This is a MetaMorph theme designed for the Cyanogen flavor of mod. If there is a demand, I will port to another.
Note that this is my very first attempt at a theme and have absolutely no programming knowledge. I would greatly appreciate constructive criticism and bits of knowledge to help me improve upon my new found hobby.
Current:
Version 1.0
- framework-res.apk near complete
- Nearly all icons/buttons modded
I dislike the text on the notification box/window immensely, and the colour doesn't really fit anything, unless I had a mandarin wallpaper or something. Keep on truckin'.
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
I am creating this R&D thread for a project I've been working on for most of this year.
The project named "oZoP" is an All-in-One mods/themes/tweaks for the phone.
The plan for the project is to make it a universally compatible for ALL stock based rom (AOSP is not and never will be supported or compatible)
I will probably release oZoP ConTroL as a stand alone zip mod that will do most of the work and include most or the options.
Eventually I will release the full Aroma oZoP (One Zip One Place) that will include a full rom with all bloat files (all optional of course), along with various other tools needed to build you phones setup the way you like it.
The reason for this thread is to receive valuable and needed user feedback, recommendations and requests.
The feedback will be used to build "OUR" project into a bug free, totally stable experience that will have something for everyone!!
We will get into more detail about what info is needed and how we can get it all put together.
I will add more details as I update this thread. There are A LOT of mods and a lot of info so this will take time.
If you are really that interested and just need to know more, you can always take a glance at some of my other projects,
Most of these projects are simply just sections of oZoP that have been pulled out as a stand alone mod.
Here are a few samples of the mods during the build phase (some features may or may not appear the same or make it to the initial public release)
SCREEN RECORDING VIDEO PREVIEWS
STATUSBAR SECTION:
Statusbar part.1
{
"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"
}
PULLDOWN QUICK SETTINGS SECTION:
Header
Expanded QuickSettings Count
Animated Pressed Toggle Icons
NavBar
Lockscreen
oZoP Theme Engine:
Keyboard Background (with users choice)
Keyboard key bg and text coloring
Full System Background
These are recording of the animations, but they also are a quick example of some of the options from the oZoP Theme Engine where everything you see that is themed is mix and match how ever you choose
Stock
Missing Link
Nexus 7
iOS
Flyme
Blur
Google Pixel
MIUI
Full-screen Caller ID
As you can see from what I have in the previews above There are a lot of options and configurations possibility and that's only about 1/5th of what is actually available at this point today.
With all those options come lots of possible conflicts with the various devices and variants that are planned to be on the list of compatible devices.
That brings me to the reason for this thread... I have the H918 Tmobile and may or may not need several users with other devices to be the support section to check compatibility!
To be clear, I have been building this project since March and have recently finished running clean install testing for the past 10 days to ensure all the defaults are set properly and that there are zero bugs that I can detect with my setup.
Again, just because everything works as it is intended for me with my model phone, carrier variant and app and setting setup, doesn't mean it will be the same for everyone.
This thread will hopefully eliminate any possibilities of this not working for everyone and ensures a wonderful experience
You may or may not have seen the following projects. They are in fact sections of oZoP pulled out as stand alone mods.
They have been sort of "silent" compatibility tests that have passed with flying colors. There has been no reports of things not working.
oZoP Modz - Full-screen Caller ID
oZoP MoDz - System Animations
BOOT/SHUTDOWN ANIMATION CHANGER
The next test is being announce as such and is starting taking place right here right now.
This has been tested privately for the last few days and the confirmed Roms and devices include Weta (all US carriers), NATF and one I can't remember right now
DEVICE REQUIREMENTS:
1. Rooted
2. Stock based deodex rom
oZoP MoDz Notifications and more
download Weta here
download for NATF rom
Included:
*volume slider sound toggle*
*volume panel timeout*
*remove ongoing notification for Powersave mode*
*quicksetting airplane toggle warning*
*quicksetting sync toggle warning*
*hide popup for incompatible charging slow mode*
*set trigger for low battery warning*
*set trigger for Critical low battery warning*
*home button pressed bg color*
*Google home button animation*
*colors for Google animation dots*
Report bug properly to get my support
Of course there are many way to properly report bugs and ALL of these ways have one thing in common, THEY ALL REQUIRE VERY DETAILED NOTES of the issue!
I'm moy goimg to go deep into how detailed you could get because lets face it, most people that report improperly are the ones who don't read and probably are going to read this! HaHaHa...
To get support from me I only ask for some simple things
1. What device, and rom you are running
2. What is the issue (no boot, fc everywhere, fc only certain app etc...)
3. Which option did you select
4. Did you get the install log
5. Did you use the restore.zip option to get back running
6. Do other choices share the same effect
That looks like a lot, but it really is the minimum amout of info need to troubleshoot!
Provide me that and I'll do my best to fix things and make this fun for everyone.
If you post things like
"Doesn't work", "bootloop" or anyone other similar post that have no value and help development is no way, actually these kinds of post only put development behind amd slow progress die the fact that anyone who cam help has to waste their time reading it!
If these kind of post ever come up, its best to ignore the lazy person and not clog the thread with flaming replies as that too slows development!
Feature list (WIP)(not even close to being finished and not sure I will until the project is ready for release)
|-|-|-Statusbar Launch Button-|-|-|
* position - hide, left, right or both
* Disabled*
* Screen Off*
* Home Button*
* Phone Dialpad*
* Play Music*
* Camera (LONG PRESS)*
* Browser*
* Screenshot*
* Calender*
* App Launcher - pick any app to quick launch*
* Statusbar Custom Backgrounds with the following options
* choose ANY from image gallery
* choose ANY 2 colors for Gradient with color picker
* choose ANY Solid Color with color picker
|-|-|-STATUSBAR LAYOUT-|-|-|
* arrange signals icons, network traffic info and batteries - left or right
* Time and date - left, center or right
|-|-|-CLOCK/DATE-|-|-|
* position - left, center or right
* click clock launcher - pick any app to quicklaunch - longpress to alarm settings
* seconds
* font style
* color picker for any color
|-|-|-Navigation Bar background-|-|-|
* Recent Panel Custom Backgrounds with the following options
* choose ANY image from gallery
* choose ANY 2 colors for Gradient with color picker
* choose ANY Solid Color with color picker
|-|-|--|-|-|
* Notification Pulldown Panel Custom Backgrounds with the following options
* choose ANY image from gallery
* choose ANY 2 colors for Gradient with color picker
* choose ANY Solid Color with color picker
|-|-|-EXTRAS-|-|-|
* Setup with Stangs Pick using One Click option in OC
* Restore Stock Colors Only with One Click option in OC
* Restore Stock Entire System Values with One Click option in OC
* 10 Quick Pick color for text, Icon and accents with One Click option in OC
* Bypass pin request with fingerprint on reboot
* 360° Rotation with toggle
XDA:DevDB Information
oZoP R&D, Device Specific App for the LG V20
Contributors
stangdriver44
Version Information
Status: Testing
Created 2017-11-12
Last Updated 2018-05-05
Reserved
Chromed Navbar Icons check this post
iOS signalbar style check this post
This is a patch made specifically for the v20 mods by Zach 4-30-18 version
The patch is to remove the dependency for a pin to be entered while using fingerprint lock security after a reboot
[URL="https://forum.xda-developers.com/attachment.php?attachmentid=4493876&stc=1&d=1525547163]DOWNLOAD_fixed version[/URL] and flash in recovery
Just curious I could have missed it but will the ability to turn off the annoying battery full notification be included in the mods? And any chance the ROM could include WETA like abilities to modify what is on the second screen (ie: 3min clock)?
Thanks for sharing all this by the way. Exciting times for our V20!
I noticed today that if I do a bulk execute on the second screen mods work on weta. But if I try to just modify them under ui mods individual it causes the system ui to crash. I'm on Verizon weta 5.1 #2
Sent from my VS995 using Tapatalk
how to restore??
I want go back cause 3mint battery is not work;;
sorry.I don't have a backup file.
inside your file restore option is fail
sorry..I'm a korean,my english level is veryX100 low..
this post from my ls997
james_pnut said:
I noticed today that if I do a bulk execute on the second screen mods work on weta. But if I try to just modify them under ui mods individual it causes the system ui to crash. I'm on Verizon weta 5.1 #2
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Same issue had to reflash entire rom to fix
I have not flashed this yet but your previews are amazing! Can't wait to try these and upcoming features. Great work!
AngryManMLS said:
Just curious I could have missed it but will the ability to turn off the annoying battery full notification be included in the mods? And any chance the ROM could include WETA like abilities to modify what is on the second screen (ie: 3min clock)?
Thanks for sharing all this by the way. Exciting times for our V20!
Click to expand...
Click to collapse
For the clock I have mod native built with control of many thing which do include layout position. I also have native build battery controls including the option to switch between stock modded or 3 minit batteries.
I have stock battery position left/right, but so far it doesn't work right for second screen so the battery will be in the stock position on the right for now.
The reason for this thread is for suggestion, recommendations.
That being said, i currently do not have a switch for the full battery notification.... Currently... I will be adding that and you can expect to see it in the official release!
Thank you
james_pnut said:
I noticed today that if I do a bulk execute on the second screen mods work on weta. But if I try to just modify them under ui mods individual it causes the system ui to crash. I'm on Verizon weta 5.1 #2
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
highgel said:
I want go back cause 3mint battery is not work;;
sorry.I don't have a backup file.
inside your file restore option is fail
sorry..I'm a korean,my english level is veryX100 low..
this post from my ls997
Click to expand...
Click to collapse
DesertEagleSlim said:
Same issue had to reflash entire rom to fix
Click to expand...
Click to collapse
For the 3 replies about having compatibility issues, I want to say this does not come to a surprise and I can assure you that this will not be the case with the official release.
I suspect the reason for this fc issue is because WETA is a very customized rom and some of the mods are probably pushing files the the sysui which I modded and the old files are conflicting because they do not include the referances to the edits I made for the animated home button etc.
This will not be an issue when all the oZoP files are in place.
So i also want to clear this up...
Once the official oZoP is ready and gets installed on to your rom, it will override ALL current mods of your rom. The mod includes most core system files that devs mod.
Don't worry though, i am pretty sure that ANY mods you currently have will be available with oZoP.
If we find out that there is a mod which I haven't included, just let me know and i will definitely do what i can to add the feature.
Sorry for the inconvenience. I will make things more clear for the future as well as add a restore failsafe to the zips.
Bubba Fett said:
I have not flashed this yet but your previews are amazing! Can't wait to try these and upcoming features. Great work!
Click to expand...
Click to collapse
Thank you sir and the previews don't give any justice to what is really going on!! This will definitely keep you busy for a while. There are a lot of variations of the mods amf theme options!
Thank you all for the replys and feedback.
Remember, this is the time and place to make requests for things you would like to see built in to a stock based rom!
Cant wait for your rom. It looks sick!
stangdriver44 said:
Remember, this is the time and place to make requests for things you would like to see built in to a stock based rom!
Click to expand...
Click to collapse
I think it would be cool to have a working color coded battery bar for the second screen especially for the AOD part as it's easier to read than a small white battery icon and even the 3minit battery is still pretty tiny when trying to see it at a glance. Not sure if it is do-able
2nd screen is awesome on this phone just wish there was more ways to customize it. Be nice to force it to max brightness as well as being able to increase the time it displays notifications like text messages and stuff.
KUSOsan said:
I think it would be cool to have a working color coded battery bar for the second screen especially for the AOD part as it's easier to read than a small white battery icon and even the 3minit battery is still pretty tiny when trying to see it at a glance. Not sure if it is do-able
2nd screen is awesome on this phone just wish there was more ways to customize it. Be nice to force it to max brightness as well as being able to increase the time it displays notifications like text messages and stuff.
Click to expand...
Click to collapse
Again, thank you and this is what this thread is about, getting things we all want in one mod!
So for battery bar in SS, i already have the options for top/bottom placement, regular (left to right) or centered style, charging animation on/off, size and colorpicker for any color. I do not have it color coded, I assume you mean by percentage of battery remaining?
I can definitely look at adding to my code, but that may come in future updates...
As for the other battery options, stock battery is only white if you choose to leave it that way. The battery icon has color optiins for background, foreground and in-battery precentage colors. The icon has several styles including hide, circle and dotted cirlces. 3minit is 3minit, no need to go into that one.
As you can see, there are currently options that could hopefully satisfy your battery needs.
I totally aggree about needing more controls for SS options like brightness and screen notification timeouts.
@Zacharee1 and I have been looking deeper to add options for pulse and text color controls, but again this one may have to be for future updates as well...
Thank you for your interest and participation here.
Thanks for taking time to clear up as to why we're having issues. Your mods are awesome. And I commend you for putting the time in to do this for this phone. ?? ?? Im sure everyone in this forum with this phone is extremely grateful to you for doing this, as we don't have many choices for roms and such for a phone that is a year old. It amazes me, my old old HTC desire and galaxy s4 are still getting roms released yet this phone is all but abandoned. Lol anyway thank you immensely and I look forward to the finished product. (I will also beta test any releases you push if needed)
DesertEagleSlim said:
Thanks for taking time to clear up as to why we're having issues. Your mods are awesome. And I commend you for putting the time in to do this for this phone. ?? ?? Im sure everyone in this forum with this phone is extremely grateful to you for doing this, as we don't have many choices for roms and such for a phone that is a year old. It amazes me, my old old HTC desire and galaxy s4 are still getting roms released yet this phone is all but abandoned. Lol anyway thank you immensely and I look forward to the finished product. (I will also beta test any releases you push if needed)
Click to expand...
Click to collapse
Thank you for the patience and understanding of working through things!
I don't plan on getting a mew phone for at least another yr so you guys are should get ready for a fun ride on oZoP!
@KUSOsan just finished up the Full battery switch and love your suggestions so keep em coming. There can't be that many left.. Haha that mod make puts the total keys used for included mods at 407! Thats 407 different settings some pf which include 50+ choices!
Do the math, its basically unlimited possibilities!
stangdriver44 said:
Just finished up the Full battery switch and love your suggestions so keep em coming.
Click to expand...
Click to collapse
I need to write them down because I can never think of stuff on the spot but it's always whenever the problem arises.
Most of my suggestions pretty much center around the 2nd screen as there is just a disappointing lack of customization for it considering that is the biggest defining feature about the V20.
I was hoping LG would add more stuff to it after they talked big about focusing on the 'V' series as their main contender with the G series taking a backseat compared to it but with the V30 coming out sans a 2nd screen I have a bad feeling that if anything they are going to abandon any 2nd screen updates completely or just streamline it (i.e. neuter it with less features but make it look prettier) for the Oreo update if this phone ever gets it.
I also have a bad feeling that Oreo is going to be a long ways out for this phone so your timing with the mods and ROM are perfect ?
I'm extremely interested in this ozop rom. Thanks for puting all you time and effort into this. Will this work for the sprint ls997 model? If so which rom will we need to be running?
stangdriver44 said:
Do the math
Click to expand...
Click to collapse
I remember a certain game company used that slogan for their Jaguar console. :silly:
Jokes aside thanks for answering my questions earlier. Looking forward to the ROM when it comes out.
The latest mod addition to join the oZoP arsenal of mods!
Navbar Music Visualizer
Still working pn a couple of user requests, but so far I've been able to deliver on most of the user requests I've gotten so far!
So if there is something you've seen or not see anywhere let me know about it with any resource links/details and I'll do my best to bring it to oZoP MoDz!
I wish all you Americans Happy Thanksgiving and good day to everyone!!!
stangdriver44 said:
The latest mod addition to join the oZoP arsenal of mods!
Navbar Music Visualizer
Click to expand...
Click to collapse
Can you share the instruction manual for android 7.0 Samsung?
Nice work bro ... I still have my v20 on probably I'II Jump to play with this new rom wend come up .
thanks on advance
Waiting mode ...lol ?
I will literally be flashing this rom (if/when) he makes it within minutes of it being uploaded. And I immediately flash every mod he does. Absolutely amazing work. I cannot thank you enough. If u need any beta testing please PM me. Deserteagleslim is my name on everything yahoo, Gmail, telegram, aim, Twitter, Facebook, Instagram everything. Easy to find me. Please let me know.
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.
Now in every new android release since kitkat there has been regressions, but in PIE I noticed this one has a fair few so I googled and I observed that almost every article was only praising the release as if they just there to promote and suck up to google developers.
Then I found this very honest post from a guy on reddit.
https://old.reddit.com/r/Android/co...eatures_since_the_pie_update_and_the/ejrdwnp/
I will quote also.
Neutered navigation bar with an increased focus on gestures rather than buttons (wit the bar using up the same amount of space with decidedly half-baked gestures). Some companies at least maintained the options of buttons or gestures, but I think the Google Pixel 3 prevents users from having the option of using the classic navigation buttons.
Horizontal Recents/Overview screen instead of a vertical variant - this "feature" is more subjective, I guess.
Enforced 3-icon limit for notifications in the status bar, all thanks to notches - for certain phones, this change completely removed the option to have as many icons in the status bar as you have space for.
The Digital-Clock/Time's position was enforced on the left instead of the classic right-side position - again, all thanks to notches..
The Volume Slider got changed to a "vertical" variant if I recall correctly, and I think that certain volume sliders can only be changed by actually diving into Settings, whereas the Android 8/Oreo implementation gave a simple quick drop-down to change all 4 at once, and Samsung even added the option to switch the controlled volume default from Ringtone to Media.
Removal of easy access to viewing System Uptime in Android Info (WHY? It's a useful metric that just sits there harmlessly!).
The DevCheck application thankfully still indicates System Uptime, although the read-out isn't as "fluid" (doesn't refresh as much) from what I've seen.
Neutering of the "Quick Toggles" pop-up thing, where you can adjust certain quick-toggles' settings quickly without actually diving into the Settings screen.
certain "Do Not Disturb" mode capabilities/workflows that were possible in Android 8/Oreo are apparently harder, if not impossible, to achieve in Android 9/Pie.
I think that the Android 8/Oreo Easter Egg got removed..? (if one counts that as a feature).
Call Recording got heavily hampered.. I'm not sure of Screen Recording... Custom theming on Samsung devices also seems like it will be harder to achieve in the near future (going by a recent changelog entry for the "Theme Galaxy" application), although "One User Interface (One UI)" seems to be softening the blow.
as others have mentioned, the method to access Android-native "Split-screen/Multi-Window view" has been altered a bit...
Click to expand...
Click to collapse
For me on a personal level the nasty ones are the removal of battery saving location from UI (the underlying code still supports it), removal of expanded controls from quick toggles, and the call recording hampering.
Now personally I dont think I have recorded more than a few calls in my lifetime on a smartphone, but I believe in user's been in control of their own device and user choice. The change to quick toggles is just mind baffling and makes no sense whatsoever, the changes to GPS may possibly make sense but it needs to be explained to users, instead of just silently removing the feature and have the media pretend its not happened.
Their minds would be better focused on fixing the flaws in the UI so e.g.
Black themes that are inconsistent so e.g. I have a black theme enabled but the navigation bar is white, and the notification boxes are white.
More control over UI elements, allow more freedom to do things like resize notification boxes (they way too large on stock android), reposition every icon and so forth. No choice on vertical or horizontal recent apps screen.
Consistency in UI, so e.g. on quick toggles when expanded you see text labels, when not expanded you dont, there is no reason for that, its just bad consistency.
I also hear of future regressions like plans to replace navigation buttons entirely with gestures, that I think is a disaster in the making as many users dont use gestures, and prefer buttons.
I think its clear changes are been made for the sake of change rather than functional improvement. I feel android UI peaked with kitkat.
Ironically that reddit thread has people praising samsung for adding sanity and reversing the changes, google dont like samsung changing the UI, but you cannot blame samsung when google are doing stupid things to the UI.
I am half tempted to go back to samsung on next phone, my oneplus6 is lightning fast tho and my s7 is really laggy and slow by comparison. But there is no doubt samsung phones have a better UI and feature set.
One thing that has always baffled me, is some users on XDA feel they must always be on the latest version of android, I seen users abandoning things like xposed, useful mods etc. just because they only support a rom version that might only be a few months out of date. This is baffling when you consider that new android versions usually have more regressions than new useful features. As an example on oneplus6 people are abandoning renovate ice because it only supports up to 9.0.6.
I will probably add my own quick toggles with tasker for GPS modes, still looking for call recording solution, as well as black notification theming, I expect the theming for navigation bar is not fixable tho. I had black notifications on havocos and to say they look better is an understatement.
Google sort out your UI department as its pretty bad right now.
rant over.
Also to mods if this post is in the wrong place, please move it rather than just removing it or warn me before removal so I can copy and paste the content to repost in right place, thanks.
Should have posted this on Google's forum, not a hacking forum