Related
Background: I've flashed with DCD's 3.0.4 rom, Verizon XV6800. ArcSoft MMS 5.0.31.11 running.
Question: How can you tell on this if an SMS text you send is read by the recipient? Honestly, I couldn't even figure that out when the phone was stock. I know on this version of ArcSoft MMS there's actually a checkbox for delivery and read reports in the MMS Options...but I only get a delivery report when sending an MMS (not a SMS message) and even THEN I can't tell when it has been read.
Is it just not possible? Older phones show a little D or a checkmark by the message when it's read...how about our flashier PPC's? Anyone know?
Older phones show a little D or a checkmark by the message when it's read...how about our flashier PPC's? Anyone know?
Click to expand...
Click to collapse
The D or checkmark does not indicate if the message has been read, rather it indicates if the message was received by the recipient's handset. For example, if the recipient had their phone off, the checkmark would not appear until they turned it on and the message was delivered to their phone.
gcincotta said:
The D or checkmark does not indicate if the message has been read, rather it indicates if the message was received by the recipient's handset. For example, if the recipient had their phone off, the checkmark would not appear until they turned it on and the message was delivered to their phone.
Click to expand...
Click to collapse
Any way to get that? or to check somewhere and see if the message has been delivered?
Any way to get that? or to check somewhere and see if the message has been delivered?
Click to expand...
Click to collapse
Yes there is a way, but there are cons. It either clutters your inbox, or you are forced to delete a message everytime you send one.
Navigate to HKCU\Software\Microsoft\Inbox\Settings and change DisableSMSDeliveryReceipt to 0 and change SMSDeliveryNotify to 1 and soft reset.
Give it a try, if it annoys you, to go back to normal, just flip flop them.
gcincotta said:
Yes there is a way, but there are cons. It either clutters your inbox, or you are forced to delete a message everytime you send one.
Navigate to HKCU\Software\Microsoft\Inbox\Settings and change DisableSMSDeliveryReceipt to 0 and change SMSDeliveryNotify to 1 and soft reset.
Give it a try, if it annoys you, to go back to normal, just flip flop them.
Click to expand...
Click to collapse
if youve got threaded sms, woulndt it store it all on one thread?
I dont actually know how or what it does, but just a thought...
thanks, will give it a try though.
gcincotta said:
The D or checkmark does not indicate if the message has been read, rather it indicates if the message was received by the recipient's handset. For example, if the recipient had their phone off, the checkmark would not appear until they turned it on and the message was delivered to their phone.
Click to expand...
Click to collapse
I was going by a friend who has Verizon and a Motorola phone and he claims that when his texts are read by recipients that it places a checkmark on his phone. Your point makes sense though.
Back to the original question however...what about on our XV6800's? Is there any way to tell when an SMS is read?
gcincotta said:
The D or checkmark does not indicate if the message has been read, rather it indicates if the message was received by the recipient's handset. For example, if the recipient had their phone off, the checkmark would not appear until they turned it on and the message was delivered to their phone.
Click to expand...
Click to collapse
Actually most phones have a delivered and a read notification. like on my girlfriends u740 it'll have the delivered time and then the read time below it. I used to have a blackberry and it would put a check if it was delivered and a check+D if it was read. I'd love to have this feature but i don't think anyone has found a workaround yet
Actually most phones have a delivered and a read notification. like on my girlfriends u740 it'll have the delivered time and then the read time below it. I used to have a blackberry and it would put a check if it was delivered and a check+D if it was read. I'd love to have this feature but i don't think anyone has found a workaround yet
Click to expand...
Click to collapse
Again, these times are NOT when the person actually reads the message. They lead you to believe that that's the case when it is not. In the case of your friend's phone, the delivered time is actually the time that the message was relayed from the network to the recipient, and the read time is the time when the handset actually receives the message. The message could sit in the recipient's Inbox for 3 weeks unread and you would never know the difference. Nevertheless, this feature does not exist on windows mobile devices and the only workaround is getting a message from System Administrator telling you the message was sent successful every time you send one. Messages from System Administrator are NOT threaded.
Example: I turn notify on and send a message but I don't have service. The message looks like it goes through on my end, but until I receive the System Administrator notification, it technically hasn't been received yet. Like I said, this clutters the Inbox with all those messages as they are not threaded, or you can delete the notification after every time you send a message. This is the only way to achieve something like this.
but even if it is succesfully sent, does that indicate receipt of the message? do you get notification when u have succesfully sent the message, even if the recipient has their phone off?
gcincotta said:
Again, these times are NOT when the person actually reads the message. They lead you to believe that that's the case when it is not. In the case of your friend's phone, the delivered time is actually the time that the message was relayed from the network to the recipient, and the read time is the time when the handset actually receives the message. The message could sit in the recipient's Inbox for 3 weeks unread and you would never know the difference.
Click to expand...
Click to collapse
So I tested this and on her u740 she sent me a message and i received it like 10 secs later and it showed delivered at that time. I waited about an hour and opened the message(even though I could read it when it came through) and closed out of my texts which got rid of the notification and it added delivered 10 mins later.
I'm pretty sure this is only a verizon thing and almost every verizon non windows phone is capable of this feature. Also verizon only charges for text messages that are read from the handset if you don't have unlimited texts which is prob why they have this feature.
Maybe it's not a feature available on our phones but It is possible to have.
So I tested this and on her u740 she sent me a message and i received it like 10 secs later and it showed delivered at that time. I waited about an hour and opened the message(even though I could read it when it came through) and closed out of my texts which got rid of the notification and it added delivered 10 mins later.
I'm pretty sure this is only a verizon thing and almost every verizon non windows phone is capable of this feature. Also verizon only charges for text messages that are read from the handset if you don't have unlimited texts which is prob why they have this feature.
Maybe it's not a feature available on our phones but It is possible to have.
Click to expand...
Click to collapse
Ok well I thought we were talking about straight SMS with no EMS application extension (which is the feature you're referring to).
I'll explain a little about the SMS system.
You get the D notification when it is a subscriber within your network (i.e. Verizon to Verizon as you've been testing), it has to do with a specific signature flag that is triggered from within that network and does not cross networks.
The check mark means the cell tower has received and cached the message on the tower server for queuing to be transmitted. Once the SMS message has left queuing and goes to transit, which means it has left the tower's local server and has been sent to the carrier message manager (or out to a different network), then the D appears saying the message has been delivered. This really means "message has been delivered to the network" not necessarily to the recipient's device. Most of the time it happens so fast it usually hits the person's handset roughly within 3-5 seconds which coincidentally is the same time the queue server will send you the D flag to notify you it's been delivered. It's a pretty accurate indicator, but is completely unrelated. This D does not indicate when the message was read. In some instances, the person's handset can be off and you'll still get the D.
The times and updated times you're seeing on the u740 is part of the Enhanced Messaging Service, or EMS, application extension to SMS. The u740 is an EMS capable device, which is why you're seeing these updates. Windows Mobile devices are NOT EMS capable, which is why you'll never see this feature, nor will you see any workaround or fix. The only way you'll be able to get this feature is if you ditch your Titan for an EMS capable non smart phone, or if in the future they decide to make WM EMS capable.
Hopefully this clears up the confusion a little.
GC
gcincotta said:
Ok well I thought we were talking about straight SMS with no EMS application extension (which is the feature you're referring to).
I'll explain a little about the SMS system.
You get the D notification when it is a subscriber within your network (i.e. Verizon to Verizon as you've been testing), it has to do with a specific signature flag that is triggered from within that network and does not cross networks.
The check mark means the cell tower has received and cached the message on the tower server for queuing to be transmitted. Once the SMS message has left queuing and goes to transit, which means it has left the tower's local server and has been sent to the carrier message manager (or out to a different network), then the D appears saying the message has been delivered. This really means "message has been delivered to the network" not necessarily to the recipient's device. Most of the time it happens so fast it usually hits the person's handset roughly within 3-5 seconds which coincidentally is the same time the queue server will send you the D flag to notify you it's been delivered. It's a pretty accurate indicator, but is completely unrelated. This D does not indicate when the message was read. In some instances, the person's handset can be off and you'll still get the D.
The times and updated times you're seeing on the u740 is part of the Enhanced Messaging Service, or EMS, application extension to SMS. The u740 is an EMS capable device, which is why you're seeing these updates. Windows Mobile devices are NOT EMS capable, which is why you'll never see this feature, nor will you see any workaround or fix. The only way you'll be able to get this feature is if you ditch your Titan for an EMS capable non smart phone, or if in the future they decide to make WM EMS capable.
Hopefully this clears up the confusion a little.
GC
Click to expand...
Click to collapse
Ok, so in essence you are saying that the ability to know when an SMS message is read does not exist, even with EMS capabilities. Why, on Windows Mobile phones, does the ArcSoft MMS Composer give a checkbox to Allow Read Reports for MMS Messages as if that is a feature that works, yet I haven't even seen that work for MMS messages either? Is that just because Verizon's network doesn't support read reports/receipts? I would think that there would be a way of knowing when a message is read (much like read receipts in Outlook, although the recipient has the option to not send the read receipt, but that's neither here nor there).
EMS phones have read reports, but apparently we don't have an EMS phone
EMS phones have read reports, but apparently we don't have an EMS phone
Click to expand...
Click to collapse
You are correct.
I was doing a little research on the capabilities of EMS and MMS, and came across something interesting in the wikipedia listing for EMS:
EMS is an intermediate technology, between SMS and MMS, providing some of the features of MMS. EMS is a technology that is designed to work with existing networks, but may ultimately be made obsolete by MMS.
What's perplexing there is that we know EMS is an extension to SMS, and it is saying that EMS is intermediate to MMS...so why doesn't MMS include all SMS and EMS capabilities?
KingofX said:
What's perplexing there is that we know EMS is an extension to SMS, and it is saying that EMS is intermediate to MMS...so why doesn't MMS include all SMS and EMS capabilities?
Click to expand...
Click to collapse
it does, but the carrier must choose to configure the mms client and mms server to support those capabilities.
gc14 said:
... Windows Mobile devices are NOT EMS capable, which is why you'll never see this feature, nor will you see any workaround or fix. The only way you'll be able to get this feature is if you ditch your Titan for an EMS capable non smart phone, or if in the future they decide to make WM EMS capable.
Hopefully this clears up the confusion a little.
GC
Click to expand...
Click to collapse
apparently at some point MS and VZ planned on ems in wm- the press releases from the 6700 mention ems:
http://news.vzw.com/news/2006/01/pr2006-01-04b.html
but a bit more current:
http://msdn.microsoft.com/en-us/library/aa919404.aspx
seems wm 6 has a regedit to allow ems.
anyone made progress getting ems to work with wm6 (or 6.1) on vz?
I'm using the TG01 and I keep getting a false positive voicemail indicator on the Titanium Home Screen. Calling and leaving a voicemail and deleting it does not work, calling ATT to have my voicemail reset does not correct the problem.
When you call into the VM ATT service from the phone to check your messages, it sends a VM control SMS to the phone, indicating that it is not being properly processed. Has anyone else seen this, or know of a problem besides a master reset - which is annoying b.c. this is the second time this has occured in three weeks.
Thanks!
Search for the tool HushSMS. I Had the same problem and did resolve it with HushSMS.
Isn't this the opposite of what we want to occur though? We are trying to hide network messages from the device not from those we send to.
No, with HushSMS it's possible to send a message to your own phone, that changes the SIM Setting and deletes the voicemails that are not there but which WM shows you.
Thanks that worked!
You're welcome
Although...on second thought - this makes it dissapear but does not prevent it from occuring again - was this the same result for you?
No, it occured never again.
Did it occur again at your phone?
Yeah it occurs again everytime I get a VM, bummer. What type of SMS did you send with Hush SMS?
Is there a way to officially set up ATT VM on an unlocked phone that I'm not following correctly?
The rom update Toshiba released recently did not correct this either as I had hoped. Any thoughts as to why these control SMS and MWI don't process correctly?
Removing the indicator with a Ping0 message in HushSMS is a workaround to parse the indicator but does not prevent it from occuring agian.
Anyone know how to fix this? Getting really irritating honestly.
Same here...
I am on Virgin mobile in the UK and I have the same problem, I got a voicemail this morning and I have deleted the voicemail but it still shows on my phone.
I have rebooted and its still the same
I have to use HUSH SMS to clear my voicemail indicator.
For me it's actually a problem on my sim card. After a flash there is this residual text message that says i have a voicemail. It's wierd.
Anyway, it's a MWI Disable command with HUSH SMS
Click Send MWI, Voice, Deactivate.
Also, you can mess with your windows mobile enabled friends by sending an enable
Check this out http://http://forum.xda-developers.com/showpost.php?p=1163312&postcount=1
I am getting SMS Error - Cause Code Addr.Vcnt.,0
I have only experienced this on sending International txt messages but when you send a long txt msg your phone normally splits the txt messages into the allowed txt size for example you can write up to 160 per message and if you go over your phone splits it into seperate txt messages instead of 1 but I tried to send one long message internationally and got the error code instead of splitting the message.
I have even tried doing this on shorter messages right over 160 like 161 it still gives me the error code. This is the first phone I experienced this on other phones it would split the message.
Has anyone experienced this or is there a fix, I wonder if sprint is aware of the problem.
Ok I called sprint and they Identified the error code right away. Stating that error is when a network on the other end does not accept msg over a certain amount of characters.
So the cause of this is motorola not Sprint, they stated they intentionally did not put in the software for splitting the msgs automatically when going over a certain amount of characters it keeps it as one big message.
The issue has been reported to them by various customers already and have gotten no response back from motorola.
Hopefully we can get an update on this soon
Try the handcent app. It will allow you to split messages. I'm using it on the photon now and it works great. Has a lot of customizable features, too. And, best of all, FREE!
kimmied2000 said:
Try the handcent app. It will allow you to split messages. I'm using it on the photon now and it works great. Has a lot of customizable features, too. And, best of all, FREE!
Click to expand...
Click to collapse
Thanks I will give it a try , but still would be nice if Motorola would change this in their first update from sprint.
sanfranx415 said:
Ok I called sprint and they Identified the error code right away. Stating that error is when a network on the other end does not accept msg over a certain amount of characters.
So the cause of this is motorola not Sprint, they stated they intentionally did not put in the software for splitting the msgs automatically when going over a certain amount of characters it keeps it as one big message.
The issue has been reported to them by various customers already and have gotten no response back from motorola.
Hopefully we can get an update on this soon
Click to expand...
Click to collapse
It is sprint. I will be on the phone and sms someone and get this error back. I am literally texting only hi or hey or test while I am on the phone and it is getting a failed error code 0.
I'm having trouble with my phone's messaging. I can send texts fine, but I can't send any group messages or MMS messages. I've tried unrooting, updating to the newest OTA update, using a third party texting app, and replacing the SIM card. Nothing works. I can't send or receive group messages or attachments. I tried Go SMS Pro, and when I tried to send group messages, it failed, then sent the message individually to each person. When I tried sending a picture, it said the service was not activated on the network.
This got me thinking it might be something with our texting plan, but everyone else in my family can send and receive group messages and attachments without problems. So it's a problem with my phone only. Does anyone have suggestions?
M0rtiferrimus said:
I'm having trouble with my phone's messaging. I can send texts fine, but I can't send any group messages or MMS messages. I've tried unrooting, updating to the newest OTA update, using a third party texting app, and replacing the SIM card. Nothing works. I can't send or receive group messages or attachments. I tried Go SMS Pro, and when I tried to send group messages, it failed, then sent the message individually to each person. When I tried sending a picture, it said the service was not activated on the network.
This got me thinking it might be something with our texting plan, but everyone else in my family can send and receive group messages and attachments without problems. So it's a problem with my phone only. Does anyone have suggestions?
Click to expand...
Click to collapse
might try going into your setting and unchecking fastboot .. read somewhere that worked for others ... good luck
Nope, that didn't work, either before or after a reboot. Any other suggestions?
Had a similar issue. I don't know if its because I'm still locked and unrooted but I recieved an error code when I would try to send messages. I actually had to get o the phone with Big Red and they had reconnect me to another network connection of some sorts. Weird.
Sent from my HTC6435LVW using xda app-developers app
Sorry, what do you mean you had to "get o the phone with Big Red"? You had to carry it back to Verizon?
M0rtiferrimus said:
Sorry, what do you mean you had to "get o the phone with Big Red"? You had to carry it back to Verizon?
Click to expand...
Click to collapse
He missed a 'n', he got on the phone with big red. Aka he called Verizon.
Sent from my HTC6435LVW using xda app-developers app
This has been solved. I switched my number in January, and the service had been disabled then. I was able to get into a live chat with a vzw customer support guy, and he was helpful enough not only to fix MMS, but also group messaging on my phone. It took a couple of hours after trying in vain to put a password in over the phone, but contacting Verizon is the only way to fix this. If you have rooted your phone (as I had previously), and you still have that ugly "tampered" or "relocked" message at the top of the bootloader, Verizon's live chat system is probably your best bet. Even if you haven't rooted your phone, live chat may be faster. You can skip the "reboot, reset, ask other employees for help" routine you'll probably go through if you go to a physical location.
I think I have the same problem too..
When I'm sending a group message .. one of or two of the messages wont send
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...