default USB Mass storage issue - HD2 Android Q&A, Help & Troubleshooting and Genera

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!

Related

SDCARD Mounting Paradigm - Cyanogenmod7

There are two sdcard mounting paradigms. Currently Cyanogenmod for the tablet is set to use the one that matches phones.
1) Internal SDCARD mounted to /SDCARD, External to /SDCARD2(or equivalent)
Pros
-Internal sdcard is easily accessible
Cons
-External sdcard isn't mounted to computer over usb
2) Internal SDCARD mounted to /EMMC, External to /SDCARD
Pros
-External SDCARD is default and mounted to computer over usb
-Works well for phones with small internal storage sizes
Cons
-Your internal storage is hard to access, not mounted over usb
I took this GIT commit and rolled the changes back for CM7. I then recompiled CM7 to use the option 1 mounting paradigm.
Let me know which you prefer. I personally like option 1 because it doesn't rely on having an external sdcard. Additionally the internal sdcard is not easily removable like the external, so being able to access it over usb is important. If there are reasons for options 2, let me know.
Download:
CM7RC0 with Option 1 Mounting Paradigm(Mounting over USB works): http://www.multiupload.com/NJFGUW04A2
Gapps: http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip
Very cool, I was planning to do that myself this weekend. I played with CM7 yesterday for a few minutes but with no SDCard in the "external" slot there were some limits to have useful the OS was....
I'll probably still pull the source down this weekend, but I can flash your ROM tonight and start having a more detailed look at CM7.
Hey Rothnic, nice call, I agree that the CM7 default mounting scheme is both somewhat confusing and somewhat less useful with the G Tablet.
Quick question - you packaged up those performance packs with updated drivers for TNT etc. I know this may be a dumb question, but are these the same drivers currently being used in CM7? Or are they Froyo specific and incompatible with a Gingerbread ROM build because of library dependencies or structural changes?
I'm just trying to figure out if there's some way to speed up 2d graphics stuff in CM7 without waiting for more drivers from NVidia.
rcgabriel said:
Hey Rothnic, nice call, I agree that the CM7 default mounting scheme is both somewhat confusing and somewhat less useful with the G Tablet.
Quick question - you packaged up those performance packs with updated drivers for TNT etc. I know this may be a dumb question, but are these the same drivers currently being used in CM7? Or are they Froyo specific and incompatible with a Gingerbread ROM build because of library dependencies or structural changes?
I'm just trying to figure out if there's some way to speed up 2d graphics stuff in CM7 without waiting for more drivers from NVidia.
Click to expand...
Click to collapse
CM7 uses the Nvidia libraries from TnT 3588. I haven't gotten to merging in the newer "performance pack" ones that TnT doesn't include.
The libraries are Froyo specific, and were for many devices. I believe the CM team has built wrappers so that it can use the froyo specific libraries. I'm not sure on the acceleration issue.
Ok I got 2 questions:
Do we have any clue how does Incredible (for example) works? It has 8gb internal plus External, they both mount on usb.
Doesnt the fact that we can mount the internal storage on the computer, etc etc, can be a reason for the corruption of partitions? (maybe unplugged before unmounting by mistake or stuff like that..). That may have happen to almost everyone, everything starts crashing, FC, etc, all because of the repartitioning. Maybe paradigm 2 its better and correct.
Another quick thing, is it possible to mount internal on /scard and external on /sdcard/sdcard2? That would make both accesible on usb mount no?
Thanks
great work rothnic
I tried to play with cm7 last night but was getting frustrated by this issue. Thanks for doing this!!
+1 for /SDCARD here...
thanks, rothnic
Thanks for the efforts. Oh, option 1until I can get my hands on a 32GB micro SD, but probably still favor /sdcard and /sdcard2 anyhow.
Also, can't wait for hardware acceleration with this Rom, best one so far.
I like option 1 over option 2 for the gTab. What would really be cool is an option 3.
Internal + External = virtual SDCard.
+1 for Option 1.
If it is going to be a 'true' Cyanogen port, it should probably use the default Cyanogen behavior, which is Option 2.
This is meant as a discussion for the merits of each. For my use case option 1 makes sense.
Id like to hear why option 2 makes sense to others. How do you access your 14gb of internal storage?
slaughts said:
If it is going to be a 'true' Cyanogen port, it should probably use the default Cyanogen behavior, which is Option 2.
Click to expand...
Click to collapse
This is handled in the device specific config files so in no way makes it different. Each device has its own specific mounting scheme.
I prefer option 1, because it does not depend on having the external inserted.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
danielsjam said:
I prefer option 1, because it does not depend on having the external inserted.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
This has to be the most compelling reason on why it should be mounted as sdcard and sdcard2.
thebadfrog said:
This has to be the most compelling reason on why it should be mounted as sdcard and sdcard2.
Click to expand...
Click to collapse
I agree. I prefer internal being SDCARD.
A vote for Option 1. As a temporary solution, I go into the Terminal Emulator and type
Code:
su
mount /emmc/ /sdcard/
and it works
gksmith said:
I like option 1 over option 2 for the gTab. What would really be cool is an option 3.
Internal + External = virtual SDCard.
Click to expand...
Click to collapse
You mean.............just like Windows Phone 7?
It depends on the read/write speed of the sdcard. But since the internal sdcard is shared with other system partitions it makes sense for the external sdcard to be mounted at /sdcard, especially if you have media on it. Processes that read/write to /sdcard (like Gallery) can't mean anything good for performance. What we should have is both the sd and emmc to have /data, /system, and /sdcard mdraid partitions created and mounted/initialized for a nice perf increase. I wonder if its possible with android. It certainly is supported in the kernel with the right config. I should check to see if there are arm binaries for mdadm. Then i could create a test partition to measure performance.
Oh and CIFS is what i use to xfer files. There are plenty of ways to access partitions without mounting them as a drive. I think that usually leads to trouble. There is even file expert which lets you create smb shares... there prob solved, map network drive.
Blades said:
It depends on the read/write speed of the sdcard. But since the internal sdcard is shared with other system partitions it makes sense for the external sdcard to be mounted at /sdcard, especially if you have media on it. Processes that read/write to /sdcard (like Gallery) can't mean anything good for performance. What we should have is both the sd and emmc to have /data, /system, and /sdcard mdraid partitions created and mounted/initialized for a nice perf increase. I wonder if its possible with android. It certainly is supported in the kernel with the right config. I should check to see if there are arm binaries for mdadm. Then i could create a test partition to measure performance.
Click to expand...
Click to collapse
How would you handle people who do not have an external sdcard?
One more for option 1.

