While Android Leaps Forward, Samsung’s Software Still has Trouble Catching Up to its Hardware

I don’t tend to keep it a secret that I am a fan of Samsung phones. I wrote about how I felt the Note7 was a “Remarkable Phone for Life”, meaning that it was suited for everything life throws at it, and I could probably rewrite that article substituting every Note7 reference for the Galaxy S8. Ever since Samsung’s renaissance with the Galaxy S6, I have been hooked.

Ultra premium designs have become more orchestrated and perfected with every generation sandwiching glass, aluminum, and more glass into a what I feel are the best built phones on the market, period. Samsung’s AMOLED displays had a really rough start but the last few years have been dominated by Samsung’s brainchild and are now delivering the most versatile, accurate, and pleasing displays that money can buy. It doesn’t stop there either: the camera is a constant top-tier contender even if it trades its accuracy for amazing focus abilities, and Samsung has led the way in mainstream water resistance. While the whole industry has moved forward from the fantastic plastic flagship era, it is hard to deny that Samsung feels and looks like it is moving at a totally different pace and momentum. All of that comes to a crashing halt though, the moment you actually have to use a Samsung phone, and in this aspect I feel that Samsung is quickly losing ground.

Back in the day there was a real need for UI and UX improvements on Android. HTC’s Sense software, in my opinion, helped move Android from what felt like a nerd’s playground – that looked the part – into a professional and aesthetically-pleasing OS. Samsung’s TouchWiz software no doubt was the starting point for what is finally becoming a fully-fledged multi-window-supporting AOSP, and Motorola innovated in hands-free intelligence, always listening microphones, and screen-off notification displays. Google has taken these features along with their basic implementation and added them to what we typically refer to as Stock Android, and in doing so has managed to keep it streamlined, responsive, and most importantly it feels bloat-free. Samsung though, must have missed that particular memo and in doing so still delivers a bloated experience that suffers due to their insistence of adding more and more “features”, and I use that term loosely, to their phones. This isn’t to say that Google does everything properly, or that every OEM should implement stock Android with merely a boot animation distinguishing them, instead, heavy-handed experiences like Samsung’s need to be cut back, optimized, streamlined and offer the user more choice.

While everyone’s baseline for what is acceptable is different, it is hard to deny that bloated options like the Samsung Experience have a detrimental effect on device performance. I am jealous every time I watch a video showing off the HTC U11 or Google Pixel; they are just so instantaneously responsive, something my S8+ cannot match even on its best days.

It’s not just the amount of added applications and services, it is also the optimization of them that matters. On your Galaxy S8 right now, there are dozens of services running that simply do not need to be there for most users, that are taking up valuable system resources, and even if the impact of them is low it is still something running that simply does not perceptibly or substantially add to our experience. These running services take up your available RAM, but more importantly are using valuable CPU time and attention. Have you ever used the the Samsung DeX system? Well, its software is running on your S8. Ever used Samsung’s woefully broken and useless “Connect” or “Bixby” services? Well, those services are running right now on your S8. Even if you have never applied a theme to your phone, there are at least 2 themes services that are running that have no need to be, because if disabled, your phone works exactly as it did prior to disabling them; I know, I have them disabled. If you have ever used GearVR, the Oculus suite is installed and stays running at all times, even if you haven’t used your headset in days or weeks or since a reboot. Normally most users won’t even notice one or two of these services running in the background, but when those services add up to dozens of unneeded running tasks, it quickly becomes a problem. 

… Just no Samsung

Samsung’s insistence on adding a growing amount of limited use and poorly-optimized software adds little more than a bullet point during an announcement and some usefulness to a small subset of users. Inversely, its negative impact affects all users of the device even if they never use the services or even know it exists. There is a reason why one of the most common comments in Galaxy S8 reviews was the skepticism over if the device will remain responsive, because the Galaxy S6 and S7 have not aged as gracefully as their less-bloated brothers from other manufacturers, and it’s not because the S7’s Snapdragon 820 magically got slower over time. Personally, I have used a package disabler to remove over 180 services and packages I simply do not need on my phone, and that is with keeping the stock camera, dialer, and calendar. The funny thing is that with all of these services and applications disabled, my phone feels more responsive, less unpredictable, and offered better battery life than before. Perhaps not substantially, but demonstrably — and I’ll back that up in an upcoming article as well. 

