Replies: 2 comments 18 replies
-
|
Dear muzkr, |
Beta Was this translation helpful? Give feedback.
-
|
In my case the list of needed features is pretty short. The rest can go. But then, I'm using this radio primary as a communication device, not scanner or analyzer. Compatibility with Chirp without using custom Python module would also be a plus. "ENABLE_FMRADIO": true, For me, the biggest reason of moving away from stock to custom firmware was change to long press buttons. And a few improved techical parameters. This is what egzumer basically achieved. Others moved in all possible directions from that point, sometimes with good results, sometimes with something that borders with pure nonsense. muzkr, if you want me to do a beta test V2 or check something in stock radios, just let me know. I still have several untouched UV-K5(8) and UV-5R Plus V1 as well as several V2s. P.S. Judging by comments in several forums, the user base of V2 radios is not that small as it might seem. They're simply waiting for firmware. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Tell me which features you want to keep and which ones you're willing to give up to get them.
Edit: By "features" I mean the various ENABLE_XXX flags as defined in the CMakePrests.json file.
Beta Was this translation helpful? Give feedback.
All reactions