Feedback for v1.11

[Dave1]

Google Pixel 3a

Most everything works fine, except I’m also having a battery drain issue. Normally, overnight battery drain is around 5%, a little more if there’s bad reception, but not much more. After the latest update the overnight battery drain has been major. For example, last night I went to bed with 94% battery and woke up this morning at 15% battery where normally I would have had around 90% battery this morning. I waited about a week to post this because I know there can be some battery issues after an update that work themselves out quickly, but this doesn’t seem to be correcting itself.

[stanwood]

Indeed, 1.11 S Stable build has not been yet published for the FP4.

Should land next week…

[anon29344687]

@AnotherElk

Is updating the recovery enabled in Settings - Updater - (three dot menu) - Preferences - Update recovery?

Of course! When I use e-Recovery on a device, it is a mandatory default. Only when using Custom Recoverys like TWRP, OrangeFOX or PitchBlack the option is basically disabled.

[El-Barto]

• Vendor Name : Xiaomi
• Device name : Mi 10T Pro
• Device CodeName : apollon
• Version of /e/OS or Stock which existed previously : e-1.10-s-20230413279105-dev-apollon.zip
• Is the device Rooted / Not rooted : Not rooted

No issues with updating (OTA), now on e-1.11-s-20230511288805-dev-apollon.zip

Everything seems to work fine so far.

As always: Thanks for keeping this device alive.

[Hiyoihoi]

Update still not available for my FP4

Does say pending release on the dev post but last update i received within 3 days

[AnotherElk]

@Hiyoihoi

Update still not available for my FP4

Might not be released yet on the stable release channel, if https://images.ecloud.global/stable/FP4/ is any indication.

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

[Skidrow]

Hello,
I don’t know exactly when the problem started. But it seems to me that it has been since the update to 1.11-S. I use a Oneplus 5 (cheeseburger):

Every now and then I have high utilisation due to the media storage and the battery capacity drops quickly.

Does anyone else have this problem?

Kind regards

[urs_lesse]

Just a wild guess: You probably rarely reboot your device (except for the obligatory reboot in the course of an /e/OS update)? My assumption is that following a reboot, Media Storage will rescan your device for media contents which might take some time and energy if there’s a lot of the latter stored on it. Once that scan is completed, battery usage from media storage should drop to a low level again.

On my own device (that holds 200+ GB of music), I have stopped this problem by using VLC and switching off that automatic scan in VLC.

[Skidrow]

I restart regularly, after three days at the latest.
I have 45 GB in use, out of a total of 128 GB.

I also suspected VLC. But it seems to have had no effect.
After installing 1.11, I noticed that some apps asked for permission to access the memory again.

[urs_lesse]

ok, I actually meant to recommend VLC in this respect because it allows you to disenable the scan. My actual “suspect” for keeping Media Storage “busy” would be the Music app (or any other media player that will not allow to disenable the scan). But I guess in your case the load sounds manageable and might not require what I did (basically I’m navigating my music folder-based only).

[Skidrow]

According to BetterBatteryStats, the com.android.providers.media.module process is responsible.

[urs_lesse]

Just in case you haven’t stumbled upon it yourself yet: https://source.android.com/docs/core/media/media-provider

[Skidrow]

I can’t find anything helpful there.

[Tentos]

Hello @Skidrow,
this seems indeed to be a bug in /e/OS 1.11 on OnePlus devices. The user @Usem and I have observed the same problem on our OnePlus smartphones:

@Usem

Hi @Manoj

• Vendor Name : Oneplus
• Device name : OP8T
• Device CodeName : kebab
• Version of /e/OS or Stock which existed previously : 1.11-beta
• Is the device : Not rooted

As reported previously during the 1.11-beta test sprint. The OP8T still have the battery drain due to the Media Storage as reported here .

@Tentos

• Vendor Name: OnePlus
• Device Name: OnePlus 6
• Device Codename: Enchilada
• Previous version of /e/OS: 1.10-dev
• Device rooted: yes

My device also seems to be affected by the battery drain due to Media Storage, as reported by @Usem for his OP8T. I will see whether the problem persists.

EDIT: I have reverted to /e/OS 1.10 for the time being. I know that this is not ideal (and I had to do a factory reset), but I need a phone with a battery life of at least one day. I hope that the battery drain issue will be fixed in version 1.12 (or in /e/OS Android T).

There is even a bug ticket for the OnePlus 5 here.

The problem was not there on /e/OS 1.10. (I have reverted back to this version although I maybe did it the wrong way, i.e., I had to do a factory reset.)

[Skidrow]

@Tentos

There is even a bug ticket for the OnePlus 5 here .

I left a comment.

The release notes of 1.11 says:

eDrive

• Fix: Uploading file doesn’t check eTag when remote file is missing
• Fix: Improve callback on account removal code
• Fix: format timestamp on chunk upload to match cloud expectation
• Fix: Sync used to be stucked in case of network loss in the middle of running sync

What is eDrive? Is this an App?

[Nicolas_Sas]

Vendor Name: Samsung
Device name: Samsung S9 SM-G960F
Device CodeName: starlte
Version of /e/OS or Stock which existed previously: 1.10-20230416280390-dev-starlte
Is the device Rooted / Not rooted: Not rooted

Just update to 1.11-20230514289715 and everything work perfectly
Well done /e/ team !!!

[Skidrow]

I have no experience with gitlab. Is there anywhere to see if the bug is being worked on?
If so, is there likely to be a hotfix or will we have to wait until 1.12?

[Tentos]

I guess we will have to wait for 1.12. Maybe @Manoj can help and ask the developers?

[Skidrow]

That would really be very helpful.
I can hardly use my device at the moment, don’t have the option of permanent charging.

Flashing 1.10 over 1.11 is not recommended?

[petefoth]

@Skidrow

If so, is there likely to be a hotfix or will we have to wait until 1.12?

/e/ generally don’t release ‘hotfixes’