Some banking apps read the file /proc/net/unix to
find out whether things like Magisk are installed/running.
To prevent that, chmod it 440.
This file isn't needed by any other process when boot is finished.
I've tested this and banking apps that did not work before
and recognized Magisk being installed now don't recognize
that and work just fine.
Signed-off-by: aswin7469 <aswinas@pixysos.com>
Signed-off-by: firebird11 <hbgassel@gmail.com>
Change-Id: I8f4c3ce55fe206786018ffba5e3301c52158a844
Signed-off-by: strwbrry143 <alexfinhart@gmail.com>
* VENDOR from LA.UM.9.12.r1-14400-SMxx50.QSSI13.0
* QSSI from LA.QSSI.13.0.r1-09000-qssi.0
* Split CAF proprietary files
* Update Keymaster to 4.1
* Use FBE v2
* Use Non 20801/20804 (Nord) libs/firmwares
* Do not use odm/vendor dir for WCNSS_qcom_cfg.ini
Sadly RF version can not act as a unique identifier for EU and GLO variant of avicii since OnePlus decided to use RF version 14 for both.
Due to this reason we're only setting the property for IN variant.
Change-Id: I9057f11f5728898530cd0504c4a0125091da6910
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
ro.boot.hardware.revision is used in fastbootd UI, getvar hw-revision
output and Settings app.
Set based on the RF version so external tools can use it to flash
the correct firmware variant and show the HW variant in Settings.
Change-Id: I1adfb6514fdbaa2e5b9782c37d9eaf8112a110fc
* 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
