[Q] SMS Random Selection Bug - Nexus One General

I've been reading about this bug for awhile now and it finally hit me. What happens is if contact A sends you a txt message and you respond. The message thread will show that your response went to contact A, but the reality is that A may not have received the response, however C,D,E,F, Z,Y and X did! It seems to be totally random, will happen regardless of the SMS app or ROM you use and can be quite dangerous. This bug renders my N1 virtually useless. Anyone else experience this or has an update on the fix for this dangerous bug?
I recommend anyone with an Android phone to be use extreme caution when sending txts or mms messages as you never know who may actually get it

Have read about it, but it's never happened to me.

Can you reproduce the bug reliably?
Can you dump the logs (/proc/kmsg and logcat, or bugreport) immediately after it happens?
Any pattern connecting recipient A and the rest?

Nightmare!
Sent from my Nexus One using XDA App

How come that not even one person from those reporting having "this bug", wants to help find out, what it is? Very interesting.

I have found that using handcent resolves this problem for me.
Sent from my Nexus One using XDA App

My wife have experienced the problem twice with Galaxy S, I haven't have similar troubles with my N1, although every now and then it takes time for some messages to go through. That is probably due the carrier, not the device.
Sent from my Nexus One using XDA App

The only trouble with messaging i have is that sometimes when i select to open the thread at the top of the list, the one at the very bottom of the screen opens. Frustrating!!!

cymru said:
The only trouble with messaging i have is that sometimes when i select to open the thread at the top of the list, the one at the very bottom of the screen opens. Frustrating!!!
Click to expand...
Click to collapse
I have this too in a pre 6.1 nightly...
But it's not the first time i hear the bug that SMS are sent to everyone, so it definitely exist
Sent from my Nexus One using XDA App

I saw the "reports" on the net popping up once in a huge while, but I never saw anyone that would report this bug and actually try to solve it, or assist anyone in solving it. Doesn't look like a normal bug report to me, and doesn't look like there is a bug. I know over 15 people with all kinds of Android, at least 6 with Nexus, and it never happened to anyone. The "bug" looks very fishy.

Jack_R1 said:
I saw the "reports" on the net popping up once in a huge while, but I never saw anyone that would report this bug and actually try to solve it, or assist anyone in solving it. Doesn't look like a normal bug report to me, and doesn't look like there is a bug. I know over 15 people with all kinds of Android, at least 6 with Nexus, and it never happened to anyone. The "bug" looks very fishy.
Click to expand...
Click to collapse
I can assure it is a bug and a major one. It is well documented if you google it. It appears to be across many different hardware platforms and therefore is most likely a source code issue written incorrectly in the android OS. And just because the 15 people you know aren't having the issue does not mean the rest of the world isn't. This is my 3rd android phone and this is the only one that does it and from I've been reading there are many others who are also having this random issue...I assure you, this isn't something that someone can do by mistake or accident...

In that case, if it's so well documented, how come that nobody has ever assisted anyone else in debugging it, yourself included?

It's happened to me.
I receive certain friend's facebook updates as sms. One time I got the facebook sms. I closed it then replied to another friend's sms. Guess what happened.... what I sent to my friend got sent as a comment to my friend's facebook status.
Looking back at the sms log, I definately wrote my reply to my friend, not the facebook sms, but somehow it was replied to the facebook sms.
This bug has been around since Android existed.
There's really no way to debug this I don't think, unless you only have a few contacts that will text u if you write something weird... cuz having a phone full if phone numbers, your text can be sent to any number, even non mobile phones, you wont know since you thought u texted the right person.
Sent from my Nexus One

There's a ton of ways to debug everything, including even specifically modified SMS app for dumping debug data - it's an open OS, yes? If I got some beta application versions for debugging from app devs to test things, I'm sure Google wouldn't do less to debug it.
For starters, the next SMS I'll check the records in kernel log and see if there's any useful data to start from there.

Jack_R1 said:
In that case, if it's so well documented, how come that nobody has ever assisted anyone else in debugging it, yourself included?
Click to expand...
Click to collapse
Well I think you bring up two entirely non-related issues... First, if you google it, you will find a vast amount of people all having that same issue, which in my mind establishes the "well documented" part of my statement. Secondly, as far as me or anyone else participating in debugging, I would love to, but it's a little out of my sphere of knowledge. If you could give me a little insight into what needs to be done, I would be more than happy to do what I can to help solve the problem. This $500 phone is totally useless to me if I can't be certain who will be receiving my txt messages. Mainly, I've been waiting and watching in the hopes that google would get involved and resolve this issue without my having to get involved. It would appear that this goes back a considerable amount of time.
Can you list out a step by step process to go about this so that all who are having this issue can also participate? What should be my next step

To even try to start with debug, you have to have a rooted phone.
The useful place to look at would be /proc/kmsg. The question is - how much data it contains after sending sms. I didn't try to dump it after SMSing yet, didn't have time for it. I'll try to find time over the weekend.
If it won't contain enough data, modification in SMS application is needed, to dump the data there to help with debug. This is much harder for me, because I'm not an app dev, and I'll have a hard time trying to find and understand the relevant data structures to dump there. Basically, when you hit "reply", some kind of indicator of current SMS thread needs to be dumped, and everything else that might result in wrong number being selected - all the chain that determines the number that the SMS goes to. Then, once the SMS was sent to wrong recipient, the info needs to be dumped and checked.
The later part is "slightly" beyond my skills. It requires knowledge of SMS application and its data structures.
It obviously happens only to those that have their Facebook contacts integrated, so the mechanisms that take care of joined contacts might be something to look at.

It never happened to me, and I've sent 12000 sms from my Nexus. Try using Handcent until this is officially fixed. Handcent is free and many people say it's not affected by the bug.

Jack_R1 said:
To even try to start with debug, you have to have a rooted phone.
The useful place to look at would be /proc/kmsg. The question is - how much data it contains after sending sms. I didn't try to dump it after SMSing yet, didn't have time for it. I'll try to find time over the weekend.
If it won't contain enough data, modification in SMS application is needed, to dump the data there to help with debug. This is much harder for me, because I'm not an app dev, and I'll have a hard time trying to find and understand the relevant data structures to dump there. Basically, when you hit "reply", some kind of indicator of current SMS thread needs to be dumped, and everything else that might result in wrong number being selected - all the chain that determines the number that the SMS goes to. Then, once the SMS was sent to wrong recipient, the info needs to be dumped and checked.
The later part is "slightly" beyond my skills. It requires knowledge of SMS application and its data structures.
It obviously happens only to those that have their Facebook contacts integrated, so the mechanisms that take care of joined contacts might be something to look at.
Click to expand...
Click to collapse
This is why I haven't, as you say, participate in resolving the issue...the level of of debugging required to get to the source of the problem is deeper than a non-developer like myself can go. And for the record, this is NOT related to the facebook app in anyway as I do not even have that app installed. This is 100% an Android code issue...

Are all your contacts Gmail-synced contacts?
Does it happen frequently enough to try to debug?

This is what happens with my N1:
I get a new text message, alerted in my notification bar
Rather than open it from the notification bar, I open the messaging app and tap the first message (just a habit, I guess)
The ninth message opens instead of the first one​
I'm not sure if this happens every single time, but it does happen frequently.
I'm wondering if it might be a bug in CyanogenMod instead, I've only started noticing it recently.
PS: I do not have a Facebook account nor any accounts synced with it. The only contacts I sync are my Google contacts.

Related

Hero and SMS

I've had two episodes where I sent a SMS to my dad, and the SMS shows up in the list of messages sendt to my sister -> My sister got the SMS.
Another example: I sent a SMS to my friend, and it shows up in the list of messages to my uncle. My friend answered the message.
Anyone else experienced something similar?
Is there a fix?
Can't say that I've ever had that happened unless I mistakeningly sent it to the wrong person. Human error rather than device error.
I'm sure you uncle must have enjoyed the message.
Have you thought that maybe your numbers are messed up?? Or maybe all your contacts are switching with each other to mess you up.
Yep, chedked the numbers. This is definately a device error.
I had this self same problem yesterday! I thought it was me.
I sent an SMS to a friend called 'Ross', it showed up as Ross in the 'To' field but when I went into my sent messages it had gone to a friend called Robert. This occurred twice - but hasn't with subsequent messages.
Weirdest thing isn't it?
Now, how do we go about fixing this?
z0nic said:
Weirdest thing isn't it?
Now, how do we go about fixing this?
Click to expand...
Click to collapse
You need to email HTC support like with any issues / bugs you find or they will never know about them. Then hope they bring out a software fix. If we don't tell them, they will think its only a handful of people and not bother to do anything.
Also make sure your contacts' numbers are correct.
I have had the same problem, but the message hasn't actually been sent to the wrong person. It seems that it gets confused about who the person is. In my example the person I texted began with Dan and the second Theresa, so not next to each other in contacts. Theresa didn't say she had received something from me.
Same problem here
I did report this to HTC along with not getting sms and getting multiple of the same sms. All they suggested I do is a hard reset (already done) which did not change anything. Not very happy with them they didn't day it was a software fault or a fix was coming
They gave me the same response (although I only reported not getting all messages). If the hard reset didn't work they said to get the phone replaced. Its definitely a software fault so I am not replacing it, seeing as others have had issues with dead pixels etc...
It's only a display problem, you just close messages then reopen it, or go to the messages tab of the contact you sent the text to then click on the message and it'll correct the names.
I've had a similar issue once! Strange experience: I actually thought I had sent all kinds of SMS-es to the wrong person ;-)
In my case the names changed back automatically after about 30 bewildering seconds. Never had an issue since.
I have uninstalled Handcent SMS that caused several conflicts on my Hero, inclusing SMS-es not arriving at all. I might have had the 'wrong name' issue when I had Hancent installed. Don't really remember.

[Android] SMS from Anonymous sender (AIRAVE PROBLEM)

