the volume list looks like this: root@android:/ # vdc volume list > 110 sdcard /mnt/sdcard 4 > 110 emmc /mnt/emmc 0 > 110 fat /mnt/fat 0 > 200 Volumes listed. >
As you thought, /system/etc/volume.cfg does not exist and /system/etc/vold.fstab contains this: > dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host > > dev_mount emmc /mnt/emmc 18 /devices/platform/msm_sdcc.3/mmc_host/mmc0 > > dev_mount fat /mnt/fat auto /devices/virtual/block/loop7 > In addition I found this with adb logcat | grep Vold: > I/Vold ( 126): Vold 2.1 (the revenge) firing up > I/Vold ( 126): Load /etc/vold.origin.fstab. Do not use internal emmc > partition. > D/Vold ( 126): Volume sdcard state changing -1 (Initializing) -> 0 > (No-Media) > D/Vold ( 126): Volume emmc state changing -1 (Initializing) -> 0 > (No-Media) > D/Vold ( 126): Volume fat state changing -1 (Initializing) -> 0 > (No-Media) > D/Vold ( 126): Volume sdcard state changing 0 (No-Media) -> 2 (Pending) > D/Vold ( 126): Volume sdcard state changing 2 (Pending) -> 1 > (Idle-Unmounted) > D/VoldCmdListener( 126): volume list > D/VoldCmdListener( 126): volume mount sdcard > I/Vold ( 126): /dev/block/vold/179:33 being considered for volume > sdcard > D/Vold ( 126): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 > (Checking) > W/Vold ( 126): Skipping fs checks > I/Vold ( 126): Device /dev/block/vold/179:33, target /mnt/sdcard > mounted @ /mnt/secure/staging > D/Vold ( 126): Volume sdcard state changing 3 (Checking) -> 4 (Mounted) > D/VoldCmdListener( 126): volume list > -- Jovan 2014-07-21 20:45 GMT+02:00 Dave Hylands <[email protected]>: > Hi Jovan, > > Device Storage gets its knowledge of which volumes exist from 2 sources. > > One is from the vold service. If you can get into an adb root shell > (either use adb shell followed by su or adb root followed by adb shell) > then you should be able to get vold's notion of volumes with this command: > > vdc volume list > > Device Storage also reads the /system/etc/volume.cfg file. I would expect > this file to not be present on a geeksphone. > > If your vdc volume list looks wonky, then we can further investigate along > those lines. > vold determines its volumes by looking at /system/etc/vold.fstab (and I > seem to recall older versions may have used another file as well, but I > don't recall off the top of my head). > > Dave Hylands > > > ------------------------------ > > *From: *"Jovan Gerodetti" <[email protected]> > *To: *[email protected] > *Sent: *Monday, July 21, 2014 11:02:47 AM > *Subject: *[b2g] [Peak] device storage does not work properly > > > Hi, > > While I experimented with my own builds and the official Geeksphone > builds, I recognized that with an official build everything works fine but > with my builds the device storage does not work as it should. > > 1. The device detects no internal storage. > 2. In Settings>Media Storage it displays Internal (actually my SD-Card) > and two SD-Card slots even though the Peak has only one SD-Card slot. > 3. I have to select internal as default storage to be able to save files > (with SD-Card I get requested to insert a SD-Card) > 3. The rescanning of the media apps does not work. If they have no > indexDB they will find every file and after that they doesn't recognize any > change... > 4. File browser apps take much longer to display the directory indexes. > > This all works with the official builds but not with my own builds. I > experienced this problem since I create my own builds (since v1.4). > Can someone think of anything how this could be fixed? > > > -- Jovan > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > > >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
