Since Android 14, “Automatic network selection” no longer works. I live in Germany on the border with Switzerland and the automatic switching between networks does not work. The switch always remains ON. It is not possible to deactivate the automatic function, although it does not work. Roaming and “mobile data” are switched on and I have an unlimited contract with Deutsche Telekom.
Hi, I have had a slightly different experience. I am in the UK on holidays with a Polish SIM and roaming. I was losing range with Vodafone (automatically selected) so I tried to turn off the automatic selection and choose EE. Now it stays on EE, even when I try to change it, the option is as you said always on
1 Like
I have the exact same problem - I live in France, also on the border with Switzerland, and this bug ruins my daily commuting life as the automatic selection doesn’t work. My contract is also unlimited (with Orange). I find this very annoying, as it used to be fine with Android 13.
I mentioned this issue here: Android 14 is here. Here's what's changed - FP5.UT20.B.041.20240624 - #167 by ceramicplanet
I have also contacted Fairphone, could you also write to them so that this problem gains more visibility? Thank you!
1 Like
Same here. FP5, FP5.UT20.B.041.20240624
Like other users, I had to manually select a different provider and regretted it ever since. When I am out of range of the selected network I get bombarded with nagging notifications about every minute.
I find it hard to fathom why this issue exists in first place, why it has existed for so long and why FP isn’t moving an inch on this issue. We are talking about a bug that has existed for over ten years now, for crying out loud.
post from 2013
(For whatever reason new users can only put two links in a post, so I must omit four other disussions where this exact problem is the issue.)
post from 2023
There is also another thread out there I can not find anymore in which some clown insists that this is “not a Fairphone problem”. I beg to differ.
Does anyone have a solution to this, perhaps something that can be remedied with a shell command?
1 Like
I received another reply [*] from the support today, stating that “To help you further with your request, I will need to ask for advice from the relevant department. As soon as we have an update, we will get back to you.” I think they are looking into it.
[*] The first reply from FP was mainly asking me to debug my SIM-card and mobile data as is, after which I explained this is clearly related to Android 14 and FP, not my provider or SIM-card.
1 Like
I dont think a FP1 topic which is 11 years will add anything to the current issue or is in any way the same issue, I would suggest to delete this referwnce.
This is related to using e/OS, so might or might not help, however is important to add
3 Likes
Ha! Interested to see that others have experienced a similar problem. Despite roaming now and again for many years, I hadn’t seen it before going on holiday this summer. Similar to Meaghan I was in the UK (though with a French SIM), and one day I discovered that nobody could call me, and I couldn’t make calls, even though the phone was seemingly properly connected to the automatically selected network.
So I set a manual selection and didn’t notice any further problems during the rest of my stay.
After I got back to France, the phone had automatically switched back to “Automatic network selection” and had connected to my French operator, but I’ve had repeated notifications saying impossible to connect to selected network (i.e. my proper operator), especially when moving from one cell to another. Rather as though it was still trying to connect to the UK network I’d selected.
I think I’ve got it sorted though.
- Disable “Automatic network selection” (henceforth: ANS) : the list of available networks is shown
- Choose the operator that the phone should be connecting to anyway
(I’ve even seen my OWN operator shown as “Forbidden” in the list: I just waited a bit and tried again) - ANS automatically re-enables itself because I’m in my “home” country and no longer roaming.
Repeat if necessary. I did, several times. The important thing seems to be, to select manually, the network that the phone should be selecting automatically.
I’ve an idea that turning on mobile data may have helped too.
I’ve also seen recommendations to turn Aeroplane mode on / off, or to leave 5G.
I get the impression that the problem happens when the phone switches to ANS by itself when no longer roaming but somehow doesn’t manage the switchover properly. It would be better if the user could have full control over manual and automatic selection, whether roaming or not.
I’m not convinced that this is entirely a Fairphone thing, since I see similar issues with other makes.
Similar problem here.
2 Likes
I could not disagree more. It is of utmost importance to disclose your sources, the more and the higher quality, the better. It’s called “research”, and this rule is standing in its way. Having reflected on this for an entire day, I can only conclude that there is no tangible reason for why a “2-quote” limit should be in place, and I would recommend a discussion about this with your peers in the best interest of this forum.
Thanks for the input. I burned through about two thirds of my battery fiddling around with airplane mode, WiFi and mobile internet connection and its flavors to no avail. This includes running to the basement, where my main provider is not available, but a “roaming partner” is - the closest I can come to simulating a “living on the border” situation. This can’t be rocket science, probably just a character in some configuration file.
To make my stand clear on this: this should not be a problem I should spend time on “fixing”. Since this issue has been out there for 11 years and affected every single FP-model in one way or another, it IS a Fairphone problem.
Thanks for the info, and please keep us update on this! The phone’s behavior after I manually selected a network thus unintentionally mangling something along the way is a nuisance to say the least.
2 Likes
Thats nonsense. I never had any issues with the FP4 or FP5 so far. With the FP2 I always had to select the provider manually when travelling, however there was zero issue to go back to automatic afterwards. And you cannot just deny that with a different OS the reason can well be triggered by the OS
“Nonsense” is a strong word from someone who has just disqualified himself from further discussion: Your logical fallacy is anecdotal . Be a moderator all you want, I don’t care.
My FP5 is as bare bone and stock as it gets, with a maximum of 10 third party apps installed, no root, no custom rom, no task killers or system cleaners. I spent a tidy amount of money on a phone which, at its price point is mediocre, for the reason of buying into the philosophy and business practises of a company comitted to making an actual difference. I have no hard feelings against them, because I am sure they struggle enough, but this issue has been and continues to be theirs to fix. Not mine. Not anyone else’s.
So unless you have actual evidence that disproves my point - or, God forbid, a solution or a workaround - I request you stopped lowering the signal-to-noise ratio in this thread.
Actually there is. You’ll find that this restriction is lifted once you are no longer seen by the system as a totally new member.
More specific info here, and a good start here.
As to the way in which ANS and roaming are managed, I certainly agree it’s flawed, but I’m uncertain as to whether this is an AOSP issue or purely FP. But do by all means take it up with official FP Support. The more reports they receive, the more likely they will be to give the problem higher priority, if it’s something that they can fix. And do mention this thread.
An example of a similar problem that may be relevant (it’s mostly about reverting to ANS) but that has nothing to do with FP. I’ve zoomed on to the last two posts of the topic but do read all of it for context. However, if it’s just a question of forcing a specific network type (as already noted at the end of my previous post) I don’t see the need for a fancy hidden menu, since the type can be set through the standard UI.
I have the same problem. automatic Network selection does not work anymore.
I will write to support.
2 Likes
Thank you Fairphone Support. The new update repaired my problem!
2 Likes
could you please elaborate on that? I am now in Italy and my FP is constantly losing signal unable to kinda find an alternative network on its own, sending me notifications as as often as 10 seconds apart about losing the range
i finally gave in and reported it to the support as well, pointing them to this thread
1 Like
same here as well. im using dualsim (Vodafone and youphone both from the Netherlands) in Switzerland Vodafone was unable to make connection at all, now 3 days in Italy and finally it dit found network (i tried manually as wel but was unavailable to connect to each network)
youphone (KPN network) dit work in Zwitserland and Italy but lots of effort to get it connected and still loos network randomly start beeping and notification.
in Frans it was a struggle as well.
i did contacted Fairphone about it. waiting for a response.
I just tried to reset the mobile network.
looks like the network is now stable again. but i just did that so don’t know if the problem will come back.
settings> Reset> phone network settings reset. need to accept multiple warnings.
the option is above the factory reset option.
so not the reset option at the mobile network settings, that one dit do notting for my.
Just to add to this again: My wife recently traveled to France with her FP5 with O2 Germany as her home network (and current FPOS). I asked her if she had any trouble with her phone finding a network and she confirmed that she didn’t do anything, the phone just automatically chose the roaming network and she could use it. That indicates that it seems to be the combination of phone and network that causes issues for some people.