On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes off, I see this on
the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these buttons be presented,
if they aren't usable? What am I missing?
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these buttons be presented, if they aren't usable? What am I missing?
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes
off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these
buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels.
They aren't buttons as such.
croy wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes off, I see this on
the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these buttons be presented,
if they aren't usable? What am I missing?
slide the blue clock to left or right as appropriate,
On 2/18/24 9:26 AM, David Higton wrote:
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes >>> off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these >>> buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels.
They aren't buttons as such.
Sliding/swiping rather than tapping is NOT intuitive. When I got my
first smartphone I had to return calls because I couldn't answer them :-(
The Real Bev, 2024-02-18 19:22:
On 2/18/24 9:26 AM, David Higton wrote:
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes >>>> off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these >>>> buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels.
They aren't buttons as such.
Sliding/swiping rather than tapping is NOT intuitive. When I got my
first smartphone I had to return calls because I couldn't answer them :-(
At least tapping the option should be supported as well, even if sliding
was the original intended way.
The Real Bev, 2024-02-18 19:22:
On 2/18/24 9:26 AM, David Higton wrote:
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes >>> off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these >>> buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels.
They aren't buttons as such.
Sliding/swiping rather than tapping is NOT intuitive. When I got my
first smartphone I had to return calls because I couldn't answer them :-(
At least tapping the option should be supported as well, even if sliding
was the original intended way.
The Real Bev wrote:
Sliding/swiping rather than tapping is NOT intuitive. When I got my
first smartphone I had to return calls because I couldn't answer them :-(
At least tapping the option should be supported as well, even if sliding
was the original intended way.
On 2/18/24 9:26 AM, David Higton wrote:
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes >>> off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these >>> buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels.
They aren't buttons as such.
Sliding/swiping rather than tapping is NOT intuitive. When I got my
first smartphone I had to return calls because I couldn't answer them :-(
Arno Welzel wrote:
The Real Bev wrote:
Sliding/swiping rather than tapping is NOT intuitive. When I got mysliding
first smartphone I had to return calls because I couldn't answer them :-( >> At least tapping the option should be supported as well, even if
was the original intended way.
I suspect the reason that tapping is not used is to avoid accidental
presses.
Andy Burns <usenet@andyburns.uk> writes:
Arno Welzel wrote:
The Real Bev wrote:
Sliding/swiping rather than tapping is NOT intuitive. When I got mysliding
first smartphone I had to return calls because I couldn't answer them :-( >>> At least tapping the option should be supported as well, even if
was the original intended way.
I suspect the reason that tapping is not used is to avoid accidental
presses.
My phone has an option "press volume up to answer calls" although I have >never tried it through fear of accidental answering.
But the slide
answer did catch me out at first. Too many things these days you have to
know from experience. Buttons should look like buttons, slidey switches >should look like slidey switches (perhaps a grip on them).
On 2/18/24 9:26 AM, David Higton wrote:
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes >>> off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these >>> buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels.
They aren't buttons as such.
Sliding/swiping rather than tapping is NOT intuitive. When I got my
first smartphone I had to return calls because I couldn't answer them :-(
On 2/18/24 9:26 AM, David Higton wrote:
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes >>> off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these >>> buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels.
They aren't buttons as such.
Sliding/swiping rather than tapping is NOT intuitive. When I got my
first smartphone I had to return calls because I couldn't answer them :-(
On Sun, 18 Feb 2024 10:22:43 -0800, The Real Bev <bashley101@gmail.com> wrote:
On 2/18/24 9:26 AM, David Higton wrote:
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes >>>> off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these >>>> buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels.
They aren't buttons as such.
Sliding/swiping rather than tapping is NOT intuitive. When I got my
first smartphone I had to return calls because I couldn't answer them :-(
Amen!
This is my gripe about Android. Some time you leave programs from the
top of the screen, some times at the bottom.
If you hit a sequence of
keys one time it will do something the next something different.
There is no consistency it what an action will do with the android system.
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes
off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these
buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels.
They aren't buttons as such.
David
On 2/18/24 12:03 PM, Frank Slootweg wrote:
But it *should* be clear what one is supposed to do when the alarm
goes off. On one of my earlier phones - forgot which one - there were
moving arrows in the direction of the intended swipe. A bit better, but
not much.
What one could/should do, is just *say* what to do, i.e. 'swipe [to
the] right to snooze' (and 'swipe [to the] left to stop). But in this
day and age of GUIs, we can't have meaningful text, can we now!? Text is
sooo last century! Even the phone in this example has silly words like
'Alarm', 'Snooze' and 'Stop'. What's wrong with these people!? Can't
they come up with some meaningless icons instead?
Best is "Ladies, please keep your knees together."
It took five minutes of googling to discover what a + inside a circle
means, and I've already forgotten it... Oh yeah, "data saver". Another
5 minutes I won't get back.
On 2/18/24 4:18 PM, knuttle wrote:
On 02/18/2024 3:45 PM, croy wrote:
On Sun, 18 Feb 2024 10:22:43 -0800, The Real Bev <bashley101@gmail.com> wrote:This is my gripe about Android. Some time you leave programs from the
On 2/18/24 9:26 AM, David Higton wrote:Amen!
In message <oce4ti1t98smv74kfkjuae511bsuj6f68i@4ax.com>
croy <croy@spam.invalid.net> wrote:
On my Moto G5 Plus, when the phone is off (sleeping?), when an alarm goes
off, I see this on the screen:
https://ibb.co/zJKz5ch
... but none of the buttons do anything when stomped on. Why would these
buttons be presented, if they aren't usable? What am I missing?
I think the idea is that you drag the clock to either of the labels. >>>>> They aren't buttons as such.
Sliding/swiping rather than tapping is NOT intuitive. When I got my
first smartphone I had to return calls because I couldn't answer them :-( >>>
top of the screen, some times at the bottom. If you hit a sequence of
keys one time it will do something the next something different.
There is no consistency it what an action will do with the android system.
Given the paucity of actual documentation and the fact that Android is
pretty much a monoculture, it seems proper that there should be a set of >generic operations. By now there has been enough time for the better
(if not best) ones to have been devised.
Buttons tap. Sliders are SLIDE-SWITCH replicas. Yes=right, no=left.
You should be able to orient the damn things so that the charger plugs
in at the TOP (if desired) so you can lean it against something and use
it while it's charging. Basic shit.
Best is "Ladies, please keep your knees together."
The Real Bev <bashley101@gmail.com> wrote
You should be able to orient the damn things so that the charger plugs
in at the TOP (if desired) so you can lean it against something and use
it while it's charging. Basic shit.
My GUESS is that the charge hole is on the bottom so the cord hangs down if
you need to charge and talk at the same time, like a corded handset used to be.
Arno Welzel <usenet@arnowelzel.de> wrote:[...]
The Real Bev, 2024-02-18 19:22:
Sliding/swiping rather than tapping is NOT intuitive. When I got myAt least tapping the option should be supported as well, even if sliding
first smartphone I had to return calls because I couldn't answer them :-( >>
was the original intended way.
I don't agree, because allowing a simple tap would also cause an
accidental 'tap' ('butt call') to turn off or snooze the alarm.
Arno Welzel wrote:
The Real Bev wrote:
Sliding/swiping rather than tapping is NOT intuitive. When I got myAt least tapping the option should be supported as well, even if sliding
first smartphone I had to return calls because I couldn't answer them :-( >>
was the original intended way.
I suspect the reason that tapping is not used is to avoid accidental
presses.
This is my gripe about Android. Some time you leave programs from the
top of the screen, some times at the bottom. If you hit a sequence of
keys one time it will do something the next something different.
There is no consistency it what an action will do with the android system.
On 2/18/24 5:18 PM, knuttle wrote:[...]
There is no consistency it what an action will do with the android system.
Any examples? Most of my Android toys are pretty much the same in how they
work.
Buttons tap. Sliders are SLIDE-SWITCH replicas. Yes=right, no=left.
You should be able to orient the damn things so that the charger plugs
in at the TOP (if desired) so you can lean it against something and use
it while it's charging. Basic shit.
Frank Slootweg, 2024-02-18 21:03:
Arno Welzel <usenet@arnowelzel.de> wrote:[...]
The Real Bev, 2024-02-18 19:22:
Sliding/swiping rather than tapping is NOT intuitive. When I got myAt least tapping the option should be supported as well, even if sliding >> was the original intended way.
first smartphone I had to return calls because I couldn't answer them :-( >>
I don't agree, because allowing a simple tap would also cause an accidental 'tap' ('butt call') to turn off or snooze the alarm.
See my other post. Android 13/14 originally also only need a tap and not
a swipe.
Android 13/14 originally also only need a tap and not
a swipe.
Arno Welzel <usenet@arnowelzel.de> wrote:
Frank Slootweg, 2024-02-18 21:03:
Arno Welzel <usenet@arnowelzel.de> wrote:[...]
The Real Bev, 2024-02-18 19:22:
Sliding/swiping rather than tapping is NOT intuitive. When I got my >>>>> first smartphone I had to return calls because I couldn't answer them :-( >>>>At least tapping the option should be supported as well, even if sliding >>>> was the original intended way.
I don't agree, because allowing a simple tap would also cause an
accidental 'tap' ('butt call') to turn off or snooze the alarm.
See my other post. Android 13/14 originally also only need a tap and not
a swipe.
What does "originally" mean? Are you saying it's no longer the case?
Anyway, my Samsung (A51, Android 13) phone needs a swipe and so did my
two earlier Huawei phones.
Andy Burns, 2024-02-25 14:29:
Arno Welzel wrote:
Android 13/14 originally also only need a tap and not
a swipe.
Pretty sure android 4 used swipes to answer calls?
Android 4 was released in 2011 - which is 13 years ago now. How relevant
is this today?
Frank Slootweg, 2024-02-25 14:36:
Arno Welzel <usenet@arnowelzel.de> wrote:
Frank Slootweg, 2024-02-18 21:03:
Arno Welzel <usenet@arnowelzel.de> wrote:[...]
The Real Bev, 2024-02-18 19:22:
Sliding/swiping rather than tapping is NOT intuitive. When I got my >>>>> first smartphone I had to return calls because I couldn't answer them :-(
At least tapping the option should be supported as well, even if sliding >>>> was the original intended way.
I don't agree, because allowing a simple tap would also cause an
accidental 'tap' ('butt call') to turn off or snooze the alarm.
See my other post. Android 13/14 originally also only need a tap and not >> a swipe.
What does "originally" mean? Are you saying it's no longer the case?
I mean as implemented by Google in AOSP and not modified by a custom UI
of a phone manufacturer.
[...]
Anyway, my Samsung (A51, Android 13) phone needs a swipe and so did my two earlier Huawei phones.
Yes, because Samsung and Huawei implemented it this way. But the
standard app provided by Google does not.
Arno Welzel wrote:
Android 13/14 originally also only need a tap and not
a swipe.
Pretty sure android 4 used swipes to answer calls?
Moral: When talking about a Google phone, *say* you're talking about a Google phone, because, for all intents and purposes, there - sadly - is
no such thing as 'standard Android'.
Android 4 was released in 2011 - which is 13 years ago now. How relevant
is this today?
Carlos E.R., 2024-02-18 21:01:
On 2024-02-18 20:42, Arno Welzel wrote:[...]
The Real Bev, 2024-02-18 19:22:
Sliding/swiping rather than tapping is NOT intuitive. When I got myAt least tapping the option should be supported as well, even if sliding >>> was the original intended way.
first smartphone I had to return calls because I couldn't answer them :-( >>>
No.
It is intentionally disabled to impede accidental tapping, like with
phone under the pillow or the pocket.
Capacitive touchscreens can not be "tapped" under a pillow or inside a
pocket since they need physical contact with a finger, so the
capacitance of the sensor grid in the screen will change.
And by the way: the original alarm clock of Android 13 or 14 also just provides a stop *button* which has to be tapped and not slided. So the explanation, that sliding was implemented to avoid accidental tapping is
a very weak argument. It's more likely that the "swipe to do something"
is just a copycat of the iPhone UI to look more "modern".
Frank Slootweg wrote:
  Moral: When talking about a Google phone, *say* you're talking about a >> Google phone, because, for all intents and purposes, there - sadly - is
no such thing as 'standard Android'.
I've always bought Nexus/Pixel phones (I inherit a Samsung, which I gave away) I will always regard Google phones as "stock", anyone who buys a modified one, it's up to _them_ to cope with the differences ...
Arno Welzel wrote:
Android 4 was released in 2011 - which is 13 years ago now. How relevant
is this today?
someone was saying swipe to answer (or stop alarm) was NEW and confusing
...
Arno Welzel <usenet@arnowelzel.de> wrote:
Frank Slootweg, 2024-02-18 21:03:
Arno Welzel <usenet@arnowelzel.de> wrote:
The Real Bev, 2024-02-18 19:22:
So the question becomes: Does anyone with a non-Google phone have an
alarm which does not need to be swiped to turn it off (but can be turned
off with a tap)? If so, what is the brand and model of your phone?
Frank Slootweg wrote:
Moral: When talking about a Google phone, *say* you're talking about a Google phone, because, for all intents and purposes, there - sadly - is
no such thing as 'standard Android'.
I've always bought Nexus/Pixel phones (I inherit a Samsung, which I gave away) I will always regard Google phones as "stock", anyone who buys a modified one, it's up to _them_ to cope with the differences ...
On 2024-02-25 14:36, Frank Slootweg wrote:
Arno Welzel <usenet@arnowelzel.de> wrote:
Frank Slootweg, 2024-02-18 21:03:
Arno Welzel <usenet@arnowelzel.de> wrote:
The Real Bev, 2024-02-18 19:22:
...
So the question becomes: Does anyone with a non-Google phone have an alarm which does not need to be swiped to turn it off (but can be turned off with a tap)? If so, what is the brand and model of your phone?
My Motorola g52, running Android 13, which has few brand made
customizations, has two different alarm displays. When the phone is not locked, the alarm displays a small window on top of whatever has the
screen, and has pushbuttons.
When the display is locked, I get the big slide buttons instead.
It is impossible to buy a google phone, they are way too expensive.
On 2024-02-25 13:40, Arno Welzel wrote:
Carlos E.R., 2024-02-18 21:01:
On 2024-02-18 20:42, Arno Welzel wrote:[...]
The Real Bev, 2024-02-18 19:22:
Sliding/swiping rather than tapping is NOT intuitive. When I got my >>>>> first smartphone I had to return calls because I couldn't answer them :-( >>>>At least tapping the option should be supported as well, even if sliding >>>> was the original intended way.
No.
It is intentionally disabled to impede accidental tapping, like with
phone under the pillow or the pocket.
Capacitive touchscreens can not be "tapped" under a pillow or inside a
pocket since they need physical contact with a finger, so the
capacitance of the sensor grid in the screen will change.
LOL.
My "smart watch" touch screen is often been activated accidentally.
For example, yesterday I was washing up some plates and glasses. My
shirt long sleeves got humid, and it activated my watch repeatedly, and managed to erase the custom display by another. I had to go into the
phone app and download/upload the custom display that I use, again.
So no, accidental tapping of a touch screen is a thing that happens
easily. Specially when one is half sleep trying to find the phone with
eyes half closed.
Arno Welzel <usenet@arnowelzel.de> wrote:
Andy Burns, 2024-02-25 14:29:
Arno Welzel wrote:
Android 13/14 originally also only need a tap and not
a swipe.
Pretty sure android 4 used swipes to answer calls?
Android 4 was released in 2011 - which is 13 years ago now. How relevant
is this today?
I think it's very relevant, because if Andy is right, if current
(Google Pixel) Android does not need a swipe, that's a rather stupid
change (for the reasons given.
Moral: When talking about a Google phone, *say* you're talking about a Google phone, because, for all intents and purposes, there - sadly - is
no such thing as 'standard Android'.
On 2024-02-26 08:26, Andy Burns wrote:
Frank Slootweg wrote:
  Moral: When talking about a Google phone, *say* you're talking about a >>> Google phone, because, for all intents and purposes, there - sadly - is
no such thing as 'standard Android'.
I've always bought Nexus/Pixel phones (I inherit a Samsung, which I gave
away) I will always regard Google phones as "stock", anyone who buys a
modified one, it's up to _them_ to cope with the differences ...
It is impossible to buy a google phone, they are way too expensive.
Frank Slootweg, 2024-02-25 20:58:
Arno Welzel <usenet@arnowelzel.de> wrote:
Andy Burns, 2024-02-25 14:29:
Arno Welzel wrote:
Android 13/14 originally also only need a tap and not
a swipe.
Pretty sure android 4 used swipes to answer calls?
Android 4 was released in 2011 - which is 13 years ago now. How relevant >> is this today?
I think it's very relevant, because if Andy is right, if current
(Google Pixel) Android does not need a swipe, that's a rather stupid
change (for the reasons given.
I think it is so for many years now. I can't remember that I had to
swipe to stop the alarm in the last 5 years.
Carlos E.R., 2024-02-26 12:58:
On 2024-02-25 13:40, Arno Welzel wrote:
Carlos E.R., 2024-02-18 21:01:
On 2024-02-18 20:42, Arno Welzel wrote:[...]
The Real Bev, 2024-02-18 19:22:
Sliding/swiping rather than tapping is NOT intuitive. When I got my >>>>>> first smartphone I had to return calls because I couldn't answer them :-(
At least tapping the option should be supported as well, even if sliding >>>>> was the original intended way.
No.
It is intentionally disabled to impede accidental tapping, like with
phone under the pillow or the pocket.
Capacitive touchscreens can not be "tapped" under a pillow or inside a
pocket since they need physical contact with a finger, so the
capacitance of the sensor grid in the screen will change.
LOL.
No, physics.
My "smart watch" touch screen is often been activated accidentally.
For example, yesterday I was washing up some plates and glasses. My
shirt long sleeves got humid, and it activated my watch repeatedly, and
managed to erase the custom display by another. I had to go into the
phone app and download/upload the custom display that I use, again.
And what exactly has a humid shirt touching the unprotected touch screen
on your smart watch which you wear on your wrist to do with a smartphone "under a pillow" or "in a pocket"?
The important thing is *capacitance* which has to change instead of *pressure*. Of course a humid shirt can do this. But I doubt that this
is possible just mechanically in a dry pocket.
[...]
So no, accidental tapping of a touch screen is a thing that happens
easily. Specially when one is half sleep trying to find the phone with
eyes half closed.
Yes, but not *in* a pocket or *under* a pillow, where the touch screen
is physically not reachable since a capacitive touch screen does not
respond to mechanical pressure.
Andy talked about answering a call, the rest of the thread is
mostly about turning off an alarm, i.e. different things with
possibly/likely different behaviour.
On 2024-02-26 08:26, Andy Burns wrote:
Frank Slootweg wrote:
  Moral: When talking about a Google phone, *say* you're talking about a >>> Google phone, because, for all intents and purposes, there - sadly - is
no such thing as 'standard Android'.
I've always bought Nexus/Pixel phones (I inherit a Samsung, which I gave
away) I will always regard Google phones as "stock", anyone who buys a
modified one, it's up to _them_ to cope with the differences ...
It is impossible to buy a google phone, they are way too expensive.
Frank Slootweg wrote:
Andy talked about answering a call, the rest of the thread is
mostly about turning off an alarm, i.e. different things with possibly/likely different behaviour.
Both are examples of actions that may require a swipe, rather than a
press, that's all ...
On 26 Feb 2024 at 12:06:33, "Carlos E.R." <robin_listas@es.invalid> wrote:
On 2024-02-26 08:26, Andy Burns wrote:
Frank Slootweg wrote:
  Moral: When talking about a Google phone, *say* you're talking about a
