yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Max Steel:
Link minimal package please!!!
[Android Software Development] jesus_c:
All links are in OP

Just use pico, nano or Micro packs
[Android Software Development] JoshuaOrphir:
Is there an option to include Face Detection for Media, Face Unlock and Google NFC Tag into the Nano Package?
[Android Software Development] nhmanas:
Aroma arm version is not working for me
[Android Software Development] bgiesing:
We can't do anything without the debug logs in the folder your zip is in, please upload them.

Also, almost everybody is on vacation so if something is broken, you might have to wait.
[Android Software Development] subaron:
Do any of the gapps in this listing work with any android phone and 5.1 custom ROM?

I am running CM12.1 (5.1.1 ROM) on Note 2 (t0lte):

http://xdaforums.com/galaxy-note-2/development-n7105/rom-unofficial-build-t3067695

Thanks

---------- Post added at 05:54 AM ---------- Previous post was at 05:05 AM ----------

Selected ARM> 5.1> Aroma.

Keep getting Error Code: 40
[Android Software Development] cobravnm13:
Try a different 5.1 package like stock or full.
[Android Software Development] MastahF:
Error 40 means that there are already gapps installed on /system.

Make sure you don't have leftovers of previous gapps packages (wipe /system before installing your ROM) and that your ROM does not contain pre-bundled gapps.
[Android Software Development] gts3212:
link die

hey man link open gapp 5.1 mini has die i can't download
[Android Software Development] Magendanz:
Yes, what's the word on builds for these ARM variants? I can find no information in the blog or wiki explaining their absence.
[Android Software Development] ISSLEDOVATEL:
remove

how to completely remove from the firmware to install another
[Android Software Development] Feimitsu:
To add on this, I've installed the latest Mini gapps package from August 8. Can I go on and flash the latest stock package from July 14 without problems?
[Android Software Development] :
Android 10 Aroma arm64 problems on Lenovo k6 power..

Followed sequence AospExtended+GApps(11th August)+Magisk+Migrate Backup Zips.

1st this came while setting up new rom

2nd this came and stuck here

Earlier builds of Android 10 arm64 Aroma works on this K6 Power device.
[Android Software Development] Nezorflame:
Hi everyone. Sorry for being away.

The "OK Google" error should be fixed in today's build - there was an issue with the system requesting a specific version of the `libcronet` lib inside of the Velvet APK, had to find the exact one to work properly.

The issue with Google backup missing SMS permission is still in progress, hopefully will fix it today.

[MENTION=6817913]gj86[/MENTION] [MENTION=903232]Magendanz[/MENTION] [MENTION=5382018]Feimitsu[/MENTION]: some ARM build variants are missing right now - it's a build error, the package variants are not going anywhere, will try to fix it today as well.
[Android Software Development] pothaiahgari omkar:
I want configuration file for SuperGapps so that i can install apps as i like and replace system apps to save memory. Can Any one share me that file?
[Android Software Development] manjaroid:
This page explains everything and includes a boilerplate gapps-config: https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
[Android Software Development] andreiuul:
Trying to build Lineage 15.1 with opengapps for Mako

Hi there;

If you hive the time, could you please help me out with building lineage with opengapps.

