When you connect the 40-pin cable, the side of the connector with the ASUS logo goes toward the display (on the tablet) or toward the keyboard (on the dock).
See this tale of woe by DoItYourselferJohn (2012-08-27). He had trouble with his Transformer Prime, and the TF700T may not have some of the issues he found, but his lesson is valuable.
It helps if there are already files on the card, so you can test if it is readable. In the stock image, the boot-time mounter will only mount cards formatted with VFAT. People say that EXFAT also works; this is a Microsoftish proprietary format used on 64Gb cards for which VFAT is not practical. For flashing a custom image, Recovery cannot read EXFAT.
The user's manual says that when the card is mounted the stock image shows an icon in the lower right corner of the screen which you can click to unmount it, implying that you could also hot-mount the card. I have not actually tested this.
The card slot is on the middle west edge. The card should of course have the contacts going inside, with the contacts to the rear and the writing to the front (toward the display). It can be tilted on insertion; don't do that. When the last 2mm of the card is sticking out it should feel springy: this is the ejector spring for when you remove it. If you don't feel the spring, don't push the card in beyond retrieval. If you do feel the spring, use your fingernail to push it in all the way, about 1mm below the surface. It should spring back a little, then stay in.
To physically remove, after unmounting or turning off power, use your fingernail to push the card in about 1mm, down to the end of the slot. It should then spring out. Keep your finger over it so it doesn't go on the floor.
Basically, you don't. I ended up putting one ext4 partition on the card.
Forum post on XDA-Developers, OP PhantomPhreek (2012-08-17) with MIUI
modded ROM, doesn't say which Android version. Kuisma responds, edit
/init.rc or /init.vendor.rc ; look for the
on fs on-unit and
insert lines like this except on an (already existing) mount point of your
mount ext3 /dev/block/mmcblk0p4 /data nosuid nodev
/init.rc is copied from an initrd inside boot.img and you need to hack there and flash the image file. Tutorial here for how to jigger a boot image. Or maybe MIUI has some kind of boot hook.
Forum post on XDA-Developers, OP Darkshado (2013-01-01). He formatted his whole card as ext4. He gives a mini HOWTO for using such a card, but there are flies in his ointment. He also has a link to what may be a howto about enabling init.d.
In the above thread, KurianOfBorg (2013-04-24) says,
you should NOT be
doing this. Android specs require that all shared storage directories
must have case insensitive filenames and no permissions, i.e. FAT32 only.
(Jimc says, what a crock!) Recent Android versions have a
utility which does something like this: mount the non-FAT partition under
/dev/fuse, and mount the userspace daemon on /storage/whatever which publishes
the real filesystem downgraded to FAT32 style. He says
CyanogenMod-10.1 does this automatically. This is a link to the GitHub
sources of sdcard in CM-10.1.
My VFAT SD card (8Gb) has one partition, /dev/mmcblk0p1, and ends up with this line in /proc/mounts:
/dev/block/vold/179:49 /storage/sdcard1 vfat \
rw, dirsync, nosuid, nodev, noexec, relatime, uid=1000, gid=1015, fmask=0702, dmask=0702, allow_utime=0020, codepage=cp437, iocharset=iso8859-1, shortname=mixed, utf8, errors=remount-ro 0 0
To unmount it, the stock image has a notification that you can click.
In CM-10.1 go to Settings-Storage, find the card, and click on the
My EXT3 SD card (32Gb) is not mounted; (something) alleges in the
notification area that it is blank or has an invalid filesystem. I ran fsck
(on Linux) and there was no error. Hmm, parted shows under Flags that the
type is 0c. Per
Partition Types by Andriews Browuwer (2012-03-24), 0c means
WIN95 OSR2 FAT32, LBA-mapped.
I removed that partition, added it back with a Linux type 83, and
remade it (mkfs).
Now CyanogenMod-10.1 mounts it. The real filesystem is mounted at
/mnt/fuse/microsd and the DOSified instance is at /storage/sdcard1.
A file in the real filesystem with a lower case 8.3 name and mode 644 root:root
is seen in the DOS emulation to have the same name and mode 664
A newly created 8.3 file in DOS emulation lands in the real filesystem with
the same name and mode 664 media_rw:media_rw.
(need to re-do)
(need to re-do)
(need to re-do)
But comparing the same phones (Motorola HT820)
doing Bluetooth A2DP vs. wired (3.5mm jack), the wired quality is
noticeably better. A similar difference is seen on Android-1.5
Froyo, and Linux bluez-4.88,
and subsequent Android versions,
suggesting that the problem is in the headphone or the A2DP
algorithm. It's hard to be sure what the difference is, but I have
the impression that the sub-bands in the midrange are not getting
matched up perfectly by the headphone.