yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Nikhil:
You can try a few things.

1. Download from a computer instead of mobile and make sure the file isn't corrupted during download.

2. Sideload the build instead of flashing from external sdcard to make sure flashing from next sd card is not the problem.

3. Share recovery.log from twrp that will provide mode details of what's going on.

Flashing arm64 build on arm device should work, we haven't put any restrictions in that area.
[Android Software Development] lojelo:
Hi Nikhil

I've already done 1 & 2 tried 4 different SD cards but will do it again later for the recovery file.

After a few test last night I think it could be a problem with TWRP which I reflashed with Odin again and still the error appears to happen. So later I will try it one more time with TWRP so I can share the logs so we can see what is actually going on. I am going to try orangefox recovery as well if that doesn't work then I will just use los own recovery and see of that works.

Many thanks for the constructive response.
[Android Software Development] osm0sis:
... Except most of the apps will be unable to function. 🤨😕
[Android Software Development] lojelo:
I have tried both arm and arm64 not much point in assuming things anymore everyone until I put some log files up.
[Android Software Development] Nikhil:
Yeah but he's flashing core, as far as core is concerned, it should work. A lot of users have reported it to work on their arm devices. If he goes higher then the actual can of worms will open :D
[Android Software Development] lojelo:
Sorry I missed this reply, the main issue I have with this device is it's age and I have to install {ROOT} quick reboot because I am having problems with the buttons when trying to get into recovery so installing Magisk is one of the 1st things I need on I can live without google apps but not quick reboot.

I haven't done another clean install yet just thought I would share the log from last night so I have attached a log but don't know if it actually got any info in it regarding any of the google apps information. Is there anything inside twrp I have to tick to make sure it's recording all installation logs?

Thanks
[Android Software Development] osm0sis:
Ah, right! Thanks. I'd still suggest maybe he try your old arm NikGApps Go test build since it'll all be smaller. Any progress on that, by the way?
[Android Software Development] bmwdroid:
Fyi: Flashing core-arm64 onto T810 worked on mine.
[Android Software Development] lojelo:
Update on this I did a clean install again, once again Nikapps/mindthegapps didn't install using twrp, so I ticked the use Lineage recovery box rebooted into recovery but it didn't go into Lineage recovery it went straight back to twrp.

Before I tried this again I downloaded a few more gapps roms and stuck this one on the sd card

MAKSU-LiteGapps-arm-13.0-20240224-official

It installed straight away!!

but these won't install

MindTheGapps-13.0.0-arm-20230323

NikGapps-core-arm64-13-20240307-signed (and I hd NikGapps on before all these issues)
[Android Software Development] retry0001-coffee:
OK. But the docs clearly state it's an ARM not ARM64 device.
[Android Software Development] lojelo:
Just to clarify on that am I misunderstanding this?

ARM = 32bit

ARM64 = 64bit?

because the T810 states the cpu bits are 64bit not 32 bit
[Android Software Development] retry0001-coffee:
Then this page is wrong https://wiki.lineageos.org/devices/gts210wifi/
[Android Software Development] lojelo:
Well the picture I posted is straight from Samsung and not wiki.
[Android Software Development] bmwdroid:
@retry0001-coffee @lojelo perhaps the pic explains all.
[Android Software Development] Nikhil:
what I meant was, grab recovery.log after you've run into error. This one doesn't capture any crashes.

For that matter, I'd prefer you flash magisk and then gapps and then pull recovery.log.

yes, I've been working on setting gapps on auto-pilot mode covering arm, go and atv in addition. It's a pretty huge task but when it will be ready, we will have faster updates in all the areas of gapps, maybe nightly/weekly builds too. :)
[Android Software Development] Ci0llu:
I flashed Nikgapps stock with lineageos 20 on my tablet, everything works fine but now I have two gesture navigation bars, any workaround about it?
[Android Software Development] hankster112:
I recently updated my OnePlus 9 Pro (A/B device) from Lineage 20 to 21 (Android 13 to 14), but NikGApps core refuses to install. My process goes like this:

Flash ROM from TWRP

Reboot to TWRP (to active slot)

Flash NikGApps and Magisk

Reboot into system

The ROM flashes fine without issues but NikGApps is never available from within the system no matter how many times I do this. I got Play services on it once but I don't know what I did to get to that point. What is the proper way to flash this?
[Android Software Development] Abdullah5490:
I struggled allot to install nikgapps_CRDREOID_official package with no success. It says "no space left" and skip all pacakges. I tried default directory, also by changing nikgapps.config to try in /product and /system directory. Everytime I choose to clean flash after changing config file, but all goes into same "no space" error.

I am attaching my logs too. Ending up now, don't know what else to do.
[Android Software Development] Nikhil:
Can you grab the installation logs and share it here? You will find the location of installation logs on screen at the end of installation.

Are you flashing it on top of GSI? the recovery log shows that the mounting is failing due to denial of permission.
[Android Software Development] CGA1:
I noticed that installing NikGapps-crdroid-official-arm64-14-20240307-signed on official crDroid 10.2 on a Redmi Note 12 (Topaz), installs Android Auto as a user app. It needs to be in /system/priv-app in order to work. I've solved with app-systemizer for the time being, but it would be better if it was installed in the right place to begin with.
[Android Software Development] rodken:
Maybe, be certain that you are on the proper slot and/or do not flash Magisk until you boot to system?
[Android Software Development] plemiannik:
Do they need to be updated and if so, how?

Sent from Redmi 5 using ReLabs
[Android Software Development] js-xda:
How to Install NikGapps

NikGapps Website

nikgapps.com

"Note: You don’t really need to update NikGapps between newer versions unless the changelog contains changes that impacts you."
[Android Software Development] MysteryOyster:
Could anyone tell me what am I supposed to download?

I don't understand the download section on Sourceforge. To be blunt, it's a complete mess.

What on earth is this?

This is not explained anywhere.
[Android Software Development] osm0sis:
Pretty basic Android knowledge...

Android version history - Wikipedia

en.m.wikipedia.org

Note the codenames in the first two columns.
[Android Software Development] MysteryOyster:
Not everyone is an expect. I'm just a user who doesn't like stock Android with all its vendor junk.

Why the folders can't be named with numbers is a complete mystery. This is only confusing.
[Android Software Development] osm0sis:
You don't have to be an expert to be aware of the basic fact of Android's famous alphabetical codenames.
[Android Software Development] MysteryOyster:
Why would I? Numbers is what defines versions, and even the damn Android primarily uses numbers. just because the versions _also_ have alphabetically coded code names is Google's quirk, and there's absolutely no reason to primarily use this over numbers whatsoever.

Assuming everyone knows everything is a really bad practice.
[Android Software Development] osm0sis:
Cool, when you're calm again you're welcome to come back and we can help you try to get set up.
[Android Software Development] MJPollard:
Some of us understand where you're coming from and agree with you. Using letters to identify Android versions used to be the thing, but now that Google has moved to using the version numbers as of version 10, IMHO developers would help users immensely by adapting to it. Or why not use both, even? NikGapps-14-U or NikGapps-U-14, for example, would easily convey the same information to all users. But that's only my opinion; Nikhil will do what he thinks is best, and I'll be good with that as it's "his project, his rules."
[Android Software Development] osm0sis:
I wasn't being condescending, let alone a jerk, so that's pretty offensive to me of you to say. Despite him being overly upset/angry right out of the gate I provided the link to help him figure out what the letters meant, and I offered to help in the future when he is able to interact more level-headed. The unnecessary attitudes in this conversation aren't coming from me...

In fact I agree using both letter and number would be totally fine and sensible if Nik wants to consider it. I just also don't think using only the letters is as big of a user-unfriendly catastrophe as it's being made out to be.
[Android Software Development] Nikhil:
@MJPollard the way @osm0sis responded was perfectly fine. If someone is at a level of rooting his device, he must have the ability to do the necessary research/reading before flashing anything on the device.

He may be having a bad day but it's really NOT that difficult to casually ask on the thread rather than reacting about it.

Besides, If one reads the OP, there's a link to 'Everything about NikGapps', the very first thing one can find from the link is the android version referenced letter. The very first thing! Quoting from the website.

I can keep documenting every bit of the project but there's a limit to the details I can go to when I've already logically put it on the website.

Your suggestion is very well taken and I will consider putting it for future releases to provide more clarity, but for now, I don't see this to be more important than bringing QPR2 release after I'm back from the vacation.
[Android Software Development] lord high executioner:
Seem to have lost significantly on meaning for several versions (and years), though. Even that WP link uses version numbers since 10, indicating there are no _official_ code names anymore.
[Android Software Development] retry0001-coffee:
I remember the first time I used NikGapps I had to ask which letter corresponded to the android version. I had no idea about the letters, and I've been using LOS for 10 years+. But I simply asked without the fuss. While I agree that dumping the letter versioning is wise (what happens after Z anyway?), RTFM was an appropriate response to the attitude given.
[Android Software Development] osm0sis:
They always still have official internal codenames though, up to Vanilla Ice Cream for 15 in that second column I pointed to.
[Android Software Development] lord high executioner:
_Official_ is the opposite of _internal_.

I don't recall any media reporting using a code name since release of Pie in 2018 (when it sometimes felt to be impossible to get a version _number_), and the offical Android documentation that the WP article refers to doesn't even mention those internal ones (begging the question how accurate and reliable the information in that WP article is):

Codenames, tags, and build numbers | Android Open Source Project

source.android.com
[Android Software Development] osm0sis:
Semantics argument now, but it's still Google making them up, so I think that makes them official still whether they're internal or not.
[Android Software Development] MysteryOyster:
I am not sure if Debloater is part of NigGapps or not, but since it's mentioned on its page, I guess I can ask about it here.

Can I flash the debloater anytime, or I need to do it during installation? Can I sideload it?

Also what does "for elite and user builds only" mean?
[Android Software Development] Nikhil:
The use of Debloater is to debloat (remove) files/folders from system. You can do it anytime you want. The changes will survive ota update so if you want to undo what you did, you need to delete the sh file with 'Debloater' in the name from /system/addon.d folder.

'For elite and user builds only' is associated with building custom Google apps packages with the apps you need. For e.g. We have omni variant that has say 15 apps, if you only need 12 out of it, you can follow this process and get a zip that will have exactly 12 apps. The same feature also allows you to debloat some of the folders with the same config file. Otherwise, you need to configure a file named Debloater.config located in /sdcard/NikGapps folder.
[Android Software Development] MysteryOyster:
Installing an user build is effectively the same as editing the config file inside the afzc folder inside the zip and changing certain apps not to install though, right?

And to expand on the question, do I understand correctly that if I only edit the config file for a build available on Sourceforge, I need to place a standalone debloater.config into the internal storage under /NikGapps?

Another thing that confuses me about the Debloater is there is nikgapps.config inside the zip as well.
[Android Software Development] MysteryOyster:
Hm, I guess I am doing something wrong.

I am trying to remove the LOS AudioFX app, which is located in /system_ext/priv-app/AudioFX/AudioFX.apk

I added "AudioFX" into debloater.config, placed in folder "NikGapps" on the internal shared storage (that's /sdcard, right?), rebooted into recovery, and sideloaded the debloater zip.

When I rebooted the phone, the app was still there.

What's up with that?
[Android Software Development] Nikhil:
The user build is smaller in size (based on chosen apps), it has download, flash and forget experience, when new updates come, you don't have to update your config everytime to get a new build.

If you prefer editing nikgapps.config under afzc folder, make sure you also set use_zip_config=1 otherwise the installer will pick the config from /sdcard/NikGapps folder.

nikgapps.config and debloater.config goes hand in hand (should also be located in same folder) when you're using debloater because the installer reads nikgapps.config for installer instructions (such as wipe runtime permissions, wipe dalvik cache after installing). debloater.config is only meant to capture folder/files you'd like to remove.
[Android Software Development] Nikhil:
You will find installer logs location at the end of the installation on screen in recovery. Grab them and share it here.

Most likely the issue is with wrong debloater.config being picked up. Can tell you Precisely only after looking at the logs.
[Android Software Development] MysteryOyster:
I have since "fixed" it by editing the config file inside the zip just like with the gapps, but it's weird, because I thought the config in sdcard/NikGapps takes priority (I got that impression reading the installation blog).

Can I access the logs after the phone has booted up?

And one more question regarding the apps installation: what situation does setting -1 for a package apply? I'm thinking, perhaps when you're flashing again to update, because uninstalling something that doesn't exist doesn't make sense.
[Android Software Development] retry0001-coffee:
Hey Nikhil. Just letting you know I updated my OnePlus 6T (fajita) to LOS21 with the latest NikGapps core and it was totally smooth. I did it 100% dirty and everything seems to be working just fine. I'll let you know if there's some issue with play store updates, but so far A+. :) Thanks for all your hard work.

And now I've dirty flashed my Moto G7 Plus (lake) to LOS21 and NikGapps core with equally smooth results.
[Android Software Development] Nikhil:
New Release is up - 19th April 2024 (Android 10-14 stable)

Changelog:

- Fixed Potential bootloops on LineageOs 21

- Update to QPR2 (Android 14)

Note:

This fixes Pixel Launcher crashes, Clean flash if you run into issues with dirty flash!

More changes will come soon, this is to stop the bleeding with QPR2 release!

Thanks for choosing NikGapps.

P.S. Following are the letter references, NikGapps U means gapps for android 14

Q - Android 10

R - Android 11

S - Android 12

SL - Android 12L/12.1

T - Android 13

U - Android 14
[Android Software Development] retry0001-coffee:
bleeding?
[Android Software Development] Nikhil:
Yeah, people going crazy on pixel launcher crashing. Too many PMs.
[Android Software Development] Nikhil:
I suggest everyone to wait for a new build and hold on before flashing 19th April build, one of the tools (aapt2 for those who want to know) was broken on the server due to which it failed generating permissions resulting into bootloop. I'll make a new hotfix release as soon as it is fixed.

Thanks for your patience!
[Android Software Development] nnwwtt:
Too late for me, didn't notice your post (the build is still up, too).

Stuck between Lineage (21 20240419) either bootlooping or starting with just about everything crashing (after reflashing the rom).

Is one still supposed to append "execute.d=0" line to afzc/nikgapps.config? I also tried the "UnInstall.zip" way in Lineage recovery (ADB sideload), but it just keeps reinstalling.
[Android Software Development] Nikhil:
Can you re-download gapps from sourceforge.net under 19th April folder and flash again to see if it boots? I've pushed another release with fix

I tested on crdroid works fine for me.
[Android Software Development] nnwwtt:
Weird.

1. Reflashed Lineage from recovery

2. Restarted Recovery

3. Flashed new NikGapps-full-arm64-14-20240419-signed.zip (sha1 f332f2cb…)

No errors in the installers.

Boots, but everything Gapps related still seems not just "crashing" but downright missing?
[Android Software Development] nnwwtt:
Tried reinstalling two more times, no change. The Gapps just aren't available to Lineage (it can't even find the names of some and presents them as random strings, their sizes given as "0 B").

To uninstall, set Mode=uninstall and every entry below & including "Core=1" to -1, right?

Assuming that won't brick my install? Or any other options?
[Android Software Development] retry0001-coffee:
Are you trying to dirty flash? Because I'm guessing you're beyond that avenue now.
[Android Software Development] nnwwtt:
Afraid so. I take it Lineage installing itself to the other slot isn't enough?

Though I don't get why the Gapps installed by the new NikGapps zip aren't available, clearly they're installed to somewhere

edit: factory reset & 20240420 Nikgapps did the trick
[Android Software Development] Nikhil:
Looks like you're on A/B device, are you rebooting to recovery after flashing the Rom?

Can you grab the installation logs, you will find the location on the recovery screen at the end of the installation.
[Android Software Development] Mine1003:
Hey guys,

i head that in newer gapps updates Googles Wellbeing is included?

I'm on LOS 21 on my Oneplus 8t... Is it safe to do a dirty flash without wiping my data? How do i do it?
[Android Software Development] hankster112:
Sorry for the late reply, install log is attached. Let me know if you need more info.
[Android Software Development] hankster112:
Ok and right after I post this it's working again.

All I did was get the latest versions of LOS/NikGapps/Magisk, reinstall them (run NikGapps uninstall > flash LOS to inactive slot > reboot to recovery > flash NikGapps > flash Magisk > reboot to recovery > flash NikGapps again), and now Play services and Magisk are back and working? The only change I really made was removing my device's PIN to prep for a TWRP backup and restore.

I don't get it but I'm not complaining.
[Android Software Development] lord high executioner:
Finally got to update my `lemonadep` and everything went smootlhy and works.

Thanks for your work @Nikhil !
[Android Software Development] js-xda:
Practical question on the manual for upgrading between Android versions: You mention "delete all the scripts that has Google Apps name in it" - what about the "XX-ExtraFiles.sh" being also part of NikGApps package?
[Android Software Development] js-xda:
And another question building on this: How about A/B devices - do I have to delete the mentioned scripts on both partitions or only the active one when flashing the ROM to the inactive slot. And flash GApps to the then active slot after reboot to recovery? Sorry for the questions but the A/B concept is still not 100 % clear to me when approaching an upgrade as this.
[Android Software Development] Nikhil:
Yes

Only the active one.

In A/B partition device, you need to flash the rom, this switches the active slot from A to B (and vice versa) which needs a recovery refresh before you can flash anything else on the active partition, that's why you need to reboot to recovery, after that, you can flash gapps or any other mods.
[Android Software Development] js-xda:
Thank you for your reply! :) Background of my question before boils down to "which scripts are executed while flashing a ROM to the inactive slot - the ones from the inactive or the active". Now, I know. :) The logic for flashing the GApps only after reboot to recovery was easier to grab for me.
[Android Software Development] cnul:
Hi, i have a question. What are Config release exactly ?

I spotted a file from 03 May 2024 in "NikGapps-U" named NikGapps-evrythingbutpixellawncher-arm64-14-20240503-unofficial.zip 1.3 GB
[Android Software Development] js-xda:
Well, running into another issue: If I don't have root and use the LineageOS recovery - is there any way to remove the scripts actually? Using adb shell, I have only read-only access to system.

Maybe also good to mention: I am trying to upgrade from LineageOS 20 to 21 and use only NikGApps core - no additional addons from NikGApps, Magisk or so on top (besides ih8sn). So, also not sure whether the removal is relevant in that case? Or should I try via uninstalling?

Content of /mnt/system/system/addon.d/ (after mounting system in recovery):

05-ExtraFiles.sh
05-GmsCore.sh
05-GoogleCalendarSyncAdapter.sh
05-GoogleContactsSyncAdapter.sh
05-GooglePlayStore.sh
05-GoogleServicesFramework.sh
50-lineage.sh
60-ih8sn.sh
[Android Software Development] js-xda:
Not 100 % sure but I think this should answer your question:

GitHub - nikgapps/config

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

github.com
[Android Software Development] Nikhil:
Yeah, those are builds created by users. Those are custom ones built using their config file, if you're flashing NikGapps and do not need a few of the apps from the variant you're flashing, you can have your own personal build created with exact number of apps you need.

Rename any NikGapps zip you're flashing to 'RemoveOtaScripts.zip' and flash it in recovery.

(Only) If you're sideloading, then open any nikgapps zip, update the contents of zip_name.txt to RemoveOtaScripts.zip. Zip_name.txt contains name of the zip, so if you change it to RemoveOtaScripts.zip, the installer will get an instruction to remove the addon.d files.
[Android Software Development] retry0001-coffee:
Did you forget to turn on usb debugging? Sounds like it. Also there is adb root shell command. But without USB debugging enabled, you won't get anywhere.
[Android Software Development] js-xda:
Thank you - had to figure out that "any" implies any NikGApps zip after at least lineage-20.0-20230813-nightly-hotdogb-signed.zip - it functions flawless with the latest one such as NikGapps-core-arm64-14-20240420-signed.zip. :)

Forgive my ignorance / lack of knowledge: Does this setting in the actual system have an impact on adb in recovery? I tried but it made no difference to what I observed before.

In the end, I succeeded (as far as it looks right now) with a dirty flash on hotdogb from LOS 20 to LOS 21 - and I learned again something. Thanks to both of you for thinking along!