There are many so called experts that know best, but quite frankly none of the expertise has produced a solution in my case.
I have run my DV4Mini from new for nearly 18 months and until the introduction of the”Talk Alias” protocol it was working 100%. I had been running it on Ubuntu Mate 16.04.01 and DV4MF2.exe very successfully on the Raspberry PI 3 and RealVNC from an android tablet, when I began to notice drops in received audio part way through a transmission by someone else. The squelch was open but the audio was not decoded.
My DV4Mini runs on 438.650 as measured by a frequency counter without need for correction, that’s channel DMR simplex channel 6, colour 1, slot 1, TG 9. It has done so for for all its time of operation and has worked impeccably. The latest firmware was 1.66.
I initially thought the Retevis RT 3 was dead or dying, but this was not the case as the newly purchased MD 380 proved. It too could not decode the DV4mini.
I upgraded the DV4mini with 1.77, and the latest drivers and software, and upgraded to mdTools in both radios but nothing changed in what was occurring with the DV4mini, until I went to Promiscuous Mode on the radios, when all the transmissions became audible again.
DOH!
Error located and dealt with as follows.
Word from the wise!
When you updated your code plug, make sure you don’t get the talkgroups wrong.
In my case follow your own advice! I had overwritten tg9 with tg4. That’s the solution.
Update 8th December 2017 – Now running K2DLS image with Raspbian Stretch and DV4MF2 look-alike with BMXTG python script. Runs 24/7 on Raspberry Pi 3 with RealVNC.