yashsingh1/xdaforums huggingface dataset:
[Android Software Development] ms178:
Google Play Services Stopped

Greetings,

I wanted to upgrade my Xiaomi Redmi 3S from Nougat to crDroid 8.1 build from April 6th (unofficial), and installed the newest Red Wolf TWRP R027 and Magisk 16 as well. Before anyone asks: I've clean flashed it. I've tried the April 1st 8.1 GAPPS (pico and nano) and installed them seperatly from the ROM after a first reboot. The problem is that I get the "Google Play Services Stopped" error as soon as I re-boot and cannot setup the device properly nor using the play store. I couldn't flash the ROM and GAPPS together as I got a warning with that TWRP version that these GAPPS are meant for a different NDK version (this error went away after the first reboot).

If flashing ROM and GAPPS together with other TWRP versions, I got a boot loop with several Oreo-ROMs before.

Is this a known issue with the new April security patch or an incompatibility with the newest ROMs? Or have I missed something? I've tried several other recent 8.1 ROMs, all install fine by itself but as soon as installing the mentioned GAPPS from April 1st I get the same error mentioned above. Hence I think it must be either related to my installation procedure or to the GAPPS.
[Android Software Development] Gus Ghanem:
Open Gapps Micro and up has it, and APK Mirror:

https://www.apkmirror.com/apk/google-inc/exchange-services/

Edit: I just installed the APK on a stock OnePlus 5 (OOS Beta 7) and rebooted; it doesn't seem to work.
[Android Software Development] SpasilliumNexus:
You're going to need more than post text. Recovery logs, OpenGapps logs if any.

Try flashing the ROM ONLY, reboot to recovery, flash GApps, reboot to system. Don't flash Magisk at all until there's verification that setup works.

And try official recovery if there's one available if that doesn't work.
[Android Software Development] ms178:
Thanks for the hints! :good: That was my procedure which unfortunatly didn't work out. I've tried two different TWRP's for my device - a Treble modded version from Jesus Klozz and the mentioned Red Wolf. Apart from that hiccup from flashing both ROM and GAPPS together, the second try after a reboot and flashing them seperatly worked fine for the installation itself though without functional Play Services in the end.

As I've seen some recent updates in the GAPPS-Github repository for the Play Services, I'll wait for the new release then and will try it again. If that won't work either, I'll try to get you the logs. Debugging my phone is not my area of expertise though and would have to invest more time to learn about it. But as I don't need my phone right now urgently I can live without it for some time or downgrade to the last known-working custom Nougat ROM I had before.

I just wanted to hear from you guys if it is a more common problem and if there is a known workaround available, but other people don't seem to have this problem or I would have read about it already. :crying:
[Android Software Development] pijas82:
Opengappa updates now it's weekly?

Thanks ks
[Android Software Development] firdausimbolon:
Probably no. The latest GAPPS updated in April 1st. It's not updated again since 9 days ago, it's more than a week and usually it takes 1-2 days to update. I hope there's no problem about the GAPPS' update.
[Android Software Development] retired_mnbooze:
We still intend for them to be daily, but there have been recurring issues uploading the builds to their Github releases. We are aware of the issue and are working on it. (NOTE: arm64 builds "slipped" through yesterday...)
[Android Software Development] jugoslavpetrovic:
In reality it is not so mandatory for daily releases, I strongly believe so. I suppose weekly is good enough even for flashocholics.
[Android Software Development] Revan335:
Hello,

Problems with the Builds?

No, Updates from 1. April to today?

Or, is this the Easteregg 2018?

I have Problems with the App, when I save the Downloads on external SD Card. Than failed the Download everytime.

To the internal Storage is is working.

Thanks you for your help.

Regards,

Revan335
[Android Software Development] Wolfcity:
Here:
[Android Software Development] tsongming:
Wipe, install rom, official Gapps, Magisk before booting.

If you boot then install Magisk, your device will be determined untrusted by Google.
[Android Software Development] pee-wee:
Always work on all my devices
[Android Software Development] ynamojn:
I think there is a bug with the latest (1 April) arm 8.1 nano build. With that package, I can't finish the Voice Match setup. No problem with 30 March build. Also the latest package file is significantly smaller than previous build.
[Android Software Development] Bianfuchen:
What happened to the daily build ?
[Android Software Development] SpasilliumNexus:
Learn to read. Same with some others that keep asking this question. There's a reply about it a few posts above.

It's like some of y'all just go straight to the reply button.
[Android Software Development] retired_mnbooze:
Here are the changes that I see from the 20180330 build to the 20180401 build:

Books: v4.0.47 --> v4.1.7

Google Pay: v1.54 --> v1.55

Contacts: v2.5.4 --> v2.6.4

Google App: v7.23.26 --> v7.24.31

YouTube: v13.11.59 --> 13.12.57

Of those changes only 1 is in Nano: Google App

As to the size difference, that is typically due to missing variants. in this case the Google App is missing the 160dpi variant, this is verified by size difference in the file: {ziproot}\GApps\search-arm.tar.lz

If the Google App is your issue, today's build could fix it since the it was updated to v7.25.17. (There are lots of other change too though)

In the future, the "Version Information" and "Source Report" links on the OpenGApps.org site are help to get this information.
[Android Software Development] ynamojn:
Thank you for your reply and suggestion. I am already using the 13 April build.
[Android Software Development] marcdw:
[MENTION=1763928]MNBooZe[/MENTION], wait, is that right? Google App is in pico? Hasn't it always been in nano and above?

LG G3 D851, CyanogenMod CM12.1 ROM, Fechda R7 Kernel, MultiROM, Tapatalk 4.9.5
[Android Software Development] sanguinesaintly:
That's always been my understanding.
[Android Software Development] MD_Wach:
Does anybody know why the ARM64 aroma packages for 7.1, 8.0 and 8.1 are greyed out (not available)?

Thank you.
[Android Software Development] retired_mnbooze:
That is correct, I mistyped pico in my response, but the original question was on nano.

---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------

This is an issue for tvstock too. My guess is that the zips just didn't get uploaded, but I am working with [MENTION=6404745]MastahF[/MENTION] to resolve.
[Android Software Development] bilal.net:
Error 126 during OpenGapps package flashing

The error (126) occurred when installing Open GApps on my Galaxy Core Prime VE G361H (ARM CPU architecture), i tried to install Super, Stock and Mini releases v7.1 (Nougat) on LineAgeOS and AOKP unofficial ROMs, always i got the same result "Updater process ended with ERROR: 126". My log debug look like the following:

I moved the package to the internal storage, i got the same message.

I'm using TWRP 3.0.0 recovery tool.

Please any idea with a lot of thanks.
[Android Software Development] Asycid:
Dear highly appreciated Developers!

My phone is a Xiaomi Redmi 3s (I'm not sure if this is important).

If a custom Oreo ROM (any 8.1 ROMs) has been flashed on the phone, none of the Open Gapps release works. Let me explain:

After flashing an oreo rom, the phone boots OK, but if I flash Open Gapps immeadiatelly (without reboot) after flashing ROM, the phone gets an infinite boot state. At this time logcat show this:

04-16 10:53:17.726 1886 1886 E MediaPlayerNative: Attempt to perform seekTo in wrong state: mPlayer=0x7b6bff0540, mCurrentState=0
04-16 10:53:17.726 1886 1886 E MediaPlayerNative: error (-38, 0)
04-16 10:53:17.726 1886 1886 E MediaPlayer: Error (-38,0)
04-16 10:53:17.726 1886 1886 E MediaPlayerNative: Attempt to perform seekTo in wrong state: mPlayer=0x7b6bff0540, mCurrentState=0
04-16 10:53:17.726 1886 1886 E MediaPlayerNative: error (-38, 0)
04-16 10:53:17.726 1886 1886 E MediaPlayer: Error (-38,0)
04-16 10:53:17.726 1886 1886 E MediaPlayerNative: Attempt to perform seekTo in wrong state: mPlayer=0x7b6bff0540, mCurrentState=0
04-16 10:53:17.726 1886 1886 E MediaPlayerNative: error (-38, 0)
04-16 10:53:17.726 1886 1886 E MediaPlayer: Error (-38,0)
04-16 10:53:17.727 1886 1886 E MediaPlayerNative: Attempt to perform seekTo in wrong state: mPlayer=0x7b6bff0540, mCurrentState=0
04-16 10:53:17.727 1886 1886 E MediaPlayerNative: error (-38, 0)
04-16 10:53:17.727 1886 1886 E MediaPlayer: Error (-38,0)
04-16 10:53:17.727 1886 1886 E MediaPlayerNative: Attempt to perform seekTo in wrong state: mPlayer=0x7b6bff0540, mCurrentState=0
04-16 10:53:17.727 1886 1886 E MediaPlayerNative: error (-38, 0)
04-16 10:53:17.727 1886 1886 E MediaPlayer: Error (-38,0)
04-16 10:53:17.727 1886 1886 E MediaPlayerNative: Attempt to perform seekTo in wrong state: mPlayer=0x7b6bff0540, mCurrentState=0
04-16 10:53:17.727 1886 1886 E MediaPlayerNative: error (-38, 0)
04-16 10:53:17.727 1886 1886 E MediaPlayer: Error (-38,0)

The 1886 PID stands for com.google.android.setupwizard.

So if I understand, the gapps setupwizard is calling for some kind of media scanning but it fails, because the needed process is not running (mCurrentState=0)? I'm not a developer, so I'm just guessing.

I've just found this in stackoverflow:

Would you be so kind and check this problem?

Thank you in advance!

P.S.: If you need any extra information to get this sorted out, please reply, and I'll check anything you need.
[Android Software Development] SpasilliumNexus:
Do not reboot if you only flashed the ROM. You need to flash gapps right after before rebooting.

Now you need to clean flash and do both this time.

Among almost every device running 8.1 (including my OnePlus 3T), Mi 3S (Land) follows the same procedure to not get that issue. See the bottom of this guide in the blue box: https://wiki.lineageos.org/devices/land/install

EDIT: I just seen the part where you did not reboot and installed gapps. I'm at a loss as to what that error is.
[Android Software Development] Asycid:
Sorry, I meant to write that if I only flash Oreo ROMs without OpenGapps, then the ROMs are booting normally. BUT if I make a clean flash (Flashing ROM AND Open Gapps without rebooting in between), then the phone gets in an infinite boot state.

BTW if I

Flash ROM --> boot into system -->reboot to TWRP --> flash Gapps -->reboot to system

Then it boots normally, but all the gapps applications are force closing.

So as you can see I've tried already clean /dirty flash with / without rebooting between flashing ROM and Gapps.

Another thing to mention that if I flash a Nougat Rom, this isn't a problem!
[Android Software Development] SpasilliumNexus:
Have you tried MindTheGapps? If they work, I'll check their releases to see what the difference is with SetupWizard and submit a fix to OpenGapps soon: https://androidfilehost.com/?w=files&flid=170282
[Android Software Development] Asycid:
Unfortunately, MindTheGapps has the same problem.

BUT!!

With MicroG, it is booting normally (and it's working), but as we know MicroG is unfortunately not really working together with google apps like gmail or other, so it is not a good solution for most of the people.
[Android Software Development] pee-wee:
Reflash gapps with gapps config 'forceclean', find in advanced features & options section.

Maybe that can help
[Android Software Development] Asycid:
I'll try as soon as I make a backup of the internal storage (takes some time- Hooray MTP!! :D ) and I'll reply back.
[Android Software Development] Asycid:
Ok, I've tried it, but no dice. The same happens. (log shows that gapps-config has been processed)

BTW the log shows there are duplicates:

!!! WARNING !!! - Duplicate files were found between your ROM and this GApps
package. This is likely due to your ROM's dev including Google proprietary
files in the ROM. The duplicate files are shown in the log portion below.

# Begin GApps <> ROM Duplicate File List
/system/etc/sysconfig/dialer_experience.xml
/system/etc/sysconfig/framework-sysconfig.xml
/system/priv-app/Turbo
# End GApps <> ROM Duplicate File List

# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 1561664 | 1561664
Remove | Existing GApps | + 1192 | 1562856
Remove | Obsolete Files | + 976 | 1563832
Remove | extservicesstock | + 20 | 1563852
Remove | extsharedstock | + 12 | 1563864
Remove | packageinstallerstock | + 5976 | 1569840
Remove | provision | + 12 | 1569852
Install | Core | - 104612 | 1465240
Install | calsync | - 1808 | 1463432
Install | dialerframework | - 32 | 1463400
Install | googletts | - 22044 | 1441356
Install | packageinstallergoogle | - 5704 | 1435652
| Buffer Space | - 9216 | 1426436
------------------------------------------------------------------
Post Install Free Space | 1426436
------------------------------------------------------------------

Could this be a problem?

P.S.:

I've attached the Gapps debug logs.
[Android Software Development] Cpt. Strawberry Crepe:
Are we getting new builds or not? Why not try to upload the builds on MEGA for the time being?
[Android Software Development] sanguinesaintly:
Because you don't really need to flash a full new build every day. GApps will automatically update themselves as necessary. Have patience.
[Android Software Development] void main():
Where arm64 aroma package of gapps?
[Android Software Development] sanguinesaintly:
See my post above yours. It will come when it comes. No need to panic.
[Android Software Development] hork-bajir12:
If you really need the aroma package, you can try to download older releases. I think the latest arm64-aroma was 20180409
[Android Software Development] retired_mnbooze:
There are 3 aromas missing from the current build here are the latest for 7.1, 8.0, and 8.1:

open_gapps-arm64-7.1-aroma-20180409.zip

open_gapps-arm64-8.0-aroma-20180409.zip

open_gapps-arm64-8.1-aroma-20180409.zip
[Android Software Development] galen2:
Just tested this gapps and working fine but... why opengapps dont include google device find and google instantapps?
[Android Software Development] SpasilliumNexus:
Find My Device is already included inside Google Play Services and enabled in Settings > Security > Device Admin. The Find My Device client app on the Play Store was never preinstalled on a Nexus or Pixel, so it will NOT be included in OpenGapps.

Instant Apps on Oreo uninstalls itself if it's installed as a user app, and disables itself if it's a system app. That is also included in Google Play Services and needs to be enabled in Settings > Google > Instant Apps, or Play Store > Settings > Use Apps Without Installation.
[Android Software Development] spezi77:
Hey there!

I also get into that bizarre bootloop (reported by Asycid) on my custom ROM for Pixel XL using "official" GApps (taken from Pixel 2XL system image) and/or OpenGapps :/

Edit: the only workaround I have found is to dirty flash.

I have a proof that with my latest ROM build from 6th April, this bootloop didn't occur at all. But with any of my builds compiled within this week, that bootloop occurred.

It could be "anything".. but my personal guess is that it has nothing to do with the gapps itself but with a change in the codebase of your custom ROM.

Edit: I have found the "faulty" commit: see

https://github.com/pixeldustproject...mmit/21abced4c135dee52532d0e84c69703802d97d24

Regards,

spezi
[Android Software Development] Iye Vice:
Can you please explain - why are there no Arm64 8.1 Aroma Gapps? GitHub has no free space left on their servers or what?)
[Android Software Development] demonoidmaster:
Oh boy look at that.

Calm down now
[Android Software Development] Iye Vice:
I'm as calm as a walking dead. & U have no Xplanation, as I C.
[Android Software Development] chewdaniel:
no one needs to explain anything. if they update it, great. if not... well, we'll just wait.
[Android Software Development] SpasilliumNexus:
But had you simply taken a look a page or two back instead of asking the same thing...

And to clarify, MNBooZe is one of the maintainers of OpenGapps.
[Android Software Development] neekless:
Is there any difference between flashing the latest build and flashing an older build then updating the apps through play store?
[Android Software Development] ipdev:
When you install Gapps, regardless what variation, they get installed in /system/

Since /system/ is read only, the update from PlayStore gets installed in /data/ and leaves the original version installed in /system/

Save for that, not really.

Example.

Google KeyBoard /system/app/ = 32.1 Meg

Google KeyBoard /data/app/ = 73.0 Meg

So that is 105.1 Megs used just for a singe app.
[Android Software Development] Iye Vice:
THAT I hadn't noticed, honestly). But it's still strange. Github has tons of data, and some measly gigabytes of 8.1 Aromas have failed to upload. Anyway, thanks. May Android be with you:highfive:
[Android Software Development] demonoidmaster:
You're not deserving of it
[Android Software Development] Iye Vice:
Bad senior member, bad.
[Android Software Development] sanguinesaintly:
Calm down gentlemen (or ladies) !
[Android Software Development] neekless:
Thanks for letting me know. I decided to wipe and flash an older build. I wanted to go back to chrome 65.
[Android Software Development] Marnux:
Wrong disk space values on Huawei P20

While installing a pico opengapps package, i noticed that the disk space values are wrong.

Total System Size (KB) | Filesystem
Used System Space (KB) | 1K-blocks
Current Free Space (KB) | Used

I was able to trace it back to the section "Detect A/B partition layout ":

if [ -n "$(cat /proc/cmdline | grep slot_suffix)" ];
then
device_abpartition=true
SYSTEM=/system/system
else
device_abpartition=false
SYSTEM=/system
fi

The evaluation is true and it should be false. So either slot_suffix should be absent or something else, i haven't thought about, causes this behaviour?

loglevel=4 initcall_debug=n page_tracker=on unmovable_isolate1=2:192M,3:224M,4:256M printktimer=0xfff0a000,0x534,0x538 androidboot.selinux=enforcing buildvariant=user androidboot.swtype=normal fastboot_version=Chipset-boston8.1.0.001(01A3)_FASTBOOT setup_logctl=0 fastbootdmd=0 enter_recovery=1 enter_erecovery=0 androidboot.mode=normal pmu_nv_addr=0x209e0014 low_volt_flag=0 usb_macbt=normal boardid=0x00001971 normal_reset_type=BR_CHECK_RECOVERY TP_COLOR=210 COLOR_TMP=0 LCD_DENSITY=0 DDIC_INFO= productid=0x39023414 efuse_status=0 androidboot.serialno=UBV7N18316012853 himntn=0111111111111010001011000000000000000010 boot_slice=0x0009ab1e reboot_reason=recovery exception_subtype=no last_bootup_keypoint=250 recovery_update=0 bootlock=unlocked hw_bfm_enable=0 hw_bfr_enable=1 ddr_density=4 swiotlb=2 mdmreglogbase=0x00000000 mdmreglogsize=0x00000000 modem_socp_enable=0 androidboot.hardware=kirin970 androidboot.veritymode=enforcing tpcolor=black androidboot.verifiedbootstate=ORANGE ufs_product_name=KLUDG4U1EA-B0C1 format_data=1 cpu_buck_reg=0x;; LCD_ID=0 androidboot.ddrsize=4 ddr_rank_boundary=0x00000000 dma_zone_only=true oba_version=20180411135215_OBA_VERSION kce_status=0 androidboot.vbmeta.device=PARTUUID= androidboot.vbmeta.avb_version=1.0 androidboot.vbmeta.device_state=unlocked androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.size=7040 androidboot.vbmeta.digest=c166060cb060fdf4d08473d8d27c6593affc9ad23c2b328b78b7886f30decb01 androidboot.vbmeta.invalidate_on_error=yes androidboot.veritymode=enforcing bl1_time=2180 bl2_time=19374 logo_time=3714 androidboot.slot_suffix=_a dsm_notify=1 backcolor=black vendorcountry=hw/eu devmodel=EML-L29 userlock=unlocked androidboot.oemmode=user console=ttyS0

If this is the case, there might need to be looked into an alternative way to determine the device_abpartition to be true or false.

When replacing the grep with something along these lines:

sed -n 's/.*slot_suffix=\(..\).*/\1/p'

It would be possible to use actual values. In my case this would be _a

DISCLAIMER: I have little knowledge about the way android oreo things are configured, so i may be way off.

As soon as i created my own package where i forced the device_abpartition to false and SYSTEM to /system, it worked without issues.

I attached the logs for the failing package for inspection.
[Android Software Development] derei:
BUG - Dark Themes.

- When on Dark Theme and selecting the Storage Place, the text is not visible (white on white background).

I've seen this is a old issue and hasn't been fixed yet. Maybe you want to rush it?

Thanks.
[Android Software Development] SpasilliumNexus:
Wrong thread.
[Android Software Development] derei:
You could at least point me towards the "right thread"... couldn't find it by myself, or I would have posted there...
[Android Software Development] SpasilliumNexus:
1. There is no "Storage Place" app made by Google.

2. No Google app in OpenGapps has ever been modified, and will not be. Especially not for themes.

3. Find whatever device forum you got your ROM from and post the issue there. Judging from your post history, P8lite.

4. If not a ROM issue, take it up with whoever made the theme.
[Android Software Development] derei:
It seems you rushed to conclusions too fast.

1. There is an app for downloading Google Apps from opengapps.org and it can be found here: http://opengapps.org/app/

2. Whatever device DOES NOT matter, as the issue is with app's Dark theme.

3. It is not a rom issue and the theme was made most probably by the same who made the gapps apk... so based on this, I believe this is the right thread for it.

Now, do you think you can have an answer for me, or you will leave it to someone else? Thanks.
[Android Software Development] SpasilliumNexus:
You should've mentioned the OpenGapps app in the first place...

Now for your answer: The app hasn't been updated for months because the person who made the app hasn't been active since. Use the website, which also has an option to download versions for Oreo for those that run Oreo ROMs, which is also missing from the selection in the OpenGapps app, for the same reason I've mentioned.

How's that for an answer?
[Android Software Development] pee-wee:
You can report here https://github.com/opengapps/opengapps-app-support/issues
[Android Software Development] demonoidmaster:
same, that's a bug in the app, they haven't updated the app in a long time so

---------- Post added at 10:56 PM ---------- Previous post was at 10:52 PM ----------

Honestly they should just ask someone else to make their app if that other person codekidx is MIA and can't be contacted
[Android Software Development] dany2189:
Gapps

What Gapps to be selected for redmi note 5.?
[Android Software Development] Ibuprophen:
What Android version do you have! Android 6, 7, 8, etc...?

I believe that your device has the "ARM64" Platform.

Also, you'll need to figure out which "Variant" you want as well. The following Official OpenGApps link, you will be able to see the Package Comparison for the different "Variant" choices.

https://github.com/opengapps/opengapps/wiki/Package-Comparison

Or, if you can, on the Redmi device, you can go to www.opengapps.org and see which one it reflects.

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Android Software Development] Not Available:
arm64 dude
[Android Software Development] Ibuprophen:
Thank you for pointing this out! :)

I just corrected my post.

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Android Software Development] xfirefist:
great work!