* This obviously causes a build error if TARGET_RECOVERY_OVERSCAN_PERCENT
is set to some value in the BoardConfig.
Change-Id: I9d34ba158a1249e58304369918408fb388be8c5c
(cherry picked from commit 3b494b7a7f6efd3b8f9016540b74815ea6e9df64)
So that read-only partitions can also get mounted.
For example, Super volumes are RO when setting up.
Change-Id: I736a738963ba208cfdeaadc05c47d45b1bb7bf3e
(cherry picked from commit b52a4815d5c3a5be1fe56968f4480c788d2eaab2)
- If the var TW_STATUS_ICONS_ALIGN can be set to:
1) 'center' or '2' to center-align the icons/text (vertically)
2) 'bottom' or '3' to bottom-align the icons/text (vertically)
( Value calculated by utilizing statusbar height & size of font_m ).
- If set to anything else or not set at all, it falls back to twrp's
old behaviour of top-aligning the status bar icons.
Change-Id: I1b292221f3c34bbac20233595fbc0958d4aa4cc1
Signed-off-by: Yillié <yilliee@protonmail.com>
Signed-off-by: Mohd Faraz <androiabledroid@gmail.com>
- The var TW_CUSTOM_CLOCK_POS, TW_CUSTOM_CPU_POS and
TW_CUSTOM_BATTERY_POS can be used to specify a custom position
for the clock, cpu temperature and battery percentage on the x-axis.
- The value can either be a whole number refering to the starting
position of that specific item on the x-axis or it can be 'left',
'right' or 'center' which will try to automatically calculate such
a value that items appear to be left , right or center aligned
respectively.
- Incase of TW_NO_CPU_TEMP being set to true, the CPU_POS var can be
used for the TWRP version text that takes the place of the cpu temp.
One of the use-cases of this var is when the status bar items overlap
with the camera cutout. In that case, instead of specifiying an offset
for the whole gui on y-axis, the status bar items can be offset along
the x-axis only.
Signed-off-by: Yillié <yilliee@protonmail.com>
Change-Id: Ic01d301731822a598b0ca8adb2280c4d01a3622f
Signed-off-by: Mohd Faraz <androiabledroid@gmail.com>
Legacy devices might have symlinks to real partitions in this folder.
Change-Id: I4d3360ff1022eabbd4f6ae7688d8bb7306ae9777
(cherry picked from commit 928234b2b704555073ab03eb6a051fa9c9fd2a86)
Native solution for ABX xml conversion will be used,
so python isn't necessary
Use TW_INCLUDE_PYTHON := true to add to build
if desired to use in TWRP
Change-Id: Ibe5cbabb6c7260966d933218f08d24e96e0b8a63
(cherry picked from commit 73ab9725661bcaafed88b70f16da200cd599e7d3)
The parser is supposed to parse plain XMLs, ABX format is not yet supported.
Continuing to parse ABX XMLs would be spamming /tmp/recovery.log until triggering OOM.
Change-Id: I5c01045d6efef0b2ac497b40d78410c2b75d30d0
(cherry picked from commit 0a352091b39cb62f919af0fbed1097194d3188bf)
For example, Super volumes are read-only by default.
Change-Id: I0fc144842e42177d715c968bd1ee79e1406dae59
(cherry picked from commit d63fcaa879adc8f4be6ca2de3967e767c7542877)
Note: This won't make super volumes default to read-write. It depends on fstab flags.
Change-Id: I7b08e090e45d1ff58f571f5b4ea55dd24ac9249d
(cherry picked from commit 47075559a7c878fa150abe7a48159d20e475f148)
exclude this dir to prevent "error 255" on MIUI
Change-Id: I7e31006617775d575cc1f37a0234369a345c372d
(cherry picked from commit 05ca8766bff3e0cb22e1d69be56fa8d9f1d9ef19)
The word usage of the translation strings in the past are in the style of China rather than Taiwan.
I'm Taiwanese, who works on Android and Translation projects.
Signed-off-by: Edward Wu <bluehome.wu@gmail.com>
Change-Id: I48fc712e6dce16a56e8cfcff58554bfe5123779c
(cherry picked from commit 2715033a420e5394b3ab36c311da0d849ad34d4a)
Current flow creates a vendor folder in the recovery ramdisk, then
the build fails when the ramdisk rule tries to create a symlink there.
Change-Id: I8bfb77d829c5dc6fcb2701cbfe44ce104058f37f
Add twrp_soong as a required module to ensure twres
folder is included in dirty builds where device out folder
is removed
Change-Id: I5b3f57664cd2aa97ff74ff594c72e6f29c6c927f
Use the TW_OVERRIDE_PROPS_ADDITIONAL_PARTITIONS flag to
specify a space-separated list of additional partitions
that should be parsed when trying to locate props
for overriding.
Example:
TW_OVERRIDE_PROPS_ADDITIONAL_PARTITIONS := vendor odm
Requires TW_OVERRIDE_SYSTEM_PROPS to be defined.
Change-Id: I7baf4c15628789fe525976d9de0251bba6882395
Should be handled via device tree's BoardConfig
Sample will be TARGET_OTA_ASSERT_DEVICE := le_zl1,zl1,lepro3,lex720,lex727,LEX720,LEX727 in BoardConfig
Only applicable for AB or VAB devices
Change-Id: I1fbe6155d3f79eee089a31dbe62ee9d04c33d65c
Needed if no ats_ files are present on qcom device
Offset is the difference between the current time
and the time since_epoch
To calculate the offset in Android, the following expression
(from a root shell) can be used:
echo "$(( ($(date +%s) - $(cat /sys/class/rtc/rtc0/since_epoch)) ))"
Add 3 zeros to the output and use that in the TW_QCOM_ATS_OFFSET
flag in your BoardConfig.mk
For example, if the result of the calculation is 1642433544,
use 1642433544000 as the offset
Change-Id: I5d58125dffc3fdbfb76a5ffde4e27659376185f1