Concerning the requirement of root, you can enable Rooted Debugging in the Developer options (tap the Build number in the settings a few times to make them visible). Not every Android flavour has this, but /e/OS in a growing number of builds has.
This gives root privileges only to ADB, so a requirement of root for executing certain ADB commands would be met.
Thanks for the tip, I didnât know that.
Unfortunately the adb shell cmd overlay enable com.android.theme.color.purple still gives an error.
I found the command: shell cmd overlay list which results to:
com.android.networkstack
[x] com.android.networkstack.overlay
android
[ ] com.android.internal.display.cutout.emulation.corner
[x] org.lineageos.overlay.customization.blacktheme
[ ] com.android.internal.display.cutout.emulation.double
[ ] com.android.theme.icon.pebble
[ ] com.android.theme.icon.square
[ ] com.android.internal.systemui.navbar.gestural_wide_back
[ ] com.android.theme.icon.vessel
[ ] com.android.theme.icon.taperedrect
[ ] com.android.internal.display.cutout.emulation.hole
[ ] com.android.internal.display.cutout.emulation.tall
[ ] com.android.internal.systemui.navbar.threebutton
[ ] com.android.internal.systemui.navbar.twobutton
[ ] com.android.internal.systemui.navbar.gestural_extra_wide_back
[ ] org.lineageos.overlay.font.rubik
[ ] com.android.theme.icon.teardrop
[ ] com.android.theme.font.notoserifsource
[ ] com.android.internal.display.cutout.emulation.waterfall
[ ] org.lineageos.overlay.customization.navbar.nohint
[ ] org.lineageos.overlay.font.lato
[ ] com.android.theme.icon.squircle
[x] com.android.internal.systemui.navbar.gestural
[ ] com.android.theme.icon.roundedrect
[ ] com.android.internal.systemui.navbar.gestural_narrow_back
[ ] com.android.internal.systemui.onehanded.gestural
com.android.launcher3
[x] com.android.launcher3.overlay
com.android.wifi.resources
[x] com.android.wifi.resources.fairphone.FP3
com.qualcomm.qti.poweroffalarm
[x] foundation.e.poweroffalarmoverlay
com.qualcomm.embms
[x] foundation.e.embmsoverlay
As the commands related to accent colors are not listed I think it means that its not available.
Did you execute adb root before that? (Perhaps I should have mentioned that.)
No I did not, thanks for that, but sadly after executing it the list remains the same. So it seems Iâll have to wait for the developers to enable it maybe one day?
I forgot about this subject until now. Tried again on Essential PH-1 with 1.8.1-q-dev and T2e emerald with 1.8.1-r-dev. Worked on both.
Being rooted, however, I was able to do the cmd command in the terminal. Havenât tried but I assume it will work via adb since both builds are dev and have rooted debugging.
Having a choice between stable and dev builds for the emerald I think I intentionally went back to dev (when I had to do a reflash from scratch) for the rooted debugging. Just in case I decided not to root.
In my understanding, the problem is that it changed with Android S. I have a FP3 and my version is 1.9-s-dev.
Or at at least I did not manage to make it work.
Ah, okay. Not on Android 12 but yeah, that could be the case. Letâs see what others say.
My experimentation with Samsung A3 (2016) 1.9-q-20230312268823-dev-a3xelte was unsuccessful even on Android 10. Agreed @Lanky, Android 12 sounds to be unresponsive to this method, from what I read.
Firstly, slightly odd to see that in searching the full output of the following command âblueâ is not even found as preselected item
$ ./adb shell
a3xeltexx:/ $ cmd overlay list
android
[snipped content]
[ ] org.lineageos.overlay.accent.black
[ ] org.lineageos.overlay.accent.brown
[ ] org.lineageos.overlay.accent.green
[ ] com.android.theme.color.cinnamon
[ ] com.android.theme.color.black
[ ] com.android.theme.color.green
[ ] com.android.theme.color.ocean
[ ] com.android.theme.color.space
[ ] org.lineageos.overlay.accent.orange
[ ] org.lineageos.overlay.accent.purple
[ ] org.lineageos.overlay.accent.yellow
[ ] org.lineageos.overlay.accent.blue
[ ] org.lineageos.overlay.accent.cyan
[ ] org.lineageos.overlay.accent.pink
I can attempt
a3xeltexx:/ $ cmd overlay enable org.lineageos.overlay.accent.green
⌠and now see
a3xeltexx:/ $ cmd overlay list
android
[ ] org.lineageos.overlay.accent.black
[ ] org.lineageos.overlay.accent.brown
[x] org.lineageos.overlay.accent.green
[snip]
This screenshot shows that the enable command was received by the device ⌠but the actual change in accent colour never happened. Same result using other colours and root.
Changes successfully reversed with
1|a3xeltexx:/ $ cmd overlay disable org.lineageos.overlay.accent.green
Hey everyone, as you noticed the commands donât work anymore with android 12. The only way I found to change the colors was by using PowerShade from the app store which requires horrible rights to your device to work.
I would be super glad for a workaround, but searching for hours I couldnât find a solution to change the color.
The only lead I found (and not tested) is this tutorial, but it seems fairly complicated, just for having accent color.
Maybe because of this: 4634-R-Disable_multiple_color_choose_for_custom_theme (9dec92c8) ¡ Commits ¡ e / os / android_packages_apps_ThemePicker ¡ GitLab
1 Like
Will we ever get this feature back? The default color affects some Material You apps and it can be often too dark for some views, causing bad contrast that can be hard to see for some people. Please let users change it to their needs, thanks.
3 Likes
Any opinions if I risk breaking something trying the adb command from above on /e/-R (Android 12)?
R=Android 11, S=Android 12.
But no, you wonât break anything. Either it works or it will not. Give it a try.
Note, if one is rooted one can do the command in a terminal, minus the adb part.
The lack of feedback from developers is incomprehensible, and the âbecause I said soâ kind of attitude makes me sick. This is not a community, is someoneâs garden.
With Lineage4MicroG accent colors work fine, soâŚso long
2 Likes
Any updates about the colour change?
Maybe good news for Android 13? 
The good news is that the setting is entirely gone, so we can concentrate on other things 
. (At least I canât find it anymore on 2.1-t-20240605406922-dev-FP3.)
The old issue about this was closed with status âwonât doâ.
Manoj told that âThe reason for disabling has more to do with it not matching our UI guidelines. The effort to customize it is too complex plus the amount of testing required will be time-consuming. Hence it has been disabled.â (Week 17 2024: Development and Testing Updates - #17 by Manoj)
Sadly, I think the chances to have this feature back are low.
1 Like
Wouldnât they have to rewrite their apps for Material 3 at some point in time? Maybe not now, but in the future, Material 3 will be the standard, and Material 2 will look ugly because its uncommon. Since Dynamic color is pretty much built-in to Material 3, the Problem could be solved then, right? Or will I never be able to change the color?
This topic was automatically closed after 2 days. New replies are no longer allowed.