Database Develop

Differences between booting from uSD and emmc?

Hey everyone,
I currently run CM7 off an SD but I was wondering if there are benefits to replacing the stock os on the emmc?
Are there any speed differences or technical pros to it?
Thanks for the input! This is a really fantastic forum!
sent from my nook color

joelszs said:
Hey everyone,
I currently run CM7 off an SD but I was wondering if there are benefits to replacing the stock os on the emmc?
Are there any speed differences or technical pros to it?
Thanks for the input! This is a really fantastic forum!
sent from my nook color
Click to expand...
Click to collapse
From my experience the booting time is almost half if using emmc version. (SD card version ran on a class 4 card). After booting the performance is almost same. You may get better boot time for sd card using a class 6 or class 10 card.

I dont have an answer for you as i picked mine up yesterday and decided to go the SD route at the start i am curious on this question myself.

JustusIV said:
I dont have an answer for you as i picked mine up yesterday and decided to go the SD route at the start i am curious on this question myself.
Click to expand...
Click to collapse
Well from my experience, running from the SD card is very smooth... so for ease of use i highly recommend it for a first go.
I have a follow up question- for some reason my macbook recognizes the second partition of my sd card but my pc desktop does not. I am referring to the partition generated for storage by the CM7 installation process that allows storage on the data card simultaneously.
Any ideas why this would be?
sent from my nook color

joelszs said:
Well from my experience, running from the SD card is very smooth... so for ease of use i highly recommend it for a first go.
I have a follow up question- for some reason my macbook recognizes the second partition of my sd card but my pc desktop does not. I am referring to the partition generated for storage by the CM7 installation process that allows storage on the data card simultaneously.
Any ideas why this would be?
sent from my nook color
Click to expand...
Click to collapse
I use Macs and Windows machines rarely (and I am guessing you run Windows on the desktop) but my guess is the ext4 partitioning that CM7 uses.
I seem to recall that working- at least somewhat- on Mac but not on Windows, but I am not positive.

i chose sd, because it's super easy to backup my sd card as an image by popping it into my laptop. I can then burn that image back to a sd card if i want to try a new android build without messing up my default android install. I can always boot into the original nook os if i want as it is unmodified.
i used a class 2 and it was pretty slow. moving up to a class 6 and 10 has really helped and i don't notice any slowness.
i have not run off internal memory though so i don't have a baseline to compare.

eMMC is faster than my class 2 uSD cards, and it's easier to swa stuff back and forth from a computer/phone/camera/whatever with a removable uSD.
Sent from my Froyo'd Epic using XDA App

Cool, I've been wondering about this myself and was about to make this same thread.
I was concerned because I get a ton of force closes running off the SD, and I wondered if that was a problem that would be solved by going to eemc. Or if somehow I've made a mistake setting up my card and that's the issue. I'm very knew to this whole scene, so I'm still a bit scared of rooting at the moment and would love to iron out the problems I'm having with the SD booting. Things run fast, and fairly smoothly but eventually something will force close, like Market, and then Google Frameworks and then pretty much everything will refuse to run after I tap their icon. Forcing me to restart. Also, some things, trying to download new skins for Beautiful Widgets is impossible. Only get force closes.
I can't figure out if it's anything in particular that causes it to spiral out of control. And what makes it more annoying is this is my girlfriend's new Nook, I'm trying to get it set up for her to work as smoothly as possible. If it was just mine, I wouldn't be as bothered by messing around and trying different configurations and whatnot. But I know she won't be as patient and tolerant of these issues and won't want to keep bugging me with every problem that pops up.
Would you say this is likely a localized problem on my end through some fault of my own? From this thread, it seems people are having pretty great experiences with the SD method. Which might be reassuring. I think I'll do a backup and start from scratch this evening.

@JRSly: What type of uSD card are you using. I was experiencing the same problems you had with booting, force close, refuse to run, thus a final restart. After swapping out four different types of uSD cards, SanDisk (class 2 and 4), A-DATA (class 6), Patriot (class10), I finally deteremined that the Nook is very picky about the type of card. All the cards work fine in my digital camera or PCs, but the A-DATA and Patriot are slow and often hang in the Nook. I am now using the three Sandisk cards with no problem. I recently updated to Nookie Froyo 6.8.5 and it runs great on the SanDisk cards. Just for the test if it will run faster on A-Data (class 6), wouldn't you know it starts to hang and FC just like before. I guess I'll use the A-Data card in my digicam. Try a Sandisk card and see what happens. I even try one of my old Sandisk 2GB card from my Blackberry which is unmarked but has a class 10 performance when measured.

