The Echo Show 8 1st gen (2019, crown) runs TECHO5. It installs with the same one command as the
Show 5, from this release, and it is the reason this is 0.8.0 rather than another 0.7.
With it, every Amazon Echo that can be unlocked now runs this daemon: the Echo Dot 2nd gen, the Echo
Spot, both generations of Echo Show 5, and now the Show 8. The unlock these devices are opened with
reaches five Echos and no more; everything else it opens is a Fire tablet.
What works on the Show 8, on the one unit it has run on: the 1280x800 screen and its touch, all four
microphones, wake word, the speaker through the Show 8's own tuning, the camera, the physical lens
cover, the mute latch, Bluetooth, Wi-Fi, phone calls, and slot updates - installed, trial-booted,
committed, and a power cut partway through did no harm. Read the caveats before you start: it has run
on one unit for a day, against two years of daily use behind the Show 5. Two things to know first - a
seller's model number does not tell the two Show 8 generations apart, so go by the year when buying
second-hand, and cycling the mute latch stops the camera until the unit is rebooted. The daemon says
so when it happens.
The documents now carry the recipe for building a Show 8 kernel and boot image, which was the part
missing rather than any code: crown_defconfig, the microphone patch it needs, and which donor image
to build against.
A Spot that was muted last time is already cutting before its first frame is captured. The Spot has
no hardware that cuts its microphones - the mute is the daemon's own - and what restored it ran after
capture had already started. Every frame in that window was handed on for real, into the pre-roll
history and into wake detection: a wake word spoken then started a turn on a device its owner believed
was deaf. Under a second, and every boot. Spot owners get this in spot-v0.4.15.
Pressing Install twice no longer reports the update as failed. The second press is refused because
one is already running, which is right - but the device answered by flashing the failure pattern and
telling Home Assistant the update had failed, while the first one carried on and succeeded.
A device is not taken for a Show 8 because it happens to carry one of its files. A Show 5 1st gen
ships an EQ_30.cfg too, which was what identified the Show 8. No Show 5 was ever tuned wrongly, but
the rule was wrong: a Show 8 is the device with an EQ_30.cfg and no EQ_60.cfg.
The installer refuses to run against a unit that already has a slot store. It would have erased it,
and the store holds the only copy of that unit's vendor tree once LineageOS is gone - so there was
nothing to rebuild from. The only guard was a typed prompt that --force skipped.
Smaller: the Stop, Snooze, Answer and Decline buttons match the rest of the device; a tap on the
setup page can no longer answer for you before anything is drawn; the screen draws at its panel's size,
which is pixel for pixel unchanged on a Show 5; the install guide says plainly that the rescue
environment has no network way in unless a key is already on the unit.
Verify this release was built by CI from its own tag:
gh attestation verify echod-arm --repo HuskerMinion/techo5 --source-ref refs/tags/v0.8.0