Yet another failure where google should be called out for not having a fallback tts engine for Talkback.
-
@Bri probably, but they at least implemented an advanced flow that I can sort of get behind, and reassured that ADB wasn't effected. so the bypass for the advanced flow delay is trigger it, install with ADB, confirm the advanced flow a day later and not deal with it again. There are apps that bypass the package installer on the play store itself.
@fireborn oh that's not the way I read it. I was under the impression that you had to confirm the sideloadd apps every 7 days or some shit, similar to AltStore on iOS
-
@FreakyFwoof My tts engine crashed, and talkback didn't try to do shit. I've implemented a safe mode in my screen reader that if restarted within 3 times in 20 seconds, it falls back to a bundled engine that cannot be overridden that lets you do whatever you needed to do.
-
@fireborn oh that's not the way I read it. I was under the impression that you had to confirm the sideloadd apps every 7 days or some shit, similar to AltStore on iOS
@Bri Not quite. After the first 24 hour wait, you can opt to allow sideloading any apk for 7 days, or indefinately.
-
@Bri Not quite. After the first 24 hour wait, you can opt to allow sideloading any apk for 7 days, or indefinately.
@fireborn Oh. That's the part I misunderstood. OK, well that's ... Fine, I guess.
-
@FreakyFwoof It's a work in progress. I have a very small internal testing team at the moment. Google's accessibility framework is very frajile and breaks if you even breathe on it wrong, so I'm optimising for an underserved market right now, that being tablets and foldables.
-
@fireborn Oh. That's the part I misunderstood. OK, well that's ... Fine, I guess.
@Bri It's at least less shit than the people on reddit are making it out to be. I will continue to use shizuku as I have for years to override the sdk checks and architecture limitations
-
@Bri It's at least less shit than the people on reddit are making it out to be. I will continue to use shizuku as I have for years to override the sdk checks and architecture limitations
@fireborn what's that. Root thing?
-
@FreakyFwoof It's a work in progress. I have a very small internal testing team at the moment. Google's accessibility framework is very frajile and breaks if you even breathe on it wrong, so I'm optimising for an underserved market right now, that being tablets and foldables.
@fireborn @FreakyFwoof Oh nice. Hopefully this will eventually fix that annoying thing where you have to wait for the screen to physically scroll before the next thing is focused, one of the things I like about VO on iPhone is the instant screen refresh where Voiceover is able to just find the next item even if its off the bottom of the screen. TalkBack, and other screen readers that I've tried, you have to wait like half a second for it to go dink dink dink and scroll to the relevant part of the screen and then put the cursor on it.
-
@fireborn what's that. Root thing?
@Bri Shizuku hooks into system APIs and you develop against it. It's like an abstraction. Needs root or wireless ADB, but can be started on device if you want to.
-
@Bri Shizuku hooks into system APIs and you develop against it. It's like an abstraction. Needs root or wireless ADB, but can be started on device if you want to.
@fireborn oh interesting.
-
Yet another failure where google should be called out for not having a fallback tts engine for Talkback. I just had to use a third-party screen reader, developed by one person (me) to recover a multi-trillion corporation's fuck up. This is fucking tragic. If you care about #accessibility, hound them. Please. Tell them this is an essencial recovery path. I can only do so much, I've been asking for a fallback for a tts engine failure since talkback 3.3. I can only do so much. Spam the shit out of every google engineer you know. Please. Get this fixed.
#1aay #accessibility #Android #inclusion #disability #activism@fireborn Are you behind Prudence?
-
@fireborn @FreakyFwoof Oh nice. Hopefully this will eventually fix that annoying thing where you have to wait for the screen to physically scroll before the next thing is focused, one of the things I like about VO on iPhone is the instant screen refresh where Voiceover is able to just find the next item even if its off the bottom of the screen. TalkBack, and other screen readers that I've tried, you have to wait like half a second for it to go dink dink dink and scroll to the relevant part of the screen and then put the cursor on it.
@alexchapman @FreakyFwoof It will not. That is a limitation of android I can't work around without developing a custom ROM, of which so few devices support these days it is not worth doing. A screen reader only indexes the vizible icons.
-
@fireborn Are you behind Prudence?
@mcourcel I am not, I don't know too much about what's going on with that project. As I said elsewhere, I'm mostly targetting foldable and tablet users, as we are an underserved market.
-
@alexchapman @FreakyFwoof It will not. That is a limitation of android I can't work around without developing a custom ROM, of which so few devices support these days it is not worth doing. A screen reader only indexes the vizible icons.
@fireborn @FreakyFwoof Oh damn, yeah that's one of the reasons I don't like using Android as a primary, if I'm trying to do something quickly and I'm being slowed down by stupid Android's accessibility framework limitation, its annoying.
-
@FreakyFwoof It's a work in progress. I have a very small internal testing team at the moment. Google's accessibility framework is very frajile and breaks if you even breathe on it wrong, so I'm optimising for an underserved market right now, that being tablets and foldables.
@fireborn @FreakyFwoof Yeah, I was going to install CSR, but it wanted you to turn on so many priviledges for it to work.
-
@FreakyFwoof My tts engine crashed, and talkback didn't try to do shit. I've implemented a safe mode in my screen reader that if restarted within 3 times in 20 seconds, it falls back to a bundled engine that cannot be overridden that lets you do whatever you needed to do.
@fireborn @FreakyFwoof since wen did you have a screenreader? i really wanna check it out once you releace it
-
@fireborn @FreakyFwoof since wen did you have a screenreader? i really wanna check it out once you releace it
@J3317 @fireborn @FreakyFwoof Personally I think ESpeak should be built into android. Because even I"m a bit skeptical about google tts. I don't use it and I'm sorry but. Google TTS shouldn't be default. If anything, it should be ESpeak. You might be like, well, why? Because it's more responsive than google.
-
@J3317 @fireborn @FreakyFwoof Personally I think ESpeak should be built into android. Because even I"m a bit skeptical about google tts. I don't use it and I'm sorry but. Google TTS shouldn't be default. If anything, it should be ESpeak. You might be like, well, why? Because it's more responsive than google.
@mckensie @fireborn @FreakyFwoof meh i could see that, but i don't like espeak, google should just make there TTS more responsive
-
@mckensie @fireborn @FreakyFwoof meh i could see that, but i don't like espeak, google should just make there TTS more responsive
@J3317 @fireborn @FreakyFwoof Not everyone likes ESpeak, I know. But it should be a fall back engine
-
@mckensie @fireborn @FreakyFwoof meh i could see that, but i don't like espeak, google should just make there TTS more responsive
@J3317 @mckensie @FreakyFwoof You liking it not the point. Boo-hoo, you put up with a voice you don't like to fix your phone. Deal with it. Espeak supports the most languages, so it makes the most sense.
