[Q] After upgrading to CM10 "emmc" changed to "extSdCard" and related problems
Hi,
I've recently updated my GNote (GT-7000) from CM9 to CM10, and looks like with CM10 the external sd card previously mouted as "emmc" has become "extSdCard".
Since then some of the apps (such as Apollo) have trouble seeing media files, others can't see the sd card at all, and when connecting to the desktop the drive which normally shows the content of the external sd card, only shows a couple of folders of it rather than the whole content as it used to do before (when using CM9 and previous roms I had).
Looked around for possible causes, but didn't find much. Someone mentioned that rommanager might have placed ".nomedia" files on the root of the internal or external sd card causing the problem, but that's not my case. Tried also doing a full wipe and reinstall of CM10, no joy.
Any idea?
Thanks!
- Adriano
That's the standard mount points for cm10 there are apps that will remount the sd and external sd in mnt as on stock roms. I had a quick look but couldn't find them, but I'm sure someone else will be able to find them.
Sent from my GT-N7000 using xda premium
clean install without restoring data of apps
Sent from my GT-N7000 using Tapatalk 2
Thank you for the suggestions -- I tried a clean install as well, but even the builtin apps (Apollo) still had troubles accessing the external sd card (not seeing any of the mp3s I had there). I have now resolved for restoring a CM9 backup I took before upgrading to 10... and everything is working as it used to.
Not sure why I ran into these issues which no one else seems having encountered so far.
- Adriano
I have the same problem except that the files on my internal sd card are not read by apollo player And the gallery. Is there any workaround. The problem started as soon as I upgraded from cm9 to cm10
Sent from my GT-N7000 using xda app-developers app
adri72 said:
Hi,
I've recently updated my GNote (GT-7000) from CM9 to CM10, and looks like with CM10 the external sd card previously mouted as "emmc" has become "extSdCard".
Since then some of the apps (such as Apollo) have trouble seeing media files, others can't see the sd card at all, and when connecting to the desktop the drive which normally shows the content of the external sd card, only shows a couple of folders of it rather than the whole content as it used to do before (when using CM9 and previous roms I had).
Looked around for possible causes, but didn't find much. Someone mentioned that rommanager might have placed ".nomedia" files on the root of the internal or external sd card causing the problem, but that's not my case. Tried also doing a full wipe and reinstall of CM10, no joy.
Any idea?
Thanks!
- Adriano
Click to expand...
Click to collapse
Download ICS SD Binder. Check all 3 options and reboot. The path should be mnt/extSdCard (i think default is odb or so, make sure you change it) . It worked for me and so I'm trying to answer everyone with this problem. Give me feedback soon. And thanks button if I heped.
Quarmzz said:
Download ICS SD Binder. Check all 3 options and reboot. The path should be mnt/extSdCard (i think default is odb or so, make sure you change it) . It worked for me and so I'm trying to answer everyone with this problem. Give me feedback soon. And thanks button if I heped.
Click to expand...
Click to collapse
It didn't -- I don't need to have /emmc bound to /sdcard/external_sd as it was in GB. With CM9 everything for me works just fine with /emmc.
I tried the latest CM10 nightly, and using ICS SD Binder didn't change things. In the latest CM10 now there is also another mountpoint, called /storage/ and underneath sdcard0 and sdcard1 pointing to the internal and external storages respectively. In addition to /sdcard/ and extSDCard. Every few builds there seem to be some new change related to the storage's mount point. Going to wait another while before doing other attempts.
- Adriano
Any update on this question?
seems these are the new mount points even on the New JB roms from samsung
Somehow in some late November nightly, after flashing it, the files on my Internal SD were detected properly and it has all been working properly since. touchwood!
Related
Hi Guys, just flashed my O2X with CM7 and it worked fine but for some reason its not detecting the internal storage. What happened is that I followed the instructions, saved the zip on my external sd card and then flashed it. Did I do something wrong?
Heyy could you say what CM7 version you are using? Plus it sounds like you did everything fine.
Sent from my Optimus 2X using XDA App
Try to reflash it ....
Sent from my GT-I9000 using xda premium
mags014 said:
Hi Guys, just flashed my O2X with CM7 and it worked fine but for some reason its not detecting the internal storage. What happened is that I followed the instructions, saved the zip on my external sd card and then flashed it. Did I do something wrong?
Click to expand...
Click to collapse
Nope, you did it right.
Sounds like you haven't used CM7 before, it's easy to think the internal SD is gone, but it isn't. CM7 by default mounts the external SD-card as /sdcard, where your internal card used to be mounted.
The internal card is at /mnt/emmc.
There is an option in the settings somewhere where you can switch them around (don't have CM7 installed at the moment, but just search in the CM7 Nightlies thread and you'll find lots of info about it.)
TrymHansen said:
Nope, you did it right.
Sounds like you haven't used CM7 before, it's easy to think the internal SD is gone, but it isn't. CM7 by default mounts the external SD-card as /sdcard, where your internal card used to be mounted.
The internal card is at /mnt/emmc.
There is an option in the settings somewhere where you can switch them around (don't have CM7 installed at the moment, but just search in the CM7 Nightlies thread and you'll find lots of info about it.)
Click to expand...
Click to collapse
I think you are wrong, i am on CM7.1 and by default my internal sd card was in mnt/sdcard and external is mnt/emmc. Now I use FadeFX 1.6 update, which changes this to internal sdcard - mnt/sdcard and external sdcard to mnt/sdcardexternal_sd as it is on samsung ROMs..... (for this you need to check this feature in settings you mentioned) ....
goranbm said:
I think you are wrong, i am on CM7.1 and by default my internal sd card was in mnt/sdcard and external is mnt/emmc. Now I use FadeFX 1.6 update, which changes this to internal sdcard - mnt/sdcard and external sdcard to mnt/sdcardexternal_sd as it is on samsung ROMs..... (for this you need to check this feature in settings you mentioned) ....
Click to expand...
Click to collapse
Ok, they may have switched the defaults around since the last time I tried it. Doesn't take away from the main point of the post though. Mount points are different in CM7 from what people are used to, and confusing if you don't know about it.
But only external sd is different... internal it is the same, isn't it ???
goranbm said:
But only external sd is different... internal it is the same, isn't it ???
Click to expand...
Click to collapse
No, I was right. (Just installed the latest nightly)
External card mounted as /mnt/sdcard, also reachable from a symbolic link /sdcard.
Internal card mounted as /mnt/emmc.
default install.
Because This feature was introduced from nightly #148 or something .... And he installed CM7.1 wich is nightly #144 I am on this too, so I know how it was after installation.
goranbm said:
Because This feature was introduced from nightly #148 or something .... And he installed CM7.1 wich is nightly #144 I am on this too, so I know how it was after installation.
Click to expand...
Click to collapse
Nonsense. It's been like that since nightly #1. There were however KANGs floating around which switched mountpoints, you may have used one of those.
Thanks for the info guys...yes this is my first custom ROM and my first CM so sorry for being noob LOL
For some reason its now working. What I did was rebooted my phone, removed the external SD, and it somehow assigned sdcard for internal storage. Rebooted the phone and put back the external SD, and its now emmc...weird but it works now. I just have to move my apps all over the place
TrymHansen said:
Nonsense. It's been like that since nightly #1. There were however KANGs floating around which switched mountpoints, you may have used one of those.
Click to expand...
Click to collapse
No i was on stock... I was reading nightly thread.... This is the way that I understand :
Before nightly #149 thing was fine, but after this nightly users must check option "use internal storage" and then everything works fine...
If i got it wrong, i apologize.
goranbm said:
No i was on stock... I was reading nightly thread.... This is the way that I understand :
Before nightly #149 thing was fine, but after this nightly users must check option "use internal storage" and then everything works fine...
If i got it wrong, i apologize.
Click to expand...
Click to collapse
You're in the wrong forum, aren't you? That's why everything's confused, you're talking about CM7 on the Galaxy? This is the Optimus 2X forum.
Ohhhh my god .... can't believe how stupid this is.... I apologize for this. I am o cell phone, and did't see this.... so embaresed
Sent from my GT-I9000 using xda premium
Hi
Some time ago I tried JB Paranoid Android and my internal and external storage worked fine but switched back to ICS roms because of the problems JB roms had.
Now I guess they are more stable and wanted to try again so I installed Utacka's P.A. and I couldn't mount the internal storage. Some apps like camera said I had to insert an sd card. My sd card is mounted as my internal storage and the internal storage isn't anywhere.
I thought it was a problem with the rom so I went back to rocket miui and everything was fine.
Now I saw the cookies and cream Rom and wanted to try it but I'm having the same problem.
I searched in this forum for similar posts and tried ICS SD Binder and it doesn't work (or maybe I'm doing something wrong) and Remount Sd without luck.
According to Solid Explorer, my "Internal" sd's path is /mnt/extSdCard ("Internal" because in fact it's my external sd card) and I also have a /mnt/sdcard folder which says it's empty.
I would really apriciate any help and I'm sorry for my bad english and possible spelling mistakes.
Thanks
perri.etb said:
Hi
Some time ago I tried JB Paranoid Android and my internal and external storage worked fine but switched back to ICS roms because of the problems JB roms had.
Now I guess they are more stable and wanted to try again so I installed Utacka's P.A. and I couldn't mount the internal storage. Some apps like camera said I had to insert an sd card. My sd card is mounted as my internal storage and the internal storage isn't anywhere.
I thought it was a problem with the rom so I went back to rocket miui and everything was fine.
Now I saw the cookies and cream Rom and wanted to try it but I'm having the same problem.
I searched in this forum for similar posts and tried ICS SD Binder and it doesn't work (or maybe I'm doing something wrong) and Remount Sd without luck.
According to Solid Explorer, my "Internal" sd's path is /mnt/extSdCard ("Internal" because in fact it's my external sd card) and I also have a /mnt/sdcard folder which says it's empty.
I would really apriciate any help and I'm sorry for my bad english and possible spelling mistakes.
Thanks
Click to expand...
Click to collapse
I had a similar problem, I used ICS SD Binder, checked all 3 options and rebooted. It worked for me. Did you check all 3 options?
Quarmzz said:
I had a similar problem, I used ICS SD Binder, checked all 3 options and rebooted. It worked for me. Did you check all 3 options?
Click to expand...
Click to collapse
Yes, I did. Every time I reboot ICS Binder force closes so I guess it isn't really doing anything.
Do you remember which original mount point you chose?
perri.etb said:
Yes, I did. Every time I reboot ICS Binder force closes so I guess it isn't really doing anything.
Do you remember which original mount point you chose?
Click to expand...
Click to collapse
It force closes for me too. Though quite annoying, it still works. I chose the something that looked like mnt/ExtSdCard (maybe I didnt spell it correctly but it is the closest to that spelling.) I think the original was odb... Try and lets see if it works...
Quarmzz said:
It force closes for me too. Though quite annoying, it still works. I chose the something that looked like mnt/ExtSdCard (maybe I didnt spell it correctly but it is the closest to that spelling.) I think the original was odb... Try and lets see if it works...
Click to expand...
Click to collapse
It's not working for me. When the phone reboots, at the beginning appears a message saying it's checking for errors on the sd card and if I enter to settings/storage it looks like if it is mounting correctly because it says internal storage 11 gb and it looks like if it is scanning it and external storage 29 gb. Then ICS Binder force closes and the external storage desapears and the internal stoage is 29 gb.
Hello,
I've been patiently following this thread http://forum.xda-developers.com/showthread.php?t=1804665 for the past several months. Thanks to the selfless, hard work of Hashcode, dhacker, and also sylentprofet and jarveson (and apologies to anyone I haven't credited), the recent builds seem to have arrived at a level of functionality and stability that I'm thinking of trying to install my first custom ROM (I've already had SafeStrap 3.0.x installed for months).
My question is the following: I understand from the above thread and from Hashcode's blog that now the external SD card will be used as the default storage location. I was wondering what happens when an app is "installed to SD". From my previous experience on an original Motorola Droid, I know that "installing to SD" would move some files to a special directory on the SD card. I was wondering if this would cause collisions if the same app was installed under multiple ROM slots using SafeStrap.
Thank you for entertaining this newbie's question.
Actually the way I understand it is there is still the internal storage and external SD which are the same, but the internal storage gets partitioned separate from the rest of the storage so if you install an app to the SD card, I think it just goes in a regular folder. The system thinks the /system partition is in the regular storage for it but it actually is tricked to the internal storage.
I hope that makes sense.
MrObvious said:
... so if you install an app to the SD card, I think it just goes in a regular folder ...
Click to expand...
Click to collapse
Thank you very much for your response.
Is this regular folder on the external SD card? If so, does it mean that this regular folder will be shared by the ROMs in multiple slots if I have the same app installed under the ROM in multiple slots?
Thank you again.
alvin_a_garcia said:
Thank you very much for your response.
Is this regular folder on the external SD card? If so, does it mean that this regular folder will be shared by the ROMs in multiple slots if I have the same app installed under the ROM in multiple slots?
Thank you again.
Click to expand...
Click to collapse
If it's on the external SD then yes it is.
I had the same doubt when I recently started using ROMs on my Droid3. This thread helped me a lot.
I have lots of apps in my stock ROM that I've installed before rooting it. Do I have to install it all again on external SD? If yes, do I have to use a new flashed ROM or the stock ROM?
Thiago AmP said:
I had the same doubt when I recently started using ROMs on my Droid3. This thread helped me a lot.
I have lots of apps in my stock ROM that I've installed before rooting it. Do I have to install it all again on external SD? If yes, do I have to use a new flashed ROM or the stock ROM?
Click to expand...
Click to collapse
On minimoto I noticed it was using the exact same sd configuration as stock, perhaps because its stock based. On CM10 the external SD card is the default /sd card but you can still access the internal sd.
Regardless of how the sd card is configured you'd still have to reinstall apps when going to another ROM. I recommend using Titanium Backup then its quite simple to restore apps on another ROM. For SD data you could just manually copy and paste the folders from the internal to external SD.
spunker88 said:
On minimoto I noticed it was using the exact same sd configuration as stock, perhaps because its stock based. On CM10 the external SD card is the default /sd card but you can still access the internal sd.
Regardless of how the sd card is configured you'd still have to reinstall apps when going to another ROM. I recommend using Titanium Backup then its quite simple to restore apps on another ROM. For SD data you could just manually copy and paste the folders from the internal to external SD.
Click to expand...
Click to collapse
Thanks! So, a separate partition on SD Card would be a waste of "space", since the ROM's doesn't share acess to this partition. I've only tried with CM10, I'm going to try with MavROM and Minimoto, but i'm almost sure that I'll end backing all up with Titanium.
Thiago AmP said:
Thanks! So, a separate partition on SD Card would be a waste of "space", since the ROM's doesn't share acess to this partition. I've only tried with CM10, I'm going to try with MavROM and Minimoto, but i'm almost sure that I'll end backing all up with Titanium.
Click to expand...
Click to collapse
Sort of kind of. Basically this would be useful if you want to share apps and their settings between the custom and Stock ROMs installed on your phone [may be odd on an app by app basis depending on a few things but a good number *should* work [I dont use external SD as it eats the battery and is MUCH slower than using the /data partition so haven't tested this], so following should be close if not 100% correct
You would in stock ROM set your apps2SD app up [I DO NOT advise you to use the sdcard function found in manage apps>app area instead you should be using an app like Link2SD that actually creates a partition on your external SD and formats it to EXT3 or EXT4 [suggest using EXT4]. This way things like widgets still work whereas they don't when using the built-in android function [this happens as android uses a folder on the SDCard [which is FAT32 by default] and file permissions needed to run Widgets and some code can't be copied as needed on to a FAT32 partition so by using an app that partitions [or the recovery can do this but you would still need an app to manage which apps are in this partion] the SDCard app instead actually formats part of the card to the EXT 3 or 4 File system so it is the same as the /data partion so Android can copy EVERYTHING and nothing is affected and broken.
So you open your SDCard app manager in Stock ROM and format the External SD [THIS WILL ERASE EVERYTHING RUN APPROPRIATE BACKUPS BEFORE PARTIONING [move them to a computer and back if you dont have enough internal storage to absorb your data]]
When that completes open the app again [usually needs a restart first to mount the new partition before continuing].
Once you get that done open the Manager app and select the apps to move to this new partition.
CUSTOM ROM: Now once that is done boot in to safestrap and either setup a Custom ROM or change to it's boot slot. Next boot in to Custom ROM and install the same SD Card App Manager you used in Stock.
Next, once you open it it should say it found a partition and ask if you want to use it if it doesn't and just lists the app view the settings in the Manager app and HAVE IT SETUP AN EXISTING PARTITION. DONT PARTITION YOUR SDCard AGAIN [or all your newly moved data will bite it].
Now restart and allow it to boot back in to the Custom ROM again. Once this happens all the apps you moved to the SDCard partition should magically appear and be usable.
SO LONG AS YOUR STOCK AND CUSTOM ROMs ARE THE SAME VERSIONS DONT DO THIS IF YOU HAVE ICS ON THE SAFE SIDE AND JELLYBEAN AS A CUSTOM ROM IT WILL MOST LIKELY CAUSE ALL KINDS OF PROBLEMS
Hi, I'm new to the SGS after having used a ZTE Blade for a couple of years.
I've got this thing pretty much setup how I want. Running a stripped down CM10.1 nightly with hugemem enabled using the semaphore kernel.
I've swapped the internal and external SD cards by modifying vold.fstab. I needed to do this because I have games that download huge amounts of data to the sd card.
I also have more game apk's than can fit in the phones internal data so some of them are moved to the SD card. Here's where the problem lies.
Clockworkmod doesn't know that the internal and external SD cards are swapped. It has the internal and external labels the wrong way around on its backup and restore routines. Hardly a major problem, but what is a problem is that it's backing up an empty .android_secure folder from the internal SD card.
Is there anything I can do about? Some setting to swap internal and external cards in CWM? Or alternatively get the rom to use the internal sd card for .android_secure despite the sd cards being swapped?
It's not the end of the world because after restoring a rom I can just restore outdated and missing apps using Titanium. I'd just like my backup to be complete if it's possible to do!
Thanks.
Nice question mate, I haven't seen someone with that issue before, may be just because they are happy enough with their swapped memories and don't think about backups. I think that for now you have to use TB to backup your apps correctly and hopefully cwm team will fix that. Have you tried to reinstall recovery?
I only actually noticed it because after switching form the Blade (an ARMv6 phone) to the SGS (ARMv7) I gradually added a load of games to my phone that were now compatible and yet my backups were getting smaller! I noticed the android_secure backup file was 0 bytes and that's when I worked out what was happening - I was moving the bigger stuff to SD and it wasn't getting backed up.
As for re-installing recovery, I switched to the Semaphore kernel and it replaced the recovery with a different one which has the same problem as the CM10.1 version.
Ok, so that's not a solution. The worst part of the story is that folder .android_secure is harder accessible even than any system files and paths. If you find a way to open it you may copy all the apk.s to some safe directory and this way you have at least the installation data of your apps and you have just to reinstall them ( I realize it's not such an easy if they are >100). Better than search the net again or copy from pc. How much easier it would be if we just have to copy apk file of the app to/data/data or .android_secure instead of installing it to get it in your app drawer. XD
A google search found this: http://forum.xda-developers.com/showpost.php?p=31148760&postcount=369
So they've at least thought about this scenario on the SGS2! I wonder if any of the SGS1 devs around here here have fixed this in their recovery without us knowing?
Cool dude, nice find. I think you loose nothing if you try that.
I'm not sure flashing recovery for another model is a good idea? On my last phone you couldn't even use recovery from a different software revision of the same phone hardware!
In any case, isn't recovery part of the kernel on the SGS? Flashing a kernel always seems to change it anyway. Which again, differs from what I'm used to.
I was more hoping this would prompt one of the devs to fix it or point me to one they'd already fixed in the past that I'm unaware of.
Hi.
I'm using Asylum Omni 4.4.3. Yesterday I tried to copu a big file (1,2 Gb) from external SD card (sdcard1) to internal SD card (sdcard0) but at 800Mb the copy stopped. I restarted the phone and tryied with small data and found that, if the data is more than 100Mb, it's easy that the copy stops and the phone have to be reboooted because it remains stuck.
If I try to use the internal SD for backup using TWRP, I'm able to save 1,5Gb of data without problems.
Instead the copy from sdcard0 to sdcard1 is working flawlessly.
I know that in KitKat there were many SD card issues.
But is it possible that 2 different sdcard on the same device have different behaviour ?
Zzgfont said:
Hi.
I'm using Asylum Omni 4.4.3. Yesterday I tried to copu a big file (1,2 Gb) from external SD card (sdcard1) to internal SD card (sdcard0) but at 800Mb the copy stopped. I restarted the phone and tryied with small data and found that, if the data is more than 100Mb, it's easy that the copy stops and the phone have to be reboooted because it remains stuck.
If I try to use the internal SD for backup using TWRP, I'm able to save 1,5Gb of data without problems.
Instead the copy from sdcard0 to sdcard1 is working flawlessly.
I know that in KitKat there were many SD card issues.
But is it possible that 2 different sdcard on the same device have different behaviour ?
Click to expand...
Click to collapse
This does not suprise me. Blame this bug.
Azeazezar said:
This does not suprise me. Blame this bug.
Click to expand...
Click to collapse
Thanks a lot for the hint.
I read the thread.
The weird thing is that I hadn't the problem with SlimBean 4.4.
Then I started to use SlimSaber, and release after release the device had some weird lock, that disappeard using an 4.4 kernel from Chasmodo.
So I tried Asylum Omni.
The external card seems ok even is VFAT and full of music. I listen music everyday with N7Player without issue.
The problem is during writing the internal sdcard, that is an ext4. And happens only with file bigger. Reading is not a problem too, as I simetimes watch films that are in the internal sd card without problems.
Today I tried to move a 2 Gb file with "adb shell" while in recovery and it worked. Slowly, but worked.
I have to try some old release of SlimBean to verify if the problem disappear. I got all my old nandroid somewhere in my notebook.
Zzgfont said:
Thanks a lot for the hint.
I read the thread.
The weird thing is that I hadn't the problem with SlimBean 4.4.
Then I started to use SlimSaber, and release after release the device had some weird lock, that disappeard using an 4.4 kernel from Chasmodo.
So I tried Asylum Omni.
The external card seems ok even is VFAT and full of music. I listen music everyday with N7Player without issue.
The problem is during writing the internal sdcard, that is an ext4. And happens only with file bigger. Reading is not a problem too, as I simetimes watch films that are in the internal sd card without problems.
Today I tried to move a 2 Gb file with "adb shell" while in recovery and it worked. Slowly, but worked.
I have to try some old release of SlimBean to verify if the problem disappear. I got all my old nandroid somewhere in my notebook.
Click to expand...
Click to collapse
After switching to exfat for both internal and external(Or sometimes ext4, if i swap out). I never had a problem, and good speeds. That is my recommendation.
I would not spent to much time looking for another way to make it work, because what seems to work for some does not work for others. But exfat seems to fix it for everyone.
Azeazezar said:
After switching to exfat for both internal and external(Or sometimes ext4, if i swap out). I never had a problem, and good speeds. That is my recommendation.
I would not spent to much time looking for another way to make it work, because what seems to work for some does not work for others. But exfat seems to fix it for everyone.
Click to expand...
Click to collapse
Just to notify that SlimKat 4.4 seems not to have such problem. I'ts not fast as SlimSaber or Asylum Omni, but file transfert seems ok.