yashsingh1/xdaforums huggingface dataset:
[Android Software Development] curiousrom:
Fast Logcat Capture - Successful ROM Update w/ Open GApps Build 2019-10-13

Or to make the logcat short & relevant: reboot, reproduce the problem & then use SysLog to quickly capture a logcat. (screenshot)

SysLog's Play Store & Github pages explains how to give the app the required permission via adb if you don't have root:

adb shell pm grant com.tortel.syslog android.permission.READ_LOGS

Syslog on GitHub with F-Droid + Play Store links.

***

Something went wrong & your logcat is too short & does not contain anything about you trying to use Google Lens.

Try the Syslog suggestion above and while it supports capturing all those logs, only the Logcat (Main log) is useful in our case:

Kernel logs (dmsg)

Last kernel log (last_kmsg, if device supports it)

Pstore logs

Main log (Logcat)

Modem log

Event logs

SELinux audit logs

And maybe you could edit your post above & delete that logcat attachment so users don't waste their time downloading it please?

***

Edit: [MENTION=2010892]Nezorflame[/MENTION] - I just updated to LineageOS 2019-10-15 via the built-in LineageOS OTA Updater (screenshot) a Galaxy S5 G900M LineageOS 16.0 klte running build 2019-10-10 + Open GApps Pico build 2019-10-13 + LineageOS AddonSU, no custom kernel or system mods of any kind & everything went smoothly.

The device was updated because that build or newer includes the 260605: Bump Security String to 2019-10-05 patch.

***
[Android Software Development] dedycx:
I use open_gapps-arm64-9.0-nano-20191013.zip

revision catlog attached

ok, thank you for telling and reminding :highfive:
[Android Software Development] Ahmad04:
The 15th October build has problems booting,

Poco F1. LOS+STOCK GAPPS clean flash
[Android Software Development] curiousrom:
Re: Open GApps Build 2019-10-15 Problem Booting?

What happens exactly? Boot loop, boot error message, thrown back to recovery, etc?

Did you 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?

Did you try with a smaller package like Pico Build 2019-10-15 or tried Open GApps Stock Build 2019-10-13?

How come in your open_gapps_log.txt it says "Device Recovery | OrangeFox Recovery!"? Did you install TWRP or an other recovery? Edit: I saw in your Recovery_tmp.log: "Starting OrangeFox TWRP 3.3.1-R10.0-1-042d07c4 (for device beryllium)".

***
[Android Software Development] Ahmad04:
My phone just did not boot up even after waiting for an hour, I wiped everything and installed via a USB OTG like always do, no I didn't tried other version of GApps, I'm using OrangeFox recovery based on latest TWRP:)

Also I'm using 13th October Build and it's working fine
[Android Software Development] curiousrom:
Re: Open GApps Build 2019-10-15 Problem Booting?

Wipe is not good enough. You need FORMAT DATA in TWRP.

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

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

I see in your Recovery_tmp.log:

I:wipe_path '/data'

Wiping data without wiping /data/media …

That means that you did not Format Data to remove the encryption that your device had previously.

***

"I'm using OrangeFox recovery based on latest TWRP" - Why? Why not official TWRP for Xiaomi Pocophone F1?

"Also I'm using 13th October Build and it's working fine" - I'm not sure I understand. Did you do the exact same clean flashing procedure with build 2019-10-13 that you used with failed to boot 2019-10-15 & it worked?

Or did you dirty flash build 2019-10-13 over failed to boot build 2019-10-15?

***
[Android Software Development] Ahmad04:
Yes sir I did the exact same procedure as on 13 to 15th October Build, and I use OrangeFox because official TWRP has some kind of INITIAL FREEZE issue.
[Android Software Development] curiousrom:
Re: Open GApps Build 2019-10-15 Problem Booting?

Is your Xiaomi Poco F1 (beryllium) encrypted by default on first boot by lineage-16.0-20191015-nightly-beryllium-signed.zip'?

***
[Android Software Development] Ahmad04:
I'm not sure, but I use Disable Force Encryption everytime to disable it whenever I use any ROM
[Android Software Development] curiousrom:
Re: Open GApps Build 2019-10-15 Problem Booting?

As you can read in the LineageOS Device Support Requirements Charter:

Your Xiaomi Poco F1 (beryllium) is encrypted by default on stock ROM so on first boot with LineageOS it should be encrypted also by default.

I see in your Recovery_tmp.log:

custom recovery instead of stock TWRP

ro.crypto.state=encrypted

I: Decrypt adopted storage starting

custom kernel which you did not mention in your original post: malakas_kernel_q_beryllium_2019-10-13.zip'

I:wipe_path '/data' Wiping data without wiping /data/media instead of Format Data which is required when doing a clean install on an encrypted device

A custom kernel can be flashed later instead of during a clean install to remove a possible fail to boot error.

BTW because just like a custom kernel 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.

So we will have to wait for Open GApps Build 2019-10-15 with regular install reports before concluding that there is a problem with it.

***
[Android Software Development] psshirke.shirke@gmail.com:
Give link to latest 10 gapps for arm devices
[Android Software Development] curiousrom:
Open GApps Older Releases & Beta Android 10 Links

You forgot to say please or por favor or s'il-vous-plait or 부디, etc. ;)

https://opengapps.org/ > OLDER RELEASES link in the bottom of the page > navigate to arm or arm64 and look for the Beta folder in it.

It's Beta @ the present but may change to official at one point. No ETA questions please.

***

[MENTION=2010892]Nezorflame[/MENTION] - Maybe that OLDER RELEASES link could be renamed ALL RELEASES & ARCHIVES instead as it also links to the most recent ones?

Or: NEW & OLDER RELEASES.

***
[Android Software Development] psshirke.shirke@gmail.com:
Of course

Pls.
[Android Software Development] curiousrom:
And now you forgot to say thanks or merci or gracias or hit the :good: button, etc. ;)

***

Get a Flag!

Tip: go to your XDA profile in this panel https://xdaforums.com/profile.php?do=editprofile and add info > City (can be fake) & Home country & then you will get a flag under your username which gives an international flavor to this thread IMO.

***
[Android Software Development] LewisM45:
Has anyone tried the latest GApps? Still bootlooping? Also I wonder if the Pixel Launcher bug is still present...
[Android Software Development] Md Hafeez HS:
Hello, please help me,

I've a Galaxy A5 2017 SM-A520F which supports VR Mode in stock ROM,

But Open GApps doesn't install Google VR Mode in LineageOS.

In opengapps log, I found, VRMode Compatible | false,

Please give me a solution.
[Android Software Development] dedycx:
use version >20191013 safe from bootloop.

Pixel Launcher, yes bug on me too I use OpenGapps Mini 20191017
[Android Software Development] dedycx:
Big Thank's to you and all dev contribution, Google Lens 100% work now in Pie Lineage :victory:

but I have bug force close in Pixel Launcher
[Android Software Development] curiousrom:
Re: Pixel Launcher Crashing

Did you try the fix described in this Open GApps on GitHub bug report: Pixel launcher crashes on android 9 #727?

Was that a clean install or just dirty flashing on an existing setup?

***
[Android Software Development] dedycx:
I read that and take me to Pixel Launcher crashing due to missing STATUS_BAR and MANAGE_ACTIVITY_STACKS permissions

ummm ya, I just dirty flashing.

and thanks again for your answers, but I choose disable Pixel launcher and change to Lawnchair ;)

All is great now
[Android Software Development] curiousrom:
Re: Pixel Launcher Crashing

But this is an Open GApps thread & you posted twice about the Pixel Launcher crashing so if you want to contribute maybe you could try the fix, enable & set as default Pixel Launcher, reboot & report here?

I am wondering because [MENTION=1763928]MNBooZe[/MENTION] (NicholasBuse on GitHub) posted a link to a patch in Pixel launcher crashes on android 9 #727 in his post here which modified etc/permissions/privapp-permissions-google.xml which is the exact same file that [MENTION=2010892]Nezorflame[/MENTION] modified to fix the fail to boot problem recently.

lober13 in his post in that thread reported:

***

Thanks for the thanks but hitting also the Thanks button :good: on the posts you find helpful is always appreciated. ;)
[Android Software Development] Dyt199412syam:
I need help here, after i flashed the latest micro-20191017 build, i faced a very slow apps download through playstore. I try to download any file through my browser and it can download any file normally, fast enough. So i concluded if there is no problem with my internet, it is pure playstore's problem. Did wipe data/cache of playstore but didnt help. Thanks for advance.
[Android Software Development] DarkHeart Z:
package update request

It's been long since I kept checking up the sources report and version information and google chrome ( latest v77), Google connectivity services (still 3.4, 3.5 came up month ago) and android messages v5 is getting seem many days ago. But still hasn't seen any updates in the aroma gapps package. Please humbly requesting for updating them. [MENTION=6404745]MastahF[/MENTION] please give an to those packages. I am waiting a notable time for seeing them to be updated. Android 7.1, aroma, last checked - october 22.
[Android Software Development] ipdev:
Thank You! to all of the OpenGApps team and contributors. :highfive:

Past, Present and Future. :)

Now that the official builds have stabilized again.

I have some questions and a few issues with the 10 Beta(s).

Pixel C.

Unofficial Lineage 17. (Includes a custom vendor image.)

The last test build worked fine. The beta builds give me an API (SDK) error.

If I install the rom and then mount system (or remove the version check) before installing OpenGApps, the beta builds work fine.

Nexus 7 (2013) WiFi and LTE.

Unofficial Lineage 17 and AEX 7.

The test builds and the beta builds break the UI. Not sure why?

Removal without a compatible replacement, permission, something in the rom?

Same story about the install, if the API (SDK) check is active it errors out. If I mount system (or remove the version check) OpenGapps appears to install.

Sidenote:

We have the option of two arm 10 GApps packages (save for SetupWizard) currently working on Nexus 7. I would like to help make OpenGapps the third and preferred version. ;)

Questions:

Will logs from the 1006 beta still help or, better to wait for a new beta to test and post logs?

Is SetupWizard working on arm 10 devices?

SetupWizard worked on Pixel C. (arm64)

It seems product (system/product) and product/priv-app (system/product/priv-app) is being ignored. Apk(s) are being installed (permissions set) into system and system/priv-app instead. Work around for SDK 29, will it cause problems in SDK 30?

Mounting seemed to be working with SDK 28.(?)

With 29 system as root is forced, just need to determine what version of SAR.

Still thinking on this one but (if greater than SDK28), check if roots_fs or system/system and mount accordingly ?

I'm sure I worded this last one wrong but, I hope the concept is understandable.

Cheers all. :cowboy:
[Android Software Development] J.2.J:
OnePlus 3T Google Photos not working or updating

Hi all. First time here.

I have flashed open_gapps-arm64-9.0-stock-20191023.zip on top of the latest nightly LOS 16 for OnePlus 3T and everything works fine with the exception of the Google Photos app.

I have tried to disable and re enable the app but nothing helps. Cannot update from the play Store either.

Any suggestions how to fix this? Thanks
[Android Software Development] :
Google Photo app isn't compatible with OnePlus 3. You have to look for mods of the Google Photo app (there are some at xda -> https://xdaforums.com/apps/google-camera-mods/app-arnovas-google-camera-port-t3862448).
[Android Software Development] J.2.J:
Hi , thanks for replying. The issue is with Google photos, as in the gallery app, not Gcam. I have Gcam sideloaded and working fine. It is the Google photos app that I use to backup my photos to my cloud account.

I did read previous posts where there was some issues with Google Photos but I believe those have been resolved?
[Android Software Development] ipdev:
Sometimes the failing App is not the problem.

Sometimes it's a conflict with another app that causes an error, even if the other app is working fine.

I haven't looked to close at the error on my phones.

Both use opengapps-arm64-9.0-nano.

Google Photos and Camera are installed from PlayStore.

When I update the rom on my main and testing phones, Google Photos will force close. It errors out when checking the camera library if Google Camera is installed. If I uninstall Camera, then open Photos, it will access the camera library. I can then reinstall Camera and Photos will still work.

Camera on the other hand, has no issues (Save for breaking Photos upon rom update ;) ).

It's been awhile since I clean flashed either and do not remember if I had to install Photos and open it once before installing Camera.

Main phone is updated once a month or so. Testing phone has been primarily stock or no rom installed lately.

You could try the same. Uninstall the modded gCam and see if Photos works correctly.

If so, then reinstall the modded gCam and see if Photos still works.

Cheers. :cowboy:
[Android Software Development] J.2.J:
I have tried your suggestions, uninstalled Gcam, disabled the Google Camera that was installed with Gapps, tried to open the Google photos but no luck. Tried disable and reenable Google photos too, still nothing. Reinstalled both Google camera and Gcam, no luck either.

I am thinking another clean flash with latest builds again but that's still more effort than I need for one app. If you have any further suggestions please let me know.

Thanks again! :fingers-crossed:
[Android Software Development] psshirke.shirke@gmail.com:
When can we get stable android 10 gapps, beta builds showing error after flashing , this is not android 10 rom, why?
[Android Software Development] guhvanoh:
No ETA questions please, XDA rule. Now are you saying that you're installing beta 10 gapps on andriod < 10? If yes, then that's just wrong and a reason why you get errors.

