Age | Commit message (Collapse) | Author |
|
We cannot use ConfigBindings as full backups happen with a base Application, not the app's custom subclass.
Bug: 63104326
Test: N/A
PiperOrigin-RevId: 161398864
Change-Id: I7f559fe7cfd8bfdd65f49efea943f3f75488d1a6
|
|
This will prevent merged conference having participant with name as following:
1. Restrict and non-restriced
"<phone number or name>"
"Restricted 2"
2. Two restricted number
"Restricted 3"
"Restricted 4"
After the change it will become:
case 1:
"<phone number or name>"
"Restricted"
case 2:
"Restricted 1"
"Restricted 2"
Note: Unfortunately there isn't a way to relate the pre-merge restricted calls to the post-merge restricted calls. So "Restricted 2" is not necessary the one pre-merge. This also means reset is safe here for merge.
Bug: 63315372
Test: manual
PiperOrigin-RevId: 161267675
Change-Id: I2df16b6f9802932c06f0bdd62618c49f4e6e87a8
|
|
The dialer voicemail UI will send the broadcast even below O.
Ideally all receiver for system and external broadcasts should be moved out of impl/ since they will not be disabled with the module, but at this point changes should be kept at minimal.
Bug: 63437675
Test: VoicemailClientReceiverTest
PiperOrigin-RevId: 161264508
Change-Id: I99476bb27ce3da9396f3b7205c98cb847bfff9b7
|
|
The tests now call through the click listener to expand instead of just calling
the expanding method directly. This was done after we had a bug come up inside
the click listener that these tests did not catch.
The bug: Lightbringer.getPackageName can return null, so when using a stub there was an NPE inside the ExpandCollapseListener.
Test: only tests
PiperOrigin-RevId: 161121777
Change-Id: Ie58a4c14a32984c183b6159db2076a96cf46b37e
|
|
This is changed in ag/2484808 to be defined by a constant telecom string. It
will be available to public in O MR. We have to hard code it until then.
(This is a take over of cl/161020406 from wangqi@)
Test: VideoCallNotAvailablePromptTest
PiperOrigin-RevId: 161030078
Change-Id: I0e1d8d98cb1f64b035d9063b28f8ba039c7378e4
|
|
There's a bug in O notification framework that the HUN(heads up notification) will always show when a notification with fullScreenIntent is updated.
Previously NOTIFICATION_INCOMING_CALL_QUIET is only used when the call is already active when the new incoming call is received. NOTIFICATION_INCOMING_CALL_QUIET will post the notification to the ongoing call channel instead of the incoming call, which in theory will have lower importance and the HUN will not show. In this CL, all incoming call notification will become "quiet" if the InCallUi is visible.
Bug: 62458080
Test: StatusBarNotiferTest.java
PiperOrigin-RevId: 161029526
Change-Id: I671105ecfc102beb43e52cf4d91d55a66d31cd0e
|
|
The reason of disconnect cause could be null.
This is regression caused by cl/160563754
Bug: 63156395,63302714
Test: manual
PiperOrigin-RevId: 160987545
Change-Id: I3fd726947601f55d5dc917b11626b64bfc9d0135
|
|
*** Reason for rollback ***
Causes crash on launch (b/63252565)
*** Original change description ***
Fix concurrency issue in constructor.
Before:
sColors served as the branch to initialize all member variables.
Subsequent calls to the constructor after sColors had been initialized,
would result in the use of static members that were not yet initialized.
Now:
We guard each reference with an explicit null check during construct.
Members that require synchronized initialization were put into a small synchronized
method.
This was chosen instead of AtomicReferences, and instead of double check...
***
Bug: 63143138
Test: N/A
PiperOrigin-RevId: 160837963
Change-Id: I2586f7586c8f39182d64c3b28a59886c5ba94789
|
|
Test: cl/160695183
PiperOrigin-RevId: 160697524
Change-Id: I07127554a968d8dc36c02b522b7536438be7fb90
|
|
Before:
sColors served as the branch to initialize all member variables.
Subsequent calls to the constructor after sColors had been initialized,
would result in the use of static members that were not yet initialized.
Now:
We guard each reference with an explicit null check during construct.
Members that require synchronized initialization were put into a small synchronized
method.
This was chosen instead of AtomicReferences, and instead of double checked locking,
because -- although verbose -- we can tolerate a small number of overwrites to
each member variable (they are idempotent within the Application scope), thus avoiding the need for any one thread to wait/acquire a lock, as well as avoiding the need to import the Atomic library (which added no incremental benefit).
It is assumed that the JVM will not garbage collect overwritten references to
member variables that are still in use across instances of LetterTileDrawable.
This shouldn't matter because the references are volatile, anyway.
Initialization-on-demand was not available due to the use of non-static
resources on construct.
Bug: 63143138
Test: No. Old unit tests.
PiperOrigin-RevId: 160696979
Change-Id: Ie17a29e48f91cb3df07d81d29b6428b70fb4408a
|
|
The original code is somehow triggering when the VVM tab is not selected.
Bug: 62517716
Test: VisualVoicemailCallLogFragment is utterly untestable
PiperOrigin-RevId: 160692310
Change-Id: Ia9da8e5aa7dd28f22c46d87dd25ebf6097918a9a
|
|
When telecom disconnect the video call with the code of DisconnectCause.ERROR and the DisconnectCause#getReason() of "IMS_ACCESS_BLOCKED", we should show an error dialog to user indicating that video call is not available and providing a option to make a voice call instead.
Screenshots:
https://screenshot.googleplex.com/YTUGVouoLmj
Bug: 33821263
Test: manual, VideoCallNotAvailablePromptTest
PiperOrigin-RevId: 160563754
Change-Id: Ie2eb735a92c577b5ae5a5e8b7efa2d699fc964bc
|
|
This CL bumps the version name of Dialer from
also bumps the version code from 14***** to 15*****.
go/dialer-v10_1 did not have a version_conf_incrementer_max_version_code set, which let it to share the version code increments between v10.1 and v11. There are version codes in v10.1 which are higher than v11 which will lead to users downgrading when we submit v10.1 to the playstore (http://cl/160476738)
To make sure users are not downgraded from v11 to v10.1 when we push to the play store, I've also set 'version_conf_incrementer_max_version_code' at go/dialer-v10_1
to 1504907.
Test: N/A
PiperOrigin-RevId: 160555974
Change-Id: I4a9e64aa2fe461019e179f544fe959b8389a02cf
|
|
*** Reason for rollback ***
Possible cause of Dialer crash: b/63128348
*** Original change description ***
Add accessibility info for bubble.
***
Bug: 62886248,63128348
Test: N/A
PiperOrigin-RevId: 160531267
Change-Id: Ia9bf5fe29523d6f6280e4ed6fcf9a8d23ee72579
|
|
*** Reason for rollback ***
Causes crash, see b/63127884
*** Original change description ***
All Fragments are now support library Fragments.
Switch a bunch of imports to support library Fragments (and Loaders) instead of framework Fragments (and Loaders). This was needed to use FragmentManager.isStateSaved() instead of manually tracking that state. This should reduce errors around committing after state is saved.
Also adds METADATA presubmit to prevent new usages of framework Fragments or Loaders.
***
Bug: 38241305,63127884
Test: N/A
PiperOrigin-RevId: 160530287
Change-Id: Ie2c4d3561ebea2d0f05097ce89bdd9bc8767c8cf
|
|
I think this was inadvertently (?) disabled.
Test: no
PiperOrigin-RevId: 160455622
Change-Id: I9f00331d7ef53108eb0adb9bec9c91be22422d2f
|
|
The state of a session is more closely tied to the session itself,
rather than the EnrichedCallManager. The enum was originally placed in
the Manager as it was used in the API, but now that's no longer the
case.
This CL moves the Session State declaration into Session, which is a
more appropriate location.
Test: tap
PiperOrigin-RevId: 160448612
Change-Id: I907476140bc174a061d48ee8e58878af64a62b29
|
|
The old Log class uses the calling class name for the tag. Proguard
minifies class names, making it annoying to figure out which class is
logging in a bugreport. You'd see something like:
06-14 08:50:10.942 10022 20233 20233 I Dialer : bhp - Phone switching
state: OUTGOING -> OUTGOING
Now you'll see
06-14 08:50:10.942 10022 20233 20233 I Dialer :
InCallPresenter.onCallListChange - Phone switching state: OUTGOING -> OUTGOING
Test: Code builds, no changes were made to the actual logged strings
PiperOrigin-RevId: 160445433
Change-Id: Id4d07a33b9ec7a9bceca48e71cdcfc5e6291b571
|
|
b/38149414 building with dreamchip regressed startup time by 400ms. This seems to be caused by linking against the library with cc_library, but the true reason is still unknown.
In this CL, dreamchip libraries is stored as an asset instead. During runtime the asset will be copied into the data directory then loaded.
Currently the copying happens on the main thread. Whether if it's acceptable to introduce further risk to handle this is to be discussed. Disk IO could already happen before this change.
Bug: 38149414
Test: N/A
PiperOrigin-RevId: 160444223
Change-Id: I9f098e7b79df113b2992d8590b33f423942716e4
|
|
populated. Will just return null in createAnimation() thus not animating (this will likely only happen if the View hasn't laid out yet, so there's nothing to animate from).
Bug: 63054791
Test: ChangeOnScreenBoundsTest.java
PiperOrigin-RevId: 160433277
Change-Id: Ib87d274fd6f109290ec74f2241e2fb559d6138cd
|
|
Including in:
- expanded call log item
- collapsed call log item
- search
- in call UI
LOG_STORAGE_INCREASE(GB/week): 3.15
5M active block user/day * 10 events/active = 350M event/wk
350M event/wk * (3 * 3 [int32])/event = 3.15GB/wk
Test: GoogleCallLogAdapterTest, ContactListItemViewTest, InCallFragmentTest
PiperOrigin-RevId: 160423797
Change-Id: I6c0ade53caf767ea9b2610a4c0eb68fcc2bcedf7
|
|
Bug: 62886248
Test: Manual with talkback enabled
PiperOrigin-RevId: 160349111
Change-Id: I9eaaac90b93b7e6f3a002288d0d68fbbe3fae56c
|
|
Bug: 63012482
Test: CallLogCacheLollipopMr1Test
PiperOrigin-RevId: 160303077
Change-Id: I00c80a681963c5a7a25fffd04e02db32ca2386dd
|
|
*** Reason for rollback ***
This CL causes a crash when swapping SIMs.
*** Original change description ***
Adding voicemail transcription branding and progress UI
screen shot showing branding (its harder to capture the progress UI):
https://drive.google.com/open?id=0B9o_KvtLkcuIdkkycVo1RFhsaENYV3J2Yi1LWnJzR0FfSHJR
***
Bug: 63059930
Test: N/A
PiperOrigin-RevId: 160296762
Change-Id: Ib8d709d03d6d8a3fee4a0c384c15df00f55cb182
|
|
The request to stop transmission can be in-flight at the time Dialer goes into the background so the pause request will still include Rx. This happens because pausing previously just gets the current video state and adds pause.
Bug: 62990728
Test: ImsVideoTechTest
PiperOrigin-RevId: 160210111
Change-Id: Ie9134c285a73d4348036f6bbb847abae53a1d373
|
|
This prevents accidental logging.
Test: GoogleCallLogAdapterTest, CallLogListItemViewHolderTest
PiperOrigin-RevId: 160207870
Change-Id: Ib0582613979114c24bb0bd38df41ad7d7dadb63a
|
|
Switch a bunch of imports to support library Fragments (and Loaders) instead of framework Fragments (and Loaders). This was needed to use FragmentManager.isStateSaved() instead of manually tracking that state. This should reduce errors around committing after state is saved.
Also adds METADATA presubmit to prevent new usages of framework Fragments or Loaders.
Bug: 38241305
Test: Covered by existing tests.
PiperOrigin-RevId: 160202511
Change-Id: I5dc0b467da984ca571e49b4dfa0deea44eb372b2
|
|
The previous fix (cl/159623587) has a regression in this scenario:
Device A: video call Device B
Device B: accept video call
Device B: go into background (press Home)
Device A: go into background (press Home)
Device B: return to foreground (return to call)
Unexpected result: A is transmitting video even though it has not returned to the foreground as well
Bug: 62784036,38359325
Test: manual
PiperOrigin-RevId: 160013824
Change-Id: I6e9c89c8fa52882c49d32e061032b93b1e8552f0
|
|
• moved scrollbar to edge of screen
• changed divider to .5dp and added shadow
• change "DECLINE" to "NO THANKS" for verizon TOS (it already was that way for non-verizon)
• changed "ACCEPT" button to "TURN ON" text
• increased the bottom bar height
• made the google transcription text in the TOS bold
• add an image to the non-verizon TOS screen (just using test image for now)
i didn't add the 'Learn more' link, since its not ready yet.
verizon screen shot:
https://drive.google.com/open?id=0B9o_KvtLkcuIcVk0dHBtWmFfdjJWQVV3OEdVc0JXN01XZHQ4
non-verizon screen shot:
https://drive.google.com/open?id=0B9o_KvtLkcuIci1OMlVXTHVuMGYwMWZVTS01dGVwMUpLdmRr
Bug: 62375681
Test: manual and updated unit tests
PiperOrigin-RevId: 160006810
Change-Id: Id45a3a848bb219a70fddbb5a7ada29cd39e604a9
|
|
screen shot showing branding (its harder to capture the progress UI):
https://drive.google.com/open?id=0B9o_KvtLkcuIdkkycVo1RFhsaENYV3J2Yi1LWnJzR0FfSHJR
Bug: 62376944,62424455
Test: device testing
PiperOrigin-RevId: 159993127
Change-Id: I8355164b5831e85de13915e221f6e0f0163e8c81
|
|
Logging impressions for interactions with the voicemail transcription server.
Bug: 62423554
Test: none
PiperOrigin-RevId: 159985772
Change-Id: I782d7eb4df917ae42940f359d98abc87f7ec0f95
|
|
screenshots:
short message (before cl): http://screen/pMAgfV540Y5
short message (after cl): http://screen/VN3TVTBYjPN
long message (before cl): http://screen/V8jSApXmEC2
long message (after cl): http://screen/Vd7zyf2JGvP
long message zoomed (before cl): http://screen/urWDNGACgOf
long message zoomed (after cl): http://screen/i2xEch8HHoq
PiperOrigin-RevId: 159968371
Change-Id: Icaf0a69949b206efd8d08001065cfb4ccdcb1726
|
|
By not checking CallUtil.isVideoEnabled, we were offering upgrading even after the user had disabled it.
I also tried to make the isAvailable method a bit more readable.
PiperOrigin-RevId: 159966735
Change-Id: Ibf828a561654e0e9521a6d86ad18269da426bba4
|
|
There is still one more violation in hangouts that i will address in a separate cl.
PiperOrigin-RevId: 159955865
Change-Id: I61cb65d5f099baae497dfe2daddb4f7da6866ad6
|
|
Replace the null "client type" value by a more detailed value in the MO SMS.
Create a client type value based on :
- Manufacturer name
- Model name
- Android os version
Test: OmtpConstantsTest.java
Original author:
http://aosp/319963 - Alexis MARCOU <alexis.marcou@orange.com>
PiperOrigin-RevId: 159906976
Change-Id: If759f7c96c9fb9a3895f8d944c842c350b8d2472
|
|
If the user disallowed the "Display over other apps" permission then
incoming calls would no longer show up on the lock screen.
The problem was that if the permission was denied then we would attempt
to ask the user to give us the permission. This causes us to start an
activity while the in-call activity is starting which break things.
Fix was to never prompt the user to give us this permission. This is ok
because not having this functionlity doesn't break anything.
PiperOrigin-RevId: 159901233
Change-Id: I3c06ba327ef265fd7981931f49c44e00d1c25350
|
|
|
|
* changes:
Only show video call option in the call log when appropriate
Switch to PROTO2 for better AOSP compatibility.
|
|
am: 842a9777de
am: 7b6472711e -s ours
Change-Id: If203f03766a5eeb0ab4d2f262bb581417146aa39
|
|
Test: IconFactoryTest.java
PiperOrigin-RevId: 159871437
Change-Id: I8df921f36bde619811129ae0f3013ff77903fc8e
|
|
This fixes two bugs we previously had:
1) If video calling was disabled in Settings, we would still show a video call option in the call log (fixed by checking the setting)
2) If a different app from Dialer inserted a video call into the history, we would incorrectly show a video call button in the call log (fixed by checking the account handle matches the default phone account)
PiperOrigin-RevId: 159870114
Change-Id: I19ef6b50db50f9961a486f48996427a1da8f8813
|
|
PiperOrigin-RevId: 159845977
Change-Id: I5615960a4d007924d3db64fc777c7a40593df612
|
|
am: 842a9777de
Change-Id: Ib1d6495d08196f047aacb3f26cab28d20542ff3b
|
|
|
|
cl/159771812.
Test: make, treehugger
This CL updates the AOSP Dialer source with all the changes that have
gone into the private google3 repository. This includes all the
changes from cl/159428781 (6/19/2017) to cl/159771812 (6/22/2017).
These changes track the dialer V11 release.
This goal of these drops is to keep the AOSP source in sync with the
internal google3 repository. Currently these sync are done by hand
with very minor modifications to the internal source code.
See the Android.mk file for list of modifications.
Merged-In: I39aba7e972bac6e5864e70ed693849d90ecd7e08
Change-Id: Ia87877f7ae67c5b56078477b8b08082de1355315
|
|
https://googleplex-android-review.git.corp.google.com/#/c/2446830/
Test: TH, make
Change-Id: I39aba7e972bac6e5864e70ed693849d90ecd7e08
|
|
This will better handle the cases where a show/hide action is performed while the Bubble is animating.
PiperOrigin-RevId: 159771812
Change-Id: I87779da8c0360906587355279b3cc9674289e30f
|
|
Reports when a user sucesfully reports a number is inaccurate caller id and
when their report fails.
PiperOrigin-RevId: 159762210
Change-Id: I8507b4d2a3d4b6f3004e8145f4ba0f9e8065e5d7
|
|
Log which tab is presented when app first launched, including:
- speed dial
- call log
- contacts
- voicemail (if not available, we move to contacts tab immediately and log the
move)
Test: manual
PiperOrigin-RevId: 159754375
Change-Id: Ice5be6c0f2c0463204fe3c1c7cf83c4dfc7df5d1
|
|
When a user uses call composer for the first time, it isn't obvious that their
messages are being stored in the Android Messages app. So we display this toast
to them on the first time they make a enriched call to let them know for
privacy purposes.
screenshots:
http://screen/pcuu4GG037Z
http://screen/MLRJiY9V7cH
PiperOrigin-RevId: 159749893
Change-Id: I0cee7b49321f1d2302ba8ed8f6e1c19c44feb19a
|
|
Current auto fill content is usually the device's own number thus not useful
and it covers "1" key.
PiperOrigin-RevId: 159742824
Change-Id: I753832120bf9436506bf5394b47c94f94899a92b
|
|
b/62666193 is one of the top crashers, the assert that the VVM config is valid has failed. This is likely caused by the PhoneAccountHandle being invalid. While the PhoneAccountHandle must be valid when the broadcast is made, the SIM might have been removed and invalidated the PhoneAccountHandle when the broadcast is still in flight.
In this CL the validity is checked first.
PiperOrigin-RevId: 159737846
Change-Id: Iae5a65978879fd1bfdf726008e8b6463499c99e8
|
|
An empty string isn't as clear and can lead to incorrectly matching other
intents when just comparing package names.
PiperOrigin-RevId: 159725546
Change-Id: I2943b3569fb6409f5c69deb2032f3d8248f6c14d
|
|
TEST=N/A
Video: https://drive.google.com/a/google.com/file/d/0ByIs9UmqOFZFZjBsUS1HQVBxUUE/view?usp=sharing
PiperOrigin-RevId: 159637501
Change-Id: If1b088f7abff2ec52fd54fbbb36d6b7c6d54a926
|
|
We need to check that we have a Context before passing it to
RenderScript.create. getContext can return null if the fragment has been
removed.
I switched this to an early return approach to avoid the deep nesting and added tests.
It is safe to ignore the IfThisThenThat
PiperOrigin-RevId: 159633511
Change-Id: If2286a545c2e514c328dff22c48a99b9ed232e88
|
|
When a user deletes a call from the call log, it might not be clear that they
aren't deleting the attachments they made with the call. So we present them
with a snackbar letting them know to open android messages to delete
attachments.
screenshot: http://screen/TSoWmNhjcn4
screenshot: http://screen/vUXShdYpXem
PiperOrigin-RevId: 159631807
Change-Id: Iaad903258160dc789e0c6a524adba56299523636
|
|
This fixes a bug where we would remember being paused after receiving a second
call incorrectly after we swap back to it.
@tgunn, adding you here to double-check I am interpreting those call session events correctly.
PiperOrigin-RevId: 159623587
Change-Id: Ic52e3e9046f767321a48e22274b8a1c27b4dfa86
|
|
PiperOrigin-RevId: 159622902
Change-Id: Idabc3122601e442a07b31c38287af767651e9970
|
|
The WindowRoot now provides a listener for when the Configuration state changes. Bubble will then reinitialize the MoveHandler (to account for potential changes in screen bounds) and ensure the window is within bounds.
PiperOrigin-RevId: 159614123
Change-Id: Icace5b52299825836fb398ce1e6234ad0bb212f3
|
|
|
|
am: f43ad4c585
Change-Id: Ic0b4394960fb1e2e81eda34c2d2e25eb23e8e281
|
|
am: 57304d887c
Change-Id: I08748f0e7890a5c2288decf02339533671049b1d
|
|
am: 6803817279
Change-Id: I43f7bdea8b1007fd947337c4abfc083913d66ef8
|
|
am: a8a71b12c6
Change-Id: I505e7c88518873c9fb1b402fa87ea407a7c56f64
|
|
am: 7cc2ab563c
Change-Id: I7285305983985264b5588f7240e19785a484cb11
|
|
am: 7cc2ab563c -s ours
Change-Id: Ie06a3dbfe5b3ce065cbfaa04c862a0ca30418dbe
|
|
e4de90c6d9
am: cccd0a8597
Change-Id: I56fa753c4191d6969b75f4e22b2013eb56655a9f
|
|
am: e4de90c6d9
Change-Id: I3c2ef89d2548ea0cb5a169b7dd1bebbf6014afa7
|
|
|
|
*** Reason for rollback ***
It's not necessary anymore after we verified it could be controlled from server side.
*** Original change description ***
Flip flag to enable ReturnToCall bubble.
Enables ReturnToCall bubble and changes the name of the flag so that it can be toggled independently from previous versions.
***
Also in the change: Restore TODOs
Test: TH
PiperOrigin-RevId: 159587541
Change-Id: I88f01550f07a7859f41b4f0fc843e92b38f5a85b
|
|
Issue steps:
1. Show overflow menu in dialpad.
2. Press Home button, start another app such as Messaging.
3. Make phone call by Messaging app.
4. After the call is active, press home button and start Dialer again.
5. Dialpad is dismissed but popup overflow menu still shows.
Solution:
Dismiss popup menu when show dialpad chooser.
Credit to:
yifan.bai <yifan.bai@spreadtrum.com>
https://android-review.googlesource.com/#/c/417719/
Test: TH, manual
Change-Id: I019a799d52282bfb47a09d43cf25c14b053f8d9b
|
|
Copybara will do this on export.
Test: TH
PiperOrigin-RevId: 159512079
Change-Id: If47ac04c42f8cc1f56e5d761d4ab1f1b6f17b57e
|
|
BitmapFactory.createBitmap doesn't carry-over image exif data. We now
hold onto exif data and reapply it through matrix transformations so
images are displayed properly.
Test: TH
PiperOrigin-RevId: 159492684
Change-Id: Ief58f5fc506214e4a6afaf36a1be7dd53c712d4d
|
|
VVM activation state is required to suppress legacy voicemail notification. It should not be shown if VVM is activated. Before this CL this information is stored in credential protected storage, and cannot be accessed right after boot. Telephony might have a stale VM count and will attempt to refresh the notification after reboot, which will not be suppressed.
In this CL the activation state is moved to device protected storage. Other account info are sensitive and remain in credential protected storage.
Test: TH
PiperOrigin-RevId: 159492498
Change-Id: I918546cd9874e47c4aa96889aa35916ca6c59890
|
|
Number shouldn't be shown in bottom row if it's already shown on name row.
Test: TH
PiperOrigin-RevId: 159468064
Change-Id: Ieb3eff270d247dd712d2fbf6fe2428038ba643c3
|
|
An annoying part of development on enriched calling is that it was
difficult to determine what sessions were in memory. We have a
number of bugs related to incorrect sessions being shown, and knowing
exactly what sessions are available in memory can help debug them.
This CL adds a "Simulator" for enriched calling. This is more of a debug
tool than a simulator since it doesn't yet support adding a new enriched
calling session.
To allow the simulator to view all of the sessions in memory, a new
EnrichedCallManager API was introduced: getAllSessionsView. This API was
designed in a way to prevent abuse, so it returns a list of string
representations of the sessions. Just returning the full list of
sessions would have allowed clients to bypass the getSession logic and
examine sessions that shouldn't be available.
Also in this change:
* Integrate changes to form a base for future copybara imports.
Test: TH
PiperOrigin-RevId: 159445010
Change-Id: Ie8fc35d817a4e3b0eac37e0c34a6592060c43b23
|
|
am: ea7890cd5e
am: 0a7b301e28 -s ours
Change-Id: Ifc2aaaa33992aaad8d5fa4b16fe47a5862385131
|
|
am: ea7890cd5e
Change-Id: I4f5e2f0040f9d8749856b6a51fb2befa398f8e4c
|
|
cl/159428781.
Test: make, treehugger
This CL updates the AOSP Dialer source with all the changes that have
gone into the private google3 repository. This includes all the
changes from cl/158012278 (6/05/2017) to cl/159428781 (6/19/2017).
This goal of these drops is to keep the AOSP source in sync with the
internal google3 repository. Currently these sync are done by hand
with very minor modifications to the internal source code.
See the Android.mk file for list of modifications.
Our current goal is to do frequent drops (daily if possible) and
eventually switched to an automated process.
Merged-In: Ie60a84b3936efd0ea3d95d7c86bf96d2b1663030
Change-Id: If1fa394df2609f0d38b4f794c83f4db3f1006484
|
|
cl/159428781.
Test: make, treehugger
This CL updates the AOSP Dialer source with all the changes that have
gone into the private google3 repository. This includes all the
changes from cl/152373142 (4/06/2017) to cl/159428781 (6/19/2017).
This goal of these drops is to keep the AOSP source in sync with the
internal google3 repository. Currently these sync are done by hand
with very minor modifications to the internal source code.
See the Android.mk file for list of modifications.
Our current goal is to do frequent drops (daily if possible) and
eventually switched to an automated process.
Change-Id: Ie60a84b3936efd0ea3d95d7c86bf96d2b1663030
|
|
8e49b42b6f am: ef26655bcf -s ours am: b3d940136e -s ours
am: 444ba7afdf -s ours
Change-Id: Ie3c3b5b1b7d3c2b0870219d0c78c80cad3994b25
|
|
8e49b42b6f am: ef26655bcf -s ours
am: b3d940136e -s ours
Change-Id: I39e54ed8fb4fe8667df40b094c2dff4cdb20df18
|
|
am: ef26655bcf -s ours
Change-Id: Ie6549560c815fb1ee03ff9ec51f27b30f5087cf9
|
|
am: 8e49b42b6f
Change-Id: If33a227619c50e0d2b19dd3cc9f14e9d45ad5807
|
|
|
|
A previous change added legacy-android-test as a static dependency to
all packages that build against the current, test_current or
system_current and failed to compile when the junit and android.test
classes were removed from the API. Unfortunately, those changes did not
take into account that some of those packages target earlier API
versions and so will always have the classes available at runtime.
This change replaces those static dependencies with dynamic dependencies
for any package that targets an earlier API version. The file changes
were made automatically by a tool that constructed and then analyzed a
full dependency graph of all the Android Java modules. The individual
changes were checked manually to ensure that the changes matched the
intent. The affected modules were built against an API with the junit
and android.test classes removed. Any issues found during this process
resulted in either the tool being updated to address the issue or a
separate change being made to fix an existing problem with the build. A
sample of the affected packages were run to ensure that they worked as
expected at runtime; no issues were found during testing.
The following change descriptions were generated automatically and so
may be a little repetitive. They are provided to give the reviewer
enough information to check the comments match what has actually been
changed and check the reasoning behind the changes.
* Android.mk
Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
because Dialer's manifest file (AndroidManifest.xml) targets API
level 23 and dynamically includes the android.test.runner library
at runtime so there is no point in statically including the
classes. It was not added to LOCAL_JAVA_LIBRARIES because module
Dialer does not have any dependencies on android.test classes
* tests/Android.mk
Added 'android.test.mock.sdk' and 'legacy-android-test' to
LOCAL_JAVA_LIBRARIES because module DialerTests builds against
'LOCAL_SDK_VERSION := current' and uses classes from packages
android.test and android.test.mock (possibly indirectly) so will no
longer compile once they are removed from the API.
They were not added to LOCAL_STATIC_JAVA_LIBRARIES because
DialerTests's manifest file (AndroidManifest.xml) targets API level
23 and uses the android.test.runner library which will provide the
classes dynamically at runtime.
Dependency 'android.test.mock.sdk' is used instead of
'android.test.mock' because module DialerTests builds against the
API not internal jars and so should use libraries that build
against the API not internal jars.
A future change will replace the dependency on
'legacy-android-test', which builds against the internal jars with
a dependency on 'android.legacy.test' which will build against the
API.
Bug: 30188076
Test: make checkbuild and ran a sample of tests
Change-Id: Ia69a25caeef20017c311f45d046fbccb83ea7394
Merged-In: I10c2c5f315e442477be81726e7df20d569fe5305
Merged-In: I37a618deba48d87a1a03d82ad4022233b408a788
|
|
Orange has made a few request that cannot be resolved in the
O timeframe. VVM support for it should be disabled in AOSP so OEMs
won't get it by default without the fixes. These issues will be
resolved in August when O is released and dialer is doing regular
drops in the public.
France is live in prod while Belgium/Luxembourg is experimental
behind a flag.
This CL does not affect GoogleDialer in the system image
Change-Id: Ia7e5c9b5d2411a15453f585bb9eae88aae1bbc00
Fixes: 62536071
Test: manual
|
|
cl/158012278. am: 91ce7d2a47"
This reverts commit c67d658e7daa453fe9ad9fd1a37f81eaf2048c44.
Reason for revert: This CL broke the sailfish-userdebug_javac-all target on master.
Change-Id: I9b54333a654c00154ca84f4ece84bea4f07cc19b
|
|
am: 91ce7d2a47
am: 274b6d320e
Change-Id: Iecf4325f314bf6c3324187e6406c8aae4675dd63
|
|
am: 91ce7d2a47
Change-Id: I1744a8bfca09eae5e9c0d7aac122515eca75bb8b
|
|
cl/158012278.
Test: make, treehugger
This CL updates the AOSP Dialer source with all the changes that have
gone into the private google3 repository. This includes all the
changes from cl/152373142 (4/06/2017) to cl/158012278 (6/05/2017).
This goal of these drops is to keep the AOSP source in sync with the
internal google3 repository. Currently these sync are done by hand
with very minor modifications to the internal source code.
See the Android.mk file for list of modifications.
Our current goal is to do frequent drops (daily if possible) and
eventually switched to an automated process.
Change-Id: I4d3f14b5140e2e51bead9497bc118a205b3ebe76
|
|
am: 141883f160
Change-Id: Ie019ef02cbc21517e78e8d053b1e7dfd150889e2
|
|
am: 28d5e3ca4a
Change-Id: Ic4912b727886f3e9a24f6e4a88ab433b57c19057
|
|
|
|
|
|
am: ae06b1b3b8
Change-Id: I37dfc5acf163aa0942803da64ec47629622580c4
|
|
am: 83b20211c3
Change-Id: Ide21415247a3ec743f5438c49d29ba2d861081b0
|
|
This release was created following the instructions at:
go/dialer-aosp-release
Subsequent dialer releases will follow as O bugs are
fixed, until we reach our final RC.
Version: 10
Candidate: RC45
Branch: dialer-android_release_branch/153304843.1
dialer-android_20170416.00/dialer-android_20170416.00_RC45
This release contains the following bug fixes since RC39:
Bug: 38131932 38302993 38347350 38368993 38395481
62100344
Test: make, on device
Change-Id: Ib4af5dcc58c684d51ea1f4628b301e40184b81b3
|
|
am: 7f7f25f903
Change-Id: I9ecaf153cf214e099228ec43cdcf8b565129ff0a
|
|
am: d40e05b9e0
Change-Id: I083c9e03f38eacd2cb4eff67b07b302e67196add
|