About a month ago I retired my trusty Sprint Evo 4G (original Wimax version) and got a Samsung Galaxy S3.
My initial impression of the Galaxy S3 was quite positive. I’ve spent a considerable amount of time now with the Galaxy S3, so I want to give a bit of an update on my experience with it. I drive a truck over the road and also use it as a podcast aggregator and playback device, so I am spending even more direct time with my phone than the average consumer might.
The Sprint version of the S3 is currently using the so-called “Ice Cream Sandwich” Android 4.04.
Battery life is excellent compared to the three previous smartphones I’ve had over the past several years using the stock battery that came with it.
The large 4.8” inch AMOLED LCD high resolution touchscreen is superb, with excellent color saturation. The extremely thin form factor allows me to easily carry the phone around in a front pocket.
Performance remains excellent even though I’ve installed several dozens and dozens of apps. App performance is rock solid. I had many of the same apps on my HTC Evo that would sometimes crash or cause problems that run perfectly on the Galaxy S3. I attribute this performance increase to more primary phone memory and perhaps better overall hardware design architecture. It’ likely that people that experience problems with certain apps are really experiencing lack of enough physical memory in their device in the same way that desktop computers experience fewer crashes and more overall stability when they have more physical RAM in which to execute the program code.
The Galaxy S3 has excellent WiFi performance. Connected to a Verizon MiFi 4G WiFi hotspot the WiFi has no slowdown issues even when simultaneously using Bluetooth.
The Bluetooth functionality works pretty well overall, but not quite as good as the HTC Evo. I have a JVC Stereo-Bluetooth-capable stereo in my pickup that functioned just fine with the Evo in speakerphone mode that doesn’t work properly with the Galaxy S3. I can hear callers through the stereo speakers but they cannot hear me through the return channel microphone. I don’t know if there is a Bluetooth version number conflict that could possibly resolve the problem via a JVC firmware upgrade, or if the problem might be resolved when Sprint and Samsung release the next “Jelly Bean” version of Android for the Sprint version of the Galaxy S3.
This problem with the S3’s Bluetooth not working properly with my JVC stereo is even more perplexing, since it works perfectly well with the other Bluetooth devices that I own, including a Tango TRX high fidelity Bluetooth stereo speaker that also can work as a speakerphone.
Overall I’m extremely pleased with the Galaxy S3. This is one of the most amazing pieces of technology I’ve ever owned.
In my opinion, the Galaxy S3 is currently the best phone on the market today.