Database Users

how do i do voice dialing?

hi i was curious if there is a quick way for me to do voice dialing on my evil ?
Sent from my PC36100 using Tapatalk

RichTJ99 said:
hi i was curious if there is a quick way for me to do voice dialing on my evil ?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
on your evil? Try dialing 666 to enable it.

In all seriousness, is there a way to do voice dialing on the EVO?

Vlingo voice. Find their sight and search cause right now it's by invite.
VVVVVVVV
Vlingo Android Beta Test Opportunity
New SuperDialer Product Testing
Hello Android Users,
Thanks for volunteering to be part of our Android test crew! We have a new beta launching and hoped you might be able to lend a hand.
How Can You Help Us Out?
This beta is focused on a new product, codenamed "SuperDialer." It's even cooler than it sounds, if that's even possible. It really is a pioneering product that allows you to call any business, anywhere, anytime, just by speaking a few words to Vlingo. After that, you can review ratings, get directions, call with just one-click - just about anything you would need.
We would appreciate it if you focused your testing and feedback on this specific product. Sure, if something else jumps out at you, we're always happy to get your thoughts. But the new functionality is really all around SuperDialer, and that's what we could use your perspective in fine tuning before the public release.
Be thinking of things like:
How useful is this in my everyday life? Is the user experience easy and intuitive? How does this compare to other stuff on the market? What else would be great to include? Is there anywhere SuperDialer breaks down?
Of course the application still has all the same functionality of previous versions - send texts and emails, update Twitter, search the web, voice dial friends from your address book, etc. So please feel free to use those as you normally would. We just want to focus your feedback on the new SuperDialer product.
When Would You Use SuperDialer?
Short answer
Any time you need to make a phone call to a business that isn't already in your address book.
Long answer
Friends in town and you want to make dinner reservations at your favorite joint, but don't have the number handy?
SuperDialer.
(Tap & Speak: "Call Toro")
Desperate for General Tso while in an unfamiliar neighborhood?
SuperDialer. (Tap & Speak: "Chinese food")
Forgot your sister's birthday and need a flower shop near her apartment for a quick delivery?
SuperDialer. (Tap & Speak: "Find a flower shop on Greenwich Ave in Manhattan")
How Do I Install Vlingo?
*** Note: Must have OS 2.0 or 2.1 to Download ***
1. Check the Unknown Sources item in Settings > Applications
This is required since Vlingo this version of Vlingo is not yet available in Android Market
2. Please be sure to uninstall all versions of Vlingo before you download the new beta.
Settings > Applications > Manage Applications > Vlingo > Click uninstall button
3. To install the beta:
a. Visit http://vlingo.com/androidbeta from your Android

TTS Discussion

Hi. This thread is made to bring all text to speech related topics in one place.
Post all your TTS queries here.

my queries
Which is the best free TTS engine? and which is the best paid one?
Also which is the best ebook reader with tts support?
Is TTS very taxing on the cpu? Does it drain battery quite fast or not?
Please reply.

I have a problem with Pico TTS. If I uninstall it, on boot the home screen is unresponsive until I press the Home key or the Back key. I'm on stock ROM with franco v14.1 kernel.
The problem goes away if I reinstall Pico TTS.
How do I fix this?
Sent from my LG-P500

VTTS Text-To-Speech service https://vtts.xyz/home lets you instantly get a human sounding voiceover. It is super easy to use. Just paste the text you want to be transformed into our online text editor and let one of our A.I. engines check your text and will add all the punctuation marks needed to make the speech sound natural. You can preview each voice to hear and find the one that best fits your needs. Also, you can add breathing sounds, longer pauses in the speech and even choose the tone of the speech: Serious, Joyful or just normal. In less than 10 seconds you’ll have your voiceover generated. You can play the voiceover directly from VTTS to see if you like it or you want to try a different voice go to: https://vtts.xyz/home/tryme
Transform any text into speech, Male & Female voices included. The only text-to-speech engine that adds inflections in the voice. Over 30 human-sounding voices

