Related
Hi,
I think I have a problem with GPS on my Oneplus One, it's so hard to lock to my location.
I use Google Maps for navigation (High Accuracy GPS), and it's always showing wrong location, sometimes even far off from my location. And if I look into the status bar, it's always showing "Searching for GPS". I thought it's a problem with Maps so I downloaded Here and Waze, but still the same story, Here and Waze always show wrong location, and Waze also says my GPS is off.
But it's also worth to mention that if I am home, all apps above showing right location. And also I just downloaded GPS Status and test it in my home, it stuck on "Looking for GPS location" message when I'm indoor, but it works when I'm outdoor. Obviously I haven't been outside since I downloaded GPS Status so I'll updated this thread later.
OPO 12.0-YNG1TAS2I3
cliffflip said:
Hi,
I think I have a problem with GPS on my Oneplus One, it's so hard to lock to my location.
I use Google Maps for navigation (High Accuracy GPS), and it's always showing wrong location, sometimes even far off from my location. And if I look into the status bar, it's always showing "Searching for GPS". I thought it's a problem with Maps so I downloaded Here and Waze, but still the same story, Here and Waze always show wrong location, and Waze also says my GPS is off.
But it's also worth to mention that if I am home, all apps above showing right location. And also I just downloaded GPS Status and test it in my home, it stuck on "Looking for GPS location" message when I'm indoor, but it works when I'm outdoor. Obviously I haven't been outside since I downloaded GPS Status so I'll updated this thread later.
OPO 12.0-YNG1TAS2I3
Click to expand...
Click to collapse
You need to be outside for GPS to work, there's no point testing inside because it'll never work.
Heisenberg said:
You need to be outside for GPS to work, there's no point testing inside because it'll never work.
Click to expand...
Click to collapse
Thanks for the info
But it supposed to work inside a moving car right? I tested and compared my OPO with my old Galaxy Tab 2 10" yesterday when I'm going outside. I ran GPS Status & Toolbox on both devices and it's seems like my Galaxy Tab locks position faster and more stable, although showed less total satellites than OPO.
cliffflip said:
Thanks for the info
But it supposed to work inside a moving car right? I tested and compared my OPO with my old Galaxy Tab 2 10" yesterday when I'm going outside. I ran GPS Status & Toolbox on both devices and it's seems like my Galaxy Tab locks position faster and more stable, although showed less total satellites than OPO.
Click to expand...
Click to collapse
Yes OPO gps detection is not so faster
If u have disabled Google play location services and maps app activate them in privacy guard
Go to settings >location > set DEVICE ONLY mode
Keep your Internet on
Place your mobile on flat surface then click on location button
Wait for 1-2min
It will detect
cliffflip said:
Thanks for the info
But it supposed to work inside a moving car right? I tested and compared my OPO with my old Galaxy Tab 2 10" yesterday when I'm going outside. I ran GPS Status & Toolbox on both devices and it's seems like my Galaxy Tab locks position faster and more stable, although showed less total satellites than OPO.
Click to expand...
Click to collapse
Have you tried using Faster GPS from the Play Store?
walpanmad said:
Yes OPO gps detection is not so faster
If u have disabled Google play location services and maps app activate them in privacy guard
Go to settings >location > set DEVICE ONLY mode
Keep your Internet on
Place your mobile on flat surface then click on location button
Wait for 1-2min
It will detect
Click to expand...
Click to collapse
Thanks! Location Service is set to allowed in Privacy Guard.
Heisenberg said:
Have you tried using Faster GPS from the Play Store?
Click to expand...
Click to collapse
No I haven't, will check it ASAP
So I went for my first run with just the watch - no phone. I started the S Health run tracking on the watch as I left. Initially it said it couldn't find location but then this message went away. Throughout the run the location icon on the watch was flashing grey to white. I don't know if this meant actively tracking or trying to find location?
When I came back the data synced over to S-Health on my phone, but there is no map.
I don't know if the distances and speeds have been tracked based on steps and cadence or by GPS?
How is this supposed to work? I presumed the watch GPS data would produce a map when synced with the phone?
It should show you a map in s health. You have to click on the specific run activity though to see it. If it isn't there then maybe GPS wasn't working for some reason. Did it show you the map on the watch in the completed workout summary?
Sent from my Pixel XL using Tapatalk
photojonny said:
So I went for my first run with just the watch - no phone. I started the S Health run tracking on the watch as I left. Initially it said it couldn't find location but then this message went away. Throughout the run the location icon on the watch was flashing grey to white. I don't know if this meant actively tracking or trying to find location?
When I came back the data synced over to S-Health on my phone, but there is no map.
I don't know if the distances and speeds have been tracked based on steps and cadence or by GPS?
How is this supposed to work? I presumed the watch GPS data would produce a map when synced with the phone?
Click to expand...
Click to collapse
I have had this happen with other watches and with a Gear Fit 2. I did a run this morning and had the map show up instantly on my watch at the completion of my run (LTE version). When you have the watch in S Health Run mode and hit the start button you will see a small icon at the top left that looks like a balloon, it is the icon for your GPS. It will be flashing. Once it is always on it means you have a GPS lock. Sounds like you never got a lock.
I recommend 2 things. Go outside with your phone and put the watch in run mode. Watch for the GPS icon, it should lock very fast since you have your phone working with the watch. Now put your phone inside or turn it off so you can try a stand alone test. Put the watch into run mode and see if you get a quicker GPS lock.
Good Luck
cdd543 said:
It should show you a map in s health. You have to click on the specific run activity though to see it. If it isn't there then maybe GPS wasn't working for some reason. Did it show you the map on the watch in the completed workout summary?
Click to expand...
Click to collapse
Thanks. No map, it's appears it failed to get a lock over the whole run.
Bladder61 said:
I have had this happen with other watches and with a Gear Fit 2. I did a run this morning and had the map show up instantly on my watch at the completion of my run (LTE version). When you have the watch in S Health Run mode and hit the start button you will see a small icon at the top left that looks like a balloon, it is the icon for your GPS. It will be flashing. Once it is always on it means you have a GPS lock. Sounds like you never got a lock.
I recommend 2 things. Go outside with your phone and put the watch in run mode. Watch for the GPS icon, it should lock very fast since you have your phone working with the watch. Now put your phone inside or turn it off so you can try a stand alone test. Put the watch into run mode and see if you get a quicker GPS lock.
Good Luck
Click to expand...
Click to collapse
Thanks. I'll try this but a bit concerned it failed to get a lock over the whole run. I hope the GPS chip isn't faulty after the hassle actually getting hold of it.
Edit: I should say I'm in the UK so this is the non LTE version. Don't know if that makes a difference.
I don't think the non LTE has GPS. It would only acquire GPS from your phone.
Sent from my Pixel XL using Tapatalk
cdd543 said:
I don't think the non LTE has GPS. It would only acquire GPS from your phone.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Of course it does.
Fozzee1970 said:
Of course it does.
Click to expand...
Click to collapse
You don't need the phone. But if you have the phone connected, the connection will be faster as it uses the phone for GPS locking
Sent from my SGP521 using XDA-Developers mobile app
Fozzee1970 said:
Of course it does.
Click to expand...
Click to collapse
Yep you're correct. My bad.
Sent from my Pixel XL using Tapatalk
photojonny said:
So I went for my first run with just the watch - no phone. I started the S Health run tracking on the watch as I left. Initially it said it couldn't find location but then this message went away. Throughout the run the location icon on the watch was flashing grey to white. I don't know if this meant actively tracking or trying to find location?
When I came back the data synced over to S-Health on my phone, but there is no map.
I don't know if the distances and speeds have been tracked based on steps and cadence or by GPS?
How is this supposed to work? I presumed the watch GPS data would produce a map when synced with the phone?
Click to expand...
Click to collapse
Check your location settings on your Gear. You should have GPS+ wifi not only wifi.
Sent from my SM-G935F using XDA-Developers mobile app
Bladder61 said:
I have had this happen with other watches and with a Gear Fit 2. I did a run this morning and had the map show up instantly on my watch at the completion of my run (LTE version). When you have the watch in S Health Run mode and hit the start button you will see a small icon at the top left that looks like a balloon, it is the icon for your GPS. It will be flashing. Once it is always on it means you have a GPS lock. Sounds like you never got a lock.
I recommend 2 things. Go outside with your phone and put the watch in run mode. Watch for the GPS icon, it should lock very fast since you have your phone working with the watch. Now put your phone inside or turn it off so you can try a stand alone test. Put the watch into run mode and see if you get a quicker GPS lock.
Good Luck
Click to expand...
Click to collapse
So I've tested this out and either I have a faulty device or the S3 is useless. I repeatedly tried to get a GPS lock on a long walk today - in open countryside with no buildings around and under clear skies. The watch connects instantly when using the phone GPS via bluetooth. When I disconnect bluetooth the watch will not connect on it's own at all despite repeated attempts. It will try for around a minute and then say 'cannot connect, move to a more open area' - this is whilst I'm stood in a field k's from the nearest building under a blue sky.
After the hassle I had getting hold of this I'm tempted just just get a refund, but if this is just a faulty unit and they generally work I guess I'll give one replacement a go - though I suspect I'll be waiting weeks for one.
photojonny said:
So I've tested this out and either I have a faulty device or the S3 is useless. I repeatedly tried to get a GPS lock on a long walk today - in open countryside with no buildings around and under clear skies. The watch connects instantly when using the phone GPS via bluetooth. When I disconnect bluetooth the watch will not connect on it's own at all despite repeated attempts. It will try for around a minute and then say 'cannot connect, move to a more open area' - this is whilst I'm stood in a field k's from the nearest building under a blue sky.
After the hassle I had getting hold of this I'm tempted just just get a refund, but if this is just a faulty unit and they generally work I guess I'll give one replacement a go - though I suspect I'll be waiting weeks for one.
Click to expand...
Click to collapse
I had carried out similar test this evening, the built in GPS worked when the bluetooth of my phone was off.
RayHK said:
I had carried out similar test this evening, the built in GPS worked when the bluetooth of my phone was off.
Click to expand...
Click to collapse
I tried a factory reset and it's now working. I found a thread on a Strava forum where someone had the same problem and switching the watch on and off worked. Must reset the GPS.
It takes around 30-60 secs to get a lock but it has worked since the reset.
photojonny said:
I tried a factory reset and it's now working. I found a thread on a Strava forum where someone had the same problem and switching the watch on and off worked. Must reset the GPS.
It takes around 30-60 secs to get a lock but it has worked since the reset.
Click to expand...
Click to collapse
But if you are going for a run do you just stand there for 30-60 after the 3,2,1 countdown? If so, isn't that going to throw off your average mile times?
awilson181 said:
But if you are going for a run do you just stand there for 30-60 after the 3,2,1 countdown? If so, isn't that going to throw off your average mile times?
Click to expand...
Click to collapse
Yes, a significant design flaw seems to be the inability to get the GPS lock before you start the run as you do with all dedicated running watches. I'm not sure what happens if you start the run then immediately pause it - whether it will continue to try and get the lock. There should be an option to set the lock then start the run. It's far from perfect.
photojonny said:
Yes, a significant design flaw seems to be the inability to get the GPS lock before you start the run as you do with all dedicated running watches. I'm not sure what happens if you start the run then immediately pause it - whether it will continue to try and get the lock. There should be an option to set the lock then start the run. It's far from perfect.
Click to expand...
Click to collapse
Yes definitely not a well thought out design of the software. Did they really test it with someone that actually runs?
It was the major reason I returned my Gear Fit 2 and went with a Garmin. I love my Gear S3, and I di exactly what you mentioned, I start the run program and when it counts down 3,2,1 I immediately hit the pause. I then wait a minute and resume it and make sure I have a locked GPS signal.
I went on too many Gear Fit 2 runs only to get back and find out I didn't have a GPS lock so info was estimated and no map info. Maybe Sammy will do a software update to the run program to fix this. Again, did Sammy have any real runners test the watch and give them feedback?
Bladder61 said:
Yes definitely not a well thought out design of the software. Did they really test it with someone that actually runs?
It was the major reason I returned my Gear Fit 2 and went with a Garmin. I love my Gear S3, and I di exactly what you mentioned, I start the run program and when it counts down 3,2,1 I immediately hit the pause. I then wait a minute and resume it and make sure I have a locked GPS signal.
I went on too many Gear Fit 2 runs only to get back and find out I didn't have a GPS lock so info was estimated and no map info. Maybe Sammy will do a software update to the run program to fix this. Again, did Sammy have any real runners test the watch and give them feedback?
Click to expand...
Click to collapse
Yeah It doesn't seem like they did as it lacks some basic functionality you would expect as a runner. I'm finding pace to be off as much as 20-30 seconds per mile compared to strava. I no longer have my fenix or I'd compare that.
Make sure Location is turned on in the settings
I started a thread on XDA comparing the G3 to my Garmin 620. In addition to the GPS issue, the HR wasn't consistent day to day either. I wasn't as concerned with that as I was the GPS. No way did they have somebody actually run with this watch. The lack of lap/split times in the run summary says it all.
Seems like an easy fix to just disregard that whole countdown timer and take you to the run screen so you can see if/when you get a GPS lock. My Garmin has a little satellite that turns solid when it locks. I'd probably get the watch, again, if they resolved this run issue.
After firmware updated today, the built-in GPS locked within 3 to 4 sec (after the count down) without a phone.
awilson181 said:
I started a thread on XDA comparing the G3 to my Garmin 620. In addition to the GPS issue, the HR wasn't consistent day to day either. I wasn't as concerned with that as I was the GPS. No way did they have somebody actually run with this watch. The lack of lap/split times in the run summary says it all.
Seems like an easy fix to just disregard that whole countdown timer and take you to the run screen so you can see if/when you get a GPS lock. My Garmin has a little satellite that turns solid when it locks. I'd probably get the watch, again, if they resolved this run issue.
Click to expand...
Click to collapse
I'll stick with it for now but it seems 5 mins with an actual runner and some of the problems would have been avoided. How are you supposed to time a race with a 3 2 1 countdown? And does the first part of the run not count whilst it's finding the GPS? If they are going after Garmin's market these are bad oversights.
RayHK said:
After firmware updated today, the built-in GPS locked within 3 to 4 sec (after the count down) without a phone.
Click to expand...
Click to collapse
I saw there is an update out. Haven't been able to push it to my device yet. Hopefully it'll show up soon.
Galaxy Samsung S7
Samsung Gear S3 watch
All updated, no outstanding software updates available.
I having the issue where 8 runs out of 10 S Health just stops tracking my distance.
Steps continue to count
Clock continues to count
The issue seems to happen when either I stop running - i.e. waiting to cross a road or when I pass under a bridge (bridge is probably 3 metres)... the watch seems to drop out. Only way is to stop and restart.
The interesting thing is if I stop and restart it works straight away - so that tells me I am within GPS signal.
The problem seems to be that if it drops out, it never can reconnect and start again. I have ran 7km, it has dropped out after 2km - yet for the rest of the other 5km - your telling me that I was never in GPS signal to pick up again ??
Can someone confirm that if I have my watch connected via Bluetooth, is the S Health app taking GPS from the watch itself or from the phone?
autonm said:
Galaxy Samsung S7
Samsung Gear S3 watch
All updated, no outstanding software updates available.
I having the issue where 8 runs out of 10 S Health just stops tracking my distance.
Steps continue to count
Clock continues to count
The issue seems to happen when either I stop running - i.e. waiting to cross a road or when I pass under a bridge (bridge is probably 3 metres)... the watch seems to drop out. Only way is to stop and restart.
The interesting thing is if I stop and restart it works straight away - so that tells me I am within GPS signal.
The problem seems to be that if it drops out, it never can reconnect and start again. I have ran 7km, it has dropped out after 2km - yet for the rest of the other 5km - your telling me that I was never in GPS signal to pick up again ??
Can someone confirm that if I have my watch connected via Bluetooth, is the S Health app taking GPS from the watch itself or from the phone?
Click to expand...
Click to collapse
-Deleted
I somehow but dialed I response to your post, smh sorry about that.
Sent from my SM-G935T using Tapatalk
gguy1 said:
Esw1122wqb4 vr7 gf miwd21111282rnI e5
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Thanks for that helpful insight !
autonm said:
Thanks for that helpful insight !
Click to expand...
Click to collapse
-Deleted
I somehow but dialed I response to your post, smh sorry about that.
Sent from my SM-G935T using Tapatalk
I have the same issue. I've tried: turning off auto pause, changing type from GPS only, GPS+wireless. I changed distance, adjusted guide, nothing has fixed it. Has been like this since Day 1 for me.
No issues for me. I'm normally tracking with S-Health on the watch and Strava on the phone as S-Health integration into Strava isn't very good.
I thought I read somewhere that when its paired it uses the phone GPS. Try it stand alone and see if it works.
just quick update - I ran 6km + on Sunday - following the same run / trail as I did previous when the S3 bombed out on me. This time I changed the following:
settings - connections - wifi - Off
settings - connections - location - on - methods GPS
It managed to track the entire 6km + without any issues or dropping out. I am running twice again this week and will let you know how it goes...
autonm said:
just quick update - I ran 6km + on Sunday - following the same run / trail as I did previous when the S3 bombed out on me. This time I changed the following:
settings - connections - wifi - Off
settings - connections - location - on - methods GPS
It managed to track the entire 6km + without any issues or dropping out. I am running twice again this week and will let you know how it goes...
Click to expand...
Click to collapse
I'll try that tonight. I had WIFI on.
Wonder if that's the key.
ok so cancel that... had the same settings as Sunday and it failed again tonight after 0.9km
Restarted the tracking again ... failed after 0.2km ... retired again - failed after 0.5km
Something is seriously wrong with the S Health app for tracking..
Next i am going to try a factory restart and see if I can block all notifications from my phone - incase the alerts / pop ups are causing issue....
not good
I have similar issue.
Ok, so I tried the suggested idea of turning off wifi, leaving BT on and GPS only. No change.
I tried turning off wifi, turning off BT. Then using gps and it worked. HOWEVER, it was only 1 test. (Basically watch only)
More testing needed.
Same issue here. Like others, I've tried different combinations of settings (wifi on/off, gps only, auto-pause on/off, etc.). I haven't turned off the Bluetooth connection to the phone, because without notifications, what would be the point - I can buy a dedicated gps watch for less than $50.
However, here are a couple of things I have found that are consistent.
shutting down the gear app on the phone, and restarting it seems to immediately help "location"
doing a reset of the watch, and reconnecting to the phone/app seems to make the s-health record distance consistently and correctly for a few days. HOWEVER, after 3 or 4 days it will stop recording distance during a run. After that, no matter what I do, it is flaky. Sometimes it won't record distance at all, and other times it will record sporadically. After a reset, it will function correctly for 3 or 4 days, and then flake out again.
After reading several threads in several forums, it appears that this is common and Samsung has no response. I really want to like the Gear S3, but this is too much money to spend on a mediocre product.
Samsung Gear S3 works fine, The S-Health app also works fine. The only thing is the working concept is not clearly understood by some people and not well explained by Samsung itself.
If your Samsung Gear S3 has problem tracking your location or distance during cycling or walking activities, here how to solve that:
Condition 1: Your Gear S3 is paired to Phone vie Bluetooth.
In this situation your Gear S3 will rely the location information from your phone.
You do not have to change any setting in your gear S3 ( Bluetooth still on, Wireless on, Location mode GPS & wireless, autopause on)
Make sure your phone Location setting is set to "On" and at "highest accuracy" mode. It means enable all GPS, WiFi and wireless networks for location searching from your phone.
Make sure your phone is not in "Power Saving" mode, because it limits the location tracking ability from your phone.
In this way your gear S3 can track your location, map your distance, and generate the route correctly. Even autopause works correctly and precisely.
Any location tracking faulty in this situation is mostly your phone location tracking faulty.
(You can test your phone tracking problem by running with your phone and S-Health app installed on it separately from your Gear S3)
Condition 2: Your Gear S3 is disconnected from the phone (stand alone)
In case you are not sure your phone can track location correctly in certain condition or you want to save your phone battery, disconnect your Gear from the phone. (Bluetooth Off, Wirelss Off, Location On- GPS & wireless / GPS only, or just simply press flight mode)
In stand alone mode, your Gear S3 will rely on its own GPS.
In this way your gear S3 can track your location, map your distance, and generate the route correctly (without detailed maps). Even autopause works correctly and precisely. The cycling and walking data will be synced to your phone after it is connected again.
Before starting your activity, make sure Gear's GPS has found your location.
At the first time you are using "standalone" mode, Gear may need some time (around 1-3 minutes) for GPS to locate your position. The small location (balloon) icon is blinking when searching and turns solid when it has found your location. Once is done, next time you use standalone GPS mode, it will locate you quickly.
At the first time you are using "standalone" mode after switching from phone connected mode, it's a good practice to restart your watch especially if it takes too long to find your location at first.
I hope this helps. I have tested it consistently on my Gear S3 Frontier, and my phone is Samsung Galaxy S6.
When I selected "Calibrate now" after few seconds show up notification: "Network unavailable"
and next time will show: "Can't get a sea level air pressure reading for your location. Enter manually?"
Data/internet connection working on News, Weather apps. This behavior is same, WiFi or bluetooth connection.
Does anybody have any idea how to fix this bug?
SM-R760
Tizen Version 4.0.0.2
R760XXU2DSA1
deffyplus said:
When I selected "Calibrate now" after few seconds show up notification: "Network unavailable"
and next time will show: "Can't get a sea level air pressure reading for your location. Enter manually?"
Data/internet connection working on News, Weather apps. This behavior is same, WiFi or bluetooth connection.
Does anybody have any idea how to fix this bug?
SM-R760
Tizen Version 4.0.0.2
R760XXU2DSA1
Click to expand...
Click to collapse
Hi,
I had the same issue. Uninstalled the Wear application from phone and installed again.
Bingo..
Hope this helps.
I'm having this issue too. Ive tried reinstalling everything and resetting the watch. Nothing seems to be fixing it. Looking at the reviews of the alt-barometer app in the Samsung store seems to suggest the issue is widespread.
Have the same issue too. I think it's a problem of the defined server in the app which doesn't respond anymore. They should update the app...
Hi, i have exactly same problem after update to tizen 4.0. Have you some solutions?
Same problem , too. Last update 14.2.2019
I have noticed today at my job that I was at 188m, and when it worked I was less than 50m.
Same thing after reinstalling "wear", maybe worst, I didn't had backup
Same problem here after Tizen 4.0.
Same problem. Also affects Hiking Activity in S-Health on the watch. (It can't detect altitude so whole activity is broken showing "0km walked", "--" instead altitude and wrong calories). Tried every combination of reseting watch (with and without backup restore), reinstalling wear app and all plugins on phone and reinstalling altimeter app on watch. Even reflashed firmware via NetOdin. Also tried disabling adblock on phone in case some url gets blocked. No difference).
I'm also starting to think this have to do with predefined altitude server altimeter is contacting being down and not responding.
I had enough fiddling with this but if someone is determined they can try downgrade back to 3.0.0.2 to see if problem persist. Or try debugging the watch to see what is actually happening behind the calibrate request. Maybe even use packet sniffer.
SM-R760
Tizen Version 4.0.0.2
R760XXU2DSA1
BTU (UK) region
It must really be a widespread problem. The same here after the update to Tizen 4.0.2. I have made several hard resets of the watch, the only thing I have not done is phone hard reset. Not going to suffer this not knowing if it helps. I was solving more problems, so I have made several hard resets of the watch. For instance, SOME of the incoming calls were not vibrating on the watch. But after the first hard reset after the update the altimeter started working the second day I think!!! I thought it was really an issue connected with unavailibility of a server somewhere. I was solving more important issues, so I have made other hard resets and since then the altimeter jut won't work...
Same problem after upgrade to Tizen 4. Tommorow i trying downgrade to Tizen 3.
SM-R770
Tizen Version 4.0.0.2
Poland
I had the same problem. After several tries is now working. All I had to do was set the location to "high precision " on my phone (note 8) and after 4-5 times the watch will update automatically. Also I went outside.
I tried today and a get altitude measurement! I turned off and on my location on phone. But... I got lucky only one time. I tried 5 minutes later, and get "network unavailable"... Strange...
Problem
I have the same problem..
agawron91 said:
I tried today and a get altitude measurement! I turned off and on my location on phone. But... I got lucky only one time. I tried 5 minutes later, and get "network unavailable"... Strange...
Click to expand...
Click to collapse
I had the same experience today. At 1 a.m. of our local time (Europe) I got one calibration but since then - nothing. It makes me believe that the problem is not in our watches or phones but on the side of a server somewhere. Were they testing something?
It seems that reinstalling the app would help. I have done it, and for now it's all good
again, network not available , one or two updates and gone again.
Another +1 here - I have just discovered that my S3 Frontier is doing exactly the same thing. Uninstalling the companion app on the phone and reinstalling it hasn't worked for me, the intermittent nature of it (based on previous posts) would suggest some back end network issue at the end of whoever provides that data.
deffyplus said:
When I selected "Calibrate now" after few seconds show up notification: "Network unavailable"
and next time will show: "Can't get a sea level air pressure reading for your location. Enter manually?"
Data/internet connection working on News, Weather apps. This behavior is same, WiFi or bluetooth connection.
Does anybody have any idea how to fix this bug?
SM-R760
Tizen Version 4.0.0.2
R760XXU2DSA1
Click to expand...
Click to collapse
As I posted before, same happened to me the first time after the update to Tizen 4
I had to turn location to high accuracy and had to go outdoors, and after 4-5 tries the altitude is calibrated and working perfectly now. One thing I noticed is that you need to set your phone location on all the time with at least "device only" option.
GOTO_GOSUB said:
Another +1 here - I have just discovered that my S3 Frontier is doing exactly the same thing. Uninstalling the companion app on the phone and reinstalling it hasn't worked for me, the intermittent nature of it (based on previous posts) would suggest some back end network issue at the end of whoever provides that data.
Click to expand...
Click to collapse
Seems that the data is provided by the android location services, not by your data/wifi; in this case you need to have the location on with "device only", seems to solved my problem, BTW I havent noticed more battery drain than using "battery save" mode.
Seems that the data is provided by the android location services, not by your data/wifi; in this case you need to have the location on with "device only", seems to solved my problem, BTW I havent noticed more battery drain than using "battery save" mode.
Click to expand...
Click to collapse
Thanks for this tip - I missed your earlier comment so repeating it here again is useful and does seem to provide a work-around. Have a "Thanks" on me.
Since this is a recent change I wonder if Samsung got their device class confused and are trying to get the watch to aquire a "true" GPS fix rather than using the phone if available, but got it wrong with the latest build so now the watch has acquired a dependency it didn't have before.
My S3 has Wi-fi (but turned off) and no carrier / network (ie mobile phone) support and that used to work perfectly well with my phone's location services set to "High Accuracy" over the Bluetooth link which should surely be enough for any non mission critical consumer device since that uses network location, Wi-fi and GPS. I can see why someone might want a high degree level of accuracy on their watch but then surely the watch should be acquiring GPS itself which is why I wonder if Samsung were trying to be smart and got their wires crossed.
I will check out the battery usage implications of restricting my location to GPS at a later date, but I am mostly indoors and a) don't use the altimeter all that much and b) won't get much of a GPS fix in the concrete and steel bunker that is my office so I am expecting it to be an absolute battery sucker.
Thanks again for the tip about changing the location services on the phone.
GOTO_GOSUB said:
Thanks for this tip - I missed your earlier comment so repeating it here again is useful and does seem to provide a work-around. Have a "Thanks" on me.
Since this is a recent change I wonder if Samsung got their device class confused and are trying to get the watch to aquire a "true" GPS fix rather than using the phone if available, but got it wrong with the latest build so now the watch has acquired a dependency it didn't have before.
My S3 has Wi-fi (but turned off) and no carrier / network (ie mobile phone) support and that used to work perfectly well with my phone's location services set to "High Accuracy" over the Bluetooth link which should surely be enough for any non mission critical consumer device since that uses network location, Wi-fi and GPS. I can see why someone might want a high degree level of accuracy on their watch but then surely the watch should be acquiring GPS itself which is why I wonder if Samsung were trying to be smart and got their wires crossed.
I will check out the battery usage implications of restricting my location to GPS at a later date, but I am mostly indoors and a) don't use the altimeter all that much and b) won't get much of a GPS fix in the concrete and steel bunker that is my office so I am expecting it to be an absolute battery sucker.
Thanks again for the tip about changing the location services on the phone.
Click to expand...
Click to collapse
My S3 is exactly the same as yours, and I dont have wifi or GPS on either, it gets the location straight from the phone, I checked it and when I go to altitude on my watch I can see that the icon of "searching location" goes on in my phone.
I am pretty sure that the GPS of the watch doesnt work by itself because I use it to run everyday (with my phone) and is tracking the metrics and altitude just well, also the location is locked and working, I run 5kms per day and I get 3 and a half days of battery and when I run with the watch alone I can get 1 and a half day (cause GPS and Spotify).
BTW, where I live/work there are no high structures or buildings miles around, maybe it means faster location.
Regards.
I found solution that help me in reddit: "Switch on "location history" in Google account. Should help"
This has been bothering me for a bit now. When using the GPS (Google Maps) Navigation on my phone, the GPS on my GW4C turns on too. If I stop the navigation on my watch, it stops it on my phone! ARGH!
This was never an issue on any of my Tizen watches before. Has anyone come across this too? If so, how did you fix it?
I didn't think Google Maps was option on Tizen watches.
Anyway, this is how you fix. While in the google map app on watch touch the search icon. Then go to settings and then auto-launch. You can choose when watch auto-launches from phone. I have it off for driving and on for walking and cycling.
Sadly, none of Wear OS apps can use location data from the phone. I've tested this using Google Maps, Strava, and my own apps. All of these apps stop working if you disable GPS on the watch, even when the GPS of the connected phone is on. This behavior contradicts the official documentation https://developer.android.com/training/wearables/data/wear-location-detection
On a watch, get location data using the FusedLocationProviderClient. The FLP automatically uses location data from the phone if the watch lacks a GPS sensor.
Click to expand...
Click to collapse
I'd prefer if smartwatch apps used phone's GPS because it's much more accurate and because the battery wouldn't drain as fast on the watch. This was easy to implement on Tizen watches, but seems to be impossible on the Galaxy Watch 4. I've tried both the Fused Location Provider and requestLocationUpdates() methods, but nothing worked.
Does anyone have any suggestions?