yashsingh1/xdaforums huggingface dataset:
[Android Software Development] 5HE5:
I'm running Android 12 on my Galaxy S10+ and always getting into a bootloop once I flash the 12 gapps (arm64).

Thanks for your work tho.
[Android Software Development] olifee:
I'm unsure whether this is a bug with OpenGApps and whether to report it on the GitHub repository, so asking here first.

I am using LineageOS 18.1 on a OnePlus 6 (enchilada) device. Google Pay is set up and works.

However, the QuickAccessWallet service is not working, i.e. the "Cards & Passes" toggle is not there in settings, and it's not showing up in the Power menu.

Checking a logcat during boot, I find:

12-23 00:42:29.791 1003 1003 W PackageManager: Failed to scan /system/system_ext/priv-app/QuickAccessWallet: Application package com.android.systemui.plugin.globalactions.wallet already installed. Skipping duplicate.
...
12-23 00:42:52.778 2173 2291 D PluginInstanceManager: Plugin doesn't have permission: com.android.systemui.plugin.globalactions.wallet
...
12-23 00:44:02.035 12627 12684 D InstalledAppProviderSer: insertAppIntoDb com.android.systemui.plugin.globalactions.wallet

I find the plugin twice in my /system partition, once in /system//priv-app/QuickAccessWallet and once in /system/system_ext/priv-app/QuickAccessWallet.

I guess one version is from OpenGApps and one from LineageOS. Is this expected? Is the permission error a ROM issue, or is some permission whitelisting to be added to the OpenGApps package?
[Android Software Development] ipdev:
@olifee

I do not use GooglePay (or have a OnePlus 6 [enchilada]) so, I do not have first hand experience.

I did a quick check and dumped the lineage-18.1-20211221-nightly-enchilada-signed build.

The QuickAccessWallet.apk in system_ext/priv-app/ is from LineageOS.

package: name='com.android.systemui.plugin.globalactions.wallet' versionCode='10000000' versionName='1.0.0.0' compileSdkVersion='30' compileSdkVersionCodename='11'
sdkVersion:'30'
targetSdkVersion:'30'

Same version OpenGApps is using.

package: name='com.android.systemui.plugin.globalactions.wallet' versionCode='10000000' versionName='1.0.0.0' compileSdkVersion='30' compileSdkVersionCodename='11'
sdkVersion:'30'
targetSdkVersion:'30'

I am a bit confused because OpenGApps includes it in the all/app/ sources so it should be installed into /system/app/ but when I checked on a device I have Lineage 19 and OpenGApps Stock installed..

find / -name 'QuickAccessWallet.apk' 2> dev/null;
/system/priv-app/QuickAccessWallet/QuickAccessWallet.apk
/system/system_ext/priv-app/QuickAccessWallet/QuickAccessWallet.apk

Not quite sure why it ends up in /system/priv-app/ :unsure:

Will look into it a bit more tomorrow night. ;)

Cheers. :cowboy:
[Android Software Development] olifee:
@ipdev Many thanks for looking into it!

So it seems from the logcat that in my case, the version from OpenGApps is loaded first / preferred and gets the permission error.

I guess the install location comes from here:

opengapps/scripts/inc.buildtarget.sh at d1db9bd9e01afa934f5787095e3c4a7a1303972d · opengapps/opengapps

The main repository of the Open GApps Project. Contribute to opengapps/opengapps development by creating an account on GitHub.

github.com

Hope this helps and cheers :)
[Android Software Development] PanosT:
Hey, can anyone make a zip file of gapps Android Auto addon? With out checking for gapps been installed?

Its for microg use

Also i need an older version of AA v.6.0

I already have v.6.6.6

Thanx
[Android Software Development] olifee:
@ipdev Happy new year to you!

Any further ideas on QuickAccessWallet? Do you also see the permission error and / or do you see QuickAccessWallet in the power menu, btw.? I think it should also show up even if Google Pay is not set up (to advertise setting it up).

Since QuickAccessWallet seems to be included in LineageOS (it seems the code has been open-sourced), I wonder whether things would work in case QuickAccessWallet was removed from OpenGapps?

Is there a clean way to do that for an existing installation?
[Android Software Development] tramp20:
Hi,

where can I find a GAPPS for Android 12 ARM Lineage OS 19?

Thank you.
[Android Software Development] zimral.xda:
look at #7219

OpenGApps UNOFFICIAL - MediaFire - Link

The Android 12 versions are in the SDK31 folder.

