Could someone confirm this Smart Mute "bug" on 9500ix

[mswlogo]

I noticed a bug in "Smart Mute" on my new 9500ix and confirmed it on 2 other 9500ix units (old and new).

First shut off GPS Filter using the GPS Button.

Now find a solid K alert (no multiples, just single stable frequency) A speed sign on a back road is perfect.

Now approach the sign at a steady speed above 20mph (say 30mph). Be sure you have a solid GPS lock (preferably have speed display on 9500ix).

Now immediately after you get the alert slow down below 20mph (preferably stop) while still well with in alert range.

Notice that as long as you stay below 20mph is will keep alerting indefinitely. It should "Smart Mute". Smart Mute would give a double brap and go silent and continue to show the alert.

What's really annoying is if you have automute on it will not automute either. Unless it automuted before you dropped below 20mph. Once you cross that 20mph boundary. It's stuck. I think it might be stuck on alert level as well.

If you receive another alert on any frequency it will correctly smart mute (this happens a lot with multiple K alerts).

If you try the same test on X Band it will works as advertised.

Note sure what Ka does. I'm told Ka is included in Smart Mute. The detector should be silent anytime you're stopped if you have a GPS lock. Except for short double braps if it sees a new Alert while under 20mph.

I recommend doing this test in Highway mode.

This is a nice feature if you don't trust locking out or autolock. But with this "bug" the feature does not work so well. Since trying to run with GPS Filter off it happens quite a bit. As I approach a busy intersection with a K false I just sit there at the light with it bleeping constantly at full volume. Reminds me of the "other" detector I just sent back . At least my old 8500 would automute.

Running with Manual/Auto-lock on basically masks this "bug". As well as getting multiple alerts later on after you're below 20mph also masks it. It just acts flakey in these situations. But I'm amazed Escort and nobody else has caught it.

I'd be curious too is a 9500ci has the same issue.

I've confirmed it on 3 detectors running standalone and in pairs.

I typically run: Factory + Auto Volume Off, Speed Alert Off, Highway, SPC Mode, Speed on Display.

[Obsidian]

I noticed a bug in "Smart Mute" on my new 9500ix and confirmed it on 2 other 9500ix units (old and new).

First shut off GPS Filter using the GPS Button.

Now find a solid K alert (no multiples, just single stable frequency) A speed sign on a back road is perfect.

Now approach the sign at a steady speed above 20mph (say 30mph). Be sure you have a solid GPS lock (preferably have speed display on 9500ix).

Now immediately after you get the alert slow down below 20mph (preferably stop) while still well with in alert range.

Notice that as long as you stay below 20mph is will keep alerting indefinitely. It should "Smart Mute". Smart Mute would give a double brap and go silent and continue to show the alert.

What's really annoying is if you have automute on it will not automute either. Unless it automuted before you dropped below 20mph. Once you cross that 20mph boundary. It's stuck. I think it might be stuck on alert level as well.

If you receive another alert on any frequency it will correctly smart mute (this happens a lot with multiple K alerts).

If you try the same test on X Band it will works as advertised.

Note sure what Ka does. I'm told Ka is included in Smart Mute. The detector should be silent anytime you're stopped if you have a GPS lock. Except for short double braps if it sees a new Alert while under 20mph.

I recommend doing this test in Highway mode.

This is a nice feature if you don't trust locking out or autolock. But with this "bug" the feature does not work so well. Since trying to run with GPS Filter off it happens quite a bit. As I approach a busy intersection with a K false I just sit there at the light with it bleeping constantly at full volume. Reminds me of the "other" detector I just sent back . At least my old 8500 would automute.

Running with Manual/Auto-lock on basically masks this "bug". As well as getting multiple alerts later on after you're below 20mph also masks it. It just acts flakey in these situations. But I'm amazed Escort and nobody else has caught it.

I'd be curious too is a 9500ci has the same issue.

I've confirmed it on 3 detectors running standalone and in pairs.

I typically run: Factory + Auto Volume Off, Speed Alert Off, Highway, SPC Mode, Speed on Display.

Sounds like a really minor bug ... Escort has some much more important 9500ix issues to work out than this, IMO. Does it mute if you hit the mute button? Easy fix.

[stlcardsfan]

Yes, I've noticed that.

[Obsidian]

The detector should not even SmartMute in highway mode ... the 9500i did not ... I don't really know why they added it to H mode on the 9500ix. Perhaps Escort didn't fully expand SmartMute to the 9500ix for the scenario you described.

99.9% of people are going to use their 9500ix with GPS on though ... so if there are no issues with GPS enabled, then it's pretty much a non-issue.

I always used my 9500ix in Highway mode with AutoMute and never noticed any problems.

[Z1NONLY]

I just had this happen in the parking lot of my last call today. Sometimes I think the ix is running windows...

[mswlogo]

The detector should not even SmartMute in highway mode ... the 9500i did not ... I don't really know why they added it to H mode on the 9500ix. Perhaps Escort didn't fully expand SmartMute to the 9500ix for the scenario you described.

99.9% of people are going to use their 9500ix with GPS on though ... so if there are no issues with GPS enabled, then it's pretty much a non-issue.

I always used my 9500ix in Highway mode with AutoMute and never noticed any problems.

It is annoying if you travel to a new territory.

It's worse than no smart mute at all because it won't automute when it gets stuck like this. I like having smartmute on highway mode. And depending on the actual cause/implications of this "bug" it is may be causing problems that are not so visible.

I think if it worked correctly you'd barely need the lockout feature.

The SmartMute behavior is not even mentioned in the 9500i manual but is in the 9500ix manual under "Audible Alerts".

[Obsidian]

It is annoying if you travel to a new territory.

It's worse than no smart mute at all because it won't automute when it gets stuck like this. I like having smartmute on highway mode. And depending on the actual cause/implications of this "bug" it is may be causing problems that are not so visible.

I can see it being mildly annoying, but you just had a V1 ... how annoying could it really be compared to that?

The SmartMute behavior is not even mentioned in the 9500i manual but is in the 9500ix manual under "Audible Alerts".

It's listed in the product features for the 9500i on Escort's website.

[mswlogo]

By the way if the problem exists on Ka (Harder to test) it would not get masked by GPS lockout.

In an embedded multithreaded, flash memory database environment, a bug that "forgets" about the tracking of an alert can't be good.

And since I'll be in learning mode for a while, it's actually worse than V1 in some instances because it won't automute and I believe it's stuck on alert level too. It's basically giving wrong information. I'm also curious if the alert was removed in this state if it would continue to alert. Because it appears it just completely forgets about the alert until you go over 20mph or get a new alert.

[mswlogo]

Escort confirmed the problem and said a fix would be in the next software update. They also said there is an automute problem fix too but I'm not sure it's related to this issue or not.

So nice to be able to talk to Escort on these forums especially with all the abuse that gets dished out at them. I know a lot of companies would have bailed. Like VR did. I praise them for hanging in there and staying very professional.

[Obsidian]

So nice to be able to talk to Escort on these forums especially with all the abuse that gets dished out at them. I know a lot of companies would have bailed. Like VR did. I praise them for hanging in there and staying very professional.

True that. Mike V could not take the heat.