Ever since I've owned this Shift, I've only ever known the microphone to work on one occasion, and then I started fiddling with flashing ROMs and Radios. Now the microphone will not work for nothing on either side of the Shift I have tried everything I can think of. I've heard that it depends on a combination of ROM and Radio, but I must of tried every single possible option and still nothing. Anyone have any experience with this? I can't just have a faulty microphone, it worked at one point. Any help would be appreciate. And yes, despite the fact that my iPhone 4 comes in the mail today, I'm am still very interested in playing around with the Shift. This getting it to call out and send my voice thing is beginning to mock me, and I'm taking it as a challenge.
Post #25 in Thaihugo's Age of Reason ROM thread gives the URL for a good radio ROM that works with his ROM.
http://forum.xda-developers.com/showthread.php?t=495143&page=3
So I'd install that radio image if I were you, and then install Thaihugos ROM. As far as I know, that combination is the most concrete base for your HTC Shift.
From there, you could see if your microphone works, and then move on to any other ROM/radio, keeping note of whether your microphone continues to work.
Hope this helps.
Related
I have been searching for an answer to this for two weeks with no success. I apologize in advance if the question has already been answered… I couldn't find it.
On Sprint's Hero, when setting up a headset (in my case the car radio BT adapter) one can enable both Phone and Media. Supposedly, this should allow a user to listen to tunes/podcasts/Sprint Nav and be able to use the phone when needed through the BT. Unfortunately, it doesn't work this way.
If I'm listening to something on the phone and wish to place a call, I will enter the contact and start the call. The phone responds by pausing the audio program I'm listening to as it should, but I get NO AUDIO from the phone! Nothing! The call is placed and the recipient hears nothing also!
Now; If I'm listening to something and a call comes in, again, as would be expected, the audio program gets paused and the phone rings through the BT. Unfortunately, there is no auto-answer in Android 1.5 (grrr!), so I reach over and press the Answer button. Lo and behold, it answers! but over the phone's speaker and mike instead of the BT!
They refused to accept that it was a problem with the phone at Sprint. Is this fixable? Can I look forward to it working in Android 2.1? Is there anyone else experiencing this problem?
As far as I have read/heard its a known issue that I think one of the roms here may have corrected. I will look around and see if I can find the thread, its been more than a month since I read it. Maybe MoDaCo but again, I will have to track it down.
EDIT:
Personally I wouldn't look towards anything in android 2.1, sprints release could be as far as 6 months away.
I'm currently using MoDaCo's UNOFFICIAL v1.3 ROM. I've tried this with his 1.1 and UNOFFICIAL 1.2 as well. I've also tried Fresh's ROMs without success.
Las_Vegas said:
I'm currently using MoDaCo's UNOFFICIAL v1.3 ROM. I've tried this with his 1.1 and UNOFFICIAL 1.2 as well. I've also tried Fresh's ROMs without success.
Click to expand...
Click to collapse
So maybe no one fixed lol
Just a quick question for you guys. When I receive a phone call (full signal strength) and slide the slider accross to answer the phone there is a long pause of silence before the call actually connects. Has anyone else run into this situation?
Nexus One running stock Froyo (At&t)
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Old MuckenMire said:
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Click to expand...
Click to collapse
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Never encountered that issue. The other side hears me immediately as I answer. I guess this is not "across all N1s", unless someone would think my N1 is special in some way (which it isn't, and so are all the other 7 N1s of my friends at work which also happen not to have this problem - and the call quality is great on at least 3 that I checked personally).
Instantly connects on my phone as well, so it's not on all devices at least. I have one of the first batches of T-Mobile N1's btw.
What carrier are you on?
this happens to me too.its so annoying. im on att
Can't find the thread but it was pretty long.
nexusdue said:
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Click to expand...
Click to collapse
I'm not so sure anymore. I decided since my only choice was to send it in for repair, I might as well one click root and install CM6 and see what happens. So far, I have not had the issue. It's only been three days but that's the longest this device has ever gone without having the "no connect" issue. Also, my low call volume and speaker phone volume issues are now resolved. I now find myself turning the volume down rather than up. I'll update this thread with final verdict on whether this fixes my issue.
This sounds like an att problem not a nrsux one problem
I notice this problem as well. If I wait until the call timer appears on screen before I start to talk the other party doesn't seem to notice.
I'm on T MO and never had this issue. Try the one click root and flash a different ROM. If it doesn't work send it to HTC. I recently sent mine back on a Monday and it was back that Friday.
Sent from my Nexus One
Well my issue has been resolved by switching to CM6. It's been a week now and the issue has not occurred even one time. This was an issue that used to happen to me EVERY DAY, so I am very happy that in my case it turned out to be a software issue.
When I was running 2.1 I hoped 2.2 would fix it and when it didn't I thought for sure it must be hardware. It's so nice to KNOW I can answer the phone if it rings now. Sometimes I would get an important call and I was afraid to answer the damn phone!
Thank you Mr. Cyanogen, whoever you are.
I get this issue once in a while. I think its a software issue. Over time something gets hung up somewhere.
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
khaytsus said:
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
Click to expand...
Click to collapse
Definitely not the finger covering the mic. Just tried it with/without and same result.
There was another thread that was at least 3-4 pages of people complaining about it.
Sounds more like a network issue than a hardware issue, IMO
This issue has come up recently for me and it's really annoying. I'm not sure what triggered this problem...
Is anyone else experiencing this issue? Any ideas on how to resolve?
I've got the Rogers/AT&T N1.
Is it possible that I have, as I saw after intensive reading of forum, microphone hardware fail? I have bought used TMOUS HD2 with stock rom 2.10.531.1 and as soon as I used it in Serbian network, microphone gets low in volume with background noise. The same is happening as I upgraded to latest stock rom 3.14.31.1. If I use bluetooth, everything is quite nice, which tells me it is not radio or network issue.
Here is a sample of my voice recorded by Voice Recorder.
Thanks for any help
Did you install Android? If you have the same problem in Android or some custom rom its probably defective.
I am thinking of doing that. Well, your oppinion is if it behave tha same, it must be hardware. Weird, no posts at all complaining mic!
Thanks anyway, keep you posted.
Happy New Year to all
After installing Android, mike becomes slightly better, but not OK. Could it be some driver issue? As soon as I get back to WM6, it got worse!
Hello all,
I was hoping someone could point me in the right direction to a Gingerbread ROM with a working media start/stop/call end headphone button (I'm using the OEM headphones that came with the phone) and 911. Both of these issues are documented bugs.
I've tried CM 7 and a couple of MIUI ROMs and the non-functioning headphone is pretty much a deal breaker, as I use my Vibrant for podcasts more or less everyday; the fact that 911 doesn't work just seems dangerous.
I've scanned lots of posts for different ROMs and neither issue really seems to come up telling me one way or the other and I don't have a day to load every single available GB ROM and figure it out via trial and error. Search hasn't been particularly revealing either.
For now, it's back to Team Whiskey NextGen v2, but I've tasted Gingerbread and I like it.
Thanks for your time.
Sorry everyone, posted in the wrong sub-forum.
I'm having problems when using earphones from the first day I bought my Omnia7. The problem is:
Earphones are fully functional, and there are no problems with listening music etc. But, after I make FIRST phone call using earphones or after I answer the FIRST phone call, my phone becomes unresponsive within short period of time, and I don't hear other people during calls nor they hear me. So the first call triggers all this. That first call however goes through without any problems, problems come after that. I tried using several earphones with same results. After I reboot everything works fine again.
I'm pretty much sure it isn't hardware related problem since I listen to music without any problem and the first call works great every time.
I'm running the latest version of OS and I got these new drivers from Samsung few days ago, but still no improvement. Anyone here with similar problems and if so, did you manage to solve it and how?
...
Almost 300 views so far, but none reply... It can't be I'm the only one with this kind of problem?!
I have same problem! Please help
When did you guys get your phone. Where are you now, have you flashed your phone or messed with any functions with in the Diagnosis App at all.
Omnia 7 has original Rom with mango update, no modding or special things.
Finally, some activity in this thread!
I had this problem, with stock Rom and also with several custom roms, so it must be hardware related. On the other hand, it shows some signs of software related issues, so I'm still confused...
hatuna said:
Finally, some activity in this thread!
I had this problem, with stock Rom and also with several custom roms, so it must be hardware related. On the other hand, it shows some signs of software related issues, so I'm still confused...
Click to expand...
Click to collapse
Samsung in a nutshell