Build Quality Issues, Scuffgate

Section by Vivek Gowri

Despite all of the effort put into the iPhone 5, Apple has had its fair share of growing pains with the 5 design. The main thing here is definitely Scuffgate, which we'll get to in a moment, but it's not just that. My personal unit had an issue with the front glass not being properly mounted into the frame, something I tried to correct by just applying pressure until it clipped in, but it ended up unclipping again after some time. I'm not sure how widespread it is, but worth noting nonetheless. Add in the litany of other issues with the 5, including a fair number of nitpick-level complaints that SNL chose to poke fun at last weekend, and it's clear that this isn't a perfectly smooth launch.

Which brings us to Scuffgate, a two-fold issue that relates to the scratchability (scuffability?) of the new iPhone. Now, iPod users have been used to devices that are near-impossible to keep in decent condition for quite some time now. Any iPod with a chrome back (the first four iPod touches, all classic iPods, 1st and 3rd gen nano) is liable to scratch just by looking at it wrong, and there was actually a class-action lawsuit filed about this some time ago. But an iPhone that scratches easily is a pretty new phenomenon, which is why this is becoming a big deal.

These surface defects are commonly occurring on both black and white iPhone 5s, with the key difference being that the silver metal doesn't show imperfections nearly as much. The raw aluminum colour is a silver that's similar enough that unless you go hunting for it, in most cases you won't notice the texture difference. The black/slate 5s tend to show it pretty clearly though - the bright silver of the raw metal contrasts quite a bit with the dark finish, so even small imperfections tend to be high visibility. If you like to keep your phones naked (without a case or protective skin), I recommend going with the white 5. As sexy as the dark metal casing is, it starts looking a bit more low rent with a couple of scratches in it.

The other problem? People are having iPhone 5s delivered with noticeable scratches and dents, straight out of the box. Mine came with a couple of very minor ones that I only noticed after hunting for them, no big deal, but I've seen some aggrieved owners posting unboxing pictures showing relatively major surface flaws in the metal. In my opinion, this is the more concerning part of the "Scuffgate" equation. It's just not acceptable for significant surface defects to exist on brand new phones out of the box. With that said, I can understand how the 5 bodies are getting scratched in the factories. Let me explain, starting with the electrochemical anodization process for aluminum.

It works like this: the raw aluminum is submerged in an electrolyte through which a direct current is applied, growing an oxide at the anode electrode (the aluminum) and hydrogen at the cathode. Essentially, this is just a controlled electrochemical corrosion reaction. It results in the production of AL2O3, which we know as aluminum oxide (or α-alumina), along with a bunch of hydrons (H+) at the anode, plus dihydrogen gas (H2) at the cathode. The anode reaction looks something like this: 2 Al (s) + 3 H2O (l) = Al2O3 (s) + 6H+ + 6e-. As this process continues, a porous alumina film is created at the surface. This gives the slightly rough texture we're used to seeing on anodized aluminum products, but also allows for coloured dye to be poured in. The dye is then sealed into the material by putting the aluminum in boiling water. Professor Bill Hammack from the University of Illinois Urbana-Champaign biomolecular engineering department gives a pretty solid rundown of the basics in the video below, if you want a more visual explanation of the process.

Basically, the key to all this is the porous aluminum oxide layer. Based on the voltage, anodization time, and the specific electrolyte solution used, the depth of aluminum oxide created and size of the pores can vary. It's actually also possible to create a non-porous barrier-type alumina if an insoluble electrolyte is used in the anode, but that's a different story for a different time. Also, since this came up during the podcast and in the comments later, it's worth mentioning that aluminum reacts with air naturally to create a very thin oxide layer to protect the bare metal in a spontaneous mechanism known as passivation. By very thin, I'm talking on the ångström level - 50 of them, give or take. That's five nanometers, which is almost negligible, but more importantly, it's nonreactive to air beyond that so there is essentially no corrosion. This makes perfect sense if you think about how bare aluminum or any other raw metal reacts to air in purely physical terms, but it's always good to relate real-world observations to the chemical reactions taking place. Now, back to the various factors that dictate the properties of the anodization process - we don't have access to any of that information, beyond knowing that the specific aluminum being used is a 6000-series alloy. My digging suggests that it is likely some form of 6061, which is composed of 95.85%–98.56% aluminum, along with some combination of silicon, iron, copper, magnesium, manganese, chromium, zinc, and titanium, amongst other elements. It's hard to know exactly what Apple doing, but we're in a pretty good position to make educated guesses as to their methods and intentions.

