This test is intended for Universal.
You need a registry editor to set the following keys values:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\BLUETOOTH\SYS
COD=1048852
DISABLEAUTOSUSPEND=1
Please report results
My bluetooth has been ON for 2 days and nights without any pause.
thx , nice try
without edit the registry key, i return to radio 1.09 and bluetooth alway on now
On the third day bluetooth went off, so this reg key setting doesn't work. I'll try radio change.
After flashing radio 1.09 lost bluetooth in 40 minutes: problem is in wm6 and not in radio rom.
Hi, all
Just a little bump!
No news on this problem?
When making a call, the other side can ear me, and I can ear the other person... but when receiving a call, I ear, but the other person doesn't ear me.
vmiguel said:
Hi, all
Just a little bump!
No news on this problem?
When making a call, the other side can ear me, and I can ear the other person... but when receiving a call, I ear, but the other person doesn't ear me.
Click to expand...
Click to collapse
its not the same problem... you are talking about something else
im trying to investigate your problem cause it's happend to me also, but somehow i fixed it & don't know how
Related
I am running asergs' aku3.3.12 for some time and I was very happy. Yesterday something very strange must have happened. I can make calls normally and I hear everything very good, but I don't have any other sound any more, meaning I don't hear my phone incoming ring, I don't have sound with windows media or any other app. When I go to sound and notifications (settungs), all sounds are still there, but I can't hear them.
I can hear sounds with the earphones, not loud, but I can hear them!
Does anyone know this problem or have a solution? Thx in advance.
I think it's the hardware problem, you can hear the sound when connect with earphone, right?
I met this problem before and it's because the connector in prophet still think the earphone is connected although it's not actually.
I don't if I understand your problem exactly but this is my understanding, and try to send it back to prophet service department to repair it.
palo
Hi,
I have the same problem. Just after installing version 12, I got this issue. I couldn't believe it was a hardware problem but, If I press at the back of the phone it starts working so now, without any doubt, I'm taking the qtek back to the shop where I bought it and see what they can do. I'll try to avoid the manual fix (replacing the speaker).
Regards,
Encinas.
Hi All,
Has anyone experienced this:
Talking on the phone using a bluetooth hands free (Moto H500) and any kind of notification comes in (new txt msg, new voicemail, low battery, etc) the call switches from the headset to the handset. I only had this happen in the WM6 ROMS, but it has been in all the ROMS i have tried. Maybe there's a fix i missed somewhere, maybe it only happens to me... Any thoughs or suggestions would be greatly appreciated.
thanks
Ya, I have the same issue with the WM6 ROMS.
I think I solved it though. You have to set Voice Command to only announce notifications though the device speaker. That seems to have solved the (annoying) issue for me.
Thanks for the info GadgetGuy, I'll give that a try... I just prefer that the people around me not know I just got a new message or my battery is low... If I find anymore on that I'll post again.
With the stock ROM from T-Mo when I had my BT enabled I could answer calls with the headset and the call would be on the headset but if I answered with the phone itself the call would be on the phone. I really like this feature because occasionly my phone would be closer than my headset so I could just hit the Answer soft key and use the phone. Does anyone know of a registry setting or cab file that would allow me to do this with Core 2.0 (or any other WM6 ROM)? My workaround for right now is to answer the call on the phone and then immediately turn off hands free, but the caller hears about a second of dead air and sometimes hangs up thinking the connection was bad... plus it's generally a pain in the a$$
TIA.
my advice, if you're in that situation just turn off yer bluetooth.... other than that i know of no such registry edit. perhaps someone else would care to chime in?
Thanks for the advice. It usually happens when i have my phone on my hip and my headset in my office while i'm going to get a cup of coffee... almost always i get stopped by someone who needs some sort of tech help along the way and my 45 second trip to get a cup of coffee turns into a 25 minute trouble shooting session with because the user "didn't make any changes to the system, it just stopped working"... i'm sure we've all heard that one... anyway, thanks for the advice, i'll keep looking for a solution and will post back if i find one, just in case anyone else is interested.
you mention that's it is on your hip a thought ame to my mind... map a button to toggle bluetooth. i.e. the camera button this way your bluetooth will turn on/off at a touch of a button.
i've had the Touch Pro for a little over a week and i absolutely LOVE IT.
the only problem i have is that every now and then, all sound output dies in the device
the phone wont ring anymore, it would only vibrate.. and if you try to raise or lower the volume, no sound comes out at all either.
the only way out is to reset the phone which i'm doing now on a daily basis hoping to avoid missing calls and messages when the phone only vibrates while it's away from me.
anyone have the same problem and/or a solution?
ROM: 1.90.456.3 WWE
ROM Date: 08/20/08
Radio: 1.02.25.19
Protocol: 52.33.25.17U
Hello AntiProxy,
Unfortunately, welcome to the club...
You are the 3rd person I've counted that has that problem. A post is already active on it:
http://forum.xda-developers.com/showthread.php?t=422322
What is weird is that you don't have the same ROM as Zillator and I (we have the same ROM).
I'm really starting to think it is an hardware problem then and that we'll have to send the phones back...
Please check the other post.
Hello Flippy.
yeah i noticed your thread earlier but thought our general symptoms are different.
in my case and when the problem happens, the phone no longer rings, no more message notifications, etc.
and it doesn't happen while the phone is ringing.. it just seems to die off randomly.
like the other day a friend came over and asked if i got his message.. i checked and found 3 messages.. no missed calls.
figured the sound was low, so i hit volume up and increased it to the max, but still no sound was coming out..
i asked him to call.. the phone vibrated, no ringtone.. i answered.. he could hear me, but i couldn't hear him.
now the only good news i might be able to give you, is that i've had this same issue back in the day with my blueangel (i-mate pda2k) and it got solved with a new radio rom.
don't ask me what's this got to do with the radio.. it worked back then.
Same here m8!
When my phone does like that I usually realize when calling. But when it does happen all my sounds are ded as well (volume up/down you don't hear sound, it vibrates without ringing and all other sounds are dead).
We have exactly the same symptoms!
i have this prob too. is worse when i use my bluetooth headset. the, it crashes while in the middle of a call.... how do we get this fixed? called HTC service centre and they suggested i upgrade ROM. read in other places that htc changed the mainboard...
any ideas??
PS, i have the exact same rom, radio and proto as @antiproxy
Hi guys.
I have an in-call problem with my Desire S.
This does not happen when I get called, just when I initiate a call.
When I call someone, the other part of the conversation will always hear a great noise or interference coming from my phone's microphone to the point that my voice is not understandable anymore.
I noticed though, that if I switch to speaker and back to earpiece the problem gets solved for that particular conversation.
Do you guys know of any permanent fix for this?
thanks.
Hey... nice to see a felow ro. on this forum.
Try a factory reset...it sounds to me like a software problem.
If that doesn't do it.....waranty should cover it.
Ok. So I hard reset and after spending a whole lot of time which I did not have reconfiguring the phone, I got the same problem.
And I figured out that the culprit is the Keep Service option in PowerAmp. Unchecked that and no more problems... and no warranty call... phew!