DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 646FWNEK2072080
Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 646FWNEK2072080
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=YmgVZ/K4
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D146E4BA23DD
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1778081541;
	bh=kCJOZMDug1GtBkDwftaQy4SXkhyRHOljUHBRgh4I+AY=;
	h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=YmgVZ/K4SwsKl0Xa+d/QNLWoJuYai+UkkjiqLq+POqvk270ARDpH2GFRX2HllGfzX
	 CVJBI/4wKe4TIQGRPJESGzHecBGTMiwvpK9CeWvPSWkK9HOEIWBPK8yIRbykdraAxn
	 Vl+0n1XMuuuLg8r5FuXs4PP21vO8IvinhfFN04PM=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0DD684BA7988
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 0DD684BA7988
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1778081491; cv=none;
 b=k5XIDCxJ/X4jvJoaD9TqRvpE/l91MqkugmuEer0F9niUVFm/unb46/tneHO8P4LTbjwa3HObAsbcRQayUfCb0Yi68uTti6PD/gEfHzgkxAsZ9IeppQpWNgKfjolRs+P/lSvY8Eel7RaddPg3JnwBhAu5HwhU3GYQDtRmo2Xa8hY=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1778081491; c=relaxed/simple;
 bh=wGsdgleE5f4FdfKfbn79/nAYCuAQrYdAZ/84p1etENo=;
 h=DKIM-Signature:Subject:To:From:Message-ID:Date:MIME-Version;
 b=b5jMwuUTm99yeOZyXb8gxcdbnr9hISZyWVr/lEeEiMg2vkl0DC+ACEUpBqKUp1e7DSCdMgSXKjsINzpEXby6hN5Wbs//X6ElPEZ60s/KacPqs2fSmIra0M1bjHniFs2H6UPuMHGfGSXL6pHdLnf/C9w2vorgSWoDQOrq7NNXeko=
ARC-Authentication-Results: i=1; sourceware.org;
 dkim=pass (2048-bit key, unprotected)
 header.d=wisemo.com header.i=@wisemo.com header.a=rsa-sha256 header.s=v2016
 header.b=mKb2LtRZ
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0DD684BA7988
Subject: Re: Access files on Android phone via Cygwin?
To: cygwin AT cygwin DOT com
References: <a44dcfda-97aa-4afd-bc61-021e3885a273 DOT ref AT att DOT net>
 <a44dcfda-97aa-4afd-bc61-021e3885a273 AT att DOT net>
 <TYWPR01MB8789A505DB757BCBFBE1CEF1C13F2 AT TYWPR01MB8789 DOT jpnprd01 DOT prod DOT outlook DOT com>
Organization: WiseMo A/S
Message-ID: <668aac5e-ea04-2588-3510-3c558c111e4f@wisemo.com>
Date: Wed, 6 May 2026 17:31:25 +0200
X-Mailer: Epyrus/2.2.0
MIME-Version: 1.0
In-Reply-To: <TYWPR01MB8789A505DB757BCBFBE1CEF1C13F2@TYWPR01MB8789.jpnprd01.prod.outlook.com>
Content-Language: en-US
X-Content-Filtered-By: Mailman/MimeDel 2.1.30
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Jakob Bohm via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Jakob Bohm <jb AT wisemo DOT com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 646FWNEK2072080

On 06/05/2026 15:34, Annihilannic via Cygwin wrote:
> On 06/05/2026 13:46, Jonathan Clark via Cygwin wrote:
>> I have a Windows11 box and an Android phone. If I stick a USB cable
>> between the two then the phone filesystems show up on the PC in File
>> Explorer, but *not* as a mount point. No mount point means no access for
>> Cygwin processes (and there may be other hurdles too, that's as far as I
>> got).
>> I am reasonably sure that in Windows10 it *was* a mount point, and I had
>> no problems with access.
>
> I'm still running Windows 10 and the behaviour there is the same for 
> me, so I don't think it's a 10/11 thing.  I think a loooooong time ago 
> some Android devices used to do what you describe, but I haven't seen 
> it recently, they all seem to use the nasty MTP mode now.  I'd also be 
> curious to hear if others have had different experiences though.
>
Many Android versions ago, Android changed the way it shared its 
internal disk to the computer over USB from acting like an USB stick 
with a FAT file system to acting like a "Multimedia shared storage" 
(MTG?) device.  This in turn caused it to be mounted differently in 
operating systems, including Windows.

Folders that show up in Windows File Explorer may be actual folders 
available via the Windows File IO APIs, or they may be virtual locations 
implemented in loadable File Explorer extensions such as the extension 
that allows using File Explorer to navigate inside ZIP files.  If (and I 
don't know if this is the case), the Windows handling of the MTG? USB 
protocol is an File Explorer extension, it probably isn't exposed to 
other software such as Cygwin or even cmd.exe .


-- 
Jakob Bohm, CIO, partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Soborg, Denmark. direct: +45 31 13 16 10 
<tel:+4531131610>
This message is only for its intended recipient, delete if misaddressed.
WiseMo - Remote Service Management for PCs, Phones and Embedded

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple