![]() ![]() The UV-3R Plus radios that I have were all sourced from the same vendor at the same time and all suffered from this issue. It sounds like the OEM software has the same issue? Do all radios behave the same, or do some interpret the offset field differently? The code as provided does not distinguish between behaviors of multiple radios, which means if we just import the code as it is, it may fix the issue for some versions and break it for others (which would make it pointless to include in chirp, IMHO). I'm not sure that it will fix all radios and not regress earlier models.It needs to go to the mailing list in patch format per the developer process docs. ![]() It is improperly formatted and won't pass the tests.It makes multiple changes, not all related to the offset issue. ![]() The attached modified driver isn't acceptable directly into the code for the following reasons: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |