58 lines
2.7 KiB
Markdown
58 lines
2.7 KiB
Markdown
# PawletOS notes
|
|
|
|
This repo is a fork of [LawnchairLauncher/lawnchair](https://github.com/LawnchairLauncher/lawnchair)
|
|
(`upstream` remote), pushed to `origin` at `git.oxmc.me/PawletOS/Lawnchair`. Kept as
|
|
its own top-level file (not folded into README.md) so pulling upstream never
|
|
conflicts with it.
|
|
|
|
## Workflow: pull upstream, apply PawletOS fixes, push to PawletOS
|
|
|
|
1. `git fetch upstream` / merge or rebase `upstream/16-dev` onto this repo's `16-dev`.
|
|
2. Apply/carry forward PawletOS-specific fixes on top (e.g. the split-select
|
|
crash fix, commit `15b7175aee`).
|
|
3. `git push origin 16-dev`.
|
|
|
|
Output: built via `external/build-tools/lawnchair/build/build.sh`, the resulting
|
|
APK is committed to `vendor/Lawnchair/LawnchairLauncher` (`prebuilt_lawnchair`).
|
|
|
|
## Submodule gotcha: platform_frameworks_libs_systemui
|
|
|
|
This is a real git submodule, with its own independent remote. **A commit made
|
|
directly in the submodule checkout is local-only until it's pushed to *that
|
|
submodule's own remote* — committing/pushing this outer repo does not push it.**
|
|
|
|
Hit this for real (2026-10-06): a PawletOS fix (`b985017f`, displaylib no-op)
|
|
was committed straight into the submodule checkout but never pushed anywhere,
|
|
since `.gitmodules` pointed at upstream
|
|
(`github.com/LawnchairLauncher/platform_frameworks_libs_systemui`), which
|
|
PawletOS has no push access to. Any other synced tree then failed `repo sync`
|
|
with `fatal: b985017f...: not a valid SHA1`, since that commit didn't exist on
|
|
the configured remote.
|
|
|
|
Fixed by creating `git.oxmc.me/PawletOS/platform_frameworks_libs_systemui` and
|
|
repointing `.gitmodules` at it. Going forward, any fix made inside this
|
|
submodule needs:
|
|
|
|
1. `cd platform_frameworks_libs_systemui && git push <pawletos-fork-remote> HEAD:refs/heads/16-dev`
|
|
2. Then, in this outer repo: `git add platform_frameworks_libs_systemui && git commit && git push origin 16-dev`
|
|
to bump the gitlink.
|
|
|
|
Skipping step 1 reproduces the exact same `not a valid SHA1` failure elsewhere.
|
|
|
|
**If you repoint `.gitmodules` at a different submodule URL** (as happened
|
|
here, upstream GitHub -> the PawletOS fork above): any *already-synced* tree
|
|
still fails the same way even after the fix lands, because git caches the
|
|
submodule's remote URL in `.git/config` on first init and does not re-read
|
|
`.gitmodules` on every fetch/checkout. `sync-s="true"` in the manifest (see
|
|
`common/pawletos.xml`) is unaffected and correct as-is -- it only controls
|
|
whether `repo` inits/updates submodules at all, not which URL. Fix on an
|
|
existing tree:
|
|
|
|
```
|
|
cd <project>/platform_frameworks_libs_systemui/.. # the outer project dir
|
|
git submodule sync --recursive
|
|
```
|
|
|
|
A brand-new tree that's never been synced before won't hit this at all --
|
|
it reads the current `.gitmodules` fresh, with no stale cache to begin with.
|