I'm very new to this... and I keep seeing emmc.
What is this? Internal memory?

ax135 said:
@JRSly: What type of uSD card are you using. I was experiencing the same problems you had with booting, force close, refuse to run, thus a final restart. After swapping out four different types of uSD cards, SanDisk (class 2 and 4), A-DATA (class 6), Patriot (class10), I finally deteremined that the Nook is very picky about the type of card. All the cards work fine in my digital camera or PCs, but the A-DATA and Patriot are slow and often hang in the Nook. I am now using the three Sandisk cards with no problem. I recently updated to Nookie Froyo 6.8.5 and it runs great on the SanDisk cards. Just for the test if it will run faster on A-Data (class 6), wouldn't you know it starts to hang and FC just like before. I guess I'll use the A-Data card in my digicam. Try a Sandisk card and see what happens. I even try one of my old Sandisk 2GB card from my Blackberry which is unmarked but has a class 10 performance when measured.
Click to expand...
Click to collapse
I feared that this might be a possibility too. My first attempts were with a little 2Gb card I'd had lying around and it didn't work very well at all. I couldn't get past installing Gapps for all the force closes. The next day I went to Target to get a larger 8 Gb one so I could also play around with Honeycomb, it's a Class 6 Lexar card. I started over last night and tried a couple of attempts at wiping and burning the image and inevitably ran into the same problems. It looks like a crummy(at least in terms of what the Nook likes) card is a distinct possibility. I'll give Sandisk a shot.

