DresOS WebView v2.3.2

Roll the arm64 engine back to the Chromium 145 build. The Cromite 148 engine crashed the renderer on real pages.

DresOS WebView Module v2.3.1

• Fixed the overlay offering both engines on the same device. The installer has always placed only one engine, chosen by the device architecture, but the overlay whitelisted both, so an arm64 phone advertised AOSmium as a selectable WebView provider even though the module never installed it there. AOSmium is the engine for the architectures the DresOS build cannot serve, not an alternative sitting next to it. There are now two overlays, one per architecture, and each device gets only the one that matches it plus the stock fallbacks.

DresOS microG v3.1.7

Automatic refresh of the bundled microG core: com.android.vending 84022630 to 84022632, com.google.android.gms 250932030 to 252432032.

The microG core is verified against the official microG signing key before it is staged. Aurora Store and Aurora Services are bundled at pinned versions and pinned keys, and are not refreshed automatically.

DresOS microG v3.1.6

• Aurora Store and Aurora Services are no longer refreshed automatically. The signing key on the Aurora Store build served by IzzyOnDroid changed from the one bundled here, and the build correctly refused to stage a system app whose signing identity had moved. Auto updating an app across a key change is exactly how a differently signed package ends up shipped, so both Aurora components now stay at pinned versions with pinned keys and are only updated deliberately after the new key has been checked. The microG core, which is the part that carries security fixes, still refreshes on its own every week.
• The release step no longer fails outright if the release it is creating already exists, which is what broke reruns.

DresOS WebView Module v2.3.0

• Carries the new DresOS WebView engine, rebuilt on Cromite 148.0.7778.168. That is three Chromium majors on from the engine the module shipped before, so it brings every upstream security fix in between.
• AOSmium is back as the backup engine on 32 bit, and it is a much newer build than the one that was bundled before. It is credited to AXP.OS in the installer, the overlay and this repository rather than presented as ours.
• The bundled engines now update themselves. A release workflow pulls the DresOS engine from its own releases and the newest stable AOSmium from the AXP.OS repository, checks both against their pinned signing certificates, builds the module and publishes it. Pre-releases are skipped, because AXP.OS marks untested builds that way.
• The signing key never reaches the workflow. The engine is built and signed on the maintainer's machine and the workflow only packages and publishes what is already signed.

DresOS WebView v2.2.1

• Repointed the in-module update check and the issues link at The DresOS Foundation. They still pointed at the old account, so update checks were resolving through a redirect or not at all. The microG module had this fixed in v3.1.3; this module was missed.
• Added minMagisk to module.prop so Magisk enforces the same floor the installer checks, rather than letting the flash start and then abort.
• The installer banner now reads the version from module.prop instead of carrying its own hardcoded copy.
• Corrected the README: the standalone engine APK is distributed through its own GitHub releases only. It is too large for IzzyOnDroid, and the link pointed at the old account.
• Dropped the 32-bit path. armeabi-v7a devices were being given AOSmium by AXP.OS, another project's engine, presented as a DresOS one. Rather than keep shipping someone else's build under our name, the module is arm64 only until a 32-bit DresOS WebView engine exists. A 32-bit device is now told that at flash time and nothing on it is touched. The AOSmium entry is gone from the RRO as well.

DresOS microG v3.1.5

• The bundled apps now update themselves. A scheduled workflow checks the microG repo and IzzyOnDroid every week for GmsCore, Companion, GsfProxy, Aurora Store and Aurora Services, and if any of them has moved it rebuilds the module, bumps the version and publishes the release on its own. Before this only a GmsCore change could trigger a refresh, so an Aurora update could sit unnoticed indefinitely.
• Aurora Store and Aurora Services are now verified against pinned signing keys before they are staged, the same way the microG core already was. They were being downloaded from IzzyOnDroid and installed as system apps, one of them privileged, with nothing checking who signed them.
• The privileged permission generator can now create an entry for a bundled app that does not have one yet. It could only add permissions to an app already listed, so a new privileged permission on GsfProxy would have been silently skipped, which is the same shape as the Aurora Services gap in 3.1.4.
• Removed INSTALL_PACKAGES and DELETE_PACKAGES from the Aurora Services allowlist entry. Those were added in 3.1.4, but Aurora Services 0.3.0 only ever requests INSTALL_PACKAGE_UPDATES, and Android cannot grant an app a permission it does not ask for, so the two entries did nothing. If a future Aurora Services requests them the generator adds them back automatically.

DresOS microG v3.1.4

Fixes stock Google Play Services being left active on ROMs where Play Services had updated itself, which made every Google dependent app crash after reboot. Fixes Aurora Services going in without the install permissions it needs. Reported from a Samsung J600F on One UI 2.0.

DresOS microG v3.1.3

Refresing apks

DresOS microG v3.1.2

Repoints the in-app update and issues links to the current organisation so updates resolve again, and removes leftover build plumbing from the retired Google-signed flavor. No change to what installs on your device.