Search This thread

Nikhil

Senior Member
Sep 26, 2012
1,697
2,675
Ahmedabad
OnePlus 7 Pro
Xiaomi Poco X3 Pro
Hello all.
I have a Pixel 7. Im trying to use LineageOS. I tried installing both CalyxOS and Lineage with Micro but sadly neither OS has the necessary functionality required by the app Duo Mobile to allow google logins. That led me to falling back to using a GApps toolset. I've been reading that I need Trichrome library, webview installed which your Gapps has. Also when I try to install from Aurora I get compatibility errors. But after 2 weeks of submitting custom configs I'm still not getting Duo to give me the login prompts. The only way so far that I have been able to get Duo to work on 3rd party OS is by using Nik Gapps Core config.

After looking at the .config for "Core" package I see that almost ALL options enabled. I was hoping I could reduced Googles foot print on my phone beyond the what the "Core" package provides.

Can anyone tell me what is the absolute minimum options I need to enable in the .config file to get the Duo Mobile app to work properly?
Can you link me to any of the pull request that you've submitted and has been waiting? I'm sure there will be necessary response if there was an issue with the config that you submitted.

Also, your best bet is building the gapps with core + Google chrome addon.

Alternatively, you can download NikGapps core and Google Chrome addon from sourceforge.net and flash it in recovery. There's Google duo app available too. No harm in flashing that but that can easily be installed from Playstore and would function the same.
 
  • Like
Reactions: ipdev

myi500

Member
Oct 2, 2010
36
3
Jacksonville
Google Pixel 7
Can you link me to any of the pull request that you've submitted and has been waiting? I'm sure there will be necessary response if there was an issue with the config that you submitted.

Also, your best bet is building the gapps with core + Google chrome addon.

Alternatively, you can download NikGapps core and Google Chrome addon from sourceforge.net and flash it in recovery. There's Google duo app available too. No harm in flashing that but that can easily be installed from Playstore and would function the same.
Here is the last 1, I submitted. I thought I did enabled Core and chrome in the .config file. Are you able to see this the file from the link below? But it was already merged... Should I resubmit or just post the .config on here?
 
Last edited:

myi500

Member
Oct 2, 2010
36
3
Jacksonville
Google Pixel 7

Nikhil

Senior Member
Sep 26, 2012
1,697
2,675
Ahmedabad
OnePlus 7 Pro
Xiaomi Poco X3 Pro
I tried clearing data on those and TTS using Swift Backup and then rebooted and still no luck. Oh well.

As for the OTA process, major success! Everything appears to have worked(!), with only one minor exception:

Debloater addon.d appears to not have worked, so Eleven and Seedvault came back after the update.

On my device ROM the respective apps are located at:
/product/priv-app/Eleven
/system_ext/priv-app/Seedvault

And debloater does work perfectly on a zip flash, so the issue is isolated to the addon.d. /sdcard/NikGapps config/logs directory zip attached.

P.S. I noticed /sdcard/NikGapps/addonLogs/NikGapps_addon.log continues to grow with subsequent OTAs, not sure if intentional; maybe it should have a date like the other or get cleared with each OTA, or it should all be in the dated logs?
Both the issues are fixed.
Fix the debloater not surviving OTA update
Fix the incorrect naming convention of addonlogs

It will be released as soon as I finish updating go apps for android 12 and 13.
 

Nikhil

Senior Member
Sep 26, 2012
1,697
2,675
Ahmedabad
OnePlus 7 Pro
Xiaomi Poco X3 Pro
New Stable Release is up - 19th Mar 2023 (Android 10-13)

Changelog:
- Fixed the incorrect naming convention of addonlogs
- Fixed the debloater not surviving OTA update in some scenarios
- Enable pixel launcher animations
- Update the Go apps to latest available versions
- Update NikGapps Logo in recovery
- Minor Script Improvements

Note:
- Clean flash is recommended!

