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
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
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
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
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
23f752dc20
New firmware tested.
2015-07-28 22:03:53 +02:00
14f754306d
Use a single queue for the whole firmware transfer.
...
At the moment the progress bar code is not useful because the FW preparation is almost instantly done, and is the BT transfer that takes time.
The transfer happens when the getQueue method is called, and there is no progress info that I can find.
2015-07-28 19:15:25 +02:00
732f26823b
move installer progressbar from PebbleIoThread to GB and use that for Mi Band fw installation
2015-07-28 18:44:54 +02:00
9f591ef8b5
Refactoring: Merge Pebble app/fw installer activity and Miband firmware update Activity
2015-07-28 17:30:20 +02:00
c3853c7735
Merge remote-tracking branch 'origin/firmware_update'
2015-07-28 16:21:57 +02:00
858c962dd0
Refactoring #45
...
- add some device and db independent model interfaces for activity samples
- use these model interfaces where possible
- chart activity does not do device dependent rendering anymore and uses
normalized values for all devices
- initial interface for daily summaries
2015-07-28 00:05:05 +02:00
91b8d7789d
Pebble: improvemnts for upcoming Gadgetbridge Pebble watchapp
2015-07-27 23:21:06 +02:00
dbbcf20bbc
reformat code
2015-07-25 21:52:52 +02:00
47cbf68c37
Merge remote-tracking branch 'upstream/master' into firmware_update
2015-07-25 21:36:46 +02:00
8f840df5f6
Set GB notification visibility to public.
...
This way on android 5 the status of the connection is shown also on the lockscreen even if the user chose to hide sensible content of the notifications.
2015-07-25 21:14:18 +02:00
716bbc7b78
Avoid NPE when fetching activity data:
...
java.lang.NullPointerException: Attempt to write to field 'int nodomain.freeyourgadget.gadgetbridge.miband.MiBandSupport$ActivityStruct.activityDataHolderProgress' on a null object reference
at nodomain.freeyourgadget.gadgetbridge.miband.MiBandSupport.flushActivityDataHolder(MiBandSupport.java:748)
at nodomain.freeyourgadget.gadgetbridge.miband.MiBandSupport.handleActivityNotif(MiBandSupport.java:689)
at nodomain.freeyourgadget.gadgetbridge.miband.MiBandSupport.onCharacteristicChanged(MiBandSupport.java:583)
at nodomain.freeyourgadget.gadgetbridge.btle.BtLEQueue$2.onCharacteristicChanged(BtLEQueue.java:369)
2015-07-25 00:09:24 +02:00
a1f60aab91
Fix logging configuration
...
Make sure to not invoke any logging before it is properly configured.
2015-07-25 00:09:24 +02:00
49cc4ec9d6
Pebble: for 3.x notification, do not zero parent UUID
...
instead reuse the same reandom UUID again.
2015-07-24 09:33:20 +02:00
91cc19befe
Pebble: spoof a newer application version (3.x)
2015-07-24 01:34:50 +02:00
f16a96e9b2
Initial support for upgrading firmware of the MiBand.
...
This release seems to be working quite well with respect to the firmware upgrading itself. The user facing part needs more work.
In order to update the firmware one has to:
- open a file ending with .fw
- switch from the firmware upgrade activity to the main one
- connect to the miband
- return to the firmware upgrade activity
- press the "install" button (that became active when the device connection was established)
Caveats:
There are almost no check wrt. the integrity of the firmware files.
2015-07-23 17:14:51 +02:00
844d929748
update remaining languages from transifex
...
Please fix the removed strings on transifex. Some of them might have been removed because the original english string has been changed.
2015-07-23 16:00:36 +02:00
69f4b11594
update Korean translation from transifex
2015-07-23 15:56:47 +02:00
268e658e6f
rename ACTION_INSTALL_PEBBLEAPP to ACTION_INSTALL
2015-07-23 12:09:01 +02:00
5c26b2281f
Pebble: try to support notification dismissal on the Pebble Time (completely untested)
2015-07-22 20:53:18 +02:00
80e93aeaf7
update CHANGELOG, bump version to 0.4.4 (not yet release time)
2015-07-21 22:55:26 +02:00
34dde2eb64
Eek
2015-07-21 22:30:11 +02:00
383a300566
Remove superfluous field
2015-07-21 22:29:29 +02:00
76fcbfcb52
Move activity data values into a separate struct ( #45 )
...
- saves some memory
- allows us to show the toast for the first chunk only
2015-07-21 22:27:15 +02:00
b3a04f7afb
Pebble: more length calculation fixes for 3.x notifications with actions
2015-07-21 22:05:25 +02:00
6c1e41b4ec
Pebble: fix some totaly obvious length calculation errors for actionable 3.x notifications
2015-07-21 21:56:11 +02:00
3662f32dbf
Remove duplicated constants
2015-07-21 21:42:04 +02:00
3590c7c853
Remove inadvertently re-added busy-state handling
2015-07-21 21:40:06 +02:00
3c35f94a7e
Pebble: enable dismiss action on FW 3.x if force option is set
...
NOTES:
- Might break notifications altogehter (can't test)
- Cannot work because we do not interpret the response yet.
2015-07-21 21:32:05 +02:00
1f2b0329c5
Misc improvelets ( #45 )
2015-07-21 21:24:35 +02:00
c9ab10e7e8
Pebble: commit missing PebbleProtocol changes for experimental notification dismissal
2015-07-21 01:33:13 +02:00
74e1598bf7
Pebble: add experimental and incomplete support for dismissing 2.x notifications
...
Currently this dismisses all notifications on the Phone-
2015-07-21 01:27:05 +02:00
0f6491a11d
More WIP: sync from the charts activity
...
Also add preliminary buttons to go forward/backward in time.
2015-07-21 00:06:20 +02:00
13d2c2166c
Let DeviceCoordinator decide which activity to launch on click
2015-07-20 23:57:01 +02:00
184e0f2dea
New dependency to format durations (and use that where applicable)
2015-07-20 23:14:08 +02:00
4aa80c149c
Add some code to set the Mi Band latency
2015-07-20 21:43:23 +02:00
5d121e6e8f
Fix a pointer aliasing issue, add some constants, remove invalid "checkpointing"
2015-07-20 21:41:18 +02:00
d967411d70
Add a toast to let the user know about the progress of the transfer.
2015-07-19 16:16:58 +02:00
6953086c99
Allow setting alarms once for the next day.
...
(cherry picked from commit 417ea02)
2015-07-19 15:58:30 +02:00
7f7cea75c1
Spare some complexity by letting the writer change the status to non-busy.
...
Before the code looked for the values written to the device with another method.
2015-07-19 15:52:27 +02:00
f847d834af
Pebble: always force 3.x notifications on FW 3.x
2015-07-19 00:26:43 +02:00
e6bc406d98
Fix funny typo :D
...
Thanks to @girlwithnoname for spotting
2015-07-18 23:38:59 +02:00
095c70d469
Pebble: preparations for WIP Gadgetbridge Pebble App
2015-07-15 00:33:44 +02:00
d498bd976a
Work in progress #45
...
Comparison between Light Sleep and Deep Sleep.
(Currently wrong, needs more analysis)
2015-07-14 00:29:32 +02:00
b1e2671bec
limit maximum intensity to 180 for now... maybe make this configurable #45
2015-07-13 21:55:52 +02:00
04e628b2d1
Separate fragments for all activity kinds and just sleep #45
2015-07-13 21:54:46 +02:00
8b44f90bb6
Some more refactorings to support different charts
2015-07-12 23:42:23 +02:00
f53a037d7f
Use query instead of rawQuery
2015-07-12 21:50:09 +02:00
623e4724c2
Slightly better text when no data available
2015-07-12 21:48:48 +02:00
47c43e9c28
Debug Activity: Fix layout for small screens and landscape mode
...
Fixes #84
2015-07-12 20:06:47 +02:00
6553558947
Experimental code for an activity sync problem. Commented out for now. #45
...
@daniele do you have an idea what this byte equence on the control point
characteristic could mean (and why the transfer stops then)?
2015-07-12 00:02:51 +02:00
b516ceda01
Support for displaying Toasts from non-ui threads
2015-07-11 21:49:51 +02:00
be45f7fe0c
check if table exists before dropping
2015-07-11 21:16:07 +02:00
a6e26e5ddc
Cleanup, use fragment based charts (WIP #45 )
...
Known issue: scrolling a zoomed-in chart interferes with swiping to the
next/previous chart (so far there's just one, but...)
Workaround: Swipe down and then left or right in one go, this will let
you scroll the zoomed chart
2015-07-11 00:03:41 +02:00
7c61bbb2be
Logging to find the cause for seldom device state/notification mismatch
2015-07-10 21:35:28 +02:00
40be935abd
Better time format for action logging
2015-07-10 21:02:03 +02:00
Andreas Shimokawa