yashsingh1/xdaforums huggingface dataset:
[Android Software Development] bersem:
The first one is from TWRP and the second after first boot taken from System. If no one will make a log after reboot / from failled boot after i will make it in next days.

1. open_gapps_debug_logs.tar.gz and open_gapps_log.txt are from TWRP after flashing

2. logcat_First_Boot.txt taken from System

Thanks in advance !

Best regards !
[Android Software Development] llaumgui007:
Have you crash on ringtone app with 20200116 ?

I have several crash but not with all app.

View attachment 4930421
[Android Software Development] Nezorflame:
Nope. So far not a single one.
[Android Software Development] ynamojn:
What's happened with 0121 build? There are tvstock and pico variants but the other variants are missing.
[Android Software Development] Nezorflame:
Congratulations everyone, the Q PR has been merged along with the APK repos to the master branch!

Release notes: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-10.x

What does this mean?

Basically that means that the Android 10 builds can now considered to be stable for daily usage.

But, as you know, there are still some issues left:

- [ARM-only] SetupWizard seems to be crashing for some due to Google changing some stuff (more details here: https://xdaforums.com/showpost.php?p=81478751&postcount=6439)

- Trying to use Pixel Launcher with Q gesture system will result in FC

- Photos still FC

This is why we're going to only enable the pico and nano variants in the daily builds since they're stable and work for the most of people.

What's next?

Currently, the plan is following:

1) fix the current issues left and add support for more package variants one by one

2) add the official stable and test build flavors, with difference being:

- test builds being built on daily basis (like we do already) and tested by people in a separate XDA thread and in the Telegram chat (might consider creating Slack/Discord group for that as well in the future);

- stable ones are pushed every week (by promoting the latest working test to the stable once testers confirm that).

Stay tuned for the more updates soon!
[Android Software Development] bersem:
[MENTION=2010892]Nezorflame[/MENTION]

Maybe this is what u need for debug. Take a look please now.

https://xdaforums.com/showpost.php?p=81532915&postcount=415

Thanks in advance

Regards !
[Android Software Development] Nezorflame:
Something's up with the buildserver, I've asked Maarten to take a look.
[Android Software Development] Nezorflame:
Seems like the ARM issue was fixed with the help from [MENTION=7268092]z3DD3r[/MENTION] who patched the SetupWizard for ARM on Q, so expect the release build to work properly!

https://gitlab.opengapps.org/opengapps/arm/commit/2a4df84427f6bc4c5e177a3091545eaf7f755713

cc [MENTION=6707196]danwood76[/MENTION] [MENTION=5480152]followmsi[/MENTION] [MENTION=7280276]ipdev[/MENTION]
[Android Software Development] z3DD3r:
Hope that this patched version will work for all devices. We have tested it only on hammerhead but i think there should be no issues with other ARM devices.
[Android Software Development] danwood76:
Thanks for your work.

I am just rebuilding LOS without my hack so I can test it now, will update you once it is complete!
[Android Software Development] danwood76:
The patched version works well on the Samsung Exynos7580 based devices (A3, A5 tested).

Great work!
[Android Software Development] vic97:
Anyone able to download opengapps for android 10? It is grayed out for me despite selecting nano.
[Android Software Development] Wishmasterflo:
Here:

https://sourceforge.net/projects/opengapps/files/arm64/beta/
[Android Software Development] andreoide:
Flashing Arm 22 Jan cause bootloop on kccat6 Samsung S5 lineeage22 Jan release.

Same lineage 22 Jan with gapps Arm Jan 17 no problem.
[Android Software Development] gordonthegopher:
Same for me with open_gapps-arm64-9.0-nano-20200123 on Xiaomi A1 (tissot) lineage-16.0-20200122-nightly-tissot-signed build. Bootloop saying I need to factory reset.

Also used open_gapps-arm64-9.0-nano-20200117 instead and it booted fine.
[Android Software Development] Bianfuchen:
open_gapps-arm64-9.0-nano-20200123.zip can not boot into system on my xiaomi mi5(omni 9)
[Android Software Development] The_Walking_Playground:
Hi,

I just tried installing the 1/16 Android 10 Pico BETA GApps to my HTC One M9 running LineageOS 17.1, and I get an incompatible error. I'm using a test version of TWRP from [MENTION=1162986]Captain_Throwback[/MENTION] that I'm told "no longer sets ANDROID_ROOT to /system_root" and that's likely the problem? I'm attaching the recovery log from TWRP for reference. Is there any way for me to install the zip?

