yashsingh1/xdaforums huggingface dataset:
[Android Software Development] cianz94:
[MENTION=5227588]Deltadroid[/MENTION] When will be available more Gapps for Marshamallow? I'm waiting for messenger and google chrome on flashable zips :D

Thanks for your amazing work ! :D
[Android Software Development] Deltadroid:
The current lollipop chrome add-on should also work with marshmallow.

I am currently unable to test the latest lollipop messenger add-on with marshmallow, but it should also work with marshmallow.

Most of the lollipop add-ons should also work with marshmallow. The only lollipop add-on that might not work yet on marshmallow is Google launcher because I'm still waiting for an update.

If there is a lollipop add-on that does not work with marshmallow, then I will create a separate marshmallow add-on.
[Android Software Development] cianz94:
Messenger and google keyboard doesn't work with MM. I test it. They don't replace the aosp apps.

Edit: problem with google dialer.

When I call, I don't have any possibility to end the call and interact with other function. Any ideas?
[Android Software Development] Deltadroid:
Thanks. The names of the aosp apps for sms and keyboard must have changed in marshmallow. Can you tell me the names of the stock AOSP marshmallow apps for sms and keyboard on the rom you are using?

The Google dialer issue will probably need either a rom update or an app update. Try rebooting after making sure Google dialer has full app ops permissions.

Edit: if the lollipop add-on was last updated this month, then it should have marshmallow support. Google is slowly releasing new app versions with marshmallow support.
[Android Software Development] cianz94:
Yes. The keyboard have the same name but the SMS app is the same of messenger but have different icon.

I have attached the screenshot.

Edit: for me, the google dialer will probably need an app update. I activated all permissions.
[Android Software Development] Deltadroid:
In Lollipop, the stock sms application is /system/priv-app/Mms/Mms.apk

Also, in Lollipop, the stock keyboard is /system/app/LatinIME/LatinIME.apk

Do you see these two files also in your Marshmallow ROM? If these files are the same name in Marshmallow, then the Google keyboard addon should replace the stock aosp marshmallow keyboard.

The Google Messenger addon probably still needs to update for Marshmallow support, but the Google Keyboard addon should work with Marshmallow because it was just updated.

EDIT: Don't forget to apply full app ops permissions to the google keyboard after installing the addon. Also, try clearing the data/cache for Google Keyboard in app settings. It may also be necessary to reboot after giving Google Keyboard permissions with app ops.
[Android Software Development] cianz94:
When I flash the google keyboard, at the reboot , the keyboard is deleted. No app ops permissions.
[Android Software Development] Deltadroid:
The Google Keyboard addon is installed correctly if you have this file:

/system/app/LatinIMEGoogle/LatinIMEGoogle.apk

Also, the stock aosp keyboard (/system/app/LatinIME/LatinIME.apk) should not exist anymore after flashing the Google Keyboard addon because it is replaced by LatinIMEGoogle.apk.

If these files exist and the keyboard is not working, then I have an idea on how to fix this and I will post an update.
[Android Software Development] cianz94:
I try with the latest version of keyboard? It support MM?
[Android Software Development] Deltadroid:
Yes, the latest version of Google Keyboard has MM support. I have uploaded a new keyboard addon to try.
[Android Software Development] cianz94:
Thanks. Which apps totally support MM?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Android Software Development] Deltadroid:
Keyboard

Google Keyboard addon version 4.1.23043.2297020-23043 has been repackaged to support Marshmallow.

Google Keyboard addon for 5.0.2+: gapps-lp-google-keyboard-20151012-2-signed.zip

Binary files gapps-lp-google-keyboard-20151012-1-signed/system/app/LatinIMEGoogle/LatinIMEGoogle.apk and gapps-lp-google-keyboard-20151012-2-signed/system/app/LatinIMEGoogle/LatinIMEGoogle.apk differ

Note: Due to new security features in Marshmallow, the Google keyboard addon has been repackaged to pass Marshmallow security verification.
[Android Software Development] Deltadroid:
All apps released within the last few weeks should include marshmallow support. You can verify by checking the version number and looking on apkmirror for the supported API target level of the application.

For example, the latest version of Google Keyboard on apkmirror says:

Target Android version: Android 6.0 (Marshmallow, API 23)
[Android Software Development] dirlan2001:
Hi,

Marshmallow Gapps ? Does that mean you have somewhere an Marshmallow AOSP on the shelve too ? Love to hear about that for my GPad :)

Cheers
[Android Software Development] Deltadroid:
[MENTION=6493367]cianz94[/MENTION]

