Interested in feedback on new Galaxy Watch 3.
My wife got me the watch as a present last week, since the day it was unpacked (especially after the firmware upgrade) I have seen the following problems:
Takes 3 to 4 hours to charge
The maximum life span of the battery is 7 to 8 hours with almost everything turned off, no location tracking, only alerts for calls / SMS etc. I have followed several youtube videos to optimise battery life - nothing makes it more than 8 hours.
Overheating - spontaneously claims it needs cooling and goes into emergency mode. (also doe this sporadically while charging).
I assumed it was faulty so returned it to the store and got a replacement.
Now the new watch does exactly the same thing.
Is this the experience of anyone else - does the store I am getting the watch from having a bad batch, has Samsungs quality control really that bad?
Any feedback/ideas welcome.
This product is currently completely useless!.
Whether you're using a phone, tablet, smart watch, or earbuds, all Galaxy devices have a set temperature range, where they operate at their best. While they may feel warm under certain conditions, like charging, this does not affect the device's lifespan or performance. However, if your devices get too warm, it could cause some issues. Give this link a try: https://www.samsung.com/us/support/answer/ANS00076952/
I have had two Galaxy Watch 3's, and while I haven't noticed the temperature problems below, they both, (one from Samsung on release, the other a month later from Amazon, both returned), had the issue of the heart rate bailing out randomly during an activity. That was why I returned the original to Samsung, and later decided to give it another try. Bought one from Amazon, did the same activity, and the HR bailed out again for about 1/3 of the activity. Then several more small disconnects. I returned it also. Now, before someone says "you're not wearing it tight/loose/high enough, I have had Suunto's, Garmins, (Fenix 3, 5, 6, 6 pro) Apple Watches, (2, 3 4, and 6) and a couple Polars a while ago, and NONE had this problem. This is unique to Samsung, and consistent (to the watches I could test). Gotta wonder why this is, and if Samsung is aware, or attempting to correct this. Anyone else seeing this?