yashsingh1/xdaforums huggingface dataset:
[Android Software Development] MastahF:
A note for everyone: Tomorrow's builds will see some changes. Because Google decided not to bundle some Google Apps on the newest Marshmallow Stock images, we follow suit. That means that the renewed StreetView app and Google Earth are no longer part of Stock. Also Android Pay is removed from the package, since it is essentially of no practical use to anyone flashing a GApps package anymore. If you still want those apps, you should use the new 'Super' package.

The Super package will ONLY be built for 5.1+.

This Super package contains more than the regular Stock package did, it also contains all the regional keyboards, it contains GCS and Project Fi, Android For Work, Google Apps Device Policy and Google Translate.

In the coming days the Aroma package will switch to being based on this Super package when [MENTION=4964524]raulx222[/MENTION] will find time to update the configurations, for now it will be based on the slimmed down Stock package.

The Nano package will also contain the FaceUnlock and FaceDetect features.

The Full package loses 'Messenger'.

This sums up the changes for now. Marshmallow builds are still not ready, because of various issues posed by new security mechanisms Google did put in place. This means that some adjustments have to be made to how e.g. the APKs are put on /system/ and permissions are granted. It is really fishy and difficult, but luckily most of the GApps packagers are working together on this like [MENTION=1277872]dankoman[/MENTION] [MENTION=2699658]xanaxdroid[/MENTION] [MENTION=5227588]Deltadroid[/MENTION] @BaNkS and our own dev [MENTION=3989659]Rapper_skull[/MENTION] (sorry for those I have missed, I have not everyone's XDA handle) to sort all issues out. It seems that some part would have to be fixed ROM-side too, because AOSP is not willing to directly 'trust' the GApps packages and grant it the necessary permissions.
[Android Software Development] Dkadr1:
Good to know! :)

By the way, any update on what's the exact function of ConfigUpdater? Some packagers include it, some doesn't. But I don't know what is its purpose.

GCS is only useful with Project Fi, isn't it?

Enviado desde mi Nexus 7 mediante Tapatalk
[Android Software Development] MastahF:
GCS is indeed meant for Project Fi.

ConfigUpdater will be included when we are ready for Marshmallow (progress here: https://github.com/opengapps/opengapps/commits/marshmallow ).
[Android Software Development] raphaelnariga:
I prefer to download the Aroma, it's good for me to choose which app I'd want to have on my phone, since I don't use 85% of these Gapps.
[Android Software Development] Dkadr1:
Hi again [MENTION=6404745]MastahF[/MENTION],

I was testing the Speech files with the gapps-config file, and I noticed something.

If I exclude Speech, it does not get installed in system and it gets downloaded in data from the Google App. This is OK, as intended.

But if I don't use the gapps-config file and it gets installed in system as expected, then later I receive a notification telling me that a new version is available to download. So I suppose that the version installed in system is an old one. When the new version is installed is it installed in data?

The most recent version of English US is #206, and it sizes 44MB. If I don't have Speech pre-installed those 44MB get downloaded, if it's pre-installed and gets updated only 18MB are downloaded. Don't know which partition they go in each case...

*Edited image because it was shown too big*
[Android Software Development] MastahF:
Thank you for that information. I had no clue that it was outdated. Where were you able to get that version info about the English US?
[Android Software Development] Dkadr1:
I tried uploading the image from Tapatalk but it shows enormous. Here it is attached.

The message says "Version 206 available (download size 17,57MB)"

.

Enviado desde mi Nexus 7 mediante Tapatalk
[Android Software Development] MastahF:
Ok, thanks. It should be updated in tomorrow's build: https://github.com/opengapps/all/commit/3e4c3ec467dfae56f873fa9589d3d90cf2929389
[Android Software Development] MastahF:
Another addendum, we decided to drop the 'keybdlib' that added Swype capabilities to the AOSP keyboard, because it gave issues to quite a lot of users. Instead we will drop the 'clean install' requirement from the Google Keyboard installs, hoping that it won't pose any unexpected issues by now anymore (like it could give in the past).
[Android Software Development] MastahF:
It appears because AOSP keyboard is incompatible with the newest Google Keyboard libs. So we decided to drop it (the post just before yours) because of the issue becoming more common now. So tomorrow's build (14 Oct) should not give you this trouble anymore.

I am still interested in the FCs you got when installing stock. Do you have any logcats of those?

PS: The debug logs of the installation you can find in the same location where you had the installer zip.
[Android Software Development] mybeshoo:
Thank God not only me :)

Regarding the Stock , well no i dont but i will be more than happy to make it for you , how can i uninstall the Nano and install the stock but please dont tell me i need to format my device :):D
[Android Software Development] androcraze:
If the ROM doesn't have the swipe feature enabled, you just can't add the library:

http://xdaforums.com/nexus-4/general/guide-how-to-enable-googles-gesture-t2012628

Or are you talking about something else?

If not, will older versions of the library still work? I think most users will probably care about usability rather than being current.... But then again (if that were the case) , you'd only have to build GApps ONCE for each Android version....
[Android Software Development] kchaisu:
Thanks MastahF for your kind info. I also have an issue on Keyboard stop working when I installed Open gapps 20151013 Pico 511.So it ended up to going no where without keyboard. I have a debug log file, but I could not find a way to upload. Thank you very much for your kind contribution.
[Android Software Development] LordNerevar:
You're right. It does appear to work with a clean install. Assuming upgrades to these 3 apps work from the play store, this should be fine if you're only targeting clean installs. I'm not really sure what happened with my dirty install, but I was able to recover so no big deal.

Good luck with the project. It seems very well documented and professional!
[Android Software Development] imcrazyz:
Calendar sync has stopped working on the 13th build pico gapps, instead of popup of error, by noticing my calendar event doesn't appear on my calendar widget. Previous version was totally fine.

Anyone having the same issue?
[Android Software Development] MastahF:
Yup, we are exactly talking about that. And it used to work as described in that post. But somehow, it did break recently in e.g. Cyanogenmod. And while we we hardly received any feedback about problems before, it became suddenly much more frequent. [MENTION=1763928]MNBooZe[/MENTION] did do some testing for us on his device with current ROMs and the various library versions, and the conclusion was that either the libs made the keyboard crash, or it did not crash but swype would not work. The sum of all this information did decide us to drop it.

Instead, we will now enforce no clean installs for Google Keyboard anymore. Because a year ago when Keyboard was still new, there were many problems with it on dirty installations. But Google is now several iterations further with development of Keyboard, so I am willing to take the gamble that those problems could be resolved by now. We will see how it behaves, if it still gives trouble on dirty installations, we might choose to enforce clean installations again.

Calsync has not been updated for a month: https://github.com/opengapps/all/tree/master/app/com.google.android.syncadapters.calendar/15/nodpi

Maybe an issue on Google's side or on your ROM?

Otherwise please try to capture a logcat if any errors related to this problem appear in it.
[Android Software Development] ADB100:
Hangouts 5.0?

I have been offered Hangouts 5.0.104885319 from the Playstore and can see this was released on 12th October so assumed this would already be in the GApps for Android 5.1.

It appears version 4.2.102354210 is still the current version. Will this get updated soon or is it being left out as its 'targeted' at Android 6.0?

Andy
[Android Software Development] Dkadr1:
Facelock gives FC when trying to set it in 5.1

Are you including the Marshmallow files? Because in app version it says 6.0
[Android Software Development] imcrazyz:
Not sure about it, but I do trust the work from cm team.

*I'm using the official cm12.1 nightly.

Btw, thanks for acknowledging.

EDIT: Is it possible to download the previous version of gapps? I really find the previous versions are more useful and stable.
[Android Software Development] MastahF:
Actually 5.0 is in the package since the 13th. I just have to update the version information script, since it cannot handle the situation where higher SDK versions are outdated compared to lower SDK versions. The package builder does pick the highest applicable version correctly, though. So you can be sure of it to be in the package :)

We use the newest Facelock available, which is indeed version 6.0 but should be completely backward compatible. But it is known that Facelock is broken on *a lot* of devices. So did Facelock ever work for your before? If yes, could you give a logcat of the FC?

Yes, we also trust the work of CM. But our suspicion is just that binary compatibility is broken, so we better leave the original CM keyboard libs then in place, instead of destroying their functionality with the Google libs that were never officially meant to be used that way.

You can fetch the old packages from the Github releases pages. They are organized per CPU architecture and in respective repos you will find the releases.

Also, you can of course build your own package using the source and add the 'ingredients' you like and find most stable.
[Android Software Development] Dkadr1:
Yes, it worked before. Now it does not even open the camera when trying to save a face.

Here is the logcat:

java.lang.NoSuchMethodError: No virtual method checkSelfPermission(Ljava/lang/String;)I in class Landroid/app/Activity; or its super classes (declaration of 'android.app.Activity' appears in /system/framework/framework.jar)
at com.android.facelock.SetupInstructionsScreen$SetupInstructionsFragment.onClick(SetupInstructionsScreen.java:121)
at android.view.View.performClick(View.java:4789)
at android.view.View$PerformClick.run(View.java:19881)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5294)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
[Android Software Development] stephendt0:
Hey guys, got a weird issue here. I'm using an AOSP based ROM called Androium 2.1.3 on the Lenovo K3 Note. It's a port from the Zapo 920.

If doesn't matter what ARM64 Gapps build I flash (even if I remove the Gapps manually), it will not go past a black screen with the status bar after boot. However, this only happens if I flash it directly after a clean install, or if I do a factory reset. If I let the ROM boot, then reboot and flash the Gapps, then it works fine (until the next factory reset). Any idea on what could be causing this and what could be done to avoid this? Reason I really want to be able to flash these Gapps is due to the fact that the stock Google Apps doesn't work with OK Google commands. Flashing these Gapps fixes this problem.

Advice would be appreciated :good: can submit logs and screenshots if needed.
[Android Software Development] :
Yes I had the same problem. I flash the ROM then I flash the GApps when I boot the ROM up its a black screen and can't pass it until I do a factory reset. [MENTION=6404745]MastahF[/MENTION] told me that the system was mounted read-only that's why there isn't a single Google app on my phone after the factory and reset.

Solution: Yesterday while I was trying I flashed the ROM then I went to Mounts ( in TWRP ) and I found that the system was already mounted so I unmounted it and unmounted cache and it solves the problem
[Android Software Development] dannyella:
Something in new releases is causing AOSP keyboard to crash in CM. Flashing TK gapps fixed it. I would really hate to stop using Open gapps. Please fix.:(
[Android Software Development] foresto:
Gesture typing is broken

I just tried open_gapps-arm-5.1-pico-20151014 with a couple recent CyanogenMod nightly builds, and discovered that gesture typing is broken.

The Gesture Typing option is available and enabled in Android Keyboard (AOSP) settings.

/system/lib/libjni_latinime.so exists, md5sum 869ef480a0cc869a455ae08eabd9d734.

Still, gesture typing doesn't work.

Gesture typing works fine when I use cgapps instead of opengapps.
[Android Software Development] Ashish.akc:
tried installing stock package on yureka(tomato) over latest AICP nightly but that gave me error 30. it was a clean install though [MENTION=6404745]MastahF[/MENTION]
[Android Software Development] MastahF:
Actually we removed in 14-10 the gesture typing libs from AOSP keyboard, because there were so many issues with it. So if you do a clean install on /system/ there should not be any gesture typing nor any AOSP keyboard crashes anymore.

If you do want gesture typing, please install the Google Keyboard, which is for now also set to be allowed on 'dirty installs'.

Please post your debug log.
[Android Software Development] MastahF:
Could you try to replace the Facelock apk on /system/ with this old version and see if the error still appears? https://github.com/opengapps/all/bl...com.android.facelock/15/nodpi/22.apk?raw=true
[Android Software Development] MastahF:
Could you attach your debug log? And would you be willing to reflash to flash Open GApps with WebView excluded (and reflash your ROM afterwards to restore the original webview) and check if those errors then still appear?
[Android Software Development] Ashish.akc:
can you please tell me how to do that. i'd love to provide you the logs so that the issue can be solved as i badly want to use your gapps
[Android Software Development] chewdaniel:
i could but it's gonna take at least another 20 hours or so since i'm off to bed now and need to work :p

i could wipe /system, flash rom, and opengapps without webview so don't have to flash twice (?)

anyway, FWIW, i'm using the stock build from 10th Oct (i don't have 11-13) without any issues on a LG-D802 on latest CM12.1 nightlies.

thanks again :)
[Android Software Development] foresto:
Where can I find details on the issues you found with gesture typing on the AOSP keyboard? Is there some way to re-enable it? If not, I guess I'll go back to cgapps.

The main reasons I wanted opengapps were to get rid of unnecessary google junk and to minimize security/privacy risks (either from deliberate data collection or from bugs). Google Keyboard's size and excessive permissions make it both bloat and a security risk, so if opengapps requires it in order to preserve gesture typing, then opengapps is not a viable option for me.
[Android Software Development] Dkadr1:
I did it. It works again. I set the same permissions that the previous one had. Is that correct?

The libraries don't need to be touched?
[Android Software Development] MastahF:
You can find the debug log (a tar file) in the directory where the Open GApps zip was located.

Yes, you can wipe /system and then flash. I also need to go to sleep now, so no hurry.

The issues were from testing with AOSP ROMs ourselves, but also multiple reports from CM users that recent CM versions had become incompatible. I don't know why (I did not look into the changed code on CM's side) but I do get the feedback, and if it gives more trouble than benefits to most of the users, I will not add it as default anymore.

I am sensitive to users that still want it, so I will look if we can make it an optional feature that can be activated in gapps-config: https://github.com/opengapps/opengapps/issues/141

From security perspective though, please be noted that nobody exactly knows what is in those libs besides Google, and that also the built-in keyboard as a system-apk has FULL permissions (and so do those libs) to do ANYTHING on your device. So if you are in a security sensitive setting, please be aware of this. Of course, (but brings same security issues like any non-open source keyboard implementation) there are other 3rd party swype-enabled keyboard apps, not only from Google.

That is correct. Thank you for testing. I know that there is then something wrong with the app. I will track your issue here: https://github.com/opengapps/opengapps/issues/142
[Android Software Development] foresto:
That's a sensible approach. Thank you!
[Android Software Development] brinsleyparagao:
in wiki page ( https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options ) the news apps and super pakage no apear yet.

So, when the news is in this page?
[Android Software Development] xenovyzarz:
open_gapps-arm-5.1-pico-20151013 installation and catlog attached,

1) got installation error (code 20), but after reboot into twrp again finally manage to install gapps...

remark : i wiped dalvik, cache and system before flashing.

2) keyboard fc every few seconds...

hope this help ><

open_gapps-arm-5.1-pico-20151015

keyboard still fc, another logs attached.
[Android Software Development] kisman72:
Installed todays OpenGapps 1015 on my cm bacon nightly 1015.

Got no swift key any longer.

Is it a cm or OpenGapps bug ?

thx
[Android Software Development] Micalus:
1015 gapps still keyboard FC but whatever installed SwiftKey and deleted Android keyboard from system.

Sent from my ONE A2003
[Android Software Development] kisman72:
sorry, don't understand you. What do you mean with FC?

Also, do you mean OpenGApps 1015 is overwriting the android keyboard and that's why swiftkey is not working any longer?

Is there a possibility to download an old OpenGApps paket?

ARM32-5.1-pico

