• 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

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?
 

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..
 
Pixel 3a LineageOS 18.1 + open_gapps-arm64 Bootloop

@Nezorflame - FWIW two Pixel 3a users reported bootloop with Open GApps but working fine with MindTheGapps in the LineageOS subreddit here:

I have tried not restarting at all between installations, restarting to recovery, and booting completely before installing, and they all have the same problem. I'm going absolutely mad. What's going on? How can I fix this?

Pixel 3a Lineage OS 18.1-20211109-nightly open_gapps-arm64-11.0-micro-20211109

To which a LineageOS team member replied:

OpenGApps are hilariously broken, as they are every second week. Wipe the system and use MindTheGapps.

This is what happens when publishing untested builds. :(
***
 
  • Like
Reactions: Nezorflame
Moto G6 Plus LineageOS 18.1 + open_gapps-arm64 Bootloop "Can't load android system"

@Nezorflame - FWIW a Moto G6 Plus user (A/B device) reported failed to boot with open_gapps-arm64-11.0-nano-20211111.zip but working fine with MindTheGapps in the LineageOS subreddit here:

"After rebooting, I get the lineageos loading symbol, it loads for ages, before rebooting and going back to recovery. ...Can't load android system, your data may be corrupt."

Pixel 3a LineageOS 18.1 + open_gapps-arm64 Bootloop

@Nezorflame - FWIW two Pixel 3a users reported bootloop with Open GApps but working fine with MindTheGapps in the LineageOS subreddit here:

To which a LineageOS team member replied:

This is what happens when publishing untested builds. :(
***
 
  • Like
Reactions: Nezorflame
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.
***
 

robin0800

Senior Member
Jan 22, 2012
483
219
68
Brighton
I am on android 10 and both 12th and 13th still crash on installation screen. Did your fix trickle down to 10 or is this a new problem?
 
I am on android 10 and both 12th and 13th still crash on installation screen.

What do you mean by "installation screen"?

Is that in recovery or when booting to system or in the Setup wizard?

If it's in the Setup wizard, it's while doing what?

Device model? ROM? GApps package? Clean install of update?

Did you try Open GApps build 2021-11-05?
***
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Re: OnePlus One - Open GApps Pico Insufficient Space - GogleTTS

    Sure, see attached. Note: this is the log I get when having installed the Jan. 10 version of OpenGApps pico and then trying to upgrade to the Jan. 15 version.

    Would you also need the file open_gapps_debug_logs.tar.gz?

    Thanks for the log & infos. :cool: 👍

    No need for the "open_gapps_debug_logs.tar.gz" in this case.

    So if I understand it correctly, then there's no harm in skipping the googletts package during installation of OpenGApps. And I can still install and update the application via the Play Store -- right?

    Yes but there is no point in doing it in your case because updates to your open_gapps-arm-11.0-pico-20220110 package, including for GoogleTTS, will be downloaded to the /data/ partition which does not have the same size limitation as the system partition where the ROM + Open GApps was installed.

    That would be helpful for a new clean install.

    I never understood why GoogleTTS is included in Pico which is the Open GApps minimal installation package. ¯\_(ツ)_/¯

    That app is not essential & can be installed later @ any time by the user if he wants it.
    ***
    2
    Also, builds are still paused since 20211221? Intentional, or something broke and nobody noticed yet?

    I noticed and was glad that the crazy machine churning out daily untested builds was finally stopped.

    Better 1 good build a month and stick with it if no issues are reported IMO.
    ***
    1
    look at #7219

    OpenGApps UNOFFICIAL - MediaFire - Link
    The Android 12 versions are in the SDK31 folder.

    But be aware that this is a REAL EARLY release.
    I would not take them for any device in production
    1

    setupwizarddefault-x86_64 is accessing a deleted field isCarrierAp of apex package android.net.wifi​


    setupwizarddefault-x86_64 is accessing a deleted field isCarrierAp of android.net.wifi.ScanResult and crashes. Since this package (com.android.wifi) is apex so it will be updated by Google automatically and EVERY x86_64 Android 11 device with openGApps installed will crash (bootloop) by this issue after com.android.wifi is updated by oepnGApps itself.
    FYI, This field is removed in this commit: https://cs.android.com/android/_/an...fi/+/c50556db869a1caefab533c64ab640a6ba1ae934

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.google.android.setupwizard.SetupWizardApplication: java.lang.RuntimeException: java.lang.NoSuchFieldException: No field isCarrierAp in class Landroid/net/wifi/ScanResult; (declaration of 'android.net.wifi.ScanResult' appears in /apex/com.android.wifi/javalib/framework-wifi.jar)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6724)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at android.app.ActivityThread.access$1300(ActivityThread.java:237)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7664)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: Caused by: java.lang.RuntimeException: java.lang.NoSuchFieldException: No field isCarrierAp in class Landroid/net/wifi/ScanResult; (declaration of 'android.net.wifi.ScanResult' appears in /apex/com.android.wifi/javalib/framework-wifi.jar)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at mm.a(PG:318)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at lr.l(PG:292)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at lr.a(PG:206)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at lr.<init>(PG:112)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at mc.a(PG:141)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at mc.d(PG:50)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at mc.b(PG:79)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at ate.a(PG:36)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at aqz.a(PG:31)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at com.google.android.setupwizard.SetupWizardApplication.onCreate(PG:11)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6719)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: ... 8 more

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: Caused by: java.lang.NoSuchFieldException: No field isCarrierAp in class Landroid/net/wifi/ScanResult; (declaration of 'android.net.wifi.ScanResult' appears in /apex/com.android.wifi/javalib/framework-wifi.jar)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at java.lang.Class.getDeclaredField(Native Method)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: at mm.a(PG:316)

    11-25 17:52:43.284 14145 14145 E AndroidRuntime: ... 19 more
    1
    Is it about "AOSP on IA Emulator" on a computer?
    Yes, in the android emulator, with a system-image as provided by the SDK Manager, from google (original post edited as per your request)
  • 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.