Reply to: Answering Incoming Call on Android Phone

[pmeswani]

I thought that must have been a spoof; when I realised it was genuine ...

It did actually cross my mind to post a spoof, but I said no in the end... I'm glad I found that link, and glad it had the double bluff effect.

[RichardCranium]

I don't know if this is of any interest to you.

Easy Answer Button applications - Android

I thought that must have been a spoof; when I realised it was genuine ...

[pmeswani]

I have the same phone and have never encountered this issue!
Do I get some kind of reward/recognition for my apparently super-human abilities?

You can have a spanner for your efforts.

[StopTheEarthIwantToGetOff]

I have the same phone and have never encountered this issue!
Do I get some kind of reward/recognition for my apparently super-human abilities?

[Fred Bloggs]

Thanks, yes.

[pmeswani]

I don't know if this is of any interest to you.

Easy Answer Button applications - Android

[Fred Bloggs]

Must admit that the swiping to answer is a bit naff and often takes 2 or 3 swipes. In the time (about two/three months) I have had the Samsung Galaxy S Android phone I have found a few annoying bugs too. Inevitable in something so complex I think.

[TykeMerc]

I spend quite a bit of time on the phone with this contract so have usually got the headset doofer plugged in. I usually answer calls on my HTC Desire using the headset centre button. It's a pretty decent hands free too.

[pmeswani]

Only if the phone isn't locked.

If It's locked you have to swipe down as usual.

I'm able to answer my incoming calls with my phone being locked and secured by a pin number and not have to swipe the phone. Be happy to demonstate if required.

[CheeseSlice]

Anyone here know any ways to answer incoming calls on an HTC Desire other than swiping the screen? The problem I have is that the swiping method often requires several attempts by which time the call has gone to voicemail.

buy a Nokia

HTH

[norrahe]

On Android 2.2, you can answer the phone without swiping the phone up and down. There's an answer button that you press to answer the call.

Only if the phone isn't locked.

If It's locked you have to swipe down as usual.

[pmeswani]

No but you can download an app that lets you anwer a call by shaking the handset apparently. There is no physical button on the handset that you can press to answer a call. The only way to answer a call is to swipe the screen in a downwards motion & if your fingers are slightly moist (for whatever reason) this doesn't always work & you get a missed call. Frustrating.

On Android 2.2, you can answer the phone without swiping the phone up and down. There's an answer button that you press to answer the call.

[wurzel]

(Can you download an app to answer the call for you while it diverts the call to a landline...? )

No but you can download an app that lets you anwer a call by shaking the handset apparently. There is no physical button on the handset that you can press to answer a call. The only way to answer a call is to swipe the screen in a downwards motion & if your fingers are slightly moist (for whatever reason) this doesn't always work & you get a missed call. Frustrating.

[RichardCranium]

"Cor, wossat?"
"It's my new Android Phone"
"Kewl! Wossit do?"
"It's great. You can download apps and play video and navigation ans scheduling and all sorts of tulip."
"Brill! Can you use it as a phone too?"
"Err... only outgoing calls. I think."

Some 'phone'!

Link:

Android phones have become popular because unlike most other phones, which have very strict rules regarding access, they are easy to manipulate, even by a consumer who is not very tech savvy.

Oh, how embarassing!

(Can you download an app to answer the call for you while it diverts the call to a landline...? )

[wurzel]

There should be an answer button when the incoming call is made which requires supressing.

Which version of Android are you using? I know I had problems answering calls on the crap LG GW620 phone (which only had Android 1.6 installed), but Android 2.1 and above should have fixed that problem.

2.1 here