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

Search This thread
By:
Advanced…
ipdev

ipdev

Recognized Contributor
Feb 14, 2016
2,546
1
5,159
Google Nexus 10
Nexus 7 (2013)
danwood76 said:
SetupWizard crashing on ARM devices is caused by google moving the TimeZoneFinder class in libcore from libcore.util.TimeZoneFinder to libcore.timezone.TimeZoneFinder.

I have created a wrapper for this class in our common device tree, not sure if this is the best way to do it but it works:
https://review.lineageos.org/c/LineageOS/android_device_samsung_universal7580-common/+/267020

@Nezorflame is this something you could integrate in OpenGapps?

Regards,
Danny
Click to expand...
Click to collapse

Thank you. :)

I asked followmsi to take a look and he added it to flo/deb (Nexus 7 2013 WiFi/LTE).
He had the same question ..is it possible to integrate this stuff into Gapps instead of device tree ?

I am happy to confirm your wrapper works on the 2013 Nexus 7 with unofficial lineage 17.1.

Nezorflame said:
Builds have been updated again, this time initial tests showed that mounting finally works :)

<SNIP>

Known issues left:
- Photos still FC, I have a possible solution for that but will be testing it further in the next build
- Trying to use Pixel Launcher with Q gesture system will result in FC, for now avoid using them together
- [ARM-only] SetupWizard seems to be crashing for some due to Google changing some stuff (more details here - https://xdaforums.com/sho...ostcount=6439)

Test them out and let me know!
Click to expand...
Click to collapse

Nexus 7 (2013) unofficial lineage 17.1 now includes @danwood76 wrapper (arm patch).
I used the nano and stock packages for testing.

open_gapps-arm-10.0-nano-20200116-BETA
Android SetupWizard - Skipped most, set time and date, toggled off most of the google crap.

open_gapps-arm-10.0-stock-20200116-BETA
Using a gapps-config file, Setup WiFi, Google account, time/date was automatically corrected since WiFi was connected. Took a little long at checking for updates but, all worked.

Notes:
I install via adb sideload.
Pushed gapps-config.txt to /sdcard/Open-GApps/.gapps-config when using stock.
Attached my gapps-config file for reference.
(Use the Include option and the file is a little outdated but, the tag options still seem valid.)

Cheers all. :cowboy:
 

Attachments

  • gapps-config.txt
    9.9 KB · Views: 31
Last edited:
  • Like
Reactions: trancinguy, Nezorflame, curiousrom and 2 others
curiousrom

curiousrom

Recognized Contributor
Jun 4, 2011
2,172
4,101
Costa Rica
www.reddit.com
Samsung Galaxy S III I9300
Samsung Galaxy Tab 2
Re: Open GApps Android 10 Beta - Build 2020-01-16 Report

ipdev said:
...I am happy to confirm your wrapper works on the 2013 Nexus 7 with lineage 17.1.

Nexus 7 (2013) lineage 17.1 now includes @danwood76 wrapper (arm patch)… open_gapps-arm-10.0-nano-20200116-BETA...
Click to expand...
Click to collapse

Thanks for the report. :good::cool:

Official LineageOS 17.1 is not launched yet so to avoid creating confusion for users it's important to mention that it's for an unofficial version & only for that device. Including a link to it's thread would be a good thing IMO.

ipdev said:
...I install via adb sideload.
Pushed gapps-config.txt to /sdcard/Open-GApps/.gapps-config when using stock...
Click to expand...
Click to collapse

Could you confirm what you wrote in your interesting Pull request - Copy logs to sdcard/ when using sideload #794:

When using adb sideload, log files are not saved.
(/sideload is RO)
If you use a gapps-config file, the logs will be saved in the same directory as the config file...
Click to expand...
Click to collapse

If so, could you edit your post above & attach the open_gapps_log.txt to it please?
***
 
Nezorflame

Nezorflame

Senior Member
Sep 7, 2009
990
2,752
Yerevan
github.com
Google Nexus 5
Google Pixel 6
  • Like
Reactions: Bonito77, mauam, trancinguy and 1 other person
B

bersem

Senior Member
Jan 19, 2014
366
165
@Nezorflame can u take a look into a log from TWRP and another file please. A big major issue on SM-G900F S5 with opengapps. Afer fresh clean install LOS 17 ROM + opengapps successfully boot into sytem. Initial-Setup works fine.

After reboot or shutdown it doesnt boot anymore. Only stucks on bootlogo...

2nd file: https://xdaforums.com/showpost.php?p=81511449&postcount=403

Thanks in advance !

Regards !


Edit: I made a logcat from the system @Nezorflame Next step a logcat from boot / after rebooting. Maybe someone will do it or i will in next days
 

Attachments

  • open_gapps_log.txt
    3.6 KB · Views: 11
  • logcat_First_Boot.rar
    88.5 KB · Views: 8
Last edited:
  • Like
Reactions: curiousrom
Nezorflame

Nezorflame

Senior Member
Sep 7, 2009
990
2,752
Yerevan
github.com
Google Nexus 5
Google Pixel 6
bersem said:
@Nezorflame can u take a look into a log from TWRP and another file please. A big major issue on SM-G900F S5 with opengapps. Afer fresh clean install LOS 17 ROM + opengapps successfully boot into sytem. Initial-Setup works fine.

After reboot or shutdown it doesnt boot anymore. Only stucks on bootlogo...

2nd file: https://xdaforums.com/showpost.php?p=81511449&postcount=403

Thanks in advance !

Regards !


Edit: I made a logcat from the system @Nezorflame Next step a logcat from boot / after rebooting. Maybe someone will do it or i will in next days
Click to expand...
Click to collapse

Is the second logcat the one which was taken on the 2nd boot? Since those files are different I'm not sure I understand which one is which.
Or are those two of the same first boot when everything was fine, and you are unable to take the one where you're stuck on bootlogo?
 
  • Like
Reactions: mauam and bersem
B

bersem

Senior Member
Jan 19, 2014
366
165
Nezorflame said:
Is the second logcat the one which was taken on the 2nd boot? Since those files are different I'm not sure I understand which one is which.
Or are those two of the same first boot when everything was fine, and you are unable to take the one where you're stuck on bootlogo?
Click to expand...
Click to collapse

The first one is from TWRP and the second after first boot taken from System. If no one will make a log after reboot / from failled boot after i will make it in next days.

1. open_gapps_debug_logs.tar.gz and open_gapps_log.txt are from TWRP after flashing
2. logcat_First_Boot.txt taken from System

Thanks in advance !

Best regards !
 
Last edited:
  • Like
Reactions: Nezorflame
Nezorflame

Nezorflame

Senior Member
Sep 7, 2009
990
2,752
Yerevan
github.com
Google Nexus 5
Google Pixel 6
Congratulations everyone, the Q PR has been merged along with the APK repos to the master branch!
Release notes: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-10.x

What does this mean?

Basically that means that the Android 10 builds can now considered to be stable for daily usage.
But, as you know, there are still some issues left:
- [ARM-only] SetupWizard seems to be crashing for some due to Google changing some stuff (more details here: https://xdaforums.com/showpost.php?p=81478751&postcount=6439)
- Trying to use Pixel Launcher with Q gesture system will result in FC
- Photos still FC

This is why we're going to only enable the pico and nano variants in the daily builds since they're stable and work for the most of people.

What's next?

Currently, the plan is following:
1) fix the current issues left and add support for more package variants one by one
2) add the official stable and test build flavors, with difference being:
- test builds being built on daily basis (like we do already) and tested by people in a separate XDA thread and in the Telegram chat (might consider creating Slack/Discord group for that as well in the future);
- stable ones are pushed every week (by promoting the latest working test to the stable once testers confirm that).

