yashsingh1/xdaforums huggingface dataset:
[Android Software Development] R7D7:
I believe I successfully added GoogleContacts to Core on T by downloading the addon, unzipping, changing to GoogleContacts=2 to keep AOSP Contacts also, zipping it back up, and sideloading. But it adding my Google account failed and brought me back to the same skip/add scree. I was also unable to Add Account from settings also so there must be some other addon required. What additional addons are needed to get Google Contacts working and synchronizing?
[Android Software Development] retry0001-coffee:
I just use core without all those gymnastics, and my contacts sync just fine with google. Google Contacts Sync must be in core. Yup it's even listed at the website under the core list: Google Contacts Sync Adapter
[Android Software Development] RoG khenwaY:
i want to uninstall gapps from my custom rom LineageOS 20 so how can i do that ???

plss help
[Android Software Development] Doomguy6:
Ability to uninstall selectively as well as completely​

Often a particular version of google app starts causing issues after installing and users starts to find ways to get rid of it.

Many times they mess up and eventually reflash the whole Rom and gapps skipping the problematic app.

If you find yourself in such case, don’t worry, we’ve got you covered. All you need to do is follow below steps

Uninstall NikGapps completely (This will remove all the traces of NikGapps from your system)​

First Method (when you are in recovery and cannot make changes to nikgapps.config)

Rename the zip you flashed to UnInstall.zip

Flash the zip to your device

Note: this method is supported only when you are not sideloading the zip, when you sideload the zip, the name of the file you are flashing changes and the installer will not be able to recognize your instructions to uninstall the apps.

Second Method (when you can make changes to nikgapps.config file)

set execute.d=0 in nikgapps.config

reflash your Rom

Note: this method only works if you have decrypted storage, for encrypted method try First method or the Ultimate method.

Ultimate Method (when first method and second method doesn’t help)

Uninstall all the playstore updates of google apps that you want to uninstall (settings -> apps -> find your app -> uninstall updates)

Find files with name #-<Package>.sh in /system/addon.d folder where # can be any number (usually 10, 50 or 51) and delete all the files (for e.g. 10-YouTube.sh, 10-GoogleDialer.sh, etc)

Reflash your Rom

Note: if you are unable to delete the files in /system/addon.d (devices with super partition don’t have the flexibility of deleting files in system), you can use NikGapps Debloater. Make an entry /system/addon.d in debloater.config, place the file in /sdcard/NikGapps folder and flash the NikGapps Debloater.

Uninstall selected packages​

First Method (when you don’t want your aosp counterpart back)

Uninstall the playstore updates of the app

Set <Package>=-1 in nikgapps.config (for e.g. YouTube=-1)

Reflash the zip that you flashed to get the package in first place

Second Method (when you want your aosp counterpart back)

Uninstall the playstore updates of the app

Find #-<Package>.sh file in /system/addon.d folder where # can be any number (usually 10, 50 or 51) and delete it (for e.g. 10-YouTube.sh)

Reflash your Rom
[Android Software Development] RoG khenwaY:
Tysm
[Android Software Development] Dismal.:
Will there ever be a 32 bit version?
[Android Software Development] osm0sis:
I've still got my fingers crossed for a 32bit arm Go GApps at some point. 😁
[Android Software Development] Dismal.:
I got a fire tablet HD 8 it handles full gaaps just fine on Android 11 I was hoping to use android 13 but only mind the gapps which are very limited
[Android Software Development] osm0sis:
My Nexus 7 2013 definitely struggles on Android 11-13, especially with normal GApps (using arm MTG currently), but yeah, very old device.
[Android Software Development] casouzaj:
Pixel Launcher settings and 'At a Glance' customization are broken. I tried the latest full package, as well as the latest Pixel Launcher add-on. Take a look at the recorded screen below. Xperia XZ2 running LineageOS 20.0.
[Android Software Development] Nikhil:
The logs correctly show where the apps are being installed (i.e. /system in this case). However, I will make changes to display the free space too, more elaborative than what it's showing.

installation location doesn't matter (at least till android 13, we'll see about future versions). The AOSP counterpart will be removed with Rom update. The execution of AOSP apps removal happens after Rom is flashed.

When you override with InstallPartition=/system, the addon.d configurations are built based on the overridden values, so the update (newer NikGapps build) should work seamlessly. And upgrade (newer android version) requires dirty flashing newer NikGapps build as you need apks with updated sdk.

When you decide to update a newer NikGapps release, it should not skip any app as long as NikGapps was flashed before first boot when you originally flashed the rom. We generate a prop file which indicates that dirty flashing is okay.

Also, the switch existsm, it is just that it is for a different purpose, you can set WipeRuntimePermissions=1 in nikgapps.config and it will override the dirty flashing rule.

Hope it helps!
[Android Software Development] Nikhil:
I just checked and 'At a Glance' works fine for me. May be clean flash is required?

also, the Pixel Launcher Addon is missing PixelThemes, which will be available in next few mins, so feel free to dirty flash and check if the issue is gone, otherwise clean flash.
[Android Software Development] KaoDome:
Than you very much! It does indeed, I wonder where the Phonesky APK went on the first install :S, I just took another look at the previous logs and there was space in /product before and after its installation, GmsCore was the first that needed to be copied in /system.

Must have been a fluke ¯\_(ツ)_/¯
[Android Software Development] casouzaj:
I dirty-flashed today's Pixel Launcher add-on, but issues with `At a Glance'' customization and Pixel Launcher settings remained unchanged. Not ready to start from scratch for the time being.
[Android Software Development] osm0sis:
Dirty flashed 0410 over 0408 and then took the latest Lineage OTA and the addon.d removals seem broken again...

Seedvault, AOSP Keyboard, etc. are all back, plus Eleven wasn't removed by the Debloater.

It's really frustrating that there are this many regressions from 0319. You finally had everything reliably solid on that build... 😕
[Android Software Development] Nikhil:
Yeah i was in the middle of a lot of script changes to bring in optimizations when QPR2 arrived and started crashing stuff, leaving me no choice but to make a release with those fixes. I tested many scenarios and overlooked a few in rush. I'll take my time and test every piece out before making another release and ensure the debloater and ota update both works flawlessly. I went through the logs and found the root cause, thanks for sharing the logs and making it easy. (y)
[Android Software Development] casouzaj:
I dirty-flashed in recovery today's LineageOS 20.0 build, followed by the latest full Nikgapps package. Issues with 'At a Glance'' customization and Pixel Launcher settings are gone. Everything seems to work now. Thanks, Nik!
[Android Software Development] Nikhil:
The debloater changes that we discussed previously are in

Allow debloating stuff that is already deleted over the air · nikgapps/build@937d872

- Up until now, when we configured debloater.config to delete something, the addon.d qualified the Folders only if they existed in the system. - Now, we're introducing the ability to debloat st...

github.com

now, the installer will consider all the listed entries in debloater.config and generate the addon.d script. Even when the app folder is deleted manually before flashing Debloater/NikGapps zip (e.g. you flash the rom, nikgapps, delete Eleven manually and configure debloater.config to include Eleven, reflash NikGapps/Debloater.zip for installer to regenerate the addon.d file -> perform OTA update -> Eleven will be removed).
[Android Software Development] Nikhil:
I'm glad, hope the next OTA update works flawlessly for you. meanwhile, can you attach the installation logs?
[Android Software Development] RoseTheFlower:
Is there a way to get this to support swipe typing on AOSP keyboard? Open-Gapps contains swypelibs that sorts it out.
[Android Software Development] osm0sis:
Dirty flashed 0418 several times and the space calculations seem off again; it moved a bunch of stuff around each time due to thinking it's out of space. The flashing output being more clear on this was a nice change!

I seem to recall on 0319 that things were reproducible and locations and reported free space for things would settle after at most a couple dirty flashes.

I ended up flashing ROM again, and then flashing GApps from Lineage Recovery to make it a "clean" dirty flash.
[Android Software Development] Nikhil:
Can you please share the installation logs?
[Android Software Development] osm0sis:
I grabbed you some fresh logs of dirty flashing over my latest "clean dirty" flash.

It at least seems a bit more predictable now over the "clean dirty" than it did over 0408->0410->0418. With that it was involving system_ext and various seemingly random apps were doing it. Now it's just GmsCore, GBoard, Velvet and sometimes GooglePlayStore.

The storage calculations progress as things get moved around:

(clean system - Lineage Recovery)

- /system available size: 969388 KB

- /product available size: 897852 KB

- /system_ext available size: 53320 KB

- Total available size: 1920560 KB

(dirty 1 - TWRP)

- /system available size: 310652 KB

- /product available size: 5652 KB

- /system_ext available size: 61312 KB

- Total available size: 377616 KB

(dirty 2 - TWRP)

- /system available size: 50028 KB

- /product available size: 4476 KB

- /system_ext available size: 61312 KB

- Total available size: 115816 KB

(dirty 3 - TWRP)

- /system available size: 42848 KB

- /product available size: 175448 KB

- /system_ext available size: 61312 KB

- Total available size: 279608 KB

(dirty 4 - TWRP)

- /system available size: 140924 KB

- /product available size: 77224 KB

- /system_ext available size: 61312 KB

- Total available size: 279460 KB

Weird that total available changes so drastically the first few times.
[Android Software Development] Nikhil:
i guess, 4th time is the charm :D kidding!

I went through the logs and it appears that the apps found to be skipping have larger required size (below are sizes in kb) than what system is left with - after installation. They are working as intended. You can check the available sizes before they are installed in package logs.

- GBoard (required - 188739 kb)

- Gmail (required - 104367 kb)

- GooglePlayStore (required - 62586 kb)

- GmsCore (required - 167805 kb)

- Velvet (required - 404647 kb)

It is noteworthy that we updated chrome apks with 18th April release so dirty flashing should bring changes in the total size left which might be the reason why there was shuffling of apps in the first two dirty flashes.

It appears to me that the apps eventually settled on the partitions and if you had performed a 5th dirty flash, it would have given you similar stats as 4th time. More importantly, all the apps were installed (correct me if I am wrong, were there any crashes or apps missing?)

Thanks to you, I did notice a glitch in the logs where instead of calculating space (after installation) from /system/product, it is calculating space from /system, not that it imacts the flashing, it just logs wrong sizes after installation. Regardless, I think I need to make the function more robust and not stop searching after it finds a substring '/system' in '/system/product'. Duh!

I will be keen on finding out how OTA went for you since I majorly focused on fixing that part between latest release and the release before.
[Android Software Development] osm0sis:
But if all of those apps are already installed, how can it be that there isn't enough space? Removing the existing one should create the exact space to install it again in the same partition. And why is the free space so drastically different, and decreasing at times, if the GApps aren't leaving something behind, or at least miscalculating, in error?

The OTA appeared to work well! Great work on the logging too! But now I just noticed that my ROM's Files app is missing, so it must have gotten removed in error somewhere down the line even though I don't have Google Files enabled in my config. Looking into that now by flashing clean dirty to 0410 to see if it comes back.

Edit: Just discovered I lost Screen Attention again too. 🫤
[Android Software Development] Nikhil:
I am not sure if those libs still work or needs an update, regardless, if you can upload those libs somewhere, I will create an addon for you that you can keep flashing after you flash a Rom.
[Android Software Development] Nikhil:
you have DocumentsUIGoogle selected under GoogleFiles which is why it is happening.

build/NikGappsPackages.py at main · nikgapps/build

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

github.com

The Screen Attention - I haven't made any changes whatsoever with regards to overlays or any other google apps. may be Dirty Flashing is screwing it up somewhere?
[Android Software Development] osm0sis:
Previously the AOSP Files app was only being removed if Google Files was installed I think? I'll poke around. 🤔

A bunch of system apps lost their permissions/data, including Google app, Play Games, Maps, and Speech Services, presumably from changing locations in the dirty flash, so that might explain a few things.
[Android Software Development] Nikhil:
The partitions size calculations that you noticed is coming from system and not from calculations. I checked NikGapps.log and the size summary after you flashed NikGapps full the nth time and the size summary fetched in the beginning of n+1th time matches.

I am unable to do the math looking at the logs because the logs are miscalculating the partition size after installation of a particular app (reading /system when it should read /system/product). I will make sure the logging glitch is corrected with next release and then will be able to determine how the system is showing variations in terms of available size.
[Android Software Development] Nikhil:
That makes sense, in that case, clearing app data to reset it, reapplying the permissions followed by a reboot should fix things.
[Android Software Development] osm0sis:
Any idea which ones I should clear to try and get Screen Attention showing again?
[Android Software Development] Nikhil:
out of these apps, I think, GMS, PlayStore, DPS absolutely needs clearing of data. I would try moving on to TTS if that's not sufficient. Others are highly unlikely to impact.
[Android Software Development] Nikhil:
I think after this, I will implement a way to skip shuffling the partitions if the space is not enough for Core apps and the apps we find to be sensitive. The space should always be enough since we're uninstalling the app but the mystery surprises me.

This way, dirty flashing will be more stable than it is right now.
[Android Software Development] RoseTheFlower:
Thanks. I'm not looking for their inclusion specifically for Android 13 and I wish to have them either as part of Nikgapps or as a standalone package for flashing after Nikgapps. You can get the file by downloading the Pico or presumably the other packages of OpenGapps. It's in the Optional folder inside the archive (though, to be clear, it's installed by default and is actually opt-out).
[Android Software Development] osm0sis:
I believe that for flashing GApps in TWRP after rebooting recovery after a ROM flash one might need to merge snapshots first so that all the free space is accessible. Doing so fixed all the issues I was seeing by allowing the GApps clean dirty flash to put things back where they probably used to be with no uninstalling messages. 🤯

Edit: DocumentsUI Files app is still missing though. I tried >>DocumentsUIGoogle=2 with >>GoogleFiles=0 and it gave me both the AOSP and Google generic "Files" apps in my app drawer, but >>DocumentsUIGoogle=1 with >>GoogleFiles=0 now gives me no Files apps at all where it used to give me the DocumentsUIGoogle generic one. 🤔
[Android Software Development] Nikhil:
probably too late for me right now but can you send the installation logs? I'll take a look in the morning if not before I go to sleep - and get back to you.

I am assuming you flashed Rom to get the aosp Files back and then you flashed NikGapps full with updated config reflecting >>DocumentsUIGoogle=2 and >>GoogleFiles=0. This should in theory skip removing aosp files app but again, the dirty flash rom update might have removed it with addon.d execution (remember, we now forcefully remove the aosp app and "debloater" folders).

I checked the code, should skip removing aosp app when it is set to 2 but again, I need to check the installation logs to confirm.

>>DocumentsUIGoogle=1 should give you the google files app.

Also, Merge Snapshots first? I don't follow. can you please elaborate?
[Android Software Development] osm0sis:
I've flashed a few more times since so I don't have that log now, but yeah Merge Snapshots is an Advanced Feature in TWRP but it's also what happens on boot to Android or on boot to Lineage Recovery after an update.

Dirty flashing the ROM in TWRP_12 on an A/B device means no addon.d running, so it's a clean system dirty data flash, so I then renamed runtime-permissions so the zip wouldn't complain. Merge Snapshots before GApps made all the weird behaviors from the zip go away and made the initial GApps "clean" flash storage space numbers match what Lineage Recovery showed.

Screen Attention is back now. Just the DocumentsUIGoogle=1 generic "Files" app is still missing though all is installed. This was the new issue with 0418 that I noted.
[Android Software Development] Nikhil:
It has been a long time since I used twrp, been on Los recovery ever since twrp support was presumably dropped for my device.

I will check the documentsUIGoogle part tomorrow in my device and see if setting it to 2 works as expected or not.
[Android Software Development] osm0sis:
Note I don't want it set to 2, I just noticed that setting it to 2 brought back the missing DocumentsUIGoogle "Files app" shortcut along with the AOSP Files app.

What I want is only the DocumentsUIGoogle=1 "Files app" shortcut in the app drawer (not the GoogleFiles app, which I intentionally don't want, hence =0 for that in my config), which I believe was there previous to 0418. Maybe it disappeared with the new QPR2 base and I just hadn't noticed?

Everything still appears to work in app file-pickers, just no app drawer shortcut anymore.

So I guess the 2 configs to compare would be:

GoogleFiles=1

>>GoogleFiles=0

>>StorageManager=1

>>DocumentsUIGoogle=1

And

GoogleFiles=1

>>GoogleFiles=0

>>StorageManager=1

>>DocumentsUIGoogle=2

Thanks for looking into things! I spent most of the evening restoring my device, and am crashing now, so apologies for the ramble. 😅
[Android Software Development] R7D7:
Has anyone had problems trying to add a Google account? Clicking on "Add account" in "Passwords & accounts" under settings causes a brief screen flash in which I can see "Add an account" at the top probably as a title but then I'm back at the "Passwords & accounts" screen. Continued clicking repeats the process.

Details: OnePlus6T, LineageOS20-20230413, Nikgapps T core 20230218 + GoogleContacts addon 20230408
[Android Software Development] osm0sis:
Double check that all the apps have WiFi/Mobile access in their app info dialog. Lineage has a tendency to disable these at times.
[Android Software Development] retry0001-coffee:
Hate to say it, because it's a lame solution, but did you try rebooting? It solves at least half of my inexplicable problems in android. I'm having more issues with LOS20 than I did with LOS19 (camera, random SIP client disconnects). Hard to say where the blame lies. Rebooting is always a good first solution unless the problem is completely persistent.
[Android Software Development] Nikhil:
I tried reproducing it and realized it was implemented a long time back (saved me some time). This is coming from the overlay where the Files app shortcut doesn't appear in the launcher with is_launcher_enabled - false.

I could turn it on but would it make a difference?

Also, I tested the 2 configs, and Files app goes away with DocumentsUIGoogle since there can only exist 1 File Manager and the combination of GoogleFiles and DocumentsUIGoogle makes it whole (that's why the packages are under 1 AppSet).
[Android Software Development] osm0sis:
Personally I think the Google Files app is *a bit much*, and just need/like the simplicity of the basic DocumentsUIGoogle. Would be nice if somehow DocumentsUIGoogle's Files shortcut could show up when GoogleFiles isn't installed; a different overlay or something for that scenario? Since the AOSP DocumentsUI that gets replaced *does* provide a shortcut, but I think Google's has the better file-picker.

Have the cake and eat it too, you know? 😅
[Android Software Development] ECrispy:
Thanks for this! I have a few questions, I've flashed roms before but not on a/b devices.

I plan to use NikGapps with crDroid rom for Pixel 2XL (taimen). If I flash rom + gapps package, that needs to be done in both a/b slots? And can that be done in same session by using ' fastboot --set-active=a', flash both zips, then change to b, flash again?

Will I get Google Assistant features if I flash this? I noticed there's something called 'Android System Intelligence' apk mentioned in other places which may be providing these services? Not sure where it comes from?

If I flash stock apps package, will the Pixel launcher replace the one in CrDroid? or is it only meant to replace aosp launcher which I'm not sure is used?

Thanks
[Android Software Development] Nikhil:
Pixel Launcher will replace crdroid.

ASI - yes its essential to get pixel specific features (basically everything that you have in PixelLauncher AppSet)

on A/B - you need to flash rom, reboot to recovery, flash gapps.

flashing the rom happens on the inactive slot and when you reboot to recovery, it becomes active, then you can flash any mods like gapps or magisk.
[Android Software Development] ALFZZ:
Hi Nikhil,

I am using an A/B Device -Poco F3 and my phone is installed with the CrDroid 9.4 A13 custom rom. Each time when I dirty flashed my phone with the latest CrDroid rom update, I performed the following steps:

boot phone to recommended recovery (twrp-3.7.0_12-v7.7_A13-alioth-skkk.img)

flash recommended Firmware (miui_ALIOTHEEAGlobal_V14.0.7.0.TKHEUXM_4f54362c0d_13.0.zip)

flash crDroid rom (toggle auto flash twrp)

reboot phone to recovery

flash NikGapps - (no auto toggle needed) [I used Nikgapps Basic]

wipe Data

flash Gapps Add-ons (no auto toggle needed) [I included AndroidAuto, Gboard, GoogleSearch, Google,Clock, AndroidDevicePolicy, DeviceHealthServices, DeviceSetup, GoogleCalendar, GoogleChrome, GoogleLocationHistory, GoogleMaps, GooglePhoto, GoogleSounds, GoogleWallpaper and SetupWizard] -total 15 add-ons

boot phone to system

For every rom updates, I have no problem and have successfully booted up my phone without losing any apps or files. When any new Nikgapps or add-ons files are available, I will always replaced the existing ones with the latest to flash them together during the rom update using the above steps.

I have recommended the above steps to people who have problem dirty flashing their rom and gapps but they said that my ways of installing gapps and add-ons are wrong. I would like your advice so that I can do it correctly. Thank you.
[Android Software Development] osm0sis:
Velvet, Maps, Play Games, Settings Services and Android System Webview all appear to have become user apps after the latest Lineage OTA. Luckily nothing critical enough to break the ROM it appears, so hopefully I can just dirty flash GApps via recovery. 😬