* 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
* 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
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
/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
* 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
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
Also, set the default root_access property to 0, and
explicitly add to the build packages tools we always
want, to avoid relying on PRODUCT_TAGS that may change
upstream
Change-Id: Iecfb8501cfb2f556d5cafe7d18d06539c0433839
* Replace the 1-to-1 variable-to-buildtype stuff with a single
environment variable. CM_[TYPE]=true becomes CM_BUILDTYPE=[TYPE]
* Change the placement of the extra version tag: 10.2-21234567-TYPE-model-TAG
becomes 10.2-21234567-TYPE-TAG-model, for consistency with the rest.
The last component of the version should always be the model.
* Add support for the SNAPSHOT build type, for use with the monthlies
* Unknown types will still fallback to UNOFFICIAL
* Accept the jenkins RELEASE_TYPE variable as an alternative to
CM_BUILDTYPE for compatibility with older branches
Change-Id: Idf96c7ca887747a5ae49a17cf5adf642fb1d561f
* This package contains Bluetooth profiles implemented by Qualcomm on
top of Bluedroid.
* Currently contains support for MAP and FTP profiles.
* Also included is BTC for wlan coex on QC chipsets.
Change-Id: I933b14de4576691c31087c9de4d60f21cbe3678b
* There are a number of issues with this app, and it's currently not
working very well on most devices.
Change-Id: I36094c68fa0f642921d478aa72387bce2b88a224
This reverts commit ea14a88a2a.
Using the Package Manager prevents any danling wakelock from
killed service/receiver.
Change-Id: Ie3162ca4b18a7bc9c55613af39e88ea980407e5f
Rather than having to maintain out of tree changes, it is often
easier to maintain a hiearchy of changes, starting with the vendors
common config file. From there, inheriting products can pick up a base
and start to add or remove certain bits from it, making use of the
BOARD_SEPOLICY_* functions documented in external/sepolicy/README.
Change-Id: I28a4aaf6c126535f0a88001582641b234a750015
It was a long a cold night of winter, and I said "Oh,
how cool would it be if I had a better camera!"
The lovely elf came and rang my doorbell, giving me
a package. Inside, there was something I've never
seen before: A mystic cloud where, while inside,
everything becomes possible. Where your wildest
creativity bits become a reality. Rainbows and
pink unicorns, this commit adds Focal to the build.
Change-Id: I7e0d14164405ef1c0b2faa46965f8ec3f38ab7df
Since not all recoveries out there will support the OTA packages'
own labeling, check at boot if the system needs labels (and
apply them)
Change-Id: I58767977b90a78a12efe7bd9d713654eadf47e7a
- remove SpareParts: it's disabled and broken, the options it provides
are either useless/broken or available in development settings
- remove modelid_cfg.sh: no devices are using this any more
- remove opticharger: it's not used any more
Change-Id: I68c86b2407486c4b40998288cf1f70b7cb8170f4
Term.apk now contains JNI shared ojbects for all architectures.
Currectly, the script would only extract and copy armeabi object.
Change the script to extract all object and copy the correct ABI
object to the filesystem.
Change-Id: I167eafab523a4104063fec89b7ba136031c1d07c
Signed-off-by: Rocky Zhang <zhangyan.hit@gmail.com>
Keep a blacklist of md5 sums for scripts known to cause issues, and
ignore them when installing new builds
Change-Id: I19a88b58194a32da5eb5fe278f2c5b9a145b57be
The "import" keyword is only parsed once, for a one shot execution, during
the initial section setup, and before running "on fs". Having an import of
a file that's located in a filesystem other than root will result in an error
like
<3> init: could not import file '/system/etc/init.local.rc' from '/init.rc'
So... any files imported into init need to be moved to the root fs.
While we're at it, move init.rc changes that are specific to CM (and don't
involve modification of preexisting configs) into this file, to ease future
upstream merges (and minimize breakage on devices that override init.rc with
their own variants)
Needs to be paired with the corresponding system/core patch
Change-Id: Iab6340db2e28ef19dbcd84ae5c71737ce0cd491f
* Promo video here: http://www.youtube.com/watch?v=ogp9f4_yEoU
* It looks *way* better on a device, though :)
* The animation is square, so the names have changed.
Change-Id: I8eebdf29a7d30632d75210a6d3975d7ea17d5246
* Remove "update-" prefix and "-signed" suffix.
* Replace SNAPSHOT with EXPERIMENTAL (arcee).
* If CM_EXTRAVERSION, force to type EXPERIMENTAL.
* UNOFFICIAL builds now with datestamp in the same manner as NIGHTLY.
* date -u uses UTC timezone for consistency.
* Remove some CM7 dead code.
Change-Id: I681fd92e27aaf62c50eae20265ce07c67d477bca
Patch 2: Fixed the possibility of no CM_EXTRAVERSION resulting in 2 '-' at the end of the file name.
Change-Id: I3025977a5da1e28247c74416e1ac50fc6901eb23
Allow user to provide userinit.sh and/or userinit.d/*
scripts under /data/local to be run on each boot.
Change-Id: I96f3034bcdea8d4cc75929d21b69efa31c1cb108
* These can be used if someone wants to filter for CM features
* Basic feature com.cyanogenmod.android is included in all builds
* Include nfc_enhanced on devices that have NFC
Change-Id: Ib7704b791c8916f1eabe5f40fd21e2f0005d32f9
* Default for tablet is horizontal-1280x800
* Default for phone is vertical-480x800
* Override using TARGET_BOOTANIMATION_NAME in cm.mk (must come before
inherit of CM base product.
Change-Id: Ibd01236847b4f1de0cfd4246c8bd93b1f047005a
Tips & Tricks
=============
* 50-cm.sh contains only a reference implementation. You may customize the methods however you wish.
For example, 20-foobar.sh pre-backup can use a loop with conditionals to generate a dynamic backup list in
/tmp/foobar_file_list which is later printed by list_files() so the backup method will act on those files.
* Optional methods pre-backup, post-backup, pre-restore, or post-restore may be defined for special purposes.
* Inject new files into /tmp/addon.d/ prior to backuptool.sh backup if you want to act during the current CM upgrade.
* Delete files from /tmp/addon.d/ during post-restore if you want to permanently remove files from /system/addon.d/
Addons may use this approach to run a script only once.
* Scripts run in sort -n order. Prefix with numbers 00 through 99 if want to run in a particular order.
* You can have two separate scripts, implementing only backup in one, and only restore in the other with a different
number prefix of each. This allows even greater control the backup/restore order even further.
* You could use pre-backup to generate a one-time use backup script in /tmp/addon.d/ that deletes itself in
post-restore.
Patch Series
============
http://review.cyanogenmod.com/#change,13265
CyanogenMod/android_build
* edify generator
http://review.cyanogenmod.com/#change,13266
CyanogenMod/android_system_core
* permissions on /system/addon.d
http://review.cyanogenmod.com/#change,13267
CyanogenMod/android_vendor_cm
* 50-cm.sh reference backup script
* modular backuptool.sh
* support backuptool.functions used by /system/addon.d/*.sh scripts
Change-Id: Ifd5eaf9dcfd68d92e5043c21d1bae1dc0ad54860
Steve Kondik
Luis Vidal
Scott Mertz
Jessica Wagantall
d34d
Roman Birg
Abhisek Devkota
Tom Marshall
AdrianDC
luca020400
Adnan Begovic
Ricardo Cerqueira
Michael Bestas
Michael Bestas
Dan Pasanen
Arne Coucheron
Konsta
myfluxi
herriojr
NBruderman
Simon Sickle
cretin45
Chris Sarbora
repo Shareef Ali
Sven
Steve Kondik
Ethan Chen
Brint E. Kriebel
Ricardo Cerqueira
Matt Garnes
Steven Luo
Tanguy Pruvot
Matt Mower
Pawit Pornkitprasan
Chris Soyars
Koushik Dutta
David Ferguson
dhacker29
William Roberts
Giulio Cervera
Chirayu Desai
sleeplessninja
jt1134
Robert Burns
DvTonder
Rocky Zhang
Andreas Schneider
Chirayu Desai
Brint E. Kriebel
Warren Togami
Trevor Gill
Simon Davie
David Thompson
Sebastian Schmidt
James Sullins
Adam Farden