I have updated to v4.1.1 on my device and it is working well
I updated to v4.1.1 but I am having issues (Please share the issue details on this thread)
I am not able to update to v4.1.1 (Please share the issue details on this thread)
0voters
To report issues with the build or applications raise an issue on gitlab. Ideally first discuss the issue here and check if users of the same device on this build are having the same issue.
When sharing your feedback or issues, Please add the following details
Vendor Name
Device name
Device CodeName
Version of /e/OS or Stock which existed previously
Refer this guide to share more details in your feedback
Do not share test build information on the forum or in this thread
This thread has been created specifically for posting information on official and community /e/OS builds.
To understand the difference between build types refer this guide
Please do not post information or links to /e/OS test builds on the forum.
The test builds are as yet untested and under development and may in some cases cause user devices to soft brick.
Such information can confuse other users who do not see these builds in the updater.
Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds
If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to join the testing team
As part of the testing team you can share your comments on the dedicated testing telegram channel.
Vendor Name: Xiaomi
Device name: Redmi 3S / 4X
Device CodeName: Santoni
Version of /e/OS or Stock which existed previously: e.OS v.4.0 Android 15
Is the device Rooted / Not root: Not rooted
I’am not able to upgrade from e.OS v4.0 (A15) to e.OS v.4.0 A16 or v.4.1.1 because of an recovery error.
This is not an Upgrade package. Looks like the error is saying that the old recovery is not competent to deliver a sideload of different Android version on a dynamic partition device.
Hello,
Thank you for the 4.1.1 update.
I’m surprised that this update is based on Lineage OS 23.0 and not 23.2, which includes the Material 3 Expressive changes.
I need this to use desktop mode efficiently; there was a major update between Material 2 and Material 3 in this regard, and it significantly improves the usability of desktop mode.
Thank you for your work and for taking my comment into consideration.
Ok I see. Normally I always would favorise a clean install over an upgrade, but I’am also unable to clean out the system partition because of another error message. So my hands are bound on this point with the e.OS recovery..
Maybe I’am in luck with a more modern version of Twrp or Orangefox recovery which I found recently for the santoni. I will give them a shot and reply if the situation have changed.
Everything is working fine (from what I’ve tested so far). Only issue is that I was hoping to get onto the offline murena voice to text and able to uninstall my third party option that I had been using (FUTO). But about halfway through downloading the language model, I was met with the following error:
Error: Failed to open microphone: A backend-specific error has occured: InvalidState
Checked permissions, tried rebooting. Didn’t get anywhere.
Possibly related, my Voice Input area in Languages –> Speech –> Voice Input says “none” and doesn’t give me the option of choosing.
Is Murena Voice to Text perhaps only available when using the default keyboard?
I think I found the solution, which might be helpful for folks like myself that use other password apps. Go to your Phones Settings and then change the default Account for passwords to Passwords
I would update the recovery file with the new one before install update by sideloading into recovery and i found this : Recovery file from A16 build doesn’t work
This 2 files isn’t working :
Version of /e/OS or Stock which existed previously 4.0
Not rooted
I think this is again a pretty nice release and I like the implementation of the text to speech function. This tool works pretty well. However, there is one drawback. In the past I have used Whisper+ Whisper+ | F-Droid - Free and Open Source Android App Repository, which works nicely for me, and it has the advantage to toggle a button for translation to English and actually to other languages too. Moreover, this tool has two operation modes. One is automatic listening and translation. The other one is push to talk, which means it only records once a button is pushed and it stops recording once a button button is released. It would be great if it would be possible. to have this tool again as an selectable IME input. The alternative obviously would be to implement these translation functionality in the tool provided by eOS.
as the good man told, wait & see.
hope that it will be solved soon.
maybe for you the holidays would be the opportunity to make a connection cut and profite, enjoy the relaxation of the moment
I agree for the connection cut, but I think vacation is the period the most prone for a stolen/lost phone (different place, different habits), so I’m not very confident with the situation.