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

Search This thread

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
16,767
40,432
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:
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: 9
  • open_gapps_log.txt
    4.2 KB · Views: 7
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
15
19
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
132
18
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
987
1,071
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
91
19
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

Nezorflame

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

Hi! Does logcat show anything of value (error-wise)?
 

Nezorflame

Senior Member
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.
Logcat output during the boot.

If it doesn't connect to phone, you can try editing build.prop and default.prop from your recovery (or edit them on PC and push to system):

build.prop (replace the existing lines if they're already there):
Code:
# debug
ro.default_usb_mode=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb

default.prop (replace the existing lines if they're already there):
Code:
# debug
ro.adb.secure=0
ro.secure=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb

this will enable debugging to gather logcat, later you can remove/restore these files (or reflash the ROM)
 
  • Like
Reactions: Daikath

kumardaksh

New member
Oct 16, 2021
4
0
Does Opengapps now supports split APKs?
Also do now packages comes with updated apps or older version like Chrome v81?
 

Magendanz

Senior Member
Mar 25, 2008
987
1,071
Issaquah, WA
www.Vote4Chad.com
Hi! Does logcat show anything of value (error-wise)?
This seems like the most relevant error:

WebViewFactory: Chromium WebView package does not exist WebViewFactory: android.webkit.WebViewFactory$MissingWebViewPackageException: Failed to load WebView provider: No WebView installed
 

Attachments

  • logcat.zip
    139 KB · Views: 31
  • Like
Reactions: Nezorflame

Daikath

New member
Oct 29, 2021
4
2
Logcat output during the boot.

If it doesn't connect to phone, you can try editing build.prop and default.prop from your recovery (or edit them on PC and push to system):

Hey thanks for replying. I tried to unpack the recovery image rom to alter it so be able to get through an error log. But I cannot get to that point sadly,.

https://wiki.lineageos.org/devices/s5neolte/install
I then use the unpack method from

I get these error messages and sadly no files to edit in the manner you described,

I'm being very stubborn and uploading a new OS onto an old phone rather than buying a new one. But if I can still save it, that would be great.It worked fine for quite a while until it wouldn't boot after an update. Now I'm just trying to get a working install agauin.
 
  • Like
Reactions: curiousrom

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.

Jusrt in case anyone else had this problem... I flashed a new recovery image, the latest twrp again (Where I had used the LineageOS rboot img). I thought I wiped my system and just installed LineageOS, but when I booted just to check.. Google pico was still on it and thankfully it did boot this time..

I'm just grateful it boots again, I'm not ging to touch it to get a logcat or anything..
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Is there anything new to say?
    OpenGApps is still pretty dead atm, which is very sad...
    I think it's safe to assume that OpenGApps is dead, it's well beyond the point of simply being temporarily on hold. The devs havent posted in many months, not even to say that it's just on hiatus and will return in the future. And besides that, the last OpenGApps releases are for Android 11, we are now on Android 14, and 15 is coming soon. Even if it comes back, they will have way too much catching up to do for the project to be manageable. There are a few other GApps providers out there that you can try, I'd move on. OpenGApps always was my fave, but I've managed without them.
    4
    What he said. There are other GApps providers like MindTheGapps and NikGapps (which is the one I use) that have taken up the mantle from OpenGApps. NikGapps, in fact, still has releases going all the way back to Android 9 (Pie), and like OpenGApps, provides packages from "core" to "full" depending on how much GApps you need. MindTheGapps, unfortunately, stops at Android 13, so if you're using 14, you're SOL there.
    MindTheGApps has Android 14 builds. I'm using it on an A14 LineageOS gsi ROM right now. The only problem with MTG, is that it isnt customizable. The zips are take it or leave it, you're installing all the components in the zip, or not at all. There is only 1 version (all the zips are the same, excluding hardware/Android version-specific details) which is essentially 1 size fits all. But most other GApps providers have customization in that you can choose which parts you do/don't want. But MTG is also very minimal, it just includes the core GApps components and little to no bloat. So it's not a big deal to me. I don't need all the extra stuff, just Play Services/Play Store/calendar and contacts syncing, not much else.

    MTG for Android 14:
    2
    Is there anything new to say?
    OpenGApps is still pretty dead atm, which is very sad...

    I think it's safe to assume that OpenGApps is dead, it's well beyond the point of simply being temporarily on hold. The devs havent posted in many months, not even to say that it's just on hiatus and will return in the future. And besides that, the last OpenGApps releases are for Android 11, we are now on Android 14, and 15 is coming soon. Even if it comes back, they will have way too much catching up to do for the project to be manageable. There are a few other GApps providers out there that you can try, I'd move on. OpenGApps always was my fave, but I've managed without them.

    What he said. There are other GApps providers like MindTheGapps and NikGapps (which is the one I use) that have taken up the mantle from OpenGApps. NikGapps, in fact, still has releases going all the way back to Android 9 (Pie), and like OpenGApps, provides packages from "core" to "full" depending on how much GApps you need. MindTheGapps, unfortunately, stops at Android 13, so if you're using 14, you're SOL there.
    1
    Is there anything new to say?
    OpenGApps is still pretty dead atm, which is very sad...
  • 837
    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