One more observation. Wi-fi does not auto-connect until swiping down the notice bar and going through those warnings and tapping the choises. Wi-fi setting has had and does still have auto-connect setting on though.
Same here this morning, all of a sudden, on an FP5.
I think this is more due to the āthingā somewhere on the network used to check for connectivity, since - at least for me - connectivity is in fact otherwise OK.
Iām on 2.2 for a while, probably not related. But I remember some service on Mozilla side being āsoonishā deactivated, and a replacement being set up. Not sure if the switch is already complete or not (or maybe I mix completely different thingsā¦).
I tend to agree with this. It seems (at least from a user perspective) that this isnāt being treated with the seriousness it deserves. Issue #7678 on gitlab says āMilestone [ /e/OS v2.3-rc.2 (expired)]ā, does that mean no fix coming in 2.3 either?
First warning on Murena came as Android system notice, with small bell icon. No warnings on LineageOs 21 phone, Windows or Linux laptops about wi-fi connectivity.
Yeah I just had this issue as well - though Iām (still) on V2.0ā¦ my wifi works fine but FP5 thinks otherwise.
All four of our devices began showing ālimited connectivityā this morning. Two of those are running T v2.2 and the other two are still on S.
1 Like
Same here.
My FP5 that has been running /e/OS 2.2 for several weeks now displays āNo connectivityā even though network runs fine.
However, it seems that some apps (e.g. Dualingo) think that Iām offline because of this. :-/
My guess is that the connectivity check server is somehow unavailable.
This means someone from the team missed out updating the milestone. The team is working on testing a fix. Expect to release with 2.4 .The milestone will also be updated accordingly
Thanks for claryfing and for the potential timeline to fix
Had this one time with S10e this morning. But no problems though.
Samsung
S9+
Device Codename:
Version of /e/OS or Stock which existed previously: 2.1
Not rooted
Worked well until battery went flat and needed reboot. Now phone is nearly a brick due to OEM lock.
See this post
Out of curiousity, did you buy from Murena or flash it by yourself? When did you do it?
I bought it on Fairphone website (main reason: they offer payment split over 3 months) early in March 2024.
I flashed it by myself right away (without easy-installer, not usable for a couple days at the time because some FP5 could get bricked).
I bought mine from Murena November 2023
Wait, you have visual voicemail without the AT&T app on an /e/os phone?!
How can I get that too?!
Bought my one from Fairphone about a year ago and flashed it myself.
- Vendor Name : Samsung
- Device name : Galaxy S8
- Device CodeName : dreamlte
- Version of /e/OS : Stock Rom
- Device Not rooted
Big thanks to the developer team. Everything works fine.
Bought it as-is from Murena, so with E/OS pre-installed by them. I just update OTA.
I have the same problem with the pixel 5
The picture was also blurry with the previous update.
I donāt understand why they donāt deal with it
How to report an issue: Report an issue ā¦ Whereās the issue in the GitLab, the place where thereās communication with and hopefully fixing by the developers going on? Was the issue raised there using other keywords to describe it? I donāt currently see it searching for āblurā or āblurryā.
If there isnāt an issue raised in the GitLab, itās very probable nobodyās working on a fix.
In case thereās indeed no GitLab issue yet (that I donāt find it doesnāt mean there isnāt one) ā¦ Discussions in internet forums (sadly) donāt tend to automagically convert to issues being raised where it matters, somebody will have to raise the issue there.
@Manoj here in the forum is constantly pointing to the GitLab in case of issues.
@Arnaud: with āhere or thereā you are linking to one post where you didnāt encounter the issue yet (not everybody will scroll to the next post) and to one post of mine where I couldnāt reproduce the issue (not everybody will have a look at the whole topic to see other posts where it was reproduced) ā¦ not ideal to make the issue visible to others. Suggestion for linking instead: here or there.