yashsingh1/xdaforums huggingface dataset:
[Android Software Development] retired_mnbooze:
I agree with Spasillium's comments and would like to amplify his statement on keeping this project moving forward. He has almost single handedly kept this moving forward since Nougat. Thanks man!

[MENTION=4122877]curiousrom[/MENTION] Should I assume you are a ROM developer by your handle and your vast knowledge of how dialer interacts with android? If so, Open GApps has Open right there in the name. Take note of Spasillim's example. Fork the code make some improvements and submit the PR (pull request not press release).

We are not a large team, we do not have a marketing department, we are not paid. We do this because we love android and want to give back to the ecosystem that we took from freely for a long time.

Thanks in advance for your help!
[Android Software Development] SpasilliumNexus:
To answer this:

"$zip_folder/.gapps-config"
"$zip_folder/.gapps-config-$device_name"
"$zip_folder/.gapps-config-$device_name.txt"
"$zip_folder/.gapps-config.txt"
"$zip_folder/gapps-config-$device_name.txt"
"$zip_folder/gapps-config.txt"

* zip_folder refers to placing the config file in the same location of the zip on the device. Obviously this won't work for sideloading.

"/data/.gapps-config"
"/data/.gapps-config-$device_name"
"/data/.gapps-config-$device_name.txt"
"/data/.gapps-config.txt"
"/data/gapps-config-$device_name.txt"
"/data/gapps-config.txt"
"/persist/.gapps-config"
"/persist/.gapps-config-$device_name"
"/persist/.gapps-config-$device_name.txt"
"/persist/.gapps-config.txt"
"/persist/gapps-config-$device_name.txt"
"/persist/gapps-config.txt"
"/sdcard/Open-GApps/.gapps-config"
"/sdcard/Open-GApps/.gapps-config-$device_name"
"/sdcard/Open-GApps/.gapps-config-$device_name.txt"
"/sdcard/Open-GApps/.gapps-config.txt"
"/sdcard/Open-GApps/gapps-config-$device_name.txt"
"/sdcard/Open-GApps/gapps-config.txt"
"/tmp/install/.gapps-config"
"/tmp/install/.gapps-config-$device_name"
"/tmp/install/.gapps-config-$device_name.txt"
"/tmp/install/.gapps-config.txt"
"/tmp/install/gapps-config-$device_name.txt"
"/tmp/install/gapps-config.txt"

I'll submit a pull for adding support for placement of a config at the root of /sdcard, without requiring it to be in a subfolder on /sdcard later today.
[Android Software Development] curiousrom:
Re: Emergency Calls Problem - Open GApps PR Disaster!

Sorry but I am not a developer otherwise I would try to fix it instead of posting about it.

You can check my posting history on XDA, I am a user support kind of guy & proud of my contributions to the community: https://xdaforums.com/member.php?u=4122877

I know that the Open GApps project is entirely supported by unpaid volunteers & I am really grateful for it.

The point I am trying to make is that the broken emergency calls is a life threatening problem and should be put on the front burner.

All hands on deck as this is unsolved since several months & the Open GApps project is getting hammered for it.

I am talking about posts like this one by respected XDA community contributor [MENTION=7978913]fitittome[/MENTION]:

If the team can't find a solution to fix the installer script that removes the stock dialer by default in the Open GApps Packages Mini, Full, Stock or Super then get some external help.

Ask for help in XDA, the LineageOS subreddit, stackoverflow, stackexchange, etc.

***
[Android Software Development] SpasilliumNexus:
Anyway, dirty hack being tested once it finishes building to see if stock dialer stays by default...
[Android Software Development] curiousrom:
Re: Emergency Calls Problem - Open GApps - Possible Fix?

Thanks! :good: :cool:

If it helps & you PM me some download links I could test on these 2 devices & post or PM Open GApps logs + any other logs you would like: logcat, etc.. I would prefer the Mini package but any other is fine too.

I can also make authorized 911 emergency test calls here in Costa Rica, w/ & w/o SIM.

My daily driver: Galaxy S5 SM-G900M (klteub) running S5 klte LineageOS beta unofficial LineageOS 16.0 klte build 2018-11-21 (made by haggertk the S5 klte family LineageOS maintainer & one of the directors of the LOS project) + Open GApps Pico 9.0 + Magisk v17.3 and TWRP 3.2.3-0. No custom kernel or any other system modifications.

Galaxy S3 i9300 running 100% stock Official Lineage 14.1 (currently build 2018-11-17) + Open Gapps ARM Pico 8.1 + Lineage ARM su add-on for root and TWRP 3.2.3-0. No custom kernel, Magisk, Substratum or system modifications of any kind.

***
[Android Software Development] SpasilliumNexus:
No need. I've personally tested an emergency call myself, as much as I dislike wasting their time, but told them exactly what I was calling for. It even works when Google Dialer is set to default.

The stock Dialer stays by default, whether or not Google Dialer the user chooses to install Google Dialer. If he/she wants to remove the stock Dialer, they can use (Dialer) in the config or manually remove it, and accept any consequences doing it.

Anyway, here's 2 builds with Dialer kept by default, among other changes listed here.

open_gapps-arm-9.0-mini-20181126-UNOFFICIAL.zip

open_gapps-arm64-9.0-mini-20181126-UNOFFICIAL.zip
[Android Software Development] Ultraboss:
Hi there,

I've notice since the nov 5th, that there is no more Android 8.0 stock package complied...

Is it because of the bug that make GooglePlayServices to disappear after install OpenGAPPS then reboot ??
[Android Software Development] FReaX908:
Here in Germany we have different numbers than 911 but just in case... If I flash Google dialer as a system app and keep the stock dialer, I just set Google dialer as default. Is it ok to flash Dialer Framework (as far as I know it's necessary for the Google Dialer)? Is it possible to disable stock dialer or just leave it? (Using stock open gapps + config.txt) Thank you all for clearing this up:svetius:
[Android Software Development] curiousrom:
Re: Emergency Calls Problem - Unofficial Open GApps Mini Test

I'm not sure I understand because I ran a test install of your open_gapps-arm-9.0-mini-20181126-UNOFFICIAL.zip using gapps-config.txt with test enable & looking in the open_gapps_log.txt it does not want to remove the stock dialer but it also does not install the Google Dialer which should be included in the Mini package, right?

Remove Stock/AOSP Dialer | false[NO_DialerGoogle]

Ignore Google Dialer | true[NoRemove]

Install | dialerframework

I am attaching all the logs including Recovery log.

Tested on: Galaxy S5 SM-G900M (klteub) running S5 klte LineageOS beta unofficial LineageOS 16.0 klte build 2018-11-21 (made by haggertk the S5 klte family LineageOS maintainer & one of the directors of the LOS project) + Open GApps Pico 9.0 + Magisk v17.3 and TWRP 3.2.3-0. No custom kernel or any other system modifications.

***

Edit: The Package Comparison page says that Mini includes "Google Phone¹² DialerGoogle" but the Mini Package description page does not mention it.

What gives? :confused:

Edit 2: There is no Google Phone in the Full Package description page aso. Just the Dialer Framework.

So did you guys decided to remove Google Phone and the users who want it will have to download it from Play Store? If so that's OK with me if it solves the emergency calls fail problem.

Or is the Package Comparison page that is out of date?

***
[Android Software Development] SpasilliumNexus:
Leave the stock dialer alone. Hide it if the launcher supports it. Do not disable it. Otherwise, broken emergency calls due to it being disabled is at the fault of the user now.

Google Phone was never in mini. Always been Stock+. Mini being marked for having it is my error. Now fixed.

Edit: Someone else has been making changes to the wiki, reflecting what's in each package, with me just making the change to stock, removing the notice of Google Phone removing Stock/AOSP Dialer
[Android Software Development] curiousrom:
Re: Emergency Calls Problem - Unofficial Open GApps Mini Test

What a waste of time. :)

But you did not reply to the other question: There is no Google Phone in the Full Package page but your edited Package Comparison page says that Full includes "Google Phone² DialerGoogle".

It also says Stock & not "Stock+".

When will either Full w/ Google Dialer or Stock or Stock+ w/ Google Dialer with the fix be available for testing?

Edit: I see build 27 November 2018 in the Download page. Is that it?

Thanks for your time. :good:

***
[Android Software Development] SpasilliumNexus:
I've also just said that I've edited the page to not have it for full. Again, my error, which I've also mentioned. If you don't see the change, you need to refresh the page.

....Stock+ as in Stock or greater, just like it says Android 6.0+, 7.0+, whatever on the Wiki.

Fix will be in the next build whenever it is available.
[Android Software Development] Dims_Camper:
Using 27th November arm64 pie aroma package, the google app installed is 8.55.5.21.arm64 but i got update of the arm version, updating from play store gives an error (ofc duh) does updating gapps package will fix the issue?
[Android Software Development] curiousrom:
Emergency Calls Problem - Open GApps Stock Removes Stock Dialer

I'm sorry to report that I ran a test install of open_gapps-arm-9.0-stock-20181128.zip using gapps-config.txt with test enabled in the same root of ext. sdcard & looking in the open_gapps_log.txt which I attached to this post:

Remove Stock/AOSP Dialer | true[default]

Ignore Google Dialer | false[DialerGoogle]

Remove | dialerstock

Install | dialergoogle

So the problem described in Emergency Calls Problem - Open GApps PR Disaster! is still present. :(

***

Tested on: Galaxy S5 SM-G900M (klteub) running S5 klte LineageOS beta unofficial LineageOS 16.0 klte build 2018-11-21 (made by haggertk the S5 klte family LineageOS maintainer & one of the directors of the LOS project) + Open GApps Pico 9.0 + Magisk v17.3 and TWRP 3.2.3-0. No custom kernel or any other system modifications.
[Android Software Development] SpasilliumNexus:
Look at the commit made: https://github.com/opengapps/opengapps/commit/0392c9cb249ce0584e5144143f6a9500941bed72

Look at this specific line: https://github.com/opengapps/openga...d72#diff-4b4d756dd3b2a232970b47588e486eddR388

That one line prevents Phone from being removed. Again, I did this on a LIVE install, with no TEST keyword, and it DOES NOT remove it. It removes other entries found (FineOSDialer and OPInCallUI) ONLY.

Edit: Even looking in your gapps-remove_revised.txt inside your open_gapps_debug_logs_Stock_Test_2018-11-28.tar.gz shows that priv-app/Dialer is not in the removal list...
[Android Software Development] curiousrom:
Re: Emergency Calls Problem - Open GApps Stock Removes Stock Dialer?

Are you saying that the Test feature described in the wiki's Advanced Features and Options is not reliable? :confused:

Why did you not say anything about it in your reply my post above Unofficial Open GApps Mini Test?

Edit: - [MENTION=5083335]SpasilliumNexus[/MENTION] Could you please attach your open_apps_log.txt to your reply?

***

BTW in that Advanced Features and Options page > Include or Exclude GApps > Include > # Mini+ > DialerGoogle # Install Google Phone (Android 6.0+). (screenshot)

But you said in a post above that only packages Stock+ (Stock, Super & Aroma) include the Google Dialer.

***
[Android Software Development] SpasilliumNexus:
Holy ****, I have never come across someone so annoying on this forum until now.

To everyone else, the stock AOSP Dialer won't be removed by default anymore IN ANY PACKAGE CONTAINING GOOGLE PHONE. The main issue brought up in these last posts before it got derailed into other garbage.

I have more important things to do in my life than sit here and go back and forth with someone throwing semantics and whataboutisms. If the wiki is outdated somewhere, fix it. That part is incredibly simple to do.

And with this post, I'm dropping it.
[Android Software Development] holavilla:
i dont agreed that asking fix for dangerous emergency call fail is anoying@ :confused:
[Android Software Development] runekock:
[MENTION=5083335]SpasilliumNexus[/MENTION]

You have done great work on Open GApps, and I for one am grateful.

Unfortunately, annoying users kind of come with the territory.

Actually, I don't think [MENTION=4122877]curiousrom[/MENTION] intended to be annoying, it's just that he failed to think about how the posts read from your side of the table. He insisted far too much on the facts as he sees them, but was actually trying to be helpful (though he failed...).
[Android Software Development] curiousrom:
Open GApps Emergency Calls Fix & Manual Removal of Stock Dialer Warning? Aroma?

Sorry if the package installation Test simulation feature does not reflect your fix.

I had no way of knowing that.

Anyway thanks for your time & fixing the failed emergency call issue! :good:

I would still like to see your open_apps_log.txt though.

I see that the Advanced Features and Options - gapps-config file page was edited and this warning was removed:

And replaced with:

Now that the packages Stock & Super do not remove the stock dialer anymore there is still the possibility of users deleting it & having the emergency calls fail. So maybe it would be a good idea to warn the users with a big visible box about not doing it either through gapps-config file or by deleting it manually.

Of note: Stock & Super packages users will not get back their deleted stock dialer just by installing the new fixed packages. They must also reflash their firmwares + the Open GApps packages one after the other then reboot. Or update their firmwares.

One last important question: can users using the Aroma package select the removal of the stock dialer or is it disabled by default as it should be? Or at least with a visible warning in that panel? :confused:

***

"...He insisted far too much on the facts as he sees them"- If you go back 2 pages & look at my posts about the emergency call issue, all the facts reported are supported by quotes, links & logs.

"...though he failed.." - Well if only 1 life is saved because pushing on the issue got the fix done then it was all worth the trouble of researching the subject, posting about it, downloading packages that I don't need to run some tests, etc.

To give you a concrete example: some Open GApps & Google Phone with stock dialer removed users reported fails when trying to make an emergency call while most said that the call would go through but the screen turned black - no UI.

In Costa Rica where I live when dialing 911 you get an answering system that says if it's really an emergency press 1. How can you do that without a dial pad? :confused:

The reason I pointed to errors in the Package Comparison, Advanced Features and Options & other pages is that I often post about Open GApps & refer to these pages & posts comments based on the content of these pages & want to make sure the info is 100% correct.

For example this post in the Android 9.0 Pie For Galaxy S5 thread where I wrote mistakenly that "packages Mini & bigger includes the Google Phone" based on the wrong info @ the time in the Package Comparison page:
[Android Software Development] Sptz:
I flashed GApps (28th November release) but there's a 30th of November now. Do I need to reflash or are they just updated normally from the Playstore?

Thanks
[Android Software Development] FReaX908:
You get the updates through the Playstore.
[Android Software Development] stibich:
the Google Photos app is only in English. My phone is in Portuguese.
[Android Software Development] demonoidmaster:
Just use pico and let the playstore update apps (YouTube, calendar, contacts, calculator, etc)

Theres no reason to use anything else in my opinion lol
[Android Software Development] lfchow:
Distance unit in Google maps

I have installed opengapps 9.0 (28/11/2018) with Bliss rom pie on Shamu. I am in Australia so we use "km" as distance unit. When distance unit in Automatic, I noticed when I search for a place, the distance still in miles. It's not a big deal as I can still set it manually to "km". Otherwise, good work on opengapps pie.
[Android Software Development] asraf115.ak:
I installed aroma gapps

Though i have selected google dialer

The system dialer isnt uninstalled
[Android Software Development] Iye Vice:
I use OG Nano, as they include trusted face/voice match. I also tried to replace stock dialer with Google, but it remains. But who cares - stock dialer has auto call recording, which is more important than emergency call, 'cause we all will die anyway.
[Android Software Development] curiousrom:
Do Not Remove the Stock AOSP Dialer or Risk Emergency Calls Fail!

Do NOT remove or disable the stock Dialer otherwise emergency calls may fail!

You can safely set the Google Dialer as the default Phone app if you keep the stock Phone app enabled.

And that's why this was done recently & on purpose:

Edit: See this issue for more details on the Open GApps GitHub: Keep the stock dialer by default, instead of as configuration due to emergency calls not functioning properly sometimes. #672

***
[Android Software Development] VincentJoshuaET:
With gapps-config, Open GApps can remove those.
[Android Software Development] SpasilliumNexus:
lmao.
[Android Software Development] ipdev:
Just to clarify for those who are not familiar with the use.

Removal of ROM installed stock apps only works if they are predefined in OpenGApps.

If you go back a few months(ok maybe more), Lineage switched their default browser to Jelly. So OpenGApps would not remove it unless you specified it.

######### Add-on removal of Stock apps
(Jelly) # Remove Lineage Browser “Jelly”
(privacy-browser) # Privacy Browser

Note:

A gapps-config file is actually very simple to use.

How the OpenGApps installer handles it is a little more complicated.
[Android Software Development] mattgyver:
Thread cleaned. Please keep it civil, and watch your language...

XDA Forum Rules
[Android Software Development] demonoidmaster:
hence why I'm thinking my stock rom apps (calendar for example is called com.simplemobiletools.calendar.pro, uses Via browser, simolemobiletools gallery pro, phonograph etc) aren't predefined in the gapps installer config in the pico zip... Oh but of course like Planetera said it's obviously my fault that these apps don't get removed or atleast removed and installed as user apps upon the next reboot (like magisk manager app does upon boot after flashing it, it installs it's apk if it's not installed)

Using Mokee for the Mi 6X (converted my A2 Jasmine into the 6X Wayne)
[Android Software Development] marcdw:
Yeah, that makes sense given that Simple Mobile Tools are third party and not part of any ROM proper. I remember one ROM that used things like K9 Mail and other tools for its defaults. So OpenGApps didn't remove them on install.

Moto G5S Plus XT1806, BootleggersROM-Shishufied, microG (NoGapps), MultiROM, XDA Legacy
[Android Software Development] EthanITA:
I was trying to install SkyDragon on my OnePlus 3T. Checking to install Google Markup or Google Tags (probably Tags, but i'm not sure which one was causing that issue) will fail to install gapps, here is the log:
[Android Software Development] MastahF:
There is no 64 bit support for 4.4, Google has never released any working 64 bit apps for such old Android, because it is not suitable for multi-architecture libs.
[Android Software Development] Sandivisi:
But can i used opengapps arm32 to my phone?
[Android Software Development] MastahF:
You could try, they might work for you, especially because my suspicion is that even though your phone has a 64 bit processor, if it is still on 4.4 it very probably is not a 64 bit OS.
[Android Software Development] brunodu91:
Hi

07 15 release is fix it ?

Thx
[Android Software Development] MastahF:
No, 0716, but it still building&uploading, because GitHub has a lot of connectivity issues, and when an upload fails, it blocks the whole building process.
[Android Software Development] MastahF:
No, it is not completely intended. Of course some space is reserved as buffer (hint: you can use the keyword 'smallbuffer' if you want a smaller buffer to be applied, but be careful with that, because ROM updates could more easily hurt you). But that there is such a large difference of 12MiB calculated free versus 25MiB actually free is weird. It might be partially explained by differences in the filesystem handling small files. Or maybe some rounding errors are occuring.

If someone would be willing to investigate and could provide me with more details about where the differences occur, we could maybe fix/improve this.

At the moment I am more focused on launching our 'stable' series (hopefully tomorrow) and setting out the new goals for further improvements of the project.
[Android Software Development] NZgeek:
Thanks for that super useful post. It has everything the devs need to fix the issue. </sarcasm>

Seriously, that's like calling up a mechanic and saying: "My car doesn't work. How do I fix it?" Where are you even supposed to start?

You need to provide the following information:

- What device you're using.

- Which recovery you're using, including the version number.

- A description of what you saw, including any error messages. If the phone reboots or turns off, say what it was doing just before the crash/reboot.

- The GApps install log, which should get put in the same folder as the zip.

- Your recovery log, which is probably in /cache/recovery.

This info at least gives the developers some idea where to start looking.
[Android Software Development] Bubino75:
Hi,

whit your pagkage open_gapps-arm-4.4-micro-20150714 and open_gapps-arm-4.4-micro-20150705 I have problem with AOSP keyboard -> fC... so the phone is unasable

With open_gapps-arm-4.4-micro-20150615 all work fine

My test are made with fresh install and some version of rom

Could you verify this?

Thanks in advance
[Android Software Development] :
Please provide the information above
[Android Software Development] TorchaOne:
Hi, I am not sure but with couple latest stock builds for arm (oneplus), my google calendar updates from exchange like 10-20 times per event. Googles own works ok. I am using gmail for exchange mails.
[Android Software Development] MastahF:
From today (17th of July) on, all releases will be published in their respective architecture's repository instead of the common 'opengapps' repository.

"Why?" you might ask: because this allows us to have several different 'latest' releases, which is beneficial to every update being a 'real' update, e.g. if a package is updated for the x86 platform it does not have to trigger a new build for arm platforms. Thus the 'latest release date' per architecture can deviate. Of course, if a package that is cross-platform gets an update, all platforms will receive a new build.

This will also allow for the introduction of different pushbullet channels per platform, so that you can choose to only track the platforms you're interested in. These channels will be published in the near-future, ..

On opengapps.org the download mechanism is still the same, but you will see that the 'latest release' text will be updated if you choose a different platform.

Also, any major development will not be done in the 'master' branch anymore, since we now consider the current code stable and reliable, which we don't want to accidentally break anymore. So any daily update you will see without any special announcements can always be considered 'safe to install' and will only contain updated google packages. Testing builds will be published via a seperate channel.

To see which exact versions are used for release we also launched a 'version information' mechanism. On the GitHub releases page you can download a text file that has all the information about the packages used (full packagename, architecture, sdk level, dpi, versionname and versionnumber). These text files can also be downloaded via opengapps.org via the Version Information button. I hope this gives greater insight for those whom are not acquinted with GitHub's file-tree and commit logs.

Also, for those who want to stay on top of the lastest contributions done by packagers realtime, I would like to highlight our twitter account at https://twitter.com/opengapps that broadcasts all GitHub's commit messages.