Without the missing “Device Maintenance” tab in settings you would be hard-pressed to even know so much is disabled. I also do not get endless runs of force closures and broken features, because the phone was built to run this way, without all of the crap and bloat Samsung markets. I don’t need eyeball aware screen timeout (it’s still there by the way), or to have the phone tell me that it can clean 700mb of perceived useless files. I don’t intend on turning my phone into a PC or unlocking it with my eyes, and I certainly never plan on using the Bixby button for more than an accidental power key when my phone is upside down. What is ironic is that the Bixby key is the physical representation of all of Samsung’s software; useful for a few but is just a useless add-on for others taking up valuable space or resources that could have been spent elsewhere or used for a different purpose. Samsung’s software ,aesthetically, is the best it has looked in years and deserves the praise it has received lately; but it is just as bloated and janky as ever, which is the complete opposite of its hardware which is simply unrivaled.

But these are also some of the same things that set Samsung apart from the competition; as I mentioned earlier their multi-window was and is still years ahead of Android’s stock implementation and they are the only company right now reliably using alternative biometric unlock methods. But we need a change that can be narrowed down to two things: the first is an opt-in or even a fully disabled opt-out methodology. If I do not want edge features, Iris unlock, and the like; I as the user should have the ability to remove them without resorting to third party solutions that sometimes do not even work, and might have uninformed users misconfigure their phone yielding adverse effects. Secondly, those services I do opt-into need to be optimized so they are not needlessly running. I don’t mind waiting an extra 2 seconds for Oculus to open up if it means its service is not running in the background for the week that I never used the service.

The main issue isn’t necessarily the gambles they are taking with new and innovative features, but that they are taking them in a way that is poorly optimized which significantly hinders the experience. General performance and efficiently handling services aren’t sexy things you can slap on a keynote, but they are much more important to our day-to-day experiences, and Samsung needs to take this into consideration when prioritizing their efforts. Android no longer needs an OEM’s customization’s to make it run better, more aesthetically pleasing, or more feature rich by default. While themes and extra features are niceties to have they shouldn’t be forced on users who simply want an uncluttered experience.

I love my Galaxy S8+ and often times I will hold it just to admire the craftsmanship, because it is a beautiful piece of hardware. However, the moment I ignite that display I am reminded of just how much I give up for that experience and at some point it just isn’t going to be worth it anymore.

Why you won’t be using Bluetooth 5 on your Galaxy S8 just yet – Gary explains

The Bluetooth Special Interest Group (Bluetooth SIG) announced Bluetooth 5 during the summer of 2016 and then towards the end of that year the new specification was officially ratified and we started to see Bluetooth 5 appear in hardware, first in development boards and then in consumer devices, most notably the Galaxy S8.

Last month I got hold of a couple of Bluetooth 5 enabled nRF52840 development boards from Nordic Semiconductor. Using these I was able to test the real world capabilities of Bluetooth 5 and also cut through some of the marketing hype about the new standard.

Most notably I was able to clear up the huge confusion around the ideas that Bluetooth 5 offers 4 times the range and twice the speed. In fact it turns out that Bluetooth 5 does offer (almost) twice the throughput when the two communicating devices are close to each other, but towards the edge of the possible range I demonstrated that Bluetooth 5 has the same throughput as Bluetooth 4.

At the same time I busted some of the myths about Bluetooth 5 offering 4 times the range. The way it has been presented is that the 4x range and the 2x throughput work hand-in-hand, whereas the truth is that the extra range is only available when using a special connection type built into Bluetooth 5, known as a CODED connection. These CODED connections offer a very low throughput, around 109Kbps, but with the advantage of greater range.

Bottom line, forget any dreams of taking your Bluetooth 5 enabled speakers out into the yard while your smartphone is in your bedroom and still getting a good connection speed. For more details on all this you really should watch my video the truth about Bluetooth 5.

After my testing with the development boards, I turned my attention to the Samsung Galaxy S8. My aim was to hack together a quick app which allowed me to test the throughput between two Galaxy S8 handsets over Bluetooth 5.

So I went to Samsung’s developer website to look for a Software Development Kit (SDK) or maybe some documentation about how to access the Bluetooth 5 features, but I found nothing. Thinking that maybe Android already supported Bluetooth 5 I headed over to the official Android Bluetooth documentation, but again nothing.

At this point I was becoming a bit worried, did the Galaxy S8 really support Bluetooth 5?

My first port of call was the Bluetooth SIG website. I was able to find there the official certificate that showed that from a hardware point of view the S8 does indeed support Bluetooth 5. But which bits of Bluetooth 5? Support for the 2 Mbps and Coded connections are optional in Bluetooth 5. The only connection that is mandatory is the 1 Mbps connection speed from Bluetooth 4. Fortunately the Galaxy S8 supports the 2Mbps connection speed, however it doesn’t support the CODED connections. This means there is no “4 times the range” support in the Galaxy S8.

I emailed the PR people at Bluetooth SIG to try to get some more information. They replied quickly and very nicely, however they weren’t able to add much information. The only information that they could share about the S8 was what is on the certification page.

This means there is no '4 times the range' support in the Galaxy S8.

While I was talking with the Bluetooth people we (as in the Android Authority team) tried to get some answers from Samsung and from Google.


At Google I/O, my esteemed colleague Kris Carlon sought out some clever engineers from Google to ask about Bluetooth 5. What we have found out is that Bluetooth 5 will be officially supported in Android O. In fact it is already in the developer preview versions of Android O and the source code has been published in the Android Open Source Project (AOSP). Android O will support the new 2Mbps connection and the new CODED connection type (for that extra range). It will also support the new longer advertising packets.

So it looks like Google’s support for Bluetooth 5 in Android O is pretty good and includes everything we need and expect.

However, before you get too excited, we must remember that Bluetooth 5 functionality will only be available in handsets which have the relevant Bluetooth 5 hardware (i.e. chipset). You can’t convert an older Bluetooth 4 device into a Bluetooth 5 device just by upgrading to Android O.

What this means is that the Samsung Galaxy S8 is well positioned to get native Bluetooth 5 support from Android, but only when Samsung releases an Android upgrade from Nougat to O.


This leads me to one conclusion, you can't use Bluetooth 5 on the Samsung Galaxy S8.

While the Bluetooth SIG and Google were very helpful, I can’t say the same about Samsung. Several different members of the Android Authority team have asked different representatives in Samsung about the status of Bluetooth 5 in the Samsung Galaxy S8. We have had a couple of replies thanking us for our question and a promise of a reply, but so far nothing. It has been more than two weeks!

Since there is no support in Android N for Bluetooth 5, there is the possibility that Samsung has included support itself or that there is an SDK which developers can use to access the Bluetooth 5 features. The normal port of call for such information is developer.samsung.com/galaxy.

Samsung provides a range of software development tools for accessing features like multi-windowing, fingerprint recognition, the S Pen and so on. However there is nothing about Bluetooth 5. Specifically for the S8 there is information about the Edge Panel and Samsung DeX, but no Bluetooth 5 documentation.

This leads me to one conclusion, you can’t use Bluetooth 5 on the Samsung Galaxy S8.


The Galaxy S8 has the right hardware to support Bluetooth 5, but it doesn’t have the right software. If Google and Samsung follow last year’s playbook then Android O will be released sometime this summer (maybe August) and then Samsung will get to work on releasing a version for the S8. The upgrade to Nougat arrived for the S7 in January/February of this year, so it is likely that the S8 will get Android O during the first part of 2018. Until then the Bluetooth 5 capabilities of the S8 remain locked and unusable.

The 10 best and worst things about the Galaxy S8

The Galaxy S8 is the hottest Android device available right now. A jack of all trades, there's plenty to love about the phone, but also an equal numbers of things that really get under my skin. Here's the top 10 best and worst things about the Galaxy S8 and S8+.

Theme your Galaxy S8/S8+ Navigation Bar using Overlays

Yesterday, a post on our Samsung Galaxy S8+ forum was making the rounds around the net which enabled you to theme the navigation keys on your phone to match the keys from the Google Pixel. This theme can be installed using an APK and it merely functions as an overlay on top of the existing navigation bar keys. Since yesterday, more contributions have been made to the thread and more bugs have been squashed, so we feel comfortable sharing some of these members’ work on the Portal.

Check out the thread linked below if you own a Samsung Galaxy S8 or Galaxy S8+ and want to theme your navigation bar. Available themes include an AOSP-based nav bar, a Google Pixel based nav bar, and a combination of either of these two with a dark notification panel. Follow the thread for more theme updates if you’re interested. Finally, you can also see our previous tutorial on how to add custom buttons to your nav bar.

Get custom nav bar themes for the Galaxy S8 or Galaxy S8+