[Q solved] cannot mount sdcard in recovery

So this was solved by using a tool from sdcard.org to format my sdcard in a PC. Once formatted with that tool cwm started seeing correctly.
-------
I'm running 3.1 rooted
I've flashed Thor's 1.4.2 recovery.
I have two sd cards: a 2g and an 8g.
Both work when accessed on a PC and on the iconia.
Neither work in cwm so I can't flash any roms.
I have tried formatting the sdcards on two different PCs. for the 2g I tried both fat and fat32. The 8g is fat32. In every case cwm says it can't mount it.
Additionally, I can't seem to use a USB key, although that may be that i don't know how to use it.
Thanks for any help.
-Bert
When in CWM and you go to install zip from sdcard do you see any folders where you choose the zip. Just wondering if it isn't mounted already. Physical sdcard is in /mnt/external_sd
and not /mnt/sdcard.
PsychosisNC said:
When in CWM and you go to install zip from sdcard do you see any folders where you choose the zip. Just wondering if it isn't mounted already. Physical sdcard is in /mnt/external_sd
and not /mnt/sdcard.
Click to expand...
Click to collapse
Thanks for your reply. I'm prety sure It's not mounted already.
I'm attaching a screenshot to show the exact message I get when trying to browse for a zip. I get a similar message when I go to mounts and storage and try to mount the sdcard.
im bumping this because I'm really becoming concerned that the device is defective in some way.
I'm hoping that someone can give me some guidence on what I may be doing wrong.
So, brosell, did you figure out a solution? I have the exact same problem - cannot mount sdcard in recovery and I get the exact same message.
When the system is booted normally, the internal storage mounts ok as /sdcard
EDIT:
It seems CWM treats the external sdcard as /sdcard, not the internal storage. So, to flash an update, you need to place it on an external SD card
I always get that error, and I never had to mount anything using cwm, just booted it selected the zip to flash and flash. I still don't mount anything...?
And the zip goes on the external sd not the inturn
Can't format SC Card in Window. If won't mount.
Guys,
Unfortunately SD cards for Android must be formatted by Android. If the card is not properly formatted CWM can not mount it, nor can CWM format it. The best way to get it properly formatted is to put it into an Android Phone and use its format functions. There really is no way on the Icona Tab to reformat an improperly formatted card or a new formatted card. If you don't have an Android phone borrow a friends. You will know that it is properly formatted when you see a lost files folder created on the card by the Android phone formatting process. This is a common problem that many people encounter when performing their first ROM flash. If it was formatted under windows as FAT 32 you can access it and store on it in normal operation mode. But ClockWorkMod can not mount it in recovery mode. Hope this helps. Good luck.
Can mount SD card in Recovery
I should have also mentioned last night in my post here, that my experience has been that it is much easier to flash a new custom ROM from a USB thumb drive. Flashing a custom ROM from USB seems to be less problematic than from an SDCard that appears otherwise to be good and formatted with FAT32, but CWM can't mount it. You can fast format the thumb drive on Windows to clean it off. Then copy your custom .zip ROM to be flashed on to the thumb drive from within Windows then insert it into the USB port of your Icona Tab, boot into CWM recovery (I'm assuming you know how to do that so I won't go into it here.) I forget exactly where in the CWM menu it is, it might be under the CWM advanced sub-menu but it say's something to the effect of Install zip from USB. It always works for me with no problem. The advantage is that you do all your prep work on Windows and then flash from the thumb drive which I believe has an ISO standard across all platforms and usually comes already per-formatted. This is an alternative method if you can't get your SDCard properly formatted (see my previous post in this thread for how to get it properly formatted so that it will mount under CWM.) Again, good luck!
I want to cry!!
I tried re formatting! Nothing! Cmw is not on sd card! Nothing is working! Still stuck on acer start screen! Yes i am a noob! But i read alot into this stuff b4 i do it! I wish there was someone i can have come to my house and do this for me! I have tried everything!!!!!!!!!!! So frustrated!!! Someone pls help me!!!!
in CWM recovery, there are 2 options,sd and "internal sd" i think(for me atleast). i chose the internal sd and it mounts.
brosell said:
So this was solved by using a tool from sdcard.org to format my sdcard in a PC. Once formatted with that tool cwm started seeing correctly.
-------
-Bert
Click to expand...
Click to collapse
Thank You Sir! been looking for this fix for a long time
brosell said:
So this was solved by using a tool from sdcard.org to format my sdcard in a PC. Once formatted with that tool cwm started seeing correctly.
-------
/QUOTE]
thanks brosell, for the solution,
I have a 512MB SD card in the g5360, was FAT formatted. reformatting the sdcard with the tool from sdcard.org worked for me as well, afterwards it could be mounted by the stock recovery
and could install update.zip (prior to install CMW)
kr, Erik
Click to expand...
Click to collapse

