BCDx36HP Firmware 1.20.00 Available

[u2brent]

nobody is forcing anybody to do anything (Or listen to anything) they don't want too or maybe they just don't understand. Maybe I don't care about Proscan and don't know why any add on is needed at all.

__________________
Uniden scanner internal encryption muting/skipping--making mobile scanning work the way it always should have.

 

[Jay911]

nobody is forcing anybody to do anything (Or listen to anything) they don't want too or maybe they just don't understand.

The entire planet doesn't understand you. You have said:

would like to have the ability (ie Option) to STOP ENC MUTING & SKIPPING.

"STOP ENC MUTING & SKIPPING" means that you want it to NOT mute and NOT skip, which means you want to be listening to a drunk R2D2 screeching through the speaker.

Answer this question:

Why would you want to do that?

 

[jonwienke]

No add-on is needed. Encrypted hits are logged in discovery sessions in the scanner. So there is no reason not to mute/skip encrypted audio.

 

[u2brent]

clearly I live on a different planet.

 

[werinshades]

...and now....back to posting about kudos/issues with Firmware 1.20.

 

[Jay911]

clearly I live on a different planet.

So you're not going to answer the question?

 

[bravo14]

I have noticed on fw .20 I see some false ids on a cap+ system.

I forgot to add this also. Even the RID are giving false ids.

 

[u2brent]

I have answered over and over again.

Clearly I'm a drunk alien robot and Nobody really wants to know the truth.

That is the answer.

In regards to the current software.

I did notice the backlight is not always released on P25 PHII TG coms.
It will sometimes stay on until the next com closes the squelch.
Or I hit the pwr button

 

[jonwienke]

I have answered over and over again.

Clearly I'm a drunk alien robot and Nobody really wants to know the truth.

The answers you've given previously indicate you (erroneously) believe that encrypted audio has to be played for you to log traffic on encrypted talkgroups. You can log encrypted traffic, including TGID and RID, in a Discovery session (which is part of the scanner menu) if you don't want to connect to a computer, or by using software like ProScan if you want extra convenience and better logging and recording options. So you have not yet offered a coherent reason for wanting to hear encrypted audio.

 

[u2brent]

I am erroneous, Exactly how should anybody respond to that? and what would be the point.

 

[INDY72]

It almost sounds like someone thinks they have magic and can decrypt audio if its heard... In which case just get an older generation scanner and drive yourself as insane as your going to drive yourself and everyone else with an literally impossible task.

 

[garys]

The first rule of holes is that once you find yourself in one, stop digging.

I am erroneous, Exactly how should anybody respond to that? and what would be the point.

 

[u2brent]

my older generation scanners don't do ph2..

I'm shoveling, but it ain't dirt..

 

[INDY72]

my older generation scanners don't do ph2..

I'm shoveling, but it ain't dirt..

LOL.... BINGO..... Ladies and gents can we call this thread basically DEAD til the new one Friday? At least on certain points?

 

[IAmSixNine]

LOL waiting for someone to say they applied 1.20 firmware to their scanner and now their iPhone has poor battery life.
Oh wait, that would be iOS 11.3.1 causing the issue. The scanner firmware was causing bad reception on the phone..

Paul a big thank you for keeping the updates coming.

 

[jonwienke]

I am erroneous, Exactly how should anybody respond to that?

Perhaps by offering a coherent fact-based rationale for what you want, as opposed to comments about drunk alien robots.

and what would be the point.

If you articulate a coherent, well-reasoned rationale for why you want to hear encrypted audio, and how it will benefit scanner users, you'll be much more likely to get what you want than by the approach you're currently taking.

 

[wm8s]

Freezing with Site Hold is on trying to dial to another System

Setup:

TxWARN [RR #4563, one of the largest systems in the country] [plus 0 or more other Systems in other FLs; that doesn't matter] are On; lots of/all other Systems in other FLs are Off.

Most of the TxWARN sites are QKed disabled, but a couple are QKed enabled; not sure if this matters.

The BCD536HP is scanning the TxWARN System.

I press [F] + [DEPT] + pause to enable Site Hold. FWIW, Site Hold seems to work as documented and as it always has (i.e., the scanner scans only TxWARN, and only the Site that I'm Site Holding on).

Problem:

If, with Site Hold on, I then press [SYSTEM] and try to DIAL around to any other system, the scanner freezes --- no audio, no display updates, no blinking LED, no nothing --- for 6-7 seconds. As long as I keep turning the dial, it will keep freezing for 6-7 seconds, beep once, freeze for 6-7 seconds, beep once, ad infinitum, until I stop turning the dial, at which point after about 2 seconds, it beeps, unfreezes, and carries on normally.

This does NOT happen by only pressing [SYSTEM]. I.e., after I press [SYSTEM], I can immediately press it again, and System lock works fine; or I can immediately press any other button with the expected result. It only happens when I press [SYSTEM] and then dial up or down.

I've tried this with other systems, and w/o getting out a stopwatch, the length of the freeze seems related to the complexity of the System [or perhaps FL; I tend to have single-System FLs]. E.g., with only pdvWireless [RR #8344] enabled, the freeze is not even a second.

Can someone else with TxWARN in their radio try this? I.e., Site Hold while TxWARN is scanning, then press [SYSTEM], then try to dial up or down?

Thanks.

...R

 

[buddrousa]

What version FIRMWARE are you running 1.19? 1.20 fixed that
1.20.00 Release Notes (05/18/2018)
Fixed odd ASCII characters issue for NXDN Alias
Improved CPU processing load for keypress lag
Modified several operations for Site/Department hold

Note: After applying new firmware, the TGID format for NXDN Trunk Systems will be set to the default (NEXEDGE type). When scanning am IDAS system, you will need to set the TGID to IDAS type again. If you do not, you can scan correctly, but the display will become NEXEDGE type.

 

[jonwienke]

If you are not running 1.20.00, update to that version using Sentinel.

Make a debug log, and post it in the .20 firmware feedback thread.

Start the scanner while holding down Avoid. You can release Avoid when it starts loading favorite lists.

Menu \ Settings \ Set Debug Log Mode \ SD Card (File)

Replicate the problem that makes the scanner lock up.

Menu \ Settings \ Set Debug Log Mode \ Off

Connect the scanner to a computer, enable Mass Storage, and copy the debug log to the computer from the SD card. Zip it, and either attach it to your post, or post a download link to Dropbox or OneDrive or whatever.

 

[jonwienke]

FWIW, I'm unable to replicate the issue running 1.20.00