Go to file
Daniele Gobbetti d68a4211b6 First attempt at parsing the live sensor data, see issue #63
- 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
2015-07-02 10:26:32 +02:00
.tx Updated translations from transifex (#46) 2015-05-06 17:39:46 +02:00
app First attempt at parsing the live sensor data, see issue #63 2015-07-02 10:26:32 +02:00
gradle/wrapper First checkin of actual code 2015-01-07 14:00:18 +01:00
.gitignore First checkin of actual code 2015-01-07 14:00:18 +01:00
CHANGELOG.md Bump version to 0.4.2, update CHANGELOG.md 2015-06-27 20:02:46 +02:00
Get_it_on_F-Droid.svg.png add f-droid logo and link. Thanks to "ghost" for the suggestion. 2015-03-29 22:22:03 +02:00
LICENSE Initial commit 2015-01-06 00:19:03 +01:00
LICENSE.artwork Bump version, update CHANGELOG.md and LICENSE.artwork 2015-06-18 21:51:06 +02:00
README.md Explain logging functionality and move download link to top 2015-06-17 23:28:50 +02:00
build.gradle A new sleep chart based on MPAndroidChart 45 2015-06-11 23:37:00 +02:00
gradle.properties First checkin of actual code 2015-01-07 14:00:18 +01:00
gradlew First checkin of actual code 2015-01-07 14:00:18 +01:00
gradlew.bat First checkin of actual code 2015-01-07 14:00:18 +01:00
settings.gradle First checkin of actual code 2015-01-07 14:00:18 +01:00

README.md

Gadgetbridge

Gadgetbridge is an Android (4.4+) Application which will allow you to use your Pebble or Mi Band without the vendor's closed source application and without the need to create an account and transmit any of your data to the vendor's servers.

Download

Gadgetbridge on F-Droid

Features (Pebble)

  • Incoming calls notification and display (caller, phone number)
  • Outgoing call display
  • Reject/hangup calls
  • SMS notification (sender, body)
  • K-9 Mail notification support (sender, subject, preview)
  • Support for generic notifications (above filtered out)
  • Music playback info (artist, album, track). Apollo and CM 12.1 Music App supported.
  • Music control: play/pause, next track, previous track, volume up, volume down
  • List and remove installed apps/watchfaces
  • Install .pbw files
  • Install firmware from .pbz files

How to use (Pebble)

  1. Pair your Pebble through Gadgetbridge's Discovery Activity or the Android Bluetooth Settings
  2. Start Gadgetbridge, tap on the device you want to connect to
  3. To test, choose "Debug" from the menu and play around

Features (Mi Band)

  • Mi Band notifications (LEDs + vibration) for
    • Discovery and pairing
    • Incoming calls
    • SMS received
    • K-9 mails received
    • Generic Android notifications
  • Synchronize the time to the Mi Band
  • Display firmware version and battery state

How to use (Mi Band)

  • When starting Gadgetbridge and no device is visible, it will automatically attempt to discover and pair your Mi Band. Alternatively you can invoke this manually via the menu button. It will ask you for some personal info that appears to be needed for proper steps calculation on the band. If you do not provide these, some hardcoded default "dummy" values will be used instead.

    When your Mi Band starts to vibrate and blink with all three LEDs during the pairing process, tap it quickly a few times in a row to confirm the pairing with the band.

  1. Configure other notifications as desired
  2. Go back to the "Gadgetbridge" Activity
  3. Tap the "MI" item to connect if you're not connected yet.
  4. To test, chose "Debug" from the menu and play around

Known Issues:

  • Android 4.4+ only, we can only change this by not handling generic notifications or by using AccessibiltyService. Don't know if it is worth the hassle.

  • The initial connection to a Mi Band sometimes takes a little patience. Try to connect a few times, wait, and try connecting again. This only happens until you have "bonded" with the Mi Band, i.e. until it knows your MAC address. This behavior may also only occur with older firmware versions.

Contribute

Contributions are welcome, be it feedback, bugreports, documentation, translation, research or code. Feel free to work on any of the open issues; just leave a comment that you're working on one to avoid duplicated work.

Translations can be contributed via https://www.transifex.com/projects/p/gadgetbridge/resource/strings/ or manually.

Having problems?

  1. Open Gadgetbridge's settings and check the option to write log files
  2. Quit Gadgetbridge and restart it
  3. Reproduce the problem you encountered
  4. Check the logfile at /sdcard/Android/data/nodomain.freeyourgadget.gadgetbridge/files/gadgetbridge.log
  5. File an issue at https://github.com/Freeyourgadget/Gadgetbridge/issues/new and possibly provide the logfile

Alternatively you may use the standard logcat functionality to access the log.