Happy Flashing!
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,435
34,978
Halifax
GT-i9250
Google Nexus 4
If this doesn't work, it's just best to clean flash. I wish I could reproduce the problem to give you recommendations that I know will definitely work.

I am advising this because these apps are the ones responsible behind the scene for the functionality to work and wiping the data should just start fresh.

I decided to grab a logcat for us to see what the exact issue is. It reads kinda interesting, kinda confusing, like something wrong with the download itself: "Unknown source", permissions issue somehow still?

I then experimented by grabbing the URL from the log, downloaded en-US v3008 manually through Chrome, unzipped it into /product/usr/srec and now all don't complain about being out of date. Good workaround so far it seems! 🤠

Does NikGapps add srec? I couldn't find the package when I looked through. I know Open GApps used to push their own from a Factory Image.
 

Attachments

  • alogcat.2023-03-20-22-37-40-0300.txt.zip
    13.9 KB · Views: 8
Last edited:
  • Like
Reactions: Nikhil

Nikhil

Senior Member
Sep 26, 2012
1,697
2,675
Ahmedabad
OnePlus 7 Pro
Xiaomi Poco X3 Pro
I decided to grab a logcat for us to see what the exact issue is. It reads kinda interesting, kinda confusing, like something wrong with the download itself: "Unknown source", permissions issue somehow still?

I then experimented by grabbing the URL from the log, downloaded en-US v3008 manually through Chrome, unzipped it into /product/usr/srec and now all don't complain about being out of date. Good workaround so far it seems! 🤠

Does NikGapps add srec? I couldn't find the package when I looked through. I know Open GApps used to push their own from a Factory Image.
yes, we do, https://gitlab.com/nikgapps/13/-/tree/main/GBoard/GBoard/___usr___srec___en-US
It's should be under /product/usr/srec/en-US folder.
do you have Gboard installed?

also, can you confirm the NikGapps build date that you are on? and that you clean flashed or dirty flashed?

Surprised to see you're still facing the language download issue :unsure: as long as you have AIS, Private Compute Services, Settings Services and you clean flashed 9th march or above build, it should work.
 
  • Like
Reactions: osm0sis

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,435
34,978
Halifax
GT-i9250
Google Nexus 4
yes, we do, https://gitlab.com/nikgapps/13/-/tree/main/GBoard/GBoard/___usr___srec___en-US
It's should be under /product/usr/srec/en-US folder.
do you have Gboard installed?

also, can you confirm the NikGapps build date that you are on? and that you clean flashed or dirty flashed?

Surprised to see you're still facing the language download issue :unsure: as long as you have AIS, Private Compute Services, Settings Services and you clean flashed 9th march or above build, it should work.
Yeah it's like I said, something with the Google account appdata restore seemed to break it for me. Haven't clean flashed again yet since the last one I reported on (0309), just dirty flashed 0311 and now 0319, and poking around to see what I can get working. GBoard is enabled in my config yeah, I just missed srec in there when looking through. 👍
 
Last edited:
  • Like
Reactions: Nikhil

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,435
34,978
Halifax
GT-i9250
Google Nexus 4
Just took another Lineage OTA and had to reflash latest GApps again after to get Debloater addon.d set up correctly, so that got me thinking:

1) Shouldn't it work using the provided keywords/paths even when GApps was flashed after, e.g., a manual removal of targeted apps/files?

2) Shouldn't the addon.d script # prefix be 04- or less so that debloating occurs before app installs, to provide the most space and mirror the order of the install zip?

3) After my usual setup with Full zip then Duo addon zip, I noticed the script ended up with:
Code:
list_files() {
cat <<EOF
etc/permissions/Debloater.prop
etc/permissions/Debloater.prop
EOF
}
So seems something might need adjusting to avoid that sort of duplicated listing?
 
Last edited:
  • Like
Reactions: ipdev and Nikhil

Nikhil

