Related
When in a phone call the other persons voice comes out of the speaker on the back of the phone, not the ear speaker like it should. Speaker phone works fine. I've tried everything. Flashed multiple different roms, switched recoveries and kernals. Anyone have an ideas? could this be hardware related?
I've seen this happen on a desire, but a full wipe (w/no settings restored from TB) fixed it.
Yeah I've every wipe possible, several times. still did not do anything.
I'm having the same problem, did you ever find a solution? The phone is currently running the most recent Cyanogen 7.
no still no solution. I've posted multiple threads on different sites. I feel like I've tried absolutely everything.
Sounds like it may be a hardware issue?
yeah it seems that way. I just dont want to believe it because that would mean I was ripped off by swappa.com/the seller because they claimed everything was working perfectly.
mitchstehlin said:
yeah it seems that way. I just dont want to believe it because that would mean I was ripped off by swappa.com/the seller because they claimed everything was working perfectly.
Click to expand...
Click to collapse
has the phone done this the entire duration that you've owned it? or did it work normal, then start doing this randomly? to me it seems like a software issue that a full wipe would solve if possible. if that dont work then yes maybe a hardware issue, though its hard to imagine how that could be possible.
I believe it has been like this since I had it. I had to root it when I got it and I think I noticed it the first call I made. but it may not have been like this although I don't see how anything I did could have caused it. I have done everything possible. every wipe imaginable. various roms, kernels, and recoveries. Even went back to stock unrooted. and the OTA gingerbread update. nothing works.
So you did a fastboot wipe?
I stand corrected. I have not done a fastboot wipe. how do you do one?
I have not because it was a MAJOR pain in the butt to do it on my G1 with a Mac. Seems like the last resort though.
oh I see. well its makes no difference to me. ill try anything. do you know of any good guides? I'm using a PC
I did a quick search but didn't find anything good, when I have more time I'll find something and share it if you haven't already.
This might be helpful...
http://theonda.org/articles/2010/03...-performance-boost-and-some-serious-geek-cred
that had nothing about a fastboot wipe in it however I did find something. I'll let you know how it goes.
I wiped it with Flashboot but it didn't help.
yeah same here. this is extremely irritating. what is htc's policy on it? like the warranty specifics.
Not sure, they just told me to call 1-888-716-3593
oh I see. let me know what they say. cyanogen tweeted that he sent in his unlocked n1 and they replaced it because of a bad power button. so I'd imagine we have hope?
So, I'm at my wit's end. I've had multiple chats with highly belligerent Google staffers who, because they don't recognise an error, refuse to help. They also won't let me return my 6P and I'm pretty close to desperation.
Essentially, my 6P just won't play podcasts without the audio continually dropping out (it goes silent, but playback continues). To get audio back, I need to unplug / replug my headphones multiple times, pause / play multiple times / sometimes restart entirely. There's a subtle click whenever this happens. This occurs with podcasts downloaded via PocketCasts and DoggCatcher and books via Audible. It happens regardless of which player I use - even if I sideload the files into Google Play Music.
It doesn't seem to happen with music files but, come on, an mp3's an mp3. My suspicion is that it's happening with long files. Maybe I should try some opera.
Google essentially say that files like podcasts and sources like the BBC aren't supported. It's CRAZY for a flagship like this. They insist the phone is fine without taking a physical look at it. They flat-out refuse to let me exchange it.
So what the hell do I do? Podcasts are, by a large margin, the thing I spend most time using my phone for. Without that very basic functionality, the 6P is next to useless for me.
Do I have to take legal action?
Legal action? I bet your success rate would be close to 0% on that.
Factory reset or reflash the stock images.
Sent from my Nexus 6P using Tapatalk
I guess it may come to that?! I'm just dumbfounded by their response, which amounts to "you're using it wrong". It's not remotely what I've come to expect from Google and the overall tone is simply hostile and callous. I'm really shocked by it, to tell you the truth.
SilkyJohnson said:
Legal action? I bet your success rate would be close to 0% on that.
Factory reset or reflash the stock images.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I troubleshoot software and hardware for a living. You've got to look at it from their perspective:
*no known issues other than yours (my guess - have to check bug tracker
*inability to replicate
*isolated issue
*not HW related
*not SW related (see bulletpoint one)
It's not that they DON'T want to help you, it's just based on the information provided and lack of other users having the same problem, they have nothing to resolve your issue with. Now if other users start reporting the same thing? Software issue that will get flagged on a bug tracker and possibly added as a bug fix in a future update.
Sent from my Nexus 6P using Tapatalk
Oh, god, I completely understand. But surely, in the interim, they should offer to RMA the device rather than simply saying: "Meh, your problem"? I mean, they're famous for being great to deal with - why this sudden lack of concern?
Inability to replicate surely means getting the questionable device in hand and testing. It's not enough to say that other devices work fine so mine should work fine too.
SilkyJohnson said:
I troubleshoot software and hardware for a living. You've got to look at it from their perspective:
*no known issues other than yours (my guess - have to check bug tracker
*inability to replicate
*isolated issue
*not HW related
*not SW related (see bulletpoint one)
It's not that they DON'T want to help you, it's just based on the information provided and lack of other users having the same problem, they have nothing to resolve your issue with. Now if other users start reporting the same thing? Software issue that will get flagged on a bug tracker and possibly added as a bug fix in a future update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Which app are you using to play podcasts?
Have you tried another? I use Pocketcasts every day and have no problems whatsoever.
EDIT: Have you also tried a different pair of headphones? Not all headphones work well with the 6P.
Put this thing on reddit and hope for a ****storm.
It sounds to me like what you're experiencing is a compatibility issue, not a phone issue. I don't see how/why they'd replace a handset in that situation.
nobnut said:
Which app are you using to play podcasts?
Have you tried another? I use Pocketcasts every day and have no problems whatsoever.
EDIT: Have you also tried a different pair of headphones? Not all headphones work well with the 6P.
Click to expand...
Click to collapse
PocketCasts primarily (which is why I'm sure it's a fault with my hardware - because people like your good self are fine!), but also DoggCatcher. I've also sideloaded the files into Play Music and the problem persists. It also happens with Audible. And, yep, I've tried several pairs of headphones. SIGH.
Heisenberg said:
It sounds to me like what you're experiencing is a compatibility issue, not a phone issue. I don't see how/why they'd replace a handset in that situation.
Click to expand...
Click to collapse
You mean that podcasts aren't compatible with the 6P? I don't follow. I'm using apps like PocketCasts, DoggCatcher and Audible - nothing odd! The problem also occurs when I sideload the files into Play Music.
Corndude said:
Put this thing on reddit and hope for a ****storm.
Click to expand...
Click to collapse
I guess I'm going to have to. I'm just dumbfounded that, being unable to help, they're not prepared to swap it out for another device - ESPECIALLY considering the absurd RMAs that people were submitting a few weeks ago. I saw one guy say he was on his 5th unit. I mean, come on...
Snarklife said:
I'm just dumbfounded that... they're not prepared to swap it out for another device - ESPECIALLY considering the absurd RMAs that people were submitting a few weeks ago. I saw one guy say he was on his 5th unit. I mean, come on...
Click to expand...
Click to collapse
Bingo! I see this every year with Nexus. Not to say it doesn't happen with other phones, but Nexus seems to attract more AR, paranoid users than any other. I'm not surprised they're trying to minimize exchanges in some cases.
If you haven't done an FDR, I would suggest that you do, and restore nothing. Install Pocketcasts and see if the issue persists.
Or.... Tell them there is a slight bulge over the volume rocker and they will exchange it. It's a "known issue" I was told by Google this very thing. And was told I could exchange if I wanted.
I had a similar thing happen on my @voice reader app and was able to correct it by setting the "between paragraph" delay to 0 ms from the standard 300 ms. Something about the way Marshmallow handled that slight break in audio focus caused it drop from bluetooth and speaker playback. I don't know if your podcast apps have the ability to speed up playback, but it might be worth a shot.
I had the same issue with pocketcasts. The only fix was a reboot. I haven't tried to listen to them on 6.0.1 yet. But I've only had that issue twice. Reboot helped.
rp1226 said:
I had the same issue with pocketcasts. The only fix was a reboot. I haven't tried to listen to them on 6.0.1 yet. But I've only had that issue twice. Reboot helped.
Click to expand...
Click to collapse
Yeah, it's pretty constant for me. I'm trying yet another pod catcher to see if that helps. I'll report back if it does. But I'm SURE it's nothing to do with the apps. Like I say, even if I sideload the files into Google Play Music, the problem persists.
Anyone know whether a bulge at the bottom is RMA-able even after the 14 days (I was one of the meh-okay-nothing's-perfect people)? I guess I could say it's developed recently??
I have a similar issue listening to Tune In radio whether live, or a recorded show. I have chalked it up to my headphones cause they're pretty Sh!tty and on their last leg. Audio keeps counting down but no sound. Unplug, replug, hit play and I am on my way again.
Are you sure it is not the headphones, have you tried with a bluetooth speaker or headset?
It will work. The bulge thing. I have screen shots of the conversation with Google telling me it's nothing to worry about and if it got worse it would be covered and I would get a new device. Can't post pics yet, my account won't let me.
Yep, definitely not the headphones. I've tried three pairs now. Thanks, though!
MoreGone said:
I have a similar issue listening to Tune In radio whether live, or a recorded show. I have chalked it up to my headphones cause they're pretty Sh!tty and on their last leg. Audio keeps counting down but no sound. Unplug, replug, hit play and I am on my way again.
Are you sure it is not the headphones, have you tried with a bluetooth speaker or headset?
Click to expand...
Click to collapse
This is really weird, I use doggcatcher, pocket casts, black player, and Poweramp and they all didn't have this issue. I listen to podcasts almost daily usually on pocket casts.
Is there one particular podcast I can try that you see there issue with our is it pretty much any one you try?,
Sent from a 128th Legion Stormtrooper 6P
So, i was having some issues with the earphone i had bought recently, but having a few problems with the same brand sometimes earlier (microsoft really put up a really interesting choice with the low price and really good bass and sound quality for its pricing, but damn, those things had caused me two replacements in earlier models) i was considering taking it to the warranty and getting a new one, fine.
Then i got the moto earphone (had never used it, was in that plastic thingy yet) to get me through the day and i put the ms one in the bag, but when i started walking, the same problems appeared. The volume would get lower, sound getting distorted, and the song started to cut to the point it would recognize as if the headphone has been unplugged and i have to start the music again. i'm no expert but i think we've got some issues here son
I went to master google in search for answers and i've found that people have been having these kinds of issues since the first generation moto g, some even got a replacement and the jack would still come faulty, there were a major "consent" that the fault was the pocket lint inside, and cleaning it would solve the problem, but my phone doesn't have even two goddamn weeks, it didn't even had time to get dirty. (and i tried it cleaning, only a lil hair came out) I am currently listening to music, and it's perfect, when the phone stays still. If i start moving it around or mess with the connector, the issues come back again.
Does someone had this problem here too? found some solution besides the pocket lint thing? i didn't found any post here on xda related to that, and i really don't wanna send it ro warranty 'cause i need it really bad for my work, and i know it's gonna take some time in there, the problem can even come back...
Please, show me a light.
I have a problem where moving the headphone jack a small amount would stop music playback its so annoying. I mostly use Bluetooth headphones though.
george241312 said:
I have a problem where moving the headphone jack a small amount would stop music playback its so annoying. I mostly use Bluetooth headphones though.
Click to expand...
Click to collapse
Moving it also distorts the sound to the point it stops. Normally this happens with detective earphones, but the jack is new to me.
I'm sure it's the jack, I just got new headphones too. What you can do is expand that contact strip in the jack inward, hence better contact? I haven't done this yet though
bestofrhcp said:
I'm sure it's the jack, I just got new headphones too. What you can do is expand that contact strip in the jack inward, hence better contact? I haven't done this yet though
Click to expand...
Click to collapse
yea, it is the jack indeed... are you facing this problem too?
i tried pulling it out a bit, but no results. Some random "solutions in the internet tell to put something behing that first metal contact strip... it that so?
So I kinda solved the problem these days... I bought a tpu case, and it has stopped. I guess that the phone is too slim, and it keeps banging in the pocket, making the jack loose and stopping the song. Now the phone is kinda bulky, fits right in the pocket, I can even run with it and the sound is still perfect. Sad that I gotta use this case, makes the phone Hella ugly, but yeah, I solved the problem
If anyone is facing it, try this, might work for you too.
Fixed my problem
I'd just like to add that I also suffered from this same issue (to the letter, volume decrease, distortion and all). It happened once a few weeks in but now, a few months later, it was happening so often that I had to give up using headphones.
Well, here's the thing: I contact Motorola and they give me the old crap about rebooting in safe mode and testing, or doing a factory reset.
As I KNOW this is a hardware issue, I just go ahead and reinstall the factory image (I was previously rooted) planning to send it in for repair/replacement: low and behold: it's fixed. So installing the original firmware and going through the setup (but choosing not to reinstall all my apps -new device option) fixed the problem. I have no idea how this can be. Maybe an app made the phone react too much to slight disturbances in the connection? When I have time, I'll be restoring my backup to see if the problem comes back, and uninstall apps one by one (starting with the xposed modules and other root apps).
I've been using the headphones a lot in the past 5 days with absolutely no issues.
tl:dr OP's exact problem, what seemed like a hardware fault, was fixed by a factory reset.
bv90andy said:
I'd just like to add that I also suffered from this same issue (to the letter, volume decrease, distortion and all). It happened once a few weeks in but now, a few months later, it was happening so often that I had to give up using headphones.
Well, here's the thing: I contact Motorola and they give me the old crap about rebooting in safe mode and testing, or doing a factory reset.
As I KNOW this is a hardware issue, I just go ahead and reinstall the factory image (I was previously rooted) planning to send it in for repair/replacement: low and behold: it's fixed. So installing the original firmware and going through the setup (but choosing not to reinstall all my apps -new device option) fixed the problem. I have no idea how this can be. Maybe an app made the phone react too much to slight disturbances in the connection? When I have time, I'll be restoring my backup to see if the problem comes back, and uninstall apps one by one (starting with the xposed modules and other root apps).
I've been using the headphones a lot in the past 5 days with absolutely no issues.
tl:dr OP's exact problem, what seemed like a hardware fault, was fixed by a factory reset.
Click to expand...
Click to collapse
Now that was unexpected lol. Anyways, thanks for the reply, i've seen much of this kinds of problems on the internet, but none of it came to a conclusion, the posts die after sometime. I hope someone finds the answer in your reply.
So, i bricked my phone sometime ago and installed the factory image. i've been using the tpu case since it came, as i stated before, it has solved my problems (i think mainly because the phone get bulkier, fits into the jeans pocket and stop moving, so the jack isn't affected by any kind of movement and it works perfectly), but after you said that i recalled, there was one day when i forgot the case at home, and unaware of that i went working with the headphone and it worked perfectly, i just noticed i had forgot the case in my way home. I'll do some further testing without the case, but your solution might just have hit the right spot.
guile50 said:
Now that was unexpected lol. Anyways, thanks for the reply, i've seen much of this kinds of problems on the internet, but none of it came to a conclusion, the posts die after sometime. I hope someone finds the answer in your reply.
So, i bricked my phone sometime ago and installed the factory image. i've been using the tpu case since it came, as i stated before, it has solved my problems (i think mainly because the phone get bulkier, fits into the jeans pocket and stop moving, so the jack isn't affected by any kind of movement and it works perfectly), but after you said that i recalled, there was one day when i forgot the case at home, and unaware of that i went working with the headphone and it worked perfectly, i just noticed i had forgot the case in my way home. I'll do some further testing without the case, but your solution might just have hit the right spot.
Click to expand...
Click to collapse
Did you, by any chance, have GravityBox installed on your phone when it was playing up? Also/or, where you using an unmodified ROM, as that's what I'm using usually (deodexed but stock) I've just restored my backup (that's rooted and has a few xposed modules on) and sure enough first time I touch the jack with music playing, it plays up (this time it triggered the voice command, which it did do some times). So I think to start by disabling GravityBox as that modifies a lot of stuff... Reboot, and the damn thing seems to work perfectly, I'm tugging and pulling at the jack right now and it's working perfectly.
I find it a bit too much to believe, and I don't want to lose GravityBox as that's a big reason I root.
One explanation I can come up with is that Motorola saw there was a problem and they fixed it in software, and installing AOSP or GravityBox that changes system files, gets rid of that software "fix".
bv90andy said:
Did you, by any chance, have GravityBox installed on your phone when it was playing up? Also/or, where you using an unmodified ROM, as that's what I'm using usually (deodexed but stock) I've just restored my backup (that's rooted and has a few xposed modules on) and sure enough first time I touch the jack with music playing, it plays up (this time it triggered the voice command, which it did do some times). So I think to start by disabling GravityBox as that modifies a lot of stuff... Reboot, and the damn thing seems to work perfectly, I'm tugging and pulling at the jack right now and it's working perfectly.
I find it a bit too much to believe, and I don't want to lose GravityBox as that's a big reason I root.
One explanation I can come up with is that Motorola saw there was a problem and they fixed it in software, and installing AOSP or GravityBox that changes system files, gets rid of that software "fix".
Click to expand...
Click to collapse
Well, try to trigger the problem a couple of times with gravity box installed. I don't have it, installed xposed once and had major lag, stuttering and FC problems, then i took the ting off. Didn't test the jack thing, but i've never been a hard xposed user.
I really think my problem is hardware-related, but tonight i'll head home without the case and report back here.
If I am on a stock Moto ROM, I have the problem. When I moved to AOSP/CM based ROM's, I can manipulate my headphones without causing it to stop.. I think maybe the stock kernel is a bit too sensitive and stops it with just a little bit of disconnection vs a more lax implementation in AOSP/CM...
So I've ran my tests: climbed stairs, climbed down stairs, run a Lil bit, shake my hips (they don't lie) and messed around my pocket: no sign of Jack problems. I guess that flashing stock firmware again did the job, as you have stated earlier. I'm going to stop using the case and go jogging, or going more often to work listening to music without it, but after today field tests, I'm sure the issue is gone.
guile50 said:
Well, try to trigger the problem a couple of times with gravity box installed. I don't have it, installed xposed once and had major lag, stuttering and FC problems, then i took the ting off. Didn't test the jack thing, but i've never been a hard xposed user.
I really think my problem is hardware-related, but tonight i'll head home without the case and report back here.
Click to expand...
Click to collapse
Just an update: I give up. I've tried multiple things, including almost bricking my device. I cannot find something definite at all. Installing a clean factory image (or a rom that has not been changed much) will get rid of the problem, even with root. However after restoring my TitaniumBackup of about 140 apps, the problem came back for a while. I noticed it after enabling MotoVoice, so I disabled moto voice and it disappeared, but then re-enabling moto voice didn't make the problem come back... And that is why I give up. I've ordered a pair of Bluetooth headphones.
I think that flashing the stock firmware again is the ultimate solution to solve the problem. After some tests I really couldn't trigger it again, so I guess that's the end of it
The problem is that the issue is so random I can't seem to find a proper way to trigger or to say it is 100% solved. I've read about it happening since the first generation moto g, seems like a hardware issue, but...
My headphone jack wont work properly when i insert the headphones into the jack completely but it works fine when i pull out a lil of the pin of headphones out of the headphone jack whats the deal its too annoying
Moto x 2013 verizon
Bought this brand new sealed and opened it up and updated to current.
Problem,
Microphone works great on the phone but won’t work anywhere else.
Ok google won’t voice match to open, voice memos, gboard, video call apps, etc.
Anyone else had this issue and fixed it?
First thing I'd do is check the app's permissions that they are allowed to use the mic
I did that
swedyk said:
I did that
Click to expand...
Click to collapse
did it work before you updated it?
Does it work with headset etc?
I'd try going to reset all apps, as a first try.
Last resort, reflash.
IronRoo said:
did it work before you updated it?
Does it work with headset etc?
I'd try going to reset all apps, as a first try.
Last resort, reflash.
Click to expand...
Click to collapse
When you plug in a headset with a mic it works fine.
Don’t know about working first because updates were right away as I knew the phone at start was not a good experience until all the updates made it great.
swedyk said:
Bought this brand new sealed and opened it up and updated to current.
Problem,
Microphone works great on the phone but won’t work anywhere else.
Ok google won’t voice match to open, voice memos, gboard, video call apps, etc.
Anyone else had this issue and fixed it?
Click to expand...
Click to collapse
I think you/we are suffering from an software issue. The PH-1 and other devices like the OP6 have the problem that thirdparty apps are using the wrong microphone, even the camera app. For me this is causing very low volume in recorded videos and anreliable "OK google" trickering the assistant. I don't use whatsapp or snapchat, so can't say anything about it.
https://www.androidpolice.com/2019/...-mic-in-some-apps-like-snapchat-and-whatsapp/
Hopefully it will be fixed later once. Fingers crossed :silly:
swedyk said:
When you plug in a headset with a mic it works fine.
Don’t know about working first because updates were right away as I knew the phone at start was not a good experience until all the updates made it great.
Click to expand...
Click to collapse
LOL, yes suppose most of us would immediately update phone is s oon as we got it also
yes, I'd think it's software issue, I've also heard of similar problems on other phones & oK goggle also causing mic issue, that's very I suggested using the reset all app option. Maybe also try boot into safe mode to see if it's a 3rd party app causing this.
I have a OnePlus 6T with Oxygen OS 9.0.11, no root.
The phone worked perfectly until yesterday, when I was having a call and suddenly I began hearing a very unpleasant noise coming from the top speaker. Even after the call ended, I could still hear it and even at this time I do it too. It is not by any means loud, I can only hear it when my ear is really close to the speaker, typically when I would place my phone on my ear to take a call. The problem is that it is always there in the background. I must also mention that the phone didn't suffer any physical damage.
The sound itself is not a continuous beep. It interrupts at some times and it sounds like radio interferences or static, but of high pitch. Coil whine is similar to this noise too.
Now, I have tried rebooting the phone and turning wi-fi and mobile data on and off. As soon as the phone powers off, the noise disappears. But immediately after I start it, the sound begins as well, so I thought it may be a hardware issue. But then I played with the camera. When inside the camera app, if I switch to the front camera and place my ear next to the speaker: magic! The noise seems to disappear. If I exit the camera app, however, it returns.
I've already spoken with those at OP support, and after recommending a factory reset they suggested I should send it for inspection. The problem is that I need the device and can't have it away from me for a week.
What do you think? Have you ever heard of issues like this one? Should I downgrade the software to an earlier version?
I have the same problem , and a lot of users of 6t have this problem, i decided not to send it to service center and I stopped paying attention to it
lwajer said:
I have the same problem , and a lot of users of 6t have this problem, i decided not to send it to service center and I stopped paying attention to it
Click to expand...
Click to collapse
How long have you been noticing it for? Did you also encounter it on earlier versions of the OS?
I don't have any issues with the earpiece. You might try to reboot your phone into the stock recovery and clean the system catch that might help!
Caltinpla said:
I don't have any issues with the earpiece. You might try to reboot your phone into the stock recovery and clean the system catch that might help!
Click to expand...
Click to collapse
Tried that already... no effect . Now I've just factory reset the phone and the buzz is still there. Nothing seems to work, I guess I'll just have to get used to it.
unowen1 said:
How long have you been noticing it for? Did you also encounter it on earlier versions of the OS?
Click to expand...
Click to collapse
Since i bought the phone. I wrote about it with support of oneplus and even with the bug department but nothing in the system did not find, I was instructed to send a phone to the service but not somehow very irritating because you can not hear it when you do not have a phone very close to your ear.
unowen1 said:
Tried that already... no effect . Now I've just factory reset the phone and the buzz is still there. Nothing seems to work, I guess I'll just have to get used to it.
Click to expand...
Click to collapse
It appears you have a hardware related defect phone so upgrade or downgrade your OS won't help!
Had a similar issue with a Samsung phone once. Hardware fault; warranty service was the only solution.
Caltinpla said:
It appears you have a hardware related defect phone so upgrade or downgrade your OS won't help!
Click to expand...
Click to collapse
Yes, that's what I'm thinking too... Though, I don't get why it started doing it so randomly. I've used the phone just fine for one and a half months and it worked perfectly. Now, after no damage whatsoever, this noise appears... strange.
Is the problem solved? I've the same issue with my OnePlus 5T.
OP5T_25 said:
Is the problem solved? I've the same issue with my OnePlus 5T.
Click to expand...
Click to collapse
No, the problem is still there. However, I can still only hear it when the camera is not active. While in the camera app the noise disappears.