[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices

[kamalgrewal]

How i create gapps-config.txt file

I want to install Pico gapps + google now launcher
I downloaded stock gapps package
Device moto e : Rom Mokee open source

 

[MultiPDev]

Hey guys I can't download the gapps, I press the red button and it does nothing. I try to download from my smartphone.

 

[mcfouch]

All is explain in the wiki https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options and there are lots of examples with comments inside in this thread.

 

[niks255]

Google Keyboard is not listed as installed in Google Play. Why?
Tested with ARM package.

 

[abrakadabra_srb]

Building AOSP with opengapps included

I'm trying to build AOSP 6.0.1 for my nexus 5 so I followed the github tutorial on how to include opengapps in it. Build goes almost to to the end when it breaks because of system.img being larger then expected:
error: failed to build out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system.img from out/target/product/hammerhead/system
Out of space? the tree size of out/target/product/hammerhead/system is (MB):
1266 out/target/product/hammerhead/system
The max is 1024 MB.

I am using GAPPS_VARIANT := stock in my device.mk which should mean that the build should be exactly the same as the prebuilt image we can download from google site right? How come I get bigger system partition error then? What im trying to do is to make a custom build from scratch so that it looks like the one I have on my nexus right now (full clean aosp build, all gapps on it). I am yet to try building it with Mini or Micro package, but I wanted to ask for help and clarification on whats going on with my build

Thanks in advance

 

[MastahF]

Thank you for your help!
Also sorry to bug you again, but you do plan on integrating Google Dialer right? For now I'll just install via Play Store, but what's the best way to get rid of 2 dialers?

Yes, in the future it will be added for devices that are compatible. For now it is best to use the universal removal feature to delete the aosp dialer's folder.

I'm trying to build AOSP 6.0.1 for my nexus 5 so I followed the github tutorial on how to include opengapps in it. Build goes almost to to the end when it breaks because of system.img being larger then expected:
error: failed to build out/target/product/hammerhead/obj/PACKAGING/systemimage_intermediates/system.img from out/target/product/hammerhead/system
Out of space? the tree size of out/target/product/hammerhead/system is (MB):
1266 out/target/product/hammerhead/system
The max is 1024 MB.

I am using GAPPS_VARIANT := stock in my device.mk which should mean that the build should be exactly the same as the prebuilt image we can download from google site right? How come I get bigger system partition error then? What im trying to do is to make a custom build from scratch so that it looks like the one I have on my nexus right now (full clean aosp build, all gapps on it). I am yet to try building it with Mini or Micro package, but I wanted to ask for help and clarification on whats going on with my build

Thanks in advance

@blystad is developer of the aosp_build; so he knows most about it.
But I can give you a general answer: on the Stock Nexus image many of the apps are not "really" included (e.g. Docs, Sheets and Slides) but only "Stubs" that directly ask to be updated with a real version from the Play Store (which will than be stored on /data/). That is why Google can add much more "default" applications to the Nexus devices without actually having the diskspace to put them there.

 

[abrakadabra_srb]

@blystad is developer of the aosp_build; so he knows most about it.
But I can give you a general answer: on the Stock Nexus image many of the apps are not "really" included (e.g. Docs, Sheets and Slides) but only "Stubs" that directly ask to be updated with a real version from the Play Store (which will than be stored on /data/). That is why Google can add much more "default" applications to the Nexus devices without actually having the diskspace to put them there.[/QUOTE]

Ok now it makes sense, its clearer for me now. I've manage to build the system with GAPPS_VARIANT := mini and it boots but play services crash until I reboot it again. Do you maybe know why is this happening on fresh boot of the device?

Never mind, found it on your github page, need a patch in source Thanks for the help and great work!

 

[niks255]

Replacing swype libs didn't help, the keyboard still crashes.

 

[MastahF]

tried 0211 build with the new pattern : gapps-config_processed.txt is empty.
I will try to ask to the maintainer of this TWRP if he can do something...

I replaced the sed line now with awk; I will hope that the awk implementation in your recovery ain't broken too: https://github.com/opengapps/opengapps/commit/043695b9ab469e906fea2991ce26bf6a99f5f311

 

[Ryuk2000]

I'm getting this error on open gapps mini arm 64 for M.
What to do ?

 

[mcfouch]

I replaced the sed line now with awk; I will hope that the awk implementation in your recovery ain't broken too: https://github.com/opengapps/opengapps/commit/043695b9ab469e906fea2991ce26bf6a99f5f311

Thanks to the team. 0214 build is OK. Awk is not suffer of the same affliction.
Ivanich, maintainer of TWRP for HTC Sensation, have build a 3.0.0 version for cm13. I will give a try to it during my next holidays.

 

[marcdw]

I'm getting this error on open gapps mini arm 64 for M.
What to do ?

I don't think that's necessarily a gapps issue. Especially if it only happens with that one app. That used to happen with some ROMs that had Layers Manager preinstalled.
Check out the link below. Layers Manager troubleshooting is in there.

https://plus.google.com/+CharG/posts/KUk1GZwnU3e

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5

 

[MastahF]

Big changes ahead: in future builds we will include our own busybox to prevent anymore issues with outdated and broken recoveries (except for the fact that we can't avoid issues if a recovery even fails to start busybox...): https://github.com/opengapps/opengapps/pull/263

 

[abrakadabra_srb]

Building AOSP with opengapps included

OK, I still have problems with permissions on a ROM with opengapps included. I took the patch from github and rebuilt the ROM but I still get:
02-16 09:04:00.348 7199 7219 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 7199
AndroidRuntime: java.lang.SecurityException: "passive" location provider requires ACCESS_FINE_LOCATION permission.

I will try to see if it will work on clean ROM without opengapps and then flashing them directly with sideload. Someone has an idea why is this permission not granted?

 

[niks255]

OK, I still have problems with permissions on a ROM with opengapps included. I took the patch from github and rebuilt the ROM but I still get:
02-16 09:04:00.348 7199 7219 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 7199
AndroidRuntime: java.lang.SecurityException: "passive" location provider requires ACCESS_FINE_LOCATION permission.

I will try to see if it will work on clean ROM without opengapps and then flashing them directly with sideload. Someone has an idea why is this permission not granted?

Remove /data/system/users/*/runtime-permissions.xml from recovery and reboot into system. Permissions will be granted correctly.

 

[MastahF]

Replacing swype libs didn't help, the keyboard still crashes.

Did the error change with the new updated libs? Or not?
If this specific ROM keeps giving errors with the stock nexus libs I would suggest using the "skipswypelibs" keyword: https://github.com/opengapps/openga...nd-Options#skip-googles-swype-library-setting

 

[niks255]

Did the error change with the new updated libs? Or not?
If this specific ROM keeps giving errors with the stock nexus libs I would suggest using the "skipswypelibs" keyword: https://github.com/opengapps/openga...nd-Options#skip-googles-swype-library-setting

The error is the same.
I solved this problem as before - replaced those swype libs with ones from google keyboard.
Does anyone else have this problem with the stock keyboard?

 

[MastahF]

The error is the same.
I solved this problem as before - replaced those swype libs with ones from google keyboard.
Does anyone else have this problem with the stock keyboard?

AFAIK most ROMs work perfectly fine with the stock libs. Could you maybe track which changes to the keyboard app your ROM does have compared to AOSP? Maybe that could help us in finding any insight and/or automatic detection of which lib should be used.

 

[JustArchi]

Are there any plans on perhaps releasing odexed versions of GAPPS?

I'm having fun with my AD and base system launches in 10 seconds after full wipe with my optimizations, I'm wondering if it's possible to ship GAPPS also in odexed versions. For non-being-updated core GAPPS taken from Nexus images it should be a simple copy paste, and for those being updated dex2oatd standalone for Linux should do.

 

[MastahF]

Are there any plans on perhaps releasing odexed versions of GAPPS?

I'm having fun with my AD and base system launches in 10 seconds after full wipe with my optimizations, I'm wondering if it's possible to ship GAPPS also in odexed versions. For non-being-updated core GAPPS taken from Nexus images it should be a simple copy paste, and for those being updated dex2oatd standalone for Linux should do.

I think that using https://github.com/opengapps/aosp_build might be a good solution for AD. It currently only supports the 'nodpi' packages, but it should be possible to add dpi-specific builds too if @blystad finds the time. aosp_build supports odexed builds.