when using basic getter, it may lead to incorrect value on multi user setup
since it depends on uid from the particular context instead of the actual
current user.

- Reduce expanded bar padding
- Make expanded bar background semi transparent just like pixel
- Tint bar background with pure black color for better contrast in-game
- Workaround compoundDrawable tint issues on android-12.0.0_r30

Translated-by: volododya <https://t.me/volododya

>
Signed-off-by: Nauval Rizky <enuma.alrizky@gmail.com>

Signed-off-by: elizabethangelalorenza <elizabethangelalorenzha@gmail.com>

Change-Id: I5ca0b3905ebfb7200cd04bfae28ad1feb06d1a55
Signed-off-by: NurKeinNeid <mralexman3000@gmail.com>

Change-Id: Ic08c97b1cadb1e4aaef5da4fa593ab1fa63b25d9
Signed-off-by: NurKeinNeid <mralexman3000@gmail.com>

Some device maintainer may want to opt-out this feature from device tree
via overlay due to their unstable graphics stack.

people are annoying when they saw 59 instead of 60, or 89 instead of 90.
So lets round it up when it's even.

Since we already have proper screen state handling on the systemui,
let's clean things up and remove some other unneeded stop handling
while at it.

Seems AndroidEntryPoint for custom view only accept Activity/Fragment
components, so for now we can only use custom EntryPoint.

Since START_REDELIVER_INTENT is just too slow, we can just grab
topActivity from ActivityTaskManager and then recreate the intent for
onGameStart usage.

gameBar may already be killed by system, thus will cause few exceptions
and prevent bar from getting started on next onStartCommand.

Thanks to jhonboy121@AOSP-Krypton for the hilt commits on his forked
exTHmUI GamingMode.

Change-Id: Ibfa0f632d9acbb920a85a613ce4e2f1d26556be2
Signed-off-by: NurKeinNeid <mralexman3000@gmail.com>

Many people finds that rounding up the value is not right
So lets drop it instead

With this we can have more stable framerate listener since it tied
together with it's own view lifecycle.

With BroadcastReceiver approach in previous changes, we can finally let
system handle the game session start and ending.
There's no need for almost-lifetime app service in the background, which
is a huge deal in terms of efficiency.

Device maintainer may want to add additional tuning when game is
active, for example : applying device-specific optimization via
DeviceParts app.

shell command does not really works, so better just nullify it instead
since it has the same effect as DeviceConfig's resetToDefaults()

At this point, TaskListener gets too many job to be called as a task
stack listener, lets split it up.
And while on it, lets start think multi-process for future usecase.

No Tile because you can just switch it from volume panel or hw slider ))

With this way, we can have better handle over staled session that caused
by so many external factors on android (crashes, low-memory situations, etc).

This reverts commit d9da06682a661fd8500a19ff80113a2e4427c70c.

there's a chance that session got nullified before restoration happens

When enabled, this will acquire wakelock so device will not going to
sleep state, just like caffeine QS Tile.

It'll automatically disabled when user press the power button to sleep,
or when user leaves the game.