Feedback for v2.1

Vendor Name: Samsung
Device name: Galaxy S9+
Code name: star2lte / SM-G965F
Version of /e/OS which existed previously: 2.0 R stable

Upgraded to 2.1 S four days ago.
Now the battery time is 34 hours.
Before the battery time was about 6 days !!!

Battery use says Android OS(17%) and WAKELOCK(16%). I have never before seen them,

1 Like

@Blars …same issue…

@Mumster normally i wait too to prevent all kinds of issues but now i screwed up by updating way to early… Still no fix and restarting my phone every damm 15minutes…

https://support.google.com/pixelphone/thread/206314448/massive-battery-drain-when-idle-after-the-march-2023-update?hl=en

@Blars @xancudo

1 Like

Galaxy S8
Update from 2.0-r-stable to 2.1-r-stable
Not rooted

AppLounge: the application download percentage no longer appears.

So I have been following the power issues that some have mentioned. I have had a couple of nights where my battery seemed to drain. One thing I noticed this AM was that my Apple Airpods where showing as connected in the Devices list. However, my Airpods where in the case.

I have never seen them connected while in the case before this AM. And in the past, when I take them off and put in the case, they would disconnect.

I’m going to monitor and see if this is why I’m seeing random power drains at night. Just wanted to share.

1 Like

Hi Manoj,

Vendor Name : Samsung
Device Name : Galaxy S9
Device CodeName : startle / SM-G960F
Version which existed previously : 2.0 R

The new update (2.1 S) kill my battery

I don’t use my phone and the battery drains very quickly

I experience currently with the 2.0 & 2.1 versions, that the programmed silence mode don’t deactivate back itself as planned…
Does someone else experienced the same ?

Samsung S9+ “star2lte” bought at Murena
SM-G965F
previously running with /e/OS 2.0 (R, stable)
not rooted

Works very well,
Thanks!

All is fine :ok_hand: v2.1 doesn’t require more energy in comparense to v2.0.

1 Like
Vendor Name : Fairphone
Device name : Fairphone 5
Device CodeName : FP5
Version of /e/OS : 2.1-t - stable
No previous version
Is the device Rooted / Not rooted : Not rooted

I had a lot of issues with the camera after upgrading to 2.1-t. No picture saved or corrupted image (see Camera issue on 2.1-t-20240603406607-stable-FP5 - #5 by ctranxuan).
Clearing the camera app. data and cache does not fix the issue (contrary to Feedback for v2.1 - #82 by octobre)

Fairphone
FP4
previous installd: /e/OS 2.0 S
not rooted

Thank you for your excellent work! Every thing is working very good.
Only one issue with the auto brightness: every time I switch on the phone, the Display gets a bit more bright. I need to adjust the brightness manually. This is even more annoying since /e/OS T, because it is no loger possible to slide on the status bar for adjusting the brightness. I need to pull down the status bar twice before I can adjust the brightness.
I appreciate the new privacy setting to deactivate the button highlighting while entering the pin!

Now I found an instruction for calibrating the auto brightness and it seems to work:

  1. go to a dark room
  2. deactivate the auto brightness
  3. manually set the brightness to minimum
  4. activate the auto brightness
  5. deactivate the auto brightness
  6. go to a very bright place
  7. manually set the brightness to a suitable value
  8. activate the auto brightness
4 Likes

Awesome! :smiley_cat: Tried on my Xiaomi Mi MIX 2, auto-brightness is now much more accurate!
@Manoj maybe this post could be moved to How-To?

Done

2 Likes
  • Vendor Name: OnePlus
  • Device name OnePlus 8
  • Device CodeName instantnoodle
  • Version of /e/OS or Stock: 1.21-r-20240323388914-stable-instantnoodle
  • Is the device Rooted / Not rooted: Not rooted

After update OTA and reboot the device enter fastboot.
I manage to reboot to previously version through

sudo -s
fastboot getvar current-slot 
fastboot --set-active=<A_IF_B_OR_B_IF_A>    
fastboot reboot

However, I cannot update to 2.1.

@Iceman @Felpa is your issue similar to this bug on Gitlab

If yes pl add your comments to the thread on gitlab.

1 Like

@Iceman @Felpa

It’s probably the same issue as mentioned by @Manoj .

Did someone to install the update manually using recovery v1.21? I read somewhere here in the forum that someone managed to install doing that. I did not try yet.

Unfortunately, over the day the auto brightness shifted more and more to more bright display. In the dark room I experienced about 10% brighter display than after the calibration. Does some one has an idea?

You may try to “teach” step 3 in a dimmed light, and lower the value at step 7.