[Feature Request] Google Fit - Strength Training with exercise detection [188854881]

Assigned

Feature Request

[AOSP] assigned

adexe s nau

Status Update

No update yet.

Description

be...@gmail.com

created issue #1

May 21, 2021 06:15PM

In November 2020 update of Google Fit for Wear OS, the strength training functionality was disabled. This functionality could:

Detect repetitions very accurately.
Automatically recognized the exercise you were performing based on the repetitive motion you were performing.
It allowed to time the rest times between sets.
It allowed you to add weights and manually enter exercises.

With the new Google Fit, for strength training, it is only limited to tracking heart rate and cardio points, also displaying the time and stopwatch on the screen. However, even though the old functionality was deactivated, the code of this functionality was kept hidden inside the app so I was still hoping that it would return in future updates of Google Fit, but in early May 2021 the code of the old functionality was completely removed.

What type of issue is this? Goggle Fit Feature Request in Wear OS
Since when does it happen? From November 2020.
What steps would let us observe? Open Google Fit (Training) on Wear OS, and select strength training.
What did you expect to happen? Strength training with exercise and repetitions detection.
How often has this happened? Every time
Related apps
- Google Fit
Actual version in my smartwatch
- Google Fit - 2.56.11.230
- Wear OS - 2.27
Smartwatch model: TicWatch Pro 3 GPS - Firmware PMRB.210407.001

Comments

be...@gmail.com <be...@gmail.com> #2May 21, 2021 06:43PM

Also confirmed issue persists on 4.4.

er...@gmail.com <er...@gmail.com> #3May 21, 2021 08:39PM

There are a lot of expensive accessories I've purchased or been gifted that quit workin with android 4.2. Android devs need to get on this. 3 broken versions and numerous minor updates and it hasn't even been triaged yet. Completely unprofessional.

vi...@google.com <vi...@google.com> May 22, 2021 06:34AM

Assigned to na...@google.com.

gg...@gmail.com <gg...@gmail.com> #4May 25, 2021 01:46PM

We are loyal to Android as and they treat us like this.. I have a google device and yet it still is not fixed.

ar...@ucm.es <ar...@ucm.es> #5May 25, 2021 05:07PM

Please fix

Message last modified on May 25, 2021 05:11PM

na...@google.com <na...@google.com> #6May 26, 2021 06:07AM

Yes, please fix it. =)

gi...@gmail.com <gi...@gmail.com> #7May 28, 2021 05:07AM

I abandoned iPhone to discover something better, but I'm finding a lot of my Bluetooth paired devices won't work properly on android... I hope this gets fixed soon. I don't want to have to buy an iPhone again and suffer with their long agreements and system restrictions.

ro...@gmail.com <ro...@gmail.com> #8May 29, 2021 12:02AM

[Comment deleted]

ad...@gmail.com <ad...@gmail.com> #9May 30, 2021 01:13PM

fix will ya? make the android better more

ro...@gmail.com <ro...@gmail.com> #10May 31, 2021 07:31PM

Yes, count me as someone who would like to see this fixed. It apparently isn't fixed in KitKat.

dh...@gmail.com <dh...@gmail.com> #11Jun 2, 2021 04:44PM

I have two nexus devices and this is a regular issue. The kid can't play games properly. Way to replace a working stack with a subpar homebrewed one.

kr...@gmail.com <kr...@gmail.com> #12Jun 2, 2021 04:56PM

Please roll back previous API. This fratura is importante.

kr...@gmail.com <kr...@gmail.com> #13
Restricted+
Jun 2, 2021 04:59PM

Comment has been deleted.

deleted

Restricted+

0 B

an...@gmail.com <an...@gmail.com> #14Jun 3, 2021 01:33AM

Please fix, pretty please

ke...@gmail.com <ke...@gmail.com> #15Jun 7, 2021 08:29AM

Comment has been deleted.

Message last modified on Jun 7, 2021 08:29AM

zo...@gmail.com <zo...@gmail.com> #16Jun 12, 2021 12:00AM

Please fix this!! We want to play with us wii u pro controller!! C'mon Google!!

ig...@gmail.com <ig...@gmail.com> #17Jun 22, 2021 07:39PM

PLEASE GOOGLE, LET US HAVE BLUETOOTH FREEEEEEEEDDDDOOOOOOOOOOOOOOOOOOM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

cd...@gmail.com <cd...@gmail.com> #18Aug 2, 2021 12:28AM

Google, please fix this issue. many games are unplayable with said issue.

al...@gmail.com <al...@gmail.com> #19Aug 8, 2021 05:24AM

Please google, can someone please fix this issue. thanks

sa...@gmail.com <sa...@gmail.com> #20Aug 15, 2021 02:01PM

Would love to see this resolved. Like a handful of others on here I just wanted to sync a bluetooth controller to my Android device to play some games. (I'm not very good at Megaman X with the touchscreen). I know it isn't a huge system issue, but maybe it could be changed anyway?

Games already look great on the Note 3, would be better with my controller.

Thanks in advance!

vi...@gmail.com <vi...@gmail.com> #21Aug 24, 2021 03:05AM

Just want to play some Bayou Billy for nes on my Note 3 with wiimote controller please.

me...@gmail.com <me...@gmail.com> #22Aug 24, 2021 08:58AM

[Comment deleted]

gi...@gmail.com <gi...@gmail.com> #23Aug 27, 2021 01:50AM

I was really upset when I went to use a feature that used to work perfectly, this is stupid, what gives Google?

ru...@gmail.com <ru...@gmail.com> #24Aug 27, 2021 09:09AM

I, like many others, wish to enjoy computer gaming nostalgia via excellent emulators. Please fix my first world problem...

js...@wealthsimple.com <js...@wealthsimple.com> #25Aug 30, 2021 06:19PM

Please fix. This is really dissapointing and I think I'm switching to Apple.

th...@gmail.com <th...@gmail.com> #26Sep 7, 2021 06:26AM

Several Android devices and several Android versions from 4.2 to 4.4 : I cannot use m'y game contrôler I bought especially for my first Android phone under 2.2. Please fix !!

ja...@gmail.com <ja...@gmail.com> #27Sep 14, 2021 03:31PM

Blue Tooth has been broken for nearly a year. How is that even a thing that is? This is how your lose paying customers, Google.

co...@gmail.com <co...@gmail.com> #28Sep 14, 2021 03:37PM

Please support Bluetooth L2CAP. This is important to me. It's hard to believe the famous Android lacks such a basic Bluetooth function.

ha...@gmail.com <ha...@gmail.com> #29Oct 1, 2021 08:35AM

Still don't work...

ja...@gmail.com <ja...@gmail.com> #30Oct 31, 2021 09:59PM

Please fix this.

pc...@gmail.com <pc...@gmail.com> #31Nov 30, 2021 04:53PM

Waht is the big deal?
Please fix this already!

to...@durge.org <to...@durge.org> #32Dec 30, 2021 12:22PM

[Comment deleted]

js...@gmail.com <js...@gmail.com> #33Dec 30, 2021 01:18PM

Please fix this. I want to pair my Wiimote with my Android phone and tablet.

me...@gmail.com <me...@gmail.com> #34Dec 30, 2021 02:27PM

Please repair this issue

js...@gmail.com <js...@gmail.com> #35Dec 30, 2021 02:31PM

I cant pair my wii remote with my new smartphone android, please fix this. :) thanks

js...@gmail.com <js...@gmail.com> #36Dec 30, 2021 02:33PM

Please fix this if you can.

js...@gmail.com <js...@gmail.com> #37Dec 30, 2021 02:33PM

I would like see this fixed too. It's extremely poor business practice to break compatibility with a software update and not address it in last three versions.

th...@gmail.com <th...@gmail.com> #38Dec 30, 2021 02:36PM

As a fellow Android user interested in this bug, I strongly agree that it should be fixed. However, by starring the issue, you've already expressed an interest in it being fixed, so it's unnecessary to add a comment saying the same thing. None of the recipients of the comments (user or developer alike) benefit from the added noise. I humbly request that instead of commenting, share this bug with your friends and get them to star it as well, or start a petition. Thanks in advance.

js...@gmail.com <js...@gmail.com> #39Dec 30, 2021 02:38PM

can't connect almost any peripheral I own VIA BT after the 4.4 update. Hardware supports it, but your software has disabled it at a core level that even root level changes cannot provide a solution. I know you want us all to buy new toys, but some of these don't have proper new replacements!!!

js...@gmail.com <js...@gmail.com> #40Dec 30, 2021 02:38PM

Wish my wiimote worked on my droid tablet

th...@gmail.com <th...@gmail.com> #41Jan 26, 2022 11:08PM

[Comment deleted]

