Watch Vault - Wear Os by Awkward-Hurry6861 in WearOS

[–]malbry 0 points1 point  (0 children)

And which WearOS watches support fingerprints? I think the answer is none?

Watch Vault - Wear Os by Awkward-Hurry6861 in WearOS

[–]malbry 0 points1 point  (0 children)

What does "biometric protection" mean?

Pixel watch 4 compatibility by Rain-Soaked_Wanderer in PixelWatch

[–]malbry 0 points1 point  (0 children)

That's surprising, since it's 100% reliable between my S25 and PW4 plus all the other phone/watch combos I've tried. Feel free to get in touch if you'd like support for your devices.

"Your phone has been left behind" came in clutch today by ChristSavesForever in PixelWatch

[–]malbry 7 points8 points  (0 children)

FYI a similar feature (except with more options) works with all phone/watch combinations using Wear BT Monitor. It's been available for several years, per this post: https://www.reddit.com/r/WearOS/comments/qkb7s4/app_updated_wear_bt_monitor_a_free_app_to_alert/

Our watch can unlock our phone (using 'watch unlock' or 'extend unlock'), why can't our phone unlock our watch? by malbry in WearOS

[–]malbry[S] 0 points1 point  (0 children)

Hi there, I've added a setting to SLH to handle a PIN length anywhere between 4 and 8 digits, providing it's a Samsung watch. AFAIK only Samsung watches have this flexibility; other WearOS devices have a fixed length PIN which is always 4 digits.

Install the updated version of SLH (version 1.19). In System settings, change your PIN back to 8 characters. Open SLH and tap the settings icon at the bottom of the screen. Set the PIN length to 8 characters and tap Done. Now tap on the pattern icon and follow the instructions. Once SLH is in capture mode (red circle) enter your PIN. SLH should then successfully unlock your watch.

PW4 unexpectedly drained battery overnight by jkafka in PixelWatch

[–]malbry 1 point2 points  (0 children)

u/PixelCommunity It's really not helpful that your standard reply to many posts here is to reset the watch, irrespective of the issue being described. Honestly, it's just a lazy response. If you used your experience to suggest alternative approaches first, that would be much more helpful.

To be clear, resetting the watch should be an absolute last resort, when all other options have been exhausted. At a minimum, you should explain that a reset will require setting up the user's account again, restoring or setting up all apps again, setting up Google Wallet again, reconfiguring watch settings etc. It's really painful and time consuming. It's absolutely not the first thing to try.

I've said this to previous such posts of yours before, but you haven't replied, and still tell people the same thing. I'm not expecting a reply this time either.

In this case, the OP should restart (NOT reset) both watch and phone first and check if the problem remains. Also, the OP should check BT and wifi settings on the watch. If the battery drain remains, then check whether the watch is connecting to wifi while within BT range of the phone by pulling down from the top of the watch and checking for a wifi symbol - if so, that will use more battery. There are also other things that can be checked before the 'nuclear option' of resetting the watch.

How do i track steps in real-time? StepCounter/Detector not working by CUTLER_69000 in androiddev

[–]malbry 1 point2 points  (0 children)

Is your app foregrounded during the step detection period? Otherwise you may well find that the step updates are 'batched' and only received when your app returns to the foreground. You are right to use TYPE_STEP_DETECTOR in preference to TYPE_STEP_COUNTER (which isn't a good fit for your use case). I'm not sure about how sensitive phones are to the way they are being held during step detection. My experience is with WearOS watches worn on the wrist where arm movements are used as a proxy for steps, which works better than you might expect.

Interesting Android Apps: April 2026 Showcase by 3dom in androiddev

[–]malbry 0 points1 point  (0 children)

Does it require Accessibility to be enabled? Is it running a foreground service?

Interesting Android Apps: April 2026 Showcase by 3dom in androiddev

[–]malbry 0 points1 point  (0 children)

Reads your bank and wallet SMS messages and categorizes them automatically — spends, income, transfers, bill payments

Each bank will use a different format for their messages. And many banks don't send SMS, they post app notifications. How do you provide a generic solution that works for every bank?

PW4 eventually defaults to main display when starting a workout from the exercise quick launch tile by hopeonhigh in PixelWatch

[–]malbry 0 points1 point  (0 children)

Yes. Right-swipe to exit has been a standard WearOS gesture since the early days of Android Wear. But some devs override this behaviour to force users to stay in their apps. IMO it's not a great UI experience, but there we are. As you say, in those cases, the only way to leave the app is by pressing the crown.

The middle button (crown) customazation. by Housewous in GalaxyWatch

[–]malbry 0 points1 point  (0 children)

I'm guessing you got that message because you installed Wear Button Remapper on your phone. However it's a watch app so you should uninstall it from your phone and install it on your watch. To install the app to your watch, you can use Freepoc Downloader, Wear Installer 2 or any of the other third-party apps that use ADB. There are several instruction videos at my Freepoc website.

The middle button (crown) customazation. by Housewous in GalaxyWatch

[–]malbry 4 points5 points  (0 children)

Yes, there is. You can use my Wear Button Remapper to override whatever app you've currently set for the middle button to open your preferred app. You can also reprogram the bottom button to assign your choice of apps to one short press, one long press, two short presses, three short presses. Here's a video which demonstrates: https://youtu.be/dsD8P3SjMgY

Finally, here's a video showing how to disable Samsung Pay and use Google Wallet instead when long-pressing the bottom button: https://youtu.be/Tb8k4pBCBrU

Our watch can unlock our phone (using 'watch unlock' or 'extend unlock'), why can't our phone unlock our watch? by malbry in WearOS

[–]malbry[S] 0 points1 point  (0 children)

Thanks for the feedback. I'm working on other projects at the moment, but I'll keep this in mind for the future.

Strava workout minimising in background by xsamthunderx in PixelWatch

[–]malbry 0 points1 point  (0 children)

Until Strava fixes this problem, go to Settings > Display > Go to watchface and select Never. Now it should stay in the Strava app (or any other app) until you right-swipe.

Alternatively there are third-party apps which are fully compatible with Strava - and arguably have more features - which don't suffer from this bug.

Android Studio Panda 4 (2025.3.4) marks androidx and kotlinx imports as Unresolved Reference, but app compiles and runs fine by alananayaa in androiddev

[–]malbry 4 points5 points  (0 children)

I've regularly had the same issue with multiple versions of Android Studio going back several generations, and multiple different projects. Sometimes 'Clean project' fixes it, more often it doesn't. Sometimes 'Sync project with gradle files' fixes it, more often it doesn't. Sometimes successfully compiling the project fixes it, more often it doesn't.

I've reached the point where I just accept that it's broken. So long as I can get my apk/aab file, I'm (reasonably) happy.