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

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

Can't reach files on my smartphone anymore

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

Contents

  Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-05 08:33 +0100
    Re: Can't reach files on my smartphone anymore "Carlos E.R." <robin_listas@es.invalid> - 2025-12-05 11:14 +0100
      Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-05 11:30 +0100
        Re: Can't reach files on my smartphone anymore "Carlos E.R." <robin_listas@es.invalid> - 2025-12-05 11:37 +0100
          Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-05 12:55 +0100
            Re: Can't reach files on my smartphone anymore Marian <marianjones@helpfulpeople.com> - 2025-12-05 06:38 -0700
              Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-05 15:26 +0100
    Re: Can't reach files on my smartphone anymore Frank Slootweg <this@ddress.is.invalid> - 2025-12-05 13:13 +0000
      Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-05 15:35 +0100
        Re: Can't reach files on my smartphone anymore "s|b" <me@privacy.invalid> - 2025-12-05 19:15 +0100
          Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-06 10:30 +0100
            Re: Can't reach files on my smartphone anymore Siard <saylor259@mailbox.org> - 2025-12-06 11:58 +0100
              Re: Can't reach files on my smartphone anymore "s|b" <me@privacy.invalid> - 2025-12-06 14:46 +0100
                Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-06 15:27 +0100
                Re: Can't reach files on my smartphone anymore Frank Slootweg <this@ddress.is.invalid> - 2025-12-06 16:47 +0000
                  Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-06 20:41 +0100
                    Re: Can't reach files on my smartphone anymore Frank Slootweg <this@ddress.is.invalid> - 2025-12-06 20:20 +0000
                    Re: Can't reach files on my smartphone anymore "Carlos E.R." <robin_listas@es.invalid> - 2025-12-07 21:24 +0100
                      Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-08 20:31 +0100
                        Re: Can't reach files on my smartphone anymore "Carlos E.R." <robin_listas@es.invalid> - 2025-12-09 16:12 +0100
                          Re: Can't reach files on my smartphone anymore Frank Slootweg <this@ddress.is.invalid> - 2025-12-09 16:35 +0000
                            Re: Can't reach files on my smartphone anymore "Carlos E.R." <robin_listas@es.invalid> - 2025-12-10 00:05 +0100
                              Re: Can't reach files on my smartphone anymore Marian <marianjones@helpfulpeople.com> - 2025-12-09 19:22 -0700
                  Re: Can't reach files on my smartphone anymore "s|b" <me@privacy.invalid> - 2025-12-06 21:18 +0100
                  Re: Can't reach files on my smartphone anymore Java Jive <java@evij.com.invalid> - 2025-12-07 09:54 +0000
            Re: Can't reach files on my smartphone anymore "s|b" <me@privacy.invalid> - 2025-12-06 14:49 +0100
              Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-06 15:26 +0100
                Re: Can't reach files on my smartphone anymore "s|b" <me@privacy.invalid> - 2025-12-06 16:17 +0100
                  Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-06 20:43 +0100
                    Re: Can't reach files on my smartphone anymore "s|b" <me@privacy.invalid> - 2025-12-06 21:21 +0100
                      Re: Can't reach files on my smartphone anymore Frank Slootweg <this@ddress.is.invalid> - 2025-12-06 20:52 +0000
                        Re: Can't reach files on my smartphone anymore "s|b" <me@privacy.invalid> - 2025-12-07 14:49 +0100
    Re: Can't reach files on my smartphone anymore croy <croy@spam.invalid.net> - 2025-12-05 08:44 -0800
      Re: Can't reach files on my smartphone anymore Java Jive <java@evij.com.invalid> - 2025-12-05 17:40 +0000
        Re: Can't reach files on my smartphone anymore Chris Green <cl@isbd.net> - 2025-12-05 17:52 +0000
          Re: Can't reach files on my smartphone anymore Frank Slootweg <this@ddress.is.invalid> - 2025-12-06 16:49 +0000
            Re: Can't reach files on my smartphone anymore Chris Green <cl@isbd.net> - 2025-12-06 17:43 +0000
              Re: Can't reach files on my smartphone anymore Andy Burns <usenet@andyburns.uk> - 2025-12-06 18:01 +0000
                Re: Can't reach files on my smartphone anymore Chris Green <cl@isbd.net> - 2025-12-06 18:50 +0000
                  Re: Can't reach files on my smartphone anymore Andy Burns <usenet@andyburns.uk> - 2025-12-06 19:28 +0000
                  Re: Can't reach files on my smartphone anymore Frank Slootweg <this@ddress.is.invalid> - 2025-12-06 20:14 +0000
              Re: Can't reach files on my smartphone anymore Frank Slootweg <this@ddress.is.invalid> - 2025-12-06 20:06 +0000
        Re: Can't reach files on my smartphone anymore "R.Wieser" <address@is.invalid> - 2025-12-07 12:26 +0100
          Re: Can't reach files on my smartphone anymore "Carlos E.R." <robin_listas@es.invalid> - 2025-12-07 21:33 +0100
            Re: Can't reach files on my smartphone anymore Andy Burns <usenet@andyburns.uk> - 2025-12-08 01:25 +0000
              Re: Can't reach files on my smartphone anymore "R.Wieser" <address@is.invalid> - 2025-12-08 08:53 +0100
              Re: Can't reach files on my smartphone anymore Chris <ithinkiam@gmail.com> - 2025-12-08 08:20 +0000
              Android auto [Was: Can't reach files on my smartphone anymore] "Carlos E.R." <robin_listas@es.invalid> - 2025-12-09 16:23 +0100
                Re: Android auto [Was: Can't reach files on my smartphone anymore] Jörg Lorenz <hugybear@gmx.net> - 2025-12-09 17:07 +0100
      Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-06 10:31 +0100
      Re: Can't reach files on my smartphone anymore Andy Burns <usenet@andyburns.uk> - 2025-12-06 14:07 +0000
    Re: Can't reach files on my smartphone anymore Stan Brown <someone@example.com> - 2025-12-05 11:42 -0800
      Re: Can't reach files on my smartphone anymore Marian <marianjones@helpfulpeople.com> - 2025-12-05 16:01 -0700
      Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-06 10:32 +0100
        Re: Can't reach files on my smartphone anymore Marian <marianjones@helpfulpeople.com> - 2025-12-07 19:44 -0700
          Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-10 09:15 +0100
            Re: Can't reach files on my smartphone anymore Marian <marianjones@helpfulpeople.com> - 2025-12-10 14:26 -0700
              Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-11 09:28 +0100
                Re: Can't reach files on my smartphone anymore Jim Jackson <jj@franjam.org.uk> - 2025-12-11 15:46 +0000
                  Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-11 20:37 +0100
                    Re: Can't reach files on my smartphone anymore Jim Jackson <jj@franjam.org.uk> - 2025-12-11 19:48 +0000
                Re: Can't reach files on my smartphone anymore Frank Slootweg <this@ddress.is.invalid> - 2025-12-11 16:17 +0000
                  Re: Can't reach files on my smartphone anymore Fokke Nauta <fnauta@solfon.nl> - 2025-12-11 20:40 +0100
                    Re: Can't reach files on my smartphone anymore Marian <marianjones@helpfulpeople.com> - 2025-12-11 19:31 -0700

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

#151838

Carlos E.R. <robin_listas@es.invalid> wrote:
> On 2025-12-08 20:31, Fokke Nauta wrote:
> > On 07/12/2025 21:24, Carlos E.R. wrote:
> >> On 2025-12-06 20:41, Fokke Nauta wrote:
[...]
> >>> Hi Frank,
> >>>
> >>> I did it and it worked! Fantastic! Haven't got a clue as to how you 
> >>> know this, but I learned this again.
> >>> Thanks very much.
> >>
> >> What was it set to?
> > 
> > Look at the message of Frank Slootweg.
> 
> I did, no answer found there.

  I think you're asking: What was the 'Default USB configuration'
setting in 'Developer options' set to? If so, it was not set to
anything, i.e.  all the five choices have an empty circle in front of
them. Only if you tap on one of the choices, the choice is selected and
the empty grey circle changes to a blue circle with a blue dot in the
white part.

  So apparently there is also a system default which is used if the
'Default USB configuration' is not set. That system default is 'Charging
phone only', i.e. the safe default.

  BUT, if you select one of the 'Default USB configuration', you can not
get back to five unselected choices, always one of them will be
selected, even if yoy turn off 'Developer options' and later turn it
back on. So for answering your question, I (or you? :-)) have ruined my
phone! :-)

  N.B. All of this on my Samsung Galaxy A56 (Android 16) phone.

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

#151840

On 2025-12-09 17:35, Frank Slootweg wrote:
> Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 2025-12-08 20:31, Fokke Nauta wrote:
>>> On 07/12/2025 21:24, Carlos E.R. wrote:
>>>> On 2025-12-06 20:41, Fokke Nauta wrote:
> [...]
>>>>> Hi Frank,
>>>>>
>>>>> I did it and it worked! Fantastic! Haven't got a clue as to how you
>>>>> know this, but I learned this again.
>>>>> Thanks very much.
>>>>
>>>> What was it set to?
>>>
>>> Look at the message of Frank Slootweg.
>>
>> I did, no answer found there.
> 
>    I think you're asking: What was the 'Default USB configuration'
> setting in 'Developer options' set to? 

Rather, what did his phone say that setting was set to when he opened 
it, before changing it to 'Transferring files / Android Auto'

> If so, it was not set to
> anything, i.e.  all the five choices have an empty circle in front of
> them. Only if you tap on one of the choices, the choice is selected and
> the empty grey circle changes to a blue circle with a blue dot in the
> white part.

Ok, sounds reasonable.

> 
>    So apparently there is also a system default which is used if the
> 'Default USB configuration' is not set. That system default is 'Charging
> phone only', i.e. the safe default.

I think mine is "asking", and after a small time it settles on "charging".

> 
>    BUT, if you select one of the 'Default USB configuration', you can not
> get back to five unselected choices, always one of them will be
> selected, even if yoy turn off 'Developer options' and later turn it
> back on. So for answering your question, I (or you? :-)) have ruined my
> phone! :-)

{chuckle} :-}

No, I did not try on my phone, it is working ok.

> 
>    N.B. All of this on my Samsung Galaxy A56 (Android 16) phone.


-- 
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;

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

#151850

>>> I did, no answer found there.
>> 
>>    I think you're asking: What was the 'Default USB configuration'
>> setting in 'Developer options' set to? 
> 
> Rather, what did his phone say that setting was set to when he opened 
> it, before changing it to 'Transferring files / Android Auto'a

Hi Carlos,

To help out, I went to my old logs and this is what mine was set to:
 <https://i.postimg.cc/JnDTWH9M/usb01.jpg> USB default settings

>> If so, it was not set to
>> anything, i.e.  all the five choices have an empty circle in front of
>> them. Only if you tap on one of the choices, the choice is selected and
>> the empty grey circle changes to a blue circle with a blue dot in the
>> white part.
> 
> Ok, sounds reasonable.

I have to admit, I've always turned Developer Options on as one of the very
first things I do on any phone, but its "organization" is really messy.
  <https://i.postimg.cc/9M0Tqzm6/adb01.jpg> 

>>    So apparently there is also a system default which is used if the
>> 'Default USB configuration' is not set. That system default is 'Charging
>> phone only', i.e. the safe default.
> 
> I think mine is "asking", and after a small time it settles on "charging".

Mine does both charging & file transfer at the same time as far as I know.

>>    BUT, if you select one of the 'Default USB configuration', you can not
>> get back to five unselected choices, always one of them will be
>> selected, even if yoy turn off 'Developer options' and later turn it
>> back on. So for answering your question, I (or you? :-)) have ruined my
>> phone! :-)
> 
> {chuckle} :-}
> 
> No, I did not try on my phone, it is working ok.

There are a ton of options in Developer Options.
 <https://i.postimg.cc/28324Hdp/devopt01.jpg> Settings > Developer options
 <https://i.postimg.cc/PrqFSfjR/devopt02.jpg> Useful devoptions switches
 <https://i.postimg.cc/7LzRSBkP/devopt03.jpg> More devoptions switches
 <https://i.postimg.cc/DZFxLn65/devopt04.jpg> Even more devoptions switches

Probably some of the most useful (besides USB Debugging) are the 
ability to randomize the MAC upon every connection (not just every AP).

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

#151750

On 6 Dec 2025 16:47:30 GMT, Frank Slootweg wrote:

>   And, as 's|b' mentioned, you can set the 'Default USB configuration'
> to 'Transferring files / Android Auto'.

So I remembered correctly! (-:

-- 
s|b

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

#151768

On 2025-12-06 16:47, Frank Slootweg wrote:
> 
>    In order to 'find' the 'Developer options', they have to be *enabled*
> first:


Yes, done already.

>    And, as 's|b' mentioned, you can set the 'Default USB configuration'
> to 'Transferring files / Android Auto'.
Now done also ... Somehow I missed 's|b's explanation, so thanks to both 
of you.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

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

#151723

On Sat, 6 Dec 2025 10:30:35 +0100, Fokke Nauta wrote:

> I haven't found Ontwikkelaarsopties.

You can open Instellingen and then type something to search for. Have
you done this or did you go through all the settings yourself?

It should be under 'Instellingen > Systeem'.

-- 
s|b

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

#151726

On 06/12/2025 14:49, s|b wrote:
> On Sat, 6 Dec 2025 10:30:35 +0100, Fokke Nauta wrote:
> 
>> I haven't found Ontwikkelaarsopties.
> 
> You can open Instellingen and then type something to search for. Have
> you done this or did you go through all the settings yourself?
> 
> It should be under 'Instellingen > Systeem'.
> 

Under Instellingen there is no Systeem or Ontwikkelaarsoptie.

Fokke

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

#151729

On Sat, 6 Dec 2025 15:26:51 +0100, Fokke Nauta wrote:

> Under Instellingen there is no Systeem or Ontwikkelaarsoptie.

<https://www.samsung.com/uk/support/mobile-devices/how-do-i-turn-on-the-developer-options-menu-on-my-samsung-galaxy-device/>

-- 
s|b

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

#151747

On 06/12/2025 16:17, s|b wrote:
> On Sat, 6 Dec 2025 15:26:51 +0100, Fokke Nauta wrote:
> 
>> Under Instellingen there is no Systeem or Ontwikkelaarsoptie.
> 
> <https://www.samsung.com/uk/support/mobile-devices/how-do-i-turn-on-the-developer-options-menu-on-my-samsung-galaxy-device/>
> 

Frank Slootweg already adviced me to do this.
And it worked!

Fokke

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

#151752

On Sat, 6 Dec 2025 20:43:30 +0100, Fokke Nauta wrote:

> On 06/12/2025 16:17, s|b wrote:
>
> > <https://www.samsung.com/uk/support/mobile-devices/how-do-i-turn-on-the-developer-options-menu-on-my-samsung-galaxy-device/>
> > 
 
> Frank Slootweg already adviced me to do this.
> And it worked!

Yeah, after I posted this link he finished the job. Glad it's working
for you.

-- 
s|b

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

#151756

s|b <me@privacy.invalid> wrote:
> On Sat, 6 Dec 2025 20:43:30 +0100, Fokke Nauta wrote:
> 
> > On 06/12/2025 16:17, s|b wrote:
> >
> > > <https://www.samsung.com/uk/support/mobile-devices/how-do-i-turn-on-the-developer-options-menu-on-my-samsung-galaxy-device/>
> > > 
>  
> > Frank Slootweg already adviced me to do this.
> > And it worked!
> 
> Yeah, after I posted this link he finished the job. Glad it's working
> for you.

  I either missed your link or your post didn't 'register' in my brain.

  As I mentioned to Fokke, I just did a Google search on 'samsung
developer options" and the Google 'AI Overview' gave the answer and was
much shorter (only 4 lines) than the Samsung article.

  So it was a combined effort, you pointed to the Developer options and
the likelyhood of a USB setting in them and I finished the job with the
specifics of the latter (and a duplication of the former),

  Good on us! :-)

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

#151774

On 6 Dec 2025 20:52:32 GMT, Frank Slootweg wrote:

>   I either missed your link or your post didn't 'register' in my brain.
> 
>   As I mentioned to Fokke, I just did a Google search on 'samsung
> developer options" and the Google 'AI Overview' gave the answer and was
> much shorter (only 4 lines) than the Samsung article.

Should have done that myself. I just started looking for the manual on
the support pages of samsung.com.

Not a big fan of Samsug BTW, I hate how they change everything to
Samsung apps. In Belgium we use the Itsme app a lot for access to
government sites and Samsung just breaks this, because they have their
own browser 'Samsung Internet'. When people come and ask me I have to
change the browser to Google Chrome.
 
>   So it was a combined effort, you pointed to the Developer options and
> the likelyhood of a USB setting in them and I finished the job with the
> specifics of the latter (and a duplication of the former),
> 
>   Good on us! :-)

Yay! (-:

-- 
s|b

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

#151677

On Fri, 5 Dec 2025 08:33:17 +0100, Fokke Nauta <fnauta@solfon.nl> wrote:

>Hi all,
>
>I have a Samsung A53 with Android 16. I have a pc with Windows 10 Pro. 
>When I connect a cable between the pc and my phone, I could see the 
>phone on my pc and open it. I could see all the folders and pictures. 
>Easy to download them.
>But my phone got an update. And now it has changed. When I connect the 
>cable, I get a message on my phone: Tap the USB notification to use USB 
>for transferring files.
>But that's all. Nothing to tap on. And though I can see the phone om ny 
>pc, I can't open it. Can't download pictures.
>I also have a SSH server on my phone. I could contact that with a client 
>on my pc, and had access to my phone. Now it also doesn't work anymore.
>
>What can I do to access my phone?
>Many thanks in advance for your answers.
>With best regards,
>Fokke Nauta

I noticed the same on my Samsung Android 16 phone.  It used to be that all
I had to do was attach the cable and log into the phone, and I could then
transfer files.  But a recent update changed that, and now I have to do
what Mr. Slootweg suggested each time I want to transfer files.  I'm
assuming that a security hole was plugged, and if that is correct, I like
it.  It had me fumbling for a bit, but now I just do the required steps and
move on.

-- 
croy

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

#151680

On 2025-12-05 16:44, croy wrote:
> 
> I'm
> assuming that a security hole was plugged, and if that is correct, I like
> it.
I fail to see how this could have plugged any security hole!  Before and 
now, in both cases you have to have possession of the phone and the 
matching fingerprint/PIN/ugly mug/whatever to log into it, so the new 
rigmarole is not discernibly more secure than the old, it's just a 
ritual bloody nuisance.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

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

#151682

Java Jive <java@evij.com.invalid> wrote:
> On 2025-12-05 16:44, croy wrote:
> > 
> > I'm
> > assuming that a security hole was plugged, and if that is correct, I like
> > it.
> I fail to see how this could have plugged any security hole!  Before and 
> now, in both cases you have to have possession of the phone and the 
> matching fingerprint/PIN/ugly mug/whatever to log into it, so the new 
> rigmarole is not discernibly more secure than the old, it's just a 
> ritual bloody nuisance.
> 
Exactly! If someone has your phone in their hands then all files are
accessible, the only possible protection is encryption.

-- 
Chris Green
·

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

#151731

Chris Green <cl@isbd.net> wrote:
> Java Jive <java@evij.com.invalid> wrote:
> > On 2025-12-05 16:44, croy wrote:
> > > 
> > > I'm
> > > assuming that a security hole was plugged, and if that is correct, I like
> > > it.
> > I fail to see how this could have plugged any security hole!  Before and 
> > now, in both cases you have to have possession of the phone and the 
> > matching fingerprint/PIN/ugly mug/whatever to log into it, so the new 
> > rigmarole is not discernibly more secure than the old, it's just a 
> > ritual bloody nuisance.
> > 
> Exactly! If someone has your phone in their hands then all files are
> accessible, the only possible protection is encryption.

  If the phone is (screen) locked, you can't do anything, that's the
whole point of locking a phone.

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

#151735

Frank Slootweg <this@ddress.is.invalid> wrote:
> Chris Green <cl@isbd.net> wrote:
> > Java Jive <java@evij.com.invalid> wrote:
> > > On 2025-12-05 16:44, croy wrote:
> > > > 
> > > > I'm
> > > > assuming that a security hole was plugged, and if that is correct, I like
> > > > it.
> > > I fail to see how this could have plugged any security hole!  Before and 
> > > now, in both cases you have to have possession of the phone and the 
> > > matching fingerprint/PIN/ugly mug/whatever to log into it, so the new 
> > > rigmarole is not discernibly more secure than the old, it's just a 
> > > ritual bloody nuisance.
> > > 
> > Exactly! If someone has your phone in their hands then all files are
> > accessible, the only possible protection is encryption.
> 
>   If the phone is (screen) locked, you can't do anything, that's the
> whole point of locking a phone.

If it's in my hands I can simply take it apart and access the memory.
It's only the same as accessing a disk drive on an 'ordinary' computer.

-- 
Chris Green
·

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

#151737

Chris Green wrote:

> If it's in my hands I can simply take it apart and access the memory.
> It's only the same as accessing a disk drive on an 'ordinary' computer.
If the eMMC/UFS chip has internal encryption?

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

#151743

Andy Burns <usenet@andyburns.uk> wrote:
> Chris Green wrote:
> 
> > If it's in my hands I can simply take it apart and access the memory.
> > It's only the same as accessing a disk drive on an 'ordinary' computer.
> If the eMMC/UFS chip has internal encryption?
> 
Is that common?  If so then you're right, although files stored on an
SD card probably won't be.

-- 
Chris Green
·

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

#151745

Chris Green wrote:

> Andy Burns <usenet@andyburns.uk> wrote:
>> Chris Green wrote:
>>
>>> If it's in my hands I can simply take it apart and access the memory.
>>> It's only the same as accessing a disk drive on an 'ordinary' computer.
>> If the eMMC/UFS chip has internal encryption?
>>
> Is that common? 

On Google devices, I think since Pixel2, encryption was added in a 
firmware upgrade, so maybe not H/W based on that model?

> If so then you're right, although files stored on an
> SD card probably won't be.

Well, no SD for me with Pixels

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

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

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

csiph-web