Database Users

default USB Mass storage issue

Hi
for the last few hours I am trying to resolve the issue that I only today found out and after lots of testing, reflashing different roms I realized that this is a general issue and not related only to me or the rom I am using. So far tried only CM7 roms and NexusHD 3.0.
First it only happens if you have second partition on your sdcard. If you have only one fat32 partition everything works OK.
To see the issue try next:
-Enable USB Mass storage via default mount option in notification area. (issue is not present with 3rd party mount apps)
-On your computer open some folder on your SD card and remember its content
-Turn off USB Mass storage
-copy any file to that folder via any file manager app ib your phone
-Turn on USB Mass Storage and again open that folder to check for the new file (second mount lasts much longer then the first)
-File is not visible via USB mount until next phone reboot.
I have tried so far:
-HyperDroid 3 and Hyperdroid GBX v12
-Typhoon 3.6.4
-NexusHD 3.0 and 3.1a
-UltimateDroid 3.3
(all cLK)
Tried to use vold files from several other roms (MIUI and sense rom) but the issue is always there.
Also tried disabling USB debugging, changing USB ports, even PC's.
After some testing I realized that it only occurs if there is extra partition on sd. I tried ReiserFS and ext4 format, no difference. Only when I deleted all the partitions, created one and reformat it to fat32 mount was working fine.
I am currently using AdamG's a2sd modified by Seader for Hyperdroid, but while trying this on NexusHD I used Darktremor 2.7.5.2 and the issue is there.
Workaround for this is to use alternative apps for mounting. I am using Multi Mount SD-Card Lite.....
I have several people so far confirming this, on HyperDroid and Typhoon. All have partitions for a2sd.
I am not sure when this started happening. I will try tommorow some older roms but until then any information about this is helpfull. Please post if you have the issue and what rom you are on.
This is a log while mounting the USB for the second time. I see lots of vold, mount lines.
http://pastebin.com/XKUqpU56
update:
The cause of this issue is definitely a2sd. After I installed fresh rom (hyperdroid) with a2sd script removed from init.d folder USB mount doesn't have this issue.
So something is happening during mount or unmount process with active a2sd which breaks the ability of USB mount to update its file index which is sent to the computer.
This is happening with both Darktremor (tried 2.7.5.2 and 2.7.5.3. beta4) and AdamG's a2sd scripts.
update2:
this is another logcat
while mounting, checking Camera folder on a computer, unmounting, takes a picture, mounting again(this mount takes about 3 times longer then the first) and then checking the Camera folder again.
http://pastebin.com/HtqXzVx4
update3:
I found a way to stop this issue from happening. I have modified one line in vold.fstab file that is located in /system/etc
from
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
to
dev_mount sdcard /mnt/sdcard 1 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
As soon as I change 1 to auto again and reboot issue is back.
This way only the first partition (fat32) is mounted and the issue is gone. I dont know if this change can cause any other issues, but so far only thing I noticed that is different is that when you turn USB Mass storage on while connecting the phone to a linux computer it only mounts first partition and no sdext one. For me this is not important, but as I said I am not sure if this change could have an impact on stability to any part of the system or phone functionality.
So to summ up:
- there is an issue of phone doesnt updating file index after first mount and you can't see any new files on your PC that are created in the meanwhile until phone reboot (for example new pictures taken with Camera)
-this only happens if you have extra partition on sdcard (for a2sd) and installed a2sd script (so far tried only Darktremors and AdamG's, but I guess that they all basically are doing the same thing). If you remove one of this elements the issue is gone
-after changing line in /system/etc/vold.fstab
"dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1 "..........from auto to 1
so the system will mount first and not automaticaly the first available partition, the issue is gone but someone with more knowledge then me could say what kind of issues this change might produce.
(Some time ago while applying this change in hyperdroid release at that time lots of people had issues with getting an corrupt SD card error. Not sure why it happened because it worked fine on my phone)

I have that issue also and i'm using NDT MIUI...now have to use the eMAgldr 1.13 USB Mount Storage to move or copy the file.

I have just installed Ultimate Droid 3.3 to check this issue and it is also there. UD is a 2.3.3 rom with tytung r9 kernel. So the issue is not so new
I need to test even older roms to find out if this ever worked right.
Is there anyone with some old rom installed on it? Nand or SD.

clyder said:
tytung r9 kernel.
Click to expand...
Click to collapse
Yup just try updating your kernel to be able to support ext2-4 partitions
its a big mistake that almost everybody does...

Dakargr said:
Yup just try updating your kernel to be able to support ext2-4 partitions
its a big mistake that almost everybody does...
Click to expand...
Click to collapse
You havent read my post. There is no problem with functionality of sdext partition. But the presense of sdext partitions is one of the conditions for this issue.
I am using Hyperdroid with kernel that is based on tytung r12. After I realized the issue I thought that it is related to that rom and after that with my sd card or something 3rd from my side. But that is not the case.
I have tried about 5 different roms, vold files from 5 more and the issue is always there. Issue is present only where there is a second partion on SD card.
Oldest rom I tried is UD 3.3. I havent found much older cLK roms to test, and now dont have time to convert older roms to test. I will do so later. I want to see if this thing ever worked right and in what point it stopped.
Also you havent mentioned if you tested the issue or not.

I think I don't have any USB Mass storage issue.
My SD card has FAT32 and Ext3 partitions but I don't use Apps2SD. (i.e. Ext3 partition is empty.)
I will try your steps when I go home. (I didn't bring my mini USB cable in hand.)
I rarely copy files using file manager apps.
If you can use USB Mass Storage, it seems there's no reason to use file manager apps.

tytung said:
I think I don't have any USB Mass storage issue.
My SD card has FAT32 and Ext3 partitions but I don't use Apps2SD. (i.e. Ext3 partition is empty.)
I will try your steps when I go home. (I didn't bring my mini USB cable in hand.)
I rarely copy files using file manager apps.
If you can use USB Mass Storage, it seems there's no reason to use file manager apps.
Click to expand...
Click to collapse
Thanx for replying. I havent tried with ext3. Only reiserFs and ext4 and the behavior was the same. Only when I removed the ext partition it was gone.
The issue is like phone is sending the same directory listing to a computer in both first and all other mounts until reboot.
One also good way to test is by taking photos from a camera. Look at the DCIM/Camera folder with USB mass storage. Turn storage off. Take another picture. Use Mass storage again and the new pic wont be visible through USB mass storage on your computer.
So far I tried only on windows and not linux. Maybe the behavior is different. I will make more tests later.
At one point I thought that my windows system made that issue, so I tried to change USB ports, also tried hooking phone to another computer and the new files wasn't present.
Also it came to me that a2sd can cause this, but on your rom I tried Darktremor a2sd, while on others it was AdamG's one. Issue was exactly the same.
I havent tried any sense rom, because I would need to reflash different partition layout and was too lazy to do that yesterday.
Point of this thread was to check other people experiences with this to try to realize if this is all general HD2 issue, or perhaps only on AOSP roms. So far not much reports
Can any of your older kernel (<r9) work with newer roms(2.3.4+). I dont care about wifi, phone or anything. It is enough if I can just boot the phone to test this.

update:
I just tried USB mount in Ubuntu and the behavior is the same. Also since I can see ext partition when do a USB mount in linux I realized that the same issues goes with files on ext. New files are not visible to the computer until phone reboot.

clyder said:
Thanx for replying. I havent tried with ext3. Only reiserFs and ext4 and the behavior was the same. Only when I removed the ext partition it was gone.
The issue is like phone is sending the same directory listing to a computer in both first and all other mounts until reboot.
One also good way to test is by taking photos from a camera. Look at the DCIM/Camera folder with USB mass storage. Turn storage off. Take another picture. Use Mass storage again and the new pic wont be visible through USB mass storage on your computer.
So far I tried only on windows and not linux. Maybe the behavior is different. I will make more tests later.
At one point I thought that my windows system made that issue, so I tried to change USB ports, also tried hooking phone to another computer and the new files wasn't present.
Also it came to me that a2sd can cause this, but on your rom I tried Darktremor a2sd, while on others it was AdamG's one. Issue was exactly the same.
I havent tried any sense rom, because I would need to reflash different partition layout and was too lazy to do that yesterday.
Point of this thread was to check other people experiences with this to try to realize if this is all general HD2 issue, or perhaps only on AOSP roms. So far not much reports
Can any of your older kernel (<r9) work with newer roms(2.3.4+). I dont care about wifi, phone or anything. It is enough if I can just boot the phone to test this.
Click to expand...
Click to collapse
This problem appears only after dismounting SD storage you don't remove the cable from the phone.
It is normal before mounting it again to disconnect the USB cable!

Denkov said:
This problem appears only after dismounting SD storage you don't remove the cable from the phone.
It is normal before mounting it again to disconnect the USB cable!
Click to expand...
Click to collapse
This is not the case here. I tried disconnecting my phone, also tried connecting it to another PC and again I can't see any new files until phone reboot.
Have you actualy tested this or just guessing? Do you have ext partition on your SD card? What rom are you using?

clyder said:
This is not the case here. I tried disconnecting my phone, also tried connecting it to another PC and again I can't see any new files until phone reboot.
Have you actualy tested this or just guessing? Do you have ext partition on your SD card? What rom are you using?
Click to expand...
Click to collapse
I have second partition ext3.
I mount SD card, check screen shot folder, unmounted the card, remove the cable, take a screenshot, mount it again and the new image was there.
When I try to do same thing second time it did't work! Maybe you are right - there is issue with th SD card mount and I think the card is not dismounted properly!

tytung said:
I think I don't have any USB Mass storage issue.
My SD card has FAT32 and Ext3 partitions but I don't use Apps2SD. (i.e. Ext3 partition is empty.)
I will try your steps when I go home. (I didn't bring my mini USB cable in hand.)
I rarely copy files using file manager apps.
If you can use USB Mass Storage, it seems there's no reason to use file manager apps.
Click to expand...
Click to collapse
I have tried it.
Mount -> check the content of a folder in the SD card.
Unmount -> Copy a file to that folder using ES File Explorer. (Second testing is Root Explorer. Has the same result.)
Mount -> new file is there.
Win7 x64
NexusHD2-Gingerbread V3.1a NAND

tytung said:
I have tried it.
Mount -> check the content of a folder in the SD card.
Unmount -> Copy a file to that folder using ES File Explorer. (Second testing is Root Explorer. Has the same result.)
Mount -> new file is there.
Win7 x64
NexusHD2-Gingerbread V3.1a NAND
Click to expand...
Click to collapse
You said before that you dont have a2sd installed. Did you tested this without a2sd also? Maybe that is the key. All my tests so far included the presence of some kind of a2sd script.
Also I am on cLK, and two other guys that confirmed it are also on cLK. I dont know about denkov.
I will do more tests later but the issue is definitely related to ext. Because of some incompatibility of a2sd scripts with some part of android system or for some other reason.

I have just tried the combination of NexusHD 3.1a/cLK/AdamG's a2sd script/ext4
issue remains here

clyder said:
You said before that you dont have a2sd installed. Did you tested this without a2sd also? Maybe that is the key. All my tests so far included the presence of some kind of a2sd script.
Also I am on cLK, and two other guys that confirmed it are also on cLK. I dont know about denkov.
I will do more tests later but the issue is definitely related to ext. Because of some incompatibility of a2sd scripts with some part of android system or for some other reason.
Click to expand...
Click to collapse
I am on MAGLDR.
And I don't use any a2sd as I said before.
So my testing is without a2sd.
I think a2sd scripts may be the suspect.

tytung said:
I am on MAGLDR.
And I don't use any a2sd as I said before.
So my testing is without a2sd.
I think a2sd scripts may be the suspect.
Click to expand...
Click to collapse
They are definitely the cause. I have tried both Darktremor's and AdamG's script.
All of the people who confirmed this to me was using a2sd.
edit:
Just did a fresh install of hyperdroid with a2sd script removed from init.d and usb mount issue is gone.
So something is happening while mounting or remounting USB with active a2sd script which breaks the file list updating when mounting it the second time.

I have found a way to stop the issue from happening. Updated first post....if anyone is actually reading this thread...
clyder said:
update3:
I found a way to stop this issue from happening. I have modified one line in vold.fstab file that is located in /system/etc
from
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
to
dev_mount sdcard /mnt/sdcard 1 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
As soon as I change 1 to auto again and reboot issue is back.
This way only the first partition (fat32) is mounted and the issue is gone. I dont know if this change can cause any other issues, but so far only thing I noticed that is different is that when you turn USB Mass storage on while connecting the phone to a linux computer it only mounts first partition and no sdext one. For me this is not important, but as I said I am not sure if this change could have an impact on stability to any part of the system or phone functionality.
So to summ up:
- there is an issue of phone doesnt updating file index after first mount and you can't see any new files on your PC that are created in the meanwhile until phone reboot (for example new pictures taken with Camera)
-this only happens if you have extra partition on sdcard (for a2sd) and installed a2sd script (so far tried only Darktremors and AdamG's, but I guess that they all basically are doing the same thing). If you remove one of this elements the issue is gone
-after changing line in /system/etc/vold.fstab
"dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1 "..........from auto to 1
so the system will mount first and not automaticaly the first available partition, the issue is gone but someone with more knowledge then me could say what kind of issues this change might produce.
Click to expand...
Click to collapse

Good job! I will try!

Ext4 / NTFS MicroSd & Usb Mounting -v2.3 (fat32 UMS) MTP/UMS Switching/ CM9/10 info

Ext4 / NTFS MicroSd & Usb Mounting -v2.3 (fat32 UMS) MTP/UMS Switching/ CM9/10 info
Hi,
i have developed an App, EzyMount - that pretty much takes care of mounting & utilising ext4 / ntfs storage properly. So no need to be limited to 4gb file size restrictions anymore !!
Updated info for CM9 / CM10 builds
****************************************************************
It seems that CM9 /CM10 changes the default mount point for external sdcards
For ntfs partition only sdcard
Change the default mount point to: /storage/sdcard1
Then try mounting here it should work ok and be picked up automatically by other Apps as well.
If you have two partitions:
1st Partition would be vfat then this should get auto mounted to /storage/sdcard1
2nd Partition (ntfs) : change the mount point to: /storage/sdcard0/extStorages1
Then try mounting here it should be ok
*****************************************************************
Version 2.3 Update
Universal Mass Storage Mode support for 7.7 tabs also most other devices.
Auto MTP/UMS Switching
When you select either MTP Mode or UMS Mode, the App will automatically switch your device into these respective USB transfer method.
It is also possible to use UMS mode for any external MicroSd card, fat32, Ext4 or NTFS formatted.
For ext4 / ntfs this is taken care of by the App
For fat32 external sd cards (these are mounted automatically by Android)
Create a new Mount Point which is the folder location of your external MicroSd card.
For example, on Galaxy 7.7 devices - this will be /mnt/sdcard/extStorages/SdCard.
For Galaxy S3 devices - this will be /mnt/extSdCard
For other devices this is typically, /mnt/sdcard/external_sd
In the partition setting put: /dev/block/mmcblk1p1
Once you have created this mount point, just select "UMS Mode".
After you have finished copying files to or from your PC, it is important to "safely eject your usb device from your PC".
Important too - Finally, disable "UMS Mode" by it pressing again.
You can switch back to MTP by selcting "MTP Mode".
(If MTP does not become active straight away (Android being slow too pick up the change)- you may need to Go to : Settings > Storage > USB PC connection & toggle between Media Device (MTP) & Camera PTP. So Android re-starts MTP. However, it should work without this step)
*****************************************************************
Version 2.1 update
1) New Sliding UI.
2) Ability to mount up to 10 devices / partitions.
Just create a new Mount Point for each device / partition you need to mount.
To create a new Mount Point:
Just slide the UI to the "mount another drive or partition". Then just use select a mount option as per usual to create a new mount point and mount at the same time. Or you can press the "microsd info" "usb drive info" to create a new Mount Point.
3) Works with ICS update
Just ignore "ICS warning messages" - when it comes to ntfs usb devices.
*****************************************************************
Version 1.7 update
1) Quite a few new features added:
NTFS / Ext4 MTP Modes - this allows you to easily switch between "normal mode" and MTP mode.
MTP mode is used for transferring files to PC.
Usage Example:
Personally, I have a 32 gb sd card
the First partion on it is an exFat 4 gb partition. This is picked up the tab and mounted as normal to the location of /mnt/sdcard/extStorages/SdCard
I can use this for my cwm backups etc, other files etc - system running as normal.
This 4gb partition will show up in windows via MTP.
The problem:
I also have a 28GB Ext4 second partition on the Card , this could be an NTFS partition too.
I want this too show up in windows so I can transfer (br rips etc) but it wont as the my first fat32 partiion is shown up instead.
By using NTFS MTP Mode or Ext4 MTP Mode - the App will automatically "switch" the partitions so the larger NTFS or EXT4 mode shows up in windows.
Once done then you can disable NTFS / EXT4 MTP MODE and the device will go back to normal as it were.
(the MTP folder location is set to work already for 7.7 devices and similiar. For other devices this needs to be adjusted. It is normally the default folder loaction of where the external SD card is mounted by the phone.)
UMS Mode - universal mass storage mode.
Although the 7.7 does not have ums mode (MTP is being standardised on ics devices and above) but there a lot of devices than can only use ums mode for transferring file to PC.
I have added a ums mode. Which basically makes your micro sd partitions available on pc. (suitable for non MTP devices)
You do not need to "turn on usb mass storage mode" just select "ums mode" from the APP and it will do it for you.
Also - in windows ext4 partitions are not recognised but ntfs one are off course. In linux both should be available. (one of the benefits of MTP)
Comaptibility Mode
Is for those users whose mounting of micro sd cards might fail for some reason. This mode tries a bit more thorough to mount your micro sd drives.
Better Error Messages
I have added a lot of better error messages that the de facto "error mounting " message
It should provide the reason why things might not be mounting.
I hope this helps some with issues and pm if you have any other issues or things you think might be useful to add.
( I will get round to updating the website with the added features soon)
*****************************************************************
version update 1.6
1) Fixed slight issue with Auto Ext4 permission handling.
2) Also changed the default mount folders of NTFS or Ext4 microsd card to the /sdcard/extStorages/SdCard
This should mean now MTP will see the card in windows properly and you can access them as you would normally. (I think this has caused some confusion - i had left this generic for other users on different devices)
(This means for other devices you should specify the folder in the "location" settings which is normally seen by windows MTP - i.e when you use a fat32 microsd)
I hope this has resolved some issues people might have been having.
version update 1.5
1) Modified labelling on some settings to make it clearer.
2) Mounting usb devices has been slightly tweaked to care of multiple partitions.
version update 1.4
Following on from your recommendations.
1) Mounting MicroSd Ext4 or Ntfs now automatically takes care of you partitions so you do not need to specify them.
This should make it much simpler to mount your microsd cards.
2) Usb Mounting widget should be compatible for all home screen launchers. (touchwiz, adwlauncher etc.)
************************************************************************************************************************************************************************************************************
please remember to unmount usb / microsd devices before ejecting - For usb devices you use the 1-click usb mount/umnount home screen widget for this or from within the App
************************************************************************************************************************************************************************************************************
There have been a few issues regarding using external Usb formatted Ntfs or Ntfs microsd drives. Also I wanted to use an internal micro sd Ext4 partition for large movies (1080p hi-def/bluray etc) or just keep them on an external Ext4 usb disk. Having looked at other solutions, there didn't seem like one that just "worked" or the way I wanted it to do so.
Using Ext4 over Ntfs is native to linux/android and it consumes less cpu than using ntfs. But you cant simply mount an ext4 device and start using it like a regular file system as the file permission are not properly created by Android. I also still needed to have Ntfs read/write support on occassions.
You can use any cheap otg usb cable found on ebay etc. (The same cables as used for 10" galaxy tab devices for example).
As I used the 7.7 as one of my development device so it is pretty suited for our tabs & similiar tablets i.e 7.0+ etc, but is more than generic enough to work on other devices.
The App provides all the necessary features and customization options so you don't need to worry about file formats, file size limitations or file permissions again !!
There are more tips on how to best use the app on my website. If you have any comments good or bad please let me know so I can improve the App.
Cheers.

Need help in mounting microSD as Mass Storage
I don't understand Settings Guide on your website. I downloaded your app but it isn't working for me and I get Partition error every time I try to mount. What should be my partition and what should be the location? I simply want to mount my NTFS microSD card as mass storage which is usually at /extstorages/SDcard/. I did root my device last night and I also installed busybox v1.19 few minutes ago. What am I doing wrong?

Same here, says "Check your partitions". Why do *I* have to worry about partitions? Can't it just work?
Using rooted Tab 7.7.

Asad_Khan said:
I don't understand Settings Guide on your website. I downloaded your app but it isn't working for me and I get Partition error every time I try to mount. What should be my partition and what should be the location? I simply want to mount my NTFS microSD card as mass storage which is usually at /extstorages/SDcard/. I did root my device last night and I also installed busybox v1.19 few minutes ago. What am I doing wrong?
Click to expand...
Click to collapse
belyj said:
Same here, says "Check your partitions". Why do *I* have to worry about partitions? Can't it just work?
Using rooted Tab 7.7.
Click to expand...
Click to collapse
Hi guys,
The default partition of your microsd card is typically:
/dev/block/mmcblk1p1
1) If you have only one partition - so you will put the following in the partition setting:
So for example an NTFS only formated microsd card :
/dev/block/mmcblk1p1
And the same would go for an Ext4 formatted only card:
/dev/block/mmcblk1p1
2) If you have two partitions then typically you will have:
/dev/block/mmcblk1p1
/dev/block/mmcblk1p2
And so on ..
(you can always check for these from a terminal/adb shell)
As these partitions are same for your microsd, you can set them once and forget them about afterwards. I don't try automatically choose these partitions for you and this depends on your partitioning scheme more than anything.
For Usb devices the App will automatically try mounting your usb partitions as these are likely to change more often then not.
Typically, I would recommend the following:
If you have a large 32gb / 64 gb microsd card
Create The first partition as fat32 - maybe 4gb.
This partition will be /dev/block/mmcblk1p1
The tab will automatically mount this first partition & you can use things like cwm recovery for backup as normal.
(Also you wont see an unsupported file system icon in your status bar.)
Then create a second large partition (ext4 or ntfs) :
This partition will be /dev/block/mmcblk1p2
So set this as your Ntfs partition or ext4 partition.
Once you can mount you microsd ok - then you can set it to automount boot.
So need to mess with the settings after that.
Hope this helps and please let me know.
Cheers.

