@mikiballester (since Marta is on vacation): Confirmed issue of the Android 13 release, not caused by the upgrading process, it would seem. Is this known already?
I have the same problem. My notification light is still turning on if I receive messages, the music continues playing and it vibrates if I doble click the power button to open the camera but the screen continues black until I forcefully turn it off and on again. Did you find a solution?
- try to turn off “auto rotate” → Settings → Screen Auto-rotate screen → off
- try to intall an alternate launcher like Nova Launcher, you can switch back anytime to your standard launcher
Thanks, I will now try turning off the auto-rotate screen and hope it’s enough.
This is just to inform you I also have a couple of these problems, namely:
Delayed SIM unlock prompt after device restart
I have to wait a minute or so to be asked for the PINs of both SIMs.
Device is slow
Both when I unlock the phone and when I’m using it.
When I unlock the phone it immediately asks to enter the pattern but then it takes 2-3 seconds to show the home screen, it didn’t took so much before the update.
I also noticed some apps are less responsive.
I might also have
4. SD Card issues
I had to change the voice recorder app and go back to the preinstalled one as when I started the old one it didn’t worked. It tried to save the audio file just recorded but it complained about an error related to the SD (I uninstalled it and can’t reproduce the problem now).
Moreover, I have one more problem, it’s described here
Just to have a reference here and keep everything together, there could be some problems with videos too, see here
@ shaakunthala what about adding also these issues to the first topic?
After some weeks using my FP3 with Android 13, I have encountered a couple of issues:
The top search bar of the applications grid doesn’t work (default launcher: Quickstep). If I tap on it, it hides the app grid and returns to the home screen. Didn’t find a solution, but not a big problem for me. Maybe this is related to the fact that I have Google app deactivated?
On the other hand, and this is more annoying to me, the notification of activated alarms has changed. The “alarm on” icon is no longer displayed either on the lock screen or in the status bar (except when the status bar is “pulled down”). You can see it in this gif:
I don’t know if this is a new behaviour afterAndroid 11, or if it’s an issue with the Fairphone implementation, but I actually find it a bit of a problem. It seems that this also happens to the FP4 with Android 12.
I have discoverd a new issue since the android 13 update… Connection using mobile data seems to be unstable, when I want to connect to a VPN it is connecting and disconnecting every 2 or 3 secondes (the frequency of disconnection/connection is very regular).
Do you guys experienced this issue ? If yes do ou know how to fix it or how can I signal it to Fairphone ?
Thanks in advance
Did you also encounter the following behaviour?
App is working properly, but you get an “app is not responding” popup every few seconds until you kill it.
I made a video: https://youtube.com/shorts/7yOZsIVbOHI?feature=share
I just remembered another behavior that changed after I updated to Android 13: before, when someone answered a call I made, my phone would vibrate to inform me that they had already answered. However, since the update, this behavior has changed.
I use the Simple Dialer app to call, I don’t know if the problem is with the app or the system. I can’t find a way to fix it either in the system settings or in the settings of the application itself. Any idea?
Leider funktioniert das bei mir nicht. Erst nach erneutem Neustart erscheint die Aufforderung zum Entsperren der SIM-Karte.
Ich muss also jedes Mal das Telefon zweimal neu starten um die Aufforderung zu bekommen.
after updating the FP3 to Android13 (yay!) I cannot hear a waiting sound whenever I start an outgoing call. I can hear the person speak as soon as they pick up the call, but before that there is just pure discomforting silence - not the “toot toot” that gives me the assuring comfort of reaching the person I want to talk to soon.
I didn’t find any settings to enable/disable this specific tone, yet - do you have any idea?
first time poster, thanks y’all
Did you try to turn off VoLTE ?
Hallo, seit dem Update ist, sobald ich jemanden auf dem Mobipnetz Anrufe, kein Klingelton/Freizeichen zu hören, aber beim Anruf zu einem Festnetz funktioniert alles wie gewohnt.
Kann das jemand bestätigen?
Hello, since the update, as soon as I call someone on the mobip network, there is no ringtone/dial tone, but when calling a landline everything works as usual.
Can anybody confirm this?
yes as you can read above, many can confirm to not hear a dial tone and it helps to turn off VoLTE.
I’ve experienced some similar issues with my FP3.
My battery even swelled up, so I will need a new one. YT is crashing, the responsiveness in general is bad, the colors are now dull and also for some of the tools I have to go into settings instead of pressing once like I used to do.
It’s been a terrible experience, I completely regret upgrading the phone.
The battery swelling is for sure not related to the update. But anyway, get a new one, use the old one until it is completely empty don’t recharge it and make sure to store it where it can not inflame anything else until you can bring it t a recycling center or similar.
FairPhone has pushed the update and not warned that the changes were going to happen with the UI or the way hardware buttons would be working going forward - So yes in essence they have indeed broken the phone by not issuing a warning - And they can communicate directly with the user and have done so on other occasions to collect surveys etc. The same with the coloring scheme / dark light settings etc. the bloated menu - Pushing an update without explicit explanation that everything about the way the phone is operated and that you are going to completely change the look and feel that people have spent a long time adjusting is in effect breaking it
My primary reason for doing any upgrade is security, I couldn’t care less for anything else
To summarize you are complaining about changes made by Google between Android 11 and Android 13. Since it was explicitly written that it was an upgrade to Android 13, I think you could also have looked a bit about the changes before updating on a website like Android 13 customisable apps and security controls – Android (Google announces the biggest changes for each version).
No not really - I am annoyed at Fairphone pushing a new update and not warning for example via the system they use to ask for user experience - I 100% believe Fairphone are responsible for upgrades happening to their mobiles and would reccommend they abolish standard Android alltogether in favor of e.foundation so that users regain more control of their sets. But it is funny how people crawl out of the woodworks to defend Fairphone this way. I have been a satisfied user up until now and the second I make a point about issues caused by a Fairphone update you are there to defend and deflect blame to Google. If I wanted Google to maintain and decide everything regarding my set I would probably have bought a Pixel. The point is that if you are building a set, and you brand this set as your own. You also owe it to your buyers to listen to them and adhere to their wishes should enough of them feel there is an issue. Please just stop your apologetic mission and instead if you want to participate look at technical solutions that will re-enable the lost functionality. And if you can’t do that simply stay silent. Fairphone doesn’t need you to champion them like knights, I am already a customer. If anything you are doing the brand a disservice by alienating me from what could be an actually useful technical community rather than several of you going on rants on how stop blaiming fairphone.