yashsingh1/xdaforums huggingface dataset:
[Android Software Development] jailedmike:
Did I miss telegram group link in there somewhere?
[Android Software Development] Darth Bidder:
I used the 20210130 AROMA version of the test build OpenGAPPS for Android 11, the GUI ran fine and installation went well as normal.

My phone was on a LOS 18.1 custom ROM and everything is working normally.
[Android Software Development] esieben1310:
I tried to build Adroid x86 with Opengapps but i got this error:

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=9

TARGET_PRODUCT=android_x86_64

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_ARCH=x86_64

TARGET_ARCH_VARIANT=x86_64

TARGET_2ND_ARCH=x86

TARGET_2ND_ARCH_VARIANT=x86_64

HOST_ARCH=x86_64

HOST_2ND_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-4.19.0-16-amd64-x86_64-Debian-GNU/Linux-10-(buster)

HOST_CROSS_OS=windows

HOST_CROSS_ARCH=x86

HOST_CROSS_2ND_ARCH=x86_64

HOST_BUILD_TYPE=release

BUILD_ID=PI

OUT_DIR=out

============================================

[1/1] out/soong/.minibootstrap/minibp out/soong/.bootstrap/build.ninja

[55/56] glob prebuilts/ndk/cpufeatures.bp

[77/77] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja

out/build-android_x86_64-cleanspec.ninja is missing, regenerating...

out/build-android_x86_64.ninja is missing, regenerating...

[95/572] including external/IA-Hardware-Composer/Android.mk ...

"PLATFORM_VERSION 9"

"ANDROID_VERSION 9"

[503/572] including system/sepolicy/Android.mk ...

system/sepolicy/Android.mk:79: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version

[572/572] including vendor/opengapps/build/modules/Android.mk ...

WARNING: No APK found compatible with API level 28 for package com.google.android.setupwizard.default on x86_64

WARNING: No APK found compatible with API level 28 for package com.google.android.setupwizard.default on x86

ninja: error: out/soong/build.ninja:408283: multiple rules generate out/soong/.intermediates/frameworks/base/core/res/framework-res/android_common/aapt2/vendor/opengapps/build/overlay/tvmini/frameworks/base/core/res/res/values_config.arsc.flat [-w dupbuild=err]

15:52:18 ninja failed with: exit status 1

#### failed to build some targets (03:03 (mm:ss)) ####

First i got this error:

tools/test/connectivity/Android.mk: error: ActionsServices: No source files specified

I fixed it by adding this two commits: https://github.com/esieben1310/aosp_build/commit/93bd1a536589b0b2fb26ae45d96283b18800e162 https://github.com/esieben1310/aosp_build/commit/19ba605f14dc6d5bd340deba4e909cbc4184c701

How can i fix this error?
[Android Software Development] dwardo:
AA and my car head unit are not happy (Usb device is not compatible) using los18.1 on my nexus 6 and opengapps 11 nano 20210130.

Switched to MindTheGapps recommended by Lineage, where everything works, until there is good news from opengapps 10 and 11 regarding AA...
[Android Software Development] Cavaler:
Looks like it. You are certainly not the first with Android Auto not working.
[Android Software Development] massima:
Flashed successfully on crdroid 7.5 the opengapps 11 beta pico package even though is old (30/01), no issues!;)
[Android Software Development] Revan335:
Any News about a Release for Android 11 on the opengapps.org Site?

The many month old Beta from Sourceforge is not Stable?
[Android Software Development] ashh87:
Hi,

I'm trying to get family link set up (Lineage 17.1, arm) and it's failing when I run the setup wizard. When I log in using a parent account and wait until play services is updated, I can then complete the process when I add new user to the phone.

