Vendor Samsung
Device Galaxy S7
Device CodeName: SM-G930F
Version of /e/OS or Stock which existed previously:1.8
Device not rooted
Unfortunately, IZLY app still missing in App Lounge, and it is an “Unsupported application” if i look for “fr.smoney.android.izlu.REC”
But Izly app is still available here https://m.apkpure.com/izly/fr.smoney.android.izly.REC
All my installation attempts have failed, more here: Missing IZLY app on Samsung Galaxy S7
Any help is welcome
I managed to update to e-1.9-r with the procedure you suggest.
Thank you.
Best
Hello,
I upgraded today from e/os 1.8.1-r to 1.9-s on my Xiaomi Mi 8 - dipper.
I followed the upgrade instructions and installed the new data via fastboot sideload. Before I removed the Island user and the security prompts in the settings.
So far so good. The system runs.
But now when I go into TWRP, I am no longer asked for my pin, although I have set it up again. Furthermore the directory /sdcard is shown to me with encrypted data. I think this is not normal, however I have no idea what I could do to restore the pin prompt. Furthermore TWRP does not save the settings anymore.
I hope you can help.
Thanks Martin
Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services
When i use mount from twrp I get:
/dev/block/sda21 on /data type ext4 …
/dev/block/sda21 on /sdcard type ext4 …
/data is readable, /sdcard looks like encrypted data. when I unmount /sdcard and mount it manually again I see the files in readable form.
I have found the solution here:
https://forum.xda-developers.com/t/recovery-3-7-0-12-1-dipper-twrp-unofficial.4490657/
using this version of twrp solves the problem!
Yes. It’s a design feature of Android 12.
I haven’t seen a launcher which lets you customise this, yet.
If you search the internet, there supposedly are Apps which let you customise the quick settings menu in the desired way, but look out for in-App ads etc.
I didn’t dig too deep, though, I’m not using the quick settings menu all day long, and it still does its job.
Sticking with Android 11 only because of this will become kind of silly at the latest when update support for Android 11 runs out, so either about this time next year, or earlier with /e/OS for the Fairphone 3/3+ because of this here …
Hello,
In my Fairephone 3, I have sometimes, an issue with “Trebuchet stopped working” when I try to switch between apps already opened.
And sometimes too, I can’t switch at all beause (I don’t know how to call it) “the menu for switching” is freezed => I restart the phone and it resolve this issue.
I try to swtich slowly and, for now, thoses issues doesn’t appeared anymore…
Edit : sorry, I was on 1.8.1 R and passed to 1.9 S
Something weird I just noticed on Fairphone 3(+) (i.e. actually on both of them). Factory-installed, unrooted.
device: FP3, FP3+
rooted: no
/e/OS version: 1.9-s-20230310268290-stable-FP3
On FP3/FP3+, the notification LED does not work anymore. The LED itself works if you go to Settings and play there with it, but when it should actually show a notification or indicate a low (or charging) battery, it stays blank.
I just checked again, and I can’t confirm this on my Fairphone 3 running 1.9-s-20230311268558-dev-FP3.
LED works for notification as well as charging.
Yup, right, I have that sometimes, too (FP3+ with 1.9-s stable): Switching active apps does not work (i.e. when pressing the “rectangular” button nothing happens). A restart solves it. I did not yet find a good way to reproduce, it just happens every 2nd/3rd day …
Is there a bug issue for this already?
At least the message was observed before.
Does it help if you explicitly set the default launcher again in Settings - Apps - Default Apps - Home App?
If you are using the default Bliss launcher which comes with /e/OS, you could try whether clearing cache and storage of Trebuchet and/or BlissLauncher helps in Settings - Apps - See all … Apps - (three dot menu top right) - Show system - Trebuchet / BlissLauncher - Storage and cache - Clear cache (try this first) / Clear storage (this should reset the home screen and settings).
If nothing else helps …
Thanks, edited to add info.
Interesting, this should basically be the same build as dev (just a different build type), released later once dev users used their dev version for a little while.
I notice there’s a notification setting “Lights with screen on”. Does it play a role if your screen is on or off?
And you checked Settings - Battery - Battery light for anything that would turn the LED off when charging?
If nothing helps, you could raise an issue in the GitLab to make the developers aware and let them have a look … https://gitlab.e.foundation/e/backlog/-/issues
Hello,
I have a Fairphone 3 I installed on /e/OS 1.9 (s-20230310268290-stable) recently (last Wednesday) and everything works very well.
There’s a little problem, the Wi-fi connection is really unstable (like not detectable in the AP’s logs), but only when the screen is off.
It looks like a settings that disables the Wi-fi when the screen is off, but the setting is absent, but I can’t find it, neither on the settings’ search engine, nor on the Internet.
Anyone knows how to disable this annoying setting?
“finally” someone to notice this issue as well. I actually thought I might be the only one having this issue…
It is really bugging me and I have tried to look for all possible settings, but can’t find any. I assumed it has something to do with battery saving, but, well, no option to be found 
Nope, that doesn’t change anything.
But playing around with the settings I noticed that what did have an impact is that the LED suddenly works fine if I make the notification a permanent on light. So the issue seems is only with the blinking LED (regardless of the interval).
Nothing funny there, it seems.
Thanks. I found an issue that seems related and added my info there:
https://gitlab.e.foundation/e/backlog/-/issues/6038
Hi Folx,
I’am using e.OS for quite while now, and more or less I never had problems with it.
But as I updated to v1.9 I realized, that the Camera App on several phones don’t work anymore…
I used several Phones to test and have the same error: Camera has closed again
The phones I used since the v1.9 update are:
On all these Phones the Cam App won’t start anymore… At v.1.8.1 it was running fine… If I use an alternate App like ‘LibreCamera’ or ‘OpenCamera’, it’s working fine…
Any ideas what could happend here?
Thanx in advance and greet’s from Berlin
Pete
Welcome … and good to see a thorough list of affected devices @Pete1
I found similar reported Post #106 I tested a fix here
It would be useful if you were to add your list of devices, if it is the same issue which it certainly looks like.
As mentionned here, is your ‘do not disturb’ option enabled ? It seems it breaks the notification LED on FP3.
Good call.
I currently don’t have it enabled and I use the Easer app to enable it during the night (along with some other stuff) and disable it in the morning.
Just in case I manually turned the DND option on and back off, and I don’t see any changes.
So far the workaround with LED notifications being non-blinking, works for me. But is still a bug. (I’ll add this detail to the bug report though)