/e/ for FP3 (Google free OS)

I can confirm HDR mode doesn’t work. The app stops after the photo is taken.

Another problem: if I use phone memory as default for photos, it’s OK, but if I use my SD card, I get blank photos.

For me the f-droid OpenCamera (not the /e/-fork) works in all modes at least HDR. (It was a hint at the end in the testing channel

Just tried Open Camera from fDroid: HDR works but still have blank photos when saved to SD card

What’s the way firmware updates (modem/baseband/etc.) are being delivered with /e/ + Fairphone?

I got an update notification for e/OS 0.9-2020051454091…

Is it save to update it (on fp3 directly) and does it update the active slot or does it overwrite the inactive one? I have the stockrom at the incative slot for backup.

Good question. I guess you need to ask that in the /e/ forum (if you haven’t done so already).

no i did not, yet. i hoped someone had tested it allredy :stuck_out_tongue:

I ran the update today and have had no issues.

2 Likes

I was responding to libre’s question about firmware updates, not yours about the slots.

It took roughly 30min to download and apply the update and this is what I found: after using the update functionality on the phone I saw that the active slot has changed.
That’s what I suspected (the update is installed on the background and then it needs a simple reboot) but now I’m sure :wink:

4 Likes

I have also installed it today, no problems so far. I wonder if there are any release notes available? The “Show Changelog” Link in the Updater-dialog goes to nowhere. :roll_eyes:

3 Likes

thx guys. I have intalled it. Looks good so far.

  1. I see that there is at least one way to enable root for /e/ on the Fairphone 3 with Magisk, great! (any opinions on if Magisk is the “best” way to enable root?)

  2. I also see that in order to invoke the Fairphone 3 warranty in case of problems with the phone, I will need to re-flash the phone with the stock Fairphone OS.

If I do need to re-flash the stock Fairphone OS for warranty purposes, would it be difficult if my bootloader is unlocked and the phone is running a rooted /e/? What are the steps? Can anyone advise on this? Thanks.

1: I’m not aware of any. Chainfire still badly missed :frowning:

2: I flashed back to stock rom following this:

Should be even more simple if the bootloader is unlocked (I had to unlock again).

3 Likes

Got it, so it’s doable, great! Thank you!

This explanation of course requires (Debian) Linux.
For us (stupid) Windows users it seems to be a bit more compicated. :wink:
@AnotherElk has already posted a solution in posting #39 in this thread

1 Like

I haven’t tried root yet (stupidly locked the bootloader before realising that I could easily have rooted my phone at that point), but otherwise I’m really happy with /e/. Even the power consumption is visibly better. After the latest update, LiveDisplay also works, so I uninstalled Red Moon, which I had installed as a replacement.

Now my only issue is that I don’t have TTS installed, which is a bit weird when using the GPS. I tried Espeak from F-Droid but it crashes, so I tried Flite and it works. I can now at least use my GPS navigation voice in English. It doesn’t have Greek installed, which offers a lot of hilarious moments when driving in Greece. But that’s currently the least of my worries.

3 Likes

For reference when using OsmAnd for navigation …

4 Likes

Fastboot should work very similar on Windows.