KODI with - amazon voice search :D (proof of concept)

Hi Guys,
I managed to root my FireTV a few days back, and yesterday decided to look at the voice search to see if I could use it for other things.
After reversing some code, I found the actual voice search is handled by com.amazon.vizzini.apk
The SearchOverlay.class has this piece of code, which calls back to the amazon fireTV UI SearchResultsActivity upon completion with the search result returned as a string.
I replaced the fire TV UI with my own code, which receives the search text, and then sends a JSON rpc to KODI's web interface, and brings KODI to the front after the search is completed.
Here is a video of it in action.
http://youtu.be/hpgKci_gJYY
android studio project
http://uptobox.com/ccykod7zua1l
mirror
http://www107.zippyshare.com/v/mAhl3UuM/file.html
***** I have a FireTV v1 updated to fire os 5 ******
I have no idea if this will work on older versions of software.
To make it work you will require ROOT, and you will have to uninstall or move the existing fireTV amazon UI.
Reason for this is that the vizinni.apk calls back to
localIntent.setComponent(new ComponentName("com.amazon.tv.launcher", "com.amazon.tv.launcher.ui.SearchResultsActivity"));
So your activity has to be in that package, and called SearchResultsActivity.
The only other way to possibly get round this would be to modify the vizinni.apk to call a different package instead, but then voice search wouldn't work on the amazon UI anyway. I wasn't really bothered about the amazon UI working myself which is why I did it the way I did.
I just moved the original system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk to /system then installed my code via android studio.
mount -o rw,remount /system
mv /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk /system/
You will also need to change KODI's settings to enable web interface control on port 8080.
On my setup it was .. system.. services.. webserver.. and tick the box that says "Allow control of kodi via http" and make sure the port is set to 8080.
edit: 07/07/2016
I did start work a few months back on an Xposed module (works but not 100%), I was going to add a settings page but I think there was issues with xposed on android version that the fire tv runs on, due to permissions etc.
You can set a prefix in the code (currently hard coded to KODI) so if you say " kodi star wars" it would pass the param of "star wars" to kodi.
If you just say "star wars" without the prefix it would pass this to the normal amazon UI.
If anyone wants to take it further, it's attached on the link below.
http://uptobox.com/ensqll4a7r65
Mick

Thats actually pretty great.
Conventional wisdom was that both voice recognition and response "results packaging" was done server side - and the only return query you could get were preexisting amazon database references - not the result of the initial voice recognition.
I've actually read that multiple places - but as it turns out, no one had bothered reversing the process I guess.
Major props and thank god for overlays containing strings... Finally - that microphone might not be so useless after all..
Next step - implement it to interface with google search. (Weather in ...)
edit: Actually - there are three interesting usecases I can think of on top of my head...
1. Launch other Apps (maybe even with "fixed Keywords (App 1 f.e. would work edit: "Number 1" delivers better results. )" if App names arent known to Amazon) - so thats text>launcher app - see if sphinx02 has any interest in coding that as part of Firestarter..
2. google search (Whats the weather in.. ) text>google search app (if possible)
3. direct text input as seen in the POC video
edit 4. forward to Amazon - not to "break" their implementation
This could be realized by a quick 4 way select screen (just confirm with the direction button) after you select the string in the overlay.

great find and implementation. would love see more expansion as above post mentions. Are you planning to share fire tv UI code?

I was playing with voice search strings and found that Amazon tends to strip out "Google" in front of search queries -so instead of "Google how is the Weather tomorrow" only "How is the weather tomorrow" will get returned.
But - Alexa as a trigger word will be returned fine, so - I vote for using "Alexa" as a trigger word to forward all search queries to the google search app.
Ok - maybe not - but conceptually, this would be a great "work of art".

An even better idea than Harklekinrains' would be to check the foreground app and do different things based on that. For example, if Kodi is open it could send the intent to Kodi. If the Fire TV launcher is open it could fall back to default functionality, etc. Simulating keystrokes could also cover 99% of the other applications. I'm excited for this. It really makes the Fire TV so much less of a novelty.

I've just updated the original post with a copy of the android studio project, and a few more details.
Mick

Great mate,thanks! gonna check it out soon!
One question (as im not firm with intents and stuff): aint there a possibility to listen for intents sent to the amazon ui and catch them? Personally, i dont care too much about it right now as im using nothing but kodi, but maybe some day when wanting to use prime or similar stuff?

dafunkydan said:
Great mate,thanks! gonna check it out soon!
One question (as im not firm with intents and stuff): aint there a possibility to listen for intents sent to the amazon ui and catch them? Personally, i dont care too much about it right now as im using nothing but kodi, but maybe some day when wanting to use prime or similar stuff?
Click to expand...
Click to collapse
I don't think so as the actual code in the vinizzi apk is as follows:
Intent localIntent = new Intent();
localIntent.setComponent(new ComponentName("com.amazon.tv.launcher", "com.amazon.tv.launcher.ui.SearchResultsActivity"));
localIntent.putExtra("identifier", null);
localIntent.addFlags(402653184);
localIntent.putExtra("term", str);
localIntent.putExtra("text", str);
localIntent.putExtra("source", "VOICE");
localContext.startActivity(localIntent);
So basically when it receives the voice search response from amazon's server, it's starting the activity com.amazon.tv.launcher.ui.SearchResultsActivity from package com.amazon.tv.launcher
Mick

Integrating the search attempt based on the previous foreground app would mean that "voice search" could never "initate a new attempt". This would prevent the "lets just ask google, or lets launch an app - impulse use" of the feature. Still - in the long term it might turn out to be the right approach - f.e. if
"People tend to use the the google search only lets say "half a dozen times", and in the majority of cases just want text input in Kodi" Also - without having a select screen with "four (dont make it too many) predefined "use options"" discoverability is pretty non existent. People would have to read readmes to find out which interactions are supported.
Also Amazon wants you to "be able to always reach the Amazon content search from anywhere" - so, political implications.
Also - each time a new app would want to integrate the voice to text feature - they would have to contact the devs of this project - if you dont use "just text input" as a default in the "use the previously open app as an indicator of intent" approach. So make sure you default to "just text input" in that case. (Amazon launcher > forward query to Amazon (do not break functionality), ....)
Dont implement it as a mixed approach though as "Kodi is open most of the time" probably for most people - and the intent (message) gets "confusing".
--
What you probably shouldnt do - regardless, is to use "trigger words" as an "indicator of intent" - because Amazon can start blocking them. "Number 1" is probably generic enough so they wont try to block that - but in principal, they can. Also Amazons "voice to text" engine is optimized for "short phrases" - the longer your input query gets the more prone to errors their results become. Leave the actual "voice input" as "natural" as possible (dont embed logic there). Imho.

I'm in the USA and uptobox.com is not available in our country.
I want to give the source a look and see what I can do to contribute.
Can you put it on github or somewhere else?
Much appreciated.

kratosjohn said:
I'm in the USA and uptobox.com is not available in our country.
I want to give the source a look and see what I can do to contribute.
Can you put it on github or somewhere else?
Much appreciated.
Click to expand...
Click to collapse
I've just uploaded it to zippyshare too. Link added to original post.
Mick

It would be nice if this could be generic way of entering text in any app, similar to the FTV Remote App that has keyboard support. I am surprised Amazon has not done this already. If you are in a text field voice search would fill in the text, else it can continue with normal Alexa functionality letting you " always reach the Amazon content search from anywhere". Should be an easy solution for Amazon to implement, not sure if it could be added with the progress here, and it would really make the voice control so much more useful.

