My review, why I returned to iOS from Android

again I completely agree with Josh Kennedy. The commentary screen reader has poorly written documentation if any. More over I shouldn't have to purchase the pro version through PayPal it should be freely available on the play store if it is legitimate.

Yeah, why commentary pro subscription can only be purchased from PayPal is rather suspicious. Not to mention,, I can barely find commentary manuals

Well I installed it in my main iPhone 13 pro. Very responsive, fast, and works well. Only issue is with notification. If I am using the phone via message or whatever VO will not read the notification. VO only reads it if I leave the phone alone. Hope RC will fix this. I am happy how iOS works well with my iPhone 13 pro 128 GB. No issues with focus and anything else. Maybe iOS 17 will be lucky iOS.

I can’t even download eloquence on my Google pixel, seven, running android, 13. Once android, 14 comes out, eloquence will be done, gone, permanently, off, android. Eloquence just isn’t 32-bit any more.

Why, does, every single bloody manufacturer, use a different version of android talk back? Just use Google, like please! This would allow people who are using Galaxy phones, tablets, etc, to switch to googles without having to use android, develop the bridge. Which, from my looking at, is very complicated.. Because you have to download the tools, download the app, go to settings go down to the about go down to the build number tab at seven times entering your credentials go back up. Go to wherever development options is in your settings up turn on USB debugging, and then use all these random terminals. Don’t make sense. You’re a person who doesn’t no trouble, just to install another manufacturer a screen reader. Bloody outrageous.
Not to mention, some people who don’t have computers, like, at all Cole, won’t be able to do this, like I don’t know

Who the hell allowed android devices to come up with the idea to have fingerprint sensors in the touchscreen, like I have a Google pixel, seventh generation, I have the fingerprint sensor activated, and it works and it worked once but the last 20/30/40 times I’ve tried using its yield with no result at all

I suspect if Apple comes up with it it will be accessible just like Face ID is. You aren't the only one to have problems with the finger print sensor. I have issues some times I know I have seen others having issues on Pixel devices with the finger print scanner.

Eloquence if you didn't purchase it when it was in the play store you can't get it on Android anymore. I agree with you about Talkback. That never made sense to me.

https://www.afb.org/aw/22/5/17556
So why are there still two different versions of talkback?

Open software unlike iOS which is close and control by apple.

in the closed Operating system of iOS a blind person can do system wide copy and paste. Why is this not possible on android? This has been requested for years.

You could get eloquent, but it had to be through in a PK file.
Are use eloquence every single day on my braille sense, and it’s an excellent experience.
I don’t think hymns will update the braille sense to support android 11, 12, 13 or 14 any time soon, so my braille sense will be stuck on android twin, which is actually pretty good because I can still use eloquence. I also can use eloquence on some of my other devices, including my iPad, iPhones, well, at least the ones running iOS, 16, and my NVDA.

Android has officially lost me. I downloaded your commentary screen reader, and there was a text to speech, and I wanted to use that text. Speech engine on my screen, reader that I have downloaded from accessible android, but I didn’t know that engine and also for you. So now my phone is not talking at all, and I don’t know how to get it back to operational species species screen reader.

Just come back to iOS and call it a day. You tried the other side it didn't work.

Is time to join the dark force. Come and let your frustration go and be part of the dark force. May the Apple be with you.

I agree with you 1 million percent.

Embrace the Darkside. We have cookies! 😁🍪

As soon as possible. I’ve got my text to speech engine, problem, shut out to Sally from accessible android. Anyway, so what I had to do was, in my absolutely furious, stated this point, I had to ask Google to open the speech output settings, not talk back directly. Since they want to screen readers enabled, I had to get to the text to speech output settings to switch stuff, preferred engine, to speech services by Google or whatever they are calling it now.. After I had open speech services by Google, I selected it as my preferred engine. Once speech was back, I turned off that of a screen reader. However, I feel that it’s absolutely outrageous that you have to do so many steps just to get your old text to speech engines back on talkback. It’s outrageous and is a waste of time. I will definitely be seeing about speeding up the process of getting my cousins iPhone 11.

I advise just hurry back to the dark side. If you can trade the Pixel for a better phone like an iPhone 13 pro do that

I tried android twice and prefer apple but took it back within the 30 day window and was able to swop my phones over,, I assume you're out of that windows date?

