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

"Unknown error" message after pressing and holding page button #5945

Open
1 task done
edwinhilkens opened this issue Feb 25, 2025 · 1 comment
Open
1 task done

"Unknown error" message after pressing and holding page button #5945

edwinhilkens opened this issue Feb 25, 2025 · 1 comment
Labels
bug 🪲 Something isn't working triage Bug report awaiting review / sorting

Comments

@edwinhilkens
Copy link

Is there an existing issue for this problem?

  • I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

TX shows an "Unknown error" message and freezes

Expected Behavior

Should not freeze

Steps To Reproduce

Press and hold the page button while on the main menu

IMG_0748.MP4

TX shows "unknow error" and freezes
Works OK when short press on Page button

Version

2.10.6

Transmitter

FrSky X9D+

Operating System (OS)

Windows

OS Version

No response

Anything else?

No response

@edwinhilkens edwinhilkens added bug 🪲 Something isn't working triage Bug report awaiting review / sorting labels Feb 25, 2025
@pfeerick
Copy link
Member

A "long page" for that class of radio is for bringing up telemetry screen... and since you are getting the ""unknown error" message, this would suggest you are running a Lua telemetry script, not just showing numbers or bars... so what Lua script are your running that might be triggering this error?

Does the handset actually freeze? i.e. is the RF still working? Do any countdown prompts / center beeps, etc, still trigger? Does it show the power down animation if you try to power off? And rather than a momentary press of the EXIT ("RTN") button, try pressing it for more than 1 second (force quit for Lua) - does that close the error messagebox?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🪲 Something isn't working triage Bug report awaiting review / sorting
Projects
None yet
Development

No branches or pull requests

2 participants