Stay tuned for the more updates soon!
 
  • Like
Reactions: Lorenzopapi99, Wolfcity, ps_minky16 and 18 others
z3DD3r

z3DD3r

Senior Member
Feb 9, 2016
313
1,559
Minsk
Google Nexus 5
OnePlus 9R
  • Like
Reactions: Crescendo Xenomorph, ipdev, Nezorflame and 1 other person
G

gordonthegopher

Senior Member
Jun 14, 2012
326
175
andreoide said:
Flashing Arm 22 Jan cause bootloop on kccat6 Samsung S5 lineeage22 Jan release.
Same lineage 22 Jan with gapps Arm Jan 17 no problem.
Click to expand...
Click to collapse

Same for me with open_gapps-arm64-9.0-nano-20200123 on Xiaomi A1 (tissot) lineage-16.0-20200122-nightly-tissot-signed build. Bootloop saying I need to factory reset.

Also used open_gapps-arm64-9.0-nano-20200117 instead and it booted fine.
 
  • Like
Reactions: andreoide
You must log in or register to reply here.

Similar threads

Deltadroid
  • Poll
[GAPPS][4.4.4][5/6/7/8/9.x.x] Delta Gapps With Modular Addons (All DPI)
Replies
4K
Views
2M
C
CyberBabay
osm0sis
  • Locked
