• 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
Yeah they're busy with their own stuff. You on the other hand are supposed to be a Recognized Contributor; maybe contribute something more than ****ing trolling to this thread for once.
You are the one avoiding the issue.

If you look at my posting history you will see that I'm a user support type of guy & not a dev.

I am fed up with helping freaked out users who are flashing a custom ROM + Open GApps for the first time and getting caught in a bootloop thinking they messed up & broke their device or something.

That's not counting the thousands of hours lost by users if you add them up.
***
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,912
33,756
Halifax
GT-i9250
Google Nexus 4
You are the one avoiding the issue.

If you look at my posting history you will see that I'm a user support type of guy & not a dev.

I am fed up with helping freaked out users who are flashing a custom ROM + Open GApps for the first time and getting caught in a bootloop thinking they messed up & broke their device or something.

That's not counting the thousands of hours lost by users if you add them up.

If you're fed up then learn how to read logs, do basic debugging and help fix issues, that's a central part of user support.

And if you're really fed up then maybe your user support isn't what Open GApps needs. It needs developers/contributors who aren't ****ing toxic and burnt out. If you're not capable of learning how to help directly then maybe you should try to recruit more people who can.
 
  • Like
Reactions: sieghartRM
If you're fed up then learn how to read logs, do basic debugging and help fix issues, that's a central part of user support.

Thanks for providing very good troubleshooting info & linking to your recovery.log. :cool: 👍

You did everything right except that in the log it says "ro.boot.bootloader=G900FXXU1ANC9" and that bootloader is from Android 4.4.2 as you can see here

Samsung vendor's firmware 6.0.1 is required for LineageOS 18.1 as mentioned in the post #1....
 

ALTracer

Member
May 5, 2018
15
19
Cheboksary
4pda.ru
Multiply this by two to eight builds per Android level (most have at least eight).
Are you perhaps missing the point of incremental packages? pico<nano<micro<mini<full<super, so testing `super` oughtta catch any bugs in subsets (stock and aroma are a different beast, judging by installer script).

Running 20211130 build now, seems to be working.

Whoa, you really pulled all the 20211204 builds? Pico was not affected by digitalwellbeing as it doesn't contain that app, and nano+ are/should still be runnable with a workaround gapps-config.txt of `Exclude \n Wellbeing`...

Saw some juicy gitlab commits on 20211206, will wait for 20211207 build to test in the next 24h. People soon flashing Google December Security Patch updates might want to grab a fresh gapps build while they're at it.

