The weirdest thing has happened a couple times and now I'm concerned. For no apparent reason, my watch keeps doin a forced reset. I then have to go through the whole process of setting it up again. This time around it completely changed the way my watch is set up. Face, settings and icon order. Can anyone help me understand why this is happening? This thing cost too much and is only 4 months old. ๐ก
How do I make this stop happening? Everyday when I take it off the charger I get a notification on my watch to reset watch and reconnect to my phone thus resulting in have to go through the same process as starting from factory settings. Why does this keep happening? I'm about to take the watch back and have them replace it. Mind you it's a new watch set up to a new s24 ultra.
your Galaxy Watch 7 keeps resetting every day, it could be due to several reasons including: low battery, outdated software, a faulty app, incorrect settings on your watch or phone, or a hardware issue; the first step is to check for software updates on both your watch and phone, then try restarting your watch and phone, and if the issue persists, you may need to contact Samsung support for further troubleshooting.
Potential causes and solutions:
Low battery:
Ensure your watch is fully charged, as low battery can sometimes trigger unexpected resets.
Software updates:
Check for and install any available updates on your Galaxy Watch 7 and the Galaxy Wearable app on your phone.
Third-party apps:
Try disabling any recently installed third-party apps on your watch, as they might be causing conflicts.
Incorrect settings:
Check watch settings: Review settings like sleep tracking, activity monitoring, and notifications to ensure they are not set to trigger resets unintentionally.
Check phone settings: Verify that the Galaxy Wearable app on your phone is properly configured and synced with your watch.
Hardware issue:
If the issue persists after trying software solutions, consider contacting Samsung support to check if there might be a hardware problem with your watch.
What to do next:
Restart your watch and phone: Perform a simple restart on both your Galaxy Watch 7 and your paired smartphone.
Check for updates: Go to the "Settings" on your watch and check for software updates.
Manage apps: Uninstall any recently installed apps that might be causing issues.
Factory reset (last resort): If nothing else works, you can try performing a factory reset on your watch, but remember that this will erase all your data.
Seriously, meself, more copy-pasted, generic recommendations which literally contradict the underlying problem? I think we can all benefit if you stop doing this. And I'm quite certain others have provided you the same feedback.
May I ask if you're even pretending to read the specific situation everybody is experiencing?? Or do you just have the same rhetoric that you paste to every conversation repeatedly, regardless of the reported problem?
We report a bug that disconnects the watch from the phone, *REQUIRING* a factory reset of the watch. So you copy-paste some long, useless list of so-called "tips" that includes a TON of useless guesses, but also includes an instruction to "factory reset". Seriously!?
Please, please do us all a huge favor & "Read the room" & only contribute if you have something of value to provide that's relevant to the issue experienced.
Signed - "Everybody".
Thank you for your consideration toward the benefit of everybody.
@meself, I'm not sure if you're being sarcastic? I did speak with Samsung Support maybe 6 weeks ago & they said they'd log a ticket for me. It was recommended here to submit feedback with logs so I did that more than once.
If you're referring to my request that you please discontinue posting the same generic Copy-Paste "tips" which are unrelated to the issue at hand, that request still stands. By request of myself & many other members, for that matter.
We'd all appreciate it very much, as these conversations are long enough already without such nonsense.
Have you (and everyone else who has this problem), in fact, put in an error report with Samsung on the issue? There is no way for the developers to address the underlying issue by posting about it in a user forum. The developers DO NOT read the forums. Sending the error report will transmit the logs so that the developers can see a common denominator among those it's happening to and create a patch. If it's a singular issue with a single user, then they should be able to isolate whatever conflict is causing this and get back to you with a resolution.
This is a peer-to-peer help forum, and the best anyone here can do for you is to suggest workarounds or options to try. No one can fix the code but the developers and no one can determine what's causing this except the developers. So, everyone who is currently experiencing this issue needs to put in an error report and upload their logs - the more reports, the sooner it gets acted upon.
------------------------------------------------------------- Please mark any response that helped you as your solution. -------------------------------------------------------------
Hello. Yes, I've absolutely used the "Submit feedback" option in the Samsung Members app immediately after a watch disconnect, & again after a failed reconnection attempt prior to factory-resetting my watch.
I posted Samsung's response on "Monday" (I believe March 10th) according to the conversation history. A copy-paste of my comment is below for the convenience of yourself & others.
Personally, & per comments from others, their response doesn't exactly make sense.
I hope this helps.
##########
All - I received the response below from Samsung Support after submitting an error report immediately after my watch ultra disconnected...
Their response: "When Google GMS service was reconnected between the phone and the watch, the life360 app attempted to connect at the same time and the watch device information was deleted on your phone. It seems that the life360 app ('com.life360.android.safetymapd') tried to connect watch unnecessary. Please block the life360 app to avoid this problem temporary. We will review a patch and apply it in next watch S/W update."
Based on their response, I have the following questions & concerns:
Question 1: Is everybody affected by this watch disconnect issue using Life360?
Concern 1: Their explanation doesn't seem to explain why the watch will not reconnect until factory reset.
Concern 2: I'm not clear why Life350 would NOW start attempting to connect to my watch when there is no Life360 integration into it in the first place.
Concern 3: I also don't follow how a phone app w/ no Watch integration can cause the PHONE to delete the watch information, while the fix is a watch S/W update?
I don't have life360 - must be a feature of OneUI7 or perhaps Android 15? I'm sorry, I did not read through all 17 pages of responses to determine which phone you are connected and whether you have the Watch7 or 7 Ultra. I have a watch 7 connected to an A54 still running OneUI 6.1/Android 14. I am not having disconnection/reset issues. As I said, no Life360 on my phone. I would take the advice, though, of disabling Life360 until they have a patch (their response seems to indicate they are working on a patch, as they know what's causing it). If you have disabled it already and are still having the issue, you should amend your report to include that information.
As for the integration with the watch, just because there is no companion app for the watch does not mean its functions are not integrated. Once you have a connected device all things interconnect in some way. I don't know what Life360 does or is supposed to do, so I can't determine how or what it integrates with - perhaps it integrates with the modes or the health app or Bixby. Oh, I just looked it up. It seems to be a family tracking app that works with Smart Things and other apps, so absolutely would integrate with the watch. It looks as if it can be uninstalled as well as disabled. If you aren't going to use its features, you may as well remove it if you can.
------------------------------------------------------------- Please mark any response that helped you as your solution. -------------------------------------------------------------
No worries, these combined conversations are making the thread(s) impossible to keep straight. It took me a while to even find my own post. ๐
It also doesn't help when certain folks keep copy-pasting the same lengthy list of nonsense "solutions" & "causes" that blatantly conflict w/ the issue & include "fixes" that folks have already explained repeatedly do not work.
As for uninstalling/disabling Life360, that's frankly not an option for me for several reasons. I have it manually installed on my S23Ultra on purpose to better track & monitor my family's locations, & vice versa, etc. So disabling it for up to ~2+ weeks waiting for the next disconnect issue to manifest is simply unfeasible. Not to mention, for as infrequent as my watch disconnects (Up to ~2 weeks between disconnects), there's no confident way to know if my disabling of Life360 was truly a solution.
Not to mention, their response doesn't make sense to myself & several others for the questions & concerns I outlined in my previous post.
It's been almost 2 months since this issue started for everybody affected & nearly 2 weeks since Samsung responded blaming Life360 for the watch disconnect issues. There's been no Watch Ultra update since ~Jan. 22nd... I think it's about time they get this fixed & pushed out to the masses. This isn't some deprecated piece of hardware, this is a major impact to their latest, flagship wearable devices. You'd think they'd put a bit more priority into fixing it.
Sorry, preaching to the choir. This issue & Samsung's obvious lack of urgency has been extremely frustrating.
