• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

G A S T

Senior Member
Apr 20, 2018
211
97
Xiaomi Mi 4
Samsung Galaxy S6
As I suggested, try formatting /system and reinstalling ROM and Gapps using their respective ZIP files. Maybe this also works for you.

So you performed a full wipe of your device to get AA to work? Sounds brutal to me.
Still thinking about other solutions. I guess there must be a less brutal and more precise attempt. It should be enough to wipe all AA related data from the device and then to dirtyflash a newer GApps-Version just after the ROM (in my case just the next LOS build).
 

rootarded

Senior Member
Sep 25, 2013
165
106
So you performed a full wipe of your device to get AA to work? Sounds brutal to me.
Still thinking about other solutions. I guess there must be a less brutal and more precise attempt. It should be enough to wipe all AA related data from the device and then to dirtyflash a newer GApps-Version just after the ROM (in my case just the next LOS build).

No no no, I just wiped the /system partition, leaving /data untouched. It's a dirty flash, just including a manual format of /system. No data is lost durig this process. And it only takes 5 minutes to do so. :)
 

G A S T

Senior Member
Apr 20, 2018
211
97
Xiaomi Mi 4
Samsung Galaxy S6
No no no, I just wiped the /system partition, leaving /data untouched. It's a dirty flash, just including a manual format of /system. No data is lost durig this process. And it only takes 5 minutes to do so. :)
Sorry! I was misinterpretating what you wrote. It's interesting that you left /data completely untouched and did not wipe "gearhead" there. Because that's what I'd wipe, too. Just to make sure that there is no bad AA leftover. 🤷‍♂️
 
Last edited:

Nezorflame

Senior Member
Sep 7, 2009
933
2,642
Moscow
nezorfla.me
Google Nexus 5
OnePlus 3
@Nezorflame: Why was the latest release (2021-07-31) removed from the servers? Is it faulty? Should I also roll back to 2021-07-30?

It seems that ARM package was built with errors, so just in case I pulled each variant from the server.
From what I can see it wasn't fully built, so if your install went fine, then you should be fine as well.
I've asked @mfonville to take a look (since build server is his domain).
 

G A S T

Senior Member
Apr 20, 2018
211
97
Xiaomi Mi 4
Samsung Galaxy S6
@Nezorflame: Why was the latest release (2021-07-31) removed from the servers? Is it faulty? Should I also roll back to 2021-07-30?
No, it's OK to use. It seems that there is only an issue with the ARM 32 Bit builds.
Im running the also pulled LOS 18.1 build from 2021-7-29 together with that pulled OGApps build for A11 from 2021-07-31 and everything works fine. So don't panic and don't roll back. 😉

By the way:
It was enough to remove the stub from app and priv-app in the system directory and to remove the remains from data and cache.
Android Auto works now with the head unit. 👌
 
Last edited:

rootarded

Senior Member
Sep 25, 2013
165
106
No, it's OK to use. It seems that there is only an issue with the ARM 32 Bit builds.
Im running the also pulled LOS 18.1 build from 2021-7-29 together with that pulled OGApps build for A11 from 2021-07-31 and everything works fine. So don't panic and don't roll back. 😉

By the way:
It was enough to remove the stub from app and priv-app in the system directory and to remove the remains from data and cache.
Android Auto works now with the head unit. 👌

I do use that 32 bit version - it installed and works just fine up until now. We'll see whether my phone explodes or not. :)
 

Linuxfan724

Member
Nov 16, 2018
6
0
I uninstalled magisk, disabled my substratum themes, and cleared my cache partition, then reflashed lineage 18.1, then gapps 20210810, then magisk. This solved my Android Auto issues.
 

Fornball

New member
Aug 15, 2021
1
0
Hello everyone, I think there is a problem with the chromebook integration in the nano package for android 11. I have recently switched from lineageos 17.1 to lineageos 18.1(flashed according nano packages each time) and since then the phone hub feature on my chromebook cant connect to my phone anymore. I have tried all possible solutions on the chromebook(even resetting it), so it must be an issue with the google play services
 

rootarded

Senior Member
Sep 25, 2013
165
106
Hello everyone, I think there is a problem with the chromebook integration in the nano package for android 11. I have recently switched from lineageos 17.1 to lineageos 18.1(flashed according nano packages each time) and since then the phone hub feature on my chromebook cant connect to my phone anymore. I have tried all possible solutions on the chromebook(even resetting it), so it must be an issue with the google play services
Did you try a clean flash already?
 

Maxii Chiara

Member
Mar 29, 2017
10
0
Buenos Aires
Hello, I have left an error or problem that occurs on my device (LeEco Le Max 2 x829) after installing the Gapps (arm64 v11.0 pico).
The problem starts to occur after the first reboot of the device.
Once you turn on the device the system UI conflicts and stops working, then when I try to enter the security pattern it asks me again endlessly and thus I can not access the device again.
The only thing I can do in those moments is see the notifications that come to me with the screen locked.
I would appreciate to verify this great inconvenience that would be happening at this moment, thank you very much in advance.
 

Maxii Chiara

Member
Mar 29, 2017
10
0
Buenos Aires
Hello, I have left an error or problem that occurs on my device (LeEco Le Max 2 x829) after installing the Gapps (arm64 v11.0 pico).
The problem starts to occur after the first reboot of the device.
Once you turn on the device the system UI conflicts and stops working, then when I try to enter the security pattern it asks me again endlessly and thus I can not access the device again.
The only thing I can do in those moments is see the notifications that come to me with the screen locked.
I would appreciate to verify this great inconvenience that would be happening at this moment, thank you very much in advance.

I forgot to mention that my device has the latest version of LineageOS ROM v18.1 so far, just like the Gapps used.
 

Top Liked Posts

  • 2
    Well, for starters some things can only be done from clean data: https://github.com/opengapps/opengapps/blob/master/scripts/templates/installer.sh#L1799

    Even if you did somehow make an identical config to avoid changing things drastically by switching GApps like that it could lead to unpredictable results since you're overlapping things (which could be quite different) in /system from both, and /data/system would also have to deal with the sudden changes.
  • 7
    Here are the test builds (nano variant) with the fixed permission, please check them out:
    ARM | ARM64
    These should just work, and the fix has been already merged, but we need to be sure that this was the only issue causing the bootloop.

    As for the other news:
    1. Unofficial builds from @ripee have been working well so far, so we're going to enable all of the package variants for SDK 30. Thanks for testing them!
    2. We've resumed the work on the build validation process, so that we can transition into the weekly-nightly scheme and release vetted (as much as possible assuming it's all going to be a volunteer work) build on weekly basis, while continuing to produce nightly builds for those who wants them. I'll share more news on this when the process will start.
    3. Before starting work on SDK31 aka A12, we'll make sure that we're able to properly generate (and validate) permissions for the APKs so that the issues like previous one don't happen anymore. We plan to integrate this check into the Gitlab pipeline to automate this process as much as possible.
    5
    New set of unofficial 11.0 packages will be up in around 6 hours, dated 20211008, from fully updated sources of course.

    Unofficial OpenGApps
    5
    Not booting open_gapps-arm64-11.0-nano-20211007.zip, drops into Android Rescue Party.
    Redmi 4X "santoni" 3/32, LineageOS 18.1 (a11) by 0xCAFEBABE 20211007 testing unofficial build. System-as-root, ARM64 A-only, OrangeFox recovery.

    I happened to have adb keys set on this rom before dirty-flash upgrading, so here's the logcat.
    Looks like a missing permission for Velvet (com.google.quicksearchbox), crashing Zygote.
    OpenGapps Build 20210925 worked fine previously. I flashed it back and booted normally.

    Code:
    E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.googlequicksearchbox (/system/priv-app/Velvet): android.permission.SUBSTITUTE_SHARE_TARGET_APP_NAME_AND_ICON}

    Huge thanks for the logcat! I was unable to reproduce this on my device so this helps a lot.

    We're going to implement automatic perm check soon-ish, for now we'll pull the problematic builds and implement the fix.
    4
    I've pinged @MastahF, @retired_mnbooze (retired?!) and @Nezorflame in our Slack to better get everyone's attention.

    Any logcat and dmesg from the bootloop? Might be a missing permission again.
    3
    Anyone else has a bootloop with open_gapps-arm64-11.0-nano-20210928 ?
  • 831
    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.