I personally see OpenGapps as a powerful project supporting a wide variety of SDK levels and architectures, employing modern VCS, CI/CD, lzip (you're cool, guys!) and customizable with text input (gapps-config-santoni.txt). No other gapps provider ever stood near (NikGapps, MindTheGapps, etc.). If your gitlab repos are open for contributions, I might consider sending simple merge requests when appropriate. I learned some shell and makefile, but my python-fu is not strong enough. Github issues maybe require moderation.
 
...People soon flashing Google December Security Patch updates might want to grab a fresh gapps build while they're at it...

That's not necessary at all.

Play Store, Play Services & libraries automatically update themselves in the background regardless of the user's update settings in Play Store.

When Google will feel that they need an update it will do it automatically.

As for the apps included in a GApps package you can either not update, manually update or chose automatically update in Play Store's settings.
***
 

ipdev

Recognized Contributor
Feb 14, 2016
1,656
1
2,272
Google Nexus 10
Nexus 7 (2013)
@ALTracer
Even though it is incremental, you would still need to test each build for dependencies.

The stock package may work but, the nano package will fail because something was updated and now requires a new dependency.

If that dependency is only installed with micro and above, the nano and pico builds will fail.

That is just one example of why all the builds would have to be tested to be able to guarantee they are stable.
Ignoring device or rom specific issues and user settings.

You could reduce the testing a bit if you only test the packages that might be affected by an update.
Test stock and mini if an update was in-between them.

Welcome to the OpenGApps party. :D
Please feel free to help and/or contribute. (y)

Cheers. :cowboy:

PS.
My python skills are currently only enough to follow along with the python bits. :ROFLMAO:
 
Last edited:
  • Like
Reactions: osm0sis

Game-R

Member
Jul 7, 2009
34
3
@Game-R
OpenGapps is designed to add GApps to a rom without it, not remove functions from a rom that included GApps from the start.

It's likely that OpenGapps makes a mess of the roms included GApps, because files are stored in different places. Don't do this.

Instead, you should research ways to de-bloat your rom. To some extent, you can delete apps by just deleting their files from the system partition. But it will be a trial and error process to find what you can remove without breaking other things. Or go the simpler route: deactivate the apps in settings without removing them fully.
Thanks for the advice @runekock.
However, I have been trying few other ROMs which doesn't come with any GApps built in. Both are based off LineageOS (https://forum.xda-developers.com/t/rom-7-1-2-unofficial-viperos-v3-1-1-25-08-2018-sumire.3756729/) (https://forum.xda-developers.com/t/...8-5-for-xperia-z5-unofficial-unified.3576281/) and I'm trying to install Open GApps 7.1 to just get Google Play store in it, but the moment I install anything on it, the Wifi Direct and it's ability to Miracast to wireless displays (which was working fine before) falls to pieces immediately.
 
Last edited:

runekock

Senior Member
Apr 24, 2012
903
512
Samsung Galaxy Tab S
Nexus 6
Thanks for the advice @runekock.
However, I have been trying few other ROMs which doesn't come with any GApps built in. Both are based off LineageOS (https://forum.xda-developers.com/t/rom-7-1-2-unofficial-viperos-v3-1-1-25-08-2018-sumire.3756729/) (https://forum.xda-developers.com/t/...8-5-for-xperia-z5-unofficial-unified.3576281/) and I'm trying to install Open GApps 7.1 to just get Google Play store in it, but the moment I install anything on it, the Wifi Direct and it's ability to Miracast to wireless displays (which was working fine before) falls to pieces immediately.
Sorry, then I misunderstood.
Unfortunately, I don't know what to do. Miracast was removed from Android in favor of Chromecast, but if it's still supported by your rom, it's crazy that play services should break it.
 
Open GApps & Miracast?

Thanks for the advice @runekock.
However, I have been trying few other ROMs which doesn't come with any GApps built in. Both are based off LineageOS (https://forum.xda-developers.com/t/rom-7-1-2-unofficial-viperos-v3-1-1-25-08-2018-sumire.3756729/) (https://forum.xda-developers.com/t/...8-5-for-xperia-z5-unofficial-unified.3576281/) and I'm trying to install Open GApps 7.1 to just get Google Play store in it, but the moment I install anything on it, the Wifi Direct and it's ability to Miracast to wireless displays (which was working fine before) falls to pieces immediately.

You cannot flash a custom ROM, boot to system then flash Open GApps later otherwise expect some issues.

It must be done in one go, one after the other after wiping System & Data.

On A/B devices you have to reboot to recovery after flashing the ROM & before flashing GApps.

On encrypted devices you need to format Data instead of a simple wipe.

FYI Miracast a.k.a. Wifi display support was dropped by Google but some LineageOS devs re-implemented it on some devices but not on all currently officially supported devices.

From https://en.wikipedia.org/wiki/Miracast : "Since Android 6.0 Marshmallow released in 2015, Google dropped Miracast support in favor of their own proprietary Google Cast protocol."

Did you test Miracast while running those ROMs without installing Open GApps?

Did you ask in those ROM's threads?
***
 

Game-R

Member
Jul 7, 2009
34
3
Open GApps & Miracast?



You cannot flash a custom ROM, boot to system then flash Open GApps otherwise expect some issues.

It must be done in one go, one after the other after wiping System & Data.

On A/B devices you have to reboot to recovery after flashing the ROM & before flashing GApps.

On encrypted devices you need to format Data instead of a simple wipe.

FYI Miracast a.k.a. Wifi display support was dropped by Google but some LineageOS devs re-implemented it on some devices but not on all currently officially supported devices.

From https://en.wikipedia.org/wiki/Miracast : "Since Android 6.0 Marshmallow released in 2015, Google dropped Miracast support in favor of their own proprietary Google Cast protocol."

Did you test Miracast while running those ROMs without installing Open GApps?

Did you ask in those ROM's threads?
***
Hi @curiousrom,
Yes, I definitely did test it every time before flashing Open GApps and it was working; able to detect wireless TVs and my Miracast devices and I'm able to rename my Wifi Direct name without errors. When I first started flashing my device, I always did install Open GApps immediately after flashing the ROM and I was encountering the problems then and spent the whole of last weekend trying to pin point the source of my Wifi Direct/Miracast troubles. So I started doing the flashing one at a time and found that the Wifi Direct/Miracast seems to work immediately after flashing the ROM but wouldn't after I flashed Open GApps.

But recently, just this evening, after my nth attempt at flashing about 10 different 7.1.2 ROMs to find out what is going on, I found that it may not be Open GApps.

One ROM, that I knew worked previously, was flashed to my phone. I then confirmed its Wifi Direct/Miracast working, but after that I was pulled away to settle something and before I could get around to installing Open Gapps, I started encountering the errors I reported.

I tried a second different ROM (that worked before), tested Wifi Direct/Mircast working, rebooted the phone, and it wasn't working after.
In both cases, I did not have the phone connected to any wifi network nor did it had a SIM card in it, let alone any data connection out.

What is going on here? Do these ROMs self destruct their Wifi Direct/Miracast capability after a couple of minutes?
 
Last edited:

runekock

Senior Member
Apr 24, 2012
903
512
Samsung Galaxy Tab S
Nexus 6
Hi @curiousrom,
Yes, I definitely did test it every time before flashing Open GApps and it was working; able to detect wireless TVs and my Miracast devices and I'm able to rename my Wifi Direct name without errors. I've spent the whole of last weekend trying to pin point the source of my Miracast troubles.

But recently, just this evening, after my nth attempt at flashing about 10 different 7.1.2 ROMs to find out what is going on, I found that it may not be Open GApps.

One ROM, that I knew worked previously, was flashed to my phone. I then confirmed its Wifi Direct/Miracast working, but after that I was pulled away to settle something and before I could get around to installing Open Gapps, I started encountering the errors I reported.

I tried a second different ROM (that worked before), tested Wifi Direct/Mircast working, rebooted the phone, and it wasn't working after.
In both cases, I did not have the phone connected to any wifi network nor did it had a SIM card in it, let alone any data connection out.

What is going on here? Do these ROMs self destruct their Wifi Direct/Miracast capability after a couple of minutes?
Maybe you need to reboot the TV as well???

Miracast was plagued by compatibility problems - that may be part of the reason that Google tired of it.

Is there a firmware update to your TV?
 

Game-R

Member
Jul 7, 2009
34
3
Maybe you need to reboot the TV as well???

Miracast was plagued by compatibility problems - that may be part of the reason that Google tired of it.

Is there a firmware update to your TV?
It's all good now. Managed to find one ROM that somehow is able to keep it's Miracast capability working regardless what is installed or not. The issue is clearly something to do with the few custom ROMs that I tried. I have two other devices, a stock OnePlus 5 and a custom ROM LineageOS Samsung that was reliably able to connect to this Miracast HUD unit while the Xperia Z5 I was trying to set up kept failing.
Appreciate all the assistance!
 
Last edited:
LineageOS Removes Links to Open GApps for Android 8.1, 9.0 & 11 in their Wiki

Well it finally happened.

LineageOS got tired of all the broken builds and this commit was merged: "Remove Open Gapps where alternatives exist - we have too many issues "supporting" users with it".

As you can see in https://wiki.lineageos.org/gapps :

Open_GApps_LineageOS_Wiki_2021-12-09_curiousrom.png
 
  • Like
Reactions: sieghartRM

G A S T

Senior Member
Apr 20, 2018
224
98
Xiaomi Mi 4
Samsung Galaxy S6
LineageOS Removes Links to Open GApps for Android 8.1, 9.0 & 11 in their Wiki

Well it finally happened.

LineageOS got tired of all the broken builds and this commit was merged: "Remove Open Gapps where alternatives exist - we have too many issues "supporting" users with it".

As you can see in https://wiki.lineageos.org/gapps :

View attachment 5478911

What a stupid move! With GApps pico I never had any problems except AA not working properly for a few months.
But on the other hand - this was clearly provoked by the whole GApps team and their useless rapid release schedule. Lots of people proposed to switch to a monthly release of better tested builds.
 
Last edited:
  • Like
Reactions: curiousrom

zimral.xda

Senior Member
I never had any problem with Open Gapps ("pico" variant) too. It is still in use on one of my test/dev devices. For my remaining last productive Samsung S5/klte i stopped using any google apps with the migration from LOS15 to LOS16 nearly 3 years ago. And i never had any problems with my ~50 apps in use. The biggest benefit of not using any google stuff is a ~15% less battery drain, a much faster GUI response and last but not least google has now nearly no chance to track me. If there are still some aliens inside the LOS rom trying to watch me, they will be stopped by ADGuard, NetGuardPro and Blokada. i already moved to the Pixel3 with my two other prod devices currently using stock Android12 with as much as possible google stuff uninstalled/deleted/deactivated and with the introduction of LOS19 for walleye i will flash a pure LOS image only. The only open question is the usage of TWRP or LOS recovery.
So i can still recommend the "pico" if someone want to be tracked by the evil company as "pico" seems to be not affected with the current open gapps bugs. :cool:
 
Last edited:
  • Like
Reactions: G A S T

Trustwizard

Member
Nov 27, 2021
7
1
Hi all and btw gratz for your amazing job! any hint of what can I do on my samsung Note 10.1 (GT-N8020) version? I'm using latest Lineage 16.0 (android 9) and I'm getting some apps like "stadia" and "Vodafone TV" (this one if I go to menu and reenter app it resize) app issues with resolution/resize I guess (green pixels and stuff).
Games like "clash of clans" background colors disapeared sometimes and crash, could it be a wrong Gapps version for my Note 10.1? Youtube/ Netflix its ok. (using arm_9_pico)

Anyone with the same issue/workaround?

Thank you all!

Have a great christmas and an awesome 2022. :)
 

