Hello!
I have a very strange problem with my Trophy's stock headset (the one that comes with the phone).
Once I tried it in my brother's Samsung (which runs Android) to test out the volume and call buttons. They all functioned as play/pause buttons. But since then my Trophy won't do anything if I press them. The earpieces are OK, and the phone turns on when I plug the headset in.
What can I do? Is it possible to somehow reset the headset or something like that?
Got the exact same problem here.
Don't think that a hardreset will solve that probleme - as I flashed a few days a go a new ROM - and I still have the problem. Don't know how to fix it tough..
Related
Sorry if I'm posting a question that's been answerred before, but I haven't been able to find a thread to this problem:
sometimes my Nokia BH-102 will disconnect in the middle of a conversation in the car. The only option at that time is to pull the TP2 from it's holder and put it to my ear.
Whether it's the headset or the phone, I don't know, but it used to work in combo with the old Nokia E60 I used to operate......
Chances are it's the TP2, but how to fix it?
Only 'tweak' was to install tomtom, but without the 2 dll's which have been causing some problems.
Has anybody experienced anything similar?
Bluetooth visor problem
I have had problems with my headset - Supertooth Visor One Bluetooth Car Kit. Not quite the same as you though - the problems I have is that when I make an outgoing call, everything works fine but when I recieve an incoming call the audio stays on the handset rather than coming out of the bluetooth headset - which means I have to pick up the phone. I also have installed TomTom 7 and I had to do the 2 dll fix as my bluetooth was completely broken otherwise. So I guess maybe TT7 is responsible in some way. Only thing is, I dont want to do a hard reset to find out!!
I'd already read about the Tomtom BT-issue so I cleared the 2 dll's out of the cab prior to installation.
So the originals should still be in use. BT is/was working and I have been synching using BT. That's not the problem.
There should be threads out here pointing you to the original dll's. you could past them over the current ones and see if it helps.
I experiencing the same problem, and didn´t install tomtom.
So now it looks like it's a problem in the TP2 then.
Hopefully a BT-guru can investigate? This is way beyond my capabilities.
In the meantime I'll know what to do if and when it happens: take a chance on the cops seeing it and issuing a ticket.....
I'm having a similar issue, my headsets plural, have this problem. It will disconnect but what is happening is the headset is shutting down. If I hold the power button on the headset it comes back on and will work again.
If it was one headset I would think it is faulty but I've had this problem with three headsets and the Bluetooth in my car.
Is it possible that the phone is sending a shutdown command? BTW I am using the stock TMOUS 6,5 ROM and have tried some of the cooked ROMS with the same effect.
Hi,
I have the handsfree headset that came with my Desire, now about 2 months old. A couple of days ago the control buttons on the headset stopped working, I can no longer remotely answer calls, or pause and change music tracks. The headset earphones and microphone still work, I can listen to music and use it for phone calls that have been activated from the phone itself.
The headset itself has not received any 'obvious' damage, it hasn't been dropped in water or the like.
Before I go out and buy a new headset I thought I'd better try and confirm if they were indeed at fault. Is there, for instance, a phone setting to disable the headset controls.
Have you tried rebooting the phone? I once had the media service play up and the keypresses stopped working until I rebooted the phone.
You could also have installed some other software which are capturing the button inputs.
The buttons work over the microphone wires, so its unlikely to be a broken cable if the mic is still working.
I have done a soft reset, taken the battery out, no help. Next move, I suppose is a hard reset back to factory settings. I've not done one of thesebefore, what do I lose, or better put, what doesn't the back-up save?
When I connect headphones or a cable between headphone connector and a sound system it seems the phone don't recognize it. If I try to start the FM-radio I got a message telling "Headphone required To listen to FM radio you must plug in headphones to the headphone jack."
If I start webradio or something else that plays music I get the sound from the built in speaker instead of the connected item.
If I restart the phone it works again but onlt for some time(a few hours) and I don't know what or when it fails again.
It feels like a software problem but I'm not sure at all.
Anyone that have a clue what I can do to get rid of this most irritating fault?
(The phone is equipped with rooted Froyo 2.2.2 Swedish version)
I was listening to FM-radio when making a call. Radio was muted and after I hang up the headphone connector stopped working again.
So it seems I'm the first one with this problem. To bad...
The problem persist. Should I return this phone or do anyone have any idea what to do about it?
Every time I get a call the headphone connector got disabled and only a reboot enables it again.
I believe you should return it. Especially if it's on the original firmware. That way you'd know for sure that it cannot be your fault.
If you already flashed something, try a full reset flash again (maybe some other rom) and reset again.
This looks very much like a software problem to me.
Just my 2 cents...
Sent from my MB525 using XDA App
Do anyone think that at factory reset could solve the problem?
Hi chaps,
Wierd issue. Headphones are not detected when plugged into my phone unless I do a reboot. Similarly, when I unplug the headphones they are not 'un-detected' until a reboot.
However, using an app called toggleheadset I can force audio through to my headphones. This is a bit of a pain because 1) I have to remember to do it and 2) I lose Beats functionality.
I have tried using different headphones but this has no effect.
Any ideas as to why the headphone state is only detected at boot?
I have tried different Kernel/ROM combinations but to no avail.
Any help would be greatly appreciated.
also, if anyone can provide me with some pictures of their headphone port so I can compare it to mine that would be great.
Hi,
I have the exact same issue with my HOX since yesterday.
At first I thought the ROM had something to do with the issue, but after flashing several other ROMs, it still wasn't solved. (I haven't flashed back to stock btw)
"toggleheadset" works ok, but I can't use the microphone that way; I can't use my headphones to make calls anymore.
Also when answering phonecalls, sometimes my headphones are still toggled on, so I can't hear the other end. And the worst thing is: when I try to toggle the headphones off during the call, my screen dimms and I struggle to activate the widget. THATS a pain in the ass.
Does anyone know if the issue is software/hardware related? And the best way to solve this?
I'm wondering if this issue affects bluetooth headsets. If it doesn't, I'll consider buying one.
Old thread, but me the same... But my HOX survived waterboarding... I felt into the wather while sailing. Changed battery and screen, but now I see i have one more problem to solve. If any one have solution - please write. But for now I'll try to fix by my own
Cleaning Hole
Try to clean the hole where the Headphones are put in...
If its clean, try to reinstall the rom.
Tested with two different headsets with the same result.
Sound works, but since yesterday control buttons stopped working. No one of them, volume up, down or play/pause.
Only thing different is that yesterday I started using bluetooth headphones and today I am back to wired ones.
Anyone experienced something similar?
ruisan said:
Tested with two different headsets with the same result.
Sound works, but since yesterday control buttons stopped working. No one of them, volume up, down or play/pause.
Only thing different is that yesterday I started using bluetooth headphones and today I am back to wired ones.
Anyone experienced something similar?
Click to expand...
Click to collapse
Tried a "restore to default" and problem continues. Looks like something broke inside.
It was a hardware problem
How did you find out it was a hardware problem?
I am experiencing the same. Only that I did not use a bluetooth headset before...