search

austgl / a2dpvolume

Automatically exported from code.google.com/p/a2dpvolume
0 stars 0 forks source link

Ford Sync causing problem? #192

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Device (phone) brand: Motorola
Device (phone) model: Nexus 6
Android OS version: 5.0
App version number: 2.11.11
What steps will reproduce the problem?
1.Phone is connect to Ford's sync system
2.This allows hands free dialing, answering of phone calls.
3.However to hear music or BT voices (like google map voice directions) the 
entertainment system source must be set to phone.

What is the expected output? What do you see instead?

Please provide any additional information below.
For other phone voices like google maps directions I have to tell the app to 
use the phone speakers. I don't use the phone as the car speaker source.  
Despite having read sms selected in the app, having my 3rd party sms app 
selected in apps for accessability, default tts Installed with no others I 
can't get sms messages read.

I'm not sure if alarm stream is the phones speaker but no stream works.

When I do put my car speaks on phone sourse I can hear the sms notification 
sound. Even then no stream reads the messages.

Original issue reported on code.google.com by soccergu...@gmail.com on 4 Dec 2014 at 2:30

GoogleCodeExporter commented 9 years ago 
First, read this for accessibility settings: 
https://code.google.com/p/a2dpvolume/wiki/Accessibility_Settings

This is also helpful for getting messages to read: 
https://code.google.com/p/a2dpvolume/wiki/Reading_SMS

This can be tricky unfortunately.  I have not had the time to work on making it 
better although the accessibility approach does seem much better.  I will 
eventually remove the separate SMS reading method as it is really redundant now.

As far as the navigation sound goes, I have this same issue.  Maps really needs 
to fix this by giving some more configuration.  Today, one app (like mine) 
can't manipulate the stream of another app.  This means I have no control over 
the maps and navigation streams.  I do have an issue here to look into ways I 
could maybe work around it.  Issue 63 
(https://code.google.com/p/a2dpvolume/issues/detail?id=63) is for this very 
topic.  It took me a while to figure out to use accessibility features to read 
out notifications so maybe there is a way to listen to the stream and repeat it 
over another stream.  

By the way, I am just one guy who does this as a hobby.  I make no money from 
this and I do it in my spare time (when I actually have some).  I wrote the app 
for my own use and decided to make it available to others for free.  I take 
user feedback to improve it.  With Lollipop coming to my device in the next few 
months, I will likely need to make an update to the app.  I always consider all 
the issues on the issues list when I make a release.  One big snag is my spare 
time will go to 0 as I mentor FIRST robotics kids and build season starts right 
after the first of the year. It could be almost April before I actually get 
time to make any changes.  It would be great to get some more developers 
working on this app but its hard (not impossible) to find good developers 
willing to work for free.

Original comment by JimR...@gmail.com on 5 Dec 2014 at 11:49

GoogleCodeExporter commented 9 years ago 
Yeah man no worries. I already went through all your self help docs. I'm pretty 
sure its the way ford sync works that causes the problem. Just wanted to 
provide feedback.  Thanks!

Original comment by soccergu...@gmail.com on 2 Jan 2015 at 5:05

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 11 Jan 2015 at 12:02