Feedback for v1.8

So, out soon in this case (stable).

Version: 1.8.1-r-20230204257076-stable-FP3
Model: Fairphone 3 “FP3”

The lock screen fails to display today’s date since it defaults to a lettered format of some sort, as opposed to what I’d prefer (YYYY-MM-DD universally), and the display only shows the first n characters so the timestamp is pretty uninformative overall:

My primary language is set to English / Canada but I have replicated the same with English / Denmark as well (they appear not to be equivalent to actual locales like en_CA or en_DK on platforms like Ubuntu though, so I dunno)

I have also set the font size back to “Normal” from “Large” and the issue persists

I have also come across a similar, but separate, issue related to date/time formats: the default messaging application cuts off the year, only allowing two-digit (YY) in both English / Canada and English / Denmark respectively, leading to ambiguous formats
I can only upload one image at once, apparently? I guess I’ll get back to it later, then

Here is image number two

Here is image number three

(That spam filter doesn’t really have the desired effect, does it? Would’ve much rather made just one post)

As you can see right up there for me it worked loading up three pics in one post.

1 Like

Oh, yes, now I understand.
I am so trustworthy…

“Updates” no longer respects Do Not Disturb

In the meantime 1.9 stable for FP3 has been confirmed to be out, and as an OTA upgrade to Android 12 (S) apparently, so before you put any more effort into finding and documenting more issues with 1.8.1-r, you might want to update/upgrade to the current version, confirm whether those issues persist, and then continue here … Feedback for v1.9

Oh, right, that’s what the loud notification from earlier on was trying to inform me of? I’ll check it out and see if that happens to solve any of those issues, thanks.

Does anyone know if the Moto G7 Play will ever get another update?

v1.8.1 broke it and don’t see any new builds since then.


The G7 Play is in the list of devices getting /e/OS T (Android 13), so I guess development for this device stopped after v1.8.1 (Android 11) and will soon switch to (probably) /e/OS 1.12.3 with Android 13.

It is highly unusual to have three builds missed with no notification and I see no open issue filed against channel in this Gitlab search. @Manoj please could you confirm if this is a known issue ? Otherwise @g7player I would be inclined to Report an issue, especially, perhaps this

otherwise other potential users have no warning of a problem, except the absence of any recent ROM

I now see that you previously asked for support on this. Were you able to recover use of the phone by

adb sideload

I do not think it was reported earlier. The T build for the device should resolve the issue, only then users will have to migrate to T

The issue for channel is now raised here

1 Like

Had a problem with Signal not working on a Fairphone 3+ with /e/OS 1.12.3-s-20230615299639-stable-fp3, and on a Terracube 2e with /e/OS/ 12.5-r-20230703306302-stable-emerald
updated today fairphone e/OS/ 1.13-s-20230724313396-stable-FP3 and the Terracube 2e e/OS 1.13-r-20230724313393-stable-emerald.
Problem seems to have cleared. At least until the next update.

1 Like

Hint: Feedback for v1.13 :wink:

Problem is still there.

No prob with Signal on FP3+ with e/OS v1.14-s-20230815320616-stable-FP3.

This topic was automatically closed after 29 days. New replies are no longer allowed.