summaryrefslogtreecommitdiff
path: root/java/com/android/voicemail/impl
Commit message (Collapse)AuthorAgeFilesLines
* Add FLAG_IMMUTABLE to PendingIntent in LegacyModeSmsHandler.Varun Berry2021-10-291-2/+2
| | | | | | | Bug: 185126549, 185126319 Test: manual. Change-Id: I1024353434674f8e4bf164c3a6c1e16924dfaa8f
* Add a permission to guard receiving intents in StatusSmsFetcher.Varun Berry2021-10-291-2/+9
| | | | | | Bug: 186405146 Test: manual. Change-Id: I98e9c3ed64829d00ce3ce685108b076110741401
* Remove PhoneAccountHandle when building the intent to call Voicemail.Varun Berry2021-10-281-1/+1
| | | | | | | | | This will break functionality for calling voicemail in a multi-sim device. Bug: 197228468 Test: manual. Change-Id: If4463a24af2feb23d033190236e314b535d10fd6
* Wait for IPv4 before sending VVM requests.Wei He2021-06-013-1/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | Precondition to reproduce: - Attached to a network where IPv6 arrives before IPv4 - WiFi is On - Mobile always-on is Disabled (that's default setting) - VVM server is IPV4 only What happened: - VVM sync failed with DATA_CANNOT_RESOLVE_HOST_ON_NETWORK Root Cause: - With above precondition, there will be >50% possibility that when App requests Cellular Data Network, IPV6 address will be reported a few millis before IPV4. This is causing the App to try using IPV6 address (when IPV6 comes first) to query the VVM Server DNS and as the VVM Server is an IPv4 one, it's possible to stabilish a route. Solution: - When App requests Cellular Data Network, if IPV6 network address arrives first, just wait up to 0.5 sec to do DNS query, so we're sure there's enough time to IPv4 address to be available. Bug: 183967989 Change-Id: I8af48b71ec9d6699f604a9db87bb0a77fa4379ca
* Merge Android R (rvc-dev-plus-aosp-without-vendor@6692709)Xin Li2020-08-271-196/+0
|\ | | | | | | | | | | Bug: 166295507 Merged-In: Ic08b97c9660daee8bd69db381ea55234d37a0106 Change-Id: Ib83cd87683ae896de789cdf6cd0c801562a191d5
| * Merge "Dialer: Fix proto warning with optmize for lite" am: c251a5b0e9 am: ↵Treehugger Robot2020-05-131-1/+0
| |\ | | | | | | | | | | | | | | | 33e47c33df Change-Id: Icdbfb2971525d130223ac7a43bf3fec8304c13d5
| * | Remove VVM configs from AOSP Dialersamalin2019-04-111-196/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | AOSP VVM configurations were historically stored in AOSP as VVM support was part of the platform. This is no longer the case, old VVM configurations are being removed and individual OEMs will now be required to provide their own configurations. Bug: 129867522 Test: make Change-Id: I299bba40548e557c9802d8241b7168e8c1a3f5e9
* | | Update language to comply with Android's inclusive language guidanceTyler Gunn2020-07-295-12/+13
| |/ |/| | | | | | | | | | | | | See https://source.android.com/setup/contribute/respectful-code for reference Test: Presubmit Bug: 161896447 Change-Id: I2cd36fd5148608caec816c159c1b5d6bfbe192bc
* | Dialer: Fix proto warning with optmize for liteLuca Stefani2020-05-011-1/+0
|/ | | | | | | | | | * option optimize_for = LITE_RUNTIME is ignored in proto 3+ * Instead we should use the java_lite compiler via the LOCAL_PROTOC_OPTIMIZE_TYPE flag which defaults to lite in java projects Test: m Dialer, no warnings Change-Id: I552f5895bbe8192a4ae870bb48e5ef6a9e7e8c78
* Update translation strings.Eric Erfanian2018-07-10164-5412/+410
| | | | | Test: make Change-Id: Ib75f4f25e91067311de244d7f1fb95bc898aec22
* Strip +1 when subscribing to VVM3twyen2018-06-291-6/+19
| | | | | | | | | | The self provisioning gateway expects 10 digit US national number. TEST=manual, VVM subscription cannot be automated. Bug: 110390254 Test: manual, VVM subscription cannot be automated. PiperOrigin-RevId: 202695056 Change-Id: I9368a4e04d50f4a402d994f7bef3fb1e4b654940
* Remove redundant @TargetApi, @RequiresApi and @SuppressWarningslinyuh2018-06-289-14/+3
| | | | | | Test: Existing tests PiperOrigin-RevId: 202589482 Change-Id: I6982e4069d30032bf46caf3c9984dfc0e7196f6f
* Post CONFIG_SERVICE_NOT_AVAILABLE if VVM provisioning failedtwyen2018-06-261-0/+1
| | | | | | | | | | this will show the "Can't active visual voicemail" message TEST=TAP Bug: 110390254 Test: TAP PiperOrigin-RevId: 201979303 Change-Id: I265dcc616ae6f14e00ae20ce2ea914d3c3b85a49
* Handle alternative form VVM SMS as legacy notification if the account is not ↵twyen2018-06-113-1/+23
| | | | | | | | | | | | activated yet. On VVM3 if subscription failed, the alternative form SMS will still be sent by the carrier. In this state dialer should fallback to legacy voicemail notification. TEST=manual - disable auto subscription in code, check legacy voicemail notification functionality. Bug: 109896901 Test: manual - disable auto subscription in code, check legacy voicemail notification functionality. PiperOrigin-RevId: 200113818 Change-Id: I55b70e7a8b2cd3d8b40864fa03b2ba209037f4e8
* Handle null carrier config for emergency call hinttwyen2018-06-051-0/+3
| | | | | | | | | | | | getCarrierConfig() is @Nullable. While the default implementation always return a bundle, this is not true for other carrier apps. ShadowTelephonyManager.getCarrierConfig() now return null as default to catch this behavior. TEST=TAP Bug: 80629471 Test: TAP PiperOrigin-RevId: 199327865 Change-Id: I7416bee3d5f5307919c6825fc74c26f25b6b001f
* Fix assert when disabling VVMtwyen2018-06-041-20/+17
| | | | | | | | | | The SIM may no longer be valid, but the rest of the deactivation process should still go through. TEST=TAP Bug: 79476712 Test: TAP PiperOrigin-RevId: 199174445 Change-Id: I52d6030320f2675ac74fc06470e3cd8f33b613b8
* Inlined ConfigProviderBindings.get() and removed ConfigProviderBindings.zachh2018-06-014-18/+33
| | | | | | | | | It no longer provides any value, so just use dagger directly. Bug: 80441695 Test: tap PiperOrigin-RevId: 198806461 Change-Id: Id607abb65b77633bce511ad0c943ac19453a85d5
* Handle invalid PhoneAccountHandle for CarrierIdentifiertwyen2018-05-182-23/+29
| | | | | | | | | | Previously the phoneAccountHandle is validated before creating the CarrierIdentifier, but it seems like there's a chance that it would be invalidated in the gap before the identifier is created. TEST=TAP Bug: 73890027 Test: TAP PiperOrigin-RevId: 197172168 Change-Id: I6f4f77819ed6ce9f3449f7e47a3538af1098d826
* Add @InstallIn and @IncludeInDialerRoot to dagger modules in dialer codebase.weijiaxu2018-05-111-0/+3
| | | | | | Test: presubmit. PiperOrigin-RevId: 196158524 Change-Id: Iec1e457039e97be0236cd700d397b4095ee3c2c3
* Remove voicemail/impl/TelephonyMangerCompattwyen2018-04-163-124/+19
| | | | | | | | | | These reflection calls are used for the transition period when amending VVM APIs in O. The public version should be used now. TEST=TAP Bug: 77334965 Test: TAP PiperOrigin-RevId: 193095281 Change-Id: Ifaf2e78f007a155221146b40369aaed66d4325c6
* Ignore case for GID matchingtwyen2018-04-111-1/+1
| | | | | | | | TEST=TAP Bug: 77838297 Test: TAP PiperOrigin-RevId: 192534802 Change-Id: I9c6b0aaab33f5ae5e9d26131c7a9a2858005c385
* Add Tracfone VZW GID to vvm_config.twyen2018-04-101-0/+1
| | | | | | | | TEST=Manual Bug: 77838297 Test: Manual PiperOrigin-RevId: 192343100 Change-Id: I2f054d432c54359b99dcf4e15d9059abdda91293
* Disable transcrption downloads for T-Mobile.twyen2018-04-023-15/+28
| | | | | | | | | In this CL, the client will stop treating text/* attachments as transcrptions for T-mobile. Transcriptions are already disabled by the device type sent during provisioning so this will not affect any existing functionality. This prevents other data on the server showing up as transcription. Bug: 77342321 Test: TAP, exact behavior not testable. PiperOrigin-RevId: 191350836 Change-Id: I758996c3fef75ece7cecf0f7a0b4df7ace970d80
* Use existing transcription from transcription server if availableuabdullah2018-03-293-1/+20
| | | | | | | | | Repeated requests from the server responds in an ALREADY_EXISTS error and does not transcribe the voicemails. In that case we should ask the server if the request is present already on the server, and if so retrieve it. Bug: 77236260 Test: N/A PiperOrigin-RevId: 191016332 Change-Id: I605c546a3bec3599c7b162853463ca7e46f63886
* Update what happens when donation is rejected & use correct donation ↵uabdullah2018-03-291-1/+3
| | | | | | | | | | | | | 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
* When transcription setting is enabled, retranscribe voicemailsuabdullah2018-03-274-4/+28
| | | | | | | | | When transcription toggle is turned off, we delete all local transcriptions. However when it is turned back on, we should re-transcribe all those( previously transcribed, then deleted) voicemails again. Bug: 74033229 Test: N/A PiperOrigin-RevId: 190640972 Change-Id: Iaaf324e74c7630852daeb314f34c2c3095fe3196
* Catch BadParcelableExceptiontwyen2018-03-264-8/+38
| | | | | | | | | | | This happens when an old dialer submitted a job and the newer dialer is trying to handle it. The class fingerprint changed so it can no longer be unparceled. In this CL, such tasks will be dropped. Bug: 64225192 Test: N/A PiperOrigin-RevId: 190491751 Change-Id: I90fe2d24a435201cfae09970387e9b1c3a58b094
* Delete locally transcribed transcripts when transcription is turned off.uabdullah2018-03-262-12/+73
| | | | | | | | | When a user turns off transcription setting we should delete all the voicemails locally transcribed by google. We do this by deleting all the transcripts associated with the source package of the app. Bug: 74033229,76167428 Test: Unit Test PiperOrigin-RevId: 190159353 Change-Id: I328aece594aa0e66de59e43fa3619b5e9ae15f78
* Increase minSdk to 24.calderwoodra2018-03-263-3/+3
| | | | | | | | | | | | | | | | Manually set to M - MissedCallNotifierTest (not sure what the issue is here...) - CallLogGroupBuilderTest (because a check was removed, some NPEs are thrown) - MainSearchControllerTest (/system/etc/fonts.xml (No such file or directory)) Ignore Tests - a few random ones in incallui/answer/impl/hint (shared prefs aren't working for some reason) - VisualVoicemailUpdateTaskTest (disabled the whole test, issue unclear) Bug: 73902692 Test: tap PiperOrigin-RevId: 190030202 Change-Id: I1e9b61d758a61582c5a183ee884dd2181d1c10de
* Refactor VM Settings and add support for voicemail transcriptionuabdullah2018-03-163-20/+93
| | | | | | | | | | | | | | | This CL refactors the existing voicemail settings fragment and adds UI support for voicemail transcription. It mainly deals with the following: - ensuring that when the VVM toggle is turned off, transcription and donations are gone. - when transcription is off, donation preference is gone. - donation is only available when transcription is available and enabled - as part of the refactor, fixes existing logging bugs - breaks preferences and its associated methods into helper methods when possible - groups relevant preferences together when possible Bug: 74033229 Test: Unit tests PiperOrigin-RevId: 189418217 Change-Id: I3442cb5752a235cfca643ba55df3fb75171e3fe4
* Move HIDE_VOICEMAIL_SETTINGS_MENU out of voicemail/impltwyen2018-03-121-4/+0
| | | | | | | | | | | The metadata belongs with the voicemail settings menu, which is moved into dialer a while ago. Not moving the metadata causes build variants without VVM to have duplicated voicemail settings in telephony and dialer. Also removed the redundant metadata in incall ui manifest. Bug: 73096806 Test: manual PiperOrigin-RevId: 188756468 Change-Id: I00174f84024c5b9ab809d99e40a55d22a07bd063
* Prevent VVM subscribing when carrier reset subscription statustwyen2018-02-234-8/+21
| | | | | | | | | | | | | On VVM3 when the user upgrade to premium VVM through the carrier, the carrier will actively send STATUS SMSes first indicating the status is unknown, then the new premium status. STATUS updates sent by the carrier were ignored until recently. Currently seeing the unknown status the provisioning process will be triggered, and the user will be downgraded back to basic VVM. In this CL if the STATUS update is initiated by the carrier instead by a STATUS request, provisioning will be ignored. Bug: 73625577 Test: N/A PiperOrigin-RevId: 186737242 Change-Id: Ieb10f9a50e0c3001d02cefc31256a9adac1ae5d1
* Disable VVM for tracfone USAtwyen2018-02-221-0/+15
| | | | | | | Bug: 72666573 Test: Updated unit test to match the real case PiperOrigin-RevId: 186376740 Change-Id: If1523963a03f89d6699ef89c8b82c4f22c04d039
* Support GID1 for VVM configstwyen2018-02-094-25/+228
| | | | | | | | | | | This CL allows VVM configs to be specifed with Group identifier, which takes precedence over configs with only MCC/MNC. TelephonyVvmConfigManger is renamed to DialerVvmConfigManger. It was created when VVM was still in telephony, and need to separate itself from the CarrierConfig app. Bug: 72666573 Test: Unit tests PiperOrigin-RevId: 184924155 Change-Id: Ic71e99ed2b3015eed87dfb7e111538ff3b744206
* Add VVM Config for Bouygues FRtwyen2018-02-091-0/+15
| | | | | | | Bug: 72647204 Test: Tested by Bouygues PiperOrigin-RevId: 184914101 Change-Id: Ic7dec5ee33a959751062127ab010dc79f6fb2bae
* Fullly disable VVM if carrier VVM app is installed.twyen2018-01-314-43/+10
| | | | | | | | | | | Previously it is only disabled when the user has not changed the VVM settings, and the user can still re-enable it. After this CL, VVM will always be disabled, and the settings will be hidden. Bug: 72668279 Test: Unit tests PiperOrigin-RevId: 184063245 Change-Id: I42c12f3fd2f3e397158e08b26875a7e99a766d33
* Use application context when fetching shared prefs.zachh2018-01-292-3/+3
| | | | | | | | Using non-application contexts incurs extra disk access because shared prefs are cached per context. Test: manually ejected sim and observed no strict mode violations PiperOrigin-RevId: 183739285 Change-Id: I9337e226ae1e060478219cf495752ceccf5a31e6
* Prevent VvmNetworkRequestCallback from releasing twicetwyen2018-01-251-5/+11
| | | | | | | | | It is unclear from the docs or implementation what callbacks are invoked when the network is lost, or does the system release the callback for us somewhere else. In this CL VvmNetworkRequestCallback.releaseNetwork() will be guarded from calling twice, and log levels for callbacks are raised. Bug: 64243619 Test: N/A, repro steps unknown. PiperOrigin-RevId: 183298754 Change-Id: I5e589b2b59478b270890056fa08abb306ee1600c
* Make sure that voicemail transcriptions are processed seriallymdooley2018-01-145-18/+124
| | | | | | | | | | | | | | | | | Since we are now using the AlarmManager to decide when to poll for voicemail transcriptions, we need to ensure that we don't start transcribing a voicemail until polling for the previous one ends. This cl postpones a voicemail transcription task if there is an alarm set to poll for a transcription result. After a transcription result is received (or we give up) the db is scanned for any pending transcriptions and the next one is started. Bug: 70242961 Test: manual and updated unit tests PiperOrigin-RevId: 181899975 Change-Id: I7b8fb696164980cf710aa58a79418c6954e2b4d2
* Remove field prefixes.linyuh2017-12-2763-1390/+1389
| | | | | | Test: Existing tests PiperOrigin-RevId: 180230450 Change-Id: I0b2589cfeeaef81e42a04efa48af24b4e4d0e95f
* Change dt for CVVM to 6twyen2017-12-141-2/+2
| | | | | | | Bug: 70243393 Test: N/A PiperOrigin-RevId: 179064288 Change-Id: Id8b2e600ae00edbe2697932ad2d9fe78ea4430b5
* Cleanup. Changing voicemail_transcription_enabled to ↵mdooley2017-12-123-5/+6
| | | | | | | | | | | | | voicemail_transcription_available Follow the convention that features allowed by server configuration flags use the word 'available' and when a feature is allowed by the user via settings then use the word 'enabled' Bug: 37340510 Test: manual and updated unit tests PiperOrigin-RevId: 178831467 Change-Id: I5691fd7db45a70908d32cdac2b049fe76e6a0680
* Allow VVM activation to be rerun if carrier sent STATUS SMStwyen2017-12-072-3/+5
| | | | | | | | | Carrier might send STATUS SMS actively if the account configuration has changed. Previously it will be discarded if the account is already activated. In this CL activation will be rerun if the messageData already exist since it is initiated by an STATUS SMS. Bug: 69857261 Test: ActivationTaskTest PiperOrigin-RevId: 178028542 Change-Id: I6d103569c2be4eeadc3a7877d160fff03ad8b40e
* Delete voicemails when disabling visual voicemailmdooley2017-11-299-5/+78
| | | | | | | | | | | | | | For privacy reasons we now delete all voicemails and transcriptions when the user disables visual voicemail, (after confirming that they want to do this via a dialog). Note: we only delete voicemails whose source package is the google dialer. Note: the voicemails will be re-downloaded and re-transcribed if the user re-enables visual voicemail Bug: 69323147 Test: manual and unit test PiperOrigin-RevId: 177315139 Change-Id: Ie04496dc5960b485794733fbf74f7f704e806023
* Switching to alarms and exponential backoff while polling for transcription ↵mdooley2017-11-295-103/+315
| | | | | | | | | | | | | | | | result This cl switches the way asynchronous transcription tasks poll for their results. it has been observed that sometimes the server side transcription takes longer than expected (sometimes many minutes), so instead of blocking a thread for all that time this cl schedules an alarm for the next time to poll. it also uses an exponential backoff scheme to determine the poll times and increases the maximum total polling time from 20 seconds to 20 minutes. Bug: 66966157 Test: manual and unit tests PiperOrigin-RevId: 177257577 Change-Id: Ib2998f03cc418d5241ccffec71ba3945c9fe4cbc
* Adding transcription rating feedbackmdooley2017-11-289-24/+338
| | | | | | | | | | | | | Allow users who have agreed to donate their voicemails to also provide transcription quality feedback. screenshot: https://drive.google.com/open?id=0B9o_KvtLkcuIajVtdFN3Y0Qydmx2NXJYN2N3OVA3N0h5UEdR Bug: 68712148 Test: manual and new unit tests PiperOrigin-RevId: 176774942 Change-Id: I08b9afbbefaedfb0de5199038a1d2769bd983855
* Force disable VVM if carrier app is preloadedtwyen2017-11-211-1/+37
| | | | | | | | | This CL checks if the carrier app is installed on the system image. If so, VVM will be force disabled (user can't turn it on, can't even see the switch as if they are on a unsupported carrier). Otherwise, VVM will only be disabled by default if the carrier app is present (User can still turn it on in settings). Bug: 67496592 Test: OmtpCarrierConfigHelperTest / manual - move carrier app to /system/app PiperOrigin-RevId: 176586849 Change-Id: Idf79bdf61c600423062ca54d1b4c6e77cfcd8033
* Refactoring and adding TOS check before transcribingmdooley2017-11-183-14/+118
| | | | | | | | | | | | This cl just adds a check before starting a transcription job to verify that the user has accepted the appropriate TOS. Its a rather big cl just because it had to expose some TOS acceptance details that were previously encapsulated in the VoicemailTosMessageCreator. Bug: 69267260 Test: manual and unit tests PiperOrigin-RevId: 176132370 Change-Id: Ic28fb197a07f9df7a9b5f1729c84566cba0890fc
* Don't transcribe voicemail unless carrier allows OTT transcriptionmdooley2017-11-184-31/+57
| | | | | | | | | | Added a carrier config and check to see if the carrier allows over the top voicemail transcription, and if not do not attempt transcription. Bug: 68951869 Test: manual and unit test PiperOrigin-RevId: 176065849 Change-Id: I69df1f2867420d7fdcc7f0a31e0e6c26da67abb1
* Hook up pre-call actionstwyen2017-11-111-3/+5
| | | | | | | | | This CL replaces all instance of CallIntentBuilder.build() with PreCall.getIntent(), which when run as an activity, will finish building the intent with user interaction. Bug: 64216442 Test: manual PiperOrigin-RevId: 174924323 Change-Id: If41868df4c7ed078d03bd3431fa85b8947056a01
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-07 21:47:39 +0000