• 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
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
13
12
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
13
12
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
1,612
1
2,159
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:

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,862
33,605
Halifax
GT-i9250
Google Nexus 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.
 
Last edited:

Simon1511

Recognized Developer
Hi, I'm facing various issues with Gapps on my Galaxy A52:
Installing any of the arm64 11.0 Gapps packages does not succeed due to not enough storage space being available. This is not true since all dynamic partitions (system, vendor, product, odm) have each 500MB of free space left.

Removing the space check from the OpenGapps installer will make them install successfully, but after booting the device will soft reboot infinitely. This reboot issue wasn't actually Gapps related, sorry. So the only issue that remains is that openGapps is unable to calculate the correct space on dynamic partitions.
Logcat and OpenGapps logs are attached.

Is that a known issue and if yes, is there a workaround?
 

Attachments

  • open_gapps_debug_logs.tar.gz
    143.4 KB · Views: 5
  • open_gapps_log.txt
    4.2 KB · Views: 5
Last edited:

Nezorflame

Senior Member
Hi, I'm facing various issues with Gapps on my Galaxy A52:
Installing any of the arm64 11.0 Gapps packages does not succeed due to not enough storage space being available. This is not true since all dynamic partitions (system, vendor, product, odm) have each 500MB of free space left.

Removing the space check from the OpenGapps installer will make them install successfully, but after booting the device will soft reboot infinitely. This reboot issue wasn't actually Gapps related, sorry. So the only issue that remains is that openGapps is unable to calculate the correct space on dynamic partitions.
Logcat and OpenGapps logs are attached.

Is that a known issue and if yes, is there a workaround?

Hi! No, it's not known yet.
I'll check that, thanks.
 
  • Like
Reactions: ipdev and Simon1511

ALTracer

Member
May 5, 2018
13
12
Cheboksary
4pda.ru
Permissions strike again, huh
I flashed 20211008 build (downloaded via OpenGapps App from SourceForge), seems to work fine. At least it booted.

Build open_gapps-arm64-11.0-super-20211020 (with gapps-config)
doesn't boot system
Found this under `/data/system/dropbox/system_server_crash*.txt`
Java:
bash-5.0 ~ > cat /data/system/dropbox/system_server_crash\@1634836516145.txt         
Process: system_server
Build: google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys

java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.projection.gearhead (/system/app/AndroidAutoPrebuilt): android.permission.UPDATE_APP_OPS_STATS}
        at com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:4703)
        at com.android.server.pm.permission.PermissionManagerService.access$500(PermissionManagerService.java:178)
        at com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.systemReady(PermissionManagerService.java:4786)
        at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21688)
        at com.android.server.SystemServer.startOtherServices(SystemServer.java:2210)
        at com.android.server.SystemServer.run(SystemServer.java:601)
        at com.android.server.SystemServer.main(SystemServer.java:417)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)

Couldn't connect with adb this time.
 
  • Like
Reactions: Nezorflame

Typhoon_Master

Senior Member
Jun 5, 2014
114
13
Hi,

when installing open_gapps-arm-6.0-pico-20211021.zip on my tablet, the assistant after the first boot

(A) forces me to login to a wifi. the "SKIP >" button is greyd out
(B) after logging in to a wifi it goes to "Checking connection... This can take a while" but it stucks there forever. Again the "SKIP >" Button is greyed out.

So flashing gapps makes my device unuseable. :-(

Is there a way to fix this?

// EDIT: REBOOT FIXED IT!

IMG_20211022_180844.jpg
 
Last edited:
  • Like
Reactions: curiousrom

Magendanz

Senior Member
Mar 25, 2008
828
795
Issaquah, WA
www.Vote4Chad.com
I'm so excited to finally have Android 11 stock builds, but am seeing a WebView problem on the Galaxy Tab A 8.0 (SM-T290, ARM64) that seems related to issues #820 and #804. Setup cannot progress past attempting Google Play Services sign-in and skipping setup results in the same problem when logging into the Play Store or Chrome, showing only a black screen and the navigation bar. If I check WebView Implementation in Developer Options, it shows None.

Can anyone recommend a workaround for this? Previously, we just needed to match versions for Chrome and Trichrome, but they both seem to currently be 81.0.4044.138.
 
Last edited:

Feimitsu

Senior Member
Aug 6, 2013
90
17
Budapest
27/28 Oct version of Gapps Stock for ARM Android 11 seems to be broken (missing play services notification at device start). It's also some 80MB smaller than the version released on the 21 Oct.
 

Daikath

New member
Oct 29, 2021
4
2
I tried to install a fresh OS onto my Samsung Galaxy S5 Neo. I did it before and it worked fine for quite a while. I then install the full package of Gapps before booting. However, it would get stuck on the starting screen looking for updates, without an option to skip it. Also messages would appear that random google apps suddenly stopped working.

I then formatted my system, just installed lineageOS and it worked fine.. It just booted into the OS and I could call and surf the web.

I went back and just installed just the pico version. Now it's also stuck at the looking for updates part without the option to skip it. I did get the message that the system UI stopped working.

I have tried older packages of gapps and lineageOS, but after like three tries I kept getting the same errors. I came back to the recent builds with just pico, yet it still wouldn't get passed the looking for updates screen.

I have used the recovery image, lineage-17.1-20211024-recovery-s5neolte.img with the LineageOS build of

I then used the Gapps build for ARM, Android 10, pico package, open_gapps-arm-10.0-pico-20211028.zip

Is there more information which would be useful? Is there something I can do other than trying out older and older builds? Thanks in advance for any help.
 
  • Like
Reactions: curiousrom

Top Liked Posts

  • 3
    Bootloop here with open_gapps-arm64-11.0-nano-20211203.zip

    Went back to 20211125 that works
    2
    Bootloop here with open_gapps-arm64-11.0-nano-20211203.zip

    Went back to 20211125 that works

    Bootloop thrown back to recovery reported on clean install of Galaxy S III Neo (Samsung Camera) (s3ve3gjv) + LineageOS 18.1 + open_gapps-arm-11.0-nano-20211203 here.
    ***

    Edit: @Nezorflame added build date as reported by the user.
    **
    1
    Bootloop here with open_gapps-arm64-11.0-nano-20211203.zip

    Went back to 20211125 that works
    In before curiousrom! 😆

    Reported it to the team. 👍

    Any in between those working?

    Edit: Also some logs of the bootloop and GApps install would be nice to help narrow it down.
    1
    Bootloop to twrp to be precise
    Haven't tried anything in between
    I can redo install to get you a last_kmsg.log and install.log. Anything else you need ?
    Attached are the gapps install logs.
    Can't find the previous kernel log... Don't have /proc/last_kmsg or /sys/fs/pstore/console-ramoops
  • 5
    Hi all. :)

    Long story short.

    Looking for opinions on reversing the order of (or improving) the abi check.
    OpenGApps - Github - Installer Script Line 1665 - Link

    Reversing it (checking for cpu.abi first) should fix the wrong architecture being found on some devices.
    Code:
    device_architecture="$(get_prop "ro.product.cpu.abi")";
      if [[ -z $device_architecture ]]; then
        device_architecture="$(get_prop "ro.product.cpu.abilist")";
      fi;
    I prefer looking for the newer prop first but, maybe this time it would be better looking for the older value first?

    I have not tried it yet but, it should fix the architecture mismatch I recently ran into on my Poco F1.
    The custom rom (used ro.product.cpu.abi) did not set ro.product.cpu.abilist in any of the prop files so OpenGApps set it from TWRP's default.prop.
    Not sure if this affect other devices or not. :unsure:
    First time I ran into it and I have wiped, formatted and flashed my Poco F1 many times.
    Not sure why this only showed up now.


    I am using the official TWRP for the Device from twrp.me
    TWRP for Xiaomi Pocophone F1 - twrp.me - WebSite - Link
    Code:
    beryllium:/ # for i in $(find / -name 'default.prop' 2> /dev/null); do echo $i && cat $i | grep 'cpu.abi'; done;
    /default.prop
    # ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
    # use ro.product.cpu.abilist instead.
    ro.product.cpu.abi=arm64-v8a
    ro.product.cpu.abilist=armeabi-v7a,armeabi
    ro.product.cpu.abilist32=armeabi-v7a,armeabi
    ro.product.cpu.abilist64=
    beryllium:/ #

    Thoughts on including one of these values. 🙃
    • ro.vendor.product.cpu.abilist
    • ro.odm.product.cpu.abilist
    • ro.system.product.cpu.abilist
    Code:
    ro.vendor.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
    ro.odm.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
    ro.system.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi

    Cheers all. :cowboy:
    @osm0sis @mfonville WDYT?
    I personally agree with this (and this is something @Nikhil suggested as well), so if there are no objections, might add this check.

    BTW @ipdev feel free to post this kind of feedback/discussion on our Github as well, might be easier to communicate there.

    Update: see https://github.com/opengapps/opengapps/pull/942 with this change.
    5
    The issue is fixed, new builds should be fine.

    Will return with the news regarding what @curiousrom said soon (tm).
    4
    In the meantime, here's a quick test A12 nano build for ARM64 for those who wants a taste :)
    Initial setup worked for me, but might have different issues I haven't found yet.

    3
    Thanks, builds have been pulled, investigating the issue.
    3
    Broken Open GApps Builds Again!

    Thanks, builds have been pulled, investigating the issue.

    The era of publishing untested rolling releases of Open GApps is over.

    Google is moving the goal posts all the time and that breaks stuff.

    Better a monthly thoroughly tested release instead.

    That's better for the reputation of Open GApps & also for the users instead of wasting their time with broken builds.
    ***
  • 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.