IDEA: Hacking internal/external sdcard mount paths

Hello.
I'm using the latest aurora and I'd like to discuss an idea I had.
Since the U8800 has plenty internal memory and it's quite fast comparing to an average sd card, it'd be great if we could use the internal memory for the tasks that need "speed" instead of "space".
Running apps from the sd card is the perfect example!
So the idea would be, while keeping the external sdcard mounted on /mnt/sdcard, having /mnt/sdcard/Android/data, for instance, point to the «internal sdcard path»/Android/data.
What do you think would be the best solution:
- hacking the mount points?
- using links?
- other solution?
Any developer or filesystem savvy user can point the advantages or dangers of using this solution?
- e.g.: the system or some apps may check if the external sd-card is mounted before trying to read/write to /mnt/sdcard/Android/data... that would mean the system/those apss may think that path isn't reachable with the ext-sdcard unmounted, altough they can be read.
Suggestions? Rants? Ideas?
Regards!
I have wondered if the /data/app or maybe the whole /data partition could be mounted in the internal storage partition. That would give 2gb space for apps and associated files instead of 3-400 ish and would mean no need to move apps to sd card which would mean faster loads at startup due to internal memory being faster.
VuDuCuRSe said:
Hello.
I'm using the latest aurora and I'd like to discuss an idea I had.
Since the U8800 has plenty internal memory and it's quite fast comparing to an average sd card, it'd be great if we could use the internal memory for the tasks that need "speed" instead of "space".
Running apps from the sd card is the perfect example!
So the idea would be, while keeping the external sdcard mounted on /mnt/sdcard, having /mnt/sdcard/Android/data, for instance, point to the «internal sdcard path»/Android/data.
What do you think would be the best solution:
- hacking the mount points?
- using links?
- other solution?
Any developer or filesystem savvy user can point the advantages or dangers of using this solution?
- e.g.: the system or some apps may check if the external sd-card is mounted before trying to read/write to /mnt/sdcard/Android/data... that would mean the system/those apss may think that path isn't reachable with the ext-sdcard unmounted, altough they can be read.
Suggestions? Rants? Ideas?
Regards!
Click to expand...
Click to collapse
Well this is known for a while now . Quoted from my thread here:
vold.fstab - CHANGE THE DEFAULT SDCARD: -thanks to julle131
There is this file named vold.fstab at your /system/etc/ folder, which controls which of your sdcards (Internal/External) will be mounted when you connect your phone to the PC. The last 2 lines are the only that matter. These are the two possibilities:
EXTERNAL SDCARD MOUNTED (DEFAULT):
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host
dev_mount emmc /mnt/sdcard1 14 /devices/platform/msm_sdcc.2/mmc_host
INTERNAL SDCARD MOUNTED:
dev_mount sdcard /mnt/sdcard 14 /devices/platform/msm_sdcc.2/mmc_host
dev_mount emmc /mnt/sdcard1 auto /devices/platform/msm_sdcc.4/mmc_host
change them as you wish with a root explorer or before flashing.
Click to expand...
Click to collapse
Make this change and every app will use the internal sdcard. Gallery works ok with images to external sdcard, it just might take a while for the first refresh. But I don't know if you'll notice any difference in terms of speed....
Cheers
spirosbond said:
Well this is known for a while now . Quoted from my thread here:
Make this change and every app will use the internal sdcard. Gallery works ok with images to external sdcard, it just might take a while for the first refresh. But I don't know if you'll notice any difference in terms of speed....
Cheers
Click to expand...
Click to collapse
That's not what he talked, I think. He said that the apparel would be installed on the external sd card, but the data would be moved to the internal one. And we have speed, but the main card would be the external one.
I think its a great idea if I understood it right!
Sent from my U8800 using xda premium
mrasquinho said:
That's not what he talked, I think. He said that the apparel would be installed on the external sd card, but the data would be moved to the internal one. And we have speed, but the main card would be the external one.
I think its a great idea if I understood it right!
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Oh I see! Sorry about that. As far as I know apps are not choosing were to put their data. They just say to the OS "I want these things to be at the sdcard" and the OS puts them at the correct place. So you can't "hack" the app to "see" at somewhere else. On the other hand the OS initialises on boot which card is the primary and which is the secondary. So my knowledge stops there and I can't imagine a way to make this separation between app data and the rest...
I hope for someone else's help!
PaulMilbank said:
I have wondered if the /data/app or maybe the whole /data partition could be mounted in the internal storage partition. That would give 2gb space for apps and associated files instead of 3-400 ish and would mean no need to move apps to sd card which would mean faster loads at startup due to internal memory being faster.
Click to expand...
Click to collapse
Maybe this cannot be done, because I think that the mapping of the partitions and mounts comes from the bootloader, but there is already the solution of resizing the data partition using the space of internal storage.
PaulMilbank said:
I have wondered if the /data/app or maybe the whole /data partition could be mounted in the internal storage partition. That would give 2gb space for apps and associated files instead of 3-400 ish and would mean no need to move apps to sd card which would mean faster loads at startup due to internal memory being faster.
Click to expand...
Click to collapse
That's a great idea!
I almost don't use the so called "internal sd card", therefor I have 2GB of fast empty space being wasted.
Why not simply mounting the internal sd-card partition in the data folder and the data partition on the internal sd card folder?
I only use the internal sd card to hold ringtones and other small stuff that I need to be in accessible 100% of the time, so a few hundred MB are enough!
Me gusta!
Every ROM flashes it's own fstab, right?
So all we'd need to do would be, editing the fstab before flashing it.
-----------------
Regarding the my first idea... I don't think one can simply mount a path on another path. We'd need a "virtual" device pointing to /mnt/sdcard-internal/data/ then mount that virtual device on /mnt/sdcard-external/data/.
My knowledge of unix mount/filesystems is not much more than what's explained here: https://help.ubuntu.com/community/Mount
OK, just found this:
http://askubuntu.com/questions/11079/mount-a-directory-to-look-like-a-drive
there is a FUSE filesystem named bindfs that probably does exactly what you want. For example the following:
bindfs -n /media/USB-HDD-01/ISO/ /home/johnc/ISO-images
Click to expand...
Click to collapse
would result in ISO-images to show up as a mounted filesystem in the Places sidepanel in Nautilus. The -n is required because otherwise bindfs tries to use the allow_other FUSE option, which by default is not allowed for regular users (if you use bindfs in /etc/fstab this is not a problem).
The first directory you give is the existing one, the second directory you give is an empty directory under which the contents of the existing one will appear.
Click to expand...
Click to collapse
So, bindfs depends on FUSE... and there's a port of fuse to android: https://github.com/seth-hg/fuse-android but looking at the README I get the feeling that it's not really working. The last step would be having a kernel with FUSE support... and regarding that, I have no idea, how easy it is to get a kernel like that for our U8800 :\
Finding such a solution to expand the DATA partition indirectly would be great!
I used to apply genokolar's custom partition method as "1.2G DATA + 1.46G INTERNAL SD" before, but i found out that it has some issues with Official 2.3 Roms. One of them -the most important IMHO- is the BOOTLOOP problem occurring in some specific situations!!!
See the details in my post here:
http://forum.xda-developers.com/showpost.php?p=25853141&postcount=134
(Seems that I don't encounter the bootloops on Custom Roms, but i'm not %100 sure and never will be )
So i unfortunately gave up using it, and revert to the stock partition .
I will be grateful to the one who will find a better and reliable solution. Hope to see it soon...
I still have to gather more information on the official update "modus operandi".
My goal is to simply reformat both partitions and then swap their mount points.
If the official update formats the partitions before applying the flashing official ROM files, then partitioning changes shouldn't cause any failure on the official update.
But like I said, I'm still yet to confirm that info.
Gen's idea was great (I learned a lot just by looking at his scripts) but resizing partitions has its dangers.
Since "no one" really uses the internal memory, why not simply exchange its room with /data, right?
This would be awesome! I would love to have 2gb for apps, instead of cluttering my phone.. plus the 2gb of internal storage are just a waste for me.. I never use them.. so this would be great!

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.

SM-T580: Issue with Card Card setup (Link2SD and Titanium access)

Edit: Title should read "SD Card" (how to edit that?)
I have root and I am trying to get Link2SD to work. I have created the FAT32 (primary) and EXT4 (primary) partitions but I keep getting a mount script error ("unable to mount") (Also tried EXT2)
I am doing the same thing as I have done on several other devices and it is not working on the samsung.
Also, I am having issues with getting Titanium Backup to wrtie to the SD card too. I tried the Kitkit SD card patch but it failed.
I know the SD card works so I am thinking it is a wonky Samsung thing?
Thoughts or advice
Edit: Pulling SD card, re-inserting and rebooting and then Link2SD reports that the 2nd partition is not accessible during boot (and suggests quick boot to fix which it does not). Samsung says the FAT32 is fine but the EXT is "corrupt" but I have confirmed on two other devices it is fine.
So this seems to be some sort of access thing. Maybe related to the removal of encryption patch as part of the TWRP install?
Edit2: cat /sys/block/mmcblk2/device/type gives back "no such file or directory"; (whereas mmcblk1 gives SD)
Total commander shows sd-card (which is internal /storage/emulated/0), sd-card(2) "/data/sdext2"), and USB (SD FAT32 as /storage/BDB2-8960)
Got TB fixed anyway. Backup one file (on device internal location), move the directory to external SD card, then TB decided it is was OK to include that location under settings so select new location.
Now need Link2SD. Could this be a mount script write issue? Encryption issue (I removed it from internal via a scripted)?
Runings Mounts2SD, installed scripts, reboot but it says External is "not mounted". Link2SD still fails with those scripts installed.
chemie99 said:
Got TB fixed anyway. Backup one file (on device internal location), move the directory to external SD card, then TB decided it is was OK to include that location under settings so select new location.
Now need Link2SD. Could this be a mount script write issue? Encryption issue (I removed it from internal via a scripted)?
Runings Mounts2SD, installed scripts, reboot but it says External is "not mounted". Link2SD still fails with those scripts installed.
Click to expand...
Click to collapse
Link2SD never worked for me either no matter what I did. Apps2SD works flawlessly. Links data, apk, obb files and everything without any issues on ext4 format.
moxalis said:
Link2SD never worked for me either no matter what I did. Apps2SD works flawlessly. Links data, apk, obb files and everything without any issues on ext4 format.
Click to expand...
Click to collapse
I tried installed Apps2SD but it never asked for root and decided half the apps could not be moved. I figured it was just offering the usual stock "move apps" which moves marginal amount.
Samsung says that the EXT partition is corrupt but Aparted says it is fine. EXT2, and EXT4 created in either Minitool or Aparted are simply not read.
Mount2SD adds scripts to mount but the partition remains unmounted after reboots.
What format does Samsung want?
chemie99 said:
I tried installed Apps2SD but it never asked for root and decided half the apps could not be moved. I figured it was just offering the usual stock "move apps" which moves marginal amount.
Samsung says that the EXT partition is corrupt but Aparted says it is fine. EXT2, and EXT4 created in either Minitool or Aparted are simply not read.
Mount2SD adds scripts to mount but the partition remains unmounted after reboots.
What format does Samsung want?
Click to expand...
Click to collapse
Samsung reads the partition as corrupt but Apps2SD is using it just fine. You should delete any mount scripts and re-create them through the Apps2SD application.
moxalis said:
Samsung reads the partition as corrupt but Apps2SD is using it just fine. You should delete any mount scripts and re-create them through the Apps2SD application.
Click to expand...
Click to collapse
How do I manually delete the mount scripts?
chemie99 said:
How do I manually delete the mount scripts?
Click to expand...
Click to collapse
There is the option "Delete mount scripts" in the Apps2SD app. Check their FAQ page for any questions, it's pretty helpful.
Hello! I was having just the exact same problem with my T580.
I just loged in to say how I fixed it:
Open SuperSU app -> Settings.
Check "Enable su during boot"
Uncheck "Mount namespace separation".
After a reboot, Link2SD detected the 2nd partition!
EDIT: Now I fin another issue. If I try to link Obb, it says my device is using "sdcardfs". It offers to install fuse insted to fix it, but after rebooting I still getting the same message.
What could I do?
otamaglimmer said:
Hello! I was having just the exact same problem with my T580.
I just loged in to say how I fixed it:
Open SuperSU app -> Settings.
Check "Enable su during boot"
Uncheck "Mount namespace separation".
After a reboot, Link2SD detected the 2nd partition!
EDIT: Now I fin another issue. If I try to link Obb, it says my device is using "sdcardfs". It offers to install fuse insted to fix it, but after rebooting I still getting the same message.
What could I do?
Click to expand...
Click to collapse
Seems Link2SD does not like Marshmallow so I switched to Apps2SD (which also suggests what you did). It would not create the partition itself but took windows EXT4 and after a bunch of config, worked. The issue I now have is that Samsung still thinks the card is corrupt (which it isnt); any EXT partition and it says that. So on any reboot it greets me with a system notification of a corrupt card (which I want to get rid of but so far can't)..
I did try adoptable using a scripts from this site (didn't work) and the Apps2SD option. Seem to work on device but windows only saw the device memory so would not copy anything when it reported full.
took another kick at the cat today; installed Apps2SD, created mount scripts, but now, for reasons unknown, it no longer reports the SD as corrupt on boot (although it does say that partition is corrupt from the storage setting menu. Weird. No idea why it is no longer doing this. I will say the reinstall was funny. I had to delete and recreate the mount scripts several times (all said it worked) to actually get apps to move without disappearing. perhpas I ended up with a different mount script method in all the trying

Categories

Resources