e43fed2e7e
Pebble: various preparations for FW 3.x support
...
- Implement encodeAppStart() for FW 3.x
- List cached PBWs in AppManager (currently only UUID)
2015-08-11 13:55:35 +02:00
13260416f3
Pebble: decode app fetch requests for debugging purposes
2015-08-11 13:21:29 +02:00
151f5b8e12
Pebble: Choose binaries from basalt/ inside .pbw files for Pebble Time
...
PBW installation is still unsupported on FW 3.x, these are just preparations
2015-08-11 12:47:23 +02:00
5a8c9a9180
Pebble: cache installed pbw files on sdcard if force untested option is set
...
This will be needed for FW 3.x on demand installations.
2015-08-11 12:04:45 +02:00
0be251e83d
Pebble: if untested features option is enabled use Gadgetbridge sample provider insted of Morpheuz
2015-08-11 11:21:10 +02:00
5884684cad
Pebble: add option to enable untested features.
...
Bad things incoming ;)
2015-08-11 11:15:44 +02:00
7bf45d9b9f
Merge branch 'master' of https://github.com/Freeyourgadget/Gadgetbridge
2015-08-10 11:24:51 +02:00
b6d3317b2d
First step for GBDeviceEvents support:
...
- change fw handling to GBDeviceEvent
- misuse the hw version for showing the MiBand device name (there is still no option to set a custom name)
2015-08-10 10:35:55 +02:00
fd5a620091
re-add support for NO_RESPONSE write characteristic
2015-08-10 09:20:06 +02:00
d983d7a5c4
Pebble: answer pings from the watch
2015-08-09 21:42:27 +02:00
27f88e484d
Make ControlCenter only ask for version details after device is initialized
...
This allows removal of a workaround which allowed ACTION_REQUEST_VERSIONINFO
to be used in connected state (instead of initialized state)
2015-08-07 22:07:48 +02:00
fe11e6d306
Some BTLE cleanup:
...
- the BASE_UUID is shared between all BTLE devices, not miband specific. So are the UUID DESCRIPTORS. Hence these have been moved to AbstractBTLEDeviceSupport
- the gatt-characteristic-property-constants used previously in MiBandNotifyAction are also general, and exposed by the gatt subsystem, hence the specific action has been dropped moving the logic to the NotifyAction class
- the logic for checking the gatt-characteristic-property-constants has been extended also to the ReadAction and WriteAction class, this way we won't try to read (or write) a characteristic that isn't readable (or writeable)
2015-08-07 16:59:52 +02:00
6125594703
Various changes related to INITIALZED device state
...
Due to a bug in DeviceCommunicationService.isConnected(), devices using the
INITIALIZED state only worked when they had useAutoConnect set to true (Mi Band)
Now setting devices to INITIALIZED state to allow any action send to
DeviceCommunicationService is mandatory. As an exception only
REQUEST_VERSIONINFO will be also be allowed for CONNECTED state.
This also fixes a problem when notifications came in on the Pebble with 3.x
FW before we actually knew it was FW 3.x (INITZALIZED state on the Pebble
now implies that we know the FW version)
2015-08-07 13:24:54 +02:00
ce7b42d9d4
Some theme cleanups and preparations for a dark theme
2015-08-07 11:49:25 +02:00
9004a8b0c1
Experimental: ACTION_START is now optional -- ACTION_CONNECT is sufficient
2015-08-06 23:17:41 +02:00
f4cb798977
Extract a method for easier reuse if necessary
2015-08-06 22:24:44 +02:00
64298fc9af
Small improvements for the install activity #30
...
Now starts the service if not already running
2015-08-06 21:35:00 +02:00
2a2eae068a
Improvements to the install activity #30
...
- made it independent of Mi fw and Pebble fw + app classes
- automatically connect to the last used device
- some other small fixes/improvements
2015-08-06 02:17:38 +02:00
8dee55198e
Don't (always) leak the file descriptor.
...
It's still very much possible to leak the descriptor (when an exception occurs
somewhere in between or anything else goes wrong). So maybe the whole thing
should be redesigned to be independent of files.
2015-08-06 00:45:07 +02:00
b7223c7e86
Initial support for transaction-local GattCallbacks (not used yet)
...
So that we won't have to mix everything in MiBandSupport
2015-08-05 23:26:09 +02:00
495a8cc650
Reorder the lines in the MiBandService class.
...
No functional changes, just clarity enhanchement.
2015-08-05 17:32:02 +02:00
65fc6f6866
Adapt the Firmware installer activity to the new FirmwareHelper
2015-08-05 17:31:11 +02:00
e92c9dbbb5
Better check for fw version major ( #30 )
2015-08-04 23:08:40 +02:00
910d9ef398
Make firmware reading a bit more failsafe #30
2015-08-04 23:02:36 +02:00
bdc9e70e6e
Attempt to fix reconnection problems after being away from the Mi Band
...
*untested*
2015-08-04 22:03:10 +02:00
c407ed1a76
Last refactoring for now: BluetoothCommunicationService
...
- rename to DeviceCommunicationService
- move all bluetooth related bits into separate DeviceSupportFactory
class
2015-08-04 01:01:14 +02:00
db4261e02b
More refactoring: new service/devices package and service/bt package
2015-08-03 23:51:53 +02:00
7c597b325a
Big refactoring: move classes and packages around to get a better structure
...
- model package contains mostly shared interfaces (UI+service), not named GB*
- impl package contains implementations of those interfaces, named GB*
the impl classes should not be used by the service (not completely done)
- the service classes should mostly use classes inside the service and deviceevents
packages (tbd)
Every device now has two packages:
- devices/[device name] for UI related functionality
- service[device name] for lowlevel communication
2015-08-03 23:09:49 +02:00
afc4c9efaa
Added some javadocs
2015-08-03 18:35:58 +02:00
c798cd00fe
Prevent tearing of the barchart values over other graph elements
2015-08-03 18:34:58 +02:00
94b9736a5d
actually bump version
2015-08-03 09:15:32 +02:00
1b1d60faa8
Updated
2015-08-03 01:36:54 +02:00
e9f693942a
Updated translations from transifex (thanks!)
2015-08-03 01:29:06 +02:00
802f48011d
Refactoring of database access
...
- the db is now exclusively locked for one thread
- the charts read from the db and analyze data in a background thread
+ some small cleanups
2015-08-03 01:21:44 +02:00
9ca595a5cb
Some javadocs
2015-08-02 00:12:21 +02:00
216cdad591
update CHANGELOG.md
2015-07-31 16:19:32 +02:00
46ee5a5499
Send the wear location (left hand / right hand) to the MiBand.
2015-07-31 16:19:32 +02:00
69ddead8fb
Reorder the COMMAND_ constants so that they are in numerical order
2015-07-31 16:19:03 +02:00
5b3510fade
Update the firmware-update notification based on the feedback we get from the band.
2015-07-31 16:18:09 +02:00
2208d5088b
Remove the timeout and handle the messages that the band sends back to acknowledge its status.
...
This should make the firmware transfer much more reliable and hopefully release-ready.
2015-07-31 12:30:42 +02:00
fbbc2afda4
Add a timeout of 1 second before rebooting after firmware update.
2015-07-31 11:28:03 +02:00
0a6dc8f7a0
Double the filter sections for opening pebble apps/firmwares and miband firmwares
...
There are some inconsistencies across ROMs: some need the mimetype filter to be present in order to match the file extension, other refuse to do so if the filter is present. Current strategy is to satisfy both requirements by duplicating the filter element.
2015-07-30 17:14:44 +02:00
e4ddbf4aaa
Update CHANGELOG.md
2015-07-30 11:58:38 +02:00
0eeb5a6479
PebbleGadgetBridgeSampleProvider: properly override getID()
2015-07-29 23:28:10 +02:00
878afd79df
Allow the user to set the target number of steps for each day (fitness goal), both in the sharedpreferences and in the MiBand.
...
The value is then used in the graphs.
#31 #44
2015-07-29 18:49:16 +02:00
27669761bf
Fix potential race condition when counted steps are above the daily target.
...
Also added a few comments wrt the labels and the values of the pie chart.
2015-07-29 18:07:35 +02:00
3ed4856bf6
Update CHANGELOG.md
2015-07-29 17:31:53 +02:00
c05cfc775e
New chart showing the steps done today and in the last week.
...
#31 #44
2015-07-29 16:30:19 +02:00
f51ffcf16f
Use animated upload icon for installation progress notification
...
Also fix a bug which caused the main gadgetbridge service notification to be reused for the installation notification
2015-07-28 23:10:21 +02:00
1bef702485
Send the progress updates from the actual BT transfer, which is where most of the time is spent.
2015-07-28 22:38:52 +02:00
Andreas Shimokawa