e6a0c35f73
Extract checksum implementations into separate class CheckSums
2015-08-17 22:43:42 +02:00
6fede31bdf
Pebble: make watchapp installation available on FW 3.x without the need for setting an option
2015-08-17 18:07:47 +02:00
9dd2f039f2
Rename AbstractBTDeviceSupport to AbstractSerialDeviceSupport
...
That way it also fits devices connected via TCP/IP for example.
2015-08-17 16:30:12 +02:00
8fee88a1ba
Pebble: use SMS/EMAIL icons for notifications on FW 3.X
2015-08-17 13:57:01 +02:00
e704357728
Pebble: set HW revision to "dvt" for basalt emulator
2015-08-17 13:19:15 +02:00
c8c882c3d1
Pebble: Support removing apps on FW 3.X (metadata)
2015-08-17 13:07:34 +02:00
f0924716fc
Pebble: when reading app fetch uuid, do not switch to little endian too early
2015-08-17 12:55:17 +02:00
0d0b3a87e1
Pebble: on FW 3.x always assume success for installation and do no wait for 2.x packets
2015-08-17 12:43:38 +02:00
bcf42f8022
Finally, the prev and next buttons do something ( #79 )
...
Far from perfect, but a start.
2015-08-17 02:22:16 +02:00
0bd65e050c
Make intensity also always positive #91
...
I never experienced such values, but others apparently do...
2015-08-16 23:18:32 +02:00
48f5931043
PebbleProtocol: add missing assignment
2015-08-16 13:13:53 +02:00
6af0bb2754
Pebble: Do not hardcode icon id for metadata installation, properly acknowledge app fetch requests
2015-08-16 11:33:32 +02:00
a4f5524f6e
Pebble: blindly implement missing parts for app installation on FW 3.x
...
This is expected to fail and needs to be enable in preferences (untested features).
2015-08-16 00:32:36 +02:00
c69bf1b0af
Pebble: always use 2.x notification on FW 2.x except for K9
...
FW 2.x notifications enables the "dismiss all" action, but for K9 we would loose
the mail icon. So K9 still needs the force option.
2015-08-15 22:38:10 +02:00
a66a3a15c2
Fix remaining byte parameter in the API for steps.
...
Maybe this was the reason for #91 (negative steps)
This could happen making at least 3 steps per second.
2015-08-15 00:23:13 +02:00
ecc483f027
Remove now unused class
2015-08-14 23:50:21 +02:00
d0229847e7
onFirmwareVersionReq() is no more
...
- version information is now provided implicitly by device initialization
- ACTION_REQUEST_VERSIONINFO is now ACTION_REQUEST_DEVICEINFO and it will
return the current device state of the service without asking any DeviceSupport
instance.
- ACTION_CONNECT now implicitly answers with a device update intent if it
IS already connected.
2015-08-14 23:37:47 +02:00
f5fbb08696
Pebble: remove unneccessary device update intent (this is done in generic code)
2015-08-14 13:46:37 +02:00
e28d6fa7cb
Pebble: try to install app metadata on FW 3.x (untested)
2015-08-14 12:51:30 +02:00
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
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
d983d7a5c4
Pebble: answer pings from the watch
2015-08-09 21:42:27 +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
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
910d9ef398
Make firmware reading a bit more failsafe #30
2015-08-04 23:02:36 +02:00
db4261e02b
More refactoring: new service/devices package and service/bt package
2015-08-03 23:51:53 +02:00
cpfeiffer