Age | Commit message (Collapse) | Author |
|
* The anti-falsing implementation from HumanInteractionClassifier
regularly prevents easy swipe to answer, requiring multiple
attempts until accepted.
Change-Id: Iebad27f9da7bb8fea6fc663dc99ac6c17d94ed5f
(cherry picked from commit 583e42df0f6f02f1a6c05dbdc5559f42e99c8727)
|
|
Change-Id: Ice040bb2785e8e4e3828c6008121520586d269ac
Signed-off-by: Joey <joey@lineageos.org>
|
|
Change-Id: I53b6ee1c70925c50e91270e0b084d777dd8c06f6
Signed-off-by: Joey <joey@lineageos.org>
|
|
* option optimize_for = LITE_RUNTIME is ignored in proto 3+
* Instead we should use the java_lite compiler via the
LOCAL_PROTOC_OPTIMIZE_TYPE flag which defaults to lite in
java projects
Test: m Dialer, no warnings
Change-Id: I552f5895bbe8192a4ae870bb48e5ef6a9e7e8c78
|
|
|
|
35c12ca943 am: 8d3f2dc70e
Change-Id: I73dac7ae2ee37068fd342aefb2426f8b85f56ab1
|
|
Change-Id: I10f10944989f058fdc441d85314f33244522aeed
|
|
Change-Id: I48476d4c4be6780ee316a65a048172d557e4b151
|
|
|
|
The public platform version no longer can be a codename, it is
always the most recently released platform. A new build property
and API provides either the offical version or the current codename
as appropriate. This will avoid breaking apps that look at the
platform version while development is under a codename.
Bug: 143175463
Test: manual
Change-Id: Ic0621234215d4ba79255b985dccdd4ae6c863fc8
Exempt-From-Owner-Approval: Previously approved, no new changes.
|
|
qt-qpr1-dev-plus-aosp-without-vendor (6129114) into stage-aosp-master am: f6b13b7304 am: 9de53ff92f -s ours
am skip reason: subject contains skip directive
Change-Id: Ic48dd840bf18c5acdc57416ea0b938b0e450c426
|
|
stage-aosp-master am: f6b13b7304
Change-Id: Id6a32cf300b7a132ab712c986c4725bfe5e6026d
|
|
stage-aosp-master
Bug: 146167222
Change-Id: I44c4fcf7b96d13ecdbcce4f79517f18a38c9726c
|
|
5fce345b14 -s ours
am skip reason: Change-Id Ib6822436bcebc799e7e920f1a5898d107dd619db with SHA-1 fab2f0fddb is in history
Change-Id: Ifd50a5adbcc855db3938f39aebee4e34efa7ccc4
|
|
Change-Id: I4b18b497583bc5d3c455e1088fd56fa5c509c23b
|
|
Currently when a call is recieved there is an option to write a custom
text message in response to the call. This could allow an attacker to
imporsonate the user. With this change devices that have a lock screen
set will require that the pattern/pin/password be entered before a
custom message can be written.
This is a cherry-pick from the Pixel dialer. The original commit can be
found at cl/257702865
Bug: b/137102479
Test: Call phone running the modified dialer and attempt to send a
custom message
Change-Id: Ib6822436bcebc799e7e920f1a5898d107dd619db
Merged-In: Ib6822436bcebc799e7e920f1a5898d107dd619db
|
|
Reason for revert: This causes a boot issue on Taimen (b/144480969). It wasn't caught by TreeHugger due to Taimen tests being disabled due to a different lab outage (b/144350336).
Change-Id: Ib9fb23e378034fe73373030e0865c6bac99d4f37
|
|
The public platform version no longer can be a codename, it is
always the most recently released platform. A new build property
and API provides either the offical version or the current codename
as appropriate. This will avoid breaking apps that look at the
platform version while development is under a codename.
Bug: 143175463
Test: manual
Change-Id: Ic8fe4defb609dee24f53358dc7b37e3590482b27
|
|
qt-qpr1-dev-plus-aosp-without-vendor@5915889 into stage-aosp-master am: 80a6f0558b
am: f2dd2154aa -s ours
am skip reason: subject contains skip directive
Change-Id: I8ef5867da89e6c2a81071a8c5492a20a2e56504a
|
|
stage-aosp-master
am: 80a6f0558b
Change-Id: Ibf2f68e3b99ed7b5c48a3185991ece7a07f02a6b
|
|
stage-aosp-master
Bug: 142003500
Change-Id: I881e2a3f4fbabb8bb5ca3959a22748508ce23f58
|
|
Use Theme.AppCompat.Light to fix IllegalStateException for
PostCallActivity extending AppCompatActivity.
Test: am start -n com.android.dialer/.postcall.PostCallActivity
Change-Id: Ica815d43cd8dae73fbc8ec948dd701a1455d1704
Signed-off-by: Taesu Lee <taesu82.lee@samsung.com>
|
|
|
|
Currently when a call is recieved there is an option to write a custom
text message in response to the call. This could allow an attacker to
imporsonate the user. With this change devices that have a lock screen
set will require that the pattern/pin/password be entered before a
custom message can be written.
This is a cherry-pick from the Pixel dialer. The original commit can be
found at cl/257702865
Bug: b/137102479
Test: Call phone running the modified dialer and attempt to send a
custom message
Change-Id: Ib6822436bcebc799e7e920f1a5898d107dd619db
|
|
stage-aosp-master am: c25d314f21 -s ours am: 519cf9138d -s ours
am: 5d734dc3e5 -s ours
am skip reason: change_id Ib82af17b8aaceab8357f6ba4280e9ec4d8eb4772 with SHA1 b6ad196f34 is in history
Change-Id: I935da6ca26163b2bbc6db32aaa8e4903a9f945fa
|
|
stage-aosp-master am: c25d314f21 -s ours
am: 519cf9138d -s ours
am skip reason: change_id Ib82af17b8aaceab8357f6ba4280e9ec4d8eb4772 with SHA1 b6ad196f34 is in history
Change-Id: I963922b5192333f6ea0599177cebf5f0e768f479
|
|
stage-aosp-master
am: c25d314f21 -s ours
am skip reason: change_id Ib82af17b8aaceab8357f6ba4280e9ec4d8eb4772 with SHA1 b6ad196f34 is in history
Change-Id: I143c0b1dd28ba679bd9917b22a18cd8bef3e34a2
|
|
No content change.
Bug: 135460123
Change-Id: I4ce8eb798889a62fb84d337d52b47526e7a6ba49
Merged-In: Ib82af17b8aaceab8357f6ba4280e9ec4d8eb4772
|
|
42aa89c0b1 -s ours am: c118fcc13a am: 4740356d31
am: 180bdfd37d -s ours
am skip reason: subject contains skip directive
Change-Id: Iff4721847dffa6ab9079399188395859e433c655
|
|
42aa89c0b1 -s ours am: c118fcc13a
am: 4740356d31
Change-Id: Iae122a09191bbdb0004197bc26e57efdb5418d67
|
|
42aa89c0b1 -s ours
am: c118fcc13a
Change-Id: I931790f36b6d0ab56072c60b072b3218d77635c0
|
|
am: 42aa89c0b1 -s ours
am skip reason: subject contains skip directive
Change-Id: I9e44e02c6a19c089e0ed9f2932198ac6530115e3
|
|
|
|
Bug: 139893257
Change-Id: Ib82af17b8aaceab8357f6ba4280e9ec4d8eb4772
|
|
am: 340e0d8847
Change-Id: I33f9c04e9acb96d68c80604ab946e12fe8fd4746
|
|
am: e9382b76b0
Change-Id: I43580a36f1fb52d9a96e6fc322dbe19221ad52b3
|
|
am: c57dd6e8be
Change-Id: Ifffc2ffc8562e55680bc43a46f1bf512dc16b12e
|
|
am: d3af7434a5
Change-Id: I79b2e735932374cc4978754a7615486e1a8c5a00
|
|
|
|
across many languages." am: 8910fde7dd am: 8f9e253e97 am: d0f720b917
am: 67f0311a14
Change-Id: Ie6a29fc3595b3a417c823b03d6bf20597264c8fd
|
|
across many languages." am: 8910fde7dd am: 8f9e253e97
am: d0f720b917
Change-Id: I6045e2a0793df21c5b3e5f0342393810da844c92
|
|
across many languages." am: 8910fde7dd
am: 8f9e253e97
Change-Id: I5c1b8b1d0e1060cc6393b119cd4addb1ba3de0cc
|
|
across many languages."
am: 8910fde7dd
Change-Id: Icb3e2fa4d4188d48c48e796db1d13e553c2f9a65
|
|
We've fixed the improperly formated resource strings, so no longer
need this flag.
Bug: 135615364
Test: TreeHugger
Change-Id: I0d546f73311f066dabeaf599f358a35fb130f71b
|
|
across many languages."
|
|
languages.
Bug: 135615364
Test: manual - Did a "make -j40" and verified that there are no warnings in strings.xml.
Change-Id: I5b835af079832c8f38bd582113559b830efedaef
|
|
(5699924) into stage-aosp-master am: 10074ae13c
am: 983e4e2861 -s ours
am skip reason: subject contains skip directive
Change-Id: I3267e64a00892e251b8dc4a181792ab056b54128
|
|
stage-aosp-master
am: 10074ae13c
Change-Id: I54562890277077d952df4ef24f0372bc00c43e5a
|
|
stage-aosp-master
Bug: 134405016
Change-Id: Ieed3a8162dfa04d26cb39eeb7e46c1c9e65e40e0
|
|
37030b0a5c am: 43b2886312
am: eb291a8fe6
Change-Id: I427c5376d22b6de281b670398016c421551734d2
|
|
am: 43b2886312
Change-Id: Icaa306eda1f7f47ba7ce32e9d83842bea266c30d
|
|
am: 37030b0a5c
Change-Id: If6ca22cb45462bb934e2195e3a213359d9c09e99
|
|
am: 058ddde95e
Change-Id: Id38ac73d9292150fce115186c8a4316e7a8c9d67
|
|
|
|
This module produces warnings that are treated as errors if --legacy
is not passed. --legacy is no longer being passed by default, so
add it here.
Bug: 135615364
Test: m java
Change-Id: I4db9606206597a58b2a6864ac5ef6d944bb292b4
|
|
am: 3a2e2153b7
am: af62f8f6a3
Change-Id: Idd638bb1763d6914dc4d21b94d5d8e829b38fafe
|
|
am: 3a2e2153b7
Change-Id: I8d14a5174f84c8fc2700e6bd9d69e0b57405d3bf
|
|
am: c87917f39b
Change-Id: Ib3098fa330aab409abfed08f9a28580c1d5ebb22
|
|
am: cca2453024
Change-Id: Ie88f806428ee174acecdfd1c724ea830e100af63
|
|
|
|
This is inteneded to be a list of directories (from the root of the
source dir), not a list of relative aidl files from the
packages/apps/Dialer directory. Since this isn't doing anything useful
right now, just remove it.
Test: treehugger
Change-Id: Ib99296e5dbeaeec92a7568bb8b0b5cfc1154974e
|
|
side. am: e9f21732d5
am: a409c6b1d5
Change-Id: Ib551eb250dbe33566f9a783995da04449fa5a157
|
|
am: e9f21732d5
Change-Id: I96cb7d15d0b35282fe8132189342031865ddeb22
|
|
1.Protect Device Identifiers: Starting in Android Q, apps must have the READ_PRIVILEGED_PHONE_STATE privileged permission in order to access the device's non-resettable identifiers
IMEI and serial is used for the *#06# dialog. OEMs needs this to run factory tests. Perhaps it is something that should be moved to telephony, but as the current state dialer is showing it.
2.Limit pre-installed app network permission:Preinstalled apps that want to access restricted network needs to declare the CONNECTIVITY_USE_RESTRICTED_NETWORKS permission.
Restricted network is used for VVM access.
3.Notification fullscreen intent attribution, Developers need to add a uses-permission tag for android.permission.USE_FULL_SCREEN_INTENT to their manifest
Full screen intent is used for incoming call notification
Bug: 132081872 132080738 132114409
Test: Compile and load build
Change-Id: Iec458cef1ff0c5a4180b438b8ba1a5159bdd8e92
|
|
890dcce1a5 am: fc10e63786
am: efe0fce79f
Change-Id: Iab022c32c517563ad2956bacceb22f320a2f6ac8
|
|
call" am: ebd9bf21e5 am: 0821635baf
am: 534ce67669
Change-Id: Ib3966f8532045d22e19f7cec9d2d207ea1924ca7
|
|
video" am: 9cd154587c am: ddc9143616
am: 02f02dca41
Change-Id: I94cd8a07ac50179b71ab6ec646d8a42955d3d9c5
|
|
holding" am: c1c93761a3 am: 12a51def3c
am: 8e9d052913
Change-Id: Ibe2491faa719e91668cccbdf72a9806d048ca24b
|
|
890dcce1a5
am: fc10e63786
Change-Id: I0d5a7576d0f1e6d2aee25db615a2459827127be1
|
|
am: 91bf209306 am: ea194aec1e
am: 96026df419
Change-Id: I97e5f8f3dacac16b4a1ae6e5140af486a011372b
|
|
call" am: ebd9bf21e5
am: 0821635baf
Change-Id: Ie604c8547fbdf8f140b133f0f9920dea4fba1cb1
|
|
am: 890dcce1a5
Change-Id: I5312fe5725cf8c7055f34fdda1149e940b535c38
|
|
am: ebd9bf21e5
Change-Id: I6f507a36bcd655350ed2558a27665cf07eb9c4d5
|
|
33cc4999be am: 2ec69519ac
am: 91c705de19
Change-Id: I44e2684c301deed8687b69aa4b492bc8766fcc89
|
|
|
|
|
|
video" am: 9cd154587c
am: ddc9143616
Change-Id: I3f30ea8f624d7768a1759dc0294103620b38c77c
|
|
holding" am: c1c93761a3
am: 12a51def3c
Change-Id: Ib9ccc7b8f8d72bab16ba7b19f1b202aa9f4bba45
|
|
am: 91bf209306
am: ea194aec1e
Change-Id: Ic0f4a39ee07ceb42caa41de325c2772400a4427b
|
|
33cc4999be
am: 2ec69519ac
Change-Id: I3f6c2b85aacce4e5b068df65a1b137888e6b4e70
|
|
am: 9cd154587c
Change-Id: Id775e4d330a5bd72e4cc8fc6d7fea93fd0015c10
|
|
am: c1c93761a3
Change-Id: I0833a15a8920489d400beda60acbf921ee226c15
|
|
am: 91bf209306
Change-Id: Ie169f85883f241807f7996712f5dfe7cbc77c02b
|
|
am: 33cc4999be
Change-Id: I1c68639b40fedde8b913c5e510e758b9d5493ea3
|
|
|
|
|
|
|
|
|
|
|
|
AOSP VVM configurations were historically stored in AOSP as VVM
support was part of the platform. This is no longer the case, old
VVM configurations are being removed and individual OEMs will now
be required to provide their own configurations.
Bug: 129867522
Test: make
Change-Id: I299bba40548e557c9802d8241b7168e8c1a3f5e9
|
|
An issue occurs because InCallFragment#onResume() that release the
automatic mute state is not called when switching fragments by adding
call.
To resolve this issue, handle automatic mute state in InCallActivity.
Bug: 110815828
Test: Checked that the mute state is turned OFF when add a video call
during a voice call.
Change-Id: Ided7c58e1148f6ee12bdfeaa813d596a4716c1d6
|
|
am: a3f70e0866
Change-Id: I3da509f7ef46f281ad42e47a8fbc34ba4f2a6270
|
|
am: 5b2ad1476e
Change-Id: I0a27012094e6e55540447d1e5badb843f38a6590
|
|
am: e516d1dc0e
Change-Id: I1e8097b1cfe07100e9284002b431df903dace3a6
|
|
When a user clicks the pause video button, the camera close request and
the session modify request are executed at the same time. However, the
session modify request fails occasionally by a limitation of the Network
side. In that case, the video session is continued with the camera
closed state and a user cannot open the camera again due to pause video
button disabled.
Remove camera close request triggered by the pause video button clicked
because it is handled appropriately according to the result of the
session modify request. Also, enable the pause video button and show
error message to a user if receiving the error result of the session
modify request.
Test: manual
Bug: 69235524
Change-Id: I9a2dde755a6c28edfb0ce962b55ac8a6e907ca97
|
|
Change-Id: Ice9562f96bde9db2da4ecca0ab08e006088c9271
BUG: 129345239
|
|
Change-Id: I34406ee33542edc5790627fbc5222da99001b52f
BUG: 129345239
|
|
am: 7a401d8bab
Change-Id: Id8755704f48e5a736b0f64e1ed602366cb48ba69
|
|
am: d8a4d83a88
Change-Id: I0fa8f789e7af6347ca2caa6a30fb6b6b07ac535d
|
|
am: 381dffd9a9
Change-Id: Ifa40ab4dcce7be62a56160bb7da8691303701d52
|