- May 21, 2015
- 2
- 0
- 0
S Health application of Samsung Gear S "Receiving Location" process never finds location
The following are what I've observed in my Gear S watch's S Health application, with "Receiving Location" never finding location in approximately 75% of attempts in using the S Health application, and it reoccurs even when the watch was replaced, and the Gear's operating system and the Gear Manager application were uninstalled and reinstalled, three times. There were additional applications added initially before the symptoms were observed (a watch face and a navigational app), but the system has been cleaned, restored to native state, and the problem still occurs. Of note, the navigational app had no difficulty in finding location (in tethered and stand-alone mode). So this appears to be in the S Health application only.
The problem occurs in tethered (bluetooth) mode and stand-alone mode with equal frequency. I have the Galaxy S6 phone (G920V), with the newest operating system (5.0.2). My partner uses the Samsung Galaxy Edge and this exact same model of watch and has not experienced any of these difficulties. To reiterate - The watch has been replaced by Verizon, kept in its factory default state, and the following problem still occurs:
My setup:
1. Gear model B6DE
2. I have the Galaxy S6 phone (G920V), with the newest operating system (5.0.2), with the latest Gear Manager application
3. Gear working in tethered or stand-alone mode
4. With additional applications added, or in factory default state
5. In areas with very strong signals or with weak signals, in urban or rural settings
To reproduce:
1. Go to S Health application on Gear S
2. Choose an exercise (doesn't matter if its running, walking or biking)
Observed behavior: "Receiving Location" runs without finding location. I allow it to try and find location for up to 10 minutes, again in tethered or stand-alone mode.
Based upon the feedback from the unfortunate souls at Verizon who were forced to try and address this problem, they had not ever seen it or experienced it, and are especially befuddled by the fact that it STILL occurs even upon replacement of the watch and being in the factory default state.
The following are what I've observed in my Gear S watch's S Health application, with "Receiving Location" never finding location in approximately 75% of attempts in using the S Health application, and it reoccurs even when the watch was replaced, and the Gear's operating system and the Gear Manager application were uninstalled and reinstalled, three times. There were additional applications added initially before the symptoms were observed (a watch face and a navigational app), but the system has been cleaned, restored to native state, and the problem still occurs. Of note, the navigational app had no difficulty in finding location (in tethered and stand-alone mode). So this appears to be in the S Health application only.
The problem occurs in tethered (bluetooth) mode and stand-alone mode with equal frequency. I have the Galaxy S6 phone (G920V), with the newest operating system (5.0.2). My partner uses the Samsung Galaxy Edge and this exact same model of watch and has not experienced any of these difficulties. To reiterate - The watch has been replaced by Verizon, kept in its factory default state, and the following problem still occurs:
My setup:
1. Gear model B6DE
2. I have the Galaxy S6 phone (G920V), with the newest operating system (5.0.2), with the latest Gear Manager application
3. Gear working in tethered or stand-alone mode
4. With additional applications added, or in factory default state
5. In areas with very strong signals or with weak signals, in urban or rural settings
To reproduce:
1. Go to S Health application on Gear S
2. Choose an exercise (doesn't matter if its running, walking or biking)
Observed behavior: "Receiving Location" runs without finding location. I allow it to try and find location for up to 10 minutes, again in tethered or stand-alone mode.
Based upon the feedback from the unfortunate souls at Verizon who were forced to try and address this problem, they had not ever seen it or experienced it, and are especially befuddled by the fact that it STILL occurs even upon replacement of the watch and being in the factory default state.