yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Magendanz:
This seems like the most relevant error:

WebViewFactory: Chromium WebView package does not exist
WebViewFactory: android.webkit.WebViewFactory$MissingWebViewPackageException: Failed to load WebView provider: No WebView installed
[Android Software Development] Daikath:
Hey thanks for replying. I tried to unpack the recovery image rom to alter it so be able to get through an error log. But I cannot get to that point sadly,.

https://wiki.lineageos.org/devices/s5neolte/install

I then use the unpack method from

https://xdaforums.com/t/guide-unpack-repack-boot-recovery-img-without-kitchen.2839670/

I get these error messages and sadly no files to edit in the manner you described,

'chcp' is not recognized as an internal or external command,operable program o - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

I'm being very stubborn and uploading a new OS onto an old phone rather than buying a new one. But if I can still save it, that would be great.It worked fine for quite a while until it wouldn't boot after an update. Now I'm just trying to get a working install agauin.
[Android Software Development] Nezorflame:
No and I doubt that we will in any foreseable future.

We use only the full APK variants.
[Android Software Development] Daikath:
Jusrt in case anyone else had this problem... I flashed a new recovery image, the latest twrp again (Where I had used the LineageOS rboot img). I thought I wiped my system and just installed LineageOS, but when I booted just to check.. Google pico was still on it and thankfully it did boot this time..

I'm just grateful it boots again, I'm not ging to touch it to get a logcat or anything..
[Android Software Development] Nezorflame:
The issue with ARM package should be fixed - it was a broken APK update, which was removed from Gitlab (basically SDK27 APK was picked instead of SDK30 one).
[Android Software Development] curiousrom:
Pixel 3a LineageOS 18.1 + open_gapps-arm64 Bootloop

@Nezorflame - FWIW two Pixel 3a users reported bootloop with Open GApps but working fine with MindTheGapps in the LineageOS subreddit here:

To which a LineageOS team member replied:

This is what happens when publishing untested builds. :(

***
[Android Software Development] curiousrom:
Moto G6 Plus LineageOS 18.1 + open_gapps-arm64 Bootloop "Can't load android system"

@Nezorflame - FWIW a Moto G6 Plus user (A/B device) reported failed to boot with open_gapps-arm64-11.0-nano-20211111.zip but working fine with MindTheGapps in the LineageOS subreddit here:

"After rebooting, I get the lineageos loading symbol, it loads for ages, before rebooting and going back to recovery. ...Can't load android system, your data may be corrupt."
[Android Software Development] Nezorflame:
Thanks, builds have been pulled, investigating the issue.
[Android Software Development] curiousrom:
Broken Open GApps Builds Again!

The era of publishing untested rolling releases of Open GApps is over.

Google is moving the goal posts all the time and that breaks stuff.

Better a monthly thoroughly tested release instead.

That's better for the reputation of Open GApps & also for the users instead of wasting their time with broken builds.

***
[Android Software Development] Nezorflame:
The issue is fixed, new builds should be fine.

Will return with the news regarding what @curiousrom said soon (tm).
[Android Software Development] Nezorflame:
In the meantime, here's a quick test A12 nano build for ARM64 for those who wants a taste :)

Initial setup worked for me, but might have different issues I haven't found yet.

https://sourceforge.net/projects/opengapps/files/arm64/test/20211112/open_gapps-arm64-12.0-nano-20211112-UNOFFICIAL.zip/download
[Android Software Development] robin0800:
I am on android 10 and both 12th and 13th still crash on installation screen. Did your fix trickle down to 10 or is this a new problem?
[Android Software Development] curiousrom:
What do you mean by "installation screen"?

Is that in recovery or when booting to system or in the Setup wizard?

If it's in the Setup wizard, it's while doing what?

Device model? ROM? GApps package? Clean install of update?

Did you try Open GApps build 2021-11-05?

***
[Android Software Development] robin0800:
Setup wizard when trying to go to google account screen it never makes it, it crashes.

Rom lineage 10.1, gaps pico 05/11/210 and clean install.
[Android Software Development] curiousrom:
Black Screen in Setup Wizard

A clean install LineageOS 18.1 Xiaomi Mi 6 (sagit) + Open GApps Stock user reported here in the LOS sub:

"Older Open GApps packages still don't seem to work completely right, the one from 11-05-2021 gives me a black screen when I choose to recover a backup...."

***

***
[Android Software Development] robin0800:
Sorry for wasting your time but it was not a gapps problem but a Rom problem. using an older Rom works with gapps 13 just fine.
[Android Software Development] ipdev:
Hi all. :)

