Develop Bugs

Problems with voice dialing on Jelly Bean

I am experiencing problem voice dialing from bluetooth headset on jellybean roms on the vzw gNexus.
On any non jellybean rom i can say... for example... "call mom on mobile" and it will, 95% of the time call mom. On jelly bean if i say the same phrase, it will 100% of the time return "calling tim, on mobile". In fact, it doesn't mater what contact name i say, it it ALWAYS suggests the wrong contact.
I thought, ok, lets try google now. If i open google not, tap the mic(voice input) option, and say, "call mom on mobile" it will fill in the search box with "call mom on mobile" so its understanding me correctly, then below that is says
"did you mean call tim on mobile"
and lists tim then mom in a list of numbers to call.
I spent over 3 hours trying to get this to work right, flashed every JB rom i could find, wiped and rewiped and reflashed. Finally went back to ICS and retested, sure enough it works awesome on ICS.
Can anyone atleast try to replicate this problem, or is anyone already experiencing it?
THanks!

Bump

Bump again.
Almost 50 views, if anyone using a bluetooth and Jellybean can at least try it and let me know if it happens to you or not. Thanks

Works fine for me.
Sent from my Galaxy Nexus using xda premium

greyphil said:
Works fine for me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
what phone and rom are you using? Looks like GSM, and OTA.
I just checked it again and i got:
"Call mom on mobile"
**Did you mean -Mark**
Mark
Mom
Kathy
thats from google now.
If it activate the voice dialer directly from the bluetooth, it will call bob, mark, tim, or funniest a business name that starts with "borderview". Even after 20 tries it will not dial "mom" lol.
Alternatively, I tried dialing mark, tim, bob, and borderview directly, and after 10 tries each, they will not dial if i try to dial them, only if i try and dial mom. lol very frustrating.

Yes stock gsm JB with root. Does it only happen with your headset? If so, try a different BT headset.
Sent from my Galaxy Nexus using xda premium

It happens using a $150 bose headset, as well as a $20 plantronics.
If it don't use the bluetooth i still get terrible suggestions, such as..
"call mom on mobile"
Did you mean call tim?
Tim
Mom
Mark
wtf???

That's weird. Only thing I'd try now is flashing a different JB rom, but I can't really imagine that being the problem. Have you let someone else try it? Maybe it is you after all.

In have tried 3 different roms, and have been using the voice dialer since android 2.1 on over 10 devices. Also it works flawlessly on ISC using the same hardware. Is anyone able to successfully Bluetooth voice dial on jelly bean on a vzw gnexus?
Sent from my Galaxy Nexus using xda app-developers app

I just flashed my Sprint Nexus to JB last night and have exactly the same problem. I hadn't tried any calling on ICS before I flashed, so I can't compare on the same phone.
I just came from an Epic 4G Touch that used Vlingo, and it was always about 95% accurate. I hate to step backwards, but I may have to switch back to that.
Why can't anyone mimic the old MS voice dial where it asked for confirmation before dialing? If I said, "Call mom on mobile", it would ask, "Call mom on mobile?" I said "Yes" and it would dial.
The way it is now goes against all safety concerns for hands-free driving. Now I have to look at the screen as it starts to dial and madly grab at the End Call button when it guesses the wrong name to call.

JimSmith94 said:
I just flashed my Sprint Nexus to JB last night and have exactly the same problem. I hadn't tried any calling on ICS before I flashed, so I can't compare on the same phone.
I just came from an Epic 4G Touch that used Vlingo, and it was always about 95% accurate. I hate to step backwards, but I may have to switch back to that.
Why can't anyone mimic the old MS voice dial where it asked for confirmation before dialing? If I said, "Call mom on mobile", it would ask, "Call mom on mobile?" I said "Yes" and it would dial.
The way it is now goes against all safety concerns for hands-free driving. Now I have to look at the screen as it starts to dial and madly grab at the End Call button when it guesses the wrong name to call.
Click to expand...
Click to collapse
Im glad someone finally responded and said yes i have this problem, or no i use this feature and it works every time.
THis is a huge concern and i feel its only happening on the ported(CDMA) roms.
Can anyone else confirm this on a toro or toroplus, and confirm that this is not an issue on GSM gnexus's?
Thanks!

urushiol said:
Can anyone else confirm this on a toro or toroplus, and confirm that this is not an issue on GSM gnexus's?
Click to expand...
Click to collapse
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.

UnknownFearNG said:
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.
Click to expand...
Click to collapse
This makes me feel very strongly that the issue has been caused by something in the porting process. I will PM on of the devs. and see if he can reproduce it.

i am also having this problem on my CDMA nexus with JB. Everytime it's not even remotely close to properly detecting my call request.

I absolutely love the cyberon voice dialer because it works and it has verification.
Unfortunately, under JB when you press the dial button on the bluetooth headset the google now voice dialer overrides my cyberon voice dialer. The only way to make cyberon work is to completely disable google search. This completely disables all the new voice command support and google now as well.
Basically 3rd party voice dialers are no longer compatible!
No, the built in dialer is still unusable especially without verification.

For me, I've always had absolutely horrible results when using voice dial initiated from the Bluetooth earpiece (two different Jawbone Icons, three different Android phones, Eclair through Jelly Bean, official or custom ROM.)
Using voice search, Google Now, JB voice typing, or Dragon with Swype, it's perfect..
Sent from my Galaxy Nexus using xda premium

Can the long button press be changed from voice dial to voice search? (I think those are the right terms.) Voice search understands and dials much better. Plus, it sucks to be limited to just dialing from the headset.

kynolin said:
For me, I've always had absolutely horrible results when using voice dial initiated from the Bluetooth earpiece (two different Jawbone Icons, three different Android phones, Eclair through Jelly Bean, official or custom ROM.)
Using voice search, Google Now, JB voice typing, or Dragon with Swype, it's perfect..
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Cyberon is awesome. I wouldn't use a voice dialer without confirmation. I don't want people calling me back because my dialer got it wrong. Sometimes this can cause serious problems. If google adds a confirmation option that's when I'll give them a serious try. I've been told even the iphone voice dialer has confirmation.

UnknownFearNG said:
Fully stock 4.1 GSM Galaxy Nexus, no issues with voice-dialing any name.
Click to expand...
Click to collapse
Same.

martonikaj said:
Same.
Click to expand...
Click to collapse
Are you both dialing through bluetooth? Honestly it hasn't got one right for me yet. Not one where cyberon is dead on.

Delayed texts & missed calls DFW

Anyone in dfw specifically in fort worth getting texts hours later than they were sent and missed calls ? I thought it was cm10 but I'm on TW and having this issue .thanks
Sent from my SPH-L710 using Tapatalk 2

Bump
Sent from my SPH-L710 using Tapatalk 2

Calls come right away. No problem with those. Sometimes text will take a while to go through. Other than that, it is all peachy.

I 9m also having this issue in Plano, and would like to know a fix, because it is really annoying.

If any of you are using an airave or whatever they are calling it now, there are issues with text messages.

My sister, brother and friend are getting messages late and missing calls . I'll get like 5 messages all at once .
Sent from my SPH-L710 using Tapatalk 2

For the past 3 weeks I have had intermittent issues with incoming calls and texts. Outgoing calls and text are fine and all data is fine.
Originally thought it was an evo lte issue so I went to my gs3. Didn't resolve it. Both stock rom non root.
Happens in different areas. Near downtown Dallas where I live and in North East Dallas where I work.
Also thought it was a prl issue so I reverted to a previous one on each phone. No help with that particular issue but I did notice better data speeds. (yes I know prl don't affect data speeds)
I have called care a few times and they do see a few days with higher then normal failed calls. Made some account settings changes but it's still an issue.
Happened as recent as this morning.
Did a few reboots and since lunch all has been well.
Sent from my EVO using Tapatalk 2

Are either of you using Google Voice?

Lancerz said:
Are either of you using Google Voice?
Click to expand...
Click to collapse
Yes I use Google voice
Sent from my SPH-L710 using Tapatalk 2

I'm in Michigan and I had a period of about 5 weeks where text's and voicemails wouldn't get pushed to my phone until hours later. I do use an Airave 2.5 but it persisted outside of it's coverage. I will say that flashing to stock and updating my profile seems to have fixed it. Either that or perfect timing of Sprint's network and a placebo effect. Good luck with your delay's. I would for sure nag Sprint about it if you don't see any improvements soon.

Lancerz said:
Are either of you using Google Voice?
Click to expand...
Click to collapse
I do use google voice but the problems i am having are directed at my actual sprint number and not GV.

Calls are fine for me text have always been a bit late for me since I live in a house with a metal roof ie no signal in the house but not hours late
Sent From My AOKP Galaxy S III From Sprint

parmend said:
Anyone in dfw specifically in fort worth getting texts hours later than they were sent and missed calls ? I thought it was cm10 but I'm on TW and having this issue .thanks
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I'm east of the metroplex and have been having these issues. I am not using google voice and on FreeGS3. Any thoughts? This is beyond frustrating. My calls go directly for voicemail and get texts hours after originally sent.

The only way i was able to get my problem resolved was to go to T-Mobile.
I spoke with Sprint network engineering in Oklahoma several times and they were telling me it was a capacity issue causing the calls not to go thru.. However i dont buy that.
On several occasions the problem would initiate in one location the i would drive from Dallas to Garland, or NE dallas to NW dallas and the calls still didnt go thru. IF it was capacity then as soon as the device went to a tower that was able to handle the calls i should have gotten the voice mails and texts AND incoming calls would once again go thru.. but that never happened. They have a bigger problem on their hands and they have yet to realize it or, like me, not enough people realize it. I dont make a lot of voice calls. Mainly data and text.. Looking back now i do remember some instance of texts coming in bunched together.

the issue is related to the network vision\ lte upgrades. Been dealing with everyday for a couple of months with people from different areas

parmend said:
Yes I use Google voice
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Do you have your Sprint number integrated with Google Voice? When I had my number integrated with GV, I had issues with getting missed calls. I would see the missed calls in GV but my phone wouldn't even ring.

Yep I have been having this issue for quite a while now, I am in Arlington most of the time and if it were not for Google Voice on my computer I wouldnt even know that I had missed calls or texts. No notifications for voicemails, calls nothing. Then other times it works fine.
I was told by a sprint tech that this was normal right now and part of the NV/LTE upgrades and that "you wouldnt be driving a car while the mechanic was working on it without problems, same principle" So yeah joke is on us for being customers I guess.

billbrasky82 said:
Yep I have been having this issue for quite a while now, I am in Arlington most of the time and if it were not for Google Voice on my computer I wouldnt even know that I had missed calls or texts. No notifications for voicemails, calls nothing. Then other times it works fine.
I was told by a sprint tech that this was normal right now and part of the NV/LTE upgrades and that "you wouldnt be driving a car while the mechanic was working on it without problems, same principle" So yeah joke is on us for being customers I guess.
Click to expand...
Click to collapse
I think the problem is on Google's end because once I undid the GV integration, my issues went away.

clankfu said:
I think the problem is on Google's end because once I undid the GV integration, my issues went away.
Click to expand...
Click to collapse
I CAN 100% tell you that this issues has nothing to do with Google Voice....it is related to the network vision \ lte upgrades.....the biggest issues that that thier is a handoff issues when going from 3g to 4g in some areas. Only fix that has been found is to with to 3g mod only are use a older phone that is not lte

skullygbear said:
I CAN 100% tell you that this issues has nothing to do with Google Voice....it is related to the network vision \ lte upgrades.....the biggest issues that that thier is a handoff issues when going from 3g to 4g in some areas. Only fix that has been found is to with to 3g mod only are use a older phone that is not lte
Click to expand...
Click to collapse
Well, I can only tell you that my issue went away immediately after I got rid of the GV/Sprint integration.

No Forwarding of Calls

I have gone thru 2 sim cards, 2 SM-N910A with similar results.
In settings, call, additional settings, it comes up with Network or SIM card error. AT&T has replaced two sim card, one a micro sim, one a nano sim with adapter.
From the keypad, **21*808551999# the error message as attach
The AT&T associate spent an hour with the advanced tech support to no avail.
I have a Nexus 6 and I can access all the above function, so my account is provisioned properly and I'm post paid

Did you ever find a solution? I'm having the same problem.

It's something to do with the phone, as you seem to be aware of, I had a customer come in who wanted to forward his note 4 to his gear s, the same issue happened, from what I can gather it seems to just be an issue with the call app itself, a fix I read but never go to try was taking a sim card from a known working phone that has call forwarding on and inserting it into the unworking phone.

Try stopping the phone app and clear all data. I got a new sim card and then did that and my call forwarding worked. YMMV

I have the same problem. I called tech support today and the lady I talked to didn't even know that the gear app could auto forward you calls. She said she would set it up for me on her end. Not what I wanted. I want this 2 high end devices to perform the way they are suppose to before att got there hands on it.
So what I did was, I pulled out my Note 3. Updated to latest FireKat Rom and problem solved.
My note 4 and gear s worked perfectly when I first got them. THEN WE GOT AN UPDATE--------THE ONLY UPDATE.
That's when I first started having this problem.
Not only do we not have root, but now it isn't doing the cool things it should. I'm sorry for the long winded ***** but I shouldn't have to wait for the chance of a possible maybe sometime in the future if everything goes right update that may or may not correct this problem and could possibly inject more issues. I'm sure someone will correct me if I'm wrong.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app

thanitos said:
It's something to do with the phone, as you seem to be aware of, I had a customer come in who wanted to forward his note 4 to his gear s, the same issue happened, from what I can gather it seems to just be an issue with the call app itself, a fix I read but never go to try was taking a sim card from a known working phone that has call forwarding on and inserting it into the unworking phone.
Click to expand...
Click to collapse
jrtireman said:
I have the same problem. I called tech support today and the lady I talked to didn't even know that the gear app could auto forward you calls. She said she would set it up for me on her end. Not what I wanted. I want this 2 high end devices to perform the way they are suppose to before att got there hands on it.
So what I did was, I pulled out my Note 3. Updated to latest FireKat Rom and problem solved.
My note 4 and gear s worked perfectly when I first got them. THEN WE GOT AN UPDATE--------THE ONLY UPDATE.
That's when I first started having this problem.
Not only do we not have root, but now it isn't doing the cool things it should. I'm sorry for the long winded ***** but I shouldn't have to wait for the chance of a possible maybe sometime in the future if everything goes right update that may or may not correct this problem and could possibly inject more issues. I'm sure someone will correct me if I'm wrong.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
I came across this post:
This is a problem with AT&T. I'm running 4.4.4 Android on a new Note 4 and discovered that Google Voice wouldn't run on the phone. I suspect the issue is tied to AT&T's implementation of their Visual Voicemail.
After spending a few calls with AT&T Tech Support, I was able to get my Google Voice to work by using the Call Forwarding Settings of "Forward When Busy", "Forward When Unavailable", and "Forward When Unreachable" to be set to my Google Voice number. The problem is that the Note 4 has the bug you mention. It's not possible for the user to access the settings on the phone without getting the "Network or SIM card error" message.
AT&T Tech Support can manually configure these settings, but this will only help if you don't change the settings often because a call to AT&T is required. I'm hoping they fix this bug in the Lollipop build.
Be careful when calling AT&T Tech Support, the first two times I called, the Tech Support Agent had no idea that this type of Call Forwarding Settings were configurable.
For the 3rd try at calling them, I got someone more knowledgeable who first reset my voicemail to "Basic Voicemail". This is done in the AT&T system, not on the individual phone. Once that had been done, I then had to "activate" the Basic Voicemail by configuring my box. As soon as that was done, the AT&T rep was able to go into the AT&T system and manually configure the three Call Forwarding options that I wanted.
It was a huge pain to go through, especially because all I wanted to do was use Google Voice which has worked on AT&T Samsung phones going back to my first Galaxy SII.
My phone still shows the "Network or SIM card Error" whenever I try to access the Call Forwarding Settings, but at least I was able to get the Call Forwarding configured for my Google Voice to work again.
I don't know if this info helps you out, but I wanted to pass it along.
Went back to AT&T yesterday, this time armed with my Nexus 6. Got a nano sim. Nexus 6 call forwarding function work. Working sim into Note 4. same crap happens.

I just check again this morning, and my Note 3 is working flawlessly. Gear app autofowards my calls as it should and advanced call settings does not show error message. I believe it's a problem with the Note 4 not able to register it's self with the network. If I use another phone it registers fine, call forwarding work as does tethering hot spot. If I try my Note 4 neither wants to work. When I call att they can fix my tethering hot spot but can't fix forwarding. My Note 3 just works by its self without having to do anything such as clear app data or anything with I have tried along with phone reset multiple times. I'm going to use my Note 3 for a while.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app

Used my Note 3 all day today. Everything worked flawlessly. Got home and started my tethering hotspot and no problems. I'm thinking that I'm getting tired of my Note 4. My Note 3 running Firekat is just as fast. The only thing is the camera and the screen is so good. I wish my Note 4 was as, we'll I'll stop there. Thinking about trading Note 4 in for the iPhone 6 plus. I'll still have my Note 3 that everything works perfectly on. I get bored and like to be able to switch up the experience so if I have android, Note 3 would be note 4 but, and the hated ios witch just works and that can be jailbroken with a lot more help because they are all the same device and dose not have individually locked boot loaders. ????? What to do???
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app

jrtireman said:
Used my Note 3 all day today. Everything worked flawlessly. Got home and started my tethering hotspot and no problems. I'm thinking that I'm getting tired of my Note 4. My Note 3 running Firekat is just as fast. The only thing is the camera and the screen is so good. I wish my Note 4 was as, we'll I'll stop there. Thinking about trading Note 4 in for the iPhone 6 plus. I'll still have my Note 3 that everything works perfectly on. I get bored and like to be able to switch up the experience so if I have android, Note 3 would be note 4 but, and the hated ios witch just works and that can be jailbroken with a lot more help because they are all the same device and dose not have individually locked boot loaders. ????? What to do???
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
Tethering should work unless you have unlimited data, all mobile share plans from att include thethering, also you can pre-order the s6 on Friday, if I remember what our new Sammy rep was talking to me about, got to play with it for 30 seconds before a customer walked in, the ui is nice and smooth and the new octa exynos chip is suppose to run cooler and it seemed, just for ui scrolling, to sail through it all. I like the look and feel, I want it......
Edit: keep in mind that you'll be in the same position you are now as far as root and unlocked bootloader, if you want these things wait to see who sells the phone unlocked then buy it at full retail and use it on your account. I work for att, I know even the nexus 6, the most close to stock phone we sell has bloat ware and is locked down tight. If I get the s6 it's out right and unlocked.

Yes I agree. It should work. If I switch my sim to another phone it works just fine. Everything works as it should, but if I put my sim back in my Note 4 in phone settings advanced settings I get an simcard or network error and call forwarding does not work. Also tethering will fail telling me to call 611 or visit website to register device for tethering. Gear app will fail to forward calls also and I have had problems with network data. If you Google this problem it is a problem with note 4. Some people on the att forums are just hoping for an update soon. That's is not acceptable to me. It worked when I bought the phone then there was an update that was pushed to my phone and now my phone is turned off and I'm using my Note 3. So by the time this gets resolved and I can enjoy my phone it will be old in the world of phone technology. So why should I keep it, hoping it will be updated sometime in the near future which keeps getting pushed back for some unknown to me reason. Don't get me wrong. I love my Note 4 but I want it to work now.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
The S6 Edge does look nice though.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app

jrtireman said:
Yes I agree. It should work. If I switch my sim to another phone it works just fine. Everything works as it should, but if I put my sim back in my Note 4 in phone settings advanced settings I get an simcard or network error and call forwarding does not work. Also tethering will fail telling me to call 611 or visit website to register device for tethering. Gear app will fail to forward calls also and I have had problems with network data. If you Google this problem it is a problem with note 4. Some people on the att forums are just hoping for an update soon. That's is not acceptable to me. It worked when I bought the phone then there was an update that was pushed to my phone and now my phone is turned off and I'm using my Note 3. So by the time this gets resolved and I can enjoy my phone it will be old in the world of phone technology. So why should I keep it, hoping it will be updated sometime in the near future which keeps getting pushed back for some unknown to me reason. Don't get me wrong. I love my Note 4 but I want it to work now.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
The S6 Edge does look nice though.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
I updated to 5.01, still has the same issue. This is quite possibly the last Samsung phone I'll ever buy

Elpidio said:
I updated to 5.01, still has the same issue. This is quite possibly the last Samsung phone I'll ever buy
Click to expand...
Click to collapse
force stop the phone app and it should fix your issue.

icexshinigami said:
force stop the phone app and it should fix your issue.
Click to expand...
Click to collapse
thanks for the tip, I force stop all three phone apps to no avail.

Elpidio said:
thanks for the tip, I force stop all three phone apps to no avail.
Click to expand...
Click to collapse
I know you tried , the dialer codes.
always call forward setting , **21*808551999# (did you make sure it is 10digits? should be , **21*1808551999# if you are in the us. it might be worth a try.
conditional call forwarding **004*1808551999# (busy, rejected, missed calls)

icexshinigami said:
force stop the phone app and it should fix your issue.
Click to expand...
Click to collapse
icexshinigami said:
I know you tried , the dialer codes.
always call forward setting , **21*808551999# (did you make sure it is 10digits? should be , **21*1808551999# if you are in the us. it might be worth a try.
conditional call forwarding **004*1808551999# (busy, rejected, missed calls)
Click to expand...
Click to collapse
sorry, there's one digit missing in my original post
should have been +18085519959
There's definitely something wrong with how AT&T network supporting this phone. I have no problem with my Nexus 6. It's very frustrating but it's something I have to live with if I want to keep using this phone.
Anyways, thanks for trying to help.

Elpidio said:
I updated to 5.01, still has the same issue. This is quite possibly the last Samsung phone I'll ever buy
Click to expand...
Click to collapse
The upgrade fixed the problem for me. I didn't change anything else besides the OTA update.

scrtsqrrl said:
The upgrade fixed the problem for me. I didn't change anything else besides the OTA update.
Click to expand...
Click to collapse
only thing I have not done is "wipe data/factory reset" from the recovery mode. I'll see if I can back up my data on ODIN

Elpidio said:
only thing I have not done is "wipe data/factory reset" from the recovery mode. I'll see if I can back up my data on ODIN
Click to expand...
Click to collapse
Weird that would have been one of the first things I did.. Assumed you already went that way.. If after all this it doesn't work it seems you may have a defective device and should bring it up with samsung or att for an exchange...

icexshinigami said:
Weird that would have been one of the first things I did.. Assumed you already went that way.. If after all this it doesn't work it seems you may have a defective device and should bring it up with samsung or att for an exchange...
Click to expand...
Click to collapse
I did the "wipe data/factory reset" from recovery and its still the same. You maybe right that the device is defective and since its more than 30 days, either I'll call Samsung for a replacement or claim insurance, however, by looking at AT&T community forum thread, I read that it all worked with N910AUCU1ANIE firmware, when AT&T updated that firmware, all hell broke loose. I'll see if I can have Samsung replace it.
https://forums.att.com/t5/Samsung-D...e-Update-Broke-my-Phone-Settings/td-p/4170378

Elpidio said:
I did the "wipe data/factory reset" from recovery and its still the same. You maybe right that the device is defective and since its more than 30 days, either I'll call Samsung for a replacement or claim insurance, however, by looking at AT&T community forum thread, I read that it all worked with N910AUCU1ANIE firmware, when AT&T updated that firmware, all hell broke loose. I'll see if I can have Samsung replace it.
https://forums.att.com/t5/Samsung-D...e-Update-Broke-my-Phone-Settings/td-p/4170378
Click to expand...
Click to collapse
Its on its way to Samsung Repair Center in Plano, TX

How Do I Enable HD Voice On The Galaxy Note 2?

Supposedly the ATT Note 2 supports HD Voice, however I don't think it's working on the phone. Is there a way to enable it, or verify that it is enabled? Assuming it even works on our phones. Thanks!

atehrani said:
Supposedly the ATT Note 2 supports HD Voice, however I don't think it's working on the phone. Is there a way to enable it, or verify that it is enabled? Assuming it even works on our phones. Thanks!
Click to expand...
Click to collapse
I can find nothing on Google regarding the Note 2 getting HD Voice. I did not even see any mention of Note 3. I did get lots of hits stating Note 4 getting HD voice. HD Voice requires both callers to have HD Voice capabilities and an indicator should appear somewhere saying HD in call.

IIRC, I've seen HD voice settings on my GN-II running stock 4.1.2: during a call there is an icon on the screen right above the "Add Call" button that looks like a squiggly line. Try tapping that and see what you get. Unfortunately I can't test it myself as my phone no longer has active service.

hi can someone help me get my screen call working.

I have a pixel 3 xl with the latest December firmware, I'm on T-Mobile and I live in Florida. As I said everything is updated I have the call screen option in the phone app, I even have dark mode. Now when you go to change the voice selection in call screen, the voice part is greyed out and says "ACTIVATING CALL SCREEN REQUIRES WIFI " I connect to both wifi and hotspot and still not activating.I contacted Google like 15 times send bug report, still no help.

Omi755 said:
I have a pixel 3 xl with the latest December firmware, I'm on T-Mobile and I live in Florida. As I said everything is updated I have the call screen option in the phone app, I even have dark mode. Now when you go to change the voice selection in call screen, the voice part is greyed out and says "ACTIVATING CALL SCREEN REQUIRES WIFI " I connect to both wifi and hotspot and still not activating.I contacted Google like 15 times send bug report, still no help.
Click to expand...
Click to collapse
Not sure what's going on. Didn't know u could change the voice for call screening. Mine worked since day one.

I'm wondering if it's my Carrier. It's greyed out

This is a pic of what I am talking about

Omi755 said:
This is a pic of what I am talking about
Click to expand...
Click to collapse
Are you a beta tester of the phone app? I was a beta tester and I had an issue slightly different than yours. I was able to activate it but it didn't work. I opted out of the beta testing and then uninstalled and reinstalled the app and it worked. Maybe try to become a beta tester if you're not one already. Just throwing some suggestions out.

Ok I will try that thank you

Omi755 said:
This is a pic of what I am talking about
Click to expand...
Click to collapse
Did you try to activate using WIFI first?

NICEGYPT said:
Did you try to activate using WIFI first?
Click to expand...
Click to collapse
+1. You don't have any wifi running in that screen shot.
Sent from my [device_name] using XDA-Developers Legacy app