GApps builds are automatic. They exist for people who want to flash them. They are not required on an existing ROM. But if you want to flash GApps every day, fill your boots. Now that's (to me) silly. Each to their own.
End of discussion for me.
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
- Thread starter MastahF
- Start date
GApps builds are automatic. They exist for people who want to flash them. They are not required on an existing ROM. But if you want to flash GApps every day, fill your boots. Now that's (to me) silly. Each to their own.
End of discussion for me.
I don't flash OpenGApps everyday. Maybe once a week? I have several applications installed in the /data partition already so wasting more space when I don't have to (i.e. by letting the Play Store automatically update Google apps that are installed in the /system partition) is silly :silly:
My point was that you stated:
When in fact that is your own advice.
It isn't written anywhere.
It is what YOU want people to believe.
If people with older devices and smaller /data partitions listen and take it as read then they will likely run out of storage.
There are other options. Which was my point.
Notice that I stopped long ago when he first said he had never heard that before. Was obvious that he had an idea of what he wants to do and will not be deterred.
Here you go:
https://www.apkmirror.com/apk/googl...8-4-56-100400-262845133-android-apk-download/
Sent from my OnePlus 5T using XDA Labs
Last edited:
Wolfcity
Recognized Contributor
I don't know what's the difference between your world and mine ...
It's a free world after all and as I said: It's a personal preference. Just do whatever you want.
Sent from my Moto G5 Plus using XDA Labs
Google Chrome in 15.08.2019 OpenGapps build is only in English. Resurrection Remix Android Pie, Samsung Galaxy S5
D
Deleted member 2044343
Guest
Search function and reading are helpful: https://xdaforums.com/showpost.php?p=79940829&postcount=6132
Yes I'm know about this. Latest Chrome is not on apkmirror in SDK24. Chrome WebView works, but app is in English. This is bug, because on old builds Chrome was in my language(multilanguage)
Hey guys... got a weird problem and I'm not sure if it's Google or GApps to blame. I just installed a clean version of LineageOS on my Galaxy Note 4 with the latest GApps and when I try to restore my settings from Google I'm asked to fill in my screen lock pattern on a 3x3 grid but my previous lock pattern was based on a 5x5 grid so obviously, I can't unlock the backup. Any idea of what to do here? Is it a GApps thingy or a Google bug?
D
Deleted member 2044343
Guest
Here we are, this should solve your problem: https://www.google.com/amp/s/xdafor...king/remove-lockscreen-recovery-t3530008/amp/
Thanks for the quick reply but I'm not sure how this would allow me to bypass the pattern lock when restoring the google backup. Because this has nothing to do with the current security lock on the phone.
After doing a bit of research on this, I understand the problem. Google by default gives you a 3x3 grid for the pattern lock and this is what it expects. Changing the size of the grid is a "hack" added by LineageOS, but the question remains: why does Google allow a different grid size other than 3x3 to encrypt the backup data of the phone when there's no way of unlocking it when you want to restore it?
This is just messed and I guess my only option is to install everything manually. Boy, this will be a fun night!
Mainly curious about Google Photos crashing.
Is Photos crashing due to Camera app?
You may have to try two or three times to find out but, what is the crash error?
If you can provide a logcat of the crash, it would help point to the actually problem.
Cheers.
Last edited:
Mainly curious about Google Photos crashing.
Is Photos crashing due to Camera app?
You may have to try two or three times to find out but, what is the crash error?
If you can provide a logcat of the crash, it would help point to the actually problem.
Cheers.
The problem appears to be where the Photos app is installed. OpenGApps installs it to /system/app/. If you move it to /system/priv-app/ (I think?) or obviously if its in /data/app/ then it works. If you search through this thread there are various references to this.
Last August 18, up until now my Nubia Red Magic 3 CN Rom is experiencing blink bugs. It will suddenly go into sleep and goes into blinking forever. The only way to stop this is to restart the phone.
Please refer to Logcat here
NRM3CN_2019-08-19-logcat.txt
Here's what it looks like
Blinking sleep bug on Nubia Red Magic 3
Not really sure if the gapps is the cause. I bought this phone last July, I root this with Magisk and installed GApps but I haven't experience this sleep blinking bug. I started to notice this when installing August Gapps. The bug is getting worse.
It just it cannot be unlocked.
Here's what it looks like
August 6 - Sleep Bug on Nubia Red Magic 3
Hoping for fix on soonest time possible
Please refer to Logcat here
NRM3CN_2019-08-19-logcat.txt
Here's what it looks like
Blinking sleep bug on Nubia Red Magic 3
Not really sure if the gapps is the cause. I bought this phone last July, I root this with Magisk and installed GApps but I haven't experience this sleep blinking bug. I started to notice this when installing August Gapps. The bug is getting worse.
It just it cannot be unlocked.
Here's what it looks like
August 6 - Sleep Bug on Nubia Red Magic 3
Hoping for fix on soonest time possible
Last edited:
I'm having a problem with opengapps pico version with a Lineage 12.1 rom (Lollipop 5.1.1), recently built for Fire HD 10. The developer has suggested using these opengapps. After much discussion there, he said that I should ask about my problem here.
When installing an app from the Play Store, "download pending" displays anywhere from 1 minute to 5 minutes before the download actually starts. I went back and installed several opengapps packages, and the last one that worked without that delay was open_gapps-arm64-5.1-pico-20190312.zip. Other packages before that also work. But then on the next day, open_gapps-arm64-5.1-pico-20190313.zip has the delay, as do versions that followed in the last 5 months.
It appears that it is the Play Store app that causes the problem. The "good" Play Store version within that 0312 zip is version 13.9.17. The "bad" version within the 0313 zip is 14.0.28. To make the problem go away, I can just uninstall updates. Or use any Play Store version 13.9.17 or earlier. (But Play Store keeps updating itself to a newer "bad" version).
So is this something that needs to be reported to Google instead of this opengapps project? I do have a logcat of the problem, but I won't include it here until you let me know how to proceed.
When installing an app from the Play Store, "download pending" displays anywhere from 1 minute to 5 minutes before the download actually starts. I went back and installed several opengapps packages, and the last one that worked without that delay was open_gapps-arm64-5.1-pico-20190312.zip. Other packages before that also work. But then on the next day, open_gapps-arm64-5.1-pico-20190313.zip has the delay, as do versions that followed in the last 5 months.
It appears that it is the Play Store app that causes the problem. The "good" Play Store version within that 0312 zip is version 13.9.17. The "bad" version within the 0313 zip is 14.0.28. To make the problem go away, I can just uninstall updates. Or use any Play Store version 13.9.17 or earlier. (But Play Store keeps updating itself to a newer "bad" version).
So is this something that needs to be reported to Google instead of this opengapps project? I do have a logcat of the problem, but I won't include it here until you let me know how to proceed.
Asus zenfone max m2 adroid pie
---------- Post added at 06:55 AM ---------- Previous post was at 06:54 AM ----------
---------- Post added at 06:55 AM ---------- Previous post was at 06:54 AM ----------
Please link donwload
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
