Age | Commit message (Collapse) | Author |
|
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
|
|
|
|
Bug: 63966743
Test: Build
Change-Id: If9454a90b03a8b907dda7c0f321b423f772effdd
|
|
am: e87be831c7
Change-Id: Iddc32e0db8dfdb79e96e6f58a1f10130cc8e8de5
|
|
am: c18d76ad7d
Change-Id: Ie5788c5d8e3009a067afb0074a54741e31bc7825
|
|
am: e6b49c90a7
Change-Id: Ib81fb054796f5a05e9376d058ab0217c95f0335b
|
|
|
|
Issue:
Buttons flicker when rotating video call screen and full screen mode.
Because initial state of these buttons(components) are "visible".
In full screen mode, these buttons should not be "visible" when video
call screen is rotated.
This patch modifies state of these buttons to "invisible" when video
call screen rotates and isFullscreen()==True to fix the flicker issue.
And, adding "enterFullscreenMode()" for getting correct view-size when
changing layout by videocall-screen regenerated.
Test: manual - Checked that not button flickering issue when video call
screen during full screen mode rotates.
Bug: 111242931
Change-Id: I271ae3fa395fa648a89c8debc5c0a76e1a0a5ecd
|
|
Test: manual
Change-Id: I1774ec71e149cfd798f7fea18c6b9640fea732f1
|
|
am: 179923ebab
Change-Id: Iac07f28759d8c0588831b81a728981ec46aeda5d
|
|
Bug: 126125118
Change-Id: Ida603dafaed0a5817a42de7be74fc5853390dd97
|
|
Bug: 120848293
Change-Id: Ia8f8939c93736c4f8977b2e27452e29aa64a826b
|
|
am: f146187989
Change-Id: Ibc2f1ea4716af52be769c98d2f4da816de0459c8
|
|
am: bea3474a93
Change-Id: I6ac8c5bcb6578a5d2c1b1585d25344b2880640dd
|
|
am: 2a96c802aa
Change-Id: Ifd9e13d150cf3739583f25ef35d802296d966f02
|
|
|
|
This app is frequently overriden by proprietary apps
on shipping devices, so move it to /product.
Also make the app inherit its privapp permission grant.
Bug: 122353713
Test: launch dialer on aosp_blueline
Change-Id: I5ed4dc4360c8a873da153b71a0ec19ff8695e85a
|
|
am: 46b23215b9
Change-Id: I030f9761764e8893c765bb265c0e5c3caef0d863
|
|
am: 01d19af44d
Change-Id: I2ce608dbf38c12f125895f44e5c75b310715981c
|
|
am: 6ed26377fa
Change-Id: I1a86268f618c66231621189b9dbd5dbc1c9a0787
|
|
|
|
Bug: 33166666
Test: gerrit uploader
Change-Id: Ieac6524a39bae720c56adb001a8f90802dcd562d
|
|
MERGE am: f844e0d526 -s ours am: 85306364e7 -s ours
am: 13c19c5b7d -s ours
Change-Id: I1ca672ac88c8e5f38945ff6276b46c20962dfe0e
|
|
MERGE am: f844e0d526 -s ours
am: 85306364e7 -s ours
Change-Id: Ied2e7833bdfcb164312e8565b12794fa4eff248a
|
|
am: f844e0d526 -s ours
Change-Id: Iaa3df41768a54f4061f1061612414129dbbbe99f
|
|
Change-Id: I5af29bcdea90ac9e562f6db0f3ce723b7720667a
|
|
MERGE am: 8607882281 -s ours
am: e0302942be -s ours
Change-Id: I1cca86046fffdc50531f54817e1ab5e52dbfdfe6
|
|
MERGE
am: 8607882281 -s ours
Change-Id: I599c00e3252ed717e178cd10910852db8164e3d3
|
|
Change-Id: Ic73ecc30ed538a63dad4bee5bb7e3cb53dd66e73
|
|
dialing" am: 1634e8180f am: 2331c8ceb9
am: 70e04c1413
Change-Id: I5b979f5b3ecd421f93ad48cce6f12f17e0c70d8b
|
|
dialing" am: 1634e8180f
am: 2331c8ceb9
Change-Id: I01d1e25fdbe8cfbade72757becfc9516f04357ff
|
|
am: 1634e8180f
Change-Id: I64fc4c4e6870e2fe2cb81a2bf5ec96ac74a18792
|
|
|
|
am: ced47b2882
Change-Id: I33c0c30ea22863656ee33fbfcbf6da5096b9827a
|
|
am: 7c40c6d18e
Change-Id: Icd3843c83384df5afdbd542fd4f676e46247dbac
|
|
am: 91952f32ff
Change-Id: I80e6a0fd58a6c55aa44f2256d40d4d979ae469f0
|
|
|
|
Bug: 73108676
Test: none
Change-Id: Ib320232b9605cbd60870c20749b3c98b56e27c4c
|
|
fc082755f3 am: 53c1dcfdad
am: 9a48ff9f9a
Change-Id: I1c7a0518cdff9608144371de0473e5d7dfe19b46
|
|
am: 53c1dcfdad
Change-Id: Icfbc1ac6eb946f8f3f962b67abef34fa74b0e212
|
|
am: fc082755f3
Change-Id: I7bab6b9e6e8d435c69740b1277d13dc6ff52c7be
|
|
am: 0ba853625e
Change-Id: Idd967d06f788bf467467b522e5578aed3f6c39fd
|
|
|
|
Bug: 111437430
Test: make
Change-Id: Ib6658962f5339c33a28e326fb0478d2f4df786bd
|
|
6d597b910a
am: 84860f3d73
Change-Id: I1c3ef8ac20960a2ad571581a20f94ae80c2bf545
|
|
am: 6d597b910a
Change-Id: I5ba235afca003cbf9043ca9eb3bfa5c76d24ffd6
|
|
am: 8fe2b8d569
Change-Id: I2461d3bf410c9b4d9611951a23d60b5eab9fbd02
|
|
am: f518e1eef8
Change-Id: Ia7f6a4125fc34c662fce697741995f5d69a6a3f1
|
|
|
|
Bug: 112104996
Change-Id: I8472e263b260d8e0cd257f02abbdfb349e995ad1
|
|
458dd1cf44
am: f0668c4880
Change-Id: I3e6d5ed477b0fd0e1bf69c314e6fd3eb75d64466
|
|
am: 458dd1cf44
Change-Id: I0e7900d413ab33e9f6ad9d5665b1fa68b701dc20
|
|
am: bba49f0286
Change-Id: If7ef28edfe1427e8ef421634e36ee2040aa84afd
|
|
am: 2789b8de52
Change-Id: Iacdc8756d31f4517f75d8bcab29dbbc36f8df41c
|
|
|
|
[Issue/Cause of defect]
If partner device is rotated during video screen of target device is in
background, and then resumes to foreground, partner image will be shown
with incorrect dimensions.
Because when video screen goes to background, VideoCallPresenter stops
checking CVO(Coordination of Video Orientation) of partner device. And
when video screen is resumed to foreground, there is no logic to update
partner image with latest peer dimensions.
[How to fix]
Even if video screen is in background, CVO(peer dimensions) is notified
to DialerCall. Therefore DialerCall should store the dimensions. And
when video screen resumes to fore, VideoCallPresenter should update the
screen with correct(latest) peer dimensions.
Test: manual - Checked that the partner image is shown with correct
dimensions.
Bug: 111575038
Change-Id: I32ff5407f1222b232b47a35e7083a473be67b468
|
|
"Ongoing video call" is displayed in dialing state on the notification.
But "Dialing" should be displayed.
Wrong order of condition to decide the text causes this issue. It should
have checked dialing state before checking video call state.
To resolve this issue, check the dialing sate at first and then, check
the video call sate.
Bug: 111424745
Test: manual - Checked "Dialing" is displayed if it is dialing state.
Change-Id: Id03909178370df3cc4905699f46e13f9a39aeb45
|
|
Now that we use d8 instead of dx we no longer get the
SimException errors. Instead we get some warnings:
In out/target/common/obj/APPS/Dialer_intermediates/classes-proguard.jar:com/android/incallui/answer/impl/affordance/SwipeButtonHelper.class:
Methods with invalid locals information:
boolean com.android.incallui.answer.impl.affordance.SwipeButtonHelper.onTouchEvent(android.view.MotionEvent)
Re-enabling proguard requires adding some missing transitive
dependencies and disabling warnings for some classes that
are not in Android.
Bug: 37077388
Test: m Dialer
Change-Id: I83e82d6665f02ec22c1d4ca47dc7ccbc564b8c8d
|