Feedback for v3.0.4

Hi,

Is it normal that Poco x3 nfc(surya) received updated only for A13 ? The A14 version didn’t receive any update since version 2.9. I switched to the A14 version because I was thinking that the A13 version would be depreciate sooner or later, but it seems that it is the opposite.
I also see that surya will receive A15… So, it difficult to know what is the way to follow to be acertain that my device will receive update in the future. Any advice or information ?
But despite this, thank for this great OS!
JJ

  • Fairphone
    
  • The Fairphone (Gen. 6)
    
  • FP6
    
  • v3.0.4

  • Not rooted

1- The default microphone used by any camera app (Default camera app, instagram, etc) has extremely low volume. It cannot be used.

1 Like
  • Vendor Name: Fairphone
  • Device name: Fairphone (Gen 6)
  • Device CodeName: FP6
  • Version of /e/OS or Stock which existed previously: Stock OS version FP6.QREL.15.105.0
  • Not rooted

I have several issues with v3.0.4:

  • as others, no camera zoom and extremely weak sound in videos (should be fixed in v3.1…)
  • screen on-time since last full charge (in Setting → Battery) is always 0 min
  • no way to limit charge to e.g. 80%
  • no AOD and thus no tap to wake

Does anyone else also have 0 min for screen-on time in battery settings?

Also note that the reported date of the security patch level in v3.0.4 is June 1, 2025 and not June 5 as mentioned on the download page of e/OS. This is probably the same thing but it makes me nervous about relocking the bootloader because the FPOS had a security patch properly dated on June 5, 2025.

1 Like

Screen-on time started to output some duration yesterday. I assume it had to learn the behaviour over some time before displaying anything. So that’s no longer an issue.

Vendor Name : Nubia

Device name : Red Magic 5G

Device CodeName : NX659J

Version of /e/OS or Stock which existed previously : /e/OS 3.0.4-t-20250710507810-community-nx659j

Is the device Rooted / Not rooted

Device Built : A13 - e_nx659j-user 13 TQ3A.230901.001 eng.root.20250710.205625

In general its working really well , but I did find some small issues.

  • Some small visual / display glitches:
    – Some times their are some lines appearing on the screen for a very short time, I was able to basically mitigate this issue by changing the display refresh rate from 60Hz to 90Hz (did not check more options as this basically makes the issue dissapear)
    – 5G option is missing , only 3G and 4G available for the network menu.(Only running with on SIM in Slot 1, I will test 2 SIMs in the future)

In general I’m very very happy, I updated from stock Red magic A11 last version (had to downgrade to A10 to install e/OS ).
I installed this on my old phone as a test to see if I would be able to run all my app like banking in e/OS, as I was planning to buy the new fairphone 6.
But its running so well I’m doubting to upgrade now :stuck_out_tongue:

It would be interresting to know if there are any Android version updates planned for this device?

PS : For anyone of interrest with tis version I’m able to run Android Auto with the stubs to be found in the forums and if I use “AAWireless TWO” adapter I can even run the magic maps :slight_smile: (If you have the “no new messages” after the initial setup and reconnecting, try enabling “developer…” in the AAWireless app under advanced setting, this worked for me)
This does not work with direct cable and I get the infamous “no new messages” on the screen

1 Like

I just wanted to post that I’m experiencing the exact same issue that was already posted, namely that the gesture hint is still showing even when you have disabled it in settings.

Fp5

I have 3.04 A14 official running since the beginning of the release. The applounge is very often broken. I am using Aurora store as backup which is much more stable.
Sometimes this also gets blocked due to ,rate limit’.
In that case it helps sometimes to reboot the phone to make it work again.
I am on WIFI at my home network, so that the IP Address is not effected by rebooting the phone.
It looks, that some of the microg service hangs and the reboot ,fixes’ this.

Regards
Oliver

A bug/ unexpected behaviour I encountered on the Fairphone 6:
The Camera quick access button on the lockscreen does not bring the camera on top the lock screen but still requires unlocking the phone first.


edit: I found a setting in the (Open)Camera app to switch on the desired behaviour: Settings → More camera controls → Show camera when locked.

What remains is a discussion on whether this setting should be on by default or not.

(end of edit)

description: When adding the camera as a quick access action to the lockscreen, pressing that button on a locked phone launches the app – but only in the background. The phone remains locked, the lockscreen in the foreground. After unlocking, the camera app is displayed as the current app.

expected behaviour: I expect (and know this behaviour from other phones and ROMs) that the camera app launches elevated above the lock screen, enabling me to quickly take photos without having to unlock the phone first.
The phone stays locked, only the photos taken during this app invocation are accessible in the camera roll. All other actions send me back to the lock screen.

Same behaviour when launching the camera via the power button double press shortcut.

@Manoj I’d love to create an issue in the Gitlab myself, but cannot register an account there due to my e-mail not matching your provider allow list. Please contact me via DM as I cannot send direct messages with my current power level AFAIK.

Hi,
I have a Fairphone 6 with /e/OS 3.0.4 and I noticed the following issues but I am unsure if they appeared with the update or not (I received my phone on July 16 and posibily did not update the OS right away) :

  • sometime, after waking the phone with the “Power” button, the the lockscreen cannot be prompted (I have to shut and wake again);
  • the pin lockscreen does not show the “delete” key (but it is there, i can use it);
  • the camera cannot be opened with the double-tap on the power button (I have to tape my PIN to acces the camera app) (same issue as @ schmittlauch);
  • the camera Zoom does not work (same issue as @ kilou);
  • the Wifi hotspot does not work (it did at the beging, it was one of the first features i tried, definitely before any OS update);
  • some notifications does not seem to prompt on screen or upper bar (mostly Whatsapp’s, i think).

That is most of it. Again, maybe some issues were there prior to the OS update and I didn’t notice.

Hope it helps to pinpoint the issues and solve them anytime soon.

Have sent you a DM. Pl check and share the details on it.

Oh and I also note spurious reboots, occasionaly.

Hope this will be solved with v3.1.1 but I thought it was worth mentioning here.

Vendor Name: Fairphone
Device name: FP4
Device CodeName: FP4
Current Version: e-3.0.4-a14-official

Hello,

I have a big problem. Since e-3.0.x, I can no longer connect to the internet without enabling IP masking in advanced privacy for 4G/5G mode. Before 3.0, I could connect to the internet by disabling IP masking (exposed IP address). This is a big problem, because I can’t connect to some websites that refuse masked IP addresses. I would like to fix this problem, because it annoys me. So I would like to use internet when I’m on ip masking or in exposed ip.

Thanks.

1 Like

Vendor Name: Fairphone
Device name: Fairphone 5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: Probably v3.0
Is the device Rooted / Not rooted: Not Rooted

If I disable animations in the accessibility settings or if I disable transition animations in the developer settings, I can no longer use apps in split-screen mode. When I switch between apps by clicking the active app symbol and selecting “split screen”, normally this app will move up, and I can select the second app. However, with one of these settings disabled, after selecting split screen for the first app, it just moves up by a little bit, and then I get a warning that the Bliss Launcher crashed. Using the Home button, I can go back, but I’m no longer able to use split-screen mode.

This remains a consistent pattern with quick settings, not just the mobile data button (I doubt this is about a particular one). A short tap frequently triggers what only a press-hold should trigger, as if the timespan to distinguish the two gestures (tap vs. hold) had been moved closer to the tap timespan.

Settings - Accessibility - Timing controls - Touch and hold delay ?

1 Like

It was indeed set to “short” and I now changed it to “medium” (hope that’s it). But I still wonder if the default setting might have changed in a recent update – I really do not remember having manually changed it (before today). Or perhaps the definition of short/medium/long changed. :thinking:

Vendor Name: Motorola
Device name: Motorola Edge 2021
Device CodeName: berlna
Version of /e/OS: eOS 3.0 A14
Not rooted
All is well after much testing. Thanks

  • Vendor Name : Fairphone
  • Device name : FP3
  • Device CodeName : FP3
  • Version of /e/OS existed previously : OTA 3.0.1-t-20250606498724-official-FP3 (A13)
  • Is the device Rooted / Not rooted : not

Updater crashes cannot go further :

  • Install OK
  • Button “Install”, but
  • Updater fails after download and preparing reboost
  • Updater app crash
  • If you wait enough or clear its cache, you can restart the app Updater
  • If I enable the next updates, 3.1.1 is displayed and the button “Apply button” is displayed
  • If I try to install again 3.0.4, same behavior
  • some apps crashes when started (Browser, Fennec, Search in Settings, Clock, Calculator, Phone, Music, Gallery, Contacts), it seems to correspond the an interrupted a update of the system and e/os apps before reboot

others ;

  • if i have before doing the Update enabled “Developer options” with “USB Debugging”
  • I don’t find the same issue (even there are a few simulated but it is not storage or the cache of Updater)
  • Storage has enough 4.8GB

I don’t got further and make it worse. For instance, could I reboot? maybe reinstall the previous of the apps, at least Phone.

bug issue : FP3 Updater crashes before reboot and update to OTA 3.0.4 (#8905) · Issues · e / Backlog · GitLab
dedicated thread to follow discussion : FP3 Updater crashes before reboot and update to OTA 3.0.4

Fairphone | FP3+ | FP3 | previously on 2.x A13 community | not rooted

Everything is fine except the GPS, which is unusable in India (worked once after a long time out of perhaps 50 attempts). It works better in Europe, although it is quite slow and unprecise.

There is already a bug report on Gitlab by someone else. I cannot register to the repo, my email addresses get refused.