Jim Chalderoni wrote:
> On Sun, 16 Feb 2014 20:40:01 -0800, Jim Chalderoni wrote:
>
>> So, I will reboot the WinXP PC and the Samsung Galaxy S3 & report back.
>
> Thanks to you, I'm close. Very close.
> But, still, the folders below "Data" & "Media" are only shortcuts:
>
http://farm8.staticflickr.com/7443/12581645514_2a07019a6d_o.jpg
>
> I'm not sure why, with Android 4.3, I'm only getting shortcuts, instead of
> the actual files, nor why I see a "Media" & "Data" hierarchy (since it
> should be all at the top level), so, I futzed about on the Galaxy S3.
>
> Settings->About Device->Build number->Build number->Build number
> Pressing "Build number" the third time turned on developer options.
>
> Settings->Developer options->USB debugging = ON
> But, that didn't seem to make any difference.
> (I'd show you a screenshot, but I can't access the Pictures/Screenshots
> folder because it's just a symbolic link, and not a directory.)
The question about "where is my MTP driver" has come up before.
MTP was added as a class, rather late in the USB development cycle.
That still doesn't explain why it had to be bundled with WMP.
At one time, Microsoft was having trouble getting people to
upgrade to the DRM-laden later versions of WMP, and the
theory was, it was a "carrot" to suck you into installing
the later version of WMP. While MTP is all about "digital rights
management", and preventing the transfer of commercial material,
that would not have prevented it from being a separate download,
just as a driver. WMP is not the only way you might talk to
a mobile device. At least, I hope not. I should be able to
write my own app if I want, and attempt to access files over MTP.
Maybe an Android user can explain the behavior you're seeing.
I haven't a clue what their file system is supposed to look like.
From the Wikipedia article:
"MTP and PTP specifically overcome this issue by making the unit
of managed storage a local file rather than an entire (possibly
very large) unit of mass storage at the block level. In this way,
MTP works like a transactional file system - either the entire file
is written/read or nothing. The storage media is not affected by
failed transfers."
So on a Windows computer, your disk is considered a block device,
and you ask for "Sectors". Whereas, with MTP, the unit of exchange
is "files". Which is why it doesn't matter what the file system is
on the Android end. As the protocol apparently exchanges "files".
The remaining question then is, why it isn't able to hop a symbolic
link and get to the real file at the end of it. Or for that matter,
how MTP deals with permissions on file systems - like, what
prevents MTP from traversing places it isn't supposed to go ?
Paul