Senior Member
Sep 26, 2012
1,697
2,675
Ahmedabad
OnePlus 7 Pro
Xiaomi Poco X3 Pro
Just took another Lineage OTA and had to reflash latest GApps again after to get Debloater addon.d set up correctly, so that got me thinking:

1) Shouldn't it work using the provided keywords/paths even when GApps was flashed after, e.g., a manual removal of targeted apps/files?

2) Shouldn't the addon.d script # prefix be 04- or less so that debloating occurs before app installs, to provide the most space and mirror the order of the install zip?

3) After my usual setup with Full zip then Duo addon zip, I noticed the script ended up with:
Code:
list_files() {
cat <<EOF
etc/permissions/Debloater.prop
etc/permissions/Debloater.prop
EOF
}
So seems something might need adjusting to avoid that sort of duplicated listing?
1) a manual removal of targeted apps/files? can you please elaborate?
2) Logically, yes! Changes made - Set the Debloater index to 04 to make sure debloater runs first (to make space for gapps restoration)
3) Thanks for finding it, Fixed the generation of duplicate prop values in list_files (addon.d)

Next release will have it incorporated and can be dirty flashed to override the existing addon.d (as long as Debloater.prop from /system/etc/permissions doesn't have duplicates). If the prop file does have duplicate, then a clean flash will fix it. Regardless, it won't hurt the restoration in next OTA update.

I appreciate you bringing in those bugs to my notice, NikGapps is getting better with every release.
 
  • Like
  • Love
Reactions: ipdev and osm0sis

Nikhil

Senior Member
Sep 26, 2012
1,697
2,675
Ahmedabad
OnePlus 7 Pro
Xiaomi Poco X3 Pro
I use the full version. It`s possible that yesterday`s LineageOS 20 build had Android 13 QPR2 merged. Pixel Launcher runs, but the recents panel is broken.
Thanks for reporting, I will take a closer look at Pixel Launcher after I update my op7 pro with next LineageOS 20 build which is due in next 2 days. Meanwhile, can you screenrecord and show how it is behaving?
 
  • Like
Reactions: ipdev
Thanks for reporting, I will take a closer look at Pixel Launcher after I update my op7 pro with next LineageOS 20 build which is due in next 2 days. Meanwhile, can you screenrecord and show how it is behaving?
It's this way, no matter if it is invoked by gestures or 3 buttons navigation.
 

Attachments

  • Screenshot_20230323-223007_Pixel Launcher.png
    Screenshot_20230323-223007_Pixel Launcher.png
    35.9 KB · Views: 18
  • Like
Reactions: Maverickiller

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
15,435
34,978
Halifax
GT-i9250
Google Nexus 4
Just took another Lineage OTA and had to reflash latest GApps again after to get Debloater addon.d set up correctly, so that got me thinking:

1) Shouldn't it work using the provided keywords/paths even when GApps was flashed after, e.g., a manual removal of targeted apps/files?
1) a manual removal of targeted apps/files? can you please elaborate?

I appreciate you bringing in those bugs to my notice, NikGapps is getting better with every release.

My bad, I could've explained that better.

After my last OTA where Eleven and Seedvault weren't removed due to the Addon zip Debloater bug, I just went and deleted those APKs manually.

So then even though I'd recently dirty flashed the NikGapps with the fixes, the Debloater config didn't add anything to the addon.d since I had already manually removed them beforehand.

My question is, why does the exact path need to be detected during the install at all? Couldn't the Debloater config (in my case just the two keywords: Eleven
Seedvault) just be dumped directly into the addon.d script and then the addon.d script could handle it all from there?

And, heck yeah, I'm really impressed by the scope and robustness of NikGapps so I'm pretty excited to see it become a bugless beast! Glad you don't mind my rigorous testing! 🤠
 
Last edited:

Nikhil

