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
The model names on stock are MB200 and MB501 respectively. This commit
changes them to the correct values on both devices.
Many thanks to @adumont for pointing this out.
Change-Id: I3ba09ca40554e4737fa67bbd1faf7001a53f303d
Hide search key settings in CMParts for galaxysmtd.
Depends on http://review.cyanogenmod.com/#change,5757 for the added config
Change-Id: Ib6600425db8a2efe002c4edc8760bde8db635dc3
The U8220 and U8230 are the same device. This should be compatible with both, but so far has only been tested on U8220 (aka T-Mobile Pulse).
device config should be forked from https://github.com/TomGiordano/android_device_huawei_u8220
Change-Id: If0141d63d8d41360a9cfa69283e5bdbda17c1b8f
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