Subscription preference

Notification emails are sent to your Samsung account email address.

* Email : anonymous@samsung.com

  

Close

Tizen 3.0.0 update => GPS does not deliver same values?

Forums View
Started by Developer svenrutten , 1130 Seed Dec 17, 2017 15:55 Replies : 7 View : 318 Likes : 0
Hi

After updating my Gear S3 to Tizen 3.0.0, my App is broken. The GPS Api does not get the same values as before. Speed seems to be 4-5 times faster (why?) and there is no altitude value (always null)

Why?

It's a pitty as my customers are getting angry...


Tags

geartizenupdate

Post Reply
Board View
Samsung Developer shihabyasin , 44330 Seed Dec 18, 2017 05:12 Post #1 0
Hi,

Could you please share some your code to check gps behavior?

Thanks.
Post Reply
Board View
Newbie bohemius , 450 Seed Dec 28, 2017 03:42 Post #2 0


This content has been quoted from shihabyasin’s thought.

Hi,

Could you please share some your code to check gps behavior?

Thanks.

I have a same problem, my gps does not return anything, the position object seems to be empty. Worked flawlessly in 2.3.2. Looks like a bug in new implementation.
Code

 this.onCurrentPositionSuccess = function (position) {
            console.log("Got reference position: " + JSON.stringify(position));
            _this.referencePosition = position;
            _this.trackingId = navigator.geolocation.watchPosition(_this.onWatchPositionSuccess, _this.onWatchPositionError, { maximumAge: 60000, enableHighAccuracy: false });
            console.log("Started tracking with watch ID " + _this.trackingId);
            _this.distanceComplication.enable();
            _this.changeSecondsHand();
        };
        this.onCurrentPositionError = function (error) {
            console.log("Error getting current position for reference: " + JSON.stringify(error));
            _this.currentState.hideState();
            _this.currentState = _this.DEFAULT_STATE;
            _this.currentState.renderState();
            _this.changeSecondsHand();
        };
        this.onWatchPositionSuccess = function (position) {
            if (_this.bearingElement.style.display === "none") {
                _this.bearingElement.style.display = "block";
            }
            console.log("Got new position: " + JSON.stringify(position));
            _this.distance = geolib.getDistance(position.coords, _this.referencePosition.coords);
            console.log("Calculated distance: " + _this.distance);
            _this.bearing = geolib.getBearing(position.coords, _this.referencePosition.coords);
            console.log("Calculated bearing: " + _this.bearing);
            _this.bearingElement.style.transform = "rotate(" + _this.bearing + "deg)";
            var cb = _this.onNewDataCbMap.get(_this.currentState.stateElement.id);
            if (cb) {
                cb(_this.distance);
                _this.currentState.renderState();
            }
            _this.distanceComplication.onInterval(_this.distance);
        };
        this.onWatchPositionError = function (error) {
            console.log("Error getting position: " + JSON.stringify(error));
        };


 



Post Reply
Board View
Developer svenrutten , 1130 Seed Jan 01, 2018 11:04 Post #3 0
I am getting some data, but speed is now 3.6x the value I got with 2.3.2, and no altitude available...
Post Reply
Board View
Developer ilya85parshakov , 1490 Seed Jan 09, 2018 08:26 Post #4 0
I'm getting 0.5 star reviews too because of this issue. Thanks Samsung!!

This issue affects only Tizen 3.0.0.1 smartwatches (not Tizen 3.0). navigator.geolocation.watchPosition returns speed in km/h instead of m/s. Altitude is broken.
Here is another topic on this problem: http://developer.samsung.com/forum/board/thread/view.do?boardName=SDK&messageId=339481

Man, this website is the worst website I've ever had a pleasure to use, no wonder Samsung doesn't want Google to index it...






This content has been quoted from svenrutten’s thought.

 

Hi

After updating my Gear S3 to Tizen 3.0.0, my App is broken. The GPS Api does not get the same values as before. Speed seems to be 4-5 times faster (why?) and there is no altitude value (always null)

Why?

It’s a pitty as my customers are getting angry...


 


Post Reply
Board View
Developer svenrutten , 1130 Seed Jan 10, 2018 16:45 Post #5 0
Damn, thats exactly what I found out, they changed from m/s to km/h WITHOUT ANY NOTICE/Changelog!
That's just crazy. And yeah. height/altitud isnt working at all...

If Google or Microsoft is changing something, there is a big changelog... Samsung just changes ...

That's really NOT good at all for us developers...

We need a fix - now!


Post Reply
Board View
Newbie jacques.francoise , 960 Seed Jan 12, 2018 16:14 Post #6 0
I have the same comment in the thread:
GPS position.coords.speed new format in v3.0.0
Could Samsung solve this problem rapidely.
We have unsatisfied customer because of this change.
Post Reply
Board View
Developer svenrutten , 1130 Seed Jan 15, 2018 15:54 Post #7 0
Saaaaamsung!
Post Reply