If the latest changes to the Google keyboard add-on fixed the problem on marshmallow, then I think I can fix the messenger add-on also.

The deal is that marshmallow has a new security feature which checks if certain system apk files have been changed. In lollipop, it was necessary to extract the libs from within the system apk files and put the libs in the same directory as the system app that needs them. In marshmallow, we must also pre extract the libs but we must also use an apk that is completely unmodified (ie; not removing the libs from the apk files after they have been extracted).
[Android Software Development] cianz94:
Hi! The google keyboard addon doesn't replace the stock keyboard. After the flash, the stock keyboard is deleted.

However, I Test this Gapps:

- The photos addon doesn't replace the stock gallery. After the flash, the stock gallery is deleted.

- Google Chrome replace the stock browser. It Works.

- Calendar Works

- The clock addon doesn't replace the stock clock. After the flash there is the same stock aosp clock.

The ROM is this: http://xdaforums.com/nexus-4/development/rom-6-0-android-marshmallow-pure-aosp-t3220900

EDIT:

Sorry, the CLOCK WORKS properly
[Android Software Development] Deltadroid:
If the stock keyboard is deleted, then the file names are the same as lollipop.

A few things to try to fix the Google keyboard:

- In settings --> apps (system), is Google keyboard in the list of system applications? If yes, try clearing data/cache for Google keyboard.

- is the Google keyboard enabled in input settings?

- is Google keyboard given full app ops permissions?
[Android Software Development] cianz94:
The keyboard doesn't in the list of system applications :(

I download it again from playstore because it was only present Japanese IME after the flash.
[Android Software Development] Deltadroid:
Google keyboard works with your marshmallow ROM if you download it from play store?

I'm not sure why Google keyboard add-on is not showing up in the list of installed system applications in Settings --> Apps (All). That is definitely the reason why it is not working with marshmallow aosp.

There could just be a problem with aosp 6.0 and replacing the stock keyboard.

The last suggestion I have is to try a factory reset with the Google keyboard add-on installed.
[Android Software Development] cianz94:
Yes, if I download it from playstore it works. I wait for fix :(
[Android Software Development] Deltadroid:
I think that in order to replace the stock keyboard with the Google keyboard on marshmallow, the system can not boot with the stock keyboard installed. Once marshmallow boots up with the stock keyboard, it can't be replaced.

If you flash aosp 6.0, gapps base, and Google keyboard add-on, then factory reset, then boot to the system, the Google keyboard should show up as a system app in the settings.
[Android Software Development] cianz94:
This procedure also works with other applications? for example, photos etc?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Android Software Development] Deltadroid:
The photos add-on may still need to be fixed the same way as the latest keyboard add-on.

Replacing the stock keyboard and the stock launcher have always had issues.
[Android Software Development] cianz94:
Thanks for your support.

Inviato dal mio LG-V500 utilizzando Tapatalk
[Android Software Development] iks8:
I have issues with google camera from this thread but when I install it with google play it works fine :/

I can open camera but swiching to video causes fc
[Android Software Development] Deltadroid:
Maybe there is a problem with that new version of Google camera with your ROM.

Here is a link to the previous version that is currently the latest version (2.5.052) that is installed by play store. This should work.

http://xdaforums.com/showpost.php?p=61314225&postcount=904
[Android Software Development] iks8:
Now it's working fine thanks a lot ;)
[Android Software Development] jerryshaw12:
After flashed google camera (L 5.1.1) why google play store didn't say installed?

