I have heard of similar issues on a few other devices that don't run stock 
Android.  However as I don't have a Droid X or an affected device I can't 
troubleshoot very easily.  I'll try and get my hands on one to try and 
troubleshoot.

FYI, the way SMS Popup works when it sends a message, is it places the message 
in the system messaging "outbox" and then relies upon the system messaging to 
send it.  It seems in this case that the system is not flushing these messages 
and trying to resend them upon reboot.

Sorry, I should have said version 1.1.1, at least that is what is showing when 
I uninstalled.

I did a few more quick tests... cleared all messages.  Sent a txt to my phone 
through an email, replied with quick reply on the phone.  Replied with email to 
that, then used the stock txt app.... rebooted.  It resent the quick reply 
version only.

I wish I had time for more exhaustive testing.  Something must be different on 
the X.  If I have some free time, I'll try to do a few test cases and execute 
them.  Thank you for responding to this, I really do love the app!

I am also having this issue. If there is any troubleshooting you would like for 
me to do, I'll gladly try my best. I also have a Droid X. I've currently 
uninstalled the application until the problem is fixed because I reboot my 
phone constantly. 

i ran across this issue as well. it only seems to happen when using the quick 
reply feature. if you send a message with the quick reply you will get the 
"sent" notification box pop up. but if you open the messaging app and go into 
the conversation there will be a small arrow indicating it is in the processing 
of sending, even though the recipient has already received, and in many cases 
replied to, the message. then upon reboot the phone sends all the messages, i 
assume, because they are in the "outbox."

That's exactly what the issue is. I was testing it today. I noticed all the 
messages I did send through the quick reply feature, they had arrows next to it 
yet some of them didn't. I was confused the first time that happened just 
figuring it's a glitch by Verizon, but I'm positive it's SMS Popup.

Any progress as of yet?

i imagine it's an issue with motorola's sms client, conversation.apk. i 
switched to the stock android mms.apk and the messages sent with quick reply 
don't get stuck in the outbox. also, i had to rename conversation.apk to 
conversation.apk.bak otherwise i would send/receive duplicate messages. 
obviously this is only possible on a rooted x.

How do I fix this issue?

I'm having the same problem with my DX.  Love this app, but unfortunately will 
have to uninstall due to the resending of texts.

