[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Retrial:
Hi Nikhil,

I see my reply about nikgapps here got your attention, I will try to explain your mentions. My posts above about nikgapps wasn't so extensive described since it was generally talking after I got mentioned by other user.

nikgapps.config

When I say the config doesn't work correctly I mean, I change the values in apps I don't want to 0 so package to not get installed and skipped but instead the apps gets installed.

I use the full package zip and the config file in the same folder in my SDcard the same way I did with other GApps like FlameGApps and OpenGApps which work just fine.

custom builds

Probably I didn't expressed myself right. When I say it doesn't work, I don't mean it doesn't build in github. The package .zip is building correctly without errors. The problem is, I tried 2 times, once in the past and once recently and both of the times I ended up with bootloops on clean install of a ROM. Here you can check my package.@SPLESHER also made his own package and he ended up too with bootloop.

other reports regarding permissions, ota survival

Honestly I can't say much about it since I couldn't make NikGApps to work the way I wanted so I skipped it, but I have seen a lot of reports about OTA survival issue (not always, just from time to time with some of yours updated packages) and permissions issues like you need to give network/internet permission to play services/store to work which other gapps doesn't have that.

package definition

When I say confusing I mean the match of the apps you include in some of your "ready" packages are weird combinations and very complex.

For example, in Basic you include Google Dialer, Google Messages, Google Contacts, Google Clock which we can consider them as the

basic google apps

but you don't include Google Calculator there, instead you have it in the Omni package, and Google Calendar and Google Gboard in another package (Stock) which is kinda weird. The user who choose to replace AOSP

basic apps

with Google one is forced to use bigger package like Full just to have the basic google apps all together. Also in Basic you include vanced manager which some people may don't want it as we talking about pure Google Apps, in fact it could be done a swap between velvet addon and vanced, which most of the users strugle and leave vanced as addon, especially now which is shut down, and could stop working anytime google decide to change it's api.

To compare FlameGApps, is much more cleaner and organized with better combinations on their just 2 packages so it can cover most of the users out of the box just fine and have simple config for extra customization+addons.

Also in my opinion the package defination page, should be in much more visible position in your website so people can understand what they choosing when editing config or when they choose a "ready" package.

in summary, the issues that you have reported are subjective

Well, to come on this conclusion I asked another user @SPLESHER which we usually are in the same ROM to try himself and he ended up on the same issues. Also I was gathering infos by watching other users reporting some issues over the time and most of the times the issues was same (permissions, OTA, bootloops).

NikGApps core work just fine most of the times tho and I already said that in my posts.

I think I read your guides and I followed the video tutorial just fine, as I include them in my thread since long time.

I appreciate the work you have done and you continue doing, my intention was not disrespect your work.

I got mentioned by other user and I replied why I prefer and suggest Flame over Nik, that's all. In the end of the day is just GApps and opinions may vary.