[MENTION=5209639]Micalus[/MENTION] or please write a PM in german ;) thx
[Android Software Development] dannyella:
But what happened tho? Gesture typing was working without any crash before 10/10 gapps.. :confused:
[Android Software Development] MastahF:
Could you wipe your /system/ and reflash your ROM before flashing the GApps? That should restore the original AOSP keyboard libs. (you won't lose any data)

We received mixed results from people using different ROMs whether gesture typing was still working. And our own tests did show it was broken with e.g. AOSP ROMs.

I am sorry for the issues people experience at the moment. I will try to write a patch ASAP that will allow the optional installation of the swypelibs.
[Android Software Development] MastahF:
Could those who would like to see the swype libs back in the package please try this build and use the line 'swypelibs' in a gapps-config file and report back if it works.

If it works, it will go into mainline ASAP.
[Android Software Development] MastahF:
Ty for the heads-up, I now updated the page. But I can really use some help with maintaining the wiki, since it distracts from the dev work itself.
[Android Software Development] gericom.hummer:
Todays arm 5.1 aroma 15 October 2015 package act like the new super package - e.g. installs apps which are not mentioned in aroma, and could not deselect them, like Project Fi, korean, hindi, japanese input, Android for work, and others...
[Android Software Development] chewdaniel:
[MENTION=6404745]MastahF[/MENTION]

Downloading 15/10 now but i see in the changelog the WebView is still the same version. Anyhow I'll give it a try and see how it goes :)
[Android Software Development] chewdaniel:
[MENTION=6404745]MastahF[/MENTION]

same thing. excluded webview. running 1510 build together with 1510 CM12.1....

for some reason debug log and opengapps log are 0 bytes in size :/

EDIT:// reverted from 1510 to 1010 and now getting all sorts of gapps FC. logcat shows sqlite cannot downgrade database or something..... sigh.... i'll try a clean flash this time :)

EDIT2:// 1510 CM12.1 and OpenGapps on a clean fullwipe install.... GPS FC during setup process can't even get to the google login screen. no logcat since adb wasn't even enabled yet... fullwipe again and reverted to 1010 with no issues...
[Android Software Development] MastahF:
Thank you, indeed there was a small error in the code, which currently based Aroma on super instead of stock. It should be fixed for tomorrow: https://github.com/opengapps/opengapps/commit/5dfd5a31a9c7c46d183f6a0ee095f26233c10a7e
[Android Software Development] MastahF:
All pico flashers, I have another updated package with swypelibs: https://www.androidfilehost.com/?fid=24052804347838107

If you use a gapps-config and add swypelibs as a keyword to it, it should install the libs. But this version should also automatically install the swypelibs if they were ever flashed before, to not leave your keyboard in a broken state. Please test and report back! I would really like to merge this in if I get positive feedback within the next couple of hours, so that it can be in tomorrow's build!
[Android Software Development] Ashish.akc:
i didnt find any of the tar files. anyting else i can do?
[Android Software Development] MastahF:
Sorry, I was also a bit sleepy. You got Error 30, so the installer never continued and there is no debug log (sorry!).

Error 30 indicates that your recovery does not support transparent compression, while your ROM does use this.

You need to update your recovery. Other people have had the same problem, maybe this can help you: https://github.com/opengapps/opengapps/issues/99
[Android Software Development] Ashish.akc:
updating the recovery solved the previous problem but installing the gapps this time gave error 70 and after reading about it i found that this was because my system memory was not enough. since i want to use the stock gapps any workaround for that?
[Android Software Development] MastahF:
Use a gapps-config file and choose to skip the installation of some apps: https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options#the-gapps-config-file
[Android Software Development] Ashish.akc:
i tried adding a config file but that didn't made any difference probably because i did something wrong :confused:

could you please create a demo version for me which excludes Books and CloudPrint as well as removal of BasicDreams. This will give me idea on how to effectively use the config file. (Sorry if it seems silly but am trying to learn something different although perfectly noob:D:p )
[Android Software Development] MastahF:
name the file .gapps-config and put in the same directory as where the open gapps zip file is.

Then put in the file:

Exclude
Cloudprint
Books

BasicDreams

No problem to help a noob once in awhile. But you can thank me for the effort by voting [removed]

it is in Dutch, but it is just clicking the radio button and at the bottom filling in your e-mailaddress, you'll get a confirmation e-mail where you'll have to click a link.

Won't cost you anything, but you'll be helping out a friend that needs the votes ;)
[Android Software Development] Ashish.akc:
removed all these apps but still got the issue. i might have to remove even more

Exclude
CameraGoogle
Cloudprint
Ears
Fitness
Movies
NewsStand
NewsWidget
Books

and yeah i did what you told but didn't receive any email yet
[Android Software Development] kchaisu:
This version of Open Gapps has solve the problem on Android keyboard FC. Thanks for your contribution.