idle time/dim screen

[stoney66]

For echo show 8 gen2 is there a setting that will dim the screen after X minutes? I've searched around on the many different settings but nothing seems to be for this. I was hoping the screensaver idle was it, but maybe that is for slideshow only.

Clock Style = Dashboard (tried a few)
Dashboard = Drawn on device
Screen auto-brightness = on
Screensaver clock = normal (tried small and off also)
Screensaver idle wait = 5m (I assume this is for slideshow only?)

[HuskerMinion]

Not yet. Screensaver idle wait is for the slideshow only. Two things come close today: Presence detection with Screen off when nobody is near (Settings → Display → Presence) turns the screen off once the room has been empty a few minutes and back on when someone comes near; it works on the Show 8 2nd gen's camera. And Night hours dims it overnight.

[stoney66]

Hmm I don't see this open on the unit or in HA

Settings → Display → Presence

I'm on 1.6.8 currently.

[HuskerMinion]

Presence only shows up when the device finds its camera, so on your unit it isn't finding it. Does the camera itself work on yours: does a camera show in Home Assistant for the device, and is the mute button off (it turns the camera off too)?

[stoney66]

oh that makes sense... I am not sure, is the camera entity under the main device?

[stoney66]

dmesg (full boot log) shows:

kd_camera_hw1@1a040000 supply vcama_sub not found, using dummy regulator
kd_camera_hw1@1a040000 supply vcamd_sub not found, using dummy regulator
kd_camera_hw1@1a040000 supply vcamio_sub not found, using dummy regulator
kd_camera_hw1@1a040000 supply vcama_sub2 not found, using dummy regulator
kd_camera_hw1@1a040000 supply vcamd_sub2 not found, using dummy regulator
kd_camera_hw1@1a040000 supply vcamio_sub2 not found, using dummy regulator

No camera sensor ever probes on I2C after that (no success or failure line, driver just moves
on to unrelated subsystems). Only the ISP hardware blocks (cam1-cam4, generic SoC level) show
up, nothing sensor-specific.

ls /sys/bus/i2c/devices/ shows devices on i2c-1 (touch, 1-0038), i2c-2, and i2c-4 (audio
codec, 4-004c), but zero registered devices on i2c-0 — which hardware.md documents as where
the main+sub camera live. i2cdetect/busybox i2cdetect aren't available on the device to probe
the bus directly.

Lens cover physically cycled open/closed, no change.

Question: is this a known gap in camera power-rail device-tree wiring under --kernel amazon
specifically, or something else? Happy to pull more diagnostics if useful.

[HuskerMinion]

Dim after idle is in v1.6.9 (Settings → Display, or Dim after idle in Home Assistant): after the time you pick with no touch, no voice turn and nobody seen near, the screen fades to its Dimmest level.

[stoney66]

Works thanks!

Either my camera doesn't work or something else is wrong, but this fixes the dim issue ;)

[HuskerMinion]

That's expected on Amazon's kernel. TECHO5 only runs the 2nd gen Show 8's camera on the mainline kernel, which is the default install. With --kernel amazon there's no camera, so Presence detection has nothing to look at. To get the camera, reinstall without --kernel amazon.

[stoney66]

That's expected on Amazon's kernel. TECHO5 only runs the 2nd gen Show 8's camera on the mainline kernel, which is the default install. With --kernel amazon there's no camera, so Presence detection has nothing to look at. To get the camera, reinstall without --kernel amazon.

Does that work on the JD9365 screen?

[HuskerMinion]

Yes. The JD9365 with KD/HSD glass (your 0x31) is one of the two screens tested on the mainline kernel. Reinstall without --kernel amazon and the camera and Presence detection should come up.

[stoney66]

Yes. The JD9365 with KD/HSD glass (your 0x31) is one of the two screens tested on the mainline kernel. Reinstall without --kernel amazon and the camera and Presence detection should come up.

ah ok, I thought when I did this couple weeks ago I had to use the amazon kernel. I just reflashed and all good now, I can see the camera and presence settings Thanks again. Maybe the dark mode lockup was the amazon kernel :)

[HuskerMinion]

Glad it's all working, and thanks for sticking with it. If the dark mode lockup comes back on the mainline kernel, let me know on HuskerMinion/techo5-athena#4.