Release 1.1.13: fix app movement and add launcher actions
Keep the displayed app order intact until the grid reuse comparison, and retain selection during rebuilds so D-pad rearranging visibly moves the chosen tile. Add Android-confirmed uninstall for user apps and a foreground-only Wi-Fi/Ethernet shortcut with separate TV-input spacing. Remove the duplicate Personalize footer. Use an explicitly authorized replacement signing identity after loss of the original key. Document the one-time reinstall and preserve signature verification. Add a portable build using ignored signing configuration and regression checks for movement, lifecycle, native network settings, and cancel/confirm uninstall. Validated on the authorized onn 4K Plus: original failing move reproduction now passes, HomeActions/GridReuse/WakeRegression/Navigation instrumentation passes, and native settings/uninstall checks pass. Input-header availability was simulated; physical Ethernet and input switching were not exercised. Restore prior visible settings and Home override; remove the disposable test APK.
This commit is contained in:
parent
2739b278cd
commit
6a08aa242c
24 changed files with 635 additions and 79 deletions
27
README.md
27
README.md
|
|
@ -2,7 +2,9 @@
|
|||
|
||||
A native, remote-first Android TV launcher designed for limited-memory streamers and integrated TVs. Its package name is `tv.luma.launcher`.
|
||||
|
||||
Version **1.1.12** removes obsolete alternate-launcher integration, avoids redundant screen-on window updates during navigation, and waits for focus to settle before transitioning app background colors. Every resume restores missing images, including when Android briefly pauses the launcher without stopping it. Leaving the launcher releases image memory. Updates can be installed directly from the TV; physical-input controls appear on compatible TVs.
|
||||
Version **1.1.13** fixes D-pad app rearranging, adds uninstall to the app menu and a network status shortcut beside Settings, and removes the duplicate Personalize footer button. Physical-input controls have their own space on compatible TVs.
|
||||
|
||||
**One-time reinstall required:** the original signing key was lost. This release uses an authorized replacement key, so Android cannot install it over versions through 1.1.12. Uninstall the old Luma and install this APK; Luma settings and Plex credentials reset. Subsequent updates use the replacement key normally. Update signature verification remains enabled.
|
||||
|
||||
## Use it
|
||||
|
||||
|
|
@ -13,10 +15,11 @@ Press **Home** after configuring Home routing, or open **Luma** from Android's a
|
|||
```
|
||||
|
||||
- D-pad navigates the installed app grid; OK opens an app.
|
||||
- Hold OK on an app to move it, move it to the front, hide it, or open Android app info.
|
||||
- Hold OK on an app to move it, move it to the front, hide it, uninstall it, or open Android app info. Uninstall is available for user-installed apps and opens Android's confirmation screen; system apps retain app info.
|
||||
- In move mode, arrows move the app; OK saves and Back restores the previous order.
|
||||
- Menu or the gear opens Luma settings. **All apps** includes hidden apps so they can be restored.
|
||||
- Back scrolls to the first row and stays on Luma. Home returns to Luma.
|
||||
- The network icon beside Settings opens network settings. It shows Wi-Fi or Ethernet for the active connection, muted when disconnected and gold when Android has not validated internet access. Its accessibility label describes the state. It uses a callback only while Home is foreground, without scans, location permission, or polling. Unsupported network-settings screens fall back to wireless settings and then general settings.
|
||||
|
||||
## Default launcher and Home routing
|
||||
|
||||
|
|
@ -91,10 +94,10 @@ No SSH key or Forgejo account token is stored on the TV. For branch-based Forgej
|
|||
### Publish an update
|
||||
|
||||
1. Increase `versionCode` and `versionName` in both `app/src/main/AndroidManifest.xml` and `app/build.gradle`. Every published update needs a greater version code.
|
||||
2. Edit `docs/UPDATE_NOTES.md`, then run `scripts/build.sh` using the existing signing keystore. The build generates `output/Luma.apk` and `output/update.json` together, including the APK checksum and size.
|
||||
2. Edit `docs/UPDATE_NOTES.md`, then run `python scripts/build.py` (or `bash scripts/build.sh`) using the existing signing keystore. Set `JAVA_HOME` and `ANDROID_HOME`. The build generates `output/Luma.apk` and `output/update.json` together, including the APK checksum and size.
|
||||
3. Commit and push the source changes, **both output files**, and release notes to `main`. The next scheduled/manual check on each TV discovers the update. No separate release upload or account setup is needed.
|
||||
|
||||
Preserve `.tools/luma-development.keystore` separately from Git: the same signing key is required for every update. The first updater-capable APK must be installed on each TV once, through ADB, Downloader, or a file manager; later updates can be handled within Luma.
|
||||
Preserve `.tools/luma-development.keystore` and `.tools/signing.json` securely outside Git: the same signing key and password are required for every update. The first APK using the replacement identity must be installed on each TV once, through ADB, Downloader, or a file manager; later updates can be handled within Luma.
|
||||
|
||||
Android scheduling and installation behavior follow the [JobInfo API](https://developer.android.com/reference/android/app/job/JobInfo.Builder) and [package installation API](https://developer.android.com/reference/android/content/pm/PackageManager#canRequestPackageInstalls()).
|
||||
|
||||
|
|
@ -117,16 +120,16 @@ Measurements are in [docs/VALIDATION.md](docs/VALIDATION.md). PSS includes Andro
|
|||
|
||||
The signed APK is [output/Luma.apk](output/Luma.apk). Source is in `app/src/main/java/tv/luma/launcher`.
|
||||
|
||||
The current workspace already contains a local JDK 17 and Android SDK under `.tools`. Rebuild without Gradle:
|
||||
Rebuild without Gradle using Python 3, JDK 17, and an Android SDK with platform/build tools 34 or newer. Set `JAVA_HOME` and `ANDROID_HOME` to those installations. On the current Windows checkout they are `.tools/jdk` and `.tools/sdk`:
|
||||
|
||||
```sh
|
||||
bash scripts/build.sh
|
||||
.tools/platform-tools/adb -s 192.168.50.195:35635 install -r output/Luma.apk
|
||||
python scripts/build.py --tests
|
||||
adb -s "$LUMA_ADB_DEVICE" install -r output/Luma.apk
|
||||
```
|
||||
|
||||
For a fresh macOS checkout, run `scripts/bootstrap.sh`, review/accept the SDK licenses, then build. Alternatively use the included Gradle project with JDK 17, Gradle 8.7 and Android SDK 34. No third-party app dependencies are needed.
|
||||
|
||||
The local build creates and reuses `.tools/luma-development.keystore`. Preserve that file to install future updates over the existing APK. It is ignored by source control. This is a development signing identity for your sideloaded build; configure your own signing identity before distributing it.
|
||||
The build reuses `.tools/luma-development.keystore` with the password in ignored `.tools/signing.json`. Alternatively set `LUMA_KEYSTORE`, `LUMA_KEY_ALIAS`, and `LUMA_KEYSTORE_PASSWORD`. It refuses to generate a missing key unless explicitly run with `--create-signing-key`; that option is only for an intentionally new identity and requires reinstalling existing copies. Passwords are passed to signing tools through environment variables.
|
||||
|
||||
To remove Luma, run `adb uninstall tv.luma.launcher`. No command in the build/install scripts disables another launcher or changes the default Home app.
|
||||
|
||||
|
|
@ -149,9 +152,9 @@ The wake regression uses a separate test APK signed with the same development ke
|
|||
|
||||
```sh
|
||||
bash scripts/build-wake-tests.sh
|
||||
.tools/platform-tools/adb -s 192.168.50.195:35635 install -r output/Luma-wake-tests.apk
|
||||
.tools/platform-tools/adb -s 192.168.50.195:35635 shell am instrument -w -r tv.luma.launcher.tests/.WakeRegressionInstrumentation
|
||||
.tools/platform-tools/adb -s 192.168.50.195:35635 uninstall tv.luma.launcher.tests
|
||||
adb -s "$LUMA_ADB_DEVICE" install -r output/Luma-wake-tests.apk
|
||||
adb -s "$LUMA_ADB_DEVICE" shell am instrument -w -r tv.luma.launcher.tests/.WakeRegressionInstrumentation
|
||||
adb -s "$LUMA_ADB_DEVICE" uninstall tv.luma.launcher.tests
|
||||
```
|
||||
|
||||
Successful output ends with `INSTRUMENTATION_CODE: -1` and PASS lines for all cases. The runner controls activity lifecycle callbacks and should be run with no other device tests in progress.
|
||||
|
|
@ -159,6 +162,8 @@ Android force-stops the target package during instrumentation and can mark its a
|
|||
|
||||
The `.AccentSchedulingInstrumentation` runner verifies focus-color coalescing, the final selected color, pause cancellation, resume recovery, and immediate reduced-motion updates in both rendering modes.
|
||||
|
||||
The `tv.luma.launcher.HomeActionsInstrumentation` runner checks the actual remote menu and all four move directions, focus, boundary clamping, save/cancel, saved order after resume, callback cleanup/recovery, and header spacing/focus with simulated physical-input availability. Run `scripts/check-app-move.py --adb <adb-path> --device <serial>` for the original UI reproduction. After instrumentation, `scripts/check-home-actions.py` checks the native network page and both canceling and confirming an uninstall of the disposable **Luma test app**; it removes that test APK as part of its check. These scripts do not uninstall user apps.
|
||||
|
||||
Additional runners in the same test APK check real GPU pixels (`.TileRenderingInstrumentation`, `.RenderingInstrumentation`) and normal/rapid D-pad navigation without spawning an input process per key (`.NavigationInstrumentation`). Pass `-e memorySaver true` to the wake or navigation runner to exercise the optional mode; the runner restores its preference afterward.
|
||||
|
||||
The same test APK also includes `tv.luma.launcher.tests/.PerformanceInstrumentation` for the background/shadow A/B benchmark. It changes only runtime view state and writes a temporary `performance.txt` in Luma's external-files directory. Reopen Luma afterward and remove the diagnostic APK.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue