Hi,
Please advise if this thread should be in another forum.
Problem: I'm working on a Galaxy S4 (aka phone1) that can receive MMS without any problems. However, phone1 does NOT receive MMS at all. The problem exists in both CM12.1 (11/15 Snapshot and any nightlies after that) and also persists in CM13.0 (any nightly). Phone1 is from T-Mobile (SGH-M919) and the carrier is also T-Mobile. If I put the SIM in a stock T-Mobile Lollipop (5.1) phone (aka phone2) that is also available for testing, phone2 receives MMS with no problem. There is yet another S4 available for testing (aka phone3) running CM12.1 and it has no problems receiving MMS at this location.
I've tried every combination and permutation of APN settings with no joy on this phone1. In any messaging app, Auto Receive MMS is enabled. Even if I disable that, I don't even get prompted to Download an MMS that is sent to this phone1.
Using Google's new Messenger app, today I prepared a MMS message (just a subject line with picture attached), used phone1's own number as the recipient (yes we can receive our SMS or MMS for testing purposes), then ran ADB (-c to clear first), then ran
adb logcat -v long > mmslog.txt
( syntax as seen here: http://forum.xda-developers.com/showthread.php?t=1726238 )
I hit the Send icon in Messenger, then let it cook for about 30 seconds, no MMS arrived,
then hit Ctrl_C to end the logging and close the txt file.
Just looking at the ADB file, I can find some seemingly relevant records that I believe are related to the outbound MMS I sent. However, I don't see anything that looks like it's related to the incoming MMS that I never see appear in the Messenger app.
Rather than just attaching a long verbose ADB log, is there an ADB syntax I could use that would be optimal for filtering just MMS related records?
Sorry for the elongated post. I appreciate any guidance offered.
Regards . . .
log the radio stack
adb logcat -b radio, and try to swap sim card
Related
I have been trying to find an answer to this, so maybe if I post I can get some feedback.
I am using an HTC TouchPro (Sprint) that I have flashed to Cricket. I have been experimenting with different ROMs and have narrowed the field down to just a handful that I would like to use.
My issue is this.
With the current ROM that I want to use (SsS 0203-NS), when I run the Cricket_Arcsoft2 CAB to set my MMS/WAP settings, I always end up receiving SMS TXT delivery notification messages from "System Administrator".
When I have the fresh flash installed, this does not happen. And it is not exclusive to this ROM, but I do enjoy this ROM and would like to use it.
To clarify: once I run the CAB to set my MMS/WAP settings for Cricket, I start to receive Delivery Notification TXTs for the SMS TXT messages that I send.
I have tried the various registry edits to deny the delivery notification TXTs as well as the Advanced Configuration APP. Neither of which seem to help.
Maybe there is another, more recent CAB that I could use, or I am just missing something completely, but any help to remove this annoyance would be greatly appreciated.
This will disable the "Administrator Ack" everytime you send a message. Open your registry editor and change below.
HKLM\Software\OEM\SMS
Change Delivery Ack DWORD Data to: 0
Hi all,
I want to preface this by saying I've searched the forums, and have not been able to find my specific circumstance addressed. I'm having a problem where I can receive MMS just fine, but I cannot send any MMS from my Galaxy S2 on KE7 with KE4 modem. I'm using AT&T in the USA, and came from an iPhone 3GS. I'm still on the iPhone unlimited data plan (haven't gotten around to switching to a 4G plan yet). MMS always worked just fine on my iPhone, both ways.
When I go to send an MMS, it just keeps trying to send the message forever. I initially see some data activity in the status bar, but it quits after about 5-6 seconds. The message just sits trying to send unless I delete it manually.
Anyone know why this would be occurring? Help is greatly appreciated!
sidenine said:
Hi all,
I want to preface this by saying I've searched the forums, and have not been able to find my specific circumstance addressed. I'm having a problem where I can receive MMS just fine, but I cannot send any MMS from my Galaxy S2 on KE7 with KE4 modem. I'm using AT&T in the USA, and came from an iPhone 3GS. I'm still on the iPhone unlimited data plan (haven't gotten around to switching to a 4G plan yet). MMS always worked just fine on my iPhone, both ways.
When I go to send an MMS, it just keeps trying to send the message forever. I initially see some data activity in the status bar, but it quits after about 5-6 seconds. The message just sits trying to send unless I delete it manually.
Anyone know why this would be occurring? Help is greatly appreciated!
Click to expand...
Click to collapse
I am having the exact same problem, but I can't even get receiving mms to work. The message comes through but fails to download. I have tried multiple apn settings but nothing works.
Just curious,but are you guys using wifi when trying to send or receive the mms? Data HAS to be on for mms to work, if I'm not mistaken..
Sent @ 04:20
Yes I have tried sending over both wifi and 3g with no luck.
mrrick said:
Just curious,but are you guys using wifi when trying to send or receive the mms? Data HAS to be on for mms to work, if I'm not mistaken..
Sent @ 04:20
Click to expand...
Click to collapse
I've tried using with WiFi and without...neither one works. Again, I can receive just fine, just not send.
Here I think is your answer.
If you say for example take a picture or video and then within the Camera app try and send either one as a Message, the MMS will fail IF you have the Camera app set to save to Memory Card.
If you change the Camera app to save to phone, then you can take a 8 MP picture and send it as a MMS from the camera app and it will resize and send.
I have mine set to save to memory card, so after you take a pic, you have to go into Gallery and find the picture, then send the exact same 8MP shot as a Message and this time the GS2 will correctly resize and send it.
I'd say its some bug having to do with saving pictures and video to the memory card, but the above way will get you a MMS to send.
Thanks for the info, but I'm pretty sure that's not my problem. I don't even have an external SD card on my phone, and when I go to the Camera options to change storage location, it's greyed out (can't change it), I assume because I have no other option since I don't have an external SD card installed.
Also, when I have tried sending pics via MMS, Handcent will resize the pic, but it still won't send it. BTW, I have tried sending MMS with the stock messaging app, and that doesn't work either...just in case anyone thought it might be Handcent with the problem.
Under Settings > Wireless and Network > Mobile Networks > Network Mode, do you have WCDMA Ony checked, or GSM/WCDMA (Auto Mode) checked?
I found that if I had WCDMA Only checked, I couldn't get MMS messages to work consistently at all.
I have Auto Mode checked.
bump....need MMS to work. help?
check your MMS message center settings. You can access it within the MMS app>menu>settings.
I had this exact same problem when I updated my modem and found out the reason I couldn't send messages because the Message Center phone number was removed.
The correct one for AT&T is +1312349810. Make sure to put the + there.
Edit: NM sounds like your prob is mms only. I have had this problem with my old vibrant galaxy S1 too. The problem was because of the way phone numbers were formatted. For what it's worth I fixed that problem by editing the contact so that their phone numbers are exactly 10 consecutive digits (3 digit area code + the number) without any hyphens or marks ie: 2382819391. No leading 1's, etc. Not sure why it happens but seems to fix it for me.
I haven't had this issue with my SGS2 though.
My Galaxy Note II can receive and send phone calls, I can use data over the 3 network and I can receive texts, but I cannot SEND texts.
My Note II is rooted, unlocked and running Jelly beans rom V5 on the 3 network in Scotland on a pay as you go SIM card. The SIM card works in my other UK phone (unlocked Nexus S), i.e. I can send texts when it's in the Nexus.
I have never been able to send texts with the 3 SIM card in the Note II, (as in this isn't something that was working and stopped, it never worked). My note II was able to send texts when it was on the Verizon SIM in the states.
After I send a text, the "view message info" screen show it as sending to a +44 number and says sent. Several hours later (after the recipient in question never receives the text) I get a text from +441144 (then recipients number) with a message stating " Your text - to - speech message to 01144 (number of recipient) has been rejected by recipient phone."
Calling my +44 contacts works just fine.
I have no idea how to fix this issue. Does anyone have any ideas/ similar issues with their Verizon note II abroad ?
Thank you for your help and time
Using rooted Verizon phone to text on UK three network
I had the exact same problem, three network, using a Verizon S3 with synergy ROM and a hacked APN (as Verizon would not allow APN to be added), I guess you figured that bit out? Using APN Manager Pro running as a system app as set by Titanium Backup Pro.
You also have to make sure you have all the right APN settings, this was done to make DATA work on the phone.
Now the problem you describe is exactly what we had, it's the format of your phone numbers in your contact list, for UK numbers while in the UK, you DO NOT use the +44 or 44... just enter the number as normal 0745 xxx xxx etc... and that fixes the problem. Btw It's quicker to log into your gmail account and edit all of your phone numbers in there, presuming you use Gmail to sync your contacts and not verizon backup as that won't work over here when off their network.
This does cause another problem though, if you happen to use Viber, then viber will not see the contact, so what you do for that is add ANOTHER entry in the same contact, so I use the WORK field, and you enter +44 745 ... you must have the + in there and you must drop the zero, this way normal text works using the MOBILE entry in UK format, and Viber can see the contact in thge WORK entry... all appears to work doing this.
I know it's off topic and you may not use viber, but if you do, then your USA contacts would have to change your phone book entry to +44 745 xxxxxx again including the + and international country code and they can then see you as a viber contact. To see my USA contacts I changed my entries to +1 xxx xxx xxxx, so an orlando number might be +1 407-999-9999 then Viber can see the contact, just use multiple entries within the same contact, there are plenty of fields available.
Hope all of this helps, took some time to figure it all out
Mark
Melian06 said:
My Galaxy Note II can receive and send phone calls, I can use data over the 3 network and I can receive texts, but I cannot SEND texts.
My Note II is rooted, unlocked and running Jelly beans rom V5 on the 3 network in Scotland on a pay as you go SIM card. The SIM card works in my other UK phone (unlocked Nexus S), i.e. I can send texts when it's in the Nexus.
I have never been able to send texts with the 3 SIM card in the Note II, (as in this isn't something that was working and stopped, it never worked). My note II was able to send texts when it was on the Verizon SIM in the states.
After I send a text, the "view message info" screen show it as sending to a +44 number and says sent. Several hours later (after the recipient in question never receives the text) I get a text from +441144 (then recipients number) with a message stating " Your text - to - speech message to 01144 (number of recipient) has been rejected by recipient phone."
Calling my +44 contacts works just fine.
I have no idea how to fix this issue. Does anyone have any ideas/ similar issues with their Verizon note II abroad ?
Thank you for your help and time
Click to expand...
Click to collapse
I'm having this problem too, on a Samsung Galaxy Stratosphere 2 that I imported from America (it's got a slide-out keyboard, we don't have them over here), also rooted and running on the three network.
I've changed all my +447 contacts to 07 but texts only send successfully when I start a new conversation and pick the 07 recipient. When they text me back the number at the top changes to +447 again and I can't reply without starting a new conversation.
Any tips?
possible workaround
I've installed Handcent to replace the stock sms app and it seems to be working well so far. As far as I can tell, replies are successful and the number doesn't default to +44
CM11 Dialer: Dialer/Browser automatically add "+1" prefix which blocks outgoing calls
Great experiences so far with CM11. Persistent issue with native dialer (as well as Google Dialer) and unnecessary plus-code dialing for domestic calls.
However, I've noticed a persistent bug: the dialer will not complete any call that begins with a plus code extension (for example, “+1 555 6946). The dialer produces a busy signal instead of completing the call. However, if I edit it before calling to remove the “+1” prefix, the call completes normally. This problem occurs even though I am only making domestic calls within the US, and occurs in every tested version of Cyanogenmod (although it is absent in the rooted stock rom).
I can replicate the problem for any number that I look up on a web browser through Google. For example, if I look up “Chipotle New York” and hit “call” it automatically sends the dialer a number with a “+1” extension. Again, this results in a busy signal unless I edit the number to remove the “+1” prefix. This means that I cannot simply edit all of my contacts to remove the prefix since the problem will occur anytime I send a contact to my dialer through a browser.
Thanks in advance for any insights.
Device Information:
- CyanogenMod 11-20141112-SNAPSHOT-M12-jewel
- Android version 4.4.4
- Baseband version 1.13.11.1105
- Sprint (USA)
- on HTC Jewel (Evo 4g LTE)
Greetings,
I'm closing this since it's posted in the wrong section and you have an identical thread in Q&A.
Please only post 1 thread on the same topic in the future.
Thanks,
BD619
CM11 Dialer: Dialer/Browser automatically add "+1" prefix which blocks outgoing calls
Great experiences so far with CM11. Persistent issue with native dialer (as well as Google Dialer) and unnecessary plus-code dialing for domestic calls.
However, I've noticed a persistent bug: the dialer will not complete any call that begins with a plus code extension (for example, “+1 555 6946). The dialer produces a busy signal instead of completing the call. However, if I edit it before calling to remove the “+1” prefix, the call completes normally. This problem occurs even though I am only making domestic calls within the US, and occurs in every tested version of Cyanogenmod (although it is absent in the rooted stock rom).
I can replicate the problem for any number that I look up on a web browser through Google. For example, if I look up “Chipotle New York” and hit “call” it automatically sends the dialer a number with a “+1” extension. Again, this results in a busy signal unless I edit the number to remove the “+1” prefix. This means that I cannot simply edit all of my contacts to remove the prefix since the problem will occur anytime I send a contact to my dialer through a browser.
Thanks in advance for any insights.
Device Information:
- CyanogenMod 11-20141112-SNAPSHOT-M12-jewel
- Android version 4.4.4
- Baseband version 1.13.11.1105
- Sprint (USA)
- on HTC Jewel (Evo 4g LTE)
Saw you hadn't gotten an answer to this in threads across a few sites, so hopefully this finds you. I've not found a proper fix for this bug either, but have been able to work around it by using an app called Prefixer from the store https://play.google.com/store/apps/details?id=com.tftbelow.prefixer&hl=en. A single outgoing rule is free. Just create one to remove all instances of +. The + will be put into the dialer still from google or calling back a number that came in with it, but when you hit send, the app intercepts the number, removes the + and the call connects.
Its a hack, but it works for now. Happy dialing!