Full client for the Tdarr /api/v2 JSON API (jobs, library, nodes, stats, logs, settings, flows, multi-server switcher) plus v0.2.0 resilience: per-server timeout + slow-connection mode, retry-with-backoff on read polls, last-good-data + reconnecting chip, 60s poll backoff after repeated failures, and keep-alive eviction on app resume. Includes GPL-3.0 licensing (LICENSE/NOTICE), README, CONTRIBUTING, PREVIOUS_HISTORY, issue/PR templates, CI release-notes script, keystore docs and the vendored OpenAPI 2.0 spec.
2.2 KiB
2.2 KiB
Summary
Linked issues
Type of change
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that changes existing behaviour)
- Documentation / repo-meta (README, CONTRIBUTING, CI, templates — no app code change)
- Refactor (no functional change)
How tested
./gradlew assembleDebugis green locally- Manual smoke test on a real device (Android 8.0+, ideally 12+ for dynamic colour)
- Unit tests added / updated (encouraged for
data/parsing and repo logic) - Gitea Actions build on this PR is green
If you added new UI, attach a screenshot or short screen recording.
Privacy / permissions checklist
- No new Android permissions requested (Trafero needs INTERNET; nothing else should be needed)
- No analytics, telemetry, or third-party trackers introduced
- No analytics, telemetry, or crash-reporting SDK introduced; Trafero talks only to the user-configured Tdarr server
- If a new permission is genuinely required, the PR description explains why
Documentation
README.mdupdated (Features section + any new build steps)PREVIOUS_HISTORY.mdhas a## v<VERSION>section for the upcoming release (if user-visible)CONTRIBUTING.mdstill accurate (branch naming, commit format, etc.)
Checklist
- I've read the Contributing guide
- My commit messages follow Conventional Commits
- My changes don't add new dependencies that aren't justified
- I've tested on at least one real Android device