Feedback for v1.9

[iwconfig]

Hey,

thank you! Actually, I mean what you did with the notes tool problem, but this answer here might answer the question as well: Deleting the account and reconnecting. We will see!

Best,
…

[aibd]

@Felpa

The process does not end successfully.

Perhaps you could clarify in what way it is unsuccessful ? Did the phone just “stick” at e-1.8.1-r … or something else ?

e-1.9-r-20230310268291-stable-instantnoodle.zip’ (~47%) adb: failed to read command: Success

Is not a fail in itself (it is an adb error) … you could probably search this forum for a fuller explanation. However having seen that error on the PC it is necessary to wait, connected, > 10 minutes to allow the other 53% of the process to happen. After that wait, often a reboot of the device will fix the issue if the flash did not appear to succeed.

[mungo]

@AnotherElk

The “forcing” part is just a question of resources, effort, and how much you want to complicate inheriting changes from the Android base.

I sense rather a form of negleciance coming from GRGL, because the said space wasting in the pulldown menu now gives me two buttons in a row instead of four as previous. It may be asked for what reason that was changed in the first place.
There is no customization for colours, button forms or size available except the contents of that menu.
That is poor.

[Insidetechnics]

Hello,
I have my Samsung A3 (2016) phone updated fom dev build q1.8.1 to the last dev build q1.9 (1.9-q-20230312268823-dev-a3xelte). The specific model name is: SM-A310F.

Since this update, the camera no longer has any function. Immediately after starting, the application crashes. The message is “Camera has been terminated” (in German: “Kamera wurde beendet”).

Since I read that something was changed in the camera app with the latest update, I strongly suspect this update 1.9 as the cause for the app crashes.

Could this be fixed please?

Thanks a lot!

[Herve5]

@Jayky

Why are there no options to get the round buttons back? Now there are only 4 buttons in quick view instead of 6.

Frankly, this single feature is just the very reason my S.O. won’t upgrade!
Is it just imposed by the new Android ? can it be solved through using another launcher?

[Philippe3]

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

[Felpa]

I managed to update to e-1.9-r with the procedure you suggest.
Thank you.
Best

[tominer]

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

[tominer]

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.

[tominer]

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!

[AnotherElk]

@Herve5

Is it just imposed by the new Android ?

Yes. It’s a design feature of Android 12.

@Herve5

can it be solved through using another launcher?

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.

@Herve5

Frankly, this single feature is just the very reason my S.O. won’t upgrade!

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 …

@Manoj

Users are informed that we plan to drop support for multiple operating systems on the same device.

@Manoj

As yet we do not have a date for this activity and will update once we have a plan in place.

[Alexandre]

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

[hook]

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.

[AnotherElk]

@hook

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.

@hook

Fairphone 3(+) (i.e. actually on both of them). Factory-installed, unrooted.

[HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc

If you read just the start of this text because it gets cited in the forum: There are screenshots here, please have a look at them before assuming you know what this is about. Thank you! As they say, every hint has its history . Where were we? Ah, yes … You are running /e/OS on your device and want to give info about your version to get support, or a simple answer to a question, or anybody else to confirm whether they can observe the same behaviour you observe? Sure … Your device will …

[iwconfig]

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?

[AnotherElk]

@Alexandre

“Trebuchet stopped working”

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 …

@rezoe

You can still start apps by swiping from the top and going to the settings by tapping on the gearwheel, then “Apps & Notifications”, choose app and open it. This way you can especially start App Lounge or F-Droid and install another launcher (I chose Simple Launcher because it needs only two rights). Then in the settings of the launcher (“Start App”) used replace bliss launcher by the new launcher and your phone is at least usable again.

[hook]

Thanks, edited to add info.

[AnotherElk]

@hook

1.9-s-20230310268290-stable-FP3

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.

@hook

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 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

[Almtesh]

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?

[z0lt4r]

“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