Database Users

Slow answering incomming calls

hello! i've searched but didnt find any help with my problem. When my jasjar rings (incomming call) and after i press the answer button (the green one) i need to wait about 1 to 2 seconds before i can hear the person that is calling me...strange...did this ever happen to you? how can i solve this problem? Thanks in Advance

Yes, i have the same problem on my MDA Pro
After pressing the green button, i have to wait 3 secounds with speaking.

I had the same problem and now is solved.
In phone/options/band select WCDMA (not automatic)

i think that didnt solve the problem...sorry...thanks

I have the same probelm on the incoming call. However, i finally realized that it's the problem on the Pocket Plus V3.0.4 installed on the system.
It appear to be normal once i removed the program.
It's the case for me, and i hope it would help you as well

I too have this problem with my I-Mate Jasjar. I need to wait for a few seconds after hitting the answer button before I can hear the calling party. I did a hard reset and installed the latest wwe ROM available on clubimate site. The problem still persists even without any third party software installed. So I do not blame pocketplus for this problem. I think this is a software/hardware issue which should be addressed in a ROM upgrade.

I have the same problem with my JasJar. I have also updated to the lates ROM from clubImate by advice from clubImate support.
Sometimes the phone does not even answer the call at all when pressing the green button. This is becoming an even more expensive phone since I have to call back so many people on account of missed calls
Seriously, It cannot be right that a problem like this exists on a phone in this price range. ClubImate support even said they had never heard of this problem before.

i did a few hard resets and the problem persists without any extra software installed. "Very bad bug". i've already test a K-jam and it works beautifull...i'm sad

Got my XDA Exec today. It's pretty good but is not the same as my XDA2. Even less phone. More PDA...
If I turn my machine off in landscape mode and then close the lid with the screen out (like the XDA2) then when a call arrives it takes ages to answer because the screen has to rotate first to portrait mode.
If I turn off and close in laptop mode (landscape) then it rings immediately and I can answer it immediately using the hinge buttons.
Maybe it is the same for you?

i have noticed it seems to be quicker to goto portrait than to landscape in all respects of use

ok, lets try it...thanks

how i test it: jasjar "on" charging, open in portait mode. same delay.

L to P is roughly twice as long for me.
going to L i get twist and flip and the display is done ready and waiting
going to P i get twist and flip then get a 2s ish of L before it flips to P
this was battery power
*** its the same on mains and battery !

Carnivor said:
L to P is roughly twice as long for me.
going to L i get twist and flip and the display is done ready and waiting
going to P i get twist and flip then get a 2s ish of L before it flips to P
this was battery power
*** its the same on mains and battery !
Click to expand...
Click to collapse
When my Exec is on, the rotation is pretty much instant. I have no apps running. It's only when a phone call wakes it up that the rotation is slooooow.

My Qtek 9100 also take app. 5 sec before it rings, and the S100 I had before was the same. My dad has an XDA mini, same problem. It seems like pocket plus will increase the problem, but even without any extra software its not working perfect. Its strange after such long time, they havent been able to solve simple problems like theese.

I also get this, Its very annying. Maybe they incorperated it so you can answer the call asap and the before it acually picks up, you have a few seconds to turn the screen round and see whos calling ect?

I have an Exec and there is certainly a knack to answering a call on it, but i'm getting better!!!
Firstly the voicemail seems to kick in way too early, i only get 4 rings of the 'ring' ringtone max before the VM kicks in, sometimes i think it is less, but i may just be going deaf! does anyone else find this a problem?(not deafness)
As i usually have the exec closed in my pocket, this is how i answer a call.
1, Hear the first ring, if i don't it's too late already!
2, Drop everything, and remove phone(ha!) from case and open into laptop mode only. If i rotate all the way into PDA mode the screen takes too long to change and the call goes to VM before i can see who it is.
3, Answer call after seeing who it is
4, Rotate or close screen and put to my ear and wait 2 seconds to speak.
It's a real pain in the arse and very annoying.
Great forum btw, it's been very helpful, i knew bugger all about PDAs three weeks ago.
Ian

Which button(s) do you have success with?
The small green on the side,
the green above the other keys on the keyboard,
the soft key button,
or touching the screen?

ipanter said:
...
Firstly the voicemail seems to kick in way too early, i only get 4 rings of the 'ring' ringtone max before the VM kicks in, sometimes i think it is less, but i may just be going deaf! does anyone else find this a problem?(not deafness)
...Ian
Click to expand...
Click to collapse
If you're using the Exec on o2, you can adjust the cut-in delay at the o2 end. You do so by keying in/sending the following to o2:
**61*901*11*xx# [send]
(where xx is number of seconds, e.g. 30.)
Note: I think the maximum delay allowed is about 30-secs - at least I've never got it to extend longer than that!
I have found that o2 occasionally reset mine back to about 10-secs, so have it programmed into a contact number.
HTH

