[Q&A] [GAPPS][2015-06-01] Open GApps for Android 5.1, 5.0, 4.4

Search This thread

dhavalmehta

Member
Sep 3, 2017
36
1
Ahmedabad, Gujarat, India
Go to the main thread and read some of the last messages.

ZTE Axon 7 A2017U, CarbonROM CR-5.1-MOO, microG (NoGapps), Multiboot, Tapatalk 4.9.5

That is the my main point. There are many unofficial open gapps build are available then also we do not have official gapps build even after 2 months. What is wrong with open gapps team that force them not to release 8.1.0 gapps?
 

wseverin

Senior Member
May 12, 2008
147
159
Phoenix
gapps for android 8.0 tvstock and aroma variant are not available to download. Also even after 2 month of 8.1.0 release opengapps are not available. why?

I cannot answer why no pre-built 8.1 yet, but it is easy enough to build the 8.1 packages for yourself. The code is all on github and the build instructions work. I just finished another build of 8.1 for arm64 mini a few minutes ago.
See the instructions for building yourself here:
https://github.com/opengapps/opengapps/blob/master/README.md
 
  • Like
Reactions: dhavalmehta

dhavalmehta

Member
Sep 3, 2017
36
1
Ahmedabad, Gujarat, India

marcdw

Senior Member
Sep 24, 2014
5,751
2,894
60
Baldwin Park
  • Like
Reactions: jdesignz

rona7do

Member
May 14, 2015
9
0
Hi,

Trying to install GAPPS clean install but getting error 70 on my Galaxy S2. any help appreciated. Thanks
 

wooleyx64

New member
Feb 7, 2018
3
1
RR on TMobile Note 3 Gapps fails

I have a SM-N900T Note 3 and I am attempting to get opengapps to work on this device. I have flashed Resurrection Remix (7.1.2r36) through TWRP 3.2.1-0 about 5-10 times now I always get the same setup wizard fails and pretty much all the gapps fail.

Cant post logs due to new user limitation: -_- They are up on the Gitter page under the same username.

Eventually the system locks up and all I get is a black screen with the clock and a blue square.

I am not entirely sure what is going on. I was able to get RR to run with Gapps on my HTC M8 this week without issue. I have more exp with HTC than Samsung devices.

My M8 was already 6.0 before flashing IDK if it matters that the note is on 4.4.2 stock tmo.

Any help appreciated,
-Wooley
 

amitroutray

Senior Member
Dec 31, 2011
898
249
Can anyone help me with script of removal AOSP application?? Open Gapps is not working properly on my Nexus10 after installing Omni ROM.

Thanks in advance :)

Triggered from RN4
 

marcdw

Senior Member
Sep 24, 2014
5,751
2,894
60
Baldwin Park
@wooleyx64, try the following tip and see if it works.
Create the file /sdcard/.removesetupwizard

This will apparently bypass the Google wizard on first startup. After getting into the ROM (and maybe checking permissions of various Google apps - optional but I like to do so) you can then create the Google account via Settings.

See this post for more details...
http://xdaforums.com/showthread.php?p=75309902



LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
 
Last edited:

wooleyx64

New member
Feb 7, 2018
3
1
@wooleyx64, try the following tip and see if it works.
Create the file /sdcard/.removesetupwizard

This will apparently bypass the Google wizard on first startup. After getting into the ROM (and maybe checking permissions of various Google apps - optional but I like to do so) you can then create the Google account via Settings.

See this post for more details...
http://xdaforums.com/showthread.php?p=75309902



LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5

@marcdw That did not seem to work. I confirmed the file was in the correct location and flashed twice with same result. Eventually the system reboots itself and then the framework services FC until eventual loop begins. I am torn between loving this ROM on my M8 and hating it here on the Note3 -_-

I tried the rom without GAPPS and it loaded up just fine.
 
Last edited:

marcdw

Senior Member
Sep 24, 2014
5,751
2,894
60
Baldwin Park
@wooleyx64, yeah, whether that tip works is hit or miss. It worked on this phone when I kept getting hit by a flood of FCs after flashing gapps. On another device testing out an Oreo ROM it didn't work. Still got the wizard and crashing apps. Couldn't even bypass the wizard with the four corner tap thing.
A pain in the rear.


LG G3 D851, CyanogenMod 12.1 ROM, Fechda Kernel R7, MultiROM, Tapatalk 4.9.5
 

wooleyx64

New member
Feb 7, 2018
3
1
@wooleyx64, yeah, whether that tip works is hit or miss. It worked on this phone when I kept getting hit by a flood of FCs after flashing gapps. On another device testing out an Oreo ROM it didn't work. Still got the wizard and crashing apps. Couldn't even bypass the wizard with the four corner tap thing.
A pain in the rear.


LG G3 D851, CyanogenMod 12.1 ROM, Fechda Kernel R7, MultiROM, Tapatalk 4.9.5

@marcdw

Of all the troubleshooting...The issue was found to be the Note 3 Flip Cover setting. Apparently the phone case has a magnet which trips the hall sensor to be always on. Taking off the case and then rebooting fixed the issue. Going into settings and turning off Flip cover fixed it for good. This was not my phone so I was unaware of this S-cover feature. Maybe this will help someone else some day.

I cannot believe how many times I flashed RR and GAPPS to this phone and I never thought to take the case off. It is true what they say: "90% of the time it's a physical problem". Granted it was a software setting, but I would not have known about it until I physically removed the phones case and rebooted.

-Wooley
 
  • Like
Reactions: marcdw

ama_211

Member
Jan 12, 2013
17
1
Jeddah
Android 8.x option is missing in Opengapps Apk
 

Attachments

  • Screenshot_20180213-030455.jpg
    Screenshot_20180213-030455.jpg
    171.7 KB · Views: 145
Aug 9, 2014
10
0
Hong Kong
Im using a Zenfone 2 Z00A with RR and official Gapps flashed. However, I don't see trusted face option in smart lock, only body detection, trusted place, trusted device and trusted voice are included. When I direct to root/system/app/FaceLock, there is only lib and no apk is included. Is it normal? Do I have any way to fix it? :confused:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    20151219.zip:
    Code:
    Installation error in /sideload/package.zip
    (Status 255)
    Installation aborted.

    So with that package actually the verification was OK again. But CM recovery has replaced their busybox with a still half-broken 'Toybox' that doesn't like our /usr/bin/ash line and demands /usr/bin/sh
    It is updated in the source and I have forced that a new ARM build will be created coming night, that should resolve this issue for you.
    3
    I have just clean-installed the latest cm12.1 nightly (march 18th) for Moto-G (2015) on my device, followed by the latest 5.1 Aroma package.
    The installation went fine. No errors. After restarting my phone, I keep getting a notification of "com.google.process.gapps has stopped", and I can't really use my phone.
    I tried repeating the process, with and without wiping data/cache/dalvik/system, with and without reinstalling the ROM. Nothing seems to change.
    My log files are here and here.

    I also see the following exception in my logcat:

    Thank you for your help.
    Last night I added dex2oat experimental code that doesn't seem to work nice on all 5.x ROMs. I adjusted it to be 6.0+ only, so please try with tomorrow's build again, probably the problem will be gone. If you need to have it work now, you can use the this keyword: https://github.com/opengapps/openga...es-and-Options#skip-smart-pre-odexing-of-apks
    3
    I use open_gapps-arm-6.0-pico and I have AOSP keyboard FC with gesture typing. This gapps don't have libjni_latinimegoogle.so.
    Are there plans to include a libjni_latinimegoogle.so in the gapps_pico?
    Yes this the plan, but we have to fix some lib-handling in the scripts per android version, which is not implemented yet.

    Aroma 6.0 not working in cm 13 sultanxda rom. Pico works fine. Aroma freezes in "installing"
    Aroma GApps 5.1.1 is not working on my TWRP (osprey). Is this a problem specific to my phone or...?
    Aroma has known issues. We are dependent of the release of a new libaroma of the Aroma developer. We can't fix it ourselves unfortunately. Try to use the non-aroma packages instead.

    Is there a reason why the Google Dialer has been removed from the Stock pacakge? I have a Nexus 6P and I'm not sure how to get it back.
    Google Dialer didn't work on most ROMs, we are still trying to figure out why with some other devs, but for now it is not in the package. If you wipe /system/, flash your ROM and then Open GApps you should be fine!

    Okay, I know this most likely has been asked before. Is it possible to create a gapps package that installs all the gapps possible leaving necessary amount of space to /system partition for Android to operate and install the rest of the apps that didn't fit in the /system to /data partition?

    Or is it possible to resize the /system partition of Nexus 5 to acommodate full stock gapps package? This is a bit iffier solution but eh.
    I just enjoy having a full gapps package that removes all the stock AOSP apps and CM apps that have their equivalent in gapps package. The picking and choosing what to install into /system and what not leaves me weird - now I have to go to play store and download the app and... Dunno.
    Nope, sorry this isn't easily possible. And we rather don't mess with the /data/ partition to prevent damaging any of the user's data. Try to pick a GApps version that matches the size of your system partition, and if you want to replace AOPS with CM apps you can use stock with a gapps-config file or aroma. Apps that don't fit on your system you can install via the Play Store on your data partition instead.

    Please excuse me for this newbie question. Had downloaded the Aroma zip. I just want to install Google Backup Transport as I had installed all others through Gapps Installer.
    When I flash the zip through TWRP recovery, will there be options to choose ? I don't want to flash other google apks. I couldn't find the answer in the whole thread.
    No sorry, that isn't possible. You can't combine Open GApps with any other GApps. So make sure you don't have any GApps installed before flasing Open GApps.
    3
    @MastahF @TKruzze @raulx222 @Rapper_skull @osm0sis
    Hi I use Android One device by google... In stock i was having FaceUnlock
    but after moving to CM i was not able to install it using ANY gapps packge

    so i was looking for whats wrong
    And here is what i found

    After skimming through update-binary and update-script of your and others' gapps packages i observed that it check for android.camera.harware.front.xml for front camera compatibility
    but some devices(like mine) have front camera compatibility mentioned in android.hardware.camera.xml

    So even if there devices are compatible , they will be shown incompatible because of this checking method


    Hope you improve it soon to fix this issue
    i'm attaching my phone's system/etc/permissions zip so that you can have a look at it
    Its from stock and they have mentioned front camera compatibility in android.hardware.camera.xml
    3
    @MastahF @TKruzze @raulx222 @Rapper_skull @osm0sis
    Hi I use Android One device by google... In stock i was having FaceUnlock
    but after moving to CM i was not able to install it using ANY gapps packge

    so i was looking for whats wrong
    And here is what i found

    After skimming through update-binary and update-script of your and others' gapps packages i observed that it check for android.camera.harware.front.xml for front camera compatibility
    but some devices(like mine) have front camera compatibility mentioned in android.hardware.camera.xml

    So even if there devices are compatible , they will be shown incompatible because of this checking method


    Hope you improve it soon to fix this issue
    i'm attaching my phone's system/etc/permissions zip so that you can have a look at it
    Its from stock and they have mentioned front camera compatibility in android.hardware.camera.xml

    Thank you for your input and research!

    I fixed the code and am testing it now. If it works I will commit it and you'll be able to find it in tomorrow's nightly.