github wilbowes/EchoMuse emos-v0.10
emOS emos-v0.10

3 hours ago

emOS v0.10

The first emOS that can be updated over the network, and that undoes an update that does not work.

New

  • An update is on trial until the controller sees the Echo again. When
    the controller installs a new image it marks it, and removes the mark once
    the Echo has reconnected on that image. Until then the Echo restarts itself
    after 3 minutes, and after three tries it puts the previous image back and
    shows an amber ring — about 11 minutes in all. Before this, a new image with
    broken WiFi stayed broken until someone power-cycled it three times, and one
    that got an address but could not run EchoMuse was kept (#573).
  • A rollback leaves a record that the controller reports in the Echo's
    log, so "it rolled back" is something the Echo said, not a guess.

Fixed

  • FireOS 6: the Echo now gets a DHCP lease from servers that only answer by
    broadcast (#704).
  • FireOS 6: IPv6 is switched off where emOS cannot filter it. These Echoes
    were accepting inbound IPv6 unfiltered; nothing in EchoMuse uses it (#702).

Upgrading

From the dashboard (needs a controller newer than 2.25.0): 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.

With controller 2.25.0 or earlier: re-run the provisioning wizard's build
and flash steps, as for 0.9.

Either way nothing on /data is touched, so WiFi and the console password
survive. To accept a new image by hand from the console instead of waiting
for the controller: rm /data/emos/update.pending.

Known issues in this release

  • WiFi on FireOS 6 with a WPA3-only network does not work and cannot: the
    driver has no SAE and the kernel is too old for us to do it in userspace.
    Use WPA2 or WPA2/WPA3 mixed (#536).
  • The rollback record was added after the hardware run that exercised the
    rollback. The rollback itself was run on an Echo; the record is covered by
    the off-target check only.

Thanks

@PrestigeWeltweit for finding and fixing the FireOS 6 DHCP fault (#704, #714).

Checksums

Verify the assets against the release page before flashing anything.

Don't miss a new EchoMuse release

NewReleases is sending notifications on new releases.