[Xperia X] Loss of mobile network
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.
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 +0200 )editSame here.
NikosAlexandris ( 2017-10-18 16:53:08 +0200 )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 +0200 )edittoday there are much less problems with mobile internet
NuklearFart ( 2017-10-19 15:25:32 +0200 )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 +0200 )editMy J1 had some problems with mobile internet but it was kind of ok. The XX startet pretty similar to the bad days but as I said there were no problems today and hopefully the problems dont come back. I did some command line commands (something with ofono) for saving internet options found somewhere around here.
NuklearFart ( 2017-10-20 01:02:42 +0200 )editFresh example: standing still for few minutes in an area with good 4G coverage, phone stuck on 3G. Manual network selection, wait 4 min (!) phone displays two available options, one pre-selected. The phone won't switch by itself the 4G one, despite Preferences . When I manually choose it moves to 4G. Sometimes it remains on 2G. Or with no network at all for minutes.
rtr2001 ( 2017-10-21 02:49:14 +0200 )editSometimes it simply finds the 4G ... but these "sometimes" translate "unreliable"
I used to work in a very poor reception area, and my X would find no signal. Going into and out flight mode gets the signal back.
However, when I left the site, the signal would be lost until I toggled the flight mode, so it really seems that the stack gets stuck or something...
Direc ( 2017-10-24 12:59:33 +0200 )editIt happens to me extremely often, also at places with usually good reception (and where nobody around me has any kind of problem). About one out of three time I want to call someone, I need to go in and out of flight mode.
Also it happens quite often during establishing a call it seems to me, just before it would start ringing the target.
An existing connection is seldomly impaired. Two days ago however I had a very long call. The connection dropped out the first time after almost exactly 2 hours, then (flightmode on, off) about another five times with intervals of 30 to 45 minutes.
When it happens, the reception bar at the far top right becomes a diagonally striped square.
By the way, I had the same or very similar behaviour (not quite as often as with the Xperia X) with my Jolla 1 right up until switching to the X, with the Sailfish OS version on Jolla 1 before 2.1.2.3 (don't remember which that was). Didn't test it with 2.1.2.3 due to the switch to Xperia X. At the time I thought it might be due to the last hard bumps and cracks my Jolla 1 suffered. Not so sure now.
I'll try to get a log excerpt at the next opportunity. If I can send logs or should test something, please give me instructions.
Flox ( 2017-10-24 23:57:04 +0200 )editI do not know if this is related, but I just had a problem where the Xperia became hot, and the battery lost charge quickly.
Using lighthouse I found that the cpu usage was somewhere around 45% most of the time, cpu 6 was running at 100% continuously, and the only process using any cpu to speak of was ofone at > 30%.
A reboot solved the problem.
Kim ( 2017-10-25 00:19:49 +0200 )editCould this be related to this problem?
Flox ( 2017-10-25 00:21:57 +0200 )editOne more detail: This happens often immediately after hanging up a call. The call itself works well to the end. The network is gone right after hanging up (showing the weird square-shaped striped reception indicator (top right of the screen) for half a minute first, then it becomes the normal "trapezoidal" one).
Flox ( 2017-10-26 19:05:39 +0200 )editI have had the same issue as @Flox a few times now.
Direc ( 2017-10-31 19:35:50 +0200 )editRestarting network sublayer about 6times a day to make Sailfish X work on Xperia.
DarkTuring ( 2017-11-08 21:25:09 +0200 )editObserved today, 3x in a row: In an area with bad reception, the phone shows (after an ofono restart) that it is connected. Trying to dial a number results in an immediate "call ended" followed by "connection problem". Afterwards, the phone shows the symptoms described above.
This means that one can't even rely on the connection status displayed, and I am not reachable sort of reliably even if I monitor the connection.
Btw. for anyone affected - the quickest way to get the connection working again seems to be opening the developer terminal, using "devel-su" and then "systemctl restart ofono".
Flox ( 2017-11-22 13:00:01 +0200 )editI experience this behaviour - loss of signal - often, both with Vodafone in Germany and Elisa (Vodafone) in Finland. Very annoying even though I am happy if this is a software issue and nothing to do with my Xperia X HW.
coolhuh ( 2018-01-08 15:45:58 +0200 )editI also have problems with automatic reconnecting to the network. At a nearby lake with bad mobile network coverage my phone regularly loses network connection. After returning to an area with good network coverage the phone stays disconnected. After switching flight mode on/off the phone reconnects - immediately in an area with 4G network - after about 30 seconds in an area with 3G network.
(Sony Xperia X single sim, Sailfish X 2.1.3.7, T-Mobile Germany)
In my Jolla 1 with Sailfish OS 2.1.3.7 the same sim-card works without any problems.
wolfgang ( 2018-01-10 17:52:17 +0200 )editHello Jolla - is there any update on this? I have assembled log dumps from the events (with journalctl), if you think this could help please feel free to contact me. I can also run some tests if it helps. Better soon, however. This impairs my Xperia's use as a daily phone so much I'm very short of abandoning Sailfish, at least for the time being. Great system, great concept, I really don't want anything else, but I'm missing important messages here on a more or less regular basis.
Has anyone had some success at solving this some way? Are your problems gone guys? Starting to wonder if my hardware is broken.
Flox ( 2018-02-06 20:54:28 +0200 )editThe problem is still here. It happened twice today to me.
Giacomo Di Giacomo ( 2018-02-06 23:02:32 +0200 )editI switched to F5122. I no more experience the problem. Same places I move around, same providers. Everything works as expected.
NikosAlexandris ( 2018-02-07 23:39:02 +0200 )edit