View Single Post
  #14  
Old May 23rd 13, 07:10 AM posted to alt.cellular-phone-tech,alt.cellular.gsm,alt.cellular.t-mobile
Gordon Burditt[_40_]
external usenet poster
 
Posts: 1
Default Confirmed: You don't need a data plan for Android voice-to-text texting!

I was simply trying to find out the answer to the question since
I have no intention of getting a data plan - yet - the voice to
text is so very important that it was a godsend that it works
without having a data plan.

In fact, I want to get my wife an Android phone, so that she can
do voice to text ... so I needed to figure out if it was a Samsung
thing or not - since the phone I get for her might be a ZTE Concord
(as she doesn't need the other Android bells and whistles).

BTW, just to be clear, *I* didn't suggest it uses MMS; that is only
what I was told by the T-Mobile store when I asked if my data block
wasn't working. The T-Mobile counterperson said it uses MMS.

But now I'm curious if it will work on another phone, or if it only
works on the Samsung Galaxy S3.

If it doesn't use data, and if it doesn't use MMS, what specific
application is voice-to-text using? (I ask so that I make sure
*that* application runs on whatever phone I buy for my wife.)


If you (the app developer) wishes to do something complicated, like
voice-to-text, (or answering natural-language questions like Siri,
or turn-by-turn driving directions, or taking college exams for you)
you have a choice:

(1) Do it yourself on the user's local device, which probably has
problems with resources (program memory, working memory, processor
speed) and a tradeoff of doing a mediocre job reasonably fast vs.
doing a poor job quickly vs. doing an excellent job way too slowly,
(doing a really excellent job would identify the speaker, too)
or

(2) offload the work to something else ("the cloud"), using whatever
communication methods you have, such as (a) SMS, (b) MMS, (c) a
cellular phone voice channel, (d) internet access to a web site /
cloud server (requires a data plan) or (e) smoke signals from a
flaming battery, or

(3) split the job between (1) and (2).

Apparently *some* voice-to-text applications manage to do voice-to-text
somewhat decently using choice (1). Choice (1) *might* be made
easier on certain phones if there's dedicated hardware to help with
the job, although I tend to doubt it as it drives up the cost and
I don't think much marketing hype is used for that feature.

If you've got digitized speech, and you want text, without hardware
assist the job is essentially a big number-crunching job. Most
any system with enough memory and processor speed can do it. I don't
the Samsung Galaxy S3 is unique in that area (although it may be
a high-end phone.) Oh, yes, voice recognition requires programming
skill also.

My experience is somewhat limited to trying to use voice dialing
on my Blackberry over a Bluetooth headset. If I say numbers, it
does fairly well. If I try to say the name of a contact, it's
pretty awful. Trying to train it with my voice didn't help much.
I'm not sure the Bluetooth is really picking up my voice well.
Maybe I should try it with just the phone, although if I am holding
the phone in my hand, voice dialing is kinda pointless.