Skip to content

New - #2

Merged
suskie778 merged 2 commits into
suskie778:Test2from
JingMatrix:master
Aug 6, 2026
Merged

New#2
suskie778 merged 2 commits into
suskie778:Test2from
JingMatrix:master

Conversation

@suskie778

Copy link
Copy Markdown
Owner

No description provided.

…owhere (#876)

The system server is offered as a synthetic row rather than an installed
package, so no filter can lead a reader back to it, yet it was subject to the
system-apps filter and a module whose declared scope is the framework showed an
empty list. Exempt the framework alone, and only when the module asks for it.

The empty-scope dialog's dismiss action closed it and returned the reader to the
page they were trying to leave, where back raised it again; the only exit was to
disable the module. Make that button leave, and offer the module's own
recommendation as the primary action where it declares one.

Legacy modules name the framework "android" and the android package "system";
modern modules and the daemon use the reverse. The store normalised the
installed scope but not the catalogue's, so one module could name one target two
ways in adjacent lines. Move the transform into one function both readings pass
through.

Module-update notifications are always enqueued for user 0 but carried the user
whose PACKAGE_REPLACED raised them, so for a module installed in a private space
as well as the main user the surviving notice pointed into a locked profile.
Prefer user 0 when the module is installed there.
#882)

Constructing a Notification on Android 16 reads an aconfig flag of the systemui
container, and the daemon cannot serve that read: it holds an ActivityThread but
no application record, so the settings provider is refused it and the
constructor throws SecurityException. Setting systemui_is_cached before the
first read leaves the flags at their compiled defaults and removes the read.

That bypass was gated on SDK_INT >= VANILLA_ICE_CREAM, wider than the release it
belongs to, because Xiaomi shipped the change on Android 15 without the SDK
level; #96 was such a device, four days before Android 16 DP1 was published.
#597 rewrote the test as SDK_INT == 36 and lost that case, which #880 now
reports on the same vendor and the same version. Android 17 sets those fields
unconditionally, so the test spans 35 to 36, the versions in which the field can
exist.
@suskie778
suskie778 merged commit 5354b38 into suskie778:Test2 Aug 6, 2026
0 of 2 checks passed
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.

2 participants