First of all - congrats Incubus, dzo and Kalt Kaffe on getting froyo working on our Vogues, and doing such a great job of it !
The primary reason I have been looking forward to Froyo is so that my wife and I can finally LEGALLY use our Android Vogues for making calls from a car. I live in Ontario, Canada, but I believe that numerous other provinces and states ban using a handheld device while driving.
My old Motorola phone does a great job of this. My wife still complains that "eyes free" voice dialing does not work on the vogue. I hear comments like "I hate this stupid phone, why can't we just get another simple Motorola phone" Nooooooo! Heresy !!!
With Incubus' RLS 10 and DZOs latest NBH, we are ALMOST there.
When I press the voice dial button on my paired and connected blueant S1 speakerphone, the phone launches the voice dial application !!!! Great !!!
What it does NOT do (yet) is give any sort of voice feedback. It does not say "say voice command" after launching the voice dial in this manner. It does reckognise my voice and come up with the person(s) it thinks I have said to dial. But the results only come up on my phone's screen. It does NOT speak to me via bluetooth audio to confirm my choice.
This means I still have to hold my phone and look at the screen when using the voice dialer, and that is still breaking the law and still unsafe.
My first thought was perhaps bluetooth media audio was not working, but when I play a youtube video with my bluetooth speakerphone paired and connected, the sound does come through the speakerphone. Also when initially dialing the touch tones come through the speakerphone.
My understanding reading several google forums, and Froyo reviews is that voice feedback is supposed to be part of hands-free voice dialling in Froyo.
I already think very highly of all of you and am very thankful for the great work you have turned out. If you guys can get this feature going, you will be like gods to me and my wife will (hopefully) stop hating me for getting her a Vogue !
+1 !!!
~fitzbg
heh heh - silly me - forgot that we have to install the TTS engine and data.
I installed PICO TTS engine and data, and when I pressed the vd button on my bt speakerphone I heard the Vogue say "speak now" !!!!
Then I pressed the end button on my speakerphone and the voice app hung then crashed. :-(
Oh well - major progress anyways - time to reboot and play some more !
EDIT: update: if after hearing the "speak now" prompt, I say something like "call Joe Smith", I get a confirmation dialog on the screen, allowing me to choose "Joe Smith Mobile" or "Joe Smith Home", but unfortunately no voice prompt asking me which choice I want. The only way I can make a selection is to press the choice on the screen. Google you should be ashamed of yourself - this is PATHETIC.
Worse yet, if there is only one number for a contact, and android comes up with only one choice - it immediately dials that choice without voice confirmation or even screen confirmation - and it may be dialing the wrong person.
Better than nothing, but sad that this so called "smart phone" still remains a very dumb PHONE, even though it is a great mobile data device. My 7 year old Motorola is still vastly superior in PHONE functions. It has amazing customisable voice dialing and voice command built in by nuance. I sure do miss that.
Thanks for reading my rant - maybe I should go to sleep now - LOL
feel free to edit the source code and add the updates you want
Seriously though, BT has come a long way, is there room for improvement? Sure.. but we can only work with what google gives us
I hope I did not give the impression that I have anything other than enthusiasm and gratitude for all the chefs that have voluntarily produced such great work. The glass is 95% full - and I LOVE having Android on my phone instead of Windows Mobile. Thank-you, thank-you, thank-you !!!! I'm only frustrated by bluetooth voice dialing. Once you have had a good version of it, you can no longer live without it !!
Now back to the technical, if anyone is willing to look into this I would be thrilled, Sorry for being long - but I think a detailed reply is more helpful than one or two sentences.
After reading through numerous google android forums, bluetooth dialing SHOULD give audio prompts to confirm a voice dialer selection. That does not happen on my Vogue with Incubus' rls 10 and dzo's July 8 froyo nbh, system and data on NAND.
I found that the bluetooth dialer after a fresh install of ROM and speech data, does work up to a few times. What happens is the bluetooth voice dialer launches with the term "starting up", the audio prompt "speak now" is heard, and the term "listening" appears in the dialog box. Other than a lack of audio confirmation, voice dialing then works. One other note, the prompt "speak now" is very very quiet, even with audio turned all the way up - although call volume is loud.
When the bluetooth voice dialer fails after a couple uses, initially it still launches the dialog box which reads "starting up" and gives the audio prompt "speak now", and then it freezes - the term "listening" does not appear.
Once bluetooth voice dialing fails, all voice recognition features, such as voice search also stop working.
A reboot does not fix the problem.
Deleting and reinstalling the audio data, along with rebooting does not fix the problem.
Re-flashing the NBH does not fix the problem.
I have to reflash the ROM to get bluetooth dialing, or any voice recognition function to work again.
If anyone is able to look into this, I would greatly appreciate it, as would some others. Hope this information is helpful. Thanks again for all the great work!
mssmison said:
feel free to edit the source code and add the updates you want
Seriously though, BT has come a long way, is there room for improvement? Sure.. but we can only work with what google gives us
Click to expand...
Click to collapse
dpkform said:
I have to reflash the ROM to get bluetooth dialing, or any voice recognition function to work again.
Click to expand...
Click to collapse
Just clearing the data partition likely have the same effect and I wonder, just maybe "rm /data/misc/bluetoothd/*" would be enough?
Not a solution and you would need to redo the pairing but sure beats reinstalling everything.
thanks Kalt_Kaffe
on vacation now, will try when I get back next week
kallt_kaffe said:
Just clearing the data partition likely have the same effect and I wonder, just maybe "rm /data/misc/bluetoothd/*" would be enough?
Not a solution and you would need to redo the pairing but sure beats reinstalling everything.
Click to expand...
Click to collapse
Related
Looks like you can use google voice, gizmo5 and sipdroid to make free landline calls with the gtablet too. I am using CM B2 and was able to set things up using the directions I have used before at h ttp://androidcommunity.com/forums/f4/how-to-free-calls-via-wifi-using-google-voice-and-gizmo5-21836/
Keep in mind this is not perfect and I was only calling some after hours mailboxes since its late here but if you turn it to speaker phone it seems we can use our gtabs as a phone as well.
Edit: When I tried to call someone this morning I could here them pretty good but they said my voice was pretty bad though it may be this crappy hotel wireless doing that.
wlawyer said:
Looks like you can use google voice, gizmo5 and sipdroid to make free landline calls with the gtablet too. I am using CM B2 and was able to set things up using the directions I have used before at h ttp://androidcommunity.com/forums/f4/how-to-free-calls-via-wifi-using-google-voice-and-gizmo5-21836/
Keep in mind this is not perfect and I was only calling some after hours mailboxes since its late here but if you turn it to speaker phone it seems we can use our gtabs as a phone as well.
Edit: When I tried to call someone this morning I could here them pretty good but they said my voice was pretty bad though it may be this crappy hotel wireless doing that.
Click to expand...
Click to collapse
not sure how a single post thread made it to front page of the portal, lol.....
especially when the method employed uses gizmo5, to which new user application is (and has been for some time) suspended.
getting sipdroid to work through pbxes is a circus too. if you come up with an easy way to get sipdroid to work, that doesn't require gizmo5 (read: another easy way), i'd love to hear more
timothydonohue said:
not sure how a single post thread made it to front page of the portal, lol.....
especially when the method employed uses gizmo5, to which new user application is (and has been for some time) suspended.
getting sipdroid to work through pbxes is a circus too. if you come up with an easy way to get sipdroid to work, that doesn't require gizmo5 (read: another easy way), i'd love to hear more
Click to expand...
Click to collapse
+1 i agree.
question comes to my mind how do posts get to the front page.. on what basis or rating?
Not sure why its on the front page of anything to be honest. The post was mainly for the people that had been using this already as I have for some time. I wasn't aware that they had closed enrollment after gizmo5 was purchased by Google. As I see it with this tablet being finicky about what apps it will run too much info is better than none.
Someone actually took the time to give my post a bad rating. Couple of minutes on Google and I found this guide to setting up a sip connection without gizmo5. I doubt I attempt it since I have a gizmoaccount but I wanted to give something additional.
http://moblog.bradleyit.com/2009/12/google-voice-via-sip-wo-gizmo5.html
wlawyer said:
Someone actually took the time to give my post a bad rating. Couple of minutes on Google and I found this guide to setting up a sip connection without gizmo5. I doubt I attempt it since I have a gizmoaccount but I wanted to give something additional.
http://moblog.bradleyit.com/2009/12/google-voice-via-sip-wo-gizmo5.html
Click to expand...
Click to collapse
That seems pretty shabby... I got basically the same working only using a Vonage Softphone SIP account instead of Gizmo... so this can be done...
I tried sipdroid + gizmo5 + google voice, but I found that the gtablet doesn't seem to play audio from the other party. The microphone works though.
Any ideas?
mscdex said:
I tried sipdroid + gizmo5 + google voice, but I found that the gtablet doesn't seem to play audio from the other party. The microphone works though.
Any ideas?
Click to expand...
Click to collapse
Hi
I used the same sipdroid+gizmo5+google voice setup and was able to talk to the other party and hear the other party by using the bluethooth. Conversation was clear on both the sides though i felt that there was some amount of lag to hear each others voice.
Hope bluetooth works for you too
Excuse my ignorance. Newbie here... Just got my Gtab and loaded Vegan 5.1. When I try and use Google Voice and Sipdroid I can only get audio from the headphones. Nothing through speakers. Can any one shed light on this?
Someone in another thread said if you hit the menu bought while you're on the call, you'll see an option for speaker. I guess the default is headset.
CSipSimple
I used SipDroid for a while when I had my Fascinate because it was the only good app that ran on 2.1. I found CSipSimple to be MUCH friendlier for my fascinate (after I put froyo on it) and GREAT on my G-Tablet (just much cleaner and friendlier looking).
I still have problems with lag and echoing in my calls, regardless of app or speed of connection. Any ideas?
Mind filling us in on how you did that? I've got a Google Voice account, but I can't get SipDroid or CSipSimple to work at all.
http://hijinksinc.com/2010/05/24/free-sip-calling-with-google-voice-sans-gizmo5/
site above explains how to set it up with csipsimple, ipkall, sipsorcery, and googlevoice for forwarding phone number. (need to replace the instructions' Ekiga with csipsimple)
since with the GTab you can only use it through wifi, i was able to get this method to work.
but this method doesn't work over 3G because of STUN/ICE server issues which prevent you from hearing the other party. so on my LG Optimus V, I use grooveIP, which works perfectly as long as your data connection is faster than 756kb.
hope that helps.
HEAD UNIT: Kenwood DDX9702S
PHONE: Nexus 6P
As far as I know, everything is up to date. Everything sounds fine when I first start my car. However, once I input my first voice command (by pressing the microphone), afterwards, all audio coming out of the right side is crackly. If I restart my car, the crackling is gone. I can go hours with it sounding just fine, but once I submit my first voice command, it all goes to hell. Any ideas? I will be reaching out to Kenwood soon about it, but this brings me to my next issue...
How the hell to we contact Google for support for Android Auto?!?!
Thanks!
Sean
seanfrisbey said:
How the hell to we contact Google for support for Android Auto?!?!
Click to expand...
Click to collapse
LOL. Google doesn't provide support...
Unless you're a business with a support contract, but they may not even have that for Android Auto.
You can at least inform Google if you want. Open the AA app, hit the dots at top right and select Help and feedback, then select the Send feedback option.
mikereidis said:
LOL. Google doesn't provide support...
Unless you're a business with a support contract, but they may not even have that for Android Auto.
You can at least inform Google if you want. Open the AA app, hit the dots at top right and select Help and feedback, then select the Send feedback option.
Click to expand...
Click to collapse
I'll have to give the in-app feedback a try. Ugh...
seanfrisbey said:
I'll have to give the in-app feedback a try. Ugh...
Click to expand...
Click to collapse
If it's happening on a Kenwood HU, ask Kenwood.
mikereidis said:
If it's happening on a Kenwood HU, ask Kenwood.
Click to expand...
Click to collapse
I have. They gave me some troubleshooting steps, which require another phone to try it with. I'm swapping out this unit for a replacement anyways this weekend for another issue it is having regarding the camera input, so I'll wait until then to try anymore troubleshooting steps.
I don't have OP's issue but I got a similar one with my ddx9902s. What happens is when google now prompts are spoken (ie when reading a text message or verifying if what you spoken was what you want to send BUT not things like map navigation) I get some distortion/static. However everything else is unaffected.
Honestly not sure if it's related to this but this is the closest problem I saw. Might be an amp/cabling issue?
I have the same issue on a DDX9702S. Only affects Android Auto, not CDs, Bluetooth, or CarPlay.
Any resolution to this, or did you just exchange it?
Hey, so I'm fairly new to android auto, having been in my 2016 civic for only a couple weeks. Everything is working great apart from the text message issue. Basically when I receive a text, it shows up on the home screen but when I click it, aa won't read it to me. The screen goes dark and the microphone icon goes blue as if it's trying to read it, but nothing happens and it returns to the home screen. Interestingly, if I press the microphone and use a voice command like 'read my last text message' aa says: "actually, I can't read your messages yet". Any help would be massively appreciated, it's really the only issue I've had so far with the vehicle or Android auto. Thanks.
Sorry, forgot to mention the phone is a nexus 5 with 6.0.1. The usb cord is the original that came with the phone, plugged into the usb port in the car designated for smartphone connection. Also I'm in Canada, if that matters.
Have you checked the permissions on the android app on your phone? Sounds like it doesn't have permissions to view your SMS?
Sent from my Nexus 6P using XDA-Developers mobile app
Yah I went to settings/apps/app permissions/sms and enabled all the apps in there. I also went to android auto, messenger, hangouts, Google play services, Google app, and contacts individually to make sure sms permissions were granted. I'm able to send a text from android auto, but it won't read out texts that I receive.
I'm having the same issue with my Galaxy S7 Edge running Android Auto on my Pioneer AVH-4100NEX. I went on vacation and my car sat for a while and now when I'm in Android Auto mode I can't receive and send text messages. I ask Google for the weather or to do a calculation and I get nothing. However, if I ask Google to dial someone whether in my contacts for not, it dials the number. Does this make any sense? There doesn't appear to be any official Android Auto support. I contact Pioneer and they told me my contacts weren't syncing with Android Auto which was strange enough when they said it, but given the fact that I don't get a reply when I ask GoogleNow for the weather means my contacts shouldn't have anything to do with it. Any help would be appreciated.
Thanks,
Matt
Same here: SEAT Ibiza with Full Link, Nexus 6 with 6.0.1 with SMS and WhatsApp. Could that be caused by some setting for language, text-to-speech? Everything else works fine, also sending messages.
PS: The system language ist German...
Similar.. it'll occassionaly read one message. But only one. Not always the first one per time I connect the phone to the car. Hyundai elantra 2017, vzw gs5.
Sent from my SM-T520 using Tapatalk
Made an account just so I could maybe help a few people. I'm using a Galaxy S6 with an AVH-4100NEX unit, and I was getting the same issue. Could send messages fine. Tap to read message - agonizing silence. Managed to solve it by factory resetting my device with Samsung's Smart Switch software. Backup. Reset to factory setting. Restore. Success. All the best!
**SOLVED** this problem has been driving me crazy, but I found the problem. Go to your Google Now settings, click "Voice" and turn OFF Bluetooth Headset.
Its to bad we can't have that on and use Android Auto. You have to choose either the built-in system in the car with Bluetooth or use Android Auto.
Anyways, I hope this solves your problems.
I was hoping Build A Wall's post was the fix but it didn't change anything at least for me. My GoogleNow works fine if I'm just using the phone in my hand. But ever since the end of June, when connected to my car, I can't text or ask for the weather but GoogleNow understand if I ask it to call someone or ask for directions. And even when it does work like making a call, it doesn't reply by saying "Calling Steve" like it used to. It's really weird. I'm wondering if Android Auto came out with an update and it screwed up things.
I don't think there has been another update, I just think it is primitive software that still doesn't quite work as it should. I have had similar problems that I have posted on here in that I could no longer send text messages but could still navigate etc. My situation now is that I have changed nothing on my Nexus or my car unit yet now it is working perfectly again! Hopefully, that is encouraging for you. I hope they will stabilise the software with some updates.
Sent from my Nexus 6P using XDA-Developers mobile app
@mpisani sorry that didn't work. It sounds like your problem is a little different than mine. I was having the same issues as the fiest post in this thread. It just wouldn't read my text to me, but everything else worked great.
I hope you get it figured out.
I turned off Bluetooth entirley before starting the car, it didn't help.
Having the same issue. Next text will come in, screen will show that there is a new text and from whom, but when you touch the card the microphone in the right corner turns blue while rest of screen changes tone a bit to show its in background but there is no audio of text message being read. ask google to read new texts and google says it cannot do that at this time. I'm wondering if it can tell thru gps if you are in a state that has banned all texting while driving and they are trying to cover their ass.
BuildAWall said:
**SOLVED** this problem has been driving me crazy, but I found the problem. Go to your Google Now settings, click "Voice" and turn OFF Bluetooth Headset.
Its to bad we can't have that on and use Android Auto. You have to choose either the built-in system in the car with Bluetooth or use Android Auto.
Anyways, I hope this solves your problems.
Click to expand...
Click to collapse
Thank you so much - it worked!!! My Voice commands did not work at all, no matter what I tried (which was a lot) - it just turned on, listened, turned off, repeated. This fixed it. Now I can again give voice commands, and it will read messages to me as well!
Sent from my Nexus 6P using Tapatalk
I've been having the same issues with my new 2017 Elantra. It's sporadic in reading it, sometimes it does and sometimes it doesn't. Interestingly, when reading messages it uses the other TTS service and not the one from Google Now.
Going to try the BT setting and see how it works. Also was wondering if the issue was from the SMS app.
Sent from my Nexus 6P using Tapatalk
tjk639 said:
I've been having the same issues with my new 2017 Elantra. It's sporadic in reading it, sometimes it does and sometimes it doesn't. Interestingly, when reading messages it uses the other TTS service and not the one from Google Now.
Going to try the BT setting and see how it works. Also was wondering if the issue was from the SMS app.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I don't believe it is the sms app purely because the fault is the same for me also with google hangouts which is of course a different app.
I'm really bored with it now sometimes working sometimes not no matter what solutions we come up with on here and try out.
Does Apple car play have all these issues with working just when it feels like it? Maybe we should all get iPhones so we can have software that just works as it should.
What about mirror link? Does anyone have experience with that? Or is it just music apps rather than communication like texting etc?
bradboyd said:
Hey, so I'm fairly new to android auto, having been in my 2016 civic for only a couple weeks. Everything is working great apart from the text message issue. Basically when I receive a text, it shows up on the home screen but when I click it, aa won't read it to me. The screen goes dark and the microphone icon goes blue as if it's trying to read it, but nothing happens and it returns to the home screen. Interestingly, if I press the microphone and use a voice command like 'read my last text message' aa says: "actually, I can't read your messages yet". Any help would be massively appreciated, it's really the only issue I've had so far with the vehicle or Android auto. Thanks.
Click to expand...
Click to collapse
Since this new update, my LG v10 Android Auto experience is horrible - essentially voice commands hardly every work - I'm not getting full prompts all the time (sometimes I get audio beeps before/after, sometimes just before, sometimes just after, sometimes never!). I've found I can guess at what I should be saying when it's listening for voice input to send a text, but I get zero feedback from the system. And my received texts will not read back. Very Very frustrating. As I work for a Honda dealer, our engineers have informed me it's all on Android. I think I'll fire up my iPhone today and go back to CarPlay for a while and hope the next release fixes my issues - it's just not usable in its current form.
The Bluetooth setting worked for me. Really odd fix that I would have never guessed to try. Thanks for the tip
Sent from my Nexus 6P using Tapatalk
So far, like others, that odd setting fixed it. Google Now update must have introduced it.
I have no idea what is going one w new look version and old versions of android auto. Either way, most commands or calling a contact, get driving directions or text someone are decli ed saying something like sorry, not sure how to do that or not know how to handle requests. Kinda frustrating and settings appear to be correct as I can see music apps, google maps etc.
Any suggestions or is it an issue somewhere else. Any other android phone and AA works fine w it whether new look version or old AA version.
Tia,
Ian B
Same problems here, Android Auto is borked big time on my fold but is still OK on my Pixel 3a. Problems are:-
1) When connected to my vehicles head unit it often disconnects for no reason
2) When I get a stable connection, and ask it to "navigate to xxxx" by voice it responds that it cannot do this "while in driving mode".
3) If I ask it to make a call or send a sms it responds "sorry I cant make calls yet" or "sorry I cant send texts yet"
4) After AA has been opened (even outside the car), Google assistant will no longer make calls or send texts via voice commands. Disabling the Google app, clearing the cache doing a restart brings the assistant functionality back but only until I use AA again.
The whole thing is a complete mess and given it is intended to be used WHILE DRIVING it is a very dangerous distraction - Google/ Samsung need to get on top of this or I can see them getting sued because they killed someone.
UPDATE: Iwas running a beta of google play services, when I uninstalled that and went back to the general release version, everything seems to be working OK with Android Auto.