#pinetime — Public Fediverse posts

@cynical13 I have two #Pinetime smartwatches. One died after a year or so, one after one week (!). To this day, @pine64eu ghosts these warranty cases. We also had to trash a now broken #PinePower USB charging station. My #Pinephone is still working though. But the quality is pretty subpar.

For a while, I had a #PineTime watch. It worked... fine, but there were definite limitations.

The charger stopped reliably charging it and I couldn't get it to sync back up to my phone.

That kind of killed my interest in smart watches in general and in #Pine64 specifically.

It seems like Pine decided that what they had was good enough and they haven't really worked to improve anything since. Their webpage is still copyrighted 2022.

@the_wub @kennergf @EUCommission

How about on my #PineTime watch?

#Pine64

A couple of years ago I forgot to take off my #PineTime smart watch when bouldering. Smashed it hard against one of he holds and cracked the screen. It's still working fine, but it's a little annoying.

Figured that I'd get a new one once this one finally gives up.

Now there's a #PineTimePro in the works and as soon as that's out it's very likely I'll upgrade. Or maybe stick to the simplicity of the OG. Or go back to #BangleJS. Who knows... The new watch from #Pine64 seems interesting at least.

PineTime Pro will be a bigger, faster, more capable open source smartwatch

More than six years after Pine64 introduced a cheap smartwatch designed to run open source firmware, the company is preparing to launch a new model. The PineTime Pro isn’t a replacement for the original PineTime (which is still available for $27). But it brings a bunch of upgrades that could make it a better platform for users that want a better screen or support for more complex […]

@geekland

I really just want something that can adequately record if I'm asleep or awake and that can also send notifications from my (preferably #MobileLinux) phone.

That's it.

I'm guessing that's a combo of SPO2,(?) heartrate and movement sensors.

I got bit hard by one of only 2 proprietary apps I had installed for sleep tracking. This could help break that dependency, as long as there's some FOSS app out there with a decent algo for turning these sensors into sleep data.

#Pine64 #Pinetime #PinetimePro

PineTime Pro is an open source smartwatch with an OLED display and GPS

Pine64 is a company that produces inexpensive single-board computers, laptops, tablets, and smartphones designed to run open source software, usually aimed at developers and open source enthusiasts.

In response to the current RAM shortage, the company has paused production of some devices, including the PinePhone, PineNote, and PineTab2. But the company is also introducing a new device: The […]

Pixel Watch 2 - Privacy Preserving Setup

I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

• Unpairing the Watch means factory resetting it.
• Every feature (literally everything) is google dependent (who would have thought.. i know)
• Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

After the watch was set up, i continued and:

• Deleted the user profile from which i connected the Watch
• Enabled wireless debugging
• Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
• Removed the Google account in the settings
• Cleared all Bluetooth preferences
• Enabled Bluetooth discovery
• Installed KDE Connect on it (not meant for WearOS but it does work barely)

The watch is now in a state where i can use it daily.

But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

Now comes the fun part.

I've created a basic Kotlin project with both a mobile and WearOS app.

I will implement features like:

• Notification sync
• Call notifications
• Media Player Control
• Weather (openweathermap)
• Heartrate monitoring
• Sleep tracking
• Do not Distrurb Sync
• Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
• And much more ..

The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

Cheers.

#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

Pixel Watch 2 - Privacy Preserving Setup

I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

• Unpairing the Watch means factory resetting it.
• Every feature (literally everything) is google dependent (who would have thought.. i know)
• Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

After the watch was set up, i continued and:

• Deleted the user profile from which i connected the Watch
• Enabled wireless debugging
• Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
• Removed the Google account in the settings
• Cleared all Bluetooth preferences
• Enabled Bluetooth discovery
• Installed KDE Connect on it (not meant for WearOS but it does work barely)

The watch is now in a state where i can use it daily.

But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

Now comes the fun part.

I've created a basic Kotlin project with both a mobile and WearOS app.

I will implement features like:

• Notification sync
• Call notifications
• Media Player Control
• Weather (openweathermap)
• Heartrate monitoring
• Sleep tracking
• Do not Distrurb Sync
• Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
• And much more ..

The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

Cheers.

