yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Nikhil:
Is that it?

Can you share recovery log?

Just flash the zip and go to advanced option in twrp and copy log.
[Android Software Development] cheanch:
[MENTION=4867515]Nikhil[/MENTION] Not sure if it's you're looking for -

https://drive.google.com/file/d/1FRvWh5RoA-gTYYgOfSlDn72hUdzHQdJn/view?usp=sharing
[Android Software Development] FlatOutRU:
My device is Galaxy S10+ (Snapdragon)

If i`m trying to flash arm64 gapps - installer says that my device is arm. ??? Its for sure arm64 :P

After adding

ro.product.cpu.abilist=arm64-v8a

to /vendor/build.prop gapps installer detect it properly with arm64.

Installation goes ok, then i reboot into system and i have absolutely nothing from gapps stuff just like it wasn't installed at all ( I am trying it to use with any GSI )

Here's the log i can take from /sdcard

Hope i can get some response, Thanks!

UPD: more logs added
[Android Software Development] Nezorflame:
[MENTION=9368743]cheanch[/MENTION] [MENTION=3149697]FlatOutRU[/MENTION] thanks for your feedback, I'll take a look today.
[Android Software Development] ynamojn:
Tried dirty flash 9 October build over 6 October build 64 bit version and my phone (Leeco Le Pro3/ZL1 with LOS 16) couldn't boot. After failed boot It restart and go back to the recovery mode.
[Android Software Development] MrKartupelis:
Same, I sadly wasted an hour trying to figure out if Lineage 16 build or Opengapps was broken. Turns out it was 9th October arm64 build of opengapps.

edit: I always do clean install.
[Android Software Development] :
Same for me, 9th Oct arm64 opengapps package nano is broken :(
[Android Software Development] lekiaM:
Yup same here, thought it was due to Los Nightlies, tried the Oct 6 Nano package and updated fine. 9th caused me instant bootlooping.

(also Arm64)
[Android Software Development] booci:
Same here, builds from Oct 9 and 10 are broken. Last good one is Oct 6. Did a quick comparison between oct 6 and Oct 9 and it seems only 2 apps were updated, com.android.vending (Playstore) and com.google.android.apps.restore. I bet the problem is from the new v17 Playstore.
[Android Software Development] ynamojn:
Yes, tried Oct 10 build and still couldn't boot. Must reverted to Oct 6 build again. Actually I am waiting for the v17 Play Store update since it will fix a bug for the "what's new section"
[Android Software Development] modpunk:
The issue that current GAPPS arent working is that two priv-app permissions are missing:

10-10 12:42:36.991 3134 3134 W PackageManager: Privileged permission android.permission.READ_PRIVILEGED_PHONE_STATE for package com.google.android.apps.restore - not in privapp-
permissions whitelist
10-10 12:42:36.991 3134 3134 W PackageManager: Privileged permission android.permission.WRITE_EMBEDDED_SUBSCRIPTIONS for package com.google.android.apps.restore - not in privapp
-permissions whitelist

Those are missing in /system/etc/permissions/privapp-permissions-google.xml

<privapp-permissions package="com.google.android.apps.restore">
<permission name="android.permission.BACKUP"/>
<permission name="android.permission.GET_ACCOUNTS_PRIVILEGED"/>
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
[Android Software Development] andreoide:
same problem , trying something different

I had the same problem, thanks to TWRP im back on builds (gapps and lineage) okt.5

(1) Now ill flash the new build lineage 10-10-2019 kccat nightly and the gapps from okt6 ARM -9-mini (wich i always flash without problems)

I tried many things before like flashing the nightly alone, wich works, than i tried flashing the 10-10 nightly with okt.9 gapps, wich fails in continuous lineage startup animation wich ens in automatic going back to recovery.

(1) So ill try the new build KCCAT6 lineage with okt 6 gapps now and report here later.

(reporting) (yes now is little later LOL )

(1) Yep, working.

(2) Question rising now is: ( since im just a user, not developer or someone having that technical knowledge about all the insides..)

Is it safe to stay on build nightly KCCAT lineage 10-10-2019 ( with working gapps okt 6 ) OR should i flash back TWRP recovery to the last working build ( for me okt 5, both gapps and lineage),

because the cause of all the failure is not clear to me: Is it the lineage build preventing the gapps to work, or the other way around?

Im afraid when developers have fixed it ( they will, im sure they will) ill have to start from scratch wich is too much work for me now....
[Android Software Development] hetor99:
tried adding those lines on the file mentioned by [MENTION=4297219]modpunk[/MENTION], and now is working fine.

this is the file if someone want to just paste it, or idk if is specific because i've used the super package with custom selection of apps
[Android Software Development] andreoide:
fixed Y/N ?

I see new Lineage 11 okt and Gapps ( all versions ) available.

Is the problem fixed now ? Anyone?
[Android Software Development] ynamojn:
As far as the required permissions, they are still missing from the file. So I modified the permission file and the phone booted up smoothly. I guess pure Gapps 11 October will not work since the required permissions are still missing.
[Android Software Development] andreoide:
re: re: FIXED Y/N

Thanks for quick responding, i have read about mod but i dunno howto do that.

I have understood i have to change something XML file, can i do that in NOTEPAD? And where i find that XML file? In the gapps package?

Im really trying to learn here, maybe you have the time to explain to me?

If not, ill just have to wait :)

Thanks anyway

Peace
[Android Software Development] :
Take the easiest way: flash latest Los together with opengapps 6th of October, all is fine then
[Android Software Development] Marcb:
New Oct 11th build is out.... is the problem fixed?
[Android Software Development] jofan:
the solution is to use october 6 and then let Play Store do it's magic
[Android Software Development] Zev Ronso:
I'm using Micro GApps for my Custom ROM and I wanna update my Play Store by APK Mirror site. Which variant should I use? Thanks!
[Android Software Development] demonoidmaster:
Check the code between the brackets, mine is [0] for all resolutions, for you it might be different but take the code you have and get whichever latest play store that matches it, but if a latest play store update has a [0] number then get that one
[Android Software Development] aliuwr:
Same issue here

10-11 03:35:43.923 1634 1634 E Zygote : System zygote died with exception
10-11 03:35:43.923 1634 1634 E Zygote : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.apps.restore: android.permission.WRITE_EMBEDDED_SUBSCRIPTIONS, com.google.android.apps.restore: android.permission.READ_PRIVILEGED_PHONE_STATE}
10-11 03:35:43.923 1634 1634 E Zygote : at com.android.server.pm.permission.PermissionManagerService.systemReady(PermissionManagerService.java:2005)
10-11 03:35:43.923 1634 1634 E Zygote : at com.android.server.pm.permission.PermissionManagerService.access$100(PermissionManagerService.java:89)
10-11 03:35:43.923 1634 1634 E Zygote : at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.systemReady(PermissionManagerService.java:2052)
10-11 03:35:43.923 1634 1634 E Zygote : at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21374)
10-11 03:35:43.923 1634 1634 E Zygote : at com.android.server.SystemServer.startOtherServices(SystemServer.java:1760)
10-11 03:35:43.923 1634 1634 E Zygote : at com.android.server.SystemServer.run(SystemServer.java:457)
10-11 03:35:43.923 1634 1634 E Zygote : at com.android.server.SystemServer.main(SystemServer.java:302)
10-11 03:35:43.923 1634 1634 E Zygote : at java.lang.reflect.Method.invoke(Native Method)
10-11 03:35:43.923 1634 1634 E Zygote : at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
10-11 03:35:43.923 1634 1634 E Zygote : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)

Add missing permissions in /system/etc/permissions/privapp-permissions-google.xml, then issue resolved.
[Android Software Development] methuselah:
Yeah. 6 is booting for me too. Needed phone so wasn't able to get recovery log.
[Android Software Development] armars:
please update youtube in aroma package

14.34.54 version is not changing lot of time
[Android Software Development] fawazahmed0:
Installation problem in newer version of gapps

Hi,

I have tried newer versions of gapps such as 20191006, 20191010, 20191011 and also 20191012. But they don't seem to install apps in system/app.

I tried older version of gapps i.e 20190823 and it works.

This seems to be a problem in installer script.

I have attached logs for 20190823 (installation works perfectly) and 20191006 (doesn't work, no gapps get installed in system/app)

I assume the problem is more related to SAR mount logic in script, but not sure. For example after flashing 20190823, the system mount folder is /system_root/system, but in case of 20191006, after flashing it, the system mount folder is /system/system
[Android Software Development] fawazahmed0:
ok, the problem is related to recent commit:

https://github.com/opengapps/opengapps/pull/761/commits/973620b6777b44b486faf8aed1774efd955f3ae3

I have raised an issue for that:

https://github.com/opengapps/opengapps/issues/776
[Android Software Development] Zev Ronso:
Thanks! It worked! :good:
[Android Software Development] jdrch:
Does anyone know if the broken builds have been fixed?
[Android Software Development] droident:
Not sure of this is a GApps or rom-related issue but has anyone come across a blank icon in their launcher? It brings up an error message. If I remember correctly, when the default browser is set to nothing there's a browser redirect which includes this package name in the URL;

org.chromium.trichromelibrary
[Android Software Development] ChaithzLuci:
I'm using mi a1 and flashed Havoc Custom Latest Rom and also flashed Gapps. The Google Photos is not opening!

This is the crash log URL: https://del.dog/ulofefuvij
[Android Software Development] curiousrom:
URGENT: Stop Building Defective Open GApps Failing To Boot

[MENTION=1763928]MNBooZe[/MENTION] (NicholasBuse on GitHub), [MENTION=5083335]SpasilliumNexus[/MENTION] & [MENTION=2010892]Nezorflame[/MENTION] & any other Open GApps team member: the last working Open GApps build @ the present is 2019-10-06 & dozens of users on different devices & using different arm & arm64 packages reported failing to boot & being thrown back to TWRP with builds 20191009, 10, 11 & 12.

IMO you should stop making new builds immediately until the problem is fixed and all builds 20191009, 10, 11 & 12 should be deleted. :eek:

User [MENTION=4297219]modpunk[/MENTION] posted here that it's probably a privapp-permissions-google.xml problem & included a solution.

Edit: - It seems that those permissions are also missing, see post below & the logcat snippet quoted above:

<permission name="android.permission.WRITE_EMBEDDED_SUBSCRIPTIONS"/>

<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>

Just curious: [MENTION=4297219]modpunk[/MENTION] - Did you manage to boot with the defective Open GApps & capture that logcat by adding ro.control_privapp_permissions=log in your /system/system/product/build.prop before flashing it? :confused:

Some of those users were clean installing but worst some were updating or upgrading & are panicking et wasting a lot of time. Here are some who posted on the LineageOS subreddit:

Oneplus One keeps booting into TWRP lineage-16.0-20191012-nightly-bacon-signed + open_gapps-arm-9.0-nano-20191012.

Stuck at Startup

twrp-3.3.1-0-yt_x703f.img

lineage-16.0-20191009-nightly-YTX703F-signed.zip

open_gapps-arm64-9.0-mini-20191010.zip

(S5 Neo) Bootloop {Open GApps Pico} 20191009 and 20191010 both failed on my first try with LOS.

Xiaomi Mi Mix 2s gapps trouble

Mi MIX 2S M1803D5XE

16.0-20191008-NIGHTLY-polaris

TWRP 3.3.1-0-b0a0dbba

open_gapps-arm64-9.0-nano-20191009.zip

Cant install on Samsung Galaxy Note 3 N9005 "So, i install TWRP 3.3.1, then format data/system/storage, then i install lineage-16.0-20191009-nightly-hlte-signed and open_gapps-arm-9.0-pico-20191009.zip ...phone just restart to twrp again".

I could post more links from XDA & Reddit but hopefully you get the point.

***

In one of the links above a user reported fail to boot with build 20191012 & fixed it by dirty flashing 20191006.

***

Edit: attached logs of failed to boot from 3 different users.

***
[Android Software Development] hetor99:
Permissions file seems to still miss those permissions

https://gitlab.opengapps.org/opengapps/all/blob/master/etc/permissions/privapp-permissions-google.xml

Also, my english is bad

:p
[Android Software Development] lekiaM:
I think Nezorflame's priority is too fix Android 10 Gapps (i see he is busy with it) in the Telegram Channel. I think we need to flash 'just' the Oct 6 Packages for the time being and manual update from PlayStore and Apk Mirror. :)
[Android Software Development] curiousrom:
Re: URGENT: Stop Building Defective Open GApps Failing To Boot

Thanks for the link. :good::cool:

I can see in line 165 @ the present:

Which are the permissions missing in the current build according to [MENTION=4297219]modpunk[/MENTION] in his post linked above.

But looking at his logcat snippet it seems that you are right and those in bold below are missing.

In the privapp-permissions-google.xml attachment that you posted here there are 2 additional permissions:

***

The Open GApps for Android 10 is in beta stage & can wait. The new priority should be all the current users wasting their time & panicking. It's also bad PR for Open GApps as I saw several posts recommending MindTheGapps as a workaround.

Only a fraction of those users will read message boards with the build 20191006 or older workaround.

I just replied to 3 other users stuck with failed boot on Reddit. :eek:

The broken Open GApps builds 20191009, 10, 11 & 12 must be deleted ASAP in https://sourceforge.net/projects/opengapps/files/ as one can see 34,387 combined downloads for those @ the present as shown in the attached screenshot.

***
[Android Software Development] Nezorflame:
Thank you all for your feedback.

Indeed, fixing the current packages should be a higher priority, and I'll address that right now.

As for the issues:

1) I'll pull the broken packages from SF and redirect the website to the ones from 6th October.

2) Missing privapp permissions were added to Q, I've added them to the current builds as well: https://gitlab.opengapps.org/opengapps/all/commit/8d6004eb2433f49f7145313d9beecd797cde97cb

3) Installer script seems to misbehave on non-LOS ROMs so we've rolled it back for the time being: https://github.com/opengapps/opengapps/commit/9d7c55f0d7e542d3d2bcf1871cbb863ec915f593

Proper fix is coming with the Q merge.

4) Photos app FCing is a known issue, I'll try to address it ASAP.

EDIT: We're building new packages right now which should work fine. I'll post an update once they're ready.
[Android Software Development] curiousrom:
Re: URGENT: Stop Building Defective Open GApps Failing To Boot

Thanks. :good::cool:

I see that Open GApps builds 201009, 10, 11 & 12 were removed & there is a new 20191013 in https://sourceforge.net/projects/opengapps/files/arm/

Does it include the fix? If so I can test it right now.

***
[Android Software Development] Nezorflame:
It's still building now, I'll post a message once the new release is ready.

But yes, it should contain the fixes.

---------- Post added at 04:16 PM ---------- Previous post was at 03:29 PM ----------

Build status for the new builds:

ARM - done

ARM64 - done

x86 - done

x86_64 - done
[Android Software Development] Nezorflame:
All builds should be up right now. [MENTION=4122877]curiousrom[/MENTION] and others - please check the new builds and let me know if the issues are gone.
[Android Software Development] curiousrom:
Open GApps Fix 2019-10-13 - Boot Success!

Happy to report success:

Downloaded open_gapps-arm-9.0-pico-20191013.zip, checked the MD5 hash for file integrity & copied to external Micro SD card.

Full TWRP backup.

Using TWRP dirty flashed pico-20191013 over Galaxy S5 G900M Official LineageOS 16.0 klte build 2019-10-10 + Open GApps Pico 2019-06-14 + LineageOS AddonSU with TWRP 3.3.1-0.

Wiped both caches & rebooted successfully to System.

Rebooted to System for good measure after 5 minutes. Checked Play Store. All OK.

Attaching open_gapps_debug_logs_20191013_Galaxy_S5_LineageOS_16_curiousrom.tar.gz in case you would like to look at it.

Thanks to you & to all the Open GApps team for your support. :good::cool:

***
[Android Software Development] bschatzow:
Can you install it on top of mind the gaps? I'm having similar issues on my t813 with a clean install.
[Android Software Development] andreoide:
Maybe...

What i would suggest to you:

Download preferred gapps

Twrp backup current rom

Flash the gapps & see if it works,

if unsuccesfull, go back to your backupped rom and report here for your question is still open

Good luck & peace
[Android Software Development] githyanki:
Why do that? You should only be flashing one gapps package. Using two is just redundant and could cause issues.
[Android Software Development] bschatzow:
I have been having intermittent boot loop issues since February on my t813. Just did another clean install and used mind the gaps, su , lineage 16 and twrp. It boot looped after the install of the daily lineage. From trwp, I installed again, cleared both caches and everything is working again.

Not sure what is causing it so I am trying to fix it. I read this forum and saw others with similar issues so wanted to see if this could fix my problem. I have lineage 16 on two identical devices and both have the same problem. What is strange is that clearing cache and delvic cache usually allows a normal boot. It is like something is corrupting the cache. Clearing it allows the system to create it on boot and allows me to boot normally.
[Android Software Development] githyanki:
Three problems I can see. One is that your not using open gapps, so any issues you do have are not due to open gapps. Of you think it is gapps related, ask in the mind the gapps forum. They may ask for logs to have any chance of helping.

Two, SU is severely outdated. Development stopped before lineage 16, so consider updating to magisk.

Third, you may have just listed the items in the wrong order, but ROM should be first. I would do gapps second and magisk third.
[Android Software Development] booci:
October 13 build working fine
[Android Software Development] curiousrom:
Open GApps Report & Galaxy Tab S2 Problems

Thanks for the executive summary. :)

More details please like was it a clean install (new install) or a dirty flash over an existing setup like what your signature says @ the present: Xiaomi Mi 5 Standard edition > Unlocked Bootloader > TWRP > LineageOS > Open GApps? Package version?

***

Like [MENTION=1631192]githyanki[/MENTION] wrote above this is an Open GApps thread which does not support MindTheGapps.

Installing one on top of the other is a bad idea IMO.

"su" - It does not mean anything. Is it SuperSU which does not work properly on LineageOS 16.0 AFAIK or LineageOS AddonSU which works fine on my Galaxy S5 G900M LineageOS 16.0 klte + Open GApps Pico.

"another clean install" - Did you try a real clean install with Format Data in TWRP (instead of a simple wipe data) + wiping System & both caches & flashing LineageOS 16.0 + Open GApps one after the other, in that order & in one go without rebooting in between?

Because either root methods LineageOS AddonSU or Magisk can be installed @ anytime afterwards contrary to LineageOS + GApps which must be installed together I prefer to keep it simple when doing a clean install, boot to System, boot to TWRP & do a full backup then root.

TWRP FAQ: What is a data/media device? for detailed explanations:

"...In TWRP we also have a wipe internal storage option that rm -rf's the media folder and a "Format Data" option that formats to recreate the entire file system in case something goes completely wrong or to remove device encryption."

Format Data adds an empty encryption footer after the end of the Data partition for some future encryption related data if enabled.

"the install of the daily lineage..." - Just because the LineageOS automated builder is churning out nightly builds for 16.0 @ the present it's not a reason to update daily. Look in the changelog for your device to see if updating is worth the trouble. Especially with many LineageOS devs working on the upcoming 17.0 the number of changes applicable to 16.0 have dropped dramatically.

Anyway if you have further problem check the thread for you device: [ROM][OFFICIAL][T813][9] LineageOS 16.0 and the LineageOS wiki - Galaxy Tab S2 9.7 Wi-Fi (2016) codename gts210vewifi which includes an installation page.

***
[Android Software Development] Nezorflame:
We do not support other GApps solutions like the previous posts said. Usually it's up to you and it MAY work, but we don't guarantee it.

SU or Magisk have nothing to do with it as well.

My advice would be to clean flash.
[Android Software Development] bschatzow:
I did do rom first. I was using opengapps. I was using Magisk. I was told that was not supported in the Sm-T813. I do have open gaps on one of my devices and it has the same bootloop issue. I have tried all combinations and problem is the same. The only reason I posted here is others had similar issues and I was hoping to get an understanding on the cause and a possible fix. I believe it maybe a twrp or an OS issue and I will look for a different forum to post to
[Android Software Development] Nezorflame:
Well, if I understood correctly, then you're having issues both with opengapps and with mindgapps. Which leads me to conclusion that there's something wrong with your ROM or some mod you're installing.

It won't hurt to send the logs here, but I doubt we'd be able to help.
[Android Software Development] dedycx:
Google Lens not work in All Pie Custom Rom,

my device Santoni (Redmi 4X).

not work in AOSPExtended/LineageOS… whats wrong?
[Android Software Development] jdrch:
Can confirm the same on LOS 16.0 on the Samsung SM-G900V.

Thanks for fixing this as soon as you did!
[Android Software Development] desosav:
October 13 build working fine as well oj OP3T los16.

thanks guys
[Android Software Development] Nezorflame:
Gonna need more than that. Please provide:

- GApps package name

- installation logs (especially the debug logs in an archive)

- logcat of an error
[Android Software Development] dedycx:
open_gapps-arm64-9.0-nano-20191013.zip

I'm sorry but I don't know how to take a catlog, whether the file I attached is correct or not.
[Android Software Development] Nezorflame:
Read this article: https://xdaforums.com/showthread.php?t=1726238

In short,

1. Start the phone

2. Enable ADB debugging

3. Start making logcat

4. Reproduce the bug

5. Stop the logcat

6. Send the result
[Android Software Development] dedycx:
done,