I bought my Xperia Arc 7 days back. Everything is just fine and I liked this cellphone very much, But suddenly yesterday when am using Google voice.. 1st and second time everything is great, Google voice recognized my every word but 4th time it says no voice input. I ended the program and go back to sleep. In the next morning one of my friend called me and he did not hear my voice. and from now on nobody is not hearing my voice. After that what I did....
1. On/off noise cancellation.(nothing happened)
2. Reset the phone to factory default.(nothing happened)
3. Restore rom with flash tool.(nothing happened)
4. installed voice meter and when I open it, its started from 70 bd not 0.
5. Checked with voice recorder. Without speaking anything its sound meter was full and when I played the recorded sound some weird sound coming.
But nothing happens to my microphone. Its just dose not working. If I close my mouth near to it and speak out loud then only my low voice is heard on the other part. Please help me as I already unlocked my boot-loader so I am now out of warranty.
Related
Problem with the sx66 that makes me crazy. I can not hear incomming calls sometimes. (1 out of 10 calls) Caller can hear me, the phone timer is counting, but no caller voice. Some times I can just hang up and when they called back everything worked fine. Sometimes I must soft reset. This also happened sometimes when I called out (not as much). Is this a pda phone thing, softwear glich, or something I am doing? Ready to go back to cans & string!
Also just got new cingular 8125. I have used the my new 8125 for one day and it has happened 2 times out of 15 calls. Any thoughts?
I have had a simular issue. Do you have TomTom Navigator? I found that sometimes the TomTom software seems to make the sound go down. I had to replace my phone shortly after i first installed TomTom because I could not get any sound out of the phone whatsoever, even after soft and hard reset. With my new phone, I still experience some volume related issues, but not as bad as before, and a soft reset usually fixes it. Now when it happens, the volume cuts down maybe a little more than half and I barely can hear the navigator voice. Good luck on your issue.
I've had my phone since Sunday, but I just put the SIM in it last night, and hadn't placed a phone call until today... That's when I discovered the horrible noises that the microphone is making during every call.. Even happens when using the built-in voice recorder.. Does not happen on a bluetooth headset, and persists after a hard reset.
Yep, that's right, going back to the store.. Sigh...
Happily the ATT store had a Tilt 2 in stock, swapped it out today without any question. They didn't even really look the phone over or verify my problem, which I was surprised at..
First thing I checked was the voice recorder, and it worked, so I've been charging and restoring. One interesting thing though, was that my ROM version appears to be different.. I'm opening a different thread on that one though.
I had this happen a few times, so I spent some time trying to figure out how to repeatedly reproduce it. It wasn't too hard.
1) Turn on a youtube video (I think that anything that used the phone's loud speaker would work).
2) Turn your media volume up to max.
3) Hold down the search button to bring up Voice Search.
I suddenly hear static and garbled audio.
4) Cancel (because I only accidentally pressed that button in the first place)
and the static and garbled audio stays around.
After that, I can go to most any audio app (visual voicemail, music beta, pandora, etc) or just get a notification sound from my phone and it will be complete static and garbage.
The first time I fixed it by playing a voicemail via visual voicemail through the normal speaker and then changing it to the loud speaker. That doesn't work every time though. I'm guessing that a reboot would also fix this.
I tried to reproduce this on my other TMO SGS2 both with the Voice Search shipped with the phone and the update from the market. On the one phone it happens with both versions and on the other, it never happens. I'm not sure that this is a hardware issue but I don't have a good explanation either way.
I've tried this a few more times today with a number of different apps and Voice Search and it hasn't reproduced itself. Most apps, like Google Music and Pandora, stop audio output when Voice Search is activated. Only YouTube seems to just ignore the Voice Search and keep going.
Edit: I exchanged my phone and this doesn't happen on the new one. Seems like a bad hardware issue.
Hi guys, I did a search in this Arc forum for In ear Speaker problems and couldn't find anything, so I chose to start a new thread. Just know I DID try to find info for this phone but I only found a few other threads about different phones.
My in-ear speaker does not work in calls. It is extremely quiet, as if the volume is turned all the way down. Thing is, I try turning up the in-call volume during a call and it does nothing. But the weird thing is, I went into the service menu to test the hardware (using the *#*#7378423#*#* trick) and tested the in-ear speaker and it works fine! Loud and clear! But then immediately following that I'll try a call and still will hear practically nothing. Putting the call on speakerphone allows me to hear the other party, as well as putting in a headset, so I am stumped. Tried pulling the battery and have rebooted the phone many times and the problem is still persisting.
AND, on top of ALL of that, the damn thing was working just fine the other day. I switched to this phone last week and have been making calls successfully being able to hear the other party just fine. But suddenly today it's deciding to not work in a call. This is really weird.
Has anyone else had this problem? What else can I try to fix it? Any help or tips would be greatly appreciated. Thanks.
EDIT: Blah a hard reset fixed it. Feel free to delete this post mods!
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.