~~(8:> android@root:/xiaomi/armani
[Android Software Development] Deltadroid:
The problem is that some add-ons must be initially installed after a factory reset on a clean install that has not booted to the system yet. For example, if the ROM is booted to the system with the stock camera installed, then data and cache are created for the stock camera. This will later on cause problems for the play store recognizing that Google's camera is part of the system when it replaces the stock camera.

The solution is to just factory reset. All of the Google apps that have replaced stock apps will then show up as installed by Google play store.

Once a stock application is already replaced by a Google application, it can be updated without any problems by either flashing another update via the recovery or just by the play store. This problem only occurs with the initial replacement of the stock application.

The trick is to never let the system boot with the stock camera, keyboard, clock, or launcher if it is going to be replaced by it's equivalent Google application.

The play store seems to only have this issue with the stock camera, keyboard, clock, and launcher.
[Android Software Development] Deltadroid:
It appears that both razor and shamu factory images have updated to LMY48T, so, I will update the 5.1.1 base gapps package using these new images with the next release (tomorrow).

Thanks for bringing this to my attention. I did not think Google would update all lollipop factory images again after they moved to marshmallow.
[Android Software Development] Barbiox Dogg:
[MENTION=5227588]Deltadroid[/MENTION] can you please kindly tell me what apps are included in Marshmallow Base Gapps package?
[Android Software Development] Deltadroid:
Google play services (dpi specific), play store, contacts sync, and face unlock.

Note: calendar sync is not included anymore
[Android Software Development] Barbiox Dogg:
Thanks for the quick reply.
[Android Software Development] itsnie:
Dev can you add tag google to repleace stock tag app ?
[Android Software Development] Deltadroid:
Yes. I will make one for Lollipop and Marshmallow.
[Android Software Development] itsnie:
But with my stock 5.1.1, tagGoogle have installed by default ?
[Android Software Development] Deltadroid:
You are right. I had to just extract Google Tag from the new factory images.
[Android Software Development] itsnie:
You rock dev thangs :D
[Android Software Development] MauroRTR:
YouTube 10.40.58-108058130 (All DPI)

YouTube 10.40.58-108058132 (240 DPI)
[Android Software Development] aben92:
Base Gapps link shows server error 500 [emoji31]
[Android Software Development] Deltadroid:
Maybe AFH just needed a few minutes to sync the files on their servers. The link seems to be working.
[Android Software Development] Barbiox Dogg:
[MENTION=5227588]Deltadroid[/MENTION] i really like your gapps alot however can I flash the Additional Lollipop gapps addons on a Marshmallow ROM?
[Android Software Development] Deltadroid:
Yes, when Google is finished rolling out marshmallow updates, then all the lollipop add-ons will be compatible with marshmallow, except for a few specific marshmallow add-ons that are marshmallow only. For example, there is a lollipop exchange add-on, but since there is also a marshmallow exchange add-on, then use the marshmallow one.

All of the lollipop add-ons that have been updated this month should also be marshmallow compatible.

Edit: I will create links under the marshmallow add-ons that point to the working lollipop add-ons to help eliminate confusion. I can understand how it is difficult to tell at this moment which lollipop add-ons work with marshmallow too.
[Android Software Development] Deltadroid:
I have updated the links on the OP for all known Standard and Additional Marshmallow addons that target the new Marshmallow API.

Note: Because of new Marshmallow security features, it is still necessary to manually give new system applications privileges via App Ops after installing Marshmallow addons.
[Android Software Development] Deltadroid:
Search

Google Search has been updated to version 5.5.26.19.arm-300552016

Google Search addon for 4.4.4: gapps-kk-google-search-20151021-1-signed.zip (replaces stock quicksearchbox)

Google Search addon for 5.0.2+: gapps-lp-google-search-20151021-1-signed.zip (replaces stock quicksearchbox)

Binary files gapps-kk-google-search-20151020-1-signed/system/lib/libcrashreporter.so and gapps-kk-google-search-20151021-1-signed/system/lib/libcrashreporter.so differ
Binary files gapps-kk-google-search-20151020-1-signed/system/lib/libcronet.so and gapps-kk-google-search-20151021-1-signed/system/lib/libcronet.so differ
Binary files gapps-kk-google-search-20151020-1-signed/system/lib/libgoogle_speech_jni.so and gapps-kk-google-search-20151021-1-signed/system/lib/libgoogle_speech_jni.so differ
Binary files gapps-kk-google-search-20151020-1-signed/system/lib/libgoogle_speech_micro_jni.so and gapps-kk-google-search-20151021-1-signed/system/lib/libgoogle_speech_micro_jni.so differ
Binary files gapps-kk-google-search-20151020-1-signed/system/lib/liboffline_actions_jni.so and gapps-kk-google-search-20151021-1-signed/system/lib/liboffline_actions_jni.so differ
Binary files gapps-kk-google-search-20151020-1-signed/system/priv-app/Velvet.apk and gapps-kk-google-search-20151021-1-signed/system/priv-app/Velvet.apk differ

Binary files gapps-lp-google-search-20151020-1-signed/system/priv-app/Velvet/lib/arm/libcrashreporter.so and gapps-lp-google-search-20151021-1-signed/system/priv-app/Velvet/lib/arm/libcrashreporter.so differ
Binary files gapps-lp-google-search-20151020-1-signed/system/priv-app/Velvet/lib/arm/libcronet.so and gapps-lp-google-search-20151021-1-signed/system/priv-app/Velvet/lib/arm/libcronet.so differ
Binary files gapps-lp-google-search-20151020-1-signed/system/priv-app/Velvet/lib/arm/libgoogle_speech_jni.so and gapps-lp-google-search-20151021-1-signed/system/priv-app/Velvet/lib/arm/libgoogle_speech_jni.so differ
Binary files gapps-lp-google-search-20151020-1-signed/system/priv-app/Velvet/lib/arm/libgoogle_speech_micro_jni.so and gapps-lp-google-search-20151021-1-signed/system/priv-app/Velvet/lib/arm/libgoogle_speech_micro_jni.so differ
Binary files gapps-lp-google-search-20151020-1-signed/system/priv-app/Velvet/lib/arm/liboffline_actions_jni.so and gapps-lp-google-search-20151021-1-signed/system/priv-app/Velvet/lib/arm/liboffline_actions_jni.so differ
Binary files gapps-lp-google-search-20151020-1-signed/system/priv-app/Velvet/Velvet.apk and gapps-lp-google-search-20151021-1-signed/system/priv-app/Velvet/Velvet.apk differ
[Android Software Development] Rock-86:
Can you add Google Now Launcher Addon (version 1.2.large) to 6.0 addons? :)
[Android Software Development] Deltadroid:
Yes, tonight I will add 1.2.large and 1.2.small in the same package and automatically install the best version depending on the dpi of the device.
[Android Software Development] vjtigas:
Great work!
[Android Software Development] iks8:
I installed gapps after booting rom first and now some of apps aren't recognized in play store as installed (camera, keyboard, music and clock). Do you think there is a way to fix it or I need to reflash rom?
[Android Software Development] Deltadroid:
The only way I know to fix those apps showing as installed in play store is to factory reset. You don't need to flash anything over again. Just reboot to recovery and select standard factory reset and then reboot to the system.

You could try just clearing Dalvik cache and cache, but I don't think that is enough. In the past, the only way I was able to have play store recognize the apps as installed (camera, keyboard, launcher) was with a factory reset.

This only occurs with the initial replacement of those apps. Once they are replaced before the initial boot to system, flashing more updates is not a problem.

Edit: if formatting Dalvik cache and cache does not fix it, then there must be something in the data partition that is confusing the play store and preventing it from recognizing those apps as installed. The apps that have these issues share the same data name and settings as the Google versions. That is why this happens when replacing those specific system apps.
[Android Software Development] iks8:
Wipe cache isn't fixing that issue so I had to make factory reset. Now everything is fine. Thanks for fast help!
[Android Software Development] vjtigas:
Google now releases beta versions for the Google app. Also, I already got this update from the Play Store http://www.apkmirror.com/apk/google...ebview-47-0-2526-26-arm-android-apk-download/
[Android Software Development] Deltadroid:
Webview Beta

Google Webview Beta has been updated to version 47.0.2526.26-252602600 for lollipop and marshmallow.

Google Webview Beta addon for 5.0.2+: gapps-lp-google-webviewbeta-20151023-1-signed.zip (replaces stock webview)

Binary files gapps-lp-google-webviewbeta-20151008-1-signed/system/app/GoogleWebview/GoogleWebview.apk and gapps-lp-google-webviewbeta-20151023-1-signed/system/app/GoogleWebview/GoogleWebview.apk differ
Binary files gapps-lp-google-webviewbeta-20151008-1-signed/system/app/GoogleWebview/lib/arm/libwebviewchromium.so and gapps-lp-google-webviewbeta-20151023-1-signed/system/app/GoogleWebview/lib/arm/libwebviewchromium.so differ
[Android Software Development] Omegadrive:
Problem with latest base gapps (10/22) in lollipop, get constant crashes of Google play services (even after data clear), flashed previous one again and all working fine.

Here is the log:

https://www.dropbox.com/s/55gk5iqowrsatnb/2015-10-22-23-27-10.txt?dl=0
[Android Software Development] Deltadroid:
The lollipop base gapps (10/22) for 5.1.1 is working fine with my cm 12.1 rom. I just dirty flashed the new version of base gapps on top of the old base gapps.

Although, there could definitely be bugs in the new version of play services. If you are having problems with the new base gapps package, you can dirty flash the previous version of base gapps back to downgrade.

Which rom are you using?

Edit:

You could help me determine if the problem is with play services itself or the way play services was packaged.

1) flash back the last version of lollipop base that was working with your rom (10/20). No more crashes when booting to the system.

2) manually install the latest version of Google play services to the data partition. The link below assumes the rom you are using is 640 dpi:

http://www.apkmirror.com/apk/google...es-8-3-00-2353383-238-3-android-apk-download/

3) reboot

If there are still crashes after upgrading play services to data partition, then we know the problem is with the version of play services and not a lollipop base gapps packaging problem.
[Android Software Development] saenanme:
I have installed this morning the base package this morning with the today cm12.1 nightly and last ak kernel in my opo without problems.

Only one fc after booting. After this everything works fine.

As always, thanks for your work.

I'm waiting to official cm13 ...

Regards
[Android Software Development] :
Play Store forces closing once in a while with the new 5.1.1 package.
[Android Software Development] Deltadroid:
It appears that Google has pushed Google play services 8.3.00 to everyone, so it should be the latest stable version. Going back to previous base gapps package will downgrade Google play services to 8.1.15, but it will probably update itself automatically to 8.3.00 anyway. The only change in the latest base gapps is Google play services.
[Android Software Development] Omegadrive:
Have latest CM12.1 (10/21)

Will try that and let you know

Update:

Installed apk (since I have auto update disabled) and cleared data, had constant crashes like crazy. All crashes started with this in log:

10-23 10:46:15.543 E/AndroidRuntime(30164): FATAL EXCEPTION: UlrDispSvcFastTask

Just in a hunch I checked the Play Services permissions, the only things that didn't had permission for was "keep awake", which I always have disabled cause of previous battery drain bugs.

As soon as i enabled keep awake the crashes stopped, this is weird.

I'm going to uninstall the update and install the zip and see how it goes now.
[Android Software Development] Deltadroid:
Good to hear that. One of the things that was fixed in new Google play services 8.3.00 was battery drain from wake lock.
[Android Software Development] :
Keep awake made the crashes stop here as well. Did you enable wake up as well?
[Android Software Development] Omegadrive:
All is enabled now, only had that disabled
[Android Software Development] Deltadroid:
Play Services (240 dpi) for Marshmallow

Google has just released a 240 DPI version of Google Play Services 8.3.00, so this is now included in the Marshmallow Base Gapps package. This addition will install an optimized version of Google Play Services for Marshmallow devices using 240 DPI.

8.3.00_(2353383-430)-8300430 (nodpi) **default**

8.3.00_(2353383-434)-8300434 (240 dpi)

8.3.00_(2353383-436)-8300436 (320 dpi)

8.3.00_(2353383-438)-8300438 (480 dpi)

Marshmallow Base Gapps package for 6.0.0: gapps-600-base-20151022-2-signed.zip

diff -ru '--exclude=CERT.RSA' '--exclude=CERT.SF' '--exclude=MANIFEST.MF' gapps-600-base-20151022-1-signed/META-INF/com/google/android/updater-script gapps-600-base-20151022-2-signed/META-INF/com/google/android/updater-script
--- gapps-600-base-20151022-1-signed/META-INF/com/google/android/updater-script	2008-02-29 02:33:46.000000000 +0100
+++ gapps-600-base-20151022-2-signed/META-INF/com/google/android/updater-script	2008-02-29 02:33:46.000000000 +0100
@@ -25,8 +25,8 @@
run_program("/tmp/install-optional.sh", "");
package_extract_dir("optional/gms/0", "/tmp/gms");
run_program("/tmp/install-core-0.sh", "");
-# package_extract_dir("optional/gms/4", "/tmp/gms");
-# run_program("/tmp/install-core-4.sh", "");
+package_extract_dir("optional/gms/4", "/tmp/gms");
+run_program("/tmp/install-core-4.sh", "");
package_extract_dir("optional/gms/6", "/tmp/gms");
run_program("/tmp/install-core-6.sh", "");
package_extract_dir("optional/gms/8", "/tmp/gms");
Only in gapps-600-base-20151022-2-signed/optional/gms: 4
diff -ru '--exclude=CERT.RSA' '--exclude=CERT.SF' '--exclude=MANIFEST.MF' gapps-600-base-20151022-1-signed/scripts/install-core-0.sh gapps-600-base-20151022-2-signed/scripts/install-core-0.sh
--- gapps-600-base-20151022-1-signed/scripts/install-core-0.sh	2008-02-29 02:33:46.000000000 +0100
+++ gapps-600-base-20151022-2-signed/scripts/install-core-0.sh	2008-02-29 02:33:46.000000000 +0100
@@ -2,8 +2,7 @@

LCD=$(grep ro.sf.lcd_density /system/build.prop | cut -d "=" -f 2);

-#if [ ! "$LCD" == 240 ] && [ ! "$LCD" == 320 ] && [ ! "$LCD" == 480 ]; then
-if [ ! "$LCD" == 320 ] && [ ! "$LCD" == 480 ]; then
+if [ ! "$LCD" == 240 ] && [ ! "$LCD" == 320 ] && [ ! "$LCD" == 480 ]; then
echo "Installing default."
cp -f /tmp/gms/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk /system/priv-app/PrebuiltGmsCore/
fi