No, GoogleClock will be compatible with all ROMs. But because only 1 application can claim a certain permission, the GoogleClock can *only* function if there are zero traces of the AOSP Clock. That is why one needs to start with a clean /data partition if one wants to start using the Google Clock, because it is almost impossible not to have any traces of the app left if one has ever travelled to another timezone, or has used the alarm function. This also explains why many people face the "-505" error when downloading the Google Clock from the Play Store.
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
- Thread starter MastahF
- Start date
No, GoogleClock will be compatible with all ROMs. But because only 1 application can claim a certain permission, the GoogleClock can *only* function if there are zero traces of the AOSP Clock. That is why one needs to start with a clean /data partition if one wants to start using the Google Clock, because it is almost impossible not to have any traces of the app left if one has ever travelled to another timezone, or has used the alarm function. This also explains why many people face the "-505" error when downloading the Google Clock from the Play Store.
I remember that in one of the older releases Google webview was optional without a check. I tried it then and removed the aosp webview from twrp before booting. Everything worked as it should, but now with the cm check it is not installing anymore. I am on Resurrection Remix ROM.
Could the cm check be skipped somehow? For example with a keyword in the config file.
Or could this feature be added?
---------- Post added at 06:17 AM ---------- Previous post was at 06:09 AM ----------
Also for your information. I do not install the Google now launched and with the override keyword I uninstall the trebuchet, even with a clean install.
Then Google will restore my launcher, nova launcher, at the end of the setup.
So as long as you restore your Google account and you had an launcher installed from the store you can safely delete the aosp launcher and choose to not install Google now launcher.
Since the initial setup checks for a launcher it might even be that it will ask you to install one from the play store if you don't have one, but I haven't tested that.
Could the cm check be skipped somehow? For example with a keyword in the config file.
Or could this feature be added?
---------- Post added at 06:17 AM ---------- Previous post was at 06:09 AM ----------
Also for your information. I do not install the Google now launched and with the override keyword I uninstall the trebuchet, even with a clean install.
Then Google will restore my launcher, nova launcher, at the end of the setup.
So as long as you restore your Google account and you had an launcher installed from the store you can safely delete the aosp launcher and choose to not install Google now launcher.
Since the initial setup checks for a launcher it might even be that it will ask you to install one from the play store if you don't have one, but I haven't tested that.
I checked the sourcecode of ResurrectionRemix and found their respective alternative WebView support patch. I added support for checking for that Resurrection Remix now:
https://github.com/opengapps/opengapps/commit/754af92a8aeff26ed6a3f77e2624eba649465712
In the long-term this check will be removed, and we will assume that all 5.1+ custom ROMs will support the alternative webview, instead of checking for this specific date per ROM. But at the moment this is still necessary, since not everybody is yet on a ROM that does.
With your launcher, I wouldn't know exactly about 'safe' removal. I at least experienced myself that I got stuck without a launcher during my experimental-phase of creating the package, when my Google Now Launcher was broken. It was really hard to fix and no 'please select a launcher' window or something like that did pop up.
Your device seems to have a 32-bit ROM installed. So in that case you also need the 32-bit (regular 'arm') GApps package.
If the ROM already contains gapps it won't work. Don't know the specifics of the miui ROM though.
Sent from my GT-I9300 using XDA Forums Pro.
I flashed the 6/20/15 ARM32 5.1 stock gapps package with AICP 6/20 nightly and now I am getting a force close every time I try to open the clock application. Is this going to happen every time because of the addition of the Google clock?
I am having a lot of trouble now. I have downloaded the Aroma package for ARM32 5.1 and if I choose to exclude anything (ClockGoogle), the installer just quits out and doesn't install any applications. It doesn't leave behind a log file either.
Edit:
I've been screwing around with the Aroma installer package and if I choose to exclude the Google Clock, the installer crashes back to TWRP on my Nexus 6. It doesn't appear to be leaving any log files behind, so I am at a bit of a loss on how to fix this.
Edit:
I've been screwing around with the Aroma installer package and if I choose to exclude the Google Clock, the installer crashes back to TWRP on my Nexus 6. It doesn't appear to be leaving any log files behind, so I am at a bit of a loss on how to fix this.
I had this. After clearing the app data (and app cache) for the Clock app (Settings -> Apps -> All -> Clock; Force Stop -> Clear Data) it works again. Had to set up alarms again, but otherwise it has been fine since. I also flash the stock package - same 20150620 as you in this case.
Have you tried wiping /system (as well as cache and dalvik/ART cache)? You then need to re-flash ROM, GApps, any custom kernel (if you use one) and any other system apps you use (for me, SuperSU and BetterBatteryStats). I don't know if it will help any TWRP/installer-related issues but it might help with any GApps "installed state" issues that could have happened due to playing around with things. You won't lose any data or apps from the Play Store by doing so (just make sure not to wipe /data).
Last edited:
Google apps not installed
Hi,
I am running 5.1..1 Carbon ROM on Nexus 5. Tried clean flash of the latest ROM with the Aroma installer. (open_gapps-arm-5.1-aroma-20150621). No Gapps are installed not even playstore. Tried thrice with clean flash each time but ot same result.
Can you please advise on what else I can do?
Thanks a lot.
Hi,
I am running 5.1..1 Carbon ROM on Nexus 5. Tried clean flash of the latest ROM with the Aroma installer. (open_gapps-arm-5.1-aroma-20150621). No Gapps are installed not even playstore. Tried thrice with clean flash each time but ot same result.
Can you please advise on what else I can do?
Thanks a lot.
Last edited:
D
Deleted member 2044343
Guest
Please post your debug logHi,
I am running 5.1..1 Carbon ROM on Nexus 5. Tried clean flash of the latest ROM with the Aroma installer. (open_gapps-arm-5.1-aroma-20150621). No Gapps are installed not even playstore. Tried thrice with clean flash each time but ot same result.
Can you please advise on what else I can do?
Thanks a lot.
My sincere apologies but now have reverted back to older version of the GAPPS. Dont have the log. I knw you cant help without that but will try to generate one later tonight and share if i can.
Open google settings, check settings and it is better to use Google Now Launcher...
Sent from my Spice Mi-498 using XDA Free mobile app
D
Deleted member 2044343
Guest
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I
peration_start: 'Flashing'Installing '/sdcard/Download/open_gapps-arm-5.1-stock-20150621.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /sdcard/Download/open_gapps-arm-5.1-stock-20150621.zip
inflating: bkup_tail.sh
inflating: g.prop
inflating: gapps-remove.txt
inflating: installer.data
################################################
____ ________
/ __ \___ ___ ___ / ___/ _ | ___ ___ ___
/ /_/ / _ \/ -_) _ \ / (_ / __ |/ _ \/ _ \(_-<
\____/ .__/\__/_//_/ \___/_/ |_/ .__/ .__/___/
/_/ /_/ /_/
################################################
Open GApps stock 5.1 - 20150621
- Mounting /system, /data, /cache
mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p16 on /cache failed: Device or resource busy
mkdir: can't create directory '/tmp/logs': File exists
- Gathering device & ROM information
sh: armeabi-v7a,armeabi: unknown operand
- Performing system space calculations
du: /system/app/Chrome: No such file or directory
du: /system/app/FitnessPrebuilt: No such file or directory
du: /system/app/GoogleCalendarSyncAdapter: No such file or directory
du: /system/app/GoogleCamera: No such file or directory
du: /system/app/GoogleEars: No such file or directory
du: /system/app/Street: No such file or directory
du: /system/app/talkback: No such file or directory
du: /system/priv-app/GoogleHome: No such file or directory
du: /system/priv-app/Wallet: No such file or directory
du: /system/app/BrowserProviderProxy: No such file or directory
du: /system/app/Gmail: No such file or directory
du: /system/app/GoogleCalendar: No such file or directory
du: /system/app/GoogleCloudPrint: No such file or directory
du: /system/app/GoogleHangouts: No such file or directory
du: /system/app/GoogleKeep: No such file or directory
du: /system/app/GoogleLatinIme: No such file or directory
du: /system/app/GooglePlus: No such file or directory
du: /system/app/PartnerBookmarksProvider: No such file or directory
du: /system/app/QuickSearchBox: No such file or directory
du: /system/app/Vending: No such file or directory
du: /system/priv-app/GmsCore: No such file or directory
du: /system/priv-app/GoogleNow: No such file or directory
du: /system/priv-app/GoogleSearch: No such file or directory
du: /system/priv-app/GoogleHangouts: No such file or directory
du: /system/priv-app/OneTimeInitializer: No such file or directory
du: /system/priv-app/Provision: No such file or directory
du: /system/priv-app/QuickSearchBox: No such file or directory
du: /system/priv-app/Vending: No such file or directory
du: /system/app/GoogleBackupTransport: No such file or directory
du: /system/app/GoogleFeedback: No such file or directory
du: /system/app/GoogleHome: No such file or directory
du: /system/app/GoogleLoginService: No such file or directory
du: /system/app/GoogleOneTimeInitializer: No such file or directory
du: /system/app/GooglePartnerSetup: No such file or directory
du: /system/app/GoogleServicesFramework: No such file or directory
du: /system/app/Hangouts: No such file or directory
du: /system/app/Phonesky: No such file or directory
du: /system/app/PrebuiltGmsCore: No such file or directory
du: /system/app/SetupWizard: No such file or directory
du: /system/app/Velvet: No such file or directory
du: /system/app/Wallet: No such file or directory
du: /system/lib/libjni_latinime.so: No such file or directory
du: /system/lib/libjni_latinimegoogle.so: No such file or directory
du: /system/lib64/libjni_latinimegoogle.so: No such file or directory
du: /system/app/LatinIME/lib/arm/libjni_latinime.so: No such file or directory
du: /system/app/LatinIME/lib/arm/libjni_latinimegoogle.so: No such file or directory
du: /system/priv-app/talkback: No such file or directory
/tmp/updater: line 918: arithmetic syntax error
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/open_gapps-arm-5.1-stock-20150621.zip'
Error flashing zip '/sdcard/Download/open_gapps-arm-5.1-stock-20150621.zip'
Updating partition details...
I
ata backup size is 3504MB, free: 37210MB.I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I
peration_end - status=1I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'mount'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'reboot'
I:Set page: 'rebootcheck'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
Rebooting...
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
