The Galaxy S5 has become an important device for other vendors to look at as a sort of standard, much like the Apple iPhone. Now this latest refresh signals Samsung's dedicateion to the device as a central piece of its overall corporate strategy.
Fingerprint authentification for mobile payments is an important step toward security in devices. Again, other companies are likely to follow Samsung's lead. This is a response to some serious security issues, and represents an appropriate response.
UPDATE: Qualcomm announced that its Snapdragon 801 processor with LTE-A will power the Galaxy S5. Snapdragon has higher speed SD card memory, carrier aggregation for download speeds of up to 150Mbps, as well as dedicated hardware for dual-SIM/dual active service in China.
The processor has an enhanced Adreno 330 GPU performance with quad core Krait 400 CPU running at up to 2.5GHz per core, as well as a custom Hexagon QDSP6 for ultra-low power applications.
Additionally, the Qualcomm Snapdragon 400 processor is featured in the Samsung Galaxy Grand 2. The processor supports 4G LTE World Mode connectivity, has a Adreno 305 GPU, and a CPU running at speeds of up to 1.2 GHz.
Just like 4K video and 16 Mpixels truly achieves equality with good 35mm film SLRs of the past, this quad core 2.5 GHz Qualcomm Snapdragon is right up there with very decent desktop PC processors. I'm impressed! Let's dock the thing and replace PCs with it! As well as film cameras.
It was predictable that eventually we'd be getting here. I think these are important milestones.
Nothing exciting in S5. All the additional features such as dust and water proof, finger print, 16M pixel camera, 2GB RAM, Quadcore etc are available in one phone or other. Only additional sensor for heart rate monitor is not justified the wearable device. Most watches have that fearture. I think Samsung killed the innovation with S5.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.