iOS: ETA wildly off when following a GPX track (73 hrs for 179 mi), while a Pixel shows 2 h 43 min with the same file
▲ 2 r/OsmAnd

iOS: ETA wildly off when following a GPX track (73 hrs for 179 mi), while a Pixel shows 2 h 43 min with the same file

On my iPhone, following a GPX track in Car profile gives 73 h 29 min for 179 miles. That's about 2.4 mph, basically walking speed. Screenshot attached.

A Pixel using the same GPX file shows 2 h 43 min, so the file itself seems fine and the problem looks specific to my app's settings. That said, the Pixel's 66 mph average also seems optimistic for a back-roads loop. So I'm curious what actually drives the estimate when following a track.

Questions:

  1. Is there a setting that controls how remaining time and ETA are calculated for a followed track, such as a default speed in the profile?
  2. Does attaching the track to roads switch the estimate to real road speeds?
  3. What settings should I compare between the two phones?
u/DiverAllen — 6 days ago
▲ 7 r/OsmAnd

OsmAnd on Android Auto: Map mode (Day/Night) won't stick? Look for the Apply button while parked

I was having trouble getting OsmAnd's Map mode to stay set to Day or Night on my Android Auto car screen, and figured out what was going on. Posting in case it saves someone else the head-scratching.

The problem: While driving, I'd open OsmAnd's Map mode menu on the car screen and change it from Automatic to Day or Night. The only way out of the menu was the back arrow in the upper left. When I backed out, it reverted to Automatic every time.

What was actually happening: When I tried the same menu with the car parked, there was an Apply button in the upper right that I'd never seen before. Tapping Apply saved the setting and it stuck. My best guess is that Android Auto hides some controls while the car is moving, so the Apply button wasn't there while driving, and backing out with the arrow cancelled the change.

Two ways to set it:

  1. On the car screen, while parked: change Map mode and tap Apply.
  2. From the phone, anytime: open Settings, search for "Android Auto," and find Day/night mode for maps. This switches the car screen's day/night appearance. Note that OsmAnd's own Map mode button may still show "Automatic" when you do it this way, but the display follows the Android Auto setting.

Hope this helps someone.

reddit.com
u/DiverAllen — 7 days ago

OneNote search is still garbage on Android — cache clear + account re-add did nothing

Mature product, mature platform, and search still can't find stuff that's right there.

Running the OneNote app on a Pixel 11 Pro, latest version (auto-updates, so no version-mismatch guesses please). Cleared the cache, wiped the app data, re-added my M365 account so it'd supposedly reindex. Nothing. Search still comes up empty for content I know exists — I can pull up the exact same note in two seconds on OneNote for Windows desktop, but on Android it's a ghost.

I've read the troubleshooting docs. I've done the "turn it off and on again" ritual. At what point does this just get admitted as broken instead of something we're supposed to work around forever?

Anyone on Android actually fixed this, or is this just OneNote being OneNote?

reddit.com
u/DiverAllen — 1 month ago

I'm new to OsmAnd and interested in using it for navigation on auto road rallies. I recently planned a route using the rubber-band method to trace a path along specific roads. During the drive I observed two unexpected navigation behaviors. The first was a notification in the upper-left area of the screen indicating an upcoming turn, with a short yellow line — maybe 100 feet — appearing perpendicular to the route. There was no road at that location. At a separate point, while traveling on a highway, the same area displayed a U-turn graphic, even though the route on screen showed no reversal of course. After uploading my .gpx file to gpx.studio, I noticed it contained two tracks. One was the road-snapped path I intended; the other consisted of straight connecting lines, which appear to represent the raw click points from the rubber-banding process. My suspicion is that the presence of the straight-line track produced the phantom turn instructions I observed. Has anyone run into this, and is there a recommended way to remove or prevent the straight-line track from being included in the export?

Update: I've since created a revised .gpx file with the straight-line track removed. I'm planning to redrive the route to confirm whether this resolves the issue — will report back.

reddit.com
u/DiverAllen — 6 months ago