Nano K 1.6.4 Crashes every time (FIXED)

[AB6RF]

New RRC Nano user here...

I have a working RRC setup with TS-480, and COM 2 used as a CAT control.
It works great using the Kenwood front panel and ARCP-480 at the Control location.

I loaded the RRC Nano K 1.6.4 from the Play Store, and installed it on my Pixel 7, running Android 13.

Every time I try to start using the Nano, it crashes after I click the "Connect" button.
I believe the connection settings are correct because:

1) after the Nano crashes, there is a "Connected" icon left behind on the display.

2) If try to use the Kenwood front panel after the Nano crashed, I get the "busy signal" beep, indicating that the Remote RRC already has an active connection.

Any suggestions why the App crashes, and more importantly any suggestions how to fix the issue?

Mikko,
AB6RF / OH1G

[Jan (Microbit)]

?

[AB6RF]

Jan, I'm not sure what your question was, the text is not there.

But if this is what you were asking, I'm not using the default port numbers, but the port settings are same in Nano and in my Control RRC and in Remote RRC.

Is it possible to get any sort of debug log, or something similar to see why the app crashes?

AB6RF / OH1G

[AB6RF]

I would like buy the App and start using it, but so far it crashes every time when I try to connect to the Remote RRC.

[Jan (Microbit)]

https://www.telerik.com/download/fiddler

[AB6RF]

Thank you for trying to resolve this!

I tried to decipher that image, but I don't understand what I'm looking at.

Should I install Fiddler on a PC and try to capture the traffic RRC Nano traffic from the Android device?
Which flow should I capture, SIP, UDP commands, or UDP Audio?

AB6RF / OH1G

[Jan (Microbit)]

 Yes

Jan

[AB6RF]

I haven’t been able to get the Fidler setup to work, but problem still continues.

I’ve installed the demo RRC Nano-K to three different Android devices, and I get the same end results every time.
The RRC Nano does connect to my Radio RRC, but after the connection is made, the app crashes every time.

I know that the connection was made because
1) if I try to afterwards connect the Control RRC, I get the busy tone and the TS-480 front panel doesn’t connect
2) if the Control RRC is first connected, and I then try to use the Nano, it says the connection is already busy

And I have double checked the connection settings. They are correct, and match my Control RRC settings.

Are there some codec, or other settings that MUST be at default values for the Nano to work?
The RRC boxes have more settings than the Nano, what if my codec settings don’t match what Nano thinks they are?

AB6RF

[BI1LLM]

Turn on RRC nano's microphone permission in the settings to solve this problem.

[Joakim (Microbit)]

Turn on RRC nano's microphone permission in the settings to solve this problem.

That is correct, we have now updated the free demo-apps to properly support the new Android 13 permissions.
This includes both the microphone and Bluetooth connection and will be requested when you attempt to connect.

[BI1LLM]

Turn on RRC nano's microphone permission in the settings to solve this problem.

That is correct, we have now updated the free demo-apps to properly support the new Android 13 permissions.
This includes both the microphone and Bluetooth connection and will be requested when you attempt to connect.

I have another problem, please check my post, I am willing to pay for it if it can be solved.

[AB6RF]

Turn on RRC nano's microphone permission in the settings to solve this problem.

Yes!  That fixed the problem, I would have never known to go into the Android Settings / Apps  and change the permissions.
Thank you!
Now I can proceed to buy the Pro version.

AB6RF