There are many ways to set the PineTime! I'll discuss the user-friendly ways, then I'll explain how *I* did it.
The most user-friendly way is to connect the PineTime to a phone or PC using one of the few companion apps available. A short summary list is: GadgetBridge for Android (use FDroid, not the play store), AmazFish for Android and SailfishOS, Siglo for Linux, etc.
The way I used did not use a companion app, because I haven't yet decided how I want to connect. It uses bluetoothctl, which is a very standard tool common to most Linux distros. The procedure is based on this FAQ answer: https://wiki.pine64.org/wiki/PineTime_FA...ineTime.3F
1) I noted the BLE MAC address given on the 3rd page of the About menu. Call it [MAC]
2) I started bluetoothctl in a terminal window on my desktop
3) I typed "pair [MAC]"
4) It didn't work! I don't know why, but PineTime is only available for pairing shortly after a restart
5) I held down the button for 10 seconds, and when it rebooted, "pair [MAC]" worked
6) I accessed the GATT menu by entering "menu gatt" after successfully pairing.
7) I typed "list-attributes", and noted that one of the attributes is called "Current Time":
[NEW] Characteristic
/org/bluez/hci0/dev_[MAC]/service0017/char0018
[UUID]
Current Time
8) I selected that attribute using "select-attribute /org/bluez/hci0/dev_[MAC]/service0017/char0018"
9) I read that attribute using "read". This wasn't required; I was just interested.
10) I pushed the new time using:
write "0xe5 0x07 0x08 0x0d 0x12 0x33 0x00 0x00 0x00"
but you'll have to update that string of hex values based on the current time. You can see what those hex values stand for by reading the FAQ above; in summary:
<lsb of year> <msb of year> <month (1-12)> <day (1-31)> <hour (0-23)> <minute (0-59)> <seconds (0-59)> <weekday (1-7 where 1=Monday)> <fractions (1/256th of second)>
where "lsb" and "msb" are "least significant bit" and "most significant bit".
The most user-friendly way is to connect the PineTime to a phone or PC using one of the few companion apps available. A short summary list is: GadgetBridge for Android (use FDroid, not the play store), AmazFish for Android and SailfishOS, Siglo for Linux, etc.
The way I used did not use a companion app, because I haven't yet decided how I want to connect. It uses bluetoothctl, which is a very standard tool common to most Linux distros. The procedure is based on this FAQ answer: https://wiki.pine64.org/wiki/PineTime_FA...ineTime.3F
1) I noted the BLE MAC address given on the 3rd page of the About menu. Call it [MAC]
2) I started bluetoothctl in a terminal window on my desktop
3) I typed "pair [MAC]"
4) It didn't work! I don't know why, but PineTime is only available for pairing shortly after a restart
5) I held down the button for 10 seconds, and when it rebooted, "pair [MAC]" worked
6) I accessed the GATT menu by entering "menu gatt" after successfully pairing.
7) I typed "list-attributes", and noted that one of the attributes is called "Current Time":
[NEW] Characteristic
/org/bluez/hci0/dev_[MAC]/service0017/char0018
[UUID]
Current Time
8) I selected that attribute using "select-attribute /org/bluez/hci0/dev_[MAC]/service0017/char0018"
9) I read that attribute using "read". This wasn't required; I was just interested.
10) I pushed the new time using:
write "0xe5 0x07 0x08 0x0d 0x12 0x33 0x00 0x00 0x00"
but you'll have to update that string of hex values based on the current time. You can see what those hex values stand for by reading the FAQ above; in summary:
<lsb of year> <msb of year> <month (1-12)> <day (1-31)> <hour (0-23)> <minute (0-59)> <seconds (0-59)> <weekday (1-7 where 1=Monday)> <fractions (1/256th of second)>
where "lsb" and "msb" are "least significant bit" and "most significant bit".