BlizzofOZ said:
I'm very new to this... and I keep seeing emmc.
What is this? Internal memory?
Click to expand...
Click to collapse
Yup. (I didn't get it either.)
Since MMC is a sibling of SD cards, it's basically dedicated internal SD storage with a controller.
http://en.wikipedia.org/wiki/MultiMediaCard#eMMC

BlizzofOZ said:
I'm very new to this... and I keep seeing emmc.
What is this? Internal memory?
Click to expand...
Click to collapse
You got it in one.
sd card is self explanatory, of course, and emmc is the internal memory of the NC.
The only DISADVANTAGE to running on emmc is that you lose the stock B&N version of Android.
Other than that- it boots a bit faster, may run a bit faster and be less likely to have force closes and similar problems.

xdabr said:
Yup. (I didn't get it either.)
Since MMC is a sibling of SD cards, it's basically dedicated internal SD storage with a controller.
http://en.wikipedia.org/wiki/MultiMediaCard#eMMC
Click to expand...
Click to collapse
That's what I thought!
Thanks for the cofirmation

[Q] Differences between full root and SD root?

I have set up the CM7 on an SD boot and it works for the most part.
However it seems very unstable, about 3/10 uses it will crash apps. I really only have Aldiko and the Nook App on it and maybe Angry Birds and a Task Killer.
Aldiko and Nook etc will just go into an error loop saying the app stopped unexpectedly and then I have to hold the power button to shut it down.
My question is if this is typical of using the SD root method?
Then, if I do a full hardware root/ROM is it generally more stable in your experiences?
I suspect that part of my problems are the SD card itself, I had a 4GB Class 2 Sandisk card initially and it worked well but it was very very slow. So I got a Transcend brand 8GB Class 6 card which should work, it is a big name brand and all, and is much faster but CM7 seems very unstable. Is it all just the card?

Yes, your card is the culprit. So far from people reporting here you need a SanDisk Class 4 card. Its all about the 4k read/write speeds of the card you're using. You want a 1.0+ in CrystalDiskMark to get decent performace and get rid of the FC's. I am using the card I linked here and have not had any problems running apps or the Nook freezing.
- Aerlock

I had similar problems (sometimes intermittently) using an A-data card, I think it was 8GB class 6. I finally installed to emmc and have not had any problems since. The CM7 nightlies go to the point of being so good that I never needed to boot into stock anymore anyway.

So if I get it working on the SD, is it even worth doing the perm internal ROM mod?
Or is the SD MOD just as good/better?

MuGGzyx said:
So if I get it working on the SD, is it even worth doing the perm internal ROM mod?
Or is the SD MOD just as good/better?
Click to expand...
Click to collapse
Running off the SD is so good I haven't even felt like trying to put it on the internal memory. The only thing you lose by running it from the SD card is the ability to pop out the SD card whenever you want, though the only times I've popped out the SD card is to put the newest nightly on the boot partition. And thats just cause I've been too lazy to figure out the exact mount commands to mount it on the nook. If I want to get/put files off/on the SD card I just plug it into my computer.
- Aerlock

MuGGzyx said:
So if I get it working on the SD, is it even worth doing the perm internal ROM mod?
Or is the SD MOD just as good/better?
Click to expand...
Click to collapse
Internal is always more stable.
Sent from my LG Optimus V using Tapatalk

I didn't run any benchmarks when I had it on a SD card (16 GB SanDisk class 4) but it seemed about as good as it has been after switching to eMMC.

The CM7 SD card mounts internal memory on mmcblk0 and uses it... (I presume for caching, etc) Speed of the SD shouldn't cause crashes. Slowness yes, but crashes?

Re: SD vs. eMMC, an SD install can be just as fast and stable as eMMC, but SD installs also seem somewhat prone to suddenly and mysteriously losing that stability, developing FCs, WiFi issues, lag and even freezes/crashes. There are also more robust and straightforward tools for managing eMMC installs; both CWM and ROM Manager tend to have quirky interactions with SD installs, performing some operations on the SD partitions and others on the internal partitions. I would advise anyone who finds that their SD install has become their sole or primary OS to eventually move it to eMMC. Even if you're still using stock quite a bit, an eMMC dual boot (see my sig link) has advantages over running one system from SD--mainly, that the two OSes can both use the SD for storage.
gyrfalcon said:
The CM7 SD card mounts internal memory on mmcblk0 and uses it... (I presume for caching, etc) Speed of the SD shouldn't cause crashes. Slowness yes, but crashes?
Click to expand...
Click to collapse
See this thread: http://forum.xda-developers.com/showthread.php?p=12964262
There's no such thing as "Speed of the SD." There are several metrics, primarily large sequential vs. small random reads and writes. Card class (what most people assume equates to "speed") is based on the former, whereas performance as a boot drive correlates with the latter. A card optimized for large writes tends to suffer badly in small-block random r/w. There's no such thing, presently, as a card optimized for small-block r/w, but SanDisk class 2, 4, and unclassed cards tend to have very balanced benchmarks, with reasonable performance across all metrics. This places their small-block r/w speeds 10x and 100x ahead of a card optimized to meet class requirements.
I've also been hearing there's an issue with some cards reporting their reads and writes using an oddball protocol that's currently unsupported in the kernel.

[Q] Help with using microSD to run CM7

Okay...I've read through quite a few posts and forums here but I still need answers. I apologize if I repeat something that's been asked and answered somewhere else.
I have a Nook Color currently at stock 1.3. I rooted it back in February and was okay with that until I jumped back on the forums and read about CM7. So I installed CM7 to the Nook directly (not booting off an SD card.) When I realized that would not allow my kids to use their Nook books, I took it back to stock and found instructions on how to boot CM7 from an SD card. GREAT!!! However, I now cannot get the file to write to my card. I have a PNY and a Transcend each 4gb. My computer will recognize each card, but when I try to use WIN Disk 32 to write the file to the card it seem to work, but when I check the card, the computer says it needs to be formatted! I used the Transcend to write the files and put CM7 directly on the Nook before, so why won't things work now??? How can I fix it? The PNY is brand new, never been used. I'd go buy a SanDisk, but I'm afraid I'll just have the same issues. I have a SanDisk MoblieMate SD+ CardReader.
I really appreciate any help! I can follow instructions, but please don't talk about partitions, scoobie doobies, or use tech speak. I'm not an idiot, but I do not understand the computer/tech jargon. I'm impressed by those that do, however, so it's to all of you that I send out my question!
THANK YOU!!! In advance!

Some card readers that are "built in" to your computer, will have this error. The usual work around is to use a separate and external card reader.

First off, I have gone through 3 cards and am now sucking it up and buying the Sandisk card. Bottom line, the Sandisck 4/8GB Class 2 or Class 4 cards are simply the best to use for this.
I had the same issues you describe with my Transcend and another off brand.
Once you do the put the Image on the card, you have to pull it out and put it back in and it should show you a tiny "root" partition, this is what you copy the CM7 or whatever ROM into and then stick the card into the nook, the rest is pretty much automated until it is done.

[SOLVED] Opinions wanted: Rooted vs. CM, etc. EDITED: SD-install of CM.

I've been looking for a tablet for some time, and the $135 refurb deal from B&N was finally enough to push me over the edge to a NC. Nothing else really comes close at that price point.
The technical explanations and threads for rooting/flashing seem pretty straightforward. As I'm familiar with CM from my Droid Eris, I think I'll be ok here.
What I would like to know is:
What do I lose/gain by flashing CM (such as Kang) over rooted stock?
* Do I lose Youtube/Flash? (I did read that there are issues with HD video)
* Can I still buy or install apps from the Market?
* I have some Humble Bundle android games (world of goo, etc) - is stock or CM better for this?
* I currently have no B&N content. I understand I will not be able to use the stock app if I flash - does the alternative B&N app limit me in any other way?
* If I flash, is there any reason I should *not* install to internal flash (emmc, i think?) ?
Sorry if some of the questions seem obvious, I just want to look before I leap
Thanks in advance,
A Nook noob
*************************************************************
EDIT: A summary for first-pagers:
I installed to the sd card, using CM7 (Kang). No real problems so far. Everything just works. I do have trouble prying the dang thing out of my kids' hands.
For the technically-minded: I will note here that apps that can usually remount /system as read/write fail on my sd-only installs. I always have to go back in through the terminal app and do the following steps manually:
bash
mount -t yaffs2 -o rw,remount /dev/block/mtdblk3 /system
This does make changing screen dpi and other similar tasks a pain in the rear, but oh well.
I have not upgraded from the inital Kang release I started with - partly because I'm not sure how using recovery mode in the sd-installed version will work (I hate having to reinstall every app), and partly because everything just works so far.
I will also note that I had to set apps to automatically install to the sd card (this is off by default) because I very quickly ran out of space on the 1GB /emmc slice. Apps get installed here by default even on sd-only installs.
I strongly recommend the "Hacker Keyboard" available on the market (free). It's great when you have to use vi in the Terminal app .
I updated framework.jar to include an IMEI number for apps in the Market. I also edited build.prop for the same reasons.
I overclocked to 1200, and it's solid as a rock at those speeds.

bigrat said:
I've been looking for a tablet for some time, and the $135 refurb deal from B&N was finally enough to push me over the edge to a NC. Nothing else really comes close at that price point.
The technical explanations and threads for rooting/flashing seem pretty straightforward. As I'm familiar with CM from my Droid Eris, I think I'll be ok here.
What I would like to know is:
What do I lose/gain by flashing CM (such as Kang) over rooted stock?
* Do I lose Youtube/Flash? (I did read that there are issues with HD video)
* Can I still buy or install apps from the Market?
* I have some Humble Bundle android games (world of goo, etc) - is stock or CM better for this?
* I currently have no B&N content. I understand I will not be able to use the stock app if I flash - does the alternative B&N app limit me in any other way?
* If I flash, is there any reason I should *not* install to internal flash (emmc, i think?) ?
Sorry if some of the questions seem obvious, I just want to look before I leap
Thanks in advance,
A Nook noob
Click to expand...
Click to collapse
This is all assuming you use CM7, which is more mature than CM9.
1. You lose the stock Nook ereader software. it can read kids books and other things which the android app cannot.
2. apps from the market work great from cm7. Don't know about Humble Bundle.
3. you do not lose youtube. (you lose HD with the newest version of Youtube, but still works on old versions.) Flash, I really don't remember. I don't think so. (edit, just checked, yes flash)
4. The only reason not to put on emmc is B&N warranty. You lose it with CM on emmc. But if your broke nook still works you can put stock back on and warranty still good.
But CM on SD works as well as on emmc. And you have stock still available for the reader and warranty.

Thanks leapinlar!

CM will allow you to get even more applications from the market. Also, performance is far better, compared to the stock.

And you can try flashing CM7 to an SD card and try it out before you flash it to internal memory (if you have a sandisk SD card, other brands don't work as well).

As leapinlar listed item 1 above, addition to that is you would lose the ability subscribe free magazine directly on your NC, other than that, CM7 is miles ahead.

The question is really what you lose by moving away from stock. Rooting doesn't really give you any advantage if you are willing to mess with stock you might as well go CM7.
As mentioned you will lose the B&N reader which is built into the Nook and has unique functions. You can still keep nearly all of the functionality of the reader though by getting the B&N app from the market. You will also technically void your warranty (though you can always flash back to complete stock).
If losing the Nook reader's specific functions or the warranty are a concern then you have the option of running a bootable SD card which leaves the internals of the Nook totally stock. This also has its disadvantages though in that you loose the extra storage capacity of the on-board memory and you lose the ability to use multiple SD cards. The slot will be filled by the bootable one you are running on so you can't put others in and out.
Everything else is an advantage in favor of CM7 and are too numerous to list. Bottom line is unless you really like the OS B&N has provided including it's limitations, then there is no reason to stay running stock. Either use a bootable CM7 SD card or put CM7 on internal and don't look back.
JP

Thanks very much for the great answers! It seems I will go CM.

J515OP said:
TThis also has its disadvantages though in that you loose the extra storage capacity of the on-board memory and you lose the ability to use multiple SD cards. The slot will be filled by the bootable one you are running on so you can't put others in and out.
Click to expand...
Click to collapse
First bold, why do say losing on-board storage? It's always there for us to use, either 1G, 5G or custom set.
Second bold, we're strongly NOT suggesting people keep inserting and removing the external uSD. Minimize to the lowest possible.

votinh said:
First bold, why do say losing on-board storage? It's always there for us to use, either 1G, 5G or custom set.
Second bold, we're strongly NOT suggesting people keep inserting and removing the external uSD. Minimize to the lowest possible.
Click to expand...
Click to collapse
1. Because by breaching the SD card wall the user can potentially make changes to the stock B&N that will cause issues and possibly void their warranty. If the concern is to leave stock alone by using the SD card method then they probably will not want to do anything to potentially mess up emmc. This is a consideration for a user that only wants to run from SD card that they may be limited to the space seen on the SD by default by the ROM and not the extra internal space.
2. Not suggesting that a users should repeatedly insert and remove cards. However running from emmc you have internal storage plus up to 32GB of SD card space available and if necessary you can swap out the SD card. However, when running from the SD card you only have the portion of the SD card unused by the ROM. This portion is split between "internal" and "sd card". If you are using a 4GB bootable SD card you may find you have very little space for apps and media with no option of expanding that by adding an external SD card since you are already using that slot.
These are just considerations that people not familiar with bootable SD cards may want to know about.
JP

J515OP said:
1. Because by breaching the SD card wall the user can potentially make changes to the stock B&N that will cause issues and possibly void their warranty. If the concern is to leave stock alone by using the SD card method then they probably will not want to do anything to potentially mess up emmc. This is a consideration for a user that only wants to run from SD card that they may be limited to the space seen on the SD by default by the ROM and not the extra internal space.
Click to expand...
Click to collapse
You probably confuse the eMMC system partitions and the eMMC /media partition. The eMMC /media partition is for us to use, it won't hurt the "stock OS/kernel" at all.
These are just considerations that people not familiar with bootable SD cards may want to know about.
JP
Click to expand...
Click to collapse
Sure, agree, but you know, say that we have a 16GB uSD card, if utilize internal memory, we have a full 16GB (don't bother to convert) as personal storage, yes.
If running ROM from a 16GB uSD card, we still have roughly 13GB left for personal storage.

Yep, I agree. Over all a bootable uSD with CM7 is a great way to go. Taking it one step further, if you use a 32GB card you really have quite a bit of space even if you only use the space on the card. This is a solid option particularly if you don't want to mess with eMMC or just have something else on eMMC entirely.
Back to the original question I still say CM7 on eMMC or uSD card is the way to go unless you need the stock B&N functions or layout. In that case root would be better than straight stock.
2 cents
JP

Guys, I really appreciate all the suggestions. I ordered two 32GB Sandisk cards, I'll probably just boot from them until maybe the warranty period is up. 32GB is a lot of space...

I've been running on an SD card for a while now but I'm considering going dual boot on the eMCC. What are the pros/cons for doing that?

mario_de said:
I've been running on an SD card for a while now but I'm considering going dual boot on the eMCC. What are the pros/cons for doing that?
Click to expand...
Click to collapse
Voiding your warranty (if you still have one) and the need to be slightly proficient with recovery either from internal or on a bootable uSD card (in case something goes wrong and you need to reflash) are the only cons I can think of.
Pros are possibly smoother (depending on the performance of the uSD card you were using) access to a straight data uSD card through the slot since you won't have to take it up with a bootable card and the ability to keep your ROM and data/backups completely separate. The last one would be for example if your current bootable card became corrupted and non-readable you might not be able to boot it or recover any backups you had saved on it possibly leading to complete loss of the card and the need to start from scratch. This would be avoidable with a little precaution though. Still it's a pro that if you back up the eMMC to the SD card and eMMC crashes you can restore backups from the card.

So, just so that I'm clear here, I'll summarize (in case anyone else wants to know this):
If I wish to install CM, I need to create a bootable uSD card with the image I want. Once I've done this, I can boot directly from this image. If I choose to do this, I do not need to root or modify my NC. Should I wish to return to the original firmware because my NC dies or whatever, all I need to do is pull the uSD card out.
If I do this, I will have access to the remaining storage of the uSD card, and the /media slice on emmc.
The only media/B&N content that I will not have access to will be that content which requires the original NC reader. Pretty much everything else will be better - I can overclock the NC, have access to normal GApps, bluetooth access, Youtube, Flash, games, etc, everything that having CM gives you.
Using the uSD for booting means I will not be able to swap the card out while the NC is running, and is really the only thing I'm giving up here.
Please feel free to correct me where I'm wrong here, and thanks to everybody for the answers.

bigrat said:
...
If I do this, I will have access to the remaining storage of the uSD card, and the /media slice on emmc.
...
Click to expand...
Click to collapse
\>>> Forget the eMMC. The eMMC is not the memory you are looking for. <<</
To me, the whole purpose of booting to the uSD is to forget, leave pristine, ignore anything on internal memory. Get a 16G Sandisk and the eMMC shouoldn't be worth your time. Better yet, http://www.amazon.com/SanDisk-microSDHC-Flash-Memory-SDSDQM-032G-B35/dp/B004G60AD6?tag=dealswoot-20

If I wish to install CM ...
Click to expand...
Click to collapse
If I was you, I would say "If I wish to run CM from the external uSD card ...."

MISRy said:
\>>> Forget the eMMC. The eMMC is not the memory you are looking for. <<</
Click to expand...
Click to collapse
There is no reason you should not use your emmc media partition in addition to the balance of the SD card. It is there so you might as well use it (especially if you have the full 5GB version). You can never have enough storage space no matter how big your SD card. I have a 16GB card with CM9 on it and have it almost full and emmc media (5GB) almost full too.

leapinlar said:
There is no reason you should not use your emmc media partition in addition to the balance of the SD card. It is there so you might as well use it (especially if you have the full 5GB version). You can never have enough storage space no matter how big your SD card. I have a 16GB card with CM9 on it and have it almost full and emmc media (5GB) almost full too.
Click to expand...
Click to collapse
There definitely appears to be two schools of thought here. With cloud options these days on board storage is really becoming less of an issue (Dropbox, Skydrive, Box etc.).
It is nice to have an informed decision based on both options but at the end of the day it is a preference call.
JP

[Q] 64GB HD Card on Lollipop ROM - What format should I use?

I have been trying to find the best method for getting a 64gb SD card to work with my phone, and it has not been all that successful. I have formatted in NTFS, exFat and FAT32, all with varying degrees of success. Either copying files over leads to data corruption, or I cannot write from and to the SD card when it is being accessed by my device. Any help would be greatly appreciated.
I am currently running CMPrime ROM v1.1Beta with the included kernel. I have also tried using it with Unnamed Kernel.

I just received my Samsung 64gb EVO MicroSDXC UHS-I card this morning. I popped it into my phone and it asked me to format before I could use it. So I clicked yes and then after that it just worked.
I am not sure what would be different for a custom rom as IU use the offical Lollipop 5.0.2. It shouldn't be much different though.

FAT32 is your best bet. I have a 64GB Lexar card formatted in FAT32 working fine with Titan Prime.
It's possible that something is wrong with the card. Does the card work fine in other devices? What brand is it?
Could also be a hardware issue with your phone, have you tried other cards?

Use fat32 no other file system

thisisjason said:
FAT32 is your best bet. I have a 64GB Lexar card formatted in FAT32 working fine with Titan Prime.
It's possible that something is wrong with the card. Does the card work fine in other devices? What brand is it?
Could also be a hardware issue with your phone, have you tried other cards?
Click to expand...
Click to collapse
I bought a no-name SD card from a Chinese manufacturer, because I figured "why not." I know quality of SD cards vary across manufacturers, but since it's an established technology and relatively easy to make, I thought it'd be worth a chance. Some quick Google-Fu showed that it is not a completely isolated issue related to SD failure.
I have a 32gb card that I'm using without any issues. I'm asking specifically about 64gb, because 32gb seems to be the max size for external storage.
mauley said:
I just received my Samsung 64gb EVO MicroSDXC UHS-I card this morning. I popped it into my phone and it asked me to format before I could use it. So I clicked yes and then after that it just worked.
I am not sure what would be different for a custom rom as IU use the offical Lollipop 5.0.2. It shouldn't be much different though.
Click to expand...
Click to collapse
I usually give ROM info, because it is common courtesy for dev communities. I have read that formatting through the device only accomplishes a rather crude job, and that file structures can be unsound. I know FAT32 is the standard, but it is an old format that has size limitations.
vikasb32 said:
Use fat32 no other file system
Click to expand...
Click to collapse
But what about the limitations regarding max. file size and data transfer speeds?

I believe you should be able to use NTFS or exFAT with the kernal you're running, though I don't know if there might be any bugs or compatibility issues with some cards. If even FAT32 isn't working correctly, my suspicion if that you have a bad MicroSD card. As a rule of thumb I always buy brand name from reputable sources when it comes to microsd cards. I know those cheap ones look tempting, but the quality issues with them are legit, so it's a real crapshoot.
And yes, you'll run into the same old limitations with FAT32 in terms of file size, etc., but I use it anyway since it has the widest support across devices and I sometimes swap my cards.

thisisjason said:
I believe you should be able to use NTFS or exFAT with the kernal you're running, though I don't know if there might be any bugs or compatibility issues with some cards. If even FAT32 isn't working correctly, my suspicion if that you have a bad MicroSD card. As a rule of thumb I always buy brand name from reputable sources when it comes to microsd cards. I know those cheap ones look tempting, but the quality issues with them are legit, so it's a real crapshoot.
And yes, you'll run into the same old limitations with FAT32 in terms of file size, etc., but I use it anyway since it has the widest support across devices and I sometimes swap my cards.
Click to expand...
Click to collapse
I am inclined to call this a bad SD card, but I want to rule out all other possible reasons. Null Hypothesis and all that.
In terms of performance of FAT32, it is registered by the ROM, and it is visible in recovery. But my music files are not readable in Google Music or any other music app. I've tried moving them to /sdcard1/media/music and it is still balls. This kind of behavior leads me to think that it is an actual formatting issue.

mrbubs3 said:
I am inclined to call this a bad SD card, but I want to rule out all other possible reasons. Null Hypothesis and all that.
In terms of performance of FAT32, it is registered by the ROM, and it is visible in recovery. But my music files are not readable in Google Music or any other music app. I've tried moving them to /sdcard1/media/music and it is still balls. This kind of behavior leads me to think that it is an actual formatting issue.
Click to expand...
Click to collapse
Google Music would actually register and access the music files in NTFS.

mrbubs3 said:
But what about the limitations regarding max. file size and data transfer speeds?
Click to expand...
Click to collapse
Max file size for fat32 is 4GB-1byte. Should be not a problem unless you plan on putting e.g. large hd-movies on the card. Speed isn't affected by the partition type (actually it is, but it's negligible in this case). No-name sdcards are often manufactured with low quality check standards. They sell cards that would normaly get tossed into trash. I use a 64gb card with no problem whatsoever. On windows use http://www.easeus.com/partition-manager/ because windows will only allow up to 32gb. On linux use gparted.

doppelhelix said:
Max file size for fat32 is 4GB-1byte. Should be not a problem unless you plan on putting e.g. large hd-movies on the card. Speed isn't affected by the partition type (actually it is, but it's negligible in this case). No-name sdcards are often manufactured with low quality check standards. They sell cards that would normaly get tossed into trash. I use a 64gb card with no problem whatsoever. On windows use http://www.easeus.com/partition-manager/ because windows will only allow up to 32gb. On linux use gparted.
Click to expand...
Click to collapse
I occasionally save audio recording/mixing sessions as OMF files, which can end up being really large, particularly if I export at 64-bit sampling and 96khz frequency. So the 4gb limit can be a bit annoying to deal with, in that regard.
I wasn't aware about the cheaper SDcards potentially being of b or failed stock. I'll probably buy a new card under a trusted brand, and report back.

mrbubs3 said:
I occasionally save audio recording/mixing sessions as OMF files, which can end up being really large, particularly if I export at 64-bit sampling and 96khz frequency. So the 4gb limit can be a bit annoying to deal with, in that regard.
I wasn't aware about the cheaper SDcards potentially being of b or failed stock. I'll probably buy a new card under a trusted brand, and report back.
Click to expand...
Click to collapse
Acquired a Sandisk MicroSDXC Ultra UHS-1 64gb card. Tried using it in my android phone. I am able to load files onto the SD card as before, but I still experienced the same issues with Media Scanner failing to account for my music files on External SD. Worse yet, my Titanium Backup files became corrupted when trying to access them via the device. I did a Nandroid Backup and tried a clean install to rule out any potential conflicts with my ROM, only to find that the issues remained, and the Nandroid disappeared from the TWRP backup folder.
At this point, I'm starting to think that it's an issue with the phone itself. WHY CAN I NOT HAVE 64GB OF SPACE, MOTO G!!!?

I bought a sandisk 64gb card off amazon on black Friday, immediately put it in my phone and let the device format it.
Later, I put the SD card in my computer so I could create a 2nd partition for ext4 storage.
The phone had formatted the card Fat32...has been working just fine since then.

agentaaron said:
I bought a sandisk 64gb card off amazon on black Friday, immediately put it in my phone and let the device format it.
Later, I put the SD card in my computer so I could create a 2nd partition for ext4 storage.
The phone had formatted the card Fat32...has been working just fine since then.
Click to expand...
Click to collapse
When I try to mount the SD card in the phone, it does not register. It only works after I format to FAT32 using TWRP. So I will probably try that.
So 32gb in FAT32, then 32GB in Ext4, and leave back-ups/other files there?

64 card files wont all play
Hi I have a new moto g, I also put in a 64 sd card, while the music files seemed to play fine, video and other files the phone reads some of them not others, I put the same file internally and on the sd card and it reads the internal version of the file. I gather from this forum (though I may be wrong) I need format the sd card, I have no idea how to do that, any help would be appreciated.
mrbubs3 said:
When I try to mount the SD card in the phone, it does not register. It only works after I format to FAT32 using TWRP. So I will probably try that.
So 32gb in FAT32, then 32GB in Ext4, and leave back-ups/other files there?
Click to expand...
Click to collapse

My understanding is that, if you have a FAT32 SD Card, then larger files (4gb+) cannot be read. ExFAT and NFTS should solve this problem, but I am still dealing with issues of reliability with my card accessing my music files post-formatting.

Finally discovered the problem. I downloaded SD Insight from the Play Store, and I found that the SD cards I got off ebay were invalid (including the Sandisk SD Card). I picked up a PNY High Performance 64GB Micro Secure Digital Extended Capacity (microSDXC) Flash Media Card from a local computer store, and after formatting to FAT32, everything works.
Moral of the story: buy your **** from a store.

I'm currently using CM 14.1 20161225 with a 32 GB SD NTFS formatted and experiencing some weird problems with Camera/Gallery, Music, etc. when on the SD.
So before I go back to FAT32 on a 64 GB SD I now have I would like to ask if anyone can comfirm exFAT would be working fine on titan CM14.1 or LineageOS?

ChriMo said:
I'm currently using CM 14.1 20161225 with a 32 GB SD NTFS formatted and experiencing some weird problems with Camera/Gallery, Music, etc. when on the SD.
So before I go back to FAT32 on a 64 GB SD I now have I would like to ask if anyone can comfirm exFAT would be working fine on titan CM14.1 or LineageOS?
Click to expand...
Click to collapse
Format your card to EXT4, works fine with any rom and has no file size limitations.

..::X-FILES::.. said:
Format your card to EXT4, works fine with any rom and has no file size limitations.
Click to expand...
Click to collapse
Sorry no good option when pushing files over and back from Win10 so I would prefer to know exFAT experiences since Win10 should be working fine with it.

ChriMo said:
Sorry no good option when pushing files over and back from Win10 so I would prefer to know exFAT experiences since Win10 should be working fine with it.
Click to expand...
Click to collapse
That's strange, i have no problems with mtp in win7, looks like win10 doesn't worth updating. Btw, i tried exFAT before and it strangely limited file size to 4 GB like in FAT32.