asked 2017-10-18 10:17:03 +0300
Sometimes my Xperia X finds itself not connected to the mobile network even if the network is present. The only way to recover from this situation appears to be to activate and then deactivate flight mode. This is a different issue from the Jolla C one where calls are not available since in this case the phone displays no network available.
answered 2017-10-19 12:23:53 +0300
I have had the same situation: Lost mobile connection and never reconnected. This happened 4-5 times in the last 4 days. Toggling the Airplane mode or even restarting the device did not always reconnect the device to the mobile network. For me, the fastest way to reconnect the device is starting up the terminal (developer mode needs to be enabled) and executing the following line:
devel-su systemctl restart ofono
The device reconnects immediately after entering the root password. Do not ask me why a restart of the phone does not always help in my case, as I would have assume it properly reset and restart the ofono stack
No, it happened several times to me since I upgraded to 2.1.4.14.
Giacomo Di Giacomo ( 2018-03-12 11:42:07 +0300 )editPERFECT ! It helped :) ....
Network access difficulties occurred while hot-switching SIM cards. This caused confusion even though device asked for reboot. As @Roger2000 mentioned, the device connected immediately after executing the command.
Thank you @Roger2000 !
launchpad ( 2018-09-14 12:19:37 +0300 )editanswered 2017-10-23 15:28:43 +0300
Thank you for all the reports. Could you also mention the country you are in and the name of your operator if you experience this problem?
Germany / O2 --> Your APN Settings are wrong. You took them from the prepaid version, not from the tariff. Internet worked almost fine the last days, today I had to switch modes to get it up and running again but I had that issue also with that bulk of droid sh*t. Might be something with the coverage :D I think about changing my provider.
NuklearFart ( 2017-10-24 00:31:33 +0300 )editanswered 2018-11-11 13:26:35 +0300
This story may be of some help, although not much of a consolation to those currently having issues.
I've had issues since this summer (2018). Long story short it seems that my Xperia X does not use specific 3g bandwidths anymore. I'm not sure if this has always been the case; when I originally switched to Xperia X Compact, far before I had the issues of this level with my Xperia X, the first thing I noticed that X Compact didn't have general roaming problems at all compared to Xperia X.
2g and 4g are fine with my Xperia X and basically the device could still be used as a daily driver. However, the lack of 3g bandwidths causes issues because during the calls SFOS tries to switch to 3g instead of 2g that would be normal with LTE for voice calls. Since 3g is not available at all, the whole modem gets stuck. I can see the switch to 3g on top bar and then the phone app freezes along with the modem. Usually I then have to reboot to fix this situation.
I understand the logic of using 3g instead of 2g; 4g is not capable of phone calls natively, so it has to switch to 2g or 3g, of which 3g provides better data speeds. (Because of the 3g bandwidth issue, I'd prefer it to be possible to enforce 4g+2g instead of just 4g+3g+2g.)
I've also had several modem malfunctions without calling where there has been 3g coverage. These also started in Summer 2018. These have been sometimes resolvable by switching to flight mode, but sometimes I have had to reboot.
I've been using 3g extensively because it usually uses up less battery than 4g and 2g for voice calls together, but it now made it easier to notice the problems getting more severe.
I'm in a lucky situation that I've been able to test this consistently using two Elisa/Saunalahti SIMs, Xperia X and Xperia X compact phones, latter equipped with g7's binary hacked Xperia X-image, as well as Xperia Z3 Compact with Android. Out of these three phones only Xperia X has coverage problems with 3g.
The problem is present with both Elisa and Saunalahti sims with Xperia X. (Elisa and Saunalahti are techically the same company and using the same APs.)
The problem is present with Xperia X using Android OmniROM. (Unfortunately Emma flashing utility registration fails for me after the Emma update so I haven't been able to reflash back to original firmware yet.)
The problem is not present with Xperia X Compact with image converted from Xperia X.
Sims: Elisa, Saunalahti
Areas where the problem occurs constantly:
Helsinki Ooppera area (intersection of Helsinginkatu, Mannerheimintie, the Opera house tram stop to be precise).
Also my working room at our company's premises at Keilaniemi, Espoo. Our company has some AP arrangements from the operator Elisa that may be limited to specific bandwidths only. Again Xperia X Compact or Z3 Compact have no issues here.
To me it looks like one of these three reasons could be behind the problems:
The antenna of Xperia X may have been damaged during the very hot summer in Finland in 2018. I remember at least two situations where the device felt dangerously hot because I had been listening internet radio on the beach (although the device was not exposed to direct sun light).
The operator Elisa/Saunalahti would have done changes to their APs: They could have removed some 3g bandwidths or APs altogether, for the reasons of interference, power use, cost or getting ready for Voice over LTE for instance. Now when I come to think of it, VoLTE could be arranged so, that voice calls are bridged over LTE interface and the operator may have reserved some bandwidths for their internal voice call routing. Note that I'm not the only person noticing changes in 3g coverage this fall in Helsinki area and moving to use 4g instead. Still, I'm only guessing here that the operator would be at fault.
Because both Sailfish X and Android OmniROM suffers from the issue, the problem could be in the Android drivers that both SFOS and Android use as a base. I'm not sure if radio drivers are part of Android and libhybris or radio firmware itself. If so, I hope it could be fixed by flashing the latest Sony's firmware with Emma tool, if I ever get it's registration/login working.
It is important to keep in mind that my Xperia X Compact, running with basically the very same image as Xperia X, has zero issues with the same SIMs. This indicates that a) X Compact is not damaged as Xperia X would be, or b) Xperia X Compact has support for more 3g bandwidths to begin with, and does not suffer from one or two lost bandwidths.
I was able to get EMMA flashing tool working again with a complete reinstall from a fresh distribution meant to be used with Xperia X. The login problem of the tool happens only if EMMA decides to autoupdate itself it seems.
I reflashed my Xperia X to the latest stock Sony Android 8.0.0 firmware 34.4.A.2.107 with baseband version 8976-8976.gen.prodQ-00017-38 and kernel version 3.10.84-perf-g51b66cc723-04731-gb5fc7b8c973 (Jul 19 2018).
The issues persists on stock Sony Android firmware:
In 3g mode the phone completely ignores the specific AP at our company offices with two separate Elisa and Saunalahti SIMs. With Xperia X Compact and Xperia Z3 Compact no problems.
Also 3g roaming in the vicinity of Helsinki Opera House is struggling heavily. There is a clear gap in the 3g coverage but with this device only.
I also paid attention how Android switched from 4g to 2g during the voice calls. It does not show it but you can try browsing, which fails or is incredibly slow, and when you hang the call the coverage bar momentarily show E, meaning Edge, which was a later standard for 2g data connections. In the previous tests with Sailfish switched to 3g even when it was not available, which lead to a freeze state with the phone app and modem. I'll try this scenario again later with SFOS.
If my Xperia X is not broken and this problem is Xperia X specific, in the roaming situations it would help to allow in the the preferences of Sailfish to switch to 4g/2g only and avoid 3g at least for the duration of the voice calls. If anyone knows how to do this bypassing the currently limited selection in the preferences, please comment below.
Next I'll have to sweet talk any of Xperia X owners in our company to visit my office for comparison between equal devices. :)
Tested my Xperia X at the office again with SFOS 3.0.0.8, with a new image downloaded from shop.jolla.com.
As with Sony stock firmware 3g signal is still completely missing. But when making or receiving calls Sailfish now drops to 2g as it should, instead of dropping to 3g and getting completely stuck.
So, I tested with my colleague's Xperia X in the same spot, and it didn't have any problems in connecting using the Elisa SIM card of our company, with the same (the latest) Sony Android ROM.
This concludes my testing. The situation is that my Xperia X's antenna or chip is most likely to be damaged from the heat.
As I mentioned, it was not in a direct sunlight when listening to internet radio on the beach, so with some bad luck this could happen to others too.
As a side note my colleague remembers another case where the phone never recovered back to its normal condition after using it as a 3g/wifi spot for a day for his family on the low 3g coverage area. (Old Nokia, this had nothing to do with Xperia X.)
To get to the bottom of problems you may have with roaming, be ready to flash the original Sony Android firmware as has been advised by Jolla Zendesk. If the roaming and coverage problems continue with the Android, the device is at fault.
Thanks for the long investigation. The problem seems to be only with Sailfish OS. I didn't go back to the original Android image yet, because I have no phone as backup right now.
But it seems to be a SFOS thing, otherwise there would be tons of search entries showing up from Android users with the same problem.
Anyway, I'll buy an XA2, when SFOS 3 comes available and then I'll try to get my X back to Android and test this.
Mat2ch ( 2018-11-12 12:35:35 +0300 )edit@Mat2ch Not necessarily. LTE has been most widely used for few years now, people use it most of the time, and since it normally backs to 2g for voice calls (just my experience with couple of company phones), while SFOS switches to 3g, this issue wouldn't be so clearly visible for Android users. And SFOS only wouldn't explain why Xperia X Compact works so well.
Unless my Xperia X radio or antenna is simply busted, of course. I'm not claiming my case would be the only possible problem scenario with similar symptoms, but I don't believe it is SFOS to blame for it because the very clear problems started in just a matter of days this summer, and there weren't any updates released at the time.
Manatus ( 2018-11-13 00:24:47 +0300 )editThank you for this detailed investigation. I have the same problem when using roaming abroad (in 4 out of 5 countries it doesn't work). Therefore I reinstalled Android via the Sony Emma flash tool, and afterwards didn't have any connectivity issues anymore abroad. So I don't think it's an issue with the antenna. I will be testing Sailfish OS on the Xperia X soon again on a roaming network and hope I'll have better results this time.
molan ( 2018-11-22 17:51:28 +0300 )editI have a very hard-to-prove theory. Flashing (a different) firmware causes a more complete reboot to the radio hardware, which in turn gets rid of some old junk in its circuitry, which in turn gets rid of issues. Flashing using Emma and back to Sailfish fulfills this.
This could be proven with taking the battery off overnight for example, as it should fix the problem (temporarily, though) but as Xperia X doesn't have user replaceable battery, this would require someone to use a heat gun and actually disassemble the device...
TL;DR I suspect that the binary blob used under SFOS is buggy as frig.
Direc ( 2018-11-22 18:05:04 +0300 )editanswered 2018-01-09 12:21:04 +0300
also roaming is very very bad!
I was in Turkey this spring, and I had a really hard time to get the phone working at all. There were three available, Vodafone and two others, but I had to reboot, search for networks and in the end force the device to 2G only in order to get the SIM pick up any network at all...
Direc ( 2018-05-27 21:22:42 +0300 )editanswered 2018-11-25 16:07:49 +0300
This problem has a known workaround: reflash phone with Android, use it with your sim for some time: do several calls, use 2g/3g/lte internet. Then reflash it back with Sailfish.
I did it a month ago and it fixed the issue for me. Well, I can't be 100% sure since it's probabilistic, I didn't have any network losses while before I'd expect them to happen like 5-7 times.
It's worth to note that it's a stopgap fix, not an acceptable solution. What happens if I change operators? Or go abroad and want to use a local SIM for cheap internet? 10 months ago I was in Finland and F5122 didn't work at all with DNA's prepaid SIM, no network. That's on Jolla's motherland. So, should I relfash the phone back and forth while crossing the border? Reflash erases all user data, and Sailfish backup doesn't restore apps and app data, only a selected few, like Gallery, SMS and contacts. So standard reflash and setup procedure will take several hours, and some data will still be irreversibly lost, like pictures in WhatsApp. There is a way to dump root and home partitions and restore everything completely after reinstall, but it's too low-level for many users. So, we are waiting for Jolla to provide a fix.
answered 2018-07-31 10:03:44 +0300
Is anyone able to confirm / negate that this bug / misbehavior occurs far less often when the systemd logs are dropped?
I changed in /etc/systemd/journald.conf the value Storage= from "volatile" to "none" and had no complete network loss anymore for three days now. Before I had to restart ofono at an average of 5,6,7 times each day, depending on how much I was moving through weak networks or whatever.
Only once in these three days I lost data connection, but was still able to make phonecalls.
In fact, I'm finally able to USE my Xperia as intended, without permanently carrying a redundant phone with me. Maybe the problem is limited to areas with crappy networks (like in Germany), but it makes SailfishX still unusable.
I just changed that and I will let you know my experience. Here at work reception is poor and therefore the bug occurs frequently.
Giacomo Di Giacomo ( 2018-07-31 13:45:14 +0300 )editI can confirm after two days of testing this, that the phone hasn't lost the 4G/3G signal, in the same conditions as before (where it could lose it 2-3 times a day). However, the network connectivity is lost even if the 4G signal is on, meaning I can receive and make calls, but to navigate I must go through plane mode (activate/deactivate) to get network again.
This definitely improves the usability of the Xperia X, thank you very much!
Jojonintendo ( 2018-08-03 10:51:37 +0300 )editanswered 2017-10-22 02:21:13 +0300
I've had the same problem every morning. Before I go to bed everything works fine but when I get in the car and start my drive to work in the morning I have no network connection. I also see a star or some other symbol inside the wifi icon at the top. Simply rebooting the phone gets everything back to normal. While it's annoying the very fast bootup of the Xperia X negates this being a huge problem for me.
answered 2018-02-21 17:14:29 +0300
Updated to 2.1.4.13 yesterday, hoping that this issue is solved. But nothing changed for me. If network gets lost once, there is no automatic reconnect. I need to go to airplane mode and back to get back GSM connection. Sometimes only a restart helps :/
How is your experience with recent update?
answered 2018-05-15 19:52:29 +0300
I have the same issue. Xperia X (SF 2.1.4.14) loses connection after restarting in a few minutes. I'll try to shed some light on the issue in my case. Here are the facts that I gathered while investigating.
When I'm sharing internet connection from the phone the connection stays longer on when data is transferred eg. YT video or even setting up ping.
When nothing is transferred and the phone is left on its own after a few minutes it seems to auto-disconnect from the network.
The connection gets back only if: 1. I restart the phone. 2. I switch plane mode off->on (sometimes twice) 3. I restart the ofono service using terminal (also twice)
Using the advice linked in this thread https://together.jolla.com/question/177574/mobile-network-issues/ I managed to gather logs from ofono service.
This is log after restart: The error "Requested file structure differs... " seems to be irrelevant.
May 15 17:36:56 Sailfish ofonod[16278]: [grilio] Deserializing RIL1
May 15 17:36:56 Sailfish ofonod[16278]: SIM card OK
May 15 17:36:56 Sailfish ofonod[16278]: [grilio] Cancelled RIL1 request 73 (0000000e/0000000e)
May 15 17:36:56 Sailfish ofonod[16278]: [mce] Name 'com.nokia.mce' is owned by :1.1
May 15 17:36:56 Sailfish ofonod[16278]: [mce] Display is currently off
May 15 17:36:57 Sailfish ofonod[16278]: Requested file structure differs from SIM: 6fb7
May 15 17:36:57 Sailfish ofonod[16278]: Registered interface org.ofono.NetworkTime, path /ril_0
May 15 17:36:57 Sailfish ofonod[16278]: data reg changed 0 -> 2 (searching), attached 0
May 15 17:36:57 Sailfish ofonod[16278]: Requested file structure differs from SIM: 6fb7
May 15 17:36:58 Sailfish ofonod[16278]: read_info_cb: 6f4a not found
May 15 17:37:00 Sailfish ofonod[16278]: export_entries_one_storage_cb with ME failed
And the log from ofono stops. In this state I have no connection whatsoever. Restarting again:
May 15 17:39:54 Sailfish ofonod[16707]: [grilio] Opened /dev/socket/rild
May 15 17:39:54 Sailfish ofonod[16707]: [grilio] Serializing RIL1
May 15 17:39:54 Sailfish ofonod[16707]: [grilio] Connected, RIL version 11
May 15 17:39:54 Sailfish ofonod[16707]: SIM card OK
May 15 17:39:54 Sailfish ofonod[16707]: [grilio] Deserializing RIL1
May 15 17:39:54 Sailfish ofonod[16707]: [grilio] Cancelled RIL1 request 73 (0000000e/0000000e)
May 15 17:39:55 Sailfish ofonod[16707]: Requested file structure differs from SIM: 6fb7
May 15 17:39:55 Sailfish ofonod[16707]: Registered interface org.ofono.NetworkTime, path /ril_0
May 15 17:39:55 Sailfish ofonod[16707]: data reg changed 0 -> 2 (searching), attached 0
May 15 17:39:55 Sailfish ofonod[16707]: Requested file structure differs from SIM: 6fb7
May 15 17:39:55 Sailfish ofonod[16707]: data reg changed 2 -> 0 (unregistered), attached 0
May 15 17:39:56 Sailfish ofonod[16707]: data reg changed 0 -> 5 (roaming), attached 0
May 15 17:39:56 Sailfish ofonod[16707]: Activating context: 1
May 15 17:39:56 Sailfish ofonod[16707]: setting up data call
May 15 17:39:56 Sailfish ofonod[16707]: read_info_cb: 6f4a not found
May 15 17:39:58 Sailfish ofonod[16707]: export_entries_one_storage_cb with ME failed
May 15 17:40:08 Sailfish ofonod[16707]: sms received, smsc_len is 8
May 15 17:40:12 Sailfish ofonod[16707]: RIL1> RESPONSE_VOICE_NETWORK_STATE_CHANGED
May 15 17:40:12 Sailfish ofonod[16707]: RIL1> 0000: 01 00 00 00 ea 03 00 00 ........
May 15 17:40:12 Sailfish ofonod[16707]: drivers/ril/ril_network.c:ril_network_state_changed_cb()
May 15 17:40:12 Sailfish ofonod[16707]: drivers/ril/ril_network.c:ril_network_poll_state()
May 15 17:40:12 Sailfish ofonod[16707]: RIL1< [0000019d] OPERATOR
May 15 17:40:12 Sailfish ofonod[16707]: RIL1< 0000: 16 00 00 00 9d 01 00 00 ........
May 15 17:40:12 Sailfish ofonod[16707]: RIL1< [0000019e] VOICE_REGISTRATION_STATE
May 15 17:40:12 Sailfish ofonod[16707]: RIL1< 0000: 14 00 00 00 9e 01 00 00 ........
May 15 17:40:12 Sailfish ofonod[16707]: RIL1< [0000019f] DATA_REGISTRATION_STATE
May 15 17:40:12 Sailfish ofonod[16707]: RIL1< 0000: 15 00 00 00 9f 01 00 00 ........
May 15 17:40:12 Sailfish ofonod[16707]: RIL1> [0000019f] OK
May 15 17:40:12 Sailfish ofonod[16707]: RIL1> 0000: 00 00 00 00 9f 01 00 00 00 00 00 00 0b 00 00 00 ........ ........
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0010: 01 00 00 00 35 00 00 00 ff ff ff ff 08 00 00 00 ....5... ........
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0020: 30 00 32 00 65 00 36 00 39 00 39 00 30 00 31 00 0.2.e.6. 9.9.0.1.
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0030: 00 00 00 00 02 00 00 00 31 00 34 00 00 00 00 00 ........ 1.4.....
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0040: ff ff ff ff 02 00 00 00 32 00 30 00 00 00 00 00 ........ 2.0.....
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0050: 05 00 00 00 35 00 39 00 30 00 31 00 35 00 00 00 ....5.9. 0.1.5...
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0060: 03 00 00 00 32 00 31 00 39 00 00 00 08 00 00 00 ....2.1. 9.......
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0070: 34 00 38 00 36 00 36 00 36 00 38 00 38 00 31 00 4.8.6.6. 6.8.8.1.
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0080: 00 00 00 00 ff ff ff ff ff ff ff ff ........ ....
May 15 17:40:12 Sailfish ofonod[16707]: drivers/ril/ril_network.c:ril_network_parse_response() roaming,(null),02e69901,14,lte,(null),20
May 15 17:40:12 Sailfish ofonod[16707]: RIL1> [0000019e] OK
May 15 17:40:12 Sailfish ofonod[16707]: RIL1> 0000: 00 00 00 00 9e 01 00 00 00 00 00 00 0f 00 00 00 ........ ........
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0010: 01 00 00 00 35 00 00 00 04 00 00 00 65 00 36 00 ....5... ....e.6.
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0020: 38 00 37 00 00 00 00 00 08 00 00 00 30 00 32 00 8.7..... ....0.2.
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0030: 65 00 36 00 39 00 39 00 30 00 31 00 00 00 00 00 e.6.9.9. 0.1.....
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0040: 02 00 00 00 31 00 34 00 00 00 00 00 ff ff ff ff ....1.4. ........
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0050: ff ff ff ff ff ff ff ff 01 00 00 00 30 00 00 00 ........ ....0...
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0060: ff ff ff ff ff ff ff ff 01 00 00 00 30 00 00 00 ........ ....0...
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0070: ff ff ff ff ff ff ff ff 01 00 00 00 30 00 00 00 ........ ....0...
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0080: ff ff ff ff ....
May 15 17:40:12 Sailfish ofonod[16707]: drivers/ril/ril_network.c:ril_network_parse_response() roaming,e687,02e69901,14,lte,(null),(null)
May 15 17:40:12 Sailfish ofonod[16707]: RIL1> [0000019d] OK
May 15 17:40:12 Sailfish ofonod[16707]: RIL1> 0000: 00 00 00 00 9d 01 00 00 00 00 00 00 03 00 00 00 ........ ........
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0010: 0d 00 00 00 50 00 4c 00 41 00 59 00 20 00 28 00 ....P.L. A.Y. .(.
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0020: 4f 00 72 00 61 00 6e 00 67 00 65 00 29 00 00 00 O.r.a.n. g.e.)...
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0030: 0d 00 00 00 50 00 4c 00 41 00 59 00 20 00 28 00 ....P.L. A.Y. .(.
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0040: 4f 00 72 00 61 00 6e 00 67 00 65 00 29 00 00 00 O.r.a.n. g.e.)...
May 15 17:40:12 Sailfish ofonod[16707]: RIL1 0050: 05 00 00 00 32 00 36 00 30 00 30 00 33 00 00 00 ....2.6. 0.0.3...
This time it has a connection.
After the screen turns off, the console stops sending log either. So I press the wake button to get the console working again. To my surprise the logs show that ofono service is also restarting for no reason
May 15 16:27:03 Sailfish systemd[1]: Stopping Telephony service...
May 15 16:27:03 Sailfish ofonod[7216]: [grilio] Cancelled RIL1 request 123 (00000191/00000191)
May 15 16:27:03 Sailfish ofonod[7216]: Exit
May 15 16:27:03 Sailfish systemd[1]: Stopped Telephony service.
May 15 16:27:03 Sailfish systemd[1]: Starting Telephony service...
May 15 16:27:03 Sailfish systemd[1]: Started Telephony service.
And of course after a while the connection is lost.
Then the log contains only: Frames beginning with DATA_CALL_LIST_CHANGED
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_list_changed_cb()
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_list() 11 cell(s):
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=1,mcc=260,mnc=6,ci=1198430,pci=191,tac=12,strength=19,rsrp=105,rsrq=11,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=279,tac=2147483647,strength=15,rsrp=103,rsrq=10,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=195,tac=2147483647,strength=15,rsrp=115,rsrq=20,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=286,tac=2147483647,strength=15,rsrp=109,rsrq=16,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=279,tac=2147483647,strength=12,rsrp=107,rsrq=8,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=0,tac=2147483647,strength=31,rsrp=0,rsrq=0,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=0,tac=2147483647,strength=31,rsrp=0,rsrq=0,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=0,tac=2147483647,strength=31,rsrp=0,rsrq=0,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=0,tac=2147483647,strength=31,rsrp=0,rsrq=0,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=0,tac=2147483647,strength=31,rsrp=0,rsrq=0,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_cell_info.c:ril_cell_info_parse_cell_lte() [lte] reg=0,mcc=2147483647,mnc=2147483647,ci=2147483647,pci=0,tac=2147483647,strength=31,rsrp=0,rsrq=0,rssnr=2147483647,cqi=2147483647,t=0x7fffffff
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_cells_changed_cb()
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_update_entries() /ril_0/cell_0 removed
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_update_entries() /ril_0/cell_1 removed
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_update_entries() /ril_0/cell_2 removed
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_update_entries() /ril_0/cell_3 removed
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_update_entries() /ril_0/cell_4 added
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_update_entries() /ril_0/cell_5 added
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_update_entries() /ril_0/cell_6 added
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_update_entries() /ril_0/cell_7 added
May 15 16:47:23 Sailfish ofonod[7272]: plugins/sailfish_manager/sailfish_cell_info_dbus.c:sailfish_cell_info_dbus_update_entries() /ril_0/cell_8 added
May 15 16:47:23 Sailfish ofonod[7272]: RIL1> DATA_CALL_LIST_CHANGED
May 15 16:47:23 Sailfish ofonod[7272]: RIL1> 0000: 01 00 00 00 f2 03 00 00 0b 00 00 00 01 00 00 00 ........ ........
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 0010: 00 00 00 00 ff ff ff ff 00 00 00 00 01 00 00 00 ........ ........
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 0020: 06 00 00 00 49 00 50 00 56 00 34 00 56 00 36 00 ....I.P. V.4.V.6.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 0030: 00 00 00 00 0b 00 00 00 72 00 6d 00 6e 00 65 00 ........ r.m.n.e.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 0040: 74 00 5f 00 64 00 61 00 74 00 61 00 30 00 00 00 t._.d.a. t.a.0...
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 0050: 10 00 00 00 31 00 30 00 2e 00 31 00 33 00 37 00 ....1.0. ..1.3.7.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 0060: 2e 00 32 00 33 00 2e 00 31 00 35 00 38 00 2f 00 ..2.3... 1.5.8./.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 0070: 33 00 30 00 00 00 00 00 1b 00 00 00 38 00 39 00 3.0..... ....8.9.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 0080: 2e 00 31 00 30 00 38 00 2e 00 31 00 39 00 35 00 ..1.0.8. ..1.9.5.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 0090: 2e 00 32 00 30 00 20 00 38 00 39 00 2e 00 31 00 ..2.0. . 8.9...1.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 00a0: 30 00 38 00 2e 00 32 00 30 00 32 00 2e 00 32 00 0.8...2. 0.2...2.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 00b0: 31 00 00 00 0d 00 00 00 31 00 30 00 2e 00 31 00 1....... 1.0...1.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 00c0: 33 00 37 00 2e 00 32 00 33 00 2e 00 31 00 35 00 3.7...2. 3...1.5.
May 15 16:47:23 Sailfish ofonod[7272]: RIL1 00d0: 37 00 00 00 00 00 00 00 00 00 00 00 00 05 00 00 7....... ........
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_data.c:ril_data_call_list_parse() version=11,num=1
May 15 16:47:23 Sailfish ofonod[7272]: drivers/ril/ril_data.c:ril_data_call_list_parse() [status=0,retry=-1,cid=0,active=1,type=IPV4V6,ifname=rmnet_data0,mtu=1280,address=10.137.23.158/30, dns=89.108.195.20 89.108.202.21,gateways=10.137.23.157]
May 15 16:47:23 Sailfish ofonod[7272]: RIL1> SIGNAL_STRENGTH
I suppose that the problem occurs due to some power-saving mode which makes ofono service fail and when restarted impossible to reconnect. Is there a way to prevent services from freezing? I would do further investigation because my phone is simply unusable right now unless left with Youtube playing all the time.
What should I check now to further investigate the issue?
answered 2018-11-11 10:04:21 +0300
Same here, in germany using otelo (vodafone), interestingly I did not have these issues with my Jolla 1 (SFOS2) which I have been using until a few weeks ago.
Ony my xperia X (SFOS2 and 3), I am experiencing several network disconnects per day, and can only re-connect manually by toggling flight mode.
Let me know if I can help with additional information or logs.
Update 2018-11-26: for me, this seems to happen reproducibly whenever I leave a known wifi network. It always leaves my phone disconnected from mobile network, until activating and deactivating flight mode. However, the phone correctly connects to other (or the same) wifi networks even when it is in the described state.
same here - but with dual sim (vodafone and telecom), it mostly happens when in areas with bad network coverage. After going back to good mobile coverage sim1 or sim2 does not connect to the network again.
jollaticktack ( 2018-11-11 10:45:08 +0300 )editAsked: 2017-10-18 10:17:03 +0300
Seen: 6,533 times
Last updated: Nov 28 '18
same here. sometimes its enough to just change e.g. 3g preferred to 4g preferred but its annoying
NuklearFart ( 2017-10-18 14:10:15 +0300 )editSame here.
NikosAlexandris ( 2017-10-18 16:53:08 +0300 )editShort version: I think the network stack is broken in Sailfish. Hopefully Jolla has the skills and will allocate the needed resources for fixing this critical part of a mobile device.
Longer + rant: My experience with cell network management/coverage/recovery Jolla devices was and is awful. Things went from bad to worse at 2.0 update (around dual sim support addition time). This is by very far my main concern with the phone.
What I have seen on both Jolla1 and JollaC:
These issues have been reported so often and all we got is that embarrassing "restart your phone" workaround.
I was in doubt on who to blame: the modest hardware in Jola1 and JolaC or SailfishOS itself. Given your post related to XPERIA, it seems to be SailfishOS (ofono?ril?), so upgrading to XPERIA won't solve my main problem. XPERIAs pack good hardware. Past experience shown reliable cell connectivity. I don't own a F5121, but reviews are good on the matter.
I start wondering if Jolla owns the engineering knowledge to address these issues at all (this may sound insulting, but it's not my intention - I know skilled engineers in this very narrow and specialised area are not legion)
Whichever at work between lack of skills and/or interest in allocating resources for fixing the basic features of a phone, the result is unreliable network. Unless you live hooked on a bird-frying 4G base. If the latter is the use-case considered by Jolla, I won't see a fix anytime soon :).
rtr2001 ( 2017-10-19 09:36:54 +0300 )edittoday there are much less problems with mobile internet
NuklearFart ( 2017-10-19 15:25:32 +0300 )edit@NuklearFart: I have not noticed any recent mobile network improvement on my say - 2-3y on Jolla1 or since 2nd batch of JollaC has been dispatched. I sincerely hoped it's the hardware, and that XPERIA +SFOS would match Android in this area.
rtr2001 ( 2017-10-20 00:58:38 +0300 )edit