I had no doubt. Cygwin is a solid tool with a long story and all the applications used by the scripts are present in all distros. The only problem is that installing Cygwin is sometimes a plague for a complete environment. BTW an eventual Windows port is the lowest of the priorities.
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
- Thread starter MastahF
- Start date
Using your information, I repacked on windows, not signed. And then my package did work. Then I repackaged it on linux nog signed, and it did not work.
I inspected the windows-made package once more, and found at the the directories(!) were there not part of the zip file, while on linux they were. So I added an extra paremeter in linux not to add the directories explicitly, and then it did work, as long as I did nog sign it
So then I tried to resolve the problem: why didn't it want to sign correctly? And my feeling was that signapk.jar was breaking the zipfile if the zip was made on unix instead of windows (it kept changing some weird archive properties). So I searched for more ways and tools how to sign the zip. I did find another source, based on a shellscript and openssl, and by adapting their script to our needs I present to you: working, compressed and signed flashable zips
Update can be found in github, of course.
Google Play Store 5.5.8
http://www.apkmirror.com/apk/google...google-play-store-5-5-8-android-apk-download/
http://www.apkmirror.com/apk/google...google-play-store-5-5-8-android-apk-download/
This is effing awesome ?. I'd like to help, I have skills, but not time. I can however look over certain things and help out with bugs, debugging, etc. Basic QA work.
What are your thoughts on integrating the Play Store version of the Webview?
Can it be used to replace the system app?
User app: Android System WebView
com.google.android.webview 42.0.2311.138
System app: Android WebView
com.android.webview version 39(e1cf507233-arm)
Can it be used to replace the system app?
User app: Android System WebView
com.google.android.webview 42.0.2311.138
System app: Android WebView
com.android.webview version 39(e1cf507233-arm)
Just curious...is it too much trouble to have different flavors of the Gapps like the PA ones used to (Pico, Nano, etc.)
Thanks for all your hard work in keeping the Gapps alive!
Thanks for all your hard work in keeping the Gapps alive!
Having multiple flavors is quite useless and time consuming, since the stock package can be easly transformed to slimmer packages.
"How?" Asked the n00b?
Here´s how (post #2): http://androidforums.com/threads/of...d-google-stock-lollipop-gapps-package.902159/
While the OP is enjoying his holiday, could somebody please write up a little tutorial how to use that building scripts, how to "roll your own", as they say by Slim gapps.
well, there's this thread, where everyone using them can post bugs, eventually...
and there's nandroid backup, which is always your truly friend...
Why don't you volunteer as a tester? :highfive:
Trying something on XDA usually means warranty void for your device, so what kind of warranty do you expect?
You do know that everything provided is free of charge and by people who decided to take some of their free time to help the ones that have no idea how to build something like this right? So demanding for something is of an extreme bad connotation and shows a total lack of consideration by the person putting this stuff out here for us to leech!
You either have the dare to try it out, how the Dev wants for it to happen, beta | alpha | pre-alpha, or you study and become one yourself. Or even better for your kind of demand... stay on the Stock ROMs / GApps that come with it, that are supposedly thoroughly tested by a team (samsung | htc and the works) than these that are provided as is.
Have a nice one
:good: :fingers-crossed:the spirit of XDA is COLLABORATION... no one HAS TO DO anything or give any type of warranty or ETA, and no one DESERVES anything...
who is capable of DOING active development DESERVES our respect, and who is less capable AT LEAST could try the stuff and report back feedback&logs, to help the former improve his work, and have the latter enjoing from the progress...
I truly see your views and understand, no sarcasm no nothing I mean it.
Don't want the thread to derail into offtopic discussion or explode into anger and rage.
After a nice holiday, I am back in town and had time to process the input about how to improve the scripts and think about how to set-up a proper infrastructure.
I am now busy with setting up this infrastructure and creating some new scripts that will be necessary to enable the collaborative tools for the team, multi-platform support and multi-Android releases support.
For those that are (willing to become) part of the team: please PM me your github-username, or if you don't have one yet: create one. Then I will be able to add you to the organisation.
Meanwhile Nicholas Buse was on github so nice to provide me with a pull request with updated sources, so I uploaded that one and will update post #1.
It is now on my todo-list
Other forum members pointed already out how to transform the stock-package into the smaller packages during execution-time at your phone.
I am now busy with setting up this infrastructure and creating some new scripts that will be necessary to enable the collaborative tools for the team, multi-platform support and multi-Android releases support.
For those that are (willing to become) part of the team: please PM me your github-username, or if you don't have one yet: create one. Then I will be able to add you to the organisation.
Meanwhile Nicholas Buse was on github so nice to provide me with a pull request with updated sources, so I uploaded that one and will update post #1.
You are welcome to help! At the first page you can see which roles are available, drop me a PM if you want to get involved
I looked into this, and yes, I think we will make this part of the Stock package, since stock-Nexus machines come with this package too.
It is now on my todo-list
At the moment this would be indeed troublesome to create those different builds, it would take me relatively a lot of time to do that manually, better to use that time to develop my scripts. Overtime they might return though, when they can be generated by scripts.
Other forum members pointed already out how to transform the stock-package into the smaller packages during execution-time at your phone.
I am working on it, it will be available soon (before the end of the month I guess)
Not yet. But In the future I think about creating a webhook from the git repository that can automatically generate new builds at the spot.
Nope, they are not, that is why they are marked as [BETA]. But you are free to try them and give feedback or even help with the development if you have the resources!
Last edited:
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
