Problem with apps thinking on board flash is microSD card??

[fuzzynco]

I'm seeing almost every app (except for CWM recovery) thinking the
/mnt/sdcard directory is the external card (which is true in most
android devices). So they are looking in and placing files in the wrong
place. Smarter apps allow me to set a virtual root for it to start with,
but Kindle and Nook insist on looking in /mnt/sdcard/<appname>
for the stored books.

Does anyone know a workaround to repoint /mnt/sdcard/<appname>
to /mnt/sdcard/ext_sd/<appname>.

Personally, I think the idea to change the meaning of
the /mnt/sdcard, (from the uSD card to part of the on
board flash memory), was not thought out well.

I saw the rezound phone also has this issue.
Someone in that forum suggested swapping
pointers in vold.fstab to make
/sdcard point at the real external sd card
and /sdcard2 point to part of the 16gb
flash memory that left for user space.

Where can I find documentation on what
/dev devices (/dev/block/?? etc) are
used for what partitions?
would adb shell mount tell me what I need?

I still do not understand why the change was made?
Was there some reason to mess up the large number
of android apps that expect /sdcard to be the real sdcard?

I hope for ICS this problem is addressed and the real sdcard
is again called /sdcard.

[Stephen.Lam]

Actually, it is designed to work this way. Approximately the first 8GB of your internal memory is treated as the system folder, where the rest is treated as an SD Card, this is to enable the "SD card" portion to mount as a Flash Drive if you connect your Andriod device to a computer using USB.

Therefore when you put in an external SD card it will be pointing to "ext_sd". If you realize when you connect your Flyer to computer via USB under the Flash Drive option, it will create two drives on your computer.