I wondered if this was to do with the play services version in OpenGApps? I've attached the section of my logs where the failure happens [edit: uploaded here]. The line 'ChimeraProxyRslvr: Chimera config error: com.google.android.chimera.config.InvalidConfigException: No registered Chimera impl for com.google.android.gms.kids.KidSetupActivity' looks like it could be the source of the failure, but I can't find much information about how chimera modules work.
[Android Software Development] hayvan96:
Hi, does this mean that we'll have a new beta soon? https://github.com/opengapps/opengapps/pull/885/commits/35ec5e58d189ce5495d6a9f5b220474e6767d4c5 (when this commit is merged)
[Android Software Development] osm0sis:
Not necessarily. It just means Nezor is catching up his eleven branch with fixes that were made to the main branch.
[Android Software Development] SteveMKII:
I'm also having the same issue and got the same message. I'm using crDroid 11. Did you try any of the older builds of opengapps? Maybe I'll give MindTheGapps a try in the meantime. AA is pretty much the only reason I still have gapps on my phone at all.
[Android Software Development] SteveMKII:
Interesting. I installed Android Auto into the system on my Moto G5 Plus crDroid 7.5 (Android 11) with the 2020-01-30 open gapps aroma and it doesn't show up in the launcher, but it shows as installed. Not sure if that's related to the AA issue or not but maybe it's worth mentioning?
[Android Software Development] dwardo:
On 11 I did not try older builds

On 10 2020-02-06 works
[Android Software Development] SteveMKII:
Thanks for getting back to me. I found a solution for Android 11, I am just about to write up a post detailing it
[Android Software Development] SteveMKII:
Ok I found a solution for getting Android Auto working which I have written about here. It looks like you need to have the little stub app installed in the system. I don't know why but that will make it work. It comes from the MindTheGapps package. @MastahF would it be possible to include the stub apk I attached in my linked post in your next OpenGapps 11 build?
[Android Software Development] Vinnom:
I don't think he involved with the project anymore. Quoting Nezorflame or maybe even Osm0sis would be better for this I think
[Android Software Development] osm0sis:
He's still involved, just not active in development beyond merging PRs and such; more on the infrastructure side:

Signature stripped · Issue #913 · opengapps/opengapps

V2 and V3 signature stripped in apk files: $ apksigner verify Phonesky.apk DOES NOT VERIFY WARNING: No SourceStamp signature ERROR: JAR signer BNDLTOOL.RSA: JAR signature META-INF/BNDLTOOL.SF indic...

github.com

But, makes sense, I guess the stub updates to the full app and then all the missing libs or whatever are provided by the updated APK. @Nezorflame is your guy, for sure. :)
[Android Software Development] ipdev:
Just to note.

Nezorflame replied in the AA thread. ;)

Android Auto and Lineage 17.1 - Post # 18 - xdaThread - Link

Cheers all. :cowboy:
[Android Software Development] hayvan96:
And new test builds are out ❤️
[Android Software Development] Nezorflame:
Hi everyone.

As mentioned, I've made a new quick test build for ARM64 only, nano and stock packages.

I *hope* that Android Auto is fixed by the inclusion of the stub APK, which is now present in nano+ packages. Installer script should ignore it if the normal Android Auto APK is present in the package instead.

Also this build should have proper webview - trichrome - chrome packages, so hopefully this will work as well.

I'll test it myself later but would love someone to check.

https://sourceforge.net/projects/opengapps/files/arm64/test/20210513/ here's the link, please report any issues you've found.
[Android Software Development] Magendanz:
I'll check this weekend on ARM64, but I can also test ARM on the Galaxy Tab A 10.1 2019 as soon as it's ready.
[Android Software Development] d7F=Dtcddt/:
Hi, i meet a problem with 20210513 nano version, which google play service can't access SMS and call log persion. So I can't restore my phone with android setting tutorial. Anyone face the same pronlem? I clean flash lineageos 18.1.

emm……google play service permission, SMS and call log can't set allow.

when setting android setting tutorial , it shows google play service error. Please cpmplete action required by Android setting tutorial.

Edit: it soved with a kind man named hwrkt on telegram. which is delete /data/misc_de/0/apexdata/com.android.permission/runtime-permissions.xml.

after doing this and restart it, the phone worked. Thanks man
[Android Software Development] Magendanz:
So, my initial smoke test of open_gapps-arm64-11.0-stock-20210513-TEST failed during the SetupWizard with a black screen after the "Checking for updates..." page. If you do an offline setup to bypass that step, however, things look pretty solid.

Testing was on AOSP11, CAOS11 and LineageOS 18.1 GSIs.
[Android Software Development] dreDREb13:
Anyone know the protocol for updating from the test version of Android 11 GApps to the official release when that finally gets added? Would this require re-flashing your current ROM or wiping data? Or should you just be able to adb sideload on top of your current working ROM and GApps?
[Android Software Development] r6680jc:
Just sideload the Gapps should be enough.
[Android Software Development] G A S T:
Will the next OGApps test builds for A11 include again all packages like the ones released in january? 🤔

