Ask / Submit
37

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

Tracked by Jolla (In release)

asked 2019-07-19 22:57:04 +0200

Mario gravatar image

updated 2019-08-29 17:48:43 +0200

harry gravatar image

Mobile data is still broken for some Android apps on XA2, even in Sailfish 3.1.0. Several prior releases provided some improvements but it's still not completely fixed. It worries me that its no longer listed in the open issues section in the release notes of Sailfish 3.1.0. Is this bug still worked on? Since it's a "reflash back to Android" kind of issue for me. So please, Jolla, can you confirm that this is still considered an issue and worked on?

Since the error pattern is really fuzzy, let's track it down together.

If you can confirm that a certain Android app does not work on XA2 (with Sailfish >= 3.1.0) over mobile data (but works on Wifi) please list the app below (or upvote if it's already listed). If the same app works for you over mobile data please write a comment and briefly describe your setting.

But let's stay focused on this specific bug (since it's hard enough to track down anyway), please do not list other kinds of connectivity issues. Also let's limit this list to apps that do not work for some (or all) people, do not list apps that generally work.

Edit: It really seems to depend on the mobile provider. Especially o2 Germany (but also some others) are affected. @Jolla, do you have any more insights about this? What's special about o2? And why is the Android subsystem affected by some provider details anyway? I would expect that connectivity (in general) is handled by Sailfish, not Android.

Edit:I found a permanent workaround: https://together.jolla.com/question/209532/track-down-mobile-data-issue-android-xa2-310/?answer=212609#post-id-212609

edit retag flag offensive close delete

Comments

4

Hi, I have a XA2 single sim and O2 Germany postpaid contract. if jolla wants to contact me, I am willing to spend time to help them debug it.

harry ( 2019-08-16 09:45:53 +0200 )edit

Hi,

I would like to hear, that this issue is important for Jolla and they are still working on this... SFOS is great but banking relies on android, so it is still crucial feature.

pemek ( 2019-08-28 15:53:54 +0200 )edit
2

@pemek, you can already "hear" / see exactly that, as this question is "Tracked by Jolla".

olf ( 2019-08-29 15:46:04 +0200 )edit

25 Answers

Sort by » oldest newest most voted
21

answered 2019-08-28 22:50:57 +0200

harry gravatar image

updated 2019-09-09 10:24:10 +0200

SOLVED

I got internet connection for all android apps on mobile data connection that did not work before, e.g. Here Maps or Telegram. The problem is indeed with the List of APNs. I have a XA2 single sim and O2 Germany postpaid contract.

What I did

1) Debug your android runtime while you are connected to a wlan

devel-su lxc-attach -n aliendalvik -- /system/bin/logcat -b radio

2) Disable the wlan and find a line like this in your logs

12:44:53.253 276 276 D DCT : [0]buildWaitingApns: usePreferred=true canSetPreferApn=false mPreferredApn=null operator=26207 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=26207

Important is the value after "getOperatorNumeric=" for me this is 26207

3) Download the xml file from https://android.googlesource.com/device/sample/+/master/etc/apns-full-conf.xml

4) Search for apn entries where the attribute @mmc is equal to the first three digits and the attribute @mnc is equal to the last 2 digits. The XPath to select the nodes is

