PS2: Adjust mnc on coop mobil MMS to be '##' format
Signed-off-by: Henning Nielsen Lund <hnl_dk@amigaos.dk>
Change-Id: I4cd0e838ca274440a56678252c8ad1f209da5a7d
* 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
These are a no-op due to the additional block-device protection from
e18c0d508a
so get rid of them entirely. Any installing recovery (or equivalent
installation process) should handle the labeling of system components
on its own.
Change-Id: I14c50f08efa6f05b03fad4fbc404219cc504e1ff
TBD: Do we still want to label unlabeled files?
This simply adds checks for selinux labels for
files under /data/misc/wifi which were not labeled
correctly for some devices
Change-Id: Iaacf6db792aaea1485502b424d639a1212c5841b
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
