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
This change adds a check for the ramzswap device. This is useful
if the kernel includes ramzswap built-in and not as a module.
Change-Id: I39105064c8fdd678ca3d7e332703b6040806f601
Support module placement other than the "modules_install" location.
(i.e. /system/lib/modules/ or /system/lib/modules/`uname -r`/)
Change-Id: I04c5175b13655c09e1eb9b47fa0745d1cfcb376d
This app is part of the new Gapps from the GRI40 N1 update.
Try it with these Gapps I packaged for lack of a better source.
Change-Id: Ib49fd13e0270dfa15d5e05843a6f11f2b2d6388e
http://bit.ly/hfgtL0
It was not working until I noticed the error,
and works since I manually edited it. First
time I thought I had accidentally edited it
to a wrong value, then I noticed that I needed
to edit every time I updated cyanogenmod, so
I found the error in the sources and I'm
reporting it here to save future updates...
It is
$ host 193.209.134.141
141.134.209.193.in-addr.arpa domain name pointer mms-service.mobile.sonera.net.
and not
$ host 93.209.134.141
141.134.209.93.in-addr.arpa domain name pointer p5DD1868D.dip0.t-ipconnect.de.
Change-Id: I62cfd18f29076189e1da5379bb37dc5bb533c815
