Unless you use app lounge anonymously, try to log out, reboot phone, log in again. Perhaps you need to reboot the phone once again after logging in.
Hello MitraMai! Sorry, Iāve tried absolutely everything, including lots of handset reboots and experimenting with different APNs just in case. The issue stays with e OS itself. FPOS wifi calling on the same handset works. I have created a github issue now, ID backlog#9290
Pixel 4a
sunfish
before: 3.6-a15-20260313593773-community-sunfish
now: 3.6-a16-20260317595985-community-sunfish
not rooted
upgrade went super smooth via ālocal updateā
Thanks a lot for this A-version upgrade!
I replied to the post above, about the app store 
It does not show very clear though. One has to look at the icon in the right upper corner.
Sorry that I canāt help with your issue. I hope it gets solved
This issue no longer happens. WEA WOW works correctly on launch.
I am not sure if this is down to the 3.6 update but when using the default browser, whether using it to view a forum using discourse or after viewing a page from an email, scrolling freezes after scrolling a couple of times and when entering a response on a different forum the ākeyboardā also stops working having to tap the screen several times to continue constructing a post or responding to one.
-
Vendor Name: Fairphone
-
Device name: Fairphone 5
-
Device CodeName: FP5
-
Version of /e/OS or Stock which existed previously: 3.5-A15
-
Not rooted
Sadly, i have the same problem and its not resolved, no mobile data after some time, noticed it after i went out. A quick enable/disable flight mode fix it for some time but not permanently.
But this was also the case with 3.5 so not an issue with the update to 3.6
1 Like
- Vendor Name: Fairphone
- Device name: Fairphone 3+
- Device CodeName: FP3
- Version of /e/OS or Stock which existed previously: 3.4
- Is the device Rooted / Not rooted: Not rooted
Since updating from 3.4 to 3.6, both of my SIM cards are stuck in emergency calls only mode. Toggling flight mode, restarting the phone several times, and removing and replacing the SIM cards with a reboot in-between did not help. The cards are from different providers and use different networks.
Indeed, no improvement regarding low sound of incoming calls when listening via device FP4 (without headset or whatever). When the device is very close to the ear it is difficult to understand the person you talk with. Headset resolves this which, i not always have with me.
Since updating my Fairphone 5 to version 3.6, it has been rebooting periodicallyā¦ Unless Iām in airplane mode.
Hi Marvelous, thanks for the details: I have added also your feedback to the gitlab issue created by @Manoj to collect problems with 3.6.
Everything was ok with e/os/ v3.6 and AA until yesterday morning.
Now, I have a grey screen in car and nothing happens on the FP6.
AA has been updated to version 16.4.661034 via Aurora Store (cause not avalaible in App Lounge). No change, nothing is working.
I donāt understand why, without any update in car nor on phone, one day it works, next day nothing works.
PS : FP6 and car connected via USB : no detection.
- Vendor Name : Samsung
- Device name : S8
- Device CodeName : SM-G950F
- Version of /e/OS or Stock which existed previously : 3.5-s-20260211580871-official-dreamlte
- Is the device Rooted / Not rooted : not rooted
Upgrade OK. Thanks for keeping this device alive !
Welcome to overall software complexity and overall software quality in the 21st century.
1 Like
* Vendor Name: Fairphone
* Device name: Fairphone 3+
* Device CodeName: FP3
* Version of /e/OS or Stock which existed previously: 3.5 official
* Is the device Rooted / Not rooted: **not** rooted
Update went smoothly on 20.03., no break-offs, took just 0:40 hrs, and everything works, let alone the vanishing of āKameraā, which ist āCameraā now.
The usage started out with a consumption of around 34% battery per day and some 3 lasting days. That felt relieving.
During past week usage massively increased, resulting in over 60% usage per day, lowering the lasting time to just over 2 days.
Obvious reason seems to be - guess what - ntfy.
It is using 50% of the whole battery consumption and I canāt keep it from doing so, even switched its connections back and forth with no changes.
So, this results in 3 hrs charging each day, having had an average of 1.5 hrs over a period of over two years (since v1.7).
What the heck does this thing so importantly that its fairly using double even of the mobile network?
Hi,
Trying to upgrade my Sony XA2 āpioneerā from 3.5-a15-20260212581008-community-pioneer to e-3.6-a16-20260318595986-community-pioneer.
Result:
Pressing 3 times the āTry againā button gave the same result. The forth, the device booted again on 3.5-a15-20260212581008-community-pioneer. (as I could see in Settings / System updates) and confirms that /e/OS 3.6 is available as an update (āApply updateā button).
I have some doubts ā¦
a) with 3.4 I had a similar issue (see Feedback for v3.4 - #278 by sonyxa2 ) , but not with 3.5. A coincidence that it is happening with even versions? Better to wait for 3.7?
b) if I try to perform a local update instead of OTA, would it change anything?
Thank you in advance
Fairphone 5 Murena user here.
Update went smooth, and everything seems to work solidly but for one issue:
Sometimes when people call me with the phone in hand and unlocked, the notification to press āacceptā or ādeclineā doesnāt come up for a while. It can take a good few seconds before you even have the option to pick up the call. This has happened for a while now, off and on, on previous versions of E/OS however last night it didnāt come up at all meaning the phone was ringing (it was quite urgent tooā¦) with no way to pick up the call.
Itās rather worrying. Iāve now reinstalled the latest Fairphone OS, but the problem with the touchscreen not responding remains. Does anyone have any idea what might be causing this and how to fix it?
After the installation, I also reset the device in recovery mode, but that didnāt help either.
Has anyone else experienced the same problem as me when installing 3.6 directly onto Fairphoneās āstandardā Android operating system?
I am not totally sure, but for me it feels more often that the touchscreem has problems with responivness after the 3.6 update. especially while working with maps.
I am having the same issue on FP5, non-rooted.