search

d4rk50ul1 / klipper-on-android

Using Android to run Klipper, Moonraker, Mainsail/Fuidd, and KlipperScreen
GNU General Public License v3.0
112 stars 23 forks source link

sudo apt install git Killed #2

Open bladedmadman opened 2 years ago

bladedmadman commented 2 years ago

I have been trying to follow this tutorial but after i ssh into the container my commands are killed. i think I'm doing everything right but I'm a noob when it come to this kind of thing. It might have something to do with samsung orcording to some posts about a similar issue i tried following some advice I tried flashing a multi disabler thing with no change so unless I have missed something dumb its a dead end for me Phone: s9 plus android 10 Root: magisk

muraveix commented 2 years ago

Phone: s9 plus

It is necessary to replace the stock firmware with a custom one

d4rk50ul1 commented 2 years ago

Not sure i follow, but the only thing you need is a rooted phone, no custom rom is mandatory so, using magisk is ok. Now in regards to ssh not sure where are you doing ssh and why is it killed. You must give more details.

muraveix commented 2 years ago

I have Samsung and had the same problem, which was eliminated after installing custom firmware. With a high probability, the problem in the security system is knox. It must die! :)

d4rk50ul1 commented 1 year ago

Gotcha, in that case, perhaps something like lineageOS rom + magisk would fix the problem. Try to flash lineageOS firmware and try again.

ZerGo0 commented 1 year ago

I'm using a S20 and rooted it using magisk as well. What issue do you have exactly? I had connection issues within a few minutes after reboot. That's because of androids deep sleep mechanism which can be disabled, but I don't know if that is what you are experiencing or not.

bladedmadman commented 1 year ago

I'm using a S20 and rooted it using magisk as well. What issue do you have exactly? I had connection issues within a few minutes after reboot. That's because of androids deep sleep mechanism which can be disabled, but I don't know if that is what you are experiencing or not.

I follow the guide and I SSH into the container from putty and any command with sudo gets killed it just responds with killed