On Android 14 no effect
Opened this issue · 3 comments
Unclelon commented
I guess the reason is that all parameters of your app changes in the global database.
Please consider that under Android 14 all the doze parameters are written in the device config and only there you can change doze parameters.
Here's the ADB command to do so:
device_config put device_idle
Please mark it in your description
farfromrefug commented
@Unclelon thanks for the report. So you are saying that instead of doing settings put global device_idle_constants TUNE_TABLES
, on android 14 i should do device_config put device_idleTUNE_TABLES
?
Unclelon commented
Hello, yeah like this:
device_config put device_idle inactive_to 0;
device_config put device_idle sensing_to 0;
device_config put device_idle locating_to 0;
device_config put device_idle quick_doze_delay_to 0;
device_config put device_idle motion_inactive_to 0;
device_config put device_idle motion_inactive_to_flex 0;
device_config put device_idle idle_after_inactive_to 0;
device_config put device_idle
light_idle_to 3600000;
device_config put device_idle
idle_to 7200000;
device_config put device_idle min_time_to_alarm 14400000;
dumpsys deviceidle force-idle
Greez Uncle Lon
…-------- Ursprüngliche Nachricht --------
Von: farfromrefuge ***@***.***>
Gesendet: 14. November 2024 12:20:03 MEZ
An: farfromrefug/EnforceDoze ***@***.***>
CC: Unclelon ***@***.***>, Mention ***@***.***>
Betreff: Re: [farfromrefug/EnforceDoze] On Android 14 no effect (Issue #6)
@Unclelon thanks for the report. So you are saying that instead of doing `settings put global device_idle_constants TUNE_TABLES`, on android 14 i should do `device_config put device_idleTUNE_TABLES`?
--
Reply to this email directly or view it on GitHub:
#6 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
VG Dirk Runge (ツ)
farfromrefug commented
@Unclelon ok i see so it is one by one. Will try to find the time to fix this.