But be aware that this is a REAL EARLY release.

I would not take them for any device in production
[Android Software Development] yujincheng08:
setupwizarddefault-x86_64 is accessing a deleted field isCarrierAp of apex package android.net.wifi​

setupwizarddefault-x86_64 is accessing a deleted field isCarrierAp of android.net.wifi.ScanResult and crashes. Since this package (com.android.wifi) is apex so it will be updated by Google automatically and EVERY x86_64 Android 11 device with openGApps installed will crash (bootloop) by this issue after com.android.wifi is updated by oepnGApps itself.

FYI, This field is removed in this commit: https://cs.android.com/android/_/an...fi/+/c50556db869a1caefab533c64ab640a6ba1ae934
[Android Software Development] yujincheng08:
https://api.opengapps.org/list is broken on Linux (as well as Android) but it works fine in Windows.

Simply `curl -v https://api.opengapps.org/list` in termux and you will see an error: transfer closed with outstanding read data remaining

EDIT: recovered
[Android Software Development] osm0sis:
Also, builds are still paused since 20211221? Intentional, or something broke and nobody noticed yet?
[Android Software Development] curiousrom:
I noticed and was glad that the crazy machine churning out daily untested builds was finally stopped.

Better 1 good build a month and stick with it if no issues are reported IMO.

***
[Android Software Development] Stamgastje:
I today tried to install the latest 'pico' package (ARM/Android 11) on my OnePlus One phone running LineageOS 18.1, but this failed with the message that there is insufficient space.

Looking at the daily builds, I notice a 5.5MB increase between the Jan. 10 and 11 builds:

OpenGApps - Browse /arm/20220111 at SourceForge.net

OpenGApps daily releases

sourceforge.net

open_gapps-arm-11.0-pico-20220111.zip

119.9MB

OpenGApps - Browse /arm/20220110 at SourceForge.net

OpenGApps daily releases

sourceforge.net

open_gapps-arm-11.0-pico-20220110.zip

114.4MB

Is this intentional? Was some component added that increases the size, making it too big now for my phone?

(For now, I stick to the Jan. 10 build.)
[Android Software Development] curiousrom:
OnePlus One - Open GApps Pico Insufficient Space

If you sideloaded Open GApps it automatically creates a log named open_gapps_log.txt in the internal sdcard folder.

If you copied to the device the GApps...zip package & installed it from there manually using the recovery then the "open_gapps_log.txt" is created in the same location as the GApps...zip package.

Maybe you could attach that log to a post? Zip it if you have issues attaching it to a post.

***

You can make Pico smaller by excluding GoogleTTS with a gapps-config.txt file with this content:

Exclude

GoogleTTS

Copy the gapps-config.txt to the root of the internal sdcard if you are sideloading LineageOS + GApps from a computer.

