Two feature requests (if the devs are listening)

Snapmaker 2.0
1

  1. Can we please get adb access to the android controller, especially for the reason to run “adb logcat”. My SM2.0 keeps having WiFi issues and having to use a USB Ethernet adapter sucks. With adb logcat there’s hope I could at least get some logs and find out why.

  2. Add an option to start the print after sending it to the controller. I have my SM2.0 in the garage which is the other end of the house, which means a lot of running back and forth. I prefer to print from the controller instead of Luban since I don’t want to lose the print should my desktop reboot (looking at you windows update). I’m fine with the initial connect wifi auth screen, that makes sense, but after sending it, I should be prompted if I want to start it and perhaps a confirm screen where I agree I understand that the printer must be ready to be used (no obstructions, etc) and that SM takes no responsibility for things going south.

2

regarding 2…

not that i recommend this, but you can just hit the play button from luban to start printing.

however, you will not have power loss or filament runout recovery.

3

You’re more likely to get feedback from the dev team by adding an issue on github: Snapmaker · GitHub

4

I wanted to, but the github area doesn’t have a repo for the actual display/android device, only the firmware that controls the actual modules. And these requests are for the android part.

5

So I guess I might as well request the repo for android so I can build my own controller software :smile:

6

They promised to make it available in the (near) future. For now I would add those requests to the Luban repo.