device/asus/sdm660-common/DeviceSettings/src/org/lineageos/settings/device/DeviceSettingsActivity.java:24: error: cannot find symbol
import com.android.settingslib.widget.R;
^
symbol: class R
location: package com.android.settingslib.widget
device/asus/sdm660-common/DeviceSettings/src/org/lineageos/settings/device/kcal/KCalSettingsActivity.java:26: error: cannot find symbol
import com.android.settingslib.widget.R;
^
symbol: class R
location: package com.android.settingslib.widget
device/asus/sdm660-common/DeviceSettings/src/org/lineageos/settings/device/speaker/ClearSpeakerActivity.java:24: error: cannot find symbol
import com.android.settingslib.widget.R;
^
symbol: class R
location: package com.android.settingslib.widget
26ffac3b24
To switch from vendor_qtr to vendor_qcc.
This is to sharing data file access between QDMA native processes
and protect data file from 3rd party access.
CRs-fixed: 3303809
Change-Id: Ieaa1f53573f9ec99a275f6abf53ca03f00aafcb9
* It's somehow broken on some specific early A14 tags
(e.g. fine on r15 and broken on r17), which results in
not being able to parse /data/system/device_policy_state.xml
* Remove it to be safe and for good now
Co-Authored-By: 0xCAFEBABE <87921983+me-cafebabe@users.noreply.github.com>
Reset traced hint value to -1 on reportActualWorkDuration or stale
timeout, and rewrite existing tracing for readability.
Bug: b/243973548
Test: manual
Change-Id: I135ec5f8971a9902d880e4089b0df746f5b917e2
* GCC has been completely removed in AOSP but we keep it
for compatibility reasons with older kernels until they
are adapted to remove all the dependencies to GCC.
* Most updated 4.19+ kernels should be able to use LLVM
binutils out of the box. 4.14 is possible with a few patches
and 4.9 with even more patches.
* Make this the default and allow devices opting out by using
TARGET_KERNEL_LLVM_BINUTILS := false
Change-Id: I569cf290b41aaf2dc16ff9cc4cc6dc461f0d504e
* W ListPreference: Setting a summary with a String formatting marker is no longer supported. You should use a SummaryProvider instead.
Signed-off-by: iusmac <iusico.maxim@libero.it>
* when tested with [1], even after exiting the app, spm was
still active in powerhal thereby keeping max freqs limited
and blocking boosts
* enable/disable it properly and end all other hints before
enabling, to fix this issue
* while we're at it, don't handle max freq for anything other
than spm in powerhint
[1] https://android.googlesource.com/platform/cts/+/refs/heads/master/hostsidetests/sustainedperf
Signed-off-by: Adithya R <gh0strider.2k18.reborn@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.
Similar to what we did for the camera app, unpin the launcher app from
memory as well. While the default launcher (Launcher3) isn't
particularly big, it doesn't make much sense to pin because the launcher
does not typically load new resources much. Most of its resources should
already be loaded in memory after it starts, so pinning the APK is
redundant.
Change-Id: Ia03de9c546a042637647f45d7b2b4072c1555fb5
We droping old deprecated vp9 media codec. This update fixing the following
errors/bugs that causing problems/flickering while playing video on Instagram
and some audio issues on other apps.
Tested with: Instagram, Facebook, WhatsApp, Viber, Duo and YouTube.
01-04 19:50:55.803 1403 6251 E OMXNodeInstance: setParameter(0xd9cc0014:qcom.decoder.vp9, OMX.google.android.index.allocateNativeHandle(0x7f00005d): Output:1 en=0) ERROR: UnsupportedSetting(0x80001019)
01-04 19:50:55.803 1403 6251 E OMX-VDEC-1080P: Extension: OMX.google.android.index.storeANWBufferInMetadata not implemented
01-04 19:50:55.804 1403 6251 E OMX-VDEC-1080P: get_parameter: unknown param 6f600011
01-04 19:50:55.804 1403 6251 E OMXNodeInstance: getParameter(0xd9cc0014:qcom.decoder.vp9, ??(0x6f600011)) ERROR: UnsupportedIndex(0x8000101a)
01-04 19:50:55.805 1403 6251 E OMX-VDEC-1080P: Extension: OMX.google.android.index.storeANWBufferInMetadata not implemented
01-04 19:50:55.805 1403 6251 E OMX-VDEC-1080P: Extension: OMX.google.android.index.configureVideoTunnelMode not implemented
01-04 19:50:55.805 1403 6251 E OMX-VDEC-1080P: Extension: OMX.google.android.index.useAndroidNativeBuffer is supported
01-04 19:50:55.805 1403 6251 E OMX-VDEC-1080P: Extension: OMX.google.android.index.describeHDR10PlusInfo not implemented
01-04 19:50:55.806 1403 1403 E OMX-VDEC-1080P: get_parameter: unknown param 6f600007
01-04 19:50:55.806 1403 1403 E OMXNodeInstance: getParameter(0xd9cc0014:qcom.decoder.vp9, ParamVideoAndroidVp8Encoder(0x6f600007)) ERROR: UnsupportedIndex(0x8000101a)
01-04 19:50:55.807 1403 6251 E OMX-VDEC-1080P: Does not handle dataspace request
01-04 19:50:55.807 1403 6251 E OMXNodeInstance: getConfig(0xd9cc0014:qcom.decoder.vp9, ??(0x7f000062)) ERROR: UnsupportedSetting(0x80001019)
01-04 19:50:55.835 1403 6251 E OMX-VDEC-1080P: Extension: OMX.google.android.index.AndroidNativeBufferConsumerUsage not implemented
Change-Id: If9ee79886b8d2a1dcc68d84102f69b96b578f68e
/system is mounted read-only. It's impossible for init to modify
the permissions on /system/bin/ip.
Change-Id: Ie5cb20bc45f9769969b71ffd747b1ed34fc27187
