# No PT Connection after 1.1.0.3 Update

**URL:** <https://forum.repebble.com/t/no-pt-connection-after-1-1-0-3-update/544>\
**Category:** Get Pebble Help!\
**Created:** [April 30, 2026, 1:54am UTC](https://forum.repebble.com/t/no-pt-connection-after-1-1-0-3-update/544 "2026-04-30T01:54:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Den\_in\_USA](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/den_in_usa/32/238_2.png) [@Den\_in\_USA](https://forum.repebble.com/u/Den_in_USA)\
**Post date:** [April 30, 2026, 1:54am UTC](https://forum.repebble.com/t/no-pt-connection-after-1-1-0-3-update/544/1 "2026-04-30T01:54:12Z")

</div>

Updated today on my Android phone then couldn’t connect to my Pebble Time watch. Enabled Airplane Mode for about 10 seconds but didn’t connect. Rebooted watch and phone. Continuously displays Connecting (BT Classic). Never displays Negotiating. I sent a bug report using the Pebble app on my phone. I also clicked Disconnect then Connect in the Devices tab of the phone app.

---

<div class="post-metadata">

**Author:** ![steve](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/steve/32/13_2.png) [@steve](https://forum.repebble.com/u/steve)\
**Post date:** [April 30, 2026, 2:07am UTC](https://forum.repebble.com/t/no-pt-connection-after-1-1-0-3-update/544/2 "2026-04-30T02:07:06Z")

</div>

Were you previous using the BT classic mode before updating the app?

We are migrating all users of "old watches to use BT classic by default with this release (which should fix a lot of reliability issues with OG/Time watches) - it should have prompted you to pair over BT classic if you weren’t already using that mode.

If that didn’t happen and you can’t connect, then please unpair on both watch and phone (in Android bluetooth settings, and in the watch bluetooth menu, and try to reconnect).

---

<div class="post-metadata">

**Author:** ![Den\_in\_USA](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/den_in_usa/32/238_2.png) [@Den\_in\_USA](https://forum.repebble.com/u/Den_in_USA)\
**Post date:** [April 30, 2026, 2:26am UTC](https://forum.repebble.com/t/no-pt-connection-after-1-1-0-3-update/544/3 "2026-04-30T02:26:09Z")

</div>

That worked, thanks! 👍

---

<div class="post-metadata">

**Author:** ![Flynn](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/flynn/32/73_2.png) [@Flynn](https://forum.repebble.com/u/Flynn)\
**Post date:** [May 1, 2026, 2:09am UTC](https://forum.repebble.com/t/no-pt-connection-after-1-1-0-3-update/544/4 "2026-05-01T02:09:51Z")

</div>

Will there be a way to use LE? Or is that just not supported anymore?

---

<div class="post-metadata">

**Author:** ![steve](https://yyz1.discourse-cdn.com/flex033/user_avatar/forum.repebble.com/steve/32/13_2.png) [@steve](https://forum.repebble.com/u/steve)\
**Post date:** [May 1, 2026, 2:31am UTC](https://forum.repebble.com/t/no-pt-connection-after-1-1-0-3-update/544/5 "2026-05-01T02:31:07Z")

</div>

Yes, but kinda hidden - behind a debug setting (i.e. we’re not going to stop you, but it’s not the “supported” way). Of course if they get a new BLE stack then we’ll revisit that.