Long story short.

Looking for opinions on reversing the order of (or improving) the abi check.

OpenGApps - Github - Installer Script Line 1665 - Link

Reversing it (checking for cpu.abi first) should fix the wrong architecture being found on some devices.

device_architecture="$(get_prop "ro.product.cpu.abi")";
if [[ -z $device_architecture ]]; then
device_architecture="$(get_prop "ro.product.cpu.abilist")";
fi;

I prefer looking for the newer prop first but, maybe this time it would be better looking for the older value first?

I have not tried it yet but, it should fix the architecture mismatch I recently ran into on my Poco F1.

The custom rom (used ro.product.cpu.abi) did not set ro.product.cpu.abilist in any of the prop files so OpenGApps set it from TWRP's default.prop.

Not sure if this affect other devices or not. :unsure:

First time I ran into it and I have wiped, formatted and flashed my Poco F1 many times.

Not sure why this only showed up now.

I am using the official TWRP for the Device from twrp.me

TWRP for Xiaomi Pocophone F1 - twrp.me - WebSite - Link

beryllium:/ # for i in $(find / -name 'default.prop' 2> /dev/null); do echo $i && cat $i | grep 'cpu.abi'; done;
/default.prop
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
beryllium:/ #

Thoughts on including one of these values. 🙃

ro.vendor.product.cpu.abilist

ro.odm.product.cpu.abilist

ro.system.product.cpu.abilist

ro.vendor.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.odm.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.system.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi

Cheers all. :cowboy:

Edit:

Dec. 15 2021 - Links to the PR and commit for reference.

OpenGApps - GitHub - Commit - Link

OpenGApps - GitHub - Pull request [# 944] - Link
[Android Software Development] Nezorflame:
While I'm researching the reported issue, quick update to the A12 test package (only has apps updated to their SDK31 variant), package installer as well so apps should install fine.

Don't expect any serious work on A12 for now until we fix more important issues, but since it's already in a more or less working state, feel free to report anything you find so that I fix it when I have time.

ARM64 nano variant only for now: SourceForge
[Android Software Development] Nezorflame:
@osm0sis @mfonville WDYT?

I personally agree with this (and this is something @Nikhil suggested as well), so if there are no objections, might add this check.

BTW @ipdev feel free to post this kind of feedback/discussion on our Github as well, might be easier to communicate there.

Update: see https://github.com/opengapps/opengapps/pull/942 with this change.
[Android Software Development] heithered:
I'm trying to set up a gapps config file to exclude same apps but couldn't manage to exclude Android auto and YouTube music. Can't find them at GitHub page, can someone help me please?
[Android Software Development] osm0sis:
[WIP] Add permission check script by nezorflame · Pull Request #943 · opengapps/opengapps

Added Python script (modified version of MindTheGApps one) to check missing privapp permissions. Also modified add_sourceapp.sh so that it also checks missing permissions for the added APKs.

github.com
[Android Software Development] curiousrom:
Testing Open GApps Packages Before Releasing Them

@Nezorflame - That's good. :cool: 👍

Next step, maybe be inspired by an other thing that MindTheGapps does: release new packages only once in a while after they are tested by actual humans.

If you look here and here the last 3 MindTheGapps-11 releases were on:

Mar 28, 2021

Apr 12, 2021

Sep 20, 2021 - That's the most recent @ the present.

Play Store and Play Services automatically update themselves in the background regardless of the user's update settings in Play Store so there is no reason to churn out daily untested releases and the apps are updated when you login Play Store: either manually or auto-updated if you choose so.
[Android Software Development] Magendanz:
If you're running into the "Speech Services by Google" (a.k.a. GoogleTTS) crash on ARM 11.0, the workaround is to roll back to GoogleTTS v.26.2.4.385195680, which was last included in the 20210925 builds.
[Android Software Development] ipdev:
Just to note.

MTG is not perfect either. ;)

