Every time I open A2DP Volume I'm asked for the TTS app to use (Complete action using...)

[GoogleCodeExporter]

Device (phone) brand: Samsung
Device (phone) model: Galaxy S 2
Android OS version: 2.3.3
App version: A2.3.8 or main
What steps will reproduce the problem?
1. Install A2DP Volume
2. Enable text reading for a car kit. I set the output stream to the call 
stream as last time it was installed I used the default which does not work if 
the
3. Open the app from either Applications if not running or from the 
notifications pull down if service running.

What is the expected output? What do you see instead?
Once this has been set for a device once I don't expect to be asked for it over 
and over again when I open the app.
This could be user error but I could find nothing in the manual to suggest what 
I should be doing.

Please provide any additional information below.
What does "Set as default" do on the "Complete action using" pop-up? As I don't 
know what it is setting the default for (device, app, handset...) I don't know 
whether to use it. Also, shouldn't the handset wide setting of TTS be ("Always 
use my settings" ticked in "Text-to-speech settings") obeyed?

Good app generally - plugs a problem with media playback over bluetooth. Thanks.

Original issue reported on code.google.com by nigel.tr...@gmail.com on 15 Sep 2011 at 9:48

[GoogleCodeExporter]

You need to check the "always use this" when it asks for tts engine.  Until you 
do that, it will always need to ask.  I need to mention this in the 
documentation.  Thatns for posting the issue.

Original comment by JimR...@gmail.com on 16 Sep 2011 at 12:08

• Changed state: Started

[GoogleCodeExporter]

Ah so it is user error - thought it probably would be.

There is no "always use this" checkbox for me - just "Set as default" which
seems to me to set the default for the handset.

In Settings->Voice input and output settings->Voice output->Text-to-speech
settings I have always use my settings checked and in Default engine I have
Pico TTS set. And still I get asked the question every time the app
starts...

Is this an Android 2.3.3 bug? 

Also, in the settings in A2DP Volume for my car kit I keep checking
"Set-in-call phone volume on connect?" and when I return to the settings it
is unchecked again.

Original comment by nigel.tr...@gmail.com on 16 Sep 2011 at 10:09

[GoogleCodeExporter]

Are you saving your device settings or just using the back key?  There is a 
[save] button at the very bottom.  If you use the back key, no settings will be 
saved.  That is different than the app preferences, where the back key does 
save the app preferences.  This is due to the implementations.  The preferences 
use a standard Android interface.  The device specific settings use a custom 
UI.  If this still does not work there could be some sort of database save 
effor I guess.  To clear than you must delete the database and start over.  
From the main screen in the app, use [menu] then [delete data].  When done with 
that click the [find devices] to reload all your devices.  Now you can 
configure them, making sure to save of course.

When the dialog asks for which to use, you must first check the "always use 
this" box at the bottom left, then select the TTS engine of your choice. Is 
that what you are doing? I think that is what you said above but need to be 
very clear.  I will test with my daughters Droid 2 with 2.3.3.  I have a Droid 
3 which has 2.3.4.

One other thing to try after you get all the settings correct.  Reboot the 
device and see if it still has the problem.  Let me know how this all goes.

Original comment by JimR...@gmail.com on 16 Sep 2011 at 10:46

[GoogleCodeExporter]

Jim you are right, I keep missing the save button as the keyboard gets in
the way. Sorry - that definitely is user error. Phone volume setting working
fine.

When I start the app... I get a pop-up, standard looking dialog which has:

    Complete action using

    Pico TTS
    Samsung TTS

    [] Set as default

Thing is I have already set the default in the Android settings - this is
what I meant by:
    In Settings->Voice input and output settings->Voice
output->Text-to-speech settings I have always use my settings checked and in
Default engine I have Pico TTS set.

I just wish T-Mobile would allow the 2.3.4 update firmware out for the
Samsung Galaxy S 2

Thanks for your help.

Original comment by nigel.tr...@gmail.com on 16 Sep 2011 at 11:05

[GoogleCodeExporter]

I just tested with a Droid 2 again (with Android 2.3.3) and it worked fine on 
all streams.  However, I tested with a friends Droid X running 2.3.3 and he had 
the same issue.  It would not read the message.  He kept getting the dialog 
asking him to select a TTS engine too.  I will continue working this with his 
device and hopefully have a solution soon.  I think it is an issue with TTS.

Original comment by JimR...@gmail.com on 17 Sep 2011 at 11:54

[GoogleCodeExporter]

Thanks Jim, you're a star. Specific to the firmware then perhaps. 

Original comment by nigel.tr...@gmail.com on 17 Sep 2011 at 9:52

[GoogleCodeExporter]

A few things to try:

 # Make sure Pico TTS engine is installed and working.  Here is some more info:
http://code.google.com/p/a2dpvolume/wiki/Reading_SMS

 # Make sure your TTS engine has updated data.  You can find out by testing in the settings menu of Android.

 # If you still have trouble after completing above, try uninstalling any other TTS engines.  Reboot the phone after you are done.

Original comment by JimR...@gmail.com on 17 Sep 2011 at 10:07

[GoogleCodeExporter]

We got it working fine now on the Droid X with the T605.  It previously had 
this same issue.  I will get the details and post here.

Original comment by JimR...@gmail.com on 19 Sep 2011 at 2:11

[GoogleCodeExporter]

The problem with the fix on the Droid X is we are not sure exactly what fixed 
it.  He reset the phone to factory defaults, however the problem was still 
there afterwards.  Then he went into [settings] -> [voice input and output] -> 
and [listen to example].  That did not work at first but when he tried it a 
dialog asked him to install the language data, which he did.  Then he tested 
again the same way.  Now it worked.  Once he got that working, A2DP Volume also 
worked.

I think the trick is to get TTS working on the device first by making sure 
[listen to example] works.  Does this fix your problem too?

Original comment by JimR...@gmail.com on 19 Sep 2011 at 9:42

[GoogleCodeExporter]

Hi Jim,

Sounds frustrating. TTS is working fine on my Galaxy S 2 - always has been.
E.g. Android tells me when e-mail or SMS messages arrive...

Original comment by nigel.tr...@gmail.com on 19 Sep 2011 at 9:57

[GoogleCodeExporter]

Nigel:

Does this app also work fine for you?  It was not clear from the comment.  

A2DP Volume works fine for most but some have had issues getting TTS set up in 
general.  Of course this app takes a hit for it.  

It just got a comment on the market blaming A2DP Volume for leaving GPS ON and 
killing the battery.  This is actually a known issue with Android and it 
happens randomly on any app that uses GPS.  I blamed the developer of GPS 
Status for the same thing but later found out Google Maps does it too.  

Original comment by JimR...@gmail.com on 20 Sep 2011 at 2:42

[GoogleCodeExporter]

I'm not sure which app you are referring to. "listen to an example" in voice
settings works fine. Sorry if I'm being a bit dense.

Volume

up

Original comment by nigel.tr...@gmail.com on 20 Sep 2011 at 5:09

[GoogleCodeExporter]

The a2dp app works fine for me - I don't use the location storage feature.
There is just the slightly annoying tts selection pop-up, but that seems
like it is a standard Android dialog.

It seems like Android 2.3.3 has a few features on my Galaxy S 2.
On Sep 20, 2011 6:09 PM, "Nigel Trousdale" <nigel.trousdale@gmail.com>
wrote:

voice

ON

too.

Original comment by nigel.tr...@gmail.com on 20 Sep 2011 at 5:34

[GoogleCodeExporter]

So far this has always related to TTS install/configuration issues.

Original comment by JimR...@gmail.com on 30 Oct 2011 at 8:00

• Changed state: CanNotFix