* Android will always try to "kick" the USB stack by setting
sys.usb.config to none before doing anything else. Failure to updating
sys.usb.state here can block the USB stack waiting and eventually
timeout.
* This fixes MTP and all the other USB issues we have seen on LOS 17.
Change-Id: Ic372aebde97cbff14cb1f140620cbcacd5523a8e
* Updated all blobs from OOS 10 OB2.
* Ramdisk is not fully synchronized, but necessary changes are made to
support the new blobs.
* Device manifest has been updated to match the new blobs. However,
clean-ups might be needed due to some vendor changes.
* SELinux permissive is flipped on for now until all the new denials are
addressed.
Change-Id: I8e0e72445da8ecab1c4e85735ebfcabc5ff2ed7b
* Since a certain funny mod does some unexpected
changes to rootfs, which essentially resets
/sbin/dashd label back to u:object_r:rootfs:s0,
the dashd cannot be started anymore.
* This change syncs attributes and allows init to
execute files with u:object_r:rootfs:s0 context
as u:object_r:dashd:s0 using seclabel service
option just like OnePlus does on stock.
* We are also reverting bea94bd just because it's
not needed anymore and dropping /sbin/dashd fs
label just so that we can easier spot this issue
if it'd ever happen again.
Change-Id: I98b376a66836aae036b8e41bb0300ce0d926f4c2
* Somehow, some third-party stuff can mess up the context of dashd and
prevent it from starting. We cannot fix third-party stuff, but at
least it makes sense that dashd isn't that "critical" to the point
that the whole system shuts down just because of this single service.
Change-Id: Ife3ca59e38782909b0b42a9b77a342d2a5b92ae8
* Added a kernel interface at `/proc/touchpanel/gesture_dt2w` for easier
interaction with power HAL.
* Add parameter to OSS power HAL to use this interface
* Added keycode for touchpanel to wake up the device
* TODO: Maybe add support for more touchscreen gestures?
* The CAF audio policy xml doesn't work properly with AOSP audio. Nuke
it and import aosp one.
* Import BluetoothResCommon overlay hack from violet. Note that we have
to insert this overlay in `on boot` because Magisk works in `on
post-fs-data`. Magisk can mess this up.