Feedback for v1.9

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

1 Like

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:

  1. Motorola G4 Play
  2. Samsung S4 i9505 / i9515
  3. Samsung S5 International (klte)
  4. Fairphone 2
  5. Motorola X Play

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

2 Likes

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.

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

1 Like

Short info for other (FP3) users who are not satisfied with the battery life in /e/OS 1.8.1 and 1.9:

After limiting location access permission of the WeatherOnline app to only while using the app and deactivating the Corona Warn App / CCTG, the energy consumption of microG is hardly measurable (1%). At the same time, the expected battery life has increased to over 2 days despite extensive use of the device (display switched on 4:14 h within 27 h).

Apparently microG doesn’t really go to sleep unless left completely alone for an extended period of time.

I am not yet satisfied with the energy consumption of the mobile network, since (unlike as in 1.8.1) it is still in first place with 26% of the energy consumption, although during the observation period not a single phone call was made, not a single SMS/MMS received or sent and only around 5 MB of mobile data was used and the mobile phone reception at my location is also quite acceptable.

Edit: Another 16 hours later…

What I learned from this:
The background activities of apps have a much bigger impact on battery life than I had expected. In this respect, I am grateful to the “annoying” location pill in the status bar in Android 12 for putting me on the right track.
Let’s see what else can be done about the mobile network…

3 Likes

Vendor: Fairphone
Device: Fairphone 3
Device codename: FP3
Previous version: 1.8.1-s
Device is not rooted

[Edit : Résolu/solved]

Bonjour, depuis la dernière MAJ, j’observe une problématique et deux gênes ennuyantes.

  • le lecteur d’empreinte digital n’est plus activé, il n’y a plus l’option pour l’activer pour le déverrouillage, donc là c’est clairement pas normal. Je ne peux plus m’en servir maintenant. [Il a fallu éteindre et redémarrer après, pour voir le problème se corriger, le reboot seul ne suffisait pas]

  • la barre du haut ou il il y’a la date l’heure, le réseau, elle disparait, il faut tirez vers le bas pour la voir, aucune option pour la maintenir au dessus de tout. [Revenu au devant et toujours visible je ne sais pas comment et pourquoi le lendemain]

  • l’horloge de l’écran de verrouillage est devenu énorme et non configurable, ce qui suivant le fond, ne rend pas agréable la lecture. [ une configuration dans parametre/affichage permet de diminuer sur une ligne au lieu de deux ]

  • les transparences des couches sur les changements d’appli, ou sur le déverrouillage par mdp de l’écran d’accueil, ont disparu et remplacé par un fond opaque. [Non résolu mais ce n’est tellement pas important]

En revanche il y a quand même du mieux pour les autres modifications, et je remercie les développeurs pour leur travail.

[Resolu]


Hello, since the last update, I’ve noticed a problem and two annoying annoyances.

  • The fingerprint reader is no longer activated, there is no longer an option to activate it for unlocking, so this is clearly not normal. I can’t use it anymore. [Solved with shutdown and reboot after. No simply reboot]

  • the top bar where there is the date, time, network, it disappears, you have to pull down to see it, no option to keep it on top of everything. [ solved i didnt know how]

  • the clock on the lock screen has become huge and non configurable, which depending on the background, doesn’t make it pleasant to read. [We have configuration for chang tail in parameter]

  • the transparency of the layers on the app changes, or on the unlock by keypass of the home screen, are gone and replaced by an opaque background. (Minor annoyance)

However, the other changes are better, and I thank the developers for their work.

[Solved]

Merci la communauté

Hello,

A quick search into this forum and even this thread will show you that:

  • A LOT of people had problems with the fingerprint sensor that was solved after a single reboot
  • some people found this big clock on lockscreen horrible and solved it by going to Settings - Display screen - Lock screen - Disable two lines clock.

The rest seems to be artifacts of Android 12 and we can only wait for the next Android version, unfortunately.

5 Likes

Xiaomi Redmi Note 8T, currently running on 1.8

No update for 1.9 available via settings-check for updates.

@Almtesh , @z0lt4r – maybe this is not be your case, but I have found a flaky wifi connection becomes disturbed by a setting only found in System > Developer options.

Please use the “Search settings” feature, search for Mobile data always active. Try disabling this feature.

Maybe it does not show until Developer options is enabled – to enable Developer options go to Settings > About phone > Build number. Tap rapidly on Build number 7 times.

The colour customization was removed by choice to prevent visual inconsistencies: https://gitlab.e.foundation/e/backlog/-/issues/4955

I already tryed this and the problem is still there. I’m trying something else with Termux, I’ll come back here to tell if it works…

After updating to e os 1.9-s-20230310268290-stable-FP4 attempting to install any downloaded apk ends with message “There was a problem while parsing the package”

updated. thanks for the tip

Fairphone
Fairphone 3+
FP3
1.8
Not rooted

Upgraded to 1.9-s-20230310268290-stable-FP3 and having following issues:
Messenger crashes, bluetooth doesn’t work

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

Thank you for your answer, i confirm what did you say. I didn’t see any post to speak about that, whereas i spend a lot of to searching. I had test to reboot my phone and didn’t see the fingerprint in activity. But after you write this, i shutdown my phone, and reboot after. And since this time, i can see the fingerprint is ok.
So I am happy. And now i can see all my problem solved.

Thank you very much.

Long live the e/ communauty.

Hi there,
Here is my feedback :

FP3, Android 12 (not rooted)
The following bugs have been noticed after update from /e/OS 1.8.1 to 1.9-s-20230310268290-stable-FP3

  • earphones no longer work (no sound at all).
  • during phone calls (without headphones), about every other time (une fois sur 2), I do not hear the interlocutor and vice versa (aucun de nous 2 n’entend l’autre).
  • some app crashes noticed when many apps launched. Seems more stable with only one at a time. (Memory management problem ?)
  • seems to work fine for the rest. The problem of calls and headphones are major.

Merci beaucoup !

What I tried is to run termux-wifi-enable true every minute to try to keep the Wi-fi alive, but it does nothing at all.

Since the topic is a general feedback, I have some other problems with this version.
When I use adb backup command, a lot of apps are missing in the result.
I also have a stability problem, apps are often killed (or they crash and they never restart).