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

Merging networks of E-Plus, O2, BASE, Simyo, Blue and so on. Here maybe the reason will be found? From a technical point of view certainly not completely faultless.

https://www.teltarif.de/tag/o2-e-plus-uebernahme/

https://www.teltarif.de/mobilfunk/national-roaming.html

I was able to install Orbot and it can start a connection even on mobile data. The Socks Proxy is reachable on 127.0.0.1:9050. However, to enable other Android Apps to connect through Orbot it is supposed to run in VPN-mode which seems not possible in Aliendalvik (Orbot is crashing when enabling VPN-mode). At least, I found another app that works on O2 mobile data while most apps dont SCNR.

For Conversations I set the server address manually to 127.0.0.1 and created a SSH-tunnel to the actual server. But Conversations didn't even try to connect, since it thought there is no Internet connection anyway.

Interesting. May this bug be related to some android-internal signalling (like a dbus message or something signalling offline status even when online?).

I think the Android subsystem actually think it is offline, therefore, signaling its state correctly. According to its wrong beliefs. Still, I don't know much about Android, I'm just guessing based on my observations (and on how I think this would fit together.

yes, exactely. Maybe related to the simcard type used by o2.

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.)

I can confirm, the issue is not limited to reseller plans. Using my original O2 SIM results in the same "mobile data unawareness"...

also on original o2 sim and can confirm the same...

Thanks for the info. Which menu is shown in this screenshot? However, this bug report is about the issue where mobile data works fine for native Sailfish apps (and also some Android apps), but won't work for other Android apps. Thus, I do not think that this issue is related to modem/hardware/Sailfish problems.

its the hardwarecheck... i guess this could be caused by bad settings transmitted by o2 that install two modems on one simcard, confusing most androidapps... u could check if u have similar outcome if u check ur device... go to productinfo and tap severaltimes on the buildnumber... so hardwarecheck will apear.... if you have also two modems where the system awaits one and the test is shown as failed, we have a similarity we could let checked by the jollaists...

I'm on Vodafone Germany and have no problems. I checked my SIM with the hardwarecheck and got the same failure like yours : 2 modems (1 is expected), so I think, that's not the problem.

ok. nice to know. thx

And I dont have any issues reported for my SIM card: The test passes. I own the single SIM version of the XA2. So this test result can't tell us anything more, as I understand the issue comes up whether the single or dual SIM version is used.