ro...@gmail.com <ro...@gmail.com> #42Apr 29, 2022 10:24AM

This bug has been unattended to for over a YEAR. This is COMPLETELY inexcusable.

ma...@gmail.com <ma...@gmail.com> #43May 5, 2022 10:47PM

Solve this problem

lu...@99bikes.com.au <lu...@99bikes.com.au> #44Jun 1, 2022 06:05AM

Can anyone tell us why this issue is still here, or why L2CAP support was turned off in the first place?

c....@gmail.com <c....@gmail.com> #45Jul 3, 2022 06:03PM

I poked around with the same question. It seems to be the case that L2CAP
was never officially supported. In fact, in some forums, there were
warnings that non-API calls like this were prone to disappear in the
future. That being the case, this is more appropriately called a feature
request than a bug.

Access to L2CAP disappeared when the Linux Bluetooth stack blueZ was
replaced by the Broadcom-built library, BlueDroid. I couldn't find any
online justification for the library swap. Maybe security, maybe
reliability. It is open source though. You can dig through the source and
find the low-level implementation of L2CAP (RFCOM builds on top of it) and
see what it takes to expose the connection. I did this a few months ago
and saw it promised to be non-trivial.

turned off in the first place?

um...@gmail.com <um...@gmail.com> #46Aug 25, 2022 02:30PM

I know that in in the rest of linux bluez just recently had a major version change and many utilities which worked well with the previous version are broken until their maintainers update their code for the new version.

That being said perhaps this change promised to break a lot of stuff for droid, or at the very least cause power consumption concerns. I haven't looked at bluez code, but it its also possible there might have been some issues with how the new version plays on ARM architecture. (to the best of my knowledge bluez is primarily written for x86 which is found on most PCs but NOT any smartphone and few if any tablets)

This is all purely speculation on my part and would need verification from someone far more knowledgeable than I.

Would anyone be able to shed more light on the issue?

js...@gmail.com <js...@gmail.com> #47Aug 25, 2022 02:34PM

Fix this please. I will have no choice but to switch to another OS if it not fixed.

ha...@gmail.com <ha...@gmail.com> #48Aug 26, 2022 09:45AM

I miss this functionality. I used it on my old android 2.1 and it worked fine. I wish it would work with my newer 4.4.2 phone. I don't understand why something that used to work breaks with updates.

um...@gmail.com <um...@gmail.com> #49Aug 26, 2022 10:37AM

Seems google is getting a reputation for things like this. Hopefully they
work to correct it

js...@gmail.com <js...@gmail.com> #50Aug 26, 2022 10:42AM

Alright so I'm on a nexus 7 rooted and running the latest official build of CyanogenMod 11 and before I flashed cm it always asked for a password when trying to connect a wiimote via straight Bluetooth and now that I'm running cm it connects to on without asking for a pin. So I'm wondering if there's an app on Google play that will make android accept its input as a native gamepad. Anyone know of such a thing?

um...@gmail.com <um...@gmail.com> #51Aug 26, 2022 11:02AM

Google! Fix this please! This is ridiculous!

js...@gmail.com <js...@gmail.com> #52Aug 26, 2022 11:46AM

wtf
Bought a TabPro 8.4 to play some games only to discover it won't work with my Wii U Pro Controller.
What a waste of money. Come the fuck on, Google!

um...@gmail.com <um...@gmail.com> #53Aug 26, 2022 11:51AM

Help!

js...@gmail.com <js...@gmail.com> #54Aug 26, 2022 01:29PM

Please fix this issue, thank you

js...@gmail.com <js...@gmail.com> #55Aug 26, 2022 01:30PM

Might need at least another 1800 folks before google takes this seriously

um...@gmail.com <um...@gmail.com> #56Aug 26, 2022 02:37PM

Fix it please

js...@gmail.com <js...@gmail.com> #57Aug 26, 2022 02:46PM

Fix please!

ma...@gmail.com <ma...@gmail.com> #58Oct 12, 2022 07:19PM

[Comment deleted]

um...@gmail.com <um...@gmail.com> #59Oct 12, 2022 08:19PM

Please work to correct this.

cr...@gmail.com <cr...@gmail.com> #60Oct 14, 2022 05:28AM

Fix it please.

ba...@gmail.com <ba...@gmail.com> #61Nov 17, 2022 06:18PM

Though I really want this to be fixed, it probably won't cause Google.

