Lagrange 1.5.3

Warning: Do not update Lagrange to v1.5.3 until your BookOrbit server has been updated to v2.10.0 or newer. This release depends on BookOrbit's dedicated audiobook API, and remote audiobook playback may not work with older server versions.

Why this hotfix

BookOrbit v2.10.0 changed audiobook delivery from the generic file-serving endpoint to a dedicated manifest and asset-content API in the upstream BookOrbit change. Lagrange 1.5.2 still used the old endpoint, so remote audiobooks could stop immediately even though the files were present and playable through the BookOrbit WebUI. This hotfix updates Lagrange to the new BookOrbit contract.

Sorry for the delayed fix. I got busy with real-life work and could not address the compatibility issue sooner. Thank you for your patience.

Fixes

• 91dcdc3 Restored remote audiobook playback against BookOrbit v2.10.0 and newer. (PR #171, #170)
  • Use BookOrbit's dedicated audiobook manifest and asset-content endpoints.
  • Preserve single-file M4B playback and manifest-ordered multipart MP3 playback.
  • Preserve seeking, next/previous transitions, resume, and progress synchronization.
  • Keep opaque audiobook asset IDs separate from stable BookOrbit file IDs.
  • Keep local/downloaded audiobook playback and non-audio file serving unchanged.

Validation

• 727 JVM unit tests passed, with zero failures, errors, or skips.
• lintDebug passed.
• Debug APK and Android-test APK assembly passed locally.
• The user installed the debug APK on a physical Android device and confirmed remote audiobook playback works.

Upgrade notes

• BookOrbit v2.10.0 or newer is supported for remote audiobook playback.
• No migration action is required for existing books, downloads, or progress data.
• The release workflow publishes Lagrange-1.5.3.apk as the default combined APK, with architecture-specific alternatives following the established naming policy.