yashsingh1/xdaforums huggingface dataset:
[Android Software Development] MastahF:
Because of the launch of Android Pay, from the build of 11th of September and forward the keyword 'Wallet' has been changed to 'AndroidPay'
[Android Software Development] Sir_gpm:
Running without an issue.
[Android Software Development] WORF84:
[MENTION=6404745]MastahF[/MENTION]

Do you plan on offering add-on similar to TK GApps?

Would be nice to see Webview as an option since it's not available in the smaller packs.
[Android Software Development] Ok_Kaleidoscope5109:
I urge you to rethink this because Android Pay doesn't work on rooted devices... So while it's cool to include this, Gapps are targeted at rooted users mainly. So it would just be a waste. While the old Wallet is not as good due to the lack of EMV tokenization, it at least works still with rooted phones.
[Android Software Development] bxlegend:
Gapps are not targeted at rooted users. They package is mainly for custom roms or roms that do not include Gapps. You successfully disable root, register your cards with Android Pay, and enable root afterwards. If the ROM maker did something to break CTS, then Android Pay will not work. There is a link somewhere that explains this but I'll have to go dig it up.
[Android Software Development] MastahF:
It is not in the current roadmap. If you want WebView or any of the other Nexus-like features I would suggest to use Stock, in combination with a configfile.

But you (or anyone else) can also clone easily the opengapps repository and build your own very custom package by making some small adjustments to the scripts :)

GApps is indeed not only for rooted users, but for all Custom ROMs and Stock ROMs. Policies about rooting and Android Pay and the verification service that it uses, called SafetyNet ( http://developer.android.com/training/safetynet/index.html ) is something that ROM developers and Google have to fix/sort out.

From our perspective, Google puts com.google.android.apps.walletnfcrel in /system/priv-app/Wallet/ and so do we. This app used to be called 'Google Wallet' and in its latest release it is called 'Android Pay', so we changed the keyword to avoid any possible confusion.

Meanwhile Google launched a new app com.google.android.apps.gmoney that they now brand as 'Google Wallet', which is not (yet) on any of the Nexus devices. As soon as it is, and a foldername would be known, we can bundle it.

We have to do it like this, because if we would use the old Wallet app, people would get an upgrade to Android Pay anyhow, since it uses the same package name. We cannot bundle the other 'new' Wallet app, since it would break current installations, especially Stock ROMs would get completely broken if a completely other app would get installed in the 'Wallet' folder.
[Android Software Development] Ultramanoid:
Another option. There's also this thread here in XDA with Gapps and a large variety of add-ons, rigorously maintained ( WebView is available ) :

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

By the way that thread is how I discovered this one and opengapps. We're truly spoiled for generous developers and packagers in XDA.

ㄟ(ツ)
[Android Software Development] 2phazt:
I personally appreciate the approach of one package with a single time configuration and afterwards fire and forget flashing. Applying multiple addons is much more hassle.
[Android Software Development] J.M.Siyath:
which gapp has smart face unlock?
[Android Software Development] tcat007:
OP "Package comparison" link.
[Android Software Development] djnata:
Is there any link to see the changelog when are updates?
[Android Software Development] MastahF:
On the opengapps.org homepage you can find a link to Twitter which streams a live changelog, aggregated from GitHub: https://twitter.com/opengapps

Also, the detailed changes can be found on GitHub itself and each release is properly tagged on Github, so you can see on which commit a release is based into detail.

Also you can download 'Version Information' on the opengapps.org website when you have an architecture + android release selected, which also gives you detailed information about the apps that were used for that release.
[Android Software Development] Leang Vannak:
how to flash new Aroma Gapps over existing Rom without bricking the phone?
[Android Software Development] tcat007:
Also, I always flash Nano on my Nexus 7 because Mini gives me low memory error (with at least 500mb free). Will Aroma flash on the N7 if I only install 3 or 4 Gapps? File is so big, just wondering.
[Android Software Development] MastahF:
I don't understand your question. You can always reflash Open GApps over an existing ROM+OpenGApps installation.

Yes, Aroma just gives you the choice which apps to install, so the size of the installer itself doesn't matter, only the amount of and which packages you select during the installation process influence the space that is used on /system/.
[Android Software Development] Zenns:
any idea why this isnt working for my phone (Yu Yureka) CyanogenMod 12.1 Nightly 64 Bit, it is saying incompatible ROM for 5.1 ??

CyanogenMod 12.1 20150915 NIGHTLY - tomato

Android Version 5.1.1

debug Logs Attached
[Android Software Development] MastahF:
Hi, thank you for the feedback, including the logs.

Unfortunately you are not the first one to experience this problem on this device. For some reason the 'tomato' has a completely broken build.prop file (look at the one supplied in the debug logs) which cannot be processed by (any) script.

The CM maintainer of this device should fix this, so best is to contact him/her about this (and I asked the ones who did report this problem before also to do so).

You could manually change the build.prop into a file that adheres to the Android specification, but best would be if upstream would fix this :-/
[Android Software Development] Zenns:
I spoke to the cm maintainer yesterday about this issue

1) they claim my build.prop is corrupted(no idea how that happen) current on TWRP 2.8.6.0

