mirrors
/
tuhi
mirror of https://github.com/tuhiproject/tuhi.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Development (markdown)

master
Peter Hutterer 2019-07-15 21:39:18 +10:00
parent a5c75e5231
commit a2af306496
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Development.md

@ -1,3 +1,7 @@
# Resetting devices
Tuhi stores the device data in `$HOME/.local/share/tuhi/<btaddress>` (i.e. `$XDG_DATA_HOME`) The primary file is `settings.ini` which is how Tuhi remembers devices it has already seen. Removing that device and/or the whole folder makes the device unknown again and the device has to be re-registered.
Tuhi stores the device data in `$HOME/.local/share/tuhi/<btaddress>` (i.e. `$XDG_DATA_HOME`) The primary file is `settings.ini` which is how Tuhi remembers devices it has already seen. Removing that device and/or the whole folder makes the device unknown again and the device has to be re-registered.
# BlueZ ManufacturerData
There's an oddity about the `ManufacturerData` property on the devices. That property is a 7-byte value when the device is running normally but a 4-byte value when the device is in register mode. The update of that property is delayed though, so a device may be in register mode before the `ManufacturerData` reverts to 4 bytes. And, crucially, it **may stay in 4-byte mode** for a successful registration but switches to 7 bytes on the next connection. When a registration times out, the device may stay in 4-byte or 7-byte `ManufacturerData`, it depends on some previous state.