It seems that something on the hardware or software side went bad. Where I first could get almost 8 days out of my watch on normal/heavy use, now seems like 2 or 3 (or 4?) days on normal/heavy use. For information about the current software, see Software
I contacted Pebble support and they asked me to test this with the following steps. The results are further on this page. After that I will send this to Pebble to verify what is wrong.
To identify the root cause follow the steps below:
- Charging pebble to 100%
- Perform factory reset
- turn off Bluetooth in the watch
- record start date and time
- Date and time are in CET:
dd/mm/yyyy hh:mm - let it run 3 days, and record state
End of Test
On the graph below is a data plot from the collected data. The parts that are missing are via interpolation extracted from the sampled data. The data from the graph are shown in the graph below.
| Nr (#) | Day | Date (dd/mm/yyyy) | Time (hh:mm) | Time from start (m) | Battery (%) |
|---|---|---|---|---|---|
| 1 | 0 | 12/03/2016 | 18:30 | 0 | 100 |
| 2 | 0 | 13/03/2016 | 00:50 | 380 | 90 |
| 3 | 0 | 13/03/2016 | 12:10 | 1060 | 80 |
| 4 | 0 | 13/03/2016 | 14:30 | 1200 | 80 |
| 5 | 0 | 13/03/2016 | 17:30 | 1380 | 80 |
| 6 | 1 | 13/03/2016 | 23:30 | 1740 | 80 |
| 7 | 1 | 14/03/2016 | 8:30 | 2280 | 70 |
| 8 | 1 | 14/03/2016 | 14:50 | 2660 | 60 |
| 9 | 1 | 14/03/2016 | 17:00 | 2790 | 60 |
| 10 | 2 | 14/03/2016 | 18:30 | 2880 | 60 |
| 11 | 2 | 14/03/2016 | 20:40 | 3010 | 60 |
| 12 | 2 | 14/03/2016 | 22:00 | 3090 | 60 |
| 13 | 2 | 14/03/2016 | 23:00 | 3150 | 50 |
| 14 | 2 | 15/03/2016 | 00:30 | 3240 | 50 |
| 15 | 2 | 15/03/2016 | 2:15 | 3345 | 50 |
| 16 | 2 | 15/03/2016 | 8:50 | 3740 | 50 |
| 17 | 2 | 15/03/2016 | 9:00 | 3750 | 40 |
| 18 | 2 | 15/03/2016 | 10:00 | 3810 | 40 |
| 19 | 2 | 15/03/2016 | 13:30 | 4020 | 40 |
| 20 | 2 | 15/03/2016 | 15:30 | 4140 | 40 |
| 21 | 3 | 15/03/2016 | 18:30 | 4320 | 40 |
| 22 | 3 | 15/03/2016 | 19:50 | 4400 | 30 |
Here are some notes per day or the steps taken that day if necessary.
Start of the test.
-
Watch is fully charged
-
Reset the watch
-
Connecting with phone
- Updating watch
- initial setup like language
-
Pebble watch settings:
- vibration disabled
- backlight off
- background app: none
- airplane mode enabled
- Time to 24H mode
-
disconnecting cable, pebble is now on battery [see
#1in table]
After going down to 30% [see #22] I decided to stop the test.
The data collected thus far gives enough insight on the battery discharge rate over time. The data collected in this test is listed in the table. I can only speculate for a conclusion, so don't quote me. The problem doesn't seem to lie with overly active connection with a phone, display or vibrating motor? These options where all disabled. My guess is that the problem lies in the software of the pebble? I will send this to the pebble customer support and will update this gist if necessarily.
A few days after sending my results, I got a response. The pebble was possible stuck in high Bluetooth battery usage. When I gave them my adders they send me a new one. After I received my replacement, I was asked to send the old one back. Of course I was very happy with this conclusion and I thank Pebble for that!
Some information regarding the current running software.
Fields containing xxx are put there for privacy reasons
Android Info:{
"androidOsVersion":"5.0.2",
"deviceBrand":"XXXXXXX",
"deviceKernel":"XXXXXXX",
"deviceManufacturer":"XXXXXXX",
"deviceModel":"XXXXXXX",
"androidSdkVersion":21
}Pebble-Android Info:{
"appVersion":"3.9.1-966-bc5f043",
"buildFlavor":"prod",
"buildType":"release",
"areNotificationsEnabled":true,
"calendarPermission":true,
"contactsPermission":true,
"locationPermission":true,
"overlayPermission":true,
"phonePermission":true,
"smsPermission":true,
"storagePermission":true
}Last connected device info:{
"capabilities":{
"mCapabilities":[
true,
true,
true,
true,
true,
true,
true,
true,
true,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false,
false
],
"support8kAppMessage":true,
"supportsAppRunStateProtocol":true,
"supportsExtendedMusicProtocol":true,
"supportsHealthInsights":true,
"supportsInfiniteLogDump":true,
"supportsLocalization":true,
"supportsSendTextApp":true,
"supportsTwoWayDismissal":true
},
"color":"COLOR_BOBBY_BLACK",
"connectionGoal":"CONNECT",
"connectionStatus":"CONNECTED",
"currentRunningApp":"07e0d9cb-8957-4bf7-9d42-35bf47caadfe",
"fwVersion":{
"mVersionTag":"v3.9.2",
"mTimestamp":1454955428,
"mMajor":3,
"mMinor":9,
"mPoint":2
},
"hwPlatform":"PEBBLE_BOBBY_SMILES",
"hwRevision":"smiles12",
"isoLocale":"en_US",
"pebbleDevice":{
"mAddress":"XX:XX:XX:XX:XX:XX",
"mName":"PEBBLE TIME XXXX",
"mRssi":-44
},
"recoveryFwVersion":{
"mSuffix":"prf",
"mVersionTag":"v3.0.3-prf",
"mTimestamp":0,
"mMajor":3,
"mMinor":0,
"mPoint":3
},
"serialNumber":"XXXXXXX",
"lastConnectedTimeMillis":1456991779916,
"healthInsightsVersion":2816,
"isRunningRecoveryFw":false,
"languageVersion":1
}
