Can some one please tell me why when you buy a memory card you never get the amount of memory specified available to you. For example I have a 32MB card but the XDA only shows this as 30.9, a bit of a bummer as I originally bought the card for Rom upgrades but had to use a 64MB instead. Does anyone know why this is the case.
PS I am surprised that there is not a declaimer when buying these. Something like “Though this card is 32MB in size there is no guarantee that the full 32MB will be available to you”
Thanks John.
For each storage media, there is a part taken to keep track of the place and attributes of each stored file. This can range from 1% for simple media like SD and MMC to around 15% for highly protected media like RAID5 storage disks.
As a practic, always subtract 1% of the capacity or you can take the job of keeping this FAT area in your diary :lol:
sd stand for secure digital which mean that each byte have encryption possiblities this also takes up room
with harddisks it's often because they state the size in bytes and not GB or MB or what ever and to get a KB you need 1024 bytes
but i do believe that flashcards do it the more real way by stating the size in MB and GB and such
Yes, 500 megabytes is often not 500x1024 but 500x1000 which also accounts for the disparity.
Related
Hi
I bought a 128mb Secure Digital Card from Expansys but when I put it
into my device the Memory on Storage Card says 118.75mb so
where's 9.25mb gone!!!!!
TIA
Charles
The file allocation table (FAT) eats up the rest.
John
And something about..
Secure Digital - This requires space for the "secureness"
So a Multimedia Card may have given you a few megs back..
Its the old saying.
You just don't get what you pay for anymore!
MmF
Missing 10mb
Thanks for the responses.
9.25mb for the FAT, Jeeeez!
Why don't they build them 138mb, and give me what I've paid for!
Rgds
Charles
Actually the FAT does not eat up that much space, not even close. Here's the other part of the reason: A megabyte and a million bytes are NOT equal!
A kilobyte is 1024 bytes. A megabyte is 1000 of those.
The card and hard drive makers say that THEY measure a megabyte as being 1 million characters even. So your 256MB card can hold 256 million characters or bytes.
The computer and PPC however, measures in real megabytes and take that number, dividing it by 1024, to come up with its reported size. Therefore, your card has 256 million bytes, but not 256 megabytes.
They've redefined the word.
Ahh I see now. Thanks Carlos
Rgds
Charles
Wallaby has a 32 mb built in memory. How can this be increased. If so How MUCH & How?
Note i have installed a 128 mb SD card and have installed most of the softwares on it but my system shows low memory while the SD card is nearly 50% empty.
I have tried to use the slider in the settings to increase the momory but it slides back and is not releasing more memory for the system.
kindly advise how to increase the momory
regards
aamer sheikh
There is a company that adds physical ram to the phone but now that prices for the xda 1 are so low I would not consider that as a realistic option. You could maybe buy an xda 1 with 64 megs of memory and a broken screen and transplant the mother board to your phone.
I think he might not know that he might free up some memmory on his devices rom. If I were you sir, I would sync my data (not backup), hard reset, reinstall everything into where I wanted it, and resync. If you have experience with hot air rework, or have a friend, you might aquire the chips and do it yourseld. THen again, if you didn't know you could add memmory to a wallaby, then you probably shouldn't do that. Be careful and good luck!
PS I'm not responsable if you junk your device, I am only giving suggestions of what could be done, not telling you it should be done!
Even by physically adding the memory chips you can get only 64meg, anything above that has to be software driven paged memory I think, bit like using a fast sd card.
I know that 128+ mb requires a driver.... I wonder if you could get in 96 somehow???? anyone done that?
I think the hardware limits direct memory access above 64.
can the chips be stacked? I thought I had read that somewhere; cut a certain pin(s) and solder/joint a second chip ontop of the origionals?????
are the user accessable ram and rom on the same chip or are they seperate chips?
could the rom size be increased? (never looked into it)
Where would one acquire the chips?
Just got a TB yesterday and am perplexed on why there is only 29.71 gb of available on a 32 gb card? I guess a few GB...no big deal but the Internal space available is only 2.47 out of 8. What gives? I maybe have 120 phone numbers.
Thanks
http://blog.premiumusb.com/2010/11/usb-flash-drive-actual-storage-space-capacity/
around 29.7 or 29.8GB is right for your SD card. and the internal storage for apps and everything is 2.5GB, some more is used for the system and firmware. I'm not sure if people found out what takes up the rest of the space though.
A 32 GB flash card holds 32,000,000,000 bytes. Your phone is measuring gibibytes (GiB), but incorrectly labeling them as gigabytes (GB).
32 GB = 29.802322387695312 GiB. The difference between that and the available capacity shown is due to formatting overhead, and whatever's already stored on the card.
One gigabyte is 10^9 bytes (SI), whereas one gibibyte is 2^30 bytes (binary). And the ***** of it is that the larger the number of GB to GiB, the more you seem to be "missing."
Thats cool. Thx. Big learning curve coming from a WOS 6.5 to this android. but I will love it.
ddemara said:
Thats cool. Thx. Big learning curve coming from a WOS 6.5 to this android. but I will love it.
Click to expand...
Click to collapse
It's the same for everything. Unless you mean Android as a whole. Anyway, welcome to Android. You'll love it.
in win7 i can choose between 32k and the new 64k when formatting the card. which should I do which is best for the phone,or should I just format it in recovery?
dyetheskin said:
in win7 i can choose between 32k and the new 64k when formatting the card. which should I do which is best for the phone,or should I just format it in recovery?
Click to expand...
Click to collapse
What file format? FAT32?
Generally I just leave it at the stock settings, which I believe is 4K allocation unit size. Android runs off a ton of smaller files, I think the larger allocation unit sizing is just going to be inefficient on space. Since this is flash based storage there probably is going to be minimal or no performance differences, I would think.
**edit**
nevermind, I need to read things first. For the SDCARD, which is mostly general storage, small file sizes arent likely a reason to opt for 4k over 32k or 64k, but I still don't know if you'll get any performance gain. Honestly, try both and benchmark them. Let us know if one is for some reason significantly better than the others..
I just benchmarked 14 tests between both 32K and 64K allocation unit sizes and 7 different caches between 128 and 4096. The sweet spot for me was 64K when formatting the card and setting sd-booster to 4096. my card is a 32gb lexar sdhc class 10. I get roughly 9.1 for write and 22.6 for read.
What did you use to format? When I put my 64gb sdxc card I got a message saying the card is damaged would you like to format it and I said why yes, I would like to format it and it just did it without any options. All I know is that it formatted as FAT32. Can I check in the phone what allocation unit size it is at?
feralicious said:
What did you use to format? When I put my 64gb sdxc card I got a message saying the card is damaged would you like to format it and I said why yes, I would like to format it and it just did it without any options. All I know is that it formatted as FAT32. Can I check in the phone what allocation unit size it is at?
Click to expand...
Click to collapse
no you cant check on the device. the options are in windows7 in the format screen
sent from tapatalk on my rezound
dyetheskin said:
no you cant check on the device. the options are in windows7 in the format screen
sent from tapatalk on my rezound
Click to expand...
Click to collapse
Okay, thanks. I formatted in the phone since I figured it would format it properly. I saw that it was FAT32 when I was putting some music on it but never check anything further than that.
Antutu Benchmark results (my card is class 6):
Write - (5.0 MB/s) 50
Read - (5.7 MB/s) 57
Internal card results:
Write - (7.0 MB/s) 70
Read - (6.4 MB/s) 64
I have no idea if that's good or bad. My first smartphone so I've never had to pay that much attention to this stuff.
Were your speeds MB/s also? If so, maybe I'll try reformatting, although mine is class 6 so I don't know how much to allow for that.
I also saw something about Android OS supposedly not supporting more than 32gb but mine is 64gb. Would that be a factor?
Allocation size should be based on "average file size"
If apps, keep it smaller, or the normal 4k. Music/movies, you can up it a few notches.
Benchmarking this with benchmark programs are useless as they have preset small files they use to bench the speeds. Being flash memory, allocation size will also most likely put forth no noticeable speed difference on already speed limited SD cards. if seektime mattered, allocation would also. in our cases allocation only has the effect of potentially wasting space.
just use the smallest allocation size for the most use of the space on your card. you select higher allocation unit sizes, all the teeny files android and apps use will take up the amount of space equal to the allocation size, regardless of its true size (4k allocation means ALL files take a minimum of 4K, or in increments of 4K. therefore files <4k take 4k, 4+ to 8 take 8k, 8+ to 12 take 12k.)
Yes 64gb cards are usually fine on aneroid. What are keeping on there, pron???
Sent from my Kindle Fire using Tapatalk
nrfitchett4 said:
Yes 64gb cards are usually fine on aneroid. What are keeping on there, pron???
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
I never keep pron on my aneroid. I wouldn't know how to get it on/in (?) there!
lol mmm Pron
My question is about the user available internal storage. According ot GSMArena the device has 4GB of internal storage, but I see only 1.78GB available. Why is this so? I'm new to the whole smartphone/android thing and I don't know if the other ~2.2GB are some system reserve or something like that.
shhnedo said:
My question is about the user available internal storage. According ot GSMArena the device has 4GB of internal storage, but I see only 1.78GB available. Why is this so? I'm new to the whole smartphone/android thing and I don't know if the other ~2.2GB are some system reserve or something like that.
Click to expand...
Click to collapse
Most of the internal storage is occupied by the ROM itself and by the then by installed applications. Now LG, being a company that develops the stock ROMs for its devices on top of Android, sadly produces ROMs that are pretty bloated in terms of unnecessary services and applications, something that has a huge effect of on the consumed space of internal storage. If you buy your device from a cellular operator, you will often get some additional bloatware from your operator as well. Only solution is to use a custom ROM like CM 10.2, which consumes much less resources comparing to the stock one. However, as it's still Android, it will consume considerable internal storage space.
I think you didn't fully understand my question.
Internal 4 GB, 768 MB RAM
This is from gsmarena. Now, how exactly is it that we only have 1.7 GB of internal storage and 588MB of RAM available to us?
shhnedo said:
I think you didn't fully understand my question.
Internal 4 GB, 768 MB RAM
This is from gsmarena. Now, how exactly is it that we only have 1.7 GB of internal storage and 588MB of RAM available to us?
Click to expand...
Click to collapse
its what digdis said.2 of 4 gb are occupied by the system partition.and when every manufacturer says 4 gb,its never exactly 4gb.its about 3.6.just like the pc hard disk.if you have for example 320gb hard disk,the actual size is about 298gb.
the same for the ram.if you have a 2gb ram phone,it actually has about 1.7gb.
our phone with stock rom has 619 mb ram.cm 10.2 has 588.i dont know why exactly(neutrondev knows),but i think it has to do with allocation.
manosper said:
just like the pc hard disk.if you have for example 320gb hard disk,the actual size is about 298gb.
the same for the ram.if you have a 2gb ram phone,it actually has about 1.7gb.
Click to expand...
Click to collapse
I disagree on the hard disk statement. Hard disk driver are simply made with a rounded capacity. 320 gigabytes of hard disk space is 320 000 000 000 bytes, which is normally incorrect since 320 gigabytes = 343597383680 bytes.
343 597 383 680 bytes / 1024 = 335 544 320 kilobytes
335 544 320 kilobytes / 1024 = 327 680 megabytes
327 680 megabytes / 1024 = 320 gigabytes
Manufacturers make hard disks by the following formula:
320 000 000 000 bytes / 1024 = 312 500 000 kilobytes
312 500 000 kilobytes / 1024 = 305 175,78125 megabytes
305 175,78125 megabytes / 1024 = 298,0232238769531 gigabytes
There is no locked/hidden space on hard disks, because there's nothing to lock/hide(if you apply the actual correct calculations). The only exception to this are hidden partitions on the hard drive used for recovery, but people who actually understand computers never use hidden partitions on the hard drive for recovering data, but rather use software to make an image of the system and store it on external storage(external HDDs, flash drives, cloud, etc).
The case with P710(and a number of other devices), I think, is much different, since I don't actually see these "hidden" or "missing" ~2.2 GB anywhere(or if we apply the correct calculations - ~2GB).
RAM memory is always manufactured with the correct calculations. 512MB is real 512MB. 1GB is real 1024MB. With that said, out of 768MB of ram on our device we only see 588MB. So my questions are:
"Where are the other roughly 2GB of storage? Are they used for pure system purposes and are made unaccessable by manufacturers or Android developers?" and "Where are the other roughly 180MB of RAM? Are they also used for addressing hardware or system purposes and are made unaccessable by manufacturers or Android developers?"
[SOLVED]
I found the answers I was looking for. The "invisible" space from storage is taken up by the OS.
This can be locked.