Hello,
All is in the title. UMS is not working, that's a fact, but where does it come from ? A kernel issue ? I doubt else CM10 team or Kholk would have been able to make it working.
Thank you for your answers
UMS requires several things, like a physical partition.
our internal storage isnt a physical partition - its located at the /data partition in the folder media.
we could only tell to UMS to use the whole data partition but thats not what we want cause we would see our whole data partition as mass storage device and also it would use the ext4 filesystem and not fat32. ext4 is only natively supported by linux distributions and not by windows or mac osx (you would need additional ext4 drivers).
now you say /sdcard actually looks like a physical partition, but thats not true. /data/media (internal storage; ext4) can be emulated to /sdcard (fat32) with FUSE but because its not a physical partition (block special/device) it cant work with UMS.
gordon0001 said:
UMS requires several things, like a physical partition.
our internal storage isnt a physical partition - its located at the /data partition in the folder media.
we could only tell to UMS to use the whole data partition but thats not what we want cause we would see our whole data partition as mass storage device and also it would use the ext4 filesystem and not fat32. ext4 is only natively supported by linux distributions and not by windows or mac osx (you would need additional ext4 drivers).
now you say /sdcard actually looks like a physical partition, but thats not true. /data/media (internal storage; ext4) can be emulated to /sdcard (fat32) with FUSE but because its not a physical partition (block special/device) it cant work with UMS.
Click to expand...
Click to collapse
Damn, so we have to use MTP and PTP protocol. On linux what tool do you suggest? I don't have windows on my pc. It looks a bit uncomfortable for me...
Neither with external sdcard we can have UMS?
external sdcard would work fine without problems.
developers just need to support it.
Gesendet von meinem LG-P880 mit Tapatalk 4 Beta
Thank you Gordon001 (clicked on 'thank you').
I have been circonspect when came the time of emulated layout MTP is slow on my side, and UMS was really easy to use.
My main concern is i'm not able to make DriveDroid working. I think it was the lack of UMS, but it seems i'm wrong, because DriveDroid is implementing is own layer on its media img/iso. Do you have experience on DriveDroid ? (CM10.2 for me).
There was an app somewhere to enable UMS on the O4X... wait... Ah, here it is: USB Mass Storage App for the LG Optimus 4X. Didn't try it yet, as I mostly stick to ADB
yes, indeed, but it is not compatible with CM10.2
Related
Paragon NTFS & HFS+ mounts NTFS/HFS+ formatted USB drives or SD cards automatically!
"Paragon NTFS & HFS+"
https://play.google.com/store/apps/details?id=com.paragon.mounter&hl=en
!!Requires root!!! To verify root access please use Root Checker app.
The only solution available on the market that mounts NTFS/HFS+ formatted USB drives or SD cards automatically!
Forget about incompatibility issues! Get unlimited access to the most widespread file systems in the world on your smartphone by mounting USB sticks or SD cards formatted to Windows NTFS or Mac OS X HFS+. Now you can easily copy, transfer and modify data previously unsupported by Android volumes.
The software was successfully tested by nearly 50,000 Android enthusiasts!
What’s new?
• Mount on boot: automatically mount all NTFS and HFS+ partitions available on boot completion
• Mount on connect: automatically mount NTFS and HFS+ partitions when a new media is connected.
The software is based on Paragon’s Universal File System Driver (UFSD) technology. UFSD is the leading cross-platform technology with millions of satisfied end users worldwide. It includes exFAT, NTFS, and HFS+ driver technology, which fully supports SDXC cards and Windows/Mac USB drives.
reserved
dborello said:
"Paragon NTFS & HFS+"
https://play.google.com/store/apps/details?id=com.paragon.mounter&hl=en
!!Requires root!!! To verify root access please use Root Checker app.
The only solution available on the market that mounts NTFS/HFS+ formatted USB drives or SD cards automatically!
Forget about incompatibility issues! Get unlimited access to the most widespread file systems in the world on your smartphone by mounting USB sticks or SD cards formatted to Windows NTFS or Mac OS X HFS+. Now you can easily copy, transfer and modify data previously unsupported by Android volumes.
The software was successfully tested by nearly 50,000 Android enthusiasts!
What’s new?
• Mount on boot: automatically mount all NTFS and HFS+ partitions available on boot completion
• Mount on connect: automatically mount NTFS and HFS+ partitions when a new media is connected.
The software is based on Paragon’s Universal File System Driver (UFSD) technology. UFSD is the leading cross-platform technology with millions of satisfied end users worldwide. It includes exFAT, NTFS, and HFS+ driver technology, which fully supports SDXC cards and Windows/Mac USB drives.
Click to expand...
Click to collapse
Does the micro sd card have to be formatted first in any particular format prior to installing the app?
hkjr said:
Does the micro sd card have to be formatted first in any particular format prior to installing the app?
Click to expand...
Click to collapse
No
Sent from my GT-I9300 using xda app-developers app
Works like a charm on my P3100.
I had to block this app cuz ask lot permission every 10min and battery drain, when need it have to unlock it from titanium. Is it normal?
Inviato dal mio Galaxy Nexus con Tapatalk 2
Fuse is not present on this device
Sony Experia Miro ..
what to do?
please help
Doesn't work on 4.2+
Hi,
I can mount my NTFS or HFS drive, I always get a 255 error: 255 mkdir failed. Any ideas?
Thanks
Piemo said:
I had to block this app cuz ask lot permission every 10min and battery drain, when need it have to unlock it from titanium. Is it normal?
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
+1
Doubt
does this apk works for ROOTED MOTO E to connect a pendrive through OTG cable since MOTO E doesnt have USB debugging mode???
plzzz provide me an answer
Hi all,
Just got me an Xperia T, very happy with it.
Only thing I am having trouble understanding is how the file system works, please let me try and explain.
I have a 16gb micro SD card in the device and it also has 16gb of internal storage.
When I mount the device to windows it shows two drives (Internal Storage and SD Card), now these are pretty obvious as to which each one is.
Now my quandary: When I use astro file manager to browse the phone the file system is different (in fact pretty much the opposite).
The micro SD card shows up as "ext_card" and the internal storage (I think) shows up as "sdcard" and then there is another folder called "int_storage" that is empty.
Is this correct?
Could someone please clarify this for me?
Thanks,
Dave
Yes, this is the way it's supposed to be.
When you connect to the PC using MTP, you mount SDcard and ext_card from mnt.
Sent from my elegant Xperia™ Ion using xda premium app.
Cheers for the super fast response!
I thought that was how it was working but it was just a little confusing since it swaps around the name of each drive when plugged into windows.
Thanks again.
The way the T handles internal storage is a little odd...
Older devices have the "internal SD" formatted as FAT32.
Newer Android devices have this trick called emulated storage, where a FUSE module does special permissions magic to allow /data/media (on an ext4 system) to be mounted to /sdcard
The T is a little odd in that instead of using /data/media, it has int_storage or something like that, which is then remapped via FUSE to /sdcard. It's the only device I know of to have the internal SD formatted as ext4 but not "unified" internal storage (e.g. /sdcard is just a directory under /data)
Didn't really understand any of that.
But it's nice to know that I was right and it does handle the storage a little strangely (I deduced that much from your post at least).
Hi
Like most of you guys know, if you install
a CM based Rom the mount points of the internal storage are three different ones.
The normal "/storage/sdcard0",
"/data/media/0" and both "/storage/emulated/0" or "/storage/emulated/legacy".
So now my question is, does this mean the data on internal memory requires four times its actual space? And if so can I delete all of them except one?
Thanks in advance for your answers
Sent from my LG-P880
the reason is our device doesnt have a seperate partition for the internal storage. instead of this the internal storage is located at the /data partition in the directory media. /data uses ext4 which means /data/media, our internal storage, uses it too and that is the problem because we want to be able to transfer files to/from your computer.. just.. ext4 isnt natively supported by windows and mac osx. it would require to install ext4 drivers. now.. fat32/vfat is supported by almost any operating system. so we need to get ext4 to fat32.. but how? with emulation (fuse). google specified where and how to mount and where to create symlinks/references to the emulated internal storage for compatibility reasons.
these symlinks/references point to the internal storage. so these are not copies. in summery any of this folders are indirectly linked with /data/media.
if you store a file at /sdcard/ or /mnt/sdcard, and the others you actually store it to /data/media
Gesendet von meinem LG-P880 mit Tapatalk 2
OK thanks for the explanation, but then why it is, that I have about 3 GB in the data/media/0 folder (the actual internal storage) and in total more than 7 GB used? The system itself doesn't require 4 GB of my internal storage, does it?
Sent from my LG-P880
Omario-242 said:
OK thanks for the explanation, but then why it is, that I have about 3 GB in the data/media/0 folder (the actual internal storage) and in total more than 7 GB used? The system itself doesn't require 4 GB of my internal storage, does it?
Sent from my LG-P880
Click to expand...
Click to collapse
With Android Jellybean 4.2 multiple user support was added. Each user get's his own private internal storage and settings. Other users can't access them except with root rights. /data/media/0 defines the private storage for the first user. /sdcard is then the emulated internal storage using /data/media/0, not /data/media. So there must be data that takes 4GB of space directly at /data/media exluding folder 0 that has 3GB of data.
/sdcard/emulated is pointed to private storage for the currently logged in user.
http://android.stackexchange.com/questions/35541/why-did-sdcard-turn-into-sdcard-0-with-4-2
Some of you might already know that I accidentally formatted my 64gb SDCard to ext4. I tried to format it again back to exFAT but I can't. Windows isn't detecting it. Tried different applications like MiniTool Partition and still no go. Tried to use Ubuntu on a virtual machine and still nothing. My last hope is to use a kernel supporting ext4. So how do I implement ext4 support?
I'd like to remove my external SD card and use my Linux (RHEL/CentOS) workstation to copy files to and from it. The card has not been encrypted and is 6¤ GB in size.
Unfortunately the workstation did not recognize the file format, Solid Explorer on the tablet does not tell me which file system is used and Googling suggests it may be a special flash file system suitable for SD cards, presumably not available on desktop Linux distributions.
Does anyone have information?
Probably exfat.
Diskinfo will tell you what it is.
Should be FAT or exFAT
Thank you, have downloaded DiskInfo from the Play Store to my phones but not yet to the tablet. I know RHEL/CentOS has drivers for MSDOS (FAT) and vFAT but do not know about exFAT.
hga89 said:
Thank you, have downloaded DiskInfo from the Play Store to my phones but not yet to the tablet. I know RHEL/CentOS has drivers for MSDOS (FAT) and vFAT but do not know about exFAT.
Click to expand...
Click to collapse
It is definitely exfat and it is an exfat flavor that can't be duplicated on Windows according to Microsloth. Although you should be able to read/write the card from a Windows PC do not try to format it on a PC. The M/S exfat format does not handle large filesystem cards.
You can read/write and I think format the card (if needed) from Linux using exfat-fuse. I built it from source the other day, took all of three minutes. Good stuff!
Depending on your package manager you should be able to search on exfat or fuse and find the drivers.
BTW I did some experimenting with card filesystems since the internal memory is supposedly ext4. I formatted a memory card ext3 and the S7 couldn't read it.
Would have been nice to have a standard portable filesystem available instead of having to use something proprietary that google has to pay Microslop for.
midnightrider said:
It is definitely exfat and it is an exfat flavor that can't be duplicated on Windows according to Microsloth. Although you should be able to read/write the card from a Windows PC do not try to format it on a PC. The M/S exfat format does not handle large filesystem cards.
You can read/write and I think format the card (if needed) from Linux using exfat-fuse. I built it from source the other day, took all of three minutes. Good stuff!
Depending on your package manager you should be able to search on exfat or fuse and find the drivers.
BTW I did some experimenting with card filesystems since the internal memory is supposedly ext4. I formatted a memory card ext3 and the S7 couldn't read it.
Would have been nice to have a standard portable filesystem available instead of having to use something proprietary that google has to pay Microslop for.
Click to expand...
Click to collapse
Have had no issues formatting 64gb sd cards as exFAT in Windows. I see no reason why it wouldn't be compatible.
It's a Windows format that has been incorporated to work on Samsung Android devices.
As for Google I don't think exfat is yet natively supported on AOSP unless it's been added recently.
You were right, a small SD card used VFAT while a 64 GB card used exFAT. The former can be read natively on RHEL/CentOS and there are third-party drivers for the latter.
Thank you, DiskInfo looks like a very nice utility.