yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] zard:
Tested Arm version. Creation of Google account still cannot be done. It keeps staying at "Checking info..." screen.

Note that I tried flashing crDroid Mi Pad, booted up before flashing latest Nano Gapps and also crDroid Mi Pad together with latest Nano gapps and removing SetupWizard.apk before booting up. Google account can't create for both methods. This is same as previous versions of Gapps.

Sent using Tapatalk
[Miscellaneous Android Development] SpasilliumNexus:
Yesterday was a bit grueling reading and editing scripts on the bringup for over half of the day.

It seems that I've missed adding new/updated permission files for the builder to pick up, so I will fix that in a bit.

Hopefully it'll also fix the issues some of you have with SetupWizard.
[Miscellaneous Android Development] laoli0913:
App installer forces stop.
[Miscellaneous Android Development] SkyShader:
Flashed the latest gapps arm64 and gives many errors. GooglePackageInstaller and SetupWizard are not properly working plus new error lol with GoogleExtServices. But managed to replaced these apps with working ones.
[Miscellaneous Android Development] SpasilliumNexus:
See above reply of mine. Missing permissions was the cause. New builds with the fixes aren't up yet. Nezorflame will build and provide them later.
[Miscellaneous Android Development] PlayFriik:
Thank you, appreciate the effort. <3
[Miscellaneous Android Development] debdecoy:
Thanks! Will the latest build solve the Contacts syncing issues.
[Miscellaneous Android Development] Nezorflame:
New build coming soon with the fixes to these crashes.

Let's hope it'll be the final one before we get to the stable phase with daily builds.
[Miscellaneous Android Development] laoli0913:
I know how to solve this, I just want to tell developer what issues the latest build have.
[Miscellaneous Android Development] Tisckkytt:
How to update new builds? Flash from twrp?
[Miscellaneous Android Development] Nezorflame:
Yup.

Usually, you don't need to update your GApps package because apps get updated from Play Store, but if you want to update manually, just dirty flash the package on top of your ROM, like you do on clean flash.
[Miscellaneous Android Development] Nezorflame:
Started the builds. Quick check gave positive results, so this build should hopefully work well for everyone without FCs.

Update:

Builds are ready!

ARM: https://builds.nezorfla.me/?dir=opengapps/pie/arm/20180820

ARM64: https://builds.nezorfla.me/?dir=opengapps/pie/arm64/20180820
[Miscellaneous Android Development] SkyShader:
That was fast for arm. Can't wait for arm64 :angel:
[Miscellaneous Android Development] zard:
Downloaded pico version. Pixel setup didn’t FC but when it reached the part after skipping copying from Android phone/from Google Drive, it kept staying at “Checking info...”. Eventually it ended up with “Couldn’t sign in”.
[Miscellaneous Android Development] k3lcior:
Did you configured Wifi or have Data enabled?
[Miscellaneous Android Development] Nezorflame:
Interesting.

It was ok for my setup though (OnePlus 3 (arm64), nano package + NOS P).

Please attach logcat when reporting issues, everyone.
[Miscellaneous Android Development] Nezorflame:
ARM64 ready as well, updated the post with the link.
[Miscellaneous Android Development] zard:
WiFi.

Sent using Tapatalk
[Miscellaneous Android Development] ruben2000de:
With OP2 and ARM64 20082018 Setup worked so far, but I got a message that recovery of Apps, etc. via Gcloud is not possible.
[Miscellaneous Android Development] PlayFriik:
Setup worked for me without any issues except one (very minor): fingerprint enrollment failed instantly (when it told me to touch the sensor (the very first time - to confirm the location of the sensor), I touched it and then it instantly said that the enrollment failed, and it went to the next page). Again, very minor, because I was able to register my fingerprints on the settings just fine. Other than that, very good - thanks!
[Miscellaneous Android Development] Ranjith_26:
With opx on arm nano package got an issue as the pixel setup was not getting completed . And it's just there on screen without any other changes and keep on loading
[Miscellaneous Android Development] Tisckkytt:
Flashed pico on whyred. Everything went smoothly. No fingerprint issue on setup like the one reported above. No hiccups whatsoever.

Just one annoyance, pixel setup detected that one app, data transfer, needs to update & for it I need to setup a WiFi connection. Since I live on mobile data I couldn't get past it. The notification just doesn't go. I'll have to connect to a WiFi after all to make it go.

BTW, in around a week, got this far with development. Awesome. Thanks for the package. Cheers. :good:
[Miscellaneous Android Development] draymond1987:
So I know I didn't reply about this, due to respect of the devs of Carbon. Now that there is a beta thread out, for the Pixel 2XL. Every package that I flash, results in a bootloop. I don't know what I can be doing wrong. Mini was the package I picked.
[Miscellaneous Android Development] RazrBR:
The Package Installer was updated to 9.0 or still bug?
[Miscellaneous Android Development] slothdabski:
Probably need to build them inline like every other taimen rom. Carbon was the exception, but they also had to build their own gapps package for this to work.

I built them inline last night with carbonbeta repos and these gapps: https://gitlab.com/PureNexus/vendor_gapps/tree/p

it would boot but setup would crash and then phone would restart. Gonna try again tonight with a different gapps repo. might also try removing the setup wizard from priv-app if i still encounter the same issue
[Miscellaneous Android Development] draymond1987:
Please keep me posted! I am waiting for my build to finish, with the gapps that you are using too. I don't know how to build unofficial gapps inline, as there's no make file. Unless I a, missing something. Wouldn't put it passed me though LOL.

[MENTION=2010892]Nezorflame[/MENTION],is there was way to build inline, like the official gapps? What would I need to put in my manifest, and how to "call" the gapps during build?

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

Deleting setup will cause build errors. Even if you take out the offending package that it's complaining about.
[Miscellaneous Android Development] slothdabski:
I mean flash the build then mount /system in twrp and remove it
[Miscellaneous Android Development] draymond1987:
Point me in the direction where it lives? I'm in TWRP now.
[Miscellaneous Android Development] zard:
I'm using Mi Pad (arm), pico + crDroid P.

I'll get a logcat done later. Will Google for guide to do a logcat via computer.

Sent using Tapatalk

---------- Post added at 06:55 AM ---------- Previous post was at 06:53 AM ----------

In TWRP, mount System. Use TWRP File Manager, navigate to root\System\priv-app\SetupWizard, delete it.

Sent using Tapatalk
[Miscellaneous Android Development] slothdabski:
i believe it is in system/priv-app/SetupWizard
[Miscellaneous Android Development] draymond1987:
Let me see if it works......

Nope, Pixel Setup crashes still
[Miscellaneous Android Development] Nezorflame:
You would need to:

1) Add proper version of your new app into the proper architecture repo (all/arm/arm64)

2) Edit few scripts to include your app in the app list

Check https://github.com/opengapps/opengapps instructions.
[Miscellaneous Android Development] Nezorflame:
Package version? Architecture? Device?

Please, be more precise.

Also logcat and installation log would be nice...
[Miscellaneous Android Development] draymond1987:
I was using this https://gitlab.com/PureNexus/vendor_gapps/tree/p

Built into Carbon. Looks like deleting Setup Wizards did the trick. Sorry, super off topic! I'm sorry! /:

Edit: I was trying mini and pico though. Arm64 :)
[Miscellaneous Android Development] SkyShader:
I have flashed the nano 20180820 arm64 on los16 mido with existing 20180819 nano gapps and it won't me allow me to setup pixel using Data connection because no option idk why is that. Everything is okay except that one. So i just did clean wipe on my phone, install rom & gapps and no force closes encountered. Here's the logs anyway if you need it.

https://drive.google.com/folderview?id=1kn4KOWk7RJ58mB0XrwKHIo6thAbNqhVp
[Miscellaneous Android Development] debdecoy:
You cannot install gapps package when another gapps package is already installed.
[Miscellaneous Android Development] SkyShader:
Yes it can, it's an opengapps package that replace existing opengapps packages. Unless you install different variety of gapps.
[Miscellaneous Android Development] SpasilliumNexus:
I don't see anything wrong in your logcat besides minor ROM and non-Google app related stuff. Did you have a data connection active (as in LTE shown next to the symbol icon)? Maybe the option is disabled/hidden if it doesn't detect a connection.

As SetupWizard Pie from a Pixel image is the only one available, it's bound to have issues with other devices, unless another Pie image releases that we can test their SetupWizard on.

For what it's worth, I was able to log into up my account on LTE with Nitrogen OS on OnePlus 3T.
[Miscellaneous Android Development] rizahakam:
I tried to use Stock GApps on my Mi 5s running LOS 16.0 however it can't boot into the rom. however if I'm using mindgapps, it can boot.

I really want to use stock GApps. is there any missing step other than flash the Open GApps?
[Miscellaneous Android Development] zard:
[MENTION=2010892]Nezorflame[/MENTION] [MENTION=5083335]SpasilliumNexus[/MENTION]

To recap, I'm running on a Mi Pad (arm), crDroid Pie and pico gapps (now on nano). Google account creation was not possible.

