Since yesterday my mdac3 will not make a sound. The external speaker seems to have given up, and I also don't seem to be able to sync with my pc!
The phone charges ok but I get 3 low beeps from my pc when I connect it to the usb. OUt of interest the fm radio still works
I can get nothing out of the external speaker at all, but the headphones still work
I have Toms B&b 4.1 loaded and have hard reset the phone with no improvement but now that I cannot sync I have no contacts
Has anyone any ideas, please?
Oh and could I send it back to Tmobile under warranty with the B&B rom loaded?
Thanks
Related
g´d evening guys.
hope that someone can help me out with this one:
i´m using schaps 3.54c and it was working fine for a long time, but now it randomly happens that my speaker dies. i mean ...yeah, well, it just dies - but audio is still working via the usb headphones. it gets even stranger because i was able to get it back working a few times by enabling/disabling flight mode or starting strange combinations of audio players at the same time.
but now it´s dead again and i can try whatever i want = no chance to get it back so far, and i don´t want to reflash.
anyone with an idea, suggestion?
Same thing happened to me. Its the plug. When you plug in the usb headset it triggers the device to send the sound via usb. When you take it out, it stays Via usb because something is broken inside the plug and it doesnt go to the external speakers. I used to have to plug it in and out 10 times to get it to go back to external speakers. Afer a few weeks of that it wouldnt go to the external speakers at all.
got the O2 official WM6 installed for about a month now, and suddenly, when i connect the pda to the computer it would not activate the activesync.
and it gets worse, there is no sound at all. I could have the phone ringing, but the speaker is not working, nor does the build in mic.
interestingly, the headphone works fine. weird!
remain the same after restore it, and refresh the ROM via SD card.
does it mean my orbit is reaching its end of life?
any ideas would be very appreciated.
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.
Yesterdaty I updated to WM6.5 and now try to get everything working again. Somehow my TP2 won't pair with my bluetooth carkit anymore. With WM6.1 this was no problem. The phone still pairs perfectly with my computer (also bluetooth connection) so I think the bluetooth connection is ok.
When parining to my carkit it finds the device, then I have to enter a password on the TP2, and after that it just sais "pairing connection failed", and it will not work. I am sure the password is not changed since yesterday. I tried it several times. I do not know what to do anymore. Could this be a setting somewhere? I get the feeling my password is not send properly but have no idea.
Meanwhile I tried pairing my carkit with another phone and no problems there. So my conclusion is: something has changed with bluetooth, updating to WM6.5 which makes it now impossible to pair my TP2 with my carkit.
Is there maybe a programm for the TP2 which give me more controll over bluetooth (like maybe go to an older standard)?
I have exactly the same problem as you
good to hear I am not the only one. Hope someone will come up with a solution for this.
I did nor observed any issues when pairing my TP2 after reflashing to WM6.5
There is another issue however - I can not hear any voice until it is charging.
Unplugging of the charger fixes this issue immediately. Horrible...
Seems, HTC guys are saving money on testing by using us as Beta Customers.
Would a custom ROM be a solution for us?
I updated to the "energy 6.5.1 rom" and guess what..............
The same problem. The rom is very nice, but my TP2 still won't pair with my BT carkit which is very big problem for me.
Is there maybe a way to downgrade just the BT part of a rom to WM6.1. I read on different forums there is something that is called a BT stack. Could this be the problem?
I have a ton of problems with bluetooth pairing now. However, I don't know whether it's the fault of 6.5 or the Tilt 2. Here is what I am experiencing...
- On car deck or headphones, the skip buttons don't do anything
- on car deck or headphones, I have to disconnect Stereo Audio and then reconnect to actually get sound. It NEVER works when it auto connects.
- Music will do a brief skip when you shut the screen off
- Stupid message about volume control every time it connects (resolved by switching to custom rom)
- SMS or any kind of alert tone now turns music way down so that the tone is the only thing you hear. Which is super awesome when I'm driving my drunk friends around and they are singing along to a song when suddenly it mutes so everyone can hear my incoming text message.
Not a single one of these issues existed when I had my Fuze.
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
orb3000 said:
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
Click to expand...
Click to collapse
No I do not think so, because I used the official WM6.5 with the same problem. Does someone know a way around this issue. I strongly believe that if only I could pair I have some options to work with it (in 6.1 it worked like a charm). If I only could pair without having to send the passkey it would be great step forward. I presume with sending the passkey, the bluetooth of the TP2 sends out other "rubbish" that confuses my carkit.
My problem is solved and guess what, it had nothing to do with my TP2. The problem was my carkit. It has a maximum number of bluetooth devices (5) it can pair to and the last one (the WM6.1 version of my phone) had been reached. So a hard reset on the bluetooth carkit and the problem was solved.
Well, at least I now know how to flash a rom to my phone and I think I learned more about the phone reading through all the forums. Thanks all for thinking with me on this problem!
Does anyone else still have this problem?? I have removed all the devices from my car and continue to have the same pairing error just after entering the passcode. Stock Spint ROM worked great, but multiple 6.5 upgrades don"t pair..............suggestions/ideas??????
bluetooth settings, advanced, enable beam data exchange,check the box
Interesting.....I actually found a fix. Instead of pairing the phone with the car, I paired the car with the phone. I didn't even know that this was possible, but it did the trick!
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?