yashsingh1/xdaforums huggingface dataset:
[Android Software Development] MastahF:
Yes, your device is not compatible with google camera, that is why it is not installed.

About the 'Eleven' application, the only keyword to remove it nowadays is 'cmeleven'.and not 'eleven'. That might be the problem. For compatibility 'eleven' was still included and accepted in TKruzze's build, but for the sake of progress I dropped this since it has not been mentioned in any documentation anymore for a long time.

Hope that can solve your problem.
[Android Software Development] dnle71:
But i don't want to remove it manually. I respect the stock build so much that i don't want to add or remove a thing, so I asked if it can be done. But if not, then it's okay. I'll just leave it there.
[Android Software Development] MastahF:
Yes, but some extra options have been added and some outdated optionally packages have been removed, you can check the details within the README information at https://github.com/mfonville/pa_gapps
[Android Software Development] MastahF:
Ah, now I get what you mean. But no, we will not remove the stock music player by default. We only 'replace' applications with their Google equivalent if they could conflict, leaving the rest of the ROM as intact as possible. But don't be scared to use any of the options in a .gapps-config file while installing, they will allow you to get the experience YOU want :)

I guess a possible future to-do would be to make a website where you can easily generate a .gapps-config by just clicking on the app-icons one would like to install.
[Android Software Development] TamNgTech:
Thank you :), one last question. Is the package naming for adding/removing app still the same like it was in the original PA Gapps thread?

Example:

"Include

Books

CameraGoogle

Chrome"

Etc.
[Android Software Development] retired_mnbooze:
Any thoughts/knowledge on the Docs and Slides icons? Dogfooded versions? They are the XXX.35 versions from APK Mirror...
[Android Software Development] MastahF:
Yes, still works the same. I will provide documentation at a later moment, when we will have somebody in the team willing to keep it up to date.

By pure chance I was also selected for the dogfooded versions on the playstore, so I could just download them myself :P (and felt forced to update the sources).

And package is still beta, so I thought: why not. In the future (when doing more stable release) I won't include these dogfood versions.
[Android Software Development] ew:
I tried this for the first time today. Flashed it over a prior PG Gapps. I flashed the nano version.

I quickly noticed that when connected to my computer, my phone storage was not visible to the computer, and the notification icons (that indicate a usb connection) did not appear.

I reverted to the nandroid backup I made immediately prior and will test when I have a little more time.

Edit - this may have been due to my computer USB connection. I will need to test again when I have a little more time...

I have a Samsung S5 (t-mobile variant) running CM5.1 (5/14/15 nightly build).

Thank you very much for taking this over.
[Android Software Development] KcLKcL:
Flashed the May 13 zip on my Nexus 4, but the launcher refuse to work. It seems that Google Search app is either missing or fail to install, making Google Now Launcher fail to work.
[Android Software Development] MastahF:
Try flashing the may 14 build, it contains a fix for this problem. Best is to wipe /system beforehand.

(So wipe /system, flash your ROM, flash gapps)
[Android Software Development] ew:
All is good, must have been a computer thing.

Question - there is a new program that I didn't have earlier "Cyanogenmod.platform - verstion 5.1.3-...". I think it came from PA Gapps and not my CM installation. What is that?
[Android Software Development] NZgeek:
A delta updater only contains the files that have changed, so it has to leave the other (unchanged) files in place. I can't think of a good reason any why GApps files would need to be touched by this process. It might be worth looking at the update script inside one of the delta zips and see what it's doing.

If the updater is applying a full OTA rather than a delta update, that could explain why it's happening. GApps will only save across OTA updates if the GApps package installs an addon.d script, and if the OTA install script makes use of the addon.d script. If your current GApps doesn't install an addon.d script, Open GApps should fix the issue. If it's the updater script, there's not much you can do except reinstall GApps every time.
[Android Software Development] onlyoneaamir:
It shows error during installation

only 5.1.x supported

i am installing it on cm12.1 64bit and downloaded open_gapps-arm64-5.1-pico-20150717
[Android Software Development] TorchaOne:
Hi, googleclock has been giving me FC sice 16th day or was it 15th. Using stock arm for oneplus and cm12.1 nighlies.
[Android Software Development] MastahF:
Please post your debug log, otherwise we cannot do anything for you.

Google stated that they should have resolved any issues for migrating to the new Google Deskclock (that is why a clean data-partition is not necessary for installation anymore). I would suggest you clear the app's data (and cache) from the app info screen. If problems still arise, you'd probably have to file a bug with google (you can do that via the play store).
[Android Software Development] TorchaOne:
Actually yeah, that helped. Even thou I though I made it once already. Thanks... sometimes brain just do not work :)
[Android Software Development] onlyoneaamir:
Here's the log

Begin Open GApps Install Log

-----------------------------------------------------------------------------

ROM Android Version |

-----------------------------------------------------------------------------

# End Open GApps Install Log

INSTALLATION FAILURE: This GApps package can only be installed on a 5.1.x ROM.

# Begin User's gapps-config

*** NOT USED ***

# End User's gapps-config
[Android Software Development] MastahF:
Your full *debug* log (tar package) please
[Android Software Development] onlyoneaamir:
Here's the link

https://drive.google.com/file/d/0BzCEjs7h7pjfSjZsY2xrVV9xLWs/view?usp=sharing
[Android Software Development] MastahF:
The (encoding of) build.prop of your device is broken. Someone else in the forum had this problem before, with I think the very same device CM ROM. Please contact your the developer/device maintainer of your device's CM ROM and tell him to fix his build.prop, because it is unprocessable by any (gapps) package in its current state.
[Android Software Development] Dr AM:
I used open gapps aroma to replace some stock apps with google ones like stock camera to google camera , If I update my ROM in future will ROM bring back stock apps or gapps backup script will prevent that and keep google apps I replaced to ?
[Android Software Development] MastahF:
If your ROM supports the addon.d mechanism (and most do) it will re-remove the system apps and re-install the google apps. So it should restore everything to the state it was before you started the ROM update.
[Android Software Development] crian:
Got an issue with setup wizard. Geeting play service stopped message after passing NFC.

Flashed the stock package.
[Android Software Development] Dr AM:
[MENTION=5419355]warrior1208[/MENTION] looks like I'm good with dirty flash now O.o
[Android Software Development] raptir:
So, I think I'm going to be the one dissenter here... but I'm not a fan of the new compression. I have a decent enough device (Moto X 2014, Snapdragon 801 with 2GB of RAM) but the additional time that the new zips take to install (about two minutes longer) is significantly greater than the time to download a larger file (about 30 seconds on my connection for 300MB extra). Plus, I would sometimes flash a given Gapps package more than once while I would never download a given release more than once so the time lost ends up being much greater.
[Android Software Development] Rojax:
Aroma reboots twrp and stock package failed error 70 free space when I flashed gapps sequentially after rom. If I flash the rom, then go back and flash gapps it works fine. https://www.dropbox.com/s/qonaguslcqew141/open_gapps_debug_logs.tar.gz?dl=0
[Android Software Development] MastahF:
Could you please give more details? So a debug log of the installation, and a logcat when you are getting those FCs.

Point taken. For your micro scale you are right, but for those who don't have a reliable fast connection this is a big plus. Also, in the long term also the calculation for you might shift, because Google is continously releasing more DPI-specific versions of all its apps, so while at the moment it is e.g. only a 400MiB difference, in the future this can easily become 800MiB difference or even more. Also at macro-scale, I do think the people at GitHub who are providing our free hosting, are happy if we only take half the diskspace and half the bandwidth.

I looked at your debug log, but it only states a successfully completed aroma installation. Could you give more details about when aroma does reboot?

I am also interested in the free space error after flashing the ROM, could you give a more detailed description (which ROM, which exact steps) and full TWRP & Open GApps debug logs of that situation?

I need the full debug logs not the installation log (it is a tar file with debug in the name). About your FCs, to investigate those I will need (next to the debug logs) a logcat.
[Android Software Development] Rojax:
Hrm, I will try to replicate it again another night. Was dirty flashing (wiped system) the latest Candy5 v3 rom on htc m8 followed by gapps. It only crashed or space error when using the flash queue in twrp. Aroma rebooted after all the menu options and install starts, getting to about 3%. I will see if I can get you better logs. Thx
[Android Software Development] ASHURiCAN:
Hi, is there an update about the Pushbullet subscription?
[Android Software Development] MastahF:
They had some trouble on their side with processing of new URLs on their website, but I have been in contact with them and it should be resolved. So pushbullet should be available again for the coming builds.

Also, for those interested in the platform-specific pushbullet channels, here they are:

https://www.pushbullet.com/channel-popup?tag=opengappsarm

https://www.pushbullet.com/channel-popup?tag=opengappsarm64

https://www.pushbullet.com/channel-popup?tag=opengappsx86

https://www.pushbullet.com/channel-popup?tag=opengappsx86_64
[Android Software Development] ADB100:
I think you misunderstood.... My phone is running LineageOS 15.1 (Android 8.1) and I am installing OpenGApps Super for x64 Android 8.1. The OpenGApps version 20190315 includes Chrome 73.0.3683.20 which doesn't work, however it has a knock-on effect of breaking most of the other Google apps (GMail, Google Search, Calendar etc). Wiping and starting again was the quickest fix.

Obviously the builders of OpenGApps saw the issue and reverted the Chrome version back to 72.0.3626.121.

I wasn't 'finicking around with it' - I just installed the latest version of OpenGApps for my phone and it broke things...
[Android Software Development] demonoidmaster:
...all you had to do was boot into twrp, mount system, go to /system/app or priv-app and delete Chrome + wipe cache, you didn't have to go through all that absurd hassle, also if i were you I'd stick to either internal rom webview or at least get the one from the playstore which gets updated along with chrome

You nuked your entire system and reinstalled just for an app that caused issues that was easily removable...

Edit: apparently my Chrome Beta got updated to v73 and it works, seems to me like they either had put the wrong chrome apk in there or your rom just panicked
[Android Software Development] ADB100:
Tried that and most of the Google apps still force closed. When I realised there was an issue with Chrome I reinstalled the previous OpenGApps that had the previous version of Chrome and most of the Google apps still force closed. Wiping and restoring from the Google cloud backup was the best option.
[Android Software Development] fdc77:
notifications issue

Device: Xiaomi Mi A1

Rom: Los 16 official

Gapps: stock arm64

This fix does not work on Mi A1 https://github.com/opengapps/opengapps/pull/685

to correctly show notification and complete configuration i must disable Android Setup (com.google.android.apps.restore), with MindTheGapps i don't have problem i think this have something to do with the AndroidMigratePrebuilt.apk

https://www.apkmirror.com/apk/google-inc/data-transfer-tool/data-transfer-tool-1-0-214934184-release/
[Android Software Development] duhec:
So what can we do about Chrome version 73 still being included in the opengapps and obviously giving a lot of headache? Wait for a version that works with other versions of Android besides Q?
[Android Software Development] SpasilliumNexus:
Except it's not. 73 was removed 5 days ago. Update.

---------- Post added at 01:29 PM ---------- Previous post was at 01:02 PM ----------

It's always the Xiaomi devices with the issues, including this. Not much anyone without that brand phone can do to pinpoint fixing it. In those 5 months since I made that pull request, so far, those with a non-Xiaomi device never came back to say it didn't work.

Also, the Pixel versions of SetupWizard and Data Transfer Tool (both which caused notification issues) were replaced with "Generic" versions of them, found on all non-Pixel phones. There is no other variant of them to test with.
[Android Software Development] duhec:
The version log says differently. WebView is 72, but Chrome is 73. With the latest opengapps I cannot get past the initial wizard because when I'm about to enter my google username, the screen goes blank because there is no WebView installed. This is in combination with LineageOS 16.0 for shamu 20190320.

[IMG="version 73"]http://shrani.si/f/2K/Ve/2PCop16A/chrome73.png[/IMG]
[Android Software Development] adek33.21:
Hi, I can't install Chrome from aroma installer. Is it known bug? Open gapps aroma 9.0 arm
[Android Software Development] duhec:
I also cannot install Chrome through Stock opengapps.
[Android Software Development] EEERicChey:
xiaomi 8se

TWRP

Rom:omni project treble

no response after swipe to install Gapps 9.0 Aroma

the log just show:

skip digest xxxxxx

starting AROMA installer version 2.70RC2

(c)2013 by axxxx...

by the way

I've tried the super version, the Pixel Launcher dose not work well

i set it as default, but it keep stopping working
[Android Software Development] Akansh25:
Bug:- when I install mini package pie arm64 in rr rom the aosp message app does not get removed. But it should get removed and Google messenger should get installed. But google messenger get installed whithout removing aosp messenger.
[Android Software Development] cmohan0004:
Hello, i m installing stock gapps 64 over los 16, customised my gapps installation with config file and everything is working at expected but i dont want to install Google webview or webview stub and want to keep stock webview installed i use +WebViewStock key to retain stock one but its keep installing webview stub... No matter what keyword i m using but i can't jeep stock webview, every time webview stub getting install ( i m not doing anything worth Chrome and letting it install normally)
[Android Software Development] holavilla:
Old aroma script not working on many phones.
[Android Software Development] adek33.21:
So, the latest version works well?
[Android Software Development] gps3dx:
Hi,

For some time now I use a custom aosp based pie rom, and it has DND feature including two "exceptions" buttons: "calls", "messeges, events & reminders".

THE ISSUE IS THAT BECAUSE OF GAPPS, when I click on either one of these two sub-dnd buttons, SETTINGS apps crash, and don't allow me to change these DND configurations.

AFAIK, and fir my best of abilities, I managed to isolate the issue to be the gapps's CORE, since I installed latest PICO ver and excluded anything special PICO contains and that can be exluded, BUT core gapps features of course.

Attached full logcat + here's the Logcat of issue ( isolated )

https://del.dog/ijuzoyisec

What open-gapps core component effects DND?

How can I bypass that issue, since I want both the gapps minimun & having a working DND.

FEW NOTES:

The crash of course happens also w/ normal pico installation & with any daily of open-gapps for at least a month

crash is NOT happening when I DO NOT install open-gapps Pico

crash exist on fully cleaned installed (i.e /system, /data, d&c wiped) rom + gapps only ( no magisk, no xposed etc), though my logcat isn't from one but from much later stage (i.e magisk installed, 3rd party apps etc).

beside the crash I described above, Gapps is working great, amooth & w/o any issues or crashes.

weirdly, the crash do not happen when gapps installed and I signed in THEN OUT of google account under settings->accounts.

BUT as soon as I enter my username ( i.e during Google account login procedure), DND crash issue cames back. (I.E only when I manually goto settings->sound ->dnd->press exceptions buttons it crashes)

Please advise
[Android Software Development] Paschfire:
Using the Advanced Features & Options @ Github link provided within the OP, you'll need to configure a .gapps-config file to remove the MMS apk during the installation process.

All instructions to which are provided within that linked page.
[Android Software Development] ADB100:
arm64 8.1 still has this version beta of Google Play Services, whilst all the others have now been updated to non-beta 15.1.80 - any idea why? I am hoping this restores Android Auto functionality?

Andy

EDIT: My device automatically updated itself to Google Play Services version 16.0.89 and now Android Auto (and Google Authenticator...) work again. Version 15.0.78 is still in x64 ARM Android 8.1 OpenGApps. I guess we just need to wait for the latest version to get included...
[Android Software Development] meeds:
Fp setup isn't detecting my finger at all. Tried older releases of the 30 March release and various roms with the same issue. I also flashed firmware drivers but the issue presisted.

(installation log in case if you need it)

https://docs.google.com/document/d/1MmZeZwnxO_YXA1hU8pSnEHMWuMo4_4oKiy7cK2XLK8A/edit?usp=drivesdk

Using Havoc os March 27 MIDO
[Android Software Development] ADB100:
I was feeling hopeful this morning when I saw the latest OpenGApps for Android 8.1 x64 ARM appeared and the version information said Google Play Services is version 16.0.89. Flashed it to my S6 Edge running LineageOS 15.1 and Android Auto doesn't work again, plus Google Authenticator now won't display the camera (Barcode scanner is not available now).

I am scratching my head as Google Play Services 16.0.89 (that got upgraded from 15.1.78) was working OK yesterday, now its installed in /system/priv-app rather than /data/app its stopped?

Confused..

Andy

EDIT: So just flashed the OpenGApps package from 31st March which contains Google Play Services 15.1.78 - Android Auto and Google Authenticator don't work (expected). Side loaded Google Play Services 16.0.89 and now they do? The only difference I can see is the .apk is in /data/app rather than /system/priv-app?

Still confused..

