This allows these same writes to happen in both Android and offline
charging mode, thus enabling VOOC during offline charging.
Change-Id: Iacf85966b5fa37eedb42887d666369fb63e13c33
* `fastchg_fw_update` seems to be needed to initialize VOOC / Warp
charging.
* `ui_soc_decimal` isn't exactly needed, as it seems to be more for
enabling the ability to calculate decimal percentages for remaining
battery capacity on the lockscreen for Oxygen OS. Nevertheless, it
doesn't seem to cause harm to enable this anyway.
Change-Id: I03dd1abe9c2c7be0b7b7576721b6f6338f1afd46
[TP0]touchpanel: tp_fw_update_work: fw_name = tp/19825/FW_S6SY792_SAMSUNG.bin
[TP0]touchpanel: fw_name_fae is tp/19825/FW_S6SY792_SAMSUNG_FAE.bin
sec-s6sy792 2-0048: Direct firmware load for tp/19825/FW_S6SY792_SAMSUNG_FAE.bin failed with error -2
sec-s6sy792 2-0048: Falling back to sysfs fallback for: tp/19825/FW_S6SY792_SAMSUNG_FAE.bin
[TP0]touchpanel: retry times 0
[TP]sec-s6sy792: sec_fw_update is called, force update:0
[TP]sec-s6sy792: img version in bin is 0x28240117, img version in ic is 0x28240117
[TP]sec-s6sy792: config version in bin is 0x28240108, config version in ic is 0x28240108
[TP]touch_interface: read block_1, free once.
[TP]touch_interface: read block_1, kzalloc success(len:1152, buf_size:1152).
[TP]sec-s6sy792: update firmware state: no need update!
[TP0]touchpanel: release all touch point and key, clear tp touch down flag
[TP]touch_interface: read block_2, kzalloc success(len:1, buf_size:256).
[TP]sec-s6sy792: sec_change_to_np_mode: change to np_mode time: 0 success!
[TP]sec-s6sy792: sec_enable_fingerprint_mode: touchhold_enable: 0 success!
[TP]sec-s6sy792: sec_enable_black_gesture, enable = 0
[TP]sec-s6sy792: sec_enable_black_gesture: 0 times change black gesture success
[TP]sec-s6sy792: limit_switch is 1
[TP]sec-s6sy792: sec_enable_charge_mode: state: 0 success!
[TP]sec-s6sy792: sec_enable_headset_mode: state: 0 success!
[TP0]touchpanel: add qos request in touch driver.
[TP0]touchpanel: fw update finished
Change-Id: Iba517b59fe2856ed6f991c07e0362b1be203af45
It turns out that if we set multisim prop too late, then we end up with
broken RIL for the first boot.
Test: rm -rf /data/property && reboot
Change-Id: I6903691ca89f99529fc6cd372179a6b10513ec93
* This is read by the feature enabler client. OOS already
does this but we want to make sure we're doing this for
users upgrading from Lineage 18.1.
Change-Id: I1d112d9cea6f3d0e87cdf12898587c7bacf8de9c
