Related to [Benjamin_Loison/Voice_assistant/issues/18#issuecomment-4414487](https://codeberg.org/Benjamin_Loison/Voice_assistant/issues/18#issuecomment-4414487).
Disabling screen lock while ADB is running is an alternative but in the case of the voice assistant may not that be relevant but note that to change this setting need ADB.
Disabling screen lock while ADB is running is an alternative but in the case of the voice assistant may not that be relevant but note that to change this setting need ADB.
for section in global system secure
doecho$section
adb shell settings list $section| grep 120done
Output:
global
wifi_power_save=120
system
screen_off_timeout=120000
secure
<details>
<summary>Bash script:</summary>
```bash
for section in global system secure
do
echo $section
adb shell settings list $section | grep 120
done
```
</details>
<details>
<summary>Output:</summary>
```
global
wifi_power_save=120
system
screen_off_timeout=120000
secure
```
</details>
for section in global system secure
doecho$section
adb shell settings list $section| grep -E 'stay|awake'done
Output:
global
stay_on_while_plugged_in=0
system
secure
<details>
<summary>Bash script:</summary>
```bash
for section in global system secure
do
echo $section
adb shell settings list $section | grep -E 'stay|awake'
done
```
</details>
<details>
<summary>Output:</summary>
```
global
stay_on_while_plugged_in=0
system
secure
```
</details>
See [Benjamin_Loison/Voice_assistant/commit/255c5d9e3288e61a22fa00aede3bf2e5d13b76dc](https://codeberg.org/Benjamin_Loison/Voice_assistant/commit/255c5d9e3288e61a22fa00aede3bf2e5d13b76dc).
So as long as click once on the screen for instance to trigger listening before the screen timeout it is fine.
Even with graphical longest setting of 30 minutes, it means that should not tap to listen for this period of time to be locked out which is a not a so frequent scenario I guess.
So as long as click once on the screen for instance to trigger listening before the screen timeout it is fine.
Even with graphical longest setting of 30 minutes, it means that should not tap to listen for this period of time to be locked out which is a not a so frequent scenario I guess.
...
INFO | Boot completed in 213986 ms
INFO | Increasing screen off timeout, logcat buffer size to 2M.
WARNING | adb command '/usr/bin/adb -s emulator-5554 shell settings put system screen_off_timeout 2147483647 ' failed: 'adb: device 'emulator-5554' not found'
WARNING | adb command '/usr/lib/android-sdk/platform-tools/adb -s emulator-5554 shell settings put system screen_off_timeout 2147483647 ' failed: 'adb: device 'emulator-5554' not found'
WARNING | adb command '/usr/bin/adb -s emulator-5554 shell settings put system screen_off_timeout 2147483647 ' failed: 'adb: device offline'
WARNING | adb command '/usr/lib/android-sdk/platform-tools/adb -s emulator-5554 shell settings put system screen_off_timeout 2147483647 ' failed: 'adb: device offline'
...
until the emulated device started, then there is no such every few seconds output anymore.
On first start:
```bash
/usr/lib/android-sdk/emulator/emulator -avd Google_APIs_PlayStore
```
<details>
<summary>Output:</summary>
```
...
INFO | Boot completed in 213986 ms
INFO | Increasing screen off timeout, logcat buffer size to 2M.
WARNING | adb command '/usr/bin/adb -s emulator-5554 shell settings put system screen_off_timeout 2147483647 ' failed: 'adb: device 'emulator-5554' not found'
WARNING | adb command '/usr/lib/android-sdk/platform-tools/adb -s emulator-5554 shell settings put system screen_off_timeout 2147483647 ' failed: 'adb: device 'emulator-5554' not found'
WARNING | adb command '/usr/bin/adb -s emulator-5554 shell settings put system screen_off_timeout 2147483647 ' failed: 'adb: device offline'
WARNING | adb command '/usr/lib/android-sdk/platform-tools/adb -s emulator-5554 shell settings put system screen_off_timeout 2147483647 ' failed: 'adb: device offline'
...
```
</details>
until the emulated device started, then there is no such every few seconds output anymore.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Related to #19.
Related to Benjamin_Loison/Voice_assistant/issues/18#issuecomment-4414487.
I verified with https://www.online-stopwatch.com that current 2 minutes screen timeout is enforced.
on my Fairphone 4 LineageOS 22.2 while being wireless debugging it from itself.
Disabling screen lock while ADB is running is an alternative but in the case of the voice assistant may not that be relevant but note that to change this setting need ADB.
Bash script:
Output:
Preferably I would like an indefinitely setting.
Note Stay awake.
Bash script:
Output:
When I toggle graphically the setting:
Related to Benjamin_Loison/Voice_assistant/issues/15.
In the context of the voice assistant need both as while driving the phone is probably charging but under the shower it might not.
For the voice assistant I assume that either a decent number of seconds (strictly more than 1) or a proposed option has been selected.
Can't we set a value such that it is always unlocked? In theory can set an arbitrary high number of minutes.
See Benjamin_Loison/Voice_assistant/commit/255c5d9e3288e61a22fa00aede3bf2e5d13b76dc.
So as long as click once on the screen for instance to trigger listening before the screen timeout it is fine.
Even with graphical longest setting of 30 minutes, it means that should not tap to listen for this period of time to be locked out which is a not a so frequent scenario I guess.
Related to Benjamin_Loison/Voice_assistant/issues/75.
Related to Benjamin-Loison/cinnamon/issues/197.
On first start:
Output:
until the emulated device started, then there is no such every few seconds output anymore.
Related to Benjamin_Loison/Backup_Android_apps/issues/40.
Would help Benjamin_Loison/Backup_Android_apps/issues/26.
Related to Benjamin_Loison/Backup_Android_apps/issues/48.