RG351V and M8 headless V3 input problems

[polysix]

When using the new M8 headless V3.0, any time I move the pointer to an empty field it gets filled with a value after about one second (like someone automatically presses the "A" button once). This happens in all input fields except the ones in the phrase view. Rolling back to V2.7.8, everything works fine again. (RG351V with latest Arkos and M8 headless V3.0)

[Pollinopops]

Updating to the latest version of m8c fixes the issue for me. Compiled m8c from the original source https://github.com/laamaa/m8c/ directly on my RG351MP.

[briwil]

Updating to the latest version of m8c fixes the issue for me. Compiled m8c from the original source https://github.com/laamaa/m8c/ directly on my RG351MP.

Any specific notes on how to do this? Because why does this “rg351_m8c” project even exist if we can just build using m8c? I thought the RG351 required a modified firmware version of m8c?

[Pollinopops]

Updating to the latest version of m8c fixes the issue for me. Compiled m8c from the original source https://github.com/laamaa/m8c/ directly on my RG351MP.

Any specific notes on how to do this? Because why does this “rg351_m8c” project even exist if we can just build using m8c? I thought the RG351 required a modified firmware version of m8c?

Follow the steps for Linux on the m8c GitHub. RG351_m8c simplifies the process by providing scripts to install the required dependencies and launching m8c from a rg351 device. You have to build m8c on your device there is no pre-compiled version of the latest m8c for rg351.

[briwil]

Updating to the latest version of m8c fixes the issue for me. Compiled m8c from the original source https://github.com/laamaa/m8c/ directly on my RG351MP.

Any specific notes on how to do this? Because why does this “rg351_m8c” project even exist if we can just build using m8c? I thought the RG351 required a modified firmware version of m8c?

Follow the steps for Linux on the m8c GitHub. RG351_m8c simplifies the process by providing scripts to install the required dependencies and launching m8c from a rg351 device. You have to build m8c on your device there is no pre-compiled version of the latest m8c for rg351.

But there is no terminal on the RG351, so how do you follow the m8c Linux instructions?

[Pollinopops]

Updating to the latest version of m8c fixes the issue for me. Compiled m8c from the original source https://github.com/laamaa/m8c/ directly on my RG351MP.

Any specific notes on how to do this? Because why does this “rg351_m8c” project even exist if we can just build using m8c? I thought the RG351 required a modified firmware version of m8c?

Follow the steps for Linux on the m8c GitHub. RG351_m8c simplifies the process by providing scripts to install the required dependencies and launching m8c from a rg351 device. You have to build m8c on your device there is no pre-compiled version of the latest m8c for rg351.

But there is no terminal on the RG351, so how do you follow the m8c Linux instructions?

Enable remote services and SSH into the device from another computer. Check the M8 discord and search for headless. Lots of information over there.

[briwil]

Updating to the latest version of m8c fixes the issue for me. Compiled m8c from the original source https://github.com/laamaa/m8c/ directly on my RG351MP.

Any specific notes on how to do this? Because why does this “rg351_m8c” project even exist if we can just build using m8c? I thought the RG351 required a modified firmware version of m8c?

Follow the steps for Linux on the m8c GitHub. RG351_m8c simplifies the process by providing scripts to install the required dependencies and launching m8c from a rg351 device. You have to build m8c on your device there is no pre-compiled version of the latest m8c for rg351.

But there is no terminal on the RG351, so how do you follow the m8c Linux instructions?

Enable remote services and SSH into the device from another computer. Check the M8 discord and search for headless. Lots of information over there.

Thank you, I got it. I realized that ArkOS actually does have a built-in terminal, so I just had to plug in a keyboard and was able to update.