@ saroumane38 Thanks you a lot ! I’ll have a look
Uh, wasn’t it supposed to be feedback for 1.10, and you just have the previous release for the moment 
Hi Manoj, hi everybody,
Thanks again for this new version!!
small additional question: why now, is there only release not for S while before there were too release notes for R & Q?
Any news about the possibility to have links in release note to all the bugs fixed and improvements added for a version? Sometimes it’s not easy to really see what is the fix or the improvement.
Thanks
A+
MIB
1 Like
The Q and R release notes should also be added by the team. It just takes some extra time after the release. The release notes should appear in the same location
Will ask the team member to share the release notes for other OS versions ASAP.
2 Likes
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 1.9-s-20230311268558-dev-FP3
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 1.10-s-20230413279105-dev-FP3.
The following things work for me:
- 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 modules - Mozilla Location Service: enabled, configured for using Wi-Fi and Cell
- Settings - Advanced Privacy - Location: Exposed
- Settings - Advanced Privacy - Manage my location: Use my real location
- 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.0
(nightly 27.01.2023 - for sync with Betterbird instead of Thunderbird) - Bluetooth (music playback, data connection)
7 Likes
Vendor Name: Fairphone
Device name: Fairphone 2
Device CodeName: FP2
Version of /e/OS or Stock which existed previously: /e/OS 1.9-r-20230312268580-dev-FP2
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 1.10-r-20230417279828-dev-FP2.
The following things work for me:
- Call / be called
- Send SMS / receive SMS
- Alarm
- Internet via Wi-Fi
- Internet via mobile network
- Wi-Fi hotspot
- Location
- Settings - System - Advanced - microG - Self-Check: all ok, including location permissions
- Settings - System - Advanced - microG - Location modules - Mozilla Location Service: enabled, configured for using Wi-Fi and Cell
- Settings - Advanced Privacy - Location: Exposed
- Settings - Advanced Privacy - Manage my location: Use my real location
- Settings - Location - Wi-Fi and Bluetooth scanning - Wi-Fi scanning: enabled
- Settings - Location - Wi-Fi and Bluetooth scanning - Bluetooth scanning: disabled
- Settings - Location - App access to location - “Allowed only while in use”: Apps are listed
- Compass
- Screenshot
- Main camera (Camera module 12 MP version 2) photo + video
- Selfie camera (Top module version 2) photo + video
(Camera records completely black video from the moment surrounding light is too dark or changes into too dark when moving … years old issue I already had with Open Camera on LineageOS, can live with it.) - USB connection to PC / MTP
-
MyPhoneExplorer 2.0
(nightly 27.01.2023 - for sync with Betterbird instead of Thunderbird) - Bluetooth (music playback, data connection)
I just now noticed that encryption was gone, probably with the upgrade to Android 11 (R) … encrypting again went fine.
5 Likes
Can someone plesse post a guide step by step on how to manually upgrade
Go to
Settings
System Updates
If no update showing, press the circle with arrow (top right) a few times, if no update appears, then one isn’t ready for your device.
I have fp4.
No ota update shows up in the settings, but 1.10 is released and im on 1.9.
Im rooted, could that be the reason why i dont see ota update?
1 Like
Are you on /e/OS S (android 12)??
Hi all, I made 4 upgrade from e-os 1.9 to 1.10
1st : MI8 dipper : OK
2nd : Lenovo tab YTX703F : OK
3rd : Samsung a5xelte : OK
4th : Oneplus8T kebab : fail 
installation error
unfortunately the kebab is my daily device
So 2 questions :
1-Am I the only one?
2-How can I get the logfile of the failing update process
Hi @PraksuQ , I have a similar issue (install error) with my Oneplus 8T kebab.
Could you tell me how to get the install logfile
Thanks in advance
thanks again for your kindness @PraksuQ.
My issue was similar to yours. As you say a more explicit message could be useful.
Just an update to your post, to fix that issue you have to use adb with both USB debug and rooted debug active on your device developper options and enter following command :
adb root
adb enable-verity
adb reboot
Obviously you have to launch again the update process.
hereunder my logcat file.
04-22 14:15:12.199 1449 1449 I update_engine: [INFO:payload_metadata.cc(221)] Metadata hash signature matches value in Omaha response.
04-22 14:15:12.205 1449 1449 I update_engine: [INFO:delta_performer.cc(1049)] Detected a ‘full’ payload.
04-22 14:15:12.208 1449 1449 I update_engine: [INFO:delta_performer.cc(1120)] dtbo does’t have version, skipping downgrade check.
04-22 14:15:12.212 1449 1449 I update_engine: [INFO:delta_performer.cc(1120)] recovery does’t have version, skipping downgrade check.
04-22 14:15:12.213 1449 1449 I update_engine: [INFO:delta_performer.cc(1120)] vbmeta does’t have version, skipping downgrade check.
04-22 14:15:12.214 1449 1449 I update_engine: [INFO:delta_performer.cc(1120)] vbmeta_system does’t have version, skipping downgrade check.
04-22 14:15:12.220 1449 1449 I update_engine: [INFO:delta_performer.cc(811)] Preparing partitions for new update. last hash = , new hash = NxhiHj6XhqdAaIKaPKX+RfSvMl2dZcEeyNF+PJQfGwc=NXo245miAOwwvRcgPrpGH5FoqUEEKcqbYaVqLoZSd7Q=
04-22 14:15:12.223 1449 1449 I update_engine: [INFO:delta_performer.cc(1394)] Resetting recorded hash for prepared partitions.
04-22 14:15:12.227 1449 1449 W update_engine: [WARNING:dynamic_partition_control_android.cc(441)] overlayfs overridesare active and can interfere with our resources.
04-22 14:15:12.227 1449 1449 W update_engine: run adb enable-verity to deactivate if required and try again.
04-22 14:15:12.228 1449 1449 I update_engine: EnsureMetadataMounted does nothing in Android mode.
04-22 14:15:12.230 1449 1449 I update_engine: [INFO:dynamic_partition_control_android.cc(762)] Erasing AVB footer of system_other partition before update.
04-22 14:15:12.231 1449 1449 E update_engine: [libfs_mgr]ReadFstabFromFile(): cannot open file: ‘/system/etc/fstab.postinstall’: No such file or directory
04-22 14:15:12.232 1449 1449 W update_engine: [WARNING:dynamic_partition_control_android.cc(636)] Cannot read fstab from /system/etc/fstab.postinstall: No such file or directory (2)
04-22 14:15:12.233 1449 1449 I update_engine: [INFO:dynamic_partition_control_android.cc(663)] AVB is not enabled on system_other. Skip erasing.
04-22 14:15:12.234 1449 1449 I update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.237 1449 1449 I update_engine: [INFO:dynamic_partition_control_android.cc(331)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/super
04-22 14:15:12.238 1449 1449 I update_engine: Update has been initiated, now canceling
04-22 14:15:12.239 1449 1449 I update_engine: Removing all update state.
04-22 14:15:12.240 1449 1449 W update_engine: Cannot read /metadata/ota/snapshot-boot: No such file or directory
04-22 14:15:12.242 1449 1449 W update_engine: Failed to get flashing status
04-22 14:15:12.243 1449 1449 W update_engine: Cannot read /metadata/ota/snapshot-boot: No such file or directory
04-22 14:15:12.245 685 685 I android.hardware.boot@1.1-service: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.246 685 685 I android.hardware.boot@1.1-service: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.247 685 685 I bootcontrolhal: set_snapshot_merge_status: MergeStatus = 0, current_slot = 1, returning: true
04-22 14:15:12.248 685 685 I android.hardware.boot@1.1-service: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.249 685 685 I android.hardware.boot@1.1-service: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
04-22 14:15:12.250 685 685 I bootcontrolhal: set_snapshot_merge_status: MergeStatus = 0, current_slot = 1, returning: true
04-22 14:15:12.252 1449 1449 E update_engine: Cannot create update snapshots with overlayfs setup. Run adb enable-verity, reboot, then try again.
04-22 14:15:12.254 1449 1449 E update_engine: [ERROR:dynamic_partition_control_android.cc(952)] Cannot create update snapshots: Error
04-22 14:15:12.255 1449 1449 E update_engine: [ERROR:dynamic_partition_control_android.cc(497)] PrepareSnapshotPartitionsForUpdate failed in Android mode
04-22 14:15:12.256 1449 1449 E update_engine: [ERROR:delta_performer.cc(822)] Unable to initialize partition metadatafor slot A
04-22 14:15:12.257 1449 1449 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-22 14:15:12.265 1449 1449 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
04-22 14:15:12.267 1449 1449 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
04-22 14:15:12.268 1449 1449 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
04-22 14:15:12.269 1449 1449 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kInstallDeviceOpenError
04-22 14:15:12.270 1449 1449 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
04-22 14:15:12.271 1449 1449 I update_engine: [INFO:update_attempter_android.cc(565)] Processing Done.
04-22 14:15:12.273 1449 1449 I update_engine: [INFO:metrics_reporter_android.cc(159)] Current update attempt downloads 0 bytes data
- Vendor Name: Fairphone
- Device name: FP4
- Device CodeName: FP4
- Version of /e/OS: 1.9-s-20230310268290-stable-FP4
- device Not routed
tout est ok
merci
2 Likes
Still not available for FP4.
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.
@Manoj may be I’m wrong, but I think that an install error on both a Pixel redfin and a oneplus kebab are not coincidental.
Probably maintainer/dev team should have a look on these issues.
After solving that problem, everythink is OK on my Kebab device.
Thanks to the team for the work done.
1 Like
Notes cannot be folded back as before. You can only add notes, since on the right there’s only a “+” sign. Very inconvenient to scroll through all the notes.
For what I know, is not because your phone is rooted. Maybe it depends on what channel (stable or dev).
But, as @Cabnedor and many others, me too I’m waiting for the OTA update, which arrives every time some days after others devices:
Don’t care, only wait.