27a9eb8a07
Only repaint chart when activity is still alive
...
(fixes error message when synchronizing in the charts activity and then
switching orientation)
2015-08-16 23:27:18 +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
567f27b0f4
Some initial fixes found by static analysis #92
2015-08-16 00:17:16 +02:00
929831e4f0
Add travis-ci badge #92
2015-08-15 23:21:42 +02:00
5e233f6eb9
First attempt at travis-ci integration #92
2015-08-15 23:02:39 +02:00
3486b5ab69
Static code analysis: run findbugs, pmd and lint at 'gradle check' #92
...
As a start, the build won't abort on any serious errors.
2015-08-15 23:02:38 +02:00
a5e009b371
update changelog
2015-08-15 22:46:04 +02:00
a2e2600469
Bump version to 0.4.6
2015-08-15 22:41:29 +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
4ba5a7804a
Updated for 0.4.6
2015-08-15 12:08:30 +02:00
b6f66eb57c
Updated translations from transifex, thanks!
2015-08-15 11:42:33 +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
f659e34efc
Pebble: do not use platform dir for pbz(firmware) files, even basalt has its files in / for fw files
2015-08-14 17:32:06 +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
2e3de0cd0f
Always send out the current state of GBDevice when asking for version
...
In a second step, request the version from the device (and send updated
values then)
RequestVersionInfo is either a misnomer or misused, depending on your view.
It is actually used by activities to get the current state of thde device.
We now provide this as quickly as possible, with the drawback of sometimes
sending results twice.
2015-08-14 00:29:05 +02:00
eec7fae288
Attempting to fix some connection problems after getting disconnected
2015-08-14 00:23:01 +02:00
eb2332c8be
Some preparations for unit tests
2015-08-13 23:23:40 +02:00
749fbe5ecc
Pebble: fix crash with emply pbw cache
2015-08-13 10:06:32 +02:00
6ed54484a6
Pebble: only fill app list in AppManager with cached apps once in onCreate()
...
This is important for FW 3.x testing, since the REFRESH intent
will never arrive and we want to see cached watchapps
2015-08-11 14:16:08 +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
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
cpfeiffer