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

Search This thread

josephcsible

Senior Member
Nov 3, 2016
223
91
I got Pixel Launcher working! Here's what I did (on a Moto X4 "payton" running the official 20220510 build of LineageOS 19.1):
  1. Install open_gapps-arm64-12L-stock-20220507-UNOFFICIAL_MOD.zip with no gapps-config file
  2. Delete /system_root/system/priv-app/NexusLauncherPrebuilt/
  3. Copy /etc/sysconfig/google-hiddenapi-package-whitelist.xml from the product partition of a stock Pixel 4a (5G) image to /system_root/system/product/etc/sysconfig/
  4. Copy /etc/permissions/privapp-permissions-google-se.xml from the system_ext partition of a stock Pixel 4a (5G) image to /system_root/system/system_ext/etc/permissions/
  5. Reboot into Android and then back into recovery
  6. Create the directory /system_root/system/system_ext/priv-app/NexusLauncherRelease/
  7. Copy /priv-app/NexusLauncherRelease/NexusLauncherRelease.apk from the system_ext partition of a stock Pixel 4a (5G) image to /system_root/system/system_ext/priv-app/NexusLauncherRelease/
I think some of that might have been unnecessary, but at least now we know something that works.
 

master373

Senior Member
Feb 1, 2022
85
30
I can confirm that as of the 20220507 build, stock now boots successfully with no workaround needed. Unfortunately, the Pixel Launcher still doesn't work:
Code:
05-11 02:00:33.046 11995 12015 E AndroidRuntime: FATAL EXCEPTION: UiThreadHelper
05-11 02:00:33.046 11995 12015 E AndroidRuntime: Process: com.google.android.apps.nexuslauncher, PID: 11995
05-11 02:00:33.046 11995 12015 E AndroidRuntime: java.lang.NoSuchMethodError: No interface method startRecentsActivity(Landroid/content/Intent;Landroid/app/IAssistDataReceiver;Landroid/view/IRecentsAnimationRunner;)V in class Landroid/app/IActivityTaskManager; or its super classes (declaration of 'android.app.IActivityTaskManager' appears in /system/framework/framework.jar)
05-11 02:00:33.046 11995 12015 E AndroidRuntime:        at com.android.systemui.shared.system.ActivityManagerWrapper.startRecentsActivity(SourceFile:3)
05-11 02:00:33.046 11995 12015 E AndroidRuntime:        at c.a.b.j1.run(SourceFile:2)
05-11 02:00:33.046 11995 12015 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:938)
05-11 02:00:33.046 11995 12015 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:99)
05-11 02:00:33.046 11995 12015 E AndroidRuntime:        at android.os.Looper.loopOnce(Looper.java:201)
05-11 02:00:33.046 11995 12015 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:288)
05-11 02:00:33.046 11995 12015 E AndroidRuntime:        at android.os.HandlerThread.run(HandlerThread.java:67)
Similar to the error I got with Pixel Launcher in the last build, the problem is that as of AOSP commit 613ba2d, IActivityTaskManager.startRecentsActivity now takes a long as its second parameter instead of an IAssistDataReceiver, which once again points to the problem being that we need to use a version of the Pixel Launcher that was built for Android 12.
i can confirm that pixellauncher is not working. The setup wizard didnt installed too idk why. Im using unofficial lineage 19.1 build for s7 with open_gapps-arm64-12L-stock-20220507-UNOFFICIAL_MOD.zip
 
Last edited:
i can confirm that pixellauncher is not working. The setup wizard didnt installed too idk why. Im using unofficial lineage build for s7

Thanks for the report but could you please edit your post & add the LineageOS version (18.1, 19?, etc) and the full name of the Open GApps file you flashed?

I tried to PM you but your XDA profile is blocked.
***
 
  • Like
Reactions: master373
Open GApps 11 ARM + LineageOS 18.1 = Bootloop!

@Nezorflame - FYI two official LineageOS 18.1 users with ARM devices reported a bootloop with Open GApps but success with MindTheGApps:

Google Nexus 6 (shamu) & open_gapps-arm-11.0-nano-20220503.zip here on Reddit.

Galaxy Note 3 LTE & open_gapps-arm-11.0-pico on XDA here.
***
 

josephcsible

Senior Member
Nov 3, 2016
223
91
I got Pixel Launcher working! Here's what I did (on a Moto X4 "payton" running the official 20220510 build of LineageOS 19.1):
  1. Install open_gapps-arm64-12L-stock-20220507-UNOFFICIAL_MOD.zip with no gapps-config file
  2. Delete /system_root/system/priv-app/NexusLauncherPrebuilt/
  3. Copy /etc/sysconfig/google-hiddenapi-package-whitelist.xml from the product partition of a stock Pixel 4a (5G) image to /system_root/system/product/etc/sysconfig/
  4. Copy /etc/permissions/privapp-permissions-google-se.xml from the system_ext partition of a stock Pixel 4a (5G) image to /system_root/system/system_ext/etc/permissions/
  5. Reboot into Android and then back into recovery
  6. Create the directory /system_root/system/system_ext/priv-app/NexusLauncherRelease/
  7. Copy /priv-app/NexusLauncherRelease/NexusLauncherRelease.apk from the system_ext partition of a stock Pixel 4a (5G) image to /system_root/system/system_ext/priv-app/NexusLauncherRelease/