Flounderist

Senior Member
Jan 7, 2016
864
421
Cork
@Nezorflame today I had a weird issue with the A12 nano package.
I tried both builds 20211112 and 2021116 and I had error 64 on recovery.
My device is Realme RMX1931 (arm64) and I was flashing Voltage OS .
The device has been recognised as arm and no apps has been flashed.
The log.txt is basically empty, just arm device detected.
Any hint?
 
  • Like
Reactions: eNVy

ipdev

Recognized Contributor
Feb 14, 2016
1,656
1
2,272
Google Nexus 10
Nexus 7 (2013)
@Nezorflame today I had a weird issue with the A12 nano package.
I tried both builds 20211112 and 2021116 and I had error 64 on recovery.
My device is Realme RMX1931 (arm64) and I was flashing Voltage OS .
The device has been recognised as arm and no apps has been flashed.
The log.txt is basically empty, just arm device detected.
Any hint?
This should help explain it.
OpenGApps - GitHub
Pull request [# 942] - Link and Pull request [# 944] - Link
The next test build should include the architecture fix. ;)

After the PR was merged, I cleaned up and re-synced my local sources.
Pixel Launcher was borked on Android 12 and I have not had time to check into it.

Until Nezorflame has time to run a new A12 test build, feel free to try one of the MOD builds I made for testing.
A12 Pixel Launcher still works on these builds, at least for arm64 🙃

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

Cheers. :cowboy:
 

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.