Debloat any Android or Google TV over Wi-Fi and get an Apple TV-style home.
Python adbadblockandroid-tvandroid-tv-launcherapple-tvbloatware-removalclaude-codedebloatfire-tvgoogle-tvlauncherprivacysmart-tvsony-braviatclvibe-codingxiaomi
examples: X.Vision 50XYU765, a CEC wake comes up on Home, not on the HDMI input
Elyas997b68f889d3
diff --git a/examples/xvision-50xyu765/README.md b/examples/xvision-50xyu765/README.mdindex ca07edd36..8f7161bf6 100644--- a/examples/xvision-50xyu765/README.md+++ b/examples/xvision-50xyu765/README.md@@ -66,8 +66,9 @@ instead (see "Inputs pill" below), so the names only show where the dropdown is- **Wake and standby are two more switches, both off by default.** `hdmi_control_auto_wakeup_enabled` lets a devicewake the TV: with it on, the PS5's `<Text View On>` arrived when it was switched on.`hdmi_control_auto_device_off_enabled` makes the TV broadcast `<Standby>` when it is switched off; the TV sent it,- but this PS5 stayed on. On the next wake the TV sends `<Request Active Source>`, a PS5 that is still on answers,- and the set comes up on its HDMI input rather than on Home.+ but this PS5 stayed on. On the next wake the TV sends `<Request Active Source>` and a PS5 that is still on answers+ with `<Active Source>`, but the set stays on Home: CVTE's own handler did not switch input, so pick the PS5 from+ Inputs. Waking the TV from the PS5 also came up on Home.- **The remote goes to the device.** On a CEC device's input the TV forwards the remote's keys as`<User Control Pressed>`; the PS5 ignored them, so the remote looked dead there. Home is not forwarded and returnsto Home; the PS5 itself is driven with its controller.