Related
Hey all.
Been having problems with a Nexus One that crashes at seemingly random times.
I have been unable to pin it on anything, and am asking your help.
It appears to be independent of the Rom installed, whether there is an SD card present, or whether its connected to a USB cable or phone charger.
Any help would be greatly appreciated.
Phone Info:
Nexus One (AT&T model)
Radio: 4.06.00.12_7
Current Rom: Enomther's TheOfficial Nexus1 - v2.12.2
Provider: Rogers (BC, Canada)
Logcat output attached as screen capture image.
This has been reported by a few users. I sent mine in for repair and got it back not repaired - they couldn't replicate the problem.
My case has been escalated which means a HTC guy called and asked me a few questions and then told me to wait for an email (a few days ago).
I believe my problem started when I seriously overheated it ... driving with navigation on, 3g downloading maps and traffic data, car charger plugged in all on a very hot day on a very hot dashboard. This was the first reboot and they got more and more often after that. Now I can't run anything for more than 5 minutes if 3G or wireless is on (in 'Airplane' mode I can run for quite a while without a reboot).
mine was doing the same thing.
getting progressively worse until the phone was basically unusable earlier this week.
I was running CM6 at first when it started happening.
installed the newest nightly and it worked better for a bit then got even worse.
uninstalled the stand alone version of gmail from the market and it worked for a couple hours and then kept rebooting on me.
finally i did a factory data/cache wipe and installed a rooted stock rom and things have been working PERFECT for over half a week.
I had the same issue. first reboot happen when i had nav running plunged in then after a few months utube , browser etc would restart my phone. it didn't matter which rom i used or stock. I sent it in and they fixed it. i had issues with htc but it got fixed.
Yup, same here, strange thing is it isn't a complete reboot. Hard to explain but what happens is i'll touch the phone and then it will immediatly go to the CM6 boot logo, then immediatly to the lock screen, (which I have disabled) then to my normal desktop. Total time elapsed maybe 5/6 seconds, wierd.
A normal reboot usually takes about say a minute or so. just started happening 3/4 days ago, and happens maybe twice a day at most, some days not at all. Probably wait until Cyanogen includes 2.2.1 into 6.0.0 stable then reflash.
Ive been having the same problem for about a week now, but I'm still using stock, not rooted. Its weird, because its a really fast reboot. It goes to the Booting X, for about 6 seconds, then it boot up just fine. I cant understand it.
this really sucks
I am keeping my ATT nexus one around for gingerbread but these random reboots are really killing me....I use the phone for five minutes and it just reboots by itself....The phone runs really well for those five minutes...Ive done five factory resets but it is still just doing these phantom reboots.... Anybody find out anything more about this...or know a fix....the phone is not rooted and it is clean stock froyo...so please help or keep talking about it so htc will address this issue lol which i doubt since this phone is starting to become ancient....(cant wait till nexus S) =P
With regards to the original problem posted, I believe I've managed to diagnose it correctly.
The problem lies with faulty heat distribution. The phone would crash and reboot more often in times of great stress:
charging the phone (heats up the battery)
running many applications at once (heavy system load)
navigation (heavy dataand gps traffic, image processing)
This coupled with the fact that changing the OS did nothing to remedy the problem solidified the notion that the problem was hardware based.
Given this, I contacted HTC Nexus One support and had the phone repaired.
Note: HTC will honor the warranty and fix hardware issues for an unlocked Nexus One. With software issues, you're on your own (for obvious reasons).
This is exactly what my phone is off to warranty for. I experienced this with every rom tried. I wipe my phone completely and put stock froyo on only to see the exact same behaviour...so at least I'm not crazy
The tech told me it was a hardware problem so that is a bit of a mind ease.
It seems Nexus One and Desire are really similar: HTC Desire rebooting on its own.
P.S. It's a problem with faulty motherboard, if you're within warranty, it should be replaced.
I also have been pleasantly experiencing this issue with the nexus one, so i sent it for repair at HTC and they have said it is an issue with the motherboard and it has been replaced, it is now in the post so I will update this post when I receive it to whether the problem is resolved. Hope so was driving me crazy!
The log did not capture the error. In most cases its a software issue, not hardware. (has happened to me too, not recently though)
Well an update as promised.
I received my N1 back after UPS had finished not dispatching it due to "Adverse weather conditions" and the issue is GONE!!! I know a week isn't really a long time to trial the device but this was happening several times a day.
HTC replaced the motherboard.
My advice to anyone having this problem, is to send it to HTC for repair (dont be worried about it being rooted/custom ROM etc mine was and because its a known hardware issue they really aren't bothered about it.)
It took two trips to HTC for them to finally address the issue. They did fix something (they didn't say what) and the problem is gone.
I believe it was the motherboard because Swype Beta decided that it was a new phone and not the one I registered (so it would not install).
Earlier, my G2 shut off on me about 5 times. -_-
First, I had it sitting in the car ,tried to take a pic but the stupid voice recognition menu kept coming up so I gave up and set it down in the console. When I got home, the phone felt warm and was.. off.
Then, I turned it on.. stuffed it in my pocket. A moment later, I pulled it out and YET AGAIN when I pushed the button I was greeted by a quick vibe and the HTC screen -_-
Then a few minutes later I ran a speed test (checking HSPA+ out in Vegas).. put it down on the table.. come back.. PHONE IS *(@#% DEAD AGAIN.
I HATE YOU! *glares at phone*
It's killing me because it either happens several times in a row, or doesn't happen for days! I've tried replacing the sim card, replacing the SD card.. moving the battery... no dice.
Maybe it's my SIM card? Would that cause it? My last phone did that -_- And I'm silly to have not yet changed the SIM lol
Good thing I have a spare sitting in my bag.
What battery are you using? Aftermarket? Is so, did you remove the sticker around the battery? If you did then make sure you place a piece of tape on the battery to avoid making contact with the metal sd card holder. The metal on metal causes it to shut down.
Sent from my HTC Vision using XDA App
Interesting. I've also been having random shutdowns (not reboots, which I've seen mentioned elsewhere, due to a hardware fault) --
HTC Desire Z, using default battery, but I'll try isolating it anyway with a slip of paper or something.
OP you on a custom rom with overclock? maybe your clocking your phone too high or low?
Also if the phone for whatever reason gets too hot or cold it will turn itself off.
Please see this forum: Phone powers down and won't turn back on w/o pulling the battery
I strongly believe that this may be an issue with the GPS and/or Google Maps. Once I have the GPS off, this has not occurred. Can anyone else try this?
I have the Bell Desire Z NAM with stock HTC Sense 2.2 ROM.
It seems to be quite prevalent, see the bottom of this review: T-Mobile G2 is speedy sequel to original Android
I think you may be onto something with that GPS note, but my phone doesnt' need the battery pulled to restart.
Also, it's running the stock firmware, stock battery (just exchanged battery and got a new SIM card yesterday, and it shut off again today.. so those aren't the problem)... so any issues I'm having are 100% stock related...
This time it shut off after using Maps so....
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
fablife said:
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
Click to expand...
Click to collapse
This was true before we received the first OTA update. Since then though the problem has been fixed.
I think it was definitely the GPS, that said I just got done with a really long phone call about this and have a replacement on the way.. but that was way too much effort AND I have to pay shipping (it's not much, but seriously.) I'm not happy that T-Mobile was THAT big a pain in the butt about getting the phone replaced with a new one in the 30 day return period.
Going by the pointers one of my close friends on sprint (that used to be on AT&T) gave me, I'd say this could've been worse with another provider.. but it shouldn't have been. The reception isn't the best so the customer service should make up for that, and it sorta does.. but it sorta doesn't.
Oh well.
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
djrajir said:
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
Click to expand...
Click to collapse
My Desire Z had the same problem and I returned it to HTC Service for repair. They said they change some cables? and a new battery. It has been nearly 3 days and I haven't experienced a single shutdown but there was one time it restarted by itself.
Yeah my only problem with that is, I am close to my upgrade date. How much did it cost. I may still do it so I can give this phone to my kid brother.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Just to update, I found that I can make it do it some times when playing with opening the hinge.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Possible cause/fix found
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Talked to tmobile CS today and was trying to get a replacement because my phone would randomly reboot and shut off. All he told me was go and pick up a new sim card. If that didn't help then they would be willing to give me a warranty replacement.
Sent from my T-Mobile G2 using XDA App
carquote said:
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobi.../513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Click to expand...
Click to collapse
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Is this possible fix something else than lining the back of the battery with a strip of paper?
whpsnp said:
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Click to expand...
Click to collapse
Sorry about that, I fixed the link and it should be working now.
Cool, thanks!
Sent from my HTC Vision using XDA App
I'm pretty sure mine is not caused by the metal strip since my battery's all proofed. I didn't have anything wrong with it until about half a month ago, and it always happened after using GPS and left it on. If I turn it off after navigation or any other app that requires GPS the phone won't go into SOD.
I switched back to CM7 RC2 around that time and starting to get the GPS no fix problem, and it could't be fixed by the dd=/dev/.... script. So I switched into Nightly 88 or something that at least I was able to get a fix but the not-so-random freezing started.
This morning I flashed the new 7.1.0 RC1 and the phone would just turn itself off (it used to just freeze and become hot), and I got really tired of it... My old G1 was much more reliable than this.
I tried the dd=/dev script again, so far after 5 min the phone is still on with GPS on....
@carcuote
Thank you! I haven't had this issue for months now. But the solution is so easy to do that I will try our anyways.
I had this issue the first month our so when I got the new phone, but went away permanently after the second month. Maybe the contacts in the battery got a little rusted? Don't know but the solution is simple enough to try...
Sent from my T-Mobile G2
My phone keeps deciding to go into car mode of its own accord!
This is both on MIUI and LeeDrOiD.
The phone also automatically goes into speaker phone mode whenever I make or receive a call.
Is there any way to disable car mode, or is there a hardware problem with my phone?
Cheers
I'm having the same problem, if you go into setting, car dock, you can uncheck "auto launch car dock" or something similar. It will stop it from entering car mode, but it will still default the speaker to on.
Delivered mine back at the shop today, they hadn't seen it before, but guessed it was a HW problem.
Just changed to AlienMinds CM7 and the problem has disappeared. Hopefully if I go back to sense it will stay fixed!
Sent from my Desire HD using XDA App
Mine does the samething doesnt matter what rom i use...sense, cm7 based they do the same thing. I know im in the wrong phone section since i have a g2(vision). But it was the only thread that had to do with my problem. Plz and thanks in advance.
Sent from my HTC Vision using XDA Premium App
There is no setting to turn off automatic car dock launch
Sent from my HTC Vision using XDA Premium App
Yeah it reared its ugly head after a reboot. I'm guessing it's a hardware problem
Sent from my Desire HD using XDA App
I don't what happen but it went away for me but I thinks it hardware related also.
Sent from my HTC Vision using XDA Premium App
I'm not too sure about why it keeps shifting to Car Mode, but as far as the activation of the speaker every time you get a call, all I can say is that, that's what it supposed to do anyway when in Car Mode.
If, for any reason, you had that problem even when your DHD was not in car mode, my guess would be that there's something up with either your gyroscope or with your proximity sensor.
I killed Car Mode and got away with it
Car Mode would pop up constantly on my HTC Incredible 2. It had nothing to do with the usb. Most times, the phone wasn't even plugged it and Car Mode would still pop up and Yes, I could click on it and disable it. For about 5 secs, then it was back. The worst part was that it would force-close the program that I was in to launch. It took me about 8 hours of research. Car Mode is a system app, and therefore can not be removed like other applications. You have to root your phone then delete, freeze or rename. Ok by me, but rooting apparently isn't stable yet for the Incredible 2 if you have a later os version than 2.2. Guess what? I have 2.3. No problem, how do i revert. Oh, i find out, you can't without resetting the phone to factory, which by the way is what verizon support suggested. I thought not before I back up, but lo and behold you can't back up more than contacts and pics without rooting. Arrrrgh! Next, I looked for an app to help me battle this devil Car Mode, so I tried apps from Amazon and market:
Advanced task killer Free
Astro
Gemini App Manager
Dock Nothingness
Dock no-op
Disable car home
and NONE of them worked, at least not for the Incredible 2.
I had a new idea, if you can't beat them, join them so I installed the latest version of Car Dock Home, hoping that at least it would give the option to not launch. Nope, didn't work. Luckily, I'm good at my job just because I don't give me 'easily'. Anyway, finally on my 14th try, I used 'DockNothing Free' from Amazon. At first, I didn't think this worked either. There was no input screen or settings but that's because the app doesn't initiate until the Car Mode launches, then it allows you to choose to select DockNothing as the default program. I had to do that 3 times: 1) Car Panel 2)Car Dock 3)Home Dock. Now I actually see a little popup that says 3 tasks killed. YEA!
Sorry for the long post, but I'll bet if you're here, you are going crazy because of Car Mode. And I read a lot more than just this much to get mine fixed.
ps. Car Mode actually looks pretty neat and seems useful IN THE CAR. But I have been too afraid to release the monster to check it out. I might at the next update. Might....
Well, got mine back.. they had only done a factory reset and an update, and now the problem is gone. So I guess atleast for my case it was software related..
The funny thing is, I did a factory reset, and had the latest update before I delivered mine for service.
have the same issue with my dhd.
in many geman forums you find the hint that is has something to do with a broken micro-usb and the dhd can't reognize if its plugged in to a dock, or not.
If i plug in a sumple usb-charging-cable neither the car dock starts nor the loudspeaker would turn up.
i took a good look on my micro usb slot and couln't find anything strange.
Anyway, i cleaned it up very well and removed any little fuzz i found.
But i still have this issue.
has anyone an idea how the dhd recognizes if its plugged to an dock or an charging cable???
thats seems to be the key to the Problem
Possible soultion
forum.xda-developers.com/showthread.php?t=1197735&highlight=screen
Sent from my Inspire 4G using XDA Premium App
maybe a possible solution, but as you mentioned i'm afraid to make it even worst.
so, as long as i have guarantee on it i think i bring it to a dealer to send it back to HTC, maybe i'll get a brand new phone, though it ****s me up to have it wiped after that.
aureldoku said:
maybe a possible solution, but as you mentioned i'm afraid to make it even worst.
so, as long as i have guarantee on it i think i bring it to a dealer to send it back to HTC, maybe i'll get a brand new phone, though it ****s me up to have it wiped after that.
Click to expand...
Click to collapse
Good luck!
Sent from my Inspire 4G using XDA Premium App
The strangest thing just happened to me. While I was charging my OPT it failed to register my fingerprint. Upon asking me for my pin, the touchscreen acted very erratic, and after 5 seconds stopped working completely. The moment I disconnect the charge cable everything works fine!
If my calc or any other app is open it also registers a lot of touches without touching the screen. It's nothing you can replicate. Kinda spooky actually lol.
I've tried a couple of things already, rebooted, killed most apps, checked the charge cable (original) and port but to no avail.
I have the US version and am on the latest stock ota, but rooted. I'm about to do a restore and after that clean install if necessary. I just wanna check if anyone experienced this before.
I will lost back if I get to the bottom of this. Hopefully it's not the hardware.
xzces said:
The strangest thing just happened to me. While I was charging my OPT it failed to register my fingerprint. Upon asking me for my pin, the touchscreen acted very erratic, and after 5 seconds stopped working completely. The moment I disconnect the charge cable everything works fine!
If my calc or any other app is open it also registers a lot of touches without touching the screen. It's nothing you can replicate. Kinda spooky actually lol.
I've tried a couple of things already, rebooted, killed most apps, checked the charge cable (original) and port but to no avail.
I have the US version and am on the latest stock ota, but rooted. I'm about to do a restore and after that clean install if necessary. I just wanna check if anyone experienced this before.
I will lost back if I get to the bottom of this. Hopefully it's not the hardware.
Click to expand...
Click to collapse
Does not happen so often on my OP2 but it happened a lot on my Nexus 4. This is a known issue with many devices but nothing you should worry about.
burnoutslo said:
Does not happen so often on my OP2 but it happened a lot on my Nexus 4. This is a known issue with many devices but nothing you should worry about.
Click to expand...
Click to collapse
Thats not great news burnoutslo! It's pretty annoying that you can't use your phone while charging. I've noticed that once it reaches 100% everything's ok again so it definitely seems software related, probably android if other devices have the same problems. I will do a nand restore back to the previous oxygen version over the weekend. Hopefully it solves my problems.
xzces said:
Thats not great news burnoutslo! It's pretty annoying that you can't use your phone while charging. I've noticed that once it reaches 100% everything's ok again so it definitely seems software related, probably android if other devices have the same problems. I will do a nand restore back to the previous oxygen version over the weekend. Hopefully it solves my problems.
Click to expand...
Click to collapse
I observed same thing yesterday,
The whole scenario was-
Yesterday when my battery gone below 15% i ran for the charger and plugged in and after that i started using phone and i noticed that my touchscreen becomes less responsive.
Difficulty in swiping between home screen, opening of apps during swiping.
So the solution i found that if i stand on the ground barefooted then only i am having this problem, when i put slippers on then its perfectly fine.
So may be it is some kind of grounding issue.
same here; issues sometimes when charging; I didn't see the differences between sleeper and barefoot but I also think it's a ground problem...
afarnedi said:
same here; issues sometimes when charging; I didn't see the differences between sleeper and barefoot but I also think it's a ground problem...
Click to expand...
Click to collapse
sushant6786 said:
I observed same thing yesterday,
The whole scenario was-
Yesterday when my battery gone below 15% i ran for the charger and plugged in and after that i started using phone and i noticed that my touchscreen becomes less responsive.
Difficulty in swiping between home screen, opening of apps during swiping.
So the solution i found that if i stand on the ground barefooted then only i am having this problem, when i put slippers on then its perfectly fine.
So may be it is some kind of grounding issue.
Click to expand...
Click to collapse
xzces said:
The strangest thing just happened to me. While I was charging my OPT it failed to register my fingerprint. Upon asking me for my pin, the touchscreen acted very erratic, and after 5 seconds stopped working completely. The moment I disconnect the charge cable everything works fine!
If my calc or any other app is open it also registers a lot of touches without touching the screen. It's nothing you can replicate. Kinda spooky actually lol.
I've tried a couple of things already, rebooted, killed most apps, checked the charge cable (original) and port but to no avail.
I have the US version and am on the latest stock ota, but rooted. I'm about to do a restore and after that clean install if necessary. I just wanna check if anyone experienced this before.
I will lost back if I get to the bottom of this. Hopefully it's not the hardware.
Click to expand...
Click to collapse
I had once this issue on cm12.1 oneplus 2 . What I did to solve this problem successfully.
1. I removed case from my phone . This causes grounding issues sometimes.
2. Reflashed OxygenOS.
3. Then I flashed cm on top of it. Wiped data, cache, dalvik only. didn't wiped system partition.
4. That's it. I'm. I'm typing right now while charging. Totally perfect.
I noticed it more with my cheaper USB C cables.
I bought a half dozen and some are better than others.
the boxed cable that was stock is the best by far.
Yesterday i aux in my phone to a audio player and observed the same problem again with touchscreen. Feeling very annoyed because of this and other bugs.
My phone used to lock up completely for up to 30 seconds after plugging in the charger. After move to cyanogenmod 13 this does not happen anymore, so obviously a bug in OxygenOS.
Skickat från min ONE A2003 via Tapatalk
Hmm, this is generally not a problem with your phone or your software, but relates to the power supply. Noise in the power or grounding issues specifically cause the 'ghost touches' and erratic behaviour you describe. If you are lucky, your charger and cable are also fine and the issue is with the power socket, in which case you need an electrician to come and take a look. If its the charger/cable, then simply get a new one and you are good to go.
To figure out where the issue is, start by using the same charger + cable in a different location (completely different physical location). If the problem persists, then try changing the cable in that same location. If it still persists, try a different charger.
If the problem is NOT there at the alternate location, then chances are its your wiring and you need an electrician to sort this out for you.
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