Hey Mick, as im still very exited about that (so frustating to enter searchphrases with a dpad...), i thought about what your great find could develop to. I hope u dont get me wrong, as i unfortunatly cant contribute any programming (if u need something made with tasker let me know ), its not that i want to demand anything - rather share my thoughts or ideas...
- I think its a good thought not to 'blow it up' by adding many keywords, make it more complicated, and avoid amzn to lock features down. even if it may be an abstract fear. I think with a well-structured menu in kodi, all apps one will need to start are just 2-3 clicks away.
- if i got it right, xposed could hook into every module and alter it, right? so basically it should be possible to avoid to exchange the amazon ui and/or alter the vizinni.apk,but just modify the SearchOverlay.class? wouldnt it be (on top) the most convenient way to decide wether one is on e.g. Amazon Prime, or on kodi, and either hand over the result to the original module, or hand it over to kodi?
So, please understand my post as a mixture between sugestions and questions, not as a demanding 'please make it how i want it asap'. Im really excited about your finding, appreciate your sharing, and want to contribute what i can do - unfortunatly its rather thoughts and suggestions. Cheers mate!

Great Work !!! I totally understand this is for amazon Fire products only. My question is would we be able to port for generic Android TV box like nVidia Shield which also has mic capability and comes with root support.

Good job @is0-mick it's great to see you accomplish something that Netflix doesn't even want to be bother with on their app.

harlekinrains said:
No you dont understand. You havent even read or understood the first posting - but you have bought another device and now want others to move in your direction on your behalf.
Click to expand...
Click to collapse
Seriously mate if XDA bothers you so much, you need to take a break from it for your own sanity!

fach1708 said:
Seriously mate if XDA bothers you so much, you need to take a break from it for your own sanity!
Click to expand...
Click to collapse
No, I really don't think he needs to take break, his argument is completely understandable. This is not a Shield forum (btw before we make judgements, I own both devices). We need to get this fixed for one device, before even mentioning whether other devices are an option.

is0-mick said:
To make it work you will require ROOT, and you will have to uninstall or move the existing fireTV amazon UI.
Reason for this is that the vizinni.apk calls back to
localIntent.setComponent(new ComponentName("com.amazon.tv.launcher", "com.amazon.tv.launcher.ui.SearchResultsActivity"));
So your activity has to be in that package, and called SearchResultsActivity.
The only other way to possibly get round this would be to modify the vizinni.apk to call a different package instead, but then voice search wouldn't work on the amazon UI anyway. I wasn't really bothered about the amazon UI working myself which is why I did it the way I did.
Click to expand...
Click to collapse
Is it not usefull for this to create a xposed mod? I thought xposed was made for this...
Perhaps you should talk with rbox in his thread about a integration into version 1.5 of his mods, look here.
is0-mick said:
I just moved the original system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk to /system then installed my code via android studio.
mount -o rw,remount /system
mv /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk /system/
Click to expand...
Click to collapse
So does that mean, while you are using your proof-of-concept you can not use the normal Launcher-UI?
Really great your work! I hope we got more
Sadly I am with my FireTV-Stick (hardware-Rooted-superSU) and my FireTV box gen1 (hardware-Rooted-superSU+custom-recovery+unlocked-bl)on the old FW. I wait for custom roms.
Greetings by Idijt
EDIT:
I forgot to ask you something. Did you got the kind of search-request back?
Can you see if amazon-voice-rgn knows if it is a app or a video or a moviestar?

This looks pretty cool since I don't like typing the name of the movie in the search box... now I can just speak it.
As a novice I have one question, You wrote:
is0-mick said:
I just moved the original system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk to /system
Mick
Click to expand...
Click to collapse
The code I downloaded was in .RAR format not .apk. Do I need to covert it to .apk or rename it to .apk before replacing the original?
I've not rooted my device yet so I haven't looked at the file structure, but I'd be willing to root to get this feature. OR is the adding of this code better done by someone other than a novice?
Thanks

