[Xiaomi Poco F1 Guides, News, & Discussion] Retrial:
Hello guys,

I suggested to move our conversation about NikGApps and general GApps in my thread and not in crDroid thread since it went too far OT. For people who may don't be aware, the conversation started from here and continued with the reply of developer of NikGApps here.

So to resume our conversation:

@Nikhil

This what I am doing, as I said I put the config in the same folder with the .zip and process.

If I remember well in TWRP I see during the installation, saying that config detected etc., but if I remember well it skipped the digital wellbeing which I set it to 0 but after that all apps get installed which I also set that to 0 and was a bit messy. I don't remember well which apps correctly installed and which not, but I remember that some of them worked according the config and some not. The config i used was the same as the pull request I made to build my own package.

Since POCO F1 is my main device, I didn't stayed to NikGapps to dig the problem because I wanted the device to work as fast as I can and so I didn't tried to take logs or whatever, but I wasn't only me who faced this issue, as I said @SPLESHER also faced exactly the same issues. I could test it in my other phone right now but it's the Galaxy S4 and it's ARM. 😝 However In case I try NiK in feature I will contact you if I face the same issue.

I understand the dynamic requests for packages but I think somewhere it became to much complex for an average user to choose between packages.

As I said the apps in each package (except core-which is just this-core) need to be reconsider for better combinations, few packages and simple. I guess you could do 3 packages, Core, Basic and Full and leave the rest apps as addons. Like in Flame. Some apps like setup wizard & velvet should be included is some packages since I always find users ask the same questions about these and complain that not working etc.

In the end a more demand user would never be happy with any of the packages no matter what, so he can always use a config or make his own package (in my case this what I did but unfortunately didn't worked), but for an average user it's much simpler to use an out of the box not much bloated packages which just replace altogether basic AOSP apps with GApps and also to have the flexibility with addons and addons remover.

About Vanced I am kinda confused, I see the config value is set 0 by default but I haven't tried the Basic package which include it to see if it's not installed by default. In this case a user need to use config no matter what to install it, so I don't understand the reason why Vanced should be included in Basic and not let's say in Full.

In my opinion the vanced shouldn't be in any package and leave it as addon. I am user of Vanced but I would like to install it alone same with other third party apps and doesn't make much sense to be in pure Google Apps packages.

The Core Go package, I don't know if its much popular and needed a specific pack of it, but you could move it to another place/position in the website page, since indeed make some confusion for an average user when selecting between packages and have the Go between there. Generally as I said the website need some lifting with some informations which are hidden to go in the proper place.

About the pull request and my build, as I said above:

"Since POCO F1 is my main device, I didn't stayed to NikGapps to dig the problem because I wanted the device to work as fast as I can and so I didn't tried to take logs or whatever, but this is the issue I faced and not only me, as I said @SPLESHER also faced exactly the same issues. I could test it in my other phone right now but it's the Galaxy S4 and it's ARM. However In case I try NiK in feature I will contact you if I face the same issue".

(BTW-Would be nice to also make ARM packges for old devices)

As I said in my previous post, I didn't faced these issued myself so I cannot quarantee about these reports, but I see a lot of reports with the same issues, so it make me thinks.

Don't get me wrong, I like the idea of NikGApps and the novelty which you can create your own build, and you were my first choice while choosing which GApps to flash but the mentioned issues I faced (and also confirmed by other user) made me reconsider and suggest in my thread and general when people asking a different GApps. However I always say that NikGApps Core is working fine and I have them awarded in my therad but for people who need at least to replace basic AOSP apps there is may be a problem.

I didn't started the comparison between GApps, I just replied to a question and said my opinion and what I encountered when I got asked. There is no intension to defame NikGApps and you are very helpful and good dev, I just didn't had time to contact you earlier about the issues I faced.

This conversation may be good about some changes that could be done in NikGApps if you agree.

@a9k1t

There is also the Basic FlameGApps which come close to Nik Core and you can also use the simple config to make it exactly how u want.

Everyone have it's own taste regarding GApps but lets agree the "ready packages" of Flame has much better combinations and can cover the majority and the general audience out of the box and and the config is so clean and simple.

@amn1987

I never faced bootloop with Flame. You did clean install wipe everything+format data before installing them? Do u use it in A12L/A12.1 ROM? Because Official FlameGApps doesn't support A12L yet but you can get a modded version which I made here to work.