Still MTP connection
Thank you for your explanation. I've can now mount/unmount SD card but when I connect it computer it starts MTP connection and still shows under my computer as a portable device rather than a Mass Storage. Also if I connect it to my computer first it would still ask me to restart the MTP connect when I click mount SDcard and again it shows as a portable device. Changing debugging settings won't help either.
Partition /dev/block/mmcblk1p1
Location /mnt/sdcard/extStorages/SdCard

Asad_Khan said:
Thank you for your explanation. I've can now mount/unmount SD card but when I connect it computer it starts MTP connection and still shows under my computer as a portable device rather than a Mass Storage. Also if I connect it to my computer first it would still ask me to restart the MTP connect when I click mount SDcard and again it shows as a portable device. Changing debugging settings won't help either.
Partition /dev/block/mmcblk1p1
Location /mnt/sdcard/extStorages/SdCard
Click to expand...
Click to collapse
I just tried this. If you click on the "portable device" in windows it shows up as tablet. You can copy files to where you mounted the sd card.
It should work fine.
For me I leave set pretty much as default. As I have the first partition on my sdcard as an exfat / fat32. Then I have an ext4 or Ntfs Partition. This way you tab will behave exactly as normal. But The App should be fine regardless of whatever partitions you have.
Please try this and let me know.
(Also I will look to be adding an auto mounting microsd feature in the next few updates if there is some demand for this. Plus any other features people might suggest in the meanwhile )
Cheers.

To those who have installed EzyMount,
I have updated the microsd mounting feature so it should automatically mount the correct partition for you.
You dont have to manually change the partition settings anymore.
Having said that if there is a particular partition on your microsd you want to mount, then put that in the settings. The app will first try to mount that partition, then try to mount the other partitions if the first mount was not successful.
Also i would suggest setting the mount point folder (location option in settings) to /sdcard/SOME_FOLDER
& not /ext/extStorages/SdCard. which is where the tab mount would mount the microsd card.
Let me know how it goes with the update.
Hope this helps.
cheers.

Hi buddy.
I am totally confused as to how this works.
I went through the info at your website, but I still cannot get this to work.
I have tried only USB flash memory with an OTG USB adapter, both EXT4 and NTFS. I just get an error that says: Error Mounting USB Drive. I can tell that it seems to try, because the activity LED on the drive will flash when I click Mount.
I am using a Samsung Note (i717), so I am not sure if that is the problem. I am only rooted, but the kernel and software is stock 2.3. The phone has both internal memory (called USB Storage by the system) and an sd card; could the app be confused by the various memory locations?
I don't have a spare microsd to format as NTFS, otherwise I would try that.
Any ideas on what I should try? I am a little confused by the settings... they seem to be in many locations, so I am not sure what things to change.
Thanks!

