My touch pro 2 first started this when I had lots of cab themes like changing the icons and clock. I was listening to music when it started to redial the last person I rang. I thought it was a cab iusse which did this.
So I removed them all and reset it to factory settings.
Its done it about another 5 times since then but not listening to music, while it was sitting on a table.
It was locked with the screen turned off then just started trying to ring the last person I called.
any help from you smart people.
And yes I did do a search on here first
Bri
Does your device only makes these calls when connected to a headset?
I previously bought a cheap headset with 3.5mm headphone adapter. It had a button on it to answer calls. Apparently something was wrong with the button since my device kept thinking the button is constantly being pressed. 2 quick presses on the button instructs the device to dial the last called contact.
My problem went away after I replaced the headset (with another cheap headset albeit!)
I used mine alot as a mp3 so it could be that but my cheap adaptor does not have a redial button like yours. And it did it with a cabled adaptor and one which has no cable. I got mine from ebay those were the only two models i found and I have them both but it did it when I have it pluged into my car charger too.
but I cant think if its done it when its not pluged into anything hmmm
My money is on your (non-HTC-approved )3.5mm adapter and your car charger being the culprit. Somehow, they are instructing your device to dial your last contact.
I'm havning the same problems recently with my TP2.
It *ONLY* happens in my car, when I have it connected to a 3-in-1 mini-usb => headphones/charger adapter. It has no buttons at all, just a passive converter.
It might have to do with the adapater, or maybe with my cars builtin BT functionality. It also only happens if I physically move the phone and put it back next to me or pick it up.
Star-Lite said:
I'm havning the same problems recently with my TP2.
It *ONLY* happens in my car, when I have it connected to a 3-in-1 mini-usb => headphones/charger adapter. It has no buttons at all, just a passive converter.
It might have to do with the adapater, or maybe with my cars builtin BT functionality. It also only happens if I physically move the phone and put it back next to me or pick it up.
Click to expand...
Click to collapse
I've had something similar happen with a broken adapter. It was acting like I was pressing the redial button, replacing the adapter stopped the problem.
Also, I've seen the TP2 act strangely near strong magnets. I can unlock mine using the clip on my (now no longer used) case without touching the phone. I also was able to get the camera to start once, I bet I could have caused a redial if I wanted to try.
any ideas of where to get an offical one from? Ive never seen one.
snuwho said:
any ideas of where to get an offical one from? Ive never seen one.
Click to expand...
Click to collapse
Check this out. But I've seen it as cheap as about 90 HKD (roughly 7 GBP) in stores.
I've actually experienced the same thing but with one difference: I was using a bluetooth stereo headset (Motorola HT 820 to be exact). Any ideas?
oh and when I say car charger I mean a Venturi mini with the offical data cable I got with the phone. Which is conected up by... bluetooth.
This is werid
Okay, seems that my case is the same and the suggested solutions don't really apply in your case. Any ideas everyone?
snuwho said:
oh and when I say car charger I mean a Venturi mini with the offical data cable I got with the phone. Which is conected up by... bluetooth.
This is werid
Click to expand...
Click to collapse
Maybe Bluetooth is the problem then.
I might check and try to reproduce the problem the next time I'm stuck in traffic again
Will try to see if it's a BT or converter problem.
Woo HOO, Got the FROYO Update this weekend! Not many changes that I have seen so far but I am glad to make at least this much progress.
Anyway, TV Out - Dag Nabbit!
First I bought the mini-jack to 3 RCA cable, tried it at home on THREE different televisions and it didn't work on any of them. THOUGHT the update would help, tried it again on the SAME 3 TVs and NOTHING. At least that cable was cheap!
Bought the MicroUSB to HDMI cable with HIGH HOPES, 45 bucks (Shipping Included) tried in on the SAME 3 TVs both BEFORE and AFTER the update to 2.2 and it didn't work either time or even TODAY!
The only setting I know of to change is the TV OUT in the SETTINGS menu. Which was turned on and since I am in NJ USA I used the NTSC (ATSC) Setting. Much to no avail. So, am I just REALLY good at wasting money or is it my phone OR is something else missing?
If MORE particulars are required let me know and I will provide them.
I got this phone BRAND NEW from T-Mobile in August of 2010, 5 months ago. I love the phone for it's display and all the working functions and apps. I DO NOT have a data plan, I use WiFi at home - works perfectly.
Thanks in Advance to all who may respond with something useful. Have a great Day (to all who respond period)!
With the rca cable, did you put the red into the yellow and vice versa?
Sent from my SGH-T959 using XDA App
kdf2883 said:
With the rca cable, did you put the red into the yellow and vice versa?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah, I have to flip the outside two plugs for mine. The middle, of course, should be switched with the other middle.
humm!
Dude has anybody ever made theirs work....I have been watchin for this since the phone came out but never seen anyone say it worked....I to have tried everything but didn't buy the hdmi......Tmo limits everything this phone can do....like rerouting our wifi calling to make sure it uses our minutes and the tethering they finally let us have now also adds additional charges to your bill. Good thing I can still run easytether free. But I really wish someone could help us get the TV OUT working...
Um.....TV Out works......If you're using a non-Samsung composite cable you'll need to swap the red and yellow connections most likely. I've had to do this with two different sets of tv-out cables (one for a Zune, one for a Sony camcorder)...
This is what I use and it works. Plug one end into the headphone jack and the Y/R/W into the exact color that they are on the TV.
http://www.amazon.com/Microsoft-Zun...9?s=electronics&ie=UTF8&qid=1296082359&sr=1-9
Thanks guys...I will ask more questions from now on.
Sent from my SGH-T959 using XDA App
Vibrant ka7..rooted and unlocked
Garminone updated to 2.1..rooted and unlocked. 68 hrs between charges!!!!
I also use the zune and it works for my vibrant too
Make sure that you buy a tv-out/av cable with long 3.5 jack, and with thin/small covering on top of it so that it fits right into the vibrant's 3.5mm hole and you actually hear it click. And yes, I use the red cable for video input instead of the yellow one.
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.
Is anyone else having issues using Android Auto with this phone? Came from a Pixel 3 and never had an issue. When I connect to my receiver, AA says it is connected but doesn't start in my phone or on the receiver. Any ideas for a fix? Thanks.
I only made a couple of short drives yesterday, but I didn't have any problems.
If you did a smart switch when you got your S20 it might have missed up the Android Auto app on your phone. I suggest to clear the data and re-install. I had to do this for mine to get it to work.
Mine is also working fine..... I'd suggest a reset also
Plugged mine in and no problem at all. Came right up.
I'm starting to suspect its a contact issue with my cable as its a hit or miss now. Thanks everyone.
I'm still having issues with this. I'm using a Pioneer 4100 Nex and its a pain to get behind the radio to change cords. I did so and still didn't fix my issue. Are you using a certain USB cable? I'm using an older Anker USB-C to USB-A cable and it connects just not loads on the screen except that one time. I guess my question is does this phone require a certain USB-C cable even though I'm certain the USB tech in my receiver is at most 2.0.
I've noticed an issue that is intermittent with the phone. If a call comes in or dial out the call screen will not display and you can't end a call or do anything.
Sent from my SM-G988U using Tapatalk