emOS v0.11-ea.1 (Early Access)
emOS on the Echo 2nd gen (radar). Early Access: only dev and EA controllers offer it; GA controllers do not see it.
New
- The Echo 2nd gen (radar) runs emOS. One init serves both Echoes and
tells them apart by Amazon's product id. Radar boots, joins WiFi, and runs
EchoMuse with no Amazon software in the path (#687, #1017). Provision it
with the wizard's emOS flow on a controller that includes #1017; radar is
not supported on FireOS.
Changed
- Echo Dot 2nd gen: nothing behaves differently. The WiFi patch helper now
pauses on an empty read instead of spinning, which radar's chip produces
between power cycles.
Upgrading
Echo Dot 2nd gen, from the dashboard (dev and EA controllers only): the
Echo's Updates tab has an emOS panel. Keep the Echo powered while it updates.
A power cut during the roughly one second in which the boot partition is
written leaves an image that cannot start, and that needs TWRP, a USB cable
and the provisioning wizard to recover. Anything that goes wrong after that
write is undone by the Echo itself, as in 0.10.
Echo 2nd gen: the provisioning wizard's emOS flow, on an Echo unlocked
with amonet-radar and carrying FireOS 6 in both slots. The wizard saves the
stock boot image first; keep that file, it is the way back. Volume up at
power-on starts TWRP on radar.
Nothing on /data is touched, so WiFi and the console password survive.
Known issues in this release
- Radar has been run on one unit (FireOS 6, NS6575), built and flashed by
hand from the wizard's own build step. A full wizard run on a fresh radar
is still owed. - WiFi on FireOS 6 with a WPA3-only network does not work and cannot: the
driver has no SAE. Use WPA2 or WPA2/WPA3 mixed (#536).
Thanks
@vithurshanselvarajah and @jcsnider, whose port in #687 found how radar's
WiFi and kernel have to be brought up.
Checksums
Verify the assets against the release page before flashing anything.