If no, well it's a beta, errors happen sometimes. Post patch to fix them.
[Android Software Development] psshirke.shirke@gmail.com:
I am installing 10 beta gapps on android 10 aosp (device mi 3 =cancrow) then error says it's not android 10 device.

And I am patient about stable build , just curious to know when we can expect it, that's it.
[Android Software Development] J.2.J:
Google Photos is somehow working!? Previously even after trying your suggestions, the app would not update via the play store either. Today I noticed that the update applied itself during auto update, and I opened Google Photos which now works without issue. Maybe your suggestion worked in the background somehow. But I am happy that everything works :victory:
[Android Software Development] cdevidal:
Help? I can't download with the Open GApps APK. The download goes to 0B then stops with no errors. Doesn't matter what variant I use. As root or not. The directory it is downloading to does exist and there is plenty of space. I don't know where open_gapps_log.txt is to share. Phone is Galaxy S3, ARM, LineageOS 14.1, Android 7.1.

FYI I had attempted to install alongside LineageOS using TWRP. Used the Aroma package and I got the wizard, but it did not install in the OS. So I thought I might try the APK instead.
[Android Software Development] sanguinesaintly:
Just download Gapps from the website. I can't remember the last time the app worked properly.
[Android Software Development] cdevidal:
Thanks. I had attempted to install alongside LineageOS using TWRP and the download from the website. Used the Aroma package and I got the wizard, but it did not install in the OS. Do I need to go back to TWRP and try again, or is there some way to use the .zip I've already downloaded?
[Android Software Development] sanguinesaintly:
I just use Pico package. As always, flash ROM and Gapps together.
[Android Software Development] cdevidal:
Thanks. And now TWRP won't load with VolUp+Home+Pwr but that's an unrelated issue.
[Android Software Development] psshirke.shirke@gmail.com:
Pixel launcher crashing everytime after 1st boot to system.

Device redmi 3s

Rom - lineage os 16 official (Pie)

Gapps - stock
[Android Software Development] mortezaali:
I need Gapps for android 10

I want to use gapps on https://xdaforums.com/huawei-p-smart/development/treble-t3983093/

I need links to download
[Android Software Development] elna.nitz:
I flashed latest nano beta package (10.0) and face unlock not found ..

Are you planning to add this feature in the following updates?

Thank you
[Android Software Development] lekiaM:
Ask Google.
[Android Software Development] elna.nitz:
What?
[Android Software Development] lekiaM:
Google removed it in 10.
[Android Software Development] AnonVendetta:
So, I have decided to flash a KitKat stock ROM (4.4.4) on one of my older Samsung tablets. Device currently has TWRP installed, custom kernel, rooted with latest stable Magisk.

The first thing I've noticed is that Google Play Store/Google Play Services never auto update, regardless of what WiFi network I'm connected to. I waited for hours on different connections. This ROM is a clean flash with Odin, otherwise unmodified.

Afterwards, i decided to remove all Google components/files with Titanium, using gappsremove.txt from an OpenGApps ROM as a reference point, but leaving a few that I know aren't safe to delete. And searching /system for all instances of "goo" helped.

I think the auto updating fails because the GApps built into the firmware are very old. Or maybe Google has entirely discontinued support for KK. Is there perhaps an archived OpenGApps zip that supports KK 4.4.4, armabi-v7a, and nano/micro? The last time I checked, 4.4 was greyed out for download. I think if I could flash a much more up to date package, this might resolve my issue.

Thanks!
[Android Software Development] emuandco:
https://sourceforge.net/projects/opengapps/files/arm/20191029/ I see Nano and Pico here.
[Android Software Development] Ultraboss:
Hi there,

I'm still building my own opengapps 8.0 super package because yours is still broken (cf https://xdaforums.com/showpost.php?p=78895380&postcount=5934).

I've check the new gitlab repo and it seems to have now, a split for previous api level in arm64 and for api 29+ arm64-new (EDIT : just renamed to arm64 and arm64-old).

My problem is that Chrome have not been updated since 77.0.3865.92 for api 26 and the last commit for version 77.0.3865.116 was put in 29 directory :

https://gitlab.opengapps.org/opengapps/arm64-old/commit/e841a87cc850ad75554a7adc46db6ecfabf96f2d

Am I right ?

Do you will still update the repo for api 26 ??
[Android Software Development] AnonVendetta:
[MENTION=1992533]emuandco[/MENTION]: Thanks for the link. I have decided to reflash the firmware, after my manual GApps cleaning a few things weren't working. I'll let the OpenGApps zip handle the old component removal/install.

I had no idea that OpenGApps had a SourceForge link where the zips can be downloaded. I still cannot DL a KitKat package from this project's main website.

---------- Post added at 11:42 PM ---------- Previous post was at 11:42 PM ----------

[/COLOR [MENTION=1992533]emuandco[/MENTION]: Thanks for the link. I have decided to reflash the firmware, after my manual GApps cleaning a few things weren't working. I'll let the OpenGApps zip handle the old component removal/install.

I had no idea that OpenGApps had a SourceForge link where the zips can be downloaded. I still cannot DL a KitKat package from this project's main website.
[Android Software Development] Wolfcity:
The site isn't optimized for mobile download but after clicking the package you want (I did it with Firefox) just tap on "Try to download anyway" on the sourceforge site (see attached screenshot). If you tap on the "I" on the first site you'll get the checksums, just in case.

I don't know why 4.4 Gapps aren't available on the main page, maybe because there aren't many users anymore who need these packages and server space and traffic isn't for free.;)

But there's a mirror and playstore will do the updating.
[Android Software Development] Nezorflame:
[MENTION=7441667]AnonVendetta[/MENTION] 4.4 OpenGApps are only being built for the ARM in the "nano" and "pico" variants.

They are present in the main page as well:

View attachment 4866999
[Android Software Development] Nezorflame:
Face Unlock (aka "Trusted Face") was removed by Google and is not coming back, it seems.

Since our project's policy is to not modify anything and keep things as close to stock as possible, we won't be adding any hacks to make it somehow work either.

We'll delete the leftover code and packages after the Q release.

See https://www.androidpolice.com/2019/...method-has-been-removed-from-android-devices/ for more info.
[Android Software Development] AnonVendetta:
[MENTION=2010892]Nezorflame[/MENTION]: That's fine, I went with nano from the SourceForge link, I prefer a minimal install. Any Google apps that are not installed by OpenGApps, I will just get them from Play Store or APKMirror.

I reflashed the firmware with Odin, then installed Magisk and OpenGApps from TWRP, all before the 1st time boot of the ROM. No issues so far.
[Android Software Development] curiousrom:
OLDER RELEASES Link Label - Smallest Open GApps Package & Donwgrading

[MENTION=2010892]Nezorflame[/MENTION] - Maybe you miss this post about the OLDER RELEASES link label or did not have time to look at it or think that it's OK as it is?

****

FYI there are new official Open GApps Beta for Android 10.0 build 20191105 available in:

ARM: https://sourceforge.net/projects/opengapps/files/arm/beta/

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

***

Nano is not the minimal Open GApps Package. ;)

I prefer the smaller Pico package & just add the extra apps I need from Play Store.

As you can see in Open GApps Package Comparison Nano includes all this extra stuff that is not required for Play Store & Play Services:

Device Health Services

Face Detect Library

Google Markup

Google App (Search)

Offline Speech Files

Google Digital Wellbeing

Trusted Face (FaceUnlock) < Google disabled that in Android 10.0 according to this post in the support.google forum

You can dirty flash (do NOT wipe System & Data!) Pico over Nano to downsize because as you can see in the Package Comparison page Nano only removes & replaces the Stock/AOSP version of Package Installer just like Pico does.

If you downgrade from a bigger package to Pico: dirty flash both your ROM + Pico to re-install the stock apps removed by the large package.

+++
[Android Software Development] Nezorflame:
I'll discuss this with the team, maybe will indeed rename it.
[Android Software Development] ipdev:
Hi all.

Need a little help/advice.

I can not build Opengapps using the current sources.

I had a little trouble updating it. I gave it a few days and tried again.

Same problem so I deleted it and cloned it again.

git clone git@github.com:opengapps/opengapps.git
cd opengapps
./download_sources.sh
make arm-28-pico

Am I missing a step ?

I attached the terminal output from downloading sources and the make arm-28-pico.

(Maybe someone will see something in the source download or build errors that I missed.)

Note:

Pulling a backup copy of opengapps that I have from beginning of October, as long as I do not update it.

I can still build using make arm-28-pico (nano, stock ..) so I don't think it has to do with updating anything on my system. (?)

Cheers.