is there a download or fix for the bluetooth voice command....my bluetooth works but when i push the button on the bluetooth it says give command and then there is an error followed by, it disconnects. any advice on what to do or where togo to get the fix for this problem?
I've not been following the latest news on Epic, but if Sprint has released 2.2 I think you need to manually update your phone. Though from what I've read in the previous days was that Sprint did send out an update to some Epic users but the update was buggy. Therefore not everyone had their phone updated. Though assuming you're new to this forum ? And perhaps your Epic ? If your phone has 2.1 then there's no way you're going to be able to use your headset as 2.1 isn't capable of dialing out only accepting calls and manually making calls. I'm using midNIGHT custom rom and by using midNIGHT my headset does dial out. So join in on the forums and read up. I know there was a recent post http://forum.xda-developers.com/showthread.php?t=967014 That should be of great assistance to making your phone a lot better. Though most importantly I'm new here too and perhaps someone can give you better advice. But I do know that your phone out of the box won't allow you to voice dial using a headset until you're updated to Froyo and that I recommend midNIGHT rom but there are many roms to choose from as well as a lot of reading and learning which can be fun.
Related
i installed eb13 froyo and rooted my phone with cwm3.0.0.5 , then flashed viper rom trinity 2.0 with the eb13 genocide 1.2 ghz..everything seems to be very good and fast, but so far i have noticed that the blue tooth is not connecting. does anyone have any answers to why bluetooth is not connecting?
so i toggled around with my settings and now my bluetooth is working allowing me to answer phone calls and talk on the phone but the only thing that my bluetooth doesnt do is allow me to give voice commands when i tap on the button on my blue tooth!!! any advice anyone?
How did you get the headset to take calls?
Bluetooth Issues - Summary of Testing Results
This is a problem that goes away if I simply go back to a DK28 based ROM (which I have no plans of doing), but appears with any flavor of the EB13 update available.
On a day when I didn't have a lot to do, I decided to do some testing to see if I could find the magic combination of EB13 loading (upgrade.apk, ODIN .tar/.pit load, Samsung SWUpgrade and the DEODEXed [stock-ish] ROMS available) to get my bluetooth working like it does on DK28. I have upgraded to EB13 stock, EB13 deodex, deodex w/EXT4 (no member ROMS yet) along with stock/Genocide/Daemon's kernels ... essentially every mix of install, ROM and Kernel available. Add to that, I also cleared data on the OPP application --- I tried to cover every base I could. That being said, I have narrowed down my list of issues with bluetooth on EB13 to:
Paired devices are not saved. I have a Jawbone ICON and I have to add it everytime my phone is rebooted.
(Only add once on DK28)
Unable to Pair and Connect on first attempt. It always takes at least 2 and most of the time 3 presses of Pair and Connect to get the Jawbone paired and connected.
(Paired and connected on first attempt on DK28)
When my Jawbone pairs up, if you watch the notification bar closely, my wifi will also do a quick off/on right after the notification shows "Paired" on the Jawbone. Before you ask - yes, I ran tests with the various radio's on and off just to see if that was the cause. Nope.
(Never saw this on DK28, but then again was not watching for it either)
Like others have said, I can voice dial using the Voice Dialer application on the phone, but I cannot voice dial by pressing and holding the voice dial activation button on the Jawbone (the start/stop/quick disconnect happens on the application).
(Press button, state name, call on DK28)
It did not matter what combination of the above I used, the result was always the above. I'll gladly assist in troubleshooting this issue, so if anyone out there knows what to look for in the logfiles, I'll gladly run a pair/connect sequence and capture the adb logcat output for review.
Thanks in advance ... None of these are showstoppers, in fact I love EB13 and also appreciate all the hard work done by the devs and contributors in these forums (plus I guess I need 10 posts now to add anything relevant to a dev thread ).
- Dan
If you use Titanium Backup and have backups from before the update, please read this:
I was having the same problem with bluetooth on EB13. Just before ODINing back to DI18, I decided to try this:
1. In Titanium Backup>Backup/Restore, find these three items backed up from a previous kernel: Bluetooth Pairings, BluetoothTest 1.0, BrcmBluetoothServices 1.0. --Touch and restore each one of these.
2. Go to Home>Menu>Settings>Wireless and Network>Bluetooth Settings (turn on bluetooth): If your device is listed as paired, unpair it. Pair it again as a new device.
This worked for me, except voice-dial through my Jawbone is force-closing (but I honestly don't know if it ever worked right anyway). At the very least, it is now pairing and connecting fine and staying connected for calls and music.
P.S.
I suppose if you don't already have a backup of these items you could ODIN back, get Titanium Backup, backup all apps and system data, then update to EB13 all over again and restore the bluetooth data.
If you flash the acs frozen rom bt voice dialing works and the rom is very fast and very smooth. The best rom I've seen yet.
I've been having problems with Bluetooth on MidnightROM 4.2. The Bluetooth is extremely flaky -- sometimes pairs, sometimes doesn't -- doesn't stayed paired.
I haven't struggled with it too much because I never used Bluetooth much, but I would like to know if there's a fix.
jbadboy2007 said:
If you flash the acs frozen rom bt voice dialing works and the rom is very fast and very smooth. The best rom I've seen yet.
Click to expand...
Click to collapse
ACS has these same issues. It is a EB issue and I find I am having the same problems.
Hell everyone,
I recently rooted my phone and installed LiquidSmooth on my AT&T Samsung S3. About three days into using the ROM, I notice some connection problem between my phone and AT&T's network. The problem I experienced was I wouldn't receive texts or calls from other people even though the phone is connected to the network. When I do receive the texts, they come all at once at the same exact moment. Which means my notification ringtone going off like crazy.
This problem usually occurs at night around 9-12PM. I also experienced the same exact problem when I first started using CM10, the stable build. The one thing I also noticed after installing both ROM's is there's no voicemail number. I had to manually add a voicemail number, which is my own number, right?
I decided to unroot my phone and run Samsung's newly released JB update, which totally blows besides the battery life. As of right now with the unrooted phone and Sammy's updates, everything is running fine.
Thanks very much, I appreciate any help I get from you guys. And, I do want to apologize in advance if this question had already been asked. I tried searching, but couldn't find anything on the subject. If you guys need anymore details, please do not hesitate to ask. I will try my best to provide as much detail as possible. Thanks once again.
Okay so I know that Google Now does not want to work with Bluetooth microphones, headphones, or anything of the sorts.
However I have heard that in the newer versions of Android (at least 4.2.2 and up) Google Now has had its code rewritten and it now works with Bluetooth.
My whole issue is that S-Voice is a slow piece of s**t and doesn't manage to do anything that I want it to do, particularly interface with Play Music. I have installed a pretty awesome stereo in my car, but I feel that S-Voice with all of its prompts and on screen pop ups is unsafe for driving, whereas Now would suit my needs much better.
Essentially what I'm asking is that if I were to put an Android 4.2.2 ROM on my device (recommendations highly appreciated, preferably with WiFi calling enabled), if it would interface with my head unit when I need to use handsfree (activated by a little telephone call button on my JVC head unit that currently enables the annoyingly slow S-Voice app).
Any ideas? I tried a workaround using 'Bluetooth Launch' and disabling S-Voice already, as advised on a few other forums... no such luck... just gave me an error code on the head unit. Kinda a strange thing, I know. Let me know if you have any ideas.
Thanks a bunch for your help and input, it's much appreciated.
PS. I'm really sorry, I hope there isn't another thread similar to this, I'm totes a noob
Not sure if bt will work like you want on a 4.2 2 rom. But you cannot have wifi calling unless its a T-Mobile Touchwiz based rom. We only have up to 4.1.2 on those.
Make a nandroid backup and try out a couple of roms. If you like the functionality enough, keep it, if not restore the nandroid.
Sent from my SGH-T999 using xda premium
I'm a first-time poster here but I've been using XDA for years to root and flash phones. My first android phone was the EVO 4G and I've had about 5 since then, all of them rooted and flashed multiple times with no issues to date... until now!
My wife has an older T-Mobile Galaxy S2 (T989). She was having problems with the keyboard hanging and text messages lagging so rather then wipe it and restore the stock ROM I figured I might as well update it.
I used the latest release of CWM and rooted the phone with SU.
Then I flashed a new radio ( SGH-T989D_TLMC4_radio ).
Then I flashed Paranoid Android 4.0 beta 6.
Then I flashed mini gapps.
Everything on the phone seemed to be working great but then today at work she tried making phone calls.
The phone is able to dial and make calls and pickup and receive calls but the actual call quality is terrible. The voices are all broken up and have high pitched digital noise mixed in with the voice of the other caller.
Should I experiment with flashing different radios? I did a search and couldn't find much but I wasn't sure how to word the problem so it might be a common issue that I'm not aware of. Thanks!
kaptr1d said:
I'm a first-time poster here but I've been using XDA for years to root and flash phones. My first android phone was the EVO 4G and I've had about 5 since then, all of them rooted and flashed multiple times with no issues to date... until now!
My wife has an older T-Mobile Galaxy S2 (T989). She was having problems with the keyboard hanging and text messages lagging so rather then wipe it and restore the stock ROM I figured I might as well update it.
I used the latest release of CWM and rooted the phone with SU.
Then I flashed a new radio ( SGH-T989D_TLMC4_radio ).
Then I flashed Paranoid Android 4.0 beta 6.
Then I flashed mini gapps.
Everything on the phone seemed to be working great but then today at work she tried making phone calls.
The phone is able to dial and make calls and pickup and receive calls but the actual call quality is terrible. The voices are all broken up and have high pitched digital noise mixed in with the voice of the other caller.
Should I experiment with flashing different radios? I did a search and couldn't find much but I wasn't sure how to word the problem so it might be a common issue that I'm not aware of. Thanks!
Click to expand...
Click to collapse
I think the radio you named above is for the Telus version of the phone (not T Mobile). Here is a link to the radio thread:
http://forum.xda-developers.com/showthread.php?t=1895400
Hello fellow galaxy users, I have this problem on my T-mobile Samsung galaxy s4 and it is when I make a call, I cant hear anybody on the like or the dial tone or anything, and when the other picks up my call they can't hear anything either. Also if I pick up a call I still cannot hear anything. It is just plain silence. NOW HERE IS THE WEIRD PART! If I turn on wifi calling, I can call and receive calls with out any problems, if I use skype I can hear from the speaker and everything. So my mic is working, my speakers are working, everything seems to be functioning... Till I make a call using data... My guess is its a T-mobile network issue? I called T-mobile and they didn't know what was wrong... I looked around google and many people are having the same problem with no solution... If anyone has any ideas or any solution and would like more info on this problem, please let me know!
Have a nice day !
im having the same exact problem! i have seen some fixes that people have posted with similar issue, leading them to believe its something with their bluetooth/ok google/s voice being involved. ive tried some of the fixes that have been posted, but no luck on fixing the issue on my end. but just like you if i go on wifi and make a call i have no issues what so ever! the sound also works just fine if i connect to a bluetooth device.
Are both of you on the full NH7 firmware?
Mismatched bootloader?
Pp.
fully stock rom, not rooted. OS 4.4.4, yes nh7
i will add that this is my first galaxy, that i haven't rooted or changed the rom on. i have yet to have a reason to root or change the rom on this phone, but if i have to, to get this fixed? i have no problem rooting and changing the rom.
also i have noticed that i drop LTE to 4g when ever i try to make a call. the wife has the same phone and is on tmobile as well but she has not had this issue.
Ok, since you are stone stock this could be a update issue, just out curiosity I would try a factory reset (hard reset ) it may solve the issue . If not I would go with stock rooted like ShinySide's rom not full custom until issue is solved.
Pp.
ive done a hard reset and the problem is still there. i guess ill go the ShinySide's rom way, until i get my s5 or wait for the rumored s6.
This by ShinySide will give you an option to flash a stock firmware if you choose to be stock again. Follow instructions using Odin.
http://forum.xda-developers.com/showthread.php?p=54155517
Pp.