Skip to content

Halium 14 resource updates#52

Open
JamiKettunen wants to merge 2 commits intoubports:halium-14.0from
JamiKettunen:resource-updates
Open

Halium 14 resource updates#52
JamiKettunen wants to merge 2 commits intoubports:halium-14.0from
JamiKettunen:resource-updates

Conversation

@JamiKettunen
Copy link
Copy Markdown

@JamiKettunen JamiKettunen commented Mar 11, 2026

In preparation for usage externally in per-port UI DPI selection while having a common source for these here.

For integration side counterpart see https://gitlab.com/ubports/porting/community-ports/halium-generic-adaptation-build-tools/-/merge_requests/70

Since we are planning to use the files from the directory as-is might as
well update them to match the modern auto-generated artifacts.

https://github.com/LineageOS/android_build/blob/lineage-21.0/core/Makefile#L2476-L2542
Change-Id: I3dcbcd85e5470f9529c0cb1dddfa5c691866fd70
We don't select the recovery DPI to be used via Android build system so
point these to the right files and just choose the whole dir externally.

https://github.com/LineageOS/android_build/blob/lineage-21.0/core/Makefile#L2466-L2473
Change-Id: I1a5c988d434861f4ddda2f2991d664b9bbd8c10e
@NotKit
Copy link
Copy Markdown
Contributor

NotKit commented Mar 12, 2026

No objections in general, but would that require us to regenerate the images on each rebase so that the language set matches? Another option is to include all the resource variants into recovery-ramdisk by modifying build/make repo (I have a PoC of that already) and then only keep the needed variant in halium-generic-adaptation-build-tools.

@fredldotme
Copy link
Copy Markdown
Collaborator

Is this the approach to go? If so, I'll happily merge it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants