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

Search This thread
Open GApps Android 11 Nano Builds 20210928 and 20210929 Bootloop!

Yes.

A Pixel 2 with Open GApps Nano + LineageOS here and LineageOS 18.1 on (Miatoll) Redmi Note 9 Pro with open_gapps-arm64-11.0-nano-20210929.zip here.

Edit: an other LineageOS 18.1 user of open_gapps-arm64-11.0-nano-20210929 with a bootloop issues here. 🤪

It's sad & an other hit on the reputation of the Open GApps project. That's what happens when builds are shipped without testing as I mentioned over & over in this thread.

Build weekly or monthly instead of daily & test before releasing!

Hello, @Nezorflame?
***

@Nezorflame - Since the bootloop with builds 20210928 and 20210929 was reported here and in your Telegram group more that 2,000 new downloads were made and I keep seeing users posting about it here, in Reddit & elsewhere. :(

That's a big waste of time for baffled users. 🥴

PLEASE REMOVE from the servers the defective builds ASAP!!!! 😳

https://sourceforge.net/projects/opengapps/files/arm64/
***
 
  • Like
Reactions: holavilla and Poquo

baudav

Member
Jul 10, 2007
17
1
Hi,
I can't add children Google account on Lineage-17.1 with Gapps; Is there a prerequisite? problem with Gapps or with the OS?
Issue Open for LineageOS: 1839

edit: it's work with 18.1 after first start (start without account, add account when lineageOS ready
 
Last edited:

ALTracer

Member
May 5, 2018
15
19
Cheboksary
4pda.ru
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.
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}
 

Attachments

  • logcat-santoni-20211007.log.gz
    737.8 KB · Views: 10

Nezorflame

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

Nezorflame

Senior Member
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.
 
Last edited:
Open GApps Android 11 Nano Builds 20211007: Bootloop Again!

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}

Thanks for the report & log. :cool:👍

An other user here in the LineageOS subreddit got fuzzed by the broken Nano Android 11 when upgrading his Fairphone 3+ from LineageOS 17.1 to 18.1 + open_gapps-arm64-11.0-nano-20211007.zip. :(
***
 
  • Like
Reactions: holavilla

ALTracer

Member
May 5, 2018
15
19
Cheboksary
4pda.ru
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.

I flashed 20211008 build (downloaded via OpenGapps App from SourceForge), seems to work fine. At least it booted.

Thanks for timely fix.

edit: see quote for device
Redmi 4X "santoni" 3/32, LineageOS 18.1 (a11) by 0xCAFEBABE 20211007 testing unofficial build.
 
Last edited:

ALTracer

Member
May 5, 2018
15
19
Cheboksary
4pda.ru
You could have more than one device, some new readers may not want to check the previous pages.

Is your copy/paste broken? :)
***
Even though I happen to have two phones, the sensible default is the one just mentioned. I never explicitly stated I'd updated my rolex from LOS17.1 or bricked my santoni.

Yes, my copy/paste is broken. XDA mobile client is really unwieldy and lagging, as that's what I'm required to use when away from my home desktop. Don't even start on discussing web mobile versions or alternative clients.

Forum rules require new readers to use SEARCH on thread. It's their problem, not mine -- also the message is quoted multiple times at the top of this page 357 (as of now). Future mod cleaning may rearrange that.

I will refrain from answering any more off-topic questions.
 
  • Like
Reactions: Nezorflame

ipdev

Recognized Contributor
Feb 14, 2016
2,547
1
5,157
Google Nexus 10
Nexus 7 (2013)
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.
With the updated permission, the arm and arm64 builds work for me. 👍
LineageOS 18.1
  • Nexus 7 (2013) [arm].
  • Poco F1 [arm64].

Cheers. :cowboy:

PS.
Will do a clean flash to test on some other devices when I have time. 🙃
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 836
    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
    36
    Is it possible to get a test version of the arm version aswell?
    I run arm/arm64 builds of pico, nano and stock for testing.

    Once they are tested a bit and seem stable, I upload them to MediaFire.
    MediaFire - Link

    Android 12 builds are in the SDK31 folder.
    The 20211218 builds include some permission updates.​

    ---

    Last week I ran SDK32 builds to test on LineageOS.
    LineageOS is merging 12.1.0_r1 into the 19.0 branch instead of creating a 19.1 branch.
    LineageOS Gerrit - Topic 12L - Link
    Edit: I just checked and see they decided to bump up to 19.1 a few days ago.​

    Note:
    Now that Android 12L is official, the release props still show as 12 not 12.1 or 12L.
    The build tag was bumped to 12.1.0 and the boot image is now SDK32 but, the kernel version is still showing as 12.0.0
    The boot image was SDK31 on the 12L preview release.​

    The only way to determine if you are running 12 or 12L is by checking the SDK level.
    SDK31 = Android 12
    SDK32 = Android 12L

    The initial 12L OpenGApps test builds were blind builds and untested.
    I did not have a device/rom to test them on. 🙃

    I few days later I was able to test them on a Pixel C, Lineage 19.0 SDK32 build.
    Since it is a tablet, it utilized the large screen layout of SDK32.​

    The 12L pico and nano builds seem to be safe.

    The 12L stock build had issues with Pixel launcher so, I would suggest not using it for now.
    Unless you are using a gapps config script to customize the install.

    Android 12L (SDK32) test builds are currently on gDrive.
    gDrive - Link


    Everyone is welcome to give them a try.

    Cheers all. :cowboy:

    Edit:
    See additional posts.
    Post # 7,316
    Post # 7,319
    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