yashsingh1/xdaforums huggingface dataset:
[Android Software Development] ph03n!x:
LOS 19.1 and unofficial gapps from this post's Google Drive link works - just follow the LOS wiki, especially the part where it says flash LOS zip, reboot to recovery and flash gapps. I'm using this on Moto Z2 Force (nash)

Only prob I've faced - Android Auto doesn't work. When the phone is connected to the car, the initial setup starts, completes, and then AA disconnects from the car.
[Android Software Development] curiousrom:
Android 12.1 - LineageOS 19 - GApps

Which package did you install exactly?

Which wiki page? Could you post a link please?

FWIW these are reports posted in this thread after that post:

***

Meanwhile until official Open GApps for Android 12.1 are posted MindTheGapps works as an alternative (downloads).

These extra apps included in MindTheGapps but not in Open GApps Pico can be disabled in Settings > Apps & notifications > Show all > 3-dots > Show system:

* Android Accessibility Suite

* Google (search app)

* Markup

These are included in both Pico & MTG can also be disabled in their respective app's info:

* Android Auto

* Google Text-to-speech Engine

* Market Feedback Agent

The rest are core GApps.

If those apps were updated that went in the Data partition.

To gain space go to Play Store and click uninstall those apps. It will remove only the updates but keep the original in the System partition.

You can re-enable those apps @ anytime if you wish & your choice survives OS updates.

***
[Android Software Development] retry0001-coffee:
There are better alternatives to MindTheGapps for those who want core/basic only. I posted earlier about this. Who wants crap on their phone they don't want and have to disable but can't remove? Also some of us would like to dirty flash to LOS19 and already use openGapps. Switching to a different gapps package would require wiping your data. You should tell people that before suggesting alternatives.
[Android Software Development] ph03n!x:
I installed the ARM64 Pico - open_gapps-arm64-12L-pico-20220311-UNOFFICIAL_MOD.zip. Mine was a dirty flash - upgrade from 18.1, so I didn't go through setup wizard.

This is the LOS Wiki for my device, the reason why I'm mentioning this is to ensure that we are rebooting to recovery *after* flashing LOS/ *before* flashing gapps - https://wiki.lineageos.org/devices/nash/upgrade

One variable between the failure reports and me could be mine is dirty flash from 18.1

Does Android Auto work with MindTheGApps, have you tested to confirm this?
[Android Software Development] curiousrom:
Re: Android 12.1 - LineageOS 19 - MindTheGApps

One can unzip MindTheGapps, delete the unwanted *.apk's, zip & then sideload or flash via recovery. It's easy. Path in the MindTheGapp file:

`system/product/app/GoogleTTS.apk (18,789 KB)`

`system/product/app/MarkupGoogle.apk (1,68 KB)`

`system/product/app/talkback.apk (15,096 KB)` (Android Accessibility Suite)

`system/product/priv-app/Velvet.apk (136,694 KB)` (Google search app)

`system/product/priv-app/AndroidAutoStubPrebuilt.apk (3,178 KB)`

That's wrong.

GApps are installed as system apps so it's has nothing to do with Data.

You don't need to wipe anything on most devices. Just check the instructions in https://wiki.lineageos.org/devices/ > *{your device}* > Upgrading.

I did it myself when upgrading Galaxy S5 G900M klte from LineageOS 17.1 + Open GApps Pico to LineageOS 18.1 + MindTheGapps more than 1 year ago and without any GApps issues since then & OTA updating at least 20 times.

***

Who Made MindTheGApps?

If you look at the Thanks and Credits chapter in the bottom of the page of https://gitlab.com/MindTheGapps/vendor_gapps there is a bunch of LineageOS devs mentioned as testers & other contributions.

The same guys that you can find in https://wiki.lineageos.org/contributors.html

***

There are more than 4,000 6,150 downloads of MindTheGapps-12.1.0-arm64 and arm so far & I did not see a report of Android Auto not working yet.

BTW thanks for the additional details in your post above. :cool: 👍

You wrote "LOD zip" in your first post & that threw me off. Maybe you could edit & fix that typo?

***
[Android Software Development] Howard Wu:
Opengapps v20220430 api29 arm pico com.google.android.gms missing some DPIs, which causes some devices to stop working.
[Android Software Development] Prof. Yaffle:
I've upgraded from 18.1 with OpenGapps to 19.1 with MindTheGapps and Android Auto has been fine all day today.
[Android Software Development] retry0001-coffee:
It might work to dirty flash one gapps package over another, but maintainers do not recommend it. For example from the NikGapps FAQ:

Can I flash NikGapps on top of other gapps such as OpenGapps?
No, please clean flash

Also why would I want to do all the extra work to customize MindTheGapps packages (and thus enter a non-default state making it harder to debug anything) when there are already several projects that package a pico/core/base like install already? (OpenGapps, NikGapps, FlameGapps, BitGapps)
[Android Software Development] ipdev:
System apps are updated (sometimes hidden) and installed in data.

There are major issues if the update of system app(s) in data are out of sync or missing from system.

Cause an infinite boot or bootloop due to missing permissions and/or core files.​

When you update a custom rom, normally a backup/restore script (addon.d) is run to preserve additional modifications like GApps.

By re-installing GApps after the update, you overwrite the backup/restore script with the new installation.

Again this can cause issues if an update in data is out of sync or missing from system. 🙃

That is why it is recommended to wipe data when switching between GApps packages.

Cheers. :cowboy:
[Android Software Development] retry0001-coffee:
Thanks for that explanation. As I suspected all along. Hopefully we'll see some stability with OpenGapps packages in the next month. I am patient and don't like to play the guinea pig these days.
[Android Software Development] dwardo:
I dirty flashed from lineage 18.1 to 19 and went from opengapps to mind the gapps without wiping data and without an issue

I have in the past gone from opengapps to mindthegapps and back (when opengapps had issues with android auto - stub app was missing) without ever wipping data...

Android auto works fine with mindthegapps. Just drove 8h today with it !
[Android Software Development] curiousrom:
Re: Android 12.1 - LineageOS 19 - MindTheGApps

Maybe on the same Android version yes.

NOT when upgrading to a new higher version of Android.

People do NOT destroy your setup, apps & data and trust the LineageOS developers: https://wiki.lineageos.org/devices/ > *{your device}* > Upgrading.

This said backing up stuff before upgrading is good practice. 👍

From this thread in the LineageOS subreddit:

Q by the OP - ...OnePlus 6T ...I am currently on LineageOS 18.1 and using OpenGApps. I want to try upgrading to 19.1 using the official upgrade procedure here, but the only question I had was when I go to sideload the GApps, can I use the MindTheGapps package as the instructions suggest even though I currently have OpenGApps installed or do I have to wait for OpenGApps to release a package for Android 12.1?

A by TimSchumi LineageOS Team Member - You can just flash MindTheGApps, it will replace OpenGApps.

Post by the OP after upgrading: Just wanted to come back to report that I sideloaded everything as instructed in the guide and everything went flawlessly. Posting from LineageOS 19.1. Thanks!

***

LineageOS 19 + MindTheGapps Feedback

Thanks for the feedback guys. :cool: 👍

***

🤪 How hard is it to unzip a package, delete some apk's and zip it back again?

***
[Android Software Development] retry0001-coffee:
It's not a question of it being hard. But it is a question of it being time consuming. You have to familiarize yourself with the package layout, understand which parts are critical to keep and which are bloat. You also have to trust that the person telling you these things isn't forgetting some important piece of missing info that bites you on the ass later. For many of us, this is our primary phone and needs to work. If I don't have to script workarounds for things that work, then I generally don't go looking to make more work for myself.
[Android Software Development] Howard Wu:
I found that all 20220430 arm32 versions have this problem

This causes the gms to stop working.
[Android Software Development] curiousrom:
open_gapps-arm-10.0-pico-20220430 & 11 Broken?

Thanks for reporting that. :cool: 👍

In open_gapps-arm-10.0-pico-20220215.versionlog.txt it says:

arm-28| com.google.android.gms | 21.48.57 | 480 320 240 nodpi

And in open_gapps-arm-10.0-pico-20220430.versionlog.txt it says:

arm-27| com.google.android.gms | 22.09.20 | 320 160

It the same for open_gapps-arm-11.0-pico-20220215.versionlog.txt vs. open_gapps-arm-11.0-pico-20220430.versionlog.txt.

But arm64 seems OK.

open_gapps-arm64-11.0-pico-20220215.versionlog.txt says:

arm64-30| com.google.android.gms | 21.48.57 | 480 320 nodpi

And open_gapps-arm64-11.0-pico-20220430.versionlog.txt says:

arm64-30| com.google.android.gms | 22.09.20 | 480 320 nodpi

Heloooo, @Nezorflame?

