| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Camera depends on libdomx which causes a boot hang.
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
| |
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
| |
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
| |
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adapted from Paul's commit for Replicant 4.2:
commit 4105187ae3ba28a5ee9e55dd52ba3596820f2fbd
Author: Paul Kocialkowski <contact@paulk.fr>
Date: Tue Dec 31 19:21:31 2013 +0100
Get rid of HDCP keys
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
| |
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
|
|
|
|
| |
Moved to hardware/ti/omap4
This reverts commit 42b138dc109af86c34a2e5d88adf3e68e5482835.
Change-Id: Ifb23acccb227cab118425347c46e87e4f1a82f62
|
|
|
|
|
|
|
|
|
|
| |
- TARGET_BOARD_OMAP_CPU is needed by omap4 hardware and ti vendor repos
which get inherit from device.mk.
TARGET_BOARD_OMAP_CPU is not defined at time if it is set in BoardConfig
- original this changes was made while unifying tuna, we are using
device specific builds here
Change-Id: If8d4569ce56fa8be68186438d9265963a6e40506
|
|
|
|
|
|
|
|
|
|
|
| |
Note that TARGET_BOARD_OMAP_CPU needs to be set first.
tuna:
- original commit applied on omap4 hardware repo,
need to be tested by motorola and amazon omap4 devices
first - inherit from device tree until that
Change-Id: I638f7af527b3724098d7379b58e30c7550aa1f16
|
|
|
|
|
|
|
| |
Since the common_mini build config frees up some space by removing
live wallpapers, we can include this in our builds instead.
Change-Id: Ia2e873e5228e49c025d6967c61008a60d3cbd3e2
|
|
|
|
| |
Change-Id: Ibeb04476b707283909704ba71bbf1bf40e8b5690
|
|
|
|
|
|
|
|
|
| |
Note that SMC requires "normal world"-assisted storage that is provided
by tf_daemon. Normally it's /data/smc directory, but this doesn't work
if one wants both /data encryption and hardware backed disk encryption
key storage. Therefore /dsg partition is used to store SMC data.
Change-Id: I9ef59d7f045c5c36950d73d5254ba751fb7853cc
|
|
|
|
|
|
|
|
|
|
|
|
| |
keymaster_tuna.cpp almost exactly matches keymaster HAL 0 interface,
only several small changes were needed.
Note the change in the flags (KEYMASTER_BLOBS_ARE_STANDALONE): this
is required for hardware backed storage of the disk encryption key
to function, see keymaster_check_compatibility() function in
system/vold/cryptfs.c
Change-Id: I207455efeb73cee26f08d2cfd12aa4fb91ccec23
|
|
|
|
|
|
|
|
|
|
| |
This lib inserts itself in front of the real RIL and shims the onRequest
function as a means of compatibility, bug fixing, and updating.
Conflicts:
system.prop
Change-Id: I779a275276816a32b19d9666021662d9dc71029d
|
|
|
|
|
|
|
|
| |
https://android.googlesource.com/device/moto/shamu/+/8de2aa968d333fe3a4ffe330859207566150bce9
Fixes ghost MTP.
Change-Id: I455278f7d8d05c9b5860c6e1dd650d20dcdef9bd
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While I preferred to just modify the RILs directly, it simply became too
tedious trying to fix three things that all have the same problem.
libsecril-compat: Log if unimplemented symbols are called.
Analysis of the RILs has shown these shouldn't be called,
but just in case, we should know if it happens.
libsecril-compat: Actually forward the writeString16 symbol.
Good thing I added that logging; somehow this IS called.
|
|
|
|
|
|
|
| |
Since these are both in our device tree now, there's no need to
have them be separated. This saves about 14KB of space as well.
Change-Id: Ibfcd7da4b30bb261586ecd9373e6fd4a343e0e06
|
|
|
|
|
|
|
|
|
| |
The kernels block subsystem has been updated which seem to have
eliminated the lockups we were seeing.
This reverts commit 0c982e56af824cfbd621e6b4e8ca3183b87ea5e9.
Change-Id: I17b0a0c724fbf1bbbf9f88a54a29447d7f592832
|
|
|
|
| |
Change-Id: Icb9afbf59715fe9039c1c03bcce9e5327e31ff57
|
|
|
|
|
|
|
| |
It makes more sense to just store it in the kernel, so it doesn't have
to wait for the filesystem to get mounted.
Change-Id: Ib5893157edd44806018f07ad8dad32ffe3704657
|
|
|
|
|
|
|
| |
Testing shows that only disabling the atlas service results in almost
identical memory savings.
Change-Id: Icc6c43fae3c1682b545d0dbc217f87b01f330fff
|
|
|
|
|
|
|
|
| |
While BFQ significantly boosts the I/O throughput, it causes random lockups.
We possibly have something conflicting with it in the kernel, but until it's
fixed, let's switch back to CFQ.
Change-Id: I8e189c16b09f3981836f22370c5a57025c9175c4
|
|
|
|
|
|
| |
From hardware/ti/omap4 revision e57f2b6.
Change-Id: I2e6164fdf6c0e2a2e75aee3bba3fe58a9c470add
|
|
|
|
|
|
|
|
|
|
| |
The prebuilt libpn544_fw.so has text relocations. Because the NFC app ends up
targeting the latest SDK API level, linker doesn't allow any libs referenced by
it to have text relocations, including the dlopen call to libpn544_fw.so;
All this lib does is contain a couple char arrays with the fw and fw version.
Change-Id: Iaac980193d92cfedb87f3cd80841f724f06d4876
|
|
|
|
| |
Change-Id: I1c8c182778fbd0538224e56612f0845837f33601
|
|
|
|
|
|
| |
It's exactly the same as ours, so there's no point having a custom one.
Change-Id: Ieb685198295bd60bbd7766a0cff4389a8a51d070
|
|
|
|
| |
Change-Id: I810d5128a0b312a189cdeec23113d0c71dcefd6d
|
|
|
|
| |
Change-Id: Ic5db1b608e8d767bd7c31f6ca6feacaeeb68a1eb
|
|
|
|
|
|
| |
Thanks to Hashcode for the values.
Change-Id: I166619632762da036fa6f2512d4092f7a64587a4
|
|
|
|
| |
Change-Id: I5e5d18ad54652bdaf61ccf7ad0372439dd8eca73
|
|
|
|
| |
Change-Id: I7a0c6a12b28df732be9d1df8963ca30307b19d22
|
| |
|
|
|
|
| |
Change-Id: Ib6e26508c05a8786948eba9f7788378689760f38
|
|
|
| |
Change-Id: I503112a3d892b489abb89520292fab9826e2bd8c
|
|
|
|
|
|
|
|
| |
The IMG architecture does not support the EGL_SWAP_BEHAVIOR_PRESERVED_BIT
in EGL configurations. This bit is used only to be able to change the
EGL_SWAP_BEHAVIOR, which matters when the default behavior is not the
one we want. However on IMG, the default swap behavior is the one we
desire.
|
|
|
|
|
|
|
| |
Conflicts:
BoardConfig.mk
Change-Id: I710674d87da75b079379fad02a84ffad52b57d69
|
|
|
|
|
|
| |
This replaces fRom, which was a proprietary non-pie executable.
Change-Id: I04bed63542f02400059968e012641c14e1a28293
|
|
|
|
| |
Change-Id: Ibbff09829d354a4e39adcf12d403c5dceb96d291
|
|
|
|
|
|
|
| |
My local make of camera.tuna didn't pick up on a few changes I made to the makefile.
Renaming libtiutils as other devices use a libtiutils_custom
as well, but ours isn't a 1:1 match with theirs.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Camera is still half-broken.
Credits to @MWisBest
Change-Id: I87a802abfacaf36ab22676f5284f0cc1996f6b03
|
|
|
|
| |
Change-Id: I4ed573bcac7e8d7b14292b928ddb9c018b70bae3
|
|
|
|
| |
Change-Id: I66d6128fa2e88b8986dc88625bf7ff08de7f7049
|
|
|
|
| |
Change-Id: Iee0fc870b5b2195c4bb369a364ef1a7dbe46ac5d
|
|
|
|
|
|
|
|
|
|
| |
HUGE thank you to @stargo for figuring this out.
Conflicts:
device.mk
rootdir/init.tuna.rc
Change-Id: I88c9c8f63a85b533bfbb459b2042aedda90ac0d8
|
|
|
|
|
|
|
| |
Change-Id: Iff82f5be1b25c4806e842319fb5b333d9a8223a0
Conflicts:
device.mk
|
|
|
|
|
|
|
|
|
| |
board-info.txt, bluetooth device name, ro.bq.gpu_to_cpu_unsupported.
Change-Id: I151ba8a7bd0c9b2a0ccf23fc97935bd63702047d
Conflicts:
BoardConfig.mk
|
|
|
|
| |
Change-Id: I68d8d05f1baa333e94da4e2450d9e961ec68bd0b
|