Hoping some of the Kenwood experts can assist here.
I have this issue with my Nexedge that I’ve been unable to resolve. I suspect it is a setting somewhere but I cannot figure it out.
When switching the radio on, it will not receive any transmissions until I ptt the radio first.
It’s as if it is in some sort of "do not disturb mode. Once I ptt it, it receives signal on all programmed frequencies.
Can anyone shed some light on this please?
I really hope somebody answers this I have this issue on two radios one a nexedge and another Kenwood, an older analogue one. It’s def in the code plug as using an older one cures it, but the trouble doesn’t appear in the others, using the ‘dodgy’ one. Driven me mad.
Its driving me mad and I’m also at my wits end.
All our vehicles has radios in them, but now I cannot reach my son at times because he forgets to ptt the radio before he drives off.
Hi Paul.
Was wondering if you have solved this issue?
Seeing as I recently started experimenting with AI, I am now going to ask Copilot for its sentiments on it.
Here is what it says:
Quick answer: What you’re describing with the Kenwood NX-720 (no RX until PTT is pressed once) is a known quirk tied to programming settings, not hardware failure. It’s usually caused by how the power‑on scan, signaling, or mute options are configured in the programming software. The radio is essentially “sleeping” until the first transmit wakes the audio path.
Likely Causes
Based on manuals and field reports, here are the most probable culprits:
Power‑on scan / zone setting
If the radio is set to start in a scan list or signaling mode, it may not open the squelch until PTT forces it to lock onto a channel.
Squelch / signaling mute
NX radios can be programmed with “QT/DQT” or “Digital Squelch” that keeps the speaker muted until a valid tone/code is received. If misconfigured, the mute doesn’t release until the first PTT event.
Ignition sense / accessory pin behavior
The NX‑720 has an ignition input line. If the radio is wired to ignition but the programming doesn’t match, the audio path may not initialize until a manual trigger.
Firmware / KPG‑111D programming software bug
Some users have reported that certain firmware versions combined with specific programming templates cause this “wake‑up after PTT” behavior. Updating firmware or re‑writing the codeplug often fixes it.
Troubleshooting Steps
Here’s a practical checklist you can try:
Risks & Trade‑offs
My Recommendation
Start with the carrier squelch test on one channel. If that fixes the wake‑up issue, you know it’s a signaling/mute programming quirk. If not, move on to firmware and ignition sense checks.
Nico, since you’re hands‑on with radios, I’d suggest pulling the codeplug into KPG‑111D and looking specifically at the “Optional Features → Power‑On” and “Channel Signaling” tabs. That’s where this gremlin usually hides.
Would you like me to walk you through the exact KPG‑111D menu paths step‑by‑step so you can check those settings directly?
Sources:
Sadly, I never did cure it - I tried most of those suggestions. I also discovered that after reprogramming some analgue 340s in my old hire stock - these did exactly the same thing - needed a ptt click to wake them up.
This is a pity. I will hopefully by the end of the day see if my new code plug works.
I have tried almost everything now and spent an entire day doing it. Nothing works.
@paulears what are the chances that updated firmware will cure this?
I can’t seem to find what version I have, it only states that it is for evaluation and demonstration purposes.
At version it merely says “sample” and thus possibly with limited features.
You have sample firmware? That sounds to me a rather risky thing to update a radio with, unless you have the old firmware to fallback to? I can’t help because I never update firmware unless there’s a really good reason - my experience is just too destructive.
Only realized it now for the first time that its sample firmware. Never saw it before. It looks like the real deal.
Currently trying to source version 3.31 for this radio. If it works, I’ll let you know and we can make a plan to get it to you via dropbox or something similar.
What model Nexedge have you got?
I’m away from the office - The kenwoods are in a box in the store, so I’d have to check. To be honest there are probably a few different models in there - I moved on from Kenwood a couple of years back - they only come out when I get a rush on - and then it’s usually what chargers are available. Thanks for the offer, though.
P
No worries. You mention chargers. Do you have problematic HT’s that has this problem? Mine is a mobile unit.
Anyway I have tracked down a well recommended expert with Kenwoods and my code plug is now with him for an assessment on whether it is something that I stuffed up.
If it is and he tells me what it is I’ll post it here.
Problem solved!!! 
what was it? Something really simple I bet?
Actually really simple.
But because I never fiddle with things I don’t use or understand, it was an area in the menus where I never would’ve thought to look.
Go to the edit menu where you would do all your programming and in the drop down menu select 5-Tone - system parameter.
Then look at the monitor function. Two options there (1) 5-Tone and (2) QT/DQT
Mine was set to 5-Tone and after changing it to QT it worked as it should.
Such a simple thing and I have no idea how or when that setting got changed in all the years I had.
The only time this radio ever went in for a problem, it was when I stuffed something up with vehicle ignition sense and the radio just died and would not switch on again.
I can only imagine that the technician that fixed it at the time erroneously/accidentally set it to 5-tones.