[Android 13] [GApps] NikGApps [ARM64]

[osm0sis]

New Release is up - Android 10-13 (29th May 2023)

Changelog:

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

Download

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

Happy flashing!

Dirty flashed flawlessly! Brilliant job!

 

[osm0sis]

Okay, one thing after the OTA I just took...

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

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

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

 

[osm0sis]

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

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

 

[Nikhil]

Okay, one thing after the OTA I just took...

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

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

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

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

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

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

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

list_files() {
cat <<EOF
product/priv-app/GoogleDialer/GoogleDialer.apk
product/overlay/GoogleDialerOverlay.apk
product/framework/com.google.android.dialer.support.jar
product/etc/permissions/com.google.android.dialer.xml
etc/permissions/GoogleDialer.prop

--following lines are duplicates pointing to system--
priv-app/GoogleDialer/GoogleDialer.apk
overlay/GoogleDialerOverlay.apk
framework/com.google.android.dialer.support.jar
etc/permissions/com.google.android.dialer.xml

EOF
}

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

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

 

[osm0sis]

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

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

list_files() {
cat <<EOF
product/priv-app/GoogleDialer/GoogleDialer.apk
product/overlay/GoogleDialerOverlay.apk
product/framework/com.google.android.dialer.support.jar
product/etc/permissions/com.google.android.dialer.xml
etc/permissions/GoogleDialer.prop

--following lines are duplicates pointing to system--
priv-app/GoogleDialer/GoogleDialer.apk
overlay/GoogleDialerOverlay.apk
framework/com.google.android.dialer.support.jar
etc/permissions/com.google.android.dialer.xml

EOF
}

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

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

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

Edit: @Nikhil I noticed a number of other apps seem to have the duplicate entries and also duplicate files in the different install locations, though only Dialer is showing a problem at the moment. Will be interesting to see what happens after it all gets cleaned up.

 

[Nikhil]

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

Edit: @Nikhil I noticed a number of other apps seem to have the duplicate entries and also duplicate files in the different install locations, though only Dialer is showing a problem at the moment. Will be interesting to see what happens after it all gets cleaned up.

yes, it's because of the same reason. I hope the other apps don't cause as much issue as google dialer. Although, dirty flashing is a workaround for now.

 

[Nikhil]

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

Edit: @Nikhil I noticed a number of other apps seem to have the duplicate entries and also duplicate files in the different install locations, though only Dialer is showing a problem at the moment. Will be interesting to see what happens after it all gets cleaned up.

hey, can you dirty flash this addon and confirm if the generated addon.d file (09-GoogleDialer.sh) is updated with unique files?

 

[osm0sis]

hey, can you dirty flash this addon and confirm if the generated addon.d file (09-GoogleDialer.sh) is updated with unique files?

Hmm doesn't look good.

Plus I still see the overlay .apk actually present in both product and system, so it's either not uninstalling, or still installing it to both locations.

 

[Nikhil]

Hmm doesn't look good.

Plus I still see the overlay .apk actually present in both product and system, so it's either not uninstalling, or still installing it to both locations.

Thank you for testing! apparently, the quick fix didn't work in all scenarios.

I am attaching a new file with more robust solution, it resets the install indicators before installing the files.This will not delete the duplicate overlays, however, the duplicate entries in addon.d file will be removed so the next OTA update will remove the duplicate overlay on its own.

Please test this at your convenience! hopefully, this will work as expected.

 

[osm0sis]

Thank you for testing! apparently, the quick fix didn't work in all scenarios.

I am attaching a new file with more robust solution, it resets the install indicators before installing the files.This will not delete the duplicate overlays, however, the duplicate entries in addon.d file will be removed so the next OTA update will remove the duplicate overlay on its own.

Please test this at your convenience! hopefully, this will work as expected.

This one looks good! Nice job!

 

[flaxx187]

Hey I have some issues with google play Services

After a quit time my apps are crashimg or i dont get notifications.

After deleting caches, everything works fine ( for a quit time )

Sadly I have a nice configuration and don't want to reflash lineage, so I would deinstall play store and play service. After it I would to install the play store.


Any experience? Is that a good way?

Wish you a great day

 

[Nikhil]

Hey I have some issues with google play Services

After a quit time my apps are crashimg or i dont get notifications.

After deleting caches, everything works fine ( for a quit time )

Sadly I have a nice configuration and don't want to reflash lineage, so I would deinstall play store and play service. After it I would to install the play store.


Any experience? Is that a good way?

Wish you a great day

yes, you should uninstall the playstore and playservices updates and reboot, it should be fine.

 

[wttc]

I'm on Lineage OS 20 (Android 13) & mistakenly installed nikgapps Android 12 version

now I can't add another Google account in Play Store.

I want to install nikgapps Android 13 version.

Do I need to uninstall nikgapps Android 12 version first & then install nikgapps Android 13 version?

.... Or , can I just install nikgapps Android 13 version??

 

[flaxx187]

yes, you should uninstall the playstore and playservices updates and reboot, it should be fine.

aah not going fine, I uninstalled playstore reboot it uninstalled google service, clear caches and reboot my device -> it is now in bootloop



the apk files I have from apkmirror

 

[Nikhil]

I'm on Lineage OS 20 (Android 13) & mistakenly installed nikgapps Android 12 version

now I can't add another Google account in Play Store.

I want to install nikgapps Android 13 version.

Do I need to uninstall nikgapps Android 12 version first & then install nikgapps Android 13 version?

.... Or , can I just install nikgapps Android 13 version??

Yes, you need to uninstall nikgapps 12 and install nikgapps 13

aah not going fine, I uninstalled playstore reboot it uninstalled google service, clear caches and reboot my device -> it is now in bootloop



the apk files I have from apkmirror

You didn't flash nikgapps? If you install the apk from apkmirror, they aren't going to be a system app and you'll definitely run into issues.

I suggest you dirty flash Nikgapps core

 

[osm0sis]

Thank you for testing! apparently, the quick fix didn't work in all scenarios.

I am attaching a new file with more robust solution, it resets the install indicators before installing the files.This will not delete the duplicate overlays, however, the duplicate entries in addon.d file will be removed so the next OTA update will remove the duplicate overlay on its own.

Please test this at your convenience! hopefully, this will work as expected.

After the OTA it seems the one the ROM wanted got removed, so now the -downloadable Phone version came from the Play Store again and I lost Call Screen.

Edit: Dirty flashing 0529 got it all working again even though the Dialer addon.d sh and prop entries remained the correct shorter lists.

Must be something still missing from addon.d for that transition to fewer entries/files to fail? Something which registers/activates the overlay perhaps?

Edit 2: Looking through the addon.d files only GmsCore, GooglePlayStore, GoogleServicesFramework, DevicePersonalizationServices, DigitalWellbeing, Gmail, GoogleCalendar, GoogleMaps, GoogleMessages, GooglePhotos, GoogleRecorder, GoogleTTS, PrivateComputeServices, TrichromeLibrary, and WebViewGoogle have the duplicate entries.

Of these most were actually installed to product only; Gmail, Photos and TTS were actually installed to system only; and Trichrome and WebView were actually installed to both, suggesting a problem there. system overlays contained duplicate files for most that aren't actually in system, suggesting another problem there.

I also noticed that AndroidAuto, GBoard, and GoogleClock create extra prop files in product, though they're empty, unlike their system counterparts.

I cleaned up all the entries and files manually, and have dirty flashed directly after to keep things working, and I went with the default product location for the complete duplicate Trichrome and WebView files.

 

[Nikhil]

After the OTA it seems the one the ROM wanted got removed, so now the -downloadable Phone version came from the Play Store again and I lost Call Screen.

Edit: Dirty flashing 0529 got it all working again even though the Dialer addon.d sh and prop entries remained the correct shorter lists.

Must be something still missing from addon.d for that transition to fewer entries/files to fail? Something which registers/activates the overlay perhaps?

Edit 2: Looking through the addon.d files only GmsCore, GooglePlayStore, GoogleServicesFramework, DevicePersonalizationServices, DigitalWellbeing, Gmail, GoogleCalendar, GoogleMaps, GoogleMessages, GooglePhotos, GoogleRecorder, GoogleTTS, PrivateComputeServices, TrichromeLibrary, and WebViewGoogle have the duplicate entries.

Of these most were actually installed to product only; Gmail, Photos and TTS were actually installed to system only; and Trichrome and WebView were actually installed to both, suggesting a problem there. system overlays contained duplicate files for most that aren't actually in system, suggesting another problem there.

I also noticed that AndroidAuto, GBoard, and GoogleClock create extra prop files in product, though they're empty, unlike their system counterparts.

I cleaned up all the entries and files manually, and have dirty flashed directly after to keep things working, and I went with the default product location for the complete duplicate Trichrome and WebView files.

Can you please share the addon.d logs?

The Dialer entries remained as is because the install location of apk did not change.

The listed apps that have duplicates, it'll be resolved once you dirty flash the newer build (which I will share shortly). After which, the overlays will be either in system or product.

AA, GBoard and Google Clock have empty prop files from an older implemented which are left in the system as residue. With the build I will share with you (also is a candidate for next release), it will remove those prop entries from addon.d and those will not survive the next OTA update.

I still have following on my todo list:
- prevent relocating of apps once they are installed.
- install all the overlays to /product/overlay only, I don't see overlay folder present in system or system_ext on my pixel 7 pro and that's a standard.

 

[osm0sis]

Here we are

 

[osm0sis]

Why did the Dialer overlay stop working until I dirty flashed though, if it only reinstalled to the same place? That's the most confusing part to me right now.

 

[Nikhil]

Why did the Dialer overlay stop working until I dirty flashed though, if it only reinstalled to the same place? That's the most confusing part to me right now.

yeah, even I am confused, can you share the installation logs from the dirty flashing?

the logs have list of files before and after installation under partitions folder, I can compare and see if there was any difference related to GoogleDialer apk and overlay.