yashsingh1/xdaforums huggingface dataset:
[Sony Smartwatch 3] cjkiller:
Not sure whats going on with stopping at 6.4k. Did you pause the app at all? If not then it must of been google play services not updating for some reason. Will look into a way of checking periodically if its working.

Just had a mad couple of updates out. Updated last night, only to create other problems by simply commenting out the wrong bit of code. Long story short woke up to find the app not working just as I was about to go running. Hopefully all working now, note to self: don't update the app after midnight.
[Sony Smartwatch 3] gs05:
Crap...can you issue a new version then as I may have the old one. Otherwise, I took it for a run over the weekend, some more comments:

1. Pace is getting better. Still a little off (too fast) compared to my garmin watch, but its getting better

2. The history screen on the phone shows all the activities in KM with miles as your default unit

3. Perhaps history should be a high level tab to make it easier to find?

4. Can it auto upload to strava? or do an upload all (those not already uploaded) via a one click

5. GPS accuracy is great...nice job. The maps on strava are spot on and without any jaggy lines!

6. Can you have it vibrate the watch every X miles?

7. Are you planning audio cues as well? Would be great.

You should sell the app as a customized GPS running tool to import into various on-line services. I think you will get better traction and people willing to pay for it...just my 2 cents! Plus if you get HRM or other sensor support setup, this is killer.

Thanks again for your support. Nice work
[Sony Smartwatch 3] cjkiller:
I update the first post with the current version (0.68). So you can keep up to date with the version there. You can check in android app settings you have the latest one. If it did not crash then its most likely you have.

Fixed km to miles, cheers.

The history tab needs some work. Before wear the app just had a finish page and did not store anything other than the last ride. So it was just an easy option to put it there. Still unsure what's best.

Auto upload to strava is on the to do list.

Need to sort out some sort of lapping system. I'm thinking of adding an option for adding 1 miles splits, or I guess this could be custom. Then make a screen pop up for 10 seconds or so on each split. This could include a vibrate as well.

The phone app uses the text to speech function on android for audio messages. It does not look like android wear has this feature. So will have to look out for methods for audio but its doubtful for now.

I hear you about a separate app, Ghostracer started as mainly a cycling app so its not been easy to trying to merge the two activities. I could make a much cleaner wear only running app.

