FORUMS
Remove All Ads from XDA
H10 Turbo

[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices

811 posts
Thanks Meter: 2,308
 
Post Reply Email Thread
15th April 2018, 03:15 AM |#5271  
Member
Thanks Meter: 14
 
More
Quote:
Originally Posted by 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 Pico: 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.

Thank you for your reply and suggestion. I am already using the 13 April build.
 
 
16th April 2018, 09:54 AM |#5272  
marcdw's Avatar
Senior Member
Flag Baldwin Park
Thanks Meter: 2,262
 
More
@MNBooZe, 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
16th April 2018, 10:12 AM |#5273  
Senior Member
Thanks Meter: 1,214
 
More
Quote:
Originally Posted by marcdw

@MNBooZe, 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

That's always been my understanding.
16th April 2018, 02:44 PM |#5274  
Junior Member
Thanks Meter: 7
 
More
Does anybody know why the ARM64 aroma packages for 7.1, 8.0 and 8.1 are greyed out (not available)?

Thank you.
16th April 2018, 04:10 PM |#5275  
MNBooZe's Avatar
Senior Member
Thanks Meter: 172
 
Donate to Me
More
Quote:
Originally Posted by marcdw

@MNBooZe, 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

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 ----------

Quote:
Originally Posted by 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.

This is an issue for tvstock too. My guess is that the zips just didn't get uploaded, but I am working with @MastahF to resolve.
The Following 4 Users Say Thank You to MNBooZe For This Useful Post: [ View ] Gift MNBooZe Ad-Free
17th April 2018, 03:46 PM |#5276  
Junior Member
Thanks Meter: 0
 
More
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:
Quote:

I: operation_start: 'Flashing'
Installing zip file '/external_sd/open_gapps-arm-7.1-mini-20180414.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: app_densities.txt
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: app_sizes.txt
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: bkup_tail.sh
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: gapps-remove.txt
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: g.prop
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: installer.sh
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: busybox-arm
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: tar-arm
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: unzip-arm
Archive: /external_sd/open_gapps-arm-7.1-mini-20180414.zip
inflating: zip-arm
Bad mode
Bad mode
Bad mode
Bad mode
/tmp/updater: line 53: /tmp/busybox-arm: Permission denied
/tmp/updater: line 53: /tmp/busybox-arm: Permission denied
Updater process ended with ERROR: 126

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.
18th April 2018, 07:43 AM |#5277  
Asycid's Avatar
Senior Member
Thanks Meter: 161
 
More
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:

Code:
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:

Quote:

You need to call mediaPlayer.start() in the onPrepared method by using a listener. You are getting this error because you are calling mediaPlayer.start() before it has reached the prepared state.

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.
The Following User Says Thank You to Asycid For This Useful Post: [ View ] Gift Asycid Ad-Free
18th April 2018, 08:07 AM |#5278  
SpasilliumNexus's Avatar
Senior Member
Flag Delaware
Thanks Meter: 2,354
 
Donate to Me
More
Quote:
Originally Posted by Asycid

-snip-

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

Quote:

NOTE: If you want any Google Apps on your device, you must follow this step before the first reboot!

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.
The Following User Says Thank You to SpasilliumNexus For This Useful Post: [ View ] Gift SpasilliumNexus Ad-Free
18th April 2018, 08:20 AM |#5279  
Asycid's Avatar
Senior Member
Thanks Meter: 161
 
More
Quote:
Originally Posted by 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

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!
18th April 2018, 08:30 AM |#5280  
SpasilliumNexus's Avatar
Senior Member
Flag Delaware
Thanks Meter: 2,354
 
Donate to Me
More
Quote:
Originally Posted by 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!

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
The Following User Says Thank You to SpasilliumNexus For This Useful Post: [ View ] Gift SpasilliumNexus Ad-Free
18th April 2018, 08:38 AM |#5281  
Asycid's Avatar
Senior Member
Thanks Meter: 161
 
More
Quote:
Originally Posted by 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

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.
Post Reply Subscribe to Thread

Tags
gapps, open gapps, open source, opengapps

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes