Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.mobile.android > #149450 > unrolled thread

Recognising (or not) QR codes

Back to article view | Back to comp.mobile.android

Contents

  Recognising (or not) QR codes Chris Green <cl@isbd.net> - 2025-07-01 15:15 +0100
    Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-01 15:39 +0100
      Re: Recognising (or not) QR codes Marion <marion@facts.com> - 2025-07-01 14:57 +0000
        Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-01 16:12 +0100
          Re: Recognising (or not) QR codes Marion <marion@facts.com> - 2025-07-01 15:25 +0000
          Re: Recognising (or not) QR codes Theo <theom+news@chiark.greenend.org.uk> - 2025-07-01 18:07 +0100
    Re: Recognising (or not) QR codes VanguardLH <V@nguard.LH> - 2025-07-01 11:24 -0500
    Re: Recognising (or not) QR codes Arno Welzel <usenet@arnowelzel.de> - 2025-07-01 20:20 +0200
      Re: Recognising (or not) QR codes Chris Green <cl@isbd.net> - 2025-07-01 19:55 +0100
        Re: Recognising (or not) QR codes "Carlos E.R." <robin_listas@es.invalid> - 2025-07-01 21:15 +0200
        Re: Recognising (or not) QR codes VanguardLH <V@nguard.LH> - 2025-07-01 20:03 -0500
          Re: Recognising (or not) QR codes Chris Green <cl@isbd.net> - 2025-07-02 07:09 +0100
            Re: Recognising (or not) QR codes Jörg Lorenz <hugybear@gmx.net> - 2025-07-02 08:48 +0200
              Re: Recognising (or not) QR codes Chris Green <cl@isbd.net> - 2025-07-02 08:07 +0100
                Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-02 09:00 +0100
                  Re: Recognising (or not) QR codes Yusuf Khan <yusuf.khan.nospam@ptcl.net.pk> - 2025-07-02 22:03 +0500
                    Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-02 18:41 +0100
                Re: Recognising (or not) QR codes Jörg Lorenz <hugybear@gmx.net> - 2025-07-02 10:05 +0200
                Re: Recognising (or not) QR codes "Carlos E.R." <robin_listas@es.invalid> - 2025-07-02 12:38 +0200
                  Re: Recognising (or not) QR codes Jörg Lorenz <hugybear@gmx.net> - 2025-07-02 17:00 +0200
                  Re: Recognising (or not) QR codes Frank Slootweg <this@ddress.is.invalid> - 2025-07-02 15:31 +0000
                  Re: Recognising (or not) QR codes Jörg Lorenz <hugybear@gmx.net> - 2025-07-03 15:54 +0200
            Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-02 08:11 +0100
              Re: Recognising (or not) QR codes Marion <marion@facts.com> - 2025-07-02 17:08 +0000
              Re: Recognising (or not) QR codes Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:24 +0200
            Re: Recognising (or not) QR codes VanguardLH <V@nguard.LH> - 2025-07-02 08:24 -0500
              Re: Recognising (or not) QR codes Jörg Lorenz <hugybear@gmx.net> - 2025-07-02 17:02 +0200
                Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-02 18:40 +0100
                Re: Recognising (or not) QR codes "Carlos E.R." <robin_listas@es.invalid> - 2025-07-02 20:11 +0200
                  Re: Recognising (or not) QR codes Frank Slootweg <this@ddress.is.invalid> - 2025-07-03 13:41 +0000
                    Re: Recognising (or not) QR codes "Carlos E.R." <robin_listas@es.invalid> - 2025-07-03 20:13 +0200
                      Re: Recognising (or not) QR codes Frank Slootweg <this@ddress.is.invalid> - 2025-07-03 19:31 +0000
                        Re: Recognising (or not) QR codes "Carlos E.R." <robin_listas@es.invalid> - 2025-07-03 22:35 +0200
                        Re: Recognising (or not) QR codes Arno Welzel <usenet@arnowelzel.de> - 2025-07-06 12:50 +0200
                Re: Recognising (or not) QR codes Allodoxaphobia <trepidation@example.net> - 2025-07-03 12:19 +0000
                  Re: Recognising (or not) QR codes Jörg Lorenz <hugybear@gmx.net> - 2025-07-03 17:22 +0200
                    Re: Recognising (or not) QR codes Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:26 +0200
                      Re: Recognising (or not) QR codes Jörg Lorenz <hugybear@gmx.net> - 2025-07-03 18:17 +0200
                        Re: Recognising (or not) QR codes Arno Welzel <usenet@arnowelzel.de> - 2025-07-06 12:52 +0200
                    Re: Recognising (or not) QR codes Frank Slootweg <this@ddress.is.invalid> - 2025-07-03 19:28 +0000
                      Re: Recognising (or not) QR codes Marion <marion@facts.com> - 2025-07-04 17:20 +0000
                        Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-04 19:47 +0100
                          Re: Recognising (or not) QR codes Marion <marion@facts.com> - 2025-07-04 23:59 +0000
                        Re: Recognising (or not) QR codes Marion <marion@facts.com> - 2025-07-04 18:51 +0000
                        Re: Recognising (or not) QR codes "Carlos E.R." <robin_listas@es.invalid> - 2025-07-05 20:10 +0200
                        Re: Recognising (or not) QR codes Arno Welzel <usenet@arnowelzel.de> - 2025-07-06 12:55 +0200
              Re: Recognising (or not) QR codes Frank Slootweg <this@ddress.is.invalid> - 2025-07-02 15:44 +0000
                Re: Recognising (or not) QR codes Marion <marion@facts.com> - 2025-07-02 17:16 +0000
                Re: Recognising (or not) QR codes VanguardLH <V@nguard.LH> - 2025-07-02 22:18 -0500
                  Re: Recognising (or not) QR codes "Carlos E.R." <robin_listas@es.invalid> - 2025-07-03 11:24 +0200
                  Re: Recognising (or not) QR codes Frank Slootweg <this@ddress.is.invalid> - 2025-07-03 19:08 +0000
          Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-02 08:05 +0100
            Re: Recognising (or not) QR codes Jörg Lorenz <hugybear@gmx.net> - 2025-07-02 10:29 +0200
            Re: Recognising (or not) QR codes "Carlos E.R." <robin_listas@es.invalid> - 2025-07-02 12:43 +0200
              Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-02 11:53 +0100
                Re: Recognising (or not) QR codes Marion <marion@facts.com> - 2025-07-02 17:49 +0000
            Re: Recognising (or not) QR codes Marion <marion@facts.com> - 2025-07-02 17:32 +0000
              Re: Recognising (or not) QR codes Andy Burns <usenet@andyburns.uk> - 2025-07-03 00:34 +0100
        Re: Recognising (or not) QR codes Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:22 +0200

