• 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

ripee

Recognized Developer / Recognized Contributor
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
 

emuandco

Senior Member
Aug 29, 2009
1,126
496
35
Steinfeld
www.dreimer.de
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
Just installed the Mini pack and it works great. Thanks for that @ripee ^^
But before someone tries it in the hope to fix Android Auto... Still the same problem here.
 

1emrys1

Senior Member
May 29, 2013
765
565
Has anyone tried the Aroma version in the last few months? Like aroma package on Lineage os 17.1. Does it work without issues? I had heard that aroma isn't supported by recoveries properly.
 

Kampfwurst

Member
Jul 24, 2021
6
1
Yep, but it does not connect, like I stated here already on Thursday...
Thanks for your confirmation!
So the AA stub in OpenGApps must be defective.

The USB-Connection flipps always back to "no data", when setting it to "MTP" manually. And meanwhile it crasehes. I made some screenshots during my last attempt yesterday...

Update:
Tried again a lot of different settings for Google Play Service rights and notifications and in the developer settings of the system. Android Auto definately does not initiate a connection to the car media system. So it's not my device/service settings. The MIUI 12.0.1 Android device of my girlfriend works instant together with it. So it is definately not the fault of the media system. By the way - a few weeks ago I connected an iPhone of another friend sucessfully with the car.
same here. open_gapps-arm64-11.0-pico-20210723.zip and no luck with AA.

please fix it.
 
  • Like
Reactions: G A S T

Gene-13

New member
Jan 12, 2021
3
2
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. :)
Can confirm the problem. 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.

Not sure if it matters/causes the problem, but the order of gmscore densities in app_densities.txt has changed in 20210727 compared to 20210724. gmscore update (from 21.24.18 to 21.24.56) might be the other reason.
 
  • Like
Reactions: curiousrom

G A S T

Senior Member
Apr 20, 2018
211
97
Xiaomi Mi 4
Samsung Galaxy S6
After updating AA a from version 6.5.612134 to the latest version 6.6.612534 I get now the following error message under "connection help" in the menu:
"Android Auto was not pre-installed on this device

Android Auto must be bundled with your operating system to work correctly. Please contact your phone manufacturer for assistance."

Now it's undoubtly clear, that the AA stub implementation in OpenGApps ist broken with regards to the car/head unit connectivity.

I dirty flashed GApps Pico x64 manually together with the latest LOS 18.1 build for my device last week. This should be enough for a working "bundling" with GApps.
 
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.
***
 
Last edited:

G A S T

Senior Member
Apr 20, 2018
211
97
Xiaomi Mi 4
Samsung Galaxy S6
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.
 

G A S T

Senior Member
Apr 20, 2018
211
97
Xiaomi Mi 4
Samsung Galaxy S6
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.
 

Nezorflame

Senior Member
Sep 7, 2009
934
2,644
Moscow
nezorfla.me
Google Nexus 5
OnePlus 3
Thank you for your reports.

We've fixed (at least according to the user reports) the AA stub APK (by moving it to priv-app instead of app folder) so that change should come live with the next build.
As for the 27th and 28th builds - I've removed them from the website and SF for now, hopefully will resolve that as well before the next build arrives. Otherwise it'll be pulled as well.
 

Nezorflame

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

FridgeBoxX

Member
Jan 10, 2008
10
2
For me Android Auto is now working, however on about every second start of the device (Pixel 4a), the Play Services are not available.
I've to investigate the cause of this, could be related to the latest broken LOS 18.1 image from yesterday or image_a/b thing.
 
  • Like
Reactions: G A S T

rootarded

Senior Member
Sep 25, 2013
165
106
I must correct myself: after formatting /system and reinstalling ROM and Open Gapps it now works flawlessly! I'd recommend doing this to anyone still having issues after updating to 2021-07-30!
@Nezorflame: Thank you for your work!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    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 the core of both, and /data/system would also have to deal with the sudden changes.
    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.
  • 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.