Fix NullPointerException in RecipientsEditor.

In function PointToPosition, should check if mLayout
is NULL before call function getExtendedPaddingTop
because mLayout is refered in getExtendedPaddingTop.

Change-Id: I750313c3a4bceb7213433cf3d110ea9e87cee0b8
Signed-off-by: Bin Li <libin@marvell.com>
Catch OutOfMemoryError for getBitmap.

Change-Id: I85bf682cc98de0f075b4d8d6ec621d56ae559adb
Signed-off-by: Bin Li <libin@marvell.com>
Send mms read report if it is required.

Change-Id: I35be42545f000c51ebe71444ab591c42b33160cc
Signed-off-by: Bin Li <libin@marvell.com>
Send next message if current one fails

If there is an exception during sending current
message, it will not try to send next pending one.

How to reproduce:
1) Send a sms to 2 recipents. First one is a
   invalid address, for example "invalid", and
   the second one is a valid address;
2) Message to the first address fails;
3) It will not send the message to the second
   address.

Change-Id: I9442711118a64d0d4b9b08a04cf717c97428bf46
Signed-off-by: Bin Li <libin@marvell.com>
Wake up TransactService when MMS data is available

In 2G network, mobile data is suspend during voice
call. MMS data will be notified as unavailable.
After voice call is end, It may notify Default data
connection before MMS data connection. When it
notify Default connection, it is unavailable in
MMS networkInfo and TransactionService will not
launch transaction; When it nofity MMS connection,
it is not connected so it will not wake up
Transaction Service.

How to reproduce:
1) Make a voice call in 2G network;
2) Try to send a MMS during voice call;
3) MMS is sending and waiting for data connection;
4) Hang up the voice call;
5) MMS stays in Sending state.

Change-Id: Ia719e8736cc6ccfcd236bceea4cb94f7c4dd94e5
Signed-off-by: Bin Li <libin@marvell.com>