Hey y'all
I'm having very odd audio issues with my Nexus One. The microphone/speaker/loudspeaker do not work at all when using the phone, playing music, recording video, etc. The audio and mic work fine with a wired/bluetooth headset connected. Now the weird part... alarms work! If I create an alarm using the clock app, the the audio chimes out loud and clear through the loudspeaker! Also, the same is true when I create a countdown using the 'StopWatch' app.
This all started happening today.
Any thoughts???
Update:
Wiped and flashed the latest Nightly, but still the same problem. But I notice that there is a strange 'headset' kind of icon (an overhead type, with attached mic, thing) in the status bar, which I've never seen before. I only mention this because I've also wiped and tried 'eViL's NXSense v.1.11' ROM, where the same icon (and problem) occurs??
Update 2:
After a bit of digging it turns out that the strange icon is to do with 'Hearing aids', and apparently it can be turned off under Call Settings > Hearing Aids. But that option isn't in my 'Call Settings'. I think this could potentially be the cause of my problem, anyone know where this check-box is located?
Example of icon: http://is.gd/eTUif
Any thoughts? Is there a diagnostic tool that can test the various audio I/O?
I think that icon refers to a headset connected to the headphone connector.
For some reason your phone thinks you have headphones attached... try to plug and then unplug earbuds or something
Tried that numerous times, to no avail. Can you see the 'Hearing aids' check-box under 'Call settings'?
Related
Its not ringing when a call comes in. It also does not vibrate.
The sound is up on the PPC and Ringer and if i go in to the phone settings it will play a ringtone fine.
Any ideas?
may be a reset might help? It also happened to me and after a reset, it all works good.
Don't know if it's the same thing with me, but my kaiser also at some point of day refuses to ring (still vibrates ok). It won't play mp3s with GSPlayer or MediaPlayer. Sometimes you can hear the song playing really quietly (only hear it if you press your ear to speaker).
It has happened like that for 3 days now. The sound will come back if I hit the tytn II gently (more like knock it). Althoug since today I'm not sure if it's the knock or the keyboard moving wich brings the sound back.
Any ideas?
What I've tried so far:
- Muting, unmuting
- changing volume
- soft reset
hard reset it. may be some programs you've installed might be conflicting. If the hard reset don't fix your problem, then you have a faulty unit. You can also try pocket mechanic to clean the registry and stuffs. Very helpful program.
Ok, will try hard reset.
Although I doubt it will help. Before hard reset, there was some very faint sound coming from the speaker. And speakerphone didn't work at all.
Back to resetting...
Try to change the ring tone to a different one, mine was doing the same thing it would only virate, I changed to a different ringtone and it worked fine.
I did try to change the ringtone. Every time the problem emerged. The problem was that the ringtone wasn't the only thing not playing. There was no sound for any of the events. And the speakerphone option also didn't work.
I did a hard reset last night. It didn't help. So I gave it up and went to sleep. I left my tytnII on a USB connection to my laptop. In the morning I checked if the problem was still there and found that the sound is back - the ringtones work.
I put it back on USB connection to sync. Copied an mp3 to test if it can play it (it has played it before). And there the sound went again - I can only hear it playing faintly if I hold the speaker to my ear. The ringtones won't even play when I check them in notification sounds setup - not even the default built-in ones.
Could it be a temperature issue? The tytnII sound was fine when I picked it up in the morning, it was room temperature. But it gets slightly warmer when I charge it or sync it.
I have done soft resets. I can play sounds in the phone settings options and music plays it will not vibrate when calling.
Resolved it was the 3G Dialer app causing the issue.Now i need a new one i hate the orange look....
I had an issue like this, but it was due to ringtones stored on the storage card ... and when the phone would wake up, since it takes the storage card driver a few secs to load, it wouldn't ring.... and I resolved it by moving my everyday ringtones to main memory
the thing is the rings are not on the card......
Maybe its the rom's radio
sleuth started to explain this in his upgrade however no one explains how to downgrade the radio. I believe mine is doing the same thing however I get no sound. maybe its the radio.
Draqula, did you solve your problem? Im having the same issue on my tytnII. I cant hear ANY SOUND. But if I play an mp3, for example, and I knock close to the speaker, the sound starts.
Any ideas?
My problem solved: The speaker was changed under warranty.
I just upgraded to 2.2 for the Captivate using the ODIN3, and everything is working great except sound through the headphone jack.
Music, navigation plays through the headset, but phone calls and notifications don't.
How am I supposed to hear them with music blearing over it?
Anyone know of a fix? I checked the settings and I don't see an option for it.
gir489 said:
I just upgraded to 2.2 for the Captivate using the ODIN3, and everything is working great except sound through the headphone jack.
Music, navigation plays through the headset, but phone calls and notifications don't.
How am I supposed to hear them with music blearing over it?
Anyone know of a fix? I checked the settings and I don't see an option for it.
Click to expand...
Click to collapse
Search would have told you that this is a known issue - 2.2 is Beta.
There is no known fix.
gir489 said:
I just upgraded to 2.2 for the Captivate using the ODIN3, and everything is working great except sound through the headphone jack.
Music, navigation plays through the headset, but phone calls and notifications don't.
How am I supposed to hear them with music blearing over it?
Anyone know of a fix? I checked the settings and I don't see an option for it.
Click to expand...
Click to collapse
You are lucky, mine doesnt let me even hear media or music thru the 3.5 mm!
???
I have 2.2 installed and don't have any issue with the headset.
Both music and phone calls work great.
BTW I'm using the stock hands free, the one that came with the phone.
My bluetooth works fine, it's the headphone jack I'm talking about.
i am having the same issue after upgrading via odin3. I also have to click the home button to clear a read text message or else it reminds me again.
B56_I897 said:
i am having the same issue after upgrading via odin3. I also have to click the home button to clear a read text message or else it reminds me again.
Click to expand...
Click to collapse
No voice out of the "3.5 mm"?
Yeah that was a LOLWUT post. And that's been on the phone since I've had it, it's intentional, I think. Because you have to press the back button to clear the notification, because when you click on messages again, it stays at the same spot and the notification stays in the title bar because you didn't clear it.
i hear sound but i dont hear voicalls or notifications. if im listening to music with my sony headphones and someone calls i dont the ring through the headphones or the voice. i have to use the handset
gir489 said:
Yeah that was a LOLWUT post. And that's been on the phone since I've had it, it's intentional, I think. Because you have to press the back button to clear the notification, because when you click on messages again, it stays at the same spot and the notification stays in the title bar because you didn't clear it.
Click to expand...
Click to collapse
when i was on 2.1, if i clicked a message from the notifiaction bar it would bring to the thread and mark it as read. froyo is not doing that. is there a way to fix it
IDK what 2.1 you had.
The one I had, I had to press back to clear the notification. It still does the same thing on 2.2.
It could be a bug, it is a beta.
alphadog00 said:
Search would have told you that this is a known issue - 2.2 is Beta.
There is no known fix.
Click to expand...
Click to collapse
I missed reading that in the notes.
I've searched quite a bit and never ran accross anyone mentioning it.
My headphones play music, notifications, everything just great, but in call volume is terribly low (NOT on headphones, but when I route the aux cable to my stereo in my car)
I had the issue initially in 2.1 from stock ROM, but managed to fix it somehow, and I can't figure out how. I tried all the evice level fixes, eve 6 different audio control apps off the market.
My typical setup is that I never use earbuds or headphones. I plug the aux cable into my headphone jack and run it sraight into my car CD player in aux mode. It plays everything at normal levels EXCEPT in call volume. If this is a bug, I'll just have to deal with it then.
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Hmmm...My Bluetooth connection never have that issues. I used Bluetooth headphones and my car head unit. Running oos 4.1.1 as well.
Try dirty flashing your ROM, there might be something wrong with the drivers. Bluetooth commands (volume, pause, voice assistant, skip, etc.) work find on my headset, I don't believe its a compatibility issue.
If that fails, it might be a hardware defect?
I don't have problems with Bluetooth im using sony wireless earphones everyday. Try reformat the phone
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Assassin1985 said:
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Click to expand...
Click to collapse
Huh? Must be an compatability issue between the BT device and your phone. I have 6 active BT devices I use all the time with this phone and my tablet. Car stereo, fitnessband, speakers and inear plugs.
Only issue I sometimes face is the 'stuck in connecting to last used device' where BT needs to be turned off and on again. Wouldn't call it a heavy issue.
bluetooth perfect here. better than my lg g3 that i had previous.
So, more info. If 2.4 GHz WiFi is active in ANY WAY, the bluetooth goes nuts. AVRCP (bidirectional commands) make it worse. Putting the phone in airplane mode to disable the "ambient" wifi location scanning and such, then turning bluetooth on manually and playing some downloaded music, seems to work fine. Switch the WiFi on though (even though my access point is 5 GHz), bam down the toilet. Ugh.
I did a complete reset and flashed OOS 4.1.1 from adb, no improvement. I'm trying the Open Beta 4 right now but I doubt it will be any better.
Did you turn off the scanning feature?
Happens to me like once every 3 days. I usually reboot by then
evilspoons said:
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Click to expand...
Click to collapse
Hi, I have the exact same phone and been having stuttering performance with Bluetooth and Sony MDR-X330BT and worked fine with the 1+ 3. I decided to tell the phone to forget the headphones and start afresh; big mistake headphones kept refusing to pair. I noticed they have the NFC symbol on one of the earpads so I enabled NFC and used app I had downloaded a while back, 'Tap-and-Pair' that did not work either. I did a search today and found a great app that worked - 'NFC Easy Connect' from the Play Store. Now all I need is stable connection from car system which appeared to be tied in with length of screen life before going to sleep but think it may be faulty Twingo as been on the car forum and found others with similar issues but different smartphone to the 1+ 3T. Hope this helps.
Edited to provide additional details.
---------------------------------------
Hey guys, tonight I noticed that the audio on my (stock ROM) Nexus 6 quit working. Sort of.
Bluetooth seems to work fine. Speakers plugged into headphone jack are fine. Regular media (music, navigation, Youtube app, etc.) or regular phone call at my ear, I get no audio.
BUT IF I turn on speakerphone then I have audio. The ringer works normally, the alarm works, the countdown timer alarm works.... basically anything designed to be LOUD works.
Also, strangely, if I'm not on speakerphone then the phone mic doesn't work either, which means no dictating text messages or anything like that.
What gives? My 1 year-old did SPLASH the phone earlier while playing with it near the dog dish, but I thought these things were splashproof. (?) Also, if I killed the mic hardware then I would think it'd be dead all the time, and not work on speakerphone.
Repeated reboots have not helped. The problem persists in safe mode. Did he somehow kill a speaker-mic combo? If so, which part do I need? (I've had this thing open twice before, it's not too bad.)
Thanks!
Weird problem, no "media" related sounds. Alarm, calls, ringtone work perfectly
Hello, for some reason in the last couple of days i can hear no media related sound.
What's weird though is that i can hear normally call sounds, phone ringing and alarm.
The issue started while on the latest version of MIUI. I thought this was related with operating system so I installed Pixel Experience 10 (through complete wipe out, even internal storage). The problem persists there as well.
After looking around, it looks like people had similar issue when the phone mistakenly thought headphones were connected. As it turns out, this is not the case with me. (see 2nd post)
Edit #2:
It looks like it's indeed the "earphone mode" thats causing the problem. Using the aerphone mode off app I managed to get media sound playing again. The problem now is that as soon as i close the app, earphone phone turns back on. Any ideas for permanent fix are welcome.
Thanks
looking around, it looks like the phone might somehow got stuck in like "headphones connected" mode.
I've never connected in the past with any kind of headphones, but i got the charging port changed.
In any case i've tried connecting and disconnecting with Bluetooth headphones but didn't solve the problem.
I will see if i can get my hands on any type-c ones and try again.
Edit: i see there is an option to select the audio output device, and the phone is the only choice, so the headphones mode wasn't the problem