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

Search This thread
@MastahF I never faced any issue with your gapps package . But recently from august 31 , I am noticing each and every gapps package doesn't contain latest google clock and android system webview for arm android 7.1 variant ( as I only downloaded and used that variant so ) . I don't update gapps from playstore , I just update them with the latest package . Can you please take a look at this issue ?
 

GCalzo

Senior Member
Feb 24, 2015
201
40
Reggio Emilia
will I have to create the file with linux? currently I'm creating the file with windows notepad

Better forget about Notepad, it's just a "basic editor"! For sure it's saving files with CR+LF as end-of-line!
I save the config file with only LF as end-of-line using EditPad Lite which has a handy menu entry to convert end-of-line, but many other editor can be used!
 

xanthrax

Retired Senior Moderator - Vampire
Guys !
Please keep on topic, this thread is about, as per its title, Open GApps project and not "I am working on something that I will tell you soon" or "Forum rules - explained"
Non thread`s topic related thoughts and considered as important to someone must go on private and the unpleasant posts gets reported.
thread cleaned a little
Thanks for understanding
Dan - forum moderator
 

darrylhadfield

Senior Member
Dec 31, 2008
51
11
Can any of the OpenGapps devs tell us anything about the Oreo versions?

And, for prior versions, I'm curious: Does the partition size check get done before culling already-installed apps that are going ot get replaced, or does it take that into account? It's frustrating as heck to have to use a Nano package, when most of what I want is a replacement for what's already on the ROM...
 

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,731
16,043
IDK
Can any of the OpenGapps devs tell us anything about the Oreo versions?

And, for prior versions, I'm curious: Does the partition size check get done before culling already-installed apps that are going ot get replaced, or does it take that into account? It's frustrating as heck to have to use a Nano package, when most of what I want is a replacement for what's already on the ROM...
I can't speak for @MastahF regarding Oreo - But if you watch the process when you Flash the Gapps package - You'll see that the very first part of the process is to check for available space - I haven't ever had a problem with available space - But it's logical to think that the fact that the available space check is the FIRST part of the process - It would abort the installation if there wasn't sufficient space.

As for Flashing Nano - That's the package that I always use - Since Google Assistant will not work if you Flash anything smaller than Nano.

From Down the Rabbit Hole by:
My SM-G930W8 ??
 

darrylhadfield

Senior Member
Dec 31, 2008
51
11
I can't speak for @MastahF regarding Oreo - But if you watch the process when you Flash the Gapps package - You'll see that the very first part of the process is to check for available space - I haven't ever had a problem with available space - But it's logical to think that the fact that the available space check is the FIRST part of the process - It would abort the installation if there wasn't sufficient space.

As for Flashing Nano - That's the package that I always use - Since Google Assistant will not work if you Flash anything smaller than Nano.

From Down the Rabbit Hole by:
My SM-G930W8

Yeah, my issue is that I'm putting this onto both a Galaxy Note3 and an HTC One M8 (both with LineageOS). The Nano package is about all I can get on there; the system refuses to accept anything larger.

I suppose I'll have to do some tinkering with the Aroma version.
 

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,731
16,043
IDK
Yeah, my issue is that I'm putting this onto both a Galaxy Note3 and an HTC One M8 (both with LineageOS). The Nano package is about all I can get on there; the system refuses to accept anything larger.

I suppose I'll have to do some tinkering with the Aroma version.
Yeah I've got a Note 3 as well & it's running Resurrection Remix.... But I've never had any issues with Nano and I'm not in in using any other version of Open Gapps.

From Down the Rabbit Hole by:
My SM-G930W8 ??
 

nick.ruler

Senior Member
Nov 22, 2015
53
17
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
7,375
7,391
Sydney
Also, can someone help me out with preodex? I'm on an odexed Nougat ROM (OmniROM). But even when I add preodex to gapps config, I'm unable to find any odex files in the APK folder. My Device is OnePlus 2
I think you ave experienced the same issue as me, only a few posts up https://xdaforums.com/showpost.php?p=73764735&postcount=4702 I actually checked and posted my logs which show that the flag/setting has been read.

If someone can help you, then they will be helping us both.
 

R814932

Senior Member
Feb 21, 2015
71
1
LineageOS version 14.1-20170905-unofficial-codina_sergyl.zip

I installed 14.1 LineageOS version 14.1-20170905-unofficial-codina_sergyl.zip on my Samsung Galaxy GT-i8160.

After 14.1 I installed UTF-8open_gapps-arm-7.1pico-20161207.zip

Although UTF-8open_gapps did not give an error message when it was flashed, I can see no changes to the apps available. There are no apps at all under G in the app list.

What is the correct version of gapps for me to flash?

I have internal shared storage 1.64gb used of 2.59gb leaving .95gb

Robin
 

sanguinesaintly

Senior Member
Apr 16, 2011
2,627
1,312
Redmi Note 9 Pro Max
I installed 14.1 LineageOS version 14.1-20170905-unofficial-codina_sergyl.zip on my Samsung Galaxy GT-i8160.

After 14.1 I installed UTF-8open_gapps-arm-7.1pico-20161207.zip

Although UTF-8open_gapps did not give an error message when it was flashed, I can see no changes to the apps available. There are no apps at all under G in the app list.

What is the correct version of gapps for me to flash?

I have internal shared storage 1.64gb used of 2.59gb leaving .95gb

Robin

What apps were you expecting? Pico only has enough to sync and allow you to install everything else from the playstore.
 

tetsuo55

Senior Member
Aug 20, 2007
588
229
@MNBooZe

I noticed some core gapps are not fully up to date on github.
Should I expect the apkcrawler to grab the latest version of for example configupdater?

The version on github is 7.1.1 and the version on apkmirror is 7.1.2
 
Last edited:

sevenrock

Senior Member
Nov 27, 2012
664
1,097
Motorola Defy
Moto G
Packages available both in "arm" and "all" repo

Hi,

building LineageOS14.1 32bit ROMs for personal usage I use the https://github.com/opengapps/aosp_build]aosp_build
scripts and your binary repo. During the last weeks I was wondering why Google tries to update the playstore app
(currently at 8.1.72 on my todays build) although the app is regularly updated in your github repo.

Today I found some time to investigate and found the problem, com.android.vending is present in both repos:
Current version 8.2.55: https://github.com/opengapps/arm/commits/master/priv-app/com.android.vending
Old version 8.1.72, last updated Aug 30th, 2017: https://github.com/opengapps/all/commits/master/priv-app/com.android.vending/14/240-320-480

The same is valid for priv-app/com.google.android.dialer
https://github.com/opengapps/arm/tree/master/priv-app/com.google.android.dialer
https://github.com/opengapps/all/tree/master/priv-app/com.google.android.dialer

Is keeping both versions already a bug or should the aosp_build script receive a fix to always find
the newest package version, even if the package is provided in both github projects?
 
  • Like
Reactions: tetsuo55
SDcard1/external storage not accessible

If this is the wrong place to ask - Sorry.
Devices
  • Galaxy S3 d2att - LineageOS 14.1 - Build Date 2017-09-18
  • Galaxy Tab 3 Wifi - Unofficial LineageOS 14.1 - Builder/Developer - Nels83
  • Galaxy Tab 3 Wifi - Unofficial LineageOS 14.1 - Builder/Developer - Nels83
Opengapps 1.1.2
Problems
The two tablets are, as far as I can tell, identical - (c) has 1 or 2 fewer apps than (b).
  1. on my phone (a) and tablet (b) if open the "Download Directory" setting I get a dialog box entitled Choose Storage, two horizontal bar graphs. But no other text. If I tap on either graph I get a directory listing with icons but NO text, the title space shows the current directory.
  2. if I select the external SDcard (SDcard1) in my case /storage/0343-0df1 everything appears to work.
    However, when i download the latest gapps package (usually nano) everything appears normal. Except that when the download completes Gapps app cannot find the DL, and if I check both the default DL location and the selected one the is no file to be found.​

I DL to external storage so that in the event I have to do a wipe & install of LineageOS the latest gapps will be avail.

what am I doing wrong? how do I fix the problem?
 

cyberpatrol

Member
Jul 26, 2015
19
5
Pico setup wizard keeps crashing

I've got a problem with the latest LineageOS build from 20170922 and Open Gapps pico from 20170923, 20170922 and 20170913.

I did a full wipe, put LineageOS, su and Open Gapps in the same flash queue in TWRP, in this order. After the first boot the LineageOS setup wizard and the Open Gapps setup wizard are started as usual. But when I disabled all Google services in the Open Gapps setup wizard the setup wizard crashes, and I get this pop up:
"Setup wizard was terminated
Reopen app"

I get this repeatedly when I tap on "Reopen app". Once I've got the message that the wizard was restarted too often. When I tap "Close app" the LineageOS setup wizard restarts from the beginning. So it's not possible to get the installation finished.

The Open Gapps FAQ says it should/could be a permission problem. Unfortunately at this stage I'm not able to change permissions.

I already posted this in the LineageOS thread for the LG L90. This answer indicates that it is a bug in Open Gapps pico, since the poster has the same issue with pico but not with nano.

I didn't have this issue with the LineageOS and Open Gapps pico builds from May 2017. I installed both builds from May and September the same way.

Maybe I should add that I tried to install the pico build for ARM and Android 7.1 (LineageOS 14.1).
 
Last edited:
  • Like
Reactions: odavans

imodev

Member
May 31, 2017
29
7
I've succesfully built unofficial opengapps for 8.0 arm device, but the installation stuck on "Installation complete", I have to hard reboot the device from twrp. How can I fix it?
 

retired_mnbooze

Senior Member
May 11, 2009
226
215
opengapps.org
Is keeping both versions already a bug or should the aosp_build script receive a fix to always find
the newest package version, even if the package is provided in both github projects?

I have removed the "all" variant of both the Play Store and Phone apps. Google has moved to architecture specific support for both. Thanks for pointing out the issue

---------- Post added at 08:45 AM ---------- Previous post was at 08:39 AM ----------

@MNBooZe

I noticed some core gapps are not fully up to date on github.
Should I expect the apkcrawler to grab the latest version of for example configupdater?

The version on github is 7.1.1 and the version on apkmirror is 7.1.2

The configupdater (among others like: faceunlock, feedback, gsf, and syncadapters) come from android images (I think @MastahF usually uses the Android One images due to support for lower memory devices???) Updating these are on the todo list for getting 8.0 builds up and going too.
 
Last edited:

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