Updated 360 to 1.6 - crossing my fingers

westwind77

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Dec 7, 2016
Messages
1,777
Reaction score
2,657
Rating - 0%
0   0   0
So, after driving back from PVD the other day with the 360 'singing' constantly I finally decided it was time to update to the latest release this evening..... came over as version 1.6 on my 85x.

Did a straight update all and seemed to go well. Unit automatically reset to standard factory defaults after the update. Update shows as v1.6. I will run this for a few weeks and document/show any K-band encounters as that was my main concern with the update. Wish me luck!
 
Last edited:

6thgear

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
Dec 10, 2017
Messages
223
Reaction score
230
Location
Central FL
Rating - 0%
0   0   0
Looking forward to hearing your feedback! I’m amazed at how well the updated firmware filters BSM/CAS. Currently I do not encounter K band, so I cannot comment/address your underlying concern.

Wishing you a happy outcome!
 

Brainstorm69

TXCTG 2016 MOTY
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
May 23, 2015
Messages
7,787
Reaction score
14,724
Location
Lone Star State
Rating - 0%
0   0   0
So, after driving back from PVD the other day with the 360 'signing' constantly I finally decided it was time to update to the latest release this evening..... came over as version 1.6 on my 85x.

Did a straight update all and seemed to go well. Unit automatically reset to standard factory defaults after the update. Update shows as v1.6. I will run this for a few weeks and document/show any K-band encounters as that was my main concern with the update. Wish me luck!
I wouldn't run it in auto mode....
 

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
Apr 9, 2017
Messages
754
Reaction score
1,118
Location
NH
Rating - 0%
0   0   0
So far the first week with my new M360 (SN:85) running v1.5 has been flawless. No visible or non-visable lockups or sleeping of any kind. Ka 35.5 has been pretty equal to my V1 (3.8952) and EL is working correctly. As you all know I talked a lot trash about the previous versions and the 3 faulty units I had prior, but I am starting to believe v1.5 to be stable. Very curious to see when escort posts the update changes for 1.6. ERF site still hasn't been updated...big surprise.
 

westwind77

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Dec 7, 2016
Messages
1,777
Reaction score
2,657
Rating - 0%
0   0   0
I wouldn't run it in auto mode....
Ha, never!

The 'quickness' against my Bushnell seems to be about the same as 1.2.....however.....I did notice one difference that they addressed/fixed. Quick pulls of the trigger would get it to alert on 1.2, but you would get the 'hollow bars' with audio but no frequency the majority of time. It would need a longer trigger pull to get the colored bars and a frequency.

However, with 1.6 with the quicker pulls it will get the same 'hollow bars' but as it ramps down they fill it with color and the frequency does appear - that never happened with 1.2.

I am feeling 'ok' about the update so far....just have to get some real world encounters to get some idea of how it compares to the prior!

--- DOUBLEPOST MERGED ---

Well.....that did not take long.....K-band lock up with 1.6

I know there was concern over a 'sleeping lock up' with newer firmware so when I would get home I would fire the Bushnell out the window towards the sky to make sure the 360 alerted.

I gave a couple 'too short' pulls with no alerts so gave a longer one, to which it alerted, waited a few seconds and hit it again, full tilt K-band lock up with the 'hollow bars' and no frequency read out.

Unit would change display brightness, mute, etc and powered down normally with the power button - but it was a valid lock up.

Obliviously there is still an issue, even on the newest 1.6 as I could hit this thing over and over on 1.2 and never an issue. I will continue to drive with it to see if I get a 'real world' lock up as well. Oh well. Escort has more work to do!

I have ALL auto-learning OFF as well as ALL databases OFF.
 
Last edited:

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
Apr 9, 2017
Messages
754
Reaction score
1,118
Location
NH
Rating - 0%
0   0   0
Ha, never!

The 'quickness' against my Bushnell seems to be about the same as 1.2.....however.....I did notice one difference that they addressed/fixed. Quick pulls of the trigger would get it to alert on 1.2, but you would get the 'hollow bars' with audio but no frequency the majority of time. It would need a longer trigger pull to get the colored bars and a frequency.

However, with 1.6 with the quicker pulls it will get the same 'hollow bars' but as it ramps down they fill it with color and the frequency does appear - that never happened with 1.2.

I am feeling 'ok' about the update so far....just have to get some real world encounters to get some idea of how it compares to the prior!

--- DOUBLEPOST MERGED ---

Well.....that did not take long.....K-band lock up with 1.6

I know there was concern over a 'sleeping lock up' with newer firmware so when I would get home I would fire the Bushnell out the window towards the sky to make sure the 360 alerted.

I gave a couple 'too short' pulls with no alerts so gave a longer one, to which it alerted, waited a few seconds and hit it again, full tilt K-band lock up with the 'hollow bars' and no frequency read out.

Unit would change display brightness, mute, etc and powered down normally with the power button - but it was a valid lock up.

Obliviously there is still an issue, even on the newest 1.6 as I could hit this thing over and over on 1.2 and never an issue. I will continue to drive with it to see if I get a 'real world' lock up as well. Oh well. Escort has more work to do!

I have ALL auto-learning OFF as well as ALL databases OFF.
Wow I guess I will hold off my update and stay on 1.5. I haven’t had any issues yet and I even drove to the same grocery store that locked up all three of my previous M360’s and still no lockup’s to report with my new one. This whole thing with the lockup’s is very strange. Escort claims if the unit reacts to button clicks it’s not truly locked up. They claim there is an issue with the pilot screen not reverting back and they working on that fix. It doesn’t sound like that’s what you experienced. Was hoping you would have same experience with 1.6... that stinks...
 
Last edited:

westwind77

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Dec 7, 2016
Messages
1,777
Reaction score
2,657
Rating - 0%
0   0   0
Wow I guess I will hold off my update and stay on 1.5. I haven’t had any issues yet and I even drove to the same grocery store that locked up all three of my previous M360’s and still no lockup’s to report with my new one. This whole thing with the lockup’s is very strange. Escort claims if the unit reacts to button clicks it’s not truly locked up. They claim there is an issue with the pilot screen not reverting back and they working on that fix. It doesn’t sound like that’s what you experienced. Was hoping you would have same experience with 1.6... that stinks...
I could understand if the pilot screen still showed the alert display but the audio changed to reflect the actual signal, but that is not the case. The audio and display are both locked. I hit the unit a few more times during the lock up and it would not display a new arrow or anything else. As far as I'm concerned the radar detection function is locked up.

I have yet to pull into a grocery store yet to see how it handles things, but that will be this weekend. Like I said what I did it not 'real world' but then again I figure it should be able to handle a single source pointed away without issues.
 

JeepLibby

Learning to Fly
Beginner User
General User
Newly Registered
Joined
Jul 1, 2018
Messages
50
Reaction score
59
Location
Louisiana
Rating - 0%
0   0   0
I just had a lockup on my 79 Max 360 today running 1.8. Here's how it went down. K band at 24.079 (probably BSM), followed by a Live Ka alert that had been intermittently annoying me on the interstate for a while, and a 24.15x at the rear, which went straight into a ---1--- type of non-stop alerting lockup.

Right now, I'm living with the potential for lockups, a Live screen that reverts to map view (bug), and the overspeed alert bug.
 

InsipidMonkey

Premium Monkey
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Acceptus
Newly Registered
Joined
Mar 22, 2017
Messages
4,897
Reaction score
8,707
Location
New England
Rating - 0%
0   0   0
I just had a lockup on my 79 Max 360 today running 1.8. Here's how it went down. K band at 24.079 (probably BSM), followed by a Live Ka alert that had been intermittently annoying me on the interstate for a while, and a 24.15x at the rear, which went straight into a ---1--- type of non-stop alerting lockup.

Right now, I'm living with the potential for lockups, a Live screen that reverts to map view (bug), and the overspeed alert bug.
Thanks for the report! The best thing you and @westwind77 can do is report it on ERF so they can't keep denying Escort Max detector lockups are an issue. There is no guarantee it will be fixed anytime soon, but at least they won't be able to gloss over the issue so easily.

Please let us know if they offer to update you to the new "diagnostic firmware"!
 

KASHER1979

Administrator
Administrator
Security Attaché
Premium Member
Advanced User
Newly Registered
Joined
Apr 15, 2013
Messages
13,241
Reaction score
10,210
Rating - 100%
2   0   0
Thanks for the report! The best thing you and @westwind77 can do is report it on ERF so they can't keep denying Escort Max detector lockups are an issue. There is no guarantee it will be fixed anytime soon, but at least they won't be able to gloss over the issue so easily.

Please let us know if they offer to update you to the new "diagnostic firmware"!
Yes!!!!!! Report at ERF. Give them all the details. The more people that report it on there the better.
 

westwind77

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Dec 7, 2016
Messages
1,777
Reaction score
2,657
Rating - 0%
0   0   0
Thanks for the report! The best thing you can do is report it on ERF

Please let us know if they offer to update you to the new "diagnostic firmware"!
Yes!!!!!! Report at ERF. Give them all the details. The more people that report it on there the better.
I plan to report it on Monday and tag ER is the post. I will see what (if any) response I receive.

I'm open for running any diagnostic software they offer, however I refuse to send it my unit to obtain it (unless they send me a unit to run during the down time they have my current unit). If I, as a consumer, agree to help them diagnose an issue they are trying to track down and fix (that really is a black eye for them), they should be more than happy to offer me a replacement unit to run. If not, then they are not serious with wanting to fix this issue.

I should be able to get a loaner from Escort as easy as I can from my car dealer!

--- DOUBLEPOST MERGED ---

***Update*** - Escort said my unit is defective and should be sent in for servicing.
 

InsipidMonkey

Premium Monkey
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Acceptus
Newly Registered
Joined
Mar 22, 2017
Messages
4,897
Reaction score
8,707
Location
New England
Rating - 0%
0   0   0
***Update*** - Escort said my unit is defective and should be sent in for servicing.
How many times has this happened since Escort offered a fix? Anyone want to bet there was never a "diagnostic firmware" and it was all just another ruse to buy more time as they parade the pig to market?
 

Duffer5

Learning to Fly
Beginner User
General User
Newly Registered
Joined
Nov 25, 2018
Messages
75
Reaction score
158
Rating - 0%
0   0   0
Please do not do duplicate cross-posting, totally not needed. It smells of post padding. Thank you.
deleted by Duffer5 due to double post. My mistake.
 
Last edited:

westwind77

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Dec 7, 2016
Messages
1,777
Reaction score
2,657
Rating - 0%
0   0   0
Had my 1st road trip with 1.6 today - about 2 hours total on 495 today. Only had 1 BSM false from a Caddy the entire trip, wow, what a difference from 1.2.

I am very please with those results.....however I have yet to have a K band encounter to see how much this new filtering will affect it.

I did have an odd Ka 35.492 today though driving along 495. It alerted with the rear arrow at low strength and I figured one merged on behind me. It went for a short bit then stopped then picked back up but this time from the front....then to the sides, then back then front, but the whole time it was no more than 2 bars, so not a strong signal by any means. I was not in an area with a lot of streets near the highway either. It went on for about a couple miles I would say then stopped. I've never had a signal 'circle me' like that before on the highway. I don't believe any other RD's false in that range, do they? I only had a couple vehicles close and I checked for RD but none were in a place I could see at least.

Then there is the 'sleeping lock up' upon start up issue - but that is in the other thread. If I don't find any LEOs around running K soon I am going to set up my Bushnell in a place I have before and make some passes just to see how it performs.
 

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
Apr 9, 2017
Messages
754
Reaction score
1,118
Location
NH
Rating - 0%
0   0   0
Had my 1st road trip with 1.6 today - about 2 hours total on 495 today. Only had 1 BSM false from a Caddy the entire trip, wow, what a difference from 1.2.

I am very please with those results.....however I have yet to have a K band encounter to see how much this new filtering will affect it.

I did have an odd Ka 35.492 today though driving along 495. It alerted with the rear arrow at low strength and I figured one merged on behind me. It went for a short bit then stopped then picked back up but this time from the front....then to the sides, then back then front, but the whole time it was no more than 2 bars, so not a strong signal by any means. I was not in an area with a lot of streets near the highway either. It went on for about a couple miles I would say then stopped. I've never had a signal 'circle me' like that before on the highway. I don't believe any other RD's false in that range, do they? I only had a couple vehicles close and I checked for RD but none were in a place I could see at least.

Then there is the 'sleeping lock up' upon start up issue - but that is in the other thread. If I don't find any LEOs around running K soon I am going to set up my Bushnell in a place I have before and make some passes just to see how it performs.
I was getting the same alerts on 495 today around 2:30 going north. There was an accident southbound but that trooper on the scene was running 35.501. I had also turned on segment 6 since I was running through MA a lot today but with all the 35.1xx falses I had turn it off. Same issues I was having with my non (c) model last week. Long story short I took my (c) back to Best Buy today. Too much weird crap goes on with these 360’s especially on K band. I just don’t want to deal with it anymore. Picked up another R3 in matte black and will keep my V1 as backup. You really appreciate the solidness of the V1 after using a 360/360c for a few weeks. It’s great Uniden has arrows in its future, I just hope they execute as well as V1. I don’t think it’s as easy as some people may think. Until then the R3 will be my copilot.
 

westwind77

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Dec 7, 2016
Messages
1,777
Reaction score
2,657
Rating - 0%
0   0   0
I was getting the same alerts on 495 today around 2:30 going north. There was an accident southbound but that trooper on the scene was running 35.501. I had also turned on segment 6 since I was running through MA a lot today but with all the 35.1xx falses I had turn it off. Same issues I was having with my non (c) model last week. Long story short I took my (c) back to Best Buy today. Too much weird crap goes on with these 360’s especially on K band. I just don’t want to deal with it anymore. Picked up another R3 in matte black and will keep my V1 as backup. You really appreciate the solidness of the V1 after using a 360/360c for a few weeks. It’s great Uniden has arrows in its future, I just hope they execute as well as V1. I don’t think it’s as easy as some people may think. Until then the R3 will be my copilot.
I was heading 495 south/east right around 3pm - never saw an accident or any leo's in either direction of travel - must of had it cleared by the time I passed. Just a Barnstable Country Sheriff Tahoe cruising past at about +15.

I know you had the issues with the 360 and now the 360c with the odd Ka alerts, is it possible your vehicle is causing these?

If anything I figure if it was your vehicle the R series would be more sensitive and pick it up before the 360 would but who knows, all very strange.
 

Gowski

Premium Member
Premium Member
Intermediate User
Beginner User
General User
Newly Registered
Joined
Apr 9, 2017
Messages
754
Reaction score
1,118
Location
NH
Rating - 0%
0   0   0
I was heading 495 south/east right around 3pm - never saw an accident or any leo's in either direction of travel - must of had it cleared by the time I passed. Just a Barnstable Country Sheriff Tahoe cruising past at about +15.

I know you had the issues with the 360 and now the 360c with the odd Ka alerts, is it possible your vehicle is causing these?

If anything I figure if it was your vehicle the R series would be more sensitive and pick it up before the 360 would but who knows, all very strange.
Nope no sensors on the Benz, and no other detectors I’ve used have had the issue, not even my Max 2. Even when I ran the V1 in ‘A’ mode it was fine. Only the 360’s have had the problem...It’s all very strange, glad I’ve moved on to be honest.
 

JeepLibby

Learning to Fly
Beginner User
General User
Newly Registered
Joined
Jul 1, 2018
Messages
50
Reaction score
59
Location
Louisiana
Rating - 0%
0   0   0
I did have an odd Ka 35.492 today though driving along 495. It alerted with the rear arrow at low strength and I figured one merged on behind me. It went for a short bit then stopped then picked back up but this time from the front....then to the sides, then back then front, but the whole time it was no more than 2 bars, so not a strong signal by any means. I was not in an area with a lot of streets near the highway either. It went on for about a couple miles I would say then stopped. I've never had a signal 'circle me' like that before on the highway. I don't believe any other RD's false in that range, do they? I only had a couple vehicles close and I checked for RD but none were in a place I could see at least.
I've only ever seen an alert circle me in two instances. The first was an off axis detection where the alert started from the rear and switched to the front as the source approached from my right. I think the gas station on the corner was in the way and split it up. The second type has happened a few times when quite close to the source in traffic. The arrows bounce back and forth. Could be the proximity to the source or reflections off other cars in traffic. In your case, it may have been an off axis detection. Have you looked at the map of that location to see if there were actually other roads near the highway? Off axis would explain only 2 bars.
 

westwind77

Premium Member
Premium Member
Advanced User
Intermediate User
Beginner User
General User
Newly Registered
Joined
Dec 7, 2016
Messages
1,777
Reaction score
2,657
Rating - 0%
0   0   0
Well, got my 1st 'real world' lock up today passing by a known weak K false area - really do hope they address this issue - I don't use auto lock out so I am aware of the lock up but I could see those who do for this to be a very troublesome problem.
 

Donation drives

RDF Server & License Fees (Mar 2019) (ACTIVE)

This donation drive covers the server and licensing fees for RDF for the month of March 2019...
Goal
$334.00
Earned
$430.00
This donation drive ends in

Latest threads

Social Group Activity

Forum statistics

Threads
79,105
Messages
1,178,340
Members
18,143
Latest member
Radarious
Top