Does anyone know if it's possible to do voice to text using bluetooth instead of the phone's mic?
no. I've looked into this before but only found apps that can read you text but as far as what your talking about no, I think it may be possible once someone makes an app for it though.
I was using VLingo for a while and it did this. Only I had a bunch of force closes with that app. Then after I removed it I had major issues with BT, it works pretty good but does have its quirks. I'd stay away from it unless you have to have this. FYI once you install it it makes a mod to your bluetooth stack that i couldn't fix without a complete wipe and reformat, then I had to roload my rom and set it back up from scratch. Some people have reported going into applications and removing the "update" to the bluetooth stack fixed for them. I didn't have an update so it didn't work for me. Also restoring a nand didn't fix either.
OnStar also has something coming out soon:
http://www.engadget.com/2011/01/04/onstar-announces-bluetooth-voice-app-reads-your-facebook-messag/
Related
Hey, i've heard that HTC didn't put the full bluetooth stack in the EVO or something, but what exactly can pair and function with it? headsets are obvious, but would it be possible to use this keyboard to play emulators and, well, use as a keyboard?
I'm going to assume someone is just going to say "No", but I'd like to hear (links or otherwise) how hard it is to flash an update.zip with the proper bluetooth, possibly robbed from the nexus one...or elsewhere. Maybe it's harder than i imagine, but if the fps issue is (somewhat) resolved, root made a 3 click process, and the camera LEDs used for incoming texts, this shouldn't be too far of a stretch, right?
amruthwo
Bluetooth has been pretty buggy once you start messing with it. Trying to add a full bluetooth stack (if it is indeed a limited version on the EVO) would take a lot of trial and error to get everything working correctly. If I had a BT keyboard I would test it out, but I don't..
This thread might have the information you're looking for. Apparently it works rather well with an app called KeyPro.
http://forum.xda-developers.com/showthread.php?t=684239
that is a promising thread! Thanks for the heads up!
Sent from my F#©&ing EVO using XDA App
I have posted this in other forums with no luck. I was hoping that maybe someone here had some answers...
I have a 2011 Ford Explorer with SYNC v2.7 (latest version until next month). It has capability to download phonebook information including photos. It is also capable of supporting SMS.
When I got the truck, I was on 2.1 (TMO-USA). The phone paired fine and people on the other end told me I sounded great. Photos from phonebook did not show up. When I tried to access messaging in SYNC, it told me phone did not support this.
I upgraded to 2.2.1 and the phone still pairs easily. Still no photos, and now SYNC recognizes that the phone has messaging capability. BUT... SYNC only randomly picks up the text messages. As near as I can tell, if I get a message just before I get in the car and start it, then there is a good chance the system picks up the message.
Lastly, now with 2.2.1, the person on the other end tells me that I sound like I am in a wind tunnel. I removed and re-synced the connection and still same thing.
QUESTIONS-
1) Anyone know what might be preventing the SYNC system from displaying my photos?
2) Anyone know why the messaging works on occasion?
3) Anyone else experience the "wind tunnel" effect?
4) Is there anything that can be done (maybe different ROM) to resolve this?
Thanks
I would advice you to try with another phone this way you might exclude the car as the reason. I suggest this because I have the feeling that the car might be the fault and the software that is incompatible with the official bluetooth standards.
If it works with other phones (maybe even Android) then the situation clears a little bit and you have a more clear way to follow.
Keep us up to speed.
I am trying to find an app that is capable of changing what app launches when I press the phone button on my car stereo. As of present in Jellybean it launches the voice dialer. Well since Google Now is capable of a great many more actions I would prefer that app launch.
Does anyone know of an app that will allow me to manipulate what actions are taken from Bluetooth controls?
Liveware manager from Sony. Just not sure if you can use non Sony devices.
Sent from my Galaxy Nexus using xda app-developers app
Dalbs2 said:
Liveware manager from Sony. Just not sure if you can use non Sony devices.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thanks Dalbs2, Ill give it a whirl and report back.
Im sure I am not the only one that wants steering wheel controlled launch for Google Now.
Just to update, the app does work on the Nexus, but it doesn't do what I need it to do. It really just seems to be an extremely simplified version of Tasker, that launches a preset app when a specific device connects to the phone.
What I am looking for is the ability to change the assigned function of a bluetooth button.
At present when I hit the phone button on my steering wheel in my car, it launches Voice Dialer. Since Google Now is capable of the same voice dialing plus a lot more, I would prefer that it launch when I press that button.
https://play.google.com/store/apps/details?id=com.kin.bluetooth_launch
Try Bluetooth Launcher
Sent from my Galaxy Nexus using Tapatalk 2
supersquishy said:
https://play.google.com/store/apps/details?id=com.kin.bluetooth_launch
Try Bluetooth Launcher
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gave it a whirl, but I cant tell if its just not compatible with JB or if the button on the wheel is not sending the standard signal... Ill have to test with my BT headset when I get home and find where ever the hell it buried at... I haven't used the thing in years.
Thanks for the heads up on the App. It was exactly what I was looking for.
Try going into Settings/Applications/Manage applications/ and select the Bluetooth Dialer and hit the Clear defaults button. Then try your headset button again. It's possible that it will now prompt you with a list of available apps to launch and then you can possibly make Google Now the new default. If that fails the Bluetooth Launcher app suggested earlier should do the trick.
Perhaps you can answer a question. Does Google Now accept voice input from the connected bluetooth microphone? Currently the bluetooth microphone input in all google apps (including the voice search) is broken in all versions including ICS. This is a major oversight and a bug that I cannot believe hasn't been fixed. hxxp://code.google.com/p/android/issues/detail?id=8973
I am very much hoping this has been corrected completely in Jelly Bean or at minimum in Google Now.
I look forward to your feedback.
creekflood said:
Try going into Settings/Applications/Manage applications/ and select the Bluetooth Dialer and hit the Clear defaults button. Then try your headset button again. It's possible that it will now prompt you with a list of available apps to launch and then you can possibly make Google Now the new default. If that fails the Bluetooth Launcher app suggested earlier should do the trick.
Perhaps you can answer a question. Does Google Now accept voice input from the connected bluetooth microphone? Currently the bluetooth microphone input in all google apps (including the voice search) is broken in all versions including ICS. This is a major oversight and a bug that I cannot believe hasn't been fixed. hxxp://code.google.com/p/android/issues/detail?id=8973
I am very much hoping this has been corrected completely in Jelly Bean or at minimum in Google Now.
I look forward to your feedback.
Click to expand...
Click to collapse
First off thanks for the idea on clearing defaults, I had already tried that, but Bluetooth Launcher is not listed in the app list under all. I have been looking through there trying to find what is controlling the bluetooth voice dial, but have been unsuccessful in my attempts to find it.
As for your question, it looks like they did fix it. I set my phone outside of my front window in the car and then hit the voice-dial button on the wheel. I then spoke softly into the mounted vehicle mic, so to make sure the phone mic would not pick it up. Worked just fine.
HOWEVER. Google NOW does not work, so it looks as though it still relies on the internal mic for that function. Considering that I have never noticed this while in use driving my car and using Google Now, Id say the internal mic does a good enough job. Of course that may vary from device to device.
For what its worth, I can no longer use my 3rd-party voice dialer without disabling google search. There is no longer, in Jelly Bean, a way to make a 3rd-party voice dialer be the default voice dialer. Shutting down google search really sucks but bluetooth voice dialing is a very high priority for me. I sure hope someone straightens this out.
BTW, the built-in voice dialer is horrible on JB bluetooth and there is still no call confirmation option.
This blows.
Looks like Google broke the Bluetooth button functionality.
Agreed. If I have to hear voice dialer say "didn't catch that" one more time on by JB loaded Galasy s3, I might have to go back to (egads) s-voice!
Even if it uses the internal Mic, google now is preferable.
ANy progress?
This bluetooth problem still exists. I'm on AT&T Galaxy S3 and have tried CM10, LiquidSmooth, BlackJelly, and HighOnAndroid. I have only been able to functionally use bluetooth voice dialer on BlackJelly and that is because it uses the default S Voice app. CM10 and LiquidSmooth did not even pick up any mic neither through bluetooth or the phone. HighOnAndroid at least picked up the bluetooth mic, but always dialed 1 of 3 contacts regardless of what I said. Is there any rom out there that has the Google Now search bar on the homescreen (ics or jb) with the ability of using a third party voice dialer app or even use Google Now instead of the Google voice dialer app? I'm assuming no, but thought I'd post even if it's just to bump up this still current issue.
I just did some searching and came across a thread with a possible solution. Here's the link:
http://forum.xda-developers.com/showthread.php?t=1883895
It basically says to convert google search from a system app to a user app. I haven't tried it, but it sounds like it allows some people to choose a different voice dialer as the default.
creekflood said:
Try going into Settings/Applications/Manage applications/ and select the Bluetooth Dialer and hit the Clear defaults button. Then try your headset button again. It's possible that it will now prompt you with a list of available apps to launch and then you can possibly make Google Now the new default. If that fails the Bluetooth Launcher app suggested earlier should do the trick.
Perhaps you can answer a question. Does Google Now accept voice input from the connected bluetooth microphone? Currently the bluetooth microphone input in all google apps (including the voice search) is broken in all versions including ICS. This is a major oversight and a bug that I cannot believe hasn't been fixed. hxxp://code.google.com/p/android/issues/detail?id=8973
I am very much hoping this has been corrected completely in Jelly Bean or at minimum in Google Now.
I look forward to your feedback.
Click to expand...
Click to collapse
On my HTC droid DNA i had the same problem. I found a very simple fix on another forums that worked.
Settings/sounds/touch sounds
Activating touch sounds for some reason made Google Now get past initializing and work with my BT.
On the other hand whenever i use bluetooth launch to launch google now, it never gets past initializing. i also have to reset the phone to make google now work again with my bt.
briguybro said:
I just did some searching and came across a thread with a possible solution. Here's the link:
http://forum.xda-developers.com/showthread.php?t=1883895
It basically says to convert google search from a system app to a user app. I haven't tried it, but it sounds like it allows some people to choose a different voice dialer as the default.
Click to expand...
Click to collapse
this worked right away!!! your ****ing awesome!!! ive been trying to do this for so loooong i made dragon a system app and when i hit the voice button on my bluetooth it asked me if i wanted to use dragon or s voice i hit dragon than always and now it always just brings up dragon!!! i cant begin to tell you how stoked i am right now i can finally make calls on my motorcycle.
After upgrading to ND8, I was really disappointed that Bluetooth would not stay connected in my car. It paired find and would happily connect. The car then sent a MAP request and a PBAP request. I accepted both (just as I would with 4.3) and all seemed to work. I could play audio and use the phone, and the car even reported that the phonebook transfer succeeded. But then somewhere between 2 and 10 minutes, it would disconnect. Then in about 15 seconds it would reconnect and be fine for another 2 to 10 minutes. And this repeats non-stop. This made phone calls almost impossible.
At first I guessed I got a bad flash. I re-flashed stock, I flashed Wicked X, then I re-odin-ed. Nothing helped. After looking at similar threads for other phones, I tried playing with WiFi settings, but that didn't do anything. Tried some Xposed settings... nope.
Finally I found that if I repaired the phone (deleting the old records on both the car and phone) and this time I refused the PBAP request, all was fine. No more disconnects!!! I don't really need my car accessing my phone book, but it was nice with 4.3 to see caller names and pictures on the car display during a call. Also I have found that an initial MAP requests is being made when bluetooth connects, but when I receive a text, I no longer get a notification on the car. So MAP is not working.
Are other people finding that MAP and BPAP are working for them on ND8? I haven't seen this reported, so I have to imagine this is not a common problem. Everything worked fine for me with 4.3 so it seems my car does support MAP/BPAP, but now there is some incompatibility and I am not sure if the bug is with ND8 or my car.
Car is a Toyota Rav4 EV. Phone is a Sprint 16G SG3.
For the MAP issue, I am wondering if I need to use Samsung Messaging to get MAP? I use Hangouts. 4.4 added a new way to select a default messaging app. In 4.3 it seemed that both apps were active, but I had turned off notifications in Messaging. In 4.4 only Hangouts is active.
It is so frustrating that the Bluetooth stack changes from version to version isn't it. You'd think they would only add features rather than break things, right?
Well, luckily I haven't had disconnect issues, but the MAP profile you are mentioning for text messages, well it comes up on the screen, but doesn't display the originator of the message in the Toyota Entune's nav screen the way it used to. Seems to display message header garbage rather than the text message originator like it used to do.
I've also noticed that the display of title metadata on the cars screen for what's currently playing isn't showing the title changes as often like it was working on 4.3.
Sent from my Nexus 7 using Tapatalk
After a bit more experimenting it seems that I was wrong. It seems that MAP is what is causing the disconnects and not PBAP. I had tested disabling MAP and PBAP together for many days which made me confident that I had found a solution. But I assumed that, of the two, PBAP was the issue. Next I tested disabling PBAP only and it seemed to be working fine so I decided my assumption was right. But I didn't test that long enough and the problem returned. I am now running with PBAP enabled and MAP disabled and it looks to be working, but its still early. I'll report back after some long drives which will test it much more effectively.
I assumed PBAP because looking through threads, others have reported disconnect issues with PBAP on other phones. It seemed a logical conclusion, but BZZZZTTTTT! OK, more after further testing...
My experience is that if I have my Sony Smartwatch 2 connected I do not have random Bluetooth audio disconnections, however if the audio accessory is the only Bluetooth device connected it will disconnect every 10 or 15 minutes. Not sure if that is helpful.
Fred
I've been doing a ton of research and I want to know what the status is of using the Nexus 7 (2013) as a hands free device. I've seen some discussion about BlueZ, adding bluetooth profiles, using hands free kits, mic input from DACs, etc. but nothing really that recent. I'm hoping that there has been some development in this area with 5.1.1. The goal is to have the call audio go to the car speakers and maybe have an external mic for the audio in.
How are others doing it and what is the current accepted way to accomplish this? Can someone point me in the right direction? I'm starting to build my system and this is one of the last things I need to figure out.
I have the cellular version Nexus 7 if there's a way I can use that to send/place calls from the same number with a second SIM or something.
you can setup the nexus through auxiliary so that audio goes through the car speakers, and if your really picky about what kind of sounds go through your car speakers or the nexus speakers you can use an app like this https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix&hl=en
For making calls and such from a different device you should use an app like Mysms https://play.google.com/store/apps/details?id=com.mysms.android.sms&hl=en
It allows texting from any device using your phone by sending the info through wifi or bluetooth to your phone. It can also route calls from your phone to what ever device you want allowing you to answer with your tablet (with mysms this requires paid version, but there are likely other apps out there).
arolust said:
you can setup the nexus through auxiliary so that audio goes through the car speakers, and if your really picky about what kind of sounds go through your car speakers or the nexus speakers you can use an app like SoundAbout
For making calls and such from a different device you should use an app like Mysms
It allows texting from any device using your phone by sending the info through wifi or bluetooth to your phone. It can also route calls from your phone to what ever device you want allowing you to answer with your tablet (with mysms this requires paid version, but there are likely other apps out there).
Click to expand...
Click to collapse
The issue is that I'm replacing the head unit with the Nexus. I have Tablet talk which allows me to answer calls on m phone from the tablet, but the audio goes over the phone. I want to be able to answer the phone call on the tablet and have the tablet handle the audio. I've seen other threads about this and I've searched, but I haven't seen anything that are very recent. The best 'solution' I saw was implementing the BlueZ bluetooth stack to provide the required profiles, but I find their instructions confusing and it doesn't seem like anyone has attempted to get it working even though many people are looking for a solution to this.
Does anyone have any experience with implementing BlueZ on 5.1.1?
ok, your saying the app requires you to still use your phone to complete a phone call.
Using google voice setup and hangouts. Using this setup is the best I can think of. You can setup your current phone number I believe to work with google voice. Then just setup your phone to tether to your tablet.
Im fairly certain google hangouts can use your cellular service to place the calls and text, but if you have no service but have data/wifi it can use those, but im not 100% sure on that.
EDIT: I should clarify, google hangouts/voice works to make calls/texts/videocalls over wifi on any smart device without cell service. By using your own number your tablet will be able to make calls/texts/videocalls all from your number, all you need is data connection/wifi. I have not tried using hangouts over cell service without data, never had a need.
Troopster19 said:
The issue is that I'm replacing the head unit with the Nexus. I have Tablet talk which allows me to answer calls on m phone from the tablet, but the audio goes over the phone. I want to be able to answer the phone call on the tablet and have the tablet handle the audio. I've seen other threads about this and I've searched, but I haven't seen anything that are very recent. The best 'solution' I saw was implementing the BlueZ bluetooth stack to provide the required profiles, but I find their instructions confusing and it doesn't seem like anyone has attempted to get it working even though many people are looking for a solution to this.
Does anyone have any experience with implementing BlueZ on 5.1.1?
Click to expand...
Click to collapse
Did you find something. Sometimes I have the impression that some people just can't understand a simple English sentence, like arolust.
lung1 said:
Did you find something. Sometimes I have the impression that some people just can't understand a simple English sentence, like arolust.
Click to expand...
Click to collapse
Nah, I gave up - I got no support so I just broke down and got the MotorMouth 2.
But if someone were to figure it out I'd like to know the solution so I can have a single device act as my HU.
I'm working on a solution. Bluez lets you build AOSP for Nexus 7 2013 and it has HFP support. I will tell you if I did something. It really looks like no one is willing to help on this area. I searched a lot, but just peaces.
Troopster19 said:
Nah, I gave up - I got no support so I just broke down and got the MotorMouth 2.
But if someone were to figure it out I'd like to know the solution so I can have a single device act as my HU.
Click to expand...
Click to collapse
Subscribed
Sent from my Nexus 7 using Tapatalk