| 16 Nov 2024 |
 atemu12 | Wait what, that's an option? | 23:49:24 |
| atemu12 | Does it show up as a system app? Is it listed in the webviev selector dev setting? | 23:50:09 |
| 17 Nov 2024 |
 samueldr | urgh, can't seem to find info quickly about that | 19:03:36 |
| samueldr | but IIRC yes it was done at some point to make it possible for the system webview to be updated | 19:03:58 |
| samueldr | not at all what I had in mind, but provides hints https://www.xda-developers.com/google-chrome-no-longer-webview-provider-android-10/ | 19:05:28 |
| samueldr | some other notes https://chromium.googlesource.com/chromium/src/+/HEAD/android_webview/docs/channels.md | 19:06:35 |
| samueldr | https://github.com/search?q=org%3ALineageOS%20%2Fcom.google.android.webview%2F&type=code | 19:08:15 |
| samueldr | and then I suppose form the context that these are signed webviews that can act as system apps https://github.com/LineageOS/android_vendor_lineage/blob/lineage-21.0/overlay/common/frameworks/base/core/res/res/xml/config_webview_packages.xml | 19:10:37 |
| samueldr | the commit history is short, and more context here https://github.com/LineageOS/android_vendor_lineage/commits/lineage-21.0/overlay/common/frameworks/base/core/res/res/xml/config_webview_packages.xml | 19:15:00 |
| 18 Nov 2024 |
| atemu12 | We should allow commen FOSS webviews by default, then users can simply install those manually | 04:51:13 |
| samueldr | .oO* android_vendor_robotnix when?) | 05:17:13 |
| samueldr | * .oO( android_vendor_robotnix when?) | 05:17:17 |
| samueldr | * .oO( android_vendor_robotnix when? ) | 05:17:20 |
| atemu12 | Haha | 05:17:29 |
| atemu12 | But I think we already do that | 05:17:39 |
| atemu12 | We have custom apps, webviews and such | 05:18:16 |
| 19 Nov 2024 |
 oak 🏳️🌈♥️ | I now upgraded my phone to have LineageOS 20.0 and made yet-an-other PR https://github.com/nix-community/robotnix/pull/258
Phone seems to be running fine on LineageOS 20, the only noticeable difference is that now instead of 10 seconds the phone boot seems to take around 1 minute | 05:31:25 |
| oak 🏳️🌈♥️ | I added instantnoodlep to the supported devices because in the other PR it was commented it would bring more comfort :) | 05:31:58 |
| atemu12 | Cool, thanks :) | 05:32:19 |
| oak 🏳️🌈♥️ | I don't know how the boot time could be improved, maybe it didn't apply the usual optimizations it does when doing OTA update (which take long time). Maybe doing first OTA update fixes it | 05:34:17 |
| atemu12 | Well, try a reboot and see whether it's still as bad | 05:34:38 |
| oak 🏳️🌈♥️ | Already tried couple of times | 05:34:55 |
| atemu12 | And it's reproducible? | 05:35:04 |
| atemu12 | Hm | 05:35:09 |
| oak 🏳️🌈♥️ | Yeah on LineageOS 19.1 the squid logo ball was only going over the line for like 3-5 times usually, now it takes 20 bounces | 05:35:51 |
| atemu12 | You could have a look at logcat and perhaps get a glance of what's taking so long | 05:36:05 |
| atemu12 | There isn't anything as nice as systemd-analyze on Android though that I know of | 05:36:26 |
| atemu12 | FWIW it's not taking that long on my device | 05:36:40 |
| atemu12 | Have you added a bunch of files to userdata in the process of updating by chance? e.g. to create a backup? | 05:37:23 |
| atemu12 | I once had super long boot times and it was caused bu Android running some SElinux re-labelling or some shit | 05:37:59 |
