Related
I've owned my Rogers Dream (rooted, no custom ROM) for a couple of weeks now - this bug has been around since the start but it's getting worse these days and it's really starting to bother me.
Basically what happens is I'll get the notification for a text message. I can see the summary in the notification bar (with the new message), but when i open a messaging app (the default one or Chomp) the message won't be there. SMS Popup will also just display the previously most recent SMS in the conversation.
It seems like the system just isn't saving the message. Besides for the notification (which disappears after i clear), it's as if I never got the message. It kind of sucks...
My searching skills came up with nothing so i'm wondering - has this happened to anyone else - any idea what the reason could be - please let me fix this.
Thanks!
Well blyn100, interesting you should point this flaw out. I have a similar issue, but so far only 1 contact has given me this same summary with no msg. Trying to figure out the source of this problem, right now I have one suspicion. A few times, i think i received these msg's after being in a no service area. I am curious if this might be a possibility for you?
Also, I have similar phone setup as you, ie same stock Rogers ROM, obviously since no choice...yet.
i have the same issue
i had a thread started, but no response yet as to how to fix this
http://forum.xda-developers.com/showthread.php?t=542178&highlight=SMS+issue
but now it seems like more and more ppl are having this issue (or it is more apparent)
its the same with Chomp, handcent, even the native app
Looks like this is mostly just a Rogers issue then?
Most of mine are occuring when I have pretty good reception, so I think i can confirm that that's not it.
Proccessor usage / avaiable RAM is what I'm leaning towards though. I might try uninstalling the virtual keyboard to free up some RAM and see if it helps anything.
Or just a bug in the stock ROM. Seems like for this to happen, the network is sending the message to the device and the device just forgets to save it, but confirms to the network that it got it. Still, i have a hard time believing a problem like this would suddenly appear for the Rogers build.
I had like 3 dropped ones last night, it's starting to get really annoying.
Are you sure it's not the timestamp bug? Look further up in your conversation to see if SMS' have been inserted there.
hellfenix said:
Are you sure it's not the timestamp bug? Look further up in your conversation to see if SMS' have been inserted there.
Click to expand...
Click to collapse
Yup, i checked all of the conversations, this isn't the case for any of them.
I had this issue on my T-Mobile G1 with the Rogers' ROMs. But I haven't had issues with Cyanogen builds...
Hi all,
I was wondering if I can't start a partition for the sms problem for leo. This is still a phone people and the two major functions of a phone are to be able to call and send text messages. Meanwhile all HTC seems to do is fix some little calendar and sd-card bugs but where is the WORKING fix for the sms messaging problem? I think if we start a petition and show HTC how much people are struggling with this problem, they will need to hurry up and fix this problem once and for all. Only problem is that I don't know how to start this off and I could use a little help. Thnx in advance.
Grtz
P.S. Still loving my snappy Leo, but it's very frustrating when you can't send messages when you're used to do this a lot..
totally agree. they should stop all other fixing not fixing anythng nd work on this issue.
I don't believe in petitions; needs someone to organise, etc.
Better idea, if you feel so strongly about it, is to write to HTC's technical department and copy their publicity and marketing people in.
WB
i dont know which problem you talk about.
but there is already a hotfix for sms-problem from htc.
http://www.htc.com/de/SupportDownload.aspx?p_id=297&cat=0&dl_id=812
i hope this will help you. otherwise, which problem do you mean?
Fonzy85 said:
i dont know which problem you talk about.
but there is already a hotfix for sms-problem from htc.
http://www.htc.com/de/SupportDownload.aspx?p_id=297&cat=0&dl_id=812
i hope this will help you. otherwise, which problem do you mean?
Click to expand...
Click to collapse
He knows that, but that hotfix dosent work. This is why he put WORKING hotfix in his message. HTC need to sort this out. coz i'm seriously thinking of selling this phone and getting another iPhone now.
Protip: The hotfix works. If it doesn't, you're doing it wrong.
DexyG said:
Protip: The hotfix works. If it doesn't, you're doing it wrong.
Click to expand...
Click to collapse
doesnt work
Gotta agree hot fix did nothing for me. Seriously annoying trying to send messages. Its rather embarrassing when i show off the phone!
The only thing that gets me by is the little work around someone suggested. When loading a contact Open and Close the menu(bottom right) then you can type. Its annoying but much faster than waiting for nearly a minute to start typing.
they should remove and return me back the old classic outlook sms!!!!
bzdemes said:
Its rather embarrassing when i show off the phone!
Click to expand...
Click to collapse
Exactly, when people use the phone to try it out and it gets stuck on one of the most basic functions, they just think "why would someone use a phone that doesn't text?". It won't do much for the "i want one" mentality that HTC want people to have when they see their friends using their phones.
DexyG said:
Protip: The hotfix works. If it doesn't, you're doing it wrong.
Click to expand...
Click to collapse
What makes you think so? There are loads of people who've installed the fix and experienced the bug since. And more are cropping up every day. Just because some people haven't had the bug come back after installing the fix doesn't mean it wont. Some users had the phone for weeks before the bug cropped up initially. Moreover, HTC themselves are not advertising the hotfix as relating in anyway to the stuck outbox problem. The accompanying description on their site is a load of marketing speak nonsense.
My 2p worth.
Firstly I have a love hate relationship with HTC Messaging. I've always used PocketCM anyway instead of the standard MS c#@* and it has worked lovely until the recent ROMS came along. Now it simply won't run alongside. Just crashes out. I don't know why and the developer can't assist as he does not have a machine to test it with and can't recreate the issue etc, etc...
Last week T-Mobile made me an offer that could not be refused and so I upgraded to the HD2. It has been with some trepidation that I have used it the past week or so as I send and receive a lot of texts on a daily basis but I have to say I have not had the problems you guys are having. They go straight away and there is none of the lag that has been reported. I'm beginning to think I must be very lucky! On the other hand I would agree that to me the two basics of these phones that must work faultlessly are the calls themselves and SMS. The fact that there is issues is pretty dreadful...
My next hope is the arrival of hacking SPL so I can flash a decent ROM onto the device and hopefully one without this program built in!!
The SMS outbox build-up (and therefore non-sending) bug is intermittent. I had it after around 4 days on my original handset. I installed the hotfix immediately upon unboxing the replacement and encountered the problem within 24 hours. There is also another, more nasty and even more intermittent SMS bug - mentioned by only a couple of people on this forum - and that is texts going to someone other than the intended recipient. I have had it happen twice to me and that is enough to give me ZERO confidence in sending texts on this device. I don't discuss anything that I would be embarrassed about if it were to get into the wrong hands. This is a bit of a disaster for a seasoned texter like myself, I used to text more than I made calls.
HTC need to address this, they obviously can't locate the 'bug' or don't fully understand the problem. Intermittent faults are notoriously difficult to fix as they never occur when the 'tester' is checking for them. Therefore if a fault cannot be replicated, how can it ever be fixed? My 2 cents is that the whole messaging app should be rewritten from scratch and the plans for the old system should not be looked at - it should all be fresh. If they can't find the bug, write some new code.
sunking101 said:
The SMS outbox build-up (and therefore non-sending) bug is intermittent. I had it after around 4 days on my original handset. I installed the hotfix immediately upon unboxing the replacement and encountered the problem within 24 hours. There is also another, more nasty and even more intermittent SMS bug - mentioned by only a couple of people on this forum - and that is texts going to someone other than the intended recipient. I have had it happen twice to me and that is enough to give me ZERO confidence in sending texts on this device. I don't discuss anything that I would be embarrassed about if it were to get into the wrong hands. This is a bit of a disaster for a seasoned texter like myself, I used to text more than I made calls.
Click to expand...
Click to collapse
Now that would be a major pain in the a#*&! As I've said I believe I must have struck lucky and have none of those issues but if I did.... God doesn't bear thinking about!
sunking101 said:
HTC need to address this, they obviously can't locate the 'bug' or don't fully understand the problem. Intermittent faults are notoriously difficult to fix as they never occur when the 'tester' is checking for them. Therefore if a fault cannot be replicated, how can it ever be fixed? My 2 cents is that the whole messaging app should be rewritten from scratch and the plans for the old system should not be looked at - it should all be fresh. If they can't find the bug, write some new code.
Click to expand...
Click to collapse
+1 to that idea but I wouldn't hold your breathe!!
One again, I repeat: I haven't seen anyone in America have this issue. I use ATT and have no issues with texts. None. I've had my HD2 for almost a whole month, as well.
*knocks on wood*
Lucky indeed
TonyJ999 said:
My 2p worth.
Firstly I have a love hate relationship with HTC Messaging. I've always used PocketCM anyway instead of the standard MS c#@* and it has worked lovely until the recent ROMS came along. Now it simply won't run alongside. Just crashes out. I don't know why and the developer can't assist as he does not have a machine to test it with and can't recreate the issue etc, etc...
Last week T-Mobile made me an offer that could not be refused and so I upgraded to the HD2. It has been with some trepidation that I have used it the past week or so as I send and receive a lot of texts on a daily basis but I have to say I have not had the problems you guys are having. They go straight away and there is none of the lag that has been reported. I'm beginning to think I must be very lucky!
Click to expand...
Click to collapse
That's the problem. Although I've read and followed these threads about this problem as they came across the forum, I had'nt had any problems myself and considered myself lucky too! But after regaining confidence in messaging with my leo, and I started to send texts again it turned out this problem occurs quite random. Sometimes I send a text and it gets delivered right away, but another time I'll send a text and a few others to other recipients, and they all get delivered 2 days later!! That's where it gets tricky for HTC I think. Then again, if they are able to create these beautiful devices, they're certainly able to rewrite a flawless messaging-app from scratch.. Only hope that this will be fixed soon Or HardSPL will be released soon.
DexyG said:
Protip: The hotfix works. If it doesn't, you're doing it wrong.
Click to expand...
Click to collapse
If you're saying that, YOU know nothing.
I too suffer this problem.
Today I got really pi**ed with it and uninstalled the Hotfix, leaving just the ROM Update, so far so good - probably just today though!
This is a really buggy phone throughout though, probably the worst I've had, but somehow this appeals to me deep down
I've had the phone since November, seen the sms problem only twice. Kinda got the impression that it only occurs if the phone has been on a good while, i.e a number of charges with no soft-resets. That could easily be coincidence.
Both times also after spotting the messages in the outbox and doing a soft reset the queued messages sent.
Still not working for me too
Just a quick question for you guys. When I receive a phone call (full signal strength) and slide the slider accross to answer the phone there is a long pause of silence before the call actually connects. Has anyone else run into this situation?
Nexus One running stock Froyo (At&t)
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Old MuckenMire said:
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Click to expand...
Click to collapse
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Never encountered that issue. The other side hears me immediately as I answer. I guess this is not "across all N1s", unless someone would think my N1 is special in some way (which it isn't, and so are all the other 7 N1s of my friends at work which also happen not to have this problem - and the call quality is great on at least 3 that I checked personally).
Instantly connects on my phone as well, so it's not on all devices at least. I have one of the first batches of T-Mobile N1's btw.
What carrier are you on?
this happens to me too.its so annoying. im on att
Can't find the thread but it was pretty long.
nexusdue said:
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Click to expand...
Click to collapse
I'm not so sure anymore. I decided since my only choice was to send it in for repair, I might as well one click root and install CM6 and see what happens. So far, I have not had the issue. It's only been three days but that's the longest this device has ever gone without having the "no connect" issue. Also, my low call volume and speaker phone volume issues are now resolved. I now find myself turning the volume down rather than up. I'll update this thread with final verdict on whether this fixes my issue.
This sounds like an att problem not a nrsux one problem
I notice this problem as well. If I wait until the call timer appears on screen before I start to talk the other party doesn't seem to notice.
I'm on T MO and never had this issue. Try the one click root and flash a different ROM. If it doesn't work send it to HTC. I recently sent mine back on a Monday and it was back that Friday.
Sent from my Nexus One
Well my issue has been resolved by switching to CM6. It's been a week now and the issue has not occurred even one time. This was an issue that used to happen to me EVERY DAY, so I am very happy that in my case it turned out to be a software issue.
When I was running 2.1 I hoped 2.2 would fix it and when it didn't I thought for sure it must be hardware. It's so nice to KNOW I can answer the phone if it rings now. Sometimes I would get an important call and I was afraid to answer the damn phone!
Thank you Mr. Cyanogen, whoever you are.
I get this issue once in a while. I think its a software issue. Over time something gets hung up somewhere.
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
khaytsus said:
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
Click to expand...
Click to collapse
Definitely not the finger covering the mic. Just tried it with/without and same result.
There was another thread that was at least 3-4 pages of people complaining about it.
Sounds more like a network issue than a hardware issue, IMO
This issue has come up recently for me and it's really annoying. I'm not sure what triggered this problem...
Is anyone else experiencing this issue? Any ideas on how to resolve?
I've got the Rogers/AT&T N1.
So, I've been having the screen sensitivity issue, jaggedy drawn lines, randomly typed keys, etc.
Now, has anyone else done the same?
As the problem is intermittent, what're the odds they'll actually fix it?
Also, is it actually going to be gone 2-3 weeks or do they usually turn around quicker?
I miss it already
mine was gone for 24 days, all it needed was a software flash. overall, good service, but could be quicker......
if they just flash the software I'll not be happy, I could do that myself.
Antimus said:
So, I've been having the screen sensitivity issue, jaggedy drawn lines, randomly typed keys, etc.
Now, has anyone else done the same?
As the problem is intermittent, what're the odds they'll actually fix it?
Also, is it actually going to be gone 2-3 weeks or do they usually turn around quicker?
I miss it already
Click to expand...
Click to collapse
I have this issue too, and I read about it on some other threads as well.
I'm not really sure what is causing it, but its more likely to be a hardware issue rather than software.
Although my friend bought his HD2 recently, and his phone doesnt have this problem. I guess this issue is fixed in newer HD2s
You can see this thread for discussion and videos about this issue
their service is worst ive ever know...4 weeks so far....never going to send my phone to them, rather send it to dodgy kev from the pub to fix
Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.
Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?
sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.
I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).
^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.
RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..
Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!
I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.