UPDATE: I've found a fix for this issue - AWESOME!
Just go to the Android Market and install the SMS Time Fix app by Matt Precious.
http://www.androlib.com/android.application.com-mattprecious-smsfix-pAFq.aspx
It works perfectly, and updates the time stamp on all messages to relfect PHONE time and not network time. HINT: Make sure the "Last Resort" option is checked in the settings and offset is set to zero. This little app now makes the Evo Messages app usable. Finally...
Hope this is helpful info
So, I've been reading and experiencing several issues with SMS timestamps on the Evo 4G.
It seems there are three distinct issues with SMS timestamps on the the Evo and I believe they all have the same root cause.
Issue 1: When roaming texts are received with the wrong time stamp, offset by several hours (typically 4 or 5 hours off). This causes them to not be threaded in the conversation correctly. Very annoying.
Issue 2: When receiving SMS messages on any network (Sprint or Roaming), the time stamp is off by an hour. The result is the same as Issue 1, but a less extreme example.
Issue 3: When texting back and forth in quick succession, SMS messages are not logged in the order in which they are received, and received text messages ALWAYS appear before sent text messages if they are sent during the same minute, regardless of which one was actually sent first. This is also very annoying.
I believe the root cause is that the native Sense UI messaging app is using the timestamp of the tower of each SMS rather than using the time stored on the phone. To prove this, if you use Handcent and set it to use "phone time" and ignore the tower time, it works perfectly. The thing is that I don't want to use Handcent and I want to use the native app. Is there a setting that can be tweaked to fix this? Has anyone talked to HTC or Sprint about the issue and is a fix in the works?
For such a major problem, I am surprised more people haven't come forward. It's a pretty significant bug...
Thanks,
Matt_TX.
Click to expand...
Click to collapse
I agree and its getting really annoying since it causes me to miss texts.
NM, too easy
Has anyone talked to Sprint or HTC about it? I am sure there HAS to be a fix in the works. The good news is that the native Froyo messaging app does not do this (as far as I can tell). I used a Nexus One on T-mobile and it doesn't occur. It appears to be using the phone's timestamp, as it should...
As long as HTC don't apply their "logic" (or lack thereof) over Froyo, it should be fixed soon.
I also can't believe that Sense UI stops the user from having more than one Exchange account. Android 2.1 (Eclair) does this by default. Why on earth would they remove it?
Anyway, back on topic... Please please post with your thoughts and discoveries around the SMS timestamp issue.
Thanks!
How is this related to development?
tkrechel said:
NM, too easy
Click to expand...
Click to collapse
I'm not sure what you mean by "NM, too easy". Can you explain or provide any insight. Please help if you can. For those of us with this issue, it's REALLY annoying. I apologize if the question is dumb and there is an easy fix.
I realize that some of you may not feel that it is related to development, but I disagree. For those geniuses out there that make ROM's, maybe there is some way to fix this with a setting or minor change in the Sense UI messaging app...
Additionally, there is no need to berate someone that's genuinely asking for help. It's obvious that this forum gets the most traffic, and it's obvious that the smartest "Evo User" minds are located here. I don't think there is any harm in reaching out for help, isn't that the purpose behind these forums
The samething was happening to me last night.
Sent From My HTC EVO 4G
nebenezer said:
How is this related to development?
Click to expand...
Click to collapse
Agreed. If its not happening with Handcent nor the AOSP apk, then its a direct HTC issue.
General Discussion. Also, probably not really that urgent.
./agree on all poins with OP.
I posted in Q&A about this same issues, with no replies 8(.
Anyway, I thought it was related to the modified prl that I installed. However it would do it even when I was on the stock prl.
Long story short, I called sprint and said I was having the issue. They said they were going to refresh something on their side, to wait 20 mins then power cycle the phone.
Did that and to my surprise it worked! Then yesterday I re-flashed a custom rom and the sms timestaps went all wonky. /sigh
suck it up and use handcent or chomp, they are overall better apps, just not as nice of a UI.
this has been a problem for quite some time. I've looked everywhere for a solution. This was a problem on winmo phones as well.
I switched to handcent and never looked back. Once you get it all customized, it's awesome.
davebu said:
suck it up and use handcent or chomp, they are overall better apps, just not as nice of a UI.
Click to expand...
Click to collapse
look at this guy.
handcent didn't work on my froyo rom, not sure about chomp, didn't try it.
at work i always have this problem, texts are recieved 5 hours into the future, whereas the ones i send are the correct time. occasionally ones they send are the correct time so i have to scroll up and down and it is very annoying.
not a fan of handcents pop up notifications, i guess i could turn em off.
guess i'll just 'suck it up'
regulator207 said:
this has been a problem for quite some time. I've looked everywhere for a solution. This was a problem on winmo phones as well.
I switched to handcent and never looked back. Once you get it all customized, it's awesome.
Click to expand...
Click to collapse
yup, had the same problem on my old HTC Diamond with Sense/TF3d on it.
Updated First Post...
Related
Is it just me, or is the SMS screen a bit jerky and slow? I do have a 1000+ messages in there, but I can't imagine why it would make the scrolling so poor.
Hes got looooooooads of mates...
dave1343 said:
Hes got looooooooads of mates...
Click to expand...
Click to collapse
Actually it's almost 3 years worth of messages (transferred it from phone to phone).
Anyone else experiencing similar issues?
I had to factory reset my phone because of this a couple of days back. My contacts went blank and I could barely load the messages.
I can confirm this. Scrolling through sms is laggy and not very responsive. Even in threads with only less than 10 messages. So annoying...
Mines always been like that :-( grown to put up with it
Sent from my HTC Desire using XDA App
doesn't froyo fix this?
If you let your message count get that high, then you're bound to encounter speed loss with the app. Try clearing your messages? Unless you need to know what happened 3 years ago?
Sent from my HTC Desire
GANJDROID said:
If you let your message count get that high, then you're bound to encounter speed loss with the app.
Click to expand...
Click to collapse
Technically no. They should have dealt with performance issues with a high volume of text messages. I work within software development, and something like this would most certainly raise a red flag.
Hey sorry to raise a thread from the dead.
My Messages app now runs extremely slowly - can take 5-10 seconds to load an SMS thread and sometimes lags when i'm typing a reply.
Sounds like other people have experienced similar issues. Does anyone have any suggestions for fixing this? It's almost certainly down to having a large number of messages in the thread (over 3,500 from this one contact for reasons i won't go into!) but surely with a modern smartphone it should be able to handle lots of text messages! My iPhone with 2 years worth of messages had no such issues.
One other issue - for no reason whatsoever it somtimes jumps me back up to the very top of the thread of texts meaning i either have to spend ages scrolling down or back up and reload it go get it to show the most recent ones. Anyone else experienced this?
I dont have any issues with lag etc but i second the jump-to-top issue.. its happening once a day for sure and im sooo sick of it! Anyone knows anything?
Sent from my HTC Desire using XDA App
So just as an update on my woes - my phone on Friday randomly wiped every single one of my text messages. I reset the phone but nothing came back.
Great.
On the plus side, messages is now running very fast. But seriously, a smartphone that can't handle lots of text messages (which are surely microscopic in file size) is just pathetic.
A person who can't be bothered to store extra messages seperatly is pathetic. There are apps to store/back up messages and if you are constantly referencing 2 year old messages you need help.
Just my opinion though.
I realise your comments aren't targeted at me but perhaps rather than just insulting someone's choices you could actually be helpeful and tell them the names of the apps you talk of.
Not even going to bother addressing the insular comments.
Search "SMS backup" on the market. There are lots and lots of apps. "Backup to gmail" is one I saw that looks good. I personally don't news or use any backup solution for SMS.
Hey everyone,
I seem to have issues with the desire Z same as my g1
This is really pissing me off cause i bought the desire z with all its extra processing power and ram thinking it would fix it up... but it hasnt. so i could of saved money and stayed with the g1.
My problem is that text messaging slows right down to the point it just frustrates me.
You open a message and it takes a few seconds to load on the screen then you type and hit send, takes another 10secs for the message to update on screen and then send.
Hit back to go back to ur list of messages and then wait longer for it to load that.
Like what the hell? Surely something can be done to keep it running well?
It seems to be the same with the std messaging app, the HTC one and also handcent.
They all seem to start doing the same thing and being slow and annoying.
Why? I dont get it? why?
Even if i limit the messages to delete at 200 it still is slow and horrible.
So anyway i am really hoping that someone will offer me some salvation and help me get a phone that i can message from and not get annoyed.
Thanks
How many messages do you have?
ante0 said:
How many messages do you have?
Click to expand...
Click to collapse
bout 3000 total
thats definitely alot. isnt there an sms apk that allows you to batch the messages? I believe handcent has it. that would kind of zip them temporarily
Just use Handcent, never had any slowdowns
I actually had the same issue at one point, ended up losing all my messages due to some weird glitch (probably too many messages).
Thought to myself, is there any reason to actually keep ALL the messages that far back? Probably not. Set hard limits on how many texts before it wipes older texts and never had an issue since.
I dislike Handcent solely due to advertisements. I'd rather keep my data plan limited to more useful things than ads. (Not that I don't support the devs, but I don't have unlimited or cheap data plan up here in Canada, heh.)
blunted09 said:
thats definitely alot. isnt there an sms apk that allows you to batch the messages? I believe handcent has it. that would kind of zip them temporarily
Click to expand...
Click to collapse
Dont know what you are meaning? But handcent lets it so it has a "click here to see older messages thing" Which i have enabled but has not changed anything.
Lennyuk said:
Just use Handcent, never had any slowdowns
Click to expand...
Click to collapse
I am using handcent and it is pissing me off. I try and send a message and hit send. if i push the power button before it comes up on screen (which takes about 10 seconds) then it wont send the message till i turn the phone on again and wait for it to display on the screen.
I dont get it.
CWolfCW said:
I actually had the same issue at one point, ended up losing all my messages due to some weird glitch (probably too many messages).
Thought to myself, is there any reason to actually keep ALL the messages that far back? Probably not. Set hard limits on how many texts before it wipes older texts and never had an issue since.
I dislike Handcent solely due to advertisements. I'd rather keep my data plan limited to more useful things than ads. (Not that I don't support the devs, but I don't have unlimited or cheap data plan up here in Canada, heh.)
Click to expand...
Click to collapse
I might try setting them all to delete at about 100 instead of 200? See if that makes a difference?
The htc messaging app is annoying cause when you click send it comes up with "please wait" on the screen and you cannot do anything till that finishes. I am going ot try the standard one to see if that happens or not.
Thanks for the suggestions. i will try removing old messages and i have set the limit to 150.
there is an option in handcent under the menu settings that allows u to specifically batch a certain amount of messages i think! im using chompsms now as i think its much faster. try that one out
i tried to change it to 150 message limit, and nothing got deleted, then tried to use an app to delete some, then somehow all of my messages got wiped when messaging app crashed. so now i have none hahaha.
but it is running much quicker. I will try and keep the limit of messages down and see how it goes.
Thanks everyone
its the sense thats slowing it down so.
I had about 5000 smses, and faced exactly the same problem. cut down to 1500 and still had problems. Overclocked to 1400mhz and still got same problem.
Flashed phone to cm6 and now everything is smooth like butter. I restored all 5000 of my smses and got about 6000 plus in the phone now and no lag at all, stock or handcent.
ck_jun said:
its the sense thats slowing it down so.
I had about 5000 smses, and faced exactly the same problem. cut down to 1500 and still had problems. Overclocked to 1400mhz and still got same problem.
Flashed phone to cm6 and now everything is smooth like butter. I restored all 5000 of my smses and got about 6000 plus in the phone now and no lag at all, stock or handcent.
Click to expand...
Click to collapse
To be fair though, you've changed a whole lot of stuff, and not just Sense, going to Cyanogen. So do we really know Sense is the main culprit here ?
ck_jun said:
its the sense thats slowing it down so.
I had about 5000 smses, and faced exactly the same problem. cut down to 1500 and still had problems. Overclocked to 1400mhz and still got same problem.
Flashed phone to cm6 and now everything is smooth like butter. I restored all 5000 of my smses and got about 6000 plus in the phone now and no lag at all, stock or handcent.
Click to expand...
Click to collapse
Thanks for that.
There is a couple of things i like about sense, but not a lot.
i dont like the interface, i like the dialer. and the icons. But yea.
I might give CM6 a try.
Thanks for the feedback
why the hell would anyone have 6000 text's?
dietotherhythm said:
why the hell would anyone have 6000 text's?
Click to expand...
Click to collapse
why the hell not?
for me deleting text messages is like deleting emails - you don't do that anymore, you archive stuff.
I know how you feel though. I love the Sense UI because it's such eye candy but when it comes to storing messages, once you get to the 3k+ mark it starts to be very sluggish. With C6.1 it's really fast but the interface is not as sweet but very functional. I kinda miss Sense even if it was hella clunky. I just might install that new Egyptian RUU to try it out again since the software version is higher.
Well it has been working much quicker with CM 6.1 but i miss the eye candy
But would much rather the whole overall speed than some prettyness. I will just wait for something new to come out
robzonpl said:
why the hell not?
for me deleting text messages is like deleting emails - you don't do that anymore, you archive stuff.
Click to expand...
Click to collapse
call me old fashioned but I like to keep my inbox everywhere nice and clean unless it's something I need. Then I save it to a 1.2mb floppy disk....lol
1.44mb?
Sent from my HTC Vision using XDA App
I was reading an article over at Anandtech the other day that commented on SMS slowdown in android.
I’ve expressed my frustration with Android’s sometimes extraordinarily sluggish SMS database and messaging application in the past, which slows down after a few days of heavy texting.
It’s something I’ve heard other users complain about, so I know I’m not alone, and even changing clients doesn’t help since they end up using the same SMS subsystem.
Click to expand...
Click to collapse
So I think your options are either deleting most of your messages or changing OS.
Someone and or google need to get their butt into gear and do some focus on the messaging subsystem
Have you read this terrible notice from engadget.com?
Android still has horrible text messaging bugs that'll get you fired, busted, or otherwise embarrassed
By Chris Ziegler posted Dec 31st 2010 1:12PM
Pardon us if the headline is a little sensational, but this is one that we've personally experienced -- and it's not pretty. For at least the last couple versions, Android has been plagued with a couple extremely serious bugs in its text messaging subsystem that can ultimately end up causing you to text the wrong contact -- even contacts that you've never texted before. There appear to be a few failure modes; the one we definitely experience on the Gingerbread-powered Nexus S involves being routed to the wrong thread when you tap it either in the Notifications list or the master thread list in the Messaging application, so if you don't notice, you'll end up firing a message to the wrong person.
More seriously, though, there's also an open issue in Android's bug tracking system -- inexplicably marked "medium" priority -- where sent text messages can appear to be in the correct thread and still end up being sent to another contact altogether. In other words, unless you pull up the Message Details screen after the fact, you might not even know the grievous act you've committed until your boss, significant other, or best friend -- make that former best friend -- texts you back. There seem to have been some attempts on Google's part over the year to fix it; we can't confirm that it still happens in 2.3, but for what it's worth, the issue hasn't been marked resolved in Google Code... and it was opened some six months ago.
This is akin to an alarm clock that occasionally won't go off (we've been there) or a car that randomly won't let you turn the steering wheel -- you simply cannot have a phone that you can't trust to communicate with the right people. It's a deal-breaker. We're pretty shocked that these issues weren't tied up and blasted to all affected phones as an over-the-air patch months ago, but whatever the reason, we'd like to see Google, manufacturers, and carriers drop every other Android update they're working on and make sure this is completely resolved immediately.
Want to see this fixed as much as we do? Scroll to the bottom of the Google Code page and hit "Vote for this issue and get email change notifications."
Click to expand...
Click to collapse
Contribute yourself to convince GoogleGuys to fix it!
Never had any issue with this...
Maybe, it happens only on the default Google sms app not the HTC one.
I've often sent 2 - 3000 text messeges a month with two diffrent devices over the last 18 months and never had this problem. on the otherhand engadget are known for chatting sensationalist rubbish, only to have to apologise later in an editorial.
Fightspit said:
Maybe, it happens only on the default Google sms app not the HTC one.
Click to expand...
Click to collapse
I have experienced this with the HTC messaging one. When I individually texted "Happy new year!!" to everyone, the bug happened twice and it actually sent to someone else.
AndroHero said:
I've often sent 2 - 3000 text messeges a month with two diffrent devices over the last 18 months and never had this problem. on the otherhand engadget are known for chatting sensationalist rubbish, only to have to apologise later in an editorial.
Click to expand...
Click to collapse
is not sensationalism, is an actual big ugly bug.
crapula512 said:
is not sensationalism, is an actual big ugly bug.
Click to expand...
Click to collapse
If it's a bug, then why have I not encountered it since owning this phone for 7 months?
It could be a stock Android problem as already mentioned (HTC Sense ROMs have a different messaging application).
I found a post in the discuss thread where a guy explain how to reproduce this *bug*:
killerbee3 said:
If anyone is interested, evidently "Darth Mo" has been able to replicate it - found in ACentral Forums - entire post follows;
"It's not user error, or at least it's a combination of user technique and a possible design. It has to do with how the stock messaging app interacts with the Android system notification.
I recreated it this way. Open a text, but only from the notification bar. You will be taken directly to the conversation from that contact. Now, just hit the home button to get back to the home screen. Repeat this four times to let the open conversations build up. We'll call the earliest contact 1, the next 2, etc. for this example. Let's say you converse with these contacts over some time so that messages occur in this chronological order (opened from the notification menu if possible) : 1, you, 2, you, 3, you, 4, you, 1, 3, you, 3.
Now, you've read the message from contact 3, but quickly hit the back button because you need to send a message to contact 4. So you're back at the conversation list and select conversation 4. You compose and send your message and off you go. But, what can actually happen is that your message went to contact 1 because there is a bug that when you use the back button, it will take you to the conversation screen and when you select one, it will take you to the conversation with the last "unreplied" message received before the last conversation you didn't reply to, regardless of the one you actually select from the list. It's easy to miss that it took you to the wrong conversation as the on screen info can take a beat to update and it looks like you've select the right conversation. The kicker is the conversation list does highlight the one you meant to select, but will take you to that other conversation. It's as if it's saying, "Hey, I know you want to go to that one, but you opened this message and jumped out of it without replying. Maybe you didn't see it."
It's pretty easy for people to not have seen this for a few reasons:
1. You open messages directly from the messaging app
2. You close out every conversation using the back button and don't let them build up on top of each other
3. Messages can come in such a sequence that the conditions are never correct
4. It has actually happened, only the last "unreplied" message was from the conversation you actually intended to enter
I was able to create reliably using my Google voice number to send myself text and watched it bounce around conversations seemingly randomly. It was only when I looked at the times of each message with no replies that I saw what it was doing actually had order to it.
About 30 minutes of experimentation to figure it out, but I had to know how this was happening as I could see it leading to an egregious error later. Now to explain it to HTC..."
Click to expand...
Click to collapse
i've never had this either - i use handcent
Since a few minutes ago, the issue is considered critical instead of of medium:
http://code.google.com/p/android/issues/detail?id=9392#c794
Are kiddin me?
I dont send any sms for a while , this is a very big issue !
It never happened to me but , this is a realy really big bug!
Mekrel said:
If it's a bug, then why have I not encountered it since owning this phone for 7 months?
It could be a stock Android problem as already mentioned (HTC Sense ROMs have a different messaging application).
Click to expand...
Click to collapse
why havent you encountered it? i have no frikking clue and i dont care.
fortunately now it is a critical bug.
btw, i just care about android stock problems, im not using that sense stuff.
I quite often get messages which are meant for other people from someone who has a samsung galaxy (seems that's it's a copy of the message, rather than it being sent to the wrong sender).
I don't text as much, so less prone to the error.
happened to me on stock Android. Never on HTC Sense or mod
I have actually had this bug... but it reported the message had gone to the wrong person, but the correct person replied so I assumed it was reporting it wrong.... only happened twice.
on stock rom unrooted desire
I'm using a stock ROM & native SMS. I get this bug quite a few times.
I'm working in a very loud environment, so I send & receive lots & lots of text messages.
I notice that when i have lots of threaded messages, the SMS starts to slow down & sooner or later the bug will cause me send a text to the wrong recipient.
I'm quite careful of what I'm sending now.
HTC & they told me to reset the phone.
It hasn't been fun for me since I have to reset the phone once a month because my threaded sms buildup very quickly...
I'll update to 2.29.405.5 to see if this fixes anything.
Guys,
Is the 'wrong' person who receives the message someone in your phonebook or a total stranger. If it'd someone you don't know... how does your phone pick that number up? Randomly?
I had my Desire since April, and never had this issue. I open texts from notification bar and have sent them frequently.
I've had a G1, Magic, Milestone and now a Desire and I've never experienced this at all.
I don't think this bug is very common... I've never experienced it myself and none of my android friends have either...
Just some evil forces trying to make the Android OS look bad. Not our fault they couldn't resist taking a bite of that apple so screw them!
Overblown sensationalism AKA typical journalism. It's a bug but seldom a problem encountered by users, or XDA-Dev would've been flooded with such problem threads long before such publicity sites noticed. Just me personally having switched between over a dozen ROMs/kernels and their versions since March with over 60 average text out per day since and not one occurrence means it isn't anything but rare. I rely on SMS very much daily.
------------------------------
- Sent via HTC Desire -
I'm using TSM GingerBliss and noticed the timestamps for incoming messages with the HTC messaging app are 3 hours earlier than my phone's current time. Haven't seen this before and haven't quite gotten around to testing with GoSMS or another app. Does anyone know why this is happening, or what file/setting I need to modify to correct this?
I would've posted this in the development area but I haven't posted enough past posts, and it's probably suitable for the general area anyway.
I am running TSM Bliss too but my time stamp is correct. I am not sure what is going on. I would try another messaging app to see if it is wrong there too. If so then you know it isn't the messaging app. There could be some sort of lag on your local Verizon network at the moment.
Hmm, thank you, and good thought on the Verizon lag, but I'm not sure if that's the issue though. As an initial test I sent myself a message, which returns within a few seconds with a timestamp 3 hours earlier than my phone's time. I'll try another app to check as well.
As a temporary fix I installed 'SMS Time Fix' which helps, but I'm curious now as to the actual problem.
Same here man idk what's going on
Sent from my ADR6350 using XDA App
honestly, i dont know why its doing that for some and not others..and tbh i dont know (ive poured through the xmls) and not seen why/what would be doing that
Yeah, that makes two of us so far I've tried with the stock and GoSMS apps with the same result. The SMS Time Fix app does work at fixing the timestamp, but I'm curious as to how it does this which could lead to some ideas. Newt's Inc2HD ROM has the same issue.
So does the messaging system rely on time zone info? I'm heading to another time zone so I'll be able to test that.
Ok, so I'm in Kansas City, and now the timestamps of my incoming messages are 2 hours behind. So for some reason the messaging system thinks I'm in the Pacific time zone. Maybe it's using my home zip code that I have setup through Verizon, which is in California...not sure. Another strange thing is that MMS are not affected, only SMS, go figure.
However, I might have found a setting on my flight over that could work. Maybe someone can confirm this, but in the folder
/data/data/com.android.mms/shared_prefs
there is a file
com.android.mms.customizationBySIM.xml
that has a line
<boolean name="SMS_Use_Device_Time" value ="false" />
I changed it to true, and now all the incoming messages use my phone's time, even after restart. I don't know, maybe that was added by the SMS Time Fix app, sounds promising though. Any thoughts?
Howdy,
Before I upgraded to CyanogenMod 9.0, I would get a Google Voice message notification for a text message. I'd go into the web version of Google Voice, answer the text and then after a bit, the notification would go away on my phone.
Now switched to CM9 and the notification doesn't go away unless I answer the text on my phone or clear it out on the phone.
I've tried GummyNex and CM9 and they both do it.
Has anyone else seen this? I've done the thing where I've uninstalled GV, did the *73, deleted all the Verizon VMs and the reinstalled GV but it still does it.
Don't think its related to your ROM as I'm having the exact same issue on stock 4.0.4 and have always been on stock. Seems to have started a couple weeks ago....
Been pulling my hair out trying to figure out what's going on and was about to start a thread myself asking if anyone else had the issue. Thought I was just crazy at first, but I know for a fact this is not how the app acted before. I've tried changing all kinds of things for my browser use of voice.google.com, deleted/re-installed the app, and nothing works.
I'll be texting using just the browser for a bit and look at my phone and I'll have a notification for "25 Google Voice Messages" or whatever. They never clear. I notice that when opening the GV app to the thread I'm texting in, it hasn't synced in the background, and takes a few seconds for the messages I had sent to show up in the thread. It seems as though Google Voice isn't getting background sync anymore.
Aww man So it was just highly coincidental that it happened around the same time I switched over to a different rom.
It's surprisingly frustrating for such a little thing. I just use it so much that it forces me to check the phone and clear it manually to make sure I don't *actually* have a new message when I'm using both my phone and the web app.
Argh.
Yeah - nothing I've found has fixed the issue.
Seijin said:
Aww man So it was just highly coincidental that it happened around the same time I switched over to a different rom.
It's surprisingly frustrating for such a little thing. I just use it so much that it forces me to check the phone and clear it manually to make sure I don't *actually* have a new message when I'm using both my phone and the web app.
Click to expand...
Click to collapse
Yes I think it's actually a coincidence as I said I've been on stock and it all of a sudden stopped working as it was. This is just really weird because there's been no update to the app or anything.
It's extra frustrating because Google Voice is my primary #, so I'm doing about 99.9% of my texting with it, and really enjoy being able to use voice.google.com. Dealing with clearing GV notifications every time I pick my phone up is very lame.
I don't believe I'm experiencing this, gv on GSM nexus, stock 4.0.4 rooted. Straight talk tmo mvno
Sent from my Galaxy Nexus using Tapatalk 2
I don't currently have this with my yakju 4.0.4 OTA stock ROM, but I have seen it before on this phone and every other phone I've owned across stock & custom ROMs. Fairly confident it's a problem with the app itself
@crachel - are you on cdma or gsm?
crachel said:
Fairly confident it's a problem with the app itself
Click to expand...
Click to collapse
What could it be though? I've done everything short of a factory reset. Nothing about the app itself or the settings I used changed and it started happening out of nowhere.
Seijin said:
@crachel - are you on cdma or gsm?
Click to expand...
Click to collapse
GSM
martonikaj said:
What could it be though? I've done everything short of a factory reset. Nothing about the app itself or the settings I used changed and it started happening out of nowhere.
Click to expand...
Click to collapse
I don't know.. I agree though that the problem just comes and goes, which is odd. Just a couple weeks ago they weren't clearing for me, but right now it's working fine. I remember thinking that's it's ridiculous this happens on stock firmware
crachel said:
I don't know.. I agree though that the problem just comes and goes, which is odd. Just a couple weeks ago they weren't clearing for me, but right now it's working fine. I remember thinking that's it's ridiculous this happens on stock firmware
Click to expand...
Click to collapse
Even moreso ridiculous if this is a known issue and they haven't addressed it even with these several early 2012 updates to the GV app, which made it a lot better overall in UI and UX. I just don't see how it can come and go with no changes whatsoever to your settings.
Mine definitely does the same thing... I thought it used to clear them for me, but I wasn't sure, and figured I was just thinking of how Google Talk clears the messages.
Not a huge deal to me, but it would definitely be nice if they would fix this. Our best bet is to make a post on the help forums with a bunch of posts in it.
xur17 said:
Mine definitely does the same thing... I thought it used to clear them for me, but I wasn't sure, and figured I was just thinking of how Google Talk clears the messages.
Not a huge deal to me, but it would definitely be nice if they would fix this. Our best bet is to make a post on the help forums with a bunch of posts in it.
Click to expand...
Click to collapse
If I get some time I'll put up a bug report on Google Groups/Google Code.
Edit: Nevermind! Someone's on it already from February: https://code.google.com/p/android/i...on&colspec=ID Type Status Owner Summary Stars
I'd appreciate if you're having this issue to star and comment there (as well as here).
martonikaj said:
If I get some time I'll put up a bug report on Google Groups/Google Code.
Edit: Nevermind! Someone's on it already from February: https://code.google.com/p/android/i...on&colspec=ID Type Status Owner Summary Stars
I'd appreciate if you're having this issue to star and comment there (as well as here).
Click to expand...
Click to collapse
Thanks for the link!
If anyone has a chance, they should make a post in the Google Voice forums here (I'll try to do it later when I have a chance if no-one else gets to it): http://productforums.google.com/forum/#!categories/voice/using-google-voice-on-a-mobile-device. I heard that Google Engineers do monitor / read these sometimes, so if we all post in a thread there is a chance it will get read / fixed.
I really wish there was a better way to get stuff like this fixed.
Bit late to the party. Just wanted to chime in that in my experience I don't think I've ever seen the GV notification clear itself after checking the web interface on my computer.
I've been using android for a year now and have gone through 3 phones and the asus transformer tablet. My current phone is running a CM9 based rom, but still it doesn't clear these notifications.
Man, I'd love it if it did.
Note: I think that if you use the GV widget, you will see that the notification on the widget DOES clear after checking the web interface (or at least it did in GB because I just tested this on my current phone and widget doesn't clear it either). I suppose this means that GV is pushing the "read" status of an sms to our phones. The notification on the notification bar, however, still persists despite this.
EDIT: Given my last test on my current phone, it looks like the widget doesn't clear the notification like it used to on GB. It looks like it is, in fact, a syncing issue.
LeoBloom. said:
Bit late to the party. Just wanted to chime in that in my experience I don't think I've ever seen the GV notification clear itself after checking the web interface on my computer.
I've been using android for a year now and have gone through 3 phones and the asus transformer tablet. My current phone is running a CM9 based rom, but still it doesn't clear these notifications.
Man, I'd love it if it did.
Click to expand...
Click to collapse
I can confirm that it actually did used to clear when viewed on another device, and this is the intended action. It should work exactly like an IMAP e-mail account (say, the GMail app). If you view a message on the device or in a web browser, it is cleared as read on the other. Google Voice used to do the same, and stopped doing so randomly. It's completely a backend problem.
Really wish they would fix this. Still happening on JB. Very annoying for those of us who text from the web all day.
xdp said:
Really wish they would fix this. Still happening on JB. Very annoying for those of us who text from the web all day.
Click to expand...
Click to collapse
Still a problem, go over to the google group link posted above and star the issue to (hopefully) increase it's priority and visibility:
https://code.google.com/p/android/i...s Owner Summary Stars&groupby=&sort=&id=25301