#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

Pixel Watch 2 - Privacy Preserving Setup

I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

• Unpairing the Watch means factory resetting it.
• Every feature (literally everything) is google dependent (who would have thought.. i know)
• Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

After the watch was set up, i continued and:

• Deleted the user profile from which i connected the Watch
• Enabled wireless debugging
• Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
• Removed the Google account in the settings
• Cleared all Bluetooth preferences
• Enabled Bluetooth discovery
• Installed KDE Connect on it (not meant for WearOS but it does work barely)

The watch is now in a state where i can use it daily.

But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

Now comes the fun part.

I've created a basic Kotlin project with both a mobile and WearOS app.

I will implement features like:

• Notification sync
• Call notifications
• Media Player Control
• Weather (openweathermap)
• Heartrate monitoring
• Sleep tracking
• Do not Distrurb Sync
• Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
• And much more ..

The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

Cheers.

#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

Pixel Watch 2 - Privacy Preserving Setup

I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

• Unpairing the Watch means factory resetting it.
• Every feature (literally everything) is google dependent (who would have thought.. i know)
• Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

After the watch was set up, i continued and:

• Deleted the user profile from which i connected the Watch
• Enabled wireless debugging
• Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
• Removed the Google account in the settings
• Cleared all Bluetooth preferences
• Enabled Bluetooth discovery
• Installed KDE Connect on it (not meant for WearOS but it does work barely)

The watch is now in a state where i can use it daily.

But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

Now comes the fun part.

I've created a basic Kotlin project with both a mobile and WearOS app.

I will implement features like:

• Notification sync
• Call notifications
• Media Player Control
• Weather (openweathermap)
• Heartrate monitoring
• Sleep tracking
• Do not Distrurb Sync
• Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
• And much more ..

The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

Cheers.

#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

Pixel Watch 2 - Privacy Preserving Setup

I've been trying everything i could think of to make the watch work under GrapheneOS - Here is what i learned:

• Unpairing the Watch means factory resetting it.
• Every feature (literally everything) is google dependent (who would have thought.. i know)
• Pairing with your phone requires the "Pixel Watch" -App to be installed on your main profile (not work, not private space) alongside Google Play Services. There's no way around.

This is obviously unacceptable. So i did a bit of research and found a way that will not only be way more practical, it will also be private.

First i created a second user on my Phone, installed Google Play Services and the pixel watch app on it, logged in with a newly created google account and completed the setup.

I know some people use a chinese version of the WearOS app to bypass the google login. Since i don't want a chinese app to configure my watch, i didn't even try that.

After the watch was set up, i continued and:

• Deleted the user profile from which i connected the Watch
• Enabled wireless debugging
• Debloated the watch as good as possible (i will have to root the watch in the future to properly do it)
• Removed the Google account in the settings
• Cleared all Bluetooth preferences
• Enabled Bluetooth discovery
• Installed KDE Connect on it (not meant for WearOS but it does work barely)

The watch is now in a state where i can use it daily.

But i also want to make use of all those fancy quality-of-life features, like heartrate monitoring, sleep tracking and so on.

Now comes the fun part.

I've created a basic Kotlin project with both a mobile and WearOS app.

I will implement features like:

• Notification sync
• Call notifications
• Media Player Control
• Weather (openweathermap)
• Heartrate monitoring
• Sleep tracking
• Do not Distrurb Sync
• Homelab integrations (Nextcloud, Immich, Uptime Kuma, ..)
• And much more ..

The goal is to keep the watch offline, let the phone do the heavy lifting and communicate with a selfhosted database. I may even add a frontend and an API so people can integrate it for their needs.

Sounds good but why don't you just buy an #opensource #smartwatch like the #pinetime - You may ask.

Because as much as i hate to admit it, i love the design, the look and feel of the pixel watch. And i'm sure that i'm not the only one.

I also bought this one cheap for around 120€ #refurbished. So the value i can get out of it seems pretty good to me.

So much for today. I haven't even started tackling the Bluetooth connection yet 😅. Let's see how that turns out

I have added a poll to this post to see how many people would be interested in a setup like this. Please let me know if you have any suggestions, ideas or expertise in that regard.