I think some of that might have been unnecessary, but at least now we know something that works.
I just dirty flashed a OnePlus 6T "fajita" from LineageOS 18.1 to 19.1. I did this same procedure again, but this time I skipped my step 5 "Reboot into Android and then back into recovery", and Pixel Launcher still worked afterwards (and even kept its data). Also, it's okay if you have a gapps-config for other things; just don't disable ActionsServices or PixelLauncher in it.
 
  • Like
Reactions: ipdev

kutiz21

Member
Apr 15, 2016
18
8
Hi. I'm having this bootloop bug as well.
I'm using fortuna3g (Samsung SM-G530H) with Lineage 18.1. UNOFFICIAL BUILD.
With the build open_gapps-arm-11.0-pico-20220215.
It was installed correctly and successfully.

I can't provide to any debugging logs here because it starts bootlooping whenever the boot logo showing up. Not even boot animation.

Other GMS installer like BitGapps works with my ROM.

I also try experimenting myself by manually installing GMS myself on the ROM without any installer zip and it was also giving me bootloops after first boot complete.

If you let the phone turn off or reboot completely. It won't bootloop.

Or whenever I INCORRECTLY TURNING OFF THE PHONE (Commanding `reboot` on terminal) OR REMOVING BATTERY, having the OpenGapps or my DIY gapps installed will making the phone bootlooping until I format /data.

Formatting/Clearing cache or ART cache won't work.
 
Last edited:
  • Like
Reactions: curiousrom

ipdev

Recognized Contributor
Feb 14, 2016
1,784
1
3,060
Google Nexus 10
Nexus 7 (2013)
@josephcsible, thank you for pointing me here from pull request: 959!

Just a question, can I build that pull request and use it, or can I just rely on ipdev's build here? I mean I can really build it, but I just want to hear the recommended way.
OpenGApps - [GitHub] - PR # 959
Is the normal additions to the build script(s) for another Android level.

Save for the cheesy work-a-round to the installer script. ;)
Display 12L instead of 12 for SDK32 when someone is installing the wrong version.


For Android 12.x and my rom is 12. What the ??
Code:
*** Incompatible Android ROM detected ***

This GApps pkg is for Android 12.x ONLY
Please download the correct version for
your ROM: 12 (SDK 32)
******* GApps Installation failed *******
Less confusing. :unsure:
Code:
*** Incompatible Android ROM detected ***

This GApps pkg is for Android 12 ONLY
Please download the correct version for
your ROM: 12L (SDK 32)
******* GApps Installation failed *******

---

You will also need the AA fix for 12/12L builds.
OpenGApps - [GitHub] - PR # 960
Includes a link to the overlay.

You will need to update your sources manually until 12 support is official added.

I gave links to my current build branch and local source changes in Post # 7,319.
I will push a few more permission updates later today after running a new test build. ;)

Feel free to build. :)

Cheers. :cowboy:
 

ipdev

Recognized Contributor
Feb 14, 2016
1,784
1
3,060
Google Nexus 10
Nexus 7 (2013)
Hi all. :)

My test builds still have some issues. :cautious:
  • Added some permissions.
    GitLab - Commit
  • Pixel Launcher v906 for SDK32 and 31.
    GitLab - Commit
    GitLab - Commit
Leave it to Google to update the sdkVersion and keep the same the versionCode. 🙁

Pulled from stock Google Pixel 6 factory image(s).
SDK31 - [oriole-sq1d.220205.003]
SDK32 - [oriole-sp2a.220505.002]
Need to update more apps (and corresponding permissions) to be more compatible with Android 12/12L. 🙃
Along with some other things.

A big Thank You (y) to all that have tested and helped me out with 12L test builds. :D

Cheers all. :cowboy:
 

josephcsible

Senior Member
Nov 3, 2016
223
91
Hi all. :)

My test builds still have some issues. :cautious:
  • Added some permissions.
    GitLab - Commit
  • Pixel Launcher v906 for SDK32 and 31.
    GitLab - Commit
    GitLab - Commit
Leave it to Google to update the sdkVersion and keep the same the versionCode. 🙁

Pulled from stock Google Pixel 6 factory image(s).
SDK31 - [oriole-sq1d.220205.003]
SDK32 - [oriole-sp2a.220505.002]
Need to update more apps (and corresponding permissions) to be more compatible with Android 12/12L. 🙃
Along with some other things.

A big Thank You (y) to all that have tested and helped me out with 12L test builds. :D

Cheers all. :cowboy:
I just updated from the 20220507 build (with my workaround) to the 20220515 one (without any workarounds), and I can confirm that the Pixel Launcher still works fine.
 
  • Like
