First hw wise, specifically this batch used old buttons that are crumbly and a lot of people had issues with them. So buyer beware. I’m fairly happy with mine, but I would call this out to a friend.
Sw wise we’re not getting support due to two BLE (blue tooth low energy) problems:
SFOS - android layer does NOT support BLE, end of story, there’s no plan to
SFOS - native DOES support BLE but it’s bugged and does not work with this watch
I’ve tried to make it work with the original SFOS rockpool dev, you can see more info as we tried to debug things here
So sadly, the TLDR is, get an iphone or android side device if you want to use the pebble. I sync mine with an old iPhone every ~1 month or so (the clock drifts) and do updates/apps etc.
Then why am I able to use the android app to manage my new duo 2 und time 2?
I have to give AAS controll over Bluetooth but then I can pair the watch and use the official app to install faces and update firmware.
My big hope is the update to SFOS 5.1 when the new phone is out.
I hope then they fixed the issue with BT.
Until then the hand over of BT control to AAS as it is described here in a thread quite detailed looks to be the most promising solution if you have to rely on android apps.
You also need to tab repeatedly on the Android version in the settings System → Android AppSupport to get into the android settings to pair Bluetooth devices.
Ah ok, yes. I was alluding to native support being impossible, but I didn’t know you could “redirect” to AAS.
From what I understand, native BLE support is broken in older kernels in SFOS (again see the rockpool repo where we tried to debug it). Note that older watches with full BT (not low energy) do work fine.
I am not quite sure; personally, it is very expensive and does not hold an advantage compared to the Jolla J2. While the Jolla J2 is high in price, I believe its specific advantages and the service it provides are worth the investment. On the other hand, I just learned about the existence of the Pebble watch here. Personally, it is excellent regarding battery life and longevity, but in all other aspects—the screen and the buttons on the right—it looks very outdated. Despite being very expensive, the only realistic features it offers are the claims of being long-lasting and having the best battery life. I feel these features fall short given the price point. I believe I have reached a stalemate
Out of interest when using AAS with rebble app, were you able to get calendar to work? My understanding is that AAS does not see SFOS calendar (even google stuff)
Xperia 10 IV, Sailfish 5.1.0.8, Android ASS with BT bridge. Initial firmware update went smooth (pairing needs to go by long-press, “Pair with Android AppSupport” in Sailfish settings), then Bluetooth decided to start crashing. Will debug and report back.
Ideally, we’d be using Rockpool, but that’s not yet finished!
Hi yall, I got linked here by rubdos!
I am one of the developers on the PebbleOS and very excited for my Jolla Phone to ship!
If there is anything I can do to help (regarding some firmware quirks) feel free to ask me! Not that versed in mobile but I’ll see what I can do!
Yay, welcome! @abranson was playing with getting the BLE version to work with current Rockpool - it was still on the original BT stack.
Meanwhile, on Android AppSupport on my Jolla C2 it pairs, syncs watch faces, and shows my heart rate (yes I should lower my caffeine). So my above report is 100% the bad Sony BT stack of the 10 IV.
After ordering I still did not receive any status update of my order.also no shipping date or any other detail. I hope this is a real transaction and not some kind of scam.
You mean the Pebble? I’ve found it one of the most transparent pre-orders that I ever participated in. Eric was continuously broadcasting status updates about the production. Since you already wrote “wait until June before it ships”, I believe you may want to wait until June for a shipping notification.
If you mean the Jolla Phone, that’s not gonna happen before July 8.
Can’t see any LE device on the scan screen.