Related
Well, thats it, I actually can't pick up my phone when I get a call. I can push the green pick up button as many times as I want, but it wont respond, and I end up having to call people back. Anyone else with this issue? (phone info in sig)
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
I agree with Neobbs although when I first read the subject, I thought maybe you needed to work out more....
Same problem here. I can have the phone in my hands looking at it straight up when the phone rings and the phone goes black for about 5 seconds (or about 2 rings) and then the caller id comes up and I start hitting the call/talk button to answer. It goes to VM eventually and me hitting the green button ends up bringing up the recent call list. Auto rotate is disabled, but I do have weatherbug, open home, caller lookup and IM running in the background. Oh... and I have the transistions/animations enabled. That's all i can think of. I'll try removing the caller lookup app to see if it eliminates the problem.
hi,im running rc33 stock rom on bronze tmo g1 in singapore..it happened many a times,even on a cold boot up..wonder what is the actual problem here,mine is not rooted at all..
screamsoflust said:
hi,im running rc33 stock rom ....wonder what is the actual problem here,mine is not rooted at all..
Click to expand...
Click to collapse
why in the world would you do that? (j/k)
bhang said:
why in the world would you do that? (j/k)
Click to expand...
Click to collapse
huh?what do you mean?
screamsoflust said:
huh?what do you mean?
Click to expand...
Click to collapse
he means.. why would you not root your G1???
I think it's a good, fair and valid question.
Do you have installed a customer ring tone ? if yes, choose original ring tone and try again.
I had the same problem when I started using my phone. I dunno what changed but the prob. has disappeared or I got used to hold the pickup button down for a bit longer automatically. I got the feeling that this helped the issue.
My phone is RC33 not rooted... and to answer you question: I've tried but I'm still fighting with my XP to accept the USB driver.
Guess again!
neoobs said:
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
Click to expand...
Click to collapse
mine does the same randomly. Straight after a factory reset.
nothing installed, and my G1 is not rooted (yet).
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
n3rdftw said:
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
Click to expand...
Click to collapse
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Meltus said:
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Click to expand...
Click to collapse
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
n3rdftw said:
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
Click to expand...
Click to collapse
I'm in austin, tx too and I also get the black screen of death almost every time I get an incomming call so maybe it is a location based thing? My g1 is rooted and I have over 70 apps installed and I'm not about to uninstall them 1 by 1 to see which one could be causing it. In the past, rings extended was said to be the one causing the problem but I don't have that installed.
Also, there have been enough requests for t9 and auto correct with chomp, I'm sure it will be in the upcomming updates
Im running Haykuro now and haven't had a single incident so far. Also, I have 73 (yes, seventy-three) MB of free system memory as I moved pretty much EVERYTHING to the SD card. In return, my phone is unable to boot without my SD card... which is a bit strange.
I've been pretty frustrated with my titan recently. The number one thing that I have had problems with is text messaging. It was just so laggy, I couldn't type a simple sentence with the hardware keyboard without having to go back and edit a bunch of misspelled words. I tried flashing to different roms to see if it was a software problem, and on a fresh rom it was faster but after using it a while it became laggy once again. So I tried the new speedbooster2.0 software that was recently posted in development and hacking forum, and it seemed to help but not enough. Still a terrible lag that frustrated me to no end. I text ALL the time, more than I talk on the phone. My girl and I probably send over a hundred texts a day, so this problem was having me thinking drastically like, just getting a new phone. Texting is my #1 purpose of my phone.
Then all of a sudden today it dawned on me that I could disable word suggestions. I tried that and guess what... Completely fixed the problem!
So if anybody else is as slow mentally as I am, this info will be helpful. Otherwise this is just a good story to laugh at.
very nice...i've seen it before...happened to me...
i didn't know how i fixed it
probably loaded a new rom...
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.
Since the update to GB... my voice-to-text has not been working properly in the car. I first thought it might be background noise like the A/C or something but it appears to only happen when the car is moving.
Isn't this the whole point of voice-to-text? To keep you safe while driving so it doesn't require typing. Am I the only one with this problem? Is there any kind of workaround? I depend heavily on this feature. This is a big negative for me.
Same issue here. Voice to text has been broken for me since the first GB update on a stock unrooted EVO.
busted here too.
sucks.
Yes this happens to me too.
Just quit using your phone in the car so i can quit flipping you people off!
Have y'all tried updating voice search from the market? I noticed there was a recent update for it mentioning bug fixes.
Tried updating everything. Full factory restore on Unrooted GB 2.3.3 both the first release and with the maintenance fix. Changed Voice Input and Output settings. Changed the Google account dashboard and personalization. Everything and even rolling back to 2.2 which doesn't work because of the new Hboot.
It is completely broken. You get going 20-25mph+ and the mic does not respond.
Hope that it is address in a future release update (not likely), but will have to root and roll back.
Can any one that is rooted and on the stock 2.3 or different rom confirm if voice search is working for them?
AudioJerm said:
Have y'all tried updating voice search from the market? I noticed there was a recent update for it mentioning bug fixes.
Click to expand...
Click to collapse
Yeah... I updated Voice Search and I will find out later if it works when I get in my car.
Well, I did the Voice Search update and still can't do voice to text in the car while it's moving. This is ridiculous! I love using HeyTell especially when driving and now it has become useless.
A guy at work asked me today if i knew anything about this problem. He has had this problem since the GB update and his EVO is stock and not rooted. I told him I would look into it. Looks like I found the answer.
Sent from my HTC EVO 4G with Tapatalk
I did; however, find out that the voice search does work in the texting mode once you've hit the car in front of you wondering why it wasn't working during the driving process. Once stopped, it is amazing!
EDIT: OK..couldn't resist, but reminds me of the little "Don't use this while your driving" disclaimer in the gps units turning them on.
I've had issues with it when not moving.
I'm not sure where this connection to driving comes into play?
dpilcher said:
I did; however, find out that the voice search does work in the texting mode once you've hit the car in front of you wondering why it wasn't working during the driving process. Once stopped, it is amazing!
EDIT: OK..couldn't resist, but reminds me of the little "Don't use this while your driving" disclaimer in the gps units turning them on.
Click to expand...
Click to collapse
The whole advantage of voice-to-text is so you don't text while driving. My phone sits in a dock in the car. If someone texts me, I can verbally respond without taking my hands off the wheel. You know... kinda like talking on the phone hands-free. That's why voice-to-text is so valuable to me.
Earlier tonight I discovered the problem is worse. I was outside taking a walk and decided to use voice-to-text and nothing. Would not recognize. But once I stopped walking and used it... it was fine. So it's not just limited to driving. They need to fix this problem!
I did some looking around on Google and this issue has been reported on multiple different sites. However, it seems that it's more related to background noise rather than being in a moving vehicle. If there is any amount of background noise, voice to text seems to not work properly. It seems that it works fine if you are in a completely silent environment.
Sent from my HTC EVO 4G with Tapatalk
kd0axs said:
I did some looking around on Google and this issue has been reported on multiple different sites. However, it seems that it's more related to background noise rather than being in a moving vehicle. If there is any amount of background noise, voice to text seems to not work properly. It seems that it works fine if you are in a completely silent environment.
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
Yeah... I read the same thing but my tests did not ring true. When I was stopped at a light, I put the AC on at full blast and the voice-to-text worked flawlessly. But as soon as I moved and even with the AC off... nothing. For me, there didn't seem to be any connection with background noise... only movement.
My only other suggestion is to try an app called Vlingo for the mean time. The In Car mode is amazing. Just say "hey vlingo" and it starts listening to commands. It really is completely hands free. You never have to touch your phone to send texts and it even reads your message back to you to confirm before sending. I've never had problems with it although the in car mode is still in beta. Good luck!
I just spoke this entire post while driving 45 miles an hour down the road using Google voice search.
I had same issue on stock Rom. I believe if u look at main settings, voice input and output, text to speach settings, and in there it should say something about downloading something. If it needs updating u can press it and market will open with what u need
Sent from my PC36100 using XDA App
So I tried going through the text-to-speech settings but no luck. The issue doesn't seem to be with text-to-speech but with voice-to-text. It's like the microphone stops picking up audio when in motion.
Nevertheless... got this today from HTC...
Dear Jack Storm,
We are sorry to hear that you are experiencing issues with your Voice to Text after the recent update.
We are aware of the issues surrounding the update to your Evo and are currently working on addressing these issues. We do not currently have an exact timeframe as to when all of these issues will be resolved. Please check our official media outlets and/or your device for any change to the update status.
We do apologize for any inconveniences that this may have caused, Jack.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number 11USCW26ENA0065.
Sincerely,
Reisa
HTC
Works fine on CM7
Sent from my PC36100 using XDA Premium App
Hi guys,
I was wondering if anyone had a similar problem as I do, and have a solution for this.
My speech to text option does not work anymore. when i say anymore, i meant it used to work before i had to change the sd card and hard reset the phone (as it was stuck on white screen couple of days ago). I got that the phone to work but now it caught a bug. I dont use this feature as much, but it sort of bug me to know that there is this bug. get it?
so.. i read on a forum elsewhere, that it was due to the headset. i did use the headset several times. But i cant remember if i used the headset before or after i found out that i have this speech problem. moreover, i have restarted the phone but still to no avail.
kindly give ur opinion or a solution to this matter.
Thanks!
so.. seriously?
no answers or opinions? im kinda disappointed now.
i figured it out on my own