Android 16 QPR1 + M3E changes the inflation and lifecycle timing of
PreferenceFragmentCompat layouts, resulting in internal RecyclerView
being created later than before.
As a result, PreferenceFragmentCompat.setDivider() can be invoked
before the internal RecyclerView exists thus causing below NPE:
11-25 18:06:19.705 7903 7903 E AndroidRuntime: FATAL EXCEPTION: main
11-25 18:06:19.705 7903 7903 E AndroidRuntime: Process: org.lineageos.lineageparts, PID: 7903
11-25 18:06:19.705 7903 7903 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.recyclerview.widget.RecyclerView.invalidateItemDecorations()' on a null object reference
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at androidx.preference.PreferenceFragmentCompat$DividerDecoration.setDivider(PreferenceFragmentCompat.java:909)
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at androidx.preference.PreferenceFragmentCompat.setDivider(PreferenceFragmentCompat.java:247)
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at com.android.settingslib.widget.SettingsBasePreferenceFragment.onViewCreated(SettingsBasePreferenceFragment.kt:47)
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at org.lineageos.lineageparts.SettingsPreferenceFragment.onViewCreated(SettingsPreferenceFragment.java:156)
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at org.lineageos.lineageparts.profiles.SetupTriggersFragment.onViewCreated(SetupTriggersFragment.java:89)
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at androidx.fragment.app.Fragment.performViewCreated(Fragment.java:3099)
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:607)
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:285)
(...)
# 11-25 18:06:19.705 7903 7903 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:9041)
# 11-25 18:06:19.705 7903 7903 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593)
11-25 18:06:19.705 7903 7903 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:929)
11-25 18:06:19.727 2241 6629 W ActivityTaskManager: Force finishing activity org.lineageos.lineageparts/.PartsActivity
Test: Open System profiles settings, create a new profile and verify
that the activity no longer crashes.
Change-Id: Ifb741011baaa6d721d0ca0db2d68d30037eb8930
I QC2Buf : Buffer 0xf3041d10 imported as 0xf3042690
W QC2V4l2Codec: [avcD_13] unknown/unsupported param Output::HdrStaticMetadata index = 0xD200180A
Change-Id: I5de137760aa0ffb5cb52a12ae074c2862de24a40
This service hogs a considerable amount of CPU all the time as its
busy calculating compensation for our under-display light sensor
(and also spamming logcat, which we can take care of later).
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
1969 system 20 0 12G 9.2M 9.0M S 4.6 0.1 1:13.15
vendor.xiaomi.sensor.citsensorservice@2.0-service
Move it to background CPU set like the sensors multihal to lower
power consumption from big cores.
Change-Id: I8c7b2835b2b53654642ac20fd97df3b8a5ad96eb
* fixes crashes and absurdly high CPU usage while using dolby
Co-authored-by: Woomymy <woomy@woomy.be>
Change-Id: Ib72b775dae677f3085d0b0e2afcbb709d8690063
* This breaks in-game voice chat and audio in some messaging apps
causing it to plays with a higher pitch and speed, making it sound
like chipmunks.
Change-Id: I0baf0d01481b755372c3420bb58b73d2f38eb2d9
Edit: Turn on by default
Bug: 389002332
Flag: android.hardware.biometrics.screen_off_unlock_udfps
Test: 1. FP screen off unlock should be included in settings
2. FP screen off unlock should be enabled by default
Change-Id: I65eda6ae6f69ff4e6a3191d91fb8be42797c7fcb
Signed-off-by: ralph950412 <ralph950412@gmail.com>
* time_daemon just refuses to work properly on mata.
Sony's TimeKeep, instead, does the job flawlessly,
so just ditch the former in favor of the latter.
Signed-off-by: Roberto Sartori <roberto.sartori.android@gmail.com>
Change-Id: I54f50ed3d49efc2834d478781b15e6ee428a3062
Turns out this is platform specific. Fixes crashes on
libarcsoft_super_night_raw calls on yupik devices
Change-Id: I06b22517d313a8eeb116b0b969615203b0d53823
This one seems to be overriding the actual overlayed value of
rounded_corner_content_padding on the device side.
Change-Id: I64383583a6a54e44a9c801bb3c8dd14c11fa45f9
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
W ExtconUEventObserver: Unable to read /sys/devices/platform/soc/soc:extcon_usb1/extcon/extcon3/cable.0/name. This probably means the selinux policies need to be changed.
W ExtconUEventObserver: Unable to read /sys/devices/platform/soc/soc:extcon_usb1/extcon/extcon3/cable.1/name. This probably means the selinux policies need to be changed.
Change-Id: I92d728a1bc283beedf33b015c3115221140d527d
* Currently, cancelEvents in MTP will cancel the requests one by
one, and it will check each response to confirm success or
failure. However, if kernel usb controller driver got the
cancel request, the driver will handle all requests in the same
endpoint so that the second io_cancel in cancelEvents will be
useless causing the cancelEvents to return error and fail the
transfer.
* Fix this by setting sys.usb.mtp.batchcancel for the targets
using MTP over FFS.
Change-Id: Icea9a2815c79ff710ee887d02e4c99dfe5ad6361
On targets where diag-router is used, override the
vendor.usb.diag.func.name property to 'ffs' to
instantiate the Diag function instances to use
F_FS instead of the legacy f_diag driver.
Change-Id: I529a081a0d6988628944a9020b61c061baa877a4