I`m asking you because you've said that you were successful while following the instructions on github.

I on the other hand I am getting building errors like the following:

[1163/1171] including ./vendor/opengapps/build/modules/Wallpapers/Android.mk ...

[vendor/opengapps/sources/all/app/com.google.android.apps.wallpaper/16/nodpi/169416333.apk]

End-of-central-directory signature not found. Either this file is not

a zipfile, or it constitutes one disk of a multi-part archive. In the

latter case the central directory and zipfile comment will be found on

the last disk(s) of this archive.

note: vendor/opengapps/sources/all/app/com.google.android.apps.wallpaper/16/nodpi/169416333.apk may be a plain executable, not an archive

zipinfo: cannot find zipfile directory in one of vendor/opengapps/sources/all/app/com.google.android.apps.wallpaper/16/nodpi/169416333.apk or

vendor/opengapps/sources/all/app/com.google.android.apps.wallpaper/16/nodpi/169416333.apk.zip, and cannot find vendor/opengapps/sources/all/app/com.google.android.apps.wallpaper/16/nodpi/169416333.apk.ZIP, period.

I seems like the sources provided are not... optimal? :confused: (no clue what i am doing)

The apks are strangely named and come in "com.google.adroid.something..." and if I try to provide the apks from other places like extracting them from system images, i encounter the problem that they are named differently (proper app names) with no obvious way to transition them automatically.

I am dealing with things way out of my league here and some help would be really appreciated.

Thanks.
[Android Software Development] Nezorflame:
If you're using our aosp_build repo, make sure you have Git LFS installed and enabled on your PC to be able to download APKs.

More info on that here: https://github.com/opengapps/aosp_build#infrastructure-issues

GH issue with somewhat the same problem and solution: https://github.com/opengapps/aosp_build/issues/229

---------- Post added at 04:23 PM ---------- Previous post was at 04:22 PM ----------

Small update:

- today's builds have some awesome fixes for the addon.d and more by [MENTION=4544860]osm0sis[/MENTION]

- ARM builds are back online in a full scale starting tomorrow

Back to fixing the other issues.
[Android Software Development] Feimitsu:
I still see Android 10 ARM builds only up to Mini :(
[Android Software Development] Nezorflame:
My bad, indeed, should be live in the next build. Sorry for the confusion.
[Android Software Development] PieroAV:
Hello, I installed the build arm 10 stock in several roms, but in all of them at the beginning they stay in the logo, then I tried with the pico build and there if they start, is it an error? Does this have a solution? I'm sorry for my English
[Android Software Development] Nezorflame:
How long do they stay at the logo? It can take quite a while to do the first boot.

If it's a bootloop, I'm going to need a logcat during the boot process to see the error. Check XDA on how to make one.
[Android Software Development] curiousrom:
Bootloop: Missing Privapp-permission AGAIN!

Thanks for reporting this & providing the logcat snippets. :good::cool:

This missing privapp-permissions problem in Open GApps for Android 10 & causing bootloop in ROMs enforcing permissions is a kind of sick running joke since months as it happens randomly across the board for all kinds of packages.

That happens every time a new app or version of an app that requires a new privapp-permission is automatically added to a Open GApps package & since the Open GApps devs won't setup a testing group they just publish untested stuff & don't care about the thousands of users wasting their time in bootloop, losing their setup, apps & data, etc.

The Open GApps Project is using the general public as beta testers. :eek:

Sorry about the tone of this rant but a post was made about this problem on December 5th, 2019 and again by one of the LineageOS directors & I on 25th January 2020 in this page and still the same problem again, and again, and again, and again!!! :eek:

***
[Android Software Development] osm0sis:
If it was an easily automated fix it already would be; it can't be predicted when it'll happen, so for now it has to be reactionary.

Since you've got so much energy and time, perhaps you should consider looking into the issue yourself? It's an open source project after all.
[Android Software Development] curiousrom:
Re: Bootloop: Missing Privapp-permission AGAIN!

Using thousands of unsuspecting non-savvy users as guinea pigs with untested Open GApps packages is not fair. :eek:

Many of them don't know that they don't need to update Open GApps & panic when they get stuck in a bootloop.

Some don't have a backup strategy & are losing hours setting up their devices again after wiping everything & trying randomly other Open GApps packages, ROMs & recovery versions.

And that's not counting all the LineageOS users I saw on XDA & Reddit losing hours on failed clean installs.

As mentioned in the post linked above & many others addressed to [MENTION=2010892]Nezorflame[/MENTION] the easy solution is to publish Open GApps weekly or bi-monthly instead of daily & setup an Open GApps testing group.

If it's not tested it should not be pushed to the general public.

I think that [MENTION=614507]razorloves[/MENTION] mentioned a script to check automatically the required privapp-permissions but that's above my paygrade.

I am not a dev but as you can see in my posting history I'm a user support guy & I'm really sorry for all the users affected by this recurrent problem that also affects severely the reputation of the entire Open GApps Project.

***
[Android Software Development] osm0sis:
They aren't being used as "guinea pigs", please get off your high horse. As you should know, Open GApps is largely automated, that's why it remains after all this time with basically nobody in charge organizationally or steering development. Because it's automated the APK crawler continues to crawl and builds continue to roll out, as they always have.

It's not some big group with things happening behind the scenes, making decisions, there's just an existing, automated project with literally 3 main contributors barely scraping together enough time to keep it going.

You're not a dev? Cool, then maybe check your entitlement about how a project should run. Also, as a self-described user support kinda person, nobody is stopping you from using this forum or the official Gitter, or even Telegram or somewhere else to curate and discuss what releases you think are more stable than others and have recommended builds, just like people have always done for ROMs.

Open GApps is nightly, and while Open GApps has always striven for a solid product, nothing about the word "nightly" has ever suggested "fully stable", so things will break from time to time, and some patience, understanding, and respect for people's time is more than deserved, and all that's asked.
[Android Software Development] curiousrom:
Re: Bootloop: Missing Privapp-permission AGAIN!

Where does it say that Open GApps MUST be built daily?

I'm an XDA member since 2011 with 1,400 posts and have been using custom ROMs even before that so "things will break from time to time" is expected & normal.

What is not normal is to repeat the same mistake over and over and over because of missing privapp-permissions & keeping on churning out untested defective builds because of it.

***

"...Because it's automated the APK crawler continues to crawl and builds continue to roll out, as they always have...":

[YOUTUBE]DfGs2Y5WJ14[/YOUTUBE]

Or use this link if the video BBcode does not work: https://www.youtube.com/watch?v=DfGs2Y5WJ14

***
[Android Software Development] osm0sis:
Go ahead and Google the word automation. Open GApps builds are automated. Nightly. That's how it's always been to try and keep up with Google and always have the latest; pretty sure that's in the OP.

Not saying that's how it has to be forever, but that's how it is, and with [MENTION=6404745]MastahF[/MENTION] only having enough time to occasionally merge our Pull Requests (he's the only one who can), don't expect any grand organizational changes any time soon.

Please read my previous post over again because I don't think you've grasped how few people there are and how time-constrained development is, nor checked your entitlement on the matter. Development is like 95% [MENTION=2010892]Nezorflame[/MENTION] right now, and he's got a life too. Show some respect for the time he's dedicating to keep this sh*t afloat.
[Android Software Development] osm0sis:
Look, for what it's worth [MENTION=2010892]Nezorflame[/MENTION] and I recently got GitHub permissions on the Open GApps repo to triage GitHub Issues, and make the Issues section useful to the project again. The recent TV Stock issue was mentioned there before here, as well I brought up that a long-term automated fix needs to be found, which I've since spun off into a dedicated issue.
[Android Software Development] Nezorflame:
Thanks! I've added the missing permissions to the list, should be fixed in the next build.
[Android Software Development] Feimitsu:
I installed August 18 OpenGapps Arm 10.0 Super modified with gapps-config with no issues.

Now when I'm attempting to install August 22 version with a slightly different gapps-config i'm getting an error code 40.

How could it happen? Am I forced to wipe System?
[Android Software Development] Nezorflame:
Please post the whole debug log file.
[Android Software Development] Feimitsu:
Too late, I wiped System and reinstalled. If it happens again i'll make sure to post the debug here. :)
[Android Software Development] githyanki:
How about adopting a system where after 2 or 3 days of no issues with a build they are called "tested" and on the download page users are given the choice of nightly or tested versions?
[Android Software Development] osm0sis:
Sure, but see the middle paragraph of my previous post.
[Android Software Development] curiousrom:
Re: Bootloop: Missing Privapp-permission AGAIN!

Thanks for making a suggestion about how to solve the problem but that is still using the general public as beta testers. :eek:

From the January post I linked to above:

"While I really appreciate the work made by the unpaid volunteer Open GApps devs :good:, it's an important & big project that impacts thousands of users & testing before release should be an essential part of the process.

If reducing the frequency of the releases is necessary because of limited testing capabilities then do it because the harm caused by releasing broken builds is too great IMO."

***
[Android Software Development] trancinguy:
Technically speaking, "everything" is beta.
[Android Software Development] osm0sis:
Once again, you've clearly got lots of energy and time, so why don't you spend some of it learning how to code and maybe fix the issue yourself? It would be more useful to the project than these little diatribes of yours.

Here's the Issue on GitHub I created, which you can link to your Pull Request once you've got it figured out: https://github.com/opengapps/opengapps/issues/874
[Android Software Development] curiousrom:
Open GApps Testing Group?

I've searched [MENTION=2010892]Nezorflame[/MENTION]'s Telegram group & found these posts about a possible Open GApps Testing Group:

Here on 23.07.2020:

Same day & just below it here:

And here on 13.08.2020:

[MENTION=2010892]Nezorflame[/MENTION] - That's awesome & hope that the project is still in the tubes. :good::cool:

Could you also post follow-ups in this thread or maybe post a link to your posts elsewhere about it once in a while please?

If I understand correctly the "stable" builds will be weekly, right? :confused:

***
[Android Software Development] ipdev:
Enough please. :)

It has been a topic of conversation before.

Major changes are tested before being implemented.

Yes, It would be great if there was a test group.

Minor changes, would be too much for a small test group.

---

Even if Open GApps released a stable Weekly, you would still have a lot of users that choose the Nightly instead because they think is is more current.

Just look back in the thread when nightly builds were interrupted and/or bad builds were removed.

I guess I would fall into using Milestone builds. :)

It is not the time or place to get into this but, most Nightly builds do NOT have changes. It is one reason I disagree with fully automatic builds.

New builds should only include changes for a specific target.

Unfortunately, build servers are normally use-it or loose-it so you might as well just build everything...

---

Every manufacture uses their users to test releases.

Asus, Google, HTC, Huawei, LG, OnePlus, Motorola, Samsung, Xiaomi, ...

It is normally referred to as a Rollout.

Once the changes have been verified by a test group, normally called alpha or closed beta.

Then it is normally pushed to the open/general beta group, to test.

Once the changes have been verified by the test groups, they are implemented and the changes are pushed out slowly.

The initial criteria of who gets the updates first might be different, but the practice is the same.

Push to a small set of users to see if users outside of the initial testing (Beta) group find issues.

- If issue found, pause release and fix issue and push the fix.

Push to a larger set of users to see if users outside of the initial testing (Beta) group find issues.

- If issue found, pause release and fix issue and push the fix.

Once the issues are none or the risk is minimal, the update is released to all.

---

I have updates and full releases on my backup drive(s) that never got officially released.

OnePlus and Xiaomi mostly. :p

It takes a lot of time, devices, and different configurations to test each and every change.

What works once may fail the second time. What works on one device may fail on another. What works on one device and fails on an identical device.

---

It is impossible to fix an issue before it is reported.

The current OpenGApps team is very good at removing bad builds and fixing or working around a reported issue.

Cheers all. :cowboy:
[Android Software Development] Rahbar11:
I am having a really bad problem that I never faced before. I flashed opengapps arm 10.0 nano and my assistant suddenly stopped voice recognition it says "'Ok Google' model update" Download failed. I thought it may be fixed in next version of opengapps, so I flashed opengapps 08-22 version but it's still same... Please help. I deleted the data of Google apps but nothing happened...
[Android Software Development] guhvanoh:
Is your connection set as unmetered?
[Android Software Development] curiousrom:
Did you try build 2020-08-29 or 30?

***
[Android Software Development] jcurtis369:
Ok google model update error happens to me on both 8-29 and 8-30 for the 10.0 arm nano packages on Lineage 17.1
[Android Software Development] Vinnom:
I've built unofficial ValidusOs for beryllium and I need some help.

When I flash gapps just after rom, when it boots, system doesn't recognize sim card. I've tried both stock gapps (my usual package) and pico so I would get minimal interference when getting logs. I booted rom+gapps, skipped setup and grabbed the validus-simcard-pico-gapps-20200901 attached below.

Then I tried to flash rom first, boot into system and then reboot to recovery and flash gapps. When I do that, stock gapps can't finish the setup because play services keep crashing (which I understand for now as an effect of booting to system before flashing gapps - maybe some permission missing? Idk) but pico gapps works fine and I can at least use it as a daily driver for now.

So I need help. Would someone be able to say if this issue regarding sim card not recognized after flashing gapps is related to device tree or to Validus itself and where to look to fix this?

beryllium and sdm845-common tree used

both pico and stock gapps version that I tried were 20200831.

PS: the trees I linked are quite old and not updated, which is making me think in rebase them to lineage ones, but I wanted to build it as-is first.
[Android Software Development] shane87:
Hey, I just wanted to report that I'm seeing the "OK Google" error on open_gapps-arm64-9.0-mini-20200831, flashed with LineageOS 16.0, nightly build from 08/31/2020, on OnePlus 5 cheeseburger. No rush, just wanted to let you know that the issue wasn't confined to the Android 10 builds.
[Android Software Development] Rahbar11:
Using 1 September build now (clean flashed everything). The issue is still present...
[Android Software Development] zzz2002:
Not sure if this is a gapps "problem".

If I add a business/company/organisation to my address book using the "company" field without the details of an individual, something (the app I believe) breaks the company field down and fills in the name fields. Eg. The "Canada Revenue Agency" is broken down into

"first name" = Canada,

"middle name" = Revenue,

"last name"=Agency

The results on the entry being mis-filed under agency. The solution might be to use a non breaking space between the elements of the name.

But I can not find how to enter a non breaking space.

Any ideas.
[Android Software Development] jlg78:
I am using Microsoft Contacts and GApps and I could not reproduce the error when I fill in just the company field. Oneplus 3 with Bliss 12.11

Hope this helps!
[Android Software Development] turnoffer:
Just wanted to let you know that 3rd September arm builds for 9 and 10 Android still has an issue with activating of OK Google at Google Assistant, just like as was already noted above by few people. Tested on Nexus 6, ColtOS based on Android 10 and NitrogenOS based on Android 9. Then I rolled back on the same NitrogenOS but with old 20190925 gapps and such config works fine.

Thanks.
[Android Software Development] rjt2291:
Anyone else getting lockscreen issues with latest version of Google play? Started just the last couple days. My N5110 display doesn't react for like 10 seconds and sometimes not at all. I have to cycle the display with power button a few times for it to even react to touch. Volume buttons don't react either which tells me the whole device is frozen until wake cycled a few times.

Tested on GT-N5110 with both LineageOS 14.1 AND Cyanogenmod 13.0. Just fresh installed ONLY LOS14 and CM13 without any unlock issue. It's clearly Google play.
[Android Software Development] droi1:
same problems here with "ok google update error android 10 +9"

also i can't use my google device backup on Lineage 17.1 (backup is same lineage version same device) clean install. (screen goes black and setup wizard restarts)

testet on galaxy s4 i9505 lineage-17.1-20200827, 813,730 with newest nano Gapps and older ones. trying now for 4 days..... can't figure out which gapps and lineage version working stable :confused:

*update

old open_gapps-arm-10.0-nano-20200430 works with LOS 16 + LOS 17.1 install wizard is the only thing not working but at least i can skip this and do later.

App Data are restored, other Stuff not.
[Android Software Development] ilunaticreature:
Gps issues

Google maps not receiving gps data. Tried google maps go with chrome and still not working. Tried yandex navigator and that worked. Link for gapps install and debug logs and logcat of when trying with google maps: https://mega[.]nz/folder/GpgF1ZaJ#ahZhM65rKfVQqYTMdn6YHA

Imcluded screenshots of portions of logcats I thought are relevant.

Rom: Aosp extended 7.3 for redmi 7

Android version :10

Gapps package: 20200905 pico
[Android Software Development] Rahbar11:
Are you serious?

I reported a bug about Ok Google not working and after that so many people reported the same bug. It's 17 September today and I'm using opengapps nano 17 September build for arm devices with Android 10 and the issue is still present but I'm not shoked by the presence of issue but I'm shoked that not a single developer even replied to any of the reports. I am not saying that this issue should be fixed soon but atleast respond to people who like this project and trying to help by submitting bug reports... Really disappointed.
[Android Software Development] Nikhil:
I'm here acknowledging your bug report.

The issue is known and already reported to [MENTION=2010892]Nezorflame[/MENTION].

We get your frustration buddy. It's just that, developers are busy with their personal lives and Google isn't keeping things simple/consistent either. It takes time to debug and fix the problem which never existed before.

Anyway, rest assured, this will be fixed soon.

As a workaround, you can update Google app on playstore and that should temporarily help you.