Wow thanks for the very rapid software feature update. Didn't clear up my interference problem, but I appreciate the effort. I'll talk with my good friend rf engineer about DIY filter options.
Overall, I really like the P25RX. Very neat device, easy setup. Works as well as my BC436 as far as I can tell. Superb ease of F/W updates and very nice database import of frequencies/systems based on location. Synced with my favorite bluetooth speaker and my truck (2019 Frontier pro4x rockford fosgate factory audio).
I did notice a minor bug in my area wherein zipcode search in the region of 70503 for 700 mhz has the LWIN Scott site incorrectly as labeled Lafayette. The Lafayette site frequencies do not properly populate (only get about 3 of them) in the search, and none of them is the control channel. Of course the software is flexible enough I can just enter it directly.
Only real challenge is that which affects all my receivers. I live in 70503 area and monitor LWIN. On all my receivers which include: cheap dongles, AirSpy, and now P25RX, there is marked and intermittent degradation of P25 reception (both voice and control channel), from what I believe is adjacent interference from Firstnet. This intermittent degradation of P25 reception and sometimes total dropout of decoding occurs the closer you get to a cell site. It knocks out all of the above radios about 1/4 mile away, and is noticable aggravating to about 1/2 a mile or so. Again, all these receivers are similarly affected. From the elevated location of my 3rd floor office which has clear line of site to two cell towers under 1/2 mile, none of my receivers can decode, but they work in the interior of this steel/concrete/brick office building in a windowless room. Seems like this interference has worsened over time. I hadn't fired up my airspy in a while and checked it on unitrunker. Very strong signal to the Scott Lwin control channel but decode was dropping out, presumably again due to the same interference. Guess I need filtration.
Back to P25 rx, again I love this thing. Despite my whining about a local problem, it works as well as any of my other devices throughout my commute, which means it works the vast majority of the way; its only small areas that are dead. It interfaces with my truck's audio system nicely and I'm getting 15 character alphatags displayed. I'm not sure what the trailing 3 characters are, which consist of a colon, letter and number like, ":H9" I look forward to testing it some Phase II systems when I find myself in range of them. I don't know what this is supposed to be; the trailing characters.
I am delighted with my purchase and again
T H A N K S! to the developer.