Edit: Ignore this post
Solution: Read it to me app was set to auto-on on bluetooth.
Problem has been fixed.
Solution left for reference.
Enjoy your laughs
Hello, all
I have an odd question
I have noticed that when I turn my bluetooth keyboard or mouse on (Logitech android keyboard, and android keyboard mouse) on my GTN7000 running stock ICS, the phone begins reading my texts aloud to me, even on silent.
But when I turn these devices off (BOTH of them, either being on will still trigger the problem), the problem goes away
This is a huge problem since this makes the phone worthless unless on airplane mode (which isn't bad but means I can't look things up on the web etc) while taking class notes, which is why I bought the keyboard in the first place.
This has been driving me nuts for the past four hours
This occurs even if I have disabled notifications in the status bar.
I have disabled text to speech
I have disabled call notifications
I have cleared all defaults for voice search
I have tried turning down all volumes.
I HAVE noticed that when I set the voice engine to something else (eg google voice engine to samsung vlingo) the voice engine changes.
I have also noticed when using driving mode on, I get two voices announcing the same thing at the same time.
please help!
Click to expand...
Click to collapse
I've got a minor voice search issue. I'm using speaktoit's assitant app, which is very helpful at times. Before I updated my ROM (insertcoin for HTC One) everything worked perfectly, but since the update, the behavior of two things are not how I like and I cant figure out how to fix them.
1. Pressing the home button and dragging up launches my assistant app. I want to disable that entirely. it already launches on home button long-press
2. When I speak, the voice search box shows that its listening to my voice, but when I stop talking, it keeps listening for a good 10 seconds before it actually passes off to the assistant. It used to be near instant, but now its as if it can no longer detect when i've stopped talking. Now I have to hit the mic button to stop it.
of course, these aren't critical, just minor, slightly annoying behaviors I'd like to iron out, and I can't find the info on google, so I'm asking the experts.
Hi all,
I've come across a couple of problems with the phone that I've put down to manufacturing, but I'm not really seeing anyone else complain about them. I'd just like to see if anyone else is experiencing these issues or if I should have my phone replaced under warranty.
Issue 1: Microphone.
During a call, people can hear me clearly, but if I switch to speakerphone (or use an app like Skype or Viber, which usesspeakerphone for video calls), they have trouble hearing me. I know there is an issue where the mic stops working for some people, but mine is still working...only I sound very faint to the other person. If I bring my face right up to the phone and speak, they can hear me somewhat clearly, but it defeats the purpose holding it to my face when I'm in a video call.
Issue 2: Screen touches during a call.
I've noticed that when in a regular call, the screen turns off when I bring the phone to my face, and turns back on as I pull the phone away, which is fine. The problem is though, that while the screen is off and pressed to my ear, shortly after the light of the screen turns back on and it seems I've been pressing things with my ear, e.g. pulled down the notification shade, opened an app on my home screen or opened my app drawer, etc. Is anyone else noticing the screen turning back on mid-call? Or does anyone know if the screen still responds to touches even though the backlighting is off? Or is this an iPhone 4-esque situation where I'm "holding it wrong"?
Thanks guys
I take it the lack of responses means that no one else is experiencing the issue and that I should swap it under Warranty :/
ronnie301184 said:
I take it the lack of responses means that no one else is experiencing the issue and that I should swap it under Warranty :/
Click to expand...
Click to collapse
nope. my speakerphone works great, everyone hears me very clearly. and during calls, when my screen goes off, the screen is actually off and my ear doesnt register touches. and yea, id rma it.
ronnie301184 said:
Hi all,
I've come across a couple of problems with the phone that I've put down to manufacturing, but I'm not really seeing anyone else complain about them. I'd just like to see if anyone else is experiencing these issues or if I should have my phone replaced under warranty.
Issue 1: Microphone.
During a call, people can hear me clearly, but if I switch to speakerphone (or use an app like Skype or Viber, which usesspeakerphone for video calls), they have trouble hearing me. I know there is an issue where the mic stops working for some people, but mine is still working...only I sound very faint to the other person. If I bring my face right up to the phone and speak, they can hear me somewhat clearly, but it defeats the purpose holding it to my face when I'm in a video call.
Issue 2: Screen touches during a call.
I've noticed that when in a regular call, the screen turns off when I bring the phone to my face, and turns back on as I pull the phone away, which is fine. The problem is though, that while the screen is off and pressed to my ear, shortly after the light of the screen turns back on and it seems I've been pressing things with my ear, e.g. pulled down the notification shade, opened an app on my home screen or opened my app drawer, etc. Is anyone else noticing the screen turning back on mid-call? Or does anyone know if the screen still responds to touches even though the backlighting is off? Or is this an iPhone 4-esque situation where I'm "holding it wrong"?
Thanks guys
Click to expand...
Click to collapse
Never faced any of such issues with my nexus. You should go for a replacement
I'll be on a call and the other person will suddenly be unable to hear me. This happens with stock and Pure Nexus (running on both elemental and shamu). It doesn't happen regularly. It hasn't happened in weeks, but yesterday it happened twice on one phone call and once on another. I can fix it during the call if I mute and unmute the phone on the display. When the phone mutes itself, the display control doesn't show that mute is active, only I after I press it and "activate" it.
I used to think it might have been my face pressing against the screen, but that can't be it as the screen is off while I'm talking. In order to fix it during a call, I have to turn the screen on first. Has anyone else had this problem?
I had this problem and found call screen lock in the play store (which solved it). It turned out I was somehow tapping mute with my face while on the phone after not tripping the proximity sensor...
It only happened rarely, but you can tell if you might be doing this if your screen occasionally wakes up while on the call without being pulled away from your face (the proximity sensor thinks it is not close to you face intermittently).
Recently I have not been able to use or see an on-screen keypad when I am using Android auto for phone calls during the call. I can get to the screen that is shown in my picture but there is no place to press a key pad during the call or an option for hanging up the call. Anyone else have this problem where can tell me how to fix it?
I usually initiate phone calls by telling Google to call a certain person.
Update: Well after a quick Google search I found that it was the Samsung car mode app that was interfering. So I uninstalled it and everything is fine. Let's just leave this here in case anyone else has the issue.