Screen Toggle

[janstadt]

I have ava all set up on an echo show 8 and have elevated rights to control the screen. When i switch off the screen it goes black, but when i try and switch it back on (via HASS) the screen doesnt wake up again. Im curious if others are having this issue?

My ideal use case for Ava is specifically for voice control as i'd like to use ImmichKiosk and ImmichFrame to show a slideshow continually with ava as an overlay for voice. The one thing i also want to get figured out is turning off the screen fully at night because these things are pretty darn bright, even when dimmed. If i can get that working, i think i'll finally be happy with these rooted echos!

[janstadt]

Oh, and the remote server url looks to have a 255 character limit so my immich kiosk urls arent working. They use 32 character guids for peoples face to determine what to show in the slideshow so the urls get quite long. Unsure if the char limit is on the field or a hass limitation/default?

[knoop7]

DisplayToggle.dex Core Logic

The screen on/off control in my Ava app is entirely based on DisplayToggle.dex, which directly invokes Android's underlying PowerManager service via app_process, bypassing conventional API restrictions to enforce screen wake/sleep. This logic works for most devices, but some heavily customized systems (like Echo8) may have permission interception or system service anomalies.

Local Testing and Log Collection

If screen control fails, I recommend manually verifying the underlying logic via ADB first:

# Screen off (parameter 0 represents POWER_MODE_OFF)
adb shell CLASSPATH=/storage/emulated/0/DisplayToggle.dex app_process / DisplayToggle 0

# Screen on (parameter 2 represents POWER_MODE_ON)
adb shell CLASSPATH=/storage/emulated/0/DisplayToggle.dex app_process / DisplayToggle 2

Important: Since I currently lack an Echo8 physical device to reproduce the issue, please provide complete ADB logs (adb logcat -d) when executing the above commands so I can identify whether it's a permission denial, class loading failure, or system service call exception.

Temporary Solution for Non-Root Environments

For devices like Echo8 with incomplete Root access or limited shell permissions, I recommend using Shizuku:

1. Install and start Shizuku (via wireless debugging or PC activation)
2. Enable Shizuku support in Ava settings, or replace adb shell with su -c execution mode in terminal
3. Principle: Shizuku provides user-level system API access, allowing display control commands to be injected without full Root

This is more robust than relying on unstable Root environments and represents the current best practice for such customized systems.

Detailed Explanation of the 255-Character URL Limit

This limitation is not a technical bottleneck but a security protection mechanism:

1. Preventing accidental generation: Excessively unrestricted URL input may cause WebView parsing exceptions, memory overflow, or unexpected redirects
2. Alignment with system limits: Home Assistant itself imposes similar limits on entity IDs and state value lengths (typically 255 bytes) to ensure compatibility with the HA ecosystem
3. Practical solution: For long parameters like 32-character face GUIDs (e.g., https://example.com/face/550e8400-e29b-41d4-a716-446655440000), I recommend using URL shorteners (like bit.ly or self-hosted YOURLS) before entering them, which satisfies the limit while remaining manageable