So I've been trying different things to hopefully get Delivery Reports working 100%. I've got an AT&T Samsung Galaxy SII i777 of course. I'm on AT&T. Currently running ShoStock 3.
Now the problem is that I can check the Status and it will never change from "Requested".
I tried switching to Miui. That one worked, but there was never an icon to show it. So I had to install GoSMS to see the delivered icon. BUT sending from GoSMS would also stay at "Pending". So I had to send by the stock app, then check if it was delivered in GoSMS. I also tried installing ChompSMS, but that one worked least of all. Didn't show any as "Delivered", even the ones sent from the stock messenger. And it also didn't get any when sent from it.
I then tried SuperNexus. It's fairly left alone...so it should work. Or so I thought. Again, the stock messenger stayed at "Requested" and never changed from pending.
And now I'm back to ShoStock. Possibly hoping that it just needed a reinstall, but no dice. Still doesn't change. Haven't checked if other apps show it as delivered, but so far, texts sent from the stock messenger stay at "Requested".
Hope this whole story didn't get too complicated.
It has never worked for me on this phone or on my cappy. I think it might have to do with the network or the other person's phone not sending the confirmation. I'm pretty sure there's a setting (maybe on iOS) that allows the phone to not send confirmation.
Sent from my SGH-I777 using xda premium
Can't be the network if switching to Miui helped, and I tried all of it by texting the same person. So they definitely are sending the confirmations. Just seems to have a problem actually receiving the confirmation.
You all realize who's fault this is right. It's that dammed Grinch. He wasn't content stealing Christmas and now he's got to steal our delivery reports? !
Related
My friend got a TB and can't send or receive pictures via mms. He gets the exact same message as a poster on a different forum:
"I just wanted to throw this out there as I have not found a solution...
I've had my Thunderbolt for like a week and a half now and for the majority its been great. Starting about yesterday, I've been unable to send or receive MMS/picture messages.
If someone sends me one, I get a little note in my conversation that says "so and so" is trying to send a message and lets me choose download or delete. This seems new to me, I don't remember seeing this notification in my text convo. If I choose download, it shows a little icon with a clock in it, as its trying to download the picture. After about 5 minutes, I get a notification that it failed because of a generic network failure.
A similar thing happens if I try to send a message to someone with a picture in it. My regular texting works fine and I can go on the internet perfectly. I've tried sending messages with WiFi and/or Mobile Data on/off... doesn't seem to make a difference.
Called VZW last night and they took me through battery pulls, SIM card pulls, and whatnot... didn't fix the problem. They were checking things on their end but did not see an issue. The last woman I got gave me two options, 1, she could open a network tix for me or 2, I could go to store and do a phone swap as I'm in my converage period. I told her to put in the tix for now, and perhaps I'd swap this weekend.
Anyone have any idea what is going on?"
So far nobody has answered. He's using stock rom, and the stock messaging settings / handcent settings match the way they are set on my Evo. If anybody could help it would be greatly appreciated.
is it on 3G or 4G? MMS will not work unless your in data coverage
Does not work on 3g, 4g, or Wi-fi.
what about sending it through regular messaging? I couldn't tell if he is using Handcent or using regular messaging. How about uninstalling Handcent?
The problem persists with or without handcent.
Make sure the picture being sent is not too big. If this doesn't do it you may have to call Verizon about it. Going back a few years I had an issue with my dumb phone. Couldn't receive picks. They had to reset my account. Also some providers don't always send pic messages so well to verizon. Have your friend have some on on Verizon send him a pic.
Sent from my ADR6400L using XDA App
Everything else works fine but I can not send or receive text messages. Message center phone number is set to 13123149810. Any ideas on what could be wrong. phone is stock setup
When you get phone?
Error message when send?
You try update profile?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
got phone yesterday at best buy, no error message, recipient just never receives the text. This is my first android, how do i update profile?
You might just call AT&T and make sure your account settings are right. For some reason, the Note is a little different setup on the back end for AT&T than a lot of other devices - particularly if you're moving from a non-LTE phone and the guys at BB may not have setup your account correctly. Still seems a little odd everything else would work right. I always thought it was an all or nothing kind of thing but who knows.
ok, thanks for your help
Been using my Razr maxx fine for 5 days now, and as of this morning, i am not receiving texts. I can send them, but i am not getting any. I have reset, hard reset, pulled the SIM card, rebooted, everything. the only thing that changed was installation of safestrap, and i know for a fact thats not the issue, because i froze it, rebooted, and tested again, still no texts. Im sure its "service issue" but there needs to be a way to fix it . Anyone know how?
It could be an issue with verizon. Give it a couple of hours or call them and ask. If they say they are unaware of any issue give it a couple of hours anyway. If evwrything was working and u didnt do anything it's not a problem with the phone ...... usually
Sent from my DROID RAZR using xda premium
Did you max your txt capacity in settings. Or delete the ones you have now. Try those two and see if you get txt now
Sent from my DROID RAZR using Tapatalk
I figured it out. After i rooted, i froze the stock text messages app (i use Chomp SMS). For whatever reason, i was still able to SEND messages, but incoming messages never got to the phone. once i unfroze the stock text app, they came back. So this one was entirely my fault.
opivboy2 said:
I figured it out. After i rooted, i froze the stock text messages app (i use Chomp SMS). For whatever reason, i was still able to SEND messages, but incoming messages never got to the phone. once i unfroze the stock text app, they came back. So this one was entirely my fault.
Click to expand...
Click to collapse
Just change your radio to 85P,
There is a thread by me in developer section
Sliced by my Razr on Tapatalk
My phones sms is all borked out. Phone is completely stock, unrootedx with the latest ota update.
My sms are ALWAYS timestamped wrong which seriously ****s with my ocd. Sent will he fine but received are always hours behind or ahead.
Also lately, phone won't send me my sms all day and then bam!! 12 messages all at once.
I have fine reception, never roaming, full bars of 3G almost always. What gives???
tawnyoc said:
My phones sms is all borked out. Phone is completely stock, unrootedx with the latest ota update.
My sms are ALWAYS timestamped wrong which seriously ****s with my ocd. Sent will he fine but received are always hours behind or ahead.
Also lately, phone won't send me my sms all day and then bam!! 12 messages all at once.
I have fine reception, never roaming, full bars of 3G almost always. What gives???
Click to expand...
Click to collapse
Are you using the AirRave (network extender) while at home? I am, and its been messing with my text messages since I switched to sprint. Doesn't matter which phone (OG Evo, Evo lte, Epic). Time stamps are screwy, duplicates sent, and sometimes it cuts the 1st half of my message off which makes my texts look like I'm crazy... lol... Only happens when I'm connected to the AirRave at home though...
I've had this sort of thing happen to me two or three times over the last 5+ years with Sprint. It was incredibly irritating, but it did go away on it's own after about two days. If it's happening to you for longer than that... I'd be concerned. And to second the above post, if you're using an Airave, all bets are off when it comes to text messages. I'm currently a month into back and forth phone calls to Sprint about getting mine replaced to see if that fixes my sms issue.
Use ICS tranquility and your timestamps will NEVER be wrong.
Not using Airrave.. its been going on for about two weeks now o__o
Thanks for the tip on ics tranquility, will definitely check it out!!
maybe this will work
I had this happen to me just a couple days ago, but I was not receiving or able to send sms at all. I went into a sprint store and the rep told me he had to call in to have my text messaging codes reset. So he called in and reset it and it worked! He said you should be able to do it over the phone, just don't be on your phone, or on chat.
Sense is completely messing with my SMS messages. Mine come in under the wrong number.
If I text a lot and delete some messages, the next person to text me comes in as the last person I deleted.
In the stock SMS app I can see it come in under the wrong person then quickly change to the right.
If I use Chomp or Go SMS Pro, it stays under the wrong person unless I kill the app and restart it. My texts are constantly going to the wrong people, and to my friends Facebook posts.
I've had this problem with every build thus far. I've wiped, RUU'd...still does it.
My friend is running Meanrom, it does it on his. Doesn't seem to do it on ROMs without Sense.
Someone else has to have noticed this.
I've never had any of this happen, nor have I ever heard of the texts messages being labeled as coming from the wrong contact. If it happens with other messaging apps, why do you think it's sense?
Sent from my EVO using xda app-developers app
mattemer said:
I've never had any of this happen, nor have I ever heard of the texts messages being labeled as coming from the wrong contact. If it happens with other messaging apps, why do you think it's sense?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
In my original post I said it happens with the stock app.
Its more of a problem with third party apps because they don't work the same way the stock app does. So when the message is displayed wrong for that brief second it grabs that. If I kill and restart third party app, the message changes back to the right person.
The reason I think its sense is because sense handles the messaging on these phones, and the problem cannot be replicated on a senseless rom. I can duplicate this problem on a rooted phone with meanrom. What are the odds chomp sms and go sms pro would have the exact same bug? Both of them rely on the core sms framework for data, so whatever is messing with them is happening in core. I've got a post about this over at sprint and it seems to be picking up a little steam. A fee more people.are crawling out of the woodwork with this problem.
if handcent is that third party app u using it will always do it .something is wrong with that app .use go sms
So... I recently got a replacement used Fascinate for my original unit that had a shattered screen. It has GeeWiz 4.2.2 loaded on it and I really like it. Damn near perfect... except for one thing and I'm not even sure/don't think it's the phone/ROM.
My texting issue is related to MMS. I can send any text... short, extended/pages long, picture texts (MMS) and I can receive all except long texts. And it's only an issue with my wife. She can write a book. LOL After doing more testing with other people, it seems to be a thing with Pageplus and Verizon. My wife is on Pageplus. I'm on Verizon...for now. My son is also on Verizon and has the same issue. I had a friend who is also on Pageplus send me a long text and it failed too. If I have someone on Verizon send me a extended text (over 140 characters) and comes thru fine. Only Pageplus customers seem to have the issue and it's only to my phone. I can have my wife send a long text to a friend who on Verizon and it goes thru fine.
The failure is on the senders side too. The senders phone will says failed to send. I don't get anything on my end. This is only to my phone.
I've searched and haven't found but a couple of references to a similar problem and no solutions. One possible thing that I haven't followed up on yet is this.... This phone was on Pageplus. I activated it on Verizon. Verizon shows no issues on their end at all but I'm wondering if Pageplus still has something in their system from the previous owner with this ESN. It's only Pageplus people that have this issue sending texts to my phone. They can send to other Verizon phones. And this is only long/extended texts that are 140 characters or more. Short texts and picture texts work fine. Oh....and if the sender attaches a pic to the long text, I will receive it.
It really weird. Wondering if anyone has seen anything similar or has any ideas. My next step is to call Pageplus support to see if they can help. I was also going to re-activate my old phone to verify the problem goes away. I welcome any insights.
Mike
PS - Sorry this is my first post. Can't believe I've been on this board this long and haven't posted before but this is a daily stop for me for years now.
Creepingdeath2 said:
So... .
Click to expand...
Click to collapse
have you checked the settings in the "Messaging" app itself, seems I recall a converting sms to mms or some setting that deals with that...
hhp_211 said:
have you checked the settings in the "Messaging" app itself, seems I recall a converting sms to mms or some setting that deals with that...
Click to expand...
Click to collapse
I thought that had more to do with outgoing texts than incoming but I will try it later and report back.
So I looked in the settings of stock texting app and it doesn't have the "convert long sms to mms" option but I'm running 8sms in Default mode, which basically just themes the stock app and adds a couple more setting/features....one of which IS "convert long sms to mms". It was doing this before I started using 8sms so it's not the app. I'll try the change and post back results.
I tried turning that option on but it had no effect. Open to other suggestions. Still need to call Page plus support yet too,
Sent from my Nexus 7 using Tapatalk
maybe try a different ROM to make sure it's not just an issue with GeeWiz? roll back to a stock ROM and see if that fixes anything... also use the right ROM, you know, eh03 for vzw devices, etc.
Or possibly try another texting app or even hangouts will do sms/mms...
It sounds like page plus is possibly not splitting the message into 2 sms or not converting a long sms to a mms unless it explicitly contains a picture,,,
I would think that is software settings
That also could potentially be the sender's messaging app not converting it to mms and/or not splitting the message into 2 sms.
I know you said there were multiple people sending you stuff,, to they both have the same app?
Let me try to clarify the scenario....
My phone is a Fascinate with Geewiz 4.2.2 ROM activated on Verizon (for now LOL).
I have several people on Pageplus that can't send me an extended text message, meaning a text message over 140 characters. One is an iPhone 4, one is a Fascinate on Superclean ROM, and the last is a Fascinate on Geewiz 2.9. If any of them try to send me a message that longer than 140 characters, it fails to send on THEIR end. I never see it. These same 3 people can send the exact same text that fails to other Verizon phones with no issue.
My phone was originally a Verizon phone that was then switched to Pageplus. When I got it, I put it back on Verizon.
It seems to me that this is an issue with Pageplus, almost like there's some information in their system still that sees my phone as inactive and refuses to send it. The texts fails on the senders end almost like they don't have service. I need to take a chunk of time and call Pageplus support and see if this is even a possibility. Regular texts and picture messages sent from those same phones DO make it thru. I can send all forms of SMS/MMS with no issues. It's only receiving and only from Pageplus customers. If a Verizon customer sends me an extended text, it comes thru no problem.
I would think if it's the ROM, the problem would be evident regardless of the carrier the message was sent from. How could a ROM single out a specific message from a specific carrier? I'm not saying it's possible but it seems like this is a system issue on Pageplus side.
Thanks for the suggestions. It helps validate the steps I've taken and my thought process to solve it.
Well, I spent about 2hrs on the phone between Pageplus and Verizon tech support. Each blamed the other for the issue but ultimately Verizon is looking into it. Made to Level 3 support for whatever that is worth. Supposed to get a call back after they pour thru whatever they have to look thru. We'll see. They all agree that if the phone can receive EMS texts (Verizons extended text message protocol), the phone itself can't distinguish between carriers. The settings for each are the same. Since Pageplus and Verizon use the same system/network, it SHOULD work and can't really be my device. It's something on one of their networks.
Oh... and nobody has ever heard of something like this ever happening....which gives me great confidence that it will get resolved... LOL
Latest... tech support has been less than helpful... SURPRISE! LOL
They said that my phone is rejecting the messages but can't explain how Verizon Extended messages get thru but not Pageplus...which uses the exact same system. Not sure what else to do than maybe try a different ROM to see if it really is Geewiz or not...or maybe swap a device on the account too.
Creepingdeath2 said:
Latest... tech support has been less than helpful... SURPRISE! LOL
They said that my phone is rejecting the messages but can't explain how Verizon Extended messages get thru but not Pageplus...which uses the exact same system. Not sure what else to do than maybe try a different ROM to see if it really is Geewiz or not...or maybe swap a device on the account too.
Click to expand...
Click to collapse
I would definitely try other roms... Not surprised about Verizon support lol...