That would be great. ✌️
[Android Software Development] @RMIN:
Hi everyone.

Last night I received a Lineage update alert (18.1-20210529) for hlte. Since I installed a custom Open GApps on my device with the help of its configuration file and deleted the stock apps, everything seemed good until after installing the lineage update (2021-05-29) that removed those which Open GApps installed and reinstalled the stock apps! What should I do to prevent this?

here the config file and the log file.
[Android Software Development] macgyver77:
Thanks for this new build and the ongoing effort to bring OpenGApps to R!

I'm using the stock build with LineageOS 18.1 and things are working nicely so far. To be honest, I don't have a car to test Android Auto, atm. However, the stub behaved as supposed - as soon as I tried to use AA settings etc., I was sent to Play Store to update the app, and as soon as it was updated, the functionality was there.

One thing only: I believe I might have found a glitch in the installation logic for the Android Auto Stub. Wondering why the stub wasn't installed even though I excluded the "full" Android Auto in gapps-config, I realized that the string "androidautostub" contains "androidauto". So, the logic in the installer script

# If we're installing androidauto AND androidautostub we MUST REMOVE androidautostub from $gapps_list (since it's not required)
if ( contains "$gapps_list" "androidautostub" ) && ( contains "$gapps_list" "androidauto" ); then
gapps_list=${gapps_list/androidautostub}
fi

that tries to exclude that both the full app and the stub are installed at the same time, _always_ excludes the androidautostub package from gapps_list , because it _always_ finds the string "androidauto" within "androidautostub".

When I renamed the stub package to "androidautstub" to avoid "androidauto" within this string, the installer behaved as supposed and installed the stub when the full androidauto package was excluded.

(My first idea would have been to rename the "androidauto" package to "androidautofull", so that a more specific check for this full package becomes possible, but then I realized that this would break backward compatibility with every existing gapps-config that tries to either in- or exclude androidauto...)
[Android Software Development] tomKater:
Hi,

Thanks for the work ! Do you have an idea when the "arm" version could be out ?

Thk.
[Android Software Development] Darth Bidder:
Stop asking about an ETA for a release in general. It will be released when it's ready to be released.
[Android Software Development] Nezorflame:
Thanks, that's a great insight and an error on my end.

I've renamed androidautostub to gearheadstub, thus we wouldn't have any collisions anymore (gearhead is just another name for Android Auto, so for now this seems fitting).

I'm rebuilding the packages ATM, so a new test build is coming soon.
[Android Software Development] FriendlyNeighborhoodShane:
Hi! I was vendoring some of the older APKs from your gitlab repo for a project of mine, but I ran `apksigner verify` on them and they failed to verify with serious errors (like dex entries being missing).

I've obtained replacement APKs from various sources. These replacements pass the verification and you can compare the fingerprints given by `apksigner verify --print-certs` to make sure of their authenticity.

How can I submit these replacements to the repos?
[Android Software Development] Flamefire:
Using the Google Package Installer uninstalling an app like WhatsApp fails with an exception: Using the Google Package Installer uninstalling an app like WhatsApp fails with an exception:

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity}:
java.lang.IllegalArgumentException: Invalid UUID string: CD28-EB81

IIRC this is due to a "bug" in the framework that returns those short UUIDs for SD cards which are not valid UUIDs (for the functions used)

LOS has fixed that with LineageOS/android_frameworks_base@6d687f0 but the OpenGapps doesn't seem to have the fix so it still crashes.

I've seen that the Google Package Installer gets installed after #591 so maybe it would be better to not do that for certain ROMs? Maybe via some ROM option?
[Android Software Development] bojan.1995:
Can somebody send me older version without Google Searchbar, not fun.

Android 6 Arm.
[Android Software Development] ipdev:
Pico build does not contain Google Search.

OpenGapps Wiki [GitHub] - Package Comparison - Link

---

You can also customize the install using a gapps-config file.

OpenGapps Wiki [GitHub] - Advanced Features and Options - Link

Since Exclude is the default, you just need a config file that contains Search.

Search

Nano and above will exclude Google search when you install OpenGApps.

---

If you install the Nano package and use the Include config from the the Wiki, comment out Search.

Include

# Pico+
CalSync # Install Google Calendar Sync (if Google Calendar is being installed)
DialerFramework # Install Dialer Framework (Android 6.0+)
GoogleTTS # Install Google Text-to-Speech Engine (Micro+ on 5.0-, Pico+ on 6.0+)
PackageInstallerGoogle # Install Package Installer (Android 6.0 only & Android 8.0+)

# Nano+
BatteryUsage # Install Device Health Services (Android 7.1+)
Markup # Install Markup (ARM64 + Android 9.0+)
# Search # Install Google App (excluding excludes GoogleNow/PixelLauncher)
SoundPicker # Install SoundPicker
Speech # Install Offline Speech Files
Wellbeing # Install Digital Wellbeing (Android 9.0+)

You will get the four from Pico and five out of six from Nano.

Google search is commented out so it is ignored and will not be installed.

Cheers. :cowboy:
[Android Software Development] hayvan96:
So 11 is finally officially available (pico/nano only)!
[Android Software Development] G A S T:
This is nothing new and was anounced yesterday via TG. But the still open question is, if Pico does include the stub app for Android Auto or not to make it work again. There is no description that explains this circumstance. Can anybody of you tell me and the other AA interested people, if AA works again with the official pico build of today or not?

Sadly, there are no "notes for Android 11" in github or gibt's in the two package descriptions for pico or nano. These are the places, where this Information should be found.

Personally I'd like to see AA stub in the pico package. Everybody who does not want that can easily perform an exclude install for AA stub via configfile.
[Android Software Development] Nezorflame:
Yup, it's true - we have released pico and nano versions to the public.

Other variants are coming as soon as we confirm that everything's working properly.

Android Auto stub is coming to the pico as well in the next build. I'll update the release notes and Wiki as soon as I have a bit of free time, stay tuned.
[Android Software Development] curiousrom:
I updated the wiki https://github.com/opengapps/opengapps/wiki/Package-Comparison and the respective package pages.

Could you edit the Android 11.0 state in https://sourceforge.net/projects/opengapps/files/ please?

BTW thanks for all the fish. :cool: 👍

***
[Android Software Development] G A S T:
Is there any way to bring back the app icon of AA to use it standalone without connecting the device to the car? 🤔

Update:

Well, 💩.

I tried everything today after updating LOS 18.1 with the latest build of today manually together with the latest OpenGApps pico package from today with gearheadstub.

It does not work.

The device just won't connect to the car media system via USB. I can do what I want - nothing helps... ☹️

Any useful suggestions?

What can I do now?
[Android Software Development] Usemyass:
GPS Not working on Samsung S4 mini LOS18.1 ARM
[Android Software Development] curiousrom:
If that's the ROM you are talking about Search this thread with GPS: [ROM][I9190/I9192/I9195][Unofficial][11.0.0] LineageOS 18.1 for S4 Mini or ask for help there.

***
[Android Software Development] Usemyass:
Yes that is the one, open_gapps-arm-11.0-nano-20210110-TEST is working fine, latest open_gapps-arm-11.0-nano-20210717 is not working, i only want to contribute this
[Android Software Development] emuandco:
Well. Right now AA does ... Something. Wired and wireless a black window pops up and stays there forever. Car says nope. ^^ i use yesterday's Nano arm64 android 11 version here. And official yesterday's Lineageos 18.1 on hotdog.
[Android Software Development] G A S T:
Yep, but it does not connect, like I stated here already on Thursday...

Thanks for your confirmation!

So the AA stub in OpenGApps must be defective.

The USB-Connection flipps always back to "no data", when setting it to "MTP" manually. And meanwhile it crasehes. I made some screenshots during my last attempt yesterday...

Update:

Tried again a lot of different settings for Google Play Service rights and notifications and in the developer settings of the system. Android Auto definately does not initiate a connection to the car media system. So it's not my device/service settings. The MIUI 12.0.1 Android device of my girlfriend works instant together with it. So it is definately not the fault of the media system. By the way - a few weeks ago I connected an iPhone of another friend sucessfully with the car.
[Android Software Development] chenjohnliu:
open_gapps-arm64-11.0-nano-20210717

Data Transfer Tool always crashes on initial setup.

Trying pico version now. Will report it later.

Update: pico version is also the same.

