Feedback for v1.5

One item I noticed since the upgrade to 1.5 is that the face detection sensor (that turns the screen off when you have the phone by your ear) takes about 1 second to react now, which means sometimes I activate various apps/menus with my ear.

To be entirely honest, I’m not sure this is a 1.5 issue, as I’m comparing a 1.5s on a Samsung S10+ with 1.4r on a Samsung S7edge. The S10+ never had 1.4 or the r version. the S7 got upgraded to 1.5r and has the delay now, but it doesn’t seem to be as long as the S10 (or it’s just my imagination).

Ok, it’s my first time doing this, so hope I got the correct infos…
I updated my FF3+ today to v1.5 (previous version was…v1.4, I think ?)
I had two issues
After the update, the “display recent apps” button didn’t work and showed a “trebuchet keeps on crashing” notice. I could solve this one thanks to @raphm 's earlier message, by putting in a default laucher app (mine was OpenLaucher). Thanks !

The other one was that I lost mobile data (couldn’t connect to mobile data, but the wifi worked). I reset the APN settings for my carrier and it seems to work now.

As for now,haven’t tested everything yet, but the rest seems to work. Curious to see if the battery is going to stay at more or less the same % of use as before…

Hi AnotherElk, thanks for your reply.

I understand you were asking about the Android version, right? It’s Android 11.

I did not know there would be a difference between a reboot and a real shutdown. Did it yesterday and surprisingly enough the battery did not need a recharge until now.

Issue with update to 1.5 Android 12
Device: Fairphone 4
Version: 1.5.1-s-20221102231514-stable-FP4 with Android 12
MicroG: 0.2.24.223616-101 (f1daeaa)-noen
I have now the problem that apps like birday can’t find Birthday dates of contacts in the phone storage.
The permission to get contacts are enabled and i try birday com.minar.birday Version 4.0.1 and Geburtstagskalender+Erinnerungen dev.cwolf.birthdaycalendar Version 2.0.12 with the same issue, both apps in current version.

Issue after updating to 1.5 Android 10
Device: Fairphone 3+
Version: 1.5-20221031230909
MicroG: 0.2.24.223616-96 (f87cb98)-noen

Since I updated, my bank app does not works seamlessly. After the 1st (re)install, it works fine but if I close it and reopen it, it gets stuck on the opening screen. To access it again I have to got the app info and delete its stored data and clean cache. Then when launching it again, I have to redo the whole process as if I just installed it (giving my credentials, get and enter a validation code sent by e-mail, etc…).
I tried disabling Advanced Privacy and modifying microG settings with no luck. As far as I know this only happens with this app on this phone.
Possible hint: I also tried installing it on my old phone (a Cubot Quest not on e/ but on which no google account is set) using Aurora Store and got the exact same behavior with, that’s new, an error message stating “this app won’t work properly except if you accept Google services request to Contacts and SMS. To continue, select Settings > Authorizations and authorize the above listed items” (translated on the fly from french)

Updated Samsung Tab S6 and S10e phone to 1.5.1-s. Restored/Moved all accounts and data from S9 with /e/OS 1.5-q with only one exception:
moving the data of WhatsApp seems to be impossible.
Anyone got this done?

If you have a dev build on source and destination devices, and access to a machine (real ro virtual) running linux, then Android Backup and Restore Tools will do the trick.

Ok, so I was talking too fast when I said it worked now…
I updated my FF3+ to v1.5-r-20221028230215-stable-FP3,
I noticed today that some phone calls don’t get through? Like, they’re not even listed as missed calls or anything, they just don’t exist, as if no one ever called. But some other calls work. Any idea ?

Also, the mobile data must be randomly switching on and off, because I’m getting updates/notifications I shouldn’t have. I tried to switch off the phone and then switch it on again, but it didn’t change anything.

No way to install it, i will have to dig a bit to learn how to do it :worried:

Edit: I panicked, went to open a support ticket for FP4, and read that maybe Safe Mode could fix the problem. I rebooted into SM, the sensor was working ok, rebooted in normal mode again, and it’s working again. I have no idea what might have happened.

I just restarted my Fairphone 4 today and was greeted with a totally new launcher - very slick, but also unfortunately with lots of bugs. Suddenly my keyboard is more wonky, and in the Hey app is just not working properly (it won’t allow me to press the spacebar to go to the next word, and yield weird autocomplete results).

But most importantly, the fingerprint sensor seems completely dead! I can’t unlock my phone, or access my banking features.

Yesterday, my FP4 + e/OS yesterday was a great combo with 99 % of what I needed, and I was recommending it to everybody. Today I’m bummed to see that this update broke so many things, I’m traveling this week and I’m worried I’m going to have problems because of it.

How can I troubleshoot this issue myself, or hopefully fix it??

I love /e/. But my family who bought a murena phone because me and my son told them how nessesary it was is not that happy. Issues that have followed are f.eks: Unstable sendig of MMS, most of the time I get an error message, Problems sending emails from the mail app. The magic earth app have trouble finding where it is because it relies on wifi positionings rather than GPS. I have downloaded maps from my country, but when advanced security is on, it is impossible to use magic earth. To get more people interested in degoogled os, things like that has to work.

You don’t need to disable Advanced Privacy. All you need to do is configure it to use real location (rather than a fake location) - this will fix your magic earth “problem”.

Unfortunately, the “Allow notification dot” option under any app’s notifications section (settings-> apps-> notifications) doesn’t seem to have any effect.

I have disabled it for multiple apps to no effect - I still get the notification dot on all the apps, when they have updates or notices.

Does anybody know if this has been logged as a defect already?

That seem correct, but what is the point of advanced security when my location are exposed? Why can’t Magic Earth, trust more the GPS than wifi location?

If you go in settings and under location services disable “Wifi Scanning”, it will stop using wifi to get your location and be forced to leverage GPS (if you have WIFI enabled, lots of times that is the only available option, as in many indoor settings or when between tall buildings, GPS is not available).

Thanks for trying centaurus. To disable wi-fi scanning was actually a good idea. But sadly it didn’t work. Both bluetooth and wi-fi scanning is disabled, but still Magic Earth use the Ip location to determine my location. This was actually interesting that Magic earth overrule settings.

Thanx for the well done build.

A few days ago i upgraded my FP3 (/+) from 1.5-Q-dev to 1.5.1-S-20221103231515-dev-FP3.
My intentions was upgrading without dataloss as described above. But it seems i made a mistake anywhere. So i did a fresh install and restored the backups, i took before.
Everything is fine now and all (Stock)Apps, i use, work as expected, even those i use from F-Droid and Aurora.
What i miss, is the option of Power-Balancing in batterie-configuration(Q) and at least a implementation of a batterie-charging-limiter. Hope it will come in future.

I upgraded from 0.x-pie-dev to 1.5 R-stable without any issues using the Easy Installer - of course having taken backups beforehand since the device was being wiped. System is solid as a rock with no hiccups whatsoever. Thanks for the great work.

Have discovered one more bug: I have the camera shortcut enabled (two consecutive presses of the power button to launch photo camera).

The shortcut works fine. But if the screen is locked, the camera launches under the screen lock (i.e. until I unlock the screen, I cannot see the camera.)

Do you have the lock screen set up to have the camera available via icon?
Else having to unlock first sounds like it would make sense.