Integrating Android KlipperScreen config to KIAUH #165

New Issue

2022-01-13T20:36:50+01:00

onehate commented

2022-01-13 20:36:50 +01:00

(Migrated from github.com)

Its not a problem but a FR

Describe the solution you'd like

Thank you for a great setup automation system, love it.

Would not want to sound cliche but, I believe the ability to run KlipperScreen thru an old android phone using XSDL is a very nice way of stopping old phones from going to landfills prematurely. It would be great if KlipperScreen Android and ADB configuration could be done through the CLI interface of KIAUH. Being able to install ADB/tools and automating the KlipperScreen service modification (if needed) would be awesome.

The manual version of this is done as an example at

https://klipper.discourse.group/t/how-to-klipperscreen-on-android-smart-phones/1196

Describe alternatives you've considered

No response

Additional information

No response

### Is your feature request related to a problem? Please describe Its not a problem but a FR ### Describe the solution you'd like Thank you for a great setup automation system, love it. Would not want to sound cliche but, I believe the ability to run KlipperScreen thru an old android phone using XSDL is a very nice way of stopping old phones from going to landfills prematurely. It would be great if KlipperScreen Android and ADB configuration could be done through the CLI interface of KIAUH. Being able to install ADB/tools and automating the KlipperScreen service modification (if needed) would be awesome. The manual version of this is done as an example at [https://klipper.discourse.group/t/how-to-klipperscreen-on-android-smart-phones/1196](url) ### Describe alternatives you've considered _No response_ ### Additional information _No response_

dw-0 commented

2022-01-16 20:57:38 +01:00

(Migrated from github.com)

Hi, thanks for your suggestion.

Basically the same answer i gave in #166 applies here as well.
https://github.com/th33xitus/kiauh/issues/166#issuecomment-1013940026

With every new feature i add, i have to invest time to also support it or fix it if something breaks. Which i can't really do if im not able to even test those things myself. So i prefer such things to be kept in guides like the one you posted. Klippers discourse forum is the better place for those kind of guides. For KIAUH i rather stick to support installations of basic components revolving around Klipper, but not those going into very specific niches.

Hi, thanks for your suggestion. Basically the same answer i gave in #166 applies here as well. https://github.com/th33xitus/kiauh/issues/166#issuecomment-1013940026 With every new feature i add, i have to invest time to also support it or fix it if something breaks. Which i can't really do if im not able to even test those things myself. So i prefer such things to be kept in guides like the one you posted. Klippers discourse forum is the better place for those kind of guides. For KIAUH i rather stick to support installations of basic components revolving around Klipper, but not those going into very specific niches.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: h3n3/kiauh#165