Thanks once more @AnotherElk .
This is exactly what happened after pinning the 5 GHz WiFi to channel 52. Some time later, my FP3 could not transfer data (apps show offline state and DAVx5 can not synchronize) although the WiFi connection is established. One look into the FRITZ!Box UI and the 5 GHz WiFi is back on channel 116. 
Now I switched off the 5 GHz WiFi to see whether that helps.
i agree to all. FP3 is nearly unusable after the update. issues with all cameras, crashes, freezes… damn!!!
anyone here who could help how to move to FP3 very own OS???
i am a bit sick of /e/OS
Strangely enough, I don’t have any of that trouble with 1.0 on my Fairphone 3. Runs rock-solid, battery doesn’t drain, camera works, Wi-Fi works … I wonder whether I’m spared due to my limited use of messenger and (a)social network Apps. There has to be a cause, one would assume.
Would be interesting to know what are the reasons for these problems.
I don’t use any other messenger than Threema (bought in their web shop, not Google Play), no social media apps and tried different camera apps (none of them works properly anymore).
I agree: Using an esolutions S9 phone, version 1.0 is the least stable of all the releases over the past two years. The app lounge is very buggy, as is the the bliss launcher.
Ok, that was fast. My Fritz!Box keeps the channel mostly for weeks, at least for days, but interference of course will differ from place to place.
AVM Support told me that the reason for the box not simply going back to the fixed channel after a while would be that the box would still detect the interference there, but I can always just fix the channel again, the same one as before, and it will be stable again for a while.
Wi-Fi being complicated tech as it is, I can just live with something like this if I can make it work in some fashion, but I always wonder where this all is headed going forth. Well 
.
If you can live without 5 GHz, and if the 2.4 GHz range isn’t too overcrowded with other networks at your place, it should help.
Ok, so the general App category doesn’t seem to be it.
I have a bit of occasional Signal use and I even have Discord (yeah, I know) running in the background, doesn’t seem to be a problem for me.
Android can be booted into a safe mode, which can confirm whether Apps installed by the user are the cause for an issue (if the issue is gone in safe mode) or not (if the issue persists in safe mode).
It isn’t as intrusive as a factory reset, but it might still be a bit of a pain with App login credentials and some other setup stuff, resources …
https://support.fairphone.com/hc/en-us/articles/360048843571
Curious to know if you’ve experienced any issues with audio playback on v.1?
Any audio playback at all, or what to check exactly?
MP3 playback from external SD card seems fine.
Same playback on 2 different devices connected via Bluetooth seems fine.
I can confirm that:
- I can’t rollback to 0.23 from 1.0 without factory reset
- Element (im.vector.app) isn’t working anymore for video call. Only audio calls. Video calls are clearly crashing the whole phone.
I’d like to use my FP3+ as before 
Interesting - I’m glad it’s working as normal for you!
For context I am experiencing frequent audio stuttering / random pauses in playback on my FP3+ since the update to v.1. It occurs both when streaming music and playing files on the SD card. It occurs regardless of whether the connection is wired, wireless (bluetooth) or even using the internal phone speaker.
Could potentially be a processing issue (?) as it seems to be worse when using the device, but still occurs when sound is being played while the screen is off and no other apps are running in the background.
Interesting indeed.
Since you have a Fairphone 3+, you have slightly different hardware in the audio section of the phone. Other Fairphone 3+ users would have to check whether this might play a role.
Does it make a difference if you set Settings - Battery - Battery saver and performance - Performance profile to the max (“Performance”)?
I have it set to “Balanced”, for reference.
Perhaps worth exploring …
Especially note https://gitlab.e.foundation/e/backlog/-/issues/2414#note_221609 and https://gitlab.e.foundation/e/backlog/-/issues/2414#note_222677.
I was using Lawnchair even before using /e/OS and stuck with it, since I don’t like Bliss (the default /e/OS launcher).
Thanks this addressed a different issue I didnt realise had a fix!
Same here on fp3+
PITA
So @AnotherElk thanks for redirecting me here. Hmm. As mentioned I am on FP3+, I dont run any SoMe, use signal a bit but mostly telegram and whatsapp (yeah I know, no choice) for calls. Whatsapp causes the most issues. I also havent turned on adv priv as i already run openvpn. And I am not on native bliss launcher.
Anything else I can add?
Edit oh yeah, I have noticed that telegram accessing the camera permanently breaks access until restart both for telegram and camera app.
In this case I suspect the new warning system that an app is using the camera as I notice this springing up
1 Like
There goes another promising culprit.
If they don’t find anything on the OS side of things, this could get really tricky.
As mentioned above, I’m on Lawnchair launcher myself.
I should also mention (looking at the other posts) that while my FP3 has a hatful of issues since installing /e/OS v1, problems with wifi or battery drain are not among them.
In terms of potential culprits, I am using this very popular Google Camera Port, which I thought I’d mention, since clashes with camera apps seem to be mentioned a lot above.
The other thing is that while I’m not using Bliss Launcher, I never found a way to uninstall it, so perhaps it could still be the culprit, despite not being in use…? #notadev
I didn’t uninstall Bliss on my phone either, even if I think it should be possible … you were aware of the ADB way, and it didn’t work?
Regarding issues you mentioned … I just called someone via Signal, seems to work for me, I don’t have WhatsApp and Telegram. Camera works, caller ID works, phone’s not less snappy than before updating.
Thanks for all the info, very informative.
I’ve tried a number of different profiles, maxed out the phone does perform slightly better however it unfortunately does not alleviate any of the issues experienced since updating.
I’m using Ruthless Launcher as default. Have tried clearing cache on Bliss even though it isn’t in use, which doesn’t seem to do anything.
Interesting, I wonder if most FP3 users are running v1 without a hitch and issues are limited to FP3+ users only…?
No, I’m on FP3 (not FP3+).
I do though have the upgraded Fairphone 3 Camera+ Module (48MP) - most commonly found in FP3+s - in case that’s a clue, especially given what @Glandos said about Element’s video calls above, and @castoak re: Telegram camera access…
I’ve no idea why that would crash caller ID though, so that one may be a separate issue with the new OS version.
Incidentally, contrary to what I wrote above, I realise I haven’t actually called or been called by anyone via Signal to crash the phone, just WhatsApp and Telegram FOSS. I just tested a Signal call and it indeed seems ok.