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

Search This thread

Cyndaquissshhh

Senior Member
Dec 25, 2021
62
24
Hello. When I flash OpenGApps stock variant on my device (ARM, 7.1) the Dialer Framework, Google Phone, and Google Messages don't install even if I include the forcedialer keyword.

The debug archive and log.txt are attached, also included the log as inline code.
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
            ROM Android version | 7.1.2
                   ROM Build ID | lineage_gtexslte-userdebug 7.1.2 NJH47F 0a114bf8b0 dev-keys
          ROM Version increment | 0a114bf8b0
                ROM SDK version | 25
        ROM/Recovery modversion | 14.1-20210611-UNOFFICIAL-gtexslte
                Device Recovery | TWRP 3.3.1-0-9d3ea68b
                    Device Name | gtexslte
                   Device Model | SM-T285
                    Device Type | tablet
                     Device CPU | armeabi-v7a
          Device A/B-partitions | false
             Installer Platform | arm
                   ROM Platform | arm
           Display Density Used | 213
                   Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
              VRMode Compatible | false
       Google Camera Compatible | true
      New Camera API Compatible | false
          Google Pixel Features | false
          Current GApps Version | No GApps Installed
          Google Camera version | Legacy
       Installing GApps Zipfile | /sdcard/open_gapps-arm-7.1-stock-20220205.zip
       Installing GApps Version | 20220205
          Installing GApps Type | stock
                    Config Type | exclude
             Using gapps-config | /sdcard/.gapps-config
      Remove Stock/AOSP Browser | true[default]
       Remove Stock/AOSP Camera | true[default]
       Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
        Remove Stock/AOSP Email | true[default]
      Remove Stock/AOSP Gallery | true[default]
     Remove Stock/AOSP Launcher | true[default]
      Remove Stock/AOSP MMS App | false[NO_Messenger]
     Remove Stock/AOSP Pico TTS | false[NO_GoogleTTS]
         Ignore Google Contacts | false
           Ignore Google Dialer | true[NoRemove]
         Ignore Google Keyboard | false
Ignore Google Package Installer | false
          Ignore Google NFC Tag | false[TagGoogle]
          Ignore Google WebView | false
         Total System Size (KB) | 1828260
         Used System Space (KB) | 572368
        Current Free Space (KB) | 1239508
   Post Install Free Space (KB) | 27060   << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log

NOTE: Stub WebView was installed instead of Google WebView because your device
has already Chrome installed as WebViewProvider. If you still want Google WebView,
you can add 'Override' to your gapps-config to override this redundancy protection.

NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
WARNING: Google Dialer has/will not be installed as requested. Dialer Framework
must be added to the GApps installation if you want to install the
Google Dialer.

# Begin GApps Size Calculations
------------------------------------------------------------------
  TYPE  |         DESCRIPTION        |      SIZE |   TOTAL
        |         Current Free Space |   1239508 | 1239508
 Remove |             Existing GApps | +       0 | 1239508
 Remove |             Obsolete Files | +       0 | 1239508
 Remove |                    browser | +    1256 | 1240764
 Remove |            calculatorstock | +     396 | 1241160
 Remove |              calendarstock | +    2496 | 1243656
 Remove |                camerastock | +    4108 | 1247764
 Remove |                 clockstock | +    3844 | 1251608
 Remove |              cmsetupwizard | +       0 | 1251608
 Remove |              contactsstock | +    6852 | 1258460
 Remove |                      email | +    6792 | 1265252
 Remove |              exchangestock | +    1468 | 1266720
 Remove |           extservicesstock | +      16 | 1266736
 Remove |             extsharedstock | +      12 | 1266748
 Remove |                    gallery | +    7524 | 1274272
 Remove |              keyboardstock | +   48520 | 1322792
 Remove |                   launcher | +    1596 | 1324388
 Remove |          printservicestock | +      36 | 1324424
 Remove |                  provision | +       0 | 1324424
 Remove |        storagemanagerstock | +    3768 | 1328192
 Remove |                   tagstock | +       0 | 1328192
 Remove |            wallpapersstock | +    2624 | 1330816
 Remove |              webviewgoogle | +       0 | 1330816
 Remove |               webviewstock | +   71168 | 1401984