I think the developer is too 'busy' to deal with this problem sadly. :(

If I had a Droid X it would be pretty quick to fix this issue - unfortunately I 
don't which means it's much more difficult.  I will spend some time trying to 
work out what's wrong as soon as I can.

Issue 159 has been merged into this issue.

You guys can help me troubleshoot this a bit:
 -in the Droid X system messaging app, what symbol do messages sent from SMS Popup get?  (from above it seems a little circle?)
 -which folder are messages placed in? (outbox/queued/sent?)
 -are you able to get this symbol for messages sent from the system messaging app?

Basically there are several folders as part of the Android messaging database: 
inbox, outbox, queued, drafts, sent.

What SMS Popup does, is it places messages in "outbox" and then tells the 
system to send them.  Upon successful send, the system app is supposed to move 
these messages from "outbox" to "sent".  My guess is this is the bit where it 
is getting stuck.  The messages are in fact sent, but are never moved to the 
"sent" folder.  On reboot, the messages are then re-sent.

Ok last update for the night.  I think I may have found the issue.  Can someone 
send me the package name for the Droid X messaging app?  To find it you will 
have to install the Android SDK, turn on debug on your phone, plug it into your 
computer and run "adb logcat" from the tools folder of the SDK.

Now launch the messaging app and review the log (just sent me the log segment 
if you can't see what the package name is).

If someone can get this to me I may have a fix for you Droid X users...

Actually even better, if someone could send me the .apk for the messaging app 
or the AndroidManifest.xml then I should be able to work this out... (you will 
likely need root to get the apk).

How do I find the messaging .apk or the AndroidManifest.xml? I have root. I 
just need to know where to go.

Here is a log. I'll get the manifest if I can figure out how.

Thanks, the log may be enough.  But if you can try and get the apk that would 
be good.  It should be on your phone in /system/app - not sure what it will be 
called though (stock one is "Mms.apk" but DroidX one might be something to do 
with Messaging or Blur).  Once you locate it you should be able to do "adb pull 
/system/app/file.apk" to get it off the phone.  Then you can rename the apk to 
.zip and extract the AndroidManifest.xml.

FYI, from your log, the package name is "com.motorola.blur.conversations".

Here's a debug version to try out that might fix the re-send issue:
http://code.google.com/p/android-smspopup/downloads/detail?name=SMSPopup-1.0.8-d
roidx-debug.apk&can=2&q=

Please try and let me know if it helps.  Also it would be really helpful (even 
if it doesn't work) to try a quick reply with sms popup and then grab your 
system logs again and attach here (adb logcat output after sending message).

Right now I have just guessed the motoblur package names, if this doesn't work 
then I will need the manifest file.  In order to enable "delivery reports" i 
will also need the manifest file.

this is happening for me but i dont have a droid x, i have an htc evo. see my 
post here - http://code.google.com/p/android-smspopup/issues/detail?id=159

i think this may be a different issue for htc evo, i'll un-dupe the other issue.

Ok it seems this fix did not work, someone with a Droid X, here is what I need 
you to do:
 -install the android sdk (http://developer.android.com/sdk/index.html)
 -turn on debug mode on your phone (should be under settings -> applications -> development)
 -plug your phone into your computer via usb cable
 -run "adb pull /system/app/Conversations.apk"
 -attach apk file here

Ok no need, I managed to get the apk from someone else.  Here is a new debug 
version that should hopefully fix things:
http://code.google.com/p/android-smspopup/downloads/detail?name=SMSPopup-1.0.8-d
roidx-debug-2.apk

Please try it out and let me know.

Any feedback on this guys?  I got some other feedback from androidforums that 
this didn't help... 

Here's another version to try:
http://code.google.com/p/android-smspopup/downloads/detail?name=SMSPopup-1.0.8-d
roidx-debug-3.apk

Both droidx-debug-2 and droix-debug-3 take different approaches.  Please try 
both and let me know as soon as you can.

i do not own a droid x, i have a motorola backflip which is unable to download 
apps from sources besides the market. Could you update the app? I could not 
download the debug.

[deleted comment]

Sorry, there isn't a way to publish "test" versions of apps to Market and I'm 
not 100% sure this fixes things so I need people to test before I update the 
Market version.  If you have a backflip or AT&T phone you can still side load 
apps using adb from the developer tools:
http://forum.xda-developers.com/showthread.php?t=643866

As soon as somebody confirms one of these fixes works I will update the Market 
version... 

No response so assuming this is fixed in v1.0.9.  Closing.

If you have a Backflip you can get the fixed version from Market now.

You're correct sir. It seems as though when I installed the latest updated 
version the resend upon reboot has seized to exist. I'm sorry I wasn't able to 
respond thoroughly because I was on vacation all of this past week. Thank you 
for the effort you have put forth. I appreciate everything. 

Also, I seemed to have noticed that when I have SMS Popup as the default 
notification handler, it doesn't use the LED correctly. I have it set to 
'Green' yet it does not blink at all.

[deleted comment]

Thanks for reporting back, fingers crossed the issue is now fixed.

The LED thing is not really within control of SMS Popup - the app just calls 
the LED settings via the standard SDK and it's up to the phone manufacturer to 
implement.

I have encountered this issue again. Whenever my phone is reset some of my 
friends get random texts that I previously sent to them. Is it a possibility 
that android 2.2 has revived the problem?

I'm having this problem with my Droid Pro - it sends old texts (not just the 
most recent one) to my contacts every time the phone is turned off and 
restarted.  I don't let that happen very often, but I'd like to figure out how 
to stop it!