[General Questions and Answers] ponnex:
Hello guys I got a problem for my A13 tablet

I got every modules to work(ts,gsensor,camera and wifi) the problem is with the micro sd not mounting or not reading :android-cry:

I got a factory firmware though and everytime I flash it back it is working in there, but in every custom rom I flash, micro sd doesnt work. when I plugged in a usb from tablet to pc I got 2 drive showing my internal mounted properly and a greyed drive. When I use file explorer(ES explorer) I can see mnt/extsd but the folder is empty though I can open it on my factory firmware but not in every custom rom for A13 (FaaastJB v2.5, CM10, CM10.1, CookRom v1.3, AOKP) tried them all it got a similar problem with micro sd, not mounting at all. In additional I tried an experiment whether it is with the CWM v6.0.2.8 for A13 with issue compatibility but it is not because I can mount my /emmc and factory firmware works with CWM perfectly with my micro sd on, I am suspecting that its with the custom rom, it doesnt support my A13 anyways,

Here's a lsmod and getevent in my factory firmware

lsmod

gsensor_calibration 6967 0 - Live 0xbf0c4000

bma220 8897 1 gsensor_calibration, Live 0xbf0bd000

sun4i_vibrator 2459 0 - Live 0xbf0b9000

cedarx 9351 0 - Live 0xbf0b2000

mcs7830 7581 0 - Live 0xbf0ac000

qf9700 9152 0 - Live 0xbf0a5000

rtl8150 10305 0 - Live 0xbf09e000

asix 24601 0 - Live 0xbf092000

usbnet 26229 3 mcs7830,qf9700,asix, Live 0xbf085000

mali 150934 4 - Live 0xbf053000

ump 49158 7 mali, Live 0xbf03f000

ft5x_ts 44907 0 - Live 0xbf02f000

sun5i_csi0 30803 0 - Live 0xbf022000

hi704 19468 1 - Live 0xbf019000

hi253 21192 1 - Live 0xbf00f000

videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf00a000

videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf000000

shell@android:/ $ getevent

getevent

add device 1: /dev/input/event3

name: "bma220"

add device 2: /dev/input/event2

name: "ft5x_ts"

add device 3: /dev/input/event0

name: "sw-keyboard"

could not get driver version for /dev/input/mice, Not a typewriter

add device 4: /dev/input/event1

name: "axp20-supplyer"

and vold.fstab in factory firmware:

## Vold 2.0 fstab for HTC Passion

#

## - San Mehat (san@android.com)

##

#######################

## Regular device mount

##

## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>

## label - Label for the volume

## mount_point - Where the volume will be mounted

## part - Partition # (1 based), or 'auto' for first usable partition.

## <sysfs_path> - List of sysfs paths to source devices

######################

# Mounts the first usable partition of the specified device

#/devices/platform/awsmc.3/mmc_host for sdio

dev_mount	sdcard	/mnt/sdcard	auto	/devices/virtual/block/nandi

dev_mount	extsd	/mnt/extsd	auto	/devices/platform/sunxi-mmc.1/mmc_host	/devices/platform/sunxi-mmc.0/mmc_host

dev_mount	usbhost1	/mnt/usbhost1	auto	/devices/platform/sw-ehci.1	/devices/platform/sw_hcd_host0	/devices/platform/sw-ohci.1

What I suspect is that the custom firmare doesnt have mmc_host or cant direct mmc_host

ls in /dev/block/ factory firmware:

ls

loop0

loop1

loop2

loop3

loop4

loop5

loop6

loop7

mmcblk0

mmcblk0p1

mmcblk0p5

nanda

nandb

nandc

nandd

nande

nandf

nandg

nandh

nandi

platform

ram0

ram1

vold

shell@android:/dev/block $

and compare it to a custom firmware ls in /dev/block (I use CookedRom):

ls

loop0

loop1

loop2

loop3

loop4

loop5

loop6

loop7

nanda

nandb

nandc

nandd

nande

nandf

nandg

nandh

nandi

nandj

ram0

ram1

vold

root@android:/dev/block #

does it have an issue when upgrading form 9 partitions to 10 partitions?

If you're asking why im trying to upgrade from my perfectly working factory firmware(ICS) to a not so working custom roms(JB), well our tablet is MyPhone Mypad 2(same with i-mobile i-note wifi 2) up-to-date doesnt have any custom roms(maybe no one doesnt want to risk their gadget) so why not give it a try. I got a patches for ts,gsensor,camera and wifi which I made specifically for this tab and bump into the last problem in which is the external not recognize/mounting/read or whatsoever it is.