Feedback for v1.10

Please share feedback on the v1. 10 build for your devices and how it is working with application you use.

Refer category description here

Builds will be rolling out in a staggered manner over the next couple of days. It will be released for a few devices at a time.

We will also have a poll to rate this build.

  • I have updated to v1.10 on my device and it is working well
  • I updated to v1.10 but I am having issues (Please share the issue details on this thread)
  • I am not able to update to v1.10 (Please share the issue details on this thread)

0 voters

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
  • Is the device Rooted / Not rooted

Refer this table for vendor, codename details

Refer this guide to share more details in your feedback

5 Likes

Vendor Name: Google
Device name: Pixel 5
Device CodeName: redfin
Version of /e/OS which existed previously: 1.9-dev
The device is: Not rooted

Download of 1.10-dev is possible, but the installation breaks with: “Install error” :frowning:

Edit:
The md5sum of /data/lineageos_updates/e-1.10-s-20230413279105-dev-redfin.zip on redfin is right.

logcat:

04-17 20:20:05.199  1249  1249 I update_engine: [INFO:multi_range_http_fetcher.cc(45)] starting first transfer
04-17 20:20:05.202  1249  1249 I update_engine: [INFO:multi_range_http_fetcher.cc(74)] starting transfer of range 2882+1250220857
04-17 20:20:05.204  1249  1249 I update_engine: [INFO:delta_performer.cc(115)] Completed 0/? operations, 16384/1250220857 bytes downloaded (0%), overall progress 0%
04-17 20:20:05.208  1249  1249 I update_engine: [INFO:delta_performer.cc(346)] Manifest size in payload matches expected value from Omaha
04-17 20:20:05.210  1249  1249 I update_engine: [INFO:delta_performer.cc(1012)] Verifying using certificates: /system/etc/security/otacerts.zip
04-17 20:20:05.213  1249  1249 I update_engine: [INFO:payload_verifier.cc(102)] signature blob size = 267
04-17 20:20:05.215  1249  1249 I update_engine: [INFO:payload_verifier.cc(118)] Truncating the signature to its unpadded size: 256.
04-17 20:20:05.216  1249  1249 I update_engine: [INFO:payload_verifier.cc(129)] Verified correct signature 1 out of 1 signatures.
04-17 20:20:05.217  1249  1249 I update_engine: [INFO:payload_metadata.cc(221)] Metadata hash signature matches value in Omaha response.
04-17 20:20:05.223  1249  1249 I update_engine: [INFO:delta_performer.cc(1049)] Detected a 'full' payload.
04-17 20:20:05.225  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] vbmeta_system does't have version, skipping downgrade check.
04-17 20:20:05.226  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] vendor_boot does't have version, skipping downgrade check.
04-17 20:20:05.227  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] dtbo does't have version, skipping downgrade check.
04-17 20:20:05.228  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] vbmeta does't have version, skipping downgrade check.
04-17 20:20:05.229  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] abl does't have version, skipping downgrade check.
04-17 20:20:05.230  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] aop does't have version, skipping downgrade check.
04-17 20:20:05.231  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] devcfg does't have version, skipping downgrade check.
04-17 20:20:05.232  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] hyp does't have version, skipping downgrade check.
04-17 20:20:05.233  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] keymaster does't have version, skipping downgrade check.
04-17 20:20:05.234  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] qupfw does't have version, skipping downgrade check.
04-17 20:20:05.235  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] tz does't have version, skipping downgrade check.
04-17 20:20:05.236  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] uefisecapp does't have version, skipping downgrade check.
04-17 20:20:05.237  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] xbl does't have version, skipping downgrade check.
04-17 20:20:05.238  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] xbl_config does't have version, skipping downgrade check.
04-17 20:20:05.239  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] featenabler does't have version, skipping downgrade check.
04-17 20:20:05.240  1249  1249 I update_engine: [INFO:delta_performer.cc(1120)] modem does't have version, skipping downgrade check.
04-17 20:20:05.246  1249  1249 I update_engine: [INFO:delta_performer.cc(811)] Preparing partitions for new update. last hash = , new hash = beVECrWFmmwTnh8HoNXArRzDv5kbl9Ji1AWL0/NERSQ=TMvoEFNlhzSHEiZpxprcW2V4tETnFGrFjnA4p9UXC7U=
04-17 20:20:05.250  1249  1249 I update_engine: [INFO:delta_performer.cc(1394)] Resetting recorded hash for prepared partitions.
04-17 20:20:05.254  1249  1249 W update_engine: [WARNING:dynamic_partition_control_android.cc(441)] overlayfs overrides are active and can interfere with our resources.
04-17 20:20:05.254  1249  1249 W update_engine: run adb enable-verity to deactivate if required and try again.
04-17 20:20:05.255  1249  1249 I update_engine: EnsureMetadataMounted does nothing in Android mode.
04-17 20:20:05.256  1249  1249 I update_engine: [INFO:dynamic_partition_control_android.cc(762)] Erasing AVB footer of system_other partition before update.
04-17 20:20:05.259  1249  1249 I update_engine: [INFO:dynamic_partition_control_android.cc(331)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/super
04-17 20:20:05.261  1249  1249 I update_engine: [INFO:dynamic_partition_control_android.cc(715)] Can't find system_a in metadata source slot, skip erasing.
04-17 20:20:05.263  1249  1249 I update_engine: [INFO:dynamic_partition_control_android.cc(331)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/super
04-17 20:20:05.264  1249  1249 I update_engine: Update has been initiated, now canceling
04-17 20:20:05.265  1249  1249 I update_engine: Removing all update state.
04-17 20:20:05.266  1249  1249 W update_engine: Cannot read /metadata/ota/snapshot-boot: No such file or directory
04-17 20:20:05.267  1249  1249 W update_engine: Failed to get flashing status
04-17 20:20:05.268  1249  1249 W update_engine: Cannot read /metadata/ota/snapshot-boot: No such file or directory
04-17 20:20:05.278  1249  1249 E update_engine: Cannot create update snapshots with overlayfs setup. Run `adb enable-verity`, reboot, then try again.
04-17 20:20:05.280  1249  1249 E update_engine: [ERROR:dynamic_partition_control_android.cc(952)] Cannot create update snapshots: Error
04-17 20:20:05.281  1249  1249 E update_engine: [ERROR:dynamic_partition_control_android.cc(497)] PrepareSnapshotPartitionsForUpdate failed in Android mode
04-17 20:20:05.282  1249  1249 E update_engine: [ERROR:delta_performer.cc(822)] Unable to initialize partition metadata for slot A
04-17 20:20:05.284  1249  1249 E update_engine: [ERROR:download_action.cc(222)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
04-17 20:20:05.294  1249  1249 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
04-17 20:20:05.295  1249  1249 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
04-17 20:20:05.296  1249  1249 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
04-17 20:20:05.296  1249  1249 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kInstallDeviceOpenError
04-17 20:20:05.297  1249  1249 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
04-17 20:20:05.298  1249  1249 I update_engine: [INFO:update_attempter_android.cc(565)] Processing Done.
04-17 20:20:05.300  1249  1249 I update_engine: [INFO:metrics_reporter_android.cc(159)] Current update attempt downloads 0 bytes data

Edit:
After “adb enable-verity / adb reboot” the installation is running.

A better error message would be desirable here. The solution is only visible in the log.

  • Vendor Name: Oneplus
  • Device name: 5T
  • Device CodeName:
  • Version of /e/OS: 1.10
  • Is the device Rooted / Not Rooted: Not

All is working ok.

1 Like

Fairphone | FP3+ | FP3 | 1.9.1-s-dev | not rooted

Installed fine (27 minutes including reboot and everything), initial impression is that it feels a bit snappier (more than after the reboots before the update).

4 Likes

Hello,
after my old phone was completely destroyed I bought a new Mi11 Lite 5G. The first attempts to install /E/ had failed, the SPL was too old and therefore an installation was refused. For weeks I then used the original software from Xiaomi, pretty corrosive vergoogelt and verXiaomit. Then I installed Lineage a few days ago - but apparently also some Google on it and somehow not as easy and nice as my old /E/. After a few days I liked Lineage better and better, but /E/ was still the better version for me - even less Google on it and still easier in everything.
Yesterday there was the V1.10 for my Xiaomi Mi11 Lite 5G. Yeah!
Installation worked this morning and the thing runs flawlessly.
Camera and everything I have tried so far works without problems.

I now carry a good feeling in my pocket again, without being permanently spied on by Google.

Thanks to you, will perhaps soon increase my monthly donation.

Translated with www.DeepL.com/Translator (free version)

2 Likes

Updated my daily driver Samsung S10e and Samsung Galaxy Tab 6. No problems so far except:

  • Do not get updates of OSS software apps (e.g. Element is still on 1.5.26, where F-Droid is 1.5.30)
  • Calendar month layout is funny on Galaxy Tab 6 (font size)

Vendor Name: Oneplus
Device name: 7T
Device CodeName: hotdogb
Version of /e/OS which existed previously: e-1.9-s-20230312268558-dev
Is the device Rooted / Not Rooted: Not Rooted

When restarting I get the following message : “The boot loader is unlocked and software integrity cannot be garanteed. […] g.co/ABH”.
Stuck at the enter PIN screen : touch screen is not responding.
Stuck too when removing the SIM card and going to the OS unlock screen.

1 Like

True …

Did you try to reboot the phone ?

Yes, I tried several times. Is there a way to go back to the previous version of /e/?

@9135ch as yours is not a “verified boot” device it should be possible to

adb sideload

the previous version found here : https://images.ecloud.global/dev/hotdogb/

e-1.9-s-20230312268558-dev-hotdogb.zip

1 Like

Can I just do the sideload command or do have to format the phone, etc.?
=> “Denying OTA because it’s SPL downgrade” I guess I have to format…

Have upgraded to 1.10s (Samsung Galaxy S10+) and it’s working well.

But I see the already reported issue around Advanced Privacy and Microsoft login URL is still present (if Advanced Privacy is on, neither Teams nor Outlook can connect).

Yes … I seem to remember more than one report of “touch screen / touchscreen is not responding” in brief searching I found this (is OnePlus 7T Pro ‘hotdog’) Feedback for v1.9 - #17 by anon29344687 . Might be worth investigating further before you wipe your data ?

Also: OnePlus 8T Touchscreen Doesn't Work After Install

2 Likes

I have backups :slight_smile: )
Thank you, I will try this tonight.

If you look at Advanced Privacy in more detail you can enable/disable the trackers found within outlook on a case by case basis. Normally, from memory, you only need to disable “mobile engagement” to send the emails.

Maybe it could help…

I tried performing the update on FP3, from 1.9.1-s, but my device is now stuck on boot screen.
I have just created a topic for this:
Device stuck on boot screen after 1.10-s update - FP3.

Vendor Name: Fairphone
Device name: FP3
Device CodeName: FP3
Version of /e/OS which existed previously: 1.9-dev
The device is: Not rooted

1 Like

Hello,

My Fairphone 3 was running /e/OS-1.9.1-s;
a few hours ago I downloaded the proposed 1.10-s update (can’t see the exact build version, given my issue).
After the background update process finished, I have hit ‘restart’ but now my device is stuck on boot screen (with “Fairphone” and “Powered by android”, not the one with /e/ logo) since 1 hour.

I fear that pressing Power+Volume buttons might break it even further, as it was performing an update.
Can I do it? Or do you have any other advice?

I know of this feature, but it still doesn’t work for these two apps.
I remember reading something in a thread (maybe in the 1.9 feedback thread, but I can’t exactly remember) that there is a bug: when advanced privacy is enabled, one of the URLs needed for Microsoft login cannot be accessed, at all - it was officially logged as a bug. It seems the fix for this bug was not included in the 1.10 update (hopefully it will make it into the next update)

1 Like

After that much time, you can do it, there’s not much else to do.

Keeping the power button pressed for about 15 seconds will force a reboot.
Keeping Volume + pressed while starting/rebooting the phone will boot the phone into recovery mode.
Keeping Volume - pressed while starting/rebooting the phone will boot the phone into Fastboot Mode.

2 Likes

I did that in the end, and it worked. My phone now shows 1.10-s-20230413279105-dev-FP3 as current version.
Tried rebooting a second time without issue.

Thank you.

Note: my storage only has 4.63 GB (now, after the update is finished). Could this be a cause of the issue? (Since it is an A/B device, I suppose not, but just asking)

1 Like