Lastest version : Pebble Changelog
Pebble Firmware 2.4 (Release Notes)
Fix a potential crash when using scroll layers or animations
Added support for realloc
Added a gbitmap_create_blank function to create empty bitmaps of a fixed size
Added number_window_get_window()
Fixed a crash with atan2_lookup when high input values were used
Fixed a bug where TupletInteger could not be used with unsigned integers
Fixed several bluetooth reliability issues
Fixed a case where the "Setup notifications" banner would erroneously show in the iOS Pebble app
Fixed a bug with the music app where media playing faster than real time could not be paused
Fixed a bug where the notifications view could show a rapidly increasing counter for number of notifications when first displayed
Fixed a bug where switching watchfaces could cause the same watchface to be relaunched
Pebble Firmware 2.3 (Release Notes)
Improved Bluetooth LE connectivity.
Added the ability to skip to the next notification with a double-click of the Down or Up buttons.
Bug fixes and stability improvements.
v.1.14.1 - Date: 11 Dec 2013
What's New
New "Do Not Disturb" feature: schedule the times you do not want to be disturbed by notifications.
Updated "Alarms" app: create multiple alarms, toggle alarms on/off and edit them.
New "Snooze Alarm" feature, customizable via the Alarms app.
Finer control over what notifications are displayed: Notifications On, Phone Calls Only or Notifications Off.
Notification settings are now accessible more quickly through a dedicated menu in the Settings app.
iOS 7 notifications now arrive more quickly on Pebble.
Bug Fixes
Fixes an issue where the Pebble may enter "recovery mode" immediately after updating to 1.13 software.
Fixes an issue affecting some iOS customers where the Bluetooth connection would be dropped after a few seconds.
Fixes a problem where phone calls would not get displayed any more after having received a missed call.
Fixes issues where Bluetooth transport would become unreliable (particularly during a firmware update).
Sometimes the Pebble would keep on vibrating after dismissing a phone call. This has been resolved.
After exiting Airplane Mode, the Pebble will now immediately attempt to reconnect to iOS devices, instead of waiting a minute first.
Click to expand...
Click to collapse
v.1.13.0 - Date: 11 Nov 2013
What's New
Adds support for Apple Notification Center Service (ANCS) notifications for iOS 7 users with iPhone 4S, iPad 3, iPad mini or iPod Touch 5 or greater (requires Pebble iOS app 1.3 or greater). See help.getpebble.com for more information on setting up iOS7 notifications. * The Pebble now can show >80 unread notifications, up from 8 previously. Bug Fixes ----------
Issues when receiving a phone call around not showing caller-ID, dismissing a call when pressing the back button, or continuing to vibrate, have been fixed.
New iOS users no longer need to manage access to their address book in order to see Caller ID on their Pebble.
Sometimes settings would be lost when the Pebble was rebooted. This issue is fixed.
Click to expand...
Click to collapse
v.1.12.1 - Date:16 July 2013
What's New
Bug Fixes
Fixed a problem that caused the phone app to disconnect immediately after a firmware update.
Click to expand...
Click to collapse
v.1.12 - Date:2 July 2013
What's New
The backlight now turns on momentarily when a charger is connected.
Lots of goodies for watchapp developers that will be unlocked when the new version of PebbleKit is released.
Bug Fixes
Fixed subject/sender cutoff in notifications with long subjects/senders.
Fixed motion backlight from sporadically not working.
Fixed factory reset to disable the QC app and perform the reset.
Fixed long click release after changing the action bar icon.
Fixed textlayergetmaxused_size to always return the right size.
Fixed graphics draw pixel, circle, round rect to draw inside the layer.
Fixed graphics draw rect, round rect to use the stroke color.
Fixed graphics GCompOpAnd bitmap compositing mode to not have artifacts.
Fixed graphics gpath filled to not have cuts.
Click to expand...
Click to collapse
v.1.11.1 - Date:1 June 2013
this minor update fixes bugs with Sports watchapps like Runkeeper and FreeCaddie.
Click to expand...
Click to collapse
v.1.11.0 - Date: 30 May 2013
What's New
Improved Notification UI
Allows multiple notifications to be viewed if they arrive within a short time frame
Improved Set Time UI
Added the option of showing your current speed (as oppossed to your pace) in the RunKeeper application.
Swapped next and previous track buttons in the music application.
Added the Simplicity watchface.
Removed the Fuzzy Time watchface (it is available through the watchapp library).
Bug Fixes
Fixed a few issues where the bluetooth module would consume too much power.
Fixed an issue where rounded rects drawn with graphics_fill_rect did not handle being clipped properly.
Sped up text rendering when some of the text layer is clipped off the screen.
Fixed a bug where the vibrating motor would get stuck on.
Fixed a crash when changing windows, most commonly seen in the set time and set alarm UIs.
Fixed an issue where SMS messages on iOS would be incorrectly shown as an email with a very long subject line.
Click to expand...
Click to collapse
Usefull links
Watch apps :
http://www.mypebblefaces.com/?date=desc
http://allpebble.com/index.asp
Source :
http://developer.getpebble.com/getting-started/index.html Preview of next firmware and next smartphone apps
https://forums.getpebble.com/discussions
It's (almost) Software Time!
Hi Pebblers!
It’s no secret that we’ve been hard at work developing better software for Pebble and this Wednesday, November 6th, we’ll be making a very important announcement.
You’re invited to join our livestream event at 10AM PST to hear what awesome new things we’ve been working on to make Pebble a more robust and feature-rich platform. To tune in, visit https://www.getpebble.com on Wednesday morning after 9AM PST to obtain a link for the livestream. After the live broadcast hosted by Eric and our very own Thomas, we will be leading a Reddit AMA discussion at noon (12PM PST) to answer any lingering questions you may have.
Still haven’t had a chance to try out the SDK? Download the SDK, check out the documentation, and get hacking!
Click to expand...
Click to collapse
Source : http://www.kickstarter.com/projects...per-watch-for-iphone-and-android/posts/651308
Any updates on V2?
slowfuse said:
Any updates on V2?
Click to expand...
Click to collapse
What update? V2 is officially out!
alex_herrero said:
What update? V2 is officially out!
Click to expand...
Click to collapse
...but there's no mention of it in this thread as of yet.
Sent from my Nexus 4 using Tapatalk
Don't really care if listed as "out" or not. I am running it.
The previous (now deleted) posts listed the change log for v1 revisions. That would be useful/interesting.
V2.0.2 firmware updated on my Pebble.
Sent from my Nexus 7 using Tapatalk
Version 2.1 updated on my pebble
2.2 is here. Music volume control + apps reordering.
Firmware 2.4 is here
2.4.1 has just been released
Sent from my C6903 using XDA Free mobile app
2.5 has just been released
DonDragonka said:
2.5 has just been released
Click to expand...
Click to collapse
Is 2.5 mostly just emoticons and compass or are there bug fixes and/or optimizations as well?
Sent from my SGH-I747M using XDA Free mobile app
There are definitely optimizations, like this: "Fixed a bug that would cause animations between windows to be slow.", but the best new feature (dismissing notifications) is sadly iOS8 only as of now. They promised to bring it to Android in the future.
Although not a feature or fix, but I love the new Domo watchface, the animations are funny and so smooth...
The Full 2.5 Changelog
Major Changes
FW 2.5 includes an optimized version of snprintf (and related functions like APP_LOG, etc) that does not support some length format specifiers previously supported (%hh, %ll, %j, %z, %t). The list of supported specifiers has been updated in the snprintf documentation. For those of you that use these previously-supported specifiers, please do not hesitate to contact us at [email protected] and we’d be happy to assist you with updating your code.
Added compass support.
Enforced versionLabel formatting in appinfo.json in preparation for app auto updates.
Added support for Pebble app relaunch on iOS when a Pebble watch is in proximity.
Added notification dismissal support on iOS8.
Added emoji support to Pebble notifications and system fonts.
Detailed List of Changes:
Changes for Firmware:
Added functions heap_bytes_free and heap_bytes_used to view current heap memory usage.
Added support for uuid_equal and uuid_to_string.
Added function accel_raw_data_service_subscribe to get accelerometer data with a single timestamp for all samples (significantly reduces memory usage for apps that do not depend on timestamps).
Added compass support.
Added emoji support to Pebble notifications and system fonts GOTHIC_24_BOLD, GOTHIC_18 and GOTHIC_18_BOLD.
Fixed a bug that would cause a crash if a screen shot was taken while one was already in progress.
Fixed an issue where Pebble APIs would use non-reentrant versions of standard C functions causing unexpected changes to return values.
Fixed a bug with accel_service that could result in memory being freed twice.
Fixed a bug where Golf API would show stale information on disconnect.
Fixed a bug that prevented calling menu_layer_set_selected_index before menu_layer_set_callbacks.
Fixed a bug which would sometimes cause the command line logging tool to crash when a watchapp crashed.
Fixed a bug that would cause the sample rate of the accelerometer to be reset when subscribing.
Added support for Pebble app relaunch on iOS when a Pebble watch is in proximity.
Added support for notification dismissal on iOS8.
Fixed numerous bluetooth reliability & connection issues.
Fixed a reset and other various bugs related to Data Logging.
Fixed a bug that allowed backing out of FW update screen.
Fixed a bug that would cause animations between windows to be slow.
Fixed a bug where the Date UI would allow selection of invalid dates.
Fixed a bug which would prevent the down button from scrolling through notification history.
Fixed a bug with AVRCP that could lead to a crash.
Set backlight to stay on during alarm ringing.
Changed the default backlight setting to AUTO.
Fixed a bug which would allow developers to ask for more than 25 accel samples per update.
Added check for NULL parameter in gpath_draw_filled.
The middle Button can not anymore be use to dissmiss Notifications. Have to use the single back Button. This was not in the previous fw.
Skickat från min GT-I9505 via Tapatalk
@ormetkruper: That's because that will dismiss the notification. This feature is already implemented with iOS8, we just have to wait till they make it work on Android too.
anyone on 2.6 for now ? Any feedback would be appreciated
My screen starting to tear now.not sure if it is because of this update.
Sent from my Nexus 7 using Tapatalk
2.6 is a very good update, I enjoy misfit app and compas gadget no problems at all using pebblebit firmware 2.6 try it yourself.
Sent from my Nexus 5 using XDA Free mobile app
I had my Note 3 long before I picked up my Gear, and as with all things, I made some adjustments to my Note 3 software experience to improve it for my use. This has had some undesirable effects on the Gear and I just want to list out what I have done and what effects it had on my Gear for awareness so those of you who plan to make changes to your Note will know what you're getting into.
I have made the following changes to my Note 3:
Rooted
Frozen all Knox apps/services
Frozen some other misc bloat
Nova Launcher set as default Launcher
S for Switch Voice installed (overrides S Voice with Google Now and gives you a Moto X - like Touchless control)
Dynamic notifications set as default lock screen
Adway blocking ads
Samsung TTS frozen (to fix the Accessibility bug for Pebble)
I usually don't modify my devices too heavily, but I really felt like my Note needed some of this and some features (such as Dynamic Notifications and S for Switch Voice) give me a Moto X type experience that I miss when using the Note. Below are the effects I have noticed this having on my Gear:
No voice feedback for S Voice on Gear (probably due to S for Switch Voice or Samsung TTS being disabled)
Notifications delay - Because of Dynamic Notifications, if my phone is face up out of my pocket, my watch will not receive a notification until the screen turns off. This is because the display is effectively on. This isn't a huge issue because if my phone is face up and I can see it, I'm not going to read the notification on my watch anyway. Most of the time, it's when it's in my pocket that I need the Gear to step in and in those cases, the notifications are instantaneous.
Occasional network errors when using S Voice - May be due to adblock (which I will not give up).
This is all I have really noticed so far. I will update this post if I discover anything else. I hope this helps anyone considering getting a gear and/or making any of these modifications on their Note 3. Happy Gearing.
I thanked your post for showing me that "S for Switch Voice" exists. Now, if we can just get a way to stream Google Now + Audio to the watch, we'd be golden.
Does Android on the Samsung Note 9 has the ability to set more than one schedule for "Do Not Disturb". I want the "Do Not Disturb" hours schedule to be different for weekdays versus weekend.
Now possible with Android Q beta
SmsGN9 said:
Does Android on the Samsung Note 9 has the ability to set more than one schedule for "Do Not Disturb". I want the "Do Not Disturb" hours schedule to be different for weekdays versus weekend.
Click to expand...
Click to collapse
Yes, it is now possible through Android Q beta. Scheduling the same default configuration of DND for different times and days is possible.
However, it is still NOT possible to configure customized DND behaviour for the schedules, like example, I want total silence from midnight to 5 am but calls from starred contacts only during 6 pm to midnight.
Separate settings for DND customized for each schedule is still absent in Note 9, though this feature was earlier there in stock Oreo, and has been made available in stock Android Q.
Hello,
Everytime I open android auto it mutes my ringtones and notifications. This did not happen on my previous phone (s7 edge); does anybody know how to disable this? It does not even show me my onscreen notifications when driving
I had the same problem, just using Android Auto on the phone, not a car screen. I'm afraid it's due to how Xiaomi have made Do Not Disturb, in that it isn't the same as standard Android. There used to be a toggle in the settings of Android Auto, but they removed that and you can't add exceptions in DND on Xiaomi. So, the only work around I have found is to download an app called Macrodroid. (Free) https://play.google.com/store/apps/details?id=com.arlosoft.macrodroid
And create a macro that detects when Android Auto is launched then disable DND, with a 5 second delay to allow Android Auto to start and switch DND mode.
If you want I can share screens of the macro.
If anyone has a better way let me know!
I might be moving from a Xiaomi phone to a Huawei one soon. The following I found most annoying things in MIUI(latest version) so I want to know how many of these things I am going to experience in EMUI too.
1. Lockscreen notifications disappear after unlocking the phone even if the notifications have not been cleared. Notifications that you receive while screen on will never make it to the lockscreen.
2. Google Smart Lock does not work and Xiaomi does not provide any alternative of their own.
3. The camera app does not have an option to review picture immediately after taking it.
4. Auto brightness is not adjustable and is simply a one size fits all option.
5. The DND mode cannot ONLY silent notifications. Notification and ringtone volume cannot be unlinked either so there is no easy way to silence all notifications.
Furthermore as I understand both of these skins have very aggressive battery management. MIUI does allow me to whitelist apps to exclude from that. Does Huawei offer this option too?
Lastly I read somewhere that you can't reply on a lock screen notification in EMUI? Is that still the case with the latest version?
Sent from my Mi 9T using Tapatalk