[RELEASE] Sprint Hobart

See merge request !7

Update launcher icon

See merge request !4

* Call recording is enabled for: Sri Lanka (413) and Costa Rica (712).
* Fixes: Removed newline from Belgium (206) and space from Russia (250).

Change-Id: I4c9ecf41e9fd472b97fff5cd03800414737be87a

Change-Id: I462cc97cbb05ddb9bcd15dc39578b7ababbd2a58

* This change handles call recording within the Dialer. Changes were made
to the template of all of the XML files, and all links were changed to
https, where possible. Quotes of the precedents and/or laws can be found
within each country's XML file. Countries' whose status was not changed
are not explicitly mentioned below, despite any changes to their files.

* Call recording is disabled for: Andorra, Iceland, Indonesia, Monaco,
Switzerland, the United States of America and some of its territories -
Guam, Northern Mariana Islands, Puerto Rico and the United States Virgin Islands.

* Call recording is enabled for: Albania, American Samoa, Argentina, Armenia,
Aruba, Belarus, Bonaire, Bosnia and Herzegovina, Brazil, Canada, Chile,
Croatia, Curaçao, Cyprus, Estonia, Faroe Islands, French Guiana, French Polynesia,
Georgia, Greece, Greenland, Guadeloupe, Hungary, India, Ireland, Israel, Japan,
Kosovo, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Martinique, Mayotte,
Moldova, Montenegro, Morocco, New Caledonia, New Zealand, North Macedonia, Peru,
Russia, Réunion, Saba, Saint Barthélemy, Saint-Martin, Saint-Pierre-et-Miquelon,
Serbia, Singapore, Sint Eustatius, Sint Maarten, Slovakia, Slovenia, South Africa,
South Korea, Turkey, Ukraine and Wallis-et-Futuna.

Change-Id: Iba5b7028d26cac281099f81bf3d5c21e2ee4d1a9

Change-Id: Ie1fda7fbca378735fba527330d4c1326c9b5d579

Change-Id: I4d8e591af2c27c621847974c695db8b06d8c8cd7

In change I9359aaaa44b89f5937cc1a7d9fbd5fe25c71133d the interface
update logic was introduced to reflect the supported audio route
change. However, on devices with call recorder support, this
change has introduced a regression hiding the "More" button from
the CallButtonFragment. This change fixes that regression.
Reported-By: Evgen Stenkin <stenkinevgeniy@gmail.com>
Signed-off-by: Vasyl Gello <vasek.gello@gmail.com>
Verified-By: ShevT <shev_t@mail.ru>
Change-Id: I3b022005dfd0ea7b23ec4c351f65ac07b6604956

The primary call info card was sized after the CallButtonFragment
making the call info displayed small. This patch fixes the sizing

Change-Id: If5dded59960c2d4534d3d7377b6970e17977d33c

Change-Id: I78ce85706ffa6cac7f514548873cb67b94a77dc8

Introduced in CAF commit 1d6722e1

Change-Id: I8f5a520aef0fb196a69ff0db5af80f913592e9d7

Change-Id: Ie5acebffe5e55f5c0eef8fe00551ae2dbd7bcb85

On some devices, there is no earpiece route available, and the speaker
is the default audio output. To make in-call UI correctly operate on
such devices, the following changes are introduced:

* the "earpiece handset" output icon becomes hidden from the list of
  choices in the audio button if no earpiece route is supported

* if device does not support earpiece route but wired headset is
  plugged in, the "earpiece handset" output icon becomes visible
  to reflect the wired headset as an actual call audio output

* the text option of earpiece becomes hidden from choices if the
  device does not support earpiece route

* audio button is shown only if there are more than one route is
  present on the device, otherwise it stays hidden

Test:

* On devices with speaker and earpiece routes present, the audio
  button is visible and acts like a speaker toggle

* On devices with speaker and earpiece routes present and wired
  headset plugged in, the audio button is visible and acts as
  a speaker toggle

* On devices with speaker-only or earpiece-only routes present
  and wired headset plugged in, the audio button is visible and
  acts as a speaker toggle

* On devices with speaker and earpiece routes present and
  Bluetooth headset paired, the audio button is visible and acts
  as a multi-state toggle allowing user to choose Bluetooth
  (by default), speaker or handset earpiece

* On devices with speaker-only or earpiece-only routes present
  and Bluetooth headset paired, the audio button is visible and
  acts as a multi-state toggle allowing user to choose Bluetooth
  (by default) and speaker or handset earpiece

* On devices with speaker-only or earpiece-only routes present,
  the audio button is invisible

Change-Id: I9359aaaa44b89f5937cc1a7d9fbd5fe25c71133d

* In some cases with VVM involved, the phone number seems to be null,
  resulting in a NPE when trying to split it by the regex
* Make sure there is always a valid string involved to prevent the error

BUGBASH-1447, BUGBASH-1242

Change-Id: I88302deeaeb3e085190fdab5fa7d2a8030bceb88

Change-Id: I42addce8ccd88ef067def3fc9a114087b87250ab

Change-Id: I26fc84c57c0c6ba3bc788771a3c7cddf9b644684

Disable lookup by default and add a disclaimer for the feature

Change-Id: If7a181952304dbaee736762bdfd5819eddc5f89b
Signed-off-by: Joey <joey@lineageos.org>

Change-Id: Ia6e9eb0efe747e65b0027b745c4ff9a0395887cf

Change-Id: I61da50a8828130bce2682bd78d7483c2f067dab7

Change-Id: I866ba34e310980122bc65b9d30df7d23e5fccad0

Change-Id: I52cc93d84168832089969c8fad253ce1d4ec9f03

If the provider is disabled or missing, trying to resolve
content://com.android.blockednumber/ will result in an
IllegalArgumentException. Don't allow to block numbers if the
provider is missing, or else the Dialer app will crash upon
opening the preferences.

BUGBASH-1260

Change-Id: Icdc97336f1c6779b3a659624dc124a62311f5052

* Thanks to Andrey (anm), Zoran (totalyfake666) and
  Kristoffer Grundström (Umeaboy) for finding

Change-Id: I1a823241e60cf30f9f6f0f625c349ac49babdc97

* Boolean values don't belong to a strings-file, move it accordingly
* A small newline-issue made a question mark appear out-of-place
* Remove unused string - just increases translation efforts unneccessarily
* Fix some upper/lower cases
* Some past tense issue

This commit also re-applies

InCallUI: Improve more CAF strings
by Michael Bestas <mkbestas@lineageos.org>

InCallUI: Use framework yes/no strings
by Michael Bestas <mkbestas@lineageos.org>

Change-Id: Ie1fc64ddf9281819e94e57af20ece102a4cea4f2

Change-Id: Ic0c5125d357c02778c73af88e2b989f7dbc91ea8

Change-Id: I65d370e2afe9cc7f1540cd966d2787843c21a079

Change-Id: I44ed5c0337c0e17419838e2656576a42d49c6591

* Squash of the following:

Revert "dialer: Remove proprietary SmartDial extension"

This reverts commit 31eaffee.

Change-Id: I893b37b58731f8823ead441d09ec3c45f5b68da6

Russian T9 for Dialer

Change-Id: Ib99ff7b9ef5184db0450fe1bc8a6de79eb7efe24

Dialer: Add Greek T9 support

Change-Id: I006745075cbb83b23a6bda170032d146d9bc5aea

Hebrew T9 for Dialer

Please check it.
The implimentaion is built on the "Russian T9 for dialer".
Also added support for English but in Israel.

Change-Id: I58bfbdf053aff94e446d54f2649070a7cebd488b

Add Korean smart dial map

Change-Id: I93b8efa9093fce4f125e6ebe5b02b5fd581cd01a

Dialer: Refactor SmartDial for additional languages

Adds Chinese support and improved Korean support.

p4: Refactor for transliterating the displayName.

Change-Id: Id3175c6f4eda4962be9d25bd43c24a834c3c5ff1

Read option for t9 search input locale and refresh smart dial db when locale changes

Change-Id: I3cd942741310f16678ed9eb675bbba2cbc72d5e8

Add setting for t9 search input locale

Change-Id: I410b4e20afa85302a9ef3174c2f219e33b1b7987

Return match positions to enable highlighting for CN smart dial

Change-Id: I9255c582708c2fbfe22e7a2bf3ad971da692e2a9

Dialer: Fix T9 for Hebrew

Change-Id: I1c8be92acc1fc29b557eb7cda0d910cf036f3aea

Move smart dialer initialization to onStart().

The SmartDialCursorLoader expects the SmartDialPrefix map to be
initialized when it's created. As
- the loader is initialized in SmartDialSearchFragment's onStart and
- the fragment's onStart is called asynchronously after the activity's
  onStart and
- the map initialization happens in
  SmartDialPrefix.initializeNanpSettings() and
- the above method is currently called in the activity's onResume()

we have a race condition between the activity's onResume() and the
fragment's onStart() (at least when processing a dial intent, which is
what causes the dialpad fragment to be immediately shown).

Fix that race condition by moving the initialization into the activity's
onStart() and running it before calling the super method to ensure it
happens before fragments are started.

JIRA:NIGHTLIES-760
Change-Id: I9767cbba3b177fdd5b1de86914cb1e40d20835ab

Ensure the smart dial name matcher is initialized in onStart().

Otherwise SmartDialPrefix.getMap() might not be initialized yet.

JIRA: NIGHTLIES-1279
Change-Id: If3aca2809faf0c1f379518096a76f17d357fb8e2

Add Ukrainian T9 symbol map

Pretty close to Russian, but with a few differences

Ref CYNGNOS-2188

Change-Id: I29b2cf54fd61ec259e8a01bcedef548ec2fe91cc

Dialer: nuke proprietary smartsearch library references

We really should not use this.

Change-Id: I51395e475a0d9de2b31493d16ac08df72f2d996f

Feijao: empty string is not a valid locale

Empty string is not a valid locale. Setting the default locale
to english (en).

Change-Id: I7bc524dbb4aa65d31f1bb33fa5e8fadf4770fbaf
Issue-Id: FEIJ-306, CD-620

Dialer: use actually supported layouts for SmartDial

Change-Id: I7aafab71c6f8d904292bb82796ab39dc84e88253

Change-Id: I53674f3445ad4a39fdae76cd1afc4d8d27241b36

Change-Id: I0e2f49bf5595c00ba3cbabc0fefbd1df7bd3e3e6

Change-Id: I993f130e68543cf49d92b7f4a6553900e9f0f7e4

REGRESSION-915

Change-Id: I06d6387043d356e901c500812d1948c8d43e232f