Andy
[Android Software Development] ADB100:
So with Google Play Services 16.0.89 in the latest OpenGApps ARM x64 8.1 package Android Auto and Google Authenticator don't work and there is no way to fix this currently as you can't downgrade Google Play Services or upgrade it (as there is nothing newer). The only way to fix it is to flash OpenGApps from 31st March or earlier to get Google Play Services 15.1.78 installed and then manually update Google Play Services to 16.0.89 with the .apk getting installed to /data/app rather than to /system/priv-app.

I tried a full wipe and reinstalled the ROM and OpenGApps from 04/04/2019 just in case there was some issue with the data left over, however the issue remains.

If Google Play Services 15.1.78 or 16.0.89 is installed in /system/priv-app it causes Android Auto and Google Authenticator to fail, however if Google Play Services is installed to /data/app then Android Auto and Google Authenticator work.

So the problem now is if you want the latest OpenGApps then you can't have Android Auto or Google Authenticator.

Any ideas why we are seeing this behaviour?
[Android Software Development] fluxus_pt:
^^

i'm struggling with that issue for a long time as well, the solution was to install stock gapps from October 2018.

Could you please tell us how did you sideloaded the updated apk of GMS?

cheers!
[Android Software Development] ADB100:
I just downloaded the .apk from apk mirror, copied it to the device and navigated to it with a file browser and clicked on it to install....
[Android Software Development] fluxus_pt:
That method works fine!

But i have concerns regarding if its legit or tampered.

Do you have any feedback?
[Android Software Development] ADB100:
I guess your other option is to just extract the .apk from the OpenGApps package.
[Android Software Development] Dirk:
That's interesting. I had that issue recently. Couldn't get through setup without hitting a Black screen. It didn't occur to me that setup needed a webview installed. (I usually remove it via gapps-config). I eventually got up and running using an old gapps zip from January.

So is this a new thing, needing webview present for setup to complete?
[Android Software Development] ADB100:
Hmm.... Think I have found the issue. In the latest OpenGApps x64 ARM packages for Android 8.1 Google Play Services version 16.0.89 (110400-239467275) gets installed. This is for API 27 (Android 8.1+). In the OpenGApps packages for Android 8.0 Google Play Services version 16.0.89 (090400-239467275) gets installed, this is for API 26 (Android 8.0+). With the former one (API 27 - 110400-239467275) Google Authenticator and Android Auto don't work, however with the latter one (API 26 - 090400-239467275) they do.

As a test I have therefore replaced the 'gmscore-arm64.tar.lz' in the latest OpenGApps for ARM x64 8.1 with the one from the latest OpenGApps for ARM x64 8.0 (090400-239467275). It is a bit tricky trying to remove updates to Google Play Services so I performed a full wipe and a reinstall of the latest LineageOS 15.1 ROM (home cooked) and the modified latest OpenGApps file and it now works :)

I am guessing this won't be the same for all devices/ROMs, however it is a definite fix for my S6 & S6 Edge, both running home-cooked LineageOS 15.1 that I built earlier today.

The workaround getting the API 26 version into the OpenGApps .zip is a bit clunky but at least its a workaround.

Andy
[Android Software Development] duhec:
Don't know if it's new but I banged my head for a whole day some time ago figuring out why the screen would go blank when I was about to enter my google account email.

Anyway, you're welcome.
[Android Software Development] mkdante381:
Google Maps after install OpenGapps is not in polish language. This is old issue and not repaired. Only English...

Please fix this.
[Android Software Development] tfae:
Sorry if this was already answered, but how's the current situation about face unlock on Android 8.1?

What's the latest package with this feature working? Or what is the currently working fix?

Searching this thread I found this post but it's from months ago.
[Android Software Development] xerxes1511:
Hello

if I flash the opengapps do I have to register at google or is that obsolete?

The last time I flashed before that came with the register :confused:
[Android Software Development] githyanki:
During setup you will be asked to login to your Google account. That seems to take care of any registering necessary at the same time.
[Android Software Development] xerxes1511:
ok because in the PlayStore stands device is not verified

that is very confusing :D

Sorry for my bad english
[Android Software Development] githyanki:
That's normal, nothing to worry about.
[Android Software Development] xerxes1511:
thanks for the enlightenment :D
[Android Software Development] mkdante381:
Where is Chrome 73?
[Android Software Development] :
hey.. uhm.. whaaa..?

i get error 70 everytime i get to install gapps on my mi a2 lite.. like.. is it normal?