* Wrong value of user_debug in cmdline prevented to try to boot in offline charging mode
* For charger, tell that we don't have a LED and to disable init blank (with this flag, charging mode showed animation, but didn't allow to show it another time when pressing power button to turn on the screen)
* Set a brightness value for charger. In this way, when power button is pressed, device turns on and shows battery icon correctly.
Conflicts:
BoardConfigCommon.mk
Our /recovery partition is very small (10MB), and we can't use xhdpi for recovery & even using hdpi for recovery still to big. Minimizing recovery's DPI even more will minimize recovery size, and we will build it.
Our /recovery partition is very small (10MB), and we can't use xhdpi for recovery. Minimizing recovery's DPI will minimize recovery size, and we will build it.
swapping back to this & removing zcache.compressor=lz4
console=null androidboot.hardware=qcom user_debug=23 msm_rtb.filter=0x37 zcache.enabled=1 maxcpus=1
It's not meant to be set as a board config flag. Simply do it by
inheriting the makefile that now also exists for devices launched
with KitKat.
Change-Id: I1ba570823a902cbd352be831b15e64c0eed63044
* Apparently settings user_debug in kernel cmdline breaks offline
charging functionality. Thanks at suudep for pointing this out
* Also remove unneeded androidboot.console=null
* P made changes to pthread_mutex_init() that are incompatible
with our libsec-ril libraries. In order for rild to even see a
radio as being availble we need the legacy behavior.
* Even though our libsec-ril libraries are from 5.0, which is API
level 21, we do not appear to require any of the other behaviors
from API levels earlier than 27.
Change-Id: I3b3d0160236df09bdae95c5d9f10a61bf91ebc72
* This singularly handles both text relocation (M) and mutex (P)
linker restrictions
* mediaserver - Needs text relocations
* mm-qcamera-daemon - Needs both text relocations and mutex restrictions
relaxed
Change-Id: I97a79fb57aaadf5cf62894489522b2de6d8c2e36
* Rename klte-common -> s3ve3g-common
* Drop fingerprint related blobs
* Drop camera shim, we do not need it
* Drop CameraWrapper to msm8226-common, as all msm8226 devices uses it
* Drop broadcom NFC
* Add buildable libpn547_fw.c, libpn547_fw_pku.c, libpn547_fw_platform.c dumped from stock S III Neo sources
* Update audio configs with stock S III Neo ones
* Update power_ext for S III Neo
* Drop broadcom WIFI for Qualcomm WIFI as we got a Qualcomm WIFI chip
* Drop broadcom bluetooth as we goot a Qualcomm bluetooth chip
* Update partitions for S III Neo
* Update rootdir for S III Neo
* Update overlay for S III Neo
* Update liblights path for S III Neo
* Update deviceperms for S III Neo
* Drop consumerir as we do not got an IR blaster
* Update TWRP files for S III Neo
* We have included the appropriate android_atomic methods in libril,
so the symbols are loaded into the process space and the libsec-ril*
dependencies for all builds are handled.
Change-Id: I93289af789df7e263488e1db29bdbde0d0964e97
* Recent binder changes caused our approach of shimming libcutils to
re-add the non-inlined android_atomic* methods to start getting
slapped, at least with NDK apps. This looks oddly similar to the
heads-up we received in 7.0, so no clue why it let us do it in 8.*
prior to now.
* See: https://developer.android.com/about/versions/nougat/android-7.0-changes#ndk
* We did this because all of the libsec-ril* blobs and libuiblur
needed it and doing each and every libsec-ril seemed fragile and
fraught with the potential for error, but "fragile and fraught with
the potential for error" is better than "phone breaking". And blur
doesn't seem to ever be coming back.
* We'll leave the "standard" libsec-ril.so here and let the
individual devices handle anything specific if they have variant-
specific blobs
Change-Id: Ib11048e4924f34ade20f44b707f0106e139f2f82
This reverts commit aee12a34df.
* No Samsung msm8974 device is going to develop an OSS camera HAL
at this point. Move this common stuff to msm8974-common.
Change-Id: Ib0bb18fe819e2ebbb39c9b278ccf687444f65488
* Mounting /system partition is handled in kernel now,
however removing the entry from fstab caused issues building
the OTA. The workaround was to have a separate fstab, but turns out
that simply setting the recoveryonly flag does the trick because
those are then ignored during a normal Android boot.
Change-Id: I2944384d0a1c41bc9f9f51e2e29daff2bed0a0f4
* In particular, the RIL on CDMA variants seems to only work reliably
on first boot after flash, when things are all slowed down while
dexopting. After that first boot, it's hit and miss whether a
particular boot will have function RIL
* Slow things down by limiting ourselves to a single CPU on boot,
bringing the rest online when boot has completed
Change-Id: Ie194740cf0487268dc0dbd3377bbb790cdd1b04d
This reverts commit 6daa361afe.
* We're out of cmdline space and we don't even make use of the symlink
that this used to automatically create.
* If we ever want to use the bootdevice symlink, just create it
explicitly (without prop) in init.qcom.rc
Change-Id: I1c45c3ed3605f4020d824be2775639c04ba8b60d
Nolen Johnson
DJABhipHop
matteo0026
RomanDesigner
Jiyong Park
RomanDesigner
Bruno Martins
Francescodario Cuzzocrea
klozz
nx111
Kevin F. Haggerty
Paul Keith
Michael Bestas