Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Voice input icon should be shown only when corresponding services are available #5698

Open
sivaraam opened this issue Apr 20, 2024 · 8 comments
Labels

Comments

@sivaraam
Copy link
Member

Summary

It's great to see the voice input option in the description and caption elements. There is a possibility that there are no speech-to-text services available on the device. Right now we seem to show the speech-to-text icon even in that case. We should identify this case and avoid showing the icon.

Steps to reproduce

  1. Open the app on a device that does not have speech-to-text services (disabling the existing service should be sufficient)
  2. Initiate an upload
  3. Tap on the speech-to-text icon near the description / caption fields

Expected behaviour

We don't show the speech-to-text icon at all as the same is not available on the device.

Actual behaviour

We show the speech-to-text icon but tapping on the same has no effect.

Device name

OnePlus Nord

Android version

Android 12

Commons app version

main

Device logs

No response

Screen-shots

No response

Would you like to work on the issue?

Prefer not

@sivaraam sivaraam added the bug label Apr 20, 2024
@rohit9625
Copy link
Contributor

I have question, i.e., what is the case or device that doesn't have speech to text feature?

@sivaraam
Copy link
Member Author

I have question, i.e., what is the case or device that doesn't have speech to text feature?

Just try uninstalling / disabling Google's speech-to-text app and other similar apps from your device. Your device would no longer have any of those services.

@rohit9625
Copy link
Contributor

I got it, thanks :)

I guess these two ways can be helpful:-

  1. Change visibility to none after checking if services are available or not.
  2. When tapped on the icon and service is unavailable, then we can ask user to enable or install speech to text services.

@kanahia1
Copy link
Contributor

@rohit9625 How about changing the color of the icon (may be to a Gray) if service is not available, unclicking the icon we can show the Toast to indicate the status of service.

@rohit9625
Copy link
Contributor

@rohit9625 How about changing the color of the icon (may be to a Gray) if service is not available, unclicking the icon we can show the Toast to indicate the status of service.

That's a great idea :)

Let's see @sivaraam's thoughts also.

@nicolas-raoul
Copy link
Member

For now the important thing is probably: How to find out in advance whether service is available or not.

@kanahia1
Copy link
Contributor

Hey @nicolas-raoul, I ran this code (https://stackoverflow.com/a/32596376) I was able to get the engines available

Here are the results

WhatsApp Image 2024-04-21 at 14 17 05_3c703a78

These are the same I got on going to settings of my phone

WhatsApp Image 2024-04-21 at 14 17 05_c76f056b

@sivaraam
Copy link
Member Author

@rohit9625 How about changing the color of the icon (may be to a Gray) if service is not available, unclicking the icon we can show the Toast to indicate the status of service.

I think it might be ideal to just hide the icon altogether when no speech-to-text services are available. I don't see any point with bothering the user about it when their device doesn't have speech-to-text services. If I'm right, the Wikipedia app does the same.

I ran this code (https://stackoverflow.com/a/32596376) I was able to get the engines available

This is good. If it's helpful, this seems like the snippet that the Wikipedia app uses in order to recognize if speech-to-text services are available. We could consider using the same too. if it seems better 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants
@nicolas-raoul @sivaraam @rohit9625 @kanahia1 and others