Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
I've had a lukewarm experience with Google's voice recognition. Between my phone and a few Nest Mini devices, it's not uncommon for the device I'm speaking into to misunderstand or outright not pick up on my Hey Google cue. And when I do so I have to speak very clearly almost to the point of it being unnatural.
I hate to say it but I've used others' Amazon/Apple devices and it's not nearly as difficult.
I find that the cadence of your words matters very much with Google. Like the words matter, but your pitch and tone matter too. I had to retain my model because it wouldn't go off when I'd yell ok Google at it, but it would go off when I'd say "ok cool" in convo. Now I have to say it with a specific inflection for it to recognize what I said. When I say it with the right inflection I'd say it works 80+ percent of the time
I've found on budget/older phones voice recognition is useless, I recommend something more modern of you can afford it, maybe a flagship from a year or two ago
is that the case even with a mic plugged in? I get similarly bad results with an external mic (though I haven’t tested a high end one, still saving for an upgrade)
unfortunately this phone is about as good as I could afford, I’m living well under the poverty line and $200 AUD (what I paid for the s10e, got it used with some scratches) is a big deal lol
Oh, you're also Australian. Yeah that explains part of a potential accent understanding problem then. I never tried with an external mic, but even in a very quiet room it wasn't always 100%. I found that the "Use verbs" setting was helpful to address some of that, because it limits the potential dictionary matching results. If you know you have shonky WiFi too, that can play a part.
Also, make sure in your phone settings under "General Management" then "Keyboard list and default" that you have set your Google Voice Typing language to Australian. I still have to be real slow and deliberate, but it's a bit better.
No worries on the expensive part, I hear you. It's shameful that the support for assistive tech on Android cuts off at about the point that the people who need it can afford it.
ill give those tips a try, thank you!!
I’ve had a lifetime of being on the shit end of the stick when it comes to “why can’t the person who needs X get it”, it really sucks. like “just buy an iphone” is what I was told asking around elsewhere and like... my guy, an iphone is basically a month of my income (before spending a cent on rent, bills, food...)
I just hope that bad things happen to the people who uphold the oppressive systems that keep me down. thats all :)
I hear you. DSP does not pay anywhere near enough, especially with how much medical stuff costs these days and close to no bulk-billing doctors left. And physical stuff like even basic switches are ridiculously expensive, even more with the NDIS rorting companies are doing. Assistive tech physical and socio-economic accessibility is something I've been ~~angry about~~ thinking a lot about lately.
looks into camera dramatically yeah DSP money sucks, good thing I can’t get it :)
I’m in the jobseeker hell until I get an assessment redone, which is an “indefinite wait plus at least a year” away. which is fine, its not like my wheelchair is half as old as I am or anything
Ugh, I am so sorry, even if I'm not at all shocked to hear that. Our society treats people shamefully, even if it's still much better than many other places.
maybe a flagship from a year or two ago
Is that not what an S10e is?
Sadly no, s10e launched March 2019, 4 years ago and was specifically the non-flagship price compromise version of the s10 and s10+.
I wish a couple of years didn't make a big a difference as it does.
2019 was 4 years ago, I just upgraded from a phone I bought in 2019
Not to mention that it isn’t dependent on the phone since it’s a standard android app
Standard Android app on a Samsung implementation of an Android OS UI. These things are not as deeply intertwined as they might seem. Not even the different Android Accessibility apps and settings are guaranteed to work well together, because they're often made by entirely different teams.
I've actually found voice recognition to be worse than it was prior to Android 12. As soon as I got that update, it started having more errors.
It could be coincidentally in line with you getting gunk in your mic or something. Or it could be that your particular phone doesn't handle android 12 very well. I've had less issue with voice recognition on android 12 and 13. Maybe try re-training the voice model.
I have one of the newest Google pixels, so it's probably not that. I've retrained it a couple of times and gave up. 🤷♂️
I swear, google's quality control on the pixels is just bad. I had a Pixel 5a, when I got it, the phone was a year old. Out of the box it was slow, I tried so many things to get it working correctly and it just never did. Then 7 months in it just died.
After a ton of back and forth with support and them trying to tell me I had water damage when I didn't, I finally got another Pixel 5a. That one works super well in comparison. I didn't use it much because I was so fed up with the whole debacle with Google that I switched to an Asus Zenfone 9. But the little I did use it, it was faster than the other 5a ever was.
My first pixel 5a almost never picked up my "ok Google"s whereas my Asus Zenfone 9 works while it's playing music full volume, or while I'm playing music in the car, and a ton of other situations where my pixel and my galaxy s9 I had before never did. It's so odd.
That being said, the Zenfone is way worse at shazaming things for some reason. I definitely think it's not only a per phone model basis but also a per singular phone basis thing.
Yeah, I've had three Pixels now and I won't be getting another. I mostly just went with them because I need something small (and even their a series Pixels are not really small).
I recommend the Asus Zenfone line, flagship processor for a reasonable price (relatively speaking) in a small form factor. It's a godsend for someone like me with small hands. I've had mine for a year or so and I really love it! And I hear the Asus Zenphine 10 is even better.
I am actually planning to get that when the new one comes out. Thanks for the recommendation, though!
I'm not a full time voice assistive tech user but I have a some experience in this area. Can you tell me which gestures you're missing / functions you're unable to activate and unexpected behaviour? Is it specific apps or websites, or all of them?
Voice Access does have a few settings which have helped me make it a little more reliable (it does not like my accent sometimes, especially if there's background noise) but without knowing more about the specifics it will be hard to tell whether there are some easy possible fixes or workarounds for the issues you're having.
the big issue is only being able to swipe left/right in the middle of the screen, I can’t scroll through pages of quick settings, the share dialog, or really anything that doesn’t appear in the middle. same issue with scrolling up and down, too, I have my font size bumped up a bit, so the “start screen recording” button needs to be scrolled down to, but you only scroll the button itself which voice access won’t do. theres some other examples but you get the idea.
occasionally if I say a command, it does it twice. I’ve had it happen on “tap X”, on saying numbers like in “show grid”, and sometimes (especially confusing) things like “send” sending a message and then typing the word send.
i also get lots of strange site specific bugs, like on mastodon I have to say my post in a single take, because saying a second sentence will clear what it already wrote. theres been way too many site specific bugs to list, but I run into them often.
also it understands me very poorly, I’m a native english speaker with an australian accent for context, and it really struggles with understanding me. short commands like “four” to tap label 4 are especially rough, but it takes me a few tries even with longer commands. theres not enough of a pattern to say its definitely an accent thing though. (talon does make some mistakes that are accent based, so its likely a factor. but it also makes way less mistakes than voice access with the same mic, so... shrug)
Ok yeah, I'm beginning to understand your problem.
Firstly, I haven't opened Voice Access in a while, but this is definitely worse than I remember. Some of it seems to be Android's fault, some of it seems to be Samsung's, but there is definitely some bad behaviour going on especially with magnification. It looks like Samsung's menu and overlay implementations are not working properly with Voice Access' magnifier, the show numbers and labels commands are all over the place. When using Voice Access' screen magnifier, they have also allowed for swiping to occur off-screen when zoomed in... so sometimes it swipes the wrong place because it's trying to do it from the centre of the edge, and sometimes you see nothing happen because that edge of the screen is out of view... Shonky work.
The good news is there's probably some workarounds for this. I'm constantly using grid mode ("show grid" / "hide grid" / "tap <square_number>" / "more squares" / "fewer squares" / "swipe <direction> <square_number>", "scroll <direction> from <square_number>" etc.), which reliably accounts for only gestures on the parts of the screen you can see and overrides most other menu, website and other interface items.
It looks also like the Phone Settings > Accessibility > Interaction and dexterity > Voice Access > Settings > More Options > Show Borders On might work a bit better for the "Show numbers" and "show labels" problems with screen magnification. It looks like I have to sometimes hide and then show them again after zooming in or out to get them to recalculate their positions, but it's better than trying to navigate with borders off.
duplicate commands
I did just have that happen. It looks like it might have to do with CPU or memory consumption, things seem to slow down while VA is going. You might have better luck if your apps that you're not actively using are fully closed, and you don't have 5000 chrome tabs like I do. This will definitely present issues for screen recording in addition to VA, along with other heavier tasks.
i also get lots of strange site specific bugs, like on mastodon I have to say my post in a single take, because saying a second sentence will clear what it already wrote. theres been way too many site specific bugs to list, but I run into them often.
Site specific bugs are usually because people are shit at accessibility. If you can send me an example link where I don't have to have an account or log in, i'll see if I can debug this one for you and get an issue opened if there's something they've done wrong. Site specific bugs can sometimes be worked around with a different browser though too, browsers are also shit.
also it understands me very poorly, I’m a native english speaker with an australian accent for context, and it really struggles with understanding me.
You're not fucking wrong, it keeps thinking i'm saying "Shore" instead of "show" and "top" instead of "tap". This was not this difficult previously, even in a noisier place. I am not sure what is going wrong here, but I can see that the settings for various language interace things are all over the place, it might be something buried deep in a menu somewhere. If you're able to speak really slowly and precisely, that will help, but I have no speech impediments and it's fucking driving me nuts. Make sure there's nothing rubbing against the mic or touching it too.
This is truly a painful UX experience, I'm sorry. Let me know if there's anything else I can maybe find an alternate action for that's more reliable, this is ludicrous.
this is super helpful, thank you. didn’t know about the “scroll <direction> from <number>”, thats genius.
also ill experiment with browsers, I’m using firefox since its what I use on my PC, but all the android browsers are haunted in their own ways. if I find anything consistently broken that doesn’t need a log in or credit card, ill give you a shout
No problem, you got lucky my brain is mostly working today and that this topic is in my very niche wheelhouse.
It also really grinds my gears that there is no documentation I have found for the actual full list of commands in VA and that I've had to trial and error discovery some of them. As though user interfaces weren't hard enough for people who use alternate input methods already. None of this should be this hard for anyone.