carpenter940 said:
The code I downloaded was in .RAR format not .apk. Do I need to covert it to .apk or rename it to .apk before replacing the original?
Click to expand...
Click to collapse
It's the source code. You have to compile it and create the apk with AndroidStudio.

Google Voice Search blocks voice calls

Hi there
My "ok google" from any screen is working. But when i get calls over bluetooth the caller can only head some strange sounds (beeps...). After closing all google apps, the calling works again.
Anyone other with this problem?
I made it with this turtorial:
-- Download the Google Voice Services...
For Android 6: https://forum.xda-developers.com/and...1/post72179874 - Then navigate to the google drive link.
For Android 5: https://forum.xda-developers.com/and...1/post72180072 - The navigate to the github link.
-- Although you won't be using the keys or steering wheel controls, you still need the custom keys APK as it has some core components to make Ok Google work. For Android 5.1.1 you need version 4.2, for Android 6, you need version 6.2.
Download from this thread: https://forum.xda-developers.com/and...l-key-t3543390
IMPORTANT NOTE THAT THE Sofia 1 C9 Serv APK included in 4.2 does not allow you to adjust the alarm volume which is necessary to hear voice feedback. You MUST use the one listed in my next bullet.
-- Ok Google works from any screen, however; the reason the google speech is not audible is because it is played through the "Alarm Volume" which is always muted and a modification must be made to adjust it...
To adjust the ALARM Volume:
Download the Sofia 1 C9 Serv APK from this post - https://forum.xda-developers.com/sho...&postcount=381 - and install in the following folder "system/app/Sofia-1-C9-Server-V1.0"
Afterward, inside the google app will appear "Enable Voice Search from Any Screen" << previously this option is not available.. now you can activate it and use it from ANY screen.

Ivona TTS engine and voices

