Yes, I just mentioned it because someone said it usually doesn’t work.
But for me it was the same for wireless and wired lan.
Now it works as it should but if someone talks about birds near my phone I probably will get a lot bird ads again.
So to be clear there never was a connection between dns and wifi security mode.
I found the real solution to this:
Go to Settings => Network & Internet => Private DNS
and switch it on and then off.
First of all: THANKS to Fairphone for keeping FP3 up to date! I really appreciate that they took the pains to implement A13 for such an “old” device (old in the sens of: SOC-manufacturer does not support it anymore).
That said, my FP3 started to “act up” today. I updated to A13 two days ago, and had a flawless day yesterday, doing a longer, GPS assisted hike with lots of usage of the phone, however in airplane mode over a longer period.
Today, on day 2, for reasons I yet could not identify, the phone kindof freezes - sometimes after 10-20 minutes, sometimes after an hour or so: The touchscreen becomes unresponsive, or near unresponsive. If it reacts at all, it mis-interpretes the input, as if system resources for the touchscreen are not enough and it does not react quickly enough to the finger. If I succeed in restarting or switching off the phone, after it has rebooted, the issue remains, i.e. the phone is unresponsive from the beginning on! Only thing that solves it is removing the battery.
Main difference between yesterday and today: Yesterday the phone was mainly in airplane mode or had Wifi, while today I’m mainly on mobile data.
Any ideas? Anyone having the same?
EDIT: Ooooooohhh - now that I move around in the forum and read more, it came back to me - I DID change something today: I activated “Show notifications by swiping across fingerprint reader” (German: Benachrichtigungen durch Wischen über den Fingerabdrucksensor einblenden" - not sure if my translation is accurate), and since the fingerprint reader seems to be a neuralgic point, this may be the cause after all. I deactivated the setting again and will see if it is the root cause.
Since updating my Fairphone3+ to Android13 I have experienced the following glitches
(1) the lowest volume setting for notifications is crazy loud. I cannot turn it down any further, have done in app and on device. Help, it is awful!
(2) volume for calls and volume for notifications are now on the same toggle - this is exceedingly stupid. Is there a fix?
(3) now the bedtime mode seems to stop messages and emails from arriving altogether, whereas previously they were simply silent. There is nowhere in app or in device settings that I can see to change this.
I would like to receive all communications but with no noise. Any fixes?
(4) the auto dimming setting in bedtime mode is messed up - it makes the apps brighter against the background, working in the opposite way from intended. Any fixes?
When doing calls, my FP3 switched on the display every 30 seconds. Which is annoying, as you have to be very careful not to accidentially press the “end call button” with your cheek.
Finally I found the reason: It was caused by the function “Keep screen on while viewing” (off by default). This function can be activated in the Android settings, using the front camera to check if somebody is looking at the display.
Unfortunately this (useful) function is buggy (at least on my phone), causing the mentioned behaviour.
Workaround: Turn off “keep screen on while viewing”. Then the proximity sensor works like a charm again.
I have notice number 5 as well in my FP3+. Many apps take a second before they respond to tapping them (to open the app) on the screen and often there is a general lag in everything.
I noticed that now there is only the google search bar when you swipe up to your apps and want to search for an app. You get the google results first and then “from your apps”. Is there any way to get it back to how it used to be, that you have a search bar that filters your apps when you are searchin for one?
Not on a regular basis, There’s a “Community Manager” but who has other duties I believe. Fairphone employees do not systematically read the forum, which is there for the community. They publish official notices mostly about updates or for running beta test programmes for example. The only way to make sure they get the message and ensure follow-up is to contactsupport through support.fairphone.com, or by telephone or through the My Fairphone app. When you contact them, you can of course point to a forum thread which might contain information relevant to the problem you’re reporting.
since i updated my fp3 to android 13,
it randomly gets stuck - after the screen went black theres a >75% chance you cannot get back and have to restart the phone…
can anyone help - what is the solution ?
when it does not come back from black-screen, this crap is unusable cause i cant do anything when a call or message comes in… (except restarting … EVERY TIME !!! )
Since updating the OS on my FP3+ the phone has become very unstable. Screen brightness was constantly changing and had to disable auto adjust.
The main issue though is the phone just turns off. Screen is black and I need to remove battery in order to reboot. I am very disappointed. The phone is becoming unusable and is only 2 years old.
Hi. I installed the update one week ago and I experiencing also issues 1, 2, 3 , 5 and 6 (specially the screenshot issue). I do know of the 4th happens because I do not have a SD card inside my device. I created a support request three days ago with id 1067726 with these and other issues like the fact that sometime the device is blocked itself with a dark screen and it is very difficult to get it alive again.
All these stuff are very annoying and wasting time, operations and functionality. I am very happy with my Fairphone 3 from 4 years ago and I never experienced any problem in previous upgrades, but this last one was a real bomb and I honestly think that it was not properly tested nor some changes introduced properly considered previously to the final delivery. I hope Fairphone engineers fix all these issues quickly. On the meantime, I am considering to get another device as I can not be without operate suddenly depending on the random behavior of this last upgrade.