My phone is suddenly announcing my calls...

[janusfenix]

I'm using a Nexus S, running stock Android updated to 4.1.2, with service from T Mobile.

Recently my phone has decided to start announcing the phone number / name of people calling.

Oddly, it sometimes continues doing so even after I've answered the phone, so I think it might be a third-party app that's doing it, but I could be wrong there.

Other forum topics have suggested Driving Mode or Caller ID Readout as possible causes, but I don't appear to have either of these options in my system settings.

How can I turn this off?

References:
hxxp://androidforums.com/samsung-galaxy-s3/646998-phone-just-started-announcing-incoming-caller-name.html
hxxp://androidforums.com/motorola-droid-razr-razr-maxx/563495-how-stop-phone-announcing-incoming.html
hxxp://www.droidforums.net/forum/droid-razr-support/205801-how-do-i-turn-off-who-calling-texting-announcement.html

 

[funkylogik]

Have a look in like "accessability" settings if the nexus has that and see if any apps have been allowed to use that service :thumbup:

 

[sleeco]

Turn off drive mode.

 

[mikedt]

Go Settings > Accessibility > Text-to-speech > Driving mode, toggle it to OFF.

 

[janusfenix]

@FunkyLogik:
Thank you - So I went to "System Settings" -> Accessibility (in the "System" section at the bottom) -> I don't see an option to view applications.
The options are as follows:
(Services)
TalkBack (off)
Widgetsoid Beta Notifications (off)

(System)
Large Text (unchecked)
Power Button Ends Call (checked)
Auto-rotate screen (checked)
Speak passwords (unchecked)
Text-to-speech output
Touch & hold delay (short)
Enhance web accessibility (Not allowed)

Are you talking about a different "Accessibility" screen?

 

[janusfenix]

@sleeco, @Mikedt:
As I mentioned in the original post, I already considered Driving Mode.

Settings > Accessibility > Text-to-speech (It's called "Text-to-speech output" on mine)
The only options are Google Text-To-Speech, Speech Rate, and "Listen to an Example".
In Google text-To-Speech, the only options are "Language", "Settings for Google Text-to-speech", and "Install Voice Data".
In "Settings for Google Text-to-speech", the only option is "Open Source Licenses".

Nowhere in here does it say "Driving Mode" or anything like that.

 

[Petrah]

Go Settings > Accessibility > Text-to-speech > Driving mode, toggle it to OFF.

Running Android 4.2.2 and I don't see a driving mode in there anywhere.

Janus; Tap on your phone icon (dial pad should come up) and go into the settings there. Check to see if there might be something in there that may have been enabled. It's probably a longshot, but you never know.

 

[janusfenix]

Running Android 4.2.2 and I don't see a driving mode in there anywhere.

Janus; Tap on your phone icon (dial pad should come up) and go into the settings there. Check to see if there might be something in there that may have been enabled. It's probably a longshot, but you never know.

Thanks! That was a good idea - I hadn't checked there yet.
In there, the only relevant setting was "Additional Settings" -> "Caller ID", which has "number displayed in outgoing calls".. I think that's just outgoing caller ID, not incoming caller ID.

Anyone else have an idea?
If not, what's the next step? Is there an official Android support line I can contact, or something?

 

[Petrah]

Tech support will ask if you've uninstalled all of your user installed apps.

Did you try uninstalling the last few apps you installed? You could try calling yourself from a landline (without answering of course) to test after you uninstalled a few.

If it is a 3rd party app, you should be able to narrow down the culprit by process of elimination.

If you find it, let us know which one it is?

 

[janusfenix]

Tech support will ask if you've uninstalled all of your user installed apps.

Did you try uninstalling the last few apps you installed? You could try calling yourself from a landline (without answering of course) to test after you uninstalled a few.

If it is a 3rd party app, you should be able to narrow down the culprit by process of elimination.

If you find it, let us know which one it is?

Yeah, that may be my best bet at this point - I can't remember for the life of me what the last few apps I installed were, maybe I can find a listing by install-date somewhere. Otherwise I can just select likely candidates. I wonder if it's Google Voice. I feel like it got an update soon before this started happening.

I receive phone calls so rarely that it could've been weeks or even a month or two since it started doing this.

I don't suppose there's a way to backup my apps before uninstalling, is there?

 

[Petrah]

Ah, it might be Google Voice. Did you check all of the settings in there? I use to use it but haven't in awhile so there may be a new option for that in there.

I use Android Assistant to back up all of my apps in apk format to my internal SD. It does not save app settings, only the apps themselves. Since I'm rooted I use Titanium Backup Pro to save user apps with settings. I know I'm saving the apps twice, but I like to be prepared just in case.

There may be another free app that will save app settings without being rooted, but I wouldn't know of any names.

 

[janusfenix]

You know, you'd think with a Nexus I'd have rooted by now...
If I can't figure out what's wrong I'll just use it as an excuse to wipe my phone and root.

Plan of action: Uninstall apps one by one, calling each time from another line, if I run out of apps then contact Android Support so that at least we have an answer.

Painful, but what can ya do.

 

[funkylogik]

I say root

 

[janusfenix]

Huh. Well, that was unexpected.
Started uninstalling apps, and one of the early ones I uninstalled was "Robin", a siri-like app.
It looks like that one was the culprit, despite the fact that I hadn't used it in a long time.

Weird.

Anyways, now that it's fixed I think I'll root anyways. Any recommendations for a first time guide?

 

[jhawkkw]

If you have Windows, Wugs Nexus Toolkit is a pretty nice tool that will take a lot of the work out of doing it. Install it, select your device/os, install the drivers, unlock your bootloader, and then root. *Warning* unlocking your bootloader will COMPLETELY wipe the device clean. Something to consider before you dive in.

 

[janusfenix]

Thanks, I'll try that!

 

[santeelj]

Huh. Well, that was unexpected.
Started uninstalling apps, and one of the early ones I uninstalled was "Robin", a siri-like app.
It looks like that one was the culprit, despite the fact that I hadn't used it in a long time.

Weird.

Anyways, now that it's fixed I think I'll root anyways. Any recommendations for a first time guide?

Thanks. I was having the exact same problem. Robin was the culprit. Instead of uninstalling, I went to settings and unchecked CALL ALERTS.

Thanks again.

 

[HelAnVal]

Language and Input settings.

Read notifications out loud is probably on.

 

[Cortriece]

This fixed my phone.... I had to do the Sprint steps but it worked

 

[Cortriece]

This fixed my phone.... I had to do the Sprint steps but it worked ....Google Voice