1. 13 Oct, 2016 1 commit
    • Tyler Gunn's avatar
      Cleanup Connections in conference controllers on CDMA<-->GSM change. · 45e0fc27
      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)
      45e0fc27
  2. 12 Oct, 2016 1 commit
  3. 10 Sep, 2016 1 commit
    • Tyler Gunn's avatar
      Cleanup Connections in conference controllers on CDMA<-->GSM change. · 136d33db
      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)
      136d33db
  4. 26 Aug, 2016 3 commits
  5. 25 Aug, 2016 1 commit
    • Sailesh Nepal's avatar
      Fix VoicemailChangePinActivity crash on dialog dismiss · de256215
      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
      de256215
  6. 23 Aug, 2016 2 commits
  7. 22 Aug, 2016 1 commit
  8. 18 Aug, 2016 1 commit
  9. 17 Aug, 2016 3 commits
    • Ta-wei Yen's avatar
    • Ta-wei Yen's avatar
      Fix MWI missing on blocked VVM3 SIM · 41fb43ee
      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
      41fb43ee
    • gitbuildkicker's avatar
  10. 16 Aug, 2016 7 commits
  11. 15 Aug, 2016 1 commit
  12. 14 Aug, 2016 1 commit
  13. 12 Aug, 2016 4 commits
  14. 11 Aug, 2016 7 commits
  15. 10 Aug, 2016 3 commits
  16. 09 Aug, 2016 3 commits