Craig
[Sony Smartwatch 3] mertzi:
Woop! I tried Ghostracer standalone today while biking to work and it was way more accurate than My Tracks has been. Would it be possible for some kind of full screen mode? I started My Tracks first just to get the GPS going (to get a more accurate starting position) and My Tracks and Ghostracer constantly fought over the top card position (I don't know what else to call it). Another solution might be a countdown timer you could set to e.g. 15-20 seconds so Ghostracer has time to find a reliable lock position before starting the activity, that way you wouldn't need to open My Tracks at all.
[Sony Smartwatch 3] gs05:
Open the app, wait until the "no GPS" on the top left is replaced by numbers. You then have a lock and can hit start.

---------- Post added at 11:05 PM ---------- Previous post was at 10:54 PM ----------

Craig,

Went for a long run today and some more comments

1. Your app says 6.7 miles, but strava has it as 6.9 miles? Strava time is 57:09 and your time is 56:55. Does it use a different method or something? Odd that it varies by that much

2. Can we have the distance in 0.01 units instead of 0.1?

3. When you go to another app, then go back via the "show stats" it should go right to the stats screen and not to the pause screen

4. Pace as I mentioned before seems to vary too much. The average pace is spot on now (great!), but pace seems to go down to 5:46 up to 11:45 and I am pretty much going the same speed on a flat surface. May have something to do with the averaging logic.

5. When going into history uploading file, then hitting back it shows the run, but not the upload icon. Could be because the screen does not refresh with back (not sure), so this may not be a bug

6. Time on the history page is wrong. I ran between 3:15 and 4:15, but the time says 20:20

7. You should replace the "No GPS" with "GPS Lock" or something when its found (with the numbers after). Even the previous user didn't realize what this means...its a great feature could be more user friendly

8. Wonder if the button on the side can be used to pause/start? May not be a Google editable feature

Again...loving the app. Thanks and here to help as needed!

Greg
[Sony Smartwatch 3] dave_id87:
not sure if its android or ghostracer but it takes FOREVER to get a gps lock now and it is never full bars. Odd, it worked perfectly a while back
[Sony Smartwatch 3] tibinet:
I just downloaded the app today. The GPS doesn't work at all. In the watch settings I allowed the GPS, at mobile I set up to force using the watch GPS, but even after half an hour the GPS wasn't connected... I tried it outside, clean sky. Is it by this latest version?

I also registered as a beta tester. How I will get the beta release? Through the Play store?
[Sony Smartwatch 3] dsenseb:
Hi, just bought myself the SW3 with the paid version of GR. I did a test run today and most things i got sorted out. Only the offline gps is not working, only when synced to the phone. I see in above reactions that i'm not the only one. The only reason i got the watch and GR is for this function so i hope there will be a sollution.

Thanks in advance
[Sony Smartwatch 3] ColonelRunner:
GPS signal on the SM3 using GR standalone is still very bad.

It takes forever to get a signal and it drops very quickly.

I had no problems weeks ago on previous versions of GR.

Any tips from the developpers would be appreciated, please.

Thank You.
[Sony Smartwatch 3] scaltro:
I'm wondering if you tried and verified if Ghostracer supports the BT cadence sensors for bike when using the app as standalone on the Sony SmartWatch 3... The idea is to get rid of the phone while biking and use the watch as collector for all the BT sensors (hearth rate, cadence and speed)
[Sony Smartwatch 3] sirrelevant:
tl;dr: no

AFAIK android wear so far has two bluetooth profiles implemented: A2DP for audio, and HRP for heart rate. That sensor needs the CSCP profile.

Maybe there's new stuff in the 5.1 firmware? Google didn't bother to announce when they added HRP, so who knows.
[Sony Smartwatch 3] dustyatxda:
I joined the beta testers and purchased the full version of the app shortly after. It used to be the best app for SW3. The watch GPS signal strength visible before you start the run is the killer feature of this app together with activity upload to other apps. Standalone watch GPS used to work flawlessly, it rarely took me more than a minute to get the full signal.

With last two or three updates however, the GPS is extremely unpredictable.

It takes forever to find the GPS signal with clear sky and no buildings around. IF it eventually finds signal after some watch or app restart plus some location disable / enable woodoo, it seems to keep the signal just fine (based on the few occasions when it actually got the signal).

However the inability to predict how long till the signal is locked (if ever) makes the app unusable.

Not sure what is wrong. The option to use watch GPS is selected and no other settings changed comparing to the time when it was working in the old version.

Factory reset and app reinstall did not fix anything. Developer feedback would be highly appreciated. If there is an old APK available somewhere, we would at least be able to test if the last few updates are the culprit.
[Sony Smartwatch 3] sirrelevant:
Craig is very active in the google group

https://plus.google.com/communities/108600094791246159447
[Sony Smartwatch 3] oliverr871:
GPS is broken in latest build. It takes a long time to get a lock. When I start a run before the lock, it used to instantly start showing my pace and how fast I am going in MPH. Now it just stays 0 until 30 min. later and it's still not accurate. Please fix this.
[Sony Smartwatch 3] ppcoban:
Regarding GPS problem and my experience so far.

Hopefully a possible insight for programmer to.

I used GhostRacer 0.85 beta for something like 1-1.5 weeks on Smartwatch 3 in stand-alone mode. Paid version.

It was first version that I installed and Smartwatch Android is 5.0.2 from the 1st day I received it (same period).

Paired it with Mio Fuse HRM, synced audiobooks trough walkman app, bluetooth earbuds...

Loged 5-8 runs and never had a problem.

GPS was pretty accurate. Music played without problems in background. Synced my completed runs with RunKeeper.

It was more than great. Perfect running watch (-battery time :) ).

Things that changed:

1st I upgraded firmware on my Z1 compact to Lollipop official. And same day GhostRacer to 0.86

Went for a run, GhostRacer stoped recording after 2.7 something km. Restarted watch, started GhostRacer again it stoped again at 1.3km or something.

Afterwards used Titanium Backup and restored GhostRacer to 0.85 again.

Restarted Watch(reset)...resynced apps took test Bike ride for 6km (HRM connected but not shown on watch screen, very slow ride, with pauses and resumes, shopping..., ... 1:30h) all went well.

Accurate GPS tracking on map. All ok.

Next run GhostRacer stoped at 3km and something. (HRM connected, version 0.85 that worked so far flawlessly!)

.

Tantrum (...and running simultaneously. 8km later nothing changed...)

.

The only thing that I changed beside phones firmware are panels on my watch.

