yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Nezorflame:
As for the testing - I've put that back for a pretty long time, and it's definitely something that I'd love to see one day, so we're returning to this idea of "stable" and "nightly" builds.

This weekend I'll start preparing the infrastructure for this, and we'll recruit testers in the Telegram group. I'll post the results, links and the process for testing as soon as it's ready.
[Android Software Development] Nezorflame:
Bootloop should be fixed now (had missing permissions again due to GMS and GRestore updates), so the next build should be good.

Would appreciate the feedback on it.
[Android Software Development] SzymonL:
arm64-11.0-nano-20210730, 27 and 24, bootloop, works fine at 20210513-TEST.

Poco F2, Havoc-OS-v4.3-20210401-lmi-Official
[Android Software Development] rootarded:
No more bootloop with arm-11.0-nano-20210730 on my LG D802 running lineage-18.1-nightly-20210729. But Android Auto still doesn't connect unfortunately.
[Android Software Development] Nezorflame:
That's unfortunate. Please gather logcat if possible.

Is it the same incompatibility error?
[Android Software Development] FridgeBoxX:
For me Android Auto is now working, however on about every second start of the device (Pixel 4a), the Play Services are not available.

I've to investigate the cause of this, could be related to the latest broken LOS 18.1 image from yesterday or image_a/b thing.
[Android Software Development] rootarded:
I must correct myself: after formatting /system and reinstalling ROM and Open Gapps it now works flawlessly! I'd recommend doing this to anyone still having issues after updating to 2021-07-30!

@Nezorflame: Thank you for your work!
[Android Software Development] G A S T:
I can confirm that.

Same error like I described here a few days ago. Still no connection to the head unit.
[Android Software Development] rootarded:
As I suggested, try formatting /system and reinstalling ROM and Gapps using their respective ZIP files. Maybe this also works for you.
[Android Software Development] G A S T:
So you performed a full wipe of your device to get AA to work? Sounds brutal to me.

Still thinking about other solutions. I guess there must be a less brutal and more precise attempt. It should be enough to wipe all AA related data from the device and then to dirtyflash a newer GApps-Version just after the ROM (in my case just the next LOS build).
[Android Software Development] rootarded:
No no no, I just wiped the /system partition, leaving /data untouched. It's a dirty flash, just including a manual format of /system. No data is lost durig this process. And it only takes 5 minutes to do so. :)
[Android Software Development] Nezorflame:
See if you have the AA stub APK in /system/app folder. If so, delete it.

Newer versions have it in /system/priv-app instead.

Shouldn't require a /system wipe this way (at least, in theory).
[Android Software Development] G A S T:
Sorry! I was misinterpretating what you wrote. It's interesting that you left /data completely untouched and did not wipe "gearhead" there. Because that's what I'd wipe, too. Just to make sure that there is no bad AA leftover. 🤷‍♂️
[Android Software Development] osm0sis:
My guess would be it's the data system packages xml list that needed the wipe to fix, since it includes APK location.

Edit: Just saw system only wipe resolved it, so guess I was wrong!
[Android Software Development] rootarded:
I know! I was also surprised that it actually worked. :)
[Android Software Development] rootarded:
@Nezorflame: Why was the latest release (2021-07-31) removed from the servers? Is it faulty? Should I also roll back to 2021-07-30?
[Android Software Development] Nezorflame:
It seems that ARM package was built with errors, so just in case I pulled each variant from the server.

From what I can see it wasn't fully built, so if your install went fine, then you should be fine as well.

I've asked @mfonville to take a look (since build server is his domain).
[Android Software Development] G A S T:
No, it's OK to use. It seems that there is only an issue with the ARM 32 Bit builds.

Im running the also pulled LOS 18.1 build from 2021-7-29 together with that pulled OGApps build for A11 from 2021-07-31 and everything works fine. So don't panic and don't roll back. 😉

By the way:

It was enough to remove the stub from app and priv-app in the system directory and to remove the remains from data and cache.

Android Auto works now with the head unit. 👌
[Android Software Development] rootarded:
I do use that 32 bit version - it installed and works just fine up until now. We'll see whether my phone explodes or not. :)
[Android Software Development] G A S T:
🤣

In that case watch out that it does not catch fire and simply install the next official build...
[Android Software Development] Cuonghmm:
Recently, limit download speed
[Android Software Development] Linuxfan724:
I uninstalled magisk, disabled my substratum themes, and cleared my cache partition, then reflashed lineage 18.1, then gapps 20210810, then magisk. This solved my Android Auto issues.
[Android Software Development] G A S T:
You should have read my exactly two weeks old post above.
[Android Software Development] Linuxfan724:
I've had issues bootlooping when removing system apps like that. Just sharing what worked for me.
[Android Software Development] rootarded:
Did you try a clean flash already?
[Android Software Development] Maxii Chiara:
Hello, I have left an error or problem that occurs on my device (LeEco Le Max 2 x829) after installing the Gapps (arm64 v11.0 pico).

The problem starts to occur after the first reboot of the device.

Once you turn on the device the system UI conflicts and stops working, then when I try to enter the security pattern it asks me again endlessly and thus I can not access the device again.

The only thing I can do in those moments is see the notifications that come to me with the screen locked.

I would appreciate to verify this great inconvenience that would be happening at this moment, thank you very much in advance.
[Android Software Development] Maxii Chiara:
I forgot to mention that my device has the latest version of LineageOS ROM v18.1 so far, just like the Gapps used.
[Android Software Development] kogz:
It seems there's an issue with OBB. I'm using open_gapps-arm-11.0-pico-20210821 on crDroidAndroid-11.0-20210811-hammerhead-v7.9. I tried to install an XAPK coming directly from Google Play (com.lego.supermario) but installation fails. I managed to install APK and OBB files manually and separately (through extracting XAPK, installing APK and coppying OBB files manually). Is this something you can check or advise what else can I check on my side? Thanks in advance.
[Android Software Development] n8mahr:
Just wanted to let you know - the latest official builds for arm64 / A11 don´t seem to work with recent lineage 18.1 on my PH-1.

Did a clean install with latest lineage 18.11 0906 and official openGapps nano, tried latest 0903 and 0904, device boots normally, but no google services.

tried unofficial micro from @ripee and it worked at once.

unofficial micro worked, but after repeating all the steps to verify it again and get the logs out, it did NOT work anymore. tried a lot of different versions of openGapps then, they all do not work with my mata /ph-1. I really do not know why the unofficial micro worked that one time I posted it here, but now it does not anymore, even a clean flash doesn´t help.

So I went back to mindthegapps, which works with mata every time i flash it.
[Android Software Development] ripee:
I'll run a new set of builds dated 0907 later today.
[Android Software Development] JuanCarlosM1:
The 9.0 version have a bug on the log in and backup service.

I use the AOSiP 9.0 for Athene (Moto G4/G4 Plus)

I fix this with the bitgapps files.

Clould you fix it
[Android Software Development] KSLevel11:
I would like to update the Gapps nano version on my phone. I'm using Lineage OS and LineageOS Recovery. Can I just sideload the newest Gapps?
[Android Software Development] Pastinakel:
Yes, open Gapps can be updated with adb side load in lineage recovery.
[Android Software Development] TheLoonyRebel:
Does anyone know what's going on with A11 GAPPS for ARM64 beyond the few that are being updated (pico/nano)? It's been a few months since the last stock test build was uploaded. Just wondering that's all. Thanks for any info in advance.
[Android Software Development] Solway:
Google play services permissions issue causes failure to a restore from backup

Ok ive seen this happen on 2 phones. Differnet lineageos Roms (but same android version)

First phone is a S4 i9505, installed with the following android 11 rom Optimized LineageOS 18.1 v5

The second phone is a S4-mini I9195, installed with the following android 11 rom [Unofficial][11.0.0] LineageOS 18.1 for S4 Mini

Ive used multiple Opengapps Arm 11 nano/pico versions on both phone, which have produced the same issue - say for example open_gapps-arm-11.0-nano-20210918

Once the ROM and Gapps are installed, and the phone boots to the google setup wizard. There seems to be a google play services permission issues. The first time it'll cause the setup to not run correctly, either with a popup error to ask for permission which can only be loaded if you lock the screen and open from the notification directly from the lock screen. Then it will continue to setup.

When this setup "finished" nothing was restored from a google online backup

so i went to google play services and gave permission to everything. however SMS and Contacts wont "save" as allow.

I re-ran the setup wizard using the following ADB

When phone rebooted, the setup wizard started. but once again popup error (that can only be accessed from lock screen notification), was asking for google play services to allow SMS. So again i went to the setting and said yes. Wizard continued and now was enable to setup/restore from a online backup.

So theres a permission issue, which is not setting the google play services to allow at first run.

and manually setting the SMS/contact to allow will not save the setting. Is there a issue here?
[Android Software Development] jokergermany:
Anyone else has a bootloop with open_gapps-arm64-11.0-nano-20210928 ?
[Android Software Development] curiousrom:
Yes.

A Pixel 2 with Open GApps Nano + LineageOS here and LineageOS 18.1 on (Miatoll) Redmi Note 9 Pro with open_gapps-arm64-11.0-nano-20210929.zip here.

Edit: an other LineageOS 18.1 user of open_gapps-arm64-11.0-nano-20210929 with a bootloop issues here. 🤪

It's sad & an other hit on the reputation of the Open GApps project. That's what happens when builds are shipped without testing as I mentioned over & over in this thread.

Build weekly or monthly instead of daily & test before releasing!

Hello, @Nezorflame?

***
[Android Software Development] SzymonL:
Bootloop on arm64-11.0-nano-20210929, 20210925 is fine.
[Android Software Development] dwardo:
I confirm !
[Android Software Development] curiousrom:
Open GApps Android 11 Nano Builds 20210928 and 20210929 Bootloop!

@Nezorflame - Since the bootloop with builds 20210928 and 20210929 was reported here and in your Telegram group more that 2,000 new downloads were made and I keep seeing users posting about it here, in Reddit & elsewhere. :(

That's a big waste of time for baffled users. 🥴

PLEASE REMOVE from the servers the defective builds ASAP!!!! 😳

https://sourceforge.net/projects/opengapps/files/arm64/

***
[Android Software Development] osm0sis:
I've pinged @MastahF, @retired_mnbooze (retired?!) and @Nezorflame in our Slack to better get everyone's attention.

Any logcat and dmesg from the bootloop? Might be a missing permission again.
[Android Software Development] Cuonghmm:
11.29 arm64 nano, normal boot
[Android Software Development] Cuonghmm:
28,gsi booted
[Android Software Development] baudav:
Hi,

I can't add children Google account on Lineage-17.1 with Gapps; Is there a prerequisite? problem with Gapps or with the OS?

Issue Open for LineageOS: 1839

edit: it's work with 18.1 after first start (start without account, add account when lineageOS ready
[Android Software Development] ALTracer:
Not booting open_gapps-arm64-11.0-nano-20211007.zip, drops into Android Rescue Party.

Redmi 4X "santoni" 3/32, LineageOS 18.1 (a11) by 0xCAFEBABE 20211007 testing unofficial build. System-as-root, ARM64 A-only, OrangeFox recovery.

I happened to have adb keys set on this rom before dirty-flash upgrading, so here's the logcat.

Looks like a missing permission for Velvet (com.google.quicksearchbox), crashing Zygote.

OpenGapps Build 20210925 worked fine previously. I flashed it back and booted normally.

E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.googlequicksearchbox (/system/priv-app/Velvet): android.permission.SUBSTITUTE_SHARE_TARGET_APP_NAME_AND_ICON}
[Android Software Development] Nezorflame:
Huge thanks for the logcat! I was unable to reproduce this on my device so this helps a lot.

We're going to implement automatic perm check soon-ish, for now we'll pull the problematic builds and implement the fix.
[Android Software Development] Nezorflame:
Here are the test builds (nano variant) with the fixed permission, please check them out:

ARM | ARM64

These should just work, and the fix has been already merged, but we need to be sure that this was the only issue causing the bootloop.

As for the other news:

Unofficial builds from @ripee have been working well so far, so we're going to enable all of the package variants for SDK 30. Thanks for testing them!

We've resumed the work on the build validation process, so that we can transition into the weekly-nightly scheme and release vetted (as much as possible assuming it's all going to be a volunteer work) build on weekly basis, while continuing to produce nightly builds for those who wants them. I'll share more news on this when the process will start.

