Raspberry not starting up after Step 6

[Zodiak1993]

Hello thank you for your tutorial. But there are two issues.

1. I had to create a UDEV rule after Step 3 for the device as descriped here:
   https://stackoverflow.com/questions/53887322/adb-devices-no-permissions-user-in-plugdev-group-are-your-udev-rules-wrong

2. After I did step 6 the raspberry is not starting anymore (cant connect to ssh, cant ping the pi). I really dont know why because I am not an expert...I had to delete the "KlippyScreenAndroid.service" (sdcard in cardreader) and the pi started normally after that.

I followed another tutorial for "step 6" and now everything is working perfect.

Here it is "step 10"
https://www.angelrojasjr.com/2021/10/30/using-an-android-device-with-klipperscreen/?fbclid=IwAR0Dfxf9sGRBGnapeckuVK4N-DR-OpFEdau4CzQzR5Y6GufsyDWSnn_boPo

I dont know why yours is not working. Maybe because there are two services "KlippyScreenAndroid.service" and the "KlipperScreen.service" - but I dont have a clue :)

[naruhaxor]

i cant seem to replicate your issue as i have both services in my system folder however the udev issue with adb is fairly uncommon and i normally wont consider it however i appriciate you explaining what has happened and keep this issue open as it is helpful for anyone that gets the same issue. the reason i didnt change the original Klipperscreen.service is to allow the ability to just plug in a Pi screen without having to redo a bunch or files i will attempt to replicate this issue but not likely again thank you for bringing this to my attention

[Zodiak1993]

After installing adb and the command "adb devices" ->

List of devices attached:
xxxxxxxx no permissions (user in plugdev group; are your udev rules wrong?);

So I had to edit the udev rules to get it working. No big deal ;)

I tried two times both tries crashed after step 6. The second time it was a clean install of everything.
I didn't make a mistake...
/Edit:
Are you sure about this?

sudo systemctl enable KlippyScreenAndroid
sudo systemctl restart KlippyScreenAndroid

Should it not be like this?

sudo systemctl enable KlippyScreenAndroid.service
sudo systemctl restart KlippyScreenAndroid.service

Glad to hear it is working for you. Thank you for your answer.

[naruhaxor]

The systemctl commands doesn't need the .service behind it however it does need the exact name

[Zodiak1993]

ExecStart=/usr/bin/bash /home/pi/KlipperScreen/launch_klipperscreen.sh

vs.

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

Maybe that is the reason for crash? I will try to find the issue today.

[naruhaxor]

i had issues with running it without the "/usr/bin/bash" however that may be model specific when it comes to the pi as i have a PI4 please comment if you have more information

[Zodiak1993]

I am also using a Pi4. I will try it again today without the "/usr/bin/bash"