cd84b891d9
micro cleanup
2016-09-05 00:17:34 +02:00
ce175c2952
Test SampleProvider (MiBand for a start)
2016-09-05 00:10:38 +02:00
2e91246a45
Make sure that every Test class has at least one @Test method, or is abstract
2016-09-04 22:52:55 +02:00
411a90326e
Fix method name
2016-09-04 22:39:35 +02:00
2c27f30575
Some testcase infra
2016-09-04 22:10:35 +02:00
549c05cd0d
Remove a slightly too technical entry
2016-09-04 21:44:28 +02:00
7c1ddc7f82
Added Mi changelog + some rewordings
2016-09-04 21:20:42 +02:00
f030a1bdea
update italian from transifex. Thanks Daniele ;)
2016-09-04 18:37:06 +02:00
aa2d37c76b
Small changes to the DB management activity #UX
2016-09-04 16:20:50 +02:00
5cbedc782d
Pebble health: accept records of firmware 4.0 (nothing changed among the data we parse)
2016-09-04 15:59:19 +02:00
41b20b8c57
update French translation from transifex (thanks!)
2016-09-04 11:28:12 +02:00
8e154ca67d
slightly more testing of Device/Attributes
2016-09-03 21:16:45 +02:00
044c9ed101
Update CHANGELOG.md
...
Add mention of the fact that data migration is not automatically performed as first point.
Added database management activity
Fix typo and add clarification about data migration
2016-09-02 12:10:56 +02:00
36b03e92b3
update changelog (in progress, incomplete)
2016-09-02 11:57:58 +02:00
5a49f1215e
Display known devices from db even if Bluetooth is off or unsupported
...
This allows to view activity data without turning bt on or connecting to the pebble emulator via tcp/ip (needs modified manifest for internet access)
2016-09-02 10:54:32 +02:00
6f02f9e350
Unit-Test and fix *Attributes sort order
...
When adding e.g. new DeviceAttributes, we cannot simply add them to the
attributes list, because that list is supposed to be ordered. We could
insert it at the beginning, but that would be brittle to changes in the
GBDaoGenerator, so we simply re-fetch them from the db after adding
new attributes.
2016-09-02 00:34:30 +02:00
507338d034
TODO: One down, but two more to go.
2016-08-31 17:36:01 +02:00
1e6cb67edd
UI refactoring of the DB management activity.
...
Added a method to delete the legacy DB only.
2016-08-31 17:35:28 +02:00
e230bd1d07
Fix reference to the DB management activity
2016-08-31 15:27:31 +02:00
6a2043eeb7
Create DB management activity by taking the existing functionalities from the debug activity.
2016-08-31 15:12:26 +02:00
84e644fa1a
Add preference for save raw pebble health data.
2016-08-31 14:05:02 +02:00
cd535a0a45
Include known devices from the database in CC
...
(as long as device-support is still available)
Fixes non-paired devices not being displayed
2016-08-31 00:33:54 +02:00
6340bcff15
Small cleanup
2016-08-31 00:03:20 +02:00
d9283d0f22
Sigh. Fix LoggingTest on Travis
...
When running all tests from gradle, they are executed in a single VM,
and from a quick look it is not configurable to start LoggingTest in
a separate VM (in order to enforce fresh logback configuration).
Thus, previously started tests interfere with the custom logback
configuration of LoggingTest.
=> Set the logback configuration in advance in build.gradle
2016-08-30 01:25:43 +02:00
b96f2ed301
Apparently that was too much output for travis...
2016-08-30 00:18:31 +02:00
29dc5daa43
try to get more output from travis
2016-08-30 00:06:34 +02:00
031a683215
update russian translation from transifex (thanks!)
2016-08-29 23:54:33 +02:00
854b925c17
add hint about importing data later in onboarding activity
2016-08-29 23:46:33 +02:00
7c2bc3804c
updated
2016-08-29 01:01:06 +02:00
93b165ee96
onboarding: use the text area not the button itself for displaying the info text ;)
2016-08-29 00:32:36 +02:00
bcb07ccacd
Enable LoggingTest with robolectric
2016-08-29 00:26:29 +02:00
c93186cc56
fix name of onboading activity
2016-08-29 00:23:48 +02:00
07ee860b1c
add information to onboarding activity, make strings translatable
2016-08-29 00:17:40 +02:00
c55369747d
launch onboarding (database migration) activity from service when:
...
- device got initialized
- is not yet in the new device db
- an old database exists
2016-08-28 23:49:05 +02:00
eb7771c1a9
Support for overlapping ActivityDescriptions + testcases
2016-08-28 00:22:34 +02:00
ca6b51b435
Updated TODO
2016-08-27 23:41:09 +02:00
39c7762416
Update the device in case it has changed
2016-08-27 23:25:37 +02:00
1a22259b4e
Good practice: use the DAO to insert/update instead of the session
...
(saves a few cycles to look up the correct DAO from the session)
2016-08-27 23:12:48 +02:00
840a125c81
Fix compilation
2016-08-27 22:55:00 +02:00
8d6e6c8675
Upon request, delete not only the old, but also the new database
2016-08-27 22:51:00 +02:00
ae2df2580c
Remove/document deprecated stuff
2016-08-27 22:45:27 +02:00
e139840fee
More appropriate user handling: update the user instead of creating new
2016-08-27 22:34:30 +02:00
c879e1c063
Update to gradle android plugin 2.2-beta3
2016-08-27 22:33:42 +02:00
bfaaed7e5c
Detcach samples from the session after querying, to save memory
2016-08-27 21:40:46 +02:00
fb30321cca
Add missing @Override and extract some constants
2016-08-27 21:17:34 +02:00
083d752011
Even more documentation/specification
2016-08-27 20:14:42 +02:00
c2a509be74
Updated TODO
2016-08-27 17:22:55 +02:00
ec9e999be1
Lots of documentation
2016-08-27 16:44:47 +02:00
ec0db033b1
Avoid potential NPE when subclasses return null for rawKindSampleProperty
2016-08-27 15:36:42 +02:00
350e72d534
Initial support for user-configured activity descriptions
...
- for a given user and time span, there may be an ActivityDescription
- with a textual description
- and a list of tags
- every tag has
- a name
- and an optional description
2016-08-27 00:25:45 +02:00
cpfeiffer