Page 3 of 3 — ← Prev page 1 2 [3]

#149605

On 3 Jul 2025 19:28:20 GMT, Frank Slootweg wrote :


>   (As I wrote,) Our banks, government, medical institutions, etc., etc.
> exactly *do* use QR codes "for financial transactions or other security
> sensitive activities", like login, transaction approval, etc., etc..
> 
>   That QR codes can be use in dangerous ways, does not mean they can
> only be used that way.

I've studied every poster to this newsgroup, to better understand them.

Since I'm always logical and sensible I agree with anyone who makes a
logically sensible statements, such as that Frank just made above.

The fact anyone has to tell this to Joerg tells us something about Joerg.

Jeorg, like VanguardLH/Vanguard, Mayayana/Newayana, JP Gilliver/John
Gilliver, et al., are the type I refer to as "racist" mentalities.

It's not that they're racist per se, but they "think" like racist people do
in that they take one fact and then form the most solidly wrong assessments
about that fact, simply because in some cases QR codes can be malicious.

To them, if one QR code is malicious, all QR codes are malicious.
What type of person thinks that way?

HINT: Look up Myers-Briggs "strongly judgmental" personality types.

[toc] | [prev] | [next] | [standalone]

#149610

Stefan Ram wrote:

>    Letting stuff run without the user doing anything is risky,
>    kind of like letting macros go off in a doc file as soon as you
>    open it. Imagine if every time you downloaded an exe, it just ran
>    right away. That would be a nightmare!
> 
>    So, if that's actually how QR codes work, that needs to be
>    fixed. When you scan a QR, it should just show you the text
>    and let you copy it if you want. If you decide to open it
>    as a URI, that should be your call.

Despite what Vanguard said, I'm not aware of any QR app that 
automatically visits a URL, or connects to a wifi SSID, or calls a phone 
number *just* because you scanned one of those types of QR code ... it's 
akin to saying mice are dangerous because you can click links with a mouse.

[toc] | [prev] | [next] | [standalone]

#149616

On Fri, 4 Jul 2025 19:47:51 +0100, Andy Burns wrote :


>>    So, if that's actually how QR codes work, that needs to be
>>    fixed. When you scan a QR, it should just show you the text
>>    and let you copy it if you want. If you decide to open it
>>    as a URI, that should be your call.
> 
> Despite what Vanguard said, I'm not aware of any QR app that 
> automatically visits a URL, or connects to a wifi SSID, or calls a phone 
> number *just* because you scanned one of those types of QR code ... it's 
> akin to saying mice are dangerous because you can click links with a mouse.

No, out here, mice are dangerous 'cuz they carry the hantavirus, which,
unfortunately for us, has a 1/3rd mortality rate, which is scary. 

Thanks Andy for answering that question since we all learn from each
others, and since I, personally, have little experience with QR codes.

I suspect you "can" set up a QR-code-reading app to "automatically" visit
the URL, but, before I even say it, I realize how absurd that would be in a
typical environment (although in some vetted environments, it could be set
up to automatically visit the site - such as in store-management tasks).

With that in mind, and knowing nothing from Joerg (or Vanguard) is
balanced, I would say what I do on Windows & Android is I set up the
*default* web browser to be something that does NOT auto-visit links.

For example, Tor browser is my default web browser on all platforms.
My Tor browser is set up NOT to connect when it's brought up.

This means no URL has a chance of executing automatically that way.

(Of course, malicious code can choose any browser, I guess, but even then,
I don't have any of the normal browsers on my phone so maybe not for me.)

[toc] | [prev] | [next] | [standalone]

#149611

On 4 Jul 2025 18:30:16 GMT, Stefan Ram wrote :


>   If just one QR code out of a hundred is bad, that means you
>   have a one percent shot at running into a malicious one.
> 
>   Security is all about checking everything in a group, since
>   you never know which ones might be sketchy. Like, here in
>   Berlin, if you show up to a concert with a bag, some guy is
>   going to look through it. Even if hardly any bags have anything
>   they shouldn't, they still have to check every single one.
> 
>   I really don't have any hands-on experience with QR codes, and
>   I barely know how they work, but I figure they just hold URIs
>   that get opened up. That would make them active content. 
> 
>   Letting stuff run without the user doing anything is risky,
>   kind of like letting macros go off in a doc file as soon as you
>   open it. Imagine if every time you downloaded an exe, it just ran
>   right away. That would be a nightmare! 
> 
>   So, if that's actually how QR codes work, that needs to be
>   fixed. When you scan a QR, it should just show you the text
>   and let you copy it if you want. If you decide to open it
>   as a URI, that should be your call.

Your example is spot on the money, as is your approach to security.
And your point of view seems to me to be sensibly logical & reasonable.

While my initial posts to this thread prove I don't usually deal with QR
codes, many people already mentioned in this thread that if the QR code
resolves to a URL, it's no different than any other URL on your system.

They all mentioned to Joerg that whether or not that URL is "active"
depends on how the user has set up their phone once it resolves the URL.

Does the phone ask the user to manually approve "going to" that URL?
Or does the phone just automatically "go to" that URL?

I don't know really, as I said from the start I was only helping out the OP
by suggesting QR code readers that I had tested long ago & didn't fail.

I suspect it depends on how the user sets up the system to act on URLs.
But I'll let those who actually use QR codes in daily use answer that.

[toc] | [prev] | [next] | [standalone]

#149632

On 2025-07-04 20:30, Stefan Ram wrote:

...

>    I really don't have any hands-on experience with QR codes, and
>    I barely know how they work, but I figure they just hold URIs
>    that get opened up. That would make them active content.

They hold text. And that text can be anything, including an URL.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#149642

Stefan Ram, 2025-07-04 20:30:

> Marion <marion@facts.com> wrote or quoted:
>> To them, if one QR code is malicious, all QR codes are malicious.
> 
>   If just one QR code out of a hundred is bad, that means you
>   have a one percent shot at running into a malicious one.

What is a "malicious QR code"? The same as a "malicious link"?

Well - if you get a phishing mail which contains a link which claims to
bring you to your online banking account, you should not trust that, of
course.

But does this means, that links in general are malicious?

>   Security is all about checking everything in a group, since
>   you never know which ones might be sketchy. Like, here in
>   Berlin, if you show up to a concert with a bag, some guy is
>   going to look through it. Even if hardly any bags have anything
>   they shouldn't, they still have to check every single one.

This is not only the case in Berlin but most likely in *every* big
concert where they have higher security.



-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#149521

VanguardLH <V@nguard.lh> wrote:
> Chris Green <cl@isbd.net> wrote:
> 
> > OP here. Yes, I've installed Google Lens (easiest option) and now I
> > can scan QR codes.
> 
> I have an 8-year old old Android 8.0.0 phone that has the Google search
> bar as a widget on the home screen.  At some point, it got updated to
> add a camera icon.  I tap on that icon, and use it to take a snapshot of
> something.  I've used it to identify plants.  It can also read QR codes.
> 
> My concern is a QR code can contain a URL.  Those are sometimes used to
> prevent typos by users to define a URL to a web site, or, I suppose, to
> add convenience of not having to enter a string into an address bar of a
> web browser.  In any case, the QR scanner could just open a web browser
> to the URL without prompting the user to tell them to where the QR code
> points.  You could end up going somewhere you don't want to go, or
> somewhere malicious.  QR codes can be produced by anyone, and I've seen
> them online, too.  

  Why the FUD!? *Does* your (built-in) camera app/icon "just open a web
browser to the URL without prompting"? If so, name it (with details) and
get rid of it.

> I use a QR scanner app that shows the content of the QR code BEFORE ever
> going anywhere; i.e., you get told what is the content, and if a URL
> then you see it before you choose to use it.  Since the app focuses on
> scanning QR codes instead of taking pictures of anything and then trying
> to identify what's in the pic, it auto-focuses on a QR image.  I just
> tried it: load the QR scanner, point the camera at something with a QR
> code image, and the app detects where is the image, locks in on it, and
> captures it.  Then it shows the content.  Makes it easier to get the
> phone at the right distance for its camera to get the image in focus,
> and then takes a pic without me having to move the phone a bit while my
> fingers manage to tap a button to take a pic.  Auto-locking onto the QR
> image also lets me know it found one rather than taking a pic and hoping
> the QR image was fully within view and right-distanced to be in focus.

  Nothing special. The (Samsung) Camera app of my Samsung Galaxy A51
(Android 51) also does all of that.

> While Google Lens got embedded into the Google search bar widget, so
> that is also usable for scanning QR codes, and taking pics of other
> stuff to identify, a dedicated QR scan app might be more convenient, and
> perhaps safer.

  I think for the majority of people, the built-in Camera app of their
phone will do everything they need and will be safe, because QR scanning
is a basic functionality since many years.

[...]

[toc] | [prev] | [next] | [standalone]

#149524

On 2 Jul 2025 15:44:49 GMT, Frank Slootweg wrote :


>   Why the FUD!? *Does* your (built-in) camera app/icon "just open a web
> browser to the URL without prompting"? If so, name it (with details) and
> get rid of it.

I agree with anyone who says something sensible, no matter his past record.

And, I've studied EVERYONE on this ng for years, and you hit Vanguard on
the nose by saying he's unnecessarily sowing FUD out of his own fears.

There's nothing wrong with being fearful (it's actually good in many ways),
but Vanguard (like Mayayana and John P. Gilliver) is "racist" in mindset).

