[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
- Thread starter MastahF
- Start date
G
GuestK0051
Guest
Same for me: Recent versions of Open GApps (March onwards) keep crashing trusted face on Nexus 6p. Before it was working fine.
At first I had only dirty flashed and assumed that either this or substratum theme could be the reason. Uninstalled substratum, to no avail. Tried different versions of GApps the same. Eventually today I tried a clean flash and flashed ROM, GAPPS, kernel and SuperSU. As soon as the phone booted up, I tried trusted face but it crashed again. Couldn't be bothered to set the phone up again and restored TWRP backup but forgot to get a new logcat, so I only have one from a couple days ago.
I've observed that recently Google camera 4.2 introduced in aroma version arm64 for 7.1
Does it work?
For AICP on ferrari
Does it work?
For AICP on ferrari
Is it only me or there's something wrong with the Open GApps site? Not letting me choose the Android version.. tried different browsers different devices.. Different connections..hence no downloads.. :'(
Edit: Downloads from Github work
Edit: Downloads from Github work
Attachments
Last edited:
Ibuprophen
Senior Member
Just as an FYI...
Though the Open GApps Project website provides the following links, they are labeled as "OLDER RELEASES" but, those Github links also contain the current releases as well.
PLEASE NOTE: The following Github links may or may not include (for each of the releases) the Md5 files and the Changelog files.
These additional files are provided only if they are released for that specific build, Platform, variant, etc... If you have any questions or concerns, please contact the TWRP support team either by way of their XDA Forum thread or through their website.
Here are The Open GApps Project's Alternative Download links to their Github page that provides both the Current and Older Releases as well.
*****************************************
Releases for the ARM (aka ARM32) Platform Devices
Releases for the ARM64 Platform Devices
Releases for the x86 Platform Devices
Releases for the Combined x86 & x64 (aka x86_64) Platform Devices
Please Enjoy!
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***
Though the Open GApps Project website provides the following links, they are labeled as "OLDER RELEASES" but, those Github links also contain the current releases as well.
PLEASE NOTE: The following Github links may or may not include (for each of the releases) the Md5 files and the Changelog files.
These additional files are provided only if they are released for that specific build, Platform, variant, etc... If you have any questions or concerns, please contact the TWRP support team either by way of their XDA Forum thread or through their website.
Here are The Open GApps Project's Alternative Download links to their Github page that provides both the Current and Older Releases as well.
*****************************************
Releases for the ARM (aka ARM32) Platform Devices
Releases for the ARM64 Platform Devices
Releases for the x86 Platform Devices
Releases for the Combined x86 & x64 (aka x86_64) Platform Devices
Please Enjoy!
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
***PLZ THANK ME WITH A THUMBS UP***
I flashed opengapps pico on LOS13 but I can't sync the contacts. I've tried nearly everything but still can't seem to sync the contacts. In the default contacts app > menu > contacts to display there is no google account shown (only local and whatsapp).
EDIT: I found a strange thing that the google contact app didn't have any permission allowed so I gave the permission to that app and other google apps too. But still, no contacts sync.
EDIT: I found a strange thing that the google contact app didn't have any permission allowed so I gave the permission to that app and other google apps too. But still, no contacts sync.
BUG: Php.Exploit.CVE_2015_2331-1
Report Details
Category: Auth Bypass
Product: None
Summary: Php.Exploit.CVE_2015_2331-1
Steps to reproduce:
1. Download latest Google Apps (bare minimum) package. This can be done easily and compiled at the same time at http://opengapps.org/
PS I have a precompiled package here: https://drive.google.com/file/d/0B6ihhZN41GENU1lUMHZFb0ZIVk0/view?usp=sharing
2. Move files to a personal computer if not already.
3. Download and install ClamAV (and GUI frontend like ClamGTK or ClamWin if necessary) with latest definitions.
(Definitions at the time of exploit found: Main 57, Daily 23241, 00:34 27 Mar 2017; ClamWin 0.99.1 for Windows 10 x64).
Browser/OS: Google Apps package for Android 6.0+. Exploit found on Windows 10 Pro x64, 1607, Build 14393.953.
Attack scenario:
All details and steps are shown in the Steps to Reproduce.
ADDITIONAL INFO:
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-2331
CVE-2015-2331
Original release date: 03/30/2015
Last revised: 12/02/2016
Source: US-CERT/NIST
Modified: This vulnerability has been modified since it was last analyzed by the NVD. It is awaiting reanalysis which may result in further changes to the information provided.
Overview: Integer overflow in the _zip_cdir_new function in zip_dirent.c in libzip 0.11.2 and earlier, as used in the ZIP extension in PHP before 5.4.39, 5.5.x before 5.5.23, and 5.6.x before 5.6.7 and other products, allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a ZIP archive that contains many entries, leading to a heap-based buffer overflow.
Impact Type: Allows unauthorized disclosure of information; Allows unauthorized modification; Allows disruption of service
Acquisition info:
This is the Google Apps package for Android, compiled from source.
Report Details
Category: Auth Bypass
Product: None
Summary: Php.Exploit.CVE_2015_2331-1
Steps to reproduce:
1. Download latest Google Apps (bare minimum) package. This can be done easily and compiled at the same time at http://opengapps.org/
PS I have a precompiled package here: https://drive.google.com/file/d/0B6ihhZN41GENU1lUMHZFb0ZIVk0/view?usp=sharing
2. Move files to a personal computer if not already.
3. Download and install ClamAV (and GUI frontend like ClamGTK or ClamWin if necessary) with latest definitions.
(Definitions at the time of exploit found: Main 57, Daily 23241, 00:34 27 Mar 2017; ClamWin 0.99.1 for Windows 10 x64).
Browser/OS: Google Apps package for Android 6.0+. Exploit found on Windows 10 Pro x64, 1607, Build 14393.953.
Attack scenario:
All details and steps are shown in the Steps to Reproduce.
ADDITIONAL INFO:
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-2331
CVE-2015-2331
Original release date: 03/30/2015
Last revised: 12/02/2016
Source: US-CERT/NIST
Modified: This vulnerability has been modified since it was last analyzed by the NVD. It is awaiting reanalysis which may result in further changes to the information provided.
Overview: Integer overflow in the _zip_cdir_new function in zip_dirent.c in libzip 0.11.2 and earlier, as used in the ZIP extension in PHP before 5.4.39, 5.5.x before 5.5.23, and 5.6.x before 5.6.7 and other products, allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a ZIP archive that contains many entries, leading to a heap-based buffer overflow.
Impact Type: Allows unauthorized disclosure of information; Allows unauthorized modification; Allows disruption of service
Acquisition info:
This is the Google Apps package for Android, compiled from source.
osm0sis
Senior Recognized Developer / Contributor
I am using oneplus x(new bootloader) with trrp-3 latest version. i have flashed latest gapps, validus rom and super su yesterday, But after flashing, google play service keeps stopping, cant sign in in my account or use any app, i came up upon this problem before sevrel weeks also, so i flashed older release of gapps and it worked!! But now this time, i have tried many older releses of gapps but the problem is not solved, please help!!
Nexus 5X here, on latest CypherOS ROM, can someone please help me solve this Ok Google problem? Been searching all day for a fix for Ok Google detection on any screen being turned off automatically right after I turn it on. No clue how to fix this, all I've learned is the problem is related to OpenGapps hotwordenrollment. I tried flashing vendor after flashing gapps, did nothing. Please help me fix this annoyance.
Try here. https://plus.google.com/communities/111402352496339801246
Sent from my Nexus 5X using XDA Labs
I've just installed: open_gapps-arm-7.1-nano-20170401 on LineageOS for Galaxy S3. Why cannot i install with Play Store: Snapchat, Facebook, Messenger and Google Chrome? The other apps i've already installed, but all the time when i try install this apps, Play Store will crash. How can i repair it?
Last edited:
This should happen automatically, all gapps are updated via google play. If you have only recently flashed open gapps then it is entirely possible that you are running the latest versions for your device.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4
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
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
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. -
837Questions? 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:
- Open GApps App
- FAQ @ GitHub
- Package comparison @ GitHub
- Advanced Features and Options @ GitHub
- Development Repository @ GitHub
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!
- Team management and projectleader: @[COLOR="blue"]MastahF[/COLOR]
- Writing of the scripts: @[COLOR="blue"]MastahF[/COLOR] & @[COLOR="blue"]Rapper_skull[/COLOR] or check the team on GitHub and many other contributors
- Updating GApp sources: @[COLOR="blue"]MNBooZe[/COLOR] & @[COLOR="blue"]DJAlik[/COLOR] & @[COLOR="blue"]bgiesing[/COLOR] & @[COLOR="blue"]mc1100[/COLOR] & @[COLOR="blue"]deadman96385[/COLOR] or check the team on GitHub
- AROMA installer: @[COLOR="blue"]raulx222[/COLOR] using LibAroma
- Custom compiled commandline tools: @[COLOR="blue"]YashdSaraf[/COLOR]
- Website: @[COLOR="blue"]raulx222[/COLOR] & @[COLOR="blue"]MastahF[/COLOR] & signalv hosted by GitHub and created with Material Design Lite and JQuery
- Artwork: @[COLOR="blue"]Yeti12[/COLOR]: Yeti-Designs website
- Documentation: @[COLOR="blue"]Trafalgar-Square[/COLOR] and @[COLOR="blue"]MastahF[/COLOR] and many other contributors.
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 @osm0sis36
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.
Edit:
See additional posts.
Post # 7,316
Post # 7,31925Tomorrow 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 now25For 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/23Sorry 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