A diagram showing the four steps of pore formation during the aluminum anodization process. The blue indicates the electrolyte solution, the light gray is the aluminum oxide, and the dark gray is the base aluminum. E indicates the flow of electrons. (Source: University of Halle-Wittenberg)

Apple has been anodizing handheld devices since the iPod mini debuted almost a decade ago, but obviously the process has been updated in the intervening years. The last notable change was a switch to an anodization process that resulted in denser pores around two years ago - it first showed up in the 2011 MacBook Pros and the iPad 2, eventually spreading to the rest of the lineup. The iPhone 5 takes that to a whole new level, with even finer and denser pores than I've seen used on any Apple product in the past (pore density is inversely proportional to pore size.) It's also a thinner metal than we've seen Apple use before. The material thickness for the iPhone 5 is just significantly thinner than they use on iPads or MacBooks, or even the old iPods that used anodized shells (iPod mini, 2nd, 4th, 6th generation nano, the last few iPod shuffles).

Which brings us to the next key detail with the anodization process: typically, the thickness of the anodization adds about half that thickness to the total aluminum thickness. So if you had an aluminum plate that was 1mm thick and added a 0.2 mm oxide, post-anodization, you would end up with a total material thickness of 1.1mm. With Apple trying to maintain as slim a profile as possible, it's in their best interests to have a relatively thin anodization. Given the graining of the anodization and based on what I've seen from scratching up my own iPhone 5, I think Apple's anodization process results in a super-thin alumina, something on the order of less than a hundred microns, at most; I'm estimating around 50-75um. (I'd also just like to note that in the process of this review, I took a jeweler's screwdriver to the back of my previously pristine iPhone 5. I love you guys, don't ever forget it.)

The oxide is even thinner on the bands, particularly the chamfers, which are just painted metal. So while the entire thing is easy to nick, it seems easiest to scratch off lots of paint on the bands, as well as the various metal edges. The soft-anodized surface is just a magnet. And the thing is, I'm not even sure they have the material thickness to oxidize more of the surface to get a more durable finish. The entire phone is so thin, and especially on the bands, I can't see a way for them to corrode any more of the aluminum than they already have without it raising questions about structural integrity. So, without very special care inside the factories, it's pretty easy to see how defects could occur. The rumors of Apple tightening down on quality control inside the iPhone 5 assembly factories comes as no surprise, since the 5 really does need extra attention to make it out of the factory unscathed.

So, are there any solutions to Scuffgate? Not really, or not anymore than there were with Antennagate. If you owned an AT&T 4, your only options were to put a case on it or just deal with the potential dropped calls. Here, your only options are to put a case on it, or just be very careful and deal with the potential scratches. If your phone came with defects out of the box, I'd just try returning it in hopes of getting a closer-to-perfect replacement unit. In the meantime, Apple needs to implement some controls internally to ensure that shipping devices don't contain any major surface-level defects. Maybe put some of those 29-megapixel cameras to good use. If Apple really wanted to fix it, they could put some sort of scratch-resistant polymer coating over the bare metal, but that'd absolutely ruin the surface feel. If I was Jony Ive, there's no way I'd let that happen, so until Apple changes up the design (like building antenna diversity into the CDMA 4 and 4S), we've just got to deal with it.

Design The A6 SoC
Comments Locked

276 Comments

View All Comments

  • themossie - Tuesday, October 16, 2012 - link

    The manufacturer's charger uses a set of pull-up resistors connected between the various USB lines, to indicate that the phone can pull maximum current. Unfortunately, every manufacturer (and sometimes different phones) use different resistances.

    See http://electronics.stackexchange.com/questions/144... for a brief writeup.

    For what it's worth, I've only had this problem with iDevices and the HP Touchpad. I own circa-2011+ HTC, Motorola and Samsung phones, and they all work fine with every charger. My Droid 2 Global was my primary work phone until a few months ago, and works great with every charger. Not sure why your wife is having problems there.
  • crankerchick - Tuesday, October 16, 2012 - link

    "The non-LTE phones see a sharp drop in battery life. At least at 28nm the slower air interfaces simply have to remain active (and drawing power) for longer, which results in measurably worse battery life. Again, the thing to be careful of here is there's usually a correlation between network speed and how aggressive you use the device. With a workload that scaled with network speed you might see closer numbers between 3G and 4G LTE."

    Perhaps you all could devise a test for this? Something like, change your LTE and 3G tests, where you decrease the time between page loads for the LTE test, to simulate doing more browsing since the pages load faster? One data point on this, with a reasonably selected change in page load duration, would be very helpful now that we have this very interesting dynamic clearly visible.

    That said, as always, I appreciate the reviews presented here. Always thorough with lots of information to chew on beyond specs and "user opinion on user experience."

    Just wish the reviews didn't take so long, but they are always worth it in the end.
  • TofDriver - Tuesday, October 16, 2012 - link

    Thanks for this awesome article. Gigantic work, we'll worth the wait.
    I've learnt so much.
    Would still appreciate it as an ebook, even after the web reading!
    Seems like you're perfectionists who love to push limits... To me it does resonate with the team who designed the reviewed product.
  • name99 - Tuesday, October 16, 2012 - link

    "Another potential explanation is that the 3-wide front end allowed for better utilization of the existing two ALUs, although it's also unlikely that we see better than perfect scaling simply due to the addition of an extra decoder."

    Remember the standard numbers. On this type of integer code:
    1/6 instructions are branch
    1/6 instructions are store
    1/3 instructions are load
    1/3 instructions are ALU
    This means the usual first throttling point i cache access, if you can only do one load/store cycle.
    If you limit your cache to one op/cycle, it's generally not worth going beyond 2-wide --- too often you're waiting on the cache.
    Once you widen your cache (usually, at this stage, by allowing simultaneous read and write per cycle) three-wide makes sense.
    Each cycle now (on ideal and some sort of "average" idealized code) you can now do some sort of combination of half a branch, 1.5 load/stores, and 1 ALU. Meaning that 2 ALUs (as long as they are not overloaded and also handling some aspect of the load/store) is enough for now.
    [Of course things never work out quite this ideal --- you have burstiness in operation types, not to mention delays. But the compiler should try to schedule instructions to get this sort of average, and likewise the re-order queues will do what they can to shuffle things to this sort of average. 2ALUs helps with the bursts, 3ALUs is overkill.]

    So I would say the primary important change made to go to three-wide in a way that is not a waste of time was to convert the L1 cache to dual-ported, supporting simultaneous load & store per cycle.
  • jiffylube1024 - Tuesday, October 16, 2012 - link

    I have to commend the Anandtech team for the great review! It was a long wait, but well worth it. The info on anodizing, the "Swift" CPU @ 1.3 GHz, camera performance, etc. was worth waiting for. This article, in my eyes, is a culmination of the Anandtech team's knowledge in the tech industry - deconstructing A6 to figure out what it's made of, discussing Apple's manufacturing capabilities, etc. Very informative and well written!

    I am always amazed at how many complaints (and petty platform wars) get exposed on the comment board. I certainly appreciate them when an article is poorly written, contains false information or outright lies, but with an article like this, the comments section seems shy of the effusive praise it deserves!
    ------

    On a slight tangent, I've enjoyed the first 8 Anandtech podcasts as well, and I have to say that I look forward to more non-iPhone related disucssion on future podcasts. The information was much appreciated, but for a tech site as broad as Anandtech, the first 8 podcasts have been VERY iPhone heavy in their content! Keep up the good work.
  • jamyryals - Thursday, October 18, 2012 - link

    I think you're right, it has been iPhone heavy, but the start of the podcast kind of lined up with the launch/review process. Let's be honest, it is a huge selling high quality device and it's treated as such. I have a feeling Brian and Anand will have a lot to say about all of the impending Nexii/WP8 when they come out this quarter.
  • krumme - Tuesday, October 16, 2012 - link

    Good to see reviewers apreciation of low light capabilities for the BSI sensor, reflecting real world usage. Oposite to a lot of uninformed stupid reviews on the net.

    Its exactly the same practical difference between s2 and s3 cameras. Big difference for real usage.

    All the mpix race must stop now. 8M is way to much for the quality anyway.
  • Zanegray - Tuesday, October 16, 2012 - link

    I love the level of analysis and attention to detail. Keep it up!
  • mrdude - Tuesday, October 16, 2012 - link

    Wow, what an article. Really fantastic read. The lengths you guys have gone to in this review is stunning, frankly. Well done. Although I'm no Apple fanatic, I must say that this is one of the better articles I've read on AT :)
  • Dennis Travis - Tuesday, October 16, 2012 - link

    Totally outstanding review. You guys covered everything. Thanks so much!

Log in

Don't have an account? Sign up now