#wearos — Public Fediverse posts

#GWB - WearOS: Schickes Watch Face wandelt die Smartwatch zu einer Pendeluhr – ein Hingucker am Handgelenk - https://www.googlewatchblog.de/2026/05/wearos-schickes-watch-face-wandelt-die-smartwatch-zur-pendeluhr-ein-hingucker-am-handgelenk-u/ #watchface #Google #wearos

RE: https://meow.social/@SebinNyshkim/116507502045101155

So I've been wearing this thing for about a week now and there's both good and bad I've learned about it.

The good thing is, this thing lasts. I can coast by two days comfortably before it needs a charge and even then it charges to 100% in like 20-30 minutes. Workout stuff works as expected. Reviews often knock on the Fitbit Premium stuff but it's not required for workout tracking.

I was also surprised to learn Wear OS supports Android's private DNS feature, which means I can hook it up to my AdGuard Home instance to block ads and tracking with the added benefit of encrypting all DNS queries the watch makes for added privacy in untrusted networks.

The app situation, however, sucks just as much as for the Apple Watch. There's just not that many utility apps available that aren't fitness focused or by Google itself. Don't get me started on the slew of "AI" bullshit apps on the store.

The Navidrome app I've been using to stream my own music collection doesn't have a Wear OS companion app, so I just dished out the one-time 6,99 for Symphonium. It's quite polished and comes with Android Auto and TV support, so that's neat.

Downloading music onto the watch for offline listening is ass tho. I have to initiate downloads on the watch and I can only sync playlists, not the entirety of my fav songs.

Wear OS also keeps cutting Wi-Fi to save battery. I had to enable dev mode and Wi-Fi debugging to prevent that. Yikes.

Contacts from my own Nextcloud instance sync, calendar appointments don't. Despite selecting non-Google calendars for sync, the calendar on the watch is empty. Only Google Calendar works apparently.

Been an issue since 2023. Nice vendor lock-in you got there with your supposedly open platform.

This checks out with how Android still doesn't offer CardDAV or CalDAV natively, whereas Apple does. You need an additional app for that. I do still get notifications for appointments as they come up on my phone, but again, it knocks off another point on the list of things for basic utility.

#Android #WearOS #PixelWatch #GooglePixelWatch

Gemini for Wear OS could also be getting a glow-up soon

New retail demo reveals a vibrant glow animation and refreshed weather icons coming to Gemini on your wrist.

✅ Details - https://www.androidauthority.com/google-gemini-wear-os-visual-refresh-apk-teardown-3662278

#Gemini #WearOS #Google

🆕Tytanowy smartwatch z Wear OS 6 wchodzi do gry! Poznajcie oficjalnie OnePlus Watch 4
➡️https://rootblog.pl/oneplus-watch-4-po-cichu-debiutuje-na-rynku/

#Oneplus #OnePlusWatch4 #WearOS

https://www.europesays.com/be-nl/50109/ Tot 35% goedkoper: Oppo Find X9 Ultra en Hasselblad camerakit kunnen worden geïmporteerd #BE #België #Belgium #ChinaModell #EarthExplorerKit #Einschränkungen #eSIM #Farben #FindX9Ultra #HasselbladKamera #import #informations #KameraKit #LTEBand20 #Nieuws #Oppo #overzichten #Science #ScienceAndTechnology #ScienceAndTechnology #Technologie #Technology #testrapporten #WasBeimImportZuBeachtenIst #WearOS #weiß #Wetenschap #WetenschapEnTechnologie #WetenschapTechnologie

Pixel Watch Fall Detection will soon require a Google account sign-in

There should be a multi-day grace period before Google disables access.

✅ Details - https://www.androidauthority.com/pixel-watch-fall-detection-account-3659960/

#PixelWatch #Google #WearOS

https://www.europesays.com/fi/227880/ Oppo Watch X3 julkaistiin globaalisti Wear OS -käyttöjärjestelmällä ja 16 päivän akulla – hinnat alkavat 349 eurosta #Älykellot #FI #Finland #Finnish #Julkaisu #Oppo #OppoWatchX3 #Suomi #Technology #Teknologia #WearOS

#GWB - WearOS: Schickes Watch Face wandelt die Smartwatch zur Pendeluhr – ein Hingucker am Handgelenk - https://www.googlewatchblog.de/2026/04/wearos-schickes-watch-face-wandelt-die-smartwatch-zur-pendeluhr-ein-hingucker-am-handgelenk/ #watchface #Google #wearos

Gemini on Wear OS might be preparing for OFFLINE support

You might be able to set alarms, timers, and launch apps without an internet connection.

✅ Details - https://www.androidauthority.com/gemini-wear-os-offline-3656267/

#WearOS #Google #PixelWatch

Wear OS 6.1: Nächstes Smartwatch-Update bringt automatische Zeitzonen und bessere Kindersicherung
https://www.schmidtisblog.de/wear-os-6-1-naechstes-smartwatch-update-bringt-automatische-zeitzonen-und-bessere-kindersicherung-1797024/

#WearOS

Google wydaje Wear OS 6.1. Aktualizacja rozwiązuje najbardziej irytujący problem smartwatchy

Bez wielkich fanfar i hucznych zapowiedzi. Google udostępniło właśnie nową wersję swojego systemu dla zegarków – Wear OS 6.1.

Z zewnątrz nie uświadczymy tu wizualnej rewolucji, bo oprogramowanie bazuje na grudniowym wydaniu Androida 16 QPR2 i skupia się na poprawkach pod maską. Przynosi jednak kilka bólowo praktycznych nowości, na czele z wyeliminowaniem jednego z największych absurdów w historii tego systemu.

Koniec z resetowaniem zegarka przez zmianę hasła

Jeśli kiedykolwiek ze względów bezpieczeństwa musiałeś zmienić hasło do swojego konta Google, doskonale wiesz, jaki koszmar czekał Cię na nadgarstku. Zegarki z Wear OS traciły weryfikację i często jedynym sposobem na ponowne podpięcie ich pod konto był całkowity powrót do ustawień fabrycznych (factory reset) i konfigurowanie sprzętu od zera.

Wear OS 6.1 wreszcie kończy z tym archaicznym rozwiązaniem. W nowej wersji systemu, jeśli Twoje dane uwierzytelniające stracą ważność, będziesz mógł po prostu ponownie zweryfikować konto Google bezpośrednio na ekranie zegarka lub przez aplikację towarzyszącą na smartfonie. To mała zmiana w kodzie, ale gigantyczna ulga dla użytkowników.

Offline’owe strefy czasowe i dorastanie z zegarkiem

Google dorzuca też dwie nowości, które docenią osoby dużo podróżujące oraz rodzice:

• Strefy czasowe bez dostępu do sieci: zegarki z Wear OS 6.1 potrafią automatycznie aktualizować strefę czasową bazując wyłącznie na fizycznej lokalizacji urządzenia. Co ważne, funkcja ta działa nawet wtedy, gdy smartwatch nie ma dostępu do internetu komórkowego ani Wi-Fi (np. zaraz po wyjściu z samolotu na zagranicznym lotnisku). Opcję tę można włączyć w ustawieniach daty i czasu.
• „Dojrzewanie” konta dziecięcego: Google dopracowało obsługę autonomicznych zegarków dla najmłodszych. Gdy użytkownik nadzorowanego konta osiągnie wiek zgody cyfrowej, może płynnie przejść na pełnoprawne konto dla dorosłych. System automatycznie zdejmie blokady rodzicielskie i odblokuje pełny dostęp do ustawień zegarka, bez utraty dotychczasowych danych.

Kiedy aktualizacja trafi na nasze nadgarstki?

Jak na razie Wear OS 6.1 wylądował w emulatorze środowiska Android Studio i jest dostępny wyłącznie dla deweloperów. Historia uczy nas jednak, że tego typu mniejsze pakiety trafiają do użytkowników dość sprawnie. Możemy bezpiecznie założyć, że oprogramowanie zadebiutuje na smartwatchach w ramach jednej z najbliższych, kwartalnych aktualizacji – w pierwszej kolejności zasilając oczywiście autorskie zegarki z serii Pixel Watch.

Google ułatwia przesiadkę. Gemini zaimportuje twoje rozmowy z innych chatbotów

#GWB - WearOS 6.1: Google veröffentlicht neue Version – bringt (bald) einige neue Funktionen auf die Pixel Watches - https://www.googlewatchblog.de/2026/04/wearos-6-1-google-veroeffentlicht-neue-version-bringt-bald-einige-neue-funktionen-auf-die-pixel-watches/ #Google #wearos

Google tells Wear OS developers to go 64-bit or get blocked from the Play Store

https://fed.brid.gy/r/https://nerds.xyz/2026/04/google-wear-os-64-bit-play/

Spotify relooke son app Wear OS avec une navigation 100 % gestuelle http://dlvr.it/TRYwgt #Spotify #WearOS

Gemini for Wear OS is getting a major weather card makeover with some much needed additions

Following a similar update on Android phones, Google is bringing a more expressive UI to your wrist

✅ More screenshots and video - https://www.androidauthority.com/gemini-wear-os-weather-card-ui-apk-teardown-3647866/

#WearOS #Google

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

Qualcomm mostra el nou xip Snapdragon Wear Elite per a WearOS.

https://9to5google.com/2026/03/01/qualcomm-snapdragon-wear-elite/

#Qualcomm #Wearos #snapdragon

Xiaomi Watch 5 Review: A Powerful Smartwatch with Impressive Battery Life

📰 Original title: Xiaomi Watch 5 unboxing

🤖 IA: It's not clickbait ✅
👥 Usuarios: It's not clickbait ✅

View full AI summary: https://killbait.com/en/xiaomi-watch-5-review-a-powerful-smartwatch-with-impressive-battery-life/?redirpost=e7c00c6c-568f-45c5-9717-021065e1b463

#technology #xiaomi #wearos #smartwatch

AndroidX Feb 25 updates are out 🚀

Compose 1.11 alpha, Material3 1.5 alpha, Navigation3, XR runtime, Wear, Camera & more.

Full list 👇
https://developer.android.com/jetpack/androidx/versions/all-channel?hl=en#february_25_2026

#AndroidDev #JetpackCompose #WearOS #AndroidXR #Kotlin #Androidx #Android

Erdbebenwarnung: Smartwatches mit Wear OS könnten auch ohne Pairing warnen https://www.computerbase.de/news/wearables/erdbebenwarnung-smartwatches-mit-wear-os-koennten-auch-ohne-pairing-warnen.96280/ #Google #wearos

AsteroidOS 2.0 sauve les montres sous Wear OS de l'obsolescence logicielle http://dlvr.it/TR6QFz #AsteroidOS #WearOS

Android's Calling Cards could be coming soon to Wear OS

✅ Details - https://www.androidauthority.com/google-phone-wear-os-calling-cards-apk-teardown-3642713/

#Google #Android #WearOS

AsteroidOS 2.0 : une dose de libre pour montres connectées
AsteroidOS est un système Linux pensé pour les montres connectées, plus d'une vingtaine de modèles sont compatibles ..
https://www.minimachines.net/?p=139583 #linux #wearos

The Android smartwatch ecosystem is dead. Not struggling. Dead. Google had ten years, billions of dollars, and the world's most popular mobile OS. They spent it renaming things, breaking promises, and burying their partners quietly in developer documentation.
This piece is not balanced. The market hasn't earned balance.
https://fireborn.mataroa.blog/blog/apple-watch-or-dont-bother/
#Smartwatch #WearOS #AppleWatch #Google #Android #Tech #TechWriting

The Android smartwatch ecosystem is dead. Not struggling. Dead. Google had ten years, billions of dollars, and the world's most popular mobile OS. They spent it renaming things, breaking promises, and burying their partners quietly in developer documentation.
This piece is not balanced. The market hasn't earned balance.
https://fireborn.mataroa.blog/blog/apple-watch-or-dont-bother/
#Smartwatch #WearOS #AppleWatch #Google #Android #Tech #TechWriting

The Android smartwatch ecosystem is dead. Not struggling. Dead. Google had ten years, billions of dollars, and the world's most popular mobile OS. They spent it renaming things, breaking promises, and burying their partners quietly in developer documentation.
This piece is not balanced. The market hasn't earned balance.
https://fireborn.mataroa.blog/blog/apple-watch-or-dont-bother/
#Smartwatch #WearOS #AppleWatch #Google #Android #Tech #TechWriting

The Android smartwatch ecosystem is dead. Not struggling. Dead. Google had ten years, billions of dollars, and the world's most popular mobile OS. They spent it renaming things, breaking promises, and burying their partners quietly in developer documentation.
This piece is not balanced. The market hasn't earned balance.
https://fireborn.mataroa.blog/blog/apple-watch-or-dont-bother/
#Smartwatch #WearOS #AppleWatch #Google #Android #Tech #TechWriting

The Android smartwatch ecosystem is dead. Not struggling. Dead. Google had ten years, billions of dollars, and the world's most popular mobile OS. They spent it renaming things, breaking promises, and burying their partners quietly in developer documentation.
This piece is not balanced. The market hasn't earned balance.
https://fireborn.mataroa.blog/blog/apple-watch-or-dont-bother/
#Smartwatch #WearOS #AppleWatch #Google #Android #Tech #TechWriting

Slowly realising that the only way to have anything non-Google for #WearOS is to build it myself

🆕Xiaomi Watch 5 w drodze do Europy! Ambitny smartwatch, który nie wszystkim się spodoba
➡️https://rootblog.pl/xiaomi-watch-5-zmierza-na-europejski-rynek/

#WearOS #Xiaomi #XiaomiWatch5

Spotify is testing a bold new look for its Wear OS app

A redesigned "Now Playing" screen puts album art front and center, while introducing gesture controls for playback.

✅ Details/video - https://www.androidauthority.com/spotify-wear-os-now-playing-redesign-3640437/

#spotify #WearOS #Music

🚀 AndroidX updates (Feb 11, 2026)

✨ Compose 1.11.0-alpha05
📸 Camera 1.6.0-beta02
🧭 Navigation3 1.1.0-alpha04
🧪 UI Automator 2.4.0-beta01
⌚ Wear Compose 1.6.0-alpha10
📄 PDF 1.0.0-alpha13

Full list 👇
https://developer.android.com/jetpack/androidx/versions/all-channel?hl=en#february_11_2026

#AndroidDev #Jetpack #AndroidX #Compose #WearOS

🚀 AndroidX updates (Feb 11, 2026)

✨ Compose 1.11.0-alpha05
📸 Camera 1.6.0-beta02
🧭 Navigation3 1.1.0-alpha04
🧪 UI Automator 2.4.0-beta01
⌚ Wear Compose 1.6.0-alpha10
📄 PDF 1.0.0-alpha13

Full list 👇
https://developer.android.com/jetpack/androidx/versions/all-channel?hl=en#february_11_2026

#AndroidDev #Jetpack #AndroidX #Compose #WearOS

🚀 AndroidX updates (Feb 11, 2026)

✨ Compose 1.11.0-alpha05
📸 Camera 1.6.0-beta02
🧭 Navigation3 1.1.0-alpha04
🧪 UI Automator 2.4.0-beta01
⌚ Wear Compose 1.6.0-alpha10
📄 PDF 1.0.0-alpha13

Full list 👇
https://developer.android.com/jetpack/androidx/versions/all-channel?hl=en#february_11_2026

#AndroidDev #Jetpack #AndroidX #Compose #WearOS

🚀 AndroidX updates (Feb 11, 2026)

✨ Compose 1.11.0-alpha05
📸 Camera 1.6.0-beta02
🧭 Navigation3 1.1.0-alpha04
🧪 UI Automator 2.4.0-beta01
⌚ Wear Compose 1.6.0-alpha10
📄 PDF 1.0.0-alpha13

Full list 👇
https://developer.android.com/jetpack/androidx/versions/all-channel?hl=en#february_11_2026

#AndroidDev #Jetpack #AndroidX #Compose #WearOS

🚀 AndroidX updates (Feb 11, 2026)

✨ Compose 1.11.0-alpha05
📸 Camera 1.6.0-beta02
🧭 Navigation3 1.1.0-alpha04
🧪 UI Automator 2.4.0-beta01
⌚ Wear Compose 1.6.0-alpha10
📄 PDF 1.0.0-alpha13

Full list 👇
https://developer.android.com/jetpack/androidx/versions/all-channel?hl=en#february_11_2026

#AndroidDev #Jetpack #AndroidX #Compose #WearOS

We've been quietly building. Now it's live. 🎉

Vayu is officially available on Android + Wear OS! 🤖⌚

Breathwork, guided — wherever you are.

This is just the beginning.
More science. More sound. More stillness.

Link in bio.

#Vayu #Breathwork #WellnessTech #AndroidApp #WearOS #BuildInPublic #MentalHealth #Meditation

We've been quietly building. Now it's live. 🎉

Vayu is officially available on Android + Wear OS! 🤖⌚

Breathwork, guided — wherever you are.

This is just the beginning.
More science. More sound. More stillness.

Link in bio.

#Vayu #Breathwork #WellnessTech #AndroidApp #WearOS #BuildInPublic #MentalHealth #Meditation

We've been quietly building. Now it's live. 🎉

Vayu is officially available on Android + Wear OS! 🤖⌚

Breathwork, guided — wherever you are.

This is just the beginning.
More science. More sound. More stillness.

Link in bio.

#Vayu #Breathwork #WellnessTech #AndroidApp #WearOS #BuildInPublic #MentalHealth #Meditation

We've been quietly building. Now it's live. 🎉

Vayu is officially available on Android + Wear OS! 🤖⌚

Breathwork, guided — wherever you are.

This is just the beginning.
More science. More sound. More stillness.

Link in bio.

#Vayu #Breathwork #WellnessTech #AndroidApp #WearOS #BuildInPublic #MentalHealth #Meditation

Any #Tennis player (or watcher) with a #WearOS #smartwatch out there?

If so, we may have cooked something for you: https://codeberg.org/LezSoft/TennisGD 👀

A minimalist tennis score tracker for your wrist, built with #Kotlin and #JetpackCompose is waiting for you on #GooglePlay and #Codeberg 🎾

Koniec bałaganu w płatnościach. Portfel Google wreszcie z pełną historią (także z zegarka!)

Polska jest jednym ze światowych liderów płatności zbliżeniowych, dlatego ta zmiana ucieszy u nas miliony użytkowników.

Google w końcu naprawia jedną z najbardziej irytujących cech swojego Portfela: brak synchronizacji historii zakupów. Wkrótce w aplikacji na telefonie zobaczysz nie tylko ostatnie 10 płatności, ale pełną listę wydatków – również tych zrobionych zegarkiem czy online.

Do tej pory Portfel Google na Androida działał w dość archaiczny sposób. Jeśli zapłaciliście za zakupy smartwatchem z Wear OS, informacja o tym (zazwyczaj) nie pojawiała się w historii na telefonie. Co więcej, aplikacja mobilna ograniczała się do wyświetlania zaledwie 10 ostatnich transakcji wykonanych tym konkretnym urządzeniem. Chcąc sprawdzić starsze wydatki, trzeba było logować się do aplikacji bankowej.

Pomóż nam rozwijać iMagazine – ruszyło badanie czytelnictwa 2026

Jeden widok dla wszystkich urządzeń

Informacje wygrzebane przez redakcję 9to5Google w notach wydawniczych Usług Google Play (wersja 26.01) wskazują na przełom. Google zapowiada, że użytkownicy będą mogli „przeglądać transakcje z innych urządzeń oraz zakupy online wykorzystujące wirtualne numery kart”.

Co to oznacza w praktyce nad Wisłą?

Pełna synchronizacja: płacisz rano zegarkiem za kawę, a wieczorem widzisz tę pozycję w historii na swoim smartfonie.

Wirtualne karty: jeśli Twój bank (np. mBank, ING czy Revolut) korzysta z tokenizacji kart przy płatnościach w sieci, te transakcje również trafią na wspólną listę w aplikacji.

Nadchodzi wyszukiwarka

To nie koniec dobrych wieści. W kodzie aplikacji (wersja 25.1.x) znaleziono ślady przygotowań do wdrożenia wyszukiwarki. Funkcja ta, dostępna już w webowej wersji serwisu (wallet.google.com), wkrótce trafi na smartfony. Dzięki temu, zamiast scrollować listę w nieskończoność, wystarczy wpisać nazwę sklepu (np. „Biedronka” czy „Orlen”), by szybko odfiltrować konkretne płatności.

Dla polskich użytkowników to spora zmiana na plus. Portfel Google powoli przestaje być tylko cyfrowym etui na karty, a staje się realną alternatywą dla historii w aplikacjach bankowych, które często bywają przeładowane funkcjami. Funkcja będzie wdrażana etapami (po stronie serwera), więc warto uzbroić się w cierpliwość – powinna pojawić się u Was w najbliższych tygodniach.

Koniec bałaganu w Mapach Google. Nadchodzi nowy wygląd ustawień

Leaving the Apple Ecosystem – Pebble Smartwatch

https://medi-nerd.com/2026/01/06/leaving-the-apple-ecosystem-pebble-smartwatch/

Wear OS 6 bug breaks AOD transitions for 3rd-party watch faces on Pixel and Galaxy watches

✅ Details - https://piunikaweb.com/2025/12/31/wear-os-6-aod-transitions-for-3rd-party-watch-faces-on-pixel-and-galaxy-watches/

#PixelWatch #Samsung #Google #WearOS #AndroidDev

Alerta para Usuarios de Galaxy Watch 4 – Samsung Pausa la Actualización de One UI 8 por Fallos Graves

Samsung ha detenido el despliegue de su más reciente actualización (One UI 8 Watch, basada en Wear OS 6) para la serie Galaxy Watch 4. Según se reporta en reddit, incluso en un foro de la propia Samsung, múltiples usuarios han informado de problemas críticos que afectan tanto la autonomía como la funcionalidad básica del reloj.

Problemas Detectados en la Actualización

Aunque se esperaba que esta fuera la última gran actualización para un dispositivo que ya tiene más de 4 años, los errores reportados son significativos:

1. Drenaje Extremo de Batería

Muchos usuarios reportan que la duración de la batería ha caído drásticamente. Relojes que antes aguantaban unas 24 horas ahora se apagan tras apenas 12 o 15 horas de uso. En algunos casos, el drenaje es aún más severo.

• Posible solución temporal: Algunos usuarios han logrado mitigar esto limpiando la memoria caché del dispositivo, aunque no funciona para todos.

2. Sensores Inutilizados

El problema más grave afecta a los sensores biométricos. Algunos propietarios del Galaxy Watch 4 Classic han descubierto que, tras actualizar, el reloj no puede detectar el pulso ni el seguimiento de salud.

• Bloqueo Constante: Al no detectar que el reloj está puesto en la muñeca, el sistema pide el código de seguridad (si está activo) constantemente, inutilizando funciones como Google Wallet o las notificaciones básicas.

3. Pantalla Siempre Encendida (AOD) con Fallos

También se han reportado casos donde la función de Always-on Display deja de funcionar por completo después de instalar el nuevo software.

¿Qué debes hacer?

Si todavía no has actualizado tu Galaxy Watch 4, se recomienda esperar. Samsung parece haber retirado la actualización de sus servidores mientras trabaja en un parche correctivo. Si ya has actualizado y sufres estos problemas, mantente atento a la aplicación Galaxy Wearable, ya que Samsung suele lanzar parches de emergencia rápidamente en estos casos.

#actualización #android #arielmcorg #Batería #FalloTecnico #GalaxyWatch4 #infosertec #OneUI8 #PORTADA #Samsung #smartwatch #tecnología #WearOS

#GWB - WearOS: Schickes Watch Face bringt den Wetterbericht, viele Vitalwerte und weitere Infos auf Smartwatches - https://www.googlewatchblog.de/2025/12/wearos-schickes-watch-face-bringt-den-wetterbericht-viele-vitalwerte-und-weitere-infos-auf-smartwatches/ #watchface #Google #wearos #wetter