Before starting work on SDK31 aka A12, we'll make sure that we're able to properly generate (and validate) permissions for the APKs so that the issues like previous one don't happen anymore. We plan to integrate this check into the Gitlab pipeline to automate this process as much as possible.
[Android Software Development] ripee:
New set of unofficial 11.0 packages will be up in around 6 hours, dated 20211008, from fully updated sources of course.

Unofficial OpenGApps
[Android Software Development] curiousrom:
Open GApps Android 11 Nano Builds 20211007: Bootloop Again!

Thanks for the report & log. :cool:👍

An other user here in the LineageOS subreddit got fuzzed by the broken Nano Android 11 when upgrading his Fairphone 3+ from LineageOS 17.1 to 18.1 + open_gapps-arm64-11.0-nano-20211007.zip. :(

***
[Android Software Development] ALTracer:
I flashed 20211008 build (downloaded via OpenGapps App from SourceForge), seems to work fine. At least it booted.

Thanks for timely fix.

edit: see quote for device
[Android Software Development] holavilla:
Pico or Nano? Arm64? Android version, rom & device?
[Android Software Development] ALTracer:
Same as before.

You of all people reacted to my previous post, duh. I didn't expect to be required to provide all the versions every post.
[Android Software Development] curiousrom:
You could have more than one device, some new readers may not want to check the previous pages.

Is your copy/paste broken? :)

***
[Android Software Development] ALTracer:
Even though I happen to have two phones, the sensible default is the one just mentioned. I never explicitly stated I'd updated my rolex from LOS17.1 or bricked my santoni.

Yes, my copy/paste is broken. XDA mobile client is really unwieldy and lagging, as that's what I'm required to use when away from my home desktop. Don't even start on discussing web mobile versions or alternative clients.

Forum rules require new readers to use SEARCH on thread. It's their problem, not mine -- also the message is quoted multiple times at the top of this page 357 (as of now). Future mod cleaning may rearrange that.

I will refrain from answering any more off-topic questions.
[Android Software Development] ipdev:
With the updated permission, the arm and arm64 builds work for me. 👍

LineageOS 18.1

Nexus 7 (2013) [arm].

Poco F1 [arm64].

Cheers. :cowboy:

PS.

Will do a clean flash to test on some other devices when I have time. 🙃
[Android Software Development] osm0sis:
...No. There's a reason you can't do that.
[Android Software Development] curiousrom:
Switching From NikGapps to Open GApps

@osm0sis - Are you sure? I have been told that you can only wipe the System partition, re-flash the same ROM, reboot to recovery (required for device with A/B partitions but does not hurt anyway) & then flash Open GApps.

***
[Android Software Development] osm0sis:
Well, for starters some things can only be done from clean data: https://github.com/opengapps/opengapps/blob/master/scripts/templates/installer.sh#L1799

Even if you did somehow make an identical config to avoid changing things drastically by switching GApps like that it could lead to unpredictable results since you're overlapping things (which could be quite different) in /system from the core of both, and /data/system would also have to deal with the sudden changes.
[Android Software Development] kumardaksh:
Thank you for responding. No problem I can clean flash.

Does Opengapps now supports split APKs? Also does it comes with updated apps now?
[Android Software Development] Simon1511:
Hi, I'm facing various issues with Gapps on my Galaxy A52:

Installing any of the arm64 11.0 Gapps packages does not succeed due to not enough storage space being available. This is not true since all dynamic partitions (system, vendor, product, odm) have each 500MB of free space left.

Removing the space check from the OpenGapps installer will make them install successfully, but after booting the device will soft reboot infinitely. This reboot issue wasn't actually Gapps related, sorry. So the only issue that remains is that openGapps is unable to calculate the correct space on dynamic partitions.

Logcat and OpenGapps logs are attached.

Is that a known issue and if yes, is there a workaround?
[Android Software Development] Nezorflame:
Hi! No, it's not known yet.

I'll check that, thanks.
[Android Software Development] ALTracer:
Permissions strike again, huh

Build open_gapps-arm64-11.0-super-20211020 (with gapps-config)

doesn't boot system

Found this under `/data/system/dropbox/system_server_crash*.txt`

bash-5.0 ~ > cat /data/system/dropbox/system_server_crash\@1634836516145.txt
Process: system_server
Build: google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys

java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.projection.gearhead (/system/app/AndroidAutoPrebuilt): android.permission.UPDATE_APP_OPS_STATS}
at com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:4703)
at com.android.server.pm.permission.PermissionManagerService.access$500(PermissionManagerService.java:178)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.systemReady(PermissionManagerService.java:4786)
at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21688)
at com.android.server.SystemServer.startOtherServices(SystemServer.java:2210)
at com.android.server.SystemServer.run(SystemServer.java:601)
at com.android.server.SystemServer.main(SystemServer.java:417)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:925)

Couldn't connect with adb this time.
[Android Software Development] Typhoon_Master:
Hi,

when installing open_gapps-arm-6.0-pico-20211021.zip on my tablet, the assistant after the first boot

(A) forces me to login to a wifi. the "SKIP >" button is greyd out

(B) after logging in to a wifi it goes to "Checking connection... This can take a while" but it stucks there forever. Again the "SKIP >" Button is greyed out.

So flashing gapps makes my device unuseable. :-(

Is there a way to fix this?

// EDIT: REBOOT FIXED IT!
[Android Software Development] Magendanz:
I'm so excited to finally have Android 11 stock builds, but am seeing a WebView problem on the Galaxy Tab A 8.0 (SM-T290, ARM64) that seems related to issues #820 and #804. Setup cannot progress past attempting Google Play Services sign-in and skipping setup results in the same problem when logging into the Play Store or Chrome, showing only a black screen and the navigation bar. If I check WebView Implementation in Developer Options, it shows None.

Can anyone recommend a workaround for this? Previously, we just needed to match versions for Chrome and Trichrome, but they both seem to currently be 81.0.4044.138.
[Android Software Development] Feimitsu:
27/28 Oct version of Gapps Stock for ARM Android 11 seems to be broken (missing play services notification at device start). It's also some 80MB smaller than the version released on the 21 Oct.
[Android Software Development] Howard Wu:
21 Oct. -> 26 Oct. Missing some DPIs
[Android Software Development] Daikath:
I tried to install a fresh OS onto my Samsung Galaxy S5 Neo. I did it before and it worked fine for quite a while. I then install the full package of Gapps before booting. However, it would get stuck on the starting screen looking for updates, without an option to skip it. Also messages would appear that random google apps suddenly stopped working.

I then formatted my system, just installed lineageOS and it worked fine.. It just booted into the OS and I could call and surf the web.

I went back and just installed just the pico version. Now it's also stuck at the looking for updates part without the option to skip it. I did get the message that the system UI stopped working.

I have tried older packages of gapps and lineageOS, but after like three tries I kept getting the same errors. I came back to the recent builds with just pico, yet it still wouldn't get passed the looking for updates screen.

I have used the recovery image, lineage-17.1-20211024-recovery-s5neolte.img with the LineageOS build of

lineage-17.1-20211024-nightly-s5neolte-signed.zip

I then used the Gapps build for ARM, Android 10, pico package, open_gapps-arm-10.0-pico-20211028.zip

Is there more information which would be useful? Is there something I can do other than trying out older and older builds? Thanks in advance for any help.
[Android Software Development] Nezorflame:
Hi! Does logcat show anything of value (error-wise)?
[Android Software Development] Nezorflame:
Logcat output during the boot.

If it doesn't connect to phone, you can try editing build.prop and default.prop from your recovery (or edit them on PC and push to system):

build.prop (replace the existing lines if they're already there):

# debug
ro.default_usb_mode=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb

default.prop (replace the existing lines if they're already there):

# debug
ro.adb.secure=0
ro.secure=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb

this will enable debugging to gather logcat, later you can remove/restore these files (or reflash the ROM)
[Android Software Development] Nezorflame:
sdk-27 only has APK for 160 DPI, so that's why it's missing - https://gitlab.opengapps.org/opengapps/arm/-/tree/master/priv-app/com.google.android.gms/27

I see that it was updated, so that's probably the cause (or another permission issue).
[Android Software Development] Howard Wu:
But why is the Play service of target API27 in the zip file of Android 10 arm pico
[Android Software Development] Nezorflame:
Thought first that it was a fallback one, my bad.

Need logcat then to be sure.
[Android Software Development] kumardaksh:
Does Opengapps now supports split APKs?

Also do now packages comes with updated apps or older version like Chrome v81?