[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices

[dpeddi]

Hi,

I'm trying to install opengapps tvstock over an aosp android 9 build for a broadcom soc.

before installing opengapps android boot and I can get Launcher3.

Opengapps installation finish correctly but on reboot i never get the LeanbackLauncher nor the setup tungsten.setupwraith. I just have a black screen with the mouse pointer.

I've tried to read logcat * but is really a mess and i can't find out why the launcher doesn't come up.

There is some hint or someone that can help me? do you need i open a separate thread?

Thank you

 

[Nezorflame]

Hi everyone! Happy holidays

A bit late to the party, but here are the new test builds for Android 11.
This time we have a couple of fixes for multiple issues (thanks @Nikhil!) including new QuickWalletAccess APK for PixelLauncher to work properly, and also SetupWizard for ARM (thanks @althafvly!).
Also replaced Play Music for YouTube Music on SDK21+ (since it's not present for lower Android versions).

So, here are the builds: ARM | ARM64

As always, please post your feedback here or in the OpenGApps Telegram group.

 

[Nezorflame]

Hi everyone! Happy holidays

A bit late to the party, but here are the new test builds for Android 11.
...

There have been reports that stock+ variants don't boot for some people, so the new builds will be up in a few.
They will include a fix for the missing GMS permission.

EDIT: and they're up: removed

EDIT2: sorry guys, screwed up permissions a bit.
New builds: ARM | ARM64

 

[landry314]

I figured out how to use gapps-config on the Pixel LOS Recovery systems.

You need to push the gapps-config file to the /tmp/install directory right before install because the /data partition is not mounting during install with the LineageOS Recovery.

This is my cute command line to turn the package into Pico:

$ ./adb shell "mkdir /tmp/install/ && echo "PicoGApps" > /tmp/install/gapps-config.txt && echo File to downgrade to the pico package created successfully\! Please sideload opengapps now\!"

I wonder if some kind of note could be added to your opengapps wiki that explains that you need to have the /data partition mounted to read the gapps-config file and that you should push the file to /tmp/install/ first if you aren't using TWRP or a recovery that mounts /data.

And/Or create some kind of error message in the installer.sh script which mentions the /data partition is not available...

 

[ipdev]

I figured out how to use gapps-config on the Pixel LOS Recovery systems.

You need to push the gapps-config file to the /tmp/install directory right before install because the /data partition is not mounting during install with the LineageOS Recovery.

This is my cute command line to turn the package into Pico:

$ ./adb shell "mkdir /tmp/install/ && echo "PicoGApps" > /tmp/install/gapps-config.txt && echo File to downgrade to the pico package created successfully\! Please sideload opengapps now\!"

I wonder if some kind of note could be added to your opengapps wiki that explains that you need to have the /data partition mounted to read the gapps-config file and that you should push the file to /tmp/install/ first if you aren't using TWRP or a recovery that mounts /data.

And/Or create some kind of error message in the installer.sh script which mentions the /data partition is not available...

Can you just push a config file to /tmp/install ?
adb push gapps-config.sh /tmp/install/.gapps-config
Then start the sideload like normal?

Does it work if you install the rom from internal storage?
I assume they still have that option.
- Push config file to /tmp/install
- Choose install from internal storage.

If so, add something like this to the wiki.

Note:
To use a config file with LineageOS Recovery.

You need to copy your config file to /tmp/install/ before you begin the install.

Cheers.

 

[Nezorflame]

Can you just push a config file to /tmp/install ?
adb push gapps-config.sh /tmp/install/.gapps-config
Then start the sideload like normal?

Does it work if you install the rom from internal storage?
I assume they still have that option.
- Push config file to /tmp/install
- Choose install from internal storage.

If so, add something like this to the wiki.

Note:
To use a config file with LineageOS Recovery.

You need to copy your config file to /tmp/install/ before you begin the install.

Cheers.

There's already a section in the official wiki which describes places for the config file:

The gapps-config file must be named one of the following:

• .gapps-config (takes precedence)
• gapps-config.txt

You can have a device-specific gapps-config file. You will need your device name, which you can find in open_gapps_log.txt or in the name of your ROM download. The gapps-config file must be named one of the following:

• .gapps-config-DEVICENAME
• gapps-config-DEVICENAME.txt

Device-specific config files will take precedence over the non-device-specific ones.

The gapps-config file must be placed in one of the following folders:

• the folder containing the Open GApps installer (takes precedence)
• /data
• /persist
• /sdcard
• /sdcard/Open-GApps
• /tmp/install

 

[landry314]

Yes, indeed, pushing the gapps-config file to /tmp/install works fine - i just said that ;-)

$ adb push PATHONPC/gapps-config.txt /tmp/install/gapps-config.txt

No, you can't install from internal storage unless it is mounted and LOS Recovery does not mount /data/ or /sdcard/ to read the installer. or the config file. It must be sideloaded. This is the issue I am talking about.

I like your addition to the wiki!

Can you just push a config file to /tmp/install ?
adb push gapps-config.sh /tmp/install/.gapps-config
Then start the sideload like normal?

Does it work if you install the rom from internal storage?
I assume they still have that option.
- Push config file to /tmp/install
- Choose install from internal storage.

If so, add something like this to the wiki.

Note:
To use a config file with LineageOS Recovery.

You need to copy your config file to /tmp/install/ before you begin the install.

Cheers.

 

[landry314]

Yes, indeed, pushing the gapps-config file to /tmp/install works fine - i just said that ;-)

$ adb push PATHONPC/gapps-config.txt /tmp/install/gapps-config.txt

No, you can't install from internal storage unless it is mounted and LOS Recovery does not mount /data/ or /sdcard/ to read the installer or the config file. It must be sideloaded. This is the issue I am talking about.

I like your addition to the wiki!

 

[landry314]

There's already a section in the official wiki which describes places for the config file:

Yes, I have read it. The issue I encountered is that if you place the config file on /sdcard/ thinking it will work, the installer goes through the motions without finding the file. I had to figure out how to do it on my TWRPless phone.

I wonder if /persist/ might be an easier way to store the file...

 

[ipdev]

There's already a section in the official wiki which describes places for the config file:

True.
I normally use /sdcard/Open-GApps/.gapps-config

With the bring up of Lineage 18.1 and the lack of TWRP compatibility, more users are going to be using LineageOS recovery.
@landry314 noted the config file was not being read when sideloading opengapps.
Apparently it worked if he created a config file in /tmp/install/

If this is the case, maybe a note page or a section in the FAQ for using Lineage recovery is needed.
Just in case it is not included in the instructions for the Lineage build.

---

Note:

I just tried l18.1 on a Pixel 4a using Lineage recovery.
First time using the new Lineage recovery.
I had no issues using a config file in /sdcard/Open-GApps/
Might be the difference between device/bringup.
Maybe steps used?
¯\_(ツ)_/¯

---

Steps used.

Installed current Google factory rom to both slots.
Flashed the lineage boot image to both boot_a and boot_b.
Rebooted to recovery.
Selected Factory reset.
- Since this was an initial install.
Used adb sideload to install rom.
Rebooted to recovery.
- To be on the correct slot.
Enabled adb under advanced options.
Used adb to push config file to /sdcard/Open-GApps/
adb push gapps-config.sh /sdcard/Open-GApps/.gapps-config
Used adb sideload to install opengapps-stock.
Pulled /sdcard/ to grab opengapps logs.
Used adb to sideload magisk-canary.
Rebooted to system.

Yes, I have read it. The issue I encountered is that if you place the config file on /sdcard/ thinking it will work, the installer goes through the motions without finding the file. I had to figure out how to do it on my TWRPless phone.
I wonder if /persist/ might be an easier way to store the file...

I would stay away from persist.
Take a look at the issues Pixel(s) have with sensors when persist is messed with.
Two examples.
I need help obtaining a the root/mnt/vendor/persist/sensors folder xda thread - Link
FIXED - Android 10 - Sensors Bug xda thread - Link

Cheers all.

Edit:
PS.
Updates kinda suck.
Lineage recovery for Pixel 4a (not sure if it is all) does not support backup scripts.
Had to reboot into recovery to reinstall opengapps and magisk.
Magisk took but, I had to reboot into recovery once again to reinstall opengapps. WTF?

 

[Nezorflame]

/tmp/install/ was specifically added for those who sideload OpenGApps without the access to /data or /sdcard. So yeah, for now this is probably the best option.

 

[curiousrom]

TWRP Not Compatible with Unofficial LineageOS 18.1?

...With the bring up of Lineage 18.1 and the lack of TWRP compatibility...
I just tried l18.1 on a Pixel 4a using Lineage recovery...

Thanks for the detailed post & report.

I don't see an official TWRP page for the Pixel 4a in https://twrp.me/Devices/ @ the present.

On what are you basing that statement?

Did you see the official TWRP post TWRP 3.5.0 Released ?
***

 

[ipdev]

TWRP Not Compatible with Unofficial LineageOS 18.1?



Thanks for the detailed post & report.

I don't see an official TWRP page for the Pixel 4a in https://twrp.me/Devices/ @ the present.

On what are you basing that statement?

Did you see the official TWRP post TWRP 3.5.0 Released ?
***

Not only Pixel devices but, as you noted, there is no TWRP for Pixel 4a.
Devices Google - twrp.me - Website - Link

Even then, only bonito, crosshatch, flame, coral and dragon got updated.
Pixel C (dragon) does not count. It is the Pixel tablet even Google tries to forget.
Dragon was originally released with Android 6.x
Followmsi is a dedicated device maintainer.

From the update note you linked.
TWRP 3.5.0 Released - twrp.me - Website - Link

And finally myself, bigbiff has put in a lot of work over the past year while Dees_Troy is able to get back to helping us again with the Android-11 release. I have started a bringup for an Android-11 merge, and will be working on the Pixel 5 bringup. I hope the progression is shorter in 2021.

An old note from Dees_Troy about Android 10.
TWRP and Android 10 - twrp.me - Website - Link

As @landry314 mentioned, TWRP for Pixel 3 does not support Android 11.

Cheers.

 

[LilBlinx]

There have been reports that stock+ variants don't boot for some people, so the new builds will be up in a few.
They will include a fix for the missing GMS permission.

EDIT: and they're up: removed

EDIT2: sorry guys, screwed up permissions a bit.
New builds: ARM | ARM64

Seems like Google Drive is crashing

01-17 02:13:54.094 21396 21497 E Cello   : [21497:cello_thread] drive_v2_cloud_store.cc:1805:HandleFileResponse Transport error: UNAUTHENTICATED:  when getting https://www.googleapis.com/drive/v2internal/files/root?allProperties=false&featureLabel=android-sync-native&includePermissionsForView=published&reason=1413&reportPermissionErrors=true&supportsAllDrives=true&fields=kind%2Cparents%2Fid%2Ctitle%2CmimeType%2Clabels%2Fstarred%2Clabels%2Ftrashed%2Clabels%2Frestricted%2Clabels%2Fviewed%2CcreatedDate%2CmodifiedDate%2CmodifiedByMeDate%2ClastViewedByMeDate%2CfileSize%2Cid%2Cshared%2CsharedWithMeDate%2CexplicitlyTrashed%2CquotaBytesUsed%2Ccapabilities%2FcanCopy%2Csubscribed%2Ccapabilities%2FcanDownload%2CprimarySyncParentId%2Cmd5Checksum%2CflaggedForAbuse%2CfolderFeatures%2Cetag%2CexportLinks%2Cspaces%2CownedByMe%2Ccapabilities%2FcanEdit%2Ccapabilities%2FcanComment%2ChasThumbnail%2Crecency%2CrecencyReason%2Cversion%2CactionItems%2Ccapabilities%2FcanAddChildren%2Ccapabilities%2FcanDelete%2Ccapabilities%2FcanRemoveChildren%2Ccapabilities%2FcanShare%2Ccapab
01-17 02:13:54.094 21396 21497 E Cello   : [21497:cello_thread] item_query_handler.cc:938:OnCloudByIdQuery Failed to get items from the cloud: MessageLite at 0x7a71c7a1b0
01-17 02:13:54.094 21396 21497 E Cello   : [21497:cello_thread] drive_v2_cloud_store.cc:177:LogBatchResponseWithTrace Transport error: UNAUTHENTICATED:  when getting https://www.googleapis.com/drive/v2internal/files/root?allProperties=false&featureLabel=android-sync-native&includePermissionsForView=published&reason=1413&reportPermissionErrors=true&supportsAllDrives=true&fields=kind%2Cparents%2Fid%2Ctitle%2CmimeType%2Clabels%2Fstarred%2Clabels%2Ftrashed%2Clabels%2Frestricted%2Clabels%2Fviewed%2CcreatedDate%2CmodifiedDate%2CmodifiedByMeDate%2ClastViewedByMeDate%2CfileSize%2Cid%2Cshared%2CsharedWithMeDate%2CexplicitlyTrashed%2CquotaBytesUsed%2Ccapabilities%2FcanCopy%2Csubscribed%2Ccapabilities%2FcanDownload%2CprimarySyncParentId%2Cmd5Checksum%2CflaggedForAbuse%2CfolderFeatures%2Cetag%2CexportLinks%2Cspaces%2CownedByMe%2Ccapabilities%2FcanEdit%2Ccapabilities%2FcanComment%2ChasThumbnail%2Crecency%2CrecencyReason%2Cversion%2CactionItems%2Ccapabilities%2FcanAddChildren%2Ccapabilities%2FcanDelete%2Ccapabilities%2FcanRemoveChildren%2Ccapabilities%2FcanShare%2
01-17 02:14:00.419 21396 21454 E GooglePlayServicesUtil: GooglePlayServices not available due to error 9
01-17 02:14:00.420 21396 21454 E AccountsCentral: [io-3] Error accessing 'com.google' accounts. Returning empty array.

 

[ipdev]

@LilBlinx

If you look a little higher in the log do you see something like this.
The errors have changed slightly but they always look something like this.

12-31 16:26:01.135 12899 12899 E ccl_wif : [vnull] Couldn't find the appropriate version of Google Play Services

01-09 16:46:24.906  6377  6377 E GoogleApiAvailability: Google Play services is invalid. Cannot recover.
01-09 16:46:24.916  6377  6377 W GoogleApiAvailability: Creating dialog for Google Play services availability issue. ConnectionResult=9

Cheers.

Edit:
If installed from PlayStore, does gDrive work correctly?

 

[LilBlinx]

@LilBlinx

If you look a little higher in the log do you see something like this.
The errors have changed slightly but they always look something like this.

12-31 16:26:01.135 12899 12899 E ccl_wif : [vnull] Couldn't find the appropriate version of Google Play Services

01-09 16:46:24.906  6377  6377 E GoogleApiAvailability: Google Play services is invalid. Cannot recover.
01-09 16:46:24.916  6377  6377 W GoogleApiAvailability: Creating dialog for Google Play services availability issue. ConnectionResult=9

Cheers.

Edit:
If installed from PlayStore, does gDrive work correctly?

Since it is the newest version, it is impossible to get it updated. Sideloading the newest version with the

adb install -r -d

command also does not work. But when I did clean flash and tried installing it directly from Google Play Store on, yes it does work.

EDIT: Meaning not installing Drive from OpenGapps packages

 

[ipdev]

Since it is the newest version, it is impossible to get it updated. Sideloading the newest version with the

adb install -r -d

command also does not work. But when I did clean flash and tried installing it directly from Google Play Store on, yes it does work.

EDIT: Meaning not installing Drive from OpenGapps packages

This error seems to be growing on all Android 11 gapps builds, not just OpenGApps.
When some apps are installed by third-party (Not installed by PlayStore).

YouTube is complete loss.
Google Maps gives the error but, seems to work if you select it from recent. Gives the error again after you close and reopen Maps.
YT Music and Google Drive worked a few weeks ago when I was looking for apps that give this error.

Not sure how/why it is corrected when installed from PlayStore?
If I remember correctly there was an error in the log when installing YouTube from PlayStore but, I did not see how it was corrected.
Edit: How it was corrected by PlayStore when installing.

Cheers.

 

[LilBlinx]

This error seems to be growing on all Android 11 gapps builds, not just OpenGApps.
When some apps are installed by third-party (Not installed by PlayStore).

YouTube is complete loss.
Google Maps gives the error but, seems to work if you select it from recent. Gives the error again after you close and reopen Maps.
YT Music and Google Drive worked a few weeks ago when I was looking for apps that give this error.

Not sure how/why it is corrected when installed from PlayStore?
If I remember correctly there was an error in the log when installing YouTube from PlayStore but, I did not see how it was corrected.
Edit: How it was corrected by PlayStore when installing.

Cheers.

True indeed, Maps is erroring out here too but it works somehow. I believe that there are more apps that have the same behavior.

EDIT: Google Docs spits out warning about not being installed from the Play Store too

 

[hzr34]

I have a problem with android auto in open gapps aroma installer linage 17 android 10. Not working also I am not able access aa developer settings. Is anyone have a idea. Btw uninstall and clean install servel times

 

[jllmoe]

I have a problem with android auto in open gapps aroma installer linage 17 android 10. Not working also I am not able access aa developer settings. Is anyone have a idea. Btw uninstall and clean install servel times

Just installed Lineage OS 18.1 and latest BitGapps, I have to go back a couple of versions to make Google Maps work, and have to go back many versions (May 2020) to make Android Auto not flash closing, BUT after Android Auto is started it says "update needed" and I have to click Accept or Exit, if I click Accept, it will be updated to the latest version and flash close, if I choose Exit, nothing will happen. So I am still unable to use Android Auto.

Personally I do not think this is a GApps issue, because I was able to install many apps including these two from the play store, I have no issue with other apps. I have used the GPS Status and Tool app to reset the GPS data, and cache clean tens of times, the only thing made some improvement was to roll back the version of the app, but this so far still did not resolve the issue for Android Auto. Any suggestion on the Android Auto fix will be highly appreciated.