Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scan mode disabled after exiting red button menu #761

Open
c5e3 opened this issue May 22, 2017 · 10 comments
Open

Scan mode disabled after exiting red button menu #761

c5e3 opened this issue May 22, 2017 · 10 comments
Labels

Comments

@c5e3
Copy link

c5e3 commented May 22, 2017

While being in scan mode, by entering the red button menu, scan mode is still on and the active channel gets displayed.
After exiting the menu by pressing the red button again or exiting by navigating to 'exit' and pressing the green button, scan mode is disabled for any reason.

@DL2MF
Copy link
Collaborator

DL2MF commented May 22, 2017

Noticed the same here on my MD390/G, scan always stops when exiting the altmenu.

Additionally I would like to suggest, to move "red button" menu to another button. The red button is used for exit/back from every menu and also is nice to check the radio status (enable backlight). With the new upcoming feature of key repeatmode, there will be very often unintentional malfunction when exiting the factory menu.

I would prefer to activate the alt/appmenu by long keypress on green button or by press the hashkey.

@Wolf-DL4YHF
Copy link
Collaborator

Wolf-DL4YHF commented May 22, 2017 via email

@c5e3
Copy link
Author

c5e3 commented May 22, 2017

Thanks for the quick reply, Wolf!
An alternative LCD driver would be overkill. Since it is this complicated, we can live with this minor bug, I guess. I just thought, that there might be an easy fix, didn't expect it to be this complex.

@Wolf-DL4YHF
Copy link
Collaborator

Wolf-DL4YHF commented May 22, 2017

Well maybe it is easy, if we knew how. Maybe it's just a bit somewhere in one of Tytera's variables in RAM that needs to be set, to force updating the screen ("Tytera's screen") completely.
Something like
redraw_screen = 1; // redraw everything on the main screen

But I'm afraid there isn't such a flag, and reverse-engineering the code to discover the relevant places in the disassembled original firmware is very time consuming. For me, 'forward engineering' (i.e. writing my own additions in C, or maybe Cortex assembler) is much easier, which is one of the reasons for beginning to develop the red-button menu (which does indeed have its own, tiny, new LCD driver).

About the "red menu key" : I wouldn't move this to another key. Like the "green menu key", it's similar to a function key. The two cursor keys between these two should keep their function (we may use them one day in the main screen to increment / decrement the frequency or the channel number). The keys in the 2nd to 4th row immediately open special-purpose screens, and I wouldn't like to change this principle now (it's already well established). The '*', '0', and '#' keys will sooner or later be needed for something else, so we really shouldn't occupy them yet.
Similar for '7', '8', '9' : When on the main screen, let's keep those keys for the future - don't use them for fixed special functions (like even more Netmon hotkeys), at least not yet.

@DL2MF
Copy link
Collaborator

DL2MF commented May 23, 2017

OK, like already discussed by mail, future keyb layout needs to respect further needs.

@paulomartinspt
Copy link

When exiting from the red button menu, the original firmware must be tricked to redraw the normal screen completely. This is done by setting a global variable (channel number) to zero, which causes the Tytera firmware to refresh everything.

dumb question: why not call a reboot when exiting the red key menu? as long at it remains on the same channel, scan will start after reboot (i believe)

@shelllanes
Copy link

the dmr marc had move to a dif website there is the link for it http://www.va3xpr.net/dmr-marc-worldwide-net/ plz fix it in the glv software it keep time out when it try to get the date base
this is the new web site for it http://dmrworldwidenet.blogspot.ca/ plz fix it asap thank you

@Wolf-DL4YHF
Copy link
Collaborator

Wolf-DL4YHF commented May 24, 2017 via email

@Wolf-DL4YHF
Copy link
Collaborator

Wolf-DL4YHF commented May 24, 2017 via email

@travisgoodspeed
Copy link
Owner

Tagging this as "won't fix" until a clean solution presents itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants