yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Nikhil:
okay so we have an overlay config_recentsComponentName which defines the recents provider without which Pixel launcher crashes.

Apprently, for Lawnchair to work with QuickSwitch (QS), config_recentsComponentName needs to be set under Lawnchair package name (which is what QS does behind the scenes when Lawnchair is selected).

Unfortunately, this is one of the config that can only exist for 1 app at a time (like we can have only one setup wizard). Due to this, Pixel Launcher being itself, it crashes when config_recentsComponentName is set to Lawnchair.

I've tried a workaround here hoping it helps. Attached two flashable zips that are interchangeable. so if you want Lawnchair to be the recents provider with QS, flash the lawnchair zip and you will lose Pixel Launcher, same goes with Pixel Launcher - flashing it will get you Pixel Launcher and you will lose Lawnchair. Only one can exist at a time.

P.S. Lawnchair also comes with Lawnfeed and Lawnicons which are not part of the attached flashable zip, I can easily add those if you prefer, let me know.

Edit: when you set lawnchair as recents through QS, it installs lawnchair as a module and flashing Pixel Launcher will not remove that module, which means you will have PL and Lawnchair installed at the same time, but like I said before, only one can work at a time. I hope I haven't confused you :P
[Android Software Development] Nikhil:
yes, that is a great idea. it can be achieved by following below steps

- uninstall playstore updates (wiping /data/app/<googleapppackagename> and /data/data/<googleapppackagename>

- removing addon.d scripts

- installing newer gapps replacing the existing gapps

I could make it so that users just by renaming the file to upgrade.zip, can perform all these operations and the gapps zip could actually perform an upgrade. :)
[Android Software Development] retry0001-coffee:
Nikhil,

I was contemplating doing the LOS upgrade this weekend (tomorrow). If you do this upgrade thing for the core package, I will test it out for you. I have a OnePlus 6T (fajita) running LOS 19.1 with nikgapps core and no other extras (nice and vanilla). I also have a Moto G7 plus (lake) in the same situation. Let me know if you can have that ready any time soon.
[Android Software Development] Nikhil:
Hey, standardizing this will require a couple of days of development, so getting it done by this weekend will be too tight. If you're willing to wait for another week, I can prioritize this over other things and send you a build as soon as it is ready.
[Android Software Development] retry0001-coffee:
Yeah sure. I was just saying that I was getting ready to do it, but by no means do I have to. Glad to give you the time you need. Let me know.
[Android Software Development] noahhhh:
I got enough space and try to flash gsi on my tab s7+, but the scripts said there is not enough space here. What should I do.

gts7xl:/ # df -ah

Filesystem Size Used Avail Use% Mounted on

rootfs 3.2G 55M 3.1G 2% /

tmpfs 3.5G 12M 3.5G 1% /dev

devpts 0 0 0 0% /dev/pts

proc 0 0 0 0% /proc

sysfs 0 0 0 0% /sys

selinuxfs 0 0 0 0% /sys/fs/selinux

tmpfs 3.5G 0 3.5G 0% /mnt

tmpfs 3.5G 0 3.5G 0% /apex

tmpfs 3.5G 4.0K 3.5G 1% /linkerconfig

tmpfs - - - - /mnt/installer

tmpfs - - - - /mnt/androidwritable

none 0 0 0 0% /dev/blkio

none 0 0 0 0% /dev/cg2_bpf

none 0 0 0 0% /dev/cpuctl

none 0 0 0 0% /acct

none 0 0 0 0% /dev/cpuset

none 0 0 0 0% /dev/memcg

none 0 0 0 0% /dev/stune

tmpfs 3.5G 1.2M 3.5G 1% /tmp

pstore 0 0 0 0% /sys/fs/pstore

none 0 0 0 0% /config

adb 0 0 0 0% /dev/usb-ffs/adb

fastboot 0 0 0 0% /dev/usb-ffs/fastboot

mtp 0 0 0 0% /dev/usb-ffs/mtp

/dev/block/sda37 226G 112G 114G 50% /data

/dev/block/sda37 - - - - /sdcard

/dev/block/sda32 468M 48K 468M 1% /cache

/dev/block/dm-3 3.9M 1.3M 2.6M 34% /odm

/dev/block/sda28 27M 104K 27M 1% /metadata

/dev/block/sda9 16M 576K 15M 4% /efs

/dev/block/sda30 872M 700M 172M 81% /prism

/dev/block/sda31 29M 1.7M 27M 6% /optics

/dev/block/sda12 16M 2.9M 13M 19% /sec_efs
[Android Software Development] RabidWolve:
Installing NikiApps Stock with CrDroid Feb Edition on Mi9t Pro using Orangefox.

Breaks the launchers on first boot, choosing either Pixel or Crdroid Launcher Crashes.

Also on installation through orangefox

Skipping google search and Google Calander due to insufficient space.

Installed Core version for now, everything working good.

Hope it gets fixed. Keep up the good work.
[Android Software Development] retry0001-coffee:
Hey Nikhil, any chance to work on that upgrade-mode script for core yet? I am getting itchy to go through with the LOS upgrade. I can delay further if you're close though. Let me know.
[Android Software Development] Nikhil:
Hey, I spent quite some time in implementing it.

Here are the things I noted.

- with NikGapps installation we remove the folder from existing packages and installs them fresh

- It also overrides the addon.d file

So when you're installing it, it's actually doing half of what it takes to upgrade.

What really makes things complicated is the incompatibility of app data when the sdk changes (which happens rarely but it does). Which is why we advise uninstalling playstore updates so you're back to what system shipped and it can be easily upgraded.

So a way out is wiping all the instances of gms from /data, unfortunately, on a recovery like Los recovery, /data is not decrypted. So there is no way we can touch /data or remove anything from script. Meaning, the uninstalling part has to be manual.

So now, I'm thinking of alternate ways of achieving this. Magisk module is one way of doing it. There may be some other way as well. Let's see. I'll keep you posted.

Edit: I can still make it working for the devices with twrp support which can also decrypt /data.
[Android Software Development] retry0001-coffee:
OK. Well I guess I'll just do it the fully manual way.
[Android Software Development] Nikhil:
If you're doing it manually, can you try flashing rom, flashing newer nikgapps version and see?

There is a high chance that you won't have to wipe anything.

And even if you experience crashes, you can uninstall playstore updates after you've upgraded.
[Android Software Development] retry0001-coffee:
Hmm ok. But what about this: Step 2: Go to /system/addon.d folder and delete all the scripts that starts with "51-" ? Skip that too or do it before upgrade?
[Android Software Development] Nikhil:
You can leave it as is. The installer will take care of it.

As long as you are flashing the same variant (core 13 on top of core 12.1, similarly basic, omni, etc)
[Android Software Development] Prittt:
Hi everybody, I recently moved to crdroid from arrowos but I have issues with gapps, android auto in particular. I made a clean flash of crdroid but when installing suggested gapps (this version) the recovery logged the message "cannot dirt flash, wipe /data to install AndroidAuto".

Any hints?
[Android Software Development] retry0001-coffee:
Alright, so I just dirty flashed both LOS20 and NikGapps core to my OnePlus 6T. Everything seems fine. I immediately updated a couple apps in the play store. Nothing looks different from LOS19.1 . I almost thought the upgrade didn't take. I can't find any NikGapps log from the sideload though. The only nikgapps log there is seems to be from routine OTA updates and the last timestamp is from Dec 2022.
[Android Software Development] KaoDome:
Hi guys, I'm cross-linking an issue I ran into that seems to relate to either Search, or Search and Assistant. There is some context up in other posts, but basically if those two were enabled I'd get a bootloop in a device running crDroid (A13): https://xdaforums.com/t/rom-13-official-crdroid-9-2.4519899/page-2#post-88184253

Just in case there's something to tweak or the incompatibility stems from the current stable release.
[Android Software Development] jpennycook:
My OnePlus 7 Pro was running LineageOS 19.1 with NikGApps. Yesterday, I upgraded to LOS 20 using NikGapps-core-arm64-13-20230218-signed.zip

Google Play Store appeared to work at first - it showed that I had a number of apps that needed updates. It didn't actually download anything (downloads were "pending") and was behaving as though it was offline.

I uninstalled updates for Google Play Store. I cleared the cache and storage for Google Play Store and the cache plus "Clear all data" for Google Play Services. I tried both WiFi and mobile data (in case there was a glitch with my WiFi).

It still was not working - it showed a picture of a sleeping satellite and said that I was offline.

Google Play Store is currently at version 30.4.21-21

In Settings, I went to Apps, click "See all ... apps", looked for Google Play Store, clicked "Mobile data and Wi-Fi", moved the slider on "Allow network access" to the right, and checked that "Wi-Fi data" was also enabled. This got rid of the message about being offline.

Unfortunately, I'm back to the original problem (15 apps show as requiring updates, but apps show as "pending" when I try to download/update them even though I'm on WiFi).

