Ultimate Drop Test: Apple iPhone 6s easily outlasts Samsung Galaxy S7

Drop tests usually “involve someone dropping a phone by hand, and the distance is often as imprecisely measured as ‘waist height’ or ‘head height,’ making it hard to be sure both phones experienced exactly the same force,” ben Lovejoy writes for 9to5Mac.

“Dropping a phone from a hand can result in differences in initial angles, and releasing one side of the phone a fraction of a second before the other can impart a rotation to the device,” Lovejoy writes. “In short, most drop-tests are more entertainment than science.”

“But the latest drop-test competition between the iPhone 6s and Samsung Galaxy S7 is done properly,” Lovejoy writes, “using professional equipment designed to ensure that both phones are released in exactly the same way from exactly the same height.”

Read more in the full article here.

MacDailyNews Take: Hey, Samsung’s iPhone wannabe actually is good at something: Breaking!

11 Comments

  1. Consumers get the “picture” very quickly, once they have to replace their inferior products they buy.

    You start learning it as a kid, when cheap plastic doesn’t last. You learn it with shiny cheap junko bicycles from China. El Cheapo “netbooks” pushed by less than honest companies taught kids why Apple laptops are worth the extra few hundreds of dollars.

  2. Where are the usual misguided band of idiot Fandroid trolls NOW? Cowering in their usual inferiority in a van down by the river no doubt. Must suck always making the cheap craptastic choices and subsequently pretending or having to justify that they’re “better” fooling no one but other equally lost souls.

      1. I reserve the “extra cl-ass” remarks to confused buffoons who use “classy” faux names (while attempting to be cute) like “Bloody dick.” (Though it probably does describe you well knowingly to your friends and family.)

        No classy mercy extended to Fandroid. They give none and they get none.

  3. This is great news for Android’s fans and users.

    Google CEO Sundar Pichai speaks during Google I/O 2016 at Shoreline Amphitheatre on May 19, 2016 in Mountain View, California.

    If you ask developers about their gripes with building apps for Android, the same problem comes up again and again and again: “Fragmentation.”

    On Android, Google’s mobile operating system, it is the smartphone manufacturers — not Google — who are responsible for pushing out software updates to users. This is in stark contrast to iOS, where Apple can push out an update to every single (compatible) iPhone in the world simultaneously. And as a result, the Android market is intensely fragmented — with numerous different versions of the OS out there.

    This complicates development, as the majority of Android phones end up unable to utilise the latest features Google introduces for developers. And more worryingly, it can leave millions of users open to hacking as security patches never reach them.

    In short: Google could build an incredible new feature for the next version of Android, but unless Samsung gets around to deciding to push the update to you, you’re never going to see it.

    https://www.yahoo.com/tech/google-plans-shame-smartphone-makers-083035486.html

    1. In related news:
      Google’s making a list: Android OEMs to be ranked, shamed by update speed
      Can Android update woes be solved by publicly calling out slow OEMs?

      No. I posted a comment on the article suggesting Google distribute ‘core’ Android updates, the core being untouchable by OEMs. The OEMs would be responsible for updating their elaborations on Android, in the form of plug-ins, drivers, frameworks, etc. THEN create a shame list according to which OEMs bother to update their own code with security patches.

      Something to this effect is going to have to happen with Android. Otherwise, its going to be FragmAndroid hell forever.

      1. I understood that since the Ice Cream Sandwich version of Android (about 4-5 versions earlier than present) Google has modularized the OS to separate their APIs from AOSP Android. This allowed Google to keep that portion of Android ‘current’ regardless of the Android OS version. In some ways this has mitigated fragmentation of Google related services on Android devices. With years of experience now successfully implementing the modular nature of Google APIs on Android, I’m sure they could gradually do the same to the rest of Android and allow customizations only via OEM original APIs.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.