Reactions: ipdev

kutiz21

Member
Apr 15, 2016
18
8
Okay, so some few tests goes by.

Seems like the culprit causing pre-bootanimation bootlooping in my system is me finishing/continuing the Pixel Migrate/Android Setup setup and lets stock apps updates went through.

On fresh wipe. Any boot interruptions won't making Android bootloop.

Hopes this will enlighten something out.
 

diemadedrei

Senior Member
Mar 13, 2012
680
253
OnePlus 6
Google Pixel 6 Pro
I run the current test build on lineageos 19 and have a problem with my camera. All camera apps are immediately crashing and other apps that start the camera, can't connect. I looked through the logs and from my limited knowledge it might have to do with gapps, since vrcore seems to crash. May be someone has an idea?
 

Attachments

  • logcat.txt
    2.3 MB · Views: 21

josephcsible

Senior Member
Nov 3, 2016
223
91
I run the current test build on lineageos 19 and have a problem with my camera. All camera apps are immediately crashing and other apps that start the camera, can't connect. I looked through the logs and from my limited knowledge it might have to do with gapps, since vrcore seems to crash. May be someone has an idea?
What phone is it? Does the camera work in LineageOS without any GApps installed? If you reflash and then use the pico build instead, does that work? If you upgraded from a previous version of LineageOS, did the camera work there with the same package size you used this time?
 
  • Like
Reactions: curiousrom

diemadedrei

Senior Member
Mar 13, 2012
680
253
OnePlus 6
Google Pixel 6 Pro
What phone is it? Does the camera work in LineageOS without any GApps installed? If you reflash and then use the pico build instead, does that work? If you upgraded from a previous version of LineageOS, did the camera work there with the same package size you used this time?
It's a oneplus 6. I haven't tested all the other stuff because I want to avoid wiping. I cannot pinpoint a certain version. If no one has any idea I might try installing mindthegapps
 

WizardsGod

New member
Dec 16, 2021
2
1
Xiaomi Redmi Note 5 Pro
Hey, is it possible for you to build the GApps for android 12.1(Idk if it's SDK 31 or 32), bc then it could be used on the Windows Subsystem for Android with the MagiskOnWSA project as Microsoft just updated WSA's Android version to 12.1.
And if you do build it, please build it for micro too.
 

josephcsible

Senior Member
Nov 3, 2016
223
91
Hey, is it possible for you to build the GApps for android 12.1(Idk if it's SDK 31 or 32), bc then it could be used on the Windows Subsystem for Android with the MagiskOnWSA project as Microsoft just updated WSA's Android version to 12.1.
And if you do build it, please build it for micro too.
Please search before posting: https://forum.xda-developers.com/t/...ndroid-versions-devices.3098071/post-86595145

And if you want micro, just use the stock zip with a config file that contains "MicroGApps", as documented at https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options#downsizing
 

WizardsGod

New member
Dec 16, 2021
2
1
Xiaomi Redmi Note 5 Pro
Thanks for helping me, but I wanted to ask if you could build for x86_64 as most installations of WSA are on the x64(amd64) platform.

I had forgotten to mention this in my previous post.
 
Last edited:
  • Like
Reactions: smae

BirdsBread

New member
May 25, 2022
1
0
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
Hey im having an issue i installed android 11 on my s5 and it wont install any apps it just tells me to free up space even though there is space, i had android 9 on it before so i decided to try that and the same issue popped up any idea how i might be able to fix this?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hi so the problem is i cannot flash gapps i install lineage-17.1-20200310-UNOFFICIAL-j6primelte with Odin3_v3.14.4 i tried others gapps like nano, mini, etc, arm/arm64 but no i can't install it say error 20 i tried flashing lineage several times let it boot and back to recovery and install gapps but i can't i need help i can't access google play service on other app

    Error Code: 20
    - Unmouting partitions
    udater process ended with ERROR: 20
    Error installing zip file 'sdcard/open_gapps-arm-9.0-pico-20220215.zip'
    updating partition details...
    ...done
    This sounds like a phone-specific problem, not an OpenGapps problem. You should read flashing instructions for you phone, and if that doesn't help, ask your question in a forum for that phone.

    One hint: you must not boot the rom before you install gapps.
    1
    After Debloating MIUI (12.5.6.0.QCQINXM) of Google, Xiaomi and 3rd party bloatware, dirty flashed Open GApps (ARM 10.0 pico), without any onscreen errors. However, there's no Play Store nor Play Services installed.

    Included the debug log for dirty flash.

    In case it is relevant, this is the list of 37+9 bloatware I uninstalled via ADB (ADB App Control and XiaomiADBFastbootTools).

    Clean flashing Open GApps makes it even worse, as I mentioned here.
    com.android.vending is the Play Store and com.google.android.gms is Play Services. Why not just skip removing them and then not need to install any GApps of your own at all?
    1
    When will the new opengapps for Android 12 appear?
  • 835
    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
    27
    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