I had captured two logcats. Here's the link: https://drive.google.com/open?id=19Vm0ktXLE7TCz_OmlmOD09vHErW7py7u

1. logcat.txt - after bootup, turned on USB debugging.

2. logcat_checking.txt - after USB debugging, started Playstore app, it shows "Checking info...".
[Miscellaneous Android Development] SpasilliumNexus:
Yeah. Logs.

Same with the rest of you posting issues, while actually providing nothing.
[Miscellaneous Android Development] rizahakam:
how to get logs from TWRP? because I can't boot into the ROM, therefore the log should be get from fastboot or TWRP.

please kindly advise how to get the log
[Miscellaneous Android Development] SpasilliumNexus:
The GApps installer makes a zip file of everything in the same location you saved the GApps package to.
[Miscellaneous Android Development] rizahakam:
this is the log I got
[Miscellaneous Android Development] Ramyski:
does pixel launcher recents (and app actions too?) work here?
[Miscellaneous Android Development] SpasilliumNexus:
I'm going to make separate flashable zip files of these that were removed with GApps, using the ROM you installed, in which I assume is from here:

https://androidfilehost.com/?fid=1322778262903984433

You'll need to flash each, but rebooting right after flashing one, like so:

- Flash ExtServices

- Reboot into Android

If it doesn't boot up, repeat the two steps above with another zip.

One of these being removed might be the problem.
[Miscellaneous Android Development] rizahakam:
yes correct the ROM I installed is come from that link.

actually the reason I use stock GApps is to get Google Dialer, Google Contact and Android Message as default system app and replace stock AOSP app. for other apps which replaced by Google apps, I can do without remove the stock app
[Miscellaneous Android Development] SpasilliumNexus:
You could use a gapps-config file to exclude everything except for those apps you want.

But since your phone isn't booting after flashing OpenGApps 9, I will need to find out which removed app is causing the problem as Nezorflame and I are the only ones doing this bringup. No one else. OpenGApps 9 works fine on our OnePlus 3 and 3T.

I've repacked each removed file into this folder on AFH: https://www.androidfilehost.com/?w=files&flid=280966

Or if you want to download them all at once, download the zip named "mi5s_removed_apps_pack.zip" in that folder, extract it, and flash one by one.

These zips won't remove anything. Only adding apps back.

Once you find out which zip you flashed that made the phone boot completely again, let me know.
[Miscellaneous Android Development] Xemica:
Hey. When installing in twrp gives an error 40. Phone Xiaomi Redmi 3S Lineage 16. How to solve this problem?
[Miscellaneous Android Development] Cpt. Strawberry Crepe:
Thanks for this great thread! I also downlaoded your 8/8.1 GApps back in the day when we didn't have official ones. Keep up the good work,
[Miscellaneous Android Development] rizahakam:
ok thank you for your help. I will try to flash it one by one.

for each flashing, I don't need to wipe anything right?
[Miscellaneous Android Development] SpasilliumNexus:
Nope. You don't have to wipe.
[Miscellaneous Android Development] vojtah1:
Problem on your side, worked fine for me on 3s with lineage 16.

Try flashing rom first and gapps after reboot
[Miscellaneous Android Development] rizahakam:
I already tried to flash your zip one by one, but it still can't boot into ROM.

it stuck on LOS splash screen and at the end will restart back to TWRP

I'm not yet tried other package from Open GApps, but what package if I just want to replace Stock Dialer, Messaging and Contact with Google Dialer, Android Messages and Google Contacts?

maybe if I used this it will boot into ROM
[Miscellaneous Android Development] bite_your_idols:
Here I have also a Mi5s with LOS 16

- After flashing rom I can Boot.

- Flash gapps stock -> bootlogo and back to TWRP

- Flash every zip one by one and after each flash I tried to boot -> bootlogo and back to TWRP

- I wipe and flash rom again, then I can boot.

- Tried with nano and pico -> bootlogo and back to TWRP

- Flash all zips and tied to boot -> bootlogo and back to TWRP

- I wipe and flash rom again, then I can boot.

- I flash mindthegapps -> I can boot but setup wizard FC and I can not sync my contacts...

If you want me to test anything else, please let me know...

here you have logs
[Miscellaneous Android Development] SpasilliumNexus:
Try this pico package. If it works, that doesn't mean the problem's solved. There's still more testing to do.

This is set up to not remove a few core files: https://androidfilehost.com/?w=files&flid=280988

