Paul HittandClaude Opus 5
4a8cb64c65
Two reports from a real phone. **A photo auto-rotated.** BitmapFactory does not apply EXIF orientation, and every image this app sends is re-encoded to strip EXIF — which is right, because that block carries the GPS coordinates the shot was taken at. The same block carries the tag saying which way is up, and a phone camera rarely writes upright pixels: it writes landscape pixels plus "turn this 90°". Decoding ignored that, the re-encode dropped the tag, and the only thing that knew which way was up was gone. The tag is now read and applied to the pixels before it is discarded, on all three paths: preparing to send, scrubbing metadata, and rendering an image received from a peer. The mirrored tags are handled too — a front camera writes them, and a selfie coming back flipped is the same bug facing sideways. 🔴 iOS is NOT affected, which is why this survived: UIImage(data:) applies orientation as it decodes, so the identical strip-and-re-encode is safe there. Same design, opposite platform default — and the reason "works fine on iOS" said nothing about Android. **The keyboard covered what was being typed into.** The manifest has said windowSoftInputMode="adjustResize" all along, and that stopped meaning anything at targetSdk 35: Android 15 forces apps targeting it edge-to-edge, and an edge-to-edge window does not resize for the IME. So the line has been a no-op on every device this ships to (minSdk 33). The root now consumes the IME inset with imePadding() — at the root rather than per screen, because every screen with a text field has this and one added later would too. 5 new tests, including one that fails if the manifest line ever becomes the only thing relied on again. 1213 tests green, counted from the result XML rather than from BUILD SUCCESSFUL. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Flamenet Messenger — Android
The Android app, and the two libraries under it.
engine/ the protocol: X3DH, Double Ratchet, sealed sender, safety numbers,
key transparency. Plain Kotlin/JVM — no Android in it at all.
client/ the relay transport: HTTP, auth, the §8 routes.
app/ the Compose app.
interop/ the cross-engine driver; not shipped.
engine and client are deliberately plain JVM libraries. The protocol has
nothing to do with Android, and keeping it off the platform means their tests
run anywhere a JVM does — no SDK, no emulator, no device, which is also what
lets them gate in CI on Linux:
./gradlew :engine:test :client:test
The app's own unit tests need the Android SDK but still no emulator (Robolectric):
./gradlew :app:testDebugUnitTest
Where it stands
PARITY.md is the definition of done for this app — read that, not this. Every row there names the iOS file it came from so it can be re-checked rather than trusted. Headlines as of 2026-08-28: messaging, groups, attachments, voice notes, stories, calls, sealed sender, key transparency and the encrypted vault are built and tested; a cross-platform round trip against iOS was verified on 2026-08-26.
⚠️ This file said "Nothing here is an app yet" until 2026-08-28, above a tree containing the finished app — the README described the repository as it was when the engine landed and nothing updated it as the app grew around it. If a claim here ever disagrees with PARITY.md or with the tree, believe those, and fix this.
Why the engine came first, and is held to the vectors
An Android client needs the protocol implemented a third time, and the third
implementation is the one that finds the places where the specification says
less than the two existing engines quietly agreed on — but only if it is
written against the spec and the published vectors rather than against a
reading of our own Swift and JavaScript. So the engine is held to
test/vectors/protocol-v1.json in
flamenet-e2e — the same file the
other two engines are checked against, read from that repository rather than
copied here, because a copied vector file drifts and a drifting vector file
stops being a check. PublishedVectorsTest looks for it beside this checkout
and fails loudly if it cannot find it; FLAMENET_VECTORS overrides the search.
Two implementations that agree may both be wrong in the same way, especially when one was written while reading the other. The audit-path ordering in §19 is the worked example: a top-down reading of a bottom-up path produces the correct root for every left-spine index, so it passes any test that only checks index 0. The vector file pins a right-descending index for that reason, and the Kotlin tests assert both that the published path verifies and that the same path reversed does not.
If this engine ever disagrees with the file, the interesting question is which of the three is wrong — not this one by default.
Contributing and security
- CONTRIBUTING.md — building (JDK 21,
JAVA_HOMEis not optional on a Mac), the test gate, and the platform traps that cost an hour each. - PARITY.md — what iOS does, what this does, and what is left. It is the definition of done for this app.
- SECURITY.md — threat model and where to send a vulnerability report. Not an issue tracker matter: security@flamenetmessenger.com.