I'm still trying to work up a way to get a decent TTS voice engine on the NST, but what I have come up with so far may be of some use for Glow4 users who wish to try out TTS in reader applications with the Bluetooth capability.
First, SVOX, which was my primary target (because the voices are many and really, really good) looks hopeless. The engine installs OK and works all the way down to Android 1.6, but the voices--even the free "trials"--require PlayStore access to complete installation and SVOX is long gone from the PlayStore, so the whole thing just hangs. I've tried various dubious schemes provided by some users, including the full set of voice data, but they don't work because the app can't be made to see that the data is already present. At least that's my experience.
But Ivona! Also gone from the PlayStore, also works down to at least Android 2.1, and I just tried it on KitKat and it works very well there.
Here is a link to what is called a "complete" collection of voices as well as the engine: https://www.reddit.com/r/tasker/comments/dnspl3/tts_ivona_tts_engine_collection_all_voices/. Follow the directions for installation.
Alas, there are too few voices, and both English voices are female. I have a preference for male readers (please don't flame me...I have heard some very well-read audiobooks done by women) which is why I initially struggled with SVOX. That said, the Kendra voice is light-years ahead of the default Pico TTS voice or even some of the early Google TTS voices.
On KitKat, the change in engines is easy. Go to your Accessibiliy settings (well, if this is non-existent on a Glow4, someone will have to be creative...) and select Ivona, then configure the voice. This should result in a system-wide change. To test, I installed AlReader and opened a book. When I opted for TTS, Kendra started right up.
Alas, for the NST/G the story does not yet have a happy ending. The tts-extended service app does allow you to "change" the default engine, setup the default voice, configure it, etc. BUT, the vast majority of apps ignore these settings and use the Pico TTS engine and the dreadful voices included with that. According to the SVOX FAQ site:
Several apps support changing voices on Android 2.1: Talk To Me Classic, PDF to Speech, Smarter Alarm, Google Translate, and others. These apps use the Extended TTS API. Apps that don’t support the Extended TTS API, such as Google Navigation, only let you change the voice on Android 2.2 and later.
Click to expand...
Click to collapse
I take it from that there must be magic code which is not present in, for example, AlReader, which would allow it to use the Ivona voice. Apparently this problem went away with Android 2.2. Naturally.
So...I'm still poking around for a work-around.
Edit: Eureka! See post #2 below!

[NST/G] AlReader speaks!
I have finally managed to modify AlReader 1.77 to work with the Extended TTS API. This allows the settings app to select the default voice engine and voice, rather than simply defaulting to Pico TTS (which is what otherwise happens in Android 2.1). Having said that, I can't claim it's always pretty. It seems like the much more complex voice data puts a bit of a strain on the NST/G. Once it gets up a head of steam, it's not bad, but it is a little slow to start. It "may" help to play a section of a book using Pico or even espeak (see below) and then exit the reader, go back to the settings app and reselect the voice engine for one of the Ivona voices. I'm not quite sure yet, still playing around. Curious? There's a bit of work to do. Here's how:
1. Install svox and espeak voice data to your sdcard. Here is a direct link to the Eyes Free project code repository: https://storage.googleapis.com/goog...gle.com/eyes-free/voicedata-(espeak+svox).zip.
Unzip the file and copy the two folders of voice data to your sdcard. Without these files present, the next step will hang because it tries to download this data from the Android Market.
2. Install the TTS Service Extended app from the Eyes Free Project repository. Here's the link: https://storage.googleapis.com/goog.../code.google.com/eyes-free/tts_3.1_market.apk. This is essentially an Accessibility Settings app for TTS which includes a pre-Google Voice api to enable voice engine selection for apps that use the api. It also installs the espeak voice engine (worse than Pico, really).
If you run the TTS Service Extended app you will find the espeak voice engine as an option (on the second screen of settings). Pico is the default.
3. Download and install the Ivona voice engine and any voices you want as described in the first post. I have tried both Kendra and Amy. Localization doesn't seem to be an issue for this business, so you can select UK English even if your device is localized for the US. Or, there are a few other English voice options (Welsh, Australian). Knock yourself out!
4. Open the TTS Service Extended app and go to the end where you can select the Ivona voice engine, then configure the voice. Back on the first screen you can set the default engine (Ivona) and select the Language to use. Don't check the box to have this app override the settings of whatever app is using the TTS service.
5. Install the modified AlReader 1.77 (attached below). If you currently use AlReader, you will lose all your settings unless there is a way to back them up and even then they might not transfer since this modified app has a new signature. Not sure about that. You cannot install this modified version over your current version, but must uninstall the old version first. Caveat emptor, blah-blah-blah.
I never did find a way to get the TTS option into the slider menu system on AlReader, so I ended up assigning it to a tap on the header. But you can also use one of the 9 action tap zones to assign a spot to TTS.
I'd reboot. If you have some trouble initially, try changing the default engine back to Pico or even espeak, let it read a bit and then go back to Ivona. That may sort it. In the end, there may be a buffering issue because of the size of the Ivona language files. It's a miracle that I actually figured out how to do this by examining the smali files of the decompiled app and comparing them with the smali files of the TTS Service Extended app. Some pattern matching and lucky guesses eventually bore fruit.
I'm working on the FBReader TTS plugin next. It seems like it should be simpler, but it's not

Hi, I installed Ivona succesfully but today Amy stopped working...I saw a message on the app saying "This is not downloaded from Play Store" French is still working..i tried everything (install, reinstall, restart...) so I tried to follow your instructions to install the tts extended, but I don't find where to extract the first two folders...I would appreciate if you make it clear, Amy was amazing...
Thanks!

josh90sp said:
Hi, I installed Ivona succesfully but today Amy stopped working...I saw a message on the app saying "This is not downloaded from Play Store" French is still working..i tried everything (install, reinstall, restart...) so I tried to follow your instructions to install the tts extended, but I don't find where to extract the first two folders...I would appreciate if you make it clear, Amy was amazing...
Thanks!
Click to expand...
Click to collapse
Just so I am clear before I start in on this, are you talking about the NST? It sounds like you did not at first have the TTS Extended app installed. I don't see how the Ivona voices could work at all without that on the NST.

I was exprimenting with responsivevoice.org - with tablet other than nook
Idea was to send text to his server as a HTML with settings and get it back as an audio stream.
Now they need to create an account to get access - but using it will be free.

Ivona
"Just so I am clear before I start in on this, are you talking about the NST? It sounds like you did not at first have the TTS Extended app installed. I don't see how the Ivona voices could work at all without that on the NST"
Yes, I downloaded the ivona apk(one for each language) and then installed also the Ivona Text-to-Speech HQ apk. After, i placed the audio folder into Android/obb/ and opened the different applications, and signed the learning agreement.
So i could choose the Ivona engine from Settings menu and it worked, I was using Moon Reader and I used it for several days until yesterday, when the unpleasant Samsung english voice surprised me.
Since then, I am only allowd to listen in french voice, that's how I arrived here. I got the apk you were talking about and the two folders but I dont know where to put them in order to get the app to work. It says: downloading from play store and then it closes.
Thanks for your reply!

josh90sp said:
Yes, I downloaded the ivona apk(one for each language) and then installed also the Ivona Text-to-Speech HQ apk. After, i placed the audio folder into Android/obb/ and opened the different applications, and signed the learning agreement.
So i could choose the Ivona engine from Settings menu and it worked, I was using Moon Reader and I used it for several days until yesterday, when the unpleasant Samsung english voice surprised me.
Since then, I am only allowd to listen in french voice, that's how I arrived here. I got the apk you were talking about and the two folders but I dont know where to put them in order to get the app to work. It says: downloading from play store and then it closes.
Click to expand...
Click to collapse
I cannot reproduce what you are describing. I don't understand your comment about the "Samsung" voice. On the Nook Simple Touch there are only the Pico TTS voices possible (and only if you install the voice data--svox at a minimum). The only way to get anything else is to install the TTS Extended settings app and find (or create) an application that supports this interim step toward Google TTS (which arrived with Android 2.2). That's what I describe in the second post. First the svox voices must be installed. Then the TTS Extended app. Then the Ivona engine app is installed. Then the Ivona voice data is copied into the Android obb folder as described.
After this, the Ivona voice engine is selected in the TTS Extended app and a particular voice selected. Now, I have only used this a little and not over a period of several days, so maybe there is a trigger somewhere based on time, but my understanding of these voices is that even when available on the Market, they were free, so I'm not sure why there would be a time limit.
My NSTG where I have this installed does have rudimentary GApps. I'm not sure if that matters.

nmyshkin said:
I cannot reproduce what you are describing. I don't understand your comment about the "Samsung" voice. On the Nook Simple Touch there are only the Pico TTS voices possible (and only if you install the voice data--svox at a minimum). The only way to get anything else is to install the TTS Extended settings app and find (or create) an application that supports this interim step toward Google TTS (which arrived with Android 2.2). That's what I describe in the second post. First the svox voices must be installed. Then the TTS Extended app. Then the Ivona engine app is installed. Then the Ivona voice data is copied into the Android obb folder as described.
After this, the Ivona voice engine is selected in the TTS Extended app and a particular voice selected. Now, I have only used this a little and not over a period of several days, so maybe there is a trigger somewhere based on time, but my understanding of these voices is that even when available on the Market, they were free, so I'm not sure why there would be a time limit.
My NSTG where I have this installed does have rudimentary GApps. I'm not sure if that matters.
Click to expand...
Click to collapse
Thanks for your reply. Sorry if I wasn't clear, and I think I jumped into the wrong post. I am currently using a smartphone, I was looking for any help for my problem.
I will try to reset the phone because I was very happy with those voices.
Thanks again!