um...@gmail.com <um...@gmail.com> #62Nov 17, 2022 07:13PM

Lads(Google), go on and fix this. Would like to be able to use BT devices on Nook again

pc...@gmail.com <pc...@gmail.com> #63Feb 2, 2023 03:42AM

Does anyone know if this has finally been addressed in Android 5.0 Lollipop?

kd...@gmail.com <kd...@gmail.com> #64Mar 20, 2023 01:52AM

Please fix!!!!

ch...@gmail.com <ch...@gmail.com> #65Jul 18, 2023 08:13AM

[Comment deleted]

pc...@gmail.com <pc...@gmail.com> #66Jul 18, 2023 09:43AM

Why has this not been fixed??

cr...@gmail.com <cr...@gmail.com> #67Jul 18, 2023 03:10PM

This is the reason why we all love Android... Otherwise We'd just buy and IOS device... Please address this issue.

da...@gmail.com <da...@gmail.com> #68Jul 18, 2023 05:07PM

please fix this

ch...@gmail.com <ch...@gmail.com> #69Jul 18, 2023 07:03PM

another fix request!! common google!!

be...@gmail.com <be...@gmail.com> #70Jul 19, 2023 02:55AM

There are 9 commits that mentions something about L2CAP in lollipop.

http://aosp.changelog.to/aosp-KITKAT-LRX21M.html

sh...@gmail.com <sh...@gmail.com> #71Feb 12, 2024 11:03PM

[Comment deleted]

nb...@gmail.com <nb...@gmail.com> #72Feb 16, 2024 01:50PM

Please, fix it.
I want use my bluetooth !!

91...@gmail.com <91...@gmail.com> #73Jun 8, 2024 05:46AM