Join us and be happy but next time something cool comes out, be careful about buying it.

I agree with brad.

I'd recommend trading in the Pixel stuff back into Telstra and getting the cheapest iPhone on a plan - most likely iPhone SE 2022.

It may help to understand exactly what an "iPhone SE" model is. Hopefully this will help you make an informed decision.
To summarize both the 2nd and 3rd gen models utilize the iPhone 8 form factor. That is to say on the outside they look, function, and feel like an iPhone 8. On the inside is where they shine, however. The 2nd Gen version is basically an iPhone 11 scaled down to fit inside the chassis of an iPhone 8, and the 3rd Gen is an iPhone 13, also scaled down to size. There is apparently a 4th Gen in the works, but I don't believe a release date has been announced as of yet.
I put a couple of links below for you to compare the 2nd and 3rd Gen models. I hope you all find the info useful. 😎

• iPhone SE 2nd Gen (2020): https://support.apple.com/kb/SP820?locale=en_US

• iPhone SE 3rd Gen (2022): https://support.apple.com/kb/SP867?locale=en_US

I do miss the split tap on iOS though. That sure helped with typing out long posts, essays, comments, you name it. That split tap allowed me to be a very fast and efficient typist on iOS. Just sitting there on the bus, or standing somewhere etc. just pecking away at the onscreen keyboard like a chicken.

Split Tap is coming to Android, if it's not already implemented.

When will split up be introduced on android

Android 14 if I am not mistaken.

It's on Android 13 at least, in TalkBack 13.1 I believe. TalkBack 14 may improve it further though.

If you're alluding to that, I tried, but somehow not been successful with that.

So if it works properly, it works the same as the split tap on iOS?

Yes, in theory, it works just as it does with iOS.

Since the update to iOS 17 on my iPhone 13 pro. Reading from my Braille dsiplay within the iMessage app has become impossible. I can write and read within the edit feild when composing a message. However, when reviewing messages within the conversation window, Braille simpy isn't outputting from any Braille device that I have. Since I rely on Braille so much not just professionally but personally. This is making me reconsider Apple as my next phone. Every platform has it's flaws and issues there is no perfect mobile platform or software. However, for Apple to miss this critical feature especially for deaf-blind people is horrible. I've reported this to Apple and recieved the automated reply without any updates or confirmation of fixing the issue. I urge you to report the same issue if you are experiencing the same problems. We expect Apple and other companies to be AT companies knowing our needs as blind people. I'm not saying that Apple or any other company doesn't care about accessibility. I'm stating that input functions such as Braille should be taken into consideration and everything that a regular user would do should be tested to make sure hardware and software work together. Sure Google has some issues bu at least through Be My Eyes you can get through to a certified accessibility agent. The same with Apple but the difference is Apple wouldn't give you feedback. Google and other Windows based companies will and bring issues up the ladder of command. Critical issues / bugs that affect the work and lives of people with disabilities shouldn't be ignored or given automatic replies via email. It makes customers with disabilities question the company committment to accessibility and begin to wonder if they know or even care about their needs or the community as a whole.

I toggled on "Handle TalkeBack Gestures' in Developer Settings under Advanced Settings. Still can't get Talkback's version of split tap to work. I have set typing preference to their version of direct typing.

Keep in mind, I am running from 1UI 6 (beta 4) from my Galaxy S23+ in Purple and Android 14 is still in beta for both Pixel & Samsung. With that being said, Split-tap definitely does work allright with most of the standard Android keyboards (regardless if you have double-tap or lift-to-tap typing enabled).
Microsoft Swiftkey keyboard if used with Talkback (unlike with Jieshuo), is the only standard keyboard that will let you direct touch-type, and does not let you change to a double-tap .

I also have single-tap turned on under the Advanced section of Talkback Settings.

I type decently well with the Samsung Keyboard using one finger, shockingly. Unlike with IOS as most know, there is no quick path-typing feature (far as I know anyway), though predictive text works out extremely well with all keyboards I've tested.
Does that matter to me on my Samsung these days? Nope?

I am using the TalkBack Braille Keyboard from time to time in Tabletop mode, using North American Grade-Two. Not too shabby with said keyboard these days. And yes, that list of Braille keyboard commands has gotten a major update!

Anyway, that's all from me.
Off I go again...