All: With reference to the issue faced by some devices post update to v3.0 as you are aware we have stopped the release.
The team has identified the issue and is releasing v3.0.1: the issue is a 3.0 regression from Advanced Privacy for all users who enabled the “Hide my IP” feature with “Always-on” VPN flag.
v3.0.1 will go out for all devices, even those that have no issues with v3.0
The reason is we want to avoid other devices facing the same bug in the future.
It is important that you update to the v3.0.1 to remain in sync with the upcoming releases
We shall update when the v3.0.1 release will be published.
The v3.0.1 build will need to be sideloaded on the devices when they are published. This is specific to devices which had an issue. For those devices which did not have an issue with v3.0 normal OTA will work.
Sideloading will help avoid overwriting existing user data.
Also note the v3.0.1 and v3.0 builds had the security patches updated so do not try to downgrade to older version as this can cause issues on the devices.
For those who are facing the issue after flashing v3.0 we have a workaround. Please be warned that it might not work for all the devices. The steps are as under:
please read all the steps carefully before starting
connect your phone via USB to a PC
When you arrive on the recovery mode with the error tap “Try again”
Disconnect the USB cable
Wait for SIM pin request
Type your PIN code and validate
Reconnect the USB cable
Unlock your screen
Quickly go to Settings > Network and Internet > VPN > gear icon next to Advanced Privacy > Always on VPN
Tap to disable “Always on”
Tap on “Forget VPN” at the bottom of the screen and “Forget” in the dialog which opens
Disable “Hide my IP” in the Advanced Privacy widget
Attaching a video ( sorry it is in french ) of these steps Murena
I was going to file a bug report with the help of adb. So, this bug report is no longer necessary ?
Many thanks to the Murena team for helping us.
For your information, when I performed the official update to E/os 3.0 via my smartphone, all the advanced privacy options were checked (including hiding my IP address), and so, when the system rebooted, these options were active (I assume). What I noticed is that when I got to the interface, all the advanced privacy options were unchecked (in red). Advanced privacy is sometimes buggy (no longer accessible via the gear icon), requiring you to go to settings. Yesterday, I had problems connecting to the internet. After a few tries, it worked. Probably some issues with the 3.0 installed.
I’m running a test. I disabled all the advanced privacy options. I will shutdown the device for 30 minutes and turn it back on after 30 minutes to see if my FP4 boots normally.
@Manoj for my Pixel 5 this process doesn’t work.
The failure point is after step 8 : as soon as I unlock the screen the phone restarts automatically so I have no time to change the settings unfortunately.
I’ve tried the plug/unplug of the USB method you mentioned at steps 4 and 7 but it did not gave me more time to change settings after I entered the pin code…
The feedback has been shared with the team. As mentioned the workaround may not work for all cases. We will check if there are other options available as workaround.While we wait for v3.0.1
Ok. No change. When the device is off during a long time, and whether I start it, the screen that asks me for the PIN code appears after a while, and the device is automatically stopped. I turn on the FP4, and the Recovery screen is present. ‘Try again’ option and normal start. I think I will wait the 3.0.1 update to see what happens.
Hello, I would like to report a bug on e/OS 3.0, cmf phone 1.
1- Create a note with the Notes application.
2- Pin the note to the home screen.
3- go to home screen
5- Go to the Notes application
4- Delete the note from the Notes app.
Result: impossible to delete the pinned widget on the home screen.
From there we consider that the user is able to run a terminal, in order to run adb command. Please refer to the Install adb on your computer if needed.
Check the link between the device and the computer
Firstly, you have to check that your computer is able to see your device and that this one is into the sideload mode. You can check that with the following command on a terminal:
command
adb devices
output
List of devices attached
27771FDH2S008W sideload
If you can see a similar output your device is ready for getting the update.
Send the /e/OS 3.0.1 update
In this step you have to paste the file path of the downloaded file. In this example, we apply the /e/OS 3.0.1 update for Pixel 7 device (codename panther).
Vendor Name: Fairphone
Device name: FP4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: e os 2.9
Is the device Rooted / Not rooted: not rooted
Update to 3.0 worked well. But WIFI Calling is not working after the update. Any ideas to get it back?
We are cooking /e/OS 3.0.1, so the rollout will be progressive, 
the left arrow on the top of the sreen:
If you can see a similar output your device is ready for getting the update.
