The current logging macro always uses LOGE, which is
confusing to external developer looking at our logs.
Also changed LOC_LOGx definition to follow the same
syntax as that of LOC_LOGX.
Bug: 29499503
Change-Id: I803233a9d0b241bf9aeb2ee0d4bd2e7cc52ed75b
CRs-Fixed: 1113702
Explicitly add liblog as dependency for modules that use Android
logging. Also remove obsolete build flag.
Change-Id: I91a458b44ff34c91a8f6875f5c3e931f620c613a
Removing statement to set LOCAL_CLANG flag explicity to
true. It will be true by default.
Change-Id: I2eaba5a89e64088e3383b962dceaaa7e975e997a
CRs-Fixed: 989476
* Due to commit I9b346b4053ec12c8a78a143a4dc0e708c44888a2
"Support EGL_KHR_partial_update without EGL_EXT_buffer_age"
in libhwui, EGL_EXT_buffer_age extension was forcibly enabled
if EGL_KHR_partial_update was available, even if the EGL driver
was not providing EGL_EXT_buffer_age support
* On older Adreno drivers, renderthread sources could use bufferAge
specific swap behaviours and would result in partially missing
display redraws upon animations and rotated screens,
for instance flashing action bars, blinking loading bars
and half black displays in landscape rotations
Change-Id: I16fe13f0726792522e382716f8f24eccf2a27701
Signed-off-by: Adrian DC <radian.dc@gmail.com>
[haggertk]: adapt to system_prop.mk
Signed-off-by: Kevin F. Haggerty <haggertk@lineageos.org>
* These doesn't work, libRSDriver_adreno is missing symbols
* We could try to shim/kang around this, but AOSP's is fine
Change-Id: Ic315c4fe3980855c53102290f9e9a532583042f8
* Remove some old hacks
* Remove an unused ril prop
* Move to using a prop for mQANElements
* Reorganize structure based on AOSP RIL.java
Change-Id: Id837ea9b9fc82ebb74212d51974da385b40180a5
* It doesn't make sense to rely on utils in recovery
when we can't guarantee they'll always work right,
and need to hack around them for secontexts
* Just use toybox's cp from /system, as it works
right, and is something that we have control over
Change-Id: I1536eebc7c974a549012aaba643b34d732665cfd
This reverts commit 4f33809cf6.
* The cause for the apparent space leak (until unmount) is caused by
asymmetric access by Android to the upper vs. lower filesystems on
external storage and the fact that sdcardfs maintained upper/lower
icache and dcache that are not synched. While normally only visible
to users on external sdcards, it could be forced on internal storage
by twiddling /data/media/0 and /sdcard.
* See https://review.lineageos.org/#/c/193137/ for resolution.
Change-Id: Ia642815aef2f7e7ab76507a27cdc7cd1d4648028
This reverts commit 3c04b582d7.
* The real cause for the seeming Adaptive LMK misbehavior was a merge
derp in the kernel that did not take into account zcache pages. This
is corrected with LineageOS/android_kernel_samsung_msm8974 1355fda449
Change-Id: I9441538de0d2d0dfc775519a7e8e17b584a2b833
* There is some kind of subtle bug related to unlink where the newly-
freed space is not propagated to lower-level storage until unmount.
* This has been observed across multiple underlaying filesystems, and
I've spent too much time already doing A/B testing, so let's do the
sane thing.
* This is a logical revert of 936ea50b37,
but it's better to leave the prop explicitly defined to false in the
event that the system-level default changes to true in the future.
Change-Id: Ie7cbce4673de7ea7d6746ae79f2cda333c96b2f6
* This is being overly aggressive, so let's go ahead and disable by
default. It is still available in kernel, so those "advanced users"
can go ahead, use it, and tweak things to their heart's content.
Change-Id: Ife119211a49479e0edb5d0c8ac04773d01d10f28
* These aren't copied to the final build, drop them
to avoid confusion of where to look for configs
Change-Id: I20a117fc2ef230e04838283be721a45405d8768f
* Move TWRP fstab to twrp directory and use TARGET_RECOVERY_DEVICE_DIRS
* Remove variables set globally in Lineage tree
* Set TW_NO_LEGACY_PROPS to true in preparation for O compatibility
Change-Id: I8b11be9dbfdb4fd9e1cde7b4a5610d5188fddd9e
* Yes, this looks horrendously wide-open, but this only applied for the
complete sandbox that is external sdcard
Change-Id: Ibd1fe240eeed65f079e810a3da5157a4e64944f2
* cpu0 is the only one with cpufreq/scaling_governor or
cpufreq/scaling_min_freq, so let's not try that for all 4 of them
Change-Id: I5820a5e436e231d77de94babbea347d63ff9853a
* The 4 bytes at 0x76c8 were edited to 00 00 00 00 (NOP) to cancel the
call to __android_log_print, eliminating LightSensor logspam, when the
sensor registers 0 lux
* Inspiration taken from k3gxx
Change-Id: I4bb25b1e6818e74e4a5eab18215e870d0b7f9c0f
vcs_stop_auth_session() was called invoking qseecom securefp app without
first calling sensor_init(). That crashes soft-reboot.
Add some more other robustness too and close the fd.
Change-Id: I586139f52d3dc841b8960e1de8c50d596e98d210
Do not grant DAC override permission which would allow this daemon
unix permissions to everything.
avc: denied { dac_override } for pid=2664 comm="rmt_storage" capability=1 scontext=u:r:rmt_storage:s0 tcontext=u:r:rmt_storage:s0 tclass=capability permissive=0
Add wakelock group to access:
/sys/power/wake_lock
-rw-rw---- 1 radio wakelock 4096 2017-06-28 00:37 wake_unlock
Change-Id: Ib02b4aedab479f5ad8aca3a2100b5c489397002a
* Update primary blob source note
* Describe where pinned blobs come from
* Copy, don't pin, the alternative BT blobs. This will make it more
clear that something should be fixed if BT firmware actually gets
updated in the future
Change-Id: Ice23b6135c84256848ef6d58d880d32b07969e33
Kevin F. Haggerty
Dan Pasanen
Kevin Tang
David Ng
Saurabh Srivastava
Michael Bestas
Adrian DC
Simon Shields
Paul Keith
Ziyan
Corinna Vinschen
Joey Rizzoli
Andrea Arcangeli
Bruno Martins
Patrick Lower
Martin Hoffmann