Senior Member
Sep 26, 2012
1,697
2,675
Ahmedabad
OnePlus 7 Pro
Xiaomi Poco X3 Pro
I've been told that the Pixel Launcher included in your package is meant for QPR1 only. Is it true?
The Packages are never meant to last a specific release only. They need an update when google brings a bigger change. There are bunch of fixes and features introduced with Pixel Launcher with QPR2 (just like QPR1) which is probably why it needs attention. The dumps are not yet up (should be soon enough) after which we will have an updated apk with their overlays shipped in NikGapps.
My bad, I could've explained that better.

After my last OTA where Eleven and Seedvault weren't removed due to the Addon zip Debloater bug, I just went and deleted those APKs manually.

So then even though I'd recently dirty flashed the NikGapps with the fixes, the Debloater config didn't add anything to the addon.d since I had already manually removed them beforehand.

My question is, why does the exact path need to be detected during the install at all? Couldn't the Debloater config (in my case just the two keywords: Eleven
Seedvault) just be dumped directly into the addon.d script and then the addon.d script could handle it all from there?
The idea behind shortlisting the paths that were debloated by the system was because the execution of finding the folder and deleting it takes a while and we may have multiple folders listed in debloater.config (say 10) but actually only a few exist (say 2). So the execution of deleting "two known paths" vs 10 "find and delete" is faster and optimized.

I did have this in place before and eventually removed it and brought in 'prop' concept which captures the folders we're deleting and operates on them only.

I will try to find an optimized solution and implement a way to delete the predefined folders always.

And, heck yeah, I'm really impressed by the scope and robustness of NikGapps so I'm pretty excited to see it become a bugless beast! Glad you don't mind my rigorous testing! 🤠
Thanks! There are a lot of new things to implement that actually gives full control over gapps. :)
 

R7D7

Member
Jan 3, 2023
5
1
Will someone point me to step-by-step documentation for how to change which packages are installed via NikGapps? I've read All about NikGapps.config carefully several times and still don't understand. While I am very well versed in *nix desktop and server system administration, I am just getting into Android and obviously don't have enough contextual knowledge to understand specifically what to do from the link.

My philosophy is to always start minimal and install things as needed rather than install the world and try to cut back. So I installed LineageOS 20 and NikGapps Core (specifically NikGapps-core-arm64-13-20230218-signed.zip) and they are working. I'd like to now modify which packages are installed.

If I understand correctly, I need to create a directory at /sdcard1/NikGapps and install (and modify) nikgapps.config. I'm then supposed to reflash the zip I used originally (the one specified above I believe). The commands I original used are
Code:
$ adb reboot sideload
$ adb sideload lineage-20.0-20230223-nightly-fajita-signed.zip
$ adb sideload NikGapps-core-arm64-13-20230218-signed.zip
then rebooted from the bootloader. Do I need to repeat the first and last steps in order to reflash after I've set up nikgaps.config?
Code:
$ adb reboot sideload
$ adb sideload NikGapps-core-arm64-13-20230218-signed.zip
 

Top Liked Posts

  • 1
    I went through the logs and noticed that we're copying the GoogleDialerOverlay.apk to both /system/overlay and /system/product/overlay with OTA update. This probably happened due to shuffling of GoogleDialer apk (and the overlay with it) at some point with multiple dirty flashes - looking for space to install.

    Since the overlay is present in both the locations, it is picking the one in /system, whereas the apk resides in /product.

    Code:
    list_files() {
    cat <<EOF
    product/priv-app/GoogleDialer/GoogleDialer.apk
    product/overlay/GoogleDialerOverlay.apk
    product/framework/com.google.android.dialer.support.jar
    product/etc/permissions/com.google.android.dialer.xml
    etc/permissions/GoogleDialer.prop
    
    --following lines are duplicates pointing to system--
    priv-app/GoogleDialer/GoogleDialer.apk
    overlay/GoogleDialerOverlay.apk
    framework/com.google.android.dialer.support.jar
    etc/permissions/com.google.android.dialer.xml
    
    EOF
    }

    When you perform an OTA update the next time, can you try removing the highlighted lines pointing to system from 09-GoogleDialer.sh and see if you still run into the issue?

    My plan to address this with dirty flash is to run a clean up function at the end of every package installation so it doesn't have duplicate entries of same file with different partitions in list_files function. As a long term fix, I will also ensure, the package doesn't move the partitions on dirty flash to prevent duplicates in the first place. 👍

    Will do! Also, I'd say let's try just the cleanup function first, since the shuffling could still be useful and harmless in most cases.

    Edit: @Nikhil I noticed a number of other apps seem to have the duplicate entries and also duplicate files in the different install locations, though only Dialer is showing a problem at the moment. Will be interesting to see what happens after it all gets cleaned up. 🤔
    1
    Will do! Also, I'd say let's try just the cleanup function first, since the shuffling could still be useful and harmless in most cases.

    Edit: @Nikhil I noticed a number of other apps seem to have the duplicate entries and also duplicate files in the different install locations, though only Dialer is showing a problem at the moment. Will be interesting to see what happens after it all gets cleaned up. 🤔
    yes, it's because of the same reason. I hope the other apps don't cause as much issue as google dialer. Although, dirty flashing is a workaround for now.
  • 5
    New Release is up - Android 10-13 (29th May 2023)

    Changelog:
    • Fixed the incorrect calculation of space after the installation was finished
    • Delete stuff before restoring the files to make space for gapps during OTA
    • Install the apps with largest size first - After Core/CoreGo is installed
    • Fixed Velvet/GoogleClock/AndroidAuto/Gboard/GoogleSounds not restoring after OTA update
    • Log file details when copied over OTA update

    Download

    Note:
    Make sure to backup your data before updating to the latest version.

    Happy flashing!
    3
    Oh? Attached. Okay, maybe I'll hold off until you look into this then, since I don't want to just straight up invite disaster if it's sure to fail. 😛

    Edit: Just saw your edit, yeah let's canary it up if it makes it more likely to work! 🤠
    Here you go - NikGapps-full-arm64-13-20230503.zip (highly compressed build :p)

    Changelog
    - Fixed the incorrect calculation of space after the installation was finished
    - Delete stuff before restoring the files to make space for gapps during OTA
    - Install the apps with largest size first - After Core/CoreGo is installed
    - Fixed Velvet/GoogleClock/AndroidAuto/Gboard/GoogleSounds not restoring after OTA update
    - Log file details when copied over OTA update

    The velvet sh file you shared, if you check list_files, it only contains prop file, so while restoring - the apk never restores. This is fixed with the shared build.

    If all works out, it will make stable branch. :)
    2
    New Release is up - Android 10-13 (29th May 2023)

    Changelog:
    • Fixed the incorrect calculation of space after the installation was finished
    • Delete stuff before restoring the files to make space for gapps during OTA
    • Install the apps with largest size first - After Core/CoreGo is installed
    • Fixed Velvet/GoogleClock/AndroidAuto/Gboard/GoogleSounds not restoring after OTA update
    • Log file details when copied over OTA update

    Download

    Note:
    Make sure to backup your data before updating to the latest version.

    Happy flashing!
    Dirty flashed flawlessly! Brilliant job!
    2
    Okay, one thing after the OTA I just took... 😘

    Phone (Dialer) suddenly gets the "-downloadable" version from the Play Store and I lose Call Screen (which I had enabled in phenotype db), so suggests something went wonky, though it's still not a user app.

    I had recently noticed this just before the 0529 GApps release and the dirty flash actually fixed it and brought the correct version and features back, and suspect another dirty flash will do the same.

    Edit: Yep, a dirty flash immediately triggered a Play Store update to the better Phone app variant. So there's something to be fixed in addon.d I guess! Perhaps the addon.d script numbering might need to be made to match the new size-based ordering in the installer? Not sure if that could cause this somehow.

    Here's the log from the latest dirty flash which fixed things again, for comparison.

    So both log zips are 0529 fixing the Phone app after it had broken from addon.d, and then that's the latest addon log. 👍

    I went through the logs and noticed that we're copying the GoogleDialerOverlay.apk to both /system/overlay and /system/product/overlay with OTA update. This probably happened due to shuffling of GoogleDialer apk (and the overlay with it) at some point with multiple dirty flashes - looking for space to install.

    Since the overlay is present in both the locations, it is picking the one in /system, whereas the apk resides in /product.

    Code:
    list_files() {
    cat <<EOF
    product/priv-app/GoogleDialer/GoogleDialer.apk
    product/overlay/GoogleDialerOverlay.apk
    product/framework/com.google.android.dialer.support.jar
    product/etc/permissions/com.google.android.dialer.xml
    etc/permissions/GoogleDialer.prop
    
    --following lines are duplicates pointing to system--
    priv-app/GoogleDialer/GoogleDialer.apk
    overlay/GoogleDialerOverlay.apk
    framework/com.google.android.dialer.support.jar
    etc/permissions/com.google.android.dialer.xml
    
    EOF
    }

    When you perform an OTA update the next time, can you try removing the highlighted lines pointing to system from 09-GoogleDialer.sh and see if you still run into the issue?

    My plan to address this with dirty flash is to run a clean up function at the end of every package installation so it doesn't have duplicate entries of same file with different partitions in list_files function. As a long term fix, I will also ensure, the package doesn't move the partitions on dirty flash to prevent duplicates in the first place. 👍
    2
    unfortunately not. I tried it today and i have again no sound after updating Speech Services.
    Downloading Speech files fails with no error message
    Here's me figuring out what sounds like the same problem you're seeing: https://forum.xda-developers.com/t/android-13-gapps-nikgapps-arm64.3915866/page-72#post-88333731

    Ensure all the apps I listed have their "App info" > "Mobile data & WiFi" > "Allow network access" enabled. And make sure you have GBoard enabled in your config, since it contains the speech files, and just to be safe uninstall updates on Speech Services and clear data+cache on the Play Store to make sure it's downloading the correct Speech Services.

    Also I'd recommend you dirty flash to the 0503 test build Nik uploaded a few posts back, since it's the most stable recent build until he releases a new official stable.
  • 240
    R5WEmSK.png


    Hi Everyone,

    Here I'd like to Introduce you with my custom Gapps package that I use on day to day basis when I flash a new Rom. As I've observed many people struggling with finding the correct version of gapps to flash, I decided to build a package of my own which lets you flash stable google apps with a lot of variants so you can decide for yourself which package suits you.

    What is NikGapps?
    • NikGapps project started with the goal to provide custom gapps packages that suits everyone's needs. A package that a user needs but cannot find and ends up setting up the device installing more apps and removing unwanted apps manually.
    • NikGapps is a gapps package built from my own device. As my device is always updated with latest version of Google Apps, every time I build a new package, I am on latest and stable version of Google Apps
    • NikGapps also comes with Android Go package for low end devices.
    • NikGapps is a bit different than other Gapps packages (written from scratch, it isn't a port of OpenGapps). It focuses on providing apps that most of the people uses but can't find it in other Gapps packages and ends up installing the apps manually
    • NikGapps supports split-apks
    • NikGapps also comes with nikgapps.config and debloater.config which allows you to control your installation and debloat unnecessary stuff from your Rom respectively.
    • NikGapps is built on a different architecture, the installation method is completely different (Every Package comes with installer.sh that installs itself). Also, it installs the gapps to /product partition instead of /system partition
    • NikGapps also allows you to configure the installation, it can be installed to any partition (be it /system or /product or any other partition which may get added in future)
    • NikGapps also allows you to keep the aosp counterpart of google app if you want (just by using nikgapps.config you can choose whether to remove the aosp counterpart or remove it)
    • NikGapps allows you to dirty flash it anytime you want, it also supports installing on top of Roms with Gapps (except for the pixel flavored Roms)
    • NikGapps also comes with addon packages (useful ones) so that users don't have to flash the whole gapps package just to have the app installed.
    • NikGapps supports the Privileged Permission Whitelisting, providing the necessary permissions to the privileged apps.
    • It supports addon.d so you need not flash the package again and again after every nightly flash
    • NikGapps addon.d functionality is built from scratch which allows you to completely control which app you want to backup/restore on dirty flash.
    • It also allows optimizing Google Play Services (when you turn off Find My Device) so that you can sleep with peace without having to worry about Google play services eating your battery. (Requires support from Rom too in order to work)
    Also, since these are custom build, I can include as many packages as I want (which I do, you can pm me if you want that package)

    NikGapps comes with following packages
    » Core
    » Basic
    » Omni
    » Stock
    » Full
    » Go (for low end devices)

    Although these packages cover a large user base, there are few users who like things differently that is where NikGapps Addons Comes into picture. These Addon packages are separate and meant to flash over NikGapps original packages.

    Everything about NikGapps

    How to create your own custom NikGapps packages!

    Flashing Instructions for A/B devices (Clean Flash is recommended)

    • Flash Rom in Slot A, Flash twrp, reboot to recovery
    • Flash Rom in Slot B, Flash twrp, reboot to recovery
    • Flash NikGapps
    • Flash Debloater (Optional)
    • Reboot

    Flashing Instructions for A-only devices (Clean Flash is recommended)
    • Flash Rom
    • Flash NikGapps
    • Flash Debloater (Optional)
    • Reboot
    How to clean flash NikGapps update without losing data?
    • Delete /system/addon.d folder
    • Dirty flash Rom
    • Flash newer version of NikGapps
    How to remove/uninstall an Addon or Package?

    Here's how

    Enjoy the package! hope it helps you somewhat!

    Downloads
    44
    Credits
    » osm0sis (for the shell scripting template)
    » Arya (for logo and his suggestions and help)
    » Vanced Team (for YouTube Vanced)
    » maartenfonville, nezorflame for creating and maintaining opengapps
    » Lawnchair Team (for Lawnchair)
    » HootanParsa (for MixPlorer)
    » xXx (for his NoLimits module - Amazing work!)

    Frequently Asked Questions

    ChangeLog
    10
    Downloads
    NikGapps Basic
    NikGapps Stock

    Changelog:

    -Fixed FC with Face Unlock
    -Added Google Sounds
    -Added Pixel Launcher
    -Updated YouTube Vanced to latest
    -Updated Google Camera to latest
    -Latest Google Apps (25th June)

    I've created Telegram Release channel for NikGapps. Those who find this useful can get the builds there faster.

    Enjoy! :)
    9
    Hey can we have a package which will replace the default ROMs aosp apps like Google calendar, Google clock, Google dailer, Google contact, google message, google calculator, google gboard, youtube vanced, pixel launcher and wallpaper, Latest Gcam with all the goodies like playground ar sticker included if you cant provide it in a single zip then provide gcam all in one zip separately. Rest all other apps can be downloaded but these apps are needed as default apps in the ROM.

    +1 to this but without the pixel launcher because I like the built launcher
    I'll create one tomorrow. I'll exclude pixel launcher as we can install it separately and there are ported versions available which are preferred over stock.
    As for ar sticker in Google camera, I'll create a separate addon zip as the file size will increase tremendously and not everyone wants to install it.
    9
    Time for another Q update! (12-Jan-2020)

    Changelog

    - Fixed NikGapps installation issues with config values not reflecting in installation
    - Added a nikgapps.config value "2" to retain aosp apps (set the value to 2 if you don't want the installer to delete the aosp counter part of Google app)
    - Aosp Dialer is now deleted by default starting omni package to maintain the uniformity.

    Note: set Dialer=2 in nikgapps.config before flashing if you want the gapps to skip removing aosp Dialer, the installer will remove the Dialer by default.

    Full Changelog and download links are in OP

    Thank you for choosing NikGapps!