|
||||
Re: Threaded texts not marked as read 6.5 (confusing, just read it)
I am running the latest Mighty rom and it is doing the same thing as well. Although it doesn't really bother me all that much.
|
|
||||
Re: Threaded texts not marked as read 6.5 (confusing, just read it)
yeah, it wouldnt bother me at all if it didnt screw up my previews in S2U2, sometimes when i click to see the text in S2U2, it's an older text rather than the newest one
|
|
||||
Re: Threaded texts not marked as read 6.5 (confusing, just read it)
This seems to be happening on all 6.5 builds (you said that in your first post). I also think this is related to the "freezing" when you close out the threaded conversation. It seems that if those texts don't get marked as "read" then it causes a lag when closing the conversation.
If you select each message individually it will mark it as "read" (this also seems to get rid of the freezing when closing the conversation). |
This post has been thanked 1 times. |
|
||||
Re: Threaded texts not marked as read 6.5 (confusing, just read it)
what exactly do you mean by select it individually? what i've been doing is tapping each message while in the convo and it marks it as read, but thats a real pain, does anyone know what's different that could be affecting it?
|
|
||||
Re: Threaded texts not marked as read 6.5 (confusing, just read it)
Yeah that's exactly what i mean. And yeah it is a real pain. You could also just hit the UP button of the D-Pad a bunch of times to select them. A little faster... All in all though, for as amazing as 6.5 is as a whole, I can live with this till it does get worked out.
|
|
||||
Re: Threaded texts not marked as read 6.5 (confusing, just read it)
i agree completely, i might try to write a script to take care of it temporarily.. if anyone comes across any kind of fix or reason why, id appreciate the info
Last edited by callmesaul8889; 08-28-2009 at 12:34 AM. |
|
|
|