| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
BUGBASH-612: do not send phone numbers to non-ssl sites for reverse/forward/people lookups
Change-Id: I677460ad5767b8698ee24d6d43ff159aee55387a
|
|
|
|
| |
Change-Id: I2ae8882a3ca9d99ecba6e1b4f8d6ed426036818d
|
|
|
|
| |
Change-Id: Iaf212538d01d1e6400ea0e4fb54b3d414e983f40
|
|
|
|
|
| |
Change-Id: I53b6ee1c70925c50e91270e0b084d777dd8c06f6
Signed-off-by: Joey <joey@lineageos.org>
|
|
|
|
|
|
|
|
| |
* The anti-falsing implementation from HumanInteractionClassifier
regularly prevents easy swipe to answer, requiring multiple
attempts until accepted.
Change-Id: Iebad27f9da7bb8fea6fc663dc99ac6c17d94ed5f
|
|
|
|
| |
Change-Id: Ia30a3c46e9c37d7d73288ec605af8efc3a46a323
|
|\
| |
| |
| |
| |
| | |
4318546 snap-temp-L23800000099760172
Change-Id: Idf1973aacafffa90c2a12019a0da2c3b0644828d
|
| |
| |
| |
| |
| |
| |
| | |
Test: builds
Bug: 64367402
Change-Id: I2cd69c0f67cb41eb9999af79313e9c8835d8fa07
|
|\|
| |
| |
| |
| |
| | |
4288633 snap-temp-L81700000095141745
Change-Id: I605c3b28a5ac328edc2328d759e18ffb10035cda
|
| |\
| | |
| | |
| | |
| | |
| | | |
am: b1161675bc
Change-Id: I0eb4994d359a50d625db0ac11396b78234ade85f
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This moves the branch forward from v11.1 RC06.
This release contains fixes for the following bugs:
Bug: 37275934 63518188 64038420 64098692 64125770 64363054 64693073
Test: make
Change-Id: If70e86738a66a264a8aae17a24dee69495a7d180
Merged-In: I5bd65215a42744ba4149a9359e443679306b6cc0
|
|\| |
| | |
| | |
| | |
| | |
| | | |
4273744 snap-temp-L04700000093069831
Change-Id: I338a60ea884fb52cb354b050d9071f27c9791307
|
| |\|
| | |
| | |
| | |
| | |
| | | |
am: 9a6afa3ae2 -s ours
Change-Id: I4903cb75f44dd4df965abd61a89be99c104bd4c6
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This moves the branch forward from v11 RC17.
This release contains fixes for the following bugs:
Bug: 63584851 63803282 63917358 64099380
64101648 64105912 64119808 64122858
64125770 64300111
Test: TH, on device
Merged-In: I858e3665253139b8aab4e4c063bfc4c419f33cc9
Merged-In: Ifc146f2fec24fd2f8a51cd32feb3699bb1c07136
Change-Id: I48296c56fb1d275a06b7c314f5380266c1195ef2
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is to resolve a merge conflict in:
I48296c56fb1d275a06b7c314f5380266c1195ef2
Test: make
master is already up to date and
Merged-In: I858e3665253139b8aab4e4c063bfc4c419f33cc9
Change-Id: Ifc146f2fec24fd2f8a51cd32feb3699bb1c07136
|
| |\|
| | |
| | |
| | |
| | |
| | | |
am: ff2ad7ffdb -s ours
Change-Id: I3f18297015268a65f3d58fcd3e5238de0fd3a4a3
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change updates the oc-dr1-dev branch to v11 RC17,
from the previous state synced @160679286.
This contains:
- A ROLLUP from 161342943
- Fixes for the following bugs:
Bug: 33490149 36608790 37846172 62294499
62338925 63013427 63089358 63104326
63112642 63143138 63161630 63405063
63415147 63450835 63494010 63522618
63523694 63523776 63524435 63575857
63594129 63634700 63642638 63643370
63709810 63710739 63716219 63757003
64009408 64025042 64060628 64073371
Test: make
Merged-In: I69ba6cbadbd1a02f05405ca0f5273b0a5ea0e5e9
Change-Id: Iaad73fa51796f62f4947571ddb744bbdadcca64e
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ours
am: 0602dd0831 -s ours
Change-Id: Ic7481ff391b93b60dd52b2bd91c5fe20dd443353
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | | |
am: 04d29c1e08 -s ours
Change-Id: I74a2079520a8c0caea39ded3403bb859492f9b26
|
| | | |\
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
am: 5fc22b92d2 -s ours
Change-Id: I042483d58f8f89ca08fb87816d4ac58ed53e69ff
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I46847dfa9efb8eb4a8d3d245739aef22d370106a
Auto-generated-cl: translation import
Exempt-From-Owner-Approval: translation import
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4185249 snap-temp-L63000000082739046
Change-Id: Ibe8fb2284880105220bdcd6f0c75450eb4999268
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: 37846172
Test: on device
PiperOrigin-RevId: 161720359
Change-Id: I2df2036c6d9941d37511f450f58682cf07e774b0
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is temporary solution to avoid expansive operation for frequent method calls. In long term we should figure out a better way for such cases.
Bug: 62424638,62426694
Test: manual
PiperOrigin-RevId: 161717598
Change-Id: I75e6589174b81ae611893e5435a94e7f629f500f
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
video: https://drive.google.com/open?id=0B2Hce9qilHmvdl8xY1hmcDZ0R3M
Test: manual
PiperOrigin-RevId: 161713747
Change-Id: I8185ca897a82479ef7c552a1ce6891e31c4c5aad
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
screenshots:
default sizes:
before: http://screen/u29zyepX0OM
after: http://screen/tXGSUbNfWAE
large sizes:
before: http://screen/NH3OmGDRyBp
after: http://screen/W6DVopCxMUp
Bug: 63156716
Test: screenshots
PiperOrigin-RevId: 161693857
Change-Id: I8310336080ae080dc586dcf21d4966260880a627
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Without this change, all video calls are referred to as just "video call". This
CL uses the Lightbringer interface to allow customizing that text.
Before: https://drive.google.com/open?id=0B7uuA4cyYX0xeVZCTGtMUUtoRVU
After: https://drive.google.com/open?id=0B7uuA4cyYX0xMnFhbTBXMDI2VW8
Bug: 63138393
Test: CallTypeHelperTest
PiperOrigin-RevId: 161692812
Change-Id: I36dc1a1fae96dddee91c5efb8892c4a6c7ef67ca
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This issue occurs when users are shown a post call snackbar and their shared
prefs are updated before pressing "send message". This change resolves the
issue by getting the phone number when the prompt is created rather than when
the button is pressed.
Bug: 62294499
Test: PostCallTest#postCall_UpdatedQuickly_PostCallStartedSuccessfully.
PiperOrigin-RevId: 161689241
Change-Id: Ie2c857f6743aa556f993bc3f8e92c8b2b7357c08
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If a user caused their activity to undergo several state changes rapidly, they
could get the contacts fragment into a state where it wouldn't have any
elements but still call onScrollChange. This would result in calls to
getFirstCompletelyVisibleItemPosition returning NO_POSITION (-1) and throw an
AIOOBE when attempting to get a row's header value.
Bug: 63594129
Test: manual.
PiperOrigin-RevId: 161610423
Change-Id: I0c53587a6499c42abe5e51b6ac2b4108c0971545
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
before: http://screen/DsVrM1vK89e
after: http://screen/RzGZvPTXRQb
Bug: 63093275
Test: manual
PiperOrigin-RevId: 161609906
Change-Id: If53681b9414dd79dba16371f42be437f1afa2729
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The Call button may have two lines of text. We were not properly setting the
second to GONE in all cases.
Note: We don't need to require Google Dialer being the default Dialer for the Duo integration to work. I added this check so removing it doesn't go against any previous well-considered decision. It also enables the Espresso test work without needing a flag to override.
Before: https://screenshot.googleplex.com/3YXaZdbQk7k
After: https://drive.google.com/open?id=0B7uuA4cyYX0xNThETTJWdTVQQWM
Bug: 63062360
Test: GoogleDialtactsActivityTest
PiperOrigin-RevId: 161606497
Change-Id: I7526a4fc60b84906cc04563b635eaad9f348415e
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4176727 snap-temp-L91200000081901352
Change-Id: I10d0449e9a44c32e8c718383ee6afc9a542e9319
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If a user took a picture then quickly closed call composer, when the image was
ready we would try to update our view state. Since our fragment is no longer
attached, this cuases a crash when we check that getContext() is not null.
fragment.getContext is never null in robolectric.
Bug: 62687110
Test: manual, cannot test b/c we cannot take photos in Espresso and
PiperOrigin-RevId: 161600278
Change-Id: If9bd98578d221fca4bc99ff17a39f917f3a8bcca
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Test: N/A
PiperOrigin-RevId: 161596844
Change-Id: Id4d8a70fe5690e05dc6bad1aca50a1a53f031a58
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is caused by setting call state to OUTGOING after it's created but before
it's connecting, which incorrectly switches state as NO_CALL -> OUTGOING ->
PENDING_OUTGOING -> OUTGOING.
The fix is giving it PENDING_OUTGOING state if an outgoing call is initialized
but still not yet getting update from telecom to CONNECTING (in which case the
call will be IDLE state).
Bug: 62965119
Test: manual
PiperOrigin-RevId: 161594187
Change-Id: I02c8b4dcb0bfd5101bc69f48bb99c66d4831b72e
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
OEM and carriers need this line to verify.
Bug: 62677283
Test: N/A
PiperOrigin-RevId: 161594185
Change-Id: I00cf649a745a45a14fcea9948f1f8c696fb4b6b1
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It was odd that we were casting and was causing some crashes. This CL makes
things work more as is typical in Dialer.
We previously did not do this because there are some parts of the
VideoShareSession which are not open-sourceable. Turns out we can simplify
those parts out of the interface.
Bug: 63523694
Test: existing tests
PiperOrigin-RevId: 161593028
Change-Id: I8f1379fc46f4e9d41413b731787dbf37e0901da9
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
VVM capability can change between dialer versions. For v10 the update is done through system image, so when the user get the new dialer they are guaranteed to received a onCellServiceConnected event() after boot, and activation will be triggered. This does not apply to play store update or side load.
In this CL, activation will also be triggered when the app is updated.
Bug: 35809267
Test: PackageReplacedReceiverTest
PiperOrigin-RevId: 161592369
Change-Id: I6904ef0514f9eec8151cd28be8cf76255640b108
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The dialer app crashes on launch right now when app data is empty, because we fetch the spam list on app start, and we don't tag the network traffic using TrafficStats, which is a strict mode violation.
This CL tags spam network traffic using TrafficStats, by providing a custom transport executor for the GRPC channel. All activity on the channel is tagged as spam.
This unfortunately required creating a new thread pool. I am not sure if this creates more threads than before, because it is not clear what type of transport executor grpc uses by default. Note that the new thread pool will kill unused threads after 60 seconds so won't consume resources when idle.
Bug: 62388129
Test: manually verified app does not crash on launch with empty data. Can add automated tests upon request.
PiperOrigin-RevId: 161568882
Change-Id: I99da6ebb649fe1a63d634871ab314d8d910658f9
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add additional null checks during deseriailzation.
Bug: 63575857
Test: unit tests, on device
PiperOrigin-RevId: 161564824
Change-Id: I54f52e12397adb4473b523325f8c006ff534fbd9
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Test: ondevice
PiperOrigin-RevId: 161548092
Change-Id: If4cde06669bc33cca69a9b602f54d873b735c730
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4173087 snap-temp-L93200000081515229
Change-Id: Iaf4293418ebe2b4c801225f2eb88a971b5e696cf
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This CL attempts to improve many related issues.
The first was that the (post-greenscreen) preview was "squished" when making an outgoing IMS video call:
BEFORE: https://screenshot.googleplex.com/cRcZYmgq1rh
AFTER: https://screenshot.googleplex.com/8cWFQw7Au2U
Another issue is that the preview on the green screen sometimes appears very zoomed:
BEFORE: https://screenshot.googleplex.com/0vyq3U87xVX
AFTER: https://screenshot.googleplex.com/zyhkdATMuUj
These two issues seem to be improved by removing our manual attempts to scale the video via VideoScale. (Note that transforms to fix rotation are still needed in landscape mode and remain.)
Another issue is that when hanging up an unanswered outgoing video call, the preview becomes temporarily extremely zoomed and unblurred:
BEFORE: https://screenshot.googleplex.com/mqwSsTXhwSw
AFTER: https://screenshot.googleplex.com/uKfEpVmd8A2
Another issue is that when rotating the device, the preview would sometimes remain rotated incorrectly.
BEFORE: https://screenshot.googleplex.com/p2mVnPJ7dww
AFTER: https://screenshot.googleplex.com/S8R0FsS0Vsn
I believe that these problems (and possibly other video related flakiness I sometimes observed) happen because we update scaling and views immediately after applying layout changes. Often times, the layout changes haven't taken effect because we're in the middle of a layout pass so the updates are not working correctly. So, I moved most of those updates into specific layout listeners for the preview and remote texture views.
(Note that something similar before was attempted using a global layout listener, but that layout listener removed itself after the first invocation so didn't seem to be working as intended AFAICT.)
The last issue was that when toggling the front/rear camera, when returning to the front camera, the video would appear zoomed. This was fixed by removing the call to setDefaultBufferSize in VideoSurfaceTextureImpl. From the javadoc of that method, it doesn't sound like something that we should need to be doing and it reliably fixes the problem.
BEFORE: https://screenshot.googleplex.com/6j0XDfLGAzk
AFTER: https://screenshot.googleplex.com/Hs7zsbtyjwc
Bug: 62437862
Test: manually placed and received IMS calls and observed improved preview scaling on multiple devices when calling from O to N, O to O, and N to O. Observed that basic features (mute/umute video, swapping cameras, greenscreens, answer screens, hanging up, etc) still behave reasonably. Open to suggestions for automated tests.
PiperOrigin-RevId: 161444534
Change-Id: I4be348875de11b8517feba86da07fe41a3e5351d
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Although we don't know the reason why v.getParent() can be null, we can avoid calling it.
Test: manual
PiperOrigin-RevId: 161442696
Change-Id: I07af0da9b64fb3fa77b01c0b619837a79d593b67
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Methods such as getAccountLabel() is called on different threads which may cause
race condition issue.
This change also delete CallLogCacheLollopopMr1 since it's not necessary that Dialer is targeting M+.
Bug: 63415147,63524435
Test: none
PiperOrigin-RevId: 161440757
Change-Id: Ia609c52e53dabdce78ffb4320f4cd66e38112e47
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
OC preview devices are hitting the assert and skewing crash rate numbers.
Bug: 62338925
Test: LegacyVoicemailNotificaitonReceiverTest
PiperOrigin-RevId: 161438516
Change-Id: Ib533947d2cd9e9a87ffd9fb629f09f877f683026
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4169335 snap-temp-L20600000081126177
Change-Id: I040cac3494f4de79b5566189af14fe13607b2fdc
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In b/63143138 we discovered an issue with the LetterTileDrawable code.
The class has static fields that are shared across both the main and
background threads, which aren't threadsafe. We attempted to make the
code threadsafe in cl/160696979, but that ended up causing issues as
well.
This CL takes a different approach. Rather than trying to make the code
threadsafe, it instead removes the shared fields and makes them final
and initialized in the constructor. This is inherently threadsafe since
threads cannot interact with the object until it is constructed.
Now that the objects aren't shared, we would potentially use more
memory, since each LetterTileDrawable will now hold onto an instance of
the formally shared object. This was not determined to be an issue
in practice, see the data and conclusion in
(go/lettertiledrawable-caching).
Bug: 63143138
Test: LetterTileDrawableTest (can't verify everything :/ )
PiperOrigin-RevId: 161432711
Change-Id: I443bef01ffac405f5e14e9d981ce1d5a8f3f8fec
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Don't allow cleartext traffic in the voicemail module. This was being overridden, anyway.
Bug: 62339559
Test: See below.
PiperOrigin-RevId: 161418474
Change-Id: Icd945902ed089bf37b43d93d8fe32983a9f88fea
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This CL bumps the version name of Dialer from Dialer v11 to Dialer v12. This CL
also bumps the version code from 15***** to 1600000.
I've also set 'version_conf_incrementer_max_version_code' at go/dialer-v11
to 1599999.
Test: N/A
PiperOrigin-RevId: 161418347
Change-Id: I961f22481d813d66b950894b3783e13624de733e
|