Cant use my wiimote on galaxy s4 due to this issue. :( Hope it gets fixed...

Just happy that i also have an ipad where it works perfectly for the time till here maybe happens something.

Issue 188854881

Description

Issue summary

Comments

be...@gmail.com <be...@gmail.com> #2May 21, 2021 06:43PM

er...@gmail.com <er...@gmail.com> #3May 21, 2021 08:39PM

vi...@google.com <vi...@google.com> May 22, 2021 06:34AM

gg...@gmail.com <gg...@gmail.com> #4May 25, 2021 01:46PM

ar...@ucm.es <ar...@ucm.es> #5May 25, 2021 05:07PM

na...@google.com <na...@google.com> #6May 26, 2021 06:07AM

gi...@gmail.com <gi...@gmail.com> #7May 28, 2021 05:07AM

ro...@gmail.com <ro...@gmail.com> #8May 29, 2021 12:02AM

ad...@gmail.com <ad...@gmail.com> #9May 30, 2021 01:13PM

ro...@gmail.com <ro...@gmail.com> #10May 31, 2021 07:31PM

dh...@gmail.com <dh...@gmail.com> #11Jun 2, 2021 04:44PM

kr...@gmail.com <kr...@gmail.com> #12Jun 2, 2021 04:56PM

kr...@gmail.com <kr...@gmail.com> #13 Restricted+ Jun 2, 2021 04:59PM

an...@gmail.com <an...@gmail.com> #14Jun 3, 2021 01:33AM

ke...@gmail.com <ke...@gmail.com> #15Jun 7, 2021 08:29AM

zo...@gmail.com <zo...@gmail.com> #16Jun 12, 2021 12:00AM

ig...@gmail.com <ig...@gmail.com> #17Jun 22, 2021 07:39PM

cd...@gmail.com <cd...@gmail.com> #18Aug 2, 2021 12:28AM

al...@gmail.com <al...@gmail.com> #19Aug 8, 2021 05:24AM

sa...@gmail.com <sa...@gmail.com> #20Aug 15, 2021 02:01PM

vi...@gmail.com <vi...@gmail.com> #21Aug 24, 2021 03:05AM

me...@gmail.com <me...@gmail.com> #22Aug 24, 2021 08:58AM

gi...@gmail.com <gi...@gmail.com> #23Aug 27, 2021 01:50AM

ru...@gmail.com <ru...@gmail.com> #24Aug 27, 2021 09:09AM

js...@wealthsimple.com <js...@wealthsimple.com> #25Aug 30, 2021 06:19PM

th...@gmail.com <th...@gmail.com> #26Sep 7, 2021 06:26AM

ja...@gmail.com <ja...@gmail.com> #27Sep 14, 2021 03:31PM

co...@gmail.com <co...@gmail.com> #28Sep 14, 2021 03:37PM

ha...@gmail.com <ha...@gmail.com> #29Oct 1, 2021 08:35AM

ja...@gmail.com <ja...@gmail.com> #30Oct 31, 2021 09:59PM

pc...@gmail.com <pc...@gmail.com> #31Nov 30, 2021 04:53PM

to...@durge.org <to...@durge.org> #32Dec 30, 2021 12:22PM

js...@gmail.com <js...@gmail.com> #33Dec 30, 2021 01:18PM

me...@gmail.com <me...@gmail.com> #34Dec 30, 2021 02:27PM

js...@gmail.com <js...@gmail.com> #35Dec 30, 2021 02:31PM

js...@gmail.com <js...@gmail.com> #36Dec 30, 2021 02:33PM

js...@gmail.com <js...@gmail.com> #37Dec 30, 2021 02:33PM

th...@gmail.com <th...@gmail.com> #38Dec 30, 2021 02:36PM

js...@gmail.com <js...@gmail.com> #39Dec 30, 2021 02:38PM

js...@gmail.com <js...@gmail.com> #40Dec 30, 2021 02:38PM

th...@gmail.com <th...@gmail.com> #41Jan 26, 2022 11:08PM

ro...@gmail.com <ro...@gmail.com> #42Apr 29, 2022 10:24AM

ma...@gmail.com <ma...@gmail.com> #43May 5, 2022 10:47PM

lu...@99bikes.com.au <lu...@99bikes.com.au> #44Jun 1, 2022 06:05AM

c....@gmail.com <c....@gmail.com> #45Jul 3, 2022 06:03PM

um...@gmail.com <um...@gmail.com> #46Aug 25, 2022 02:30PM

js...@gmail.com <js...@gmail.com> #47Aug 25, 2022 02:34PM

ha...@gmail.com <ha...@gmail.com> #48Aug 26, 2022 09:45AM

um...@gmail.com <um...@gmail.com> #49Aug 26, 2022 10:37AM

js...@gmail.com <js...@gmail.com> #50Aug 26, 2022 10:42AM

um...@gmail.com <um...@gmail.com> #51Aug 26, 2022 11:02AM

js...@gmail.com <js...@gmail.com> #52Aug 26, 2022 11:46AM

um...@gmail.com <um...@gmail.com> #53Aug 26, 2022 11:51AM

js...@gmail.com <js...@gmail.com> #54Aug 26, 2022 01:29PM

js...@gmail.com <js...@gmail.com> #55Aug 26, 2022 01:30PM

um...@gmail.com <um...@gmail.com> #56Aug 26, 2022 02:37PM

js...@gmail.com <js...@gmail.com> #57Aug 26, 2022 02:46PM

ma...@gmail.com <ma...@gmail.com> #58Oct 12, 2022 07:19PM

um...@gmail.com <um...@gmail.com> #59Oct 12, 2022 08:19PM

cr...@gmail.com <cr...@gmail.com> #60Oct 14, 2022 05:28AM

ba...@gmail.com <ba...@gmail.com> #61Nov 17, 2022 06:18PM

um...@gmail.com <um...@gmail.com> #62Nov 17, 2022 07:13PM

pc...@gmail.com <pc...@gmail.com> #63Feb 2, 2023 03:42AM

kd...@gmail.com <kd...@gmail.com> #64Mar 20, 2023 01:52AM

ch...@gmail.com <ch...@gmail.com> #65Jul 18, 2023 08:13AM

pc...@gmail.com <pc...@gmail.com> #66Jul 18, 2023 09:43AM

cr...@gmail.com <cr...@gmail.com> #67Jul 18, 2023 03:10PM

da...@gmail.com <da...@gmail.com> #68Jul 18, 2023 05:07PM

ch...@gmail.com <ch...@gmail.com> #69Jul 18, 2023 07:03PM

be...@gmail.com <be...@gmail.com> #70Jul 19, 2023 02:55AM

sh...@gmail.com <sh...@gmail.com> #71Feb 12, 2024 11:03PM

nb...@gmail.com <nb...@gmail.com> #72Feb 16, 2024 01:50PM

91...@gmail.com <91...@gmail.com> #73Jun 8, 2024 05:46AM

Add comment

Issue metadata

kr...@gmail.com <kr...@gmail.com> #13
Restricted+
Jun 2, 2021 04:59PM