/*/apn[@mcc = '262'][@mnc = '07']

5) Find the entry that is the correct for your provider. For me it was

<apn carrier="o2 Internet"
  mcc="262"
  mnc="07"
  apn="internet"
  mmsc="http://10.81.0.7:8002"
  mmsproxy="82.113.100.5"
  mmsport="8080"
  type="default,supl,mms"
  mvno_match_data="2620739"
  mvno_type="imsi"
/>

6) Tweak the entry till it works. I changed it to

<apn carrier="O2 DE Internet"
  mcc="262"
  mnc="07"
  apn="internet"
  mmsc="http://10.81.0.7:8002"
  mmsproxy="82.113.100.5"
  mmsport="8080"
  type="default,supl,mms"
/>

I removed the @mvno_match_data and the @mvno_type attributes and changed the @carrier attribute a bit. I don't know which change did it, but the configuration now works for me. - Itseems that changing the carrier attribute has no affect.

7) Backup the file /system/etc/apns-conf.xml on your phone.

8) Rename the file to "apns-conf.xml" transfer it to your phone and replace the file called /system/etc/apns-conf.xml

devel-su
cp apns-conf.xml /system/etc/apns-conf.xml
chown root:root /system/etc/apns-conf.xml

9) restart the phone and disable wlan

edit flag offensive delete publish link more

Comments

1

this sounds very promising. i have o2/drillisch...will try that in the next days. hope others will too and report.

donni106 ( 2019-08-29 00:17:04 +0200 )edit
3

This worked for me! Thank you very much!

I didn't replace the file, though, just made a backup copy of /system/etc/apns-conf.xml and edited the carrier attribute and removed the mvno_match_data and mvno_type attributes in the original file.

I wish I hadn't bought a D1 sim card just yesterday noon... :D

Karin ( 2019-08-29 18:19:39 +0200 )edit
2

As Karin wrote, this indeed works for o2/Drillisch. Thank you very much for the effort. :-) Let's hope this fix is actually stable in daily use.

Mario ( 2019-08-29 18:20:33 +0200 )edit
2

Great work! I will try it as well later this evening, but I'll assume it'll work for me. I just was curious to see which setting actually has the gamechanging effect here and while researching the net about the mentioned attributes, I stumbled on the follwowing android documentation: https://developer.android.com/reference/android/provider/Telephony.Carriers where it is stated that those attributes are deprecated. Could this have something to do with it? Still this would sound like a generic problem and not only applicable for some providers. Unless those attributs including their names are exchanged/checked regarding some validity by the provider. But I'm not a mobile dev, so I might be wrong badly. Still it is needed to find out why it works like that in order to verify it regarding a permanent solution...

majuss ( 2019-08-29 18:38:23 +0200 )edit

It doesn't work for me because my logcat prints "22208" as operator code but it isn't available in the apns-full-conf.xml file . I'm using Fastweb sim operator in Italy.

Luca ( 2019-08-29 20:50:38 +0200 )edit
10

answered 2019-07-28 19:25:56 +0200

Raymaen gravatar image

updated 2019-07-29 08:53:13 +0200

HERE Maps, Shazam, DB Navigator,...

do not work on mobile data while they work on WiFi

(XA2 single sim) Germany Provider: Drillisch/WIN Sim o2

edit flag offensive delete publish link more

Comments

I have the same problem with DB Navigator and netzclub (German O2 network) with XA2 Dual Sim.

carolus ( 2019-08-07 11:57:28 +0200 )edit

For me, everything used to work fine but suddenly most apps (including microg) cant connect any more. This is extremly weired since it used to work in tje beginning (including DB navigator) and I really didn't change anything.

inte ( 2019-08-12 01:34:13 +0200 )edit

DB navigator doesn't work on mobile data My phone / sim provider: XA2 Dual Sim / Drillisch discotel / O2 "Settings" says: Sim Card "unknown"

juru2 ( 2019-08-16 18:47:11 +0200 )edit
7

answered 2019-07-19 22:59:50 +0200

Mario gravatar image

Conversations (XMPP messenger)

Works on Wifi but not on mobile data (Sailfish 3.1.0). XA2 dual sim (only one SIM installed). Provider Drillisch / o2 Germany.

The app always says "No Internet connection" and does not even try to connect.

edit flag offensive delete publish link more

Comments

So we have a quite minimal reproduceable testcase with a working setup and a non working setup. This should be a very helpful input to Jolla for isolating and fixing this bug. If they are even still working on it. What is the different between o2 and Vodafone that confuses the Android subsytem?

Mario ( 2019-07-21 11:35:50 +0200 )edit

@pemek, can you convert this to an answer, so it can be separately commented? What is you setting, o2 Germany, as well?

Mario ( 2019-07-21 11:37:00 +0200 )edit

Yes, o2 Germany

4carlos ( 2019-07-21 11:58:10 +0200 )edit
1

I have an Xperia XA2 Plus dual SIM. The first SIM (o2 Germany) has issues. The second SIM (Telekom Germany) works fine. o2 Germany seems to be problematic for many users.

scharelc ( 2019-07-24 00:05:47 +0200 )edit
1

oh man...it is depending on the operator :o??! i have o2 (drillisch) and also still mobile network issues after latest update today :(

donni106 ( 2019-07-26 03:38:12 +0200 )edit
7

answered 2019-08-01 13:02:35 +0200

Nrsisti gravatar image

O2 users have you tried manually set the access point details in settings? Does that help?

edit flag offensive delete publish link more

Comments

2

i triied. but lots of values i can't fill in in the gui. like mnc and mcc fe...

toba ( 2019-08-01 13:14:34 +0200 )edit
2

... i also asked o2 to send their conf again.... also no effect...

toba ( 2019-08-01 13:23:19 +0200 )edit
1

Hi, thanks for getting involved. Which settings shall we try? And where; Sailfish settings or Android settings? Note that mobile data works fine in Sailfish (native apps). Mobile data also works for some Android apps, but not for all. Interesting observations: In Android settings "Network & Internet" > The field "Mobile Network" (or similar, translated from German) shows the name of the provider "maXXim" (virtual provider in the o2 network), but clicking on it goes back to overall settings (as if I clicked the back button). If I open SIM card settings, it shows provider: "Unknown", mobile number: "Unknown". Clicking on "Mobile Plan" is shows "maXXim has no known source website".

Mario ( 2019-08-01 22:15:38 +0200 )edit
1

Interesting: I don't have that maXXim stuff, its showing 'o2 - de+'. Where do you find the SIM card setting within the android settings? When I tap on the 'mobile plan' section, there is the following message: "Please connect to the internet". This is consistent in the end, that even the settings app of android can't detect an internet connection. However, the questions @Mario asked (which settings should be checked, and applied exactly where?), are still the same.

majuss ( 2019-08-02 17:13:20 +0200 )edit
1

I also switched some settings today: The data access point (sailfish settings -> mobile internet -> data access point) can be set between Ip (v4, I guess), Ipv6 and dual mode. Restarted android support after every change, but still the same issue regerding the relevant apps (checked with here maps and komoot). So from gui, I don't think we can do much more, can we? Any suggestions, what possibly can be done via some cli actions in that case? I still have the impression, that we all (including jolla) can describe the problem, but nothing is known about its root cause so far. It's slighty isolated by the provider dependency, but thats all. Why O2 germany (and partially vodafone?) and not any other operator, nobody can tell. How can we learn more about this?

majuss ( 2019-08-03 12:43:24 +0200 )edit
7

answered 2019-08-20 18:48:46 +0200

inte gravatar image

updated 2019-08-28 00:55:33 +0200

Fasten your seatbelts.... I think I solved this issue, and the answer was always there: https://together.jolla.com/question/200333/mobile-data-doesnt-work-after-updating-to-30114-on-xperia-xa2/?answer=200508#post-id-200508

(Very well hidden in tjc and with just 2 upvotes)

I put a (even inactive) sim (klarmobil/D2) in the secondary slot, and I could then disable the first (O2) sim. Once I reactivated it - baaam - data connectivity was restored for android apps. I guess this bug is probably related to some internal routing, maybe even on the hardware base since the inability to route data through sim 1 withstands factory settings once appearing. I also guess this issue is NOT network dependend and the quite high number of German O2 customers is just pure statistics - O2 is simply the largest German provider, and Jolla has a quite large German user community. Hope that helps...

edit flag offensive delete publish link more

Comments

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

jollajo ( 2019-08-20 19:06:29 +0200 )edit
2

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.

inte ( 2019-08-20 19:08:22 +0200 )edit
1

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

inte ( 2019-08-20 19:11:25 +0200 )edit
2

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

scharelc ( 2019-08-20 19:50:25 +0200 )edit

@scharelc Which provider(s)?

inte ( 2019-08-20 20:07:39 +0200 )edit
5

answered 2019-07-21 07:13:26 +0200

4carlos gravatar image

updated 2019-07-21 11:56:50 +0200

Well known to me (same device, same conditions, O2).

I replaced the SIM for testing purposes with Vodafone SIM. Mobile data was there right now for ALL Apps. O2 seems not a good choice for the XA2.

It is reproducible.

Edit: o2 Germany + Vodafone Germany

edit flag offensive delete publish link more

Comments

We have this behavior on both devices a Xperia X and a Xa2. (O2)!

sailaway ( 2019-08-03 11:27:00 +0200 )edit

hi. also o2 client with contract.... in my case xperia x f5121 running 3.1.0.11 has no problems, all android apps have internet on mobile data..... but the xa2 h4113 has only threema and firefox connected via mobile data. all other android apps won't connect....

toba ( 2019-08-05 20:57:16 +0200 )edit
4

answered 2019-07-20 09:50:53 +0200

Karin gravatar image

Telegram messenger (Telegram-FOSS v5.7.1 (1608) universal armeabi v7a armeabi)

Works on Wifi but not on mobile data (Sailfish 3.1.0).

XA2 dual sim (only one SIM installed). Provider Drillisch / o2 Germany.

The app always says "Waiting for connection".

edit flag offensive delete publish link more

Comments

Replace O2 SIM. Look at my comment above.

4carlos ( 2019-07-21 07:17:00 +0200 )edit
2

Telegram for Android v.5.9.0 (1648) arm-v7a works fine on 3.1.0.11/XA2 and the mobile data network of Telia FI.

jovirkku ( 2019-07-23 16:34:23 +0200 )edit
4

answered 2019-07-28 19:51:45 +0200

toba gravatar image

updated 2019-08-02 10:12:32 +0200

same problem here... i have o2 as provider and am using a h4113.... o2app, deutsche bank, blockfolio, deutsche bahn are not working. threema and firefox are working....

sad jolla is issuing this update as out of beta....

would love to have sone feedback from them....

edit flag offensive delete publish link more
3

answered 2019-07-23 18:07:50 +0200

Luca gravatar image

updated 2019-08-22 11:58:45 +0200

Spotify App. Doesn't work on mobile connection (Fastweb - italy).

edit flag offensive delete publish link more

Comments

Works without issues for me on XA2.

bomo ( 2019-07-23 23:03:39 +0200 )edit

I'm in italy using Fastweb sim. By reading others' posts it seems to depend on some provider setting...

Luca ( 2019-07-23 23:45:32 +0200 )edit

@bomo Which provider do you use? (Indeed, it seems to depend on the provider. But we haven't figured out, what exactly causes the issue, yet.)

Mario ( 2019-07-24 15:46:45 +0200 )edit

@Mario, I'm using Vodafone Germany

bomo ( 2019-07-25 21:29:06 +0200 )edit
1

it is so unbeliveable, that the combination of XA2, some random Android apps and a German provider results in no connectivity. I think there are other providers in europe with the same problem. maybe we should open a thread with listing the bad providers across europe??

donni106 ( 2019-07-28 23:20:38 +0200 )edit
2

answered 2019-07-23 22:19:38 +0200

cy8aer gravatar image

Tiny Tiny RSS - f-droid version from https://fdroid/repo - works fine withWifi

Mein O2 - again

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
15 followers

Stats

Asked: 2019-07-19 22:57:04 +0200

Seen: 4,368 times

Last updated: Sep 09