I think Uniden needs to get it's act together and come out with a scanner that blows the market away. They did this with the 396, GRE did it with the PSR series - now they need to do it again. The 396 is a great design both in terms of software and hardware, it would be a shame to re-design that from the ground up. Physically, there are a few tweaks that (I think) should be done;
1) Change "polarity" of the SMA so that industry-standard LMR antennas can be use (note: do NOT switch to BNC, stay SMA).
2) Make the case more durable. Granted, mine has put up with a year of man-handling just fine.
3) Have an easily removable belt clip, like a commercial radio, not an ungodly huge belt clip and cheap plastic belt part (mine broke within 2 weeks, and I'm told it isn't a warranty thing, and my local dealer says they cannot order just that piece).
4) LOUDER audio. I'm not expecting volume that of a Motorola, but come on - full-volume on my 396 is LESS than half volume on my Motorola Astro Saber.
As for changes that should be done to the software/firmware;
1) Support for Patching on both EDACS and Motorola systems. C'mon guys, memory is cheap - it isn't rocket science to support patch list announcements.
2) The ability to assign a talkgroup as Analog or Digital.
3) The ability to assign a conventional frequency as Analog, Digital or Mixed-Mode WITH NAC support.
4) The ability to program a System ID in the trunking data to ensure it doesn't pick up the wrong system.
5) Add an option to change the initial volume knob mode - IE, either "Click for volume" or "Click for channel".
6) The ability to decode P25 when in Close Call mode (this is VERY annoying).
7) Ability for Close-Call to both auto-store AND listen at the same time, not just selecting between either one.
Those are about all I can think of right now. Every single "software" suggestion can be done through firmware upgrades with minimal fuss. As for the hardware ones, as I said - I'm not COMPLAINING about the current setup, it would just be nice to have a couple of minor changes made.
These software options are not something I would be willing to pay for, nor should they be something Uniden should even dream of charging for. However, the following are features I would hand over $$ for in a second;
1) D-Star decoding
2) MotoTRBO decoding
3) iDEN decoding (there, I said it...)
4) ProVoice decoding (Yea yea, I know... Just throwing it out there)
5) NXDN decoding (it's gaining steam VERY quickly)
6) Signaling Package. In order to make this a pay-feature, the following would need to be enabled;
-Analog and Digital Trunking ID Display on Motorola and EDACS
-Conventional ANI (MDC, DTMF, FleetSync and G-Star)
-Aliasable ID lists on both trunking and conventional
-MDC/Trunking Call-Alert capabilities (IE, when a particular radio ID is paged, the scanner wakes up).
As for price points on the pay features, it would depend on the feature, but I don't think charging $50 for any of the above would be unreasonable. I think it would depend on any licensing fees that are required. Personally speaking, I value certain features over others. I would (seriously) be willing to drop $200 for JUST patch support, for example. Others might say $50 is too much for adding certain features, but they just don't need them. I don't personally care about ProVoice decoding (yet), so I wouldn't pay much more than $50 for it - but if I lived in an area that was all ProVoice, I'd drop a considerable amount on it.
I really do believe this "Paid Features" thing is the way Uniden is going to go. Look at commercial radio companies for example. Motorola makes a single radio architecture that is capable of a boat-load of features, but the customer only has access to the features encoded on the Flashcode they pay for. Where Motorola screwed up was putting every feature the radio is ever going to be capable of in each radio, regardless of what it is flashed for. This opened the door for people to hack the Flashcode - and as we now know, it is a piece of cake to enable flash features you haven't paid for. If Uniden wants to avoid that potential loss of business, they can create "custom" firmware files. IE, when you purchase a particular feature, it the firmware gets generated and sent to you - to have it only work on YOUR ESN, and ONLY the features you've paid for - thus ensuring you can't scam the system so to speak.
Those are my suggestions anyhow. Take them for what they're worth.