G8351427 said:
Hi buddy.
I am totally confused as to how this works.
I went through the info at your website, but I still cannot get this to work.
I have tried only USB flash memory with an OTG USB adapter, both EXT4 and NTFS. I just get an error that says: Error Mounting USB Drive. I can tell that it seems to try, because the activity LED on the drive will flash when I click Mount.
I am using a Samsung Note (i717), so I am not sure if that is the problem. I am only rooted, but the kernel and software is stock 2.3. The phone has both internal memory (called USB Storage by the system) and an sd card; could the app be confused by the various memory locations?
I don't have a spare microsd to format as NTFS, otherwise I would try that.
Any ideas on what I should try? I am a little confused by the settings... they seem to be in many locations, so I am not sure what things to change.
Thanks!
Click to expand...
Click to collapse
Hi,
I have slightly updated the labelling in the App so should a bit less confusing
You shouldn't really need to change anything.
Partition - refers to the actual "physical" location of your drive as sen by the Androis OS / kernel but this is taken care of automatically so you dont need to specify this. Although you can still specify a partition and that will be mounted.
(You can see the list of your partitions by doing ls /dev/block/* for a command prompt for example)
Location - is where your microsd or usb device will be mounted. Basically the folder loaction on your device where you can see its files / folder contents etc.
The other option refer to the various features - such as auto mounting at boot, auto fixing ext4 permissions, auto usb mounting. If you dont need them you can disable them.
So hopefully we can narrow down the issue.
Do you have busybox,superuser installed ok?
I am not sure what the actual "Usb Storage" on the note is. Maybe there is a variation in the labelling but it should be resolvable.
If you can get me the output from your device from an adb shell or connectbot for example of the following commands:
# mount
and
# df -h
These should help me figure out what might be going on.
(i'll see If i can get my hands on a galaxy note - or have a look at some of the dev stuff in the meanwhile)
Cheers.

Hi. I also heve this problem with Galaxy Note (unable to mount USB drive with one NTFS partition).
Please describe how can i help you to figure out the issue step by step.
Thenks.

-=galex=- said:
Hi. I also heve this problem with Galaxy Note (unable to mount USB drive with one NTFS partition).
Please describe how can i help you to figure out the issue step by step.
Thenks.
Click to expand...
Click to collapse
No problems - been busy with some other work.
So far the App has been installed on the note more tham any other device so seems to be working for some.
A lot of problems are being caused by some users not unmounting the usb device after mounting it for the first time. Which confuses things. I will be releasing an update that takes care of this and possibly a self diagnostics checker that should help in identifying some potential problems.
Also android / linux can be somewhat particular about ntfs so best run a drive check in windows first. Or even better can you try another newly formatted ntfs usb device and see if that works.
I will pm you once i get the chance.
Thanks.

-=galex=- said:
Hi. I also heve this problem with Galaxy Note (unable to mount USB drive with one NTFS partition).
Please describe how can i help you to figure out the issue step by step.
Thenks.
Click to expand...
Click to collapse
I have sent you a pm. Also i have been looking at some of the note dev threads so should have a solution for you I think.
Cheers.

Hi All,
Updated the App to version 1.7.
Check the first post.
Cheers.

This is working great for my 64GB microsd as NTFS. The main problem i have (rather an annoyance) is there is now a constant notification about a "Blank SD card" in the notifications shade.
Does anyone know how to supress this, as it is very annoying to keep seeing it.

rEVOLVE said:
This is working great for my 64GB microsd as NTFS. The main problem i have (rather an annoyance) is there is now a constant notification about a "Blank SD card" in the notifications shade.
Does anyone know how to supress this, as it is very annoying to keep seeing it.
Click to expand...
Click to collapse
You could use the solution ezynow mentions in the first post. Create a small fat32 partition at the start of the SD card, this will also be accessible by things like recovery. Then use the rest of the card as NTFS.

I should apologize for not seeing that tip in the OP. I'll have to wait till i've got some time to repartition the card - any suggestions of what size to make the small one?
Only other problem I see is that the "mount at boot" option doesn't seem to work and I still have to go to the app to enable this.

Trouble with Ext4 MTP
I'm using a 32GB external sd card with a very small 8MB fat32 partition followed by an ext4 partition using the remainder of sdcard. Using Ezymount 1.9, I have been able to mount/bootmount my ext4 partition nicely. Where I'm still struggling is to get the ext4 partition to be accessible when the phone is USB attached to my Linux pc. When the USB cable is attached, I see the phone's internal sd and fat32 partition. When the EXT4 MTP option is enabled, still the fat32 partition is mounted on my pc. I've experimented with UMS and Compatibility modes, but the behavior remains the same.
On my SGS2, the default mount location for the fat32 partition is /mnt/sdcard/external_sd. I created /mnt/sdcard/external_sd_ext4. My external sdcard appears as /dev/block/cyasblkdevblk0, with the fat32 partition as p1 and ext4 as p2. I've configured Ezymount for ext4 with /dev/block/cyasblkdevblk0p2 with a location of /mnt/sdcard/external_sd_ext4. I've tried a number of points for the MTP location, but the resulting behavior remains the same.
Can you help me to get the ext4 partition accessible from my pc when attached via USB?
Thanks

GalaxyQuest99 said:
I'm using a 32GB external sd card with a very small 8MB fat32 partition followed by an ext4 partition using the remainder of sdcard. Using Ezymount 1.9, I have been able to mount/bootmount my ext4 partition nicely. Where I'm still struggling is to get the ext4 partition to be accessible when the phone is USB attached to my Linux pc. When the USB cable is attached, I see the phone's internal sd and fat32 partition. When the EXT4 MTP option is enabled, still the fat32 partition is mounted on my pc. I've experimented with UMS and Compatibility modes, but the behavior remains the same.
On my SGS2, the default mount location for the fat32 partition is /mnt/sdcard/external_sd. I created /mnt/sdcard/external_sd_ext4. My external sdcard appears as /dev/block/cyasblkdevblk0, with the fat32 partition as p1 and ext4 as p2. I've configured Ezymount for ext4 with /dev/block/cyasblkdevblk0p2 with a location of /mnt/sdcard/external_sd_ext4. I've tried a number of points for the MTP location, but the resulting behavior remains the same.
Can you help me to get the ext4 partition accessible from my pc when attached via USB?
J
Thanks
Click to expand...
Click to collapse
Hi GalaxyQuest99,
Could you please run the diagnostics report and send it to me. Hopefully, it is a configuration issue.
What phone/tablet are you using & Also what linux os are you running so i can repoduce the issue.
I am also working on some major new features - so version 2.0 is in the works
Thanks.

Diagnostic?
ezynow said:
Hi GalaxyQuest99,
Could you please run the diagnostics report and send it to me. Hopefully, it is a configuration issue.
What phone/tablet are you using & Also what linux os are you running so i can repoduce the issue.
I am also working on some major new features - so version 2.0 is in the works
Thanks.
Click to expand...
Click to collapse
I have a Samsung Galaxy S2. I use Ubuntu 12.04 LTS. I ran the diagnostics, but don't where to find the report.
Thanks

GalaxyQuest99 said:
I have a Samsung Galaxy S2. I use Ubuntu 12.04 LTS. I ran the diagnostics, but don't where to find the report.
Thanks
Click to expand...
Click to collapse
Hi,
There should be a report generated under /sdcard/ezymount_test.txt.
Could you email it to [email protected].
If there isnt a report then email me at this address too so i can you send you an updated version of the app if needed.
Will setup ubuntu and test this also.
Cheers.

Not mounting verbatim external hdd otg

Hi, I'm trying to mount a external hdd on my nexus 7 but in es file esplorer the folder is empty.
I'm stock 4.2.2 rooted, using stickmount (tried others app with no success)
Tried ntfs and fat32..
I can mount other drives but the verbatim is not accessible.
The drive has it's own power.
So i want to know if there is a workaround for this
Or not all the drives can work on the nexus 7 ?
Will a kernel or custom rom can make it work?

Tried apps especially for ntfs mounting , one see the drive but will not mount it.
Anyway I have ntsf file for stickmount, it should make it.
As I can see, it is just not mounting, stickmount say it is but not really.
Is there a way to force mount?
Or app that could bring more success?

Oh so now, with nexus media importer i can acess my disk read only mode.
Better than nothing
Still accepting ideas.

[Q] Write permissions OTG

Hey XDA,
Lately I've been wondering if it's possible to write to USB via the Nexus 10. I've been looking for a solution but I can't find anyone who actually got this question answered. I can read/copy from the USB via OTG to my nexus but I am not able to write/modify the files on the USB. The only thread I found what seems like something useful is this: http://forum.xda-developers.com/showthread.php?t=1724078 but I have no idea how this works.
I'm using RootBox ROM (latest version), I'm rooted and I am using Solid Explorer to browse through my files.
Thanks!

Joeyyz said:
... Lately I've been wondering if it's possible to write to USB via the Nexus 10. ...
Click to expand...
Click to collapse
It depends on what file system format the target media (e.g. SD Card) was formatted with. With a rooted device and a custom ROM you can get this type of support:
1) FAT16 or 32 has RW access but maximum file size of ~4GB
2) Ext2,3,4 has RW access but all ROMS do not automatically recognize these file format system formats
3) NTFS has RO access but here are instructions to add RW access capabilities
4) exFAT is a Microsoft proprietary format. An SD card formatted as exFat cannot be mounted/recognized.
A number of custom ROMs automatic mount file system formats 1-3. Rooted Stock ROM requires add on apps such as StickMount[/URL. Unrooted Stock ROM, to the best of my knowledge, only supports FAT16/32, is restricted to RO access and still needs an additional app.

3DSammy said:
It depends on what file system format the target media (e.g. SD Card) was formatted with. With a rooted device and a custom ROM you can get this type of support:
1) FAT16 or 32 has RW access but maximum file size of ~4GB
2) Ext2,3,4 has RW access but all ROMS do not automatically recognize these file format system formats
3) NTFS has RO access but here are instructions to add RW access capabilities
4) exFAT is a Microsoft proprietary format. An SD card formatted as exFat cannot be mounted/recognized.
A number of custom ROMs automatic mount file system formats 1-3. Rooted Stock ROM requires add on apps such as StickMount[/URL. Unrooted Stock ROM, to the best of my knowledge, only supports FAT16/32, is restricted to RO access and still needs an additional app.
Click to expand...
Click to collapse
I am looking to achieve number 3.
3) NTFS has RO access but here are instructions to add [URL="http://forum.xda-developers.com/showthread.php?t=1724078"]RW access capabilities
I've found that thread myself too but I have no idea how to execute the steps.

Use ktmanta kernel and USB OTG helper app... Ktmanta has ntfs built in but you'll need the app to use it...
Just tested and works perfectly
Edit: make sure you have your storage device Unmounted from your native OTG or else you will get an error from the helper app... Took me a bit to figure that out

the_boo said:
Use ktmanta kernel and USB OTG helper app... Ktmanta has ntfs built in but you'll need the app to use it...
Just tested and works perfectly
Edit: make sure you have your storage device Unmounted from your native OTG or else you will get an error from the helper app... Took me a bit to figure that out
Click to expand...
Click to collapse
Thank you! I tried it and it worked. However I was unable to rename existing folders on the USB, neither could I create folders on the USB itself. Moving files from my nexus to the USB worked great.
Why isn't this build into a rom yet so you do not have to download apps haha.

What file manager are you using?

just letting you know, es file explorer lets me create and rename folders on my drive...

Joeyyz said:
Why isn't this build into a rom yet so you do not have to download apps haha.
Click to expand...
Click to collapse
It is built into some ROMs.

the_boo said:
What file manager are you using?
Click to expand...
Click to collapse
the_boo said:
just letting you know, es file explorer lets me create and rename folders on my drive...
Click to expand...
Click to collapse
I'm using Solid Explorer, as said in the OP.
jcollier said:
It is built into some ROMs.
Click to expand...
Click to collapse
Like fully non-app OTG with NTFS write permissions? Can you give me some names?

Joeyyz said:
I'm using Solid Explorer, as said in the OP.
Like fully non-app OTG with NTFS write permissions? Can you give me some names?
Click to expand...
Click to collapse
Yes. I am using RootBox with KTManta kernel.

jcollier said:
Yes. I am using RootBox with KTManta kernel.
Click to expand...
Click to collapse
I'm using the exact same! Anyways not such a big deal, at least I can copy stuff onto the USB now. Can't wait til RootBox gets auto mount + write permissions for NTFS usbs so I don't have to use the OTG helper app!

All I did to get RW on NTFS (on all ROMs that I've tried) was to install Stickmount(pro) and NTFS Mounter ! I've never really had a problem with it, just choose them as default if asked. Plus I have found if you run them both first before inserting the OTG it seems more liable to work.
Thought this might help
USB is in the directory - SDcard/usb storage/sda1
Sent from my Nexus 10 using XDA Premium HD app

[Q] [PA 3.99] Enable USB mass storage instead of MTP?

Hello,
Is there a way to enable USB Mass Storage on Paranoid Android 3.99? I know it will supposedly prevent the phone from accessing the virtual sdcard partition while plugged to a computer, but this would be a minor annoyance in comparison to the complete pain in the ass that is MTP:
1. Transfers are slow and unreliable (stopping unexpectedly...)
2. It can only perform one task at a time (can't browse folders while copying files for example)
3. Poor implementation on Windows (Explorer keeps asking stupid questions like "are you sure this type of file will be recognized by your device?")
4. Computers with restricted user rights prevent MTP devices from installing.
and so on...
I've tried the following trick:
Code:
su
setprop persist.sys.usb.config mass_storage
reboot
But it didn't work.
Please help. I know it may require a lot of effort but I don't care: MTP is really too much of an annoyance.

No you cannot mount the sdcard as usb mass storage
In order to do that the sdcard has to be it's own fat partition.
On the nexus 4 it is part of the data partition and the folder is fused to the sdcard mount point.
Basically meaning that you can't mount /sdcard because it's not able to be mounted as it's not actually a partition.
And secondly the format is ext4 so even if you could mount it, it would not be readable by Windows
Sent from my Nexus 4 using xda app-developers app

Alex240188 said:
No you cannot mount the sdcard as usb mass storage
In order to do that the sdcard has to be it's own fat partition.
On the nexus 4 it is part of the data partition and the folder is fused to the sdcard mount point.
Basically meaning that you can't mount /sdcard because it's not able to be mounted as it's not actually a partition.
And secondly the format is ext4 so even if you could mount it, it would not be readable by Windows
Click to expand...
Click to collapse
How would Android react if /sdcard was actually a separate FAT32 partition mounted in its usual location?

CutterX said:
How would Android react if /sdcard was actually a separate FAT32 partition mounted in its usual location?
Click to expand...
Click to collapse
According to this article that should work.
http://www.engadget.com/2011/11/21/ice-cream-sandwich-supports-usb-mass-storage-after-all-galaxy-n/
Swyped from my Nexus 4 using Tapatalk 4

CutterX said:
How would Android react if /sdcard was actually a separate FAT32 partition mounted in its usual location?
Click to expand...
Click to collapse
It would work. However doing that is not an easy task.
It would require;
1. Changing the partition table on the phone.
2. Rewriting the bootloader (not 100% sure on this one, but it would be needed to flash any rom from the bootloader (stock)).
3. Rewriting a recovery to support the new partition.
4. Finally making the changes to the rom to support ums mounting.
Sent from my Nexus 4 using xda app-developers app

It looks like this would be something in relatively high demand. So I've been trying to get Android/vold to mount and recognize a vfat image as an sdcard but haven't had any success. It might be easier to work with if I killed off the fuse mount to start, but I'm not really looking to do that right now. Manually mounting the image isn't a problem (busybox mount or using losetup first to establish the loop) but without Android recognizing it, there's no chance of being able to use usb mass storage.
Of course the inherent issue will then be "lost" space with regards to the internal storage, since it'd be dedicated to the "sdcard". It seems most users would be fine with this, setting aside a gig or two.