Issue #1203
closedCannot send MMS messages
0%
Description
Using the V0003 images of Replicant 4.2 for GT-I9100
logcat | grep mms
D/ConnectivityService( 2829): ConnectivityChange for mobile_mms: CONNECTED/CONNECTED
V/TransactionSettings( 3419): APN setting: MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc looked for: current IS NOT NULL AND apn=?
D/Mms ( 3419): [89] markAsRead: update read/seen for thread uri: content://mms-sms/conversations/30
E/Mms:transaction( 3419): Url: http://mms.msg.eng.t-mobile.com/mms/wapenc
E/SendTransaction( 3419): at com.android.mms.transaction.HttpUtils.handleHttpConnectionException(HttpUtils.java:296)
E/SendTransaction( 3419): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:282)
E/SendTransaction( 3419): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:175)
E/SendTransaction( 3419): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:153)
E/SendTransaction( 3419): at com.android.mms.transaction.SendTransaction.run(SendTransaction.java:113)
E/SendTransaction( 3419): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:205)
D/ConnectivityService( 2829): ConnectivityChange for mobile_mms: DISCONNECTED/DISCONNECTED
I'm using the messaging app that came on my phone (com.android.mms 4.2.2-eng.paulkocialkowsk.20131205.151543)
Updated by Paul Kocialkowski over 9 years ago
- Priority changed from High to Normal
- Target version set to Replicant 4.2
Please try on CyanogenMod 10.1 and report if it behaves the same. If it does, then this is not specific to Replicant.
Updated by Denis 'GNUtoo' Carikli almost 9 years ago
- Category set to Telephony and mobile data
- Status changed from New to Feedback
- Assignee set to Paul Kocialkowski
- Device Galaxy S 2 (I9100) added
Updated by Denis 'GNUtoo' Carikli almost 9 years ago
- Assignee changed from Paul Kocialkowski to Thomas Kitchin
Updated by Wolfgang Wiedmeyer over 7 years ago
- Status changed from Feedback to Closed
- Resolution set to wontfix
Closing as there was no feedback for a long time. Feel free to open a new issue if the issue still exists for Replicant 6.0.