bc9041a4c9
Pebble 2/LE: on connect wait 30s max and stop waiting immediately if a real PP connection got establish (ie write request on the gatt server)
2016-12-02 08:07:44 +01:00
3eda2d4b81
Pebble 2/LE: honor reconnect tries
2016-12-02 00:38:53 +01:00
44f74270df
Mi2: Experimental support for activity recognition
2016-12-02 00:22:06 +01:00
da297ecd8b
Fix + cleanup time setting and calendar sending #441
2016-12-01 22:51:08 +01:00
0746aaa579
app: Random typo and consistency fixes.
2016-12-01 20:22:12 +01:00
6dd74d04ac
code/docs: Consistently use the "Gadgetbridge" spelling.
...
"Gadgetbridge" appears to be the common spelling as per most docs,
code comments, wiki, and so on. Thus avoid using "GadgetBridge".
2016-12-01 17:28:51 +01:00
1352575f12
changelog_master.xml: Random typo and consistency fixes.
2016-12-01 17:22:29 +01:00
f0789cc147
Pebble 2/LE: fix another bug when reconnecting
2016-12-01 00:28:23 +01:00
2993bb6b5c
Pebble 2/LE: fix potential NPE
2016-12-01 00:20:21 +01:00
74c20f3a82
Pebble 2/LE: More fun with reconnect
2016-11-30 23:56:58 +01:00
b878fa5eda
Pebble LE/Pebble 2: Fix reconnect not working when first attempt fails
2016-11-30 22:28:34 +01:00
95ec1fb44c
Pebble LE/Pebble 2: Improve reconnect
2016-11-30 19:54:21 +01:00
092012ab31
Changelog for 0.14.3
2016-11-29 23:28:15 +01:00
09ff95eb34
Support for continuous hr readings (live activity) #323
2016-11-29 23:25:11 +01:00
49acde118d
Do not log heartrate separately during miband 1s sync
2016-11-29 23:25:11 +01:00
1862b59dad
bump version and add changelog
2016-11-29 22:36:05 +01:00
011646b097
Fix activity data on Mi Band 1 #440
2016-11-29 22:22:54 +01:00
2677dad873
Fix a recent regression that caused the database migration dialog to never pop up
2016-11-27 22:50:21 +01:00
109a032f1e
Pebble: fix Pebble LE address not being propery added to device attributes
2016-11-27 22:45:57 +01:00
d9e20b161a
Merge pull request #437 from Almtesh/master
...
French translation.
2016-11-27 21:02:07 +01:00
84327a5b86
Pebble: use also the device address as seed to store app configuration
...
This is not needed as long as one GB instance is used to manage a single pebble device, if multiple devices are managed the stored watchapp configuration could be messed up.
2016-11-27 11:31:03 +01:00
fa8df9f552
add missing migration script
2016-11-27 10:52:43 +01:00
16b4bfd0e7
Pebble LE: also return to control center if successfully initialized
2016-11-27 10:38:16 +01:00
723ad53588
Call getDevice always when connected
...
This fixes a longstanding bug where device attributes where ONLY updated when fetching activity data or when pairing a new device
2016-11-27 10:32:56 +01:00
24752d3455
Pebble: try harder to get LE address into the database, does not work
2016-11-27 10:10:50 +01:00
34ad088b88
Pebble: Experimental support for BLE on all models via dev option in Pebble Settings
...
HOWTO:
1) Pair you normal Pebble (not necessary if already done), make sure it was connected once
2) Unpair your LE pebble if already paired
3) Switch on "Always prefer BLE" in Pebble Settings
4) Tap on the + in Control Center to add a new device
5) Pair your Pebble-LE XXXX or Pebble Time LE XXXX inside Gadgetbridge's Device Discovery actibity
Now Gadgetbridge will connect to your LE Pebble when tapping on Pebble XXXX if "Always Prefer BLE" option is enabled.
You can easily switch back to classic LE by turning that option off again
2016-11-27 09:49:28 +01:00
2f7eb9ef23
Some more improvements to discovery
...
- pass service uuids to GBDeviceCandaidate so that DeviceCoordinators
can detect devices by their services.
Note: they should not rely on service uuids being available
2016-11-27 02:46:07 +01:00
b9ff2cd468
A few improvements to discovery
...
- display the right icon for found device candidates
- scan for specific LE services
2016-11-27 01:09:20 +01:00
c84003c1c0
Allumer instead of Alumer
2016-11-25 19:37:21 +01:00
b2e86ca061
fix xml in changelog
2016-11-25 14:55:30 +01:00
352fc1a030
fix wrong return value
2016-11-25 14:53:12 +01:00
6106dda2a3
bump version, update changelog
2016-11-25 14:31:56 +01:00
a5263141d7
Pebble 2: Ignore all GATT communication with all other that the current device
...
Fixes a bad bug where disconnecting from another BLE device caused the Pebble2 to disconnect
2016-11-25 14:28:04 +01:00
2d4645f6cc
Fix only the first day label being displayed in Week Steps charts
2016-11-24 23:35:10 +01:00
79eb4f32df
update Japanese and Spanish from transifex (thanks!)
2016-11-24 22:44:18 +01:00
84caf22479
fix weekly charts to start y axis at 0
2016-11-24 22:27:44 +01:00
7da328d5db
Fix an invalid leftover check for array length
...
Also removed a method invocation that did not belong there.
2016-11-24 22:16:04 +01:00
df4293108a
update changelog (again)
2016-11-24 22:11:59 +01:00
9d083e2330
Pebble: add Kickstart Watchface to app manager on FW 4.X
...
I know it only exist on 4.3+, but I am lazy
2016-11-24 22:10:32 +01:00
02e6ce02b2
Add to 0.14.1 changelog
2016-11-24 22:03:02 +01:00
3fdfb7d172
Mi2: Support for setting the fitness goal (steps)
2016-11-24 21:58:32 +01:00
9bebf1d32f
When memory is really low, free up some memory #436
...
(although we probably can't save much)
2016-11-24 21:15:27 +01:00
60cb67c3c8
Some cleanup
2016-11-24 21:15:27 +01:00
cc0fbff297
Set the sample provider in getLatestActivitySample()
2016-11-24 21:15:27 +01:00
6520b46238
bump version, update changelogs
2016-11-24 19:01:15 +01:00
381323011e
Pebble 2: work around FW installation problems
...
Wait a 0.5s after each complete Pebble packet and do not longer wait at all after a completed GATT package chunk (was 0.1s)
Big outgoing messages will be now much faster such as firmware installations but smaller take more time than before.
(This is not the proper fix but I could update the firmware this way, failed 10 times before after a few percent)
2016-11-24 18:52:58 +01:00
5b804effa4
Pebble: use a proper event handling in the configuration JS
...
This allows more advanced configuration pages to work properly. The problematic config pages emerged while fixing #431
2016-11-24 18:03:47 +01:00
a5a5e66c62
French translation.
...
Changed and added several French messages.
2016-11-24 17:06:43 +01:00
67d89ce1b9
Create the correct start-sync timestamp #323
2016-11-22 22:52:26 +01:00
dfbaba4cb6
Make sure that the charts display the requested time range
...
(instead of only the range with available samples)
2016-11-22 15:53:58 +01:00
Andreas Shimokawa