-
• #1802
No I won't. All my devices work perfectly well.
I wasn't talking to you.
-
• #1803
Why did you quote me then?
Anyway if he can download Strava then it will work. Stop trying to get lock indoors..
-
• #1804
Because you seemed to be suggesting that if SamJT just stood there long enough his Android handset would work, which is not the case- a number of Android phones won't work with Strava.
Hence, you can stand there as long as you want, and unless a passer by gives you a new phone, you are not going to get Strava to work.
-
• #1805
Yes I am. Because the Galaxy S2 works with Strava and that is the device he has.
Try reading his posts.
-
• #1806
^^I thought Strava was in the business of getting people to work, not the other way around.
-
• #1807
Yes I am. Because the Galaxy S2 works with Strava and that is the device he has.
Try reading his posts.
So he's lying?
-
• #1808
To us, to his friends and loved ones, and most saliently to himself.
-
• #1809
The S2 is known to work with Strava so my suggestion to wait longer for the GPS lock remains valid.
No one mentioned lying except you.
-
• #1810
Well, as you are an IT professional I will accept that "waiting until it starts working" is the first choice when attempting to fix a technical problem.
-
• #1811
Well as you are an IT salesman I will accept that you probably didn't bother trying to solve the problem.
-
• #1812
I usually start it and it gets a lock within 300m or so
Maybe you've found the solution.. say.. something like standing still outside until it gets a GPS lock... ;)
I'm here all day, try the veal.
-
• #1813
Well, as you are an IT professional I will accept that "waiting until it starts working" is the first choice when attempting to fix a technical problem.
This is an accurate description of my professional approach to programming.
-
• #1814
Maybe you've found the solution.. say.. something like standing still outside until it gets a GPS lock... ;)
I'm here all day, try the veal.
That's terrible performance for a modern smartphone though- clearly either the phone is crap or something is wrong with it, or both.
-
• #1815
Bollocks. He's said it's worked previously within 300m of running. You have no idea of the satellite positions, atmospheric conditions or tree cover, etc on his run course at the time.
You can quit digging your hole any time you want. -
• #1816
Ok, he might be starting running in an underground carpark, or in a mine, or maybe he wears a very large lead hat.
You're talking bollocks, not me- a modern smartphone should have GPS lock pretty much as soon as you get it out of your pocket.
Mine does, and it's hardly a DARPA experimental prototype.
-
• #1817
Bollocks.
Once again, no consideration for where the phone was started or the location and number of sats available. Go and have a read about Assisted GPS.
For what it's worth I start mine underground and it works fine as far as I know but I don't examine the output with a fine tooth comb.
-
• #1818
Ok, SamJT- where are you?
If he's anywhere in London, or the South of England pretty much, you can apologise.
If he's in the middle of Lapland or similar then I'll say sorry.
-
• #1819
I was thinking about how segments are declared unsafe...
if someone gets KOM and then declares it unsafe it's their segment forever... I maybe falsely accusing but I feel some safe segments have been flagged and this might be a reason?
Sorry is this has already been covered
-
• #1820
If a segment is reported then there isn't a Leaderboard or kom
-
• #1821
If a tree falls in the forest but no-one is there to hear it why do you care?
-
• #1822
If a segment is reported then there isn't a Leaderboard or kom
Not true. I am the KOM of an unsafe segment that is still listed in my KOMs. Not that this is something to be proud of, as it is rightly flagged as unsafe.
-
• #1823
If a tree falls in the forest but no-one is there to hear it why do you care?
That depends - What Watts/Kg is it putting out?
-
• #1824
Also there is a report abuse option on the segments page, just after where it says unsafe blah blah blah
-
• #1825
Wow, this has kicked off a bit!
I've started around 20 runs/rides from the Kingston area (wide open space, no lead helmets, no reindeers) and every time I've been fine locking onto a signal within about a minute of starting my strava activity (I tend not to wait for it to locate because every time it has worked fine after a minute delay or so), this equates to around 300m of running, or a km on the bike, whatever. Anyway a week ago within a couple of days, it hasn't picked up a signal at any point. And having not experienced any issues before, me and a couple of friends (andriod users) have all been hit with the same thing at the same time (2 of them have had the same issue but in sheffield (possibly a worse signal)).
Essentially I thought it might be an android specific update or something which caused it, because two other friends with iphones, in the same area doing the same activity, had no problems and locked on within about 10 seconds.
In summary... bit annoying. Use a garmin edge 500 now on my bike, probably could use it on the runs as well.
massive sigh
Yeah I ran 5k yesterday and it didn't pick up a signal at all, I know it's better if you stay still but I usually start it and it gets a lock within 300m or so