Fork of Gadgetbridge with initial support for Here Active Listening devices
 
 
 
 
 
Go to file
Andreas Shimokawa c0bfe2f715 make quit button work by letting BtSocketIoThread actually leave its main loop, do not display "Unknown" for unknown numbers but the number itself. 2015-01-31 11:49:46 +01:00
app make quit button work by letting BtSocketIoThread actually leave its main loop, do not display "Unknown" for unknown numbers but the number itself. 2015-01-31 11:49:46 +01: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
LICENSE Initial commit 2015-01-06 00:19:03 +01:00
README.md Native support for K-9 Mail, bugfixes for generic notifications 2015-01-26 18:52:19 +01:00
build.gradle First checkin of actual code 2015-01-07 14:00:18 +01: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 a Android (4.4+) Application which will allow you to use your Gadget (Smartwatches/Fitness Bands etc) without the vendors closed source application and without the need to create an account and sync your data to the vendors servers.

Right now this is in very early testing stages and only supports the Pebble.

USE IT AT YOUR OWN RISK. It will problably not work. And if it works it will annoy you more than it helps you ;)

Features:

  • Incoming calls (caller, phone number)
  • SMS notification (sender, body)
  • K-9 Mail notification support (sender, subject, preview)
  • Support for generic botificaions (above filtered out)

Known Issues:

  • Can't reject or hang up phone calls yet
  • Phone calls that are taken or rejected both count as rejected to make the Pebble stop vibrating. (No in-call display yet)
  • No outgoing call support (No in-call display yet)
  • Notifications are not properly queued, if two arrive at about the same time, one of them will get lost (TODO: confirm)
  • 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.

Apart from that there are many internal design flaws which we will discuss using the issue tracker.