Install this on a clean system. No dirty flashing.
[Miscellaneous Android Development] bite_your_idols:
It doesn't work...
[Miscellaneous Android Development] rizahakam:
same with me, it's also didn't work. I tried from clean install
[Miscellaneous Android Development] slothdabski:
if you edit your device tree so this line gets added to build.prop

ro.setupwizard.mode=DISABLED

it will skip the setup wizard without having to manually delete it in twrp
[Miscellaneous Android Development] SpasilliumNexus:
Looking at your logs, OneTimeInitializer and BookmarkProvider were removed.

Two more tests here.

- Do a clean install once more, and right after flashing ROM and the DEBUG GApps, flash the onetimeinitializer.zip attached.

- If that's no good, do the same clean install, but instead, flash the onetimeinit_bookmarkprovider.zip attached.

I'm really hoping one of these being removed was the problem.
[Miscellaneous Android Development] bite_your_idols:
Both tests failed to me...
[Miscellaneous Android Development] SpasilliumNexus:
I'm out of ideas after these last two.

==============================================

Let's see if the ROM has USB Debugging enabled by default.

Are you able to run ADB on your PC? If so:

1. Run this in Command Prompt or Terminal without having the phone connected:

adb logcat -d > logcat.txt

2. It should say "Waiting for device" after pressing enter.

3. Reboot the phone and connect it to the PC as soon as you see the bootlogo. If you time connecting it right, Command Prompt or Terminal should still say "Waiting for Device".

4. Let the phone boot and it should reboot to recovery, and ADB should have a logcat saved.

5. Send that to me.

==============================================

Last effort to get the phone booting with GApps.

- Clean flash the ROM and GApps.

- Remove one folder in the list below while in recovery, making sure to reboot after each removal:

1. /system/priv-app/AndroidPlatformServices
2. /system/app/GoogleExtShared
3. /system/priv-app/GoogleExtServices
4. /system/priv-app/ConfigUpdater
5. /system/priv-app/GmsCoreSetupPrebuilt
6. /system/priv-app/GoogleOneTimeInitializer
7. /system/app/GoogleCalendarSyncAdapter
8. /system/app/GoogleContactsSyncAdapter
9. /system/priv-app/GooglePackageInstaller

For example:

- Remove /system/priv-app/AndroidPlatformServices

- Reboot to Android.

- Doesn't boot? Remove the next folder.

Continue doing this until either the phone gets to setup or all 9 items are removed.

If all 9 are removed and the phone still goes back to recovery, unfortunately someone else with that has that phone (like the ROM dev) will have to do troubleshooting, or an alternative GApps package other than OpenGApps will have to do.
[Miscellaneous Android Development] :
Thanks for stealing my avatar :good:

Edit: and my signature... LOL
[Miscellaneous Android Development] bite_your_idols:
Clean install rom and debug pico gapps.... removing 9 folders one by one and it still fails... :p

For logcat I need to wait until this evening since I don't have an avaliable PC right here.

By the way this gapps work flawlessly, in case you can take a look to discover something: https://androidfilehost.com/?fid=1322778262903983907

thanks for your support and work!
[Miscellaneous Android Development] SpasilliumNexus:
Yeah I've checked out the contents of that before, and it's exactly the same with the OpenGApps setup, with the exception of OpenGApps having 8.0+ versions of Play Services install instead of 9.0+.

You could try flashing the correct version of Play Services 12.8.74 (100400-204998136) from my Google Drive to see if anything changes: https://drive.google.com/file/d/1lHmY6ppaM7DoBlkRQ3t16VvTECi3l91q/view?usp=sharing

Also, with this, don't use the DEBUG GApps I've shared before. Use one of the versions in OP with this to test.

