No, I don’t think you should. If for any reason a “current” build collected by the System updater failed to apply an update, the error would be reported at that point.
If you unlock now you will loose data and you will lose the ability to relock.
Always good to have a little reminder to have some “backup of essentials” strategy for any electronic device.
For me the Easy Installer didn’t work, because the device was not recognized in fastboot mode. Using the cmd line, my device was recognized with adb devices, but also not with fastboot devices when in fastboot mode. The problem was that I didn’t have the Google USB driver installed on my laptop, so it’s probably good to add a step with a link on how to install this driver.
On step 5 of Installing /e/OS from the bootloader it says: * The last command will ask you to confirm on the device to lock the bootloader. I didn’t get this command and the bootloader didn’t lock (official build). Perhaps include a link to: https://support.fairphone.com/hc/en-us/articles/10492476238865-How-to-unlock-and-re-lock-the-bootloader at the end of the documentation.
Here we go again with the versions until 3.0.4, where we see some continuities.
The table hasn’t changed very much:
| subversions | median | versions | ||
|---|---|---|---|---|
| 100% every | 12,86 | 12,86 | 12,86 | days |
| average caring time | 01:45 | 01:40 | 01:35 | per day or |
| 7,34 % | 6,96 % | 6,58 % | daytime | |
| lasting days | 4,24 | 4,18 | 4,13 | |
| usage/hr | 1,06 | 1,07 | 1,07 | % |
A slight increase in caring time comes with a slightly prolonged lasting time.
Keeping in mind that the FP3 is now nearly four years old and in daily use, the battery seems to age slowly which is not a surprise.
In the last months I changed the provider (who got accused by Advanced Privacy to be the top tracker on my phone) and had a strongly different using pattern through my vaccation in April/May, where I went down the Altmühl and the Danube to Vienna by bicycle and heavily used routing. Had to charge twice a day sometimes and mostly did quick charge, which I usually avoid (only 63 of some 1.000 charging circles).
These are the graphs for every single subversion:
The full version comparision is here:
Slightly different is the output, if one just installs the full versions only (I keep installing the release candidates):
Now we are at day 935 of keeping the battery between 30 and 70 percent, fully loading every 10th circle (73 so far, every 11,9 days in average) and noting battery data.
The high usage and low lasting time of v2.9 resulted from my vaccation and - as I learned on the way - from the IP spoofing: Advanced Privacy was the top user until I shut that off on 18.07. Result: the lasting slowly rose from 3,06 days to 4,40 days within a fortnight. Seems to not fit with the new provider.
To me it was unclear what “here” meant:
Maybe it can be specified to:
Git Bash emulates a Linux-like terminal on Windows. You only need the Git Bash terminal emulator, not the Git Bash GUI.
As I ordered a FP6 today, this might be the last update for this device.
The results on day 1.069 of keeping track are the following:
| subversions | median | versions | ||
|---|---|---|---|---|
| 100% every | 12,92 | 12,88 | 12,85 | days |
| average caring time | 01:45 | 01:41 | 01:37 | per day or |
| 7,34 % | 7,04 % | 6,73 % | daytime | |
| lasting days | 4,29 | 4,19 | 4,09 | |
| usage/hr | 1,08 | 1,08 | 1,09 | % |
During this period of time it was 83 times fully loaded to 100%.
The average charging time from 90 - 100% was 1:20 hrs (40 times), the last (99 - 100%) had an average of 23:52 min (40 times).
Battery health is called “Good” by BatteryBot.
And then we have the latest graphs. I kept installing the release candidates (RCs) as they became available, so this is how it actally looked for me.
Power usage:
Charging:
Run time:
Same for the subversions:
If you had installed the full versions only, it might look like that:
I have not been able to manage a visual output that correlates with the time factor and the charging process as well. Sorry for that.
Fairphone has recently changed their domain name by adding shop. at the beginning, so the links to obtain the bootloader unlock code are nomore leading to the page.
Your device requires a code to unlock the bootloader. Get the code here before proceeding with the next steps
Unlock the bootloader
- Allow the bootloader unlocking by following the official FP3 unlock documentation
https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone
https://shop.fairphone.com/en/bootloader-unlocking-code-for-fairphone
all Fairphone devices /e/ install pages are concerned !
So, this is going to be one of the last postings around the FP3 as I’m going to switch to FP6 these days.
Since ntfy came up with v3.3 there is a huge increase of usage to be noticed while there was hardly any change in the using pattern. Presently ntfy seems to use half of the whole energy consumtion and even nearly double as the mobile network:
Here we go with the latest graphs of power usage, charging and runtime/lasting.
As you see I experience a set of the worst versions seen from the perspective of consumption and especially caring time, since the average numbers until v3.2 where as follows:
| subversions | median | versions | ||
|---|---|---|---|---|
| 100% every | 12,40 | 12,38 | 12,36 | days |
| average caring time | 01:49 | 01:43 | 01:37 | per day or |
| 7,57 % | 7,16 % | 6,75 % | daytime | |
| lasting days | 4,15 | 4,12 | 4,09 | |
| usage/hr | 1,12 | 1,10 | 1,09 | % |
Now I find a steady charging rate of about four minutes per percent while due to the high consumption rate and neccessity of longer charging at some caring time way over three hours per day or around 15% of daytime, all of which has more than doubled.
So, I will change to my already dropped in new phone, but I can’t say whether we stay with e/OS, if the outcome is similarly frustrating.
