yashsingh1/xdaforums huggingface dataset:
[Android Software Development] SpasilliumNexus:
libfrsdk.so and libfacenet.so are also tied to that crash: https://pastebin.com/Hc9bj7A8

The only difference between the regular GApps and the test I posted for testing a while ago is swapping out libfrsdk.so, found in /system/lib, from here.

As for the previous "fix", when I posted the test package, I announced wanting testers here and in the unofficial Telegram group.

It was downloaded over 30 times, but got ONE feedback about it working here.

Everyone else who kept complaining about it on Telegram never gave any kind of feedback, despite me repeatedly asking for some.

On top of being pretty much the only person fixing other issues, no getting feedback from the loud ones was enough for me to give up trying to pin down the Trusted Face problem on ARM devices.

I (luckily) still have the testing package, and put it on AFH.

If anyone wants to mess around with it to try finding the cause, be my guest: trusted_face_test-open_gapps-arm-9.0-nano-20181016-UNOFFICIAL.
[Android Software Development] runekock:
I understand your frustration. Still I hope you have the patience for one more question.

When you created the pie version, you added the libfrsdk.so file that now crashes. From where did you get the file?
[Android Software Development] SpasilliumNexus:
That libfrsdk.so file came from the first Pie factory image for the Pixel 2 XL, located in /system/lib/.

That same library I swapped out for testing with is from the SDK26 (Oreo) folder on the OpenGApps repo.

What I would need is someone seeing if that file that I swapped out the Pixel 2 Pie version for the Oreo version works on Pie, in that test package.

Hopefully this makes sense.
[Android Software Development] retired_mnbooze:
Seems like a trivial fix (not to take away from your work, just not a hard code review...) Have you tested it? If not, what variant do you want me to build with that PR cherry picked for your testing?
[Android Software Development] SpasilliumNexus:
The rearranged setup was accepted (Thanks [MENTION=1763928]MNBooZe[/MENTION]!), so I suggest taking a look at the Package Comparison and if you use one, updating your gapps-config.

Especially if you're running a Pie ROM, since Digital Wellbeing and Markup aren't in all packages by default anymore, due to respecting the Pico package of it being the preferred package containing apps for an absolute minimal setup with a ROM. Those two apps have been moved to Nano and higher.
[Android Software Development] ThE_MarD:
It does work fine for me and my A- only partitioned device (in the comments I linked my gist results) but I can't test for a/b devices as I don't have one (so I can't confirm if they keep their build.prop in /vendor/vendor like it has for /system/system/ ) so that's all that really needs to be tested.

If you wish to ensure it works for your device be it treble or non-treble or a-only partition? That's cool too, but yeah, mainly needs to be a/b partitioned treblized devices that need testing. :good:
[Android Software Development] Heiko77:
I'm facing a language issue on gapps mini for 9.0 arm 64v8a. My system language is German. Gapps are only English. Any help for this?
[Android Software Development] runekock:
It is currently an unsolved problem, see

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/post77915718

I believe that a workaround is to use a smaller gapps package, and then install the apps from the play store.
[Android Software Development] Heiko77:
Thanks for your reply. Maybe deinstall apps and install them from Playstore may work, too?
[Android Software Development] Macusercom:
Does Open GApps support A/B devices? Would it survive a dirty flash or is it excluded from addon.d2? The question has been asked before in July just curious if something has changed :)
[Android Software Development] SpasilliumNexus:
https://github.com/opengapps/opengapps/commit/854a211da76eef15bd5bac5220faaaf8c9d69aa3
[Android Software Development] AnonVendetta:
Got a quick question:

I just flashed ARM64 OpenGApps Super package on my ZTE Axon 7 running AOSP Extended 7.1.2. However, later on when I boot into the ROM, I noticed that 2 GApps files are missing:

/system/etc/permissions/com.google.widevine.software.drm.xml

/system/framework/com.google.widevine.software.drm.jar

I know that these files are a standard part of GApps. Why are they not flashed. Is Google removing/deprecating them, so therefore you guys aren't including them either?

Thanks!
[Android Software Development] SpasilliumNexus:
They aren't in the Pixel factory images since I believe Nougat, and are named and in a library format (*.so). I'm not home right now so I can't remember the exact file name.

Does anything act different without them for you? The ROM I'm using (OmniROM) has it included, but doesn't automatically switch video apps like YouTube and Netflix into HD, which is what they're supposed to do.
[Android Software Development] AnonVendetta:
[MENTION=5083335]SpasilliumNexus[/MENTION]: No, nothing seems to be acting different. But I haven't tried YouTube yet. I'm sure there are some legacy apps out there that will look for these files. Any idea where I can grab them?

Edit: I also noticed dialing 911 doesnt seem to be working when I flashed the Super package. I had to do so for a friend earlier today when she had a seizure. It wasn't ringing after I dialed so I had to get someone else to do it. I think it has something to do with Super removing the inbuilt dialer app, maybe the one that's included in the ROM can dial emergency services, but not other dialers. I've never had trouble dialing "regular" #s with Google Dialer/Phone, but maybe special #s are an exception. Probably a permissions thing. I'm going to reflash but with a Full package this time.
[Android Software Development] runekock:
Hope your friend is ok.

Usually, the 911 problem is that you haven't selected the default phone app in settings->apps. OpenGapps tells you to do that when you flash it, but I guess most people don't read that text.
[Android Software Development] AnonVendetta:
[MENTION=4610285]runekock[/MENTION]: No, I read that, and I always do it manually. But it seems that Google Dialer cannot dial 911 if the stock dialer is removed, which is what the Super package does. If both the stock dialer and Google Dialer are present, then GDialer can initiate the call, but it hands off to the stock dialer. When dialing "normal" phone numbers that doesn't seem to happen. Which is why I think it is a permissions issue, even when GDialer is set as default.

The Full package keeps both dialers, I made a test call through GDialer and everything worked, told them there was no emergency and that I was testing. They didn't sound too happy about it, but if this happens in the future (and it will, since she has a medical history of seizures) then everything will work.
[Android Software Development] SpasilliumNexus:
For the widevine files you can find them here

XML: https://github.com/opengapps/all/tree/master/etc/permissions

JAR (either 19, 24, or 25 folders): https://github.com/opengapps/all/tree/master/framework

As for the emergency call, I'm assuming the UI never showed up after dialing. There was a change to include the keyword "+DialerStock" in your gapps-config to prevent the stock dialer from being removed while allowing Google Dialer to still install, above this link: https://github.com/opengapps/openga...-and-Options#prevent-automatic-stock-removals

I'm thinking of making a change for the stock dialer to not be removed in Oreo or later, but I haven't thought exactly how to tackle it yet. Once I get some free time I'll work on it, if no one else doesn't by then.
[Android Software Development] runekock:
Okay, I guess that a Pixel2-file may use some 64-bit instructions or something, even if /system/lib is supposed to be 32 bit. Or maybe the Oreo version had to be hacked to use the strange libprotobuf-cpp-****.so.

I have done these new tests:

Your test-package (which doesn't crash trusted face setup), replaced libfrsdk.so with the Pie version and then setup crashes.

Normal gapps-package (where setup crashes), replaced libfrsdk.so with the Oreo version, and then setup works.
[Android Software Development] AlfaRune:
I am using oneplus3. Using PIE and when i installed gapps. After installing i tried recovering data from online and got error can't recover data. This working fine on October opengapps
[Android Software Development] riyan65:
Links are broken for arm<8.1<full,mini,micro,etc.while at end of download. Please fix this as soon as possible
[Android Software Development] plukanin:
In a first Start boot, setup, got a SIM detection failure, I know, I have one inserted

Just rebooted

Got a SIM detection failure again

...........

That s my actual configuration:

Decrypted, MSM xtended, OnePlus 5

Flashing procedure I ve taken

Flashed ob 19 firmware

Flashed ROM 1011

Flashed Gapps 0611, 2810(Tried several times)

Any idea to solve that issue?

Thanks in advance
[Android Software Development] SpasilliumNexus:
Thanks for confirming! I'll get a pull submitted which will swap the Pie libfrsdk for Oreo's version either later tonight or tomorrow morning.

You'll need to get a logcat taken after trying to do the restore. Make the option come back and run it again using an Activity/Shortcut maker with Android Setup's ".deferred.DeferredSetupWizardActivity"

Screenshot attached showing it being created with Nova Launcher.

Searching "SIM" in that ROM's thread seems to be a ROM and/or firmware issue, with the developer acknowledging it: https://xdaforums.com/showpost.php?p=78031450&postcount=313
[Android Software Development] SpasilliumNexus:
Ended up finding the issue myself while going through setup.

The exact error message is "Couldn't finish restoring the backup."

Not to mention the option to select a backup is skipped completely during setup.

Logcat gave:

I SetupWizard: [UsbMigrationHelper] Package com.google.android.apps.restore not found

Searching "com.google.android.apps.restore" on APKMirror leads to:

https://www.apkmirror.com/apk/google-inc/android-setup/

Building with that included and testing now. Will be submitted for pull once I verify it working.

The reason why I missed this problem is because I do not restore my apps or data on a clean install, and instead, do everything fresh.

EDIT: Fixed.
[Android Software Development] AlfaRune:
Thanks
[Android Software Development] ADB100:
Play store offereing updates that are the same version?

I have an odd issue that seems to reoccur every so often and the apps vary. I have a couple of Samsung S6's - one is my daily running LOS 14.1 and one has a cracked screen that I test stuff on and this is running LOS 15.1. I install OpenGApps Super with a config file to stop the installation of some apps that I don't want (some apps were removed from the stock OpenGApps recently that I wanted to keep so I now use Super with a config file).

Anyway, the issue is every so often the Play store offers updates for Google apps that are the same version as the ones installed with OpenGApps. For example at the moment on both devices I am offered an update to the Phone application. If I check what version is on the phone its 25.0.220310144, the version offered on the Play store is exactly the same. On one of them at the moment I am also offered an update to Google Street View and if I check the version installed is 2.0.0.218515229 and the version installed by OpenGApps is exactly the same.

Usually after a couple of weeks it seems to sort itself out - I am guessing probably because a newer version appeared and it was added to the OpenGApps package and then the Play store app did some sort of re-checking?

Obviously this is not 'service affecting', however its a bit annoying.
[Android Software Development] SpasilliumNexus:
I have the same thing happening, and have yet to figure it out why it's doing it.

In case anyone else is wondering about this weird issue, what happens is despite having the latest version of a Google app, the Play Store silently updates the app with no kind of notification to the EXACT same version, down to the version code (for those who know what that is) for the multi-variant apps. Even if auto-updates are disabled and network preference is set to "ask", the Play Store will ignore those settings. It's noticable when you go to the updates screen and see Google apps installed to /system have been updated, that you know are the latest.

Usually when you uninstall an update to a system app, settings for the app are wiped. With these weirdly updated apps, uninstalling the update keeps the settings. Some time later, the same app updates itself again with no notification. This process is an endless cycle.

Chrome, Messages, Gmail, Google Pay, and Google Play Music are a few to be affected by this.

Edit: I should add that I'm on the beta channel for Play Services, in which I've been thinking could be the cause.
[Android Software Development] ADB100:
I have Play store set to manual updates and I don't believe any of them get updated automatically - except Play services or the Play store app as I think regardless of the auto/manual setting these will get updated if there are updates.

Its weird, but as I say not service affecting and usually goes away once there is an update and GApps includes it.
[Android Software Development] psshirke.shirke@gmail.com:
i am installing stock gapps but want stock camera coming with rom and dont want gapps camera so what gapps config should be pls give config file i am noob... thanks in advance
[Android Software Development] SpasilliumNexus:
Refer to it, which is also in OP: https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
[Android Software Development] methuselah:
I guess this is the best forum to ask this question. With time there are devices that due to small system partitions they are getting useless because google with time making apps bigger and size of apks is getting big. ROMs itself getting bigger. So there are also some lite versions of apps are available there in play store. So I guess there are apks and they can also work with the way gapps. I have no expertise but is this possible to change big apks with lite versions of Google apps? I tried to search this question but didn't find so asked here the same.
[Android Software Development] drose28357:
@ methuselah : do you know the tool repit to "transfer" partionssize from /cache to /system ? It was original develloped for Manta (Google Nexus10).

repit for Manta and Flo

or for the tool lanchon-repit for Manta

and some explanation how to configure the tool

After repartitioning of /System you have to do a resize of the filesystem with resize2fs to max partition size.

And you have to do a resize2fs afte you had you put a e.g. 800 MByte image on an 1.2 GByte /System-partition.
[Android Software Development] loony_tuna:
What does "extra features not available from Google Play" include?
[Android Software Development] Dims_Camper:
is it just me, or latest pie aroma gapps's google message is missing the dark mode toggle?
[Android Software Development] SpasilliumNexus:
Would be nice to know exactly where you're getting that from.

Have the ROM creator patch whatever ROM it doesn't work on, except LineageOS Official (if available) as they're NOT going to add in such a hack. Tell them to look at Nitrogen OS's or SkyDragon's commit history in frameworks_base for it, named along the lines of "Status Bar" or "Pixel Launcher".

The stupid Android One version of Messages snuck its way back into OpenGApps again, which takes priority of installing since that version minimum target is Oreo, and affects Oreo+ ROMs, whereas the proper ones with working dark mode minimum target is Lollipop.

Workaround for now is to either build OpenGApps with the Oreo Messages removed, or don't have Messages install and instead install it from the Play Store.

Previous issue report, resolved until now: https://github.com/opengapps/opengapps/issues/681

Problematic Messages for Android One (arm): https://github.com/opengapps/arm/tree/master/app/com.google.android.apps.messaging/26/213-240

Problematic Messages for Android One (arm64): https://github.com/opengapps/arm64/tree/master/app/com.google.android.apps.messaging/26/213-240
[Android Software Development] VincentJoshuaET:
To fix the Pixel Launcher issue universally, I think Open GApps should include generic RRO overlays on Pie. Look into PixelExperience/vendor_pixelstyle for those. I also has other uses e.g. making Markup as the default screenshot editor app, Google Wallpapers as the default wallpaper picker.
[Android Software Development] VincentJoshuaET:
Here's the stock android overlay APK from PE. (Of course, those values that should be device specific should be removed)
[Android Software Development] laupuy:
https://opengapps.org/ and click* on the green square on the right of the nano package

Edit: in fact, don't click, just fly over to see the text

;)

---------- Post added at 07:56 AM ---------- Previous post was at 07:52 AM ----------

Don't know really but take a look here: https://github.com/opengapps/opengapps/wiki/Package-Comparison
[Android Software Development] Sukrut4778:
Micro gapps are better
[Android Software Development] SpasilliumNexus:
I'll look into it later today and test myself if I can get the APKs to build as I've never messed around with anything RRO.

Ah. Thanks! That button takes me to the description of the package and lists stuff not on Google Play: https://github.com/opengapps/opengapps/wiki/Nano-Package

Dialer Framework, Package Installer, and Trusted Face (Face Unlock) are a few items one cannot download from the Play Store.

K.
[Android Software Development] laupuy:
I just edited my post, in fact, don't click, just fly over to see the text "extra features not available from Google Play"

:o
[Android Software Development] demonoidmaster:
resize your system partition... Or yknow, use pico gapps, there's literally no reason to use any other higher package on a device with limited system space, also if you use a custom rom then you might wanna remove some bloat from your rom (system/app and system/priv-app) but make sure you know what you're doing, if you don't know what some apps are don't touch it
[Android Software Development] SpasilliumNexus:
Because it has been moved to Super, along with a few other apps not pre-installed on Pixel devices, since the 5th of November.

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/post78070740

---------------

An update to Google Markup on Pie: it will be included for ARM devices soon, once I confirm it working with some testers. If all is good, it won't be limited to only ARM64 anymore.
[Android Software Development] curiousrom:
Emergency Calls Problem - Open GApps PR Disaster!

I am a fan of Open GApps & have been using Pico & Nano for a year on 3 devices & posted dozens of times about it on XDA & the LineageOS subreddit but this unsolved emergency call problem makes me sad & mad.