Install |                       Core | -  236920 | 1165064
Install |               batteryusage | -     192 | 1164872
Install |           calculatorgoogle | -    2860 | 1162012
Install |             calendargoogle | -   25884 | 1136128
Install |         cameragooglelegacy | -   31396 | 1104732
Install |                     chrome | -   65208 | 1039524
Install |                clockgoogle | -    8904 | 1030620
Install |             contactsgoogle | -   12984 | 1017636
Install |                      drive | -   84440 |  933196
Install |             exchangegoogle | -     480 |  932716
Install |                      gmail | -  144692 |  788024
Install |                       keep | -   15552 |  772472
Install |             keyboardgoogle | -   61292 |  711180
Install |                       maps | -  142140 |  569040
Install |                     photos | -   80084 |  488956
Install |                 pixelicons | -     336 |  488620
Install |              pixellauncher | -    2296 |  486324
Install |                  playgames | -   19224 |  467100
Install |         printservicegoogle | -      32 |  467068
Install |                     search | -  164448 |  302620
Install |       storagemanagergoogle | -    3708 |  298912
Install |                  taggoogle | -     324 |  298588
Install |                   talkback | -   25184 |  273404
Install |                 wallpapers | -    2368 |  271036
Install |                webviewstub | -     404 |  270632
Install |                    youtube | -  204480 |   66152
Install |                    ytmusic | -   29876 |   36276
        |               Buffer Space | -    9216 |   27060
------------------------------------------------------------------
                        Post Install Free Space |   27060
------------------------------------------------------------------

# End GApps Size Calculations

# Begin User's gapps-config
GearheadStub
GoogleTTS
Speech
Books
Movies
Music
Newsstand
AndroidAuto
Duo
GooglePay
Translate
VRService
# End User's gapps-config

Note: As I said a while ago I included the forcedialer keyword. I only did so while doing a test install (the outcome was the same as now). I didn't include it on the actual installation now, but I did some time ago and the results were the same.
 

Attachments

  • open_gapps_log.txt
    6.3 KB · Views: 24
  • open_gapps_debug_logs.tar.gz
    67.9 KB · Views: 27
  • Like
Reactions: ipdev

Flounderist

Senior Member
Jan 7, 2016
869
423
Cork
Noob question here: are the Gapps controlling in any way the Google System Services updates?
I am using arm64 nano package and my log is flooded with failed system update warnings.
I am using an old (early December) build. The issue started a couple of weeks ago.

Device is a Realme X2Pro (RMX1931) running an unofficial LOS 18.1 build with November security patches.

Any hint?
 

Cyndaquissshhh

Senior Member
Dec 25, 2021
62
24
Noob question here: are the Gapps controlling in any way the Google System Services updates?
I am using arm64 nano package and my log is flooded with failed system update warnings.
I am using an old (early December) build. The issue started a couple of weeks ago.

Device is a Realme X2Pro (RMX1931) running an unofficial LOS 18.1 build with November security patches.

Any hint?
LineageOS cannot take Google Play system updates straight from the Play Store. Maybe your device is trying to get updates and Google's servers reject it
 

ipdev

Recognized Contributor
Feb 14, 2016
1,859
1
3,284
Google Nexus 10
Nexus 7 (2013)
Hello. When I flash OpenGApps stock variant on my device (ARM, 7.1) the Dialer Framework, Google Phone, and Google Messages don't install even if I include the forcedialer keyword.

