Given a basic (i.e. Google Pixel or Android One) phone running Android
10 or 11 what is the call answering sequence?

.... or is only Android Go Edition going to give me a consistent way of
call answering (if it does)?

--
Chris Green
·

On 04/05/2021 20:01, Chris Green wrote:
> Given a basic (i.e. Google Pixel or Android One) phone running Android
> 10 or 11 what is the call answering sequence?

On Pixel: if the screen is locked, swipe up to answer or down to reject.
If it's unlocked, click Answer on the heads-up notification to answer,
or Reject to reject.

Calum <com.gmail@nospam.scottishwildcat> wrote:
> On 04/05/2021 20:01, Chris Green wrote:
> > Given a basic (i.e. Google Pixel or Android One) phone running Android
> > 10 or 11 what is the call answering sequence?
>
> On Pixel: if the screen is locked, swipe up to answer or down to reject.
> If it's unlocked, click Answer on the heads-up notification to answer,
> or Reject to reject.

Is Android One the same (and/or Go Edition)?

--
Chris Green
·

Chris Green wrote:

> Calum <com.gmail@nospam.scottishwildcat> wrote:
>
>> On 04/05/2021 20:01, Chris Green wrote:
>>
>>> Given a basic (i.e. Google Pixel or Android One) phone running Android
>>> 10 or 11 what is the call answering sequence?
>>
>> On Pixel: if the screen is locked, swipe up to answer or down to reject.
>> If it's unlocked, click Answer on the heads-up notification to answer,
>> or Reject to reject.
>
> Is Android One the same (and/or Go Edition)?

Given that billions of people manage to answer zillions of phone calls a
day, why do you anticipate having problems?

In message <5ai8mh-j1mr.ln1@esprimo.zbmc.eu>
Chris Green <cl@isbd.net> wrote:

> Given a basic (i.e. Google Pixel or Android One) phone running Android 10
> or 11 what is the call answering sequence?

Do what it says on the screen when the call comes in.

David

Andy Burns <usenet@andyburns.uk> wrote:
> Chris Green wrote:
>
> > Calum <com.gmail@nospam.scottishwildcat> wrote:
> >
> >> On 04/05/2021 20:01, Chris Green wrote:
> >>
> >>> Given a basic (i.e. Google Pixel or Android One) phone running Android
> >>> 10 or 11 what is the call answering sequence?
> >>
> >> On Pixel: if the screen is locked, swipe up to answer or down to reject.
> >> If it's unlocked, click Answer on the heads-up notification to answer,
> >> or Reject to reject.
> >
> > Is Android One the same (and/or Go Edition)?
>
> Given that billions of people manage to answer zillions of phone calls a
> day, why do you anticipate having problems?
>
Because I had problems with my Moto E (Android 5 or 6 or so) and
that's why I moved from a smartphone to a feature phone.

..... and lots of people *do* have problems answering the phone with
Android, it's nut *just* me! :-)

The 'obvious' thing to do when you see a green phone icon and a red
phone icon is to tap them, other icons mostly do somehting when you
tap them.

Even if swipe is the default (to avoid 'pocket answering') it should
be possible to change it for those of us who don't keep our phones in
our pockets.

--
Chris Green
·

David Higton <dave@davehigton.me.uk> wrote:
> In message <5ai8mh-j1mr.ln1@esprimo.zbmc.eu>
> Chris Green <cl@isbd.net> wrote:
>
> > Given a basic (i.e. Google Pixel or Android One) phone running Android 10
> > or 11 what is the call answering sequence?
>
> Do what it says on the screen when the call comes in.
>
Ha! Go find my glasses first. I don't wear glasses most of the time
because my distant vision is OK still but I have no chance of doing
anything to do wth text one a phone screen without them.

I don't use a mobile much so it's never going to become second nature
to me unless it's *very* obvious what to do.

--
Chris Green
·

In article <750amh-p2ku.ln1@esprimo.zbmc.eu>, Chris Green <cl@isbd.net>
wrote:

> .... and lots of people *do* have problems answering the phone with
> Android, it's nut *just* me! :-)

no they don't.

nospam <nospam@nospam.invalid> wrote:
> In article <750amh-p2ku.ln1@esprimo.zbmc.eu>, Chris Green <cl@isbd.net>
> wrote:
>
> > .... and lots of people *do* have problems answering the phone with
> > Android, it's nut *just* me! :-)
>
> no they don't.

Well I've met quite a few!

--
Chris Green
·

In article <fedamh-kbfv.ln1@esprimo.zbmc.eu>, Chris Green <cl@isbd.net>
wrote:

> > > .... and lots of people *do* have problems answering the phone with
> > > Android, it's nut *just* me! :-)
> >
> > no they don't.
>
> Well I've met quite a few!

maybe on the very first call with a new phone if the phone does
something different than a prior phone, like slide up instead of
sideways, but after that, there should be no problems whatsoever.

there are over 2.5 billion android users worldwide (2019 numbers) and
it's simply not an issue.

nospam <nospam@nospam.invalid> wrote:
> In article <fedamh-kbfv.ln1@esprimo.zbmc.eu>, Chris Green <cl@isbd.net>
> wrote:
>
> > > > .... and lots of people *do* have problems answering the phone with
> > > > Android, it's nut *just* me! :-)
> > >
> > > no they don't.
> >
> > Well I've met quite a few!
>
> maybe on the very first call with a new phone if the phone does
> something different than a prior phone, like slide up instead of
> sideways, but after that, there should be no problems whatsoever.
>
> there are over 2.5 billion android users worldwide (2019 numbers) and
> it's simply not an issue.

Well it is for me and, from what I see in other newsgroups such as
uk.mobile, it is for some other people too.

As I said (I think) it's the reason I stopped using smartphone/android
and I've been using a 'feature phone' ever since. No question about
how you answer the phone, press the Green button.

I would point put that I don't answer very often because I don't use a
mobile very much. About once a week is a *lot* of calls for me to
answer.

--
Chris Green
·

Chris Green <cl@isbd.net> wrote:
> Ha! Go find my glasses first. I don't wear glasses most of the time
> because my distant vision is OK still but I have no chance of doing
> anything to do wth text one a phone screen without them.
>
> I don't use a mobile much so it's never going to become second nature
> to me unless it's *very* obvious what to do.

Perhaps you could practice by calling your own phone a few times and
familiarising yourself with what happens?

Theo

In comp.mobile.android, nospam <nospam@nospam.invalid> wrote:
> Chris Green <cl@isbd.net> wrote:
>> .... and lots of people *do* have problems answering the phone with
>> Android, it's nut *just* me! :-)
> no they don't.

You just love to argue, don't you? An unqualified "lots" of people in a
sentence ending in a smiley and you feel the need to contradict.

Elijah
------
agrees it is not technically spam coming out of "nospam"

In article <eli$2105051440@qaz.wtf>, Eli the Bearded
<*@eli.users.panix.com> wrote:

> >> .... and lots of people *do* have problems answering the phone with
> >> Android, it's nut *just* me! :-)
> > no they don't.
>
> You just love to argue, don't you? An unqualified "lots" of people in a
> sentence ending in a smiley and you feel the need to contradict.

there is no argument or contradiction.

there is no evidence that 'lots of people' have trouble answering their
android phone. it's a ridiculous claim.

there are ~3 billion people with android phones, and if it was actually
a problem (and it isn't), then there would be a lot of complaints, and
there aren't.

Eli the Bearded <*@eli.users.panix.com> wrote:
> In comp.mobile.android, nospam <nospam@nospam.invalid> wrote:
> > Chris Green <cl@isbd.net> wrote:
> >> .... and lots of people *do* have problems answering the phone with
> >> Android, it's nut *just* me! :-)
> > no they don't.
>
> You just love to argue, don't you? An unqualified "lots" of people in a
> sentence ending in a smiley and you feel the need to contradict.

He's a compulsive arguer who contradicts everything and anything
anyone - especially his self-assigned 'foes' - says and if you wait long
enough, he'll even contradict himself [1].

> Elijah
> ------
> agrees it is not technically spam coming out of "nospam"

Well, in the original Usenet context - too many substantially
identical postings (i.e. Breidbart index et al) - it *is* spam! :-)

[1] Example:
<http://al.howardknight.net/?STYPE=msgid&MSGI=%3Cqj1asa.62g.1@ID-201911.user.individual.net%3E>

In comp.mobile.android, Frank Slootweg <this@ddress.is.invalid> wrote:
> Eli the Bearded <*@eli.users.panix.com> wrote:
>> agrees it is not technically spam coming out of "nospam"
> Well, in the original Usenet context - too many substantially
> identical postings (i.e. Breidbart index et al) - it *is* spam! :-)

I don't know Seth Breidbart personally, but I have read a lot of his
posts (back when he was active). His definition of "substantially
identical" is much tighter than you imply.

Elijah
------
had the BI criteria in mind when making the statement

On 05/05/2021 10.04, Chris Green wrote:
> Andy Burns <usenet@andyburns.uk> wrote:
>> Chris Green wrote:
>>
>>> Calum <com.gmail@nospam.scottishwildcat> wrote:
>>>
>>>> On 04/05/2021 20:01, Chris Green wrote:
>>>>
>>>>> Given a basic (i.e. Google Pixel or Android One) phone running Android
>>>>> 10 or 11 what is the call answering sequence?
>>>>
>>>> On Pixel: if the screen is locked, swipe up to answer or down to reject.
>>>> If it's unlocked, click Answer on the heads-up notification to answer,
>>>> or Reject to reject.
>>>
>>> Is Android One the same (and/or Go Edition)?
>>
>> Given that billions of people manage to answer zillions of phone calls a
>> day, why do you anticipate having problems?
>>
> Because I had problems with my Moto E (Android 5 or 6 or so) and
> that's why I moved from a smartphone to a feature phone.
>
>
> .... and lots of people *do* have problems answering the phone with
> Android, it's nut *just* me! :-)

Hum. I had problems answering the phone the first time. I had to phone
back and ask how to do it. Slide the button. Ah, ok. No more problems
since that day. Forgotten issue.

I consider it a good idea to "slide" the button to activate instead of
tapping. At least when locked.

--
Cheers, Carlos.

Carlos E.R. <robin_listas@es.invalid> wrote:
> On 05/05/2021 10.04, Chris Green wrote:
> > Andy Burns <usenet@andyburns.uk> wrote:
> >> Chris Green wrote:
> >>
> >>> Calum <com.gmail@nospam.scottishwildcat> wrote:
> >>>
> >>>> On 04/05/2021 20:01, Chris Green wrote:
> >>>>
> >>>>> Given a basic (i.e. Google Pixel or Android One) phone running Android
> >>>>> 10 or 11 what is the call answering sequence?
> >>>>
> >>>> On Pixel: if the screen is locked, swipe up to answer or down to reject.
> >>>> If it's unlocked, click Answer on the heads-up notification to answer,
> >>>> or Reject to reject.
> >>>
> >>> Is Android One the same (and/or Go Edition)?
> >>
> >> Given that billions of people manage to answer zillions of phone calls a
> >> day, why do you anticipate having problems?
> >>
> > Because I had problems with my Moto E (Android 5 or 6 or so) and
> > that's why I moved from a smartphone to a feature phone.
> >
> > .... and lots of people *do* have problems answering the phone with
> > Android, it's nut *just* me! :-)
>
> Hum. I had problems answering the phone the first time. I had to phone
> back and ask how to do it. Slide the button. Ah, ok. No more problems
> since that day. Forgotten issue.

Yeah, I had problems with my first smartphone - a Huawei Ascend Y300 -
as well. Totally silly graphics animation, instead of - at least also -
some simple *text* saying what to do.

My current smartphone - a Samsung Galaxy A51 - is equally - or even
more - stupid. When it 'rings', there are green (left) and red (right)
buttons, with pulsating halos around them. No clue whatsoever what to do
to pick-up/reject. The correct action is to swipe the appropriate button
*up* or *over the other button*, but why would there be an up arrow or
text when you can let the user *guess/wonder* what to do!? :-( We don't
need no stinkeen ergonomics/user-friendliness!

> I consider it a good idea to "slide" the button to activate instead of
> tapping. At least when locked.

Eli the Bearded <*@eli.users.panix.com> wrote:
> In comp.mobile.android, Frank Slootweg <this@ddress.is.invalid> wrote:
> > Eli the Bearded <*@eli.users.panix.com> wrote:
> >> agrees it is not technically spam coming out of "nospam"
> > Well, in the original Usenet context - too many substantially
> > identical postings (i.e. Breidbart index et al) - it *is* spam! :-)
>
> I don't know Seth Breidbart personally, but I have read a lot of his
> posts (back when he was active). His definition of "substantially
> identical" is much tighter than you imply.

