Make sure to disconnect the link when RIL reported link property change
which could cause connectivity issue. (i.e. IP address)
Change-Id: I6601ef53e4561bdc7d2760d00e134b8431512cb2
Additional deactivate cause so RIL could take intelligent action
on data stall occurrence if necessary.
Change-Id: Iae4accda879efb5679085c518117617fb16631c3
Handles the scenario of radio technology handover with IP continuity.
Once RIL/Modem finished a handover operation, an unsol data call state
change will be send up to FW notifying all link propertes changes.
FW will then re-configure the device with new link properties
including iptable used by Tethering.
Change-Id: I05e29f66ac3db8ba4274d3662642607742ba1d12
Added CommandsInterface.registerForRilConnected which allows components
to register for when the ril connects and provides the version of the
ril to the registrants or a -1 if the ril disconnects.
For ril version 6 RIL.setupDataCall needs to have RadioTechnology + 2
as the radioTechnology parameter when the rilVersion is >= 6.
DataConnection then uses registersForRilConnected to get the ril
version and provide the proper radioTechnology value to
RIL.setupDataCall
Change-Id: Iacba764b9e38a4a138d186ccf1625fea760cc56d
Refactor things a bit. Promoting GsmDataConnection's apn (ApnSetting) to DataConnection.
Use DataConnection's resetSynchronously rather than tampering with it from another thread.
bug:3486066
Change-Id: I2a7f7368f73c7d5c81e821976efafd56aca7aa69
Generates InetAddresses without risking an accidental dns lookup. For use with supposedly
numeric-only ip address strings.
Change-Id: I694f3976ce1c6382854706f6557ea88a289add3a
Handle version 4 returning more than 3 strings and
handle addresses and dnses which are possibly zero length.
Change-Id: Ic58231aa53ccb1fa2b2aaa19580f83f71db1cca3
Removed ACTIVATION_REJECT_GGSN and ACTIVATION_REJECT_UNSPECIFIED from
DataConnection#isPermanentFail() so they won't be detected as permanent.
bug: 3070773
Change-Id: I18d10bc44609e550d7932cd9600116f074bcb8dd
Commit 323f059d65 introduced a side effect that
PPP and MIP cannot be disconnected gracefully in case of 1X data calls.
The new disconnect reason field in DEACTIVATE_DATA_CALL will help RIL and Modem
to know whether the disconnect was done for modem shutdown or not. And
the followings can be achieved at the same time.
- Graceful PPP termination
- MIP de-registration
- RF Release Order with "Power Down De-registration" if modem is powered off.
(Also cleaned up the deprecated functions for setup/deactivate default PDP)
Change-Id: If79842ad05827326b6994e1148a6ae68b4467c45
Since we have NetworkProperties we can remove the individual accessors
from Phone and its subclasses.
Change-Id: Id9969a880405900a63051b3ae4019d889afb1fe8
Really fix it this time. The previous fix had a flaw which tested ok but was removed
after a code review. This flaw masked problems in DataConnection, which this fix
fixes.
bug:2849192
Change-Id: I50d2dd827d4427f8030c0f590c85672869b509ff
- Fix typos in Javadoc and comments.
- Fix Javadoc @link references to other classes/methods.
- Rename MISSING_UKNOWN_APN to MISSING_UNKNOWN_APN in DataConnection.
- Remove unused (and misspelled) RETRYIES_* consts in RetryManager.
Change-Id: I3b44ac8320d6c1e4c350be600c7ef266aaf735e4
In change I5776324a I made DataConnection.reset asynchronous.
That was a mistake as callers to cleanUpConnection assumed
it was synchronous. Added DataConnection.resetSynchronously
as a fix, someday the trackers will become asynchronous and
this won't be necessary.
Change-Id: I4669901e5c47a712212bb388c35fbb9f9ff603a7
Fix a bug in DataConnection state machine where the notification
of disconnection completion was sent before we actually transitioned
to the in active state. Also, change conn.reset to send a response
so the user can know when the transition to the in active state
completes for that also.
bug: 2471897
Change-Id: I5776324ac89a607925d07f4a600bc5b34c3f3ed6
events (and in one case, a DropBox entry).
Add a simple intent that triggers master-clear (and toggle EFS), given the
right permissions.
Bug: 2264596
Bug: 2350452
Bug: 2264596
