If the only thing you change is makefile then provide the build option that you choose. You should have started with that. Think again, how am I suppose to track it down without it?

If you made source code changes then you caused the bug that you have hunt down on your own.

from uv-k5-firmware-custom.

compile options (see README.md for descriptions)

0 = disable

1 = enable

ENABLE_CLANG := 0
ENABLE_SWD := 0
ENABLE_OVERLAY := 0
ENABLE_LTO := 1
ENABLE_UART := 1
ENABLE_AIRCOPY := 1
ENABLE_FMRADIO := 0
ENABLE_NOAA := 0
ENABLE_VOICE := 0
ENABLE_VOX := 0
ENABLE_ALARM := 0
ENABLE_TX1750 := 1
ENABLE_PWRON_PASSWORD := 0
ENABLE_BIG_FREQ := 0
ENABLE_SMALL_BOLD := 0
ENABLE_KEEP_MEM_NAME := 1
ENABLE_WIDE_RX := 1
ENABLE_TX_WHEN_AM := 0
ENABLE_F_CAL_MENU := 1
ENABLE_CTCSS_TAIL_PHASE_SHIFT := 1
ENABLE_BOOT_BEEPS := 0
ENABLE_SHOW_CHARGE_LEVEL := 1
ENABLE_REVERSE_BAT_SYMBOL := 1
ENABLE_CODE_SCAN_TIMEOUT := 0
ENABLE_AM_FIX := 1
ENABLE_AM_FIX_SHOW_DATA := 0
ENABLE_SQUELCH_MORE_SENSITIVE := 1
ENABLE_FASTER_CHANNEL_SCAN := 1
ENABLE_RSSI_BAR := 1
ENABLE_AUDIO_BAR := 0
ENABLE_COPY_CHAN_TO_VFO := 1
ENABLE_SPECTRUM := 1
#ENABLE_SINGLE_VFO_CHAN := 1
#ENABLE_BAND_SCOPE := 1

#############################################################

from uv-k5-firmware-custom.

is there a problem ? or not?

If you are asking me. Then Yes I would agree theres and issue relating to ENABLE_TX_WHEN_AM := 0 which is impacting the radio's functions

from uv-k5-firmware-custom.

This is because of the FM radio disabled, it blocks some code that resets the VFO state.
BTW linux compiler (I use docker ) creates smaller binaries that can fit FM radio too.
Your options + FM radio: firmware.packed.zip

from uv-k5-firmware-custom.

I don't have such a problem. Does it work like that when the plug is disconnected? Where did you get the firmware from?

from uv-k5-firmware-custom.

it works the same way with the plug disconnected, the firmware from your repo

from uv-k5-firmware-custom.

But did you build your own or did you use the release provided, which version?

from uv-k5-firmware-custom.

collected in visiual studio code , today from repo

from uv-k5-firmware-custom.

am wondering which Frqs, I di have similar issue if AM band is one of the two selected Frqs on screen. And if AM is being received or just finished it can be a second or tow before I can trans on my other frq..

from uv-k5-firmware-custom.

yes, it 's Am , it's the same at closed frequencies, the inscription does not go out

from uv-k5-firmware-custom.

yes it is am

then thats the actually issue... I am pretty sure because the Radios chips do funky things to get AM it takes time to switch back for FM... I notice the same issue on Stock FW's and all other custom ones too but is a little worse on customs possible due to the AM fixes employed...

from uv-k5-firmware-custom.

with other messages the same trouble

from uv-k5-firmware-custom.

All you do is press the PTT and the message stays on permanently? Every time?

from uv-k5-firmware-custom.

with other messages , the same trouble , for example , busy on a busy channel ,yes every time

from uv-k5-firmware-custom.

Did you try with the release provided?
https://github.com/egzumer/uv-k5-firmware-custom/releases

from uv-k5-firmware-custom.

it works, but I need to change some functions

from uv-k5-firmware-custom.

This is Matoz's FW (still base on 1of11/fagci's) and you can see the issue... will not trans if AM in use or just been in use.. If I have ANY other bands set no issue... Only occurs(for me anyway) when AM is in use. This has always been an issue from Stock.

from uv-k5-firmware-custom.

When dual watch is in use, the last channel that was receiving becomes an active channel for tx for couple of seconds, no issue there.

The issue supposedly is that the massage stays permanently.

from uv-k5-firmware-custom.

from uv-k5-firmware-custom.

it is worth paying attention to the fact that the second channel is already receiving and this one is still blocked

from uv-k5-firmware-custom.

firmware.zip

from uv-k5-firmware-custom.

downloaded the repository https://github.com/egzumer/uv-k5-firmware-custom ,compiled in visual studio code

from uv-k5-firmware-custom.

Try the relese i provided

from uv-k5-firmware-custom.

relese is good. all work.

from uv-k5-firmware-custom.

Then provide what you change

from uv-k5-firmware-custom.

the release works, but I'm not used to asking and would like to change some data myself, font, etc.

from uv-k5-firmware-custom.

I change the makefile from your repo , I don 't touch the source code , the output is what I wrote about

from uv-k5-firmware-custom.

#define ONE_OF_ELEVEN_VER

#ifdef GIT_HASH
#define VER GIT_HASH
#else
#define VER "231004"
#endif

#ifndef ONE_OF_ELEVEN_VER
const char Version[] = "OEFW-"VER;
const char UART_Version[] = "UV-K5 Firmware, Open Edition, OEFW-"VER"\r\n";
#else
const char Version[] = "1o11+fagci-"VER;
const char UART_Version[] = "UV-K5 Firmware, Open Edition, 1o11+fagci-"VER"\r\n";
#endif

from uv-k5-firmware-custom.

#define ONE_OF_ELEVEN_VER

#ifdef GIT_HASH #define VER GIT_HASH #else #define VER "231004" #endif

#ifndef ONE_OF_ELEVEN_VER const char Version[] = "OEFW-"VER; const char UART_Version[] = "UV-K5 Firmware, Open Edition, OEFW-"VER"\r\n"; #else const char Version[] = "1o11+fagci-"VER; const char UART_Version[] = "UV-K5 Firmware, Open Edition, 1o11+fagci-"VER"\r\n"; #endif

the info from the make file not version file, version file will not actually give version it defines how to write it on boot screen!

from uv-k5-firmware-custom.

Makefile.zip

from uv-k5-firmware-custom.

compile options (see README.md for descriptions)

0 = disable

1 = enable

ENABLE_CLANG := 0 ENABLE_SWD := 0 ENABLE_OVERLAY := 0 ENABLE_LTO := 1 ENABLE_UART := 1 ENABLE_AIRCOPY := 1 ENABLE_FMRADIO := 0 ENABLE_NOAA := 0 ENABLE_VOICE := 0 ENABLE_VOX := 0 ENABLE_ALARM := 0 ENABLE_TX1750 := 1 ENABLE_PWRON_PASSWORD := 0 ENABLE_BIG_FREQ := 0 ENABLE_SMALL_BOLD := 0 ENABLE_KEEP_MEM_NAME := 1 ENABLE_WIDE_RX := 1 ENABLE_TX_WHEN_AM := 0 ENABLE_F_CAL_MENU := 1 ENABLE_CTCSS_TAIL_PHASE_SHIFT := 1 ENABLE_BOOT_BEEPS := 0 ENABLE_SHOW_CHARGE_LEVEL := 1 ENABLE_REVERSE_BAT_SYMBOL := 1 ENABLE_CODE_SCAN_TIMEOUT := 0 ENABLE_AM_FIX := 1 ENABLE_AM_FIX_SHOW_DATA := 0 ENABLE_SQUELCH_MORE_SENSITIVE := 1 ENABLE_FASTER_CHANNEL_SCAN := 1 ENABLE_RSSI_BAR := 1 ENABLE_AUDIO_BAR := 0 ENABLE_COPY_CHAN_TO_VFO := 1 ENABLE_SPECTRUM := 1 #ENABLE_SINGLE_VFO_CHAN := 1 #ENABLE_BAND_SCOPE := 1

#############################################################

this I what I have

from uv-k5-firmware-custom.

firmware.zip

from uv-k5-firmware-custom.

firmware.zip

Now flashed your compiled version... what are the actual Frqs used so I can try and reporduce

from uv-k5-firmware-custom.

That is all I need for now, I'm away, I'll look at it when I'm back.

@lohtse you are too agressive in our posts, stop doing that. And to both of you, plowing through your shit posting is the last thing I want to do. Short questions, short answers, facts. Want to have discussion go somewhete else.

from uv-k5-firmware-custom.

well I can confirm using the provide make file it triggers a tx disabled that requires a reboot

from uv-k5-firmware-custom.

130,300 , 118,200 , 27,135
please try this

from uv-k5-firmware-custom.

130,300 , 118,200 , 27,135 please try this

with your make file it just happened with out the need to use yours . both frqs was Airband. and pushing ppt caused it

from uv-k5-firmware-custom.

Once I enabled

ENABLE_TX_WHEN_AM := 1

the issue is resolved for me

thats the only thing I changed in your make file..

if tx disabled is displayed waited a second or two if does not disappear just press ptt message disappears and can transmit

from uv-k5-firmware-custom.

reflashed my preferred FW checked functions, reset the provide make file to ENABLE_TX_WHEN_AM := 0 reflashed and back to the issue reported, reset makefile back too ENABLE_TX_WHEN_AM := 1 reflashed and problems resolved

from uv-k5-firmware-custom.

try to turn on channel busy lock now, transmit fm and any frequency from 144 to 435 mhz on a busy channel. you will be surprised

from uv-k5-firmware-custom.

try to turn on channel busy lock now, transmit fm and any frequency from 144 to 435 mhz on a busy channel. you will be surprised

with the channels I have set I have no busy message on ranges 15X.XXXXX and 40X.XXXX. No issue with 144.000 or 435.000 ranges either.

from uv-k5-firmware-custom.

without a difference

from uv-k5-firmware-custom.

without a difference

if I don't do this ENABLE_TX_WHEN_AM := 1 I know I will have issues... As it happened instantly when I tried as stated earlier.

from uv-k5-firmware-custom.

"if I'm not looking, then there's no problem "

from uv-k5-firmware-custom.

is there a problem ? or not?

from uv-k5-firmware-custom.