Use the search button: https://xdaforums.com/t/gapps-daily...ndroid-versions-devices.3098071/post-86595145
Use the search button: https://xdaforums.com/t/gapps-daily...ndroid-versions-devices.3098071/post-86595145
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-86824021The 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?
I don't see any reports of the nano builds for Android 12 or 12L being broken...
...And as for stock, it isn't totally broken, but rather just needs a workaround that I posted...
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.Sending users to broken builds is a waste of time for them if you don't include a warning & a link to your workaround.
The builds in my gDrive link are initial test builds.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".
***
<permission name="android.permission.MANAGE_MUSIC_RECOGNITION"/>
<permission name="android.permission.MANAGE_UI_TRANSLATION"/>
<permission name="android.permission.SYSTEM_CAMERA"/>
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. ...
Using 12L on lineage 19.1 ((Samsung A5).. awesome work.. keep it upI run arm/arm64 builds of pico, nano and stock for testing.
Once they are tested a bit and seem stable, I upload them to MediaFire.
MediaFire - Link
Android 12 builds are in the SDK31 folder.
The 20211218 builds include some permission updates.
---
Last week I ran SDK32 builds to test on LineageOS.
LineageOS is merging 12.1.0_r1 into the 19.0 branch instead of creating a 19.1 branch.LineageOS Gerrit - Topic 12L - LinkEdit: I just checked and see they decided to bump up to 19.1 a few days ago.
Note:
Now that Android 12L is official, the release props still show as 12 not 12.1 or 12L.
The build tag was bumped to 12.1.0 and the boot image is now SDK32 but, the kernel version is still showing as 12.0.0
The boot image was SDK31 on the 12L preview release.
The only way to determine if you are running 12 or 12L is by checking the SDK level.
SDK31 = Android 12
SDK32 = Android 12L
The initial 12L OpenGApps test builds were blind builds and untested.
I did not have a device/rom to test them on.
I few days later I was able to test them on a Pixel C, Lineage 19.0 SDK32 build.
Since it is a tablet, it utilized the large screen layout of SDK32.
The 12L pico and nano builds seem to be safe.
The 12L stock build had issues with Pixel launcher so, I would suggest not using it for now.
Unless you are using a gapps config script to customize the install.
Android 12L (SDK32) test builds are currently on gDrive.
gDrive - Link
Everyone is welcome to give them a try.
Cheers all.
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)
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.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.zipI can confirm that as of the 20220507 build, stock now boots successfully with no workaround needed. Unfortunately, the Pixel Launcher still doesn't work:
Similar to the error I got with Pixel Launcher in the last build, the problem is that as of AOSP commitCode: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)
613ba2d
,IActivityTaskManager.startRecentsActivity
now takes along
as its second parameter instead of anIAssistDataReceiver
, 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.
i can confirm that pixellauncher is not working. The setup wizard didnt installed too idk why. Im using unofficial lineage build for s7
Sorry. I did edit my post hope its okay nowThanks 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.
***
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.I got Pixel Launcher working! Here's what I did (on a Moto X4 "payton" running the official 20220510 build of LineageOS 19.1):
I think some of that might have been unnecessary, but at least now we know something that works.
- 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/
OpenGApps - [GitHub] - PR # 959@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.
*** Incompatible Android ROM detected ***
This GApps pkg is for Android 12.x ONLY
Please download the correct version for
your ROM: 12 (SDK 32)
******* GApps Installation failed *******
*** Incompatible Android ROM detected ***
This GApps pkg is for Android 12 ONLY
Please download the correct version for
your ROM: 12L (SDK 32)
******* GApps Installation failed *******
I run arm/arm64 builds of pico, nano and stock for testing.Is it possible to get a test version of the arm version aswell?