Trailforks Mobile App Feedback & Bugs

PB Forum :: Trailforks Feedback
Trailforks Mobile App Feedback & Bugs
Author Message
Posted: Jun 30, 2020 at 18:10 Quote
Please revise the Dufferin County Forest Main Tract (in Mansfield Ontario) Completionist badge. The 4 following trails have been removed from public visibility & as such riders are unable to find or ride them to achieve badge completion status.

3rd of 21: Connector (Green)
https://www.trailforks.com/trails/connector-101086/

4th of 21: Connector (Blue)
https://www.trailforks.com/trails/connector-100153/

12th of 21: Starter (green)
https://www.trailforks.com/trails/starter-100146/

21st of 21: Thusters (Green)
https://www.trailforks.com/trails/thusters/

Possible Replcements:

-The Lollipop
https://www.trailforks.com/tracker/map/?ping=44.212962,-80.016520

-Trail to Somewhere
https://www.trailforks.com/tracker/map/?ping=44.207994,-80.014345

-Ravine Run
https://www.trailforks.com/tracker/map/?ping=44.210819,-80.037928

-Ken's Extension
https://www.trailforks.com/tracker/map/?ping=44.225626,-80.021889

Thanks in advance

Andre

Posted: Jul 1, 2020 at 16:17 Quote
When I try and pull up driving directions to a parking area on the app when Google Maps launches it pulls up "undefimed, undefined" as the gps coordinates and it glitches out.

Posted: Jul 1, 2020 at 16:42 Quote
Some of the locations do not have coordinates. I noticed that when I was trying to navigate to Mansfield, Ontario. Neither Waze nor Google Maps could get a location. They both threw an error about undefined coordinates.

The only think I can think is the switch to the new map provider has resulted in some locations lacking coordinates.

I had to manually scroll to the navigation tool map to the location closest to where I wanted and hope it got me there.

provin1327 wrote:
When I try and pull up driving directions to a parking area on the app when Google Maps launches it pulls up "undefimed, undefined" as the gps coordinates and it glitches out.

Posted: Jul 1, 2020 at 16:50 Quote
dangaras wrote:
Some of the locations do not have coordinates. I noticed that when I was trying to navigate to Mansfield, Ontario. Neither Waze nor Google Maps could get a location. They both threw an error about undefined coordinates.

The only think I can think is the switch to the new map provider has resulted in some locations lacking coordinates.

I had to manually scroll to the navigation tool map to the location closest to where I wanted and hope it got me there.

provin1327 wrote:
When I try and pull up driving directions to a parking area on the app when Google Maps launches it pulls up "undefimed, undefined" as the gps coordinates and it glitches out.

Yea I just opened Google Maps and dropped a pin where it looked like the parking area on Trailforks was.

Posted: Jul 2, 2020 at 5:51 Quote
provin1327 wrote:
When I try and pull up driving directions to a parking area on the app when Google Maps launches it pulls up "undefimed, undefined" as the gps coordinates and it glitches out.

Works fine for me on iPhone 7 (13.4.1), Trailforks v1.39

Posted: Jul 2, 2020 at 11:31 Quote
With which navigation app, & have you tried one of the parking lots at Mansfield. for eg?

Crapalier wrote:
provin1327 wrote:
When I try and pull up driving directions to a parking area on the app when Google Maps launches it pulls up "undefimed, undefined" as the gps coordinates and it glitches out.

Works fine for me on iPhone 7 (13.4.1), Trailforks v1.39

Posted: Jul 2, 2020 at 21:15 Quote
dangaras wrote:
With which navigation app, & have you tried one of the parking lots at Mansfield. for eg?

Trailforks : Google Maps (defaulted) on clicking "Driving Instructions"


Home to Mansfield trail parking is about 39 hours apparently.

Mod Plus
Posted: Jul 3, 2020 at 9:11 Quote
provin1327 wrote:
When I try and pull up driving directions to a parking area on the app when Google Maps launches it pulls up "undefimed, undefined" as the gps coordinates and it glitches out.

There was a bug just on POI driving directions link in the infoWindow popup. It's now fixed in the update rolling out today.

Posted: Jul 3, 2020 at 12:48 Quote
MrEndo wrote:
I started using Trailforks app on my iPhone 2 weeks ago. All 3 rides which I tried to log stopped logging GPS tracks after less than 20 minutes. The app continued to operate but without GPS, apparently, but my phone was in my Camelbak and I wasn't actively using it (since my hands were on my handlebars). When I unlocked my phone again, the app said it was still going (for 2 hours 8 minutes, for instance), but had only .25 miles of GPS log, not the 8 miles I expected.

What could be wrong that the app just stops track logging? Obviously a position logging app which cannot log your position is not useful at all, so I expect that most people do not have this problem.

I am having this same exact issue. I was using it last year without any issues but now this happens almost every ride. Using an old iPhone SE. I tried all of the suggestions found here : https://www.trailforks.com/help/view/112/ . Nothing worked. Any suggestions?

Posted: Jul 4, 2020 at 19:59 Quote
Lol. U sure Google maps wasn't in Tricycle mode??

Hopefully the fix pushed out today will fix the issue.

Crapalier wrote:
dangaras wrote:
With which navigation app, & have you tried one of the parking lots at Mansfield. for eg?

Trailforks : Google Maps (defaulted) on clicking "Driving Instructions"


Home to Mansfield trail parking is about 39 hours apparently.

Posted: Jul 4, 2020 at 21:19 Quote
dangaras wrote:
Lol. U sure Google maps wasn't in Tricycle mode??

No. BC to Ontario is quite a ways. Done the drive. It sucks.

Posted: Jul 5, 2020 at 11:53 Quote
Crapalier wrote:
dangaras wrote:
Lol. U sure Google maps wasn't in Tricycle mode??

No. BC to Ontario is quite a ways. Done the drive. It sucks.

Lol. Stop at all the bike trails along the way. Makes it more tolerable.

Posted: Jul 7, 2020 at 13:59 Quote
Still having crazy accuracy issues and offshoots. Location allowed all the time, power optimization turned off for app. Pixel 3, android 10, June 5th security patch.

This is way worse than normal for this trail.


This should be on the upper trail, no where near the purple fireroad.

This is a disaster, it jumps into a ravine.

A friends garmin watch looks fine on all these trails. My older ridelogs (i.e. 2019) are way better.

Posted: Jul 7, 2020 at 20:58 Quote
Unfortunately I agree. We, there are 3 of us, are seeing this very sloppy, meandering, tracking that is actually making us not "get" trails we have ridden.

The admins have at least once corrected/adjusted a trail to match my ridelog which didn't match the other 2 riders I was with. They got the trail listed in the ridelog & I didn't.

Strava I hear, is having similar gps issues.

This is difficult to deal with and is probably putting a lot of pressure on the development team. Hopefully this kind of inaccuracy is resolved soon.

eh-steve wrote:
Still having crazy accuracy issues and offshoots. Location allowed all the time, power optimization turned off for app. Pixel 3, android 10, June 5th security patch.

This is way worse than normal for this trail.


This should be on the upper trail, no where near the purple fireroad.

This is a disaster, it jumps into a ravine.

A friends garmin watch looks fine on all these trails. My older ridelogs (i.e. 2019) are way better.

Posted: Jul 8, 2020 at 14:28 Quote
dangaras wrote:
Unfortunately I agree. We, there are 3 of us, are seeing this very sloppy, meandering, tracking that is actually making us not "get" trails we have ridden.

The admins have at least once corrected/adjusted a trail to match my ridelog which didn't match the other 2 riders I was with. They got the trail listed in the ridelog & I didn't.

Strava I hear, is having similar gps issues.

This is difficult to deal with and is probably putting a lot of pressure on the development team. Hopefully this kind of inaccuracy is resolved soon.


Waze as well, apparently. The google forum is quite active with these types of complaints. There is a huge thread called "gps issues after android10 update".

Google pulled the high accuracy option from the settings in android 10 and has prioritized battery life over location accuracy. I'm assuming a lot of apps were battery drains due to pulling location more often than needed.

I haven't looked into it heavily but it looks as though things have changed for developers in android. If you are using a library or framework (like most apps, so you can run on more than one platform) rather than writing and android app directly in Kotilin or Java your hands are somewhat tied (other than figuring it out yourself and create a pull-request.. assuming the library/plugin/framework/platform is open source).

I didn't miss any trails (amazingly) so I'm assuming as a workaround they've made the matching a little more loose. Still sucks as my trail times and distances aren't accurate. I can ride with a friend and my distance is a km short of both his distance and the distance of the ride plan.


 
Your subscriptions
no posts

Copyright © 2000 - 2020. Pinkbike.com. All rights reserved.
dv56 0.009079
Mobile Version of Website