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

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,342
123
The Hague
github.com
Has anyone else observed the installer.sh parsing everything correctly, with the exception of the include command?

I feel like I'm going a little bit crazy here, as I've read the RegEx in installer.sh and it looks fine to me, and my gapps-config_original.txt definitely contains 'include' as the first line, but yet gapps-config_processed.txt does not.

I've tried a variety of permutations in the gapps-config.txt, including extra line breaks before or after the 'include', case sensitivity, although I think all of these should pass the relevant checks in the code (although please double-check me).

I'm attaching full logs for anyone to review - thanks!
Hi, thanks for your feedback and logs!
I tracked down the cause: the windows/DOS-style line endings instead of UNIX-style line endings (CRLF vs LF in technical terms).
I will try to make the installer deal with these kind of situations :)

UPDATE: fix https://github.com/opengapps/opengapps/commit/783ff4ef1f587121b9c82e29b5709ddea427ce1f
 
Last edited:

chewdaniel

Senior Member
Feb 27, 2011
2,013
859
183
Kuala Lumpur
Has anyone else observed the installer.sh parsing everything correctly, with the exception of the include command?

I feel like I'm going a little bit crazy here, as I've read the RegEx in installer.sh and it looks fine to me, and my gapps-config_original.txt definitely contains 'include' as the first line, but yet gapps-config_processed.txt does not.

I've tried a variety of permutations in the gapps-config.txt, including extra line breaks before or after the 'include', case sensitivity, although I think all of these should pass the relevant checks in the code (although please double-check me).

I'm attaching full logs for anyone to review - thanks!
Hi, thanks for your feedback and logs!
I tracked down the cause: the windows/DOS-style line endings instead of UNIX-style line endings (CRLF vs LF in technical terms).
I will try to make the installer deal with these kind of situations :)

UPDATE: fix https://github.com/opengapps/opengapps/commit/783ff4ef1f587121b9c82e29b5709ddea427ce1f

am i safe to assume this currently affects gapps_config with an INCLUDE ? while i'm still downloading the 1702 build... :p
 
  • Like
Reactions: DA6030

Diego1751

Senior Member
Nov 4, 2012
240
47
0
I am not sure if I need arm or arm64 for the dorid turbo xt1254. I did some searching and the googles said that the phone has a 64bit bus could someone point me in the right direction?
 

DA6030

Senior Member
Oct 3, 2007
285
130
63
Hi, thanks for your feedback and logs!
I tracked down the cause: the windows/DOS-style line endings instead of UNIX-style line endings (CRLF vs LF in technical terms).
I will try to make the installer deal with these kind of situations :)

UPDATE: fix https://github.com/opengapps/opengapps/commit/783ff4ef1f587121b9c82e29b5709ddea427ce1f
Good find @MastahF! Thanks for the quick patch!
To any other users facing this issue, I recommend the "Edit-->EOL Conversion" function in Notepad++
 
  • Like
Reactions: xenovyzarz

organick87

Senior Member
Jun 12, 2014
432
122
0
long story short, I forgot which gapps i flashed. i went between two packages (doing all necessary wipes in between) trying to fix a problem that ended up being an app problem. forgot which gapps I stuck with. is there anywhere where it'll tell me banks or opengapps?
 

TeutonJon78

Senior Member
Jul 24, 2010
574
283
83
I'm trying to install the aroma version on the Nexus 4 (CM13 - 20160217 and openGapps 20160218 Aroma). On install, it's giving me a constant error 20, saying that the ROM isn't a 6.0.x ROM. I've booted up just the ROM and it's definitely the CM13 ROM, so 6.0.1.

The only odd thing I noticed is that when flashing the ROM, it says it's using the 5.1.1 release keys. However, there are youtube videos of the same issue and flashing opengapps successsfully (but nano instead of Aroma).

Doing a little more debugging:

20160218 Aroma and nano fail with same error 20
20160217 Aroma and nano work (although, my install from aroma failed from error 70, but that's my fault for selecting too many apps)
20160208 nano works

So, something from 20160218 broke install on CM13 by thinking it's the wrong android version.
 

SuperSimian

Senior Member
Aug 22, 2012
802
1,076
133
I'm trying to install the aroma version on the Nexus 4 (CM13 - 20160217 and openGapps 20160218 Aroma). On install, it's giving me a constant error 20, saying that the ROM isn't a 6.0.x ROM. I've booted up just the ROM and it's definitely the CM13 ROM, so 6.0.1.

The only odd thing I noticed is that when flashing the ROM, it says it's using the 5.1.1 release keys. However, there are youtube videos of the same issue and flashing opengapps successsfully (but nano instead of Aroma).

Doing a little more debugging:

20160218 Aroma and nano fail with same error 20
20160217 Aroma and nano work (although, my install from aroma failed from error 70, but that's my fault for selecting too many apps)
20160208 nano works

So, something from 20160218 broke install on CM13 by thinking it's the wrong android version.
I can confirm this. Error 20
 

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,342
123
The Hague
github.com
Last edited:

SuperSimian

Senior Member
Aug 22, 2012
802
1,076
133
Today's build tries to use recovery's getprop to fetch the necessary ROM properties.
Could you test which output the "getprop" command gives in your recovery shell (make sure system is mounted)?

Sent from my XT1562 using XDA Forums Pro.

UPDATE: I will remove today's build until we sorted this out
Sorry, I'm unable to test this out until I get home (in about 12 hrs)
 

J0shimi

Senior Member
Jan 22, 2016
68
10
0
Hi all,

I have recently done a clean Flash of the latest Mokee and OpenGapps (Nano) and do not have the option to sync Contacts? It is completely missing from my account settings, doesanybody know what could be wrong and is it missing from Gapps currently?

Many thanks.
 

sarreq

Senior Member
Aug 31, 2010
155
15
0
here's what's probably a dumb question. weekday is the minimal package to include play store recovery of your apps after a data wipe?
 

Heathered

Senior Member
Jun 24, 2012
198
41
0
Belgrade
I'm trying to install the aroma version on the Nexus 4 (CM13 - 20160217 and openGapps 20160218 Aroma). On install, it's giving me a constant error 20, saying that the ROM isn't a 6.0.x ROM. I've booted up just the ROM and it's definitely the CM13 ROM, so 6.0.1.

The only odd thing I noticed is that when flashing the ROM, it says it's using the 5.1.1 release keys. However, there are youtube videos of the same issue and flashing opengapps successsfully (but nano instead of Aroma).

Doing a little more debugging:

20160218 Aroma and nano fail with same error 20
20160217 Aroma and nano work (although, my install from aroma failed from error 70, but that's my fault for selecting too many apps)
20160208 nano works

So, something from 20160218 broke install on CM13 by thinking it's the wrong android version.
Where you find 20160218 gapps? Last version on their site is from yesterday, 20160217...
 

Trudi

Senior Member
Jan 2, 2009
594
195
73
46
Lausanne
20160217 mini arm 6.0, no contacts sync anymore. 20160215 is ok.

---------- Post added at 03:47 PM ---------- Previous post was at 03:47 PM ----------

Where you find 20160218 gapps? Last version on their site is from yesterday, 20160217...
It has been said a few posts before that it was removed to sort those bugs.
 
  • Like
Reactions: Heathered

TeutonJon78

Senior Member
Jul 24, 2010
574
283
83
Today's build tries to use recovery's getprop to fetch the necessary ROM properties.
Could you test which output the "getprop" command gives in your recovery shell (make sure system is mounted)?

Sent from my XT1562 using XDA Forums Pro.

UPDATE: I will remove today's build until we sorted this out

UPDATE2: I have now this patch ready: https://github.com/opengapps/opengapps/commit/80597aa958d1b638d126efa9ca6f1dd6545ed7e7
ro.build.description: omni_mako-eng 5.1.1 LYZ28J test-keys
ro.build.displayid: omni_mako-eng 5.1.1 LYZ28J test-keys
ro.buildfingerprint: google/omni_make/mako:5.1.1/LYZ28J/end/test-keys

Which matches the text it shows when flashing the ROM (and from the youbtube video, has shown since december).
So, it's odd that it says OMNI when it's CM. It's definitely CM13. So, only two options: either a bug in CM13 not updating the build variable, or it's a problem with the Nexus 4 due to it not having an official N6 build to have keys from.

I also checked another CM13 device (unofficial, NookHD+), and it's showing the same thing -- still using the CM12.1 build strings and 5.1.1 reference numbers.

All of the "System Settings > About Phone/Tablet" show the correct CM13 6.0.1 build info. So, it seems it's more a CM13 issue all around.

So, it seems like openGapps isn't really the problem per se, but it being correct prevents it from working. :/

Edit: just checked out OmniROM 6.0 for Nexus 4, and it has the correct build keys for 6.0 in the build.prop

Specifically, from the CM13 build.prop file, here are the values:
ro.build.id=MMB29U
ro.build.display.id=cm_mako-userdebug 6.0.1 MMB29U d34e4c2d70 test-keys
ro.build.version.release=6.0.1
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=occam-user 5.1.1 LMY48M 2167285 release-keys
ro.build.fingerprint=google/occam/mako:5.1.1/LMY48M/2167285:user/release-keys

Is the getprop pulling in the information from the TWRP recovery and not the actual build? (not the different value and eng vs user build)
 
Last edited: