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

Search This thread

drewski_1

Senior Member
Jul 20, 2012
3,828
1,602
SF Bay Area, CA
kindly
When you download and install OpenGapps package, the apps go into system partition, the same partition as typical Android ROM goes. System partition is read-only during Android runtime and is not affected by factory reset.

When you download, install or update from Playstore, they go into data partition. Data partition will be wiped on factory reset, so if you ever need to do this, you will have to re-install them from Playstore. If Playstore updates the Gapps already on system partition, they also take up space on data partition. Essentially the older copies in the system partition will be disabled in favor of the newer version in data partition.

Free space in system partition is not usable during Android runtime. Unless you prefer to go into exotic & risky measures of re-partition to shrink system partition, it is better just to use as much of system partition as possible. Periodically refreshing Gapps on system partition will free up space on data partition used by Playstore updates.

he's asking about using the Open Gapps app, not updating a GApp via Play Store.

I haven't tried it so can't say for certain, but would assume it's works similarly
. . . and flashes through TWRP

Sent from my Nexus 6P using XDA Labs
 
Last edited:

csk1jw

Senior Member
Apr 1, 2014
397
1,037
I see... I didn't try OpenGapps App, too, so can't say for sure. If it just download the same zip and one has to reboot to recovery to apply the zip, then it just saves the need for PC host.
 

caliban2

Senior Member
Mar 9, 2009
2,187
407
Periodically refreshing Gapps on system partition will free up space on data partition used by Playstore updates.

Depends on how you define "periodically".

Until incl. Android 5 it worked like this: "version number on /system is higher or the same as version number on /data, then update on /data will be deleted". Google changed that with Android 6, since then this only happens if the version on /system is higher than on /data. If it's the same version, the update on /data stays.

Meaning: Once an app has been updated via Play Store, flashing a GApps-file with the same version won't delete the version from Play Store. You'll have the same apk on /system and /data.

So if you want to free up space on /data, you'll have to disable auto-update for all apps in Play Store you want to update with OpenGApps. You can't do that for Play Store and Google Play Services, btw. I did that for some time, but to be honest, it really isn't worth the hassle - unless you're really really short on free space on /data (like devices with 8 or 16 GB storage space in total)

Edit:
Another possibility, if versions on /system and /data are the same, would be deleting updates for the app in Android settings. That way the /data-version gets deleted. But that also means the app is reset to a fresh install, so again -> hassle...
 
Last edited:
  • Like
Reactions: GCalzo and Alsidsds
D

Deleted member 2044343

Guest
Edit:
Another possibility, if versions on /system and /data are the same, would be deleting updates for the app in Android settings. That way the /data-version gets deleted. But that also means the app is reset to a fresh install, so again -> hassle...
In this casa the app isn't reset to a fresh install, app's data won't be deleted.
 

poxer1933

Member
Nov 18, 2015
22
10
Minsk
Problems with the graphical interface of the Google Assistant, with the locked screen works perfectly, but with the unlocked screen it just loads the voice but there is not any graphical interface. lenovo a6010 with a Lollipop custom rom.
 

ApoelEllhnwn

Senior Member
Aug 1, 2016
165
31
Nicosia, Cyprus
I can't sing in to my account with​ latest update (Google play services FC every time) . Also I have problem with hotword, package installer, and pixel icons.
I have Nexus 6p and i use aroma-arm64-7.1
 

rajatgupta1998

Senior Member
Jan 12, 2015
1,126
3,509
25
Shimla
Moto G4 Plus
OnePlus 6
I can't sing in to my account with​ latest update (Google play services FC every time) . Also I have problem with hotword, package installer, and pixel icons.
I have Nexus 6p and i use aroma-arm64-7.1
What ROM are you using? Also are you dirty flashing the GApps? My advice will be to do a clean flash of the ROM and then flash GApps without rebooting to System.
 

Northtech

New member
Oct 29, 2010
2
2
openGAPPS PICO/ARM64/6.0 (from 4 March 2017 - 22 March 2017 Size: 75.78 MiB) induce bootloop in Xiaomi Redmi Note 3 Pro (Qualcomm).
In previously versions (PICO/ARM64/6.0) size been ~100 MiB and all was normal.

logs in twrp: not mount /system as before versions, only mount /persist.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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