Hello everyone,
I recently obtained an S3 i535. At first, it was working very well. Suddenly the audio became wonky. Now, all audio that emanates from the phone speaker "stutters". This includes ringtones, notifications, music...even the boot audio on startup cuts in and out. Audio through the headphones works perfectly.
I am not completely sure when it started, but it seems that it was right around the time that I rooted.
I HAVE Odin'd back to 4.1.2, with no luck. The stuttering persists.
Also, FYI - at one point, this phone had shattered glass. . I had the glass replaced just before rooting....
Any ideas out there? Thanks in advance...
Mac
ripdoozer said:
Hello everyone,
I recently obtained an S3 i535. At first, it was working very well. Suddenly the audio became wonky. Now, all audio that emanates from the phone speaker "stutters". This includes ringtones, notifications, music...even the boot audio on startup cuts in and out. Audio through the headphones works perfectly.
I am not completely sure when it started, but it seems that it was right around the time that I rooted.
I HAVE Odin'd back to 4.1.2, with no luck. The stuttering persists.
Any ideas out there? Thanks in advance...
Mac
Click to expand...
Click to collapse
Can you provide us a little more detail? Stuff like:
Software:
What ROM are you running?
Are you running any audio mods?
Have you tried re-rooting?
What root method did you use?
Hardware:
Have you recently dropped the phone?
Have you tried to clean the phone's speaker with canned air?
Etc.
Thanks!
Sorry, I left out some info.
Running stock 4.1.2... just flashed back to stock. (problem has ocurred on multiple roms)
First time around used Casual root method.
I have not rerooted.
I have not dropped the phone recently and have not tried to clean the speaker with compressed air.
Thanks for helping.
Sent from my SCH-I535 using xda app-developers app
Kelter said:
Can you provide us a little more detail? Stuff like:
Software:
What ROM are you running?
Are you running any audio mods?
Have you tried re-rooting?
What root method did you use?
Hardware:
Have you recently dropped the phone?
Have you tried to clean the phone's speaker with canned air?
Etc.
Thanks!
Click to expand...
Click to collapse
Also, I just discovered that the sound works MUCH better when the phone is plugged in and charging. Not perfectly...but very nearly perfect.
If I unplug the charging cable. The audio barely works, if at all.
Though maybe this info might help with the mystery...
Thanks again
Mac
ripdoozer said:
Also, I just discovered that the sound works MUCH better when the phone is plugged in and charging. Not perfectly...but very nearly perfect.
If I unplug the charging cable. The audio barely works, if at all.
Though maybe this info might help with the mystery...
Thanks again
Mac
Click to expand...
Click to collapse
SOunds like maybe you broke something internally when you dropped it.
DigitalMD said:
SOunds like maybe you broke something internally when you dropped it.
Click to expand...
Click to collapse
If its charging and sitting on my night stand like it is right now, it works well. If I touch the screen, even without picking it up, it starts to cut out. Do you think it sounds like a hardware problem?
Could installing TWRP have anything to do with it? I installed it right after rooting/unlocking.
I am going to try to flash back to the first 4.1.2 ota. If that doesn't work, I will try to flash to 4.1.1. Personally, i think something got messed up during the root process because it didn't go smoothly the first time....I had to try a second time to get it to work, then the problem started.
Btw, this was my friend's phone. She dropped it, shattered the glass and wanted to get an iPhone. I convinced her to give me the phone, then I had the glass repaired. The speaker was working perfectly until around the time I rooted.
ripdoozer said:
If its charging and sitting on my night stand like it is right now, it works well. If I touch the screen, even without picking it up, it starts to cut out. Do you think it sounds like a hardware problem?
Could installing TWRP have anything to do with it? I installed it right after rooting/unlocking.
I am going to try to flash back to the first 4.1.2 ota. If that doesn't work, I will try to flash to 4.1.1. Personally, i think something got messed up during the root process because it didn't go smoothly the first time....I had to try a second time to get it to work, then the problem started.
Btw, this was my friend's phone. She dropped it, shattered the glass and wanted to get an iPhone. I convinced her to give me the phone, then I had the glass repaired. The speaker was working perfectly until around the time I rooted.
Click to expand...
Click to collapse
Software is never intermittent , hardware is. I suspect you have a lose connector to the speaker inside, I can;t tell you how to fix it, but I'm sure you can find some disassemble instructions that will show you the connectors.
DigitalMD said:
Software is never intermittent , hardware is. I suspect you have a lose connector to the speaker inside, I can;t tell you how to fix it, but I'm sure you can find some disassemble instructions that will show you the connectors.
Click to expand...
Click to collapse
Thanks MD. I pulled the back off the phone and reseated the speaker connection. All is working well...for now at least.
Thanks again.
Mac
And now....the stutter is back....great!
Sent from my SCH-I535 using xda app-developers app
ripdoozer said:
Thanks MD. I pulled the back off the phone and reseated the speaker connection. All is working well...for now at least.
Thanks again.
Mac
Click to expand...
Click to collapse
I have discovered that, after a battery pull, the speaker works much better, then deteriorates over time. I am confused.
Related
Hi there, I'm currently running Darky's Rom 8 on my Samsung Captivate and for some odd reason shortly after installing my accelerometer went dead. I can hear it role around and move when I move my phone but theres no activity with the accelerometer.
I'm not sure If its the ROM or if its my phone.
Any suggestions?
(Sorry if this thread is in the wrong place.)
KyleTroy said:
Hi there, I'm currently running Darky's Rom 8 on my Samsung Captivate and for some odd reason shortly after installing my accelerometer went dead. I can hear it role around and move when I move my phone but theres no activity with the accelerometer.
Click to expand...
Click to collapse
What? You can hear it roll around?
Ya you Should not hear it rolling around
Sent from my SGH-I897 using XDA App
That makes it sound bad. I can hear it (I think its it) with the battery and the back cover off and my ear against the phone.
KyleTroy said:
That makes it sound bad. I can hear it (I think its it) with the battery and the back cover off and my ear against the phone.
Click to expand...
Click to collapse
Flash back to stock and see if that fixes it. If it doesn't, then you have a broken sensor. If it does, then it's a rom issue.
My accelerometer sometimes doesn't respond, when switching screen modes in web browser or similar. Good thing I got insurance for my phone in case I need to get it replaced for any reason.
att8525user said:
My accelerometer sometimes doesn't respond, when switching screen modes in web browser or similar. Good thing I got insurance for my phone in case I need to get it replaced for any reason.
Click to expand...
Click to collapse
If the hardware fails in your phone it is a warranty issue not insurance.
It's just as the title states my nexus s sound isn't working! There isn't any sound at all. Ringtone/notification/media.
When i receive a phone call my phone vibrates but it doesn't ring and when i pick up the phone i can't hear the person i'm speaking to and they can't hear me either.
Had my phone since mid-october,and the first time i encountered this issue is when i put ICS on my phone at the end of december and its been an on and off thing since then but it would last for like 2-3 mins, and it used to be fixed by putting my phone on vibrate, lock it, unlock, turn the volume back up and it would work but that doesn't work anymore i even reverted back to GB and it didn't solve anything
so WHAT CAN I DO TO FIX THIS ? also, do you think it's a hardware or software issue ?
forgot to add whenever i try to use google voice search it crashes
If you plug in headphones, can you hear music? Were you using custom ROM or Stock? Have you tried installing a custom ROM with a complete wipe (factory reset)?
I'd put my money on software. Full wipe (data/factory reset, format /system, format /boot) and then flash your preferred ROM. See if it works after this.
Oogway13 said:
If you plug in headphones, can you hear music? Were you using custom ROM or Stock? Have you tried installing a custom ROM with a complete wipe (factory reset)?
Click to expand...
Click to collapse
Yup, even with headphones there isn't any sound and it first occurred on a custom ICS rom and yesterday I flashed 2 more custom roms with a complete wipe still no progress
Harbb said:
I'd put my money on software. Full wipe (data/factory reset, format /system, format /boot) and then flash your preferred ROM. See if it works after this.
Click to expand...
Click to collapse
just did that and unfortunately it still didn't fix the problem
skillz398 said:
just did that and unfortunately it still didn't fix the problem
Click to expand...
Click to collapse
That's not good
You may be the very unlucky owner of a dead Wolfson chip in the phone. Is the phone still under 1 year old? Might be time to give samsung a ring and hope for the best. If you do decide to take it in, remember to flash a stock ROM and lock the bootloader.
Maybe someone else on the forum has an idea to help you though, but so far i'm afraid chances look slim. You could possibly try heating behind the battery a little with a hairdryer (not too much) and see if it would work afterward, it could just be a dry solder joint on the audio chip, but you'd still want it fixed.
Harbb said:
That's not good
You may be the very unlucky owner of a dead Wolfson chip in the phone. Is the phone still under 1 year old? Might be time to give samsung a ring and hope for the best. If you do decide to take it in, remember to flash a stock ROM and lock the bootloader.
Maybe someone else on the forum has an idea to help you though, but so far i'm afraid chances look slim. You could possibly try heating behind the battery a little with a hairdryer (not too much) and see if it would work afterward, it could just be a dry solder joint on the audio chip, but you'd still want it fixed.
Click to expand...
Click to collapse
*sigh* I feared that its a hardware issue and as far as warranty goes I bought it in 11/2011 and it was bought used so how much would it cost to get that fixed ? Also I restored my phone on a custom 2.3.6 from then rebooted my phone and the sound was working, then after a hour of inactivity, then I rebooted my phone and it started working and got greedy and flashed another rom then the sound was cut off again so should I have hope and try your method of drying ?
I have the same problem. Samsung Infuse 4g. I'm back to stock. Tried everything including GTG and Heimdall. (sigh) Sux. I hope u get urs working again, as I do mine. Saw another post where somebody dropped theirs and it starting working again. Better start praying... Good luck to u!
^^^^^^ i'm about to drop mine for an experiment lol
Hard to say how much. Might be easier to replace the whole board or just one chip, or just because it's too much trouble to find the problem. Also depends on shipping as you'd have to pay to send it to samsung, unless they have some kind of repair centre nearby where you can drop it off - and you'd likely be left without your phone for a couple weeks.
I'd be ringing samsung and asking all of this first. Afterward you may be able to get some quotes from a phone repairer if they can find the problem. These days it's often "throw it away and get a new one", and i'm afraid it's largely the same with phones despite what would be only minor problems/fixes.
OK, y'all. I've got news and info on this issue. First, i have the Samsung Infuse 4g. After trying everything possible short of throwing it into the river, I figured it was def hardware related. I, of course prayed & am convinced that is the real reason it started working, bit jic here is what I did. I checked online just to see (I'm not an idiot, I wasn't going to take it apart. Well, probably not). But I was still all for slapping and twisting and flicking the heck out of it. Then, I decided to look at the other side of it. So I removed the battery and there is a tiny little slit-like hole there. I got out a safety pin and just kinda wiggled of a bit mostly toward the inside of phone. Lo and behold sound was working when I turned it back on. I can't believe it! I'm so happy!
Sent from my SAMSUNG-SGH-I997 using XDA
OK, y'all. I've got news and info on this issue. First, i have the Samsung Infuse 4g. After trying everything possible short of throwing it into the river, I figured it was def hardware related. I, of course prayed & am convinced that is the real reason it started working, bit jic here is what I did. I checked online just to see (I'm not an idiot, I wasn't going to take it apart. Well, probably not). But I was still all for slapping and twisting and flicking the heck out of it. Then, I decided to look at the other side of it. So I removed the battery and there is a tiny little slit-like hole there. I got out a safety pin and just kinda wiggled of a bit mostly toward the inside of phone. Lo and behold sound was working when I turned it back on. I can't believe it! I'm so happy!
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
Glad to hear that
Sent from my Nexus S using Tapatalk
So I rooted my Skyrocket last week and I screwed something up and since than I've had problems with the audio on the phone part. So I'm running Odin and even after double and triple checking I managed to screw it up by not having Auto Reboot checked. In a panic (and after waiting a long time) I unplugged the phone and powered it down. I booted into Recovery and did a wipe and installed CM 10.1.2 and I swear it worked fine for a week but all of a sudden I started having this weird issue with the phone audio. I'll call a number up and I won't be able to hear anything but I can put it on Speaker and it comes through fine or if I use my Bluetooth Headset it works fine.
I reloaded CM 10.1.2 and still nothing. I tried a nightly, I tried 10.1, I tried Beanstalk, and I now I'm back to stock and no luck on the phone audio. I have no idea what to do. I've tried Google searching and I'm coming up with a bunch of things but not what I'm looking for. I've even found some people having similar problems but they got no answer as well and I'm waiting to hear back from them (I found at least three people reporting the problem over on Cyanogenmod's Skyrocket Forum). I found some reference to it possibly being a Kernel problem. Thoughts?? I'll do some reading up on that tonight.
As a last resort I'm looking into buying a used Skyrocket to replace this one because I'm still 6 or 7 months till I'm eligible for an upgrade. HELP!
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Oh and yes I've tried back to stock with no luck.
dfwjose said:
Oh and yes I've tried back to stock with no luck.
Click to expand...
Click to collapse
Seems like you have your answer then. If the problem persists regardless of which ROM or kernel you're using then logically it would seem that it can't really be software related, right?
Brought to you but time and relative dimensions in space.
dfwjose said:
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
Click to expand...
Click to collapse
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
And just like that I'm up and running again and my phone works. I had given up and was having problems with a CM nightly so I did another wipe and loaded a stockish AT&T ROM that I've installed before and no my phone is working fine. I'm going to leave this thing alone until I pick up a spare phone!!
xcrazydx said:
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm sure it is and that's why I took the phone apart to see if I could get to it. I tried all kinds of things to get that tip out before tearing the phone down and I had no luck. I should have taken some pictures but I've tried tweezers (everything I had was to big or to weak to pull it out) and even glue before resorting to taking the phone apart. Unfortunately with the design it's enclosed all the way around with no way to really get to it. I even thought about replacing it but that piece looks to be soldered on.
In the end, I might just send it back to Samsung and see if they will fix it. Not sure if it's worth it but I never got serious about it because I didn't have a spare smart phone other than my work iPhone.
I shouldn't have spoken so soon. Rebooted the phone and it's locking up now. I give up. I can't find anything that will work. I either have sound with a phone that locks up or have to live with Speakerphone/Bluetooth and be able to reboot.
I woke up today to my alarm vibrating and with no sound. I checked volume levels and everything looked good.
I tried to play audio in a few apps and nothing worked.
I rebooted and everything was good.
A little worried I'm going to miss my alarm if this happens intermittently
Sent from my Nexus 5 using Tapatalk
epg0 said:
I woke up today to my alarm vibrating and with no sound. I checked volume levels and everything looked good.
I tried to play audio in a few apps and nothing worked.
I rebooted and everything was good.
A little worried I'm going to miss my alarm if this happens intermittently
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My main loud speaker stopped working yesterday (1 day after receiving the phone) and I just contacted Google for an RMA and replacement. I tried rebooting and toggling settings and even a factory reset but the speaker just does not work at all.
UberGoat said:
My main loud speaker stopped working yesterday (1 day after receiving the phone) and I just contacted Google for an RMA and replacement. I tried rebooting and toggling settings and even a factory reset but the speaker just does not work at all.
Click to expand...
Click to collapse
I don't think my issue is with the speaker, because even the headset speaker doesn't work when the sound cuts out. It seems like it must be a software issue.
UberGoat said:
My main loud speaker stopped working yesterday (1 day after receiving the phone) and I just contacted Google for an RMA and replacement. I tried rebooting and toggling settings and even a factory reset but the speaker just does not work at all.
Click to expand...
Click to collapse
Same exact thing here. Ive tried calling but they want me to put up another $350 until the recieve the defective device which could be a week. So frustrating.
Grims said:
I don't think my issue is with the speaker, because even the headset speaker doesn't work when the sound cuts out. It seems like it must be a software issue.
Click to expand...
Click to collapse
Yeah I have exactly the same issue as you. Was playing music on my phone through headphones. Took headphones out when I arrived at where I was walking. When I put my headphones back in to listen to music again, the screen said it was playing but nothing came out. I took out headphones and didn't get any sound out the speaker. I rebooted and all was fine again.... Is this a software bug or hardware? Should I try get a replacement for my phone?
timfimjim said:
Yeah I have exactly the same issue as you. Was playing music on my phone through headphones. Took headphones out when I arrived at where I was walking. When I put my headphones back in to listen to music again, the screen said it was playing but nothing came out. I took out headphones and didn't get any sound out the speaker. I rebooted and all was fine again.... Is this a software bug or hardware? Should I try get a replacement for my phone?
Click to expand...
Click to collapse
It's possible it's an issue with the headphone jack thinking headphones are plugged in when they're not. I've seen it happen before, and even plugging in headphones didn't resolve it until I cleaned the jack. Haven't seen that issue on a brand new device though.
Google has fantastic support, so I'm going to wait it out as long as possible so if I do have to RMA it I'll have a better chance of getting a later hardware revision.
Is the devices still locked and rooted? My still new from factory. When I do a factory reset sound will work for few seconds and give out. I am going to try to root and unlock load a custom rom and see if that fixes the problem.
Mine is stock, unrooted.
It has to be a software issue because when I reboot the sound works again.
I really do not want to RMA, everything else seems fine.
Just rooted unlocked flashed a custom rom. Still no sound...then just now out of nowhere sound works??
emeniit ealdne
Reporting a similar issue on my end. Doublethinking if I ripped out the headphones too roughly but initially thought my right earbud was busted so a coworker opted to let me use his. It was playing YouTube videos on loudspeaker just fine during lunch. OTW back to the office noticed that sound notifications were buggy. Plugged in coworker's headphones to confirm if mine was busted but experienced same outage. Then both earbuds went silent. Thought I had to clean the jack when I got home but I did a restart and they work fine.
I have the same problem with my N5. When I adjust the volume with the rocker, I no longer hear the sound that lets you know it's being changed. It resolves itself after a few minutes, but it concerns me.
Sent from my Nexus 5 using Tapatalk
I have the same issue. Restarting put it right. Last night I used headphones, and it's possible that this is what causes the sound to stop working, since I can't remember hearing any notifications after that.
epg0 said:
I woke up today to my alarm vibrating and with no sound. I checked volume levels and everything looked good.
I tried to play audio in a few apps and nothing worked.
I rebooted and everything was good.
A little worried I'm going to miss my alarm if this happens intermittently
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
gdarren said:
I have the same issue. Restarting put it right. Last night I used headphones, and it's possible that this is what causes the sound to stop working, since I can't remember hearing any notifications after that.
Click to expand...
Click to collapse
In my case it is the headphones. Everything works fine until the headphones are pulled out. Now sound is not working again, hoping it will fix itself like it did yesterday. 2nd time this has happened. Reboot does not fix my problem. How did yall clean the headphone jack safely?
kp432 said:
In my case it is the headphones. Everything works fine until the headphones are pulled out. Now sound is not working again, hoping it will fix itself like it did yesterday. 2nd time this has happened. Reboot does not fix my problem. How did yall clean the headphone jack safely?
Click to expand...
Click to collapse
I just posted about this issue -- a reboot does fix the issue. I also had it partially working with just the left earbud working. Once again, a reboot fixed.
zmattmanz said:
I just posted about this issue -- a reboot does fix the issue. I also had it partially working with just the left earbud working. Once again, a reboot fixed.
Click to expand...
Click to collapse
Ive rebooted multiple times, wiped re-flashed rom, and nothing. The only reason i unlocked/rooted was hopes that a new Rom would fix. Started acted this way fresh from the box. Thinking of flashing the whole .img?
This problem started for me a few days ago, when I got a call and noticed there was no sound from the speaker. After fiddling with my sound settings and rebooting all was working again for a few hours, then the sound stopped again. I had a colume toggle widget installed which I though may have been causing a prob so uninstalled it. This morning, I had no sound from the speaker again. Did a safe mode boot and still no sound. Fiddled with the volume controls, rebooted a couple of more times and still nothing. I rang Google, and while I was on hold, hit the speaker button and the speaker worked fine in-call. Spoke to a Google device "expert" who had not heard of this prob, and suggested I do a factory restore (the good old "Have you tried turning it off and on again?" fix). Just did a factory restore and the speaker is working fine again. So seems like a software issue, I hope Google addresses this soon.
hi guys,
not sure if this is still actual but same thing happened to my missus tonight. she missed the work today cos of this. there is no sound what so ever. for now I haven't have much time to play with it as she was running late. its the latest device bought just few weeks ago and there is latest update on it. its in factory state, untouched, no root as she doesnt want me to touch her phones (not sure why ??? )
anybody else still having same issues these days? anyone can confirm if it is SW or HW issue?
thx
it seems a software issue though i never faced it try flashing the factory imange after a clean wipe or switch to cm
bhavstech said:
it seems a software issue though i never faced it try flashing the factory imange after a clean wipe or switch to cm
Click to expand...
Click to collapse
phone is in factory condition as I mentioned I haven't touch it as I'm not allowed only thing what was done is the OTA update from new.thats all.
will see tonight when she come back from work. in worst I will RMA what I dont really want to do
rikardo1979 said:
phone is in factory condition as I mentioned I haven't touch it as I'm not allowed only thing what was done is the OTA update from new.thats all.
will see tonight when she come back from work. in worst I will RMA what I dont really want to do
Click to expand...
Click to collapse
If it's completely stock then perform a factory reset from the stock recovery and make sure she hasn't installed any apps that could interfere with sound. Apps like Tasker may be.
- Sent from an IceCold Hammerhead!
Hello!
I've got an strange problem with the audio on my Nexus 5. If I play music without headphones, there's no audio output through the phone speakers. But if I press the Volume-Up-Button the typical sound is played through my phone speakers, and also the ringtone when I'm called is hearable.
If I plug in a headset, every sound is played through the headset, like normally.
I've got the newest CyanogenMod Nightly and I already tried returning to stock, but it doesn't help
It's really frustrating, it suddenly occured, from one day to another.
Looks like my Nexus is always thinking that theres a headset plugged in, even if there isn't. And there's also nothing in the headphone jack.
I've already searched, but hadn't found someone who has a similiar problem, so I thought I ask here, before I contact the Google Support.
Maybe someone of you can help me. Thanks in advance!
Greetings,
Markus
PS: Sorry for my bad english
markus_xx said:
Hello!
I've got an strange problem with the audio on my Nexus 5. If I play music without headphones, there's no audio output through the phone speakers. But if I press the Volume-Up-Button the typical sound is played through my phone speakers, and also the ringtone when I'm called is hearable.
If I plug in a headset, every sound is played through the headset, like normally.
I've got the newest CyanogenMod Nightly and I already tried returning to stock, but it doesn't help
It's really frustrating, it suddenly occured, from one day to another.
Looks like my Nexus is always thinking that theres a headset plugged in, even if there isn't. And there's also nothing in the headphone jack.
I've already searched, but hadn't found someone who has a similiar problem, so I thought I ask here, before I contact the Google Support.
Maybe someone of you can help me. Thanks in advance!
Greetings,
Markus
PS: Sorry for my bad english
Click to expand...
Click to collapse
Have you looked at the media volume level in settings/sounds/volumes? Just to rule it out.
Couple of things.
The phone could think that the headphones are still plugged in. Try plugging it in and pulling out a couple times.
It could be RMA time if you go back to completely stock and this still happens.
gee2012 said:
Have you looked at the media volume level in settings/sounds/volumes? Just to rule it out.
Click to expand...
Click to collapse
of course I already did that
mistahseller said:
Couple of things.
The phone could think that the headphones are still plugged in. Try plugging it in and pulling out a couple times.
It could be RMA time if you go back to completely stock and this still happens.
Click to expand...
Click to collapse
I got that problem since more than a week already and I still use my phone, so I plugged it in and out almost permanently, but thanks.
And yeah, looks like it's RMA time, unfortunately.
markus_xx said:
of course I already did that
Click to expand...
Click to collapse
Then you can do a data factory reset or reflash the factory image and if that doesn`t help yo might contact Google for a RMA (as allready stated above by another user).
gee2012 said:
Then you can do a data factory reset or reflash the factory image and if that doesn`t help yo might contact Google for a RMA (as allready stated above by another user).
Click to expand...
Click to collapse
already did a factory reset and flashed the factory image, like mentioned in my first post.
Hey, OP, did you find a solution to this? My phone just started doing this today as well, and I'd prefer to avoid RMA if possible.
Well, I found out the phone had been dropped in some semi-liquid food. So I opened up the back cover a bit, found some remains and cleaned it up and now it works fine again. Woot! Not sure if that is relevant to anyone else though (or if it really made a difference or was just a coincidence), lol.
In my case, it wasn't something like that. I just contacted Google for a RMA and got a new device very fast.
Some liquid inside the phone
Hey there!
This afternoon my Nexus 5 started to have the same problem you have related. I remove the back cover and I discover that it was full of liquid against the surface. I was running with the phone in my pocket (condensed sweat), so I recommend not to do that.
I have dried it and it seems that doesn't work yet =(
I hope my answer will help anyone with the same problem (at least to know a possible source of the problem).