this post was submitted on 28 Jul 2023
62 points (93.1% liked)

Android

17682 readers
18 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS
 

The Google Maps app for Android has, for years now, had the same old voice input that’s slow and not as accurate as Google’s latest offerings. Finally that’s changing, as Google Maps is rolling out a new voice input experience powered by Google Assistant.

top 10 comments
sorted by: hot top controversial new old
[–] eggshappedegg@sopuli.xyz 12 points 1 year ago (2 children)

All of my Google home (nest) speakers have gotten worse for every moth that passes. They understand less and less for every time and often even just ignore me (even though LED register input). I'm removing them all because from what I've experienced they're programmed to break just about a year past the warranty. I'm not replacing all of my nests every 2-3 years. I'll just press that light switch myself instead like in the old days

[–] sloonark@lemm.ee 10 points 1 year ago

for every moth that passes

This is such a cool typo. I love the mental image.

[–] yourdogsnipples@lemmy.world 3 points 1 year ago

The ability of my Google Home gadgets to correctly understand speech drops sharply whenever there's a promo on them - I imagine the influx of new speech patterns from new users tanks the recognition/parsing systems at Google.

[–] Moonrise2473@feddit.it 7 points 1 year ago (1 children)

not as accurate as the latest offerings

Maybe the opposite? Ten years ago it understood everything, now it's a 80% chance of "sorry, I didn't understand"

[–] XTornado@lemmy.ml 3 points 1 year ago (1 children)

Could have been a patent issue or some weird shit?

Like I think Apple for example had some headphones that did a super awesome noise cancellation but suddenly in a update it got worse and it was although not sure if publically confirmed to the fact it was breaking some patent and they had to introduce workarounds.

[–] Moonrise2473@feddit.it 3 points 1 year ago (1 children)

No, because if you go on history.google.com you can see what you said, and often it shows exactly what you said. Probably they want to make it look smarter to have some hard coded smart responses instead of just reading a summary of a Google search, but it fails miserably all the times

[–] ayyndrew@lemmy.world 1 points 1 year ago

Yeah the issue isn't the voice recognition, from what I can tell that has only gotten better and is really great on my Pixel 6 Pro, it's how Assistant interprets the commands that has degraded

[–] limecool@lemmy.ml 5 points 1 year ago

For some reason Youtube does the fastest and the most accurate voice recognition compared to the offline google Speech to Text. If they want to improve. Implement that in the Speech to Text app.

[–] ElPussyKangaroo@lemdro.id 5 points 1 year ago

How does Google have 4 different Voice Input technologies for essentially the same product?!

The Gboard uses the new Speech Services. But Assistant uses a better thing... Which is slow at times. But there's still many Google apps using the old shitty Speech utility. And then there's YouTube. Goddamn.