[GAPPS][5.1.x] [CLOSED] Up-to-Date GOOGLE APPS (TK GApps) [2015-10-04]
Replies
26
Views
2M
osm0sis
osm0sis
Chainfire
[Android 2.1+][03.10.2011][v3.2] Chainfire3D [ROOT][OpenGL ES 2.0+]
Replies
3K
Views
3M
rignfool
rignfool
jajb
[GAPPS][2015-04-04] Google Apps Minimal Edition for Android 5.0.x & 5.1.x
Replies
1K
Views
1M
thiago_727
thiago_727
nathanchance
[GAPPS] [7.1.2] [ARM/ARM64] [July 25th] Beans GApps
Replies
838
Views
923K
mAnN14
mAnN14

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 4
    A
    AnonVendetta
    G A S T said:
    Is there anything new to say?
    OpenGApps is still pretty dead atm, which is very sad...
    Click to expand...
    Click to collapse
    I think it's safe to assume that OpenGApps is dead, it's well beyond the point of simply being temporarily on hold. The devs havent posted in many months, not even to say that it's just on hiatus and will return in the future. And besides that, the last OpenGApps releases are for Android 11, we are now on Android 14, and 15 is coming soon. Even if it comes back, they will have way too much catching up to do for the project to be manageable. There are a few other GApps providers out there that you can try, I'd move on. OpenGApps always was my fave, but I've managed without them.
    View
    4
    A
    AnonVendetta
    MJPollard said:
    What he said. There are other GApps providers like MindTheGapps and NikGapps (which is the one I use) that have taken up the mantle from OpenGApps. NikGapps, in fact, still has releases going all the way back to Android 9 (Pie), and like OpenGApps, provides packages from "core" to "full" depending on how much GApps you need. MindTheGapps, unfortunately, stops at Android 13, so if you're using 14, you're SOL there.
    Click to expand...
    Click to collapse
    MindTheGApps has Android 14 builds. I'm using it on an A14 LineageOS gsi ROM right now. The only problem with MTG, is that it isnt customizable. The zips are take it or leave it, you're installing all the components in the zip, or not at all. There is only 1 version (all the zips are the same, excluding hardware/Android version-specific details) which is essentially 1 size fits all. But most other GApps providers have customization in that you can choose which parts you do/don't want. But MTG is also very minimal, it just includes the core GApps components and little to no bloat. So it's not a big deal to me. I don't need all the extra stuff, just Play Services/Play Store/calendar and contacts syncing, not much else.

    MTG for Android 14:

    Releases · MindTheGapps/14.0.0-arm64

    Contribute to MindTheGapps/14.0.0-arm64...
    github.com github.com
    View
    2
    MJPollard
    MJPollard
    G A S T said:
    Is there anything new to say?
    OpenGApps is still pretty dead atm, which is very sad...
    Click to expand...
    Click to collapse

    AnonVendetta said:
    I think it's safe to assume that OpenGApps is dead, it's well beyond the point of simply being temporarily on hold. The devs havent posted in many months, not even to say that it's just on hiatus and will return in the future. And besides that, the last OpenGApps releases are for Android 11, we are now on Android 14, and 15 is coming soon. Even if it comes back, they will have way too much catching up to do for the project to be manageable. There are a few other GApps providers out there that you can try, I'd move on. OpenGApps always was my fave, but I've managed without them.
    Click to expand...
    Click to collapse

    What he said. There are other GApps providers like MindTheGapps and NikGapps (which is the one I use) that have taken up the mantle from OpenGApps. NikGapps, in fact, still has releases going all the way back to Android 9 (Pie), and like OpenGApps, provides packages from "core" to "full" depending on how much GApps you need. MindTheGapps, unfortunately, stops at Android 13, so if you're using 14, you're SOL there.
    View
    1
    G
    G A S T
    Is there anything new to say?
    OpenGApps is still pretty dead atm, which is very sad...
    View
  • 837
    M
    MastahF
    ​
    Questions? Use Q&A!
    Please read the FAQ before reporting any bugs or errors!
    If you post in the main thread not having read the FAQ or error message itself, not included a debug log when reporting a malfuction or reporting a Force Closure without a logcat, your post will be ignored by the developers!
    Not because we are evil, but because the same questions keep popping up over and over again and too often we get a "X doesn't work, plz fix" without any clue what is happening. We don't have telepathic connection to your device and all the time unnecessarily wasted on this can't be spend on development of Open GApps itself.

    The Latest builds of Open GApps for Android can easily be downloaded from the:


    I work on this project for FREE and putting in a lot of hours into it. While not mandatory, donations encourage me to continue to further pursue this project and I'd deeply appreciate them, if you feel generous.
    Donate to The Open GApps Project

    Are you a ROM developer and want to hotlink to the latest Open GApps package? Then check this wiki entry for details.
    Please don't publicly mirror the prebuilt packages without explicit consent of @MastahF, to ensure that users will always be directed to the very latest version and the source code of the project.


    About The Open GApps Project
    Open GApps is a Google Apps package completely developed by writing buildscripts which allow for the automated creation of new up-to-date packages automatically.
    The development process is completely open-source (GPLv3) and the goal is to have multiple contributors involved, to secure and reinforce the sustainability of Open GApps development.
    Builds are generated every (European) night automatically (if there are any changes) and uploaded to GitHub.

    Official AROMA Open GApps package is developed in collaboration with long-time LP-AROMA-developer @raulx222 and has a dedicated XDA thread
    For any questions about the AROMA installer development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.

    Official Open GApps For Stock support is developed in collaboration with @Rapper_skull and has a dedicated XDA thread
    For any questions about the GApps for Stock development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.

    The x86 package branch of the package is focused on Zenfone support and is maintained by @deadman96385 of the famous Zenfone GApps packages and has its own topic for x86 related questions

    For those that cook their own ROM, an AOSP-build mechanism for Open GApps has been developed by @blystad and can be found at GitHub, remember that you should not bundle any pre-packaged Google Apps with any ROMs you want to distribute further though.

    To gather all the various APKs that are necessary for the packages our master of the APK Universe @MNBooZe has written a tool called APKCrawler that scrape these from the internet, e.g. from APKMirror, it can be found at GitHub too.

    Characteristic of Open GApps:

    • Some highlights about the characteristics of the Open GApps packages:
    • All platforms and and all Android versions are supported
    • DPI-optimized support for all Google packages (unlike other GApps)
    • Frequently updated Google Apps: The pre-built OpenGApps.org packages are updated every (European) night (if there are any updated Google Apps available)
    • Strong compression, allowing for relatively small downloads of even the most complete packages
    • Automatic backup: It is not necessary to re-flash Google Apps when you flash a ROM update. Most ROMs support this (addon.d) function
    • The installer checks your device’s capabilities, like the system partition size. It will notify you, before making any changes, if it finds any problems
    • Several package variations, from a Google Super Package (includes all applications that ever shipped on a Google device), to a Stock package that equals the set of applications found on the most current and complete Nexus, to smaller, minimalist packages and an AROMA package that allows graphically selection of what to install
    • A special ‘for Stock ROM’ installation mode that allows to update the Google Apps on Stock ROMs that conform to the original Google Nexus filesystem structure
    • All package installations can be customized to your individual preferences using our Advanced Features and Options

    The idea behind this project:
    I believe a big source of the problem for many GApps packages to stay up-to-date (or not be forfeited) is the lack of time for developers to do labour-intensive repetive every time a new google-app apk is released.
    That is why I have taken it upto myself to write some Linux shell scripts to automate the packaging and to share these efforts with the world with the goal to create a team to continue this package together under the name Open GApps.

    This project should not be managed by a person, but by a team, so volunteers willing to help are more than welcome!

    Open GApps installer uses open source third-party tools, like busybox and xzdec, compiled by @YashdSaraf; See his busybox thread for more info.
    Open GApps is originally based on the now discontinued PA GApps package of @TKruzze and @osm0sis
    View
    36
    ipdev
    ipdev
    HtHNightwolf said:
    Is it possible to get a test version of the arm version aswell?
    Click to expand...
    Click to collapse
    I run arm/arm64 builds of pico, nano and stock for testing.

    Once they are tested a bit and seem stable, I upload them to MediaFire.
    MediaFire - Link

    Android 12 builds are in the SDK31 folder.
    The 20211218 builds include some permission updates.​

    ---

    Last week I ran SDK32 builds to test on LineageOS.
    LineageOS is merging 12.1.0_r1 into the 19.0 branch instead of creating a 19.1 branch.
    LineageOS Gerrit - Topic 12L - Link
    Edit: I just checked and see they decided to bump up to 19.1 a few days ago.​

    Note:
    Now that Android 12L is official, the release props still show as 12 not 12.1 or 12L.
    The build tag was bumped to 12.1.0 and the boot image is now SDK32 but, the kernel version is still showing as 12.0.0
    The boot image was SDK31 on the 12L preview release.​

    The only way to determine if you are running 12 or 12L is by checking the SDK level.
    SDK31 = Android 12
    SDK32 = Android 12L

    The initial 12L OpenGApps test builds were blind builds and untested.
    I did not have a device/rom to test them on. 🙃

    I few days later I was able to test them on a Pixel C, Lineage 19.0 SDK32 build.
    Since it is a tablet, it utilized the large screen layout of SDK32.​

    The 12L pico and nano builds seem to be safe.

    The 12L stock build had issues with Pixel launcher so, I would suggest not using it for now.
    Unless you are using a gapps config script to customize the install.

    Android 12L (SDK32) test builds are currently on gDrive.
    gDrive - Link


    Everyone is welcome to give them a try.

    Cheers all. :cowboy:

    Edit:
    See additional posts.
    Post # 7,316
    Post # 7,319
    View
    25
    M
    MastahF
    Tomorrow there will be 7.0 builds
    Small update concerning Nougat: everything is almost in place, only HotWord Enrollment is not de-odexable yet.
    So tomorrow there will be 7.0 builds, ready for when the first source and custom ROMs will drop.
    Of course beta-quality because they cannot be tested yet, so be careful.
    There are some minor changes, Google changed their keyboard stuff, so there will be no swypelibs possible anymore.
    Google VR Services is backported to all Android versions (so all the way from 4.4 to 6.0) but ofc not yet known how well it will work.
    Also there are some new 7.0 core apps for Google's Shared Android Services (com.google.android.ext.shared; com.google.android.ext.services)
    Trusted Face's unlock has also some major changes, it seems the pittpatt suff is not necessary anymore for 7.0.

    That's it for now
    View
    25
    M
    MastahF
    For those who hadn't spotted it yet: we can celebrate 1 year of Open GApps :)
    http://opengapps.org/blog/post/2016/05/09/open-gapps-first-anniversary/
    View
    23
    mark manning
    mark manning
    Sorry to drop in but needed to clean up some unnecessary posts that were burying more legitimate posts to the thread.

    Going into someone's thread and demanding they make you something is not only just plain rude, it goes against everything XDA is about. Numerous people suggested a way for you to remove the gapps and you chose to ignore them. The dev isn't going to make an uninstaller just for you. You could also always use root explorer and remove the apps that way too. Anywho, there won't be an uninstaller made so no need to continue this conversation.

    Thread Cleaned
    View

New posts