yashsingh1/xdaforums huggingface dataset:
[Android Software Development] NZgeek:
If the problem didn't happen on older GApps versions, it probably means that Google have made a code change. If that's the case, there's not a lot that the Open GApps team can do to help. They don't write the GApps code, they just take the Google apks and bundle then into a zip.

It's also worth noting that the problem may not be the GApps themselves, especially if it's the location service that's using the battery. The location service acts on behalf of other apps, so it takes the blame for battery usage even if it's some third party app that's constantly asking for location.

I suspect that it's a third party app, given that not everyone is having the same battery drain issues.

Edit: Re-reading the thread, it sounds like the issue has been going on for a while now, and you've been disabling the wake-up permission to stop the battery drain. This is fixing the symptom, not the cause.

The first thing to check is Google's location settings. If you've got location history on then the phone will be frequently checking your location and sending it to Google. Turning this offs will help.

If it's not Google then you've got some app that's spamming location services with requests. You'll need to start freezing then one by one to find out which it is.
[Android Software Development] raptir:
Anyone having trouble with Hangouts since the last update? SMS/MMS works fine but all of my Hangouts messages are substantially delayed and seem to come in "waves" so that I will get all of my Hangouts messages at once about once an hour. I tried a different ROM with OpenGApps and it persisted, but reverted back to a factory image and it works fine.
[Android Software Development] D@rekills4:
Location requests are already turned off.

This is an issue with OpenGApps package because I have OpenGApps older package installed on two other phones and their Google Play Services app has updated but they don't have this issue. I have disabled wake up and keep awake on them as well.

It's only an issue with flashing the OpenGApps packages with the last two weeks I guess.

And regarding you saying that I fixed the symptom and not the cause, there is no fix to the cause.

I have had the phone being kept by Google Play Services issue on every custom ROM I flashed on any of the phones.

Mostly they were CyanogenMods. I have flashed it on over 10 devices now and each ROM has the problem of phone being kept awake by Google Play Services. Even with different GApp packages.
[Android Software Development] sperelli:
same issue on TK Gapps, too
[Android Software Development] D@rekills4:
Yes, but which one?

The phone being kept awake or the Google Play Services app crashing constantly?

I believe the latter one is a OpenGApps specific issue.
[Android Software Development] NZgeek:
I'm also running CM on my phone, but have an older Open GApps package installed. I'm overdue for an OS upgrade, so I'll do that tonight with the latest GApps package and see how my battery life is affected. I get fairly good standby time with my current setup, so I'll notice the drain pretty quickly.
[Android Software Development] lilbigdude1:
If you change your locations setting to device only the Google play services will stop crashing. It does it on every gapps package. From what I've read it's a Google issue that's been going on since before June.
[Android Software Development] D@rekills4:
Yes it's been going on since a long time but the Play Services crashing issue began in the last 2 weeks.

I didn't do any different settings from last time.
[Android Software Development] Oblox:
Im not sure if this is an issue for just me but ive experienced it a number of times now and on 2 different phones.

Ive tried 4.4.4 gapps (pico ARM) and 5.0 gapps (pico ARM) and whilst both flashed they didnt actually do anything, there was no ability to add a google account nor access the play store.

Tested on Xperia SP kitkat CM11 and Xperia SP 5.0.2 Revolution remix.

An old PA gapps pico works fine on both.
[Android Software Development] ATomCZ:
Hi. I'm looking for the way how to install this great gapps distribution to the Genymotion emulator.

It allows to flash ZIP update only by drag&drop file to the windows, but it doesn't recognize advanced format of TWRP custom recovery, but it support only basic recovery format.

Does somebody know some way?
[Android Software Development] NZgeek:
Have you tried the nano or pico packages? These use the old CWM-style script, and are more likely to be compatible with the emulator.

If there's something in the script that doesn't work (e.g. the size calculations) then you could try hacking the install script, or even writing your own. The Edify scripting language is pretty easy to understand.
[Android Software Development] fr3quency:
Glad to be of use! :)

