Calling is-board-platform-in-list from this makefile was not
returning the desirable output, thus resulting in a failure
to meet the conditions for the UM4.9 and UM4.14 family platforms.
Due to the fact that this makefile is included in a very early
stage in the build process, the QCOM macros are not defined.
Simply use standard macros like in rest of the makefile.
Change-Id: Iad889882f94167f1bc1761ddd549dac9dcdee3ba
* Reorganize
* Remove no longer used Development package
* Remove LiveWallpaperPicker/PhotoTable which are included in full_base.mk
Change-Id: I56f9f586f27172e7336699dbe57f7a43d7ef8722
* No longer used by any device and fw/base part is missing
Revert "Update boosted audio files 2/2"
This reverts commit 103c64a964.
Revert "Add volume boosted ringtones (1/2)"
This reverts commit a1c783fb28.
Change-Id: I384f44d515e2bcc237662184de0830836ba95b09
The kernel make command is executed in the build root. Without absolute
out paths, kernel out start with "out/" meaning it would be created in
the kernel source. Add BUILD_ROOT to the argument to ensure it's always
made in the actual out/ dir.
Change-Id: I425134a893d4d5c9f31efccaf75e153b5462b76c
The GCC toolchains are no longer added to the path by default, so
we need to hardcode the full paths for these. Also set variables
for every arch, and then set the toolchain to the arch specific var.
This is so we can set the ARM32 cross compile flag for vDSO32
enabled kernels.
Change-Id: I7e099a26a17f4a3cc9be6232a26c671e8fcfbdef
* -androidkernel ones became symlinks to -android ones long time ago, use
-android executables directly to simplify the logic on these platforms.
* Keep arm on -androidkernel because it doesn't boot for some reason.
Change-Id: I97dd93121fc0e805a965e3f8b84466dd7bd686c0
Using preinstalled system headers and libraries is no longer allowed.
So we're gonna make our own prebuilts/openssl so we can build kernels.
Change-Id: Ic5bc3b14c37b3bca352932c6f19a592377dbaf27
The built ccache command is now deprecated and spits out errors. ccache is
also no longer used for the full build unless CCACHE_EXEC is defined. Move
the kernel to the same logic in order to actually use ccache and silence
the warnings.
Change-Id: Iccedd9d5868d31060677667cc18810aae0149a26
Required for new commits on frameworks/native
* Fix lag during screen recording on some platforms
* Fix screen flickering after disconnecting from Android Auto on some platforms
Change-Id: Ia0ed0bbfda44fb5ccb184ace854ec1bf9a7d819a
... in order to make them selectable in charging sounds settings.
This way the user can go back to the default sound.
Change-Id: Iced4614baddd9033e0772e4a4221ed48dea6fc57
* Note: msmnile is treated like msmnile because unlike other Qualcomm
codenames msmnile does not expand to 8150.
Change-Id: If246c0ec06de22097d369c17ce48aa1270bab19c
* These are pretty useful for debugging config.fs
changes without rebuilding full system/vendor image.
Change-Id: I68fdeb2dc7c9f225784b55425407657645e34ac8
* There's actually not a whole lot QC-specific about these macros,
make them available at definition.mk inclusion time rather than
relying on BoardConfig to include them.
* Don't create a dependency on QCOM macros from a makefile
that is included very early in the build process.
Change-Id: I3dcaf0e068ca44732cfe58f69384621781ddda67
* Instead of nesting ifeq/else/ifeq/else/endif/endif construction, make
allows the more readable ifeq/else ifeq/else/endif construction. Use it
instead.
Change-Id: Ifd2635929799db593e04a13827f05c97e95487e4
These configuration options are set based on the Google configurations
located in kernels
(ex. https://github.com/LineageOS/android_kernel_google_wahoo/blob/lineage-16.0/build.config)
This is composed of 2 parts:
Revert "kernel: Correct CROSS_COMPILE_ARM32 toolchain"
This reverts commit c77bb3a5ba.
This breaks builds when building with upstream commit
ad15006cc78459d059af56729c4d9bed7c7fd860. That commit fixes LD being
used from outside the path, however androidkernel toolchains don't
have elfedit. Google specifically doesn't use androidkernel, so we
need to follow them on this.
Set CROSS_COMPILE_PREFIX to aarch64-linux-android- for clang builds
Upstream commit ad15006cc78459d059af56729c4d9bed7c7fd860 makes the
kernel build system use GCC toolchains for elfedit, so we have to
actually use a real GCC toolchain, not the androidkernel one.
Change-Id: I79ac4ac47d3ba6c2abbc5ce40e56ed5c707295b4
Currently we handle the DTBO images from start to finish, including
AVB footers, and just drop them in $(PRODUCT_OUT)/dtbo.img when done.
While this works for the most part, we are limited in what we can do
with the DTBO images. For example non-A/B device recovery images must
have a copy of the DTBO image appended to recovery (see AOSP docs:
https://source.android.com/devices/bootloader/recovery-image ). This
means that we need to pass the pre-AVB dtbo image into
BOARD_PREBUILT_DTBOIMAGE in order to let the AOSP build system handle it.
This commit reworks the way the DTBO images are built, placing them at
$(PRODUCT_OUT)/dtbo-pre.img instead and setting BOARD_PREBUILT_DTBOIMAGE
to that path so the AOSP build system can pick the images up and sign
them and append to recovery (for applicable devices).
Change-Id: I8819d7cd92ba298de67dbc7f6b321917ba8524f1
The lack of these whitelisted permissions causes a bootloop
when upgrading from earlier OS versions on devices that enforce
the whitelist.
Change-Id: I76b8fad5f0c49a7d008d19e7a116b5f19c75f739
* Add GRALLOC_USAGE_PRIVATE_WFD as valid gralloc bits for all
the platforms and GRALLOC_USAGE_PRIVATE_10BIT_TP only for the
UM 4.9-based platforms. Both are defined in the respective
display HALs (in gralloc/gralloc_priv.h) being the latter
only available for sdm845.
* This results in the same as applying https://goo.gl/SR7sFY,
but it's preferable since it makes use of our own method of
extending the valid gralloc 1.0 usage bits (see commit 59009f8).
TARGET_ADDITIONAL_GRALLOC_10_USAGE_BITS is extended here on
purpose and as a bitwise OR of all the values in order not to
clear what might have been set in the device trees.
Change-Id: I5536f341e75088cc72ac369065011388f0a6d3f1
* libemoji doesn't exist
* libprotobuf-cpp-full is always built and part of VNDK
* librsjni is always built by renderscript
Change-Id: I379aa405f937d54fc7ab1fb7a120683e91f2bbac
For Example new devices need the new Sprint APNs, so add a new board flag for
them to set that will make the build system add the new APNs to
the APN config XML. If the flag is not set, continue to use the
old APNs.
To add or replace APNs, the custom_apns.py script has been
added. If CUSTOM_APNS_FILE is defined, custom_apns.py
is run and generates a new version of apns-conf.xml.
Change-Id: I7ff12a4342de2a7663b2b66fd627244214a8dc71
Test case: override ro.adb.secure in vendor/extra/product.mk
Before this patch, the override would not affect the resulting
property.
Change-Id: I0deb8a6865030b09ed6ba0ede1658319ca033e67
Kernel source settings should always come at BoardConfig population
time so things that use the variable later don't end up pointing to
an empty or wrong variable.
The following is also squashed in:
Author: Christopher N. Hesse <raymanfx@gmail.com>
Date: Fri Aug 10 00:23:54 2018 +0200
tasks: kernel: Honor prebuilt kernel flag
For devices that want to use a prebuilt kernel, TARGET_KERNEL_SOURCE
would still be set to TARGET_AUTO_KDIR, meaning the build system would
still try to build the kernel if TARGET_AUTO_KDIR was present.
Setting TARGET_PREBUILT_KERNEL indicates this is not wanted, so don't
attempt to do it.
Change-Id: Ic79b3ac1b9c946fd258ada43dce2b08bb74ea0d9
Change-Id: If046b86ff0d18c76898e90295be873a8379f678a
HALs are starting to move to blueprint files, which means that pathmap
ifeqs no longer work. This results in modules with the same name in
different platform HAL directories. Since these modules aren't used or
linked anywhere outside the HAL directories and a device's device.mk,
we can safely use a soong namespace to isolate the different HAL
directories' blueprints. This defines the PRODUCT_SOONG_NAMESPACES
make flag so make knows which namespace to look in as well.
Change-Id: I549e6da863465d79b12c7453aa169d5d963afa52
These variables are usually set in a device's BoardConfig, setting them
in qcom_target is at the very end of the "configuration process" which
results in them being unavailable to plenty of other configuration
"things" (ex. soong namespaces or soong config). Move them to right
after a device's BoardConfig has been found and loaded.
Change-Id: Iddd731202d22ed3f8eb010197ce20d3c75a1f40a
* prepend-product-if-exists was developed specifically to handle some
special cases where Cyanogen Inc configuration ordering needed to be
handled ahead of the standard inclusion order.
Change-Id: Ia3e041fb9e3c84d0763d18e4a401121bc210b976
* Include all debug packages via PRODUCT_PACKAGES_DEBUG.
* Remove oprofiled and sqlite3 from the list, because the former
no longer exists and the latter is already part of
build/target/product/core_base.mk. Also remove gdbserver, since
it's already built by default.
Change-Id: Icde54061cd5a85d381b756364287344c3d216957
(cherry picked from commit e4d54e65cef919a77d51cce721eb741d2e512688)
* otasigcheck doesn't work on encrypted devices and makes
the zip installation fail since oreo.
* The build part of this was never ported to oreo.
This reverts commit aff5e54c4e.
Change-Id: I411f33c1db64844091c1692ef4706ae541925d4f
* Along with it, remove tune2fs as the tool is already part of
build/target/product/core_minimal.mk. Despite Google did quite
a big cleanup in master branch, it's still built by default.
Change-Id: I4cf1178c2f99eda5a45de4ba79705093de5cd9bf
* This ensures the prop is set correctly for devices
that build a vendor image by placing the prop in
/system/etc/prop.default, rather than /vendor/default.prop
so it'll be in a prop file that is run for mangle_default_prop
in build/make/tools/post_process_props.py, therby
setting persist.sys.usb.config correctly to "none".
Change-Id: I4027541cf1eae9dd967636efe35de9578922b725
* A/B OTA devices wont run backuptools in recovery (because they don't
go in to recovery to do an OTA). In these cases let's use a modified
version to backup/restore from within android upon postinstall.
* Add backuptool_postinstall.sh which will be run prior to the normal
postinstall script in order to backup/restore via addon.d scripts.
* This needs to be done in such a manner because we need /postinstall
mounted rw instead of the ro with context= options which are used for
the normal postinstall (dexopt) script.
Change-Id: I51511870634dd1ec5388adafddb446f95cc5a950
* Include MTK/QCOM rules directly from the build/core/config.mk hook.
* Place main.mk hook and main_version.mk into build/core with the rest
of the make system hooks.
Change-Id: Iad2f808f3e3eefbd2be2ca5facb907ff31babbb7
* Our properties were supposed to go to /system/etc/prop.default
after the following commit:
"lineage: Move to Google's method of defining system default props"
Change-Id: I6cb0e28a7599b010b389cc541015a37010a00f4b
* However if BOARD_PROPERTY_OVERRIDES_SPLIT_ENABLED is not true,
only /default.prop will retain the properties contents of
ADDITIONAL_DEFAULT_PROPERTIES and PRODUCT_SYSTEM_DEFAULT_PROPERTIES,
and none of our versioning identification was held in the system
* Enabling BOARD_PROPERTY_OVERRIDES_SPLIT_ENABLED globally would
break all properties on devices that handle partitions usually
at the device level rather than the kernel due to mounting races
* Create a new main_version.mk file to isolate LineageOS properties
that define the system's versions identifications, and use the
ADDITIONAL_BUILD_PROPERTIES internal build variable to include
from build/make through a common vendor main.mk entrypoint
Change-Id: I0060141c097b3d14c3710eee1e0caf7110634967
Signed-off-by: Adrian DC <radian.dc@gmail.com>
Add android.permission.MODIFY_DAY_NIGHT_MODE for com.android.systemui.
Introduced in styles api change.
Change-Id: Ic864da8eb01faa270bae22cabaddcb9458c8a6c6
PRODUCT_SYSTEM_DEFAULT_PROPERTIES can now be used to define system default
properties which should be installed in system partition.
Those props are stored in /system/etc/prop.default.
Change-Id: I6cb0e28a7599b010b389cc541015a37010a00f4b
* We no longer need to build the mount.exfat tool because
only kernel implementations will be supported from now on.
Change-Id: Ic7e1354e6ead6a96a9d6021de8dac4cfdabcbbce
For Treble enabled devices, PRODUCT_PROPERTY_OVERRIDES puts props
added with that in /vendor/build.prop. While that's great for
device-specific properties, these are global Lineage properties
which are descriptive of the system side, so move them to the list
that gets populated into /system/build.prop.
Change-Id: I8bb3d0fe13188478d4f7dedc306740a40f44a3e8
* Starting with Oreo, all the apps that target O+ are always subject to
background restrictions (android/platform_frameworks_base@42a386b771).
The manifest-registered receivers of apps with a targetSdkVersion
higher than 25 won't receive the broadcast. Instead, a message similar
to the following will appear in LogCat:
10-07 14:13:49.594 719 736 W BroadcastQueue: Background execution not allowed: receiving Intent { act=lineageos.intent.action.LID_STATE_CHANGED flg=0x20000010 (has extras) } to org.lineageos.flipflap/.EventReceiver
* Exempt some of our broadcast actions so that we can keep targetting
the latest SDK.
Change-Id: I075608e18994f64db5e89658757dca307f07c417
*) Put Lineage rc files in /system/etc/init instead of /init.lineage.rc
*) Split into function specific files (vibrator-specific stuff moved to
our custom vibrator HAL service)
Change-Id: I1d00950253fbf7fdd7a4b7bd52adbed971923575
When WITH_TWRP=true is set:
* Set recovery variant to TWRP, it should be synced
under bootable/recovery-twrp in Lineage
* Exclude SuperSU, we have our own su solution
Change-Id: I5e5e6f2b42282c4666cdc013405a1488a9c6341d
Considering sensitive phone numbers to be, hotlines dealing with
violence against women.
In the EU, these numbers do not show up in the phone bill.
In order to avoid these phone numbers to be listed in the Call Log, we
have implemented a new XML file which is parsed with phone numbers
from different countries to be filtered. This file needs to be copied to
device via desired Android.mk file in order to be able to process it.
The comparison is made checking the network MCC the SIM is connected to
in order to consider roaming and multisim scenarios.
Test: CallLogManagerTest.testDontLogCallsToSensitivePhoneNumber PASS
Change-Id: I2e78d0f3e13d1ad1298613651ece136e30b86dfe
Signed-off-by: Olaia Segovia <olaia.segovia@bq.com>
* Aosp browser is really old and insecure, remove it
* Jelly is a simple webview-based browser, so it relies on installed webview,
which makes it secure as long as webview is updated
* Gello is still alive, it overrides Jelly instead of Browser target
Change-Id: Idd1dbe37879e1c1d466b93f5e754f1108f4dcfa6
Signed-off-by: Joey Rizzoli <joey@lineageos.org>
This is required for all ATV builds. SUW will crash looking up the
wifi activity is it isn't installed.
Change-Id: Iccc982f46963024c065ac0b7c578ad60eb4d7d7a
* This is wasting space and is totally unused
Change-Id: I85115e979f4ff593df9a0c3a3ceb104b55bafe06
Signed-off-by: Paul Keith <javelinanddart@aidenswann.com>
Until CMFileManager is revamped or a suitable replacement is written, do
not include it in general builds. Basic storage activities can still be
completed with Android's built-in storage management:
1) Use the Downloads launcher
2) Settings > Storage (select volume) > Explore
Change-Id: Ic9c4eb2d0347332c4631d55c480b87cbc131116c
* remove aosp soundrecorder and cm screencast
* add only on full builds
Change-Id: I68f7c62d2f78ce3d34e3ecaa554544d11fd7cc92
Signed-off-by: Joey Rizzoli <joey@lineageos.it>
All usages of ro.com.android.dataroaming default to false.
The rest of the props are no longer used.
Change-Id: I2320e82a1859f8c13f3430a43aa8714186158ee0
(cherry picked from commit 76b66c1ab812e6e4749bec53e03bfc5084c38257)
- We plan on distributing an addon for our SU
- Developers that want SU by default can export
WITH_SU=true to their env
- This helps with application compatibility for
various services, while maintaining user flexibility
Change-Id: I6d52159676f805c3698ff59c896d943a3a4b25db
This property is already defaulted to 0 in the code.
The su_daemon is also disabled by default.
Thus, for all intents and purposes, root access is
already being disabled by default.
Change-Id: I1241689c0d3253aa2e44835c55839f24b3b74341
We no longer sync Launcher3. This entry never did anything anyway,
since we build Trebuchet instead, which overrides Launcher3.
Change-Id: Ia2c56c9f819025ba34cbff1daf8d3380a924a8a5
Trusted Face depends on libprotobuf-cpp-full.
Some devices already ship it (eg RIL needs it).
Include it here to build it for every device.
Link to OpenGapps issue:
https://github.com/opengapps/opengapps/issues/390
Change-Id: Iffee0aa6218dfef45f5cd728a999fa1114c0dd57
Signed-off-by: Alexander Martinz <eviscerationls@gmail.com>
The servers do not have ImageMagick installed right now,
breaking the automated builds.
Revert this for now.
This reverts the following commits:
840e781408 bootanim: Use a for loop to make part# folders
ce5405d1f7 Fix wrong bootanimation.zip from mkdir .../part{0..2}
6179d9494f cm: Build bootanimation.zip
67ddf37281 cm: Rework boot animation generation
Change-Id: I63fc43da9b1a6afea5f791e879f0bfc9a385d98d
* In init.rc, this prop will be used to set DOWNLOAD_CACHE
* If a device specifies having a dedicated /cache partition, by setting
BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE, use it!
* Default to /data/cache per AOSP
Change-Id: I838672ca4638c9665333c1a67257fc435f33f388
This was used for the HCE implementation by SimplyTapp in CM 9 - 10.2.
Since then, Android has an HCE implementation and this is no longer used.
Change-Id: Icd9db39829c1863c4962aab53959ad527da28bcd
RomManager hasn't been properly updated in years.
Is this still even a reliable ROM updater anymore?
Change-Id: I3ea57ec0121e6d6f933dd80031bb53514a44e362
* Honestly, I have no idea why this works. Or, to put it more
precisely, why it works without this on _some_ devices and not
others. All of a sudden?
* Without this patch I'm getting:
/opt/out/14.1/build-cm_d2vzw-clobber.ninja is missing, regenerating...
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::erase
make: *** [build/core/ninja.mk:167: /opt/out/14.1/build-cm_d2vzw-clobber.ninja] Aborted (core dumped)
#### make failed to build some targets (5 seconds) ####
Change-Id: I4bf43868bf7dfe13df57151ae3597246164cbebc
TeleService (com.android.phone), which is built on all devices,
also has dependencies on telephony-ext. As telephony-ext is
currently absent on non-telephony devices (most tablets),
FCs are rampant on these devices.
Build telephony-ext for all device configurations to fix
the dependencies.
Change-Id: I4094ace3764d9f41ed28fbb62067ad2b2228c3a7
In Nougat, CAF removed Helium as it is a duplicate of Hassium.
Switch back to choosing Hassium as the default alarm tone.
This essentially reverts commit 2b999181c8.
Change-Id: I62ff1565c76fddf2f744c26c44f30e940cf25b7b
Include the telephony-ext jar library in PRODUCT_PACKAGES
and in boot jar path.
The telephony-ext jar is needed for MSIM manual provisioning
and other telephony related functionalities to work.
Change-Id: I049ec39e88ec734e3770a9439d4c7ba8949b4357
* Move extra tools to common.mk. These are needed for CMFM, and should
be included for all.
* Move PhotoTable, LiveWallpapersPicker, SoundRecorder and Screencast
to common.mk. These apps are extremely small, and only takes up
less than 1 MB combined.
* Remove obsolete live wallpapers.
* Move sound property overrides to common.mk. There's no need
to have them spread across several files.
* Include CM audio files from common.mk
Change-Id: If308506cd9cd0a75014de988c242d700db5d16f3
* The maintenance version should not be set optionally
to its official value status, but only be used when needed
* Use the TARGET_VENDOR_SHOW_MAINTENANCE_VERSION := true
introduced in I77c924a13122c8e1d9af14501e46bc532f7aefbd
to show the value of the maintenance version in releases,
with an intermediary CM_VERSION_MAINTENANCE variable
Change-Id: I22b944a1d2d8586e5f3c75e19ca1c53aa3b22b59
* Moving this to open-source from CyanogenOS :)
* Thanks to Chao Chen, Ethan Chen, Pat Erley, Scott Mertz,
and Keith Mok for various contributions to this.
Change-Id: If79f9c279668d14ee0cde62889bb09e7185ef08c
CyanogenMod builds shouldn't show maintenance versions. Allow the
environment to override this behavior instead
Change-Id: I77c924a13122c8e1d9af14501e46bc532f7aefbd
As of f/b 9b8c6d2df35455ce9e67907edded1e4a2ecb9e28
we need to whitelist who can be backup services.
Change-Id: I52a004924e6d2651c5ecdec51a8c5a80bdd54a38
This allows projects to opt out for space limited devices.
Also create a common_mini.mk and populate it with common stuff from
the common_mini_*.mk files.
Change-Id: I7d7dee73b70f97a778353ca136434a6e36edaf7e
* backuptool.sh and its dependencies are to be used
on devices without the flags being checked, not with
Change-Id: Ia2e1e32c4878f52a0a781e64583a95b32f8d3611
Introduce the weather system feature, which will be used to
identify if the Weather Content Provider/Weather services are
available in the device.
Add SELinux entries for the cmweather service
Change-Id: Ibe862903095276f87f23c0d7dae54733eeeb5638
The priority order for overlays is PRODUCT > DEVICE > LOCAL
Having PRODUCT here was overriding all of the DEVICE_ specifics
mentioned in device repositories, which was not the intent.
vendor/cm is present as a set of sane defaults, but for the most
part these overlays are intended to be overridable by the device
if needed.
The logic is that PRODUCT_PACKAGE_OVERLAYS should be used by a
particular product while DEVICE_PACKAGE_OVERLAYS is used by
several products that share common device configs. Yeah, the naming
is counterintiuitive, but that's the implementation in
build/core/package_internal.mk
Partially addresses CYNGNOS-2229
Change-Id: Icfbc92593e37f3c00c3d26dd09e08d09267621ed
The default behavior is as if this setting is off. There's no need
to set it. Settings will now set it at boot if not configured.
This reverts commit e0e8c2772e.
OPO-490
Change-Id: I77963dfc9eea8ece25ed1b6b17bd2c6936ae69ee
These servers are being retired. Use C-Apps (Cyanogen Acct),
Android Device Manager, or one of the many other services
that are capable of performing these tasks.
Change-Id: Ifc20768f24d3a5f9a7510b98c5e7d563fc703382
* Lots of stuff in the wild actually uses wget, and Toybox doesn't
provide it. We already have Curl which does the same thing just
with some different arguments. This wrapper script can handle it.
Change-Id: Ic02da709fcd29808b96fabcd1ac4ddd9465f635f
Allow global disable of exFAT through environment variable
WITH_EXFAT. Maintain exFAT as enabled by default.
Change-Id: I85e8b14c51441fe52bd185be83880419ee831d5c
* Build new AOSP messaging app
* Remove no longer used WhisperPush/CMHome
* Messaging no longer depends on SoundRecorder
Change-Id: I202203449c97814972f1aad1af4d69afa1a61e7d
This will allow us to add supported mimetypes in libcore.net.MimeUtils
which in turn will allow more recognized mimetypes for anything that
uses android.webkit.MimeTypeMap.
Change-Id: I97febe17cff1d196f479b557fef3bca1b11bdd74
Issue-Id: CYNGNOS-1176
This was done for one specific carrier, and is breaking most others
that rely on DUN profiles. Don't.
Addresses CYNGNOS-999
Change-Id: I42fbbabfc87001bcec0c9978e33b999de8d5aecd
Change-Id: If62e6b1d2ac41730ff2a8d562173abd2cb768f93
Add cmstatusbar service to system server services context
Change-Id: I77c5de75722cc5f36a5326e3da57ab661b89d189
Build Platform resource package.
Change-Id: Id60f66b6db23989db1472a19bcb079b0083f7393
vendor/cm: Lock cm platform library/cmsdk to non-release builds.
Change-Id: I01c1c3fe559d438e28339ce426d7ba7e42724002
These were overloading the ASCII names to region-specific charsets,
which looks nice but it's horribly confusing if you're not native
from those regions and happen to be roaming there.
So... like our upstreams, just show the original carrier names
Change-Id: Icb3c6c9be2a4ee57866f2f57411a4f441be88f7c
/data is supposed to be inaccessible to begin with, and we don't
want the init sequence tampered with for user builds
Change-Id: If3eb5573248956a14ad56516a9871758f4c00989
(cherry picked from commit a9d772166365a27181a7441c10a6c60a2bab7dab)
this project does not exist in cm12 nor does it have a branch.
For cleanliness remove it
Change-Id: I956cb2e98b4e3fc0184cd614e180451a3d0b23d2
Signed-off-by: Simon Sickle <simon@simonsickle.com>
* Drop DSPManager and libcyanogen-dsp. Devices should switch to
standard Android effects or offload-capable versions.
Change-Id: I4f4eec5747e9073e576fe70e720ac3ffebb3fdd9
The group that maintains and builds the Terminal Emulator
have run into Google Play issues resulting in a package name change.
Update associated libraries for this change as well.
See also:
https://github.com/jackpal/Android-Terminal-Emulator/wiki/Recent-Updates
Change-Id: Ib50a8d8435ea12d2c74ea9a68f5f9ddadc7601a5
As new features and enhancements to the theme apk format are added
we will need a way for themes to specify which version of the theme
format they are targeting. Exclusion of the theme feature in a
theme apk will imply v1.
Change-Id: I0016d58341ca3144bb4a4faa16663ab29439ab24
* There is still a race condition here.
* Power users can re-enable this by setting
persist.sys.dalvik.multithread to true
Change-Id: I03686bafbac1859695466fcb522bc5436ec82e0d
Mini targets didn't include FFMPEG so far.
I don't see the reason to do this, the plugin takes up minimal space.
Change-Id: I712982c245f9cdb8dd1052a071a7590219b9a9c3
Default recovery flashing on system updates to false. This can be
overridden for specific builds/devices, but the option can be enabled
or disabled on all builds.
Change-Id: Ia1bc94bd1e5f799fc894286a6b2f4f7a8a3816dd
This reverts commit d2d1a7ffb1.
Revert "selinuxrelabel: Remove attempts to relabel /system"
This reverts commit cae5f24530.
Revert "Recheck /data for selinux labeling"
This reverts commit c4dcb16ca9.
Revert "selinuxrelabel: Add a check for dalvik-cache"
This reverts commit c7e9230614.
Revert "selinuxrelabel: Need to check in priv-app now"
This reverts commit 3013c99acb.
Revert "selinux: When adding userdata labels, do cache too"
This reverts commit 8994907baf.
Revert "selinux: Use a more reliable sentinel to flag /data labelling"
This reverts commit b52874de53.
Change-Id: I7779aaca3b0751ed74d525292681817182a0aa7f
This variable is used to build the fingerprint and description on
signed builds, and the dash can't go in there. Add it only when
constructing the final display version variable
Change-Id: I0736d3a88e5f9980c28e6e9afa7e2f9e2d23f815
On low-end devices, the current 48 fps boot animation can use more than
50% of CPU time, and if the texture cache is enabled, a majority of main
memory as well. For these devices, add half-resolution variants of the
lower-resolution boot animations which display 2x upscaled -- this
greatly speeds the boot process and makes the boot animation run more
smoothly.
Change-Id: I0140616ca38c52a06dd4622f1c20a9ca0da95f4b
The variable used does not exist at this stage of the build. Switch
to PRODUCT_DEFAULT_DEV_CERTIFICATE, which does exist when in use.
Change-Id: Icb3bbaa437e68b96e1ce05a09f6525cd1ddb9a6a
* patch set 1 to 7 doesn't fix the problem, it bruce forces the spn
list to ALL DEVICES.
* this change and http://review.cyanogenmod.org/#/c/57393/
will attack the problem at lowest level, customized it for speed
and memory.
* the best part is that it handles letters and exit the
function when it find a letter in the response from ril.
Change-Id: Ia63309acf38617e68b98ff1068463a942fa793df
Don't assume the path to the signing key is the default, it can
be empty and have the same meaning...
Change-Id: Id545d6436e9f21d6b62eec5a317ea7665190f104
Similar to the ro.build.id/ro.build.display.id distinction, and with
the same rationale; signed builds are intended to be stable by
definition, the release types have different meanings (user vs
userdebug), and the full CM version has too much duplicated information:
the device's name and build date are already present elsewhere in the
same information screen.
For signed builds, remove the duplicated information and the type,
leaving only the actual numeric version and the verbose build identifier,
turning for example "11-20140109-SNAPSHOT-HappyPonies-device" into just
"11.0-HappyPonies". If a simplified display version can't be built,
it'll be the same as the full ro.cm.version
Change-Id: I7d8cccbb3205bde710f0004df0a6bd12c39693f1
* Remove all this stuff. If a device wants ZRAM, it should be
enabled by the maintainer and properly configured and tuned.
* This stuff currently causes a conflict with the ZRAM support
added in Kitkat. Kill it.
Change-Id: Ib2488ea4463e32ec44b65fe786f732145b5b6e23
By defining TARGET_UNOFFICIAL_BUILD_ID in a device's cm.mk, users can
build custom CM builds with their own identifier in place.
This adheres to CM's policy that unofficial builds must be
marked as such, as both the filename and internal version will still
contain the word UNOFFICIAL.
Example:
TARGET_UNOFFICIAL_BUILD_ID := CatEater01
results in
cm-11-20131211-UNOFFICIAL-CatEater01-device(.zip)
Change-Id: I61acdf4698a7fe2b35d3d5315be4b444b1b97987
* These need to be installed setuid, which is a no-no for CTS.
Change-Id: I68d111db2db675116e214108776aa13c848d0c9a
Put procmem and procrank back into non-user builds
Change-Id: I193a9607dad40043649de6fea1f9bf0ab0c437f1
Tablets want MMS too (carriers send messages, etc), lets make this
for any device inherenting telephony.mk
Change-Id: Ida0e86d1f4d982580cef72816f93f88d0b0313e4
PRODUCT_COPY_FILES vendor/cm/prebuilt/common/media/audio/
notifications/Doink.ogg:system/media/audio/notifications/Doink.ogg
ignored.
This is due to Doink.oog already existing in frameworks/base
Change-Id: I7ab091680f9cb0fb349ff425cb3ee1273d32ee89
