Hi! maybe it was on this forum about that but I couldn't find it. Sorry for my poor english
I have a problem with answer call lag. it's mean that when my wife call me she has 2 rings (in hear phone) and after that TP turn on screen and starting to ring. I know earlier that call is comming because led is blinking, but screen is off to 3. beep (in my wife phone).
and I have some times another problem, when time from my calendar comming reminder ring, vibrate, screen turn on (why?), but when phone is locked TP doesn't go back to stand by and the screen is still active, you can see today screen.
maybe someone has any experience with such a problems? please help me!
thank you!
I noticed the call lag in my TP as well.
anyone has an explanation?
lag here also but dont know how to fix... i dont think this can be fixed.
Related
My new xda2i seems to have a glitch, it doesn't like incoming calls. That is to say when I receive an incoming call it does't ring or vibrate. (yes I've set those settings properly!) If I do an SR it will then respond appropriately for a while but not always and not for long.
I thought it might have been something to do with Wibar advance 2.XXX but Ive disabled this and its still doing it, or not as the case actually is here!
Anyone else had these issues or got any thoughts other than send the thing back??
Pete
i have the same problem, and did as well on my old XDA2 and the XDA2s, the XDA2i is no different, after a while the phone gets "cloged up) some times it will ring but as i go to answer it says unable to answer the call, so i ring the caller back and they tell me they had been ringing for ages, and they hear the ringing tone and just think i am not answering the call.
but a spft reset fixes it, i am always soft reseting, and i have learned to live with it
John
thanks for the post, I guess I'm not the only one then huh? However I dont think SR's are the answer here I think this needs a more thorough resolution. If anyone has any ideas or solutions please respond on this thread.
I had the same problem and found that WisBar Advanced was causing this...
I uninstalled WisBar Advanced and the ringer worked again... There is a new Wisbar Beta that addresses this problem but I have not tried it yet.
Does this happen to any one or is it just me?
I have an ordinary case for my Touch Pro. Almost 10 out of 10 times when the phone rings and I reach out to my phone, try to take it out - boom - the call becomes a missed call. I guess what is happening here is that once the phone rings, the screen is active and either your finger accidentally touches the volume key or any other key or even the screen, it makes it a missed call. It is very annoying and how to avoid this????
Thanks
kmahesh said:
Does this happen to any one or is it just me?
I have an ordinary case for my Touch Pro. Almost 10 out of 10 times when the phone rings and I reach out to my phone, try to take it out - boom - the call becomes a missed call. I guess what is happening here is that once the phone rings, the screen is active and either your finger accidentally touches the volume key or any other key or even the screen, it makes it a missed call. It is very annoying and how to avoid this????
Thanks
Click to expand...
Click to collapse
there is a key disabler cab look for it
There are many options how to disable the touchscreen.
There was a topic not long ago about this.
Answerkey Disabler
PocketShield (I currently use this one)
TouchProLock
Sensorlock
Throttlelock
S2U2 (not recommended for TP, drains the battery for unknown reason)
All these deal with locking the TP.
Sorry for not posting links but I don't have much time. All of them are available on XDA though.
You do have the option of extending the time it takes for a call to go to voice mail, it can be extended up to 30 seconds. The option is under settings > phone > Services > Call Forwarding
There is also a lot of lag on between the time the caller's phone is ringing and you get a ring on the Fuze
I guess this is not because of the keys. Just keep the phone in front of you and try to call your phone and see your self, first you will see the incoming call indicator light, and after some time you will start hearing the ring tone. Now by the time you take the phone from the case - it's a miss call. I tried to search all over XDA but didn't find a way to start ringing immediately when call comes, I read some where that this is due to the dialer skin and by using default WM dialer this can be fixed. I didn't try this.
kmahesh said:
Does this happen to any one or is it just me?
I guess what is happening here is that once the phone rings, the screen is active and either your finger accidentally touches the volume key or any other key or even the screen, it makes it a missed call.
Click to expand...
Click to collapse
I think he was talking about the touchscreen being active on incoming calls.
If however the problem is in the delay, then the dialer skin is the key.
You have to change it to the WM default (it does work, the lag is almost gone) and have the ringtone in WAV format (not tested, I didn't bother to put any wavs).
if you get rid of the dialer and switch to WM
you will lose functionality including the symbol to show bluetooth being on or off
I downloaded and installed disableanswerkeys and it works fine. It took a while for me to understand the cryptic question it asks in the beginning - i get stumped if there are two negatives in a sentence So It is on and i tried and it works ok. I also downloaded sensorlock and throttlelock. Yet to try these ... will post my comments.
the lag in answering the call - i believe there is a separate thread about that, right?
Thanks for the help
lbhocky19 said:
if you get rid of the dialer and switch to WM
you will lose functionality including the symbol to show bluetooth being on or off
Click to expand...
Click to collapse
LOL, that's what happened to my bluetooth......thanks
I posted on the X10 app forum but since there was no reply i repeat it here....
1) I'd like to replace the calling screen on the X10... Anybody knows any program to do that? more usable to get the call and hang it up...
2) Is there any program to beep every 5 minutes (or similar) if you have any unread sms?
Thanks
2. handcent/chompsms/smspopup
got it! thanks
any body knows anything about the calling screen? sometimes I even hang up the call with my ear it's ****ing horrible...
The proximity sensor takes care of that most of time, just turn off the screen or don't hold the phone against your face with the sensor exposed.
I posted this on the Verizon forums and it was suggested that I also post here looking for an answer so here it goes.
My phone will randomly turn sound off. According to all sound profiles my sound is on and it should make noise when ringing or text messages come in. The problem is that the sounds will randomly turn off but not necessarily all of them. I may receive text notifications and not rings or vice versa or I may not receive either. Then randomly they will come back and I will receive all the sound notifications.
I recently had my phone replaced and once I got the new one it began doing the same thing. I just can't believe that it is a coincidence that I would get two phones (both brand new) that would do the same thing. In an effort to fix it I updated my firmware on my old phone and everything but did not help.
I love this phone and I don't want to get rid of it and I don't want to go back to the Verizon store if there is a fix for it.
Thanks in advance for any advice you may have.
Hi,
I also have an Omnia II. And I do not have those issues. But what I do know is that there is an option that if you flip your phone (with the screen facing ground) the sound will shut off if someone is calling. Like if you are in a meeting and someone is calling, you just turn your phone and the sounds is then silenced.
You can find these this setting in Start>Settings>Basic settings>Motion setting
(could be other names as I use a Dutch windows)
IannEefje said:
Hi,
I also have an Omnia II. And I do not have those issues. But what I do know is that there is an option that if you flip your phone (with the screen facing ground) the sound will shut off if someone is calling. Like if you are in a meeting and someone is calling, you just turn your phone and the sounds is then silenced.
You can find these this setting in Start>Settings>Basic settings>Motion setting
(could be other names as I use a Dutch windows)
Click to expand...
Click to collapse
This is the most likely problem. They set it up so that, even if the phone is tiled just slightly downward, the sound will be turned off. They really should have made it a more direct-downward position. If you turn that off and still have problems then check to make sure you're not activating a silent mode with the volume-down rocker on the side of the phone. Holding the rocker down for a few seconds will put the phone into either vibrate or silent. Hope you get it figured out!
Hello, I have a problem with my Nexus 5 (stock) ringtone and vibrate, I also had the same issue on my HTC One, which I had changed to Google Edition.
If someone calls the phone will ring and vibrate for about 1 second only and then it goes silent and stops vibrating, the call is still there ringing on the screen but just no sound or vibrate. This iv very annoying as I keep missing calls, can anyone please help with this issue.
Thanks
sferg.410 said:
Hello, I have a problem with my Nexus 5 (stock) ringtone and vibrate, I also had the same issue on my HTC One, which I had changed to Google Edition.
If someone calls the phone will ring and vibrate for about 1 second only and then it goes silent and stops vibrating, the call is still there ringing on the screen but just no sound or vibrate. This iv very annoying as I keep missing calls, can anyone please help with this issue.
Thanks
Click to expand...
Click to collapse
Did you ever find a solution to this? My phone has started doing exactly this, and I don't really know how to even begin troubleshooting it.
Yes I did. It was a 3rd party app causing the problem. A call control app that lets you accept and block numbers.....
Thanks for replying. That was my problem too. You saved me going through app by app to figure this out.