Cheers.

#privacy #security #android #google #pixel #pixelwatch #degoogle #degoogling #degoogled #adb #rooting #grapheneos #smartwatch #development #wearos #bluetooth #qualityoflife #GooglePlay #GooglePlayServices #frontend #api #selfhosting #selfhosted #homelab #opensource

Todavía me preguntaba por qué la navegación no me funcionaba (PineTime + Amazfish en #UBports). Al final, resultó ser AppArmor en Pure Maps (ahora hay una versión sin restricciones de la aplicación en la tienda). La navegación debe estar habilitada en la configuración de #Amazfish, y los recursos (imágenes de navegación) deben cargarse en #PineTime.

Traducido de https://fosstodon.org/@jmlich/115915545379851674

#PineTime #Pine64 #PureMaps #Amazfish #GPLv3 #OpenStore #UbuntuTouch #Lomiri #SoftwareLibre #GNULinux

Todavía me preguntaba por qué la navegación no me funcionaba (PineTime + Amazfish en #UBports). Al final, resultó ser AppArmor en Pure Maps (ahora hay una versión sin restricciones de la aplicación en la tienda). La navegación debe estar habilitada en la configuración de #Amazfish, y los recursos (imágenes de navegación) deben cargarse en #PineTime.

Traducido de https://fosstodon.org/@jmlich/115915545379851674

#PineTime #Pine64 #PureMaps #Amazfish #GPLv3 #OpenStore #UbuntuTouch #Lomiri #SoftwareLibre #GNULinux

Todavía me preguntaba por qué la navegación no me funcionaba (PineTime + Amazfish en #UBports). Al final, resultó ser AppArmor en Pure Maps (ahora hay una versión sin restricciones de la aplicación en la tienda). La navegación debe estar habilitada en la configuración de #Amazfish, y los recursos (imágenes de navegación) deben cargarse en #PineTime.

Traducido de https://fosstodon.org/@jmlich/115915545379851674

#PineTime #Pine64 #PureMaps #Amazfish #GPLv3 #OpenStore #UbuntuTouch #Lomiri #SoftwareLibre #GNULinux

Todavía me preguntaba por qué la navegación no me funcionaba (PineTime + Amazfish en #UBports). Al final, resultó ser AppArmor en Pure Maps (ahora hay una versión sin restricciones de la aplicación en la tienda). La navegación debe estar habilitada en la configuración de #Amazfish, y los recursos (imágenes de navegación) deben cargarse en #PineTime.

Traducido de https://fosstodon.org/@jmlich/115915545379851674

#PineTime #Pine64 #PureMaps #Amazfish #GPLv3 #OpenStore #UbuntuTouch #Lomiri #SoftwareLibre #GNULinux

Todavía me preguntaba por qué la navegación no me funcionaba (PineTime + Amazfish en #UBports). Al final, resultó ser AppArmor en Pure Maps (ahora hay una versión sin restricciones de la aplicación en la tienda). La navegación debe estar habilitada en la configuración de #Amazfish, y los recursos (imágenes de navegación) deben cargarse en #PineTime.

Traducido de https://fosstodon.org/@jmlich/115915545379851674

#PineTime #Pine64 #PureMaps #Amazfish #GPLv3 #OpenStore #UbuntuTouch #Lomiri #SoftwareLibre #GNULinux

I was still wondering why navigation wasn’t working for me (PineTime + Amazfish on #UBports). In the end, it turned out to be AppArmor in Pure Maps (there is now an unconfined version of the app in the store). Navigation must be enabled in the #Amazfish settings, and the resources (navigation images) must be uploaded to the #PineTime.

I was still wondering why navigation wasn’t working for me (PineTime + Amazfish on #UBports). In the end, it turned out to be AppArmor in Pure Maps (there is now an unconfined version of the app in the store). Navigation must be enabled in the #Amazfish settings, and the resources (navigation images) must be uploaded to the #PineTime.

I was still wondering why navigation wasn’t working for me (PineTime + Amazfish on #UBports). In the end, it turned out to be AppArmor in Pure Maps (there is now an unconfined version of the app in the store). Navigation must be enabled in the #Amazfish settings, and the resources (navigation images) must be uploaded to the #PineTime.

I was still wondering why navigation wasn’t working for me (PineTime + Amazfish on #UBports). In the end, it turned out to be AppArmor in Pure Maps (there is now an unconfined version of the app in the store). Navigation must be enabled in the #Amazfish settings, and the resources (navigation images) must be uploaded to the #PineTime.

I was still wondering why navigation wasn’t working for me (PineTime + Amazfish on #UBports). In the end, it turned out to be AppArmor in Pure Maps (there is now an unconfined version of the app in the store). Navigation must be enabled in the #Amazfish settings, and the resources (navigation images) must be uploaded to the #PineTime.

Even my #pinetime is feeling the #congress vibes today.

#39c9 #ccc #opensource #smartwatch #LVGL

Even my #pinetime is feeling the #congress vibes today.

#39c9 #ccc #opensource #smartwatch #LVGL

Daily driving a Pixel 3a while on a three week holiday wrap-up

https://my-place.social/display/e599373b-7168-6c62-c6a3-b86258671760

Daily driving a Pixel 3a while on a three week holiday wrap-up

https://my-place.social/display/e599373b-7168-6c62-c6a3-b86258671760

Daily driving a Pixel 3a while on a three week holiday wrap-up

https://my-place.social/display/e599373b-7168-6c62-c6a3-b86258671760

I've bought a #Bangle.js 2 at #FOSDEM, I like it!

I've charged it once just after FOSDEM (on Sunday), and it still shows 40% of battery, screen is sun readable, and several useful sensors.

Being a #Python dev, I was more into micropython (I have a #PineTime with #WaspOS). But the #espruino tool chain is really nice: 600+ apps easy to upload from browser (sadly not supported by Firefox), simple IDE with REPL, and CLI tools. I can use Python on computer with #javascript on watch.

Neat work!

My #PineTime smart watch suddenly stopped working last year (not expensive, but not high quality either). Now I can't decide between buying

1️⃣ an open-source #BangleJS that has more features, supports apps and is easily programmable, but also costs much more and could turn out to be low-quality too,

2️⃣ a high-quality #AndroidWear watch that has all features imaginable but isn't supported by #MicroG. Flashing #AsteroidOS could break some functionality & the “ease-of-use”.

What should I buy?

@tuxedocomputers #Linux #FreeCAD #Marlin #Gimp #Nextcloud #Thunderbird #Firefox #libreoffice #inkscape #android #KiCad #IronOS #Pinetime #calyxos #openwrt #turrisomnia #pandas #appimagelauncher #podaddict #davx5 #fennec #gadgetbridge #tusky #osmand #oeffi

@hamblingreen I've been tempted to get the #PineBudsPro to replace my JBL earbuds that have never fit my ears correctly. Are you able to adjust the size while still fitting them in the charging case?

Also, have you checked out the #Bangle.js2 to compare with #PineTime? I'd be curious to know your thoughts on how they compare.

@jawsh I don't think so... at least not just yet. I've only heard of people using #Siglo as a #Pinetime companion app with the Pinephone, and last time I tried that didn't seem to support notification sync yet. Hopefully soon though!

@normandc Yeah. #Gadgetbridge + #Android unfortunately. Was just about to try setting up the #Pinetime with #Siglo on my #Pinephone.

Tracking down a firmware bug in #PineTime @PINE64 ? Or trying to understand an alien chunk of firmware code? #VSCode Debugger with #STLink can help! Lemme show you how I used the debugger for my first contact with #RIOT_OS... https://medium.com/@ly.lee/debug-riot-os-on-pinetime-with-vscode-12f00c69c120?source=friends_link&sk=a836d511355876bf81855db9f1e94124

Sharing my delightful experience debugging @RIOT_OS on #PineTime @PINE64 with #VSCode and #STLink... Not that different from #Mynewt OS! https://youtu.be/a_VD-p1XwBg

#FIDO 2FA security keys generated by #RustLang and #TockOS on Nordic #nRF52840... Supported by Google! Hope to see TockOS on #PineTime someday...

https://security.googleblog.com/2020/01/say-hello-to-opensk-fully-open-source.html