Repository navigation
This is a stability and honesty release. Nothing in it finds a camera that v0.98
could not. What it changes is how much you can trust the screen.
The app used to treat the companion and the GPS as working until a screen said
otherwise. A board that browned out, or a header that worked loose mid-drive,
kept showing ESP and the last frame rate for as long as you looked at it. After
five seconds of silence the header now reads ESP?, the rate goes blank, and the
Flipper gives one short vibration. A GPS fix expires the same way instead of
being stamped onto every later detection. A companion that reboots comes back
with Bluetooth detection on, where before it came back Wi-Fi only and said
nothing.
One visit to the Locator no longer stops the Air Survey for the rest of the run.
The flag that keeps the survey poll off the radio during a hunt was never
cleared, so after any Lock-in the survey was not asked for again until the app
was restarted.
A Flock network name in a probe request no longer confirms the device that sent
it. A beacon carries the transmitter's own name. A probe request carries the
name the sender is looking for, so a phone that once joined a camera's
provisioning network was being listed as a confirmed camera under the phone's
own address. It is capped at Likely. The same name in a beacon still confirms.
Two prefixes left the detection table. One is registered to a chip vendor whose
other prefixes were already rejected for that reason. The other has the
locally-administered bit set and was never a registered prefix at all. Both are
blocked in CI so they cannot come back.
Saved data is harder to lose and easier to clear. hits.csv is written beside the
old file and swapped in, and an interrupted swap is completed on the next start.
Clear Saved Hits clears the hits found in the current run too, and says so if
the card refuses. "It's mine: never alert" now removes what is already stored,
not only the next sighting, and keeps the row with an error tone if the
exclusion could not be saved. Holding OK while the alert card is up acts on the
device on the card rather than the row hidden underneath it.
The ESP32 flasher locks Back while it is erasing and writing, and only then.
Leaving the flasher could run the Flipper out of memory and reboot it on
firmware that loads a lot alongside the app. Two small tables that nothing reads
any more were cut down, which returns about 5.6 KB, and the allocation that
failed now falls back instead of halting.
Reflash the companion for this release. The prefix table and the scoring
changes live on the board as well as in the app, and Health / Preflight will
tell you when the two builds are paired.
Verified on hardware, against a bench emitter: the silent-companion warning and
recovery, the survey continuing after a Locator round trip, the probe-request
cap, the acoustic class for a Raven, the alert-card hold, Clear Saved Hits, the
exclusion removing a stored row, recovery of an interrupted save, the Back lock
during a real flash, a clean exit after flashing, and Health reading READY with
app and companion both at 0.99. The S2 and C5 companion images are
compile-verified, not hardware-verified.
Not fixed in this build. A camera on a randomised address with no usable
fingerprint is still invisible to the detection list. User OUI and SSID entries
in signatures.json still cannot create a detection on the Companion backend,
only on Marauder. Bluetooth scanning is active, so the companion sends scan
requests. The flasher still writes whatever .bin it is given without checking
that it suits the connected chip. Free memory remains thin on heavily loaded
firmware.
Full detail is in changelog.md.
What's Changed
- Name the companion build, exclude your own gear, report a camera we missed by @ReconGrunt in #29
- Credit @wiilover22 in CONTRIBUTORS.md by @ReconGrunt in #28
New Contributors
- @ReconGrunt made their first contribution in #29
Full Changelog: v0.98...v0.99