Google phone, because, for all intents and purposes, there - sadly - is >>>> no such thing as 'standard Android'.
I've always bought Nexus/Pixel phones (I inherit a Samsung, which I gave >>> away) I will always regard Google phones as "stock", anyone who buys a
modified one, it's up to _them_ to cope with the differences ...
It is impossible to buy a google phone, they are way too expensive.
I've only owned Nexus and Pixel phones for many years.
As for expense, I recently bought a Pixel 4 from eBay for �94.
It is in "as-new" condition.
On 2024-02-26 19:59, Arno Welzel wrote:
Carlos E.R., 2024-02-26 12:58:
On 2024-02-25 13:40, Arno Welzel wrote:
Carlos E.R., 2024-02-18 21:01:
On 2024-02-18 20:42, Arno Welzel wrote:[...]
The Real Bev, 2024-02-18 19:22:
Sliding/swiping rather than tapping is NOT intuitive. When I got my >>>>>>> first smartphone I had to return calls because I couldn't answer them :-(
At least tapping the option should be supported as well, even if sliding >>>>>> was the original intended way.
No.
It is intentionally disabled to impede accidental tapping, like with >>>>> phone under the pillow or the pocket.
Capacitive touchscreens can not be "tapped" under a pillow or inside a >>>> pocket since they need physical contact with a finger, so the
capacitance of the sensor grid in the screen will change.
LOL.
No, physics.
My "smart watch" touch screen is often been activated accidentally.
For example, yesterday I was washing up some plates and glasses. My
shirt long sleeves got humid, and it activated my watch repeatedly, and
managed to erase the custom display by another. I had to go into the
phone app and download/upload the custom display that I use, again.
And what exactly has a humid shirt touching the unprotected touch screen
on your smart watch which you wear on your wrist to do with a smartphone
"under a pillow" or "in a pocket"?
That it also reacts to accidental touches and does things.
On 2024-02-25 13:40, Arno Welzel wrote:
Carlos E.R., 2024-02-18 21:01:
On 2024-02-18 20:42, Arno Welzel wrote:[...]
The Real Bev, 2024-02-18 19:22:
Sliding/swiping rather than tapping is NOT intuitive. When I got my >>>>> first smartphone I had to return calls because I couldn't answer them :-( >>>>At least tapping the option should be supported as well, even if sliding >>>> was the original intended way.
No.
It is intentionally disabled to impede accidental tapping, like with
phone under the pillow or the pocket.
Capacitive touchscreens can not be "tapped" under a pillow or inside a
pocket since they need physical contact with a finger, so the
capacitance of the sensor grid in the screen will change.
LOL.
My "smart watch" touch screen is often been activated accidentally.
For example, yesterday I was washing up some plates and glasses. My
shirt long sleeves got humid, and it activated my watch repeatedly, and managed to erase the custom display by another. I had to go into the
phone app and download/upload the custom display that I use, again.
I had to do this many times over the two or three years I own this watch.
On 2024-02-26 19:59, Arno Welzel wrote:[...]
Carlos E.R., 2024-02-26 12:58:
For example, yesterday I was washing up some plates and glasses. My
shirt long sleeves got humid, and it activated my watch repeatedly, and
managed to erase the custom display by another. I had to go into the
phone app and download/upload the custom display that I use, again.
And what exactly has a humid shirt touching the unprotected touch screen
on your smart watch which you wear on your wrist to do with a smartphone
"under a pillow" or "in a pocket"?
That it also reacts to accidental touches and does things.
I have more than once stopped the alarm clock when I wanted to snooze,
by accident when trying to get hold of the phone.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 11:55:56 |
| Calls: | 6,666 |
| Files: | 12,214 |
| Messages: | 5,336,442 |