fancypants' experiments
epic
Oh yeah, fixed this. This could be a bug in servicemanager itself. servicemanager shouldn't be trying to free an already freed handle on failure. This will (obviously) only happen on selinux conflicts. (Had multiple context declarations for the same thing)
Oh just noticed, SAR devices don't have a system dir in the system partition anymore. everything in that dir is moved to the partition itself. So, "/system/system/*" is not a thing, but "/system/*" is.
Small clarification to everyone saying "/system/system" never existed. I mean, the system image containing a directory named "system" which is no more on 11.
Forwarded from Rohit Sekhar
GitHub
sm6150-common: Set TARGET_RECOVERY_UI_MARGIN_HEIGHT to avoid obscurin… · sm6150-dev/android_device_xiaomi_sm6150-common@8630702
…g recovery text.
Fixes: 77281082
Test: Build and flash recovery image (which is boot.img) on b1. Check
the recovery UI.
[Pig]: Bump 20 to 35 so that it looks better.
Change-Id: Ife964c74924...
Fixes: 77281082
Test: Build and flash recovery image (which is boot.img) on b1. Check
the recovery UI.
[Pig]: Bump 20 to 35 so that it looks better.
Change-Id: Ife964c74924...
fancypants' experiments
Bluetooth fixed! Thanks @shivatejapeddi :D
Switched to AOSP QCOM bluetooth and dropped the the bt vendor overlay for it ^^
fancypants' experiments
https://android-review.googlesource.com/c/platform/external/selinux/+/1428348
For people with prebuilt vendors, having system_ext selinux errors
if you need something in particular, i can probably send you a diff. I would not upload something like this publicly 😆
so looks like the way dynamic ims packages are added has changed a bit
you need to define a mmtel package and rcs package separately which telephony will dynamic bind to as opposed to the older
config_ims_package and config_dynamic_bind_ims