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

Search This thread

ipdev

Recognized Contributor
  • Feb 14, 2016
    1,367
    1
    1,536
    Google Nexus 10
    Nexus 7 (2013)
    Since it is the newest version, it is impossible to get it updated. Sideloading the newest version with the
    Code:
    adb install -r -d
    command also does not work. But when I did clean flash and tried installing it directly from Google Play Store on, yes it does work.

    EDIT: Meaning not installing Drive from OpenGapps packages
    This error seems to be growing on all Android 11 gapps builds, not just OpenGApps.
    When some apps are installed by third-party (Not installed by PlayStore).

    YouTube is complete loss.
    Google Maps gives the error but, seems to work if you select it from recent. Gives the error again after you close and reopen Maps.
    YT Music and Google Drive worked a few weeks ago when I was looking for apps that give this error.

    Not sure how/why it is corrected when installed from PlayStore?
    If I remember correctly there was an error in the log when installing YouTube from PlayStore but, I did not see how it was corrected.
    Edit: How it was corrected by PlayStore when installing.


    Cheers. :cowboy:
     
    Last edited:
    • Like
    Reactions: LilBlinx

    LilBlinx

    Recognized Contributor
    Jun 17, 2012
    2,033
    5,576
    Skopje
    This error seems to be growing on all Android 11 gapps builds, not just OpenGApps.
    When some apps are installed by third-party (Not installed by PlayStore).

    YouTube is complete loss.
    Google Maps gives the error but, seems to work if you select it from recent. Gives the error again after you close and reopen Maps.
    YT Music and Google Drive worked a few weeks ago when I was looking for apps that give this error.

    Not sure how/why it is corrected when installed from PlayStore?
    If I remember correctly there was an error in the log when installing YouTube from PlayStore but, I did not see how it was corrected.
    Edit: How it was corrected by PlayStore when installing.


    Cheers. :cowboy:
    True indeed, Maps is erroring out here too but it works somehow. I believe that there are more apps that have the same behavior.

    EDIT: Google Docs spits out warning about not being installed from the Play Store too
     
    • Like
    Reactions: ipdev

    hzr34

    Senior Member
    Jan 5, 2012
    452
    29
    Istanbul
    I have a problem with android auto in open gapps aroma installer linage 17 android 10. Not working also I am not able access aa developer settings. Is anyone have a idea. Btw uninstall and clean install servel times
     
    • Like
    Reactions: jllmoe

    jllmoe

    Member
    Dec 27, 2017
    30
    1
    I have a problem with android auto in open gapps aroma installer linage 17 android 10. Not working also I am not able access aa developer settings. Is anyone have a idea. Btw uninstall and clean install servel times

    Just installed Lineage OS 18.1 and latest BitGapps, I have to go back a couple of versions to make Google Maps work, and have to go back many versions (May 2020) to make Android Auto not flash closing, BUT after Android Auto is started it says "update needed" and I have to click Accept or Exit, if I click Accept, it will be updated to the latest version and flash close, if I choose Exit, nothing will happen. So I am still unable to use Android Auto.

    Personally I do not think this is a GApps issue, because I was able to install many apps including these two from the play store, I have no issue with other apps. I have used the GPS Status and Tool app to reset the GPS data, and cache clean tens of times, the only thing made some improvement was to roll back the version of the app, but this so far still did not resolve the issue for Android Auto. Any suggestion on the Android Auto fix will be highly appreciated.
     
    • Like
    Reactions: hzr34

    giddie

    Senior Member
    Apr 20, 2012
    69
    32
    Birmingham
    I'm trying to install LineageOS 17.1 with GApps 10.0 "stock" on my OnePlus 5T (wiped /data) and have run into issues. It seems the boot process freezes once the OnePlus boot logo is displayed, before the LineageOS boot animation starts. The really interesting thing is that it books OK with "pico". Any idea what may be present in "stock" that could be causing issues?

    Unfortunately I'm still unable to boot Open GApps 10.0 Stock on OnePlus 5T with Lineage 17.1 Official, even after factory reset. Nano boots OK. Is there anything I can do?
     
    • Like
    Reactions: curiousrom

    KSLevel11

    Senior Member
    Jun 6, 2011
    540
    69
    Hello!

    I had to reinstall OS on my phone. So I went back to stock and then installed LOS 17.1 for Redmi Note 5. Then I installed newest GApps (nano version), wiped cache and dalvik and I can't get through first configuration process - after adding fingerprint, there is an info about Google Assistant and examples of use. The only way to proceed is clickin "next" and then there is info about setting "Ok, Google" voice match. There is "no, thanks" option, but after clicking it, configuration process gets back to adding fingerprint. I tried installing older GApps but with no luck.



    Any suggestions?

    Thanks in advance.
     
    • Like
    Reactions: curiousrom

    Ahmad04

    Senior Member
    Feb 4, 2017
    340
    47
    21
    PATNA
    Anyone having setup wizard just turning straight black issue, is it a crash? Having this issue in last 4-5 builds, clean flashed. There is no navigation bar too.:(
     

    Nezorflame

    Senior Member
  • Sep 7, 2009
    919
    2,571
    Moscow
    nezorfla.me
    Google Nexus 5
    OnePlus 3
    Hello!

    I had to reinstall OS on my phone. So I went back to stock and then installed LOS 17.1 for Redmi Note 5. Then I installed newest GApps (nano version), wiped cache and dalvik and I can't get through first configuration process - after adding fingerprint, there is an info about Google Assistant and examples of use. The only way to proceed is clickin "next" and then there is info about setting "Ok, Google" voice match. There is "no, thanks" option, but after clicking it, configuration process gets back to adding fingerprint. I tried installing older GApps but with no luck.



    Any suggestions?

    Thanks in advance.

    Hi, I've had previous reports on this issue, but it should've been fixed.
    Please grab logcat, reproduce the issue during it and send me the ouput.
    Also send me the debug log file (it's an archive should be present in the same folder where your GApps zip file is during the install).
     
    • Like
    Reactions: mauam

    Nezorflame

    Senior Member
  • Sep 7, 2009
    919
    2,571
    Moscow
    nezorfla.me
    Google Nexus 5
    OnePlus 3
    Anyone having setup wizard just turning straight black issue, is it a crash? Having this issue in last 4-5 builds, clean flashed. There is no navigation bar too.:(

    Please also grab logcat, and add more info about your issue (Android version, GApps package variant, architecture), and send me the debug log file (it's an archive should be present in the same folder where your GApps zip file is during the install).
     
    • Like
    Reactions: mauam

    Nezorflame

    Senior Member
  • Sep 7, 2009
    919
    2,571
    Moscow
    nezorfla.me
    Google Nexus 5
    OnePlus 3
    New builds, including the fixes from #905 (this time without the fixes from #902 and #903) are up: ARM | ARM64

    There is a new PlayStoreOverlay specific for R to allow Google apps to be installed from non-Play Store locations (thanks to @coin3x and @r6680jc from the Telegram discussion group!).

    Also we should now have Chrome and Webview working properly due to the return of the SDK29+ verions of these apps.

    EDIT: and they're up. Enjoy, and report any issues you've encountered.
     
    Last edited:

    Vinnom

    Senior Member
    Jun 21, 2012
    1,705
    1,143
    Campinas
    Xiaomi Poco F1
    I've just tried to install Open GApps 20210130. My setup:

    Device: beryllium
    ROM: awaken 1.5.2

    Issue: I couldn't restore my data. In Setup Wizard, it just go through it to adding lockscreen security and fingerprint. If you go all the steps and try to restore data later, the app crashes. I've tried with almost all OpenGApps versions (excluding super) w/o a boot in between ROM and GApps and I've tried booting first and then installing the GApps, neither worked.

    I've took a logcat with the full version but the issue happened with all of them.
     

    Attachments

    • gapps-full-20210130.txt
      803.3 KB · Views: 5
    • Device_Space_After.txt
      2.5 KB · Views: 1
    • gapps-config_processed.txt
      562 bytes · Views: 2
    • gapps-remove_revised.txt
      4 KB · Views: 1
    • open_gapps_log.txt
      6.6 KB · Views: 3
    • System_Files_Before.txt
      534.1 KB · Views: 1
    • Device_Space_Before.txt
      2.5 KB · Views: 1
    • gapps-config_original.txt
      3.6 KB · Views: 1
    • System_Files_After.txt
      554.4 KB · Views: 1
    • Like
    Reactions: Meowdib
    Black Screen during Setup Wizard - Android 10

    Anyone having setup wizard just turning straight black issue, is it a crash? Having this issue in last 4-5 builds, clean flashed. There is no navigation bar too.
    Please also grab logcat, and add more info about your issue (Android version, GApps package variant, architecture), and send me the debug log file (it's an archive should be present in the same folder where your GApps zip file is during the install).

    An other user reported the same issue on official LineageOS 17.1 in the Lineage subreddit here:

    "Blank screen during setup wizard using stock Open GApps ...Oneplus 7T Pro: lineage-17.1-20210126-nightly-hotdog-signed.zip open_gapps-arm64-10.0-stock-20210127.zip ...When I flash full Open GApps instead, everything is working fine."

    If you sideloaded Open GApps it automatically creates a log named open_gapps_log.txt in the internal sdcard.
    ***
     
    Last edited:
    • Like
    Reactions: Naxiz

    Naxiz

    Senior Member
    Jan 12, 2012
    66
    39
    Groningen
    ict-crew.nl
    Hey! Thanks @curiousrom, this is exactly my problem!

    So I installed lineage-17.1-20210126-nightly-hotdog-signed.zip and open_gapps-arm64-10.0-stock-20210127.zip, nothing else. Now the setup wizard just shows a black screen after the "checking info" step.

    I've gathered some more info: if I skip the setup wizard and go to developer options, there are no WebView implementations available. I tried using a `gapps-config.txt` file to keep the stock WebView implementation, but that doesn't help. Using the full GApps package everything is working as it should.

    The GApps log is attached to my post! :) I couldn't add the debug log so it is here on Google Drive: https://drive.google.com/file/d/1ezcfKn10sia5LVO_XNk732vsZ3mmbgeR/view

    New builds, including the fixes from #905 (this time without the fixes from #902 and #903) are up: ARM | ARM64

    There is a new PlayStoreOverlay specific for R to allow Google apps to be installed from non-Play Store locations (thanks to @coin3x and @r6680jc from the Telegram discussion group!).

    Also we should now have Chrome and Webview working properly due to the return of the SDK29+ verions of these apps.

    EDIT: and they're up. Enjoy, and report any issues you've encountered.

    Could this be related to my issue? I would love to try the test build, but it only seems to be for Android 11. Will this fix also become available for Android 10?

    --- EDIT ---

    Using the following gapps-config it's working!

    Code:
    Exclude
    
    WebViewGoogle
    WebViewStub
    
    +WebViewStock
     

    Attachments

    • open_gapps_log.txt
      7.1 KB · Views: 12
    Last edited:
    • Like
    Reactions: curiousrom

    Vinnom

    Senior Member
    Jun 21, 2012
    1,705
    1,143
    Campinas
    Xiaomi Poco F1
    recovery.log is notably missing, can you upload it as well?
    sure!

    Sorry the delay, as I wasn't quoted and new xda isn't as good as the old one to follow participated threads, I didn't see your request.

    PS: I've tried to upload it together with the others, but I think 9 is the maximum and I didn't upload it anywhere - if so I could share the link.

    EDIT: for some reason, xda is refusing to updload it, so I saved it into this deldog
     
    • Like
    Reactions: osm0sis

    armars

    Senior Member
    Jul 24, 2011
    53
    2
    since for arm 6.0 it left only one mirror in San Diego

    downloading arm 6.0 packages are impossible :(

    every single day there are network problems so download crashes

    also resuming is not possible :(
    it is not only my problem
    I asked my friends in different countries to try
    result is same :(
    even downloading from LA has same results

    it is maybe 60 or more days


    every time I report here in forum


    but problem still exists


    file is aroma version arm 6.0
     
    • Like
    Reactions: artiG

    Top Liked Posts

    • There are no posts matching your filters.
    • 2
      Anyone know the protocol for updating from the test version of Android 11 GApps to the official release when that finally gets added? Would this require re-flashing your current ROM or wiping data? Or should you just be able to adb sideload on top of your current working ROM and GApps?
      Just sideload the Gapps should be enough.
      2
      Hi,

      Thanks for the work ! Do you have an idea when the "arm" version could be out ?

      Thk.
      Stop asking about an ETA for a release in general. It will be released when it's ready to be released.
      1
      Will the next OGApps test builds for A11 include again all packages like the ones released in january? 🤔
      That would be great. ✌️
    • 829
      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.