Question - how do I get Google Play Store to download apps/updates again?
[Android Software Development] jpennycook:
Well, that's embarrassing. Assuming that clicking on things randomly and opening play.google.com in a web browser hasn't made a difference, it looks like my Pi Hole might be to blame. I disabled blocking, and app updates worked. Also, Google Play now says "Device is not certified" on the Settings page, which it didn't before.

It turns out that I was blocking gvt1.com and gvt2.com - unblocking those let Google Play Store work. All my own fault!
[Android Software Development] kundifon:
Some custom installation package may save me pretty much manual work. But I'm not sure/ can't find answer in FAQ.

For old Huawei P9-eva is maintained rom still available, but unfortunately come with microG. So for every update/flash new build of rom I have to manually clean up all traces of microG and delete additional apps to get enough free space. Only then Nikgapps instalation is possible.

https://xdaforums.com/t/rom-treble-microg-lineageos-16-0-for-huawei-p9.4078383/page-34#post-88132405

If I configure debloater.config and nikgapps.config then repack instalation package and install it with TWRP. Should this work? I have 3 such phones in family to maintain them.

Do the instalation process first read and execute debloater.config and then carry on with instalation and consider nikgapps.config along?
[Android Software Development] asripath:
From the telegram group

How to configure debloater.config?

1. Find the package name of the apk (MixPlorer is easy to use)

2. Find the install location of the app (run 'pm path packagename' in terminal app)

3. Note the Folder name (usually found in app or priv-app folder inside /system or /system/product folder)

4. Open debloater.config and enter the Folder name (it is case sensitive)

5. Flash latest version of Debloater.zip in recovery

In short

Debloat config

Flash debloat zip

custom config

Flash gapps

NikGapps - Browse /Releases/Debloater/18-Feb-2023 at SourceForge.net

A Custom Google Apps Package that Suits Everyone Needs!

sourceforge.net
[Android Software Development] kundifon:
Sure.

As I see the gapps package, there are inside the zip booth confing files. Coul'd be clean up and gapps instaltion be done in one step? - just flash gapps with proper configured debloater.config and nikgapps.config inside the zip?
[Android Software Development] Nikhil:
Yes you can do that.

You just need to set use_zip_config=1 in nikgapps.config and the installer will read debloater.config to remove the files and nikgapps.config to choose the packages to install.

You can also create your own custom build, that way you will have exactly the apps you want to install and then you won't have to disable packages in nikgapps.config. It will save some data. Check config repository on NikGapps Github.

The key here is to set use_zip_config so the installer reads your modified configs from within zip.
[Android Software Development] xdaattah:
This nikgate gaps has a serious issue, that is pixel launcher...it contains blinking that one can not open any app. I had to reflash the lineage and another gaps before it is working well right now....

This update of 26/02/2023
[Android Software Development] Nikhil:
Which NikGapps build did you flash? It's all fixed with 18th Feb release.
[Android Software Development] osm0sis:
I can confirm something similar, unfortunately.

Something is causing a bootanimation + reboot loop for any NikGApps 13 higher than omni with a clean flash on Lineage 20 on my OnePlus 9 Pro. I'm trying various configuration changes now to try and single out the bad package.

Edit: @Nikhil So it's definitely Velvet that's broken, not sure if it's a permissions issue or what since I can't do both a clean flash and collect adb logs during boot on this device.

Edit 2: Velvet seems broken (or at least doesn't work anymore) as far back as 0908, going to keep going to see if I can find the last one where it works. (y)

Edit 3: Repeatedly clean flashed over a ROM reinstall and can't seem to find any T release that works now when Velvet is in the config. 😲

Edit 4: And flashing MindTheGapps first to get their Velvet, then any NikGApps config excluding Velvet remains working, though obviously messy. I'll see if copying the MTG Velvet.apk over the NikGApps Velvet.apk fixes it directly or if it's more likely a permissions thing.

Edit 5: Yessir, pushing just the MTG Velvet.apk does work! Could still be permissions of course, since it's an older APK, but hey, at least it works. (y)
[Android Software Development] Nikhil:
Thank you very much for finding the root cause.

From your tests, yeah, you're right, it seems to be a permission issue with latest velvet apk since the apk wouldn't cause the bootloop, the priv-app permissions can potentially cause bootloops.

Can you please try below two things?

- Try and get the bootloop logcat, you can flash the rom, boot, edit the nikgapps.config and set WipeRuntimePermissions=1, reboot to recovery and flash NikGapps. (if you are encrypted, you can skip the editing part and just flash rom, boot, enable the developer options, reboot to recovery and flash NikGapps)

- Test the same build on OnePlus 7 pro on latest los 20 (

only if that's possible for you

). I am asking you this because I just flashed latest LOS 20 on my oneplus 7 pro with 18th Feb NikGapps full and it booted fine. I am surprised to not be able to reproduce the same. Attaching the screenrecord.

Appreciate your efforts into narrowing down the root cause! :)

Edit: I did format data (including internal storage as I was switching from crdroid to los) - I've had reports in past of users needing to format data before they can make it work. Very strange and rare but a couple of users reported so if you're into the bootloop after all, can you once try and format the /data and see if that boots up?
[Android Software Development] Nikhil:
Fabulous! I've made the changes, I will release a hotfix build 28th Feb with the changes. Thank you! :)

Fix bootloop with installing Velvet or Google Search addon · nikgapps/build@b71c11d

- Velvet requires android.permission.MODIFY_AUDIO_ROUTING in addition to the ones defined in the app. Thanks to @osm0sis for finding the root cause.

github.com
[Android Software Development] retry0001-coffee:
Nikhil. I just updated my Moto G7+ (lake) with LOS 20 + NikGapps core with no wiping, resets, or downgrades of store apps. Everything seems to be running fine. So that's two devices I've done completely dirty upgrades on (lake and fajita) with so far no negatives. I run pretty vanilla over here. I don't bank, nor use NFC/bluetooth, nor magisk. I mainly use firefox beta, sms, Jabber client, VOIP/SIP clients, email, google maps, and camera apps (stock and opencam). If something changes, I'll be sure to say so, but so far so good.
[Android Software Development] retry0001-coffee:
Well I spoke too soon. I just found out that neither of my phones can send MMS messages. This might just be a t-mobile issue and have nothing to do with NikGapps or LOS. I'm using the stock messenger app, so I don't see how it would pertain to nikgapps.
[Android Software Development] Nikhil:
Try deleting runtime_permissions.xml
[Android Software Development] retry0001-coffee:
OK. where is that located?
[Android Software Development] Nikhil:
It can be found at /data/misc_de/*/apexdata/com.android.permission/runtime_permissions.xml
[Android Software Development] retry0001-coffee:
so I delete this file and then what? Do I have to reflash roms? Do I have to restart the phone? Or will it just regenerate the file on the fly?
[Android Software Development] Nikhil:
Delete and reboot. The file will be regenerated with updated permissions on boot. So if the issue that you're facing is related to permissions, it'll be resolved. If not, then the issue must be something else.
[Android Software Development] retry0001-coffee:
So my oneplus 6T no has no Tmobile data. This happened before I deleted the permissions file. I tried to adjust the APN based on Tmobile's website recommendations (trying to get MMS working) and now this. I did a total network reset and it's not coming back. I'm so pissed off. I don't think this has anything to do with NikGapps or your recommendations. My anger is directed towards Tmobile because they probably blocked my phone for some BS reason.
[Android Software Development] retry0001-coffee:
I strongly suspect T-mobile in my area is having issues and my decision to upgrade at the same time has created a red herring situation. Terrible carrier. They have no service outage/status page. I still stand by the dirty flash working just fine. I just got networking back and now MMS seems to work. GD annoying. Thanks as always, Nikhil. (y)
[Android Software Development] osm0sis:
Nice! Thanks! Now.. any ideas why Live Translate and Live Caption don't work? :)

Also wondering if enough APKs exist to do an Android Go 12L or 13 for arm devices? Android Go GApps would come in handy most on old struggling arm hardware. 🤞
[Android Software Development] osm0sis:
In exploring the above weirdly broken features I discovered some more issues, @Nikhil 🥲

I noticed this got added in January: https://gitlab.com/nikgapps/13/-/commit/6c55e8dd2e9b282b3ad6517d68754ce7730d9d2d

The newer Pixel Experience xmls in Core/ExtraFiles seem to break Photos editing on my OnePlus 9 Pro, break Photos unlimited Pixel original quality upload on Pixels, etc.

See my conversation with Lineage devs here:

Remove the googlepixelconfig package by razorloves · Pull Request #935 · opengapps/opengapps

Each of the files in this package are device specific so they shouldn't be getting installed to all pixel devices.

github.com

In a nutshell, they tend to break more than they fix on non-Pixel devices.

I'd probably only leave the old nexus one, and the one specifically in the Recorder package, since it's needed for Play Store updates of Recorder, but remove all the other experience xmls.

Any chance you could remove them again and run another hotfix?
[Android Software Development] Nikhil:
yes, Live Translate and Live Caption requires a lot of configurations

- a specific ASI (pixel one) to work but unfortunately on non pixel devices, play store updates the apk to regular one and we lose the feature.

- ASI also requires android.permission.READ_DEVICE_CONFIG which for some reason is not applied just by adding it to priv-app permissions (I need to check a way out here).

- Probably GoogleTTS installed too

We also don't have Now Playing feature which needs these files and some overlay changes.

All this can be fixed (I think) by following ways

- Spoofing the device to a pixel device before first boot (or clear google apps data if done after first boot) but that's not recommended.

- There is an alternate way that most of the Roms have incorporated. i.e. spoofing specific apps based on the features (for e.g. using PixelPropsUtils)

- Using Pixelify Module as it has the ability to modify specific apps in system through Magisk which gapps cannot do through recovery.

From Gapps end, I will add those files and overlays, see if we get lucky, if not we'd have to rely on aforementioned alternatives.

The apks exists to do an Android Go 12L or 13 for arm devices, I just don't have an arm device to test it out. Which is why we only have arm64 builds. I can do blind builds if we have many people looking for this option and a few testers to make sure the build is working. :)
[Android Software Development] osm0sis:
I'd be happy to test out Android Go 12L arm on my Nexus 7 2013 running Lineage 19.1. :cowboy:

Any thoughts on my above (previous post) suggested changes for the problems introduced by the new pixel_experience_*.xml files? I've had to manually remove them from my device and format data again to get things working correctly.

Edit: FYI The unofficial Lineage flo ROM is up to Android 13 now.
[Android Software Development] Nikhil:
I was able to reproduce this issue with google photos and as you rightly said, by removing following files

pixel_experience_2021_midyear.xml

pixel_experience_2021.xml

pixel_experience_2022_midyear.xml

pixel_experience_2022.xml

I was able to edit images in google photos app and I noticed I had Unlimited Pixel Original Quality Upload too, so certainly a hotfix is coming. :)

as far as other files are concerned,

- We need pixel_experience_2017.xml for GoogleRecorder to work so I'll have to keep that in ExtraFiles otherwise the core users will not be able to install GoogleRecorder from playstore.

- 2018/2019/2020 I will keep it for the next hotfix build and remove it in longer run (once I determine its signifance - mostly with next stable release).

Thanks for bringing it to my notice!(y)
[Android Software Development] kundifon:
Ok, initial install of LineageOS 20 (android 13) together with custom repacked gapps went trough flawlessly. Instalation was done via TWRP. Here is the code I put in the debloater.config.

#/system/product/app/Aperture
/system/product/app/Etar
/system/product/app/ExactCalculator
/system/product/app/Gallery2
/system/product/app/messaging
/system/product/app/Recorder
#
/system/product/media/audio/alarms
/system/product/media/audio/notifications
/system/product/media/audio/ringtones
/system/product/media/audio/ui/Effect_Tick.ogg
#
#/system/product/priv-app/Contacts
/system/product/priv-app/Dialer
#

Then I download update trouhh OTA (settings/system/Updater). Just let the system that did all itself. When applying update, I saw some backup procedure. There is debloater mentioned. See attached picture. Actually delete all except anoying /system/product/media/audio/ui/Effect_Tick.ogg

Why?

What are ExtraFiles? Is there any way to backup and then restore folowing folders (and maybe some others if the need arises)?

/system/product/media/audio/alarms

/system/product/media/audio/notifications

/system/product/media/audio/ringtones
[Android Software Development] osm0sis:
I seem to recall 2018/2019/2020 all force it to Unlimited High Quality Photos backups, and only with only the 2017 can you get Unlimited Original Quality.

Edit: Correction, I double-checked my old notes, and experience xmls 2018 and 2019 (including midyear) are safe, but 2020 onward force it to High Quality instead of Original. And then exclusive xml 2016 (i.e. nexus PRELOAD entries) seem harmless, but 2017 onward breaks things again.

Some of the entries you've left in your experience xml files are VERY device specific to Pixel hardware and Pixel stock ROM.
[Android Software Development] Nikhil:
Point Noted! (y)

I checked the usage of all the features - the attachment gives us a glimpse of impact on a particular app - doesn't tell what impact it exactly does.

In summary,

- We need 2017

- It is safe to delete others (2018+)

- All the features seems to be part of GooglePhotos so if we're deleting any of the files other than 2017, it's impacting Photos app only.

I am performing some tests on GooglePhotos to note the impact of deleting those files, I think rest of the google apps are safe.