The debug archive and log.txt are attached, also included the log as inline code.
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
            ROM Android version | 7.1.2
                   ROM Build ID | lineage_gtexslte-userdebug 7.1.2 NJH47F 0a114bf8b0 dev-keys
          ROM Version increment | 0a114bf8b0
                ROM SDK version | 25
        ROM/Recovery modversion | 14.1-20210611-UNOFFICIAL-gtexslte
                Device Recovery | TWRP 3.3.1-0-9d3ea68b
                    Device Name | gtexslte
                   Device Model | SM-T285
                    Device Type | tablet
                     Device CPU | armeabi-v7a
          Device A/B-partitions | false
             Installer Platform | arm
                   ROM Platform | arm
           Display Density Used | 213
                   Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
              VRMode Compatible | false
       Google Camera Compatible | true
      New Camera API Compatible | false
          Google Pixel Features | false
          Current GApps Version | No GApps Installed
          Google Camera version | Legacy
       Installing GApps Zipfile | /sdcard/open_gapps-arm-7.1-stock-20220205.zip
       Installing GApps Version | 20220205
          Installing GApps Type | stock
                    Config Type | exclude
             Using gapps-config | /sdcard/.gapps-config
      Remove Stock/AOSP Browser | true[default]
       Remove Stock/AOSP Camera | true[default]
       Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
        Remove Stock/AOSP Email | true[default]
      Remove Stock/AOSP Gallery | true[default]
     Remove Stock/AOSP Launcher | true[default]
      Remove Stock/AOSP MMS App | false[NO_Messenger]
     Remove Stock/AOSP Pico TTS | false[NO_GoogleTTS]
         Ignore Google Contacts | false
           Ignore Google Dialer | true[NoRemove]
         Ignore Google Keyboard | false
Ignore Google Package Installer | false
          Ignore Google NFC Tag | false[TagGoogle]
          Ignore Google WebView | false
         Total System Size (KB) | 1828260
         Used System Space (KB) | 572368
        Current Free Space (KB) | 1239508
   Post Install Free Space (KB) | 27060   << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log

NOTE: Stub WebView was installed instead of Google WebView because your device
has already Chrome installed as WebViewProvider. If you still want Google WebView,
you can add 'Override' to your gapps-config to override this redundancy protection.

NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
WARNING: Google Dialer has/will not be installed as requested. Dialer Framework
must be added to the GApps installation if you want to install the
Google Dialer.

# Begin GApps Size Calculations
------------------------------------------------------------------
  TYPE  |         DESCRIPTION        |      SIZE |   TOTAL
        |         Current Free Space |   1239508 | 1239508
 Remove |             Existing GApps | +       0 | 1239508
 Remove |             Obsolete Files | +       0 | 1239508
 Remove |                    browser | +    1256 | 1240764
 Remove |            calculatorstock | +     396 | 1241160
 Remove |              calendarstock | +    2496 | 1243656
 Remove |                camerastock | +    4108 | 1247764
 Remove |                 clockstock | +    3844 | 1251608
 Remove |              cmsetupwizard | +       0 | 1251608
 Remove |              contactsstock | +    6852 | 1258460
 Remove |                      email | +    6792 | 1265252
 Remove |              exchangestock | +    1468 | 1266720
 Remove |           extservicesstock | +      16 | 1266736
 Remove |             extsharedstock | +      12 | 1266748
 Remove |                    gallery | +    7524 | 1274272
 Remove |              keyboardstock | +   48520 | 1322792
 Remove |                   launcher | +    1596 | 1324388
 Remove |          printservicestock | +      36 | 1324424
 Remove |                  provision | +       0 | 1324424
 Remove |        storagemanagerstock | +    3768 | 1328192
 Remove |                   tagstock | +       0 | 1328192
 Remove |            wallpapersstock | +    2624 | 1330816
 Remove |              webviewgoogle | +       0 | 1330816
 Remove |               webviewstock | +   71168 | 1401984
Install |                       Core | -  236920 | 1165064
Install |               batteryusage | -     192 | 1164872
Install |           calculatorgoogle | -    2860 | 1162012
Install |             calendargoogle | -   25884 | 1136128
Install |         cameragooglelegacy | -   31396 | 1104732
Install |                     chrome | -   65208 | 1039524
Install |                clockgoogle | -    8904 | 1030620
Install |             contactsgoogle | -   12984 | 1017636
Install |                      drive | -   84440 |  933196
Install |             exchangegoogle | -     480 |  932716
Install |                      gmail | -  144692 |  788024
Install |                       keep | -   15552 |  772472
Install |             keyboardgoogle | -   61292 |  711180
Install |                       maps | -  142140 |  569040
Install |                     photos | -   80084 |  488956
Install |                 pixelicons | -     336 |  488620
Install |              pixellauncher | -    2296 |  486324
Install |                  playgames | -   19224 |  467100
Install |         printservicegoogle | -      32 |  467068
Install |                     search | -  164448 |  302620
Install |       storagemanagergoogle | -    3708 |  298912
Install |                  taggoogle | -     324 |  298588
Install |                   talkback | -   25184 |  273404
Install |                 wallpapers | -    2368 |  271036
Install |                webviewstub | -     404 |  270632
Install |                    youtube | -  204480 |   66152
Install |                    ytmusic | -   29876 |   36276
        |               Buffer Space | -    9216 |   27060
------------------------------------------------------------------
                        Post Install Free Space |   27060
------------------------------------------------------------------

# End GApps Size Calculations

# Begin User's gapps-config
GearheadStub
GoogleTTS
Speech
Books
Movies
Music
Newsstand
AndroidAuto
Duo
GooglePay
Translate
VRService
# End User's gapps-config

Note: As I said a while ago I included the forcedialer keyword. I only did so while doing a test install (the outcome was the same as now). I didn't include it on the actual installation now, but I did some time ago and the results were the same.
Device Type | tablet is the reason.

Currently there is nothing to determine if a tablet is Mobile (LTE) or WiFi only.

A while back I was looking for a prop or prop value to use to determine it.
26.Dec.21 was the newest file date in that test folder.

OpenGApps Installer script [GitHub] Link
Code:
# If $device_type is not a 'phone' make certain we're not installing messenger
if ( contains "$gapps_list" "messenger" ) && [ $device_type != "phone" ]; then
  gapps_list=${gapps_list/messenger} # we'll prevent messenger from being installed since this isn't a phone
fi
If you follow the GitHub link, you can scroll up and down from there and see all the app/services that are not installed on tablets or TV boxes.

Once a way to determine a Mobile/LTE tablet, it could then be changed to.
Code:
# If $device_type is not a 'phone' or 'tablet' with mobile data make certain we're not installing messenger since it is not supported by the device.
if ( contains "$gapps_list" "messenger" ) && [ $device_type != "phone" ] && [ $tablet_type != "mobile" ]; then
  gapps_list=${gapps_list/messenger} # we'll prevent messenger from being installed since this isn't a mobile device.
fi

I haven't had time to work on this more.

If any one has suggestions or wants to look into it. 🙃
OpenGApps Installer script [GitHub] Link
Code:
if echo "$(get_prop "ro.build.characteristics")" | grep -qi "tablet"; then
  device_type=tablet

The rough WIP I was last using.
Code:
if echo "$(get_prop "ro.build.characteristics")" | grep -qi "tablet"; then
  device_type=tablet
  if echo "$(get_prop "ro.telephony")" | grep -qim1; then
    if [ $? -ne 1 ]; then
    tablet_type=mobile
    fi
It has been a while and I do not remember if I ran into an issue using ro.telephony
I did not leave myself a note about it but, I thought I found it set on a WiFi only tablet or an LTE tablet that did not include it. :unsure:

Cheers all. :cowboy:
 
Last edited:

Flounderist

