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

Search This thread


Senior Member
Jan 15, 2011

I'm running LineageOS 17.1 on my Nexus 6 and my OnePlus 6T with OpenGapps (nano variant).

After a recent upgrade of both LineageOS build (2021 02 17) and OpenGapps 10 nano (2021 02 13) on my OnePlus 6T my Android Auto (6.1.610534) started not being happy ("no app compatible with USB device") when connecting to my car head unit (Rlink2)

My Nexus 6 with Lineageos build from 2021 02 06 and OpenGapps 10 nano from 2021 02 06 was still working flawlessly with Android Auto (6.0.615343) and my car head unit...

So I did a few tests on Nexus 6 to figure what was the cause : the LineageOS upgrades or OpenGapps Upgrades

Open Gapps 10 nano 202102 06OpenGapps 10 nano 2021 02 17
LineageOS 17.1 build 2021 02 06OKProblem
LineageOS 17.1 build 2021 02 17OKProblem

This clearly suggested OpenGapps was the culprit and was confirmed by downgrading my OnePlus 6T to OpenGapps build 2021 02 06 which also solved its Android Auto issue.

So something is not OK in OpenGapps 10 nano builds 2021 02 13 to 2021 02 17... and maybe ealier as I haven't tested builds 2021 02 07 to 2021 02 12...
Anything <= 2021 02 06 works.

I can do tests if it can help narrow things down...

Issue still present in openGapps 10 nano 2021 04 14
Last edited:


  • Dec 26, 2012
    I am trying to use latest test version of GApps for Android 11 (HavocOS 4.2 ROM for Xiaomi Mi 9), and I encountered a problem.

    Data migration from cloud is not working, since seemingly now Backup and Restore tool requires Data Transfer Tool (pixelmigrate), which is not installed:
    03-05 14:51:57.808 8095 8095 E AndroidRuntime: FATAL EXCEPTION: main
    03-05 14:51:57.808 8095 8095 E AndroidRuntime: Process: com.google.android.apps.restore, PID: 8095
    03-05 14:51:57.808 8095 8095 E AndroidRuntime: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=com.google.android.apps.pixelmigrate.ACTION_D2D_MIGRATE_FLOW (has extras) }

    I managed to circumvent it by manually extracting AndroidMigratePrebuilt.apk from GApps package, installing it, granting it all possible permissions from GUI and also granting android.permission.WRITE_SECURE_SETTINGS manually via adb.

    But I really hope it will be fixed in future releases.
    • Like
    Reactions: luc_luke


    Senior Member
    Mar 22, 2012
    Hi, Nokia PL2, Lineage 18.1 (0308) and opengapps 0130 nano. After adding an account, no calendar or contacts sync is available. With google calendar app added, calendar sync is available, contacts won't sync even with google contacts installed. (google contacts asks to configure an account)

    Edit: installed pico opengapps (0130) and contacts sync. Looks like there is an issue with the nano packaging.
    Last edited:


    Senior Member
  • Mar 25, 2008
    Issaquah, WA
    Hello, Nexus 6 latest LOS 17.1 here.
    Since a few OpenGapps releases, Photos and Google news crash on startup. I'm using stock version of Gapps. Anyone with the same issue?
    Yes, I'm seeing the same thing on both arm and arm64 builds for 10.0. I'm rolling back to see if I can determine the last known good build.

    UPDATE: I rolled all the way back to the 20210130 build and was still seeing the problem with Google News, but Google Photo was fine in the 20210311 build. I think I'm just going to stick with the 20210311 build and manually replace the Newsstand folder.

    BTW, the problem seems to be a missing resource (Resources$NotFoundException: Resource ID #0x7f08038a).

    UPDATE 2: Glad to see a 20210324 build today, and Google Photo is working again! Google News, however, still crashes on launch and only works for me when Newsstand is replaced with version


    • debug.log
      10.4 KB · Views: 3
    Last edited:


    New member
    Nov 14, 2015
    On the latest versions of opengapps, it is impossible to configure Google Assistant, it crashes when connecting to it, the last working version of this assistant was 2020.04.22


    Senior Member
    Sep 6, 2009
    Yogyakarta & Purbalingga
    I've tried that, with TWRP and X-plore. It crashes when launching. Apparently that's an Android 10 thing. Some apps work with this method, most don't.
    It's because the apk contains compressed "native libs".
    Two options:
    1. Repack the apk with the libs uncompressed.
    2. Extarct the libs to the same folder as the apk, example for 64bit:
    • Like
    Reactions: oidicle


    Senior Member
    Apr 10, 2015
    It's because the apk contains compressed "native libs".
    Two options:
    1. Repack the apk with the libs uncompressed.
    2. Extarct the libs to the same folder as the apk, example for 64bit:
    Okay, so option 1 I'm unsure how to proceed.
    Option 2: I copied the files from a ROM which had it installed and running perfectly on the System partition, it has the lib folder inside. See image below:

    It didn't work. Unless I did something wrong. I'm running LineageOS 17.1 on a Galaxy Note 5.


    Senior Member
    Apr 10, 2015
    Nevermind, I did it!

    I first installed it via the Play Store and then copied the APK's folder containing the lib and oat folders, then moved it to System/App, using X-plore. Take a look.👇🏽👇🏽

    Everything's fine now. Now, should I ever need to do a factory reset, I won't have to worry about these apps (Gallery Go and Nova Launcher) being deleted.

    Thanks a lot.
    Last edited:


    Senior Recognized Developer / Contributor
  • Mar 14, 2012
    Nexus 7 (2013)
    • Like
    Reactions: luc_luke


    Senior Member
    Sep 2, 2010
    OnePlus 3T
    OnePlus 8T
    I was just curious on status of 11 builds and certainly didn't intend my wording to be taken as any kind of statement. Thanks for the link.
    I rarely update my Gapps packages unless there's something specific that's broken and needs fixing.
    I've had absolutely no problems with 210130 so my next update will be the release version and that will be it for me until Android 12.
    Note: I use the Pico package and install the apps I use from the Play Store.
    • Like
    Reactions: luc_luke

    Top Liked Posts

    • There are no posts matching your filters.
    • 2
      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.

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

      Stop asking about an ETA for a release in general. It will be released when it's ready to be released.
      Will the next OGApps test builds for A11 include again all packages like the ones released in january? 🤔
      That would be great. ✌️
    • 829
      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
      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
      For those who hadn't spotted it yet: we can celebrate 1 year of Open GApps :)
      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
      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.