- 13 Oct, 2016 1 commit
-
-
Tyler Gunn authored
When a call switches technology between CDMA and GSM, the TelephonyConnectionService will end up re-adding it to the appropriate conference controller due to the original connection change. This is problematic, as it means that the connection will still be tracked by the conference controller of its previous technology. Worse yet, if a call makes a GSM-->CDMA-->GSM transition, it will be added again to the GSM call tracker. There is still an underlying issue in that the TelephonyConnection subclass type doesn't change when the radio technology changes -- that is a larger issue to solve and should be addressed at some point (ie not now). To fix this, added code to ensure that connections are removed from other conference controllers when added, and also to prevent adding duplicates. Bug: 31288401 Change-Id: I5e95d4f72be6af473eeec1b92f47ad77a783c9b2 (cherry picked from commit be89962c)
-
- 12 Oct, 2016 1 commit
-
-
gitbuildkicker authored
-
- 10 Sep, 2016 1 commit
-
-
Tyler Gunn authored
When a call switches technology between CDMA and GSM, the TelephonyConnectionService will end up re-adding it to the appropriate conference controller due to the original connection change. This is problematic, as it means that the connection will still be tracked by the conference controller of its previous technology. Worse yet, if a call makes a GSM-->CDMA-->GSM transition, it will be added again to the GSM call tracker. There is still an underlying issue in that the TelephonyConnection subclass type doesn't change when the radio technology changes -- that is a larger issue to solve and should be addressed at some point (ie not now). To fix this, added code to ensure that connections are removed from other conference controllers when added, and also to prevent adding duplicates. Bug: 31288401 Change-Id: I5e95d4f72be6af473eeec1b92f47ad77a783c9b2 (cherry picked from commit be89962c)
-
- 26 Aug, 2016 3 commits
-
-
gitbuildkicker authored
-
Sailesh Nepal authored
Orange (23434) was supposed to be removed a while ago. See b/29416060. EE needs to be removed for b/31004603 and b/30085854. Bug: 31004603 Change-Id: I6d1af749f3e6e63aa801d155e9bcfd45f79a3b84
-
gitbuildkicker authored
-
- 25 Aug, 2016 1 commit
-
-
Sailesh Nepal authored
The VoicemailChangePinActivity code would crash if the activity was torn down before the async task finished. Fix was to check the activity state before calling Dialog.dismiss(). Bug: 31068693 Change-Id: I0089f13ab8f0cc88b960b6733ba6176f77ce57fa
-
- 23 Aug, 2016 2 commits
-
-
gitbuildkicker authored
-
Ta-wei Yen authored
With ag/1338663 ACTION_VOICEMAIL_SMS_RECEIVED will still be sent if the message body matches the carrier regex but is not parsable. Currently the client does not understand anything else and it is unlikely to be sent by real servers so just ignore it. Bug: 30954955 Change-Id: I31ecd9fb0cfb79a6ac99bd272752c7dc15890ab6 (cherry picked from commit 45bbf2c9)
-
- 22 Aug, 2016 1 commit
-
-
gitbuildkicker authored
-
- 18 Aug, 2016 1 commit
-
-
gitbuildkicker authored
-
- 17 Aug, 2016 3 commits
-
-
Ta-wei Yen authored
-
Ta-wei Yen authored
Previously MWI will be suppressed if the notification channel state (phone signal) is active. This will only work if VVM is fully active or fully disabled. In VVM3 there is a new state that the VVM client is enabled but the carrier has blocked the service. The notification channel state will be active, but VVM SMS will not be sent and MWI will continue as usual and mistakenly be suppressed by VVM client. After this CL, instead of checking the notification state to suppress MWI, the configuration state which determines if the service is actually active will be used. Change-Id: Id55a88ff3c188113f1f40f56503d2b61dd5c0c40 Fixes: 30883795
-
gitbuildkicker authored
-
- 16 Aug, 2016 7 commits
-
-
Brad Ebinger authored
-
Brad Ebinger authored
The CNAP name is now filtered based on a String array that is defined in the CarrierConfig. This filtering helps remove caller id information that is not useful, such as "WIRELESS CALLER" and "UNKOWN NAME". Bug: 30142293 Change-Id: Ic59dc984b61277fad53d88db5b4cce6f67989c8c
-
Tyler Gunn authored
-
TreeHugger Robot authored
-
gitbuildkicker authored
-
Bill Yi authored
Change-Id: I34ccb71fe078e448467f94869b02306991d8c50b Auto-generated-cl: translation import
-
Tyler Gunn authored
-
- 15 Aug, 2016 1 commit
-
-
Ta-wei Yen authored
-
- 14 Aug, 2016 1 commit
-
-
gitbuildkicker authored
-
- 12 Aug, 2016 4 commits
-
-
Ta-wei Yen authored
Previously the dirty state is cleared by marking the voicemail as read again. This confuses the VoicemailContentProvider. Sending a update with no values is enough to clean the flag. The dirty flag is used to track external changes like read flag that should be uploaded to the server. + Reverts ag/1314867, the "new" column is not updatable through the VoicemailContentProvider Change-Id: I17a3c50622d98397fd27dc1097c15219fcd1196c Fixes: 30105817
-
Tyler Gunn authored
Bug: 30702393 Change-Id: I8979ac32e2ba94656239c6d8939d609bd3896302
-
Tyler Gunn authored
Per bug, the new UX requires the "Incoming Wi-Fi call" text to be "Wi-Fi call from". Bug: 30828844 Change-Id: I3d4797f04f6f907c5b6e3607ffcaab169e0eacbb
-
Tyler Gunn authored
-
- 11 Aug, 2016 7 commits
-
-
TreeHugger Robot authored
-
Bill Yi authored
Change-Id: I9ae799cb895e136b3fe348ac3267bb038828f0a4 Auto-generated-cl: translation import
-
Ta-wei Yen authored
The voicemail notifications are tracking new voicemails. Once the voicemail is set as read on the server it should no longer be treated as new. Change-Id: I503a8f0eae3aece5388ce8586082b7613ffebd72 Fixes: 30105817
-
Tyler Gunn authored
Bug: 30702393 Change-Id: Ie3c3697ce021808469d08f52d353fbdc9524ec19
-
Ta-wei Yen authored
This CL allows the default dialer/apps with carrier privileges/apps with MODIFY_PHONE_STATE permission enable or disable the visual voicemail client. + Fix the bug where the configuration state error was not cleared for subsequent activation due to the edit was not applied. Bug: 30709089 Change-Id: Ie3e4a8b48a6862e10b7381520d07d0f879b1884b
-
Ta-wei Yen authored
-
gitbuildkicker authored
-
- 10 Aug, 2016 3 commits
-
-
Brad Ebinger authored
-
Brad Ebinger authored
The original assumption that a participant's endpoint is unique is invalid. Instead, we now key on a Pair containing both the User and Endpoint Uris of a conference participant. Bug: 30777779 Change-Id: I2bc7b1a694ddbdb18284e28bbf31dacff5c0d679
-
gitbuildkicker authored
-
- 09 Aug, 2016 3 commits
-
-
Tyler Gunn authored
-
gitbuildkicker authored
-
gitbuildkicker authored
-