Their installer script was broken.

[ROM][UNOFFICIAL][LineageOS][18.1/19.0][dragon] -> 2021-11-17 - xdaThread - Link

Four months to incorporate the PR to fix it. :(

Cheers. :cowboy:
[Android Software Development] curiousrom:
Re: Testing Open GApps Packages Before Releasing Them

I never said it was & that was not my point.

How about almost 2 years to check the priv-app permissions with a script? ;)

See the quote in this post.

It takes time to do stuff in volunteer based projects & that's expected.

***
[Android Software Development] Magendanz:
So, I did ultimately find a workaround: Adding WebViewGoogle to the gapps-config.txt allowed me to get through the Setup Wizard and Google Play Services sign-in. WebView implementation shows as "Android System WebView 94.0.4606.71" (which I assume it got from my underlying GSI) and everything seems to be working fine now.

Shouldn't it be installing WebViewStub for Android 7.0+, though?
[Android Software Development] Md Husain:
Hello,

In the open_gapps_logs file, there is a line, Google Pixel Features | false

So actually which devices it will support on?

Is it possible to force this features to support, making Google Pixel Features | true ?
[Android Software Development] WasikFahim:
Copied from log file: "INSTALLATION FAILURE: This Open GApps package cannot be installed on this

device's architecture. Please download the correct version for your device."

I'm using arm64 device (redmi k20 pro) but can't install test build of A12 open gapps. I've downloaded arm64 version though.
[Android Software Development] myxal:
Cheers.

TL;DR: Can any developer tell me if it's okay for a ROM developer to provide android version info only via the

ro.vendor.build.version.*

properties? (Ie. without the

ro.build.version.*

properties, which the opengapps installer is currently looking for).

I have a Nexus 4 which I'm keeping alive with CarbonROM (8.0, Android 10). Since one build about 6 months ago, opengapps stopped being installable, always complaining about insufficient android version. The version detected by opengapps installer would be 5.1.1 - which - I'm guessing - is the version of android the recovery is using.

After tinkering with the installer script to find out what's going on, I concluded that the properties that the installer is checking (ro.build.version.release and ro.build.version.sdk) are not present in any property file shipped by CarbonROM in the current build. I now have noticed however, there are ro.vendor.build.version.release and ro.vendor.build.version.sdk properties under /system/vendor/build.prop. Is this some new normal? Does opengapps need to fix the installer, or is this a broken ROM build?
[Android Software Development] ipdev:
Nice investigating and a good question. :)

The OpenGApps scripts can be a little confusing.

To clarify.

The installer script uses the SDK level.

# Get ROM SDK version
rom_build_sdk="$(get_prop "ro.build.version.sdk")"

[GitHub] - Installer script lines 1635-1636 - Link

The value found is compared to the OpenGApps build ($req_android_sdk) that you are trying to install.

# Check to make certain user has proper version ROM Installed
if [ ! "$rom_build_sdk" = "$req_android_sdk" ]; then

[GitHub] - Installer script lines 1651-1652 - Link

--

I checked CarbonROM 8 for mako.

Extracted and mounted the system image.

The system build prop does contain ro.build.version.sdk.

Part of the system/build.prop

# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Sat Nov 20 05:22:56 CET 2021
ro.system.build.date.utc=1637382176
ro.system.build.fingerprint=google/occam/mako:5.1.1/LMY48T/2237560:user/release-keys
ro.system.build.id=QQ3A.200805.001
ro.system.build.tags=release-keys
ro.system.build.type=user
ro.system.build.version.incremental=033719fce0
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=google
ro.product.system.device=mako
ro.product.system.manufacturer=LGE
ro.product.system.model=Nexus 4
ro.product.system.name=occam
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QQ3A.200805.001
ro.build.display.id=QQ3A.200805.001-carbon@saturn.carbonrom.org
ro.build.version.incremental=033719fce0
ro.build.version.sdk=29
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10
ro.build.version.security_patch=2021-11-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Sat Nov 20 05:22:56 CET 2021
ro.build.date.utc=1637382176
ro.build.type=user
ro.build.user=carbon
ro.build.host=saturn.carbonrom.org
ro.build.tags=release-keys
ro.build.flavor=carbon_mako-user
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=mako
# Do not try to parse description or thumbprint
ro.build.description=occam-user 5.1.1 LMY48T 2237560 release-keys
ro.carbon.device=mako
# end build properties

