Picked up the Evo car kit today and the sound output going to my car stereo through the 3.5mm jack is noticably lower when the phone is connected to the car kit vs. without the car kit. Wondering if there is something wrong or if this is by design, and if there is a way to change it. Thanks.
That's by design ... They intentionally locked the output volume to 75% when it's in the car kit. They were wanting to protect people from blowing out their speakers or some BS like that. I went through all this when I got my car kit for Christmas and have been sending hate filled, profanity laced emails to Sprint ever since.
There was a thing going around the interwebs after those kits got released that explained how to crack them open and cut a ground wire that made the phone register it being in the kit. That fixed the problem by essentially keeping the phone from realizing it was in the kit. As a side effect, it caused it to not automatically start the car dock app though, but who really uses that? You could still manually start it and it charged just fine.
Alternatively, have you upgraded to Gingerbread 2.3.3 yet? I might have gotten hit in the head yesterday and don't remember it, but it seems like since I installed the 2.3.3 update it doesn't do that anymore. I'm wondering if Sprint finally disabled that stupid "feature."
I actually just came to the forums to see if anyone else had noticed it.
Newest Gingerbread update does not fix it. Not sure if having root will though, as my phone isn't (currently) rooted...I ran the OTA with S-ON before realizing I'd lose it. While I'm not opposed to running stock and modifying the dock, if root solves it (when I can eventually root again), I will wait. The output is just a bit too low even with my stereo cranked...in a Wrangler no less. So when the top is down, forget it.
nerrollus said:
There was a thing going around the interwebs after those kits got released that explained how to crack them open and cut a ground wire that made the phone register it being in the kit. That fixed the problem by essentially keeping the phone from realizing it was in the kit. As a side effect, it caused it to not automatically start the car dock app though, but who really uses that? You could still manually start it and it charged just fine.
Click to expand...
Click to collapse
Scoured the internet looking for the physical modification instructions, but haven't found anything relating to it whatsoever. Do you remember where you saw it, or do you have a link?
http://androidforums.com/evo-4g-accessories/149183-evo-car-dock-now-available-7.html
That's the closest I could come. Thee used to be a picture of a guy doing it. He basically used a razor the cut the connection to pin 4 so the phone didn't know it was docked but still charged. This was like 6 or 7 months ago so I don't remember exactly where I saw it.
If I find it I'll post a link. Fyi if your rooted you can also replace the file that does this and fix it. that had been posted on these forums before.
Found a temporary workaround. Downloaded "Equalizer" from the app market, and bumped all the settings to max to pump more sound out of the jack. I suppose that will work for now until the devs have cracked the new hboot and I can root again. Don't feel confident enough to rip the new car kit apart just yet, though it may fix the USB/AC charging issue as well if I unground the pin...as the car charger I have connected shows as AC out of the box.
phishstics said:
Found a temporary workaround. Downloaded "Equalizer" from the app market, and bumped all the settings to max to pump more sound out of the jack. I suppose that will work for now until the devs have cracked the new hboot and I can root again. Don't feel confident enough to rip the new car kit apart just yet, though it may fix the USB/AC charging issue as well if I unground the pin...as the car charger I have connected shows as AC out of the box.
Click to expand...
Click to collapse
I'm a little dumbfounded as to what happened with my phone and why it doesn't lower the volume when I stick it in the car kit anymore.
There were several podcasts that I just could not hear on full blast when I stuck them in the kit, but now they're blasting so loud I actually have to turn my stereo down.
don't know if it works on unrooted phones but dsp manager also has some features that most the volume or at least clears up some sound.
i say this because my stock stereo sounds like ass without a few tweaks that dsp manger has but just a suggestion
Related
Meritline is carrying the original desktop dock for all Galaxy S models:
http://www.meritline.com/samsung-galaxy-s-desktop-dock-cradle-captivate-i897-at-t---p-60544.aspx
$26.99 + Free Shipping
Good find, thanks for posting!
I read some bad reviews about it, I guess the usb port is for charging only, not computer connectivity. Can someone confirm that?
That is correct, I havent been able to do any development while using the dock. Also, I havent been able to get the Audio Out to cooperate. Looks nice though.
Apparently the audio-out won't work until 2.2 is released. Don't understand why the computer connectivity won't work though. I have two of these things. Works fine as a charging only station next to the bed.
MSHampton said:
Apparently the audio-out won't work until 2.2 is released. Don't understand why the computer connectivity won't work though. I have two of these things. Works fine as a charging only station next to the bed.
Click to expand...
Click to collapse
I tried the audio out on an old 2.2 Cognition build before; it works. But yeah, I really don't get why this doesn't connect to the computer.
I just got mine, so I thought I'd do an impromptu unboxing.
One thing I noticed is that desk home FC's on Cognition 2.3b6 when I try to change the weather settings, so I likely won't be using that too often. I haven't looked for other desk-friendly software, so I might just use this as a place to keep my phone while I work.
Despite having 2.2, the speaker jack out the back does not seem to work for me. That, combined with the fact that the dock itself covers the speaker port, unless I find a way around that, I will not be able to use it as an alarm clock dock. It doesn't fit as tightly into the dock as I hoped it would, but part of that is the phone's design, I'm sure.
For the past 2 days, no matter what ROM I flash, car dock comes on at every reboot. I've never used the car dock app, so I'm at a loss as to why it starts up every time I reboot my phone. I exit out of car dock, and it doesn't start back up until the next time I reboot.
Also, every time a call comes in, or if I make a call, speaker phone is always on by default. Again, this happens on every ROM I flash, and it's only been happening the past 2 days.
I'm rooted, currently using Warm Z, with netarchy 4.3.2 cfs more havs.
I should also mention that I've tried multiple kernels with the hopes that maybe that would solve the issue, but sadly it hasn't. Any help would be appreciated.
Well I have no idea why or how, but both issues have solved themselves. Nothing was installed or uninstalled, and my phone is back to normal.
Anyone have any ideas at all?
Sent from my PC36100 using XDA App
I'm having the exact same problems with my G2. If the Evo and G2 are anything like many of the other phones out there, they use a magnet to switch into car mode.
My problems started when I first started using a belt pouch with a magnetic closure - before I knew about the magnet/car mode thing.
Has your phone been exposed to a magnet for any period of time?
My phone is doing the same thing! Did you find any solution?
On my G2 I did a SuperWipe and then installed a new ROM and the problem was solved.
I believe that the car dock mode is regulated by the pin out of the power cable. Recall it being that two of the ground wires are attached in the car dock and not in regular power cable mode.
Also in car dock application, you can go into the menu option and turn it off so that the car dock application isn't the default action when it senses that connection.
I actually own the car dock, but hate the application since I usually only dock the phone when in GPS mode.
Having the same problem.
Sent from my PC36100 using XDA App
I've had the same problem for a month now anybody find a solution really annoying at this point.
I had Car Dock starting for no reason on my phone. What I was found was that launching Car Dock was done so by certain pins in the Micro USB port on the phone. What was happening to me was that the Micro USB plug on my charger was messed up in a way that made the phone think it was plugged into the dock instead of just a regular charger. I bought a new charger on Ebay for like $3 and never had the problem again.
I've read that some people have Car Dock launch without their phone being plugged in. Almost all of them noticed that they had some sort of tiny debris within the usb port that was crossing the pins and causing the app to launch. Cleaning out the port with something like a toothpick should help eliminate that possibility.
Hope this helps.
Yes I read that as well, and tried cleaning the port with a soft tooth brush and compressed air and didn't help. the most annoying part is the load speaker is the default for incoming/outgoing calls and the media volume is stuck on full, much to load for headphones. More than likely the pins are touching and so small that I can't see them much less straiten them out. Trying to find someone who can solder a new port, so if anybody has sent there evo to have the port fix with good results I would appreciate a good recommendation.
thank
Two point five questions here I guess but I've tried everything and I don't know what else to do. Rooted phone, got it back in july not long after the launch. For the last week or two, maybe more, I was using MIUI with tiamat 0.7. Most recent version of both. For a while Car Home kept popping up always and being super freaking annoying. Eventually I had to freeze it with Titanium backup.
Another very bothering thing is that the audio output for media is incredibly loud. Like if I plug in some five dollar headphones and keep media on lowest, I can hear it about ten feet from the buds. Not even cupping to bounce sound, just sitting on a surface. I don't know what caused this but it may have been fault, I'm not sure if doing what I did, did this; I had a pair of broken headphones so I whittled and scraped them down just to the plain bare jack and use it as a soundkiller while I'm at work. I've done this before with no problem but this time I scraped down so some metal is exposed while the jack is in and I'm sure I touched it when I removed it. I did this for a few days and suspected it might be the issue causing the sound so I stopped.
I also wiped very thoroughly the phone and SD card and went to the latest nightly of CM7. Same issues, including car home so I'm not sure what the hell is wrong with that damn app. Also now my phone is ALWAYS rotating anything even when I tell it not to and keeps making itself silent as far as ringing and notes go. What can I do?
Tl;DR: Car home always popping up, Media sound is incredibly loud, CM7 is ALWAYS rotating.
I realized this was due to a loose connector in the headphone or usb port and the phone always thinks it is in a car docked or does whenever this is loose. I found an app called NoDock in the market, it requires root but it works on the OS level disabling the feature all the time when I want to meaning I can still use it. There is a trial that claims to work for 7 days however I've been using it for the day after I posted this until now. Another person posted in the market a bad review because his trial lasted only 30 minutes so it is a formula or something. Normally it is 3 USD so it isn't too bad.
The choices I had were using this with this app or getting a replacement through sprint officially as a damaged hardware. The replacement would be a brand new model that couldn't be rooted as of yet so I figured I'll deal with this. The evo is over a year old now and I can't be sure people will keep trying to do new things to root it so I'll keep my beloved.
I'm posting this so in case someone has the same issue and searches 3 years from now and sees this they will know what i did.
Car home is caused by pins getting crossed within the USB jack. Check for a few things:
1. Does it happen only when the phone is plugged in?
2. Is there any debris or the like inside of the USB jack that is crossing the pins?
3. Does the same thing happen when you plug another USB cable into it?
Mine did the same thing and it turned out to that my charger was screwed up and making the phone think that it was docked. So I bought a samsung charger off of Ebay for like $3 and it's worked flawlessly ever since. If there is junk inside of the phone's jack get a toothpick, or something similar, to clean it out and see if that helps. If the jack is clean and the phone still launches car home while NOT plugged in then your USB jack may be screwed up.
Not sure if it had anything to do with the update, but I have been power cycling my phone a lot lately...
Headphones: My headphones don't seem to be registering that they're in, so the sound comes through the speakers--but the headphones work when plugged into other devices. (I have picked up a pair of bluetooth headphones until I figure it out, which work fine.) After power cycling the headphones work again for a while somehow, but will randomly stop again, so it must be a software issue. It could have to do with being unplugged while audio is going?? Not sure
In-call: I can't hear the other person, but they can hear me. If I switch to speaker phone, I can hear them (not sure if they can hear me while on speakers, they usually hang up by the time I realize they are really there but I can't hear them...) It's so weird. I have to say, "I can't hear you, I'll reset my phone and call you back in a minute".
Anybody else with this problem???
I've been struggling with the same problem on 3 different Fire Phones. All phones are running Fire OS 4.6.3. I discovered this problem after plugging into my car stereo via the 1/8" audio jack. If not immediately, shortly after disconnecting the cable I would be unable to hear the party on the other end during a phone calls, though they could hear me. I also found that the jack would no longer switch from Speaker to Wired audio and vice versa when I plugged a cable into and out of the 1/8" audio jack.
It looks to be an OS issue as the problem is remedied by a restart. I am really curious if I happened to get 3 lemons or if anyone else experiences this. If this is an issue with Fire OS, have so few people used the audio jack? I am tempted to install Cyanogenmod to see if this remedies the problem, though I would expect this sort of issue to occur with Cyanogenmod as opposed to the stock FireOS install.
Thanks for letting me know there is someone else out there with the same issue. I hate thinking I'm the only one!
BTW alexandergrig did you get a warranty replacement for them or you just bought 3 when they were on sale or something?? I am thinking of trying to replace it on warranty, since the issue is new-- it just started a couple of weeks ago, and I didn't experience the headphone/call "mute" issue throughout most of the life of the phone. The other thing that I don't get is why it won't let me take a video--it stops after 1 second (also a recent issue).
The phones were not on warranty replacement but rather purchased new. How long had you been using your phone without issue? What version of FireOS are you currently on? Have you side loaded Google Play?
Today, for example, I had no issue with plugging headphones in and removing them. I later plugged the phone to my car stereo via mini-jack and had no issues playing music or placing and receiving calls (using the speakerphone) while it was plugged in. When I unplugged it, I was able to make calls. Later when I plugged the phone into my car stereo again, I had the same problem. Basically all the audio was being routed to the speaker and not the audio jack. No matter how many times I plugged and unplugged the cable, no audio was being sent through the audio jack.
I also happened to try the Soundabout app on the Google Play store, thinking that perhaps the audio was not being routed properly. Unfortunately, when I forced the output to the "wired" audio jack, at best I would hear some popping noises. All this gets resolved with a restart, however inconvenient that may be.
I find it hard to believe that the 3 phones I have worked on all happen to be lemons, though I guess it's possible. I wish I could get some feedback from others to determine if they are having any such issues. Like I said before, this is something that you might expect from a custom ROM not a stock OS install. I'm not sure how much of a pain making an Amazon warranty claim would be. If you opt for this, I would appreciate it if you could let me know how this goes and if the replacement unit works properly. Part of me wonders if a Cyanogenmod install would remedy this issue. If not, then it's got to be something more complicated beyond my ability to troubleshoot. I am very tempted to try.
I got the phone in February, and it has worked fine until about two weeks ago. My headphones (the ones that come with the phone) started malfunctioning, and there was an OTA update around that time, so I am suspecting it could have been either thing. I side loaded Google's apps during my first week with the phone, and my current OS is 4.6.3 (463001620) [but I don't know why is says "Installed Tuesday, February 18, 2014" since it has definitely been updated since then...]
I'lll let you know how the warranty stuff goes. Maybe they'll give me a replacement that works...
All 3 phones were on 4.6.3 while having this problem. They had immediately been updated to 4.6.3 after purchase. I did test this prior to installing all the Google Play services, but there was no difference. I have not tested this on any other version of FireOS.
Today I made a point to test this more thoroughly. Phone works properly while connected to car stereo via audio jack. I can call out via Speakerphone without issue. However 5 times today when I disconnected the mini jack from the phone, I could no longer router audio through the jack when plugged in again and I experienced the issue where I could not hear the person on the other end of the call but they could hear me.
Plugging in headphones also would not work. This evening, I tested it with a pair of stock apple iPhone earbuds and it has not been behaving in the manner described above. I listened to music for 15-20 minutes, unplugged it and then I'm able to hear the music through the phone's speaker. After plugging it in again, the audio is properly routed to the headphones again. I was able to do this about 10 times without issue. Then at some point the same issue occurred.
I'd like to say that it's an issue with 4.6.3 or perhaps some sort of service that is not handling the audio routing properly and needs to be restarted via a reboot. I kind of wish that I would have tested this issue on another version of FireOS. Despite everyone's disdain with FireOS and my own past inclination to play around with stuff, I really wanted to stick with the stock FireOS, but this lack of proper functionality is bothering me so much I might be inclined to try CM11.
I don't know if this will help you but there's an app called SoundAbout that will force audio through the headphone interface whether the phone thinks a headphone is plugged in or not. You'd have to get a copy of the apk and sideload it on fireOS though. https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix
I had SoundAbout installed a few days ago but that didn't seem to solve the problem. When I force switched it to the audio jack, I got nothing or some pops. It just seems something gets corrupted or quirky until one restarts the device.
danielnealclark, today I was trying to shoot some video with the Fire phone and ran into the same problem that you had by the way. I'll start another thread on this issue to see if anyone else has experienced this.
I only add this because it's getting to the point where I am very tempted to install CM11. If the sound issue persists (though I'm sure other issues might crop up then, lack of mute during a call being one as I understand it...) then I'll have to give up and come to the conclusion that it is some intermittent hardware issue on some of these units.
Let me know how CyanogenMod works if you try it. It prob has it's own issues too. I am going to try to get a new phone through the limited 1 year warranty. I'll keep you posted about the process
Got a replacement phone, and it worked fine until today...
I thought that a certain pair of headphones were the culprit, and I never should have plugged them in to my replacement phone (they are official amazon fire phone headphones BTW). This pair of headphones went bad and were only working in one ear when in the fire phone (but they work fine in both ears on my computer, which I don't understand) and it was around the same time my last phone had the headphone issue described at the beginning of the thread, so I thought the issues may be related. I tried them today, and oops, they messed up another phone!
From the other posts on this thread, there is an issue with certain headphone jacks--not sure why. But if a certain headphone jack gets plugged in, the phone will forever think (until power cycling) that there are headphones in during a call, and never think headphones are if you try to plug in headphones for music/games.
I guess I still have it under warranty since it is a replacement through Amazon. I'm gonna try to do some resets, troubleshooting, etc...
So pissed right now
I've been having this issue as well. It is very annoying!
I have the same problem, as I previously posted. Unfortunately nothing I did remedied the problem nor was I able to find out any more information.
Daniel, did you end up getting Amazon to replace your phone previously, as you had mentioned?
I honestly think that this is not a problem particular to only a few models. I don't feel that a replacement would help because sooner or later it arises again it seems. It could very well be a jack problem, but I really feel this is some low level quirky OS issue. Originally I had mentioned that I might switch to CM. I've decided that this would lead to additional quirks going this route, so I will continue to keep my phone stock. The true test is if someone with CM experiences this issue or if switching to CM remedied the problem. Unfortunately, I've had so many frustrations with technology as of late and so little time, I don't have it in me to fiddle around anymore. I'm not sure if we can expect Amazon updates to remedy this, and all we can do is hope some day we get an update.
My main problem was that I use my Fire phone to connect to my stereo via Aux input. So I was constantly having issues. I ended up simply purchasing a USB bluetooth adapter for my car stereo and going wireless with the Fire phone and it's worked well. I must admit my Fire phone is not my go to phone for listening to music with headphones because of this, but I always found that the Amazon earbuds were less likely to cause this problem than other ear buds in my case.
After a long listening session, the only thing that helped me was simply rebooting the phone. A really crappy solution, but definitely more productive for me than continuing to tinker with this issue for me. Or going bluetooth. For those experiencing this issue, please keep us updated if you find a long lasting solution or if you have experienced any remedy with CM. Or, if our farfetched dream of an Amazon update were to become a reality...
All the best in the New Year folks!
danielnealclark said:
I thought that a certain pair of headphones were the culprit, and I never should have plugged them in to my replacement phone (they are official amazon fire phone headphones BTW). This pair of headphones went bad and were only working in one ear when in the fire phone (but they work fine in both ears on my computer, which I don't understand) and it was around the same time my last phone had the headphone issue described at the beginning of the thread, so I thought the issues may be related. I tried them today, and oops, they messed up another phone!
From the other posts on this thread, there is an issue with certain headphone jacks--not sure why. But if a certain headphone jack gets plugged in, the phone will forever think (until power cycling) that there are headphones in during a call, and never think headphones are if you try to plug in headphones for music/games.
I guess I still have it under warranty since it is a replacement through Amazon. I'm gonna try to do some resets, troubleshooting, etc...
So pissed right now
Click to expand...
Click to collapse
alexandergrig said:
For those experiencing this issue, please keep us updated if you find a long lasting solution or if you have experienced any remedy with CM.
Click to expand...
Click to collapse
I second that post! If anyone solves this one, let us know.
alexandergrig: I did get them to send me a new phone, since it was under the 1 year warranty. The phone call took about 45 minutes, with me trying to convince them by plugging in headphones/unplugging headphones to show that it was really broken. Before that call, though, they told me the first thing I had to do was perform a factory reset before they would even consider progressing to a replacement. [BTW the Fire phone has a great native backup tool if you are just migrating from one fire phone to another, it's all cloud based]. The new phone was a refurb.
I think I'll try the bluetooth thing for my car, that's a great idea. I really like my bluetooth headphones for work (as a bonus I found out they connect to my computer super easy too--at the same time as my phone even--so I can run desktop-only music sites)
Curious if anyone was able to fix this. I had this occur on my original Fire Phone. Amazon replaced it in Nov 2015 and my new one just started doing this....
jagernbeer said:
Curious if anyone was able to fix this. I had this occur on my original Fire Phone. Amazon replaced it in Nov 2015 and my new one just started doing this....
Click to expand...
Click to collapse
Good luck. I also am on my 2nd Fire, and like you have the same problem back again. The funny thing is, it was caused by the stock headphones, other headphones gave me no problems. So what did I do? I gave up! And now I LOVE LOVE LOVE my bluetooth headphones. They are so easy to use and no more cords. Try it out, you'll never go back (until the batteries die... but they charge pretty quick)
Good luck to you.
I experienced this problem on 3 separate Fire Phones. So either I am very unlucky or this problem is more widespread than we know. Because of this, I doubted that a replacement would help me. I will say that I have used my one 64gig Fire Phone without this problem being an issue for months and so I came to my own conclusion which might not end up being very helpful but...
I was able to experience this constantly when I made it a point to plug and unplug the headphones for testing purposes (both stock Amazon as well as the older Apple earbuds). Ultimately, the way I ended up using my phone's audio output was by streaming audio via bluetooth to a USB bluetooth adapter connected to my car stereo almost daily. Also most every day I would usually go from the Bluetooth audio in the car, to plugging in my headphones for my 3 mile walks, and then unplugging the headphones and reconnecting via Bluetooth in the car to drive home. Doing this for the past many months, I did not encounter one issue with placing calls via the phone itself, speakerphone or even via the mic on the earbuds.
Because of this I am concluding (as I initially believed) that it might not be hardware but rather the Fire phone's low level OS/system software that governs the audio jack that happens to be buggy. It's like there is an issue with the jack status detection routine and it gets "stuck" in one mode. I may be wrong, but there is a good possibility that Fire phone users that do not experience this problem, very well might start if they constantly plugged and unplugged their headphones from the jack, attempting to place and/or receive calls in between. At some point this issue might arise. But in my experience it goes away and corrects itself until the next time, unless anyone else has experienced otherwise.
Due to the lack of significant continued development of the Fire Phone, Amazon will likely not address this problem via an update. My sense is that if not everyone is experiencing it because it is a software issue, then it's prevalence is due to usage patterns. I, like others, in the beginning found this to be a constant problem the more I tested it, especially with plugging and unplugging the headphones and making calls. With my 3 phones, I have a hard time believing it's actual hardware only because it eventually seems to resolve if I change my usage patterns.
Might be totally different for you guys, but I guess this is my final conclusion. I sold one of my 32gig Fire Phones and still plan on using the 64gig, despite picking up a couple of other phones.
A.G.
I tried plugging in an aux cable last night, and I couldn't get it to go all the way in. If I pushed it hard enough, the sound would come through the speakers but as soon as I let go, it disconnected. I tried a few different pairs, and it seems there's something preventing the 3.5 mm jack from being inserted all the way. I tried it with and without my Rugged Armor case, too. Anyone else have this issue? Might have to take it in, but with the Pixel XL being in short supply I really don't want to go without a phone
Just rma it
I gave it quite a bit of pressure. I didn't wanna break it, lol. I shouldn't have to push it in that hard though, just wondering if this was a universal issue or is it an isolated incident
ChrisAC84 said:
I gave it quite a bit of pressure. I didn't wanna break it, lol. I shouldn't have to push it in that hard though, just wondering if this was a universal issue or is it an isolated incident
Click to expand...
Click to collapse
Hi Chris,
It appears I am having the same, or nearly identical issue. I tried using my aux cord, as I normally do nearly every day, on Wednesday and it wasn't connecting properly, giving some weird feedback through the output (or no output at home) and thought it was an issue with the aux to cassette (very possible with the high use and mechanical failures).
At home I tried with headphones, and I could not get a full connection. The device stopped playback of the music as it always does when it detects some input, but there was no output, and at times google now would be activated or the volume down would be activated, but this headphone had no control on it whatsoever, so some sort of short/feedback was emulating a volume control.
Talking with project fi now about my options...still haven't sold my 6p yet so I could still use as a backup, but what a hassle...
I've never had this problem before. Could it be lint? I can't look inside and tell, and I don't have tweezers small enough to reach in.
PapaGUnit said:
Hi Chris,
It appears I am having the same, or nearly identical issue. I tried using my aux cord, as I normally do nearly every day, on Wednesday and it wasn't connecting properly, giving some weird feedback through the output (or no output at home) and thought it was an issue with the aux to cassette (very possible with the high use and mechanical failures).
At home I tried with headphones, and I could not get a full connection. The device stopped playback of the music as it always does when it detects some input, but there was no output, and at times google now would be activated or the volume down would be activated, but this headphone had no control on it whatsoever, so some sort of short/feedback was emulating a volume control.
Talking with project fi now about my options...still haven't sold my 6p yet so I could still use as a backup, but what a hassle...
I've never had this problem before. Could it be lint? I can't look inside and tell, and I don't have tweezers small enough to reach in.
Click to expand...
Click to collapse
If you take it into a bestbuy and go to the Samsung reps they'll take a look at it for you and tell you if there is lint or not and get it out for you I know that they're Samsung reps but they help with any Android device lol
Veid71 said:
If you take it into a bestbuy and go to the Samsung reps they'll take a look at it for you and tell you if there is lint or not and get it out for you I know that they're Samsung reps but they help with any Android device lol
Click to expand...
Click to collapse
No need, went to one of the phone service kiosks in the mall and they used tweezers to pull out a sh-t load of lint. Looked like a magic trick, neither of us could believe it.
Take a toothpick and press towards the bottom, if it's spongy, it's probably lint. Use a bright light to look inside.
A good sucking of the head jack should clear up any clogs..
I actually had the same problem (Pixel XL and I could not plug in my headphone jack all the way). I received the XL on 10/20, but had yet to use my headphones until this past weekend. It seems like this might be a common problem because when I called the Google Pixel Support, they immediately transferred me to Project Fi support and the girl I was speaking with immediately began the process of sending me a new phone (this was on Sunday 11/28). I received the new phone today (11/30) and everything works fine with the new phone and headphone jack.
I have this issue with the Google Pixel. I just got the device yesterday and when plugging it into aux cord in vehicle the sound was distorted. I tried the next time I got into car and it doesn't go in all the way. I went home and tried multiple pairs of headphones and they don't fit into headphone jack 100%. It goes in most of the way but stops at the top and doesn't hold in place. I called Google support and am waiting on a callback.
I had the exact same issue. A bit of canned air worked for me!