[Settings UI] Custom tinted icons in Sound & Vibration menu do not apply on initial open

[titusevan]

Issue type

User interface

Device

POCO X6 (garnet)

crDroid version

crDroid 12

Exact version / Build date

crDroid 12.10 / 2026-05-17

Bug description

[Android 16 QPR2] Settings UI: Custom tinted icons inside "Sound & vibration" menu do not apply their color on the initial window open, reverting to the default theme until the activity is backgrounded and reopened.

Steps to reproduce

1. Open system Settings.
2. Navigate to "Sound & vibration" (Звук и вибрация) menu.
3. Observe the volume slider icons on the right: some icons successfully apply the new custom accent color tint, while others remain stock/uncolored on the initial load.
4. Minimize/collapse the Settings app to the background (or go back and enter the menu again).
5. Reopen the "Sound & vibration" window — now all icons dynamically update and apply the correct custom tinted style.

Relevant log (logcat/build log)

N/A (Visual UI styling lifecycle / race condition bug during View binding)

Screenshots or videos

Solution

The issue appears to be a typical lifecycle race condition or an incomplete state binding on the initial layout inflation.

The color tinting logic for the icons (VolumeSlider or individual preference layouts inside the Sound panel) likely triggers before the custom crDroid themes/assets are fully initialized in the local Context, or it lacks a proper observer/updater during the initial onCreate / onStart pass.

Forcing the theme/tint update explicitly during the initial binding or ensuring that all volume panel icon components listen to the same theme wrapper configuration should resolve this delayed tinting issue.

Additional context

This styling inconsistency happens only on the first launch of the specific Settings sub-menu. Once cached in the memory or triggered by an activity lifecycle update (like resuming the window), the UI fixes itself.

Acknowledgements

• I've checked device is officially supported and that no support is provided for unofficial devices (for device specific reports and not source related).
• I'm running latest version available on crdroid.net for this device and that the device is still maintainer supported (not flagged unsupported on download page)
• I have searched the existing issues and this is a new and no duplicate or related to another open issue.
• I have written a short but informative title.
• I filled out all of the requested information in this issue properly and understand that not doing so will automatically result in closing of ticket.