FP4: Force rollback timestamp to be of the 05th of the month
Description
FP4: Force rollback timestamp to be of the 05th of the month
Screenshots
Technical details
- Fairphone uses the rollback from the SPL, but their SPL is always for the 05th of the month.
- /e/ OS merges the security updates from AOSP which is for 1st of the month.
- Even if both the OS-ses are on the same SPL, /e/ OS would always be behind, which is leading to more rollback flashing failures, internally.
- So match with FPOS by using the 5th of the month, rollback timestamp
Tests
- Rollback timestamp is for the 5th day of the month, regardless of what day the SPL is.
❯ avbtool info_image --image vbmeta_system.img
Minimum libavb version: 1.0
Header Block: 256 bytes
Authentication Block: 320 bytes
Auxiliary Block: 2176 bytes
Public key (sha1): cdbb77177f731920bbe0a0f94f84d9038ae0617d
Algorithm: SHA256_RSA2048
Rollback Index: 1770249600
Flags: 0
Rollback Index Location: 0
Release String: 'avbtool 1.3.0'
Descriptors:
Prop: com.android.build.system.os_version -> '14'
Prop: com.android.build.system.fingerprint -> 'Fairphone/FP4eea/FP4:13/TKQ1.230127.002/TP31:user/release-keys'
Prop: com.android.build.system.security_patch -> '2026-02-01'
Prop: com.android.build.system_ext.os_version -> '14'
Prop: com.android.build.system_ext.fingerprint -> 'Fairphone/FP4eea/FP4:13/TKQ1.230127.002/TP31:user/release-keys'
Prop: com.android.build.system_ext.security_patch -> '2026-02-01'
Prop: com.android.build.product.os_version -> '14'
Prop: com.android.build.product.fingerprint -> 'Fairphone/FP4eea/FP4:13/TKQ1.230127.002/TP31:user/release-keys'
Prop: com.android.build.product.security_patch -> '2026-02-01'
❯ date -d 'TZ="GMT" 2026-02-01' +%s
1769904000
❯ date -d 'TZ="GMT" 2026-02-05' +%s
1770249600
Issues
https://gitlab.e.foundation/e/devices/backlog/-/issues/1706