Age | Commit message (Collapse) | Author |
|
Bug: 70988915
Test: CnapPhoneLookupTest
PiperOrigin-RevId: 193968830
Change-Id: I7f0c8468472e831699e56e399060067286e3ea0d
|
|
call log.
For some reason not understood, startActivity with the call intent causes the current activity (MainActivity) to be paused, resumed, and paused again. This results in an opportunity to double-tap the row which causes the InCallUi to open in bubble mode (this is also not well understood).
In any event, PreCall.start eventually uses TelecomManager to place the call rather than startActivity, which is presumably the thing that fixes the problem.
Also refactored TestPreCallModule to remove the many test implementations of PreCall and remove the static field in the module which could cause test interference.
TEST=manual
Bug: 78187587
Test: manual
PiperOrigin-RevId: 193596093
Change-Id: I933020d33db1c158628f14b30c2681c59c86201b
|
|
Bug: 70988915
Test: CompositePhoneLookupTest, PhoneLookupTest
PiperOrigin-RevId: 193592973
Change-Id: I27b6a63049117ce6d31e50aea9c56c14f01d0e1d
|
|
If the disambig dialog would only show one option, just skip the dialog and
place the call directly. Don't save the number as a default entry though
because the contact could potentially change later (become duo reachable, get
another number, ect.)
Bug: 36841782
Test: SpeedDialIntegrationTest
PiperOrigin-RevId: 193555958
Change-Id: Icbb7e876b7a7c5aaa979980249bf074ec1d7a395
|
|
In order to connect SpeedDialUiItems to the correct SpeedDialEntry in the
database, we need to pipe the entry ID throgh to the UI item. So this
change includes the logic to pipe the id as well.
Bug: 36841782,77760800
Test: DisambigDialogTest
PiperOrigin-RevId: 193550938
Change-Id: I6ec64d0aec7f85d36555707a54953bfdff938bb5
|
|
Bug: 70177426
Test: RttTranscriptUtilTest
PiperOrigin-RevId: 193549902
Change-Id: Icb10e44edf32ef7913783628b38861465d0f6c93
|
|
1. default to show first message
2. fix bug that first timestamp is not full format when it's grouped with previous messages
Bug: 70177426
Test: RttTranscriptAdapterTest
PiperOrigin-RevId: 193542992
Change-Id: Ic7a00f1fad8a9305b6fc1111783d589cc7956d58
|
|
This change deletes the AddFavoritesActivity in favor of the activity provided
to us by the Intent.ACTION_PICK intent.
Bug: 36841782
Test: SpeedDialUiItemLoaderTest
PiperOrigin-RevId: 193439522
Change-Id: Ie297abd2307c727d746f26ba99961de116636dc4
|
|
@DialerRootComponent.
Test: local test.
PiperOrigin-RevId: 193435828
Change-Id: Ieb2be7c7d3e2861c0d2f32f1461535e439dbcb1a
|
|
Bug: 70988691
Test: ModulesTest
PiperOrigin-RevId: 193434411
Change-Id: I3fe493eeb2869cad0d42ccf08d57018a42b1b84e
|
|
Bug: 36841782,77724710,77760800
Test: SpeedDialUiItemLoaderTest
PiperOrigin-RevId: 193432314
Change-Id: If9e0aa05b1aeb266960281ac13218091882ff4c3
|
|
telecom/Duo calls.
Bug: 70988691
Test: ModulesTest, DuoCallModuleTest
PiperOrigin-RevId: 193431749
Change-Id: I2af9979504b99175513cb753a030244f735828be
|
|
Test: BluetoothDeviceProviderTest
PiperOrigin-RevId: 193401073
Change-Id: I3483392d1d7a473a753477074b5c377af257186e
|
|
notification
Test: N/A
PiperOrigin-RevId: 193290689
Change-Id: Idff99e2f67d5161d09b7ea3c0818ed92d2286b61
|
|
Use ShortNumberInfo to identify shortcodes and apply more basic matching for them; without this short codes like '5555' and '55555' would match due to being a SHORT_NSN_MATCH even though they should not match.
Also removed the PhoneNumberUtil argument from DialerPhoneNumberUtil's constructor as it was always PhoneNumberUtil.getInstance(). (This allowed me to do a similar thing for ShortNumberInfo.getInstance()).
TEST=unit
Bug: 71586485
Test: unit
PiperOrigin-RevId: 193288929
Change-Id: Ia16c78e7eee5e0912d3913660952b9ee32713731
|
|
TEST=unit
Test: unit
PiperOrigin-RevId: 193288015
Change-Id: I350fa06cb96ff1887c428c8d60c489ddf0da81f6
|
|
Bug: 78132954
Test: listnr
PiperOrigin-RevId: 193279654
Change-Id: I0d6e2e39d2f695b2e7d51ddf8c5abbc689187fbd
|
|
It is not marked "not null" in the system call log and our simulator gives it null data, so handle it more gracefully to be on the safe side.
Also enforce "not null" for IS_READ and NEW in annotated call log as I observed that happening somehow (possibly from older builds though).
TEST=existing
Test: existing
PiperOrigin-RevId: 193271095
Change-Id: I780db20c9d6ea5cf5e1d757def9ea06b492267c1
|
|
Bug: 67596257
Test: CallDetailsCursorLoaderTest
PiperOrigin-RevId: 193259769
Change-Id: I8c6a8eb9a6bf06e9c1c25c45fc035f8db8ae5a65
|
|
The changes in this CL improve the loader in the follow ways:
- Speed: by reducing the number of queries
- Long term accuracy: by using lookup URIs
This change also adds ViLTE presence and contact labels to
the results returned by the Loader.
Bug: 36841782,77724710,77725860
Test: SpeedDialUiLoaderTest
PiperOrigin-RevId: 193235046
Change-Id: If5e6aa821c8bad88dc77af81827abbd8e0f1b28e
|
|
Bug: 77974883
Test: tap
PiperOrigin-RevId: 193225925
Change-Id: I0698abffa232a2e3a575de80642005b454a743ca
|
|
Test: CallLogDatesTest
PiperOrigin-RevId: 193124157
Change-Id: I552bf7fa50142dd51c9a7dda9eaceb7d445607fb
|
|
RTT transcript needs to be loaded after call details is loaded.
Test: OldCallDetailsActivityTest,CallDetailsActivityTest
PiperOrigin-RevId: 193113115
Change-Id: I86e64ac00b17549864ed0778f79ec3aee58b7a1a
|
|
Bug: 70989614
Test: NewCallLogAdapterTest
PiperOrigin-RevId: 193101600
Change-Id: I52b0db9dc03d5e44cad7462403c2639fb33b5f33
|
|
call log.
Bug: 77808449
Test: NewCallLogViewHolderTest + existing tests for the call log framework
PiperOrigin-RevId: 193086917
Change-Id: I39244c69acf1d261699610f6010c0cf147ca3492
|
|
Bug: 77736276
Test: MainActivityOldPeerSearchIntegrationTest
PiperOrigin-RevId: 193081987
Change-Id: I466b6094f4d7851033be3bf68f170485a2ec733d
|
|
Bug: 36841782
Test: manual
PiperOrigin-RevId: 192828773
Change-Id: Id9066346e6b2a03f672ce3ad11027f15adfbb7e6
|
|
Test: tap
PiperOrigin-RevId: 192825959
Change-Id: I814537b08d9afd678c1cb88e6012e60e5511b6bb
|
|
Accomplished by replacing margin with padding.
TEST=manual
Bug: 77812328
Test: manual
PiperOrigin-RevId: 192818386
Change-Id: Iaf58b8460c18259a0472fd154695238c7e93a489
|
|
Bug: 70989614
Test: NewCallLogAdapterTest
PiperOrigin-RevId: 192692744
Change-Id: I42dbb5738558803ad6eae9fe2c2f98b31c49f360
|
|
Bug: 77715083
Test: unit
PiperOrigin-RevId: 192688918
Change-Id: I4448162871ea69ba07c1ed022e9c7daa936dab64
|
|
1. Save RTT transcript when call is destroyed
2. Show RTT transcript link when it's available
Bug: 67596257,77717594
Test: manual
PiperOrigin-RevId: 192673172
Change-Id: If541ad9137c965166548d2fb449e835b95566727
|
|
Bug: 77908301
Test: opened dialpad, didn't crash
PiperOrigin-RevId: 192654487
Change-Id: If5bf9b6df7f15364358fb601d154d4bb99dd5b55
|
|
Bug: 36841782
Test: OldMainActivityPeerTest
PiperOrigin-RevId: 192647371
Change-Id: I3fff1784ce642b86f1e87a27e38737833f74c6b0
|
|
Bug: 36841782,77761023
Test: WIP
PiperOrigin-RevId: 192556602
Change-Id: I50c0baef7ef6c8ae533545567ec797283a9a870f
|
|
Bug: 36841782
Test: SupportUiListenerTest
PiperOrigin-RevId: 192502743
Change-Id: Id06ed732528db1ae486def86ecc2f44828635d81
|
|
Bug: 77717594
Test: ContactPhotoViewTest
PiperOrigin-RevId: 192492913
Change-Id: I6db36017fde2cf9dca580d60d5c88bf2ad2dfe16
|
|
This is for old call log UI.
This change also improves scaling for vector drawable icons.
Bug: 67596257
Test: manual
PiperOrigin-RevId: 192359601
Change-Id: I3322fe08b668f01c1e3a7ce3264c2988e2703aae
|
|
Test: SpamBlockingPromoHelperTest
PiperOrigin-RevId: 192355809
Change-Id: Id9fc792b6e4649af4df588a523299a8fcf7727f0
|
|
Bug: 36841782,77760800
Test: DisambigDialogTest
PiperOrigin-RevId: 192354880
Change-Id: Ie7e9f0e3994d871ce6c90e4028131204ccb0a32a
|
|
This change is mostly just a migration from a cursor loader and
cursor to a listenable future and list of POJOs.
Bug: 36841782
Test: tap
PiperOrigin-RevId: 192349724
Change-Id: I37140dcc2e5e03bc5745573c0d777e18c4f1a880
|
|
the capability is present.
Bug: 70989603
Test: ModulesTest
PiperOrigin-RevId: 192302145
Change-Id: I3162e7d22223aa02709d0d401c70c6fc37a00e3b
|
|
Bug: 36841782,77724716,77725859
Test: implemented
PiperOrigin-RevId: 192191296
Change-Id: I7a22367b33c7555d014a29a2af2942f2eb76c0a5
|
|
SpeedDialUiItemLoader builds a listenable future for returning
a list of SpeedDialUiItems which are the POJO representation of
each speed dial list element.
Bug: 36841782
Test: SpeedDialContentObserverTest
PiperOrigin-RevId: 192186376
Change-Id: I70f3abbeac14117ff4a68355e3a07b395b72386b
|
|
Bug: 70988687
Test: Cp2DefaultDirectoryPhoneLookupTest, PhoneLookupInfoConsolidatorTest
PiperOrigin-RevId: 192085574
Change-Id: I4512c9e2e9e14340fa3aa9b2d7d6aaea6344bba6
|
|
Disambiguates the "this" by adding the reference to settings as required by privacy.
Test: N/A
PiperOrigin-RevId: 191970994
Change-Id: Idc357e8c908b4f54273bf1b2823a6759ea1332b6
|
|
Bug: 77710848
Test: None
PiperOrigin-RevId: 191957734
Change-Id: I0b2674298722a405f4f2e970e877671cff37e60f
|
|
Bug: 75962146
Test: screenshot
PiperOrigin-RevId: 191948101
Change-Id: Icba3cb63cbfe42ce0f193e731dbe2240b3dfc27d
|
|
Bug: 36841782
Test: MainActivityNewPeerTest
PiperOrigin-RevId: 191924314
Change-Id: I5e4a4adadd5477115d6b4daf8afb8c6f819496c8
|
|
Bug: 77586391
Test: manual
PiperOrigin-RevId: 191924178
Change-Id: I792a6f0308f0dde9b4ae82227aa6a8327208a192
|
|
-Moved rootcomponentgenerator/annotations to dialer/inject to reduce the number of deps engineers need to include
-Move rootcomponentgenerator/processor into rootcomponentgenerator/ since the other package is now gone
-Added inject/demo and tests
TEST=unit, tap
Test: unit, tap
PiperOrigin-RevId: 191916595
Change-Id: Ic155808c7435bdce198970caa92309edb9fadac8
|
|
Bug: 77496097
Test: SystemCallLogDataSourceTest
PiperOrigin-RevId: 191845115
Change-Id: Id0d3770e0cd21383cf2f4c5ae5314ca4de258edd
|
|
enabled
Bug: 69072794
Test: Tap
PiperOrigin-RevId: 191824966
Change-Id: Ia219074f32f77f308d88e9c29edb1e56c694bcc7
|
|
@IncludeInDialerRoot in root component generator.
Test: local test.
PiperOrigin-RevId: 191820677
Change-Id: I9df15cccf65e8c51c8fadf57eabec4fd41a51007
|
|
Added status() and audioCallable()
TEST=TAP
Bug: 76430187
Test: TAP
PiperOrigin-RevId: 191767563
Change-Id: I5852b93bd3042f3c6ed8f2155e57fdefe58edd32
|
|
This makes the old peer read the CallLogConfig#isNewVoicemailFragmentEnabled and show the old or new fragment accordingly.
If the user is viewing the NewVoicemail and the CallLogConfig needs to disable the framework, the new fragment is immediately replaced with the old one. This is necessary because if the user were to scroll the fragment, the AnnotatedCallLog database would be read, which would trigger creation.
I tested this by flipping flags and observing underlying data being removed:
> dialer-cmd configprovider set new_voicemail_fragment_enabled false
> adb shell ls /data/data/com.google.android.dialer/databases/ && echo && adb shell cat /data/user_de/0/com.google.android.dialer/shared_prefs/com.google.android.dialer_preferences.xml
I test flipping flags back and forth on the voicemail tab, call log tab and ensuring that they are independent.
Bug: 77601968
Test: unit and manual. Some tests are failing, so to ensure we can have the voicemail ready for the bug bash tomorrow, I've ignored them temporarily but will be fixed in a follow up CL (tracked by b/77601893)
PiperOrigin-RevId: 191738860
Change-Id: I24ca38b862e98324cf802a3020e7e9df31c0b966
|
|
The RemoveView is pushing it around. Since RemoveView and SearchBarView are mutually exclusive, this CL put them into a FrameLayout to avoid position interference.
Bug: 77273749
Test: manual
PiperOrigin-RevId: 191678018
Change-Id: If4000f63c77c9da6794193d389f890d21452dcbf
|
|
Bug: 77484989
Test: TAP
PiperOrigin-RevId: 191677909
Change-Id: If49a357a9ba158cd740eb789befd2ff802f670d4
|
|
- Content description for voicemail button is now "1... double tap and hold to
call vociemail"
- Content description for 0 button is now "0... double tap and hold for plus
symbol"
Bug: 19621015,62712616
Test: manual + a11y office hours
PiperOrigin-RevId: 191673375
Change-Id: I9b5d8d875f1bf218be6fcc33dff4ac9e479e4f43
|
|
Bug: 75972847,77595270
Test: manual
PiperOrigin-RevId: 191672019
Change-Id: I9ea7fb67b4dffeb6acb30840eaf093e4d00a3bcf
|
|
Bug: 74196353,77485680,77486095,77540395
Test: tap
PiperOrigin-RevId: 191666270
Change-Id: I0423735dde42299bf33ea0b8482c03fd3c2d4675
|
|
This change also moved chat history to be saved in DialerCall, thus it will be persist when switching calls.
Bug: 67596257
Test: RttChatMessageTest
PiperOrigin-RevId: 191626079
Change-Id: I65e9c6ac7aa41beb45dfe561b0a48506ea938e6f
|
|
Duo.
Bug: 77535982
Test: ModulesTest + Manual
PiperOrigin-RevId: 191612821
Change-Id: I417b46ed3ec131bf409c427d82f5b2fa6b791054
|
|
Bug: 70988682
Test: ContactPhotoViewTest
PiperOrigin-RevId: 191600243
Change-Id: I60f979241898f1799a57c2401cbddb8975a9caa7
|
|
This should be handled by PhoneAccount.hasCapabilities(PhoneAccount.CAPABILITY_RTT)
Test: none
PiperOrigin-RevId: 191522319
Change-Id: I28244a725c63fb3b83e97fd9a585473a94da96d9
|
|
The fix is to use FutureSerializer instead of synchronizing on the method. FutureSerializer provides the guarantee that the next AsyncCallable won't even be submitted until the ListenableFuture returned by the previous one completes.
Bug: 73877234
Test: added sleep to update task, and verified that resuming activity > 5 times does not deadlock the app
PiperOrigin-RevId: 191494662
Change-Id: I5dc2bed7e117fd3ba5a3cd6a8c39c82a565ce070
|
|
The phone number can be null in the call log (typically for conference calls),
but this wasn't handled properly for calls from non-contacts.
This CL fixes the issue by instead using the display number. PhoneNumberUtils
properly handles null values and can parse the formatted version.
Bug: 77486039
Test: manual :/
PiperOrigin-RevId: 191492307
Change-Id: I1be427b3f4ed1381bea3943d130256618f730f5d
|
|
Bug: 77513242
Test: None
PiperOrigin-RevId: 191470111
Change-Id: I0220a342dc1ff04f247ad09dc1fc308f61bbe80c
|
|
Bug: 76445204
Test: manual
PiperOrigin-RevId: 191470043
Change-Id: I8d57331b2fbeff358535d92852d6bbb2ac677613
|
|
Test: unit
PiperOrigin-RevId: 191380073
Change-Id: If554d5ee0c55754802692a364bae591c3951c060
|
|
the new call log.
Test: CoalescerTest
PiperOrigin-RevId: 191376690
Change-Id: Id5939175edddd164a1b477319fb20e6d2a9671a9
|
|
Bug: 70988685
Test: DuoCallModuleTest, PlaceDuoCallEndToEndTest, Manual testing
PiperOrigin-RevId: 191372706
Change-Id: I439be71c361eaca722820b81278e5f95322e100c
|
|
@DialerCompoennt. Delete related tests.
Test: On a local device.
PiperOrigin-RevId: 191365675
Change-Id: Ia90463b936f3f07df99909c463b2bdb51223fbe6
|
|
We want to be more consistent with other usages of NEW in the app, i.e. NEW should be used primarily by notifications.
Bug: 74821515
Test: unit
PiperOrigin-RevId: 191139559
Change-Id: Ib6fbead8b5589aedd881db26a07f7daed4d83543
|
|
This button has higher priority over add call button if RTT is enabled.
Bug: 67596257
Test: ButtonChooserIntegrationTest
PiperOrigin-RevId: 191129313
Change-Id: I5a3302a0970e77a933439749e0e559a691235523
|
|
Bug: 36841782
Test: SpeedDialEntryDatabaseHelperTest
PiperOrigin-RevId: 191121137
Change-Id: Iab712d5fac56e515bd4e977282656bf80db4337d
|
|
Bug: 70989667
Test: unit
PiperOrigin-RevId: 191099351
Change-Id: I47f1e487e2a0cc23af7b39ae89e20abf993933ea
|
|
Also use a flag to control the threshold at which we process invalid numbers.
Bug: 70989667
Test: unit
PiperOrigin-RevId: 191095892
Change-Id: Idb424831d637ae44e5e5915afaf59c3d534ce4a0
|
|
Old blocking is deprecated.
Bug: 70989544
Test: TAP
PiperOrigin-RevId: 191086875
Change-Id: Icde4963fce603fc4e16e486b78c070bd439e26e4
|
|
new UI.
Bug: 70988686
Test: CallLogEntryTextTest
PiperOrigin-RevId: 191071267
Change-Id: I392e3b4c47e266f0a553fe28079d4800fc174a8f
|
|
availability check
Checking donation is not a simple config check, but everything that donation availability is dependent on via the isVoicemailDonationAvailable() helper method. We update the code accordingly.
When the user declines the promo for donation, we should also update the toggle accordingly.
Bug: 74033229
Test: N/A
PiperOrigin-RevId: 191011808
Change-Id: I6e4ff9914355deed72175179fc7b9009f2395ef5
|
|
Bug: 77242856
Test: N/A
PiperOrigin-RevId: 191002650
Change-Id: Ia74423f28a40f148d507fb9f907fc2e5c41fc183
|
|
- back arrow in search now flips in RTL mode http://screen/1eccBLDqPp0
- search text no longer overlaps icons http://screen/Mq0omQEuZez
- keyboard now always closes on pause
- location permission is no longer visible in dialpad search
Bug: 73088433,74784637,76117373,76440832,76441216
Test: keyboard and rtl tested manually, added test for location permission
PiperOrigin-RevId: 190981686
Change-Id: Ia121d410c158df0de9cd731ab280a6d8e9b300d9
|
|
Bug: 76221932
Test: manual
PiperOrigin-RevId: 190948113
Change-Id: I4151ab3fc5231183d49fc1bdc247a09e5ffadc22
|
|
Bug: 70988682
Test: Existing tests
PiperOrigin-RevId: 190946639
Change-Id: Iaa8294e8ba6e85ab3c27bb2e67200d7972a240f2
|
|
Bug: 65490850
Test: manual
PiperOrigin-RevId: 190859631
Change-Id: I89aeb41a7709e9366367cdc54ba506e276685b5f
|
|
optional badge.
Bug: 70988682
Test: ContactPhotoViewTest
PiperOrigin-RevId: 190855440
Change-Id: Ib658efa6486b66548c710804049517905dc67b13
|
|
Bug: 75308663
Test: N/A
PiperOrigin-RevId: 190825933
Change-Id: Iaf112cfec81c82e127d77aedba351788a03eee54
|
|
Test: Existing tests
PiperOrigin-RevId: 190820867
Change-Id: I4835bcbc7698075fb54015dccc6823ada4c71651
|
|
System blocking should be used instead. These code are obsolete.
Bug: 70989544
Test: TAP
PiperOrigin-RevId: 190818334
Change-Id: I71475905ba110fdc0560991a2a9c2b9e2f2de9f2
|
|
When a user accepts the Dialer ToS for the first time, we should also enable transcription if it is available.
Bug: 74033229
Test: N/A
PiperOrigin-RevId: 190794147
Change-Id: I7eb9b3d481426aceb55a8990fdbd246101937e7b
|
|
When a user declines the transcription, we should turn off transcription and never show the transcription promo ever again.
Bug: 74033229
Test: N/A
PiperOrigin-RevId: 190790323
Change-Id: Ida60592b0550b18b28e7f7a7a22d19100f56231a
|
|
Bug: 70988682
Test: NewCallLogViewHolderTest
PiperOrigin-RevId: 190783830
Change-Id: Ib0b1ec23b7c278b83516019924b6c68ff12adaf9
|
|
This makes the old peer read the CallLogConfig#isNewCallLogFragmentEnabled and show the old or new fragment accordingly.
If the user is viewing the NewCallLog and the CallLogConfig needs to disable the framework, the new fragment is immediately replaced with the old one. This is necessary because if the user were to scroll the fragment, the AnnotatedCallLog and PhoneLookupHistory databases would be read, which would trigger creation.
I don't expect this to be a common case because 1) we hopefully never have to disable the framework and 2) Framework is only updated on Phenotype broadcasts and JobScheduler jobs, which hopefully don't typically happen when user is viewing the call log. However, I still want to make sure that if it happens we don't irreversibly break users when we turn the framework back on.
I tested this by flipping flags and observing underlying data being removed:
> dialer-cmd configprovider set new_voicemail_fragment_enabled false
> adb shell ls /data/data/com.google.android.dialer/databases/ && echo && adb shell cat /data/user_de/0/com.google.android.dialer/shared_prefs/com.google.android.dialer_preferences.xml
I test flipping flags back and forth on the call log tab, speed dial tab, and while the activity was paused (pressing Home after viewing call log).
Note that this CL doesn't address showing missed calls and badge counts correctly with the new fragment; that will come in a later CL.
Bug: 74821995
Test: unit and manual
PiperOrigin-RevId: 190706481
Change-Id: I618d9c1649169abd65733502cfebc662a835e787
|
|
ConfigProvider should not be used directly for reading NUI flags as CallLogConfig needs to perform work when they change.
Bug: 74821995
Test: existing
PiperOrigin-RevId: 190698415
Change-Id: Ic084d9032d2a6f35ffba9f395eaaff9053cfa262
|
|
transcription is available.
Also updated the isVoicemailAvailable helper method, since just checking if the flag and OS is not enough (we have other things such as is VVM enabled, is VM activated), if we don't do this, it doesnt make sense to turn on transcription e.g Why what would happen if transcription is turned on but vvm is disabled
Bug: 74033229
Test: Added a todo, will be added later (there are a few more similar CL's that I am sending for other ToS conditions) to ensure the logic is correct for all ToS conditions first and I can add a test right at the end for all conditions.
PiperOrigin-RevId: 190696695
Change-Id: I9cb063a97e11943abeb1f823dc661efe88dfa3f1
|
|
When an existing dialer user is shown the ToS and they declines it, the transcription setting must be turned off, to respect the users wishes.
We also no longer take the user to the settings page.
Bug: 74033229,77147114
Test: Unit test
PiperOrigin-RevId: 190682249
Change-Id: I8c0abf9f3cbb15ded12a760abe540c557fd2e7d3
|
|
Test: N/A
PiperOrigin-RevId: 190673495
Change-Id: I1587449f6b0b53e7a16aac0b334225649a94f27b
|
|
Bug: 76445204
Test: n/a
PiperOrigin-RevId: 190650130
Change-Id: I594a16676cfcca4e6a10c1f5bc6604509417ad23
|
|
Adds the we can turn off transcription from settings.
Bug: 76226374
Test: N/A
PiperOrigin-RevId: 190626638
Change-Id: I22b56f133cc83749cdd52a4406be0c36c5a0d0ac
|