yashsingh1/xdaforums huggingface dataset:
[Android Software Development] DECEiFER:
Google Dialer being Removed

Hi,

I'm using Open GApps on my stock-firmwared Nexus 6 in order to remove the excess bloat easily without going in one by one every time I do an update monthly to apply the security patches that Google releases (I can't seem to get the OTA to work as I'm always rooted and unlike in the past when you could, sometimes survive an OTA, that's no longer the case since Lollipop, I've gathered). Since the Nexus 6 is left with 15MB on the system partition on the stock firmware - thank you, Google. It's not enough to work with really and I'm a minimalist anyway so a small package suits my needs and anything else can be installed from the Play Store and go on the data partition. Win-win.

The problem is and this is only happening, I think, on builds within the last month, is that it's removing the dialer files from etc/permissions and framework, but not the apk itself whether I use the "mini" or "stock" package, even though the stock package includes the dialer and the mini does not. Either way, I'm left with no choice but to replace those files manually after flashing Open GApps now, which is a pain. On one attempt it even corrupted the system partition and caused my phone to ask for a password (I use a pattern) to unlock it on boot, which meant I had to flash the system partition again, etc. I must've ****ed with a permission incorrectly or something but managed to get it working after that. Note that I didn't play around with the config file or anything like that.

Is this a known issue already and is there any chance of a fix before next month's security patch? :)

I've attached the log of my most recent flash in case it's needed. Thank you. Besides this hiccup, I've always loved using this set of GApps for its simplicity and pleasantly-designed and informative website to get 'em.
[Android Software Development] Jinghis:
Hi all!

Is it me just, or anyone have problem when I want to play a youtube video the 480, and the 720 fps vids are just blank black screens. I've flashed this great GApps package a couple of times now, but I don't know where is the problem.

the ROM I'm on is Resurrection Remix Marshmallow - Amami, if there is anyone who can help thank you for that ^^.
[Android Software Development] Heathered:
What's about new Google Play Services 8.9.16?
[Android Software Development] MastahF:
Dialer is not part yet of the regular installs yet because it does not work on most devices, but its files are part of the removal/cleanup script... If you use Google dialer please add "DialerGoogle" to a gapps-config (https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options#the-gapps-config-file ) for the moment.

You need to contact your ROM dev about this. It is very probably in the graphics driver. If it is not, than it is inside the YouTube app and you should go to Google. In any situation it cannot be caused by the Open GApps scripts/installer.

That is an N preview and won't work on Marshmallow afaik (and even it would we wouldn't put an alpha-version in the package).
[Android Software Development] gpvecchi:
I confirm that choosing the default dialer makes the Google dialer work on Galxy S2. On this device I still have the issue of aroma not loading saved config...
[Android Software Development] Heathered:
[MENTION=6404745]MastahF[/MENTION] Doesn't know it's from N preview. I install it from APK Mirror on CM13 and after few days haven't any issue...
[Android Software Development] vjtigas:
http://www.apkmirror.com/apk/google...le-app-5-12-30-21-arm-3-android-apk-download/
[Android Software Development] raulx222:
Does it save the selections? But doesn't load them?
[Android Software Development] :
[MENTION=6404745]MastahF[/MENTION] AndroidPolice wrote that the last version of Google contacts is compatible with Lollipop (see its article of 2016/04/13, sorry, I can't post a link). If so, could you include it in your builds for Android 5. Thanks in advance.
[Android Software Development] osiedacz:
Using CM13 nightly on Nexus 9 LTE (flounder LTE), both the stock and aroma installer use the legacy camera instead of current. At first boot, the tablet has to update the app. Any specific info you need to get this on the white list.
[Android Software Development] thisisapoorusernamechoice:
Actually it depends on the three digit variant number appending the apk file name. So far (from what I have seen) one variant of 8.9.16 has surfaced, 438. The 4 indicates it's for android 6.0, the 3 indicates it's for CPU architecture armeabi-v7a, and the 8 indicates it's for 480 dpi.

So (just for the sake of example) it's compatible with my Galaxy S5 running CM 13, but not my Galaxy Tab 4 running CM 13 (right android version and CPU architecture, wrong dpi)
[Android Software Development] vjtigas:
You're talking about Google Play Services, not Google Contacts.

---------- Post added at 12:22 AM ---------- Previous post was at 12:11 AM ----------

http://www.androidpolice.com/2016/0...-to-devices-running-android-5-0-apk-download/

Google Contacts doesn't have different APKs for different DPIs.
[Android Software Development] MastahF:
Yes, done: https://github.com/opengapps/opengapps/commit/c3e5998f16f8ad1df68d5087c58c22e010ecb6aa

Thanks for reminding me. I had spotted the changed sdk (and we had cleaned-up our repo of the sdk23 version), but I had forgotten to enable it for those builds.

I had only added volantis* to the whitelist, assuming that was the N9 productname, but apparently I needed to add flounder* too: https://github.com/opengapps/opengapps/commit/4f85632b3fa0c40958a0522358f0d356c17b7e0e
[Android Software Development] thisisapoorusernamechoice:
Oops you're right I replied to the wrong post, sorry about that, that's my bad

On a completely unrelated note, adding the line "+CMSetupWizard" (minus the quotes obviously) to your gapps-config file solved the FC issue myself and others were having in CM 13 a few pages back. I feel silly for not figuring it out before needing to post
[Android Software Development] gpvecchi:
Yes, I have to check if the files structure is correct, but they are in Open Gapps folder. But when I load choices there are none selected.
[Android Software Development] raulx222:
The issue might be fixed now. Please wait for the build from 18 April and try it. I'm waiting your report.
[Android Software Development] g104:
18th April PICO is missing??
[Android Software Development] brolee93:
Ye why Pico isn't available in android 6.0 version ?
[Android Software Development] MastahF:
Seems GitHub had a hickup again. I let the buildbot re-build and upload the 6.0 pico
[Android Software Development] MastahF:
Google Dialer update+changes

I reconsidered the Dialer-situation again, and implemented these changes for future builds:

DialerFramework and DialerGoogle are now split into 2 separate packages.

DialerFramework is included in pico+ and enables Google Dialer installation from the Play Store. Because this framework is only updated when you update GApps, and it concerns here a core part of the system with many (dangerous) permissions (it can make calls, send SMSes) I urge all ROM developers to make their users aware of the importance of regularly updating their GApps installation(!)

DialerFramework is only installed on whitelisted devices. This are all (and only the) Nexus and Android One devices at the moment. Other devices have many and various issues. But the user can override this using the forcedialer keyword in gapps-config, but won't receive any support.

DialerGoogle is included in stock+ and is only installable if DialerFramework is installed (duh).

You need to set Google Dialer as the default phone application if installed, otherwise your device will reboot if you make or receive a call: https://www.youtube.com/watch?v=BXg7k75sVc8

Source code changes: https://github.com/opengapps/opengapps/commit/cf5a2b32c1baa739600e6131cfe70fee131e986c

Package content changes: https://github.com/opengapps/opengapps/wiki/Package-Comparison/_compare/f7fb445^...f7fb445

Keyword behaviour changes: https://github.com/opengapps/openga...tures-and-Options/_compare/9e9fb05^...9e9fb05

Updated FAQ: https://github.com/opengapps/opengapps/wiki/FAQ/_compare/af3463f^...af3463f
[Android Software Development] TonySuperPony:
Where can I find the white list? Thanks in advance
[Android Software Development] osiedacz:
Camera installed perfectly on the 4/18 version, thank you very much.
[Android Software Development] gpvecchi:
Nope, still the same problem. I checked and the files are correct (settings are saved inside them), but aroma package doesn't load them. I noticed this strange thing, in TWRP file manager, the SDcard folder is empty, but all the files/directories are in emmc folder. It seems that the ZIP writes in the correct place, but reads from the wrong one. Checking in mounts settings, SDcard is correctly thicked. No issues on N5X...
[Android Software Development] raulx222:
[MENTION=4909585]gpvecchi[/MENTION]

Thanks for your report. I might need you help to find a fix. Please send me a PM if you are able to try a test build. Thanks!
[Android Software Development] guhvanoh:
In the very next sentence where you were informed of the whitelist.
[Android Software Development] TonySuperPony:
Haha, sorry ? I see now. So only nexus devices. Thanks
[Android Software Development] vjtigas:
Request: keyword to force installation of nonlegacy Google Camera to devices that aren't whitelisted.
[Android Software Development] MastahF:
Good idea, I added the 'forcenewcamera' keyword:

sourcecode: https://github.com/opengapps/opengapps/commit/8bc67580ea2660eddb44cf719aeee5358bf493bb

doc: https://github.com/opengapps/openga...tures-and-Options/_compare/040c80d^...040c80d
[Android Software Development] MastahF:
I am testing an updated packaging format that should enable us to build 'dynamic' packages in the future too.

Would some people be willing to test either the arm64 or the x86 version, because I don't own these devices myself and report back whether they installed successful on their device?

https://www.dropbox.com/s/l0h3g4phdmka3sz/open_gapps-arm64-6.0-pico-20160419-UNOFFICIAL.zip?dl=0

https://www.dropbox.com/s/vcr2wywuc1o8a1h/open_gapps-x86-6.0-pico-20160419-UNOFFICIAL.zip?dl=0
[Android Software Development] vwnut13:
So this does work? I'll have to try the next time I need to flash.
[Android Software Development] vjtigas:
What is the difference of these dynamic packages to the prebuilt packages available?

Sorry, can't test (no arm64/x86 device).
[Android Software Development] MastahF:
These are not yet dynamic, but they incorporate some structural changes (which are prone to coding errors from my side, that is why I prefer to have it tested before putting it in the regular builds) that marks every app with an architecture.

E.g. that means is that chrome is instead of just "chrome" marked as "chrome-arm" or "chrome-x86" and the installer script installs the best fitting match for the device.

That will allow us in future changes to build a package that can be flashed on any architecture. This could i.e. be useful for e.g. the nano and pico flavours.
[Android Software Development] thisisapoorusernamechoice:
Yes I've flashed several times since adding that line to my gapps-config, with the 14 April, 16 April, and 18 April stock packages and haven't had that FC issue since
[Android Software Development] Sanchezoo:
Will they work on arm64 v8a? I am willing to try them.
[Android Software Development] krasCGQ:
I could test the x86 one. Will get it right away and flash it ASAP.

It should work. Most or nearly all arm64 CPUs are armv8a.
[Android Software Development] krasCGQ:
Yes! It works on my Z00AD. Anyway, for debugging purposes if needed, I attached recovery log and Open GApps logs.
[Android Software Development] Sanchezoo:
Which one is arm64? Do I need to do a clean install of a ROM or can I install this package over an existing gapps package? (The reason I asked is because I downloaded a arm64 gapps package from opengapps and upon install it said that I need gapps for arm64v8a)
[Android Software Development] krasCGQ:
The 1st link. The 2nd one is for x86 devices like mine.

If you have another GApps installed, wipe /system first, install ROM+GApps, clear cache/dalvik, then reboot.
[Android Software Development] Ok_Kaleidoscope5109:
Anyone lose HDR capabilities in the latest Camera update on Nexus 6P?
[Android Software Development] vjtigas:
Not thread related. Can't answer the question as I don't have the device.
[Android Software Development] djha53k:
new built

Hello,

I´m trying to build my own OpenGAPPS...

So far I did this:

mkdir opengapps; cd opengapps
git clone git@github.com:opengapps/opengapps.git
cd opengapps
./download_sources.sh --shallow arch arm
git checkout master

But when I try make something I got following errors :crying:

[djh@server opengapps]$ make arm
make: *** No rule to make target 'arm'. Stop.

[djh@server opengapps]$ make arm pico
make: *** No rule to make target 'arm'. Stop.

And when I try without parameter... I got error for each OpenGAPPS version (this is just for pico, but its loooong list for each version) :(

Generating Open GApps pico package for arm with API level 23...
zipalign is outdated. Install a more recent version from the Android SDK and findable in sh $PATH.
Aborting.

The "zipalign" is up to date, same as SDK... I use BBQ Linux:

[djh@server opengapps]$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/opt/android-host-tools/bin:/opt/android-host-tools/bin:/opt/android-host-tools/bin:/opt/android-sdk/build-tools/23.0.3

Any idea? Thank you. :confused:
[Android Software Development] MastahF:
mkdir opengapps; cd opengapps
git clone git@github.com:opengapps/opengapps.git
cd opengapps
./download_sources.sh --shallow arch arm
git checkout master

that should be ./download_sources.sh --shallow arm

(arch is an example $variable)

[djh@server opengapps]$ make arm
make: *** No rule to make target 'arm'. Stop.

[djh@server opengapps]$ make arm pico
make: *** No rule to make target 'arm'. Stop.

You can't make 'arm', that is described in the README. Use e.g. arm-23 or arm-23-pico (because it needs an android version too)

Generating Open GApps pico package for arm with API level 23...
zipalign is outdated. Install a more recent version from the Android SDK and findable in sh $PATH.
Aborting.

You need to set $PATH for 'sh' (and not for bash) so e.g. in ~/.profile

[djh@server opengapps]$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/opt/android-host-tools/bin:/opt/android-host-tools/bin:/opt/android-host-tools/bin:/opt/android-sdk/build-tools/23.0.3

Also you need to give the path to the binary location, so not to /opt/android-sdk/build-tools/23.0.3 but to /opt/android-sdk/build-tools/23.0.3/bin (or whatever the exact path of aapt is)
[Android Software Development] djalfy:
Hi. I have an issue with the latest gapps build. After i flashed it whenever i try to make a call with the google dialer app i get an instant reboot. My phone is nexus 5 running cm13.0 caf. I tried to delete the app's data but the reboot still occurs.
[Android Software Development] momo00:
It is explained in the FAQ: https://github.com/opengapps/openga...boots-when-i-receive-or-make-a-phone-call-why

Also it was mentioned in [MENTION=6404745]MastahF[/MENTION]'s post. Please search & read before post.
[Android Software Development] djha53k:
I am using the /bin/bash shell, so it depends on the ".bash_profile" and the path is there:

[djh@server ~]$ cat .bash_profile |grep PATH
export PATH=$PATH:/opt/android-host-tools/bin:/opt/android-sdk/build-tools/23.0.3

And binaries are directly in the "/opt/android-sdk/build-tools/23.0.3" folder, there is no bin sub-folder:

[djh@server ~]$ ll /opt/android-sdk/build-tools/23.0.3
-rw-rw-r-- 1 android users 727899 Apr 6 20:10 NOTICE.txt
-rwxrwxr-x 1 android users 1146608 Apr 6 20:10 aapt
-rwxrwxr-x 1 android users 1932780 Apr 6 20:10 aarch64-linux-android-ld
-rwxrwxr-x 1 android users 254032 Apr 6 20:10 aidl
-rwxrwxr-x 1 android users 3570836 Apr 6 20:10 arm-linux-androideabi-ld
-rwxrwxr-x 1 android users 35077 Apr 6 20:10 bcc_compat
-rwxrwxr-x 1 android users 633272 Apr 6 20:10 dexdump
-rwxrwxr-x 1 android users 2577 Apr 6 20:10 dx
-rwxrwxr-x 1 android users 3570836 Apr 6 20:10 i686-linux-android-ld
-rw-rw-r-- 1 android users 9448185 Apr 6 20:10 jack.jar
-rw-rw-r-- 1 android users 3238087 Apr 6 20:10 jill.jar
drwxrwxr-x 2 android users 4096 Apr 6 20:10 lib
-rwxrwxr-x 1 android users 2228528 Apr 6 20:10 llvm-rs-cc
-rwxrwxr-x 1 android users 4340 Apr 6 20:10 mainDexClasses
-rw-rw-r-- 1 android users 885 Apr 6 20:10 mainDexClasses.rules
-rwxrwxr-x 1 android users 1919720 Apr 6 20:10 mipsel-linux-android-ld
drwxrwxr-x 5 android users 4096 Apr 6 20:10 renderscript
-rw-rw-r-- 1 android users 17 Apr 6 20:10 runtime.properties
-rw-rw-r-- 1 android users 39 Apr 6 20:10 source.properties
-rwxrwxr-x 1 android users 1106588 Apr 6 20:10 split-select
-rwxrwxr-x 1 android users 92759 Apr 6 20:10 zipalign

And here is other fodler:

[djh@server ~]$ ll /opt/android-host-tools/bin
-rwxr-xr-x 1 root root 568512 Jan 1 18:02 fastboot
-rwxr-xr-x 1 root root 96824 Jan 1 18:02 img2simg
-rwxr-xr-x 1 root root 84336 Jan 1 18:02 minigzip
-rwxr-xr-x 1 root root 14536 Jan 1 18:02 mkbootfs
-rwxr-xr-x 1 root root 14600 Jan 1 18:02 mkbootimg
-rwxr-xr-x 1 root root 121352 Jan 1 18:02 mkyaffs2image
-rwxr-xr-x 1 root root 96824 Jan 1 18:02 simg2img
-rwxr-xr-x 1 root root 14528 Jan 1 18:02 unpackbootimg
-rwxr-xr-x 1 root root 88448 Jan 1 18:02 zipalign

Aall binaries are in the PATH:

[djh@server ~]$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/tools:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/opt/android-host-tools/bin:/opt/android-sdk/build-tools/23.0.3

So, now what :confused: :(
[Android Software Development] MastahF:
You misunderstand. The scripts are called using a /bin/sh shebang, so it doesn't matter what shell you use or from where you call it. It will always be executed by 'sh' and your bash-profile is NOT included. You need to follow the instructions I gave you.
[Android Software Development] djha53k:
Thank you, but I´m sorry, it is still not clear :(

I don´t think it is this case as all shells are just symlinks to the /bin/bash :angel:

[djh@server ~]$ ll /usr/bin/sh
lrwxrwxrwx 1 root root 4 Nov 23 21:20 /usr/bin/sh -> bash

[djh@server ~]$ ll /bin/sh
lrwxrwxrwx 1 root root 4 Nov 23 21:20 /bin/sh -> bash

There is no bin folder there:

[djh@server ~]$ ll /opt/android-sdk/build-tools/23.0.3/bin
ls: cannot access '/opt/android-sdk/build-tools/23.0.3/bin': No such file or directory

Both binaries are directly in the folder (no sub-folder there):

[djh@server ~]$ ll /opt/android-sdk/build-tools/23.0.3/aapt
-rwxrwxr-x 1 android users 1146608 Apr 6 20:10 /opt/android-sdk/build-tools/23.0.3/aapt

[djh@server ~]$ ll /opt/android-sdk/build-tools/23.0.3/zipalign
-rwxrwxr-x 1 android users 92759 Apr 6 20:10 /opt/android-sdk/build-tools/23.0.3/zipalign

I tried to trick it with:

cp .bash_profile .profile

but the error is still present :crying:
[Android Software Development] MastahF:
Can you check the output of:

which zipalign

and of:

zipalign
[Android Software Development] djha53k:
[djh@server ~]$ which zipalign
/usr/bin/zipalign

[djh@server ~]$ zipalign
zipalign: error while loading shared libraries: libc++.so: cannot open shared object file: No such file or directory

The aapt works OK:

[djh@server ~]$ which aapt
/opt/android-sdk/build-tools/23.0.3/aapt
[djh@server ~]$ aapt
Android Asset Packaging Tool

Usage:
aapt l[ist] [-v] [-a] file.{zip,jar,apk}
List contents of Zip-compatible archive.
.... etc....
[Android Software Development] MastahF:
So you have a 'wrong' zipalign at /usr/bin/ that is frustating all the effort. Most simple and destructive fix:

sudo rm /usr/bin/zipalign
[Android Software Development] djha53k:
Hooray, the install of libc++ fixed the issue:

pacman -S libc++

uncle google helped me :cyclops:

Thank you very much, the previous your helped me fix it :good:

One more question: is it possible to build only "arm pico" version?

[djh@server opengapps]$ make arm pico
make: *** No rule to make target 'arm'. Stop.

Thank you.
[Android Software Development] momo00:
Did you read his whole answer? http://xdaforums.com/showpost.php?p=66456860&postcount=2551

The answer has already literally been given.
[Android Software Development] djha53k:
Yes, you are right, I´m completely blind :rolleyes:

Thank you [MENTION=6404745]MastahF[/MENTION]

I follow the post and here we go :victory:

INFO: Total size uncompressed applications: 258M
WARNING: Can't establish if enough free memory is available: parallel compression mode disabled.
Compressing Package: Core/configupdater-all
Compressing Package: Core/defaultetc-all
Compressing Package: Core/defaultframework-all
Compressing Package: Core/gmscore-arm
Compressing Package: Core/googlebackuptransport-all
Compressing Package: Core/googlecontactssync-all
Compressing Package: Core/googlefeedback-all
Compressing Package: Core/googleonetimeinitializer-all
Compressing Package: Core/googlepartnersetup-all
Compressing Package: Core/gsfcore-all
Compressing Package: Core/gsflogin-all
Compressing Package: Core/setupwizarddefault-all
Compressing Package: Core/setupwizardtablet-all
Compressing Package: Core/vending-all
Compressing Package: GApps/calsync-all
Compressing Package: GApps/dialerframework-all
Compressing Package: GApps/googletts-arm
Compressing Package: GApps/packageinstallergoogle-all
Compressing Package: Optional/swypelibs-arm
INFO: Total size compressed applications: 71M
Packaging and signing /home/djh/opengapps/opengapps/out/open_gapps-arm-6.0-pico-20160420-UNOFFICIAL.zip...
SUCCESS: Built Open GApps variation pico with API 23 level for arm as /home/djh/opengapps/opengapps/out/open_gapps-arm-6.0-pico-20160420-UNOFFICIAL.zip
[Android Software Development] Sanchezoo:
Working on my Idol 3 arm64

It is working great on my idol 3 arm64. My phone now has button sounds for the number pad. Does that come from the gapps?

***UP DATE So the arm64 gapps causes a weird reboot thing. It did it the first time but I thought it was a random glitch. But I installed a second time to be sure and sure enough it did it. What happens is when installing the gapps package the phone blanks out and returns to the twrp boot screen. twrp continues to load and I can do a wipe and restart. The gapps do load though. The only problem I had was in messaging, it would stop working and then restart.
[Android Software Development] Sukarn:
Hi,

As a part of an OTA app for a custom ROM, I've been working on automatic ROM+gapps download before they are both flashed automatically. Of course, the OTA app includes a switch for automatically downloading the latest version of gapps, and lets the user select which gapps type (nano, pico, mini, etc) the user wants. The latest version check and the automatic download, is done directly from github, bypassing opengapps website.

The OpenGapps wiki on hotlinking mentions how to treat hotlinking to opengapps.org but it does not mention anything of the sort I have built as a part of the as-yet-unreleased OTA app, which checks for the latest version directly on github.

I have not found anything barring such automatic downloads, however, I still wanted to ask whether or not this is okay to do.

To recap: Un-released OTA app does automatic gapps download of latest version directly from github, bypassing opengapps.org and I'm not sure whether this is banned behaviour according to opengapps or github.

Where the app gets this info: https://github.com/opengapps/<arch>/releases
[Android Software Development] HeD_pE:
Thanks a lot for the fix mate, I tested today's build and it's now installing properly. Cheers