How come iphone 6 128gb only has 114gb (capacity 114gb, available 110)installed but sells as 128gb?

Great job, thank you for your amazing help on these Apple Support Forums!

TheSnapDude wrote:

Great job, thank you for your amazing help on these Apple Support Forums!

That was so nice of you. Meg is a great help on these forums. Yes she is!

TheSnapDude wrote:

Great job, thank you for your amazing help on these Apple Support Forums!

Thank you!

I exactly agree with the confusion this causes. I have the same on my ipod 128GB which shows 114 instead of 128 and only after that a further deduction for Apps etc. Roaminggnome - very interesting and I have researched and now understand the decimal v binary bases, GB v GiB etc but we are not all computer engineers or geeks, so looked at by the ordinary intelligent and logical consumer a 14GB differential between advertised and displayed capacity appears huge without further explanation. What very much annoyed me was that when I spoke to someone at Apple Support they were blissfully ignorant of this explanation - which I would have thought technically pretty basic and something a lot of people would have contacted them about. They told me there must be a fault and to take it back for a replacement - which of course merely takes you back to square one. Ditto the "technician" at the Apple store. What are these people employed for? I shouldn't have to rely on researching such a basic source of consumer confusion myself over the internet. Now I seem to have returned a perfectly sound ipod needlessly, at great inconvenience. No doubt without this research I'd be returning the second one. Apple "support" really ought to get a grip and ensure all their technical personnel are fully trained to explain this problem. The guy I spoke to was clearly clueless and could not even look me in the eye. Hopeless.

Yes, snapdude but we shouldn't need to rely on forums when technical staff are employed to deal with precisely these sort of problems.

wildejamey wrote:

Yes, snapdude but we shouldn't need to rely on forums when technical staff are employed to deal with precisely these sort of problems.

A) I am not a dude. B) Almost everyone here is a volunteer. C) There is no problem. D) Of course you have to do some research about anything you don't know much about. That's how many of use ended up here. We came with questions and learned enough to help others.

wildejamey wrote:

Yes, snapdude but we shouldn't need to rely on forums when technical staff are employed to deal with precisely these sort of problems.

We are all volunteers, not employees.

Why does MacOS (Since OS X 10.6) use 1 KiloByte = 1000 Bytes while iOS uses 1KiloByte = 1024 Bytes?

The following is from: How OS X and iOS report storage capacity - Apple Support

Understanding storage capacity in Mac OS X v10.6, OS X Lion, and OS X Mountain Lion

In Mac OS X v10.6 and later, storage capacity is displayed as per product specifications using the decimal system (base 10). A 200 GB drive shows 200 GB capacity (for example, if you select the hard drive's icon and choose Get Info from the Finder's File menu, then look at the Capacity line). If you upgrade from an earlier version of OS X, your drive may show more capacity than it did in the earlier OS X version.

Yes, roaminggnome provided that link in September of 2014 in the first answer in this thread.

Yes, I realized that, but since he contradicted what it said by saying "Same reason almost all computers and other devices with storage do this." I felt it needed to be pasted directly into my post.

Certainly it is not true for all Macintosh Computers since 2011 and especially since this is an Apple website he should not have said it. He should have said all Microsoft Windows computers and since I know nothing about Microsoft Windows I certainly couldn't even make that claim.

If iOS used 1 KiloByte = 1000 byte units like MacOS, and the capacity on the device reflected what the box said like my MacBook, this thread wouldn't even exist.

Every single binary computer and operating system (iOS, OS X, Linux, Windows, Android, etc) all actually use the convention of 1Kilobyte = 1024 Bytes since they actually compute everything from an effective transistor state of ON or OFF.

Any one with basic math skills can convert from base 2 to base 10. OS X reports capacity in base 10 but it does not use capacity in base 10. It could be coded to report capacity in base 7 if someone wanted it to.

Regardless how capacity gets reported by a piece of software to the end user, all binary computers read and write binary data, and thus work in RAM and storage in base 2 units of capacity. Thus in a binary system a Gigabyte is always 2^30 bytes, no matter how some piece of code converts and reports that.

The question was not about Circuit design, or assembler language or why 0x40000000 = 1073741824 or why octal is used with permissions.

99.99% of iPhone users do not care to know their binary. In todays age most programmers don't ever need to think in those terms. In MacOS's GUI "Aqua" (Since 10.6) when a GB is being referred to the definition is 1 GB = 1,000,000,000 Bytes and the stated capacity in "Aqua" always matches the drives capacity stated on the outside of the box. This also applies to a Terminal login. diskutil info "/volumes/Macintosh HD" reports "Total Size: 750.0 GB (750046937088 Bytes)"

BTW 750046937088/1073741824 = 698.5 not 750.

The reason the capacity listed for a 128 GB iPhone is stated as 113.99 GB is the programmers don't care enough to make it look right to the average user.