Aruna | අරුණ

That is weird, can you confirm it using the log. ```shell adb logcat | grep RestartReceiver ``` This should be triggered if the broadcast is sent. My expected logic was...

@Ethanol10 For the beta build I removed the broadcast. Looks like we no longer have #39, but #49 exists. We might be able to fix it more effectively.

@Ethanol10 can you help me to do some experiments on this. Get into `adb shell` on your rooted image and type `getevent`. Then using the stylus, touch somewhere on the...

Mmmm interesting. Based on your comment, it looks like this issue is too fundamental to the firmware level. You have several event values for the pen. ```shell add device 8:...

Okay, then the next option is to try creating the touch pen input from the Android itself. Let me check how we can do that.

Wait a minute, @Ethanol10 looks like I misunderstood how the the events work. This is a protocol, we have to run a series of events to register the touch event...

Mmm Interesting Let's go with the other option, `InputManager` then. Something on this nature should do it. ```kotlin import android.content.Context import android.hardware.input.InputManager import android.os.SystemClock import android.view.InputDevice import android.view.MotionEvent fun injectStylusTap(context:...

Did you try it as a separate app? There should be a way in `adb` to grant the required permissions.

Just an update on this, @Ethanol10 found the issue related to this. Basically, Duo 1 settings are applied on Duo 2 causing this issue.

I was able to get the most out of BE200NGW with CM4 on Debian. I am using [RaspAP](https://github.com/RaspAP/raspap-webgui) for the router functionalities. So far so good including the Wifi repeater...