Instead of scanning dead air, we all should chime in on encrypted city/counties so we can weed out the silent Police channels.
...Or submit updated information to the database, so everyone can see which channels are encrypted when viewing that county's or system's page.Instead of scanning dead air, we all should chime in on encrypted city/counties so we can weed out the silent Police channels.
I found that the data for my location is wrong. Lee County
Did you report the corrected info to RR?
No due to the fact that the DB is correct just that spreadsheet is wrong. Figured it was an internal communications breakdown .
Some departments encrypt their proprietary channels, others don't. Some departments use them frequently, others don't. If the database entry for a talkgroup has an "E" or "e" then it is encrypted full time or part time, respectively.Referencing to: Proprietary channels for a certain city
Are they encrypted or active?
I seen them, but I just ignored them
Maybe. It's possible that the agency may turn off encryption in the future. It's possible that an individual user of that talkgroup may have a radio that isn't programmed for encryption on that talkgroup, but they use the radio anyway.When the RRDB lists something in the trunked system as fully encrypted, does that mean, there is no use in entering it into any scanner, because it’ll be garbly noises?
Encrypted talkgroups can only be received in the clear by subscriber radios with the necessary keys.Are there any radios on market that can receive fully encrypted?
I still enter them in mine. If I know there is a very slim chance of the TG not using encryption, I may avoid it. If it's a TG I don't hear very often or can't personally verify they use encryption 100% of the time, I leave it on. It's easy enough to temporary avoid if the TG starts holding my scanner up on a regular basis. The database is not always accurate on who is 100% E and who is not.To the point. When the RRDB lists something in the trunked system as fully encrypted, does that mean, there is no use in entering it into any scanner, because it’ll be garbly noises?
To the point. When the RRDB lists something in the trunked system as fully encrypted, does that mean, there is no use in entering it into any scanner, because it’ll be garbly noises? Are there any radios on market that can receive
It also depends on the scanner you're using. I have a Uniden BCD-436HP & an SDS-100; they both automatically mute encryption. So I program all the encrypted talkgroups, 'cuz as @AK9R pointed out, you just never know....fully encrypted?
I've noticed that the SDS100 occasionally tunes to an encrypted channel for a split second but doesn't record or decode. I usually have to reboot to correct it.It also depends on the scanner you're using. I have a Uniden BCD-436HP & an SDS-100; they both automatically mute encryption. So I program all the encrypted talkgroups, 'cuz as @AK9R pointed out, you just never know....
(Yes, I have heard occasional clear traffic on talkgroups that are labeled "DE".)
I noticed that ADP encryption is falsely tuned into the most. Setting Avoid helps a lot! But every now and then it'll do it regardless.The most advanced digital encryption used on MPSCS is detected very quickly and gets skipped. I suspect there’s a slower detection with the old ADP encryption and sometimes you’ll hear gobble de gook until the transmission ends. Have you tried hitting avoid when that occurs? That’s worked for me.