Decided to give it another try after the latest update.
So far, no restarts for about 20 hours. 5G on, VoLTE on, Wifi/5G switching regularly.
I have good hopes 
Unfortunately, I experienced the same problem. (since the Android 13. update at october 2.)
Sometimes it is rebooting in a loop which can take over 20 minutes then 5 ninutes okay and another 20 minutes of rebooting looping. 
I hoped it would have been solved with the next update, but that was a few days ago, and still suffering the same problem.
I use the phone for work, and not being able to call (back) a customer for at least 30 minutes is driving me nuts.
Reading this topic, I will try to switch of 5G, but I hope for a good updte which solves the problem.
But 5G cannot be the only issue. Iâve never experienced any sudden reboots and I am on 5G pretty much all the time, when I am not at home.
1 Like
No one said that 5G is the only reason, it might very well be provider, setting or whatever specific. Still turning off 5G for those affected helped in I would say most cases, so it remains the common culprit from current knowledge here in this topic.
Its important everyone affected contacts support to provide as much information as possible.
Alright then. In between this topic, 5G sometimes seemed to be THE cause, resulting in people complaining about Fairphone for rolling out A13 âanywaysâ. Of course, I can understand anyoneâs frustrations, but personally, I am more than happy to finally have A13.
Oh, great, so they updated the list on Friday and added this issue. So they officially admitted the problem. Good first step.
1 Like
Sarcasm on // Then Fairphone has recognised the problem at the speed of light // Sarcasm off
2 Likes
Fairphone 4.
Fairphone has been very slow updating their phone to Android 13.
First of they where very slow to update to use the hotspot 5 Ghz, then they where very slow to update the automatic screen dimminig in summertime (warm phone) which made the screen almost unreadably in sunlight. Then they introduces this bug, i made a it reboots several times a day for me, one day up to 11 reboots in one day. Itâs terrible. I do expect a phone for several hundred dollars to have the basic funtionality to work out of the box, and any bugs which renders the phone partly useless fixed ASAP.
I really donât want to ditch this phone, but my patience is running low with Fairphone. Iâll probably wait until the next update and hope that itâs fixed then,
2 Likes
To my knowledge it was there before last Friday. Not sure if thatâs better or worse.
The page says last update 10 Nov. And I checked about a week or 2 ago amd it wasnât listed.
So it is definitively better. No completely random reboots so far .
However I had two reboots on unlocking the phone which has not happened in 2 years before.
Very strange and annoying.
My case with support has not seen any update yet so I guess there hasnât been anything changed in the latest firmware update.
For transparency: the issue was indeed reported during the beta testing phase, and it has been thoroughly investigated but given its nature, it was impossible to reproduce internally and it could have been related to a fault of the beta tester device that originally reported the issue.
In fact, the initial inputs and evidence that came from the beta testing group have been precious to speed up the later investigation.
These kinds of issues are quite complicated to investigate and we are working really hard to identify the root cause and provide you with a stable fix (I can guarantee that we are making progress).
Just wanted to stress that the beta testing program, as well as the issues reported to our customer support team, is crucially helpful in squashing early issues and we take it with seriousness
22 Likes
Sure, but helps with what exactly? 
-
- There is clearly a new (as in: âwasnât there beforeâ) epidemic of reboots, which appeared after the A13 update. Letâs call them âA13-related rebootsâ.
-
- Cases of random reboots have already existed before A13, and those were indeed 5G-related. But they canât be A13-related, since they already existed on A12, and A13 didnât fix or worsen them. Letâs call them â5G-related rebootsâ.
There are clearly two different issues, and making a convenient hodgepodge of those (probably unrelated) issues doesnât help anybody: Magical thinking hasnât ever fixed anything.
On the contrary, it will prevent us from understanding the reasons of those new, A13-related reboots.
Iâd suggest to not follow the usual SOP of stuffing everything in one ragbag thread, but to make two different threads, preventing frustration and allowing people to progressively understand how their problem works and what their options are.
Again, just my 2 cents worth.
.
TL;DR: Reasons to believe there are 2 different issues both causing reboots:
- 5G-related reboots are clearly tied to specific locations and operators: Connecting to a specific mast will reboot your phone, but else it works as expected. A13-related reboots on the other hand are apparently location-independent and seem random (so far).
- People with A13-related reboots report having 5G disabled and yet still experiencing reboots. Unlike people suffering from 5G-related reboots, for which switching off 5G apparently fixes the issue (no more reboots).
- Last but not least, people with A13-related reboots report their problem only started after the A13 update, while 5G-related reboots already happened back on A12.
1 Like
Thank you a lot for stepping in, Francesco. You finally broke the silence. I think the silence is what most people here are scared of. With such critical problems, I think the community would deserve a bit faster official response than after more than a month. It would probably save some work of the support personnel.
4 Likes
Thank you for the official information that the problem has been recognised by Fairphone.
Such contributions are important to ensure that Fairphone users are taken seriously even after the purchase.
1 Like
Just to give a few more information: the issue seems to be related to the 5G radio operations, in particular in mobility scenarios, when the modem jumps between different cells quickly (i.e. on a train trip).
That is the reason why disabling 5G seems to help reduce the occurrence of the issue.
The issue does also affect only some carriers, because of the different infrastructure and radio settings deployed across Europe.
Our team has spent days investigating the issue, even by going back and forth on trains with multiple devices in their hands and we now have a potential solution that we will be testing as extensively as possible during the coming days.
Beware that âpotentialâ is the keyword here, as the solution might not work as expected or might be too unstable to be publicly released, but we are definitely making some progress.
I (or one of my colleagues) will try to keep you informed about that.
19 Likes
Appreciate the much more detailed update on this. As a Fairphone customer, an update like this gives me the confidence youâre working on it. Thank you for going the extra mile - quite literally this time!
2 Likes
Hi @FrancescoSalvatore, donât know if itâs a good idea but do you think it can be helpful if some forum moderator make a poll to understand which countries and carriers are affected?
I know itâs giving up some privacy, but if the poll can be anonymized it could be done.
1 Like
@LukeSkywalker that would be indeed a good idea for future (similar) issues, however, we already managed to find some carriers that are affected and we are able to reproduce it on those networks.
Thank you for the proposal though, in general, it is indeed very helpful to understand where/when/how an issue is happening, and having some statistical data certainly helps the investigation process.
3 Likes
It should still be clear: That will not prevent people from reporting to support who will gather the information needed.
In case anyone wants to write a wiki, if they dont have the proper trust level, what moderators can do is, convert a topic into a wiki, else moderators are not here to write such topics.