Pebble Steel + Rockwork = ...
-
@moem
Oh ok!
With the Pinephone and Nexus 5 it was so that you first had to confirm the pin on the phone and then confirm on the clock that the pin was confirmed.
That with the forgetting of the Bluetooth devices is tricky. for me helped from time to time UT Tweak Tool. Clear cache from system settings.
sometimes it helped to connect both Bluetoooth devices (LE & other) and then remove these devices from the list of known devices. -
@ohnez Thank you for more good hints!
I tried the 'deleting cache' trick using UTT tool. It did not seem to help.I also tried confirming the PIN from the phone first, but it's like it does not even get send (or the watch does not receive or understand it): if I then press Pair on the watch, even after waiting for 5 seconds or so, the watch then tells me to confirm the PIN on the phone. Eventually it gives me the 'not sucessfully paired' screen.
I'm now looking at pairing over the terminal as per this post. If I can manage to connect a keyboard somehow, that might help, or it might give useful information.
-
@moem
oh I forgot to say, you must of course also in the Peeble under Settings / Bluetooth remove the Phone (OPO).if it does not work with the terminal
I can write on which way I have managed.
but this applies only to Nexus 5 and PinePhone. -
@ohnez said in Pebble Steel + Rockwork = ...:
@moem
oh I forgot to say, you must of course also in the Peeble under Settings / Bluetooth remove the Phone (OPO).Yes, thank you, that makes sense.
if it does not work with the terminal
I can write on which way I have managed.
but this applies only to Nexus 5 and PinePhone.Always worth a try. I will report.
-
So... this was interesting. Did not work, but was interesting.
In a terminal, using the program bluetoothctl, this is what happened:# pair B0:B4:48:AF:3A:64 Attempting to pair with B0:B4:48:AF:3A:64 [CHG] Device B0:B4:48:AF:3A:64 Connected: yes Request confirmation [agent] Confirm passkey 516792 (yes/no): yes Failed to pair: org.bluez.Error.AuthenticationFailedSo, it failed again. But now we can see it happen!
-
HOLY
it's working! How did that happen?! Maybe the 'trust' action that I did in the terminal did the job?dances the Happy Dance like Snoopy
-
More observations = more data!
On OTA15, Stable, the Pebble will not stay connected and reconnect as reliably. In fact it's pretty impossible to connect.
On the Edge release channel, the Pebble works much betterbut the phone screen stops rotating!I have since been informed that this can happen sometimes and it's usually cured by a reboot.
BUT...
on the Release Candidate channel, the Pebble will auto-reconnect as it shouldAND screen rotation works!
-
More Pebble adventures. With the help of @AntiDroid and @Keneda, I created an icon in Launcher Modular that immediately reconnects the Pebble when it's unconnected because it's been too far from the phone, or because it's not detected any movement for half an hour (stand-by mode).
The icon triggers this command:rfkill block bluetooth && rfkill unblock bluetoothand that results in the Pebble reconnecting instantly.
Here is the image I'm using for the icon in case anyone wants to use it:
-
Moar Pebbles, moar problems!
My Steel works really well with UT and Rockwork these days. Now a new friend came to my door today: a Pebble Time Steel. I would love to use both Pebbles alternatingly, depending on my plans for the day.
But Rockwork sees only the Steel, connected or not, and does not offer a way to connect a second Pebble. I can connect the Pebble to the bluetooth of the phone just fine, but I can't use Rockwork to interact with it.Ideally I want Rock work to show two Pebbles, and connect to the one that I'm wearing that day. As a workaround, a separate instance of Rockwork with its own settings might also be an option.
Does anyone have any ideas about whether this is possible, and if so, how?Since writing this I have learned that Rockwork does work with more than one Pebble! Just connect the new Pebble to the Bluetooth of the phone, and it will show you the option to manage one Pebble, or the other.
-
@moem said in Pebble Steel + Rockwork = ...:
Ideally I want Rock work to show two Pebbles
ThreeFour Pebbles...
Yes, things have taken a turn for the worse.
-
@moem Thanks for all the information. With your help I was able to pair a Pebble Time with my Pixel 3a (Xenial, as Rockwork is not available on focal yet). I guess the 'trust' option in bluetoothctl did the trick. Are you still using your Pebbles?
-
@lioh-0 said in Pebble Steel + Rockwork = ...:
Are you still using your Pebbles?
Yes! Today it's the Time Steel's turn. Glad to hear you found the topic useful!
-
@moem Great! May I ask which Firmware version you are running on the watch? I am still on 3.6.1 here.
-
-
@moem yes, It's only possible from Android e.g. using Gadgetbridge. A 4.4 FW is also available. Usually download Updates from here: https://github.com/Freeyourgadget/Gadgetbridge/wiki/Pebble-Firmware-updates
-
@lioh-0 said in Pebble Steel + Rockwork = ...:
yes, It's only possible from Android e.g. using Gadgetbridge.
Ah yes. I've always used old, side-loaded Pebble apps.
-
@moem how exactly have you managed to create the reload icon? Or do you have found another solution for the disconnect issues?
-
@lioh-0 said in Pebble Steel + Rockwork = ...:
how exactly have you managed to create the reload icon?
I used Launcher Modular, which allows you to make a launcher for a custom command. But I don't actually need or use that anymore. It works well enough without it.
-
Rockwork works amazingly well on Xenial. Hopefully we can have it on Focal in the future. It's a great app. I am ready to help with it when needed.
-
@malditobastardo It does, and that would be great, and YES please! I will not move to Focal otherwise. Gotta have my Rockwork and my Pebbles!