On 1st screen I have:

Time,24h watch

distance,heart-rate

pace,cadence

where I didn't use heart-rate data (looked at Mio fuse instead), and cadence data (but was shown on second screen that i hardly ever flipped) throughout the time that everything worked great.

Hm...and for the last 2 runs that crashed I didn't use headphones.

So anyone any idea?
[Sony Smartwatch 3] gs05:
It is google services...it is messing up the GPS lock. It is a problem for all of the GPS applications and not just for Ghostracer, so lets not jump on the dev for doing something wrong.

Google updated the services element recently and it has caused the watch to be a bit lackluster for GPS. However, it seems (at least for me) the locking issue has gone away over the past few days and now it locks within 5-10 seconds as expected.
[Sony Smartwatch 3] sketron13:
Same issues as everyone else over the past few weeks, used to work perfect. Interesting comment on the Google services, as I've had some weird Google services messages on the watch today and yesterday. Now that I think about it, I ended up having to wipe the watch once this happened since it wouldn't connect to the phone anymore.
[Sony Smartwatch 3] ppcoban:
Hello, t'smi again :)

Went yesterday for a test walk/run 5km cca 1h(kind a resting day). with skies dark as they can get and some rain too.

On sole purpose to have as bad GPS signal as it gets.

Ran trough wood area with heavy green foliage. Even went indoor and out again just to mess the GPS.

Didn't have success. :)

In other words GostRacer behaved as great as in good old times (few days ago up until that Lollipop(phone) / 0.86 update combo and that 2 runs in the row that stuck)

What I changed this time:

-Instaled 0.861 version

-H7 HRM instead of Mio fuse

-changed panels on watch (removed cadence to second screen looked at it 1-3 times during activity. Yup it's my superstition trouble candidate :))

I agree that it could be Google services and probably is. Didn't want to offend dev, just sort few

things I tried in case there might be a simple glitch.

Still think that GostRacer is the only thing that keeps me from giving up on my SW3 and buying dedicated running watch.

Anyway will test further.
[Sony Smartwatch 3] sketron13:
Okay, app worked mostly great yesterday. Distance was recorded to 3.8 miles, then the next 0.7 didn't get registered.

Maybe related, the music I had playing to my BT headphones quit and the Walkman app did the weird behavior it did while the GPS was hexing this same issue a few weeks ago. The music will play when you touch play then stop after a couple seconds, still showing on the screen as still playing. When you push pause on the screen (screen shows as playing), the app kicks you to home screen, swipe up and the song is stopped at the beginning.

Maybe Google still hasn't got something together in wear. The Bluetooth weirdness sounds more like a Sony software issue.
[Sony Smartwatch 3] jim_7_9:
I have same problem as some here has. I use last GR version.

GPS always has problem recording around 6th km and then stops when i reach about 7th km. Every version of Ghostracer i used has the same behavior.

Walkman music also stops in the middle of the run with no reason.

It's frustrating because that app has so much potential, but its useless if data is wrong :(
[Sony Smartwatch 3] ppcoban:
Ok, all went ok today

Went for a run:

Ghostrace 0.862

No headphones and music

Polar H7 hrm

Watch charged to 100%.

Not connected to phone.

Wetter, partly cloudy. GPS lock at 1 line. 80% open road 20% park with lots of trees. No problem there.

Track doesn't lock erratic on map so the gps tracking was good as usual.

At 14.5Km battery died. (cca1.30h) :(

But! No problem Ghostracer recorded everything up until then. Had no problem syncing once watch charged again.

Question for jim_7_9 did you wait for GPS lock before starting a run(how many lines)? Might be that I didn't wait for lock 2 times that it stopped measuring distance mid run for me.

Question for everyone else: How long a distance / time did you manage to record using sw3. Somehow I always thought it would be something like 3h with HRM connected. 1h30 seems a little bit strange to me. Waited this morning extra just to have it charged to 100%...
[Sony Smartwatch 3] Basch88:
Ran 50min today with HRM, battery went from 100% to 67%. So theoretically should last up to 2.30h
[Sony Smartwatch 3] jim_7_9:
Yes, i always wait and get 2 to 4 bars, depending of the day.
[Sony Smartwatch 3] jerrytlr:
api error again...

Hi all I have been using Ghostracer for many weeks now without issue but last weekend I just get the 'Google api failed play service needs updating error'. Any ideas re how to get it working again? I have the latest version of the Ghostracer app, have resynced apps, and restarted the watch but still not working - help!

The app is amazing when it works

Cheers

Jerry
[Sony Smartwatch 3] sketron13:
I described the same thing on post 192, factory reset is the only thing that worked for me
[Sony Smartwatch 3] ppcoban:
Quick bike ride to work this morning, cca 9-10km.

Latest Ghostracer

HRM connected (Mio Fuse)

No bluetooth headphones

Waited for lock (4 lines, very nice weather), open road 100%

10km fast ride.

It stuck on 1.88km and didn't register distance any more!

Other than activity type and HRM device nothing changed from last time.
[Sony Smartwatch 3] applesandsynths:
Issue with time/km/pc not matching up

Hey guys,

Quick question, I just tried out Ghostracer for the first time on my SW3 and was very impressed. Everything worked great until I went to sync my data to Runkeeper. In Ghostracer, I posted a 7.02km run, 34:59 for time, and pace 4:58/km.

In Runkeeper, It shows as 7.02, 39:34, 5:38/km. Has anyone seen this happen or know how to fix it? I've noticed before when trying trying to export/import .gpx files between Runkeeper and Runtastic that this very same thing happens with all my numbers being different. I don't get it.

In this instance, I tried exporting the gpx to Runtastic as well, and that site also showed my time as being 39:34 instead of Ghostracer's 34:59. Importing the gpx into Ghostracer as a Ghost file also yielded the same 39:34 result.

I'm wondering if me pausing Ghostracer on my watch a couple times on my run would have caused this issue? Anyone know if the accumulated pause time for some reason gets tacked onto the gpx file?

Thanks in advance
[Sony Smartwatch 3] Ironic6925:
Really great app! Makes me even more happy with my SW3! Just bought the app yesterday in the playstore after being highly recommended to me here. I am using the GPS of my phone because I alway take my phone with me when I am running (just in case) but being able to see my times and distance on my SW3 is very handy! Syncing with Runkeeper (my former running-app) also works great.

Thanks for your hard work and keep it up! If you could add a option that makes my watch vibrate every km, that would be awesome!
[Sony Smartwatch 3] sketron13:
Hasn't worked for a month, took off wrist and worked perfect...

So I've been having the usual Ghostracer/Google/whatever app trying to use standalone GPS issues as everyone else. This went on for roughly a month now, with most runs not recorded or only a fraction is recorded. Always run with SW3 - Motorola BT headphones - Mio HRM and usual use Ghostracer, but have tried all others simultaneously and alone, all with comparable results.

So I'm running yesterday and the first 2 miles is not recorded (no surprise). I thought "I'll at least get my HR data and figure out how to extract it from the exported file," and take the watch off. I turn on Wear GPS to see the signal. It slowly gets better. I've used this app lately to see what's going on, and it seems when the watch is on my wrist the GPS signal is lost. Holding it in my hand I started to run again. It recorded the last 2 miles flawlessly...

Hardware issue? Anyone else seeing this?

I'm going on a run in a little bit, will try to repeat and see how it does. It's a cloudy day, so worst case scenario.
[Sony Smartwatch 3] ColonelRunner:
I had a 10km run this morning (sunny day) and it only recorded 2,40km... whereas yesterday it recorded 9,64km (cloudy day)... just the first 350m were missing because i had no GPS signal on my SW3.

It's getting annoying there is still no fix available from Google / Android Wear / whatever.

Months ago it took only a few seconds to get a solid gps signal, now it takes forever, and most of time it stops recording after a while.

I will try tomorrow the "Wear GPS Statut" app before my running session and see what happens (never tried it before).
[Sony Smartwatch 3] sketron13:
Okay held the watch instead of wearing it on my wrist, just like yesterday. The sky had black clouds and there was a tornado warning, so GPS is worst case scenario.

The watch records the run flawlessly. You can even see how I was on the sidewalk on one side of the street, then crossed to the other side.

Looking at Wear GPS before my run, when the watch was on my wrist, I got no signal. This was even walking out into a culdesac. Took it off and the signal was great.

WTF Sony?!? I think it's a hardware design issue. That would explain why it affects some and not others. Maybe has something to do with how much you sweat (I sweat tremendously). I've never had good luck with a device that has a flap over a micro USB port, crapped out over a dozen BT headphones from this no matter how careful.
[Sony Smartwatch 3] ColonelRunner:
Thank you for your feedback, i'm gonna run today, so i will try to hold the watch in my hand instead of my wrist, and see how it goes.
[Sony Smartwatch 3] jwelch010:
I use a wrist band under my watch with no issues.

Also have had many issues with Bluetooth headphones dying on me. Right now I'm going for a record with the Jabra Pulse headphones. 7 months with no issues (also has a very precise heart rate monitor built in). Bought the extended warranty through Best Buy for like $25 just in case.
[Sony Smartwatch 3] ColonelRunner:
Back from a 12km run. Well, everything was ok this time...

- Watch battery 100%. Dropped to 65% at the end of the run, with HRM On (Runtastic Combo Bluetooth belt)

- Cloudy day

- I opened first "Wear GPS Statuts" on my SW3, it took only a few seconds to catch between 13 and 17 satellites in my street.

- I opened Ghostracer (standalone) on my SW3 and i immediatly had 2 or 3 bars.

- The whole distance was recorded, BUT it stopped refreshing distance when i was in a park with a lot of trees. Indeed, as soon as i got out of the park, the distance which was stuck to 5,29km went to 6,16km... so it catched up the un-recorded distance.

I think the SW3 GPS is "lazy", so just open "Wear GPS Statuts" on your watch, it seems to force and "stress" the watch to connect to satellites, and get a quicker GPS signal on Ghostracer.

Ah, and i tried holding the watch in my hand, to see if it finds more satellites, there was no real difference.
[Sony Smartwatch 3] sketron13:
Another flawless recording of my run, almost 5 quick miles with 3 short walks of a minute or two. Holding the watch by the sides of the band, Wear GPS is showing many satellites with good signals. Immediately after I put it on my arm, the numbers at the bottom drop to read 0-0-0 or 0-0-1. I'm sure each one of these isn't going to have the same issues/solutions, this is just what is working for me.
[Sony Smartwatch 3] andy905:
Could you upload a screenshot of the track
[Sony Smartwatch 3] ppcoban:
Upgraded phone to new firmware a week ago.

Upgraded SW3 to new firmware (5.1.1) wanted to to go for a test run.

Installed ghostracer again.

Now having a new problem.

On starting app on phone I get following message: Problem setting up in-app billing: IabResult: Billing service unavailable on device. (response: 3:Billing Unavailable)

If I go to settings and try to setup watch face again app crashes.

App was purchased and I'm beta tester. Any idea what to do?
[Sony Smartwatch 3] sketron13:
Here's the run from yesterday.
[Sony Smartwatch 3] sketron13:
Here's the run from an hour ago.
[Sony Smartwatch 3] ppcoban:
Yey

First run after 5.1.1. update, and a first run in a long while that was 100% OK.

5K, HRM, no headphone. Partly cloudy.
[Sony Smartwatch 3] ColonelRunner:
My last run (yesterday) was completely f***ed.

Ghostracer stopped recording distance all the time, and hardly got back.

And sometimes it works perfectly. I really don't understand what's going on.
[Sony Smartwatch 3] ColonelRunner:
My SW3 just updated to a newest version. I will try it out tuesday and let you know about GPS issues.
[Sony Smartwatch 3] dougi83:
No problem for me, always using the SW3 built-in GPS.

When running or bike riding, everytime it's recording perfectly.

Upload to strava works perfectly.

(Running with SW3 only ie, not connected to an HRM or BT headset)

(Last version of the SW3 firmware 5.1.1 and GhostRacer app)

The only problem is with Ghost functionnality. The virtual "Start Line" is not always recognized, and the current run is not compared to the ghost in watch memory.
[Sony Smartwatch 3] Orc7:
Please add app support old HxM BT - Zephyr with bluetooth 2.0 version
[Sony Smartwatch 3] mertzi:
Today I couldn't upload to Runkeeper nor Strava. It gives new an error saying "errorThe file is empty," and then an html link command to Strava.zendesk something something. I see all the data for the run in the Ghostracer app so it is not empty.

Edit: my bad, didn't have the latest version of Ghostracer.

---------- Post added at 10:29 PM ---------- Previous post was at 10:14 PM ----------

Today I used the ghost function for the first time to get vibrations every 1k. Could we get the option to disable the info popup and only get vibration? Keep up the good work.
[Sony Smartwatch 3] ColonelRunner:
Since last SW3 update, GR seems to work pretty good.

Just had a 8km run and it recorded everything. I hope the GPS issues are sorted now.