I was on latest FP6 stock android and I think Android security level was 05-07-2026 , and now I just installed /e/os but I see that the security level is 01-07-2026 , I don’t recall the original vendor security level, my question is, can i re-lock the bootlader without triggering anti-rollback?
an /e/OS version update (4.2) is expected for the 24 of this month
Thanks for the heads up, i relocked ny bootloader and all went okay, from what I understood from the docs, that SPL month is important and 01-07-2026 will have anti rollback date of 05-07-2026, so all good here
1 Like
Having used the installer to re-flash my work Fairphone6 with /e/ OS, works just fine. I’m left with an unlocked bootloader. Is there a way to enhance the installer? I ended up using the manual installer instructions Install /e/OS on a Fairphone - The Fairphone (Gen. 6/Gen. 6+) - "FP6" | /e/OS documentation which does the job, it would be nicer if it could be included.
One challenge though in windows to use fastboot one needs to install the android usb drivers, you first have to update the android_winusb.inf to include the fairphone6 and then have to disable driver signing, which you can do via advanced startup. And finally in develepor options disable “OEM unlocking"“. All work, so really nice if the installer could take care of this. As in my view this should be included to have a secure phone
I changed a few things in my behaviour, for I learned that after fully charging it helps to keep it plugged in some 15 minutes to achieve the last tiny bits of the battery being used. In fact it seems to result in a capacity increase after fully charging.
To get a grip on that I introduced a graph for the battery capacity (which I should have done long ago…) into the daily figure.
Also for correct measure I have excluded charging times from the calculation of the cumulated lasting time, which altered the already shown figures.
Generally the charging process tends to start very slow in slow mode, as I found numbers up to 19 min./% for the first %. It ends up with normal numbers around 5+ minutes for the charging of 1% at the end of the process.
A strange experience was the “refusal” of the phone to charge on August 26th, when it was connected to USB 3.0 charging “fast” but did not at all charge for 44 minutes, saying it’d be “full in 10 days”. I switched to another USB 3.0-port, and then fast charged it.
Still the sudden changes to usage are inexplainable, not resulting out of any known changes in my using pattern.
E.g., on August 21st it jumped from 22,5 to 52,8% per day, resulting in the lowest battery number (2%) as I only charged to 60% the day before. Also on October 1st usage jumped from 18,4 to 56,4% per day, resulting in a low battery of 9%.
I can’t help to still suspecting ntfy as a source for this, as it doesn’t show up in the apps-list of battery usage at all, is anounced as one of two apps always active and supposedly included in the “system-apps” that are not specifically shown. For these system apps I have a current usage of 37% which makes them the second highest usage factor, not specifying the actual system parts.
So, the actual numbers at this time look like this:
| Numbers | ||
|---|---|---|
| runtime | 4.203:53 | hrs |
| or | 175,2 | days |
| ø runtime versions | 35,0 | days |
| battery capacity | 4.458 | mAh of 4.527 mAh |
| or | 98,48 | % |
| ø battery | 53,9 | % |
| charging | 160 | times |
| or every | 0,92 | days |
| fast charging | 23 | times |
| Averages | ||
| usage | 1,40 | %/hr |
| or | 33,6 | %/day |
| lasting | 3,03 | days |
| charge 1% | 5:23 | min. |
| 100% every | 13,5 | days |
| caring time | 2:36 | /day |
| or | 10,9 % | daytime |
The figure for battery/runtime/lasting:
The average battery level lies mostly a little north of 50% as to be expected. Only in v3.7.1 it has been lower, corresponding to rather high usage and low lasting times.
The charging:
Another new one for the extreme numbers of daily usage:
You see the average usage mirroring the lasting numbers. The extreme numbers, namely the maximal usage have been corresponding until v3.7.3, especially in v4.0 and v 4.2 the maximal numbers seem to behave more counter-cyclically.
…and the daily oversight:
As you can see here I didn’t charge on many days (see the green, grey and red numbers side by side in the same place), mostly after fully charging but also during times of low usage. Also I tend to stop charging around 60% battery in phases of low usage (as today).
1 Like