Senior Member
Jan 7, 2016
869
423
Cork
Maybe your device is trying to get updates and Google's servers reject it
I think so. Here is screenshot of the error I get in matlog:
Screenshot_20220209-071327969 (1).jpg

I was wondering if it is a ROM or Gapps issue.
 

Black_Eyes2

Member
Jan 26, 2022
9
2
Redmi k40 pro, twrp 3.6, magisk 24.1, android 11, miui 12
BootLoop with latest opengapps pico build (09/02/2022)
I never had a bootloop before, don't know what to do to fix it
 

Black_Eyes2

Member
Jan 26, 2022
9
2
I'll flash stock rom and keep stock gapps and never use openGapps again ^^
EDIT: flashed it, installed twrp and magisk again. I won't try to redo the opengapps things.
 
Last edited:
  • Haha
Reactions: G A S T

Cyndaquissshhh

Senior Member
Dec 25, 2021
62
24
Device Type | tablet is the reason.

Currently there is nothing to determine if a tablet is Mobile (LTE) or WiFi only.

A while back I was looking for a prop or prop value to use to determine it.
26.Dec.21 was the newest file date in that test folder.

OpenGApps Installer script [GitHub] Link
Code:
# If $device_type is not a 'phone' make certain we're not installing messenger
if ( contains "$gapps_list" "messenger" ) && [ $device_type != "phone" ]; then
  gapps_list=${gapps_list/messenger} # we'll prevent messenger from being installed since this isn't a phone
fi
If you follow the GitHub link, you can scroll up and down from there and see all the app/services that are not installed on tablets or TV boxes.

Once a way to determine a Mobile/LTE tablet, it could then be changed to.
Code:
# If $device_type is not a 'phone' or 'tablet' with mobile data make certain we're not installing messenger since it is not supported by the device.
if ( contains "$gapps_list" "messenger" ) && [ $device_type != "phone" ] && [ $tablet_type != "mobile" ]; then
  gapps_list=${gapps_list/messenger} # we'll prevent messenger from being installed since this isn't a mobile device.
fi

I haven't had time to work on this more.

If any one has suggestions or wants to look into it. 🙃
OpenGApps Installer script [GitHub] Link
Code:
if echo "$(get_prop "ro.build.characteristics")" | grep -qi "tablet"; then
  device_type=tablet

The rough WIP I was last using.
Code:
if echo "$(get_prop "ro.build.characteristics")" | grep -qi "tablet"; then
  device_type=tablet
  if echo "$(get_prop "ro.telephony")" | grep -qim1; then
    if [ $? -ne 1 ]; then
    tablet_type=mobile
    fi
It has been a while and I do not remember if I ran into an issue using ro.telephony
I did not leave myself a note about it but, I thought I found it set on a WiFi only tablet or an LTE tablet that did not include it. :unsure:

Cheers all. :cowboy:
Oh... is there any way to force those apps to install?
 

Homewrecker

Member
Jan 9, 2009
14
0
Anyone else here experiencing issues when trying to pair their Google TV remote?
When I perform a clean install of Lineage OS 18.1 for ATV on my RPI 4, I can pair my remote.
When I flash the opengapps package, the pairing fails every time saying "Could not pair".
There is an issue open on the opengapps github (https://github.com/opengapps/opengapps/issues/915)

Anybody know a workaround for this, because my Android TV is quite useless without a working remote :)

Thanks in advance.
 

Darth Bidder

Senior Member
May 11, 2017
148
23
Xiaomi Redmi 7
I have a Redmi 7 and I installed LOS 18.1.
I'm stuck on the setup wizard, I can't get past the copy data part.
I just reinstalled LOS.
I can't tell if it's LOS latest update or the OpenGAPPS Aroma Feb 5 build.

So I'm stuck with the copying data part where it's just black screen but the back button is just right at the bottom but it doesn't do anything but vibrate the phone.

UPDATE: I got past the setup wizard by going offline but now the problem is I can't login to Google.

I just installed the Nano version of the Feb 2, 2022 build and it's not doing that issue, I guess it's one of the apps I installed that does that or the Aroma version itself is just bugged.
 

Attachments

  • open_gapps_debug_logs.tar.gz
    129.9 KB · Views: 21
  • open_gapps_log.txt
    6.1 KB · Views: 22
Last edited:

Lederhose

Member
Apr 29, 2016
18
1
Is the DialerFramework still included in OpenGapps? The wiki page about the config file mentions it, but as I understand, the Google dialer app has become available for most devices via the Play Store without further measures?
Is the following still an issue, as stated in the OpenGApps blog in 2016?
"It is important to note, that the DialerFramework only receives any security updates if you update your Open GApps installation and not via the Play Store. So make sure to update your Open GApps installation at least once a month, after Google’s monthly security updates are added to the Open GApps repository."

I don't want to use the Google dialer and I don't want the framework - it is not needed for anything else, right?
 

Cyndaquissshhh

Senior Member
Dec 25, 2021
62
24
I have a Redmi 7 and I installed LOS 18.1.
I'm stuck on the setup wizard, I can't get past the copy data part.
I just reinstalled LOS.
I can't tell if it's LOS latest update or the OpenGAPPS Aroma Feb 5 build.

So I'm stuck with the copying data part where it's just black screen but the back button is just right at the bottom but it doesn't do anything but vibrate the phone.

UPDATE: I got past the setup wizard by going offline but now the problem is I can't login to Google.

I just installed the Nano version of the Feb 2, 2022 build and it's not doing that issue, I guess it's one of the apps I installed that does that or the Aroma version itself is just bugged
Aroma is no longer actively developed and might no longer work with newer recoveries. That could be your problem
 
  • Like
Reactions: curiousrom

Nezorflame

Senior Member
Is it possible to get a test version of the arm version aswell?
Hi!

Unfortunately right now I don't have any spare time for opensource (due to the world's situation you're probably aware of).
I hope that I'll resolve my issues during March and will be able to continue in April. Until then, either someone from the community will step up with a custom build, or you could use some other gapps package.
 

ipdev

Recognized Contributor
Feb 14, 2016
1,859
1
3,284
Google Nexus 10
Nexus 7 (2013)
Is it possible to get a test version of the arm version aswell?
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
 
Last edited:

maxed4901

Senior Member
Aug 11, 2013
1,020
390
Male'
www.blogger.com
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:
I tried nano - boots but has setup wizard issues.
Stock - didn't boot. Bootloops. Galaxy note 8

Galaxy s8+ nano doesn't boot.
 
  • Like
Reactions: ipdev

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Dirty flash from 18, had to reset data to boot.
    lineage-19.1-20220729-nightly-vayu-signed.zip
    lineage-19.1-20220729-recovery-vayu.img
    open_gapps-arm64-12.0-nano-20211112-UNOFFICIAL.zip
    Start at post # 7,256.

    ---

    The pico and nano builds should be good.

    Micro and larger are affected by Google wallpaper not working at the moment.
    This will not affect the device or boot, you just can not change the wallpaper.
    Also a few other non-working things in the micro and larger builds.

    ---

    You can always take a look at GitHub and GitLab to see what is happening. 🙃

    OpenGApps
    GitHub - Link
    GitLab - Link

    My forks.
    GitHub - [build] - Link
    GitLab - [all] - Link

    Cheers. :cowboy:
    2
    Does perhaps opengapps include Drivers, so the Stick will probably Work with one of the bigger packages of opengapps?
    You should ask to the ROM developer maybe. It is quite likely that the custom ROM that you are using is missing some libraries that are present on your stock OS instead. Adding Gapps won't help at all.
    1
    damn i cant wipe system in orangefox
  • 836
    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
    32
    Is it possible to get a test version of the arm version aswell?
    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
    25
    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
    25
    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/
    23
    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