Related
i tried hijacking the other 1.4.0 thread but got ignored and didnt want to keep a something stale that was off-topic alive.
so, i have flashed 1.4.0, verified that the kernel is in fact running. i wiped before the update to get rid of other issues i was having with some apps.
now, with 1.4.0 running, it appears that the external sdcard is not mounting while the system is booted. in recovery, it shows up as it should with all of the files. i have an /mnt/sdcard/sdcard2 and i have an an external directory under /sdcard
ive tried with card in before boot and after. i can say that dmesg is in fact seeing the card being removed and pushed in; however it doesnt seem to 'automount' from vold.fstab properly, or something else is jacked.
that being said, i dont seem to have a /devices which is where these things are suppose to be mounting from, is it not?
/sys/devices/platform/sdhci-tegra.2/mmc_host/mmc1
should i add the prefix /sys to both the usbOTG and sdcard to fix this?
or is there something else that is missing? presumably i could also create a symbolic link /devices -> /sys/devices, or does the kernel chroot to /sys at some point so none of this is needed, and i am having a different problem?
thanks for the help,
~marion
ya i noticed mine sd card is doing the same thing wont mount but works in recovery and i know it did work bc i had sdcard access through root explorer on v1.4.0 and now it does not work like it died over night
mine has not worked since moving to 1.4.0.
i originally went from 1.3.2 to 1.4.0 but the update didnt work well through the clockworkmod steps was having problems mounting e: so i went back to 1.3.1 then -> 1.4.0 [after wiping cache/data, and readding an sdcard2] using kernelmanager.
the update worked well, i rebooted to recovery and say that i could mount e:, and files where on the sdcard as expected. when booting to OS external has no files and sdcard2 has no files. also using connectbot for a shell, df shows nothing mounted.
is this because vold.fstab isnt mounting from /sys as described in my earlier post?
still unable to mount external sdcard while xoom is boote in 1.4.0.
Am able to pc-mount, and back up to it via recovery... no one else is seeing anything similar?
In 1.4.0 the sdcard should be in /sdcard/external not sdcard2. The card has to be in before turning it on. They are not hot-swappable.
Sent from my Xoom
Guys this is why Mass Storage has been removed in 1.4.1. Here's basically what's going on. When the device boots, the Sdcard is mounted to data/media/external which is the same as Sdcard/external. The Sdcard mounts before data/media is "fused" to create a virtual internal Sdcard. This is the only reason why you can actually see the external Sdcard inside the internal Sdcard. And this is why gallery can see the external Sdcard. However, in order for the Sdcard to mount as mass storage, Vold.fstab MUST mount the Sdcard at mnt/Sdcard so that Vold service can see it. But, this is the same mount point the internal storage is "fused" to. So when mass storage is done, it attempts to remount the sdcard where it was previously mounted, sdcard/external. But because of the way "fuse" works, it does not let any devices be mounted inside it. This is why I need source to do it right. I can then tell Vold to look some other place for the sdcard mount point. Until then, it's borked and that's why I pulled it.
@bwcorvus: in my first post i said that it wasnt showing up in sdcard2 or external... maybe i wasnt clear enough but its there.
@bigrush: thats exactly what i was seeing, and what i was presuming. i figured the lack of response meant either people werent seeing the issue or noticing it.
that being said... dmesg shows the device showing up if inserted/removed while running. but its showing out of /sys/devices... instead of /devices... changing that in vold.fstab didnt do anything for me as im not sure i have a great grasp on the boot sequence.
~marion
That's odd, mine mounts to external with no issue with 1.4.0
Hi,I am on Mac OSX Lion and since i upgraded to Jellybean I am not able to mount my one x as the USB mode to mount disc drive has disappeared?
Any ideas?
Thanks!
First off, this should be posted in Q&A not general. This thread will probably be moved.
I haven't really used JB Sense but do you not get the prompt to select Disk Drive or charge only when you plug in your phone via the USB?
In JB they removed the mounting prompt, now your phone should just be recognized automatically, There is no Disk Drive Mode anymore.
hi
sorry for posting in the wrong area, there is no prompt to mount the disc on the phone anymore, before you could click in the phone and change USB from Charging to mount as disc, and its not appearing in Finder in OSX, thanks for your help
I just installed a new ROM and the SDCARD and SDCard-ext are in the wrong location. They are listed under the root director ( / ) and /storage instead of under /mnt/sdcard
Does it work? You could create a symlink. If that fixed it, put it in a script on bootup.
post-mortem said:
Does it work? You could create a symlink. If that fixed it, put it in a script on bootup.
Click to expand...
Click to collapse
Does it work is a relative question. (wasn't meant to sound wise-a$$). I can access them, but apps do not see them at all. They are looking for the cards in /mnt therefor not finding them.
I changed them in /system/etc/vold.fstab but now it won't boot. The not booting is not an issue, I can fix that, but I don't know how to fix these incorrect paths/
No one else who's using this ROM is having these problems? I say either reflash, create symlinks, or choose another ROM.
post-mortem said:
No one else who's using this ROM is having these problems? I say either reflash, create symlinks, or choose another ROM.
Click to expand...
Click to collapse
Not sure if anyone else is running it. Haven't been able to find a thread on here for it. How do you do symlinks?
mikemikemikexxx said:
Not sure if anyone else is running it. Haven't been able to find a thread on here for it. How do you do symlinks?
Click to expand...
Click to collapse
ln -s target shortcut
See a bit more here.
Make a script in your /system/etc/init.d directory, so these links will be created on every boot.
post-mortem said:
ln -s target shortcut
See a bit more here.
Make a script in your /system/etc/init.d directory, so these links will be created on every boot.
Click to expand...
Click to collapse
From what I have read you cannot use them on FAT.
Why does editing this file not work? I fail to see how Android could do anything other than read the file, provided permissions are the same.
mikemikemikexxx said:
From what I have read you cannot use them on FAT.
Why does editing this file not work? I fail to see how Android could do anything other than read the file, provided permissions are the same.
Click to expand...
Click to collapse
The internal memory is not FAT; typically, only the 1st partition on the SD card is FAT, everything else should be EXT. So, executing ln -s /storage /sd-ext should work (or wherever it's currently being mounted).
post-mortem said:
The internal memory is not FAT; typically, only the 1st partition on the SD card is FAT, everything else should be EXT. So, executing ln -s /storage /sd-ext should work (or wherever it's currently being mounted).
Click to expand...
Click to collapse
I meant the card but ln is not working.
One more thing I am going to try is an ADB pull and push. If that doesn't work I really need some community support.
bump to the front.
Are my questions that complex or that dumb that I get so few replays? /bump
Sent from my XT875 using xda app-developers app
Is there a good reason that you don't want to use another ROM?
Mainly speed and compatibility. I need the offline commands only available in JB. Stock ROM is dead slow and is only ICS. Other custom ROMs were also on the slow side and/or battery hogs.
Sent from my XT875 using xda app-developers app
So, is this right?
FAT partition is currently being mounted as /storage
EXT partition is currently being mounted as /mnt/sdcard
post-mortem said:
So, is this right?
FAT partition is currently being mounted as /storage
EXT partition is currently being mounted as /mnt/sdcard
Click to expand...
Click to collapse
Well the way my phone is laid out is
System (I assume too large so they split it in two which resulted in the below SD-Card)
SD-Card
SD-Card EXT (The actual SD Card) - FAT32
I assume the System and SD-Card are standard Android partition format.
Do you use a file manager on the phone, such as ES File Explorer? Are you familiar with using adb?
Edit: Basically, I'm trying to figure out the exact path of the mounted partitions, and where they're supposed to be mounted.
post-mortem said:
Do you use a file manager on the phone, such as ES File Explorer? Are you familiar with using adb?
Edit: Basically, I'm trying to figure out the exact path of the mounted partitions, and where they're supposed to be mounted.
Click to expand...
Click to collapse
They are 100% supposed to be mounted under: /mnt/sdcard and /mnt/sdcard-ext
Right now they are mounting to: /storage/sdcard and /storage/sdcard-ext
There is also an entry in under root ( /sdcard and /sdcard-ext --- For these two I am booting into stock ROM to see if they are suppose to be directly in root as well, will post up when I know)
Check the scripts in your init.d to see if one of them is mounting the sd partitions under /storage.
I suppose you could also try booting without the sd card in place, and see if those /storage directories still exist. Not sure how much that will tell you, though.
post-mortem said:
Check the scripts in your init.d to see if one of them is mounting the sd partitions under /storage.
I suppose you could also try booting without the sd card in place, and see if those /storage directories still exist. Not sure how much that will tell you, though.
Click to expand...
Click to collapse
The init.d for sure says to load sdcards to /storage . (on this particular ROM only)
I will try without the sdcard as you suggested and let you know. Battery died on me, phone won't boot even when plugged in until at least 10%.
Which script is mounting the sd card to /storage? Is it part of the ROM, or is it something which the dev included in this ROM? I ask in case the ROM expects the sd card to be mounted there.
Regardless, try changing the script to link to /sdcard.
How do enable this so I can transfer some files on my computer? I only get mtp or some other camera option. I just want it to show up as a normal drive. Is there a different driver to be installed?
google removed mass storage mode from android (jellybean(?) and later)
(i think it was b/c mass storage mode does not allow the phone to mount /sdcard while connected to PC.... so apps using /sdcard for storage may become unstable... MTP allows both phone and computer to access /sdcard together, with the phone controlling access)
custom kernels/roms may still include this feature
It can't be done on a FUSE file system
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
abmone said:
How do enable this so I can transfer some files on my computer? I only get mtp or some other camera option. I just want it to show up as a normal drive. Is there a different driver to be installed?
Click to expand...
Click to collapse
Via Developer Options and enabling USB Debugging, mine shows up as you say "like a normal drive". To see everything, you'll want to make sure "Media Device (MTP)" is selected. Also make sure you have the drivers for your device installed on your computer.
If that still doesnt work, try using: SG USB Mass Storage Enabler, available for free on the app store (play.google.com)
That worked for me on my Galaxy S4 on the GPE Rom.
paperWastage said:
google removed mass storage mode from android (jellybean(?) and later)
(i think it was b/c mass storage mode does not allow the phone to mount /sdcard while connected to PC.... so apps using /sdcard for storage may become unstable... MTP allows both phone and computer to access /sdcard together, with the phone controlling access)
custom kernels/roms may still include this feature
Click to expand...
Click to collapse
this is just all kinds of wrong.
google didnt remove it, there's just no sdcard slot so there is no mass storage mode. end of discussion.
This is also wrong. The one x had no sdcard slot but still had mass storage mode.
The reason it's gone is because of the fused sdcard partition. It is actually an ext4 partition which cannot be read by windows in mass storage mode.
The reason they did this was firstly better performance and less limitations than fat in android. And that the partition can be dynamically changed so no risk of /data becoming full and not being able to install anymore apps etc..
There are several other reasons but I'm not going into the boring stuff
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
The reason it's gone is because of the fused sdcard partition. It is actually an ext4 partition which cannot be read by windows in mass storage mode.
The reason they did this was firstly better performance and less limitations than fat in android.
Click to expand...
Click to collapse
Exactly. Windows blows, we all know that.
Alex240188 said:
There are several other reasons but I'm not going into the boring stuff
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think I pretty much covered the reasons in my n5 data thread in general if anyone wants to read it
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I have a cheapo DragonTouch Y88X. I'm not looking for a custom ROM or anything - its for the kids and honestly it does everything they need, with one exception: Disney Movies Anywhere can't download videos to the external SD card.
As near as I can tell, this is an application problem - hardwired looking for /mnt/sdcard instead of using the Google API to find where the SD card is mounted, and DragonTouch was brain dead an mounted part of the internal storage to /mnt/sdcard (the actual SD card gets mounted to /mnt/extsd).
OK, so I'm not going to get Disney to change the app, so I started poking around how to change the mount points. I'm reasonably familiar with linux, sys admin duties and the like. But the format and options on the fstab file are a bit unfamiliar to me... All I really want to do is make the external SD card be mounted at /mnt/sdcard (and maybe mount the internal partition to something useful - maybe app cache space or something?)
I managed to get root and installed ES File Explorer, and the fstab file (/fstab.sun8i to be specific) has the following lines that I think are relevant...:
...
/devices/virtual/block/nandk auto vfat defaults wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.2/mmc_host auto vfat defaults wait,check,noemulatedsd,voldmanagedsd=sdcard:auto
/devices/platform/sunxi-mmc.0/mmc_host /mnt/extsd vfat rw,realtime,fmask=0000,dmask=0000,wait,check,voldmanaged=extsd:auto
/devices/platform/sunxi-mmc.1/mmc_host /mnt/extsd vfat rw,realtime,fmask=0000,dmask=0000,wait,check,voldmanaged=extsd:auto
...
I don't know quite enough about either fstab or Android/DragonTouch's variant of it to know why both sdcard and extsd have two entries each... Or exactly how to swap them. I could try to change the voldmanaged=[name] entry on each - would that be safe?
Is what I'm trying to do crazy, or should this work?
Thanks
Hello,
Welcome to XDA.
Most android devices have a setting to set download location to extsdcard, also, there is usually a setting in most apps that can be used to choose the location the app data downloads to. Since you are rooted then you may be able to create a script that directs your download to where you want but I'm not as knowledgeable about scripts as others here are.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help.
Remember to register an XDA account so you can post and reply in the forums. Good luck.