yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Nikhil:
New Release is up! (Android 10-13)

Changelog:

Introduced elite builds - more on this shortly.

Fixed the issue when dirty flashing leads to duplicate entries in addon.d

Control the overlays through code - better control over configurable features

Fixed Pixel Setup Wizard (Android 13) (find the addon to flash)

Make the addon.d logs better readable while restoring

Fixed the Pixel Launcher crashes on ArrowOs

Improvements in installer script

Config upgraded to v28

Note:

- we're trying very hard to allow dirty flashing without issues, however, I would still suggest backing up everything before flashing to make sure you don't lose anything if things go south.

Cheers!
[Android Software Development] osm0sis:
So far so good! Flawless dirty flash here. 🤘

Fingers crossed for Tuesday's OTA. 🙂
[Android Software Development] js-xda:
First of all a big thank you to all the work providing the these GApps! I am using the core addition on multiple devices without any additions or customization since quite a while as OpenGApps struggled to keep up providing their packages (I used to rely on Pico flavor). I am glad about this lite GApps package as too many aim rather for "full experience" while I just want to have the very basic functionality.

The remark about Gboard I don't understand. To my knowledge, one can install Gboard straight from the Play Store without any issues. Or is there a specific benefit of flashing it via GApps?

This one (additon: "Fixed Velvet/GoogleClock/AndroidAuto/Gboard/GoogleSounds not restoring after OTA update") made me worry a bit as I upgraded just lately a OnePlus 5 from LOS 19.1 with NikGApps core to LOS 20 (following the advice in this thread to remove all updates of the Play Store and Play Services before flashing ROM and GApps). I installed NikGapps-core-arm64-13-20230418-signed.zip and the system runs smoothly now. But I am wondering now whether I have to expect any issues with the next OTA (addition: running an earlier version). If so, should I upgrade to the latest (at the moment June 9th) and should I follow the same advice about removing all updates for Play Store and Play Services? Sorry, maybe a (too) basic question but since I am not the actual user (and live quite some distance from that one), I prefer not to run into big issues.
[Android Software Development] Doomguy6:
Same
[Android Software Development] Nikhil:
There is no significant benefit of flashing GBoard other than removing aosp keyboard from the system. GBoard does become a system app when you flash the addon, so it will never miss a feature just because it didn't have enough privileges. I myself don't use GBoard so to me its same as installing from playstore.

I suggest you go ahead with dirty flashing NikGapps core to latest version, you will not experience any issues.

You don't need to perform all those steps that you did to upgrade from Los 19.1 to Los 20, a simple dirty flash will be enough.

as far as that changelog goes, have you flashed addon of any of the apps listed? (Velvet/GoogleClock....) if not, just go ahead with dirty flash of NikGapps core.
[Android Software Development] Nikhil:
Greetings,

Today, we’re excited to introduce

NikGapps Elites

to everyone - A program to recognize the past contributors and make way for new contributors

What do Elites get?

Elite builds that are Highly Compressed Zip Files: Saving your data and speeding up downloads.

Signed Zips: Ensuring a secure and reliable NikGapps experience.

Consistent Releases: A personalized build automatically created with every stable release. No need for manual custom build requests, saving your time.

Exclusive Folder on Sourceforge: A dedicated folder for your personalized builds on Sourceforge.

Personally Validated Builds: Ensuring packages don’t conflict for a seamless user experience, you don't run into errors while flashing the builds just because the chosen combination of pacakges wasn't right.

Device Specific Builds: Rom Devs can establish a device specific folder for their ROM depending on the configuration of the device, allowing users to download a build tailored to their device. Instead of suggesting separate NikGapps core and addons, Rom Devs can recommend a single NikGapps-DeviceName-arm64-1x-YYYYMMDD-signed.zip file with all components included.

Name in the Recovery: A special badge of honor (Coming soon).

Ability to Debloat with your <elite>.config: You will be able to debloat your system using your personalized config (Coming soon).

Head over to this page to get all the information regarding NikGapps Elites and spread the word. :)
[Android Software Development] osm0sis:
Unfortunately still seeing the same issue with Dialer after addon.d, triggering the -downloadable version. One thing I notice is it goes back to showing v96 in App Info after the addon.d, and opening it at this point shows the unsupported device warning, which might be a clue.

Dirty flash fixes it perfectly again.

Seems like this is the last wrinkle to iron out and then all is solid. 🤘
[Android Software Development] osm0sis:
Okay I think I possibly cracked it.

Looks like none of the extra XML files generated as part of the ExtraFiles install get backed up or restored with addon.d.

So that's:

- /system/product/etc/permissions/com.google.android.dialer.support.xml Successfully Written!
- /system/product/etc/permissions/com.google.android.maps.xml Successfully Written!
- /system/product/etc/permissions/com.google.widevine.software.drm.xml Successfully Written!
- /system/product/etc/permissions/com.google.android.media.effects.xml Successfully Written!

None of which are then listed in the ExtraFiles prop or addon.d sh.

So I guess get those in there and hopefully all is good? Also shouldn't some of those be generated by other solo packages as well - like dialer.support.xml by Dialer and maps.xml by Maps?

Edit: I also notice a few other differences that might need fixing, like as.xml, messaging.xml, ime libs, some overlays and a bunch of usr files that seem to go missing after addon.d but the dirty flash then restored. 🤯

Edit 2: @Nikhil I added a filtered diff of just the concerning ones (i.e. I removed the ones that are just clearly an app switching partitions). Quite a few things actually, though mostly accessory files, but hopefully you can make sense of what's going on and get it all persisting through addon.d.
[Android Software Development] Nikhil:
First of all, thank you for finding the root cause and saving me hours. I was counting on build.prop changes not surviving the OTA but I didn't know these dynamically generated files are also not surviving.

Second of all, all the issues are now resolved (from my tests).

Here are the details.

- 4 permissions files not surviving the OTA - these had a different implementation where the files were dynamically generated and because of a bug not being added to the ExtraFiles.prop file and thus not making it to final addon.d sh file. (Fixed)

- The overlays and files that you find missing are actually relocated with dirty flashing, that includes usr and other xml files too (Fixed)

- overlays are supposed to be part of product partition, regardless of it's original apk location (Force install overlays to product)

The reason why few of the files (such as dialer support xml) are part of both ExtraFiles and respective packages is because we want the core package to function even when you install the apps from playstore. Could have kept in Core only but we have a few users who only flash the addons and then we want to ensure they get the needful files too. :)

I am yet to figure out how to make build.prop entries to survive the OTA update - that's not critical but still requires a solution.
[Android Software Development] osm0sis:
Nice! No problem! Thanks for the quick fixes. 😁

What about the other 2 XML files that showed up but don't seem to be part of their respective packages? Generated and need to be backed up too?

+/product/etc/permissions/com.google.android.as.xml

+/product/etc/permissions/com.google.android.maps.xml
[Android Software Development] Nikhil:
the file is installed in both /system and /product. you can check all_files.txt from before and after, in before it is only in system, in after it is in both.

the reason why it is in both partition is because, now we're not uninstalling the package unless system runs out of space. so the file was already present and when you dirty flashed, it went to the default partition as it had enough space.

This gets resolved with ota update as addon.d only has one of two entries. and with next release, this relocating of files will also be resolved, the installer will now check the partition of apk first and will stick to that partition only.
[Android Software Development] osm0sis:
I wonder if you could just directly echo out to the new slot's build.prop the entries you need to add from the addon.d sh as part of the restore section? 🤔🤠
[Android Software Development] Nikhil:
Yes, I will do that and do it soon so that next Tuesday's ota update is by far the smoothest update you have. (y)
[Android Software Development] osm0sis:
They're already quite smooth, just the dirty flash extra step is a minor inconvenience at the moment! Thanks for your hard work! 😁

My patch_prop function from AK3 could be useful if there's a chance the entry already exists in the prop: https://github.com/osm0sis/AnyKernel3/blob/master/tools/ak3-core.sh#L713

🙌
[Android Software Development] Nikhil:
Thanks, this helps! :)
[Android Software Development] Pixel86:
Any description of what's included in each Elite builds? Would help in choosing. Curious what's included in the @osm0sis version.
[Android Software Development] Nikhil:
Put it in /sdcard/NikGapps folder.
[Android Software Development] Nikhil:
New Update is up :)

NikGapps Website
[Android Software Development] sumochan:
work great, thank you so much :D
[Android Software Development] jandia7381:
On 10 or pie bro?
[Android Software Development] jandia7381:
Hi dev. I'm on 17.11 basic build. Running havoc 3.0 on my kate(reno3SE)

Here my logs and my ss.

- gplayserv not optimised n no face unlock coz if i'm not wrong those included in ur packages. SORRY IF I'M WRONG n thnx for ur hard work :svetius:

https://drive.google.com/file/d/1-f6qfrBEcbsufgr-Y9c_DUjCEos3JZBE/view?usp=drivesdk
[Android Software Development] Nikhil:
GMs optimization will come with next build, Disabling find my device should do the trick for you starting next build.

As for face unlock, google dropped its support so it won't be included in gapps package
[Android Software Development] mvlad:
Any way to get the new Google assistant in? Or is that more dependant on the rom than the gapps?
[Android Software Development] :
I just saw the new announcement on telegram. What does it mean that the debloater gets separated? So if someone comes from a different gapps like opengapps and switch to nikgapps, you will have to first run the debloater so that the currently installed gapps get removed?
[Android Software Development] enes3626:
How can i sync my contacts? It doesn't work
[Android Software Development] gianton:
It's working fine with stock gapps.
[Android Software Development] D1stRU3T0R:
Nice build, but why you added Lawnchair launcher? There are many more and much better launchers. Also less bloated ??
[Android Software Development] :
For some reason I still have both dialer, Google and AOSP. Some with the keyboard. The reason is maybe that I had both before using nikgapps? Both Google apps were installed as user apps.
[Android Software Development] gianton:
It's easy to remove from the zip file.
[Android Software Development] yodainascoda:
another joker so coz you dont like it we should change it ? Change it yourself or maybe too difficult for you
[Android Software Development] D1stRU3T0R:
Did you even checked the launcher feedback? Just check the latest xda post from xda about this launcher, literally no-one liked it from the comment sections. I never used it, so I don't have an opinion, but almost 99% i hear users that they changed it for some reason(s)
[Android Software Development] yodainascoda:
Iv been using it for months its a superb launcher instead of listening to others try for yourself you might be surprised
[Android Software Development] :
What are you talking about, lawn chair is highly used and the go-to launcher if you want a customizable pixel launcher.
[Android Software Development] tezukaryoma:
Can i flash nikgapps on top of opengapps?
[Android Software Development] Black_Stark:
May be U need nik gapps debloater i think.

If failed then wipe ur system partition.
[Android Software Development] :
For some reason, nikgapps can only show Lockscreen Temperatur in Fahrenheit ans Not in Celsius. Mit sure if the Google app or the play services is the issue but this should be fixed. Not just Americans are using nikgapps ;)
[Android Software Development] osm0sis:
You can see the configs here:

config/elite at main · nikgapps/config

Contribute to nikgapps/config development by creating an account on GitHub.

github.com

Once the ability to add a debloater.config is added I'll have mine there too to remove Eleven from LOS. But so far it's just my app selection, like I prefer Lawnchair or Trebuchet instead of Pixel Launcher, but I do want Live Caption and Screen Attention that come with it, I hate Google Files app so make it use the DocumentsUI Files shortcut instead, and I keep Lineage's SetupWizard in addition to Google's since it's important for feature setup and avoiding odd behavior when it's removed (but sometime removing it is fine, depends on the ROM). That sort of thing.
[Android Software Development] Pixel86:
Thanks for the update 👍
[Android Software Development] Nikhil:
@osm0sis any chance you can try this arm go build and tell me if it works or not?

Download: NikGapps-go-arm-13-20230617.zip
[Android Software Development] osm0sis:
It's working great so far! Play Store gave me some "Something went wrong. Try again." messages when trying to view the Manage apps lists at first, but once I installed an app it seems to be fine now. 🎉🤘🙌

Edit: Go arm seems like the perfect lightweight package for an old device! My Nexus 7 2013 honestly hasn't run this smooth/stable in years, and never has truly well on Android 13 until now. 🤯🥳
[Android Software Development] Pixel86:
A follow up to your debloater comment. Does that mean in the interim, your current Elite build will still contain the default NikGapps debloater or no debloater at all?
[Android Software Development] osm0sis:
Default, which is none.
[Android Software Development] Nikhil:
That is wonderful. It's kinda difficult to maintain the apk updates without the device but I will try my best to provide timely updates for arm.

Also, could you please wait one more day? I'll release a new build so you can dirty flash that before your OTA update. This one should be the most stable build (fingers crossed).
[Android Software Development] Nikhil:
New Release is up! (Android 10-13)

Changelog:

Fixed the dynamically generated files not surviving the OTA update

Fixed relocating of files upon dirty flashing

Fixed build.prop changes not surviving OTA update

Make sure the overlays are always installed to product partition

Remove StorageManager with StorageManagerGoogle

Update nikgapps.config version to 29

Elite Builds - Add the ability to debloat stuff using elite.config (v29+)

Elite Builds - Add creator's name in recovery as a special badge of honor

Elite Builds - Auto upgrade the config version from v28 to v29

Note:

- we're trying very hard to allow dirty flashing without issues, however, I would still suggest backing up everything before flashing to make sure you don't lose anything if things go south.

Cheers!
[Android Software Development] Nikhil:
@osm0sis your elite config will be auto upgraded to v29 shortly (as soon as deployment is done), once it is upgraded, feel free to send a pull request with Debloater changes (including Eleven) and it will be auto merged after a few mins.

Also, to trigger a new elite build manually, all you need to do is change the RELEASE_DATE value to any number less than its current value. You can do it along side debloater changes in the config and you will find a new elite build created shortly after that.
[Android Software Development] osm0sis:
Dirty flashed, OTA'd and all is good! No more Play Store shenanigans with Dialer! I did lose Call Screen temporarily, but a couple app Force closes got it back, so it must just be some phenotype db thing getting reset then resolved and presumably not really GApps' fault.

I did another dirty flash after the OTA just to double check how it went and it looks pretty great!

--- before/all_files.txt	2023-06-21 03:34:28.000000000 -0300
+++ after/all_files.txt	2023-06-21 03:36:22.000000000 -0300
@@ -3317,6 +3317,7 @@
/system/lib64/shared-file-region-aidl-cpp.so
/system/lib64/slicer.so
/system/lib64/spatializer-aidl-cpp.so
+/system/overlay
/system/priv-app
/system/priv-app/BackupRestoreConfirmation
/system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk
@@ -3890,6 +3891,7 @@
/system/usr/srec/en-US/endtoendmodel/marble_rnnt_model.word_classifier
/system/usr/srec/en-US/endtoendmodel/marble_rnnt_model.wpm.portable
/system/usr/srec/en-US/endtoendmodel/marble_rnnt_voice_actions_frontend_params.mean_stddev
+/system/usr/srec/en-US/g2p
/system/usr/srec/en-US/g2p.syms
/system/usr/srec/en-US/g2p_phonemes.syms
/system/usr/srec/en-US/hotword.data
@@ -4300,12 +4302,6 @@
/system_ext/priv-app/LineageSetupWizard/oat/arm64
/system_ext/priv-app/LineageSetupWizard/oat/arm64/LineageSetupWizard.odex
/system_ext/priv-app/LineageSetupWizard/oat/arm64/LineageSetupWizard.vdex
-/system_ext/priv-app/QuickAccessWallet
-/system_ext/priv-app/QuickAccessWallet/QuickAccessWallet.apk
-/system_ext/priv-app/QuickAccessWallet/oat
-/system_ext/priv-app/QuickAccessWallet/oat/arm64
-/system_ext/priv-app/QuickAccessWallet/oat/arm64/QuickAccessWallet.odex
-/system_ext/priv-app/QuickAccessWallet/oat/arm64/QuickAccessWallet.vdex
/system_ext/priv-app/Settings
/system_ext/priv-app/Settings/Settings.apk
/system_ext/priv-app/Settings/oat

Looks like something in the installer is still creating an empty /system/overlay, but no big deal there. The missing srec file is a bit odd, but I guess just got missed from the addon.d .sh somehow? Then not entirely sure what to make of the QuickAccessWallet stuff, but could just be the ROM version of it being removed again, so that might be missing for removal from one of the addon.d .sh files too.

Thanks so much for all the hard work! I'm avidly looking forward to using the new Elite builds with debloater built-in! So great! This is truly the most robust GApps solution, and soon to be a bugless beast! 😁🤘
[Android Software Development] Nikhil:
okay, the issues are now resolved.

while building the prop file, the installer was skipping g2p because it already had g2p.syms - Fixed the addon.d script losing a file when the approximate match is found

+/system/usr/srec/en-US/g2p
/system/usr/srec/en-US/g2p.syms

The overlay folder was forcefully generated in /system because the files were being installed in /system for some of the packages -

