Feedback for v4.2

And for the fp6? I can’t find the download img, and the ota is not showing the update

Is not available yet:

2 Likes

I’m trying to download the update OTA, but again it’s slow (around 100KB/s in EU) and interupting. Downloading the zip file from the ecloud.global server goes at the internet line speed (110MB/s). Going to try to do it manually again.

  • Vendor Name : Oneplus

  • Device name : Oneplus 9

  • Device CodeName : Lemonade

  • Version of /e/OS or Stock which existed previously : e/OS/ 4.1.1 a16

  • Is the device Rooted / Not rooted : NO

No problem detected since update. Thanks.

No problems detected so far after the update yesterday morning. :+1:

Had to install 4.2-A15 for the OnePlus 6T manually, because it was taking many hours and needed constant resuming. So I did a local update by downloading the zip file from /e/OS community fajita download , upload it somewhere to the phone (I choose Downloads), proceeded to Settings - Updates - … - Local update.

  1. Vendor Name - OnePlus
  2. Device name - OnePlus 6T
  3. Device CodeName - fajita
  4. Version of /e/OS or Stock which existed previously - -4.1.1-a15-20260718651076-community-fajita
  5. Is the device Rooted / Not rooted - Rooted

No issues detected so far ! Hoping for A16 soon !

  1. Vendor Name - OnePlus

  2. Device name - OnePlus 11

  3. Device CodeName - salami

  4. Version of /e/OS or Stock which existed previously - -4.1.1 A16

  5. Is the device Rooted / Not rooted - not rooted

Update went smoothly. No problems found so far. Thank you for the team!

I got the update notification yesterday. I started the download but it failed due to the network connection. Then, the update is not notifed anymore. I also tried to download the image (4.2-A15], but it does not get validated by the updater. So I am stuck at 4.1.1-A15.

Vendor Name: Fairphone

Device name: Fairphone 3

Device CodeName: FP3

Version of /e/OS or Stock which existed previously: Still on 4.1.1 Community Edition

Is the device Rooted / Not rooted: Not rooted

Tried clearing the cache of updater (system app)?

2 Likes
  • Vendor Name xiaomi
  • Device name redmi note 9
  • Device CodeName merlinx
  • Version of /e/OS or Stock which existed previously 4.1.1
  • Is the device Rooted

No 4.2-AXX version for merlinx

4.2-T is working
Applounge seem repared

If you mean the image from https://images.ecloud.global/community/FP3/, that will not work, because it’s for manual install with fastboot.
For use with the recovery or the updater you would need an OTA update file from https://ota.ecloud.global/api/v1/FP3/community/ (see the “url” lines there for the download links).

It’s still the staggered release phase. Try refreshing the updater with the refresh button at the top right a few times, or a few times more.
It’s how the release gets staggered technically. The OTA update server simply randomises whether to answer a request from an updater with the new version or not.
If this doesn’t help, then what @obacht wrote should help.

5 Likes

I wasn’t aware of this and I downloaded the zip-file from /e/OS community fajita download (for my OnePlus 6T ‘fajita’ device), so not the ota.ecloud.global link. This has worked a couple of times for me. Is there nuance to this why this has worked for me and not for @igi77 ?

The nuance is that you link an OTA_PACKAGE ROM, so it is expected to work.

@AnotherElk effectively asks (as it failed) did you try to update with an Install only ROM designated by a leading IMG-?

1 Like

If you have a look at the command line manual install guides, fajita gets installed via recovery already, while FP3 gets installed with fastboot … Install /e/OS on a OnePlus 6T - "fajita" | /e/OS documentation … Install /e/OS on a Fairphone FP3/3+ - "FP3" | /e/OS documentation.
So the manual install files for fajita are suitable for installing via recovery, while the manual install files offered for FP3 are not. They have differently prepared content. But the updater needs OTA files for updating FP3, too, so those exist for FP3, too.

1 Like

Thanks for the explanation, that clears it up for me :slight_smile:

1 Like

Device: pdx224 (Sony Xperia 5 IV)

Unimportant:

  1. I had to reload the update many times to make it appear.
  2. Still no Android 16.1?

Important:
3. Still no seedvault backup/restore to/from USB??

1 Like

Google

Pixel 3 XL

Version of /e/OS or Stock which existed previously: 4.1.1

Not rooted

And all good !

Vendor Name: Sony

Device name: Xperia XZ2 Compact

Device CodeName: xz2c

Version of /e/OS or Stock which existed previously: e-4.1.1-a15-community

Is the device Rooted / Not rooted: Not rooted

Looks fine after update.

Thanks guys!

  • Samsung
  • S10e
  • beyond0lte
  • Version previously: 4.1.1-a16-community
  • Not rooted

Update went smooth and fast. No issues so far.
Thanks to the team maintaining this device.

  • Google
  • Pixel 4a5g
  • bramble
  • from: e-4.1.1-a16-20260717651035-community-bramble
  • to: e-4.2-a16-20260814662908-community-bramble
  • rooted

It works fine. :slight_smile:

The auto-dimming seems to have gotten way too aggressive; it keeps dropping to 50%, and I have to manually change that to 75%. But I think that started in 4.1.1 and I just hadn’t noticed yet when I posted in that version’s thread.