switch to using a monochrome apk instead of separate chrome/webview apks

[thestinger]

It's not clear if the necessary sources are public yet, but this should happen once it becomes possible.

[rsesek]

In order to support users disabling (Mono)Chrome, Android system still ships a SystemWebViewGoogle. That way there's a fallback package to keep WebView working if the Monochrome package is explicitly disabled. If you're not concerned about users disabling Chrome, then you can just use Monochrome.

[rsesek]

In order to support users disabling (Mono)Chrome, Android system still ships a SystemWebViewGoogle. That way there's a fallback package to keep WebView working if the Monochrome package is explicitly disabled. If you're not concerned about users disabling Chrome, then you can just use Monochrome.

[thestinger]

@rsesek The part that I'm unsure about is what the target is to build monochrome. There are chrome_public_apk and system_webview_apk but I don't see one to actually make a Chrome build include the monochrome libraries, or an option to make it do that.

[thestinger]

@rsesek The part that I'm unsure about is what the target is to build monochrome. There are chrome_public_apk and system_webview_apk but I don't see one to actually make a Chrome build include the monochrome libraries, or an option to make it do that.

[rsesek]

The monochrome APK target isn't yet upstreamed. WebView team is working on unforking it, though (should be part of the crbug mentioned in #420).

[rsesek]

The monochrome APK target isn't yet upstreamed. WebView team is working on unforking it, though (should be part of the crbug mentioned in #420).

[rsesek]

There's now a bug dedicated to tracking the public monochrome target: https://bugs.chromium.org/p/chromium/issues/detail?id=650927.

[rsesek]

There's now a bug dedicated to tracking the public monochrome target: https://bugs.chromium.org/p/chromium/issues/detail?id=650927.

[thestinger]

AFAICT, some of the changes required for this landed but now it isn't progressing. It's not super important but it does make our updates significantly bigger which is a bit annoying. Chromium updates aren't frequent enough for it to be a high priority though.

[thestinger]

AFAICT, some of the changes required for this landed but now it isn't progressing. It's not super important but it does make our updates significantly bigger which is a bit annoying. Chromium updates aren't frequent enough for it to be a high priority though.

[rsesek]

I don't know much about the Chromium Android build configuration, but if you can post on the bug what issues are still outstanding, that'd probably be helpful to the people who do know.

[rsesek]

I don't know much about the Chromium Android build configuration, but if you can post on the bug what issues are still outstanding, that'd probably be helpful to the people who do know.

[thestinger]

It turns out that the remaining issues were resolved recently, I just had to deal with porting it to using 64-bit processes:

https://github.com/CopperheadOS/chromium_patches/blob/master/0017-use-64-bit-Monochrome-processes.patch

[thestinger]

It turns out that the remaining issues were resolved recently, I just had to deal with porting it to using 64-bit processes:

https://github.com/CopperheadOS/chromium_patches/blob/master/0017-use-64-bit-Monochrome-processes.patch