I've found something interesting.
I tried to swap two sim cards.
<boring>
The one originally in my phone was a sim card from Orange Denmark (where I live). Orange has since been bought by Telia, and this same sim card is now using Telias network. This is by design. It gives my the roaming symbol all the time since the buy-over.
To say the least, some things have been very ****ty in this process, so I thougt that I might try another sim card.
</boring>
I had another one from TDC (another danish operator), and bang! My Universal (Jasjar) answers instantly - every time - on all the buttons!
Could some of you who have this problem as well, please confirm this? Please tell what kind of sim card (and country) you are networking through, and try another one.

O2 XDA Mini Button Hangup after incoming Call

Hi there,
i've got a HTC Magician, branded as as O2 XDA Mini and put on it the latest ROM, I got here.
Now I have the problem, that after every incoming call, I receive, the buttons do not work any more. I still can use the touch screen, but all keys are dead until a soft reset.
Has any one an idea of getting rid of the problem?
cheers,
Nachtkrapp

Same problem here
I have the same problem, could you let me know if you found a solution?
Thanks

sorry, did not find a solution.
the problem magically disappeared after a few days..
probably due to the name of the device

What do you mean with "probably due ot the name of the device"??
Are you saying that if I rename my device, to what (??) it could disappear??

Serious problem... cant answer incoming calls!

I think its a software bug... Its really annoying if someone calls me and I cant accept the call My ringtone just keeps ringing and I just can stupidly look on the screen without answering :S I push the green "answer" button but the call doesnt accept. I neither can use the red "ignore" button. This problem gets solved with a reset but happends again after a short time.
Is there any solution for this´? Is there any possibility to accept the call trough the touchscreen?
Please help me I am really desperate!!!
Thanks in advanche.

Uhhmm.....i guess you know that you have to 'slide' the button to the green field if you wanna answer...not 'push' the green spot.
Anyways...you can also use the (physical) buttons of the phone to answer or disconnect.

I think you missunderstood me. I actually mean the physical buttons! They arent working anykind. Normally if I press the green "dial/answer" button the dialer application appears right? But it dont! After software resetting it does again somehow for short time. And if I get a call then I press the physical button but the call doesnt accept. It just keeps ringing further. There is no chance to accept the call. And there is no option to accept the call trough the touchscreen.

Indeed, i misunderstood..sorry!!
If the buttons didn't work at all, i would be thinking of a hardware problem, but since you can solve it for a short while with a soft reset.....i'm not so sure of that.
You still have the option of a hard reset, you could give it a shot, just to be sure(Remember to back up your stuff ).
Otherwise send it in for warranty...presuming you still have it.

Thanks for the reply!
I dont think its a hardware problem because the buttons are working again somehow after a software reset. But the problem happens again some time later
Sending it to warranty is no choice since I always got trouble with my warranty!
My old touch had an software problem and couldnt boot so i send it to the warranty and they just send it me back with no repairs claiming that the warranty gets lost if I connect my device with a computer :S
Anyway i hope there is a solution without hardware resetting

Just a thought....
Did you install any locking software which locks the device fully? It may be the one preventing you from answering calls...
HTH...

No I didnt install anything kinda like that. Is there a dialer replacement I could use instead?

I have also noticed this bug on my Jade running the official 2.32 update from HTC:
When a cal is received, the phone rings but it doesn't display who is calling (the device keeps showing the home screen). This is not happening at every call, but I can't find what is causing this behaviour (it happens even after hard reset, so no additional programs running in the background).
Any ideas how to overcome this?

[Q] HD2 weird issues UNRELATED to rom's....

Hey all.. Have a quick question.. Well so I hope!
Lately my phone has been randomly selecting things, without touching the screen. I have read through a lot of posts, most of which talk about 3 pole ear buds. Not the case here, have only used the 4 pole set that came with the phone.
This is very odd.. It does it randomly, like in the middle of text. The phone will start typing on it's own, or heck even back out and call the person. For the record, I do not have bear mitts and fat fingering keys instead of the correct ones.
I have tried soft reset. The only thing that cures this when it starts to happen is, press the end button to lock, wait a second then unlock.
FYI, I have tried multiple rom's.. no avail...
any thoughts? Thanks in advance
.d

Get Your phone replaced or repaired, it´s a hardware issue .......

[Q] Google Voice - Can't Press 1 to accept + Greeting is cut off

I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?

pissinguoff247 said:
I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?
Click to expand...
Click to collapse
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.

Bigger problem
fookxixi said:
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.
Click to expand...
Click to collapse
I never had the phone to my face when I did my test calls - this was always phone in my hand and calling from my office phone.
I think I just came across a bigger problem - the dialpad doesn't work on incoming calls. I just called my phone from my office on the regular (not G-voice) number and pushed a bunch of buttons, and couldn't hear the tones.

You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.

bojackson63044 said:
You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.
Click to expand...
Click to collapse
Is this actually a bug? I posted another thread here and am trying to have people verify whether or not this is a real issue - if it's not a bug then I definitely need to replace the phone, 'cuz it's been factory reset as of last night.