Voicemail bug in 1.08 on Samsung Moment?

[Chris Lemon]

I've just gotten an Android phone (a Samsung Moment, which means it's
running Cupcake), and I'm loving SMS Popup; it's one of those apps
where I said "you know, I wish the SMS system did this", and this does
it.

But, I'm finding something weird: When I get a voicemail WITHOUT it
turned on, I get two notifications: one for the missed call, and a
second one telling me I have a voicemail. Great, expected behavior.

If SMS Popup is turned on, I get those two, with no popup (expected,
since they're not SMS), and third weird one that IS SMS (and so
generates a popup), as follows:

From: 901-6

//ANDROID:<phone#> has sent you a Sprint Voice Message. Call <another
phone#> to listen. MMSN, <long ID>//CM

Attempt to read or reply to this deletes it immediately out of
Messaging. Simply hitting Back on the popup makes the popup go away
but the notification sits there.

Anyone else have this problem? I've tried setting an exemption to
popups from this source in SMS Popup, but it doesn't work and would
require me to add 901-6 as a contact, which is a really inelegant
solution anyhow.

Is this a known issue? Is there a workaround? I like SMS Popup but
this is going to annoy me really fast.

Thanks!

-- Chris

[Chris Lemon]

So what I have discovered through other research is that this is a
"silent" text message sent to the phone from Sprint that triggers
Visual Voicemail to download the message to the phone. Sprint's own
notification system knows to kill it immediately once it's triggered
that download. SMS Popup basically gets to it too fast.

I wouldn't expect additions to be made to this just for Sprint's sake,
but it seems that the ability to set a filter list for things like
this (again, without having to deal with extra superfluous Contact
list entries) would be a good thing. (Honestly, I'm not sure why the
exemption thing isn't working in the first place.

Any plans to address this?

[Adam K]

Hi Chris,

Interesting issue. First of all, creating a contact with that number
and adding it as a customized notification with no popup and no sound
should work. Can you try again and see? That's definitely the
quickest solution. I realize its not ideal as you have to create a
dummy contact (we could possibly fix this by allowing number entry for
the customizations as well as contact selection).

Within the Android SDK there is also the ability to fetch other
information about SMS, in particular I noticed this:
http://developer.android.com/reference/android/telephony/gsm/SmsMessage.html#isReplace()

I'm not familiar with what this is, but perhaps Sprint uses these
special "replace" messages to signify SMS, in which case I should be
able to check for this and ignore.

I see you entered an issue for this already in our bug tracker, so
I'll create a special build when I get a chance and let you test it
out to see if the isReplace() type message is the culprit.

Out of interest, do you ever see this messages in the system messaging
app? What about with SMS Popup running?

Adam

[Chris Lemon]

Hey Adam,

Did the below, as you can see in my addition to the bug report. No go,
alas. (yes, allowing number entry would be helpful, although I don't
know if it will work. Contact selection does NOT.)

I'd be happy to help with any testing on this!

No, these messages do NOT show up in the Messaging app. (I can drag
down the Notifications bar, see it, and tap on it, but there's nothing
in Messaging when I get there.) My suspicion is that these are
instructions of some sort that tell Android to go download the message
to Visual Voicemail. Normally, Messaging would intercept it, tell
Voicemail what to do, delete it immediately, and it does it. In your
case your app is too smart and is intercepting it before any of this
can happen. :)

Does any of that help?

On Mar 4, 5:42 pm, Adam K <a...@everythingandroid.net> wrote:
> Hi Chris,
>
> Interesting issue.  First of all, creating a contact with that number
> and adding it as a customized notification with no popup and no sound
> should work.  Can you try again and see?  That's definitely the
> quickest solution.  I realize its not ideal as you have to create a
> dummy contact (we could possibly fix this by allowing number entry for
> the customizations as well as contact selection).
>
> Within the Android SDK there is also the ability to fetch other

> information about SMS, in particular I noticed this:http://developer.android.com/reference/android/telephony/gsm/SmsMessa...()