summaryrefslogtreecommitdiffstats
path: root/java
Commit message (Collapse)AuthorAgeFilesLines
* This change brings Dialer oc-mr1-dev up to date with v11.1 RC06.Eric Erfanian2017-08-07576-1373/+4958
| | | | | | | | | | | | | This is to resolve a merge conflict in: I48296c56fb1d275a06b7c314f5380266c1195ef2 Test: make master is already up to date and Merged-In: I858e3665253139b8aab4e4c063bfc4c419f33cc9 Change-Id: Ifc146f2fec24fd2f8a51cd32feb3699bb1c07136
* Set CallDetailsActivity exported to false.erfanian2017-07-131-5/+1
| | | | | | | Bug: 37846172 Test: on device PiperOrigin-RevId: 161720359 Change-Id: I2df2036c6d9941d37511f450f58682cf07e774b0
* Cache video state to avoid performance issue.wangqi2017-07-132-10/+17
| | | | | | | | | 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
* Contacts headers now update properly when you fast scroll backwards slowly.calderwoodra2017-07-131-0/+1
| | | | | | | video: https://drive.google.com/open?id=0B2Hce9qilHmvdl8xY1hmcDZ0R3M Test: manual PiperOrigin-RevId: 161713747 Change-Id: I8185ca897a82479ef7c552a1ce6891e31c4c5aad
* Adjust call composer for dimensions so all items fit on screen for large dpi.calderwoodra2017-07-132-7/+8
| | | | | | | | | | | | | | | 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
* Display correct string for Lightbringer calls in call detailsroldenburg2017-07-137-5/+67
| | | | | | | | | | | | 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
* Resolve NPE in post call send message prompt.calderwoodra2017-07-131-3/+5
| | | | | | | | | | | | 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
* Fixed ArrayIndexOutOfBoundsException in Contacts Fragment.calderwoodra2017-07-131-0/+4
| | | | | | | | | | | | | 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
* PostCallActivity edittext is not always visible on all screen sizes.calderwoodra2017-07-134-26/+33
| | | | | | | | | before: http://screen/DsVrM1vK89e after: http://screen/RzGZvPTXRQb Bug: 63093275 Test: manual PiperOrigin-RevId: 161609906 Change-Id: If53681b9414dd79dba16371f42be437f1afa2729
* Fix Call button text alignment in expanded call log itemroldenburg2017-07-133-6/+37
| | | | | | | | | | | | | | 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
* Fixed NPE in CameraComposerFragment.calderwoodra2017-07-121-1/+5
| | | | | | | | | | | | 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
* Strip verbose and debug logs for VvmLogtwyen2017-07-121-0/+4
| | | | | | Test: N/A PiperOrigin-RevId: 161596844 Change-Id: Id4d8a70fe5690e05dc6bad1aca50a1a53f031a58
* Fix bug that proximity sensor is turned on too early.wangqi2017-07-122-3/+6
| | | | | | | | | | | | | | 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
* Add log when sending VVM SMStwyen2017-07-121-0/+6
| | | | | | | | | OEM and carriers need this line to verify. Bug: 62677283 Test: N/A PiperOrigin-RevId: 161594185 Change-Id: I00cf649a745a45a14fcea9948f1f8c696fb4b6b1
* Move VideoShareSession to third_party to remove bad cast in VideoShareManagerroldenburg2017-07-124-0/+58
| | | | | | | | | | | | | | 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
* Run VVM activation when dialer is updatedtwyen2017-07-122-0/+50
| | | | | | | | | | | 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
* Tag spam network traffic using TrafficStats.zachh2017-07-121-0/+5
| | | | | | | | | | | | | 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
* Remove obsolete wrapper bundle from CallIntent Bundle.erfanian2017-07-122-16/+32
| | | | | | | | | Add additional null checks during deseriailzation. Bug: 63575857 Test: unit tests, on device PiperOrigin-RevId: 161564824 Change-Id: I54f52e12397adb4473b523325f8c006ff534fbd9
* Update AOSP Dialer license Data.erfanian2017-07-122-681/+1712
| | | | | | Test: ondevice PiperOrigin-RevId: 161548092 Change-Id: If4cde06669bc33cca69a9b602f54d873b735c730
* Improved preview scaling in IMS video calls.zachh2017-07-112-64/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Fix NPE in PhoneFavoriteTileView.onClick.yueg2017-07-112-2/+7
| | | | | | | | 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
* Make CallLogCache thread safe.wangqi2017-07-114-110/+52
| | | | | | | | | | | 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
* Remove Assert(isAtLeastO) in LegacyVoicemailNotificaitonReceivertwyen2017-07-111-1/+12
| | | | | | | | | OC preview devices are hitting the assert and skewing crash rate numbers. Bug: 62338925 Test: LegacyVoicemailNotificaitonReceiverTest PiperOrigin-RevId: 161438516 Change-Id: Ib533947d2cd9e9a87ffd9fb629f09f877f683026
* Remove letter tile's manual asset cachingmaxwelb2017-07-101-66/+56
| | | | | | | | | | | | | | | | | | | | | | | | 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
* Update merge strategy. The legacy strategy is deprecated.erfanian2017-07-101-5/+1
| | | | | | | | | * 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
* Bump version code and name to Dialer v12sail2017-07-101-2/+2
| | | | | | | | | | | | 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
* Remove ConfigBindings from DialerBackupAgentuabdullah2017-07-101-83/+65
| | | | | | | | | 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
* Reset restricted count on merge.wangqi2017-07-101-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Guard VoicemailClientReceiver when VVM module is disabledtwyen2017-07-101-0/+6
| | | | | | | | | | | 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
* Improve GoogleCallLogAdapterTest to better emulate realityroldenburg2017-07-101-0/+7
| | | | | | | | | | | | 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
* Update REASON_IMS_ACCESS_BLOCKED definition to match framework change.sail2017-07-102-3/+7
| | | | | | | | | | | 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
* Use NOTIFICATION_INCOMING_CALL_QUIET when the in call UI is visibletwyen2017-07-101-5/+14
| | | | | | | | | | | 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
* Fix NPE crash when haning up conference call.wangqi2017-07-101-1/+1
| | | | | | | | | | 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
* Automated g4 rollback of changelist 160696979.sail2017-07-101-57/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | *** 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
* Fix 2 NPEs in CallLogAdapter.yueg2017-07-101-1/+3
| | | | | | Test: cl/160695183 PiperOrigin-RevId: 160697524 Change-Id: I07127554a968d8dc36c02b522b7536438be7fb90
* Fix concurrency issue in constructor.erfanian2017-07-101-26/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Move voicemail notification dismissing to VisualVoicemailCallLogFragmenttwyen2017-07-102-28/+9
| | | | | | | | | 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
* Add video call not available dialog.wangqi2017-07-0695-477/+304
| | | | | | | | | | | 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
* Bump version code for Dialer v11 (again)uabdullah2017-06-301-1/+1
| | | | | | | | | | | | | | 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
* Automated g4 rollback of changelist 160349111.sail2017-06-305-74/+0
| | | | | | | | | | | | | | | | | *** 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
* Automated g4 rollback of changelist 160202511.sail2017-06-3056-177/+189
| | | | | | | | | | | | | | | | | | | | | *** 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
* Re-enabled strict mode in bugfood.zachh2017-06-301-1/+1
| | | | | | | | I think this was inadvertently (?) disabled. Test: no PiperOrigin-RevId: 160455622 Change-Id: I9f00331d7ef53108eb0adb9bec9c91be22422d2f
* Move Session State definition into Sessionmaxwelb2017-06-304-44/+43
| | | | | | | | | | | | | | 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
* Change InCallPresenter to use LogUtilmaxwelb2017-06-301-54/+92
| | | | | | | | | | | | | | | | | 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
* Load dreamchip from assetstwyen2017-06-301-1/+1
| | | | | | | | | | | | | 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
* Avoid NPE in ChangeOnScreenBounds when the start or end values are not ↵keyboardr2017-06-301-4/+15
| | | | | | | | | 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
* Log the number of times when Lightbringer video call button appears.yueg2017-06-307-15/+95
| | | | | | | | | | | | | | | | 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
* Add accessibility info for bubble.keyboardr2017-06-305-0/+74
| | | | | | | Bug: 62886248 Test: Manual with talkback enabled PiperOrigin-RevId: 160349111 Change-Id: I9eaaac90b93b7e6f3a002288d0d68fbbe3fae56c
* Fix NPE in CallLogCacheLollipopMr1.isVoicemailNumber()twyen2017-06-302-2/+10
| | | | | | | Bug: 63012482 Test: CallLogCacheLollipopMr1Test PiperOrigin-RevId: 160303077 Change-Id: I00c80a681963c5a7a25fffd04e02db32ca2386dd
* Automated g4 rollback of changelist 159993127.sail2017-06-309-113/+14
| | | | | | | | | | | | | | | | | | | | *** 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
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 03:49:17 +0000