Rubylight Android 0.4.5 fixes a reproducible pairing failure affecting device model names containing spaces or non-ASCII characters, including names such as Odin2 Portal.
The client encoded the device name twice, sending Odin2+Portal instead of Odin2 Portal. The Rubylight host rejected that name, and Android displayed the generic network/firewall error. Pairing requests now encode the name once. The fix covers ordinary PIN pairing, one-time PIN pairing, and the final HTTPS challenge.
Install rubylight-0.4.5.apk over your existing installation. It uses the same signing key and package ID as 0.4.4. The APK and app bundle contain arm64-v8a, armeabi-v7a, x86 and x86_64 builds.
Validation: all 1,675 Android unit tests passed, including an Android 13 regression that failed before the fix. Both signed release APK flavors, the app bundle and release lint passed. Signing continuity, version 0.4.5 (322), source revision 43944bfc, and 16 KB native/ZIP alignment were verified.
The exact signed APK passed an emulator upgrade from 0.4.4. The saved PC, client certificate, private key and installation ID were retained. A local host fixture confirmed that the device name reaches the host unchanged, the PIN stays visible while waiting, and Cancel returns to the PC list without an app crash or ANR.
Retesting on the affected Odin 2 Portal and Galaxy Z Fold6 with a live host is still needed; this release does not establish that every failure reported in issue #2 is resolved.