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:
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..
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..
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.
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!
Previous e/OS version : 3.2-A15-community → 3.3-A15-community
Not rooted
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
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.