W/libperfmgr(798): Failed to write to node: /dev/stune/camera-daemon/schedtune.boost with value: 0, fd: -1
W/libperfmgr(798): Failed to write to node: /dev/stune/camera-daemon/schedtune.prefer_high_cap with value: 0, fd: -1
W/libperfmgr(798): Failed to write to node: /proc/sys/kernel/sched_energy_aware with value: 1, fd: -1
W/libperfmgr(798): Failed to write to node: /dev/stune/camera-daemon/schedtune.boost with value: 0, fd: -1
W/libperfmgr(798): Failed to write to node: /dev/stune/camera-daemon/schedtune.prefer_high_cap with value: 0, fd: -1
W/libperfmgr(798): Failed to write to node: /sys/class/devfreq/soc:qcom,cpu6-cpu-l3-lat/min_freq with value: 1516200000, fd: 10
W/libperfmgr(798): Failed to write to node: /proc/sys/kernel/sched_energy_aware with value: 0, fd: -1
Change-Id: I55c65018f1635353ebd6082e1a45c363424f881c
Signed-off-by: K A R T H I K <karthik.lal558@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
* for some reason, some apps automatically detects that we're rooted due to verityUtils failing to measure the apps apk fs-verity.
Change-Id: Ib716d6e375c9d1063a958523ad2de028115bcb3c
Signed-off-by: minaripenguin <minaripenguin@users.noreply.github.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
* Our maximum brightness is 500.
* However, for safety related reason, I have capped this to 255.
* 255 is more than sufficient, and I do not want to be responsible for LED damage.
* Finding the default percentage took some trial and error, in this case, 59% correlated to 75.
Co-authored-by: rahul <rahul@aospa.co>
Change-Id: Ie20969362c531391e4c51b22365b74d62ccb8e5e
Signed-off-by: John Galt <johngaltfirstrun@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
80 was default for torch, so set 80 as default.
Change-Id: I6711c8a77ed04f01a9afeff14325e62404f66ff7
Signed-off-by: John Galt <johngaltfirstrun@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
* breaks google voice match with pixelpropsutils as
we don't have hotword enrollment support
Change-Id: I213626f9729e5ff47ce7e6c990d605ed669b97e3
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
HWC and cit sensor logspam is so intense it bumps up logd's idle CPU
usage up to over 3%. With this change, logs are much cleaner and logd
idle CPU usage is reduced to under 1%, while still allowing error logs
to pass through.
- Do this only in user/debug builds (except eng).
- Add wifi and cnss too while we're at it, they can get noisy at times.
Change-Id: I3322e333f9f18ad73e3774d322474e3a779eb7ed
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
Set persist.vendor.qti.telephony.vt_cam_interface=2 for
legacy targets to enable Camera2 API usage in VT telephony.
Change-Id: I571e543bb8ba8b3fb3f29e11c8f0c7cc912e246d
Signed-off-by: IMMANUEL44 <immanuelr44@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
Enable support for the Video Distribution Profile (VDP) on the
IP Multimedia Subsystem (IMS) to enable operator video-calling
functionality on 4G IMS if the carrier supports it.
Change-Id: Iba23e5fb308a7b7868e910bc17634800c10e0a13
Signed-off-by: AngeloGioacchino Del Regno <kholk11@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
* so LTE+ icon will show whenever it's available
Change-Id: I45a569fa52d19f4b9af370d7a18c4198e29febc6
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Change-Id: Id41fbe7260557a2c596c090ba4ac4c1d90993d06
Signed-off-by: Tim Zimmermann <tim@linux4.de>
Signed-off-by: therealmharc <therealmharc@gmail.com>
Changed “ro.ril.disable.power.collapse” value to zero.
Seems to be a debate on what value is more effective but after more reading and testing found that a value of “0” shows more improvement.
Have also added “ro.mot.eri.losalert.delay=1000 “ that helps smooth out disconnects and reconnects, saving battery.
Changed “ro.ril.disable.power.collapse” value to zero.
Co-authored by: KARTHIK LAL <karthik.lal558@gmail.com>
Change-Id: Ic86e75a637f67b753bbe4edbf9d081303473ae77
Signed-off-by: etylix <me@etylix.me>
Signed-off-by: therealmharc <therealmharc@gmail.com>
- Kernel idle time enabled, as it supports better power management
Change-Id: I2736b5ebf0c97498a1a2854f747547d84757cd9e
Signed-off-by: Guidix <guidixm@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
* Bluetooth libs look for them
Change-Id: I72ac9c1edf6b05947034908339dbe6a19b8088c0
Signed-off-by: Akash Srivastava <akashniki@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
- This turbulence effect causes tremendous lags on devices with a midrange/low-end GPU as it requires expensive rendering.
- Hence, disable it by default to alleviate the situation.
Change-Id: I1a446adb36a2a9834b7733b74d8057e38425f8a6
Signed-off-by: Cyber Knight <cyberknight755@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
Implement a smarter system on whether to connect
to the provided 2Ghz or 5Ghz network.
Change-Id: Idd41e3d9a5e2bde3ea9b4873dffc4274d1530324
Signed-off-by: Alex Naidis <alex.naidis@linux.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
Firmware TWT feature is causing latency spikes, more noticeable on some
select APs.
Specifically, Qualcomm-based APs with QCN9024 prominently cause latency
spikes exceeding multiple seconds frequently from many client generations,
including kona, lahaina and waipio.
Many vendors are disabling FW TWT by default, follow it and disable FW TWT
for faster Wi-Fi experience.
Note that this does not disable TWT altogether and the host software will
be handling it instead.
Change-Id: Ib8b1f93ea051e27626381268aab031b461183055
Signed-off-by: Juhyung Park <qkrwngud825@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
Extend buffer size for offload playback to reduce the frequency of CPU
wake up.
It makes ADSP to process more data one time and reduce the number of
times to wake up CPU.
Bug: 137973303
Test: MP3 playback
Change-Id: If8eb1d3041161979063bf852e2b0b397e87e7c05
Change-Id: Idff8ed8f4d0e7032054eebea45a62f8a7c5db50c
Signed-off-by: justinweng <justinweng@google.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
Some devices with video mode panels experience refresh rate mismatches when the screen is turned off. Specifically:
- The scheduler sets the refresh rate to 120 Hz after the screen turns off at 60 Hz (VRR idle).
- However, the HWC ignores this change, resulting in SurfaceFlinger (SF) incorrectly assuming the device is at 120 Hz when the display is turned back on.
- This causes a mismatch, as HWC continues rendering at 60 Hz, leading to inconsistencies.
To enable this behavior, set the following property:
- `debug.sf.defer_refresh_rate_when_off=1`
Change-Id: I46fd9e6b983138c1f625d52a65451eb04ce42820
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
* This gives proper permission to /dev/diag node so that diag driver can load successfully
Before in log:
Diag_Lib: Diag_LSM_Init: Failed to open handle to diag driver, error = 13
After in log:
Diag_Lib: qpLogDiagInit <== result : 1
Diag_Lib: QMID : gIsQXDMDisabled 0, gIsADBDisabled 1, gIsDebugDisabled
0, gIsIMSLogsDisabled 0
Change-Id: Id85a0424647fb1e855eaa4d417e7ef37f4ee8878
Signed-off-by: Haran Govindan <32816717+YourDeathWish@users.noreply.github.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
* This gives proper permission to /dev/diag node so that diag driver
can load successfully
* Logs spam with error '-13' which basically translates to access denied/invalid permission.
* Fix this by giving system read and write access.
Change-Id: I743de1ca77c5ddedd6905117e4d35cdcfb1541ab
Signed-off-by: Michael W <baddaemon87@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
* Seems to improve the HDR processing in Gcam a bit fast
and we don't have any boostframework binaries either
Change-Id: If0b974fd10ce8d09bc8eb91669fa1ab06ac2e546
Signed-off-by: GeoPD <geoemmanuelpd2001@gmail.com>
Signed-off-by: therealmharc <therealmharc@gmail.com>