Skipped building overlay directory unnecessary

It appears that QuickAccessWallet is being shipped from Rom which is why it is being cleaned up. This will appear again after OTA update because Rom is shipping it and we didn't remove it - Remove the AOSP version of QuickAccessWallet

Fingers crossed on these being the last remaining issues to sort. 🤞
[Android Software Development] Nikhil:
New Stable Release is up - 27th June 2023 (Android 10-13)

Changelog:

- Fixed the addon.d script losing a file when the approximate match is found

- Skipped building overlay directory in system unnecessarily

- Remove the AOSP version of QuickAccessWallet

- Elite Builds - Auto upgrade the elite.config to latest version including debloater changes

- Drop support for android 12 as most people use android 12.1. You can still create User Builds for android 12.

Note:

- it is dirty flashable over previous build, recommending everyone to update to this build.

- we're trying very hard to allow dirty flashing without issues, however, I would still suggest backing up everything before flashing to make sure you don't lose anything if things go south.

Thanks for choosing NikGapps. We appreciate your continued support and encourage you to share this update with others.

Happy flashing!
[Android Software Development] osm0sis:
:/sdcard/Download $ diff before/all_files.txt after/all_files.txt
:/sdcard/Download $

*Chef's kiss* 🥳
[Android Software Development] LeBeNo:
Just wanted to say that I found NikGapps because no matter what I did, MindTheGapps-13.0.0-arm64-20230408_162909 just kept on saying "Google keeps stopping" on lineage-20.0-20230624-nightly.

I tried with NikGapps in stead of MindTheGapps and no more "Google keeps stopping". \o/
[Android Software Development] Nikhil:
Thanks! I wonder when will LineageOS team start recommending NikGapps. It's already stable enough to be used as daily driver.
[Android Software Development] fireangel403.sa:
Can it be

@Nikhil first of all many thanks for your active support in the thread.

While my install of MindTheGapps with LineageOS 20 is working almost fine, except for the google password manger sync not working across the apps on Mi A2 Lite (daisy). That is the saved passwords are not being synced acors the apps.

Please let me know

1. What is the NikGApps variant that is equivalent to the default MindTheGapps?

2. Can i only install particular component from NikGApps to overcome the google password manager issue?

3. Can it be dirty flashed after i have setup my device? In way that i factory reset my device after flashing NikGApps?
[Android Software Development] itsAlphaFox:
Hey I have a Nexus 7 2013; is there any arm (not 64-bit) build that is up right now? This link is dead :(
[Android Software Development] osm0sis:
Repost until it's officially added to the roster. 👍

Only other thing I've maybe noticed is that Smart Lock for location doesn't seem to work even though it looks like it will, so Google Location Services might be needed or something.
[Android Software Development] Nikhil:
1. There is no NikGapps variant that is same as MTG. However, NikGapps offers the ability to create a variant of your own, you can list the apps included in MTG and create a NikGapps variant following this guide.

2. You need GooglePlayServices for that and we don't have an addon just providing GooglePlayServices, I suggest you create that variant of your own and include Core in it.

3. Yes, you can dirty flash NikGapps but only if you originally had NikGapps installed. You cannot switch from MTG or OpenGapps to NikGapps without clean flash.

Also, the reason why your passwords are not in sync is probably due to mismatch in gms version present in your devices. you can head over to apkmirror and installed the same apk in all the devices and that should help.

yes, I will include GoogleLocationServices in the next arm build that I provide. Meanwhile, you can try flashing the GoogleLocationHistory Addon as the apk is common for both arm64 and arm so it should work. I don't remember if it needs clean flash but I suppose not.
[Android Software Development] blumentopf75:
Hello, and thank you for this highly customizable gapps-package.

is there a chance to have the same for an ARMv7 -CPU?

I made my own config (needed Andoid Auto only, nothing else).

Installation zip with TWRP works so far without errors. But the app is not listed in settings.

No wonder, since I have this old SM-A510F. (With LOS18 and microG).

Maybe there is also an other gapps-package, for my CPU, which is also highly configurable?

Thank you.
[Android Software Development] osm0sis:
I think it worked! 🥳🙌

Any other addon packages that have common apks/files like that and could be used on arm? 😯
[Android Software Development] blumentopf75:
Do I understand you right: there is (or will be) an arm build of your NikGapps?