Software: KNOX & TouchWiz

Around a year ago, Samsung announced SAFE with KNOX, which was effectively Samsung’s attempt to enter the Enterprise sector that BlackBerry and Apple were dominating. This announcement was effectively ignored, but it set the tone for things to come. With the Galaxy S4, at launch it was effectively untouched by these new policies outside of SEAndroid enforcement. However, as 2013 progressed, we began to see the true effects of Samsung’s attempt to gain ground in the BYOD space, as the Note 3 was the first Android phone to have a Knox warranty void QFuse that would lock out any KNOX features if tripped by unsigned software loaded into the system partition or any other partition that had signature checking enabled. This isn’t unusual for Samsung as they have had warranty void flags before, but what was truly exceptional was that this leveraged a QFuse, which makes it impossible to revert the warranty void flag if tripped, because QFuses are physically modified on the SoC rather than on a file in random partition on the eMMC device.

The next noticeable step was when the Galaxy S4 received an OTA update that enabled such behavior as well, and not only did it add the KNOX warranty void flag, it also would make it impossible to downgrade the firmware, which was likely done for security reasons and any attempt to do so would trip the warranty void flag.

With the Galaxy S5, KNOX has finally come full circle, as all US carrier variants are shipping with a locked bootloader. While it’s true that some variants of the Galaxy S4 had a locked bootloader, it wasn’t quite indicative of a real trend, as both AT&T and Verizon are well known for their bootloader locking policies and will often place such a requirement in their RFPs for a new device. On the other hand, Sprint and T-Mobile US are generally accepted as less stringent in their policies for rooted devices. In short, you cannot flash a custom ROM the same way that you could on the Galaxy S4 with an unlocked bootloader.

Update: Based upon recent events the Sprint and TMOUS variants both have an unlocked bootloaders, despite statements to the contrary.

Based upon my own cursory examination, the Galaxy S5 has SEAndroid active, and also has the warranty void flag, although I can’t find any evidence within the system that the Galaxy S5 has a locked bootloader. The AT&T and Verizon versions still retain the locked bootloader, and they don't have any outward indication of such a bootloader lock.

Quibbles with the Knox flag aside, Samsung truly has improved TouchWiz. I’m happy to say that they have finally added some level of aesthetic cohesiveness and just about every major application that I tried was noticeably better than before. Previous pain points such as the horrific tab view that effectively made the settings menu impossible to navigate without frustration, the stuttery launcher, and difficult keyboard have been fixed. The keyboard is now usable, and with Swiftkey’s prediction engine, I don’t actually feel a strong need to immediately replace the keyboard, although I still prefer SwiftKey due to its rather cramped layout from the very large spaces that Samsung has put between the keys, which means the spacebar is incredibly small. The launcher is now smoother than the one I used in TouchWiz 4 on the Galaxy S2, and the settings menu has a much more tolerable grid view by default, although I still find myself preferring the list view, which is thankfully also an option.

Even the simplest things have been changed dramatically for the better. The multitasking menu as seen below is much cleaner in its aesthetics, and the email application (as seen above) finally looks like it was made for Android 4.0 and newer rather than a port of an email application made for Gingerbread/Android 2.3.

However, in some ways TouchWiz takes a step back. There is still quite a bit of inconsistency with their icon design as some icons retain the old rectangular format while others gain the new circle design and the new launcher. Although the launcher is now smooth and clean in its aesthetics, there's a new homescreen called My Magazine, as seen above. Samsung emulates HTC's BlinkFeed down to the placement of it, which is the left-most homescreen. Unlike BlinkFeed though, it is noticeably more limited in functionality as only a few selected topics can be added with no custom RSS feed capability and it can only show one article from each topic at a glance, rather than providing a feed that can scroll infinitely if desired. Trying to look at more than one article requires going straight into FlipBoard, which seems to be the application that drives My Magazine. It’s also quite clear that My Magazine is separate from the home screen because the multitasking menu shows it as a discrete application, and swiping back from the application has a noticeable lag compared to swiping on the homescreens. On the bright side, this can be disabled by going into the home screen settings menu, which is conveniently accessed by pinching on a homescreen to enter the helicopter view, which activates the home screen edit mode. This new view doesn’t display all the screens at once, rather it provides a card view of sorts that the user can swipe left and right upon to view all of the homescreens as seen below.

If this sounds familiar, that’s because it is. This is quite literally the exact same way that one accesses the home screen edit mode for Sense 5 and 6 on HTC devices. Even the widget panel has been moved from the application drawer to this display.

Samsung has finally brought their user interface up to date, and while there are still improvements to be made (e.g. bringing up the multitasking UI takes way too long), I finally no longer feel like TouchWiz is a negative to Galaxy phones.

WiFi, Cellular & Download Booster Final Words
Comments Locked

296 Comments

View All Comments

  • Saltank - Wednesday, April 9, 2014 - link

    Not a single word about actually making phone calls? No call quality / HD Voice stuff? I was awestruck by how awesome my iPhone 5 handles regular non-HDVoice calls, and the GS3 was good, too, but my old HTC One was subpar.

    Also, how come camera comparisons don't take WP's in to account? No Lumia 1020/1520/930?
  • Lightstorm66 - Wednesday, April 9, 2014 - link

    I thought Anandt ech knew that the Samsung Browser is faster than chrome and achieves in the Galaxy S5 even better results than the iphone 5s in sunspider.

    Galaxy S5: 385,8 ms
    iphone 5s: 414,7 ms
  • ryanmt - Wednesday, April 9, 2014 - link

    The LG G2 is the unsung camera hero here. It outperforms it all. Why are only the HTC M8 and 5S called out for their good low light performance when the G2 is actually (subjectively) better?
  • echo9251 - Wednesday, April 9, 2014 - link

    There should be more talk about the lack of a 64MB option. I have a 64MB HTC One (M7) and enjoy never having to worry about running out of storage for apps, etc. Losing half my storage is a big disincentive to "upgrading" to a new phone.
  • Brian Z - Wednesday, April 9, 2014 - link

    Well they did include a micro SD card that supports up to 128gb.

    I am not going to make the case that having more storage considering the outrageous prices of the these devices. But at a point it gets a ridiculous. People complain loud OMG no external storage. No buy. Then they make 32gb device with expandable storage. People still complain
  • Streamlined - Thursday, April 17, 2014 - link

    Uh, because SD cards are dog slow compared to storage on the motherboard. SD CARDS SUCK and that is why HTC includes larger storage options. Just another reason the M8 is the best Android phone money can buy.
  • Myrandex - Wednesday, April 9, 2014 - link

    I'm disappointed no Nokia's showed up in the camera tests. I've love to see how this lined up with my Lumia 920, particularly in the low light tests. My wife's 1020 is a beast too.
  • Souka - Wednesday, April 9, 2014 - link

    Here's a another way to test durability and take apart a S5

    https://www.youtube.com/watch?v=newNF1UsOcw
  • dlang1234 - Wednesday, April 9, 2014 - link

    What I'm most impressed by, is how well the LG G2 is performing at these benchmarks against much newer phones. I have had my G2 for a while now, and it is an awesome phone.. so much so that these phones look more like side grades than upgrades even though, I mean it was released September 12, 2013 and now almost 6 months later, the epic increases of speed in mobile seems to be subsiding some.
  • chrcoluk - Wednesday, April 9, 2014 - link

    agreed.

    I own a S3 and a galaxy ace.

    The galaxy ace has cyanogen mod 7.2 installed on it.
    The S3 has touchwiz based on android 4.3

    In terms of hardware spec the S3 is many multiples more powerful than the ace.

    However many basic functions are much snappier on the ace, in particurly using it as a phone, bringing up the call log, scrolling the call log, making calls, answering calls, opening contacts, all these functions much faster on the ace. The ace also wakes up immediatly whilst the S3 has wake lag, the ace has much longer lasting battery even tho it has a weaker battery. However the ace does suck when it comes to using it for the internet/gaming most 3rd party apps as thats where its hw spec hits it, but its limitations are mostly down to its lack of ram. IT seems to always have more spare cpu cycles than the S£ as the S3 is bogged down by touchwiz.

    So why havent I got the S3 on AOSP. google edition etc? the problem is the contacts/dialer app on AOSP sucks really bad, its aweful. Especially with the default white background. Samsung have at least maintained a half decent UI design in their dialer/contacts the problem is its mega laggy. But sadly UI design wins over performance. CM7.2 has the best ever dialer/contacts I have seen on a android phone but new phones cannot use CM7.2.

    I have recently decided to start using the ace as my main phone (its easier to use out and about also due to its smaller size) and primarily use the S3 as a portable computing device. That way I can stick AOSP on the S3 and not worry about the crappy contacts app.

    Do samsung deliberatly make their interface laggy? not sure, its certianly possible tho as they want to give a people a reason to upgrade to the next phone every year.

    Also notice how every new software update increases the fotn size as well, to give people a reason to want the higher DPI. The relative font size looks equal on my ace vs the S3 even tho the S3 has a way higher resolution.

Log in

Don't have an account? Sign up now