and

2) fingerprints on cm are always the last/latest official build fingerprints for market compatability; they should be going off cm version name or some other prop to get the actual os version
[Android Software Development] shag00:
Running CM 12.1 201509015 with Baseband N9005ZSUG0H3. Attempted to install gapps 20150916 and 20150906, both are not installing the core apps and I have no play store nor can I add my google account. Please see attached log.

Suggestions?
[Android Software Development] MastahF:
Thank you for the response. Weird that your build.prop got corrupted, but as I said, some people did report it before. So I guess *something* on the tomato devices like a broken ROM or a broken TWRP is triggering this corruption :-/

As far as it concerns the GApps installation we look at ro.build.version.release which identifies the Android version, for both official stock ROMs as Custom ROMs including CM.

Could you please attach the full debug log? Then we can try to see what is going wrong.

Also I already see you use PhilZ's recovery, I strongly suggest to use TWRP to avoid any compatability issues (if it is available for your device ofc).
[Android Software Development] shag00:
Debug log attached.
[Android Software Development] MastahF:
Thank you.

As I already suspected, the error is with the recovery. The 'tar' command is not able to process the '-' as compressed input OR the filepaths to be extracted argument .

Your recovery is also quite old, if you want to stay with Philz, please update to the latest version available, which should not have this problem anymore.

But I strongly suggest to use TWRP, for your device I think it should be this one (but be careful to check): https://twrp.me/devices/samsunggalaxynote3internationalqualcomm.html

[MENTION=3989659]Rapper_skull[/MENTION] Do you think we could write some (trivial?) extra error-detection code in update-binary that could check if tar supports '-' as input and/or the extractrion filepath arguments?
[Android Software Development] sigprof:
Your build.prop is not actually corrupted — it is compressed, but transparent decompression did not happen as intended. Transparent compression support was enabled in CM12.1 for tomato on 2015-06-24, but it needs the corresponding kernel changes(1, 2) to work properly; without those kernel changes the compressed files will just be read in the compressed form, which apparently happens for you. Most likely the problem is that your TWRP recovery image is too old and contains a kernel without the transparent compression patches.
[Android Software Development] MastahF:
Thank you [MENTION=4421569]sigprof[/MENTION] for this detailed explanation. I had no idea that feature did exist and that this could happen. I might put something in the script then to detect such malformed uncrompessed output to give a better and more useful error output to the user. Is there a specific 'signature' that appears within these compressed files, like certain start-characters?

UPDATE: I checked back the earlier reports and I always see all these 'broken' build.prop starting with a hex "7a7a 7a7a 1002" so I assume checking for that magic header would do the trick.

Now I need a volunteer for testing that :P
[Android Software Development] sigprof:
The format is described here; the signature is 4 bytes "zzzz" (not an ideal choice, because it is pure ASCII text); subsequent bytes may differ according to the chosen compression method and other parameters.
[Android Software Development] MastahF:
Thank you, I added it now as a check to the script (and it will be in tomorrow's build) but we still need someone to take test it, otherwise we won't be sure it really gives this error when having this issue.
[Android Software Development] Rapper_skull:
Can you open an issue on Github? I can't take a look at it right now and I'm afraid I'll forget.
[Android Software Development] MastahF:
Ok, I added it, and assigned it to you :P

https://github.com/opengapps/opengapps/issues/111
[Android Software Development] tcat007:
I just started using Aroma, big file, but nice you can pick and choose, and uninstall other crap on a rom.

Question, is there any way to save settings in various apps (like ringtones in Hangouts)? Every time I flash a new rom or new Gapps settings go back to default. Saving data doesn't seem to save some settings.
[Android Software Development] MastahF:
All settings are normally saved on /data/ and should persist through any ROM or GApps updates.

What can happen with *specifically* the ringtones, is that if you (re)flash your ROM and/or restore your apps with Titanium Backup is that these get assigned wrongly. Cause of that is because the reference for which ringtone is set, is done by the app by referring to a ringtone ID and not to e.g. the name. These IDs are (randomly) reassigned when you reinstall the ROM with a clean /data/ partition, which can result in a previous ringtone choice to refer to another ringtone when the app is reinstalled.

So if you upgrade your ROM it is most easy to a 'dirty' flash, not wiping /data. With most updated ROM builds this should also not pose any problems, only if you are specifically told not to dirty flash because of incompatibilities you'd need a clean flash. Wiping (dalvik)cache after each flash is still strongly recommended.
[Android Software Development] jeevan_500:
hi thanks for the gapps

i am an user of Yu Yureka (tomato) i am using micro gapps in which i don't want to install google now launcher app only is there any way to edit such that i can exclude google now launcher.if yes kindly provide detail procedure how to exclude google now launcher
[Android Software Development] dannyella:
Hi everyone, I'm new to this gapps package. Updated CM wiki page got me here. Does PICO include Google search app? If no, what is the most minimal package that includes it? Does full Stock replace AOSP apps with Google variants?
[Android Software Development] MastahF:
To see which package includes which applications see our Wiki: https://github.com/opengapps/opengapps/wiki/Package-Comparison

To exclude an application you need to use a gapps-config file. It is explained on the wiki here: https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options#the-gapps-config-file

There are also very detailed examples of how such config files look like in this thread and across the internet.
[Android Software Development] Zenns:
[MENTION=4421569]sigprof[/MENTION]

thank you for clear explanation :) you save alot of people the trouble and the open gapps, the issue have been reported to TWRP Lead Developer :) [MENTION=3476147]Dee_[/MENTION]Troy

[MENTION=6404745]MastahF[/MENTION]

I have tested your open-gapps 16 build with Cyanogen Recovery and it works fine no unknown issue with google apps that I used to have ;) knew that yours was the best working one just let people know about twrp issue so they don't freak out :)
[Android Software Development] tcat007:
Thanks. I just notice, especially in Hangouts, that I always turn off vibration and change ringtone in about 5 places (account and SMS), and anytime I flash (clean or dirty, or just flashing Aroma without flashing ROM), they all are back on (with default ringtones). Not a big deal, I am use to checking them after a flash and changing them back. Google seems to remember most settings related to your account, just not in Hangouts. Just wasn't sure if it's a ROM or Gapps or Google issue.
[Android Software Development] MastahF:
Would you be willing to check out today's build with the 'broken' recovery you were using earlier? I would be very interested if the detection mechanism for this specific error does work. Thank you!
[Android Software Development] shag00:
[MENTION=6404745]MastahF[/MENTION]

