yashsingh1/xdaforums huggingface dataset:
[Android Software Development] zedoc:
Hi,

if i want the Core version without playstore in config (>>GooglePlayStore=0) and replace it with Aurora and Aurora service after first clean flash ROM, should i install Fakestore from Fdroid also?

Is there a big downside not using Playstore for certain apps or future dirty flash?
[Android Software Development] iamMG:
Hi.

I am trying to install a package. Recovery says "Skipping DeviceSetup" due to insufficient space. 'Fetching System Size' section says '/system available size 1688 KB'. Searching this thread I found that there are many such issues. What's causing them?

I am using crDroid 8.6

Log file attached.
[Android Software Development] Nikhil:
Try debloating a few apps, there's no space left in the system.
[Android Software Development] iamMG:
I tried debloating but it's not working. I am flashing 'Debloater-20220429-signed.zip' using 'adb sideload "D:\Downloads\crDroid ROM\Debloater\Debloater-20220429-signed.zip"' from my laptop.

I go to crDroid recovery and go into the 'apply update from adb' option.

I have these lines added in the 'debloater.config' file:

/system/product/app/Jelly
/system/product/priv-app/Eleven
/system/product/app/messaging

This didn't work. So I tried with these lines:

Jelly
Eleven
messaging

Still won't work. What am I doing wrong? There isn't a detailed method mentioned anywhere in this thread.
[Android Software Development] Nikhil:
Can you share the logs?

You don't seem to be doing anything wrong, however you'll find detailed method in faq section on NikGapps website if you want to check that out.
[Android Software Development] iamMG:
Sure.
[Android Software Development] Nikhil:
Where did you keep the debloater.config file? Is it not in /sdcard/NikGapps folder?

In any case, I suggest you to edit the debloater.config file located in the zip and reflash. You're probably encrypted so the installer is unable to read sdcard.
[Android Software Development] iamMG:
Thanks for the quick help. I'm trying to uninstall NikGapps completely as per your website FAQ.
[Android Software Development] Nikhil:
A little tip: set use_zip_config=1 in nikgapps.config in the zip and make changes to that file only before flashing. Since you're encrypted, it's best you make the installer use the config file from the zip.
[Android Software Development] iamMG:
I followed that exact method.

Thanks. I tried this method. It worked. Cheers. Thanks for the prompt replies. I request you to add the line 'if you are encrypted, it's best you make the installer use the config file from the zip' somewhere in the OP or on the #2 post. This is extremely crucial. Might help the next guy. :)

Edit: Most apps are working except Play Store. It's crashing. Also, app name is being shown as 'Last Update'.

These are the crash URLs:

crDroid paste - share logs, bugs, code and whatever else remains in plan text

paste.crdroid.net

crDroid paste - share logs, bugs, code and whatever else remains in plan text

paste.crdroid.net
[Android Software Development] retry0001-coffee:
Can I just say right here, that I'm very impressed with this project. While OpenGapps is still languishing away in endless beta development (or alpha really) with no ETA for android 12 support whatsoever, you Nikhil have been totally on the ball with a great offering for the android community. Over at LOS, they're pusing MindTheGapps which only comes in one, bloated flavor that you *can* customize to slim down, but that's a lot of extra steps. Core NikGapps is working brilliantly on both my phones (a Moto G7 Plus and a OnePlus 6T) with LOS. Kudos to you, sir.
[Android Software Development] Nikhil:
What did you do after uninstalling?

Thanks! :) Not everyone acknowledges that! The next update will be even better.
[Android Software Development] iamMG:
Nevermind, I had not progressed much after clean flashing crDroid ROM. So I will start everything from scratch. Thanks for the help anyway.

I am new to the open Gapps business so cannot truly vouch for what @retry0001-coffee is saying. But I can certainly say that you are very responsive to the community feedback. And seeing the number of regular updates you bring about, I can say that this project is very well maintained and is in capable hands. :)
[Android Software Development] iamMG:
I have a question. In the 'nikgapps.config' file, does the order of the entries matter? I am sure that these lines have to stay together, as they are a part of a 'group':

Core=1
>>ExtraFiles=1
>>GooglePlayStore=1
>>GoogleServicesFramework=1
>>GoogleContactsSyncAdapter=1
>>GoogleCalendarSyncAdapter=1
>>GmsCore=1

But other than these groups, can I bring other individual apps closer together? For ex:

DeviceSetup=1
PixelSetupWizard=0
AndroidDevicePolicy=1
GooglePartnerSetup=0
[Android Software Development] :
Yes, I have been doing this for a long time.
[Android Software Development] Seb_Lz:
Hello and thanks for this great project !

I've been running NikGapps with LOS 18.1 (Android 11) for a while on my Poco F3 but have recently had issues with Gboart (constantly crashing => I uninstalled it) and "Hey Google" feature (greyed out - not working anymore). I've also noticed that I can't find any "nikgapps.config" on my device (neither in /tmp, nor in /sdcard/NikGapps), but I do find scripts in /system/addon.d/ (cf picture). As suggested earlier on this thread, I wanted to delete 50-GBoard.sh and reflash LOS ROM but its located in a read-only partition so I can't execute the operation (the device is rooted but I am still not sure if it's a good idea to try and remount the partition in r/w to do that).

Is there a recommended way to reinstall in a proper way the gapps and maybe solve the "Hey Google" and GBoard problems?
[Android Software Development] Nikhil:
It's hard to fix GBoard without clean flash once it is tempered. You can try this.

- Use latest available gboard addon

- Open the zip file and locate nikgapps.config in it

Set use_zip_config=1 (this will force the installer to use config from zip)

- Set GBoard=-1 in nikgapps.config

- Flash gboard addon (this should uninstall gboard)

- Delete /data/misc_de/*/apexdata/com.android.permission/runtime_permissions.xml

- Flash untouched gboard addon (different than the one that you modified)

Like I said before, it's hard to fix gboard once tempered, you should be able to install gboard with above method but I can't guarantee that you won't run into any issues after that.

If this is too much to do, just clean flash.
[Android Software Development] Seb_Lz:
Dear Nikhil, thanks for taking the time to answer my question, it's really appreciated.

The steps you describe are clear and I see no difficulty executing them, but I understand this won't garantee the expected result. I guess it's probably time for me to start over clean again (and maybe take the opportunity to try Los19.1).

Small question: is it mandatory to flash with embedded cfg file and 'use_zip_config=1' when you have an A/B device? Or can I simply put the cfg in /sdcard/Nikgapps and flash the gapps zip after rom Ota update?
[Android Software Development] Nikhil:
use_zip_config is only for those who are sideloading or have encrypted /data partition as in these cases chances are your recovery isn't going to be able to read /sdcard/NikGapps folder

More info on it here: https://nikgapps.com/misc/2022/02/2...e-sideloading-or-running-on-encrypted-storage
[Android Software Development] retry0001-coffee:
Honestly you should be on LOS19 by now. There have been enough CVEs patched that unpatched 18 code is not a good idea. With that said, you can dirty flash from 18 to 19. I did it and have had no problems on my OP6T. I clean flashed my Moto G7 plus, but that was because I had to put the last stock ROM on it to get some sort of update that fixed problems on Tmob with registering as a device capable of using VoLTE and Wifi calling. Huge pain that was, but story for a different XDA thread :).
[Android Software Development] Doomguy6:
Hi.

Can i dirty flash 12.1 gapps over 12 or i need to do a clean flash first?
[Android Software Development] Nikhil:
Clean flash
[Android Software Development] Seb_Lz:
Just to give a feedback: I went to LOS 19.1 (clean flash) and installed nikgapps full package (I unticked some apps, but kept things like gboard, google assistant, chrome,...). Everything seems to be working great so far, even Hey/Ok Google feature, android auto, etc. Great job @Nikhil !
[Android Software Development] lm089:
Hi,

I'm running LOS19.1 on my OnePlus6, until yesterday with NikGapps Core build 20220421. When I originally installed NikGapps back in April I think there was no 12.1 version available so I installed the one for A12, which was working fine.

However there was this slightly annoying bug with the location indicator frequently showing up in status bar. Yesterday while I installed the latest LOS OTA (build 20220712) I found out that there was a new NikGapps version apparently addressing that bug, so I decided to go the "clean-flash-without-losing-my-data" way described in the FAQ section, and hey: that location indicator bug was gone, and everything else semmed to be working just fine.

Until today: I'm frequently using an outdoor app "oruxmaps" for GPS tracking while hiking or cycling; that app never let me down since I started using it many years ago.

This evening on a short cycling trip however I realized that the track recording would always stop ~1 second after I had started it.

I tried many things to repair that (delete Cache, even delete all data) but that didn't help.

On my way home I thought hard what had changed since I last used the app without problems (which was the day before yesterday), and the only to changed where NikGapps and LOS updates.

Back at home I ran the following 3 tests:

1. restored a Nandroid I had created just before updating LOS and NikGapps, so that I was back at LOS build 20220705 and NikGapps build 20220421 >> result: oruxmaps again worked fine, as usual, no problems with recording GPS tracks

2. staying at the older LOS build I again performed the NikGapps update the way described in the FAQs (yes, I uninstalled play store updates, deleted all "51-*" scripts, dirty flashed LOS 19.1 build 20220705, then the latest NikGapps, also rebotted to recovery in between etc); so now I was at LOS build 20220705 with NikGapps build 20220709 >> result: oruxmaps again would beheve strangely and would not record any track

3. repeat step 1 with the same positive result, then did another LOS OTA plus reboot so that now I am at LOS build 20220712 with NikGapps build 20220421 >> result: oruxmaps working fine as ever.

I know, that sounds extremely weird that NikGapps would be causing an app to malfunction but that is the only conclusion I can draw here.

Let me know If your interested in logs (although I wouldn't know which type of logs that would be)
[Android Software Development] Nikhil:
Hi, can you ping me on Telegram? @inikhilmenghani
[Android Software Development] retry0001-coffee:
Hey I have that location indicator thing going on too. I didn't think it had anything to do with NikGapps. Is it something to be concerned about? I mean it's not *that* annoying, unless it indicates excessive battery drain or actually leaking location when I have all location /gps stuff shut off.
[Android Software Development] Nikhil:
As reported by some of the users, the fix relies on Rom side change too. Assuming you're on latest Los 19.1, you should not see the location indicator being accessed by phone services on latest NikGapps build, I've removed all the permissions which were previously set by default.

I do have mixed feedback, some of them say that it's fixed for them and some say that phone services is accessing location in the backend. I personally am not able to reproduce so it's kinda hard to actually confirm if the issue is at rom side or gapps.

I'd suggest you monitor your battery and the services consuming it to gauge if the issue persists.
[Android Software Development] retry0001-coffee:
Well the location display in the upper right corner (little green icon) persists. I can't really tell if it's a battery drain or not. 19.1 seems to be a bit more of a drain than 18.1, but it could be my imagination or just my phone's battery has wear leveled some.
[Android Software Development] Nikhil:
Oh you're on 18.1, I've made the changes only to Android 12.1, guess I'll have to back port to a11 too. Next release!
[Android Software Development] retry0001-coffee:
No I am on 19.1 . I installed NikGapps when I flashed to 19.1 because I had been using openGapps but their project is a mess now. I'm using NikGapps core and LOS 19.1 . I am on the June 23rd build right now: https://download.lineageos.org/fajita I'll probably update to the next July release since it will include CVE patches.
[Android Software Development] Nikhil:
Let me know if the issue still persists after you update your Rom and flash latest NikGapps build (9th July)
[Android Software Development] retry0001-coffee:
Oh i had no intention of updating NikGapps. I mean I'm just doing OTA updates for LOS now. How would I go about flashing NikGapps? Can I do it after I update LOS and boot into it, or do I have to do it all from recovery before first boot?
[Android Software Development] Nikhil:
The fix from gapps end came with 9th July NikGapps release. If you are on older build I highly doubt updating rom will auto fix for you.

Since the new release removes a lot of unnecessary stuff, dirty flashing it via recovery won't help.

You'd have to clean flash :(
[Android Software Development] retry0001-coffee:
Does that mean I have to wipe out my data partition and lose all my stuff? (i.e. clean flash LOS too?)
[Android Software Development] Nikhil:
Well, there's a way to update nikgapps without losing data.

Details are on FAQ page (How to clean flash NikGapps update without losing data?) - https://nikgapps.com/faqs

But I would take a nandroid backup before updating, just in case!
[Android Software Development] retry0001-coffee:
OK I was just looking at that FAQ item as you were typing that out. Sorry to make you do that, when you wrote a pretty clear FAQ. But it gets confusing between clean flash and dirty flash when there's nikgapps and the underlying ROM. Anyway, this doesn't sound hard. I will just use adb root and adb shell to get in there and clear that stuff out of addon.d . Then I'll just sideload new LOS and new NikGapps through recovery. Piece of cake ;) .
[Android Software Development] Doomguy6:
Hi

I updated to the newest crDroid 8.7(dirty flash)but playstore isn't working.

Tried dirty flashing again all the gapps(12.1 latest)some add-ons and core but still not working.

I need to clean flash every time the update with gapps?
[Android Software Development] lm089:
@Nikhil No pressure, just curious: did you get my messages on telegram and here (PM)? I'm asking cause I had some trouble re-activating telegram after my account apparently was deleted after a year of inactivity...
[Android Software Development] fenwuwen:
I rarely comment online, but you do a fantastic job.
[Android Software Development] fenwuwen:
I'm getting a lot of errors, all because I'm using android 12.1, but have been using Nikgapps 12. I hate myself for being careless.
[Android Software Development] Nikhil:
Oh! At least now you'll be able to use it without errors.
[Android Software Development] Udeson:
Can someone pls explain to me for which use case do I need this setting in config file?

# set WipeRuntimePermissions=1 if you want to wipe runtime permissions

WipeRuntimePermissions=0

Is there any dependency with the execute.d setting?
[Android Software Development] xVincentx:
I have a request if it's feasible:

I've noticed that NikGapps will consider any flash a dirty flash so long as any file with the name runtime-permissions.xml exists inside the /data partition. This is counterproductive to doing ROM updates, especially in the case of A/B-style phones, whose system image is likely completely overwritten on update. This is ALWAYS going to be the case on any Android device that uses the Super partition rather than separate /system, /vendor, /product, etc. partitions. Some apps included in the fuller packages, including Android Auto, absolutely must exist as a system app otherwise they will not function for their intended use case. Android Auto is one who refuses to do a dirty flash from NikGapps, resulting in broken Android Auto functionality every time you do a ROM update without a /data wipe.

My request is this: Please allow us a way to directly tell the installer that it's being clean flashed even if that file I mentioned exists, as a bad actor could place a file with that name somewhere under /data specifically to prevent it from doing a clean flash. It is easy to revert a change of that nature, though, so long as one has knowledge of a Linux shell, or at least the find command. The other main reason I would love to be able to tell it to act as a clean flash explicitly is for when you're patching the ROM on a device whose /system partition does not retain any previous data during an update. Again, that includes many A/B style phones, and ALL phones whose /system partition is really a logical area of a "super" partition, regardless of A-only or A/B styling.

I don't care really how it's implemented, whether it's by naming the zip, placing some config option somewhere in a file, or even volume buttons. Shoot, even manually installing it from somewhere you can use some kind of keyboard to press a Y/N option would work for me.

In my eyes, it would be simpler for the end user to be able to do so that way rather than go find whatever file (or files, depending on the device, or if a bad actor created another file in another area in /data) that the commands cd /data and find "runtime-permissions.xml" return in output.

The installation is otherwise a simple breeze, and the apps all work flawlessly in tandem with genuine Google-provided updates, as well as having others installed manually from the Play Store if need be. Even by doing that workaround when I went to update the ROM on my phone just a bit ago, I've found no issues that cause any problems. I did it as I didn't want to lose all my data just to have it behave like it's doing a "clean" flash, when on a ROM update, it's technically clean flashing anyway (at least in my case).

I recognize that not all devices operate the same way, and that some may not effectively wipe /system or /vendor on a ROM update (Lineage doesn't wipe /vendor or / out, just /system on my phone, and then writes whatever new files it needs into / and /vendor).
[Android Software Development] Nikhil:
When you flash gapps after first boot, gms fails to get sms permissions and no matter what you do, you just can't provide sms permissions to gms. In such case, you need to wipe runtime_permissions.xml so the permissions are regenerated upon next boot allowing gms to acquire sms permissions.
[Android Software Development] Nikhil:
Hi,

Once you install NikGapps and you get a Rom update, even when you have A/B device, doesn't gapps survive the ota update? (should survive dirty flashing the rom through recovery too). That's the whole purpose of addon.d implementation that you can update your Rom without losing data.
[Android Software Development] Princknoby:
Anyone having issues with the initial setup?

I'm using LOS 18.1 [OFFICIAL], NikGapps Omni.

It is simply impossible to do the initial configuration, when I select WiFi, it goes to the next screen and loads until it gives an error, then I select skip, until it reaches the "Just a second" screen And it keeps loading infinitely!

I tried mobile data and got the same result.

Tried offline configuration and same result... :(
[Android Software Development] retry0001-coffee:
Most phones have moved on to 19.1 . Are you using the correct version of nikgapps for the LOS version? That's the only thing I can guess at.
[Android Software Development] Princknoby:
Sorry, it was really my mistake, I downloaded android version 12 from NikGApps instead of 11. I downloaded the correct version and it worked! Thanks and sorry
[Android Software Development] Nikhil:
Can you try flashing pixel setup wizard on top of your existing setup?

Edit: didn't realize you responded further, glad to know it worked out for you.
[Android Software Development] retry0001-coffee:
My guessing powers are at their peak! Time to go play the stock market...
[Android Software Development] Mycroft2046:
libsketchology_native.so is missing from libs for the latest build, and that crashes Google Markup. Request a rebuild with the included lib file.
[Android Software Development] blinoff82:
I can confirm. Same problem here.
[Android Software Development] Nikhil:
The same has been fixed with latest canary build if you want to try it out.
[Android Software Development] blinoff82:
Of course. Where I can to download it?

UPD: Find it https://sourceforge.net/projects/nikgapps/files/Canary-Releases/

UPD2: Same error on canary builds.
[Android Software Development] Shimmy99:
I'm curious. I left another post regarding this in the "HELP THREAD - Ask ANY Question" thread in one of the general forums but got no useful replies, and am wondering if this place will work better because it specifically concerns the package I am trying to install.

I have a very new (i.e. it was just recently introduced) Android-running computer board (NOT a phone or tablet, but more like an SBC) called the "ITX-3588J" from the Chinese manufacturer Firefly (T-Chip Intelligent Technology Co. Ltd; headquartered in Zhongshan city, Guangdong province). This computer board is very potent - it has an also rather new Rockchip RK3588 processor that packs 8 ARM cores and seems to perform faster than my old 2018 vintage x86 desktop ... from what I have been able to test. And I want to use this as a desktop system running Android 12, which the vendor gives a stock image for.

Trouble is, that stock image is very bare bones. It does not come with the Google Apps - most necessary for me, the Google Play Store. And given that the Open GApps package doesn't appear to support Android 12, I have to use NikGApps instead. Yet the instructions do not really explain how to install it. Note that because this is a general-purpose computer, it has none of the root lockouts and other encumbrances that are typically found on a phone (you can reflash the entire eMMC), so in theory this should be easy, right? Wrong!

At least for me. As someone who's never done this before, after much frustrated googling and failed (i.e. garnering no replies) askings on different sites I managed to piece together what I need to do is to use the Android Debug Bridge (ADB), which I've had for a while because I've used it to develop apps for Android for my phones (e.g. "SI Metric Clock"). And from what I gather, one should be able to load the NikGApps zip using "adb sideload" command.

However, I can't make it work. I reboot the device to recovery via "adb reboot recovery", then when the recovery screen comes up I hit "Apply update from ADB" and then tried to "adb sideload <NikGApps zip name>.zip", and it started then failed at 47% with "E:Signature verification failed", suggesting a security interlock. There did not appear to be any way to override this.

What can I do?

The other thing is that from other googling it seems that perhaps one should use an "Advanced" option in the recovery instead of "Apply update from ADB". However, this recovery has no "Advanced" option. Other instructions suggest using a custom recovery like TWRP, however TWRP is not available for Android 12.

So what can I do to get the NikGApps Google Play pack up and running on this system? Remember: this is not your garden variety phone or tablet.

Thank You!
[Android Software Development] retry0001-coffee:
"Add-ons aren’t signed with an official key, and therefore when they are sideloaded, Recovery will present a screen that says Signature verification failed, this is expected, please click Continue."

It'll hit 47% and stop showing any progress. That isn't abnormal. Just wait. If it still doesn't look like it's completed its task after 5-10 minutes, then it didn't work.
[Android Software Development] Shimmy99:
(rm)