TWP
[Android Software Development] Nezorflame:
Hi. Yes, indeed, that is a problem for us. It's unfortunate that folks at TWRP decided to change this behavior again (I believe it's the third time they do this), and since we relied on this variable, it seems that we can't anymore.

We've discussed this change already with [MENTION=4544860]osm0sis[/MENTION] (since our mounting scripts are based on his solution for the AnyKernel 3) and if that change will be accepted and merged, we'll adapt the scripts accordingly.

For now the only solution for you will be to use an older version of the recovery.
[Android Software Development] curiousrom:
Boot Fail - Open GApps Android 9.0 Builds 2020-01-22 & 23

What are the exact names of the LineageOS & Open GApps files that you flashed & failed to boot please?

Guys, how did you flash Open GApps? By sideloading or copying to the device & flashing from there with a Recovery?

Do any of you still have the open_gapps_debug_logs.tar.gz from the failed install?

[MENTION=2010892]Nezorflame[/MENTION] - 2 other LineageOS users reported failed to boot with Open GApps Android 9.0 builds 2020-01-22 & 23 here in the LineageOS subreddit.

There are very few commits in https://github.com/opengapps/opengapps/commits/master made on Jan 21, 2020.

Could the fail to boot problem be related to [MENTION=7280276]ipdev[/MENTION]'s Copy logs to sdcard/ when using sideload commit?

***
[Android Software Development] Bianfuchen:
Guys, how did you flash Open GApps? By sideloading or copying to the device & flashing from there with a Recovery?

YES!

Do any of you still have the open_gapps_debug_logs.tar.gz from the failed install?

no,How can i do to catch logs?
[Android Software Development] curiousrom:
Where to Find the Open GApps Installation Logs

From Pull request - Copy logs to sdcard/ when using sideload #794:

So starting with build 2020-01-22 or newer, if you sideload the logs should be in the internal sdcard or /data/media/0/.

If you copy or move the open_gapps...zip to the device & flash from there using the recovery the Open GApps installation log will be created in the same directory as the open_gapps...zip.

***

[MENTION=2010892]Nezorflame[/MENTION] - Why not simplify for users & the Wiki and always save the logs to /data/media/0/?

***
[Android Software Development] Bianfuchen:
ok
[Android Software Development] danwood76:
I have had users reporting that if they choose to install the TWRP app (prompted before reboot to system) that they get a boot loop when installing opengapps.

Are you buy any chance doing that?

My advice is, you don't need the TWRP app so don't install it.
[Android Software Development] Bianfuchen:
I do not choose to install twrp app when using twrp to flash opengapps.
[Android Software Development] gordonthegopher:
I flashed by copying open_gapps-arm64-9.0-nano-20200123.zip to the device then flashing from TWRP (which I've been doing since the first release of official Lineage for the Mi A1 without issue). Unfortunately I don't have a log as it's my daily driver and I needed to get it back up.

Just to clarify, OpenGapps appeared to flash without issue at all - it was when booting I had the issue: the Lineage boot animation would just loop and loop for a few minutes before it rebooted back into Lineage recovery (each flash overwrites TWRP and I wait until a successful first boot before reflashing it) saying there was a problem with my device and I needed to factory reset. This was with lineage-16.0-20200122-nightly-tissot-signed. The same thing happened with official Lineage builds from 17th, 18th, 20th and 21st as well (initially I thought it was a Lineage issue so I tried rolling back for a few versions before coming here and realising others seemed to be having issues with Gapps).

Once I used an older version of OpenGapps (open_gapps-arm64-9.0-nano-20200117) instead, it was fine.
[Android Software Development] LilBlinx:
Could you post a logcat while the device is booting. It's a permission issue once again...
[Android Software Development] metterschling:
The bootloop some of you are seeing seems to be an issue with recent Opengapps when one has the TWRP app installed - see opengapps forum: https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/page648
[Android Software Development] LilBlinx:
I don't really think that is an issue because few of my users of Lineage 16.0 builds with both OrangeFox and unofficial TWRP had bootloop issues. I guarantee that is once again a permission issue which hasn't been solved for a week. If someone can please flash the latest build and upload a logcat so we can fix it for future builds it would be great.

EDIT:
[MENTION=2010892]Nezorflame[/MENTION] can we get some info on this one?
[Android Software Development] martixy:
I was trying to flash my OnePlus One with LineageOS 16.0(lineage-16.0-20200123-nightly-bacon-signed) and it seems the prebuilt opengapps(20200124) prevent the OS from ever booting. It gets stuck in the boot animation for 10 minutes then reboots into TWRP again (v3.3.1-0).

Everything is clean, freshly unlocked bootloader, wipe/format everything, clean sideload of both together as instructed by lineage. No TWRP app or anything else allowed. Tried micro and nano.
[Android Software Development] LilBlinx:
Please post logcat. Known issue but no logs from anyone.

Easiest way is to flash Lineage, boot, enable ADB from system and then flash opengapps and collect logcat from PC.
[Android Software Development] popxunga:
On January 18, I installed a bacon device with TWRP 3.1.1 (app not installed), reboot to recovery and then installed lineage 16 and nano gapps, both built on January 17 via TWRP, and everything worked fine.
[Android Software Development] martixy:
Ooof.... I kinda lied a bit. Not my phone, a friend's phone (even if I have the same one - I flashed mine a few months ago). Came over for a root-party. Except its now getting late over here and I have to go home. So I can't collect logs.

Btw, do you mean go against the instructions which specify to flash lineage and gapps before booting lineage first? As in flash lineage, boot, enable adb, flash gapps?
[Android Software Development] phillip zanders:
How do I post a logcat? I am using a Samsung Galaxy Tab S2 T810. LinageOS 16. I'll do anything I can to help as I am not in dire need of my device to work at this time.
[Android Software Development] EfficiencyNerd:
Just adding my 2 cents...

I got gapps installed by using an older version on my Oneplus 3T. I was installing via TWRP and did NOT let TWRP try to install its app afterwards. I simply flashed the ROM, flashed the old gapps, and finally was able to get into the OS.

I was using:

lineage-16.0-20200123-nightly-oneplus3-signed.zip

open_gapps-arm64-9.0-pico-20200117.zip
[Android Software Development] LilBlinx:
Easiest way is to do the following

1. Download and extract platform tools from Google's platform tools

2. Go to the folder where platform tools (adb.exe) is extracted, hold shift and select Open PowerShell here or Open Command Prompt here whichever available

3. Flash Lineage 16.0 without OpenGapps and let it boot

4. Enable Developer Settings (by pressing build number 5 times) and enable ADB

5. Connect your phone to PC and type adb devices. Make sure the device is recognized.

6. Reboot to twrp or whichever recovery you use, flash OpenGapps and reboot the phone

7. Once it gets stuck on bootloop in the command window you opened in step 2, type adb logcat -d > logcat.txt

8. Upload the file here

---------- Post added at 00:51 ---------- Previous post was at 00:43 ----------

Apparently from 20200117 onward there is an issue. One log would mean a lot for me and the OpenGapps team since I have no access to my device currently to check
[Android Software Development] phillip zanders:
Ok I'll work on that tonight or tomorrow and get that to you no later then Monday Alaska standard time.
[Android Software Development] Mukuhorisu:
I found a simple solution when flashing latest gapps but can not boot into system , before flashing latest gapps, try to flash gapps 20200117

Sorry bad english :(
[Android Software Development] phillip zanders:
I just get a waiting for device screen in command prompt.
[Android Software Development] curiousrom:
Boot Fail - Open GApps Android 9.0 Builds 2020-01-22, 23, 24

About the bootloop or fail to boot for Open GApps Android 9.0 Builds 2020-01-22, 23, 24 the Galaxy S5 klte + variants maintainer [MENTION=2693412]haggertk[/MENTION] who is also one the 7 directors of the LineageOS Project posted this in the LineageOS subreddit: {bold by me}

***

From a post I made in this thread on December 5th, 2019 and addressed to [MENTION=2010892]Nezorflame[/MENTION] & [MENTION=1763928]MNBooZe[/MENTION] (NicholasBuse on GitHub):

Hundreds of confused users are wasting their time with broken builds which adds up to hundreds of hours of wasted time.

Many of them make posts about it on XDA, Reddit & elsewhere & that's bad for the reputation of the Open GApps project.

This happened a couple of times recently. The general public is not a testing group.

Maybe it's time to create an Open GApps testing group? Small banners & images could be made and members of that group could use them in their forum signatures for example.

Why not switch to a weekly build instead of daily & test properly before launch?

While I really appreciate the work made by the unpaid volunteer Open GApps devs :good:, it's an important & big project that impacts thousands of users & testing before release should be an essential part of the process.

If reducing the frequency of the releases is necessary because of limited testing capabilities then do it because the harm caused by releasing broken builds is too great IMO.

And why on earth are the known broken builds still available in https://sourceforge.net/projects/opengapps/files/ :confused:

Edit 2020-01-26: The broken builds have been removed from the Open GApps servers. :good::cool:

***
[Android Software Development] haggertk:
And to be more specific, these two things are boot-breakers for, at a minimum, P:

https://gitlab.opengapps.org/openga...ermissions/opengapps-permissions.xml#L326-327

https://gitlab.opengapps.org/openga...ermissions/opengapps-permissions.xml#L394-397

Nuke them and, at least as of a couple days ago, P boots again. No, I'm not opening a pull request because I have no clue how the opengapps team wants to approach this (needed for Q, breaks things below Q) with the one branch to rule them all (and in the darkness bind them) development approach.
[Android Software Development] Nezorflame:
First of all, thank you for your feedback. Although harsh, it is mostly valid.

1) I'm going to pull all of the builds after the Jan 17th one, except for the Q builds which are fine now.

2) [MENTION=2693412]haggertk[/MENTION] thank you for noticing this, I'll make a test build without these permissions to check, and if it works, will incorporate a fix which will have these permissions added only for Q.

3) [MENTION=4122877]curiousrom[/MENTION] regarding your points (any opinion on this is purely mine, I can't speak for the whole team but this is how I see things):

1. Yes, users are wasting their time with broken gapps. So does everyone with broken ROMs, kernels, etc. So do I when Google decides to break something just because. This is life, **** happens.

2. I think "reputation" is a strong word. You're talking about an opensource project which is supported by a very small group of people (mostly myself, [MENTION=1763928]MNBooZe[/MENTION], NicholasBuse with occasional help from [MENTION=4544860]osm0sis[/MENTION] and others) right now who are doing this out of pure enthusiasm without any guarantees, like most of the projects here on XDA.

I, for one, am not doing this for reputation or fame, this is a poor motivation in a world of opensource. I do that purely out of self-motivation, to keep the project going, and of the desire to have a working device with AOSP-based ROM with Google stuff.

Also I don't remember anyone making commitments about the 100% working builds all the time, daily builds have a tendency of being broken from time to time, so there's that.

3. Yes, and most probably will happen again for reasons described earlier.

4. I've already spoken to you, and wrote about it here - we are going to do that, but in order to launch a testing group and a test build workflow, we have to modify a lot of stuff:

- change the SF structure

- modify buildserver to push "test" builds instead of "stable"

- create and admin the testing group

- modify API to have some kind of "promotion" of the latest working "test" build to the "stable"

- change the website to support that separation

Assuming I'm pretty much the only one doing this stuff right now (except for the buildserver which is managed by [MENTION=1763928]MNBooZe[/MENTION]) this will take a while. And managing a separate testing community will be a very time-consuming process which someone will have to burden. I'm not sure that I'll be able to handle it per se.

5. Making weekly builds is feasible, but honestly, what does it matter? If it becomes broken, you're still left with a week-old build, much like now. Separation of the builds to the test-stable should resolve that.
[Android Software Development] phillip zanders:
Don't get it wrong, even though it is frustrating to get blindsided by say open Gapps causing a bootloop. I am so grateful that people do take the time to make things like open gapps and custom roms. Because of the developers. You have saved me hundreds and help reduce E-waste. So take what is being said as a learning experience. I do hope to see more great work from you and other developers.
[Android Software Development] curiousrom:
Broken Builds Not All Deleted?

I am posting this because I sent you an XDA PM about it but got no reply. Do you read them?

I see that you deleted broken builds 2020-01-22 & 23 but in the 2020-01-24 folder they are still there. :eek:

Can't you keep the Android 10 builds & delete the others ASAP please?

For example in https://sourceforge.net/projects/ope.../arm/20200124/

Thanks for your time. :good:

***
[Android Software Development] Nezorflame:
Yeah, I was stuck with the website not being able to pick different dates for different architectures.

Since changing it will require some time, I had to mark the 10.0 release of the 24th January as the 17th January in order to show both pre-Q builds and the Q ones.

So, for now, ignore the fact that the 20200117 build of 10.0 GApps is actually the 20200124 one :D

Apart from that, the defective releases are now purged. New build should incorporate the fix.
[Android Software Development] Bonito77:
[MENTION=2010892]Nezorflame[/MENTION], thanks for all the years of your great and solid work. Your project is really one of the essential of hole modding scene. Of course there where some problems the last weeks but that's more because of the ****ing changes of google and you have to look how came out of this ***t. Thanks to you and maartenfonville.
[Android Software Development] Nezorflame:
It's OK, I've screwed up as well with testing for the older packages, and in the current state of having everything in master, bugs are very likely to happen.

We'll see if the testing workflow will help us to remedy that.

---------- Post added at 06:25 PM ---------- Previous post was at 06:07 PM ----------

To everyone with the bootloop issue on P: please try this nano build for ARM64 to see if the issue is resolved: https://sourceforge.net/projects/op...-arm64-9.0-nano-20200126-FIXED_2.zip/download
[Android Software Development] Nezorflame:
OK, initial tests went fine, so the fixes are in (see https://github.com/opengapps/opengapps/pull/800 and the linked GitLab MR's). Next build should be OK again.

Thanks everyone who've posted feedback on this, we'll try to do better next time.
[Android Software Development] LilBlinx:
I think everyone should admit that this issue has been resolved quite quickly. Good work!
[Android Software Development] Nezorflame:
Today's builds are in, please check them out to see if the issues are resolved.
[Android Software Development] curiousrom:
Dirty Flashing Pico 2020-01-27 Success

FWIW after creating a full TWRP backup: dirty flashing open_gapps-arm-9.0-pico-20200127.zip using sideload on my Galaxy S5 G900M LineageOS 16.0 klte build 2020-01-23 + Open GApps Pico + LineageOS AddonSU went smoothly & booted to System without any problem.

Thanks to the new feature Pull request - Copy logs to sdcard/ when using sideload #794 by [MENTION=7280276]ipdev[/MENTION] the logs open_gapps_log.txt and open_gapps_debug_logs.tar.gz were automatically created in /data/media/0/ a.k.a. the internal sdcard.

Previously it was not possible to get some Open GApps installation logs when using sideload.

Obviously the more complete test is a clean install & a new setup to check the permissions but can't do that @ the present & hopefully other users can report about it.

Thanks for the nice work. :good::cool:

Looking forward to participate in the future Open GApps Testing Group. ;)

***
[Android Software Development] mc510:
I'm having exact same problem ... just put Lineage 12.1 on my Fire 7" (5th gen) with latest opengapps pico 5.1, and Play Store won't download apps. At least not while I'm watching; I basically have to put the tablet down and go away for at least an hour, sometimes more. I can see from the traffic monitor on my router that it's not downloading slowly, it's just not downloading at all. Perhaps there's some incompatibility between this rom and opengapps? Maybe we should try gapps from a different source?

[edit] I have no solution, but I've decided to test out Lineage 14 and I can report that opengapps Play Store works perfectly on it. [/edit]
[Android Software Development] andreoide:
Hi, sorry for not responding on earlier request, but today I used the lineage 16.0 20200127 kccat6 for Samsung S5plus with gapps arm 9.0 mini 20200127 and all is okay, smooth quick boot after update!

Well done sir! Thank you :good:
[Android Software Development] curiousrom:
Re: Open GApps Mini 2020-01-27

Thanks for reporting back. :good::cool:

Was this a dirty flash of "gapps arm 9.0 mini 20200127" over an existing LineageOS + Open GApps setup to update GApps like I posted above or a clean install after wiping System + Data?

If it was a clean install, did you restore a Google Backup on first boot?

***
[Android Software Development] andreoide:
I did a dirty flash over existing Lin.&gapps..

Like I always do after a twrp-backup just in case something fails.
[Android Software Development] Wolfcity:
I did a clean flash of Resurrection Remix followed by gapps arm 9.0 Pico 20200127 and Magisk 20.3 on my Moto G 2014, no Google backup restored.

Everything went fine as it used to be, no problems.

Good job!
[Android Software Development] psshirke.shirke@gmail.com:
Tried latest nano Android 10 GAPPS on Mi 3 on AOSP build , ended with error 70.
[Android Software Development] Redline:
Tested latest 27-1-20 arm64 10.0 nano, dirty flashed over the previous same version beta on LineageOS 17.1 on my LG V40.

Dirty flashed ROM, Gapps & Magisk.

Booted & tested working ok.

Congrats on stable status <3
[Android Software Development] Nezorflame:
We have some mounting issues left with some of the devices (see https://github.com/opengapps/opengapps/issues/789 for reference), fix is in the works.