more reliable reconnection to Pebble: Pebble status notification will stay in notification area more consistently
improved detection of already paired Pebbles
New in 1.9.1:
Onboarding will be skipped if you have a previously paired device.
Added an settings to indicate that onboarding should always be skipped.
Known issue: there are some phones which will not reliably detect that a Pebble (or other Bluetooth device) has been paired.
If this happens, just hit the back button on your phone to skip onboarding.
If you skip onboarding by pressing the back button, a dialog will prompt to ask you if you want to always skip onboarding.
Fixes for crashes
What's New in 1.9.0
Added new introduction and setup screen.
Getting started with Pebble is now easier. No need to go to the Android Bluetooth settings; everything you need is right in the app
Fixes carried over from v1.8.2
Enable Google Hangout notifications
Google changed the way it sends notifications and the Pebble app was unable to see them, until now. Users on phones with a version of Android before 4.1 (JellyBean) won't be able to see the message bodies on Pebble if there's more than one unread notification. There is no workaround for this—Google only provides the information using an API available in Android 4.1 and later. Known issue: we exclude sending Hangout requests to the watch—it's not possible to easily track those for this release.
Fixes crashes logged in previous versions
Sometimes the Update Firmware/Install App UI would crash as it came up.
Invalid application info messages sent by Pebble will be logged and not crash the Android app.
Fixes issues reported by developers
Don't squash app transaction IDs
Send proper, unsigned transaction IDs from Pebble to apps
Fixes carried over from v1.8.1:
Repaired issues with Gmail notifications
At some point 4 months ago, we stopped sending all email notifications to the watch and only sent the last message if more than one email arrived since the last notification. Now we send up to 10 emails per notification. Gmail login tokens were sometimes expiring super-quickly, causing delayed message receipt. This is resolved.
The mail library would stop working, causing dropped notifications. This is resolved.
Starting in 1.8.0, in order to receive Gmail notifications, we require that the device has Google Play installed (this is Google's supported way of allowing Android apps to log into Gmail). If Google Play is not installed, we prompt the user to install it (or upgrade if Android Market is present on the device). On Android 2.3 devices, the prompt was not functioning. This is resolved.