While Google provides seamless upgrade of Android version, the AOSP Updater does not provide this.
/e/OS official allows Murena to sell devices which are hoped to be able to OTA Android Version Upgrade for their life. This is complex to achieve in a trouble free way so there can be some disappointment at the lag in these builds. Efforts are made to ensure that the builds are also optimised to allow “secure apps” to work where also the Bootloader can be locked. (Working with “secure apps” is a moving target.)
Hi,
I ran the (OTA) update from 3.2 ce to 3.3 ce - the problem with display brightness is now worse:
up to v3.2 it was always getting dimmed to the minimum brightness after some time, but now display is at max brightness and the settings are not respected - same brightness if slider is at min and at max. even a
adb shell settings put system screen_brightness (some value)
adb shell settings put system screen_brightness_mode 0
changes nothing:
Vendor Name Fairphone
Device name FP6
Device CodeName fairphone-fp6 ?
Version of /e/OS or Stock which existed previously /e/OS 3.2
My Moto G30 stopped working after update from 3.2 to 3.3.
It boots, but the system does not load fully: it only shows the background image, a “back” button and sometimes the status bar on the top after I enter my PIN.
It looks like it is booting but it is not responsive to touch and, after a while, it returns to the “bouncing e” screen like it had rebooted.
If anyone have suggestions of what to do, I would appreciate!
Use the try again which should after couple attempts go to the other slot. Which would make it ‘a’ again and I expect you will be back to the state which does boot but is unuseable (3.3)
That’s the recovery mode. You have to boot into the bootloader (fastboot).
How to boot into the bootloader depends on the device you have (see documentation).
I see, thank you for taking the time to reply. Based on the explanation from Manoj, I should not be impacted, since I have not added any new contact addressbook to my account.
* Vendor Name: Fairphone
* Device name: Fairphone 3+
* Device CodeName: FP3
* Version of /e/OS or Stock which existed previously: <dev>
* Not rooted
Every now and then in past time I encountered freezes of the phopne in case I wanted to share pics right out of the camera app (tapping last pic, tapping share, freeze). This seems to be gone.
The current experience does not include any other issues that I’m aware of, BUT as I focus on power usage and battery life, can’t help to point out an average of 2,22 days for the phone lasting without recharging.
This is the worst number by far, as the overall average of lasting since v1.7 for me is 4,21 days. All versions performed over three days, except v2.9, which was in my case result of excessive use of Routing and Hotspot during a vaccation.
Now my provider (?) seems to be the source of the drain, as the mobile network is held responsible for 63% of the power usage.
This is east of problematic and I would very much appreciate it to be adressed.
Issues reported by moto users - @jalmer@LeonardoBarichello@egbert Shared with the build team.
Will update once I get a response from the team.
Assuming all are on the A15 community builds