Logs from today's build.
[Android Software Development] Zenns:
the broken recovery ? TWRP 2.8.6.0 :( I have already flash cynaogen recovery quite hassle to go back
[Android Software Development] MastahF:
You could probably boot the old recovery via fastboot, without having to flash it.

Boot your device in fastboot/download mode and attach the USB to your computer.

Run the commands: 'fastboot boot /path/to/old/twrp.img'

then it should boot that old TWRP just for once.
[Android Software Development] lunarplexus:
Drive and Street View crashes

I've installed Open GAPPS ARM 5.1 Aroma 20150906 on my Moto G 2014 Titan running AOSP 5.1.1-20150911 by LuK1337. Google Drive crashes every time I try to open PDF files with it and Street View crashes on opening or when closing from the Profile tab. Logcat attached.
[Android Software Development] jcadduono:
Could you add an option to the site to generate a direct link, even if it's using a temporary GET token? It would be nice to be able to download gapps over mobile data, which the usual Android browsers are seemingly incapable of due to corrupted data / lost connection. I have to use wget -c for pretty much everything over 2 MB. The joys of living in Canada, where everything is an unstable 1xRTT generation backbone broadcasting HSPA or LTE signals to keep up with modern phones, lol...
[Android Software Development] musabhai:
Are these packages supported by android 5.1.1 ?
[Android Software Development] WhipeeDip:
Yes.
[Android Software Development] MastahF:
If you want direct links I suggest to use the GitHub releases page, e.g for arm it is: https://github.com/opengapps/arm/releases/latest

There are direct HTTP links. Also, if you look at the URL pattern, you can easily see how each day the URL changes. So you can adjust any wget command easily to a specific (future) release.
[Android Software Development] MastahF:
Hi,

it is hard to tell what exactly is going on, but it is not a problem of the GApps package itself. It must be in the Google Application or in your ROM.

The interesting lines are at e.g. 1754 where you have for example:

09-19 18:43:21.627 D/Error (32530): ERR: exClass=android.os.StrictMode$StrictModeDiskReadViolation
09-19 18:43:21.627 D/Error (32530): ERR: exMsg=policy=903 violation=2
09-19 18:43:21.627 D/Error (32530): ERR: file=StrictMode.java
09-19 18:43:21.627 D/Error (32530): ERR: class=android.os.StrictMode$AndroidBlockGuardPolicy
09-19 18:43:21.627 D/Error (32530): ERR: method=onReadFromDisk line=1137
09-19 18:43:21.628 D/Error (32530): ERR: stack=android.os.StrictMode$StrictModeDiskReadViolation: policy=903 violation=2

Something called android.os.StrictMode is alarming that the Google Application is trying to do something that is not allowed. So my guess would be that your ROM has some security features enabled or set too strict. Best would be to approach your ROM developer with this logcat.
[Android Software Development] lunarplexus:
Thanks so much. I'll ask them. Would you be interested in looking at the gapps logs or is there no point?
[Android Software Development] Leang Vannak:
thank you so much for this GApps.
[Android Software Development] Tung_meister:
Just flashed a new ROM on my nexus 9 and used these gapps however I don't have the option for OK Google always on, it's grayed out stating not available in my language. I'm using UK English which I know is supported, I tried switching to US English but the issue is still present, any ideas?
[Android Software Development] D@rekills4:
Strange, I flashed yesterday and have that option available to me on my language as well as yours.
[Android Software Development] GirishSharma:
Device: OnePlus One

ROM: SlimSaber-bacon-5.1.1-20150910

Android Version: 5.1.1

Gapps: Open_gapps-arm-5.1-stock-20150910

If I don't flash Open gapps, then I am able to flash any other mod like xposed, sound mod by ergo proxy etc., all gets flashed and there is no bootloop, but if I first flashes open gapps and after that I flashes any other mod/zip, then then device in bootloop i.e. if my steps are :

1.Flash rom

2.Flash any other mod/zip

3.Flash open gapps

then there is no bootloop, device starts working smoothly....

but, if my steps are like below:

1.Flash rom

2.Flash Open gapps

3.Flash any other mod/zip

then this is bootloop, device just shows only boot animation....
[Android Software Development] MastahF:
More people experience issues with OK Google in the Google APp when using non-US English. Sometimes it works, sometimes it doesn't, often depending on your system language etc. It is very inconsistent and hard to find out what the exact issue is.

But I updated now the 'offline language' files, which will be included part of future builds (22 september and later) and lets hope that it it will solve your issue: https://github.com/opengapps/all/commit/986f758aa4bc2afd97d214dc88d6f4ac2dce6e3b

Please include at least debug logs of the BOTH installation attempts. Also, please try whether you can get a logcat (if possible) of the failing bootprocess.
[Android Software Development] GirishSharma:
[MENTION=6404745]MastahF[/MENTION]

At this moment, I have installed Open gapps as mentioned above and if I flashes any mod/zip, device will fail to boot for sure. I don't know how do I capture the log which will helpful to you.
[Android Software Development] MastahF:
I need the log to be able to see the (possible) differences between your different installation methods.

You can retrieve the debug log after installation in recovery. The debug log can be found in the location where the Open GApps zip was located when flashing (see https://github.com/opengapps/openga...stall-what-information-do-you-need-to-help-me )

It will be named open_gapps_debug_logs.tar.gz and even when in recovery you should be able to retrieve and copy this file, e.g. using a computer via USB, or using the file manager within the recovery itself and copying to e.g. the sdcard. NB: the debug log is overwritten when you are re-running the installation. So make sure to copy the log directly after trying the first method, before trying the second.
[Android Software Development] GirishSharma:
I am having below file which you said at the same location where i have above open gapps zip file. I did not permormed two installations, i.e. first i flashed rom, super su zip and this open gapps zip. Now, i wish to flash some more other miod/ zips like xposed, sound mods, etc.; files are getting flashed successfully, but there is only boot logo after clicking start system in twrp recovery.

I don't know attached file will helpful to you or not.
[Android Software Development] MastahF:
But you described that if you'd flash Open GApps *after* the installation of the mods, you did not have problems. And if you'd flash the Open GApps *before* the mods, you'd get the bootloop.

The only way to find out what is different, is to flash it in both manners, collect the debug log, and then I can look what is different: because the debug logs contain for example an overview of all files on your system. So I could check if one of the mods removes e.g. some of the Open GApps files.

So only this single debug log is not enough, I need also one from the situation where it is in a broken state.
[Android Software Development] GirishSharma:
I understands that you need two logs for compare, so for that i have to flash my current system. Are below steps are correct:

1.Current log somewhere and rename xda.tar.tz.(which i have just posted above).

2.Complete wipe system, data, delvik.

3.Flash slimsaber zip rom file.

4.Starts device.

5.Again in twrp and flash the mods which i want.

6.Start device.

7.Again in twrp and flash open gapps.

This is log1.tar.tz. Cut and paste in other folder.

8.Now i tries to flash other mod, it is boot failure, so :

1.Above step 1.

2.Above step 2.

3.Starts device.

4.flash open gapps.

5.I will get another tar file and i attach here.

6.If i wish to other mod, device will be in bootloop, because i have flashed open gapps, so i shall attach the last tar.gz file.

Are above steps right please?

Between, I don't know why device is in boot failure( only boot animation ) with open gapps, while earlier i have played around tk, pa gapps too, and with them there was no such issue though.
[Android Software Development] MastahF:
The order of the steps are correct. Booting the device between flashing is not necessary. You can flash one zip directly after the other in TWRP.
[Android Software Development] imcrazyz:
Hello. I'm new to this gapps thingy.

Recently I did some research on which gapps is better but I couldn't find any reliable information.

Just curious between TK, PA and Open, are they actually the same?

Some people say TK is faster, Open is faster and stuff, aren't they the same?

Please enlighten me. Thanks.
[Android Software Development] MastahF:
If you go for a very minimal GApps (like pico) for ARM platform and Android 5.1, the differences are not that large. Most GApps will install a Google Play Services for your specific screen DPI. Some GApps, like ours, adds some extra features to some of the smaller packages, like off-line voice recognition support.

But if you want a package that is most up to date (literally every day), supports all hardware platforms, supports multiple Android versions and offers a full set of Google applications that also *do* have DPI-optimized apps (which are faster and use less of your battery) for all your applications, you should use Open GApps.

Also, since we are a fully open source initiative, you also get the power and opportunity to create your very own (customized) GApps and to even contribute programming code or APKs to the project. Also you can use our preliminary toolset to create 'trusted' GApps of which you can be sure that all applications are signed by Google and do not contain any malicous code. Which is not possible with any of the third party, by hand crafted, GApps.

For your question about the exact difference between Open GApps, TK and PA. The codebase of our downloadable packages is derived from PA GApps, nowadays called TK GApps. But TK GApps only supports arm 5.1, is only updated on the weekends and does not have DPI-optimized apps for many of the applications (like YouTube, Hangouts, Drive, Docs, Sheets, Slides etc) neither does it contain the extra compression levels to keep the download relatively small. That's ofcourse our description of the differences, so you'd better ask the creator of TK too.