Phantom unread SMS/MMS about dashclock

[GoogleCodeExporter]

I'm also currently experiencing this, if you need logs I can provide.

Original comment by [email protected] on 12 Feb 2013 at 12:11

[GoogleCodeExporter]

Thanks folks. I'll reach out as soon as I'm ready to troubleshoot. In the 
meantime, feel free to prod around in the source to see if you can spot the 
issue :)

Original comment by roman.nurik on 12 Feb 2013 at 12:13

[GoogleCodeExporter]

I had the same issue, fixed it by installing and running this:

https://play.google.com/store/apps/details?id=net.tsoft.resetunreadsms&hl=en

Original comment by [email protected] on 12 Feb 2013 at 1:20

[GoogleCodeExporter]

As an alternative, I may just hide unread messages older than say, 5 days, if 
this is a problem for a lot of people.

Original comment by roman.nurik on 12 Feb 2013 at 1:22

[GoogleCodeExporter]

Ditto on this issue. Here's some more details about the message that is being 
seen as unread:

The message was a response to a mass message MMS, from someone who is not in my 
contact list, so I deleted the whole thread after this app reported it as 
unread. However, it still reports an unread message from that phone number even 
after deleting the message (which was already marked as read about a month 
before it was deleted.)

Hopefully that helps figure out what's causing this.

Original comment by [email protected] on 12 Feb 2013 at 2:03

[GoogleCodeExporter]

Original comment by roman.nurik on 12 Feb 2013 at 9:09

• Changed state: Accepted

[GoogleCodeExporter]

I have the same issue and even after deleting the entire thread, the count is 
still set to 1.

Original comment by [email protected] on 12 Feb 2013 at 11:14

[GoogleCodeExporter]

Used tip from #3. Worked just fine even though app agreed that I had no unread 
sms, it still cleared the problem.

Original comment by [email protected] on 13 Feb 2013 at 8:22

[GoogleCodeExporter]

Potential reproduction steps;

1. Receive a text with app not installed.
2. Read the message to mark as read.
3. Install the app and observe the incorrect count.

Original comment by [email protected] on 13 Feb 2013 at 9:36

[GoogleCodeExporter]

Used tip from #3 and it didn't work. The application doesn't find the unread 
message.

Original comment by [email protected] on 13 Feb 2013 at 10:49

[GoogleCodeExporter]

I had a same issue.
Tip from #3 makes it alright!
Thanks friend :)

Original comment by [email protected] on 13 Feb 2013 at 12:52

[GoogleCodeExporter]

Answer to #10 : The application doesn't find any unread message for me too, but 
I force the "read all messages" action, and it fixes the dashlock bug.

Original comment by [email protected] on 13 Feb 2013 at 1:10

[GoogleCodeExporter]

Answer to #12 : I've tried to force the "read all messages" action, but it 
doesn't work. the button is still orange/yellow and the application doesn't 
respond. 

Original comment by [email protected] on 13 Feb 2013 at 2:24

[GoogleCodeExporter]

#3 worked for me.  Even though the app did not find any unread SMS.

Original comment by [email protected] on 13 Feb 2013 at 2:26

[GoogleCodeExporter]

#13 : It took few minutes to complete on my phone (Galaxy Nexus, ~2k messages), 
I choose the waiting option two times for the "App doesn't respond" message.

Original comment by [email protected] on 13 Feb 2013 at 2:35

[GoogleCodeExporter]

Same boat as #14. #3 fixed the problem, but didn't find any unread SMS.

Original comment by htwyford97 on 13 Feb 2013 at 2:38

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

#3 Ok, it took a while, but it finally worked ! Thanks !

Original comment by [email protected] on 13 Feb 2013 at 2:48

[GoogleCodeExporter]

Looks like the phantom/orphan message has an empty thread_id. I think I've got 
a fix.

Original comment by roman.nurik on 13 Feb 2013 at 3:01

[GoogleCodeExporter]

#19: Sweet! I didn't want to have to install that app suggested by #3.

Original comment by [email protected] on 13 Feb 2013 at 3:12

[GoogleCodeExporter]

This issue was closed by revision 27ca50ee16e9.

Original comment by roman.nurik on 13 Feb 2013 at 4:03

• Changed state: Fixed

[GoogleCodeExporter]

Will be fixed in version 1.1.

Original comment by roman.nurik on 13 Feb 2013 at 4:04

