my computer actually mounted the SD Card... ONE TIME. and one TIME ONLY Since. Here is how it happened:
I plugged it in last night at some point, and all of the sudden, ADB saw a device. Usually ./adb devices will show nothing connected, although System Profiler / USB shows the Samsung Android.
So I messed around with ADB, pushed and pulled a file to the sdcard. Success.
Still no dice on the mount.
I ran mount_msdos -o nodev /dev/disk1 (because disk1 was the identifier shown in Profiler) and received this error:
mount_msdos: Unsupported sector size (0)
Ran gpt show /dev/disk1 and it gave another error. But then, and all of the sudden, the disk shows up and Aperture starts, trying to import photos. And the sdcard partition shows up on my desktop and it's called NO NAME
And all my files are there.
I have not been able to reproduce this. I have restarted, trashed USBMassStorage and Image Capture preferences, plugged and unplugged, and replugged, and replugged. Did it with USB Debugging on and USB Debugging off. Tried it telling to Mount and telling the phone Not to Mount.
This is the most frustrating, piece of junk. And something tells me that it's all related to the Verizon Wireless CD partition that it tries to mount first. But maybe not, who knows.
Titanium Backup requires Root Privileges.
I have not had the chance, obviously, to get root on the phone.
So Mr. Norris isn't going to be able to help me here.
Can anybody think of something I'm overlooking?
Thanks,
Dan.
PS - Better yet, can ANYBODY confirm reproduction of what I'm seeing? I have and parts and pieces of all of this on other forums, but not the type of intermittent behavior. The only thing I haven't done, is use a different cable between the phone and the USB Hub. Best Buy was out of USB A-USB Micro cables.