• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

r6680jc

Senior Member
Sep 6, 2009
438
84
Yogyakarta & Purbalingga
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?
Just sideload the Gapps should be enough.
 

@RMIN

Member
Jan 13, 2009
15
4
Semnan
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.
 

Attachments

  • gapps-config.txt
    8.8 KB · Views: 19
  • open_gapps_log.txt
    9.9 KB · Views: 11
Last edited:

macgyver77

New member
Jun 8, 2021
1
3
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.
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

Bash:
# 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...)
 

tomKater

Member
Jul 29, 2014
33
7
Huawei MediaPad M5 Lite
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.
Hi,

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

Thk.
 
  • Like
Reactions: UlricGrave34

Nezorflame

Senior Member
Sep 7, 2009
924
2,604
Moscow
nezorfla.me
Google Nexus 5
OnePlus 3
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

Bash:
# 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...)

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.
 
Apr 4, 2017
288
148
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?
 

Flamefire

Senior Member
Jul 26, 2013
101
135
Sony Xperia XZ1 Compact
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:
Code:
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/[email protected] 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?
 

ipdev

Recognized Contributor
Feb 14, 2016
1,433
1
1,669
Google Nexus 10
Nexus 7 (2013)
Can somebody send me older version without Google Searchbar, not fun.
Android 6 Arm.
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.
Code:
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.
Code:
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:
 

G A S T

Senior Member
Apr 20, 2018
195
89
Xiaomi Mi 4
Samsung Galaxy S6
So 11 is finally officially available (pico/nano only)!
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.
 
Last edited:

Nezorflame

Senior Member
Sep 7, 2009
924
2,604
Moscow
nezorfla.me
Google Nexus 5
OnePlus 3
So 11 is finally officially available (pico/nano only)!

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.

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 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.
 

G A S T

Senior Member
Apr 20, 2018
195
89
Xiaomi Mi 4
Samsung Galaxy S6
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?
 
Last edited:

emuandco

Senior Member
Aug 29, 2009
1,125
496
34
Steinfeld
www.dreimer.de
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.
 

Top Liked Posts

  • 4
    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. :)
    4
    As for the testing - I've put that back for a pretty long time, and it's definitely something that I'd love to see one day, so we're returning to this idea of "stable" and "nightly" builds.

    This weekend I'll start preparing the infrastructure for this, and we'll recruit testers in the Telegram group. I'll post the results, links and the process for testing as soon as it's ready.
    3
    Open GApps for Android 11 Build 2021-07-27 & 28 Causing Bootloop - Android 10 Also?

    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).

    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.

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

    problem with the latest opengapps (28.07.2021)
    hello guys, i tried with twrp and the lineage one, too.im pretty sure the opengapps build is the problem, I tried open_gapps-arm64-11.0-nano-20210720, and it went good! xiaomi mi mix 2 (chiron)

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

    I had the same issue... Thanks to this post I tried a rollback and so I can confirm that open_gapps-arm-10.0-nano-20210727.zip works fine for my SM-A510F (unlike 20210728).

    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.
    ***
    2
    Open GApps for Android 11 Build 2021-07-27 Causing Bootloop





    Well an other user reported the same issue in Reddit here



    Heloooo @Nezorflame?

    As I posted several time in this thead because Google is changing the goal posts all the time with privapp permissons (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 when the user logs in Play Store?
    ***
    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.
    2
    The AA-Problem will be fixed soon:

    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.
  • 17
    So 11 is finally officially available (pico/nano only)!

    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.

    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 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.
    9
    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.

    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: 👍
    ***
    5
    So 11 is finally officially available (pico/nano only)!
    5
    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
    4
    Can somebody send me older version without Google Searchbar, not fun.
    Android 6 Arm.
    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.
    Code:
    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.
    Code:
    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:
  • 830
    Questions? Use Q&A!
    Please read the FAQ before reporting any bugs or errors!
    If you post in the main thread not having read the FAQ or error message itself, not included a debug log when reporting a malfuction or reporting a Force Closure without a logcat, your post will be ignored by the developers!
    Not because we are evil, but because the same questions keep popping up over and over again and too often we get a "X doesn't work, plz fix" without any clue what is happening. We don't have telepathic connection to your device and all the time unnecessarily wasted on this can't be spend on development of Open GApps itself.

    The Latest builds of Open GApps for Android can easily be downloaded from the:


    I work on this project for FREE and putting in a lot of hours into it. While not mandatory, donations encourage me to continue to further pursue this project and I'd deeply appreciate them, if you feel generous.
    Donate to The Open GApps Project


    Are you a ROM developer and want to hotlink to the latest Open GApps package? Then check this wiki entry for details.
    Please don't publicly mirror the prebuilt packages without explicit consent of @MastahF, to ensure that users will always be directed to the very latest version and the source code of the project.


    About The Open GApps Project
    Open GApps is a Google Apps package completely developed by writing buildscripts which allow for the automated creation of new up-to-date packages automatically.
    The development process is completely open-source (GPLv3) and the goal is to have multiple contributors involved, to secure and reinforce the sustainability of Open GApps development.
    Builds are generated every (European) night automatically (if there are any changes) and uploaded to GitHub.

    Official AROMA Open GApps package is developed in collaboration with long-time LP-AROMA-developer @raulx222 and has a dedicated XDA thread
    For any questions about the AROMA installer development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.

    Official Open GApps For Stock support is developed in collaboration with @Rapper_skull and has a dedicated XDA thread
    For any questions about the GApps for Stock development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.

    The x86 package branch of the package is focused on Zenfone support and is maintained by @deadman96385 of the famous Zenfone GApps packages and has its own topic for x86 related questions

    For those that cook their own ROM, an AOSP-build mechanism for Open GApps has been developed by @blystad and can be found at GitHub, remember that you should not bundle any pre-packaged Google Apps with any ROMs you want to distribute further though.

    To gather all the various APKs that are necessary for the packages our master of the APK Universe @MNBooZe has written a tool called APKCrawler that scrape these from the internet, e.g. from APKMirror, it can be found at GitHub too.

    Characteristic of Open GApps:

    • Some highlights about the characteristics of the Open GApps packages:
    • All platforms and and all Android versions are supported
    • DPI-optimized support for all Google packages (unlike other GApps)
    • Frequently updated Google Apps: The pre-built OpenGApps.org packages are updated every (European) night (if there are any updated Google Apps available)
    • Strong compression, allowing for relatively small downloads of even the most complete packages
    • Automatic backup: It is not necessary to re-flash Google Apps when you flash a ROM update. Most ROMs support this (addon.d) function
    • The installer checks your device’s capabilities, like the system partition size. It will notify you, before making any changes, if it finds any problems
    • Several package variations, from a Google Super Package (includes all applications that ever shipped on a Google device), to a Stock package that equals the set of applications found on the most current and complete Nexus, to smaller, minimalist packages and an AROMA package that allows graphically selection of what to install
    • A special ‘for Stock ROM’ installation mode that allows to update the Google Apps on Stock ROMs that conform to the original Google Nexus filesystem structure
    • All package installations can be customized to your individual preferences using our Advanced Features and Options

    The idea behind this project:
    I believe a big source of the problem for many GApps packages to stay up-to-date (or not be forfeited) is the lack of time for developers to do labour-intensive repetive every time a new google-app apk is released.
    That is why I have taken it upto myself to write some Linux shell scripts to automate the packaging and to share these efforts with the world with the goal to create a team to continue this package together under the name Open GApps.


    This project should not be managed by a person, but by a team, so volunteers willing to help are more than welcome!

    Open GApps installer uses open source third-party tools, like busybox and xzdec, compiled by @YashdSaraf; See his busybox thread for more info.
    Open GApps is originally based on the now discontinued PA GApps package of @TKruzze and @osm0sis
    25
    Tomorrow there will be 7.0 builds
    Small update concerning Nougat: everything is almost in place, only HotWord Enrollment is not de-odexable yet.
    So tomorrow there will be 7.0 builds, ready for when the first source and custom ROMs will drop.
    Of course beta-quality because they cannot be tested yet, so be careful.
    There are some minor changes, Google changed their keyboard stuff, so there will be no swypelibs possible anymore.
    Google VR Services is backported to all Android versions (so all the way from 4.4 to 6.0) but ofc not yet known how well it will work.
    Also there are some new 7.0 core apps for Google's Shared Android Services (com.google.android.ext.shared; com.google.android.ext.services)
    Trusted Face's unlock has also some major changes, it seems the pittpatt suff is not necessary anymore for 7.0.

    That's it for now
    25
    For those who hadn't spotted it yet: we can celebrate 1 year of Open GApps :)
    http://opengapps.org/blog/post/2016/05/09/open-gapps-first-anniversary/
    23
    Sorry to drop in but needed to clean up some unnecessary posts that were burying more legitimate posts to the thread.

    Going into someone's thread and demanding they make you something is not only just plain rude, it goes against everything XDA is about. Numerous people suggested a way for you to remove the gapps and you chose to ignore them. The dev isn't going to make an uninstaller just for you. You could also always use root explorer and remove the apps that way too. Anywho, there won't be an uninstaller made so no need to continue this conversation.

    Thread Cleaned
    23
    A very small update on the latest Open GApps development focus: Recently most effort went to the APKCrawler project.
    We wanted to mature our playstorecrawler scripts and with the help of @therealssj, who is expert on the Play Store protocol, we were able to make a fully functional crawler for the Play Store (next to our regular crawling of websites like apkmirror). That means we (read: @MNBooZe) are able to fetch APKs for all dpis and all architecture straight from the Google source and greatly helps to have as complete as possible packages for every device available.