When can we expect gapps for Android 12? LOS already switched to A12 but I don't understand what's that good for without gapps....
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
- Thread starter MastahF
- Start date
curiousrom
Recognized Contributor
When it's ready obviously.
Volunteer based projects usually don't provide any ETA & asking for one is not cool IMO.
Meanwhile see the linked alternative in https://wiki.lineageos.org/gapps
Also some Open GApps 12 test builds were linked to & discussed in the last couple of pages of this thread.
***
Last edited:
I don't really go to these forums anymore and haven't for a long time, and since I wanted to install LOS19 on my Pixel 3, seeing as it's not getting anymore updates from Google, and noticing there were no gapps 12 available, I naturally wanted to ask (and 300+ pages is a bit too much to digest, lol).
Did you try Mind the Gapps? There is a link for it in this thread: [ROM] [OFFICIAL] [blueline/crosshatch] [Android12.1] LineageOS 19.1
Start at post # 7,258.
---
The pico and nano builds should be good.
Micro and larger are affected by Google wallpaper not working at the moment.
This will not affect the device or boot, you just can not change the wallpaper.
Also a few other non-working things in the micro and larger builds.
---
You can always take a look at GitHub and GitLab to see what is happening.
OpenGApps
My forks.
Cheers.
Is there a GApps compiled version for x86 Android 12? if not, is it possible to compile it to x86 from source currently?
Can anyone help me with following: I tried installing only Google Play Store app (Phonesky.apk) from OpenGapps' Vending-x86.tar.lz archive onto Android 11 AVD Emulator using adb root , remount and moving the .apk to /system/app/ directory, but the app keeps crashing when I start the emulator or open the app. When I check adb logcat I see "java.lang.SecurityException: You either need MANAGE_USERS or CREATE_USERS permission to: query users" when I try to open the app. And I tried granring this permission using pm grant but am unable to do so due to: "java.lang.SecurityException: Permission android.permission.MANAGE_USERS requested by com.android.vending is not a changeable permission type".
So I am stuck. What can be done?
So I am stuck. What can be done?
Hi. I cant upgate gapps to latest 07.05. it say no space in system. How can i update this? I have early gapps now 05.15Start at post # 7,258.
---
The pico and nano builds should be good.
Micro and larger are affected by Google wallpaper not working at the moment.
This will not affect the device or boot, you just can not change the wallpaper.
Also a few other non-working things in the micro and larger builds.
---
You can always take a look at GitHub and GitLab to see what is happening.
OpenGApps
GitHub - LinkGitLab - Link
My forks.
GitHub - [build] - LinkGitLab - [all] - Link
Cheers.
Ok. Format system partition and flash lineageos then new gapps.
Last edited:
Why are you installing that way rather than with one of the flashable zips?
Yes.
i installed nano 0507 12L build with crdroid official on my redmi note 7 but cant get "ok google hotword" to work. when i want to activate voice match it says its actually not avaible for my device. any ideas ?
Its first time installation for me. So i cant say.
But other users using other gapps it seems to work.
Any change to deinstall gapps and try other without loosing data ?
But other users using other gapps it seems to work.
Any change to deinstall gapps and try other without loosing data ?
You can try to wipe system only and try to flash again rom+gapps
But i can not guarantee it will work
Make a Backup before you do it
Dunno know where the Problem iss.
I installed new with another Gapps package with same problems.
When liad google app from playstore hotword wont work.
I injected per gapps addon and now it works.
So its not opengapps fault.
I installed new with another Gapps package with same problems.
When liad google app from playstore hotword wont work.
I injected per gapps addon and now it works.
So its not opengapps fault.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
6
Start at post # 7,256.
---
The pico and nano builds should be good.
Micro and larger are affected by Google wallpaper not working at the moment.
This will not affect the device or boot, you just can not change the wallpaper.
Also a few other non-working things in the micro and larger builds.
---
You can always take a look at GitHub and GitLab to see what is happening.
OpenGApps
My forks.
Cheers.2
You should ask to the ROM developer maybe. It is quite likely that the custom ROM that you are using is missing some libraries that are present on your stock OS instead. Adding Gapps won't help at all.1 -
836Questions? 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 @osm0sis32
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
