Vendor Name : Fairphone
Device name : Fairphone 5
Device CodeName : FP5
Version of /e/OS or Stock which existed previously : 2.3T
Is the device Rooted / Not rooted : Not rooted
Update was ok but there are (still) some things that dont work or are missing:
I̶t̶s̶ ̶n̶o̶t̶ ̶p̶o̶s̶s̶i̶b̶l̶e̶ ̶t̶o̶ ̶r̶e̶c̶o̶r̶d̶ ̶v̶i̶d̶e̶o̶s̶ ̶w̶i̶t̶h̶ ̶m̶o̶r̶e̶ ̶t̶h̶e̶n̶ ̶3̶0̶F̶P̶S̶ ̶b̶e̶c̶a̶u̶s̶e̶ ̶t̶h̶e̶ ̶f̶i̶l̶e̶ ̶i̶s̶ ̶c̶o̶r̶r̶u̶p̶t̶e̶d̶ ̶-̶ ̶r̶e̶c̶o̶r̶d̶i̶n̶g̶ ̶s̶t̶u̶t̶t̶e̶r̶s̶ → Ok with new camera
Eco Charge is still missing (and maybe limiting charge state)
Chromecast does not work (MicroG crashes) but that could be a Google thing
Changing the USB behavior if connected to PC - No quick panel to change this, only if USB debugging is enabled (also only changeable if USB debugging is enabled and if disabled, then only for some time, then you cannot change it again)
Since 2.1 after some weeks the foundation.e.blisslauncher drains a lot of energy, this starts randomly → EDIT: still high drain
App related issues:
Techniker Krankenkasse - No login with biometric possible because of missing Playstore
Tomorrow - “Its not possible to scan IBAN because device does not support it” (issue with camera?)
REWE - Searching for current location crashes the App
My wife cannot update to 2.4 also because of the download issue
Vendor Name : Murena
Device name : Fairphone 5
Device Code Name : FP5
Version of /e/OS : 2.4-t - stable
Previous version of /e/OS: 2.3-t stable
Is the device Rooted / Not rooted : not rooted
I was somehow lucky that at that time the update appeared it could be downloaded
in one try more then 1 hour but finally it worked - till today.
Similar to the known “reboot” it doesn’t start with the logo and pin, it just
went to the pin entering screen.
Afterwards it showed the dialog which standard launcher I prefer.
So far it looks like not really solving the “reboot” problem, it changed…
Normally the FP5 will be at least restartet once a week, I have a reminder set.
Rest of the time it is on 24 hours, flightmode at sleeping time.
Using Nova Launcher.
I can explain, that why I ask the question.
There is an “/e/OS 2.4.1” dated from October 8th in the update menu. No more info about it, maybe it’s a dev version.
2.4.1 and 4.4.1 is not the same and like that it makes more sense.
You must have the testchannel activated in the developeroptions. Not sure why you activated it butmthink about maybe deactivating it again. It already got you confused one time
Sorry for the typing error.
The test channel is activated because without it it can takes one or two weeks before update appears after the release and it’s a problem when you have a bug like random reboot and the update is supposed to correct it (it was the case several time this year).
Now that the OS is finally truly stable, maybe I don’t need this anymore.
Just a quick update on my specific case : the upgrade manager finally finished downloading and installing the 2.4 version a few days ago, and I’ve been running it without any problem so far. Did not encountered the infamous UI reboot bug yet. I enabled the Fairphone camera and so far it seems kinda cool and efficient. Due to Murena cloud current outage, my Murena account/calendar is not reachable, but I expect it to come back fully when the outage is resolved.
Now I must say after 10 days that the random crashes seem indeed fixed. At least I did not have any while using 2.4.
Now on 2.4.1, lets see if things work from now on.
