androbility / keydroid Goto Github PK

KeyEvent definition.

Use cobra and viper to handle configuration.

This can wait until v0.5.

It'll be renamed adbi since it provides an interface to the adb command and will likely progress at a different pace than keydroid.

adbsuper monitors and restarts adbcmd. After a specified number of failures, it exits.

Push main into a subrepository that main can watch.

Can an Echo Dot be controlled via adb?

A Google Nexus Player?

A Nexus Phone?

They all run Android, so they should. It might be good to have every device type in one repo.

This will eliminate some typo-driven runtime errors, as they will be detected at compile time.

KEYCODE_WAKEUP.

Would adb scripting be useful in version 0.4 and beyond?

Determine yes or no. wait-for-server seems useful.

start-server, kill-server, reboot, and get-state all do as well.

My university technical writing course has an assignment which involves editing documentation on GitHub repositories as practice in real world settings. Edits may involve aspects like style, structure, and concision.

Existing style guidelines would be taken into account. The following is one of the resources I would be using:
https://jacobian.org/writing/technical-style/

Would anyone mind if I propose edits to documentation in this repository? It would really help me out!

Source repo.

Minor improvement.

Switch keymap to map[rune]int.

Each command should be an int constant so errors can be detected at compile time.

I was thinking of adding a file for potential contributors. @stephenwithav , could you clarify the following points:

1. are first-time contributors welcome?
2. are there any files with version numbers that need to be incremented?

Thanks in advance!