The Thunderbolt is supposed to support BT Phone Book Access Profile (BT PBAP) per Verizon and HTC web sites.
Using the Verizon 2.11.605.9, and even older firmewares, I can't get my car's BT system to access my TB's phone book, even when I allow the request, and check the box for always allow.
Why do I want this? So that I can hit a button on my car to show the TB's phone book on the car screen, and be able to scroll/select who I want to call. It would also mean the Name of the caller also appears on the screen for incoming calls, rather than just the phone number.
Interestingly, while trying the leaked OpenMobile ROM, its BT PBAP DOES work properly. Unforuntately, none of the Verizon apps work, and it lacks Verizon's Visual Voicemail support.
So now for my question...
Is there a way to get BT PBAP working on 2.11.605.9? maybe use some of the BT files from the OpenMobile rom on the VZW firmware?
Any thoughts how to do this? or does anyone have any suggestions?
not sure why but for me it does work, i do use an aftermarket BT stereo... but what is your deck thats not working?
outsid0r said:
not sure why but for me it does work, i do use an aftermarket BT stereo... but what is your deck thats not working?
Click to expand...
Click to collapse
Pairing and Connecting the TB to car's stereo works (for BT Hands Free audio/BT Headset profiles). After pairing, the car kit tries to access the TB's phone book, I see prompt on phone, I select ALLOW on the TB's screen. The PB is then not an option on the car's screen. I can "digit dial" or view a list of incoming/outgoing calls for this BT session via the car's screen, but the on screen button to bring up the TB's phone book isn't there, and the names don't show on the screen for incoming calls.
Using my Bionic, BB 9780, or the TB with the OpenMobile rom on it, the car's kit CAN access the phone book, the onscreen button for it is there, and I can scroll through the names/pick via the car's screen, and it shows me the incoming caller's names.
I'd just use the leaked OpenMobile firmware if it supported the My Verizon app, Verizon's Visual Voice Mail, and the "Verizon specific" apps like NFL Mobile, etc.
I'm using stock, but rooted 2.11.605.9 on my TB. Its not DeOdexed. I don't know if its possible to pull the APK and ODEX files from the original OpenMobile RUU, or not. The version I flashed, was rooted, deodexed, etc.
I guess at this point, I could try finding a de-odexed version of 2.11.605.9, flashing my phone, and pulling the files from Openmobile, and dropping them onto my phone (overwriting the existing) and see what happens?
Related
This is a question I've had since owning the G1. Can we make it so that our incoming text messages get pushed through Bluetooth? I know the functionality is not there with the stock messaging app, but does there exist one that does? Or can one be programmed to do so?
This would be helpful to handful of people (like me) that have Microsoft Sync systems in their Ford/Lincoln/Mercury cars. Sync is able to read you your text messages while driving, and allows you to reply with your voice or call the sender, but only if the handset supports sending texts through Bluetooth.
I would imagine that since we have the latest version of BT, it could at least be programmed into a third-party messaging app, by someone with more knowledge than I. The only handsets to support this feature out of the box are some candybar Nokia and Motorola featurephones, so it wouldn't be too far fetched to get Android to support this.
Any thoughts?
This is the only thing i've been able to find that looks anything remotely close to what your asking for...
http://www.myblueant.com/android/index.php
Hope this helps
I believe I saw on the official Sync website that one of the Android phones was working with the text part of Sync. Posted by a Android user. You might look into that and see if it leads anyplace.
Sent from my SAMSUNG-SGH-I897 using XDA App
Try out the vlingo app in the market. It has something called Safe reader. It will read your sms out loud. When I'm driving and have my phone hooked up to my stereo, through bluetooth, it plays the message through my speakers. Not sure about standard bluetooth headsets but its worth a shot.
DriveSafe.ly will read your incoming messages to you via BlueTooth, and can be configured to autoreply, if you wish.
I looked through the syncmyride website and several people are reporting the Droid X works with the text messaging part of the Ford Sync system. Maybe there is hope for a direct connection. Although they also talk about Samsung phones in particular having issues with the Sync.
I'm trying to get this working as well. Stock EVO
Thanks for the suggestions of DriveSafe.ly and Vlingo. This is a great alternative, however in my case they would only work if I had the car stereo connected through Bluetooth (the Sync system allows you to do a Bluetooth media stream).
The issue, however, is that most of the time I have either my Zune or my Toshbia media player playing through a USB connection in the car. Say I get a phone call, Sync knows to pause the music in the USB connection, alert me to the phone call, talk on the phone through the car speakers, and then when the call is disconnected it will resume playing the music from the USB. Since the USB is selected and not the Bluetooth stream however, DriveSafe.ly and Vlingo won't automatically notify Sync of the text (it does work if I'm using the Bluetooth streaming option though, since Android is handling the streaming).
After rummaging through some posts, it seems that Syncs ability to communicate with your texts stems from a Bluetooth profile known as MAP (Messaging Access Profile), and while Bluetooth 2.0 and higher support this feature, only some handsets have that Bluetooth profile supported. How hard would it be to add a Bluetooth profile to the Android core through, say, a custom ROM? Or would the Kernel have to be modified?
Looking at the compatibility list it seems that the Motorola phones work with the text messaging system. All ( or most) of them, not just the Android phones. So it may be deeper than ripping the BT control scheme out.
But it would be great if someone could figure it out. I don't think many people care though, if you search here for Ford Sync you don't get many hits.
Blue control
search blue control on the marketplace or appbrain. this app allows sms to be played (and responded to) through a bluetooth headset!
Vibrant reads text out loud stock.
Settings>Voice Input and Output>Text-To-Speech Settings> Check Driving Mode...though..be warned. This will read ALL incoming texts out loud, and when you get a call, it will say Call from (caller or number if it's not in your contacts)
Don't have a BT headset..well I do..just can't find the charger. lol, so can't test it. And I'm not rich enough to have a BT enabled car.
Bumpity bump
gahockey05 said:
search blue control on the marketplace or appbrain. this app allows sms to be played (and responded to) through a bluetooth headset!
Click to expand...
Click to collapse
In the app description, it says it does not work with in-car bluetooth "at this time". So we can keep our fingers crossed.
Sent from my ADR6300 using XDA App
I have found, that to get messages read to me and be able to reply, I had to install a custom rom (CyanogenMod 9-20120710-nightly), it works great! I hope this helps.
I'm running DL09 Super Clean 0.4/EB01 2.4 on a Fascinate. Kernel is EB01-based Voodoo.
I took the plunge and got a Motorola Roadster bluetooth car kit, preferring a car kit to an earpiece. With my Froyo based Fascinate, I was eagerly anticipating voice dial, etc. No such luck.
Car kit pairs and requests phone book access. Grant privilege (always). Great!
But... Car kit does not announce caller name, even though it is a contact in the phone. Seems like although the rights are granted for PBA, the request for an phone book entry by the car kit fails.
Also, no bluetooth voice dial
Pressing the command button on the car kit returns and annoying "not supported by phone" message.
Is the BT stack still under development, or do I need to configure something? (seems unlikely).
Thank you in anticipation.
I don't know anything about phone book access, but to use voice dialing on Super Clean, you need to flash the Nuance zip in that thread. Nuance is the stock app that handles bluetooth voice dialing.
Thank you for the tip. Installed Nuance. Useless. My accent is South African / Oz / USA. Voice commands deliver some interesting response. Even after adaptation, recognition (in a quite environment) is no better than 10%. Too bad.
And just a heads up...post questions in the General section
I pulled out my bt headset the other day and was disappointed to discover the same thing. I agree that Nuance is trash (and is why my bt has been in storage for a while). I haven't done so yet, but have you tried Vlingo?
Sent from my SCH-I500 using XDA App
Installed Vlingo and have been using it for a few days. Recognition is great, but does not cut media sound when waiting for command and does not handle car noise well. Maybe my car more noisy than average... I'm going to keep it and watch for updates.
In my opinion there is most definitely an issue with the Bluetooth stack in EB01. I just had a head unit installed in my car that is capable of streaming music and phone calls. Whenever I make or receive a call through the unit, it force closes upon hanging up, with both devices indicating they still have a connection (and they definitely do not). I have to power down the stereo and turn bluetooth off and back on the phone.
It is extremely aggravating. I feel like this phone has been one huge repeat of "one step forward, two steps back".
I love Froyo except this bluetooth issue is a major disappointment. That, and I've tried everything posted and still have lousy battery compared to DL09. But that's another thread.
Anyone know if this is any better in ED01? Im running SC2.9.2 and see no reason to go back to stock or even an ED01 ROM -- unless the BT voice dial is working...
So I feel like this should be something pretty simple. I'm trying to use voice command with the bluetooth in a VW, but when I activiate bluetooth in the car it dosen't automatically allow for voice commands. Can still use the phone, but it would be nice to be able to use voice command without having to log into the phone. I've tried turning on driving mode and that doesnt' seem to work.
Any advice?
i dont think you can activate the 'voice commands' option from the VW bluetooth. I have a VW Golf and I can only make and receive calls from the car's BT system. If I want access to anything else, I need to use the phone itself.
Yeah, that's exactly the issue I'm having. Would think that you could also use voice commands. It worked fine with the iphone, but doesn't seem to like the galaxy for whatever reason.
While you can still use the VW's built in voice commands (to dial numbers, etc.), I don't believe you can use the car's mic/speaker for the phone's voice command functionality. Since it's just an app, it can't integrate into the car's systems. You can however stream music to the car's audio system via bluetooth.
Does your VW stereo have a button that you push to initiate the voice command application? I had this problem on my Subaru as well. It wasn't launching the application that listens for voice commands when pressing the button. I installed an app called Choice Dialer (Which is actually now Hands-Free Voice Dialer) and it started working.
I'd give this a try and report back if it works.
Thanks for the responses. It actually ended up being something pretty stupid. Pretty sure it's still using the built-in BT, but it takes care of what I was trying to solve.
For whatever reason the first time it requested access to my address book ti apparently didn't work. If someone else has the problem what you need to do is make sure your phone and bluetooth are connected. While connected, open your notification screen, it will probably say there are no att notification, hit that, then it will show a request by your VW bluetooth to your address book. Accept it and now you can use the 'call whoever on mobile' functionality.
Glad you got it figured out. Having half-*** handsfree is a big step backwards after being able to throw voice commands out.
I'm hoping someone here has some *real* ideas or answers regarding this issue.
I have a handsfree Bluetooth kit in my car so that I can safely place calls while driving. This worked flawlessly with my previous Windows Mobile phones (Tilt/Tilt II). With the phone tucked in my pocket and the mobile OS “locked” I could press the voice activation button on the dashboard and easily call someone. Not so with my shiny new AT&T Samsung Galaxy S II. Now I have to dig the phone out and unlock the device before I can use my handsfree system… are we back in the smartphone dark ages?? I might as well take up texting and driving while I’m at it and forget the handsfree unit altogether.
Apparently Google in their infinite wisdom has decided already paired Bluetooth devices pose a security risk. As such, when Android is “locked” it disables any control from Bluetooth. I suppose if you work for the government or some place that you need Pentagon like security this makes sense. For the 95% of us that don’t need these draconian measures this is just plain stupid and potentially unsafe.
I've already rooted my phone. I've tried other ROMs like the latest builds of UnNamed, ICS'd Out, and CyanogenMod. None of these allow Bluetooth operation while the phone is locked (and in fact all of them introduced other issues). I've searched the forums but most similar posts go unanswered or contain nonconstructive replies (flames, unrealistic answers, etc).
I can't and won't disable ALL security. I won't give up making phone calls while driving - I'm on the road a decent amount and need to use that time productively. What are my other choices? Go buy an iPhone or a Windows Mobile unit which work "right"?? Seems like a crazy oversight by Google/Samsung/AT&T if those are my only options!
I would suggest using the official samsung Car dock, as the USB port on there has a special impedance that tells the phone to go into driving mode, which once you unlock the phone, it stays unlocked until you either lock it, or take it off the dock. It also charges your phone at the same time. However if you have a case, this will not work for you. You would need to solder up your own usb plug that has a certain impedance over some pins (theres a thread somewhere about that, its like a jig, but with different impedance) and just plug that in when you're driving, but you still have to unlock the phone at least once with it plugged in.
My clarion cz500 car stereo has no issues making or receiving calls via Bluetooth while my phone is locked.
Sent from my GT-I9100 using xda premium
My biggest gripe with Android is that BT calling does not work as well as it did with WinMo's Voice Command (which works really well considering how poorly much of WinMo worked). Initiating calls via BT is my main gripe with Android. I wish Google would get it right already. That said, I have no problems answering calls via BT even when the phone is locked.
My phone is paired with the built-in BT in my car and I have no issue with making/taking calls while the phone is locked. Maybe its a compatibility issue with your particular hands-free device?
I also have no BT problem when locked, using the standard BT in my Toyota Avalon, 2011. Running rooted, UnNamed ROM, Entropy's DD 120811 kernel.
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Miami_Son said:
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Click to expand...
Click to collapse
Sgs2 does this stock with no problems via samsung/vlingo voice command app. Seems hit or miss on some custom roms. As long as device has bt turned on and had been prior paired with a headset, just have to turn headset on then hit the button on the headset. Voice prompts over headset ensue
Sent from my SGH-I777 using XDA App
I'm headed into the AT&T store tomorrow to do some definitive tests but so far I'm skeptical people who say it's working for them truly have their phone locked. The Bluetooth unit in question is a Parrot CK3100 LCD - a bit dated (3 years old) but it works flawlessly with several WinMo phones, several non smartphones (mostly Nokia's), and we just tried a friend's iPhone 3GS and iPhone 4. In all cases phonebook and voice dialing not only worked excellently it worked when the phones were truly locked and the screen off.
On the other hand the 3 Android devices I've tried all have the same problem - they won't dial out either by phone book entry or voice recognition unless you unlock the device first. The 3 devices are: Samsung Galaxy S II (AT&T), Samsung Galaxy S (Verizon), and EVO 3D (T-Mobile).
Unfortunately I don't have any other Bluetooth headsets to try out, hence my planned trip to AT&T. I plan on walking out of their either with a Bluetooth device that works or an iPhone Thanks for the replies.
I hear you. I have a Motorola FINITI bluetooth headset and it will not voice dial with the screen locked on my AT&T Galaxy SII.
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
mohitrocks said:
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Some roms give you a quick toggle in your status bar called secure mode, this should do it.
I'm on villain rom with jaykay mod quick toggles and i have that options.
Sent from my GT-I9100 using xda premium
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
GeorgeP said:
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
Click to expand...
Click to collapse
Are you using a pattern/pin lock? Or just the slide to unlock.
Just slide to unlock.
It works very well and very straightforward. I just press and hold the call button on my headset (while the phone is locked), and then after the tone say, "call John Doe on mobile" and it works.
Something for OP to consider in troubleshooting why he is unable get this work:
The BT voice dial works through the older pre-installed Vlingo (version 2.x). Even though I have the newer version (3) of Vlingo installed, the phone still launches the older preinstalled version of Vlingo for BT voice dial. So it seems the BT voice dial function is in some way hardcoded to that version of Vlingo.
Perhaps OP is using a custom ROM in which the older pre-installed Vlingo is removed(?). I know that is the case with some of the custom ROMs for the Int'l SGS2.
If I were to freeze or remove the older version of Vlingo, that might impact BT voice dial. Although I wouldn't expect it to affect the use of my phone through my car's build in BT.
Try it with a pattern lock or some kind, I believe that is what the OP has and its what "locks" the phone from using BT dialing, whether its voice based, or address book based from a headunit.
OK, if OP means that type of lock, then, no you cannot make a call when locked.
Although, it is not clear to me why one would want BT to bypass the lock in this manner. It seems the PIN or pattern lock would be pointless. If the phone is stolen (or lost) the person who stole it (or found it) could have access to your phone's contents through bluetooth. Am I missing something?
Definitely missing something. He wants the phone to be able to make calls while the phone is locked which is why i suggested to keep it unlocked by enabling driving mode through the mount.
My point was that allowing bypassing the lock through BT creates a exposure many would not want. The simplest solution might be keeping it unlocked either using a mount as you suggest, or using one of the profile apps that lets you create a profile to keep the phone unlocked when plugged in. He could then plug it into the car power adapter.
I use a pattern lock, and can make calls through the built-in BT in my car when the phone is locked. I can dial on the car's touch screen (disabled when the car is in motion, except for pre-set speed dials), or tell it to call someone by pressing a button on the steering wheel and saying the name. The car BT compares the spoken name with the list of contacts from my phone that have been BT-loaded into the car's contact list. Nevertheless,the call is made though the phone, since the vehicle BT is not itself a phone. Has anyone noticed that we have not heard again from Rajah, the originator of this thread? Rajah, are you there? Were your issues resolved?
Hey All,
My phone is pretty much stock, (close to) latest HBOOT/Radios/OTA (ICS), although I have flashed whatever version of TWRP was around way back when the latest OTA came about and rooted it.
Anyway, I've got a peculiar thing happening that I only just discovered: When I pair and connect my phone's bluetooth radio with the audio system in my car (the car is a recent addition to the family), I can't get the phone app audio to work properly over the car's audio system.
One possible clue is that I do use PowerAmp to play music over BT, and it works fine. When I dial the phone and press send, as soon as dialing ensues, music is interrupted, the phone number I'm dialing shows in the radio's screen, but audio goes completely silent. I have to manually change the phone app's sound from BT to speaker to continue with phone calls.
Have any of your experts ever had, and solved, this issue?
Thanks!
john