d68a4211b6
- Live sensor data reading is toggled using the "Set music info" in the debug activity. - The readings are ONLY logged at the moment - The miband increments a "counter" (two bytes) at every reading, but it may be that more readings are sent with the same counter value. This is already addressed. - The name of the axes is general (axis1, 2 and 3) because we still don't know which is which - It could be that the axes depend on the wear location (especially wearing as a necklace means that the miband rests in a vertical position, while wearing on the wrist means it rests in a horizontal position). NB: It could be that we get RAW data, hence not dependent on the wear location. - Since the miband may be inserted in two directions in its strap, I guess this also has to be taken into account - the battery impact of reading this data in unknown |
||
|---|---|---|
| .. | ||
| .settings | ||
| aidl/com/android/internal/telephony | ||
| assets | ||
| java/nodomain/freeyourgadget/gadgetbridge | ||
| res | ||
| .classpath | ||
| .project | ||
| AndroidManifest.xml | ||
| lint.xml | ||
| project.properties | ||