Feedback for v3.3

Just for the records: This is how my battery history looked this morning:

The numbers are strange, as we know them, and they resemble at least the top users.

Interesting is your suggestion that the reason of exceeded power use might be in the prioritized use of 5G. I understand your speculation and followed up on that. Well, I found this:

I cannot pull back from 5G, because it isn’t possibly activated.

Just for research I activated 3G as prioritized. Let’s see what happens.

bug: USB stick : OTG not working (oneplus 9 pro) lemonadep

  1. /e/OS version:http://e-3.3-a15-20251211556413-community-lemonadep.zip
  2. Device model(s):lemonadep

Just allowed my phone to update to 3.3-a14-20251210556412, now the camera does not work;

Error; FAILED TO OPEN CAMERA. CAMERA MAY BE IN USE BY ANOTHER APPLICATION? ID:0

The torch wont come on and states; ‘Camera in use’

Any chance of a swift update to correct this? Alternately, access to a previous build so I can re-install the O/S? I did look around the website but could not locate a previous build..

Just before xmas, with all my family coming around, and I have no camera for the occasion.. Last build I downloaded was e-3.0.1-a14-20250606498933.ch Suppose I could install that one if I really had to..

Xiaomi

Pocophone F1

Berylium

no idea how to get ‘previous version’, phone updated to 3.3-a14-20251210556412, there is a build number (about phone/build number) 14 AP2A.240905.003, ENG.ROOT.20251210.230712

Also says A15 (community) on website for my phone model.. First install on this phone was e-3.0.1-a14-20250606498933.

After update, camera and torch does not work, also getting the odd error when updating apps eg f-droid, but if I repeat the update, it works.. For the camera I get;

Error; FAILED TO OPEN CAMERA. CAMERA MAY BE IN USE BY ANOTHER APPLICATION? ID:0

The torch wont come on and states; ‘Camera in use’

Just spotted the response from Manoj;

We will continue roll out of builds on Monday. Some device users especially on Xiaomi and Motorola community builds have raised issues with the camera and torch not working. One user had to do a factory reset. The team is evaluating the impact and will resume the release once we have a go ahead from QA on Monday.

I will check from Monday, appreciate you guys look like you are on the case..

Still no update for FP5 :man_shrugging:

As everything is fine currently I will not complain, but shouldn’t updates arrive around every 4 weeks? Last update days 22. October ..anyway, I hope you manage to get back to track and solve the problems.

2 Likes

There is one easy place you can spot why:

Even in this one, if you scroll up…

And I will just guess that you mean ‘official’ build or else I would not know what you mean.

2 Likes
  • Vendor Name: Oneplus

  • Device name: 11

  • Device CodeName: salami

  • Version of /e/OS or Stock which existed previously: 3.2 A15

  • Is the device Rooted / Not rooted: not rooted

All working fine so far. Thank you team for your hard work!

Many thanks for this advice Mihi. Indeed using local update worked without issues. Never encountered issues before using the integrated online updated so unclear what caused the issue.

Vendor Name: Oneplus
Device name: Nord
Device CodeName: Avicii
Version of /e/OS or Stock which existed previously: 3.2 A14 Community
Is the device Rooted / Not rooted: not rooted

All working fine so far. Thank you team for your hard work!

  • Vendor Name: Google
  • Device name: 4a5G
  • Device CodeName: bramble
  • Version of /e/OS or Stock which existed previously: 3.2 A15 community
  • Is the device Rooted / Not rooted: not rooted

everything fine so far - update went smooth - thanks to the team!

  1. Vendor: Fairphone
  2. Model: Fairphone 3
  3. CodeName: FP3
  4. Previous e/OS version : 3.2-A15-community → 3.3-A15-community
  5. Not rooted
  6. Bootloader: locked

Everything went smoothly. I had been messing around with Android Auto because it didn’t work (before I got to know that we needed to wait for a fix), so I needed to reinstall it. It’s been working well so far, except for the address book, which only displays entries that start with the letter ‘a.’

Any other people with the same problem, or is it just me?

Vendor Name: 2x Fairphone
Device name: 2x Fairphone 3
Device CodeName: 2x FP3
Version of /e/OS or Stock which existed previously:
2x /e/OS 3.2-a15-20251025540112-community-FP3
Is the device Rooted / Not rooted: 2x Not rooted

No issues with updating, now 2x on 3.3-a15-20251213556761-community-FP3.

The following things work for me (2x):

  • Call / be called
  • Send SMS / receive SMS
  • Notification LED
  • Alarm
  • Internet via Wi-Fi
  • Internet via mobile network
  • Wi-Fi hotspot
  • Location
    • Settings - System - microG - Self-Check: all ok, including location permissions
    • Settings - System - microG - Location - Wi-Fi location - Request from online service: enabled
    • Settings - System - microG - Location - Wi-Fi location - Request from Hotspot: enabled
    • Settings - System - microG - Location - Wi-Fi location - Remember from GPS: enabled
    • Settings - System - microG - Location - Mobile network location - Request from online service: enabled
    • Settings - System - microG - Location - Mobile network location - Remember from GPS: enabled
    • Settings - System - microG - Location - Location server - Use /e/OS’s location system: enabled
    • Settings - Advanced Privacy - Geolocation: Exposed
    • Settings - Advanced Privacy - Geolocation - Use my real location
    • Settings - Location - Use assisted GPS: enabled
    • Settings - Location - Location Services - Wi-Fi scanning: enabled
    • Settings - Location - Location Services - Bluetooth scanning: disabled
    • Settings - Location - App location permissions - “Allowed only while in use”: Apps are listed
  • Compass
  • Screenshot
  • Main camera (original FP3 Camera module, not +) photo + video
  • Selfie camera (original FP3 Top module, not +) photo + video
  • USB connection to PC / MTP
  • MyPhoneExplorer 2.3
  • Bluetooth (music playback, data connection)
2 Likes

Do we have any info on when the official builds for Fairphones are going to be rolled out? FP6 here.

2 Likes

The team is checking as to when the roll out will resume. We had stopped the roll out after inputs from users of Xiaomi and Moto devices of issues in their builds. The development team is evaluation any possible impact on official builds.
Will have more clarity on when the builds will be resumed later today. Will update.

6 Likes

The Update of v3.3 rollout is as under:

  • Xiaomi and Motorola device builds of v3.3 will be on hold and removed if already showing up on the server
  • A fix specific for Xiaomi devices will be rolled out as v3.3.1
  • For the issue on Motorola devices we are still investigating.
  • The release of v3.3 will continue for all other devices - Official and community as we these issues were device specific.
8 Likes

Vendor Name: Samsung
Device name: Galaxy Tab S7
Device CodeName: gts7lwifi
previously: stock A13
now on e-3.3-a15-20251212556760-community
Magisk rooted

  • Bluetooth keyboard not working!
  • I have no clue how to configure / “use” parental control. After initial setup, I’m missing any kind of detailed configuration.

I would also be interested to know when the official build for the Faiphone 6 will be released.

3 Likes

Manoj said that 1h ago, so for the FP6, it will be soon too (i hope).

4 Likes

As this is my first /e/OS Update. I guess [Settings → System Updates] will notify me / show available Updates after manual refreshing?

2 Likes

Yes, thats how it should work.

1 Like