Logs are provided in the telegram group. (Don't know why I cannot upload here.)
[Android Software Development] ripee:
My Unofficial 11.0 builds

With @Nezorflame's permission, I ran my own unofficial builds dated 0719 for the full set of packages, since only official pico and nano builds have been released for now. I used the master source branch. arm and arm64 are up now and x86 and x86_64 are on their way as I write this post.

Unofficial OpenGApps 11.0
[Android Software Development] emuandco:
Just installed the Mini pack and it works great. Thanks for that @ripee ^^

But before someone tries it in the hope to fix Android Auto... Still the same problem here.
[Android Software Development] 1emrys1:
Has anyone tried the Aroma version in the last few months? Like aroma package on Lineage os 17.1. Does it work without issues? I had heard that aroma isn't supported by recoveries properly.
[Android Software Development] osm0sis:
Development of AROMA itself is very dead. Open GApps should probably just retire their packages built using it to save the headaches..
[Android Software Development] Kampfwurst:
same here. open_gapps-arm64-11.0-pico-20210723.zip and no luck with AA.

please fix it.
[Android Software Development] rootarded:
open_gapps-arm-11.0-nano-20210727 is making my LG G2 (D802) bootloop after installation. Switched back to 20210724 and it boots up normally.

I am using the latest LineageOS 18.1 nightly (2021-07-22).

Not a big problem, just a heads up to all 32 bit fellows. :)
[Android Software Development] Gene-13:
Can confirm the problem. Exactly the same behavior with my Samsung S5 klte (SM-G900F) and LineageOS 18.1 (tested the latest one 20210725 and the previous one 20210718). Installing open_gapps-arm-11.0-nano-20210727 results in a bootloop, downgrading to open_gapps-arm-11.0-nano-20210724 solves the problem.

Not sure if it matters/causes the problem, but the order of gmscore densities in app_densities.txt has changed in 20210727 compared to 20210724. gmscore update (from 21.24.18 to 21.24.56) might be the other reason.
[Android Software Development] G A S T:
After updating AA a from version 6.5.612134 to the latest version 6.6.612534 I get now the following error message under "connection help" in the menu:

"Android Auto was not pre-installed on this device

Android Auto must be bundled with your operating system to work correctly. Please contact your phone manufacturer for assistance."

Now it's undoubtly clear, that the AA stub implementation in OpenGApps ist broken with regards to the car/head unit connectivity.

I dirty flashed GApps Pico x64 manually together with the latest LOS 18.1 build for my device last week. This should be enough for a working "bundling" with GApps.
[Android Software Development] curiousrom:
Open GApps for Android 11 Build 2021-07-27 & 28 Causing Bootloop - Android 10 Also?

Well an other user reported the same issue in Reddit here:

Edit: an other user in that same Reddit thread but this time for for Android 10 Builds:

Heloooo @Nezorflame?

As I posted several time in this thread because Google is changing the goal posts all the time with priv-app permissions (causing bootloops) & other changes, the era of automatic building & publishing Open GApps without testing is over IMO.

What's the point of daily Open GApps updates if the apps are updated either automatically or manually when the user loggin in Play Store?

And for those who don't know 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 update Open GApps on your device unless it's defective.

***
[Android Software Development] G A S T:
I think you made a right point here. There should be a shift to weekly or perhaps better for monthly builds, because they should be tested before an official release goes online on the homepage. Less capacity for building, but more capacity for testing OpenGApps (internal or together with the help of the supporting community) seems to be the only good way to stable and working builds in the future.
[Android Software Development] G A S T:
The AA-Problem will be fixed soon:

Fix gearheadstub by moving it to priv-app (!49) · Merge requests · OpenGApps / all · GitLab

Architecture-independent sources for OpenGApps https://opengapps.org

gitlab.opengapps.org

This is also a good example for a missing testing procedure. Somebody in the team just forgot for the install routine to place the stub app in the the only right priv-app folder, although it was already known that this had to be done to make AA work. If that would have been just checked once... everything would have been fine.

My contribution here is absolutely no offense/disrespect to the great work of the OpenGApps Team, but perhaps this could be a beginning of a contemplation about the daily, very rapid release cycle of OpenGApps since they aren't updated daily by google. A little bit more time for checking and testing would lead to much more quality releases.
[Android Software Development] Nezorflame:
Thank you for your reports.

We've fixed (at least according to the user reports) the AA stub APK (by moving it to priv-app instead of app folder) so that change should come live with the next build.

As for the 27th and 28th builds - I've removed them from the website and SF for now, hopefully will resolve that as well before the next build arrives. Otherwise it'll be pulled as well.