I wanted to ask something. How do you guys extract(and delete) and lib folder from inside the .apk? I've tried doing it with WinRar(extracting the lib folder, and then deleting it from inside the .apk) but when I flash the modified Gapps package(as I try to maintain my own for my own personal use) I get errors all over the place. Two notable examples are Google Play Services(I'd get error messages) and Hangouts 4(it wouldn't open. It force closed when I hit the icon).

Thanks for your time.
[Android Software Development] jawz101:
I kinda wish we had a zip you run in recovery that looked for any apps signed by Google as updates or as independent apps and moved the app from user to system. That way you could have a seed install of OpenGapps you'd use once then leave it up to the Play Store to update... Then every now and then you run the zip to move any user apps by Google into system.

Essentially you could get away with a Pico install then install what you want from the Play Store, then run the 2nd zip that's just a tiny script to move the new and updated gapps to system.

It'd be no maintenance in the end.
[Android Software Development] ASHURiCAN:
http://xdaforums.com/showthread.php?p=62427590
[Android Software Development] lo2ay:
Where can I find older versions of Open Gapps?
[Android Software Development] fr3quency:
It's not a bug. The only version for the newest Play Services is -438 for the time being. Check www.APKmirror.com

Sent from my Nexus 4
[Android Software Development] ASHURiCAN:
That's what I did but I was just wondering if it could cause problems or not in the services. Until now, my Galaxy Nexus runs fine so it's ok for me [emoji4]
[Android Software Development] ipdev:
Interesting that they do not have a link to MindTheGapps for Android 10.

or test builds for Android 12

Why are they linking to OpenGApps nano packages?

I have not compared them recently.

The last time I checked MindTheGapps was closer to pico.

--

I would recommend you contact @hazzer (if he even is still on xda) and ask him to rewrite that warning a little nicer.

That kind of negativity is what makes everyone walk away from a project.

Unless that is the goal.

The You've been warned. part is salt in a wound and over the top. 🤬

Cheers. :cowboy:
[Android Software Development] curiousrom:
@ipdev - Your are missing the points:

The era of publishing untested rolling releases of Open GApps is over.

It's not fair to use unsuspecting users at large as beta testers.

It takes too long to remove broken builds from the servers and that was discussed in this thread a while ago.

BTW MindTheGApps is similar to Nano but without Google Digital Wellbeing and it's always tested by several users before being released.

***
[Android Software Development] Nezorflame:
You're all correct.

To reiterate on what has been said before:

1 - permission verification script is in the works, there's an open PR on Github which will help us with this kind of issues in the future

2 - for now this is done manually, so fixes are slow - should be fixed by 1

3 - ALWAYS have a backup gapps package (OpenGApps or any other one) before updating, this applies to any kind of software, ROM or kernel. We do have testing issues so that's especially true in this case.

Once we have script in the pipeline and testing bot/group, we will continue A12 work.

In the meantime, bad packages have been pulled and permission fix was merged.
[Android Software Development] ipdev:
I understand.

I for one, can not wait for a stable (milestone) source branch that stable releases can be build from. ;)

Since Google keeps pushing the finish line, it is harder to keep up with newer builds.

---

I am nowhere near others when it comes to contributing to open source and/or the Android community.

I might get more angry about it because I respect all who freely give their knowledge and limited free time.

Including those who try to help and contribute when they can.

---

Lineage, for as much as they try to separate themselves from it, builds MindTheGapps.

They only update when needed and have time, the apps are often out dated.

This require users to update and use space in userdata.

I agree with this to a certain degree.

Opposite from their rom nightly builds that build everything even if there is no change for the device.

Use it or Lose it build server time.

MindTheGapps is build to a specific Android (SDK) version.

This means they can make simple changes to the build and installer scripts without worry.

---

OpenGApps is a completely different project.

It is meant to be the most up-to-date version of gApps.

I do not think daily builds should be run if there is no change.

Again, the use it or Lose it build server time.

---

The point everyone seems to be missing is OpenGApps is a large project.

Supports more than one Android (SDK) version.

So the build and install scripts have to be written to be compatible with multiple Android versions and device architecture.

Not only updated but also make sure not to break backwards compatibility.

To fully test, every build would have to be tested on ...

arm

arm64

x86

x86_64

Multiply this by two to eight builds per Android level (most have at least eight).

Currently twelve official (SDK19 -> SDK30) and one more unofficial (SDK31).

Not including the TV builds.

That will never happen.

As I noted in a previous post.

Every developer uses their user base as a test subject.

Roll out release.

---

Save for contributors, at the core there is currently only four active members.

Please correct me if I missed an active core member.

Nezorflame took up the mantle to keep OpenGApps updated and at the forefront. (y)

---

If LineageOS has issues with OpenGApps.

Maybe more than just a few lineage developers could help by contributing to the OpenGApps project. 🙃

Cheers. :cowboy:
[Android Software Development] osm0sis:
A few Lineage developers do actually contribute to Open GApps fairly regularly. 🙃

But, yeah, it's pretty much 98% Nezorflame now, so honestly it would be nice if some people took all the energy they use to write pages of commentary about how Open GApps should/shouldn't be run and would use it to learn how to shell script or Python script and actually contribute something useful. 🙄😉
[Android Software Development] curiousrom:
That would not solve Open GApps's #1 issue. 😕

***
[Android Software Development] osm0sis:
I think Open GApps' #1 problem is ****ing complainers.

If there were more people working on the project instead of complaining about the project then there really wouldn't be any issues. Scripting the automated adding of the new permissions will resolve pretty much all the problems that have cropped up recently, but Nezorflame is one guy trying to fit things in when he can.

Next time you want to complain about how long it's taking to get something done how about you try to figure out how you personally can contribute code to get it done more quickly.
[Android Software Development] curiousrom:
Ya those fuzzing annoying users caught in a bootloop & those lazy LineageOS team members are real $!%$#!

***
[Android Software Development] osm0sis:
At no point did I call anyone from Lineage lazy, so you can drop that nonsense right now.

Feel free to become capable of contributing code to help, or at the very least anything other than your ongoing shi*ty attitude.
[Android Software Development] curiousrom:
But they are criticizing as quoted above & they aren't helping churning out daily untested Open GApps builds!

***
[Android Software Development] osm0sis:
Yeah they're busy with their own stuff. You on the other hand are supposed to be a Recognized Contributor; maybe contribute something more than ****ing trolling to this thread and project for once.
[Android Software Development] curiousrom:
You are the one avoiding the issue.

If you look at my posting history you will see that I'm a user support type of guy & not a dev.

I am fed up with helping freaked out users who are flashing a custom ROM + Open GApps for the first time and getting caught in a bootloop thinking they messed up & broke their device or something.

That's not counting the thousands of hours lost by users if you add them up.

***
[Android Software Development] osm0sis:
If you're fed up then learn how to read logs, do basic debugging and help fix issues, that's a central part of user support.

And if you're really fed up then maybe your user support isn't what Open GApps needs. It needs developers/contributors who aren't ****ing toxic and burnt out. If you're not capable of learning how to help directly then maybe you should try to recruit more people who can.
[Android Software Development] osm0sis:
I fail to see how that pertains to Open GApps, but it's nice to see that you're able to communicate appropriately elsewhere on xda. Feel free to use those skills to triage some issues on Open GApps' GitHub and send us pull requests for simple fixes going forward. (y)
[Android Software Development] ALTracer:
Are you perhaps missing the point of incremental packages? pico<nano<micro<mini<full<super, so testing `super` oughtta catch any bugs in subsets (stock and aroma are a different beast, judging by installer script).

Running 20211130 build now, seems to be working.

Whoa, you really pulled all the 20211204 builds? Pico was not affected by digitalwellbeing as it doesn't contain that app, and nano+ are/should still be runnable with a workaround gapps-config.txt of `Exclude \n Wellbeing`...

Saw some juicy gitlab commits on 20211206, will wait for 20211207 build to test in the next 24h. People soon flashing Google December Security Patch updates might want to grab a fresh gapps build while they're at it.

I personally see OpenGapps as a powerful project supporting a wide variety of SDK levels and architectures, employing modern VCS, CI/CD, lzip (you're cool, guys!) and customizable with text input (gapps-config-santoni.txt). No other gapps provider ever stood near (NikGapps, MindTheGapps, etc.). If your gitlab repos are open for contributions, I might consider sending simple merge requests when appropriate. I learned some shell and makefile, but my python-fu is not strong enough. Github issues maybe require moderation.
[Android Software Development] curiousrom:
That's not necessary at all.

Play Store, Play Services & libraries automatically update themselves in the background regardless of the user's update settings in Play Store.

When Google will feel that they need an update it will do it automatically.

As for the apps included in a GApps package you can either not update, manually update or chose automatically update in Play Store's settings.

***
[Android Software Development] ipdev:
@ALTracer

Even though it is incremental, you would still need to test each build for dependencies.

The stock package may work but, the nano package will fail because something was updated and now requires a new dependency.

If that dependency is only installed with micro and above, the nano and pico builds will fail.

That is just one example of why all the builds would have to be tested to be able to guarantee they are stable.

Ignoring device or rom specific issues and user settings.

You could reduce the testing a bit if you only test the packages that might be affected by an update.

Test stock and mini if an update was in-between them.

Welcome to the OpenGApps party. :D

Please feel free to help and/or contribute. (y)

Cheers. :cowboy:

PS.

My python skills are currently only enough to follow along with the python bits. :ROFLMAO:
[Android Software Development] Game-R:
Thanks for the advice @runekock.

However, I have been trying few other ROMs which doesn't come with any GApps built in. Both are based off LineageOS (https://xdaforums.com/t/rom-7-1-2-unofficial-viperos-v3-1-1-25-08-2018-sumire.3756729/) (https://xdaforums.com/t/resurrection-remix-5-8-5-for-xperia-z5-unofficial-unified.3576281/) and I'm trying to install Open GApps 7.1 to just get Google Play store in it, but the moment I install anything on it, the Wifi Direct and it's ability to Miracast to wireless displays (which was working fine before) falls to pieces immediately.
[Android Software Development] runekock:
Sorry, then I misunderstood.

Unfortunately, I don't know what to do. Miracast was removed from Android in favor of Chromecast, but if it's still supported by your rom, it's crazy that play services should break it.
[Android Software Development] curiousrom:
Open GApps & Miracast?

You cannot flash a custom ROM, boot to system then flash Open GApps later otherwise expect some issues.

It must be done in one go, one after the other after wiping System & Data.

On A/B devices you have to reboot to recovery after flashing the ROM & before flashing GApps.

On encrypted devices you need to format Data instead of a simple wipe.

FYI Miracast a.k.a. Wifi display support was dropped by Google but some LineageOS devs re-implemented it on some devices but not on all currently officially supported devices.

From https://en.wikipedia.org/wiki/Miracast : "Since Android 6.0 Marshmallow released in 2015, Google dropped Miracast support in favor of their own proprietary Google Cast protocol."

Did you test Miracast while running those ROMs without installing Open GApps?

Did you ask in those ROM's threads?

***
[Android Software Development] Game-R:
Hi @curiousrom,

Yes, I definitely did test it every time before flashing Open GApps and it was working; able to detect wireless TVs and my Miracast devices and I'm able to rename my Wifi Direct name without errors. When I first started flashing my device, I always did install Open GApps immediately after flashing the ROM and I was encountering the problems then and spent the whole of last weekend trying to pin point the source of my Wifi Direct/Miracast troubles. So I started doing the flashing one at a time and found that the Wifi Direct/Miracast seems to work immediately after flashing the ROM but wouldn't after I flashed Open GApps.

But recently, just this evening, after my nth attempt at flashing about 10 different 7.1.2 ROMs to find out what is going on, I found that it may not be Open GApps.

One ROM, that I knew worked previously, was flashed to my phone. I then confirmed its Wifi Direct/Miracast working, but after that I was pulled away to settle something and before I could get around to installing Open Gapps, I started encountering the errors I reported.

I tried a second different ROM (that worked before), tested Wifi Direct/Mircast working, rebooted the phone, and it wasn't working after.

In both cases, I did not have the phone connected to any wifi network nor did it had a SIM card in it, let alone any data connection out.

What is going on here? Do these ROMs self destruct their Wifi Direct/Miracast capability after a couple of minutes?
[Android Software Development] runekock:
Maybe you need to reboot the TV as well???

Miracast was plagued by compatibility problems - that may be part of the reason that Google tired of it.

Is there a firmware update to your TV?
[Android Software Development] Game-R:
It's all good now. Managed to find one ROM that somehow is able to keep it's Miracast capability working regardless what is installed or not. The issue is clearly something to do with the few custom ROMs that I tried. I have two other devices, a stock OnePlus 5 and a custom ROM LineageOS Samsung that was reliably able to connect to this Miracast HUD unit while the Xperia Z5 I was trying to set up kept failing.

Appreciate all the assistance!
[Android Software Development] curiousrom:
LineageOS Removes Links to Open GApps for Android 8.1, 9.0 & 11 in their Wiki

Well it finally happened.

LineageOS got tired of all the broken builds and this commit was merged: "Remove Open Gapps where alternatives exist - we have too many issues "supporting" users with it".

As you can see in https://wiki.lineageos.org/gapps :
[Android Software Development] G A S T:
What a stupid move! With GApps pico I never had any problems except AA not working properly for a few months.

But on the other hand - this was clearly provoked by the whole GApps team and their useless rapid release schedule. Lots of people proposed to switch to a monthly release of better tested builds.
[Android Software Development] zimral.xda:
I never had any problem with Open Gapps ("pico" variant) too. It is still in use on one of my test/dev devices. For my remaining last productive Samsung S5/klte i stopped using any google apps with the migration from LOS15 to LOS16 nearly 3 years ago. And i never had any problems with my ~50 apps in use. The biggest benefit of not using any google stuff is a ~15% less battery drain, a much faster GUI response and last but not least google has now nearly no chance to track me. If there are still some aliens inside the LOS rom trying to watch me, they will be stopped by ADGuard, NetGuardPro and Blokada. i already moved to the Pixel3 with my two other prod devices currently using stock Android12 with as much as possible google stuff uninstalled/deleted/deactivated and with the introduction of LOS19 for walleye i will flash a pure LOS image only. The only open question is the usage of TWRP or LOS recovery.

So i can still recommend the "pico" if someone want to be tracked by the evil company as "pico" seems to be not affected with the current open gapps bugs. :cool:
[Android Software Development] Trustwizard:
Hi all and btw gratz for your amazing job! any hint of what can I do on my samsung Note 10.1 (GT-N8020) version? I'm using latest Lineage 16.0 (android 9) and I'm getting some apps like "stadia" and "Vodafone TV" (this one if I go to menu and reenter app it resize) app issues with resolution/resize I guess (green pixels and stuff).

Games like "clash of clans" background colors disapeared sometimes and crash, could it be a wrong Gapps version for my Note 10.1? Youtube/ Netflix its ok. (using arm_9_pico)

Anyone with the same issue/workaround?

Thank you all!

Have a great christmas and an awesome 2022. :)
[Android Software Development] Flounderist:
@Nezorflame today I had a weird issue with the A12 nano package.

I tried both builds 20211112 and 2021116 and I had error 64 on recovery.

My device is Realme RMX1931 (arm64) and I was flashing Voltage OS .

The device has been recognised as arm and no apps has been flashed.

The log.txt is basically empty, just arm device detected.

Any hint?
[Android Software Development] ipdev:
This should help explain it.

OpenGApps - GitHub

Pull request [# 942] - Link and Pull request [# 944] - Link

The next test build should include the architecture fix. ;)

After the PR was merged, I cleaned up and re-synced my local sources.

Pixel Launcher was borked on Android 12 and I have not had time to check into it.

Until Nezorflame has time to run a new A12 test build, feel free to try one of the MOD builds I made for testing.

A12 Pixel Launcher still works on these builds, at least for arm64 🙃

OpenGApps UNOFFICIAL - MediaFire - Link

The Android 12 versions are in the SDK31 folder.

Cheers. :cowboy:
[Android Software Development] Flounderist:
Thank you!

I reverted on an A11 build (LOS18.1) and I already formatted and set up my device again so I don't think I will move to A12 shortly but I really appreciate that!

Bye!
[Android Software Development] Nezorflame:
What @ipdev said.

I'll run new builds this weekend.