[How To] KlipperScreen on Android Smart Phones

Glad you solved your problem, I don’t think it matters about the name of the shell script, so long as the line in the KlipperScreen.service to execute it is correct and it is indeed located at the specified path. You could call it Big_Hairy_Balls.sh and change the following line to:

ExecStart=/home/pi/KlipperScreen/Big_Hairy_Balls.sh

Maybe it was JHS’ intention to call the script lauch_klipperscreen.sh. I’ve never been much of a fan of the letter ‘n’ myself; I called mine lauch_klipperscree.sh.

My problem with that method could have been related to adb’s permissions. worth exploring if my endeavors with android and linux deploy are fruitless.

I was always able to edit the KlipperScreen.service, without that systemctl command. I just had to edit with nano over ssh.

Not sure about your moonraker getting borked on reboots. I started from a fresh fluiddpi image, it was already installed and worked flawlessly,

For me at least, when I start XSDL, I enter the menu from the splash screen by tapping the bar at the top that says change device configuration. Then it’s Mouse Emulation>>>Mouse Emulation Mode>>>Desktop, No Emulation.


My problem isn’t with the linux kernel as I assumed. Android is the one taking care of the handshake with the printer’s serial port and it seems the kernel module for the CH340 on my Creality v4.2.7 isn’t commonly included in android kernels. If it is there, it’s often not enabled. So now I have to back up my working debian.img and hunt for a ROM for the OnePlus3 that can run a custom kernel with the module included, or, more than likely, compile my own. Hopefully there’s one out there as I’m already out of my depth! :sweat_smile: I also suspect I’m going to run into issues with the OTG cable being able to both charge the phone and connect to the printer simultaneously. (an issue Somekev ran into with the octoprint install he did initially on his S5 - solved with wireless charging on his S6; apparently, there’s a workaround for that too) Probably another couple of days of banging my head against this problem until I have it sorted!