commit 31aed67a0fc541ecf0cdb283e0aad6e13b38940d
author paulhu <paulhu@google.com> Tue Dec 18 19:30:16 2018 +0800
committer paulhu <paulhu@google.com> Tue Dec 18 19:30:16 2018 +0800
tree 4f83bdaf8af983a157e29df38cafbe50d7741bdc
parent 4ffb6e0bd8d7939047e0fa37ce30aca4e84190e5

Expose detailed data call end reasons

Currently, most of the fail causes for data connectivity are
exposed as ERROR_UNSPECIFIED. To know the precise fail
cause not just common exception, add more cause definitions
let exact fail reason can pass up to the apps from modem.

Bug: 113505704
Test: Build pass and data call can setup normally.
Change-Id: I1c8b910c272a027c811434d6d034b60ebfd64afa

radio/1.4/Android.bp

diff --git a/radio/1.4/Android.bp b/radio/1.4/Android.bp
index 6257112..ad114f3 100644
--- a/radio/1.4/Android.bp
+++ b/radio/1.4/Android.bp
@@ -26,6 +26,8 @@
         "CellConfigLte",
         "CellInfo",
         "CellInfoLte",
+        "DataCallFailCause",
+        "DataConnActiveStatus",
         "DataProfileInfo",
         "DataRegStateResult",
         "EmergencyNumber",
@@ -34,12 +36,14 @@
         "FrequencyRange",
         "LteVopsInfo",
         "NetworkScanResult",
+        "PdpProtocolType",
         "PhysicalChannelConfig",
         "RadioAccessFamily",
         "RadioCapability",
         "RadioFrequencyInfo",
         "RadioTechnology",
         "NrIndicators",
+        "SetupDataCallResult",
     ],
     gen_java: true,
 }