mirror of
https://github.com/meshtastic/meshtastic.git
synced 2024-12-25 21:54:20 -08:00
android usage cleanup
This commit is contained in:
parent
54725b3e11
commit
8aa7174314
|
@ -20,26 +20,15 @@ You will need a device with Meshtastic installed to go any further. See the [get
|
|||
|
||||
To find devices via Bluetooth click the button on the bottom right corner of the Settings tab (last tab).
|
||||
|
||||
If the button is disabled, there are no devices available. To refresh the button state, click `None (disable)`.
|
||||
|
||||
Make sure the device is turned on and not connected to any other app or client. Try to reset, or forget the device on Android Bluetooth settings.
|
||||
If the button is disabled, there are no devices available. To refresh the button state, click `None (disable)`. Make sure the device is turned on and not connected to any other app or client. Try to reset, or forget the device on Android Bluetooth settings.
|
||||
|
||||
[![Device available to select](/img/android/android-settings-connect-sm.png)](/img/android/android-settings-connect.png)
|
||||
|
||||
1. Select the Device by name, "Meshtastic_bebc" in the example above. (You will see any active devices within range, so make sure to get the right one.)
|
||||
2. You will need to "pair" the device by entering a PIN shown on the device screen. This can alternatively be done in the phone Bluetooth settings. If the Device has no screen, but it's connected via USB, it may be displayed on a serial terminal (921600 Baud). For a development device, the PlatformIO terminal would come in handy. Some nodes have buttons allowing you to change the page displayed on the nodes screen. If you double click this button, it will set the pairing code to `123456`.
|
||||
3. Edit the "Your name", e.g. to be "Mike Bird". This is the name that other people will see, so make it unique within your group.
|
||||
4. The initials e.g. "MB" should also be unique and will be used to identify you in the message history and on the device screens.
|
||||
2. You will need to "pair" the device by entering a PIN shown on the device screen. This can alternatively be done in the phone Bluetooth settings. Some devices have buttons, where a double click sets the pairing PIN to `123456`.
|
||||
3. This should start the communication with the Device. The cloud icon, on the status bar, will have a tick.
|
||||
|
||||
[![Changing device name](/img/android/android-settings-mike-sm.png)](/img/android/android-settings-mike.png)
|
||||
|
||||
5. This should start the communication with the Device. The cloud icon, on the status bar, will have a tick.
|
||||
|
||||
![Connected](/img/android/android-cloud-tick.png)
|
||||
|
||||
If there is no Device shown, just the `None (disable)` as below, then the device may be off, or in a sleep mode. Try to reset, or press a button to wake it.
|
||||
|
||||
[![No devices available](/img/android/android-settings-mike-c.png)](/img/android/android-settings-mike-c.png)
|
||||
[![Device connected](/img/android/android-settings-mike-c.png)](/img/android/android-settings-mike-c.png)
|
||||
|
||||
The cloud icon at the top right corner indicates if you are connected to a device. This currently has three states:
|
||||
|
||||
|
@ -51,11 +40,17 @@ The cloud icon at the top right corner indicates if you are connected to a devic
|
|||
|
||||
## Common tasks
|
||||
|
||||
Once you are connected to a device, the App will work, and you can test it by "sending" a message. However, you will need to join or create a new mesh network so you have someone to communicate with. If you have been sent a QR code or link for Meshtastic, then skip ahead to [Join a Channel](#join-a-channel), otherwise you will need to Setup a Channel.
|
||||
### Change your name
|
||||
|
||||
Edit the "Your name", e.g. to be "Mike Bird". This is the name that other people will see, so make it unique within your group. The initials e.g. "MB" should also be unique and will be used to identify you in the message history and on the device screens.
|
||||
|
||||
[![Changing device name](/img/android/android-settings-mike-sm.png)](/img/android/android-settings-mike.png)
|
||||
|
||||
### Setup a channel
|
||||
|
||||
To use Meshtastic, you need to setup a Channel and share the details with your group. The group is private and only those who have the details can join the group and see the messages. You will need to do this once initially, and then only when you want to change or make a new mesh network group. For a new device you will see there is a default setting, shown as `#LongSlow-V (Long range / Slow)`. It is OK to use this initially.
|
||||
If you have been sent a QR code or link for Meshtastic, then skip ahead to [Join a Channel](#join-a-channel). Devices have a default channel preconfigured, shown as `#LongSlow-V (Long range / Slow)`. It is OK to use this initially.
|
||||
|
||||
You can also create a new Channel and share the details with your group. The group is private and only those who have the details can join the group and see the messages. You will need to do this once initially, and then only when you want to change or make a new mesh network group.
|
||||
|
||||
The Channel tab allows you to do this. This screen is initially locked so that you don't change it accidentally. Press the lock symbol, and you will be able to edit. First, select the Channel options, as shown here, and chose the most appropriate option:
|
||||
|
||||
|
@ -170,7 +165,7 @@ Pressing the three vertical dots in the top right corner shows the configuration
|
|||
|
||||
This allows you to disable or change the frequency with which your location is broadcast across the mesh. By default, this is set to 900 seconds (15 minutes). The minimum time this can be set for the default channel is 375 seconds, the reasons for which have been [discussed on the forum](https://meshtastic.discourse.group/t/lost-messages-while-testing/2455/19).
|
||||
|
||||
#### Device sleep period (This feature is disabled by default and no longer recommended)
|
||||
#### Device sleep period (now disabled by default & no longer recommended)
|
||||
|
||||
ESP32 devices can enter sleep mode to save battery life. During sleep Bluetooth is turned off. This setting allows the length of the sleep mode to be changed from the default 300 seconds (5 minutes). After this time period, they awake to check the phone for any queued messages and then go back to sleep, alternating between sleep and awake states. Receiving a message over LoRa (the LoRa receiver never switches off) or pressing a program button (if there is one on the device) also awakes the device.
|
||||
|
||||
|
@ -178,7 +173,7 @@ ESP32 devices can enter sleep mode to save battery life. During sleep Bluetooth
|
|||
|
||||
[![Debug page](/img/android/android-debug-sm.png)](/img/android/android-debug.png)
|
||||
|
||||
The debug page allows you to see all packets sent between the application and the device. This can be useful for debugging purposes.
|
||||
The debug panel allows you to see all packets sent between the application and the device. This can be useful for debugging purposes.
|
||||
|
||||
### Export rangetest.csv
|
||||
|
||||
|
|
Loading…
Reference in a new issue