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


Groups > comp.mobile.android > #110515

Re: Permissions in Android 12

From "Carlos E. R." <robin_listas@es.invalid>
Newsgroups comp.mobile.android
Subject Re: Permissions in Android 12
Date 2023-11-23 00:26 +0100
Message-ID <ks7h1dFmdagU2@mid.individual.net> (permalink)
References <ujg48o$d581$1@dont-email.me> <ujgcug.sp4.1@ID-201911.user.individual.net> <ujipga$tqvl$1@dont-email.me>

Show all headers | View raw


On 2023-11-21 18:30, The Real Bev wrote:
> On 11/20/23 10:44 AM, Frank Slootweg wrote:
>> The Real Bev <bashley101@gmail.com> wrote:
>>> ...and a few versions back.
>>>
>>> Apparently whatever file manager you use to copy files from your 
>>> computer (specifically .pdfs and ebooks) sets the permissions on 
>>> those files so that you can ONLY read them with your reader by going 
>>> through that file manager -- which alters the way the readers 
>>> operate.  If it weren't for that this would be a nuisance, but 
>>> acceptable.
> 
> Addendum:  I had used the 'files' manager to do the transfer on the 
> no-name tablet and thought that that solved the problem on the Lenovo 
> tablet, but it didn't.  'Files' just assumed ownership instead of ES or Cx.

Certainly, as intended.


>>> Removing the 'defaults' doesn't work.  Deleting the offending file 
>>> manager doesn't work.  We've used Cx, ES and the 'Files' app on the 
>>> just-purchased Lenovo.
> 
> I use the ftp function of ES or Cx to suck files from my computer.  That 
> seems to be the only way to do it with tablets or the Pixel2.  I have 
> been thus far unable to 'see' the phone with my computer in spite of 
> plugging in the USB cable and setting the USB to 'file transfer'.  lsusb 
> sees
>       Bus 003 Device 016: ID 18d1:4ee1 Google Inc. Nexus 4 / 10
> 
> but fdisk -l doesn't see it.  dmesg sees
>       new high-speed USB device number 16 using xhci_hcd

No, fdisk will never see the "disk" on modern Androids (modern since 
perhaps a decade).

The computer doesn't see a disk, but what Android decides to show via 
PPT or MTP protocol. And it is a limited access, not all file or disk 
functions are implemented (intentionally). This is to avoid corruption 
of files when the user suddenly disconnects the cable, and to allow both 
computer and phone to access simultaneously "the disk".


Whether MTP or PTP are available depends on the choice you do on the 
phone when connecting the USB cable. A prompt asks you.



You can change your permission problem if you use a file manager on the 
computer, not on the phone. If you use any app on the phone or tablet, 
only that app will have access to the files, unless you give explicit 
permission to some other app. This step I don't have clear.


Or you can try, using the phone file manager, to save files in a 
commonly accessible folder in your phone, perhaps /downloads.


Maybe your pdf reader can ask for permission to read some folders, or 
maybe all folders, on the phone.

-- 
Cheers,
        Carlos E.R.

Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Permissions in Android 12 The Real Bev <bashley101@gmail.com> - 2023-11-20 09:16 -0800
  Re: Permissions in Android 12 Frank Slootweg <this@ddress.is.invalid> - 2023-11-20 18:44 +0000
    Re: Permissions in Android 12 The Real Bev <bashley101@gmail.com> - 2023-11-21 09:30 -0800
      Re: Permissions in Android 12 Wally J <walterjones@invalid.nospam> - 2023-11-21 14:53 -0400
        Re: Permissions in Android 12 The Real Bev <bashley101@gmail.com> - 2023-11-21 20:41 -0800
          Re: Permissions in Android 12 Wally J <walterjones@invalid.nospam> - 2023-11-22 01:54 -0400
          Re: Permissions in Android 12 Frank Slootweg <this@ddress.is.invalid> - 2023-11-22 15:50 +0000
            Re: Permissions in Android 12 Wally J <walterjones@invalid.nospam> - 2023-11-22 15:22 -0400
              Re: Permissions in Android 12 Frank Slootweg <this@ddress.is.invalid> - 2023-11-23 11:32 +0000
                Re: Permissions in Android 12 Wally J <walterjones@invalid.nospam> - 2023-11-23 10:03 -0400
      Re: Permissions in Android 12 Dave Royal<dave@dave123royal.com> - 2023-11-22 22:55 +0000
      Re: Permissions in Android 12 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-23 00:26 +0100
        Re: Permissions in Android 12 The Real Bev <bashley101@gmail.com> - 2023-11-22 18:15 -0800
          Re: Permissions in Android 12 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-23 09:09 +0100
            Re: Permissions in Android 12 Wally J <walterjones@invalid.nospam> - 2023-11-23 10:34 -0400
            Re: Permissions in Android 12 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-24 20:38 +0100
            Re: Permissions in Android 12 The Real Bev <bashley101@gmail.com> - 2023-11-26 09:26 -0800
              Re: Permissions in Android 12 "Carlos E. R." <robin_listas@es.invalid> - 2023-11-26 19:57 +0100
          Re: Permissions in Android 12 Dave Royal<dave@dave123royal.com> - 2023-11-23 09:47 +0000
            Re: Permissions in Android 12 Wally J <walterjones@invalid.nospam> - 2023-11-23 10:35 -0400
          Re: Permissions in Android 12 Frank Slootweg <this@ddress.is.invalid> - 2023-11-23 14:43 +0000
            Re: Permissions in Android 12 Wally J <walterjones@invalid.nospam> - 2023-11-23 11:14 -0400
            Re: Permissions in Android 12 The Real Bev <bashley101@gmail.com> - 2023-11-26 08:42 -0800
              Re: Permissions in Android 12 Wally J <walterjones@invalid.nospam> - 2023-11-26 21:34 -0400
  Re: Permissions in Android 12 David Oseas <doseas{nospam}@usa.net> - 2023-11-20 10:58 -0800
    Re: Permissions in Android 12 David Oseas <doseas{nospam}@usa.net> - 2023-11-20 11:34 -0800
  Re: Permissions in Android 12 Wally J <walterjones@invalid.nospam> - 2023-11-20 18:20 -0400

csiph-web