[GoogleCodeExporter]

Original comment by roman.nurik on 13 Feb 2013 at 4:07

• Added labels: TargetRelease-1.1

[GoogleCodeExporter]

Issue 58 has been merged into this issue.

Original comment by roman.nurik on 13 Feb 2013 at 4:58

[GoogleCodeExporter]

The delete all messages function on the stock app *does* resolve this, even if 
it's not entirely desirable.

Original comment by [email protected] on 13 Feb 2013 at 5:00

[GoogleCodeExporter]

#25: True, that worked. I thought of trying it earlier but didn't want to lose 
all my messages. Ah, what the heck! Good one.

Original comment by [email protected] on 13 Feb 2013 at 5:48

[GoogleCodeExporter]

Issue 60 has been merged into this issue.

Original comment by roman.nurik on 13 Feb 2013 at 6:02

[GoogleCodeExporter]

Issue 61 has been merged into this issue.

Original comment by roman.nurik on 13 Feb 2013 at 6:31

[GoogleCodeExporter]

Issue 65 has been merged into this issue.

Original comment by roman.nurik on 13 Feb 2013 at 7:35

[GoogleCodeExporter]

I got the 1.1 update but it still had the issue. I then uninstalled and 
reinstalled the app and no more phantom text.

Original comment by [email protected] on 13 Feb 2013 at 7:39

[GoogleCodeExporter]

I uninstalled ver1.0 and then installed over 1.1 and the issue is gone, happy 
days!

Really nice app too :-)

Original comment by [email protected] on 13 Feb 2013 at 8:09

[GoogleCodeExporter]

Installed the update and I went from 2 to 1 phantom she's. Uninstalled and 
reinstalled and still seeing 1 phantom. 

Deleted all the all messages to be sure. 

Original comment by [email protected] on 14 Feb 2013 at 1:36

[GoogleCodeExporter]

Interesting that this is still happening. If someone can provide more 
information about what types of messages are still showing up that'd be great.

If the 1.1 update fixed this bug for you, please feel free to unstar this issue 
to stop receiving emails about it.

Original comment by roman.nurik on 14 Feb 2013 at 3:29

• Changed state: Accepted

[GoogleCodeExporter]

Issue 78 has been merged into this issue.

Original comment by roman.nurik on 14 Feb 2013 at 3:33

[GoogleCodeExporter]

Original comment by roman.nurik on 14 Feb 2013 at 5:09

• Removed labels: TargetRelease-1.1

[GoogleCodeExporter]

#3 fixed it! Thanks! 

Original comment by [email protected] on 14 Feb 2013 at 3:07

[GoogleCodeExporter]

#3 also fixed it, but damn that took HOURS to get it right. It locked up over 
and over.

Original comment by [email protected] on 15 Feb 2013 at 1:24

[GoogleCodeExporter]

For those that have used the fix in comment #3 with success... has the issue 
come back since using that fix?

Original comment by roman.nurik on 15 Feb 2013 at 4:54

[GoogleCodeExporter]

#38 Nop !

Original comment by [email protected] on 15 Feb 2013 at 8:26

[GoogleCodeExporter]

Is anyone still seeing this problem?

Original comment by roman.nurik on 16 Feb 2013 at 5:52

[GoogleCodeExporter]

Using DashClock V1.1 on a Galaxy Nexus 4.2.2 and has one phantom message. The 
number is not in my contact list and i have no such message in the stock 
message app.

Original comment by [email protected] on 16 Feb 2013 at 11:37

[GoogleCodeExporter]

Same as #41, just installed the app today. I don't recognize the #, phantom 
message. 

Original comment by [email protected] on 18 Feb 2013 at 7:52

[GoogleCodeExporter]

same as #41 Android 4.2.2

Original comment by [email protected] on 21 Feb 2013 at 12:48

[GoogleCodeExporter]

OK, to anyone still seeing this error, it would help if you could do the 
following:

1. Download and install 
https://code.google.com/p/dashclock/downloads/detail?name=DashClock-1.4.2dbg-sms
.apk

2. Ensure you see the phantom unread text message show up

3. Go into DashClock settings, press the action overflow (3 dots at the top 
right), and press "Send debug log"

4. Enter some text into the email window that pops up indicating that this is 
related to issue 8.

5. Send the email

The email will contain a bunch of debug log information (only related to 
DashClock, no other apps). This special APK has extra logging that'll spit out 
everything it can about all unread messages.

Original comment by roman.nurik on 3 Mar 2013 at 7:56

[GoogleCodeExporter]

Just updated the download link with a new version: 
https://code.google.com/p/dashclock/downloads/detail?name=DashClock-1.4.2dbg-sms
.apk

I'm optimistic/hopeful this should fix the problem for good...

Original comment by roman.nurik on 4 Mar 2013 at 4:59

[GoogleCodeExporter]

This issue was closed by revision 243a4d828093.

Original comment by roman.nurik on 4 Mar 2013 at 5:43

• Changed state: Fixed

[GoogleCodeExporter]

This should be fixed in 1.4.2. Thanks to Sam H for helping to troubleshoot.

If you'd like to try it out, here's the debug APK:
https://code.google.com/p/dashclock/downloads/detail?name=DashClock-1.4.2dbg.apk

Original comment by roman.nurik on 4 Mar 2013 at 5:45

• Added labels: TargetRelease-1.4.2

[GoogleCodeExporter]

v1.4.2 published a few minutes ago. Will be live on Google Play in the next few 
hours.

Original comment by roman.nurik on 6 Mar 2013 at 2:25

• Changed state: Released

[GoogleCodeExporter]

I fixed this by going into hangouts and checking my message archive and i found 
some unread sms there. That fixed it when I read them 

Original comment by [email protected] on 10 Nov 2013 at 9:22

[GoogleCodeExporter]

#49 did the trick. Thanks! Didn't realize archiving left it unread, but sort of 
makes sense albeit confusing. 

Original comment by [email protected] on 13 Dec 2013 at 4:18

[GoogleCodeExporter]

#49 fixed. 

Original comment by [email protected] on 16 Dec 2013 at 3:18

[GoogleCodeExporter]

#49 fixed

Original comment by [email protected] on 24 Dec 2013 at 7:06

[GoogleCodeExporter]

I'm still running into this. I had to delete the whole thread for the count to 
disappear. 

Original comment by [email protected] on 31 Dec 2013 at 5:02

[GoogleCodeExporter]

I am still seeing this as well just like #53. 

Original comment by [email protected] on 16 Jan 2014 at 6:50

[GoogleCodeExporter]

I am having this issue also with mass text/ group text. 

Original comment by [email protected] on 12 Feb 2014 at 6:06

[GoogleCodeExporter]

I tried step #3 in downloading the Unread SMS program but it didn't clear my 
stuck unread text message. I tried resetting/clearing hangouts cache but that 
didn't work.

Any suggestions?

I am on a Nexus 5 with stock 4.4

Original comment by [email protected] on 20 Feb 2014 at 8:02

[GoogleCodeExporter]

Same here. Nexus 5,unread conversation stuck. 

Original comment by [email protected] on 20 Apr 2014 at 9:03

[GoogleCodeExporter]

I am still showing an unread SMS on the widget. I have checked that there are 
no unread text messages. I've uninstalled and re-installed the app, but it is 
still showing an unread SMS.

Original comment by [email protected] on 28 Apr 2014 at 9:42

[GoogleCodeExporter]

I ran the suggestion in #3 without luck.  Nothing showing as unread in either 
regular or archived Hangouts.  The contact DashClock showed as having sent the 
unread message had recently sent a group MMS (in addition to previous 
hangouts).  I deleted that latest group MMS and rebooted.  A few minutes later, 
it reappeared as unread.  I marked the new message as read and that fixed my 
issue.  

Nexus 5 on AT&T, DashClock 1.6, Hangouts as Default SMS/MMS app.

Original comment by [email protected] on 13 Aug 2014 at 3:20

[GoogleCodeExporter]

#49 fixed it for me.  Using Hangouts for SMS of course.  Don't know if it's 
possible but it would be great if archived messages didn't count toward the 
unread count.

Original comment by [email protected] on 5 Sep 2014 at 3:59

[GoogleCodeExporter]

I'm a tad late, but I have the same issue; only my count for unread says 18 
currently even though I have 0. Every time I receive a new message, the count 
keeps going up even after I've opened it. However, my google+ account is 
connected to my SMS Hangouts app, part of the unread messages were from my 
'archived' tab. Even knowing this, my archived folder is now empty & I am still 
having the same issue. 

Original comment by [email protected] on 2 Feb 2015 at 12:12