Not sure why SDK29 is not found for you. :unsure:

Cheers. :cowboy:

PS.

I charged mine up and will test once I (re)partition it. ;)
[Android Software Development] myxal:
Thanks for taking a look at this.

Interesting. 🤔 I only checked the system partition (didn't have a linux box ready) after installing CarbonROM with TWRP, and manually resizing the partition (via adb shell):

# e2fsck -fy <system partition>
# resize2fs <system partition>
# e2fsck -fy <system partition>

I just installed the ROM again, without resizing or checking the partition - that file exists but is empty.

My /system/addon.d only has "50-hosts" and "70-gapps" in it, and none of those touch the file AFAICT. Is there anything else that might be touching the system partition after the image is written to the partition? (aside from CarbonROM's own installer, which I'm just about to check)
[Android Software Development] myxal:
I think I see what's going on...

CarbonROM ROM's system partition image is sized to 1.2 GiB.

The image of the system partition itself does not contain the build.prop file - it's part of the zip archive as a dedicated file.

The 1.2G partition size is not enough for opengapps nano, which I wish to use.

opengapps' addon.d script backs up opengapps and restores it after a new CarbonROM system image is recorded on the partition. Crucially, this happens before I have a chance to manually resize the partition to fit opengapps (my system partition is 2 GiB)

(My guess) The system.build prop should be copied after the addon.d scripts are executed.

However, restoring the opengapps backup onto the not-yet-resized system partition exhausts all free space, so when the installer tries to copy build.prop file, it only manages to create the directory entry, but doesn't copy any data. (How the **** is this not detected as an error is beyond me.)

My question for opengapps would be - does the opengapps backup contain anything that's not in the installer? (I would just nuke the system partition before installing CarbonROM and installing opengapps as "new")

I used to have an addon.d script to do the resize automagically during ROM installation years ago, but recall it not working for some reason. I found and will try this one to see if it works.

EDIT: I got the script working (the payload version from here), and was a bit surprised - the filesystem was grown, and the gapps script executed with errors on chcon (couldn't change context), so actually I ended with a filesystem filled less than it was before. (0.8 GB vs 1.2 GB). Nevertheles, build.prop was copied successfully and opengapps installation worked without issues.
[Android Software Development] dwardo:
Bootloop here with open_gapps-arm64-11.0-nano-20211203.zip

Went back to 20211125 that works
[Android Software Development] osm0sis:
In before curiousrom! 😆

Reported it to the team. 👍

Any in between those working?

Edit: Also some logs of the bootloop and GApps install would be nice to help narrow it down.
[Android Software Development] curiousrom:
Bootloop thrown back to recovery reported on clean install of Galaxy S III Neo (Samsung Camera) (s3ve3gjv) + LineageOS 18.1 + open_gapps-arm-11.0-nano-20211203 here.

***

Edit: @Nezorflame added build date as reported by the user.

**
[Android Software Development] dwardo:
Bootloop to twrp to be precise

Haven't tried anything in between

I can redo install to get you a last_kmsg.log and install.log. Anything else you need ?
[Android Software Development] dwardo:
Attached are the gapps install logs.

Can't find the previous kernel log... Don't have /proc/last_kmsg or /sys/fs/pstore/console-ramoops
[Android Software Development] curiousrom:
@Nezorflame - A user reported here bootloop with Nano but not with Pico: open_gapps-arm-11.0-nano-20211202.zip on Nexus 7 & clean install of official LineageOS 18.1.

***
[Android Software Development] sevenrock:
Hi,

Play Store and Play Services seem out-of-sync:

using this tree

Files · c595fb978256a0a8ae191aa3c8383d91f1f6bb03 · OpenGApps / arm64 · GitLab

ARM64 sources and releases for OpenGApps https://opengapps.org/?arch=arm64

gitlab.opengapps.org

with opengapps included into my private los-18.1 build using https://github.com/opengapps/aosp_build

Will try to revert https://gitlab.opengapps.org/opengapps/arm64/-/commit/8810d419f3e0806aae3bb41a9bd4d493bfa96dbb in the next build and report back.

EDIT 1: Was not enough, will try to remove the Google Play services from Nov 29th as well...
[Android Software Development] Game-R:
Hi there,

Would like to inquire if it's a known issue that Open GApps would break Wi-Fi Direct and Miracast?

I have a Sony Xperia Z5 flashed with an Android 7.1.2 ROM that I use for a car diagnostic display that was able to connect to a Hudway Cast device that uses the Miracast protocol. I've discovered that upon completing running 7.1 version of Open GApps Aroma installer, to remove some apps I don't want in the phone (I don't want GMail and YouTube that came in the ROM to take up space and memory), the device isn't able to detect any wireless (Miracast) displays.

I also noticed that the Wi-Fi Direct configuration page, that was working fine before, is completely dead: Clicking on "Search For Devices" would do nothing and upon attempting to rename the device would result in a "Failed to rename device" error message.

I've tried installing all of the GApps and selected not to remove any of the LineageOS or AOSP programs to see if there was something I was removing or not including in the installation that was causing this problem, but I found that regardless, after completing GApps installer, the phone's Wi-Fi Direct and Miracast capabilities just dropped dead.

Any advice on this and what I would need to do to get Miracast working on my phone would be greatly appreciated!

Thank you
[Android Software Development] runekock:
@Game-R

OpenGapps is designed to add GApps to a rom without it, not remove functions from a rom that included GApps from the start.

It's likely that OpenGapps makes a mess of the roms included GApps, because files are stored in different places. Don't do this.

Instead, you should research ways to de-bloat your rom. To some extent, you can delete apps by just deleting their files from the system partition. But it will be a trial and error process to find what you can remove without breaking other things. Or go the simpler route: deactivate the apps in settings without removing them fully.
[Android Software Development] ALTracer:
Got some logs for you.

After trying to update open_gapps-arm64-11.0-super 20211112->20211204, my phone failed to boot. Reverting to 20211125 achieved successful boot, but apps are old (and Play Store offers updates).

Apparently Wellbeing now requires android.permission.REAL_GET_TASKS and android.permission.START_TASKS_FROM_RECENTS.

Regarding @curiousrom 's suggestion. Can your team at least try your biggest arm64 `super` packages on some Android-capable Raspberry Pi 3/4 before rolling them out into production? Why did the script detecting permissions miss this?

Phone: santoni 3/32

ROM: LineageOS 18.1 20211111 mi-msm8937 landtoni unofficial by 0xCAFEBABE (nevermind the raven fingerprint).
[Android Software Development] curiousrom:
@Nezorflame - Please remove the broken builds from the server ASAP!

Oh My Gosh, the bootloop was reported 48 hours ago in this thread & on Telegram and hundreds of users keep on downloading the broken builds, wasting their time & posting about it. :(

A OnePlus 7T + LineageOS 18.1 reported it here in the LOS subreddit and @haggertk who is one of the 9 Lineage Project director posted in it:

"Opengapps is perennially broken. You can play whack-a-mole and start picking older and older packages until you find a non-broken one, or use MTG, which is actually tested, instead."

This is so bad for the Open GApps Project's reputation. :( 🤦‍♂️

This is a draft and the commit is not merged yet but LineageOS is about to add a warning against Open GApps in it's wiki: https://lineage.harryyoud.co.uk/318857/2/gapps.html :

***
[Android Software Development] TheDarkDefender:
+1

Noticed this twice. On a nexus 6.

Sent from my Nexus 6
[Android Software Development] dkm911:
Yep. If we don't disable Keep awake for Google Play Services, then it will keep waking the device, like yesterday, it kept awake for 12 hours. When I disable the awake, it then shows FCs constantly especially when using location service apps.
[Android Software Development] D@rekills4:
Exactly. This is very annoying and this issue is not present on older OpenGApps versions.

Please fix guys.

Basically the phone does not sleep ever if these two things aren't disabled. It will always stay awake and battery will be drained out rapidly.