summaryrefslogtreecommitdiffstats
path: root/Android.mk
diff options
context:
space:
mode:
authorWink Saville <wink@google.com>2009-08-18 12:08:59 -0700
committerWink Saville <wink@google.com>2009-08-18 12:08:59 -0700
commit95a1d1a89e383dab893750638c2393dec54833ff (patch)
tree57d7106336e1cee68373421ff4f7cd454ba00d96 /Android.mk
parent6a2d513a4ad116fc5405d4d4f1f6fdb692bdefbc (diff)
downloadframeworks_base-95a1d1a89e383dab893750638c2393dec54833ff.zip
frameworks_base-95a1d1a89e383dab893750638c2393dec54833ff.tar.gz
frameworks_base-95a1d1a89e383dab893750638c2393dec54833ff.tar.bz2
E911 call fix in ECM
Based on the VZW requirement, phone should be still in ECM mode in 2nd emergency call. but in the current phone call, if a 2nd emergency call is originated, ECM mode will exit. For fixing this problem, the coding design is as below: 1. In framework, canceling the first ECM timer immediately upon the origination of the 2nd E911 call, and restarting a new timer when the 2nd E911 ends. 2. Framework needs to syncronize the timer with phone app by sending notification to phone app to inform timer is canceled or re-started, since phone app needs to show how much ECM time left on the status bar. 3. In phone app's emergency callback mode service, the timer in this service will be canceled when it receives the timer cancel notification from framework; the timer will be restarted once it receives timer restart notification from framework.
Diffstat (limited to 'Android.mk')
0 files changed, 0 insertions, 0 deletions