Track down mobile data issue (Android, XA2) [3.1.0]

Someone having this issue should capture and paste the logs for debugging! Command is: "devel-su lxc-attach -n aliendalvik -- /system/bin/logcat -b radio"

Where to send logs? What scenario? When aliandalvik starts? Or application start? Please point out some scenarios, it would be easier then to provide sensible data.

Here are my logs:

08-28 06:31:10.086   284   284 D DCT     : [0]buildWaitingApns: mAllApnSettings=[[ApnSettingV3] O2 DE IMS, 556, 26207,
ims, , , , , , -1, ims, IPV4V6, IPV4V6, true, 0, 0, 0, false, 0, 0, 0, 0, , , false]
08-28 06:31:10.086   284   284 D DCT     : [0]buildWaitingApns: couldn't handle requested ApnType=default
08-28 06:31:10.086   284   284 D DCT     : [0]buildWaitingApns: 0 APNs in the list: []
08-28 06:31:10.086   284   284 D DCT     : [0]notifyNoData: type=default
08-28 06:31:10.087   284   284 D DCT     : [0]isEmergency: result=false
08-28 06:31:10.122   284   284 I chatty  : uid=1001(radio) com.android.phone identical 7 lines
08-28 06:31:10.127   284   284 D DCT     : [0]isEmergency: result=false
08-28 06:31:10.131   284   284 D DCT     : [0]trySetupData: X No APN found retValue=false
08-28 06:31:10.132   284   284 D DCT     : [0]onDataConnectionAttached
08-28 06:31:10.132   284   284 D DCT     : [0]isEmergency: result=false
08-28 06:31:10.154   284   284 I chatty  : uid=1001(radio) com.android.phone identical 7 lines
08-28 06:31:10.158   284   284 D DCT     : [0]isEmergency: result=false
08-28 06:31:10.162   284   284 D DCT     : [0]setupDataOnConnectableApns: dataAttached hipri:[state=IDLE,enabled=false]
mms:[state=IDLE,enabled=false] supl:[state=IDLE,enabled=false] cbs:[state=IDLE,enabled=false] dun:[state=IDLE,enabled=
false] fota:[state=IDLE,enabled=false] ims:[state=IDLE,enabled=false] default:[state=IDLE,enabled=true] ia:[state=IDLE,
enabled=false] emergency:[state=IDLE,enabled=false]

It is pretty obvious to see, that android only finds a single APN which is of type ims. and ims is the APN for Voice over LTE.

And what shoud it look like when it is ok?

Edit: Looks like Android sees Play provider, some apps (settings) sees SIM and internet, but some still cant connect to internet. In particular bank app which is crucial for me.

08-28 12:44:53.245 276 276 D DCT : [0]applyNewState(default, true(false), true(true)) 08-28 12:44:53.251 276 276 D DCT : [0]isEmergency: result=false 08-28 12:44:53.251 276 276 D DCT : [0]trySetupData for APN type default, reason: dataEnabled. Data allowed, reason: NORMAL 08-28 12:44:53.252 276 276 D DCT : [0]buildWaitingApns: E requestedApnType=default 08-28 12:44:53.252 276 276 D DCT : [0]getPreferredApn: mAllApnSettings is empty 08-28 12:44:53.253 276 276 D DCT : [0]buildWaitingApns: usePreferred=true canSetPreferApn=false mPreferredApn=null operator=26006 radioTech=14 IccRecords r=SimRecords: mDestroyed=false mContext=com.android.phone.PhoneGlobals@6f176a2 mCi=com.android.internal.telephony.RIL@9582fd0 mFh=Handler (com.android.internal.telephony.uicc.UsimFileHandler) {a410f33} mParentApp=com.android.internal.telephony.uicc.UiccCardApplication@4c732f0 recordsLoadedRegistrants=android.os.RegistrantList@ff60069 mImsiReadyRegistrants=android.os.RegistrantList@a145aee mRecordsEventsRegistrants=android.os.RegistrantList@736b8f mNewSmsRegistrants=android.os.RegistrantList@b848e1c mNetworkSelectionModeAutomaticRegistrants=android.os.RegistrantList@653a25 recordsToLoad=0 adnCache=Handler (com.android.internal.telephony.uicc.AdnRecordCache) {6f37fa} recordsRequested=true iccid=894806105[****] msisdnTag= voiceMailNum=null voiceMailTag=null voiceMailNum=null newVoiceMailTag=null isVoiceMailFixed=false mImsi=260060[****] mncLength=2 mailboxIndex=0 spn=null mVmConfigcom.android.internal.telephony.uicc.VoiceMailConstants@7c531ab mSpnOverride=com.android.internal.telephony.uicc.SpnOverride@95a7008 callForwardingEnabled=0 spnState=IDLE mCphsInfo=null mCspPlmnEnabled=true efMWIS=[B@a194a7c efCPHS_MWI=null mEfCff=null mEfCfis=[B@95eaf05 getOperatorNumeric=26006

With respect to network dependency I can say that I have Vodafone.de as SIM1 and congstar as SIM2 and don't see those mobile data issues. So I would suggest it is somehow related to O2

Activating flight mode and reenabling Mobile networks again triggers the no connectivity bug on my phone again. It can then again be repaired by switching sim cards as described above. So my solution is rather a workaround until this is fixed by Jolla and it won't help single sim phone users, but hopefully it helps for tracking down the issue.

@jollalo I was using my phone for quite some time until this problem appeared for me and even disappeared briefly again. Can't say if it's coincidence. However, what I CAN say is that switching sims helps for me. My second sim is klarmobil/D1 (but inactive). Maybe it would help to test if switching between two O2 simcards would also "repair" data connectivity. I currently don't have a second O2 simcard at hand, though. Maybe someone else could try to test this or even reproduce my method to restore data connectivity on O2.

this workarount does not seem to work for me (XA2 Plus)

@scharelc Which provider(s)?

Yes, Atalk works over mobile data (could reproduce with o2/Drillisch). So this disproves other theories that regular TCP sockets would not work, only HTTP requests. I think there is a call in Android to ask the operating systems, whether there is an Internet connection or not. And this always returns "False" on mobile data. However, if the app does not care about this and just opens a connection, it works. I think that's the difference between Conversation and Atalk, here. (However, I'm not an Android programmer, this is just an assumption.)