Customers can now purchase Sony's SmartWatch 3 for as low as $147.97, as the wearable device is now on sale at online retail giant Amazon.
The $147.97 price tag is for the white version of the SmartWatch 3. The lime version of the wearable device will cost $159.95, and the black version will carry a price tag of $170.11.
The new prices represent huge savings from the original listed price of the SmartWatch 3. The white and lime versions of the wearable device have an original listed price of $249.99, with the new prices offering customers with a 41 percent and 36 percent discount, respectively. The black version, on the other hand, is offering the biggest discount among the three models at 43 percent, from its original listed price of $299.99.
The higher price of the black version of the SmartWatch 3 is likely because there is a higher demand for that model of the wearable device.
There is no indication on how long the offer will stand from Amazon, and so users looking to pick up a wearable device and have been looking at Sony's SmartWatch 3 as an option should take this chance to purchase one at as much as a 43 percent discount.
Sony's SmartWatch 3 was unveiled by the company in the IFA conference of last year, which was held in Berlin. The device features a 1.6-inch display with 4GB of internal memory capacity, and is IP58 rated as a waterproof device. The SmartWatch 3 also packs a built-in GPS, and has recently been updated to the latest version of the Android Wear OS, namely Android Wear 5.1.1.
However, potential customers should be warned that there is a bug in Android Wear 5.1.1 that is causing battery drain issues in the wearable devices that have the latest version of the operating system installed.
The problem seems to affect all the devices that have received an update to Android Wear 5.1.1 to keep at par with Android 5.1.1 Lollipop for mobile devices. In addition to Sony's SmartWatch 3, other affected devices include LG's G Watch, G Watch R and G Watch Urbane and Samsung's Gear Live.
A representative for Google acknowledged the issue back in June, and has said that the company is aware of the problem and is working on a fix for the issue.
