| 0852a954be5937a1b0bca94df0c2007d7ee3c0c7 |
|
13-Apr-2016 |
Jack Yu <jackyu@google.com> |
Fixed that data retry didn't happen issue
When modem return -1 as the retry value in setup data call response,
we should interpret it correctly and retry the data connection.
bug: 27787361
Change-Id: I0a3e442f5125730dd9a196ce632120b44b880090
/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/DcFailBringUp.java
|
| e3f497323441d0c9215f6cbad9ce950f054cce72 |
|
09-Mar-2016 |
Jack Yu <jackyu@google.com> |
Added unit test cases for DataConnection
bug: 25691077
Change-Id: I90920c7625ec7f8f716fbab15f65c7f4323628cc
/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/DcFailBringUp.java
|
| 0e664d8c9ff3a1f2ab03d2bef4268615335ea1a2 |
|
17-Dec-2015 |
Jack Yu <jackyu@google.com> |
Data call retry refactoring
Moved retry manager from DataConnection to ApnContext.
bug: 22208242
Change-Id: I0baa80e06e6d815643782c2b549460547d0bfef9
/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/DcFailBringUp.java
|
| ff4e317d24f0d23bdc0f306d53ddc51f2f1ecf6a |
|
22-Mar-2013 |
Wink Saville <wink@google.com> |
Move retrying into DC.
This is the first step in refactoring for bug 4772191.
Bug: 4772191
Change-Id: Id54a20ab192783c63939158670faaf531a527640
/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/DcFailBringUp.java
|