* All of the variants are close enough to each other that
carrying these in the device-specific trees doesn't
add much.
* Sizes picked by selecting the smallest value from each
of the device-specific trees for each variable.
Change-Id: Ibe024ec857db971ff1522d05cf55e8492816b7ec
* This removes /system entry from fstab, since this partition
is now early-mounted and the fstab entry is specified in device tree.
* At the same time, also include a fully populated fstab, in order to avoid
build breakage while generating recovery updater scripts.
Change-Id: I8e558458b984e97a45a920c3751a6b7c3f2ebc5c
* cmhw is dead, but we don't actually carry any local classes. Just
stop appending to the variable altogether
Change-Id: I075ad79ed99b0b85a21af594db0036136c984542
* This now matches the expected library name for Oreo and the scheduler
library is removed at the same time because it's not needed
Change-Id: Iec80b9fd871f82d4c34d54f70360eed77559f52f
* The updated audio HAL sources (for instance 8.0.0_r33) use
the formats directly through the pcm_format_from_audio_format
inline functions to resolve and validate provided formats,
however in our case the formats include values outside
of the allowed AUDIO_FORMAT_PCM_... values and fail
* Crash situation was happening upon 3.5 Jack plug only
Change-Id: I4b613c25ea7fd202a434c18c2fdd06e55a57c456
Signed-off-by: Adrian DC <radian.dc@gmail.com>
The current HIDL implementation needs BT_WAKE_VIA_PROC_NOTIFY_DEASSERT,
and PROC_BTWRITE_TIMER_TIMEOUT_MS = 0, same as angler.
Change-Id: I1b5d12788ab2689b3fb1779957d263c804def590
Test: Manual use of Camera, Movies, Photos and YouTube apps.
Test: With CtsMediaTestCases.apk installed,
adb shell am instrument -e size small -w
'android.media.cts/android.support.test.runner.AndroidJUnitRunner'
Bug: 31399200
Change-Id: Ib2d43fcfc7bbd00d47cf81a98b415d2be2e0e12a
We need our new wifi native daemon wificond for Android O.
This CL gets it installed on the device.
BUG=29220405
TEST=compile
Change-Id: I2fcd62b1dd6cbe292d89cf97085c9549bf69ba39
*) frameworks/base bool config_intrusiveBatteryLed is no longer
used so it has been removed.
*) Use LIGHTS_BATTERY_LIGHT capability in lineage-sdk instead.
*) Update config_deviceLightCapabilities comments
*) Move bool config_intrusiveNotificationLed out of Lineage-specific
overlays because it's an AOSP config
Change-Id: Ia813cdd0596ece07ff38e1087d9cdf9e135f20be
This reverts commit b7f109ed9f.
* So, that was 100% my derp. The cpufreq directories come and go as
cores go on- and off-line.
* Now, I wish I had notes as to whether I made this change in the
first place because of an error in a log or just based on manual
inspection.
Change-Id: I2782fefa80560bf9e20001e72ad378553d787ac0
The new camera interface calls set_callbacks with a pointer
to it's internal CameraDevice and expects following calls to
the callbacks to use that pointer.
Store the pointer in the camera wraper and intercept the
callbacks calls to pass it along.
Change-Id: I99f02484e12a3f72cf1be13f1c724f474a452d7f
* Don't do this, it destroys performance!
* Android uses memory cgroups to manage ZRAM. Memcg allows you to
view stats as well as set options like swappiness on a per-cg
basis. In the main init.rc, the background cgroup already has it's
swappiness set to 100. This patch sets it globally, which will
aggressively swap even foreground tasks into ZRAM which has a huge
amount of overhead.
Change-Id: I9f39b830e5817f796a42c377696864aec9bf2f22
AOSP and mainline are going towards removing old 32-bit binder API support.
64-bit binder is 100% compatible with 32-bit kernel and userspace,
so there is no reason for us to keep using the old solution anymore.
We've switched to new API in our kernel, same thing should be applied to our userspace.
Change-Id: I3c95bd7fbd023c5cb08e856b3a3889c03228e843