18 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHSpeedo compared to Waze
Leading reported evidence
Replace no significant tire wear
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Leading evidence: 'Replace no significant tire wear' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Replace no significant tire wear' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Test friend�s phone or a friend�s car (and compare)
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Only way know is to test a friend�s phone or a friend�s car (and compare).
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
The issue is that Waze uses a different GPS sensor than Google Maps on the phone.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Since it's using the GPS in the phone this seems to make sense.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
18 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T181445Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Not the normal question. My car has always shown 3 mph over the actual speed when compared to radar-enabled signs. I know that is typical and I know why it's that way. Today I took a trip and the Waze app (based on GPS) mirrored exactly what my speedometer was showing. This was true at low speeds and those over 70 mph. Has anyone else noticed this, or has my speedometer somehow corrected itself? FYI, no work has been done on the car recently.
I've read before that 3 mph over actually is by design. Something about manufacturers facing heavy fines for a speedo ever showing slower than actual speed so they set it higher to cover their ***.
My car's speedo reads 4 over at highway speeds on the radar signs, ie speedo shows 75 radar sign shows 71. Compared to Waze it seems to fluctuate, sometimes Waze shows the "correct" speed when on flat straight sections. I've noticed in hills or on turns that Waze tends to show higher speeds than "correct". Since it's using the GPS in the phone this seems to make sense. The GPS speed is updated once per second, and is probably averaged over several seconds.
I know about the 3 mph differential and why it's there. I'm asking why it STOPPED. No changes, no significant tire wear. In the past my speedometer always showed 3 mph over the actual. Now it's showing exactly the same as Waze.
Yes, the default indicated speed is almost always (if functioning correctly) overestimated by 2% or something like that per engineers. In terms of your Waze et al GPS indicated speed, the error rate is probably due to the sampling rate of your GPS in the phone (i.e. slow).
If you have an external GPS puck like a GoPoint GPS that has a much higher sampling rate, your indicated GPS speed will be more accurate. The slower comparative rate of your phone GPS is also the reason why your distance estimates and turn by burn directions in the navigation aren't precise.
Good question. Maybe try downloading a different GPS app and see what it reports.
It�s either your phone or the car. Only way know is to test a friend�s phone or a friend�s car (and compare).
In the past, the Waze app used to show the actual speed vs the 3 mph cushion of my speedometer. Sampling rate is not the issue because no data point is going to be higher than the actual speed. I guess it just has to remain a mystery.
I do. The issue is that Waze uses a different GPS sensor than Google Maps on the phone. And the polling satellite on Waze is also different than Google because the two different satellites are off by a small amount of mph between them. Once the start of winter is official, Sept 23rd I think, the satellite resync will take place and the issue will likely be resolved.
The only other thing it could be - and I hesitate to say this because it�s unlikely - is that the firmware update on the DME when used with the magnetic oil drain plug causes this electromagnetic interference that causes the GPS signal to miss the update, and therefore, the phone must estimate speed, which is not as accurate.
Did the OP recently install the magnetic oil plug? If so, switch it back to the original and report back.
