From http://androidsu.com/superuser/
This brings the version in line with the current version of
the su binary and fixes the bug where su approval is
not stored.
Change-Id: I0ca67ae79942f34eaa16cc3cf26b312cf7a8cd67
backuptool should not be messing with whether /system is mounted
or not as it screws up the expectations of other scripts run
in the install process. instead the mounting/unmounting
functionality has been moved to ota_from_target_files
Change-Id: I0711afd517638e7d0a0c39369d3a776748245dd2
New notifications and ringtones were added[1], but without proper
metadata. This caused "House_of_house.ogg" for example to be
displayed as "House_of_house" in the ringtone-selection dialog.
Adding the TITLE tag fixes this.
[1]http://review.cyanogenmod.com/#/c/16482/
Change-Id: Ie8b7baeb42410205b399bbc2014d09c6d8946a4e
Allow user to provide userinit.sh and/or userinit.d/*
scripts under /data/local to be run on each boot.
Change-Id: I96f3034bcdea8d4cc75929d21b69efa31c1cb108
* 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
A Mobifone user contacted me and alerted me that the APN settings for Mobifone was wrong and provided the correct ones.
Change-Id: I8a6b9bde39d7394db2fdf7261b2a8026692fb808
Currently the tool only backs up the lib, but not the apk.
Seeing as how the market version of voice search is still not
up to date with the current release, it should still be backed
up with this script.
Change-Id: Ia130bb3e289fc3c2206a60ed0fcfd7dab816425d
Since the destination for all backed up files during an installation was
/tmp, all files sharing a name (like the full_model.bin files from
the various face detectors) ended up being restored as copies of
the last such file, effectively breaking the backup.
As a fix, when backing up files, use the entire original path to make
sure they're kept separate and restorable.
Change-Id: I399f7a9433a225871d97e0ecaeb051a90e68696b
At present, when running a busybox shell ("busybox sh") from mksh
(/system/bin/sh), one gets the following message before every command line:
sh: precmd: Permission denied
This is due to mkshrc exporting a PS1 which depends on a mkshrc defined
function, "precmd". Since "busybox sh" does not source mkshrc, it does not
have this function defined, resulting in the above error.
By not exporting PS1, "busybox sh" uses its own reasonable default. mksh
subshells continue to work as usual, since they (re)source /etc/mkshrc
anyways.
Change-Id: Ic9182e42aa033e811300d9e6e8d6d3f43e14e58f
increase required space needed for market downloads from ~20MB
to ~60MB (~105MB if system dalvik is on /cache)
Change-Id: I52fcd648374db4bf73ff478e9991a6a3162521d5
This corrects the MMS settings to match those seen on Virgin provided stock handsets and
fixes receiving of media messages.
MNCs 31 and 32 are likely to also require changing but have not been tested so are
unchanged by this patch.
Change-Id: I6bc40fa7bfa7f21cf3c6a36cdef2b46512075c6a
Signed-off-by: Pat Thoyts <patthoyts@gmail.com>
According to packages/providers/TelephonyProvider/src/com/android/providers/telephony/TelephonyProvider.java,
getRow() method is knowing nothing about such attribute and just ignore it.
So it should do no harm to remove such.
There's a "authtype" attribute that is parsed, but its value should be an integer.
Change-Id: I9cca16cdd68db30c3a1f76149b0699d49d82fb71
It seems such entries are coming from apps like APN backup&restore,
which have a slightly different format.
Change-Id: I51d949e4dc13e832c84ecccd66cd9cd723ea2ec4
This duplicate appeared with commit 294302200411907d848a0f51652a233398056360
"apn list refresh from paulweiss"
Change-Id: I0b66591088f67d04e8b7f94ebc5d1e41b1c45596
Previous default apn is a provider's special offer. After first connect
provider eats 5 UAH ($0.62), and users does not have enough time to disable
data at first boot.
Change-Id: I36f753608c91a0acba2dace4bebd86b4324a1f09
This is regarding the following patch:
5cdb4ec653
The patch which was to allow custom_backup_list.txt to be maintained while flashing via ROMManager
WHILE the flag/file force_backuptool is set/present still has issues. There are 2 reasons for this.
1) The flag is only checked during the first pass (backuptool.sh backup), as once /etc/force_backuptool
is known to exist, all files are moved to /tmp/backupdir as designated, but when the script is
ran again once /system has been wiped and updated, the file /etc/force_backuptool no longer exists
as it was moved to /tmp/backupdir/force_backuptool, so the script fails as it is not checking that
location.
2) When the backuptool.sh script is called, the above function (checking for force_backuptool) is called
*before* the /system partition is mounted. This therefor ignores the file regardless of whether it
exists or not. This is caused by check_installscript being called at the wrong point of the script.
There are therefor 2(two) main changes to this script to allow the force_backuptool override to work.
The first being within the main function of check_installscript, and the second being the location of
where check_installscript is called (ie, I moved it to below check_prereq call in the case statement,
as mounting is called before the check_prereq function checks if the ROM version is the same).
This affects *all* devices.
Change-Id: Ia7438f396eaa91b0723e56bb32ce98725e2b2025
The new Gtalk app with video and voice chat from the Nexus S
OTA update is currently not backed up by the script because
Google renamed it Talk2.apk and added a new lib for it.
Change-Id: I2b0245d561584fa4d84e7d424653543d723a1ac6