****
[Android Software Development] josephcsible:
Another update: I thought https://developer.android.com/guide/app-compatibility/restrictions-non-sdk-interfaces might be relevant, since it says that accessing a restricted non-SDK interface will cause an error like the one I was getting (NoSuchMethodError: No static method getWindowCornerRadius(Landroid/content/res/Resources;)F in class Lcom/android/internal/policy/ScreenDecorationsUtils;), and https://dl.google.com/developers/android/sc/non-sdk/hiddenapi-flags.csv lists that as "blocked". However, I'm now beginning to think that this might be a red herring, since /system/etc/sysconfig/google-hiddenapi-package-whitelist.xml already whitelists com.google.android.apps.nexuslauncher, and further, running adb shell settings put global hidden_api_policy 1 also didn't change the error.
[Android Software Development] Nezorflame:
Thanks for the reports guys, package has been disabled and removed from the website.

Will look into the error.
[Android Software Development] josephcsible:
Now I see why this is really failing: that code is trying to call ScreenDecorationsUtils.getWindowCornerRadius with a Resources parameter, but as of AOSP commit 6603444, that method now takes a Context parameter instead. I decompiled NexusLauncherPrebuilt.apk and discovered that it ships its own version of QuickStepContract that doesn't incorporate that change. I think the problem is we're trying to use an Android 11 version of it on Android 12.

Next, I tried putting /system/system_ext/priv-app/NexusLauncherRelease/NexusLauncherRelease.apk from a stock Pixel 6 on my phone instead (along with whitelisting more permissions). It got further, but then it crashed with this message:

05-01 15:12:44.074 9169 9192 E AndroidRuntime: FATAL EXCEPTION: launcher-loader
05-01 15:12:44.074 9169 9192 E AndroidRuntime: Process: com.google.android.apps.nexuslauncher, PID: 9169
05-01 15:12:44.074 9169 9192 E AndroidRuntime: java.lang.SecurityException: Permission Denial: createPredictionSession from pid=9169, uid=10006 expected caller to hold PACKAGE_USAGE_STATS permission
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:2425)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:2409)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2392)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2334)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.app.prediction.IPredictionManager$Stub$Proxy.createPredictionSession(IPredictionManager.java:329)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.app.prediction.AppPredictor.<init>(AppPredictor.java:102)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.app.prediction.AppPredictionManager.createAppPredictionSession(AppPredictionManager.java:47)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at com.android.launcher3.model.QuickstepModelDelegate.recreatePredictors(SourceFile:9)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at com.android.launcher3.model.QuickstepModelDelegate.workspaceLoadComplete(SourceFile:2)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at com.google.android.apps.nexuslauncher.model.NexusLauncherModelDelegate.workspaceLoadComplete(SourceFile:1)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at com.android.launcher3.model.LoaderTask.run(SourceFile:21)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
05-01 15:12:44.074 9169 9192 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)

I'm open to suggestions on what to try next to make this work.
[Android Software Development] robin0800:
03/05/2022 arm64 pico opengapps just posted on Sourceforge this appears still broken!
[Android Software Development] diemadedrei:
I used the unofficial pico build posted a few posts back on a dirty flash of los 19 and everything (I use) works
[Android Software Development] robin0800:
Not to worry the old 15/02/2022 on the official site still works I see 03/05/2022 is now on the official site The one I said above does not work.,
[Android Software Development] curiousrom:
03/05/2022 arm64 Pico Broken?

What happens exactly? Bootloop? Crashing at the Setup Wizard, etc?

Android version? Device? OS on your device?

If you sideloaded Open GApps it automatically creates a log named open_gapps_log.txt in the internal sdcard folder.

If you copied to the device the GApps...zip package & installed it from there manually using the recovery then the "open_gapps_log.txt" is created in the same location as the GApps...zip package.

Maybe you could attach that log to a post? Zip it if you have issues attaching it to a post.

***
[Android Software Development] robin0800:
it boots but continuously shows the LineageOS boot logo and never gets beyond that.

Will attach more info and the log tomorrow (did check the log but saw no error) the 15/02 gapps works with the same setup.

A new Rom with May's security patch seems to boot OK with 03/05/2022 open gapps now.
[Android Software Development] Bork Bork:
open_gapps-arm64-11.0-pico-20220503.zip boots correctly on uptodate LOS 18.1.
[Android Software Development] Alixfi:
Is there an update planned for opengaps 12?
[Android Software Development] josephcsible:
Use the search button: https://xdaforums.com/t/gapps-daily...ndroid-versions-devices.3098071/post-86595145
[Android Software Development] curiousrom:
Re: Android 12 - Open GApps?

Yes eventually. No ETA.

Meanwhile check this post and below it for the MindTheGApps alternative.

The Nano & Stock from that link were reported broken in the last few pages.

Also Android Auto is broken in that Pico test build.

@ipdev: Maybe you could delete those builds or try to fix them?

When I asked Nezorflame in his Telegram group if there was hope for Android 12 packages he replied "Yes, more like in first days of May but yes".

***
[Android Software Development] josephcsible:
I don't see any reports of the nano builds for Android 12 or 12L being broken. Are you sure you aren't confusing them with reports for some of the builds for Android 10 and 11 being broken? And as for stock, it isn't totally broken, but rather just needs a workaround that I posted: https://xdaforums.com/t/gapps-daily...ndroid-versions-devices.3098071/post-86824021
[Android Software Development] curiousrom:
See the quotes in https://xdaforums.com/t/gapps-daily...ndroid-versions-devices.3098071/post-86822647

FYI you can click on the arrows to see the original posts.

Sending users to broken builds is a waste of time for them if you don't include a warning & a link to your workaround.

***
[Android Software Development] josephcsible:
ph03n!x said that it worked fine (except for Android Auto). master373 and I were only talking about stock, not nano. auspufftröte tried to use API31 GApps on an API32 OS. It looks like the only person you quoted who had a real issue with nano was maxed4901 (which I acknowledge I did miss at first), but I don't think that means the package is broken, since it seems fine for everyone else.

Valid point.
[Android Software Development] ipdev:
The builds in my gDrive link are initial test builds. ;)

Seem to work as well as expected for an initial test build.

- So, no I will not delete them any time soon. ;)

I (and others) are using them on a few different devices without major issue(s).

Android Auto is broken.

The stock 12L build might break touch on SELinux permissive devices.

Missing permissions in the stock build will cause a bootloop on SELinux enforced devices.

- That is why I noted not to use the test stock build unless you are using a config script.

I am currently using the 12L nano test build on my Pixel 5a official lineage 19.1.

- No issues that I ran into so far (save for Android Auto).

--

It takes time to do this.

My time has been limited so I try to do a few things each night. 🙃

I am planning to test a new build this weekend. ;)

Thanks to @josephcsible - Post 7,293

- I do not have to figure out Actions Services.

- - Only have to add camera.

Spoiler content hidden.

Thanks to a dev I highly respect. :D

- Leading me to the solution for Android Auto.

- Suggesting other updates/fixes.

Cheers. :cowboy:

PS.

Please remeber there is one big difference between MindTheGapps and OpenGApps.

The MindTheGapps project builds GApps for one level of Android.

The OpenGApps project builds GApps for multiple levels of Android.

It becomes more complicated when the build scripts and defualt apks have to be compatible with multiple versions of Android and device architectures.

Add multiple release varations from pico to super and it complicates matters more.​
[Android Software Development] curiousrom:
OK.

Maybe you could Edit and add some parts of what you just wrote to your post? https://xdaforums.com/t/gapps-daily...ndroid-versions-devices.3098071/post-86595145

**
[Android Software Development] LeZamalien:
Using 12L on lineage 19.1 ((Samsung A5).. awesome work.. keep it up
[Android Software Development] ipdev:
Hi all. :)

I realized I never gave my current testing branch in this thread. 🙃

build - [GitHub] - Link

I pushed my local source changes to gitlab.

My local changes - [GitLab] - Link

My local changes - [GitLab] - Link

AA v1.2.512130-stub was pulled from my Pixel 6 [oriole-sp2a.220505.002] stock Google (May 2022).

I might revert the AA-stub update or replace it with a different version.​

My new test builds still have some issues. :cautious:

Spoiler content hidden.

AA gave me a few problems but, I was able to work around them.

Spoiler content hidden.

--

A big Thank You (y) to all that have tested and helped me out with 12L test builds. :D

We are getting closer to a stable 12L build. 🙃

Cheers all. :cowboy:

PS.

OpenGApps - [GitHub] - PR # 959

OpenGApps - [GitHub] - PR # 960
[Android Software Development] josephcsible:
I can confirm that as of the 20220507 build, stock now boots successfully with no workaround needed. Unfortunately, the Pixel Launcher still doesn't work:

05-11 02:00:33.046 11995 12015 E AndroidRuntime: FATAL EXCEPTION: UiThreadHelper
05-11 02:00:33.046 11995 12015 E AndroidRuntime: Process: com.google.android.apps.nexuslauncher, PID: 11995
05-11 02:00:33.046 11995 12015 E AndroidRuntime: java.lang.NoSuchMethodError: No interface method startRecentsActivity(Landroid/content/Intent;Landroid/app/IAssistDataReceiver;Landroid/view/IRecentsAnimationRunner;)V in class Landroid/app/IActivityTaskManager; or its super classes (declaration of 'android.app.IActivityTaskManager' appears in /system/framework/framework.jar)
05-11 02:00:33.046 11995 12015 E AndroidRuntime: at com.android.systemui.shared.system.ActivityManagerWrapper.startRecentsActivity(SourceFile:3)
05-11 02:00:33.046 11995 12015 E AndroidRuntime: at c.a.b.j1.run(SourceFile:2)
05-11 02:00:33.046 11995 12015 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
05-11 02:00:33.046 11995 12015 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
05-11 02:00:33.046 11995 12015 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
05-11 02:00:33.046 11995 12015 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
05-11 02:00:33.046 11995 12015 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)

Similar to the error I got with Pixel Launcher in the last build, the problem is that as of AOSP commit 613ba2d, IActivityTaskManager.startRecentsActivity now takes a long as its second parameter instead of an IAssistDataReceiver, which once again points to the problem being that we need to use a version of the Pixel Launcher that was built for Android 12.
[Android Software Development] josephcsible:
I got Pixel Launcher working! Here's what I did (on a Moto X4 "payton" running the official 20220510 build of LineageOS 19.1):

Install open_gapps-arm64-12L-stock-20220507-UNOFFICIAL_MOD.zip with no gapps-config file

Delete /system_root/system/priv-app/NexusLauncherPrebuilt/

Copy /etc/sysconfig/google-hiddenapi-package-whitelist.xml from the product partition of a stock Pixel 4a (5G) image to /system_root/system/product/etc/sysconfig/

Copy /etc/permissions/privapp-permissions-google-se.xml from the system_ext partition of a stock Pixel 4a (5G) image to /system_root/system/system_ext/etc/permissions/

Reboot into Android and then back into recovery

Create the directory /system_root/system/system_ext/priv-app/NexusLauncherRelease/

Copy /priv-app/NexusLauncherRelease/NexusLauncherRelease.apk from the system_ext partition of a stock Pixel 4a (5G) image to /system_root/system/system_ext/priv-app/NexusLauncherRelease/

I think some of that might have been unnecessary, but at least now we know something that works.
[Android Software Development] master373:
i can confirm that pixellauncher is not working. The setup wizard didnt installed too idk why. Im using unofficial lineage 19.1 build for s7 with open_gapps-arm64-12L-stock-20220507-UNOFFICIAL_MOD.zip
[Android Software Development] curiousrom:
Thanks for the report but could you please edit your post & add the LineageOS version (18.1, 19?, etc) and the full name of the Open GApps file you flashed?

I tried to PM you but your XDA profile is blocked.

***
[Android Software Development] curiousrom:
Open GApps 11 ARM + LineageOS 18.1 = Bootloop!

@Nezorflame - FYI two official LineageOS 18.1 users with ARM devices reported a bootloop with Open GApps but success with MindTheGApps:

Google Nexus 6 (shamu) & open_gapps-arm-11.0-nano-20220503.zip here on Reddit.

Galaxy Note 3 LTE & open_gapps-arm-11.0-pico on XDA here.

***
[Android Software Development] Nezorflame:
Thanks! I've removed those just in case, will take a look at the reports.
[Android Software Development] master373:
Sorry. I did edit my post hope its okay now
[Android Software Development] josephcsible:
I just dirty flashed a OnePlus 6T "fajita" from LineageOS 18.1 to 19.1. I did this same procedure again, but this time I skipped my step 5 "Reboot into Android and then back into recovery", and Pixel Launcher still worked afterwards (and even kept its data). Also, it's okay if you have a gapps-config for other things; just don't disable ActionsServices or PixelLauncher in it.
[Android Software Development] rooooooooooooooooooooooot:
@josephcsible, thank you for pointing me here from pull request: 959!

Just a question, can I build that pull request and use it, or can I just rely on ipdev's build here? I mean I can really build it, but I just want to hear the recommended way.