hey guys, with every build of android i've tried with the vogue, sometimes an sms comes in with Anonymous as the sender's name/number. There is no sender info there at all, so I just have to guess who sent it. Has anyone else encountered this problem? Thanks so much in advance
EDIT: We(Sjs01) have narrowed it down and discovered that it is a problem when using an Airave. If we turn off the airave or leave it's coverage messages come in with the contact name like normal. Great catch sjs01! So, we are hoping a dev could look at this to see if there may be a fix for it. Thanks!
Leukay said:
hey guys, with every build of android i've tried with the vogue, sometimes an sms comes in with Anonymous as the sender's name/number. There is no sender info there at all, so I just have to guess who sent it. Has anyone else encountered this problem? Thanks so much in advance
Click to expand...
Click to collapse
I've tried nearly every build, and I have never once had this error. I send around 5000 txts a month.
scizzle said:
I've tried nearly every build, and I have never once had this error. I send around 5000 txts a month.
Click to expand...
Click to collapse
Yeah, it's really odd, I can't find anyone with the same issue at all
EDIT: It has become more and more frequent. About 1 in every 15 texts actually display the sender's name/number. Hmmmmmm...
What is your carrier? I have mine on sprint with 1.5 standard system from the vogue-android proj page.
I seem to have hit or miss text message receiving and havent pinpointed the issue with sending SMS to a "CONTACTS" cell number. Basically I cant reply to a text or 'send' to a contact's SMS/mobile number, They never get it. If i send it using raw digits they do.
Was kind of curious about your experience there.
kkruse said:
What is your carrier? I have mine on sprint with 1.5 standard system from the vogue-android proj page.
I seem to have hit or miss text message receiving and havent pinpointed the issue with sending SMS to a "CONTACTS" cell number. Basically I cant reply to a text or 'send' to a contact's SMS/mobile number, They never get it. If i send it using raw digits they do.
Was kind of curious about your experience there.
Click to expand...
Click to collapse
I'm on sprint, "dzo booting" the donut build here: http://forum.xda-developers.com/showthread.php?t=591104 But I've had this problem with every build I try, even when running from the SD. And regarding your issue, I can send to a contact name and they receive it every time, but it's when they reply to me, it comes in as "Anonymous" and I cant reply to it. Also, I just did a test, and even when the number isn't in my contacts, it comes up as Anonymous.
Leukay said:
I'm on sprint, "dzo booting" the donut build here: http://forum.xda-developers.com/showthread.php?t=591104 But I've had this problem with every build I try, even when running from the SD. And regarding your issue, I can send to a contact name and they receive it every time, but it's when they reply to me, it comes in as "Anonymous" and I cant reply to it. Also, I just did a test, and even when the number isn't in my contacts, it comes up as Anonymous.
Click to expand...
Click to collapse
How do you have the numbers saved in your contact list? I had issues before with sending SMS and found that I needed to remove the leading +1 from all the numbers I had stored. One I had them all setup as (area-code) XXX-XXXX then my SMS was working great again.
stickus said:
How do you have the numbers saved in your contact list? I had issues before with sending SMS and found that I needed to remove the leading +1 from all the numbers I had stored. One I had them all setup as (area-code) XXX-XXXX then my SMS was working great again.
Click to expand...
Click to collapse
Yeah, I heard about that, so I tried it, but none of the numbers have the 1 at the beginning. I deleted the contact, re-entered them, everything. I had to flash back to WM (poo) because it got to the point that every SMS that I received was from "Anonymous." Ugh I can't be the only person that's ever had this problem can I? lol
i've read just about every thread on android, and don't recall seeing this problem. i used to have a problem with missing incoming sms (people would send to me, and I would never receive them), but it seems to have fixed itself - coincidentally around the time I stopped using compcache, don't know if it had anything to do with it.
sorry, i've got nothing for you. i'm sure you have already tried deleting all files from your SD card and putting fresh stuff.
I am also having this problem, the text almost never comes in the persons name, I have tried the fixes in this thread with no success.
Sjs01 said:
I am also having this problem, the text almost never comes in the persons name, I have tried the fixes in this thread with no success.
Click to expand...
Click to collapse
I'm not the only one!!! Yess!!!
Now, how to fix it. Since nobody seems to even know about this problem, let alone how to fix it, I'm just going to ask some questions.
What COULD be causing it. It can't be the system, because it happens with every build I try.
Sjs01 said:
I am also having this problem, the text almost never comes in the persons name, I have tried the fixes in this thread with no success.
Click to expand...
Click to collapse
Interesting issue,
If you guys could do this that would be great.
connect your phone to your linux (or windows if you're not using the latest nand boot files)
at shell do ./adb logcat -b radio > radiolog.txt
have someone send you a txt who regularly comes up as unknown
ctrl c in your terminal window to end the logcat, and post the radiolog.txt,
We can look over your log and see what may be causing it, if it's RIL related you will have to wait for vilord to impliment a needed change, however because so many people aren't having the issue it may take a while.
Hope this helps
I'm using the same version (http://forum.xda-developers.com/showthread.php?t=591104), booting from nand, and having this exact issue.
I'd try to use adb to see the log but there is an issue using windows adb with nand flashed android.
Im having trouble trying to create the logcat, but I've made an interesting discovery. I tried out HeroZenMagic--102309--system.sqsh rom the host site where they are keeping the old hero builds, and with that build pretty much every sms came through with the contact name. That got me thinking, all of the older builds seem to work just fine, its just the newer ones. And the problem with that is, they are much less advanced and more sluggish. Maybe this information can help? The build can be downloaded here: http://www.mediafire.com/?sharekey=aa29b5ef55091cf1c79b87b207592a1c3574eefa2a593379ce018c8114394287 Try it out and see if your results are the same, and if so, maybe we can figure something out!
mssmison said:
Interesting issue,
If you guys could do this that would be great.
connect your phone to your linux (or windows if you're not using the latest nand boot files)
at shell do ./adb logcat -b radio > radiolog.txt
have someone send you a txt who regularly comes up as unknown
ctrl c in your terminal window to end the logcat, and post the radiolog.txt,
We can look over your log and see what may be causing it, if it's RIL related you will have to wait for vilord to impliment a needed change, however because so many people aren't having the issue it may take a while.
Hope this helps
Click to expand...
Click to collapse
I'm not actually booting from nand, I'm just have been using haret to boot up android. I was also having some trouble creating a logcat but I think I managed to get one that I think has what you need. If something is wrong with it let me know and I'll try to get a better one. I would try to make it write a radiolog.txt but it wouldn't work. So I ended up just copying what was in cmd and pasting it into a notepad and just saving it.
Leukay said:
Im having trouble trying to create the logcat, but I've made an interesting discovery. I tried out HeroZenMagic--102309--system.sqsh rom the host site where they are keeping the old hero builds, and with that build pretty much every sms came through with the contact name. That got me thinking, all of the older builds seem to work just fine, its just the newer ones. And the problem with that is, they are much less advanced and more sluggish. Maybe this information can help? The build can be downloaded here: http://www.mediafire.com/?sharekey=aa29b5ef55091cf1c79b87b207592a1c3574eefa2a593379ce018c8114394287 Try it out and see if your results are the same, and if so, maybe we can figure something out!
Click to expand...
Click to collapse
I'll have to try this and let you know, but I can't tonight. When I used to use the older builds normally my texts would come in fine, but texts from other sprint customers would almost always be anonymous, but now it's with almost everyone.
Leukay said:
I'm on sprint, "dzo booting" the donut build here: http://forum.xda-developers.com/showthread.php?t=591104 But I've had this problem with every build I try, even when running from the SD. And regarding your issue, I can send to a contact name and they receive it every time, but it's when they reply to me, it comes in as "Anonymous" and I cant reply to it. Also, I just did a test, and even when the number isn't in my contacts, it comes up as Anonymous.
Click to expand...
Click to collapse
I think I may have figured out the issue (at least my issue), Leukay, do you by chance have an Airwave? I am on Sprint and had realized that, for the most part, whenever I would go out of my house the texts would start coming in with the actual name/number, but when I would go back into my house my texts started coming from "Anonymous" again. So tonight I went down and unplugged my Airwave, sure enough the texts started coming in as the actual name and number again. So if you do have an Airwave you should probably try to unplug it and see if the texts start coming from the right numbers.
Sjs01 said:
I think I may have figured out the issue (at least my issue), Leukay, do you by chance have an Airwave? I am on Sprint and had realized that, for the most part, whenever I would go out of my house the texts would start coming in with the actual name/number, but when I would go back into my house my texts started coming from "Anonymous" again. So tonight I went down and unplugged my Airwave, sure enough the texts started coming in as the actual name and number again. So if you do have an Airwave you should probably try to unplug it and see if the texts start coming from the right numbers.
Click to expand...
Click to collapse
As a matter of fact, I do have an Airave. I try that today and post later today! thanks for the tip
EDIT: That completely gets rid of the problem! The only problem is I need the airave to make calls in my house. Hopefully the devs can figure out why the airave produces this problem
I have an Airwave too. I guess that's definitely the problem. Can't disconnect it though cause I won't have any service in my house.
Leukay said:
As a matter of fact, I do have an Airave. I try that today and post later today! thanks for the tip
EDIT: That completely gets rid of the problem! The only problem is I need the airave to make calls in my house. Hopefully the devs can figure out why the airave produces this problem
Click to expand...
Click to collapse
I know how you feel if I don't have my airwave I can barely get a signal in my house. I guess we can just hope the devs can fix this. But they're really busy so I'm not expecting it anytime soon.
Do we have a way to force roam in android?

[Q] Issue with txts going to the wrong person magically...?

When you have a text log with the original person? I have noticed it shows up in the notification tray under 1 name and then under the actual msg app its to the right person but it makes me scared at times who the last txt REALLY went too..
In the stock messaging app (all I use) Ill start a txt conversation with person x then down the line it'll send the next to person y... idk if it was a confusion between the linked fbook accounts but it almost got me in trouble so now for safety sake I dont have fbook linked to contacts...
Anyone notice this or is it just me?
Sorry to hear this. If its the same two contacts each time, I'd suspect your two contacts may have automatically linked or merged phone numbers. Inspect each one's details for the other's phone number. For example, I found that two contacts who shared the same email were merged, completely deleting one's name entirely.
I'm using Handcent myself so not sure if this would be related, but I've found that text messages received from one particular number (my bank's alerts) always appear as another contact (a friend) in the initial pop-up alert but then appear correctly in Handcent's actual message threads. I've since swapped and rebuilt the handset to no avail. This issue remains a mystery.
Sent from my SGH-T959 using XDA App
not the same contact. Thats what I originally thought it was something merged weird but its random. so I am not too sure but it makes me whery what I send to certain ppl. For some reason im friends with enemies of the other friend so saying 1 thing starts a fight btwn the 2.. lol I cant win.
same problem, HTC EVO, seems like it goes to a random person, facebook contact or not.
This is a huge problem and is related to the Android platform, not just the Vibrant. You can find more information in the following two links:
1. www.google.com.vn/support/forum/p/android/thread?tid=345259e6d424bad3&hl=en
2. http://code.google.com/p/android/issues/detail?id=9392
The best thinking that we have on the problem so far is that it is in the ComposeMessageActivity.java file. But it would be great to get more eyes looking over the code to try to get this one licked.
Note: A 3rd party app may make the situation better, but will not resolve it. Best solution is that if you receive a text or e-mail message (or anything that plays with the notification bar or takes focus from what you're typing), quit your message and start over.
This scares the hell out of me. Is there any specific instance when this always happens?
Strange, never had this problem and I've been using Android since the G1. There must be something you are doing or a setting you have that specifically triggers it.
There's nothing related to Facebook - I don't have anything linked on my phone. And I never had this issue on my G1, but I also didn't start screwing with the Vibrant until recently, so it's not something I'm "doing" - it's happened within weeks of getting the Vibrant on launch day.
It can be quite scary. Luckily my friends getting msgs meant for my wife hasn't bit me in the ass yet. But if it ever gets mixed up going to a female friend, I could see this not working out in my best interests, ya know?
-bZj
I've had the same problem on my vibrant and my g1. What I've noticed is that if I send a nescafe to person A then receive a message from person B and access that message by using the notification bar and answer person B, the message can go to person A (the last person I sent to.) I've found that if I remember to not use the notification bar and only access messaging by using the icon, I haven't had the problem. Not the best solution but at least it seems to work.
This could be bad
This could be bad especially if you have more than one girlfriend
Omg glad im not the only one. Had to couch it one night cuz of this issue. Now i only text my girl from my phone. Everyone else i text through gv lol.
I use the notification bar all the time and occasionally reply to the weekend person but that's just because I didn't press on the right notification...
yea i had this happen to me as well. luckily or unluckily a txt i was sending to a girl whom i was fooling around with got sent to a girl i had just met 3 days prior. after that needless to say she wouldnt talk to me waa waaa. it was prob a random bug introduced in earlier builds.. say around a month and a half ago. oh yea i had about 12 threads running around 50 a piece.. maybe that had something to do with that and maybe the random stuttering of the vibrant when too many programs are running. Havent had that happen again thankfully but one would have to say.. slow down on the texting sometimes lol
vinnydakid said:
This scares the hell out of me. Is there any specific instance when this always happens?
Click to expand...
Click to collapse
The evidence seems to suggest that the problem is in the ComposeMessageActivity.java file, which means it is not SMS Client related. Said differently, using a 3rd party SMS client might reduce the likelihood of the problem but does not eliminate it.
Now, to answer your question. It seems like the problem happens when multiple threads or events happen when using SMS. For example, it might happen when you are editing a message and when you receive a SMS text message. (It is more likely if you use the notification bar to pull down the message rather than navigating to it in the SMS client.) The good news is that people are trying to reliably reproduce the problem so that we can troubleshoot and fix the problem. (See my earlier post in this thread for a link of those discussions).
kangxi said:
Strange, never had this problem and I've been using Android since the G1. There must be something you are doing or a setting you have that specifically triggers it.
Click to expand...
Click to collapse
Based on the review of the code, one fix seems to have been made to the 2.2 code branch. However, people using 2.2 have indicated that they are still experiencing the problem. The problem is in the library. However, there is a very unique set of circumstances that have to occur before you see the problem. It's quite possible that people who haven't seen this problem yet just use the UI in such a way that the problem doesn't show up.
98classic said:
Omg glad im not the only one. Had to couch it one night cuz of this issue. Now i only text my girl from my phone. Everyone else i text through gv lol.
Click to expand...
Click to collapse
i second that. this glitch can be nasty. hopefully it will be addressed soon. GV for the win.
I have the same issue here. It will show one name but have a conversation for another, or the name and the convo are right, but the picture is wrong.
I think I found a solution to the thing. Been getting it a LOT and pissed me off on more than a single occasion.
So. If you are talking to someone and SUDDENLY receive a text message from that person but when you open it, it changes the name of the contact to someone else or ....I guess everyone who has experienced it KNOWS what it looks like. So when you GET IT, open it, then CLOSE the whole messaging app. Then restart it and it should fix itself and be back to texting the right person. If it doesn't (or if you want to be on the safe side), kill the messaging app with a task killer or task manager and restart it.
This has fixed it recently for me. Had it happen a total of about 15 times, with me finding and using the trick about the latest 5 times and it worked every time.
Note that I AM running Bionix Fusion 1.0 with Voodoo if that makes any bit of a difference.

How does Sprint sync your real voicemail box with Visual Voicemail?

Happily running CM7 with one issue:
If I dial my own number (or longpress "1" in the dialer) to access my real voicemail box, I have many "new" messages.
But I have been receiving, listening to, and deleting these same messages using the Sprint Visual Voicemail program installed as per the usual method (see http://forum.xda-developers.com/showpost.php?p=12219741&postcount=2 under "visual voicemail" for the one-sentence version).
Why are the two voicemail "boxes" not in sync?
I'm pretty convinced this is a bug-not-a-feature because it gives two different versions of the "truth" to anyone who uses both methods to check VM (because, say, your bluetooth headset doesn't allow you to hear locally-stored VVM audio files.. but that's another topic..). I'm not even sure what happens when this goes on for a month or two- do callers hear some kind of "mailbox full" announcement? Do the oldest messages just go away once they reach a certain age?
I have returned to a sense-based ROM and tried to "update my profile" and PRL, I have sent a VVM to [email protected], and I have gotten the little "toast" that says I have been provisioned successfully. But no sync. I have rebooted. I have waited overnight. I have turned off wi-fi to force 3G communication with Sprint. I have scoured the internet for these and other recommendations. Still no sync. The only thing I haven't done is called Sprint and asked them to get involved (which of course is a bit of a last resort considering we are talking about a rooted phone here).
So I'm asking for help from a) anyone who has experienced this and solved it and/or b) anyone who can shed some light on how Sprint VVM synchronization works.
Thanks in advance...
PS- I already know I can always "solve" my Sprint VVM issues by switching to Google Voice: I'm sure GV is great, but my question is not about GV. I'm just looking for basic information on the signalling method Sprint uses to synchronize your VVM with the cloud. Thanks!
I've been wondering and experiencing the same exact stuff that you mentioned, any input is appreciated here too!
NxNW said:
Happily running CM7 with one issue:
If I dial my own number (or longpress "1" in the dialer) to access my real voicemail box, I have many "new" messages.
Click to expand...
Click to collapse
After reading your post I pressed 1 to go into my voicemail and it said I had 12 messages. Never noticed this issue before (I never actually call for my messages, I just use the app), very strange. Unfortunately I don't know the answer.
Thanks ausch- I should have cited your FAQ as another excellent one-sentence summary of the basic method for getting Sprint VVM to run on CM7. And then of course there's this thread http://forum.xda-developers.com/showthread.php?t=982966 which spells it out a little more explicitly and, after getting a bunch of blog mentions at some point, had quite a bit of traffic for awhile. I originally reported this issue there but got no response after a few days so I just started up a new thread to get some more visibility.
I think you need another apk installed for that part to work.
This one. I think it is what updates your visual voicemail and deletes messages, not positive though.
aimbdd said:
I think you need another apk installed for that part to work.
This one. I think it is what updates your visual voicemail and deletes messages, not positive though.
Click to expand...
Click to collapse
I just installed that through ES File Explorer, we'll see if it works.
NxNW said:
I should have cited your FAQ as another excellent one-sentence summary of the basic method for getting Sprint VVM to run on CM7.
Click to expand...
Click to collapse
Lol, yeah when I was typing all that **** up I got lazy and just wrote it up real quick. Probably should have gone a little more in depth.
I installed it too (thank you for the suggestion aimbdd) but it force closes a lot and generally does not seem to fix my issue.
I'm getting plenty of notifications (my VVM "widget" shows the right number of unheard messages and the stock android VM notification up in the status bar shows the right number as well), the version is 5.1.0.34, and everything seems to function pretty well with this one exception.
I see references to Sprint_App_Updater.apk in lots of places (here's an example: http://forum.xda-developers.com/showpost.php?p=7246771&postcount=35 ) but it's not clear to me if the app is actually essential to the VM sync issue I'm talking about.
And one last thing, just a random quote (from http://www.evo4gforum.net/htc-evo-4g-how-to/visual-voicemail-9708/ ) from a person who had the exact *opposite* issue: he prefers using phone-call-based voicemail and wanted his visual voicemails to go away: "I did talk with Sprint and ... I asked them why are the messages that I delete on Sprint VM (#1) still going to VVM and not being deleted. No real answer except for that's the way the VVM app works. He assured me that if I delete a VVM that it will also delete it on Sprint's (#1), but for whatever reason it doesn't work the opposite way. "
This last sentence tells me there is supposed to be at least one-way sync.
I accept that the VVM app holds previously-downloaded audio files and it may not be desired (or even feasible) for Sprint to reach into your phone and delete a static audio file just just because you called into your voicemail and manually erased the original voicemail that spawned it. So maybe we will never have two-way sync.
But that quote above clearly promises that when things are functioning normally the mailboxes *do* sync in the direction I care about: if you delete a message from your phone, a signal goes back to the cloud so that the original is deleted there also.
aimbdd said:
I think you need another apk installed for that part to work.
This one. I think it is what updates your visual voicemail and deletes messages, not positive though.
Click to expand...
Click to collapse
I just got a voicemail and it was still in Sprint's system after deleting it from the app so I don't think this fixes the problem. Thanks for the suggestion though.
Today's PRL update did not change the behavior.
I might start casting about for answers outside the EVO 4G forum. Seems like it would be a generic Sprint issue that would apply to more than just EVO users..
Well just to close this out, I did find a solution after posting in various other threads until someone came up with the simple suggestion of uninstalling and reinstalling.
So the issue that prompted my question is resolved and my voicemail boxes *do* sync.
But I still never did find out *how* they sync.
Seems strange the underlying sync mechanism isn't more widely understood. Guess I'll let it drop for now. Thanks to everyone who chimed in.
NxNW said:
Well just to close this out, I did find a solution after posting in various other threads until someone came up with the simple suggestion of uninstalling and reinstalling.
So the issue that prompted my question is resolved and my voicemail boxes *do* sync.
But I still never did find out *how* they sync.
Seems strange the underlying sync mechanism isn't more widely understood. Guess I'll let it drop for now. Thanks to everyone who chimed in.
Click to expand...
Click to collapse
question, how did you uninstall and reinstall this...was it from titanium backup or something similar?
Nevermind, I found the fix/culprit (go sms) and now I'm all good.

[Q] Group message sent but individual responses returned?

Every time I send a group message that includes one of my friends, his messages always get sent back to me individually rather than as part of the group thread like all the others. Does anyone know why this may be? I'm fairly certain he's the only one that I have this problem with, though everyone else I've group messaged in recent memory was using an iPhone (though I'm pretty sure I had no problems with other androids in the past). He's also using a S4, but on Verizon. His messages still are listed as a MMS on my end (it's the only thing that tells me that he responded to the group rather than just me), and I believe the iPhone user in the threat is receiving his messages as a group just fine, but I'm still getting this issue. Additionally, I do not have this problem when my brother is in a group thread and he is using a S4 on Sprint. Is there some setting I can change to correct this, or is the problem on his end? If it is him, do you have any suggestions for what he may be able to change? We're both using the stock messaging app. It's really annoying because it often causes me to accidentally reply to just him rather than the whole group.
are you sure he isn't selecting to do a individual reply?
jmarrale said:
are you sure he isn't selecting to do a individual reply?
Click to expand...
Click to collapse
Just updated the post, sorry for not being specific earlier. I'm pretty sure because it comes in as a MMS and I think the guy in the chat with an iPhone receives them as a group just fine. Turns out my friend with an S3 also responds individually and not as an MMS, so I guess it's dependent on the sender, but since I know this guy has an S4 and I know that his phone supports this feature (because I know the S3 does not), I don't understand why this is happening.

Categories

Resources