Or if you are flashing from the device copy the gapps-config.txt to the same location as your open_gapps-arm-11.0-pico-......zip`.

See Open GApps Wiki - Advanced Features and Options.

***

You could unzip them & check the size of the different components. Check the "app_sizes.txt" in the root of the installation zip.

Or compare the respective open_gapps-arm-11.0-pico-....versionlog.txt.

I use DiffMerge to compare files. It works on Windows, OS X, and Linux.

The ...versionlog.txt are in the respective Open GApps Sourceforge folders or use the "VERSION INFORMATION" link in the bottom of https://opengapps.org/

***

That's fine.

Play Store, Play Services & libraries automatically update themselves in the background regardless of the user's update settings in Play Store.

When Google will feel that they need an update it will do it automatically.

As for the apps included in a GApps package you can either not update, manually update or chose automatically update in Play Store's settings.

***
[Android Software Development] Stamgastje:
Sure, see attached. Note: this is the log I get when having installed the Jan. 10 version of OpenGApps pico and then trying to upgrade to the Jan. 15 version.

Would you also need the file open_gapps_debug_logs.tar.gz?

Thanks, I'll consider that.

The two changes are:

vending-arm: 61028 (vs. 60844)

googletts-arm: 46476 (vs. 29512)

So indeed, it looks like package googletts increases significantly in size.

So if I understand it correctly, then there's no harm in skipping the googletts package during installation of OpenGApps. And I can still install and update the application via the Play Store -- right?
[Android Software Development] curiousrom:
Re: OnePlus One - Open GApps Pico Insufficient Space - GogleTTS

Thanks for the log & infos. :cool: 👍

No need for the "open_gapps_debug_logs.tar.gz" in this case.

Yes but there is no point in doing it in your case because updates to your open_gapps-arm-11.0-pico-20220110 package, including for GoogleTTS, will be downloaded to the /data/ partition which does not have the same size limitation as the system partition where the ROM + Open GApps was installed.

That would be helpful for a new clean install.

I never understood why GoogleTTS is included in Pico which is the Open GApps minimal installation package. ¯\_(ツ)_/¯

That app is not essential & can be installed later @ any time by the user if he wants it.

***
[Android Software Development] Stamgastje:
Thanks for the explanation, @curiousrom. Greatly appreciated!

Going forward, I'll then use the latest packages and exclude GoogleTTS.
[Android Software Development] curiousrom:
Could you please edit your post & add in the top part of it for which device and ROM you are talking about?

Is it about "AOSP on IA Emulator" on a computer?

***
[Android Software Development] banzeo:
Yes, in the android emulator, with a system-image as provided by the SDK Manager, from google (original post edited as per your request)
[Android Software Development] G A S T:
I would appreciate when an android 12 Pico test build would be released soon. Since there's already the Nano Version, that shouldn't be a huge effort.
[Android Software Development] Flounderist:
Noob question here: are the Gapps controlling in any way the Google System Services updates?

I am using arm64 nano package and my log is flooded with failed system update warnings.

I am using an old (early December) build. The issue started a couple of weeks ago.

Device is a Realme X2Pro (RMX1931) running an unofficial LOS 18.1 build with November security patches.

Any hint?
[Android Software Development] Cyndaquissshhh:
LineageOS cannot take Google Play system updates straight from the Play Store. Maybe your device is trying to get updates and Google's servers reject it
[Android Software Development] ipdev:
Device Type | tablet is the reason.

Currently there is nothing to determine if a tablet is Mobile (LTE) or WiFi only.

A while back I was looking for a prop or prop value to use to determine it.

26.Dec.21 was the newest file date in that test folder.

OpenGApps Installer script [GitHub] Link

# If $device_type is not a 'phone' make certain we're not installing messenger
if ( contains "$gapps_list" "messenger" ) && [ $device_type != "phone" ]; then
gapps_list=${gapps_list/messenger} # we'll prevent messenger from being installed since this isn't a phone
fi

If you follow the GitHub link, you can scroll up and down from there and see all the app/services that are not installed on tablets or TV boxes.​

Once a way to determine a Mobile/LTE tablet, it could then be changed to.

# If $device_type is not a 'phone' or 'tablet' with mobile data make certain we're not installing messenger since it is not supported by the device.
if ( contains "$gapps_list" "messenger" ) && [ $device_type != "phone" ] && [ $tablet_type != "mobile" ]; then
gapps_list=${gapps_list/messenger} # we'll prevent messenger from being installed since this isn't a mobile device.
fi

I haven't had time to work on this more.

If any one has suggestions or wants to look into it. 🙃

OpenGApps Installer script [GitHub] Link

if echo "$(get_prop "ro.build.characteristics")" | grep -qi "tablet"; then
device_type=tablet

The rough WIP I was last using.

if echo "$(get_prop "ro.build.characteristics")" | grep -qi "tablet"; then
device_type=tablet
if echo "$(get_prop "ro.telephony")" | grep -qim1; then
if [ $? -ne 1 ]; then
tablet_type=mobile
fi

It has been a while and I do not remember if I ran into an issue using ro.telephony

I did not leave myself a note about it but, I thought I found it set on a WiFi only tablet or an LTE tablet that did not include it. :unsure:​

Cheers all. :cowboy:
[Android Software Development] Flounderist:
I think so. Here is screenshot of the error I get in matlog:

I was wondering if it is a ROM or Gapps issue.
[Android Software Development] Black_Eyes2:
Redmi k40 pro, twrp 3.6, magisk 24.1, android 11, miui 12

BootLoop with latest opengapps pico build (09/02/2022)

I never had a bootloop before, don't know what to do to fix it
[Android Software Development] Black_Eyes2:
I'll flash stock rom and keep stock gapps and never use openGapps again ^^

EDIT: flashed it, installed twrp and magisk again. I won't try to redo the opengapps things.
[Android Software Development] Flounderist:
Did you checked if the ROM that you was flashing was already providing for Gapps itself?
[Android Software Development] Cyndaquissshhh:
Oh... is there any way to force those apps to install?
[Android Software Development] luisl173:
Any news about Android 12 packages apart from the test build?
[Android Software Development] Homewrecker:
Anyone else here experiencing issues when trying to pair their Google TV remote?

When I perform a clean install of Lineage OS 18.1 for ATV on my RPI 4, I can pair my remote.

When I flash the opengapps package, the pairing fails every time saying "Could not pair".

There is an issue open on the opengapps github (https://github.com/opengapps/opengapps/issues/915)

Anybody know a workaround for this, because my Android TV is quite useless without a working remote :)

Thanks in advance.
[Android Software Development] Darth Bidder:
I have a Redmi 7 and I installed LOS 18.1.

I'm stuck on the setup wizard, I can't get past the copy data part.

I just reinstalled LOS.

I can't tell if it's LOS latest update or the OpenGAPPS Aroma Feb 5 build.

So I'm stuck with the copying data part where it's just black screen but the back button is just right at the bottom but it doesn't do anything but vibrate the phone.

UPDATE: I got past the setup wizard by going offline but now the problem is I can't login to Google.

I just installed the Nano version of the Feb 2, 2022 build and it's not doing that issue, I guess it's one of the apps I installed that does that or the Aroma version itself is just bugged.
[Android Software Development] Lederhose:
Is the DialerFramework still included in OpenGapps? The wiki page about the config file mentions it, but as I understand, the Google dialer app has become available for most devices via the Play Store without further measures?

Is the following still an issue, as stated in the OpenGApps blog in 2016?

"It is important to note, that the DialerFramework only receives any security updates if you update your Open GApps installation and not via the Play Store. So make sure to update your Open GApps installation at least once a month, after Google’s monthly security updates are added to the Open GApps repository."

Google Dialer

OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.

opengapps.org

I don't want to use the Google dialer and I don't want the framework - it is not needed for anything else, right?
[Android Software Development] Cyndaquissshhh:
Aroma is no longer actively developed and might no longer work with newer recoveries. That could be your problem
[Android Software Development] HtHNightwolf:
Is it possible to get a test version of the arm version aswell?
[Android Software Development] Nezorflame:
Hi!

Unfortunately right now I don't have any spare time for opensource (due to the world's situation you're probably aware of).

I hope that I'll resolve my issues during March and will be able to continue in April. Until then, either someone from the community will step up with a custom build, or you could use some other gapps package.
[Android Software Development] ipdev:
I run arm/arm64 builds of pico, nano and stock for testing.

Once they are tested a bit and seem stable, I upload them to MediaFire.

MediaFire - Link

Android 12 builds are in the SDK31 folder.

The 20211218 builds include some permission updates.​

---

Last week I ran SDK32 builds to test on LineageOS.

LineageOS is merging 12.1.0_r1 into the 19.0 branch instead of creating a 19.1 branch.

LineageOS Gerrit - Topic 12L - Link

Edit: I just checked and see they decided to bump up to 19.1 a few days ago.​

Note:

Now that Android 12L is official, the release props still show as 12 not 12.1 or 12L.

The build tag was bumped to 12.1.0 and the boot image is now SDK32 but, the kernel version is still showing as 12.0.0

The boot image was SDK31 on the 12L preview release.​

The only way to determine if you are running 12 or 12L is by checking the SDK level.

SDK31 = Android 12

SDK32 = Android 12L

The initial 12L OpenGApps test builds were blind builds and untested.

I did not have a device/rom to test them on. 🙃

I few days later I was able to test them on a Pixel C, Lineage 19.0 SDK32 build.

Since it is a tablet, it utilized the large screen layout of SDK32.​

The 12L pico and nano builds seem to be safe.

The 12L stock build had issues with Pixel launcher so, I would suggest not using it for now.

Unless you are using a gapps config script to customize the install.

Android 12L (SDK32) test builds are currently on gDrive.

gDrive - Link

Everyone is welcome to give them a try.

Cheers all. :cowboy:

Edit:

See additional posts.

Post # 7,316

Post # 7,319
[Android Software Development] M1LL3R:
Thank you @ipdev builds for 12L working great!
[Android Software Development] Magendanz:
I don't see any notices on the blog, wiki or SourceForge explaining why there have been no builds posted since Feb. 15th. Has anyone heard anything?

UPDATE: Sorry, I hadn't realized that @Nezorflame was the maintainer and is located in Moscow. It's starting to make sense now.
[Android Software Development] maxed4901:
I tried nano - boots but has setup wizard issues.

Stock - didn't boot. Bootloops. Galaxy note 8

Galaxy s8+ nano doesn't boot.
[Android Software Development] master373:
Same for s7 bootloop on stock package
[Android Software Development] Sexy scientist:
Sorry for replying on an old post, but this is the only open GApps for arm64 android 12 I can find and tried flashing. It gives error 64 "This Open GApps package cannot be installed on this device's architecture. Please download the correct version for your device: arm". However, this package is labelled as arm64
[Android Software Development] guhvanoh:
I don't know what fone you have but it seems not to be of 'arm64' architecture. Go look for the 'arm' zip and try flashing that.
[Android Software Development] Sexy scientist:
I have sony xperia xz1 compact (lilac) G8441 which has armv8-a architecture. Little googling doesn't tell if it is 32 bit or 64 bit. I tried this GApps which failed. So, I am looking for one made for arm architecture, but I couldn't find any. Can you please direct me to one? Pico, nano, micro, anything is fine. I am desperate right now.
[Android Software Development] Cyndaquissshhh:
Wrong reply
[Android Software Development] Nezorflame:
No problem. I will update these in the near future, sorry for the wait.
[Android Software Development] Sexy scientist:
Based on the output of Open GApps, I downloaded mindtheGApps for 32 bit and got the output that the device is 64 bit architecture. I downloaded the 64 bit version and it flashed successfully. So, the point is that

this build has a bug in case of lilac.
[Android Software Development] ipdev:
armeabi-v7a and armeabi is 32-bit.

Normally just referred to as arm.​

armv8-a and arm64-v8a is 64-bit.

Normally just referred to as arm64.​

The architecture fix was merged after the 20211112 test build.

OpenGApps - GitHub - Commit - Link

If you want to give it a try, I gave a link to some newer test builds a previous post.

Post # 7,259 - Link

Cheers. :cowboy:
[Android Software Development] Sexy scientist:
Thanks. I want to test them, but I am not able to find a 12.0 rom for lilac which supports IMS features for my carrier (Reliance Jio).
[Android Software Development] abergmeier:
Is there a GOA for SDK32? With Lineage 19.1 the latest gapps I could find (SDK31) is not working :(
[Android Software Development] auspufftröte:
I can confirm that SDK31 (nano+stock) are not supported with LOS 19.1

"incompatible Android ROM detected.

This GApps pkg is for Android 12.0.x ONLY

Please download the correct version for

your ROM: 12 (SDK32)"
[Android Software Development] BillGoss:
Interesting! Android 12 is SDK 31 and 12L is SDK 32.

SDK Platform release notes | Android Studio | Android Developers

Discover release information about the SDK packages available for download from the SDK Manager, in the SDK Platforms tab.

developer.android.com
[Android Software Development] master373:
Yes you can define 12L as an new major android version
[Android Software Development] Darth Bidder:
Just an update to this issue.

I used Feb 5, 2022 builds. I've tried nano ,super, full, then stock in different installs. I've been using a gapps config which I got when I was using the Aroma variant before.

I've narrowed it down to full and stock variants using my config until I removed "Android System Webview" from my config and that resolved my issue.

I have GCS on that config but that's the only app I want to install from the Super variant so I didn't bother testing that one out.
[Android Software Development] Brad2607:
Does anyone know where to get the latest GApps that works with Lineage 19.1 on Pixel C?

I can't seem to find any for Android 12?
[Android Software Development] master373:
You can try nikgapps, flamegapps etc
[Android Software Development] BTW lover:
Can you guys tell me what minimum open gapps package is needed to make voice input work? Whenever I try to use voice input (Gboard keyboard, Google search etc.) My phone doesn't seem to recognize any voice input. It starts the input (like speak now...) but no sound input us recognized.

I feel like maybe, with the nano install I use, there might be a Googly bit missing somehow.
[Android Software Development] diemadedrei:
Now that los 19 is official, has anyone tested these builds? Or are there newer ones somewhere?
[Android Software Development] a9381:
can't install open Gapps on LineageOS 18.1 (Android 11) with OpenGapps app...

i download&install the app

The Open GApps Project

OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.

opengapps.org

app/opengapps-app-v16.apk

And I can't choose my Android version.

The highest Android version you can choose is 7.1, and my device is identified as Android 7.
[Android Software Development] Darth Bidder:
Why not just download it normally on their website instead of using their app?

If you don't know the CPU architecture of your phone, you can download an app like CPU-ID on the Play Store.
[Android Software Development] josephcsible:
I tried the stock 12L build on LineageOS 19 on a Moto X4, and (as others have mentioned upthread) it bootlooped.