Usual steps. Clean flash, flash GApps, then flash the Play Services zip.
[Miscellaneous Android Development] bite_your_idols:
Unofficial pico gapps + Play Services 12.8.74 = no boot... :(

Also, I have to say that mindthegapps don't work "flawlessly", app data can't be backed/restored and google asystant is the old fashioned one... but at least rom boots and there is google contact/calendar sync.
[Miscellaneous Android Development] rizahakam:
same with me also. the ROM didn't boot and will be reboot into TWRP.
[Miscellaneous Android Development] zard:
[MENTION=2010892]Nezorflame[/MENTION] and [MENTION=5083335]SpasilliumNexus[/MENTION]

Have you managed to look at the logcat files I captured?

Well, was told by someone from Mi Pad 1 Telegram group that restoring Data via TWRP works.

I installed crDroid Pie from Tommy, flashed latest arm nano Opengapps for Pie from here, restored my Data in TWRP and booted up.

Using Tapatalk now and my Mi Pad is automatically downloading updates from PlayStore.

Sent using Tapatalk
[Miscellaneous Android Development] SpasilliumNexus:
I have looked at them before and still don't know why only Xiaomi devices have issues with these GApps when others such as OnePlus and Moto work fine.

Until someone with a Xiaomi device running Pie can dissect GApps and whatever Pie ROM is out for those, I'm not going to look into it any further. At this point I'm already quite a bit frustrated with posting every kind of suggestion possible between here and Telegram, only for them to not work at all. Not having such devices in possession makes this entire situation much more frustrating.

Anyway, here's some errors and fatal outputs from both those logs. The fatal at the top is also common with Xiaomi devices running Pie.
[Miscellaneous Android Development] Tisckkytt:
i am running xiaomi whyred with aosp pie and pico gapps. no problems for me. setup wizard, log in everything ok.
[Miscellaneous Android Development] PlayFriik:
The GApps seem to cause an issue where Ringtones/Notification sounds lose its display names (PixelExperience 9.0, OnePlus 3T, "stock" package): https://i.imgur.com/y15w8JT.png, https://i.imgur.com/1IR1J6c.png

This seems to happen to other people too.
[Miscellaneous Android Development] lekiaM:
Hey guys, is it normal that the unofficial Gapps causes Play Store>Device not certified? Besides that Nano Gapps package, no issues :)
[Miscellaneous Android Development] laoli0913:
It always shows like that. Unless you use stock ROM.
[Miscellaneous Android Development] RazrBR:
Worked super fine, even restore my backup apps on Google could. Thanks
[Miscellaneous Android Development] laupuy:
Flash magisk, wipe data of play store, and you should be certified
[Miscellaneous Android Development] :
Does it work for you with other gapps packages? Those strings rely on SoundPickerPrebuilt
[Miscellaneous Android Development] PlayFriik:
It seems that the problem is with any package. I have heard even small packages like Nano can cause the same issue.

https://xdaforums.com/showpost.php?p=77403410&postcount=483

https://xdaforums.com/showpost.php?p=77408108&postcount=518

https://xdaforums.com/showpost.php?p=77408503&postcount=520

https://xdaforums.com/showpost.php?p=77409500&postcount=529
[Miscellaneous Android Development] :
You need the SoundPickerPrebuilt apk. Either ask your ROM or the gapps maintainer to include it.
[Miscellaneous Android Development] PlayFriik:
The PixelExperience 9.0 ROM has built-in GApps, and the sounds had its display names when I didn't flash this OpenGApps package (so the ROM seems to have it), but as soon as I did, all the sounds' display names were gone.

This method works with the PixelExperience 8.1 ROM + OpenGApps 8.1.

I guess that this OpenGApps package removes the SoundPickerPrebuilt apk during the built-in GApps removal process, and doesn't add it back.
[Miscellaneous Android Development] :
The 8.1 audio files dont use those strings, they have the names directly in the ogg files. Idk why google thought it would be smart to do it like this :confused:
[Miscellaneous Android Development] PlayFriik:
Oh, that may be why this OpenGApps doesn't have the apk..?

As far as I know, this OpenGApps is updated from 8.1 source where the apk wasn't needed.
[Miscellaneous Android Development] :
Could be
[Miscellaneous Android Development] SpasilliumNexus:
com.google.android.soundpicker is the Google version of SoundPickerPrebuilt, which IS in the Super and Aroma package of the updated ones.

I've added that because I thought it would be a nice addition to choose from. It looks like I'll need to move it down to essential (core, aka required).

Not only are there no ARM factory images to extract things such as libraries from, in case they're needed, more of Google's apps are required to be used in favor of AOSP ones, instead of being optional.

F'in thanks, Google...
[Miscellaneous Android Development] :
Yeah.. No idea why Google did this. Rediculous.
[Miscellaneous Android Development] koushik21:
Same thing happening to me too . I am going to try flashing the rom again . It's gettiing stuck in the checking for updates screen
[Miscellaneous Android Development] Sabissimo:
Pixel Launcher, included in this GApps is Oreo version. Is there any way to install new version? Or am I doing something wrong? I've found apk, it installs, but crashes, requiring "android.permission.status_bar" permission. I've tried to manually move this apk in nexuslauncherprebuilt in priv-apps, add this permission to nexuslauncherprebuilt in /system/etc/permissions, in privapp permission, but still the same.
[Miscellaneous Android Development] SpasilliumNexus:
Pie version of Pixel Launcher isn't included because of that exact statusbar permission issue, and it won't be added until we know what fixes that.

Modding the launcher is out of the question, as OpenGApps only adds non-modified Google apps.