I have the problem for some time now, that the other party is too loud when calling via mobile phone. Even at the lowest volume setting, you can almost hear everything, just like with hands-free calling.
With calls via signal, on the other hand, the volume is pleasant. I have also tried another phone app, unfortunately without success, problem remains.
I also found a thread about this in the Fairphone forum, called “fp4-call-volume-too-loud-with-and-without-loud-speakers”.
Making calls with this problem is virtually impossible if you don’t want to damage your hearing and don’t want everyone around you to overhear.
Vendor Name : Fairphone
Device name : one FP3 and one FP3+
Version of /e/OS or Stock which existed previously : e-1.16
Is the device Rooted / Not rooted : Not
No special trouble after various days of use, with the now usual exception of Citymapper which blocks at it first freen screen with no comment (the GPS dot switches on).
This is really specific of Citymapper, as all other mapping/routing softwares do work properly, be it OsmAnd or all bus or train routing things, and it has been failing for more than a year now.
Vendor Name: Fairphone
Device name: FP3+
Version of /e/OS or Stock which existed previously: e-1.16
Is the device Rooted / Not rooted: not rooted
I have two issues, but they were also already in e-1.16. Did not find the best place to report them however, so here we are.
Calendar app
When you choose “go to” and choose a date, you most likely end up at a wrong date. For example I just tried to go to December 8, but landed on December 29. When choosing December 18, I landed on December 25. It seems that you end up at the last weekday in relevant month of the weekday you chose.
So I have flashed e/os on my Fairphone 4. I am very happy in general with the performance, but there is a catch. I cannot lock the bootloader: I have performed the command fastboot flashing lock critical. That worked. But flashing lock just sent me into an eternal loop with the bootloader. Only way out was restore and flashing unlock. Saw a post that there was a similar issue with FP3, but no fix… Is there a fix? I want apps on this phone that required to be unrooted…
thanks a lot! So does that mean that I just have to wait until the release that has the security patches, install those, and I will be in good shape? Bought this Phone in november s o shouldn’t be too long then…
(We can expect the e-1.18 release to be month ahead.)
Even now it might be informative to anyone who might offer any further advice to check Settings > About phone > Android version > Android Security patch level, to see if this still reflects the SPL of the phone as delivered to you.
OK for my Pixel5 (purchased in /e/-shop) not rooted. It was upgraded 30 mn ago with 1.17-t stable release (updated from 1.16 to 1.17 (1.17-t-20231109350751-stable-redfin)).
All functions seems OK except the citymapper app which is generally freezed (no map and/or functions) when I opened it (same pbm as with previous releases (1.15 & 1.16).
I still have the camera pbm (described here or there) : when I take a picture with lens1 the final picture is blurry when I’m not in “auto” mode. It never append when I received my phone from Murena.
Vendor Name : Motorola
Device name : Moto G4 Play (Harpia)
Version of /e/OS or Stock which existed previously : e-1.16
Is the device Rooted / Not rooted : Not
Since my device would’nt upload OTA the update, I tried to flash it with TWRP 3.6.2_9-0 that I used in the first place last year or more when i flashed the e-1.1
It made a mess !
I had to :
format the hole phone,
restore a nandroid backup made before switching to /e/
flash again the e-1.1-q-20220629200240-dev-harpia.zip
test the phone if it work normaly
restore a nandroid backup made before the upgrade (this was a clever choice)
And it is now running normal, I only lost a few bits of data because it took me nearly 3 day to find out how to do.
Vendor Name: Fairphone
Device name: FP3+
Version of /e/OS or Stock which existed previously: [dev-version]
Is the device Rooted / Not rooted: not rooted
The upgrade went smoothly, while I had the display permanently active.
Install time 0:52 hrs.
So far most things are fine, there still is the known camera-focus issue unsolved though.
Only there is a quite poor performance on my favorite subject, the battery usage: It is - after 8 days - about 3.8 days per 100% which makes it a further decrease, as v1.15 performed with 5.7 days and v1.16 with 4,6 days.
It seems to me that Advanced Privacy is a major player in this game.
Please have a look into this and carry on with the good work.
Version of /e/OS or Stock which existed previously: 1.16 (stable)
Is the device Rooted / Not rooted: Not rooted
It is indicated in the Release Notes for Teracube 2e 2020 and 2021: “Fix double tap to wakeup”.
But when I double tap the screen, the display remains black.
So, I don’t see the issue solved or maybe I have not understood what’s meant behind the sentence “Fix double tap to wakeup”.
Version of /e/OS or Stock which existed previously: /e/ OS Version 1.16
Is the device Rooted / Not rooted: Not rooted
Update seemed to go fine, but now the camera isn’t working and the flashlight claims that the camera is in use. The front-facing camera works fine. Have been trying different things to get the camera working but nothing has worked. No one else has reported this from what I’ve seen so maybe I did something to break it…?
EDIT: Reseated the camera module and it’s working fine now
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 1.16-s-20231019342893-dev-FP3
Is the device Rooted / Not rooted: Not rooted