I say that purposefully to make the strong point, not that he's against any
race of people, but his mind is EXTREMELY strongly biased toward a SINGLE
datapoint from which he invokes a plethora of his fears and worries.

Vanguard remains ignorant of the full and complete pictures.

Most importantly, Vanguard is completely ignorant that he's ignorant.
Just as Mayayana (aka Newayana) and JP Gilliver (aka John P. Gilliver).

Each of them is racist in that they conclude everything from a single
datum. Which means they're always wrong. And they don't know it.

Hence, Vanguard won't take in the data that Frank so correctly just
supplied.

Which means Vanguard will remain wrong, but convinced he's right.
-- 
And yes, I know the ignorant trolls will respond that it's me.
But all they see are words - the trolls don't actually undersatnd.
I do understand Vanguard. Very well. He'll be ignorant forever.
It's who he is. He can't NOT be a racist in the way he thinks.

[toc] | [prev] | [next] | [standalone]

#149546

Frank Slootweg <this@ddress.is.invalid> wrote:

> VanguardLH <V@nguard.lh> wrote:
>> Chris Green <cl@isbd.net> wrote:
>> 
>>> OP here. Yes, I've installed Google Lens (easiest option) and now I
>>> can scan QR codes.
>> 
>> I have an 8-year old old Android 8.0.0 phone that has the Google search
>> bar as a widget on the home screen.  At some point, it got updated to
>> add a camera icon.  I tap on that icon, and use it to take a snapshot of
>> something.  I've used it to identify plants.  It can also read QR codes.
>> 
>> My concern is a QR code can contain a URL.  Those are sometimes used to
>> prevent typos by users to define a URL to a web site, or, I suppose, to
>> add convenience of not having to enter a string into an address bar of a
>> web browser.  In any case, the QR scanner could just open a web browser
>> to the URL without prompting the user to tell them to where the QR code
>> points.  You could end up going somewhere you don't want to go, or
>> somewhere malicious.  QR codes can be produced by anyone, and I've seen
>> them online, too.  
> 
>   Why the FUD!? *Does* your (built-in) camera app/icon "just open a web
> browser to the URL without prompting"? If so, name it (with details) and
> get rid of it.
> 
>> I use a QR scanner app that shows the content of the QR code BEFORE ever
>> going anywhere; i.e., you get told what is the content, and if a URL
>> then you see it before you choose to use it.  Since the app focuses on
>> scanning QR codes instead of taking pictures of anything and then trying
>> to identify what's in the pic, it auto-focuses on a QR image.  I just
>> tried it: load the QR scanner, point the camera at something with a QR
>> code image, and the app detects where is the image, locks in on it, and
>> captures it.  Then it shows the content.  Makes it easier to get the
>> phone at the right distance for its camera to get the image in focus,
>> and then takes a pic without me having to move the phone a bit while my
>> fingers manage to tap a button to take a pic.  Auto-locking onto the QR
>> image also lets me know it found one rather than taking a pic and hoping
>> the QR image was fully within view and right-distanced to be in focus.
> 
>   Nothing special. The (Samsung) Camera app of my Samsung Galaxy A51
> (Android 51) also does all of that.
> 
>> While Google Lens got embedded into the Google search bar widget, so
>> that is also usable for scanning QR codes, and taking pics of other
>> stuff to identify, a dedicated QR scan app might be more convenient, and
>> perhaps safer.
> 
>   I think for the majority of people, the built-in Camera app of their
> phone will do everything they need and will be safe, because QR scanning
> is a basic functionality since many years.
> 
> [...]

Not in my camera app ... of many years.  I don't have Android 11, and
whatever phone and model the OP has.  Mine is an old Android 8.0.0
phone, and, nope, no QR code scanning it the embedded camera app.  And
why I mentioned getting a QR scanning app.  Android 8.0 was released
back in 2017.

The OP's camera app also doesn't, according to his description, include
QR scanning, and he's on Android 11 which was released in 2020.  Doesn't
seem to be the pervasive feature you think it is.

Neither the OP or I have a Samsung phone.  What you experience with
Samsung is not incumbent on every other phone brand and model.

My LG phone has not only the navbar at the bottom, but a 2nd navbar (aka
shortcut bar) at the top).  That is also not prevalent amongst other
phones back then, or ever since.

[toc] | [prev] | [next] | [standalone]

#149549

On 2025-07-03 05:18, VanguardLH wrote:
> Frank Slootweg <this@ddress.is.invalid> wrote:
> 
>> VanguardLH <V@nguard.lh> wrote:
>>> Chris Green <cl@isbd.net> wrote:

...

>>    I think for the majority of people, the built-in Camera app of their
>> phone will do everything they need and will be safe, because QR scanning
>> is a basic functionality since many years.
>>
>> [...]
> 
> Not in my camera app ... of many years.  I don't have Android 11, and
> whatever phone and model the OP has.  Mine is an old Android 8.0.0
> phone, and, nope, no QR code scanning it the embedded camera app.  And
> why I mentioned getting a QR scanning app.  Android 8.0 was released
> back in 2017.
> 
> The OP's camera app also doesn't, according to his description, include
> QR scanning, and he's on Android 11 which was released in 2020.  Doesn't
> seem to be the pervasive feature you think it is.

You are correct, I have a friend that asked about this, her phone can 
not point and click on a QR. I tried to install something, I couldn't. I 
recommended to think of a newer phone, it is not the only thing that 
doesn't work.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#149580

VanguardLH <V@nguard.lh> wrote:
> Frank Slootweg <this@ddress.is.invalid> wrote:
[...]
> >   I think for the majority of people, the built-in Camera app of their
> > phone will do everything they need and will be safe, because QR scanning
> > is a basic functionality since many years.
> > 
> > [...]
> 
> Not in my camera app ... of many years.  I don't have Android 11, and
> whatever phone and model the OP has.  Mine is an old Android 8.0.0
> phone, and, nope, no QR code scanning it the embedded camera app.  And
> why I mentioned getting a QR scanning app.  Android 8.0 was released
> back in 2017.

  Yes, I know you've an 'old' phone. Note that I said "for the majority
of people". The majority of people will have new(er) phones.

> The OP's camera app also doesn't, according to his description, include
> QR scanning, and he's on Android 11 which was released in 2020.  Doesn't
> seem to be the pervasive feature you think it is.

  Yes, Carlos and I already addressed that. Sad that Android 11 is
'old', but it is. Even my Android 13 phone is 'old'.

> Neither the OP or I have a Samsung phone.  What you experience with
> Samsung is not incumbent on every other phone brand and model.

  Carlos mentioned that his Moto phone (phones?) also has QR scanning
capability and so have several others for their phones.

  Bottom line: No QR scanning capability is the odd one out, not the
common situation.

[toc] | [prev] | [next] | [standalone]

#149496

VanguardLH wrote:

> The circle-to-search feature may not be available in your Android
> version.  I didn't bother to search in which Android version it became
> available, because a cursory search shows it is apparently inherent to
> the brand and model of phone you have.

I think circle-to-search was exclusive to Samsung for a few weeks, then 
rolled-down to flagship Pixels and later to all Pixels, presumably it's 
on just about all devices now?

[toc] | [prev] | [next] | [standalone]

#149502

On 02.07.25 09:05, Andy Burns wrote:
> VanguardLH wrote:
> 
>> The circle-to-search feature may not be available in your Android
>> version.  I didn't bother to search in which Android version it became
>> available, because a cursory search shows it is apparently inherent to
>> the brand and model of phone you have.
> 
> I think circle-to-search was exclusive to Samsung for a few weeks, then
> rolled-down to flagship Pixels and later to all Pixels, presumably it's
> on just about all devices now?

It is not a circle, it is a rectangle with rounded corners and is 
present since almost 15 years. It is not a Samsung-invention.


-- 
"Roma locuta, causa finita." (Augustinus)

[toc] | [prev] | [next] | [standalone]

#149508

On 2025-07-02 09:05, Andy Burns wrote:
> VanguardLH wrote:
> 
>> The circle-to-search feature may not be available in your Android
>> version.  I didn't bother to search in which Android version it became
>> available, because a cursory search shows it is apparently inherent to
>> the brand and model of phone you have.
> 
> I think circle-to-search was exclusive to Samsung for a few weeks, then 
> rolled-down to flagship Pixels and later to all Pixels, presumably it's 
> on just about all devices now?
> 

No, my phone does not support it (Motorola G52).

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#149510

Carlos E.R. wrote:

> Andy Burns wrote:
> 
>> I think circle-to-search was exclusive to Samsung for a few weeks, 
>> then rolled-down to flagship Pixels and later to all Pixels, 
>> presumably it's on just about all devices now?
> 
> No, my phone does not support it (Motorola G52).
"exclusively available on the Edge 50 Ultra and the Razr 50 series"

So moto are using it to "push" certain models for a while, like Samsung 
did ...

[toc] | [prev] | [next] | [standalone]

#149531

On Wed, 2 Jul 2025 11:53:18 +0100, Andy Burns wrote :


>> Andy Burns wrote:
>> 
>>> I think circle-to-search was exclusive to Samsung for a few weeks, 
>>> then rolled-down to flagship Pixels and later to all Pixels, 
>>> presumably it's on just about all devices now?
>> 
>> No, my phone does not support it (Motorola G52).
> "exclusively available on the Edge 50 Ultra and the Razr 50 series"
> 
> So moto are using it to "push" certain models for a while, like Samsung 
> did ...

Circle-to-Search is sufficiently powerful and ubiquitous and well supported
and useful and an AI hook into the phone, that I opened a separate thread.
 Subject: Do you use "Circle to Search" and what do you use it for?
 Date: Wed, 2 Jul 2025 
 (archives aren't updated yet for a link)

Having gone from never having heard of it moments ago to knowing something
about it (after running a search which the Apple trolls can never do), I
think it will be on every phone moving forward since Google wants it to be.

I suspect it's an entrée point (or, in French, point d'entrée) for AI.
So Google wants it bad(ly) on every phone.

[toc] | [prev] | [next] | [standalone]

#149525

On Wed, 2 Jul 2025 08:05:23 +0100, Andy Burns wrote :


>> The circle-to-search feature may not be available in your Android
>> version.  I didn't bother to search in which Android version it became
>> available, because a cursory search shows it is apparently inherent to
>> the brand and model of phone you have.
> 
> I think circle-to-search was exclusive to Samsung for a few weeks, then 
> rolled-down to flagship Pixels and later to all Pixels, presumably it's 
> on just about all devices now?

Damn you Andy. Always saying fancy 'tings that I never 'hoid of b'fore.
You trying t' make me feel styupid or sumphun?
   
*Circle-to-Search*
      WTF?

I don't even know what "circle to search" is, but it appears Vanguard
believes it's device-specific, while Andy provided a more detailed, phased
rollout history. That's classic for both, in that Vanguard is always making
conclusions based on only one datapoint, while Andy is more balanced and
well read.

But still, I don't even know what "circle to search" even is.... Google...
google...google....  OK. 

Circle to search debuted on Samsung Galaxy S24 series in mid-January 2024.

It rolled out to Google's flagship phones, the Pixel 8 and Pixel 8 Pro by
the end of January 2024 (which we could consider almost simultaneous).

Within months, it had expanded to older Samsung and Google devices,
including the Pixel 7, 7 Pro, 7a, and even some Pixel 6 series phones, as
well as various Samsung Galaxy S23, S22, S21 series, Galaxy Z Fold/Flip
devices, and some A-series phones and tablets. It has already rolled out to
some phones from Honor, Xiaomi, Motorola, OnePlus, Nothing, and TECNO.
Google had a stated goal to bring the feature to 200 million devices by the
end of 2024.

OK. It's big. But why haven't I ever heard of it? Am I styupid or sumphun?
Since I am not an Apple troll, so I know how to hit a search button,
apparently you draw a circle with your big fat finger around an object or
image or you scribble over something or you tap on an item as a "gesture"
and then Google's search results appear at the bottom of the screen
providing information about what you've selected to search for.

Ug. Yuck. I removed Google search from my phone from day one. Aurgh. 
But still... why don't I see it on my phone?

Again, I'm not an Apple troll (nor am I Carlos who can't search either), so
I can search for things first, I see the Samsung A-series doesn't generally
get AI powered features. So circle-to-search (by implication) is an AI
feature perhaps?... hmm... 

Furthermore, Circle-to-Search is, for Samsung, a One UI 6.1 and up feature,
which I most likely don't have (I use Nova launcher but the One UI is still
on the phone). Besides, I'm stuck on Android 13 and Android 13 is older
than One UI 6.1 (so I'd have to get it with effort - and I won't bother).

Besides, even if I did, my phone is mostly degoogled so the Google Search
assistant doesn't exist. But, for others to know what I've learned,
apparently a crucial requirement for Circle to Search is that Google must
be set as your default digital assistant app.

Interestingly, Google specifically blocks the Circle-to-Search feature if a
non-Google app is set as the default assistant.

In summary, Circle-to-Search seems like a feature rolled out since January
of 2024 to new'ish high-end'ish phones where it's apparently an AI that
works on finger gestures (you don't wanna know what mine will be). 

Thanks for bringing Circle-to-Search to the fore!
I learn from others.

[toc] | [prev] | [next] | [standalone]

#149545

Marion wrote:

> In summary, Circle-to-Search seems like a feature rolled out since January
> of 2024 to new'ish high-end'ish phones where it's apparently an AI that
> works on finger gestures (you don't wanna know what mine will be).

Yep, it was all the rage last year, but it ain't all that ... take a 
photo of something, highlight it, it'll tell you what it is, and take 
you to a webshop where you can buy one of your own...

[toc] | [prev] | [next] | [standalone]

#149564

Chris Green, 2025-07-01 20:55:

> Arno Welzel <usenet@arnowelzel.de> wrote:
>> Chris Green, 2025-07-01 16:15:
>>
>>> I have an Umidigi Bison phone running Android running Android 11, it
>>> works OK with most of the things I want it to do.
>>>
>>> However it never seems to want to recognise QR codes, is there some
>>> magic technique for doing this or are they just rubbish?
>>
>> What is "it"? The camera app? A dedicated QR code scanner app - and yes,
>> which one?
>>
> The camera app I assume, the thing that takes pictures of my knees by
> mistake! :-)
> 
> All the promoters of QR codes just say 'scan the QR code' and assume
> all the magic will then ensue.

Yes, they assume, all camera apps recognize QR codes as well - but this
is not the case. If your camera app does not support this, try a
dedicated QR code scanner app like this:

<https://play.google.com/store/apps/details?id=de.markusfisch.android.binaryeye>

This works quite well, is for free, supports not only QR codes but many
other code formats as well and you can even generate your own codes if
needed.

-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | comp.mobile.android

csiph-web