You just love to argue, don't you? :-)

But seriously: Yeah, I know Seth Breidbart's definition of
"substantially identical" is much tighter, hence the smiley.

> Elijah
> ------
> had the BI criteria in mind when making the statement

Fair enough. I should have known better, knowing that you're an old
hand who's well aware of these things.

On 06/05/2021 17.07, Frank Slootweg wrote:
> Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 05/05/2021 10.04, Chris Green wrote:
>>> Andy Burns <usenet@andyburns.uk> wrote:
>>>> Chris Green wrote:
>>>>
>>>>> Calum <com.gmail@nospam.scottishwildcat> wrote:
>>>>>
>>>>>> On 04/05/2021 20:01, Chris Green wrote:
>>>>>>
>>>>>>> Given a basic (i.e. Google Pixel or Android One) phone running Android
>>>>>>> 10 or 11 what is the call answering sequence?
>>>>>>
>>>>>> On Pixel: if the screen is locked, swipe up to answer or down to reject.
>>>>>> If it's unlocked, click Answer on the heads-up notification to answer,
>>>>>> or Reject to reject.
>>>>>
>>>>> Is Android One the same (and/or Go Edition)?
>>>>
>>>> Given that billions of people manage to answer zillions of phone calls a
>>>> day, why do you anticipate having problems?
>>>>
>>> Because I had problems with my Moto E (Android 5 or 6 or so) and
>>> that's why I moved from a smartphone to a feature phone.
>>>
>>> .... and lots of people *do* have problems answering the phone with
>>> Android, it's nut *just* me! :-)
>>
>> Hum. I had problems answering the phone the first time. I had to phone
>> back and ask how to do it. Slide the button. Ah, ok. No more problems
>> since that day. Forgotten issue.
>
> Yeah, I had problems with my first smartphone - a Huawei Ascend Y300 -
> as well. Totally silly graphics animation, instead of - at least also -
> some simple *text* saying what to do.
>
> My current smartphone - a Samsung Galaxy A51 - is equally - or even
> more - stupid. When it 'rings', there are green (left) and red (right)
> buttons, with pulsating halos around them. No clue whatsoever what to do
> to pick-up/reject. The correct action is to swipe the appropriate button
> *up* or *over the other button*, but why would there be an up arrow or
> text when you can let the user *guess/wonder* what to do!? :-( We don't
> need no stinkeen ergonomics/user-friendliness!

Yes, my first was a Samsung. Galaxy mini II, I think. I don't remember
the exact graphics, but I couldn't find out what to do.

>
>> I consider it a good idea to "slide" the button to activate instead of
>> tapping. At least when locked.

--
Cheers, Carlos.

In comp.mobile.android, Frank Slootweg <this@ddress.is.invalid> wrote:
> You just love to argue, don't you? :-)

Sometimes yeah. I do find myself resisting the urge and discarding
replies unposted when I realize it's just that: arguing without hope of
winning.

Elijah
------
certain posters are more likely to trigger such feelings

Eli the Bearded <*@eli.users.panix.com> wrote:
> In comp.mobile.android, Frank Slootweg <this@ddress.is.invalid> wrote:
> > You just love to argue, don't you? :-)
>
> Sometimes yeah. I do find myself resisting the urge and discarding
> replies unposted when I realize it's just that: arguing without hope of
> winning.

Same here. I currently have 54 unposted - but saved - responses in my
home directory. That's for the last ten years, so not too bad (or very
bad, depending on the way you look at it).

> Elijah
> ------
> certain posters are more likely to trigger such feelings

On Tue, 4 May 2021 20:01:57 +0100, Chris Green wrote:

> Given a basic (i.e. Google Pixel or Android One) phone running Android
> 10 or 11 what is the call answering sequence?

Swipe up. Google Pixel 3, Android 11.

--
s|b