Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 9d052635 authored by Jack Yu's avatar Jack Yu
Browse files

Fixed that APN context stuck in SCANNING state 

1. When data retry fails at trySetupData, we should apply
   FAILED state to the APN context otherwise it will be
   in SCANNING state forever since we are not going to
   schedule for the next retry.
2. When we get a new network request in applyNewState,
   if the APN is in SCANNING state, we should trySetupData
   immediately instead of waiting for the next retry,
   which might still minutes/hours away from now.

Test: Telephony sanity tests
bug: 38113800
Change-Id: I6edd7555327f41ee713a256edfe641a41ca6f969
parent 0501652b

src/java/com/android/internal/telephony/dataconnection/DcTracker.java

+8 −2
Original line number Diff line number Diff line
@@ -1596,9 +1596,15 @@ public class DcTracker extends Handler { 
                str.append("isDataEnabled() = false. " + mDataEnabledSettings);

            }



            // If this is a data retry, we should set the APN state to FAILED so it won't stay

            // in SCANNING forever.

            if (apnContext.getState() == DctConstants.State.SCANNING) {

                apnContext.setState(DctConstants.State.FAILED);

                str.append(" Stop retrying.");

            }



            if (DBG) log(str.toString());

            apnContext.requestLog(str.toString());



            return false;

        }

    }
@@ -2464,7 +2470,6 @@ public class DcTracker extends Handler { 
                DctConstants.State state = apnContext.getState();

                switch(state) {

                    case CONNECTING:

                    case SCANNING:

                    case CONNECTED:

                    case DISCONNECTING:

                        // We're "READY" and active so just return
@@ -2474,6 +2479,7 @@ public class DcTracker extends Handler { 
                    case IDLE:

                        // fall through: this is unexpected but if it happens cleanup and try setup

                    case FAILED:

                    case SCANNING:

                    case RETRYING: {

                        // We're "READY" but not active so disconnect (cleanup = true) and

                        // connect (trySetup = true) to be sure we retry the connection.