It's extremely rare that I rant about something but this is worth it in the hope of kicking the butt of the Open GApps Team into action.

This delay in fixing the automatic Open GApps removal of the stock Dialer by default when installing the Open GApps Packages Mini, Full, Stock & Super & how it affects emergency calls is totally irresponsible and a major PR disaster for the Open GApps Project.

Check Open GApps Package Comparison and search the page with DialerGoogle to see which packages is including it.

Why does it take so long to take this problem seriously? :confused: It's been months now without any action.

This was posted in 19th March 2018:

One can find several pages about it on the web:

Google search: "Open Gapps" Emergency calls

"Open Gapps" Emergency calls site:www.reddit.com

site:reddit.com/r/LineageOS Gapps "Emergency call"

site:xdaforums.com/ "open Gapps" "Emergency call"

And people promoting MindTheGapps because of it: site:xdaforums.com/ MindTheGapps "Emergency call"

Searching this thread with emergency call

Etc, etc!

And on the Open GApps GitHub some lame discussions with no sense of emergency or consideration about the impact of a failed emergency call can have for users in emergency situations.

This one is marked Closed for some reasons: Request: Option to keep the AOSP Dialer when Google Dialer is installed.

And nobody is posting in this one or caring at all: Keep the stock dialer by default, instead of as configuration due to emergency calls not functioning properly sometimes.

The link you posted to the Advanced Features and Options - gapps-config file page and it's emergency call warning is just lipstick on a pig IMO as just a tiny fraction of Open GApps users will see it and even a smaller % will apply it:

The solution is simple: DO NOT REMOVE the stock Dialer by default in the Open GApps Packages Mini, Full, Stock & Super.

Meanwhile I am attaching to this post a clunky workaround for users: just copy this gapps-config.txt to the EXACT same location as your TWRP flashable Open GApps installer and the stock Dialer will not be removed and you will NOT risk your life with a broken emergency call function.

It also contains some info, links & Test function.

***

This will not work as explained by a LineageOS Team member. Just leave the default Dialer alone. It's not simple enough?

Take the time to read this thread: https://www.reddit.com/r/LineageOS/comments/8ee2hi/cant_call_112/

***
[Android Software Development] David B.:
Thanks for sharing this! I wasn't aware that this configuration feature existed for OpenGApps! One question though: how do I use this configuration when I am installing OpenGApps through TWRP using adb sideload? Obviously the image is not on my phone when I do this.
[Android Software Development] curiousrom:
Re: gapps-config file & adb sideload

I never used sideload but if you check the page linked above: Advanced Features and Options - gapps-config file:

The gapps-config file must be placed in one of the following folders:

the folder containing the Open GApps installer (takes precedence)

/data

/persist

/sdcard/Open-GApps

/tmp/install

"Thanks for sharing this!" - Thanks for the Thanks. Maybe you could Thanks :good: the posts you find helpful? Besides being good for the ego of the poster, it indicates to other users that the suggestions/tips were useful to somebody so may be good for them too.

Could you do me a favor & edit your post above & trim the huge quote? You can delete some stuff between the 2 brackets ] and [ and still keep the quote & included link.

Like this for example:

***
[Android Software Development] SpasilliumNexus:
Yes

Plain and simple, I for one do not have time to try going through the install system and HOPE that I can change the process. I will make this clear right now: I am nowhere near of having in and out knowledge of how scripting works.

Everything I have helped with this project is from hours upon hours of frustrating Google searches (a lot of info I've gotten from StackOverflow) and taking notes, coming from knowing NOTHING of scripting, and yet I still don't fully comprehend it. On top of that, when **** doesn't work as I hope it would, I sit on the verge of giving up.

At the moment, there are two of us doing what we can: MNBooze and I. Hell, I think it's safe to assume that if I hadn't liked this project so much, we'd probably still only support Nougat at the most, and plenty of people here will do nothing but complain about it.

Until I get time to figure out how to change it so the stupid stock dialer doesn't get removed automatically, or unless someone gets off their ass and start learning this ****, seeing as the source is pubically available to everyone, the "lipstick on a pig" workaround stays. And right now it's better than nothing.