Related
Hi
I have the newest firmware version installed on my Qtek 9090 (BA_WWE_14000_147_11200_Ship), and I experience a problem again which I had first when I bought my Qtek but was gone after I had installed Radio version 1.08.00:
Once a day I have to reset my Qtek because I can't hear the one I am calling - usually this happens when I call my mobile phone's answer phone. The phone gets connected but I don't hear anything. After a soft reset everything is fine again.
Is this a known issue? Any solutions to it? Ok - I know I can downgrade to 1.08 again but I dont really wanna do that. And yes, I can stop calling my anser phone ....
Anyone knowing what is causing the problem?
Reagrds,
A
I had the same problem with my Qtek 9090 until I stopped use the Bluetooth feature completely. Since then, everything is fine.
tot 1.12 radio has solved the "no sound" issue.
keeping_sg said:
tot 1.12 radio has solved the "no sound" issue.
Click to expand...
Click to collapse
I cannot verify this, i have an mda3, upped it to R1.12 but i had many "no sound" problems. Now i downgraded to R1.10 and had not a single no sound issue ..yet
ThExSenatoR said:
keeping_sg said:
tot 1.12 radio has solved the "no sound" issue.
Click to expand...
Click to collapse
I cannot verify this, i have an mda3, upped it to R1.12 but i had many "no sound" problems. Now i downgraded to R1.10 and had not a single no sound issue ..yet
Click to expand...
Click to collapse
i have tried 1.06 & 1.10, all are having that issue. that's why i have upgraded to 1.12 so far so good. umm.....................strange..
keeping_sg said:
ThExSenatoR said:
keeping_sg said:
tot 1.12 radio has solved the "no sound" issue.
Click to expand...
Click to collapse
I cannot verify this, i have an mda3, upped it to R1.12 but i had many "no sound" problems. Now i downgraded to R1.10 and had not a single no sound issue ..yet
Click to expand...
Click to collapse
i have tried 1.06 & 1.10, all are having that issue. that's why i have upgraded to 1.12 so far so good. umm.....................strange..
Click to expand...
Click to collapse
For me, radio 1.12 delivered:
- worse signal reception
- higher battery consumption
- still no sound issue.
flashed twice & still having the bloody "no sound" issue. really give up. i think the next thing to change is the motherboard. sigh.........................
I had never had this issues untill I upgraded my Radio to 1.12 and then I had it 5 times in one day, went back to 1.10, no more issues
Hmm. This is a really 'odd' problem. I didn't originally have this problem with my SX66. Then, it just 'popped up' one day, and I can't seem to get rid of it.
I have tried different ROM versions (currently 1.40), and my radio version is at 1.10.
I have NEVER used radio 1.12, so I know that's not the CAUSE.
We need to compile a list of people with the problem, and see exactly what combination of ROM and Radio they have, as well as the programs they have installed.
if you read the cingular forums, there are a few folks there that say they have had it all along so I am not sure where to start...
umm....... different ppl have different problem. seems like it's a integration issue.
If you go to some HK forums, you will also find a lot of people suffering from this.
To me, I seldom use it as a phone. I only use it to receive emails and website browsing. When I go overseas and I used it as a phone with a BT handsfree (shut down GPRS connection), everything is just fine. I only encountered once with no sound problem when I take away my BT handsfree on a plane....
It's definitely a bug since a long time ago with old and new versions.....
Sad....and disappointed......
Hi all,
I upgraded my phone to the 1.12 radio along with the 1.40 CE ROM and am always resetting due to the "can't hear caller" issue and I never had this problem before.
I'm going to do a hard reset and see if that helps (clear out all the apps and use it for a day or so). If this doesn't work, I shall revert back to the 1.10 as I had no problems with that.
ROM 1.40.00
Radio 1.12.00
EXT ROM 1.13.139 (with Updated CallerID [1.20] and older version of O2 Active [3.0])
This cant hear caller issue, is it cant AT ALL hear caler or caller is so faint I cant hear him.
I ask as sometimes I get calls that are faint however when the caller rings back it fine. Not sure if its crap reseption or the device.
I got O2IIs from UK and had the same "No sound" problem. I have to SR about 5 times daily to sort it out. However, if I turn off Bluetooth (pairing with my Bluetrek G2) then everything's OK.
My ROM version is 1.31.00 WWE, Radio : 1.10.00, ExtROM: 1.31.139 WWE and BT 1.0.0 Build 3500
Had up to BT 3900 but wont help. Gonna up radio to 1.12. Will post the outcome soon.
I've only experience the problem once since the imate 1.40 upgrade.
Now, I must say that I don't use the phone THAT heavily.
I upgrade to 1.40 EX, it seems working fine, still the sound quality is not good enough...
people!
A guy called Derek has posted a possible solution to this problem here! http://forum.xda-developers.com/viewtopic.php?p=118364
It involves removing the Bluetooth for the startup because he believes that even with the bluetooth off, the unit is still trying to connect to a bluetooth headset.
I'm going to remove/unpair my Bluetooth Headset and see if that makes a difference. If anyone else can try this and post results I'm sure this would help loads of people.
Dom
Please confirm this and I will post it to wiki
@xdadom,
It's correct. As I mentioned in my post, when I "turned off" Bluetooth, everything's OK. The way I "turned off" Bluetooth is exactly the same with Derek did in his post, i.e. delete "Run_BTTrayCE" from Windows\StartUp\
However, I still need Bluetooth for my hand-free device. In my opinion, it's rather a trick, not a solution to kill "No sound" problem. Anyway, we can wait the updated BT version from supplier to sort it out.
Hi!
My tytn II w/ original WWE HTC Rom (installed apps: Tomtom 6, MS Voice Commanc 1.6) sometimes just makes no sound when I´m calling someone or someone is calling me. I just can´t hear anything from the built-in speaker nor from the speakerphone. Ringing and playing mp3 is working fine.
When I get that problem I have to restart the device.
I tried the search function but didn´t really find a solution, just for problems that occur ALWAYS and not intermittend....
Thanks in advance,
Ingo
I have the same issue and resolve it the same way.
burli said:
I just can´t hear anything from the built-in speaker nor from the speakerphone. Ringing and playing mp3 is working fine.
Click to expand...
Click to collapse
How does it go with the original supplied headset plugged in? What does WWE mean (with regards to the ROM)? Have you made any changes to the device since you got it and if so does a hard reset fix it (that is if you haven't spent ages custimising things so wont be loosing much in a hard reset)? I've never had this problem with my TyTN II other than of course sometimes when the reception is dodgy but thats not a problem with the device.
As far as I know now, the problem is MS Voicecommand. I uninstalled it today and no problems so far.....
burli said:
As far as I know now, the problem is MS Voicecommand. I uninstalled it today and no problems so far.....
Click to expand...
Click to collapse
I have this problem too, but I don't think it's related to Voice Command because I don't have it installed.
Flying Kiwi said:
How does it go with the original supplied headset plugged in? What does WWE mean (with regards to the ROM)? Have you made any changes to the device since you got it and if so does a hard reset fix it (that is if you haven't spent ages custimising things so wont be loosing much in a hard reset)? I've never had this problem with my TyTN II other than of course sometimes when the reception is dodgy but thats not a problem with the device.
Click to expand...
Click to collapse
Just FYI; WWE stands for World Wide English (or some people say World Wide Edition)
Occasionally I have a problem where when making or receiving calls I pick up and there is no sound. If I Soft Reset I can make the call and it works fine. It's been starting to happen more often recently, and is really bugging me. It happens both when I'm using the phone speaker, and my headset.
what rom are you using? I have noticed the same thing the last couple of days since upgrading to L26 M2D v1
ah, here it is the same thread.
I use WM 6.1 htc version
Is there no bugfix?
Have you tried flashing a new radio?
Ta
Dave
data at info:
ROM: 3.28.407.0 GER
funkempfänger (i guess it's the radio): 1.65.16.25
protocoll: 25.83.40.02H
it was updated with the new htc 6.1 version what i've heard.
or can i downgrade it to a version that is working fine? when yes, where is the file to do so..
Right now I'm using Radio 1.58.16.27, I'll try another one, which do you recommend?
I was using 1.65.29.22, switched to 1.65.24.36 (I was using this with L26 diamond V12 with no issues)
had the same issue today.
hm, looks like a big upcoming problem for everyone...
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
virusv69 said:
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
Click to expand...
Click to collapse
Old thread but still, I've been experiencing this issue on the Hyperdragon series of ROMs from late October. Also had this problem in the past on some of Dutty's roms. The latest Raphael version (15/11/2008) has not exhibited this problem in 4 days. Only difference I can see is a slightly newer version of MSVC (1.6.19965).
Cheers.
gatewayer said:
hm, looks like a big upcoming problem for everyone...
Click to expand...
Click to collapse
I am getting the same problem intermittently, with a soft reset as the solution.
I am running a bone stock AT$T rom,recently upgraded to 6.1. It started happening post upgrade.
An upgrade problem?
same here... im playing around with different radios, it has to be a radio issue imo
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
1stPeregrine said:
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
Click to expand...
Click to collapse
My phone rings and notifies just fine when Texts,emails and calls come in. It answers just fine, but there is no sound. Then when I try to call people back, there is no dial sound and the call appears to not go through, until I do a soft reset, then all is back to normal.....................for a while.......................
I'm having this issue also. The other party can hear me when I answer, but I can't hear anything after the initial incoming-call ringing. A power-cycle restores normal operation but only for a while.
ROM: 3.28.405.0 WWE, 05/02/2008
Radio: 1.71.09.01
Protocol: 25.75.40.02.eMo
I'm in same boat as everyone else here.
Sometimes my phones rings, but when I answer I have no sound and other party can't hear me. Other times, my phone doesn't ring and all audio is muted (despite volume on). Soft reset is the only thing that works for me.
I gotta say this is really pissing me off. I'm missing lots of important calls because my phone doesn't ring when it should, or if I'm lucky it rings but has no audio so I have to soft-reset and wait 5 minutes for my phone to reboot & re-establish signal all whilst my clients are trying repeatedly to call me.
I'm willing to try other radios, but no one seems to have any working suggestions.
Thought maybe it was software, since I don't remember this happening after my initial WM6.1 upgrade. Uninstalling S2U2 didn't work (happened again today). Just uninstalled Voice Command, too, but haven't tested yet. VC's been flaky since upgrading to 6.1, working sometimes, failing to announce calls other times, plus occasional VC crashes at boot claiming "out of memory" which is blatantly untrue.
Just out of curiousity, is everyone with this problem using Voice Command, or just some of us?
Think I might have to go back to WM 6.0 since 6.1 didn't solve my Bluetooth issues plus screwed up Destinator...oh well. Schap's WM6 4.31 was best ROM anyway.
Anyone having any luck with this problem?
Like I said, I was running AT$T WM6 with no issues. The I updated to WM6.1 and started having these call issues.
Last week I flashed to HD III still no joy. SJ says that he is running the same radio as me, 1.65.24.36 with no problems.
Is it " my " phone? Microsuck 6.1 ? The radio ? Has anyone solved this with a new radio flash ?
I run a business on this phone and it is getting really frustrating, I don't want to go back to 6.0 just so I can get my phone calls?
I'm not just whining, looking for sucess stories.
Hi, havent been here in a while but i thought i'd add to the list. I have recently flashed HD3 (one of the early november editions) and it was without problems until friday when i dropped my fone. Ever since then i have had the intermittent sound in call which is only fixed by a soft reset (exactly the same as denco7). I haven't changed the radio since dutty's 1st diamond rom (a while ago) as i haven't had any problems but now im thinking about it.
Current setup (from device info):
ROM version: HD_III_Jade WWE
ROM date: 09/30/08
Radio version: 1.65.24.36
Protocol version: 25.94.40.06H
Not using MSVC
Recently flashed to HD III Blackstone hoping this might work but still having the problem.
I also flashed radios 1.65.24.36 and 1.70.18.02
and now I am running 1.70.19.09....... and it is still happening. It has got to be something in WM 6.1. Cannot be a software conflict, because it was happening when I was running bone stock AT$T 6.1 upgrade with no software add ons.
Again, I would hate to think that I have to downgrade to 6.0 just to get my phone calls.
Damn WM6.1 sound!
Well, I thought I'd let everyone know that I've uninstalled all my favorite apps from my Kaiser. No MSVC, no S2U2, occasional hands-free Bluetooth, and no A2DP. In that time, I've had only 2 incidents of no sound for the last 3 weeks--much better than no sound every few days or even several times a day. Don't know that the apps have anything to do with it since denco7 had same problem on an unadulterated AT&T ROM.
The big question is why do we all have the same sound problem but most WM6.1 Kaiser users do not (if everyone did I'm sure there would be a lot more *****ing). If we could reproduce it at will, we'd at least have something to focus on. Not knowing that, I'll have to guess and say that I suspect one or more of the following:
WM6.1 and/or the 1.65+ radios required for WM6.1 introduced some sound bug (deadlock, dereferenced pointer, etc.). The more apps that interact with sound and/or the radio, the more likely the bug will be triggered. But even if this is true, why does it happen to us but not to others?
The bug exists only in a particular base ROM source used by the ROM cookers. Still, should be affecting more people.
Maybe people who customize their phones are more likely to reset and clear any conditions that lead to no sound? Doesn't seem likely, but hey...
The problem exists only in specific Kaiser versions, perhaps even in conjunction with only specific WM6.1 builds and/or radios. I think there's been 5+ different hardware versions of the Kaiser line, but I can't find where I read this or how to tell what version your Kaiser is.
Bluetooth affecting sound? Got absolutely nothing to back this up other than WM6.1 supposedly fixed a lot of Bluetooth problems and during the time of my frequent lockups, I was using A2DP to stream an audiobook to my car's Parrot MK6000. Finished the audiobook & quit traveling so much, so I rarely used Bluetooth during the last few weeks when I've had only 2 no sound incidents. BTW, I upgraded to WM6.1 specifically because of the Bluetooth fixes, hoping they fixed the 100% CPU usage after finishing a hands-free call and fixed the A2DP dropping after calls. WM6.1 didn't fix either, so what did they do? Maybe their "fixes" just introduced new problems?
Possible dead zone f'ing up the radio and consequently sound? I offer this only because when I was working in a particular dead zone I had frequent sound problems. For some reason, my phone has problems reconnecting after leaving this dead zone and I have to reboot. Occasionally it would reconnect without rebooting, but I never correlated this to no sound. However, I haven't been there in weeks, and my problems with sound decreased (although I also uninstalled apps & quit using Bluetooth as much). Went there last Friday, and while I was there I found I had no Windows sounds. Could dead zones or even just temporary signal loss be f'ing up the radio and consequently the sound?
These are all just guesses--I'm just throwing out some possibilities so we can find something in common between us. However, I gotta say that if I don't find a solution soon, I'm going to switch back to WM6. Threaded messages are nice, but they're not worth this no sound headache.
BTW, I'm using:
AT&T Tilt (purchased within a month of initial release)
ROMeOS v4.21.1 (OS v5.2.20273, AKU 1.3.3)
Radio 1.71.09.01
Hi guys,
I''m new to this forum and I'm also new to HTC Diamond. However I found great guidance to "upgrade" my MDA Compact IV to HTCs original patched rom (1.93.407.1 GER) and had a radio update to 1.00.25.05, but after upgrading to these versions with Hard SPL oni 1.30, my phone is experience problems with phone calls. Whenver I'm at a phone call either I my HTC looses signal so that I cannot hear my counter part or It simply disconnects. I'm pretty annoyed with this and I dont know what to do.
Would appreciate answer on If some one is experiencing simliar problems or on a guideline to how to "cure" my phone.
Thank you!
And btw I'm also having this problem where I cannot hear the caller nor can the caller hear me the first 2-3 secs. Is this due to my upgrade? Or is It a radio prob or maybe the rom itself?
i would suggest changing the Radio... although i havent heard of problems with this radio version before (i am using it too)
Thanks for the reply mugglesquop. Neither have I heard of anything bad regarding this version, but I'm a bit worried. Can It be also a hardware defect? And If you would suggest me to switch to another radio, which version would It be? If I perform an upgrade of radio I will need to re-install rom as well. Is this true?
My X1 has had problems with it's Bluetooth cutting out during calls ever since I got it. Even after a replacement phone and the new R3A firmware the problem persists. So now I am going the custom route...
Can anyone recommend to me a custom ROM for the X1 that has had improvements to the Bluetooth implementation?
jhbodle said:
My X1 has had problems with it's Bluetooth cutting out during calls ever since I got it. Even after a replacement phone and the new R3A firmware the problem persists. So now I am going the custom route...
Can anyone recommend to me a custom ROM for the X1 that has had improvements to the Bluetooth implementation?
Click to expand...
Click to collapse
Never heard any cook do BT differently exept base on differenr WM built. I do patch the driver w/ HD one such that Cyberon VC over BT works. I never had bt cutting out during call but sometime AFTER the call (and it's a well known issue to all HTC device)
Perhaps it is worth to try other radio (you don't have to change rom, just update radio). I'm really not sure, but radio probably contains Bluetooth drivers too. Is that right?
netbat said:
Perhaps it is worth to try other radio (you don't have to change rom, just update radio). I'm really not sure, but radio probably contains Bluetooth drivers too. Is that right?
Click to expand...
Click to collapse
When flashing generic ROM you flash a corresponding radio (R3A with 1.14, R2A with 1.11 or 1.10). So this is probably no solution, but always worth a shot.
Diferent RADIOs are NOT the solution (I tried more than five radios).
I have tried more than 30 diferent ROMs in spanish and english, with WM6.1 and WM6.5, and no one go right with the Bluetooth.
I call Sony Ericson and they said that is normal because to save energy. It´s my first phones that disconect the bluetooth.
I've had all kinds of BT problems.
It usually turns of by itself, even in the middle of a call. (not so fun in the car, driving)
An I've also tried different ROM's and radios, no better.
BT is not very good on X1 I'm afraid... : (
mattiL said:
I've had all kinds of BT problems.
It usually turns of by itself, even in the middle of a call. (not so fun in the car, driving)
An I've also tried different ROM's and radios, no better.
BT is not very good on X1 I'm afraid... : (
Click to expand...
Click to collapse
Would you say that this problem affects all Windows Mobile devices? For example, if I get an HTC Touch Pro 2 am I going to have the same issues?
I have no idea really, I only have the Xperia.
Any htc owners here ?
jhbodle said:
Would you say that this problem affects all Windows Mobile devices? For example, if I get an HTC Touch Pro 2 am I going to have the same issues?
Click to expand...
Click to collapse
jhbodle said:
My X1 has had problems with it's Bluetooth cutting out during calls ever since I got it. Even after a replacement phone and the new R3A firmware the problem persists. So now I am going the custom route...
Click to expand...
Click to collapse
A friend and me, we both have the same problem as described by jhbodle since approx 6 months back.
During almost every call the sound is transferred back to the phone (as if I would have shut down the headset).
The weird thing is that bluetooth is still on and the headset is still treated as if it would be connected, meaning that I can still end the call by pressing the call button on the headset.
I can get the sound back to the headset (during the conversation) in two ways:
By choosing "Turn hands-free off" and then "Turn hands-free on" from the phone, or by shutting down the headset and then starting it again.
We have narrowed it down to that this happens whenever the phone disconnects from dataconnection (which seems to happen from time to time when using Activesync with Push - it disconnects and then directly reconnects). It does not matter if the phone is in 3G or GSM mode.
Have any of you noticed any similar problems during calls?
We are using the Swedish Telenor network. It might be possible that they have changed something that triggers the dataconnection to reset, and you on other networks are not beeing disconnected and therefore have not noticed this issue?
Maybe most of you are not using your dataconnections that heavely?
Those who are - could you test to disconnect the dataconnection while in call with TB headset..?
My friend have kept his phone with stock ROMs - he have had this problem with 3 or more different headsets.
I am flashoholic and have tried every ROM release from the top five cookers since the Hard SPL release for the Xperia. I have had the phone replaced once for a month ago - I have had this problem with both phones.
Hope you can help me to narrow this problem down even more, and most of all, I would like to know if we are alone with this problem..?
I have searched the forum for similar problems, but only found this one, so I did not want to create a new thread even if I it should be in the "General" category...
Oops... apparently I did not search enough - i have now found some other threads discussing this issue, but without any solutions.
I know that the most common BT issue for everybody is the BT deactivating itself after a call (I have had this from time to time aswell -especially after I have installed the MSVC software).
I don't want to start cross linking and dubbel posting, so I will wait and see if anybody has something to add to my previous post over here...
Would be nice to know if others, having this issue, can also link this to the dataconnection disconnecting.
How long are you talking on the phone for? I don't talk on mine for more than a few minutes, but occasionally I do get the 30+ minute calls that I have to deal with and I've never had blue tooth just shut off for no apparent reason.
For both me and a friend of mine, this happens during most calls regardless of the call duration (my calls usually take between 30sec and 10 minutes).
Sometimes, when I know that the conversation will take time, I reroute the sound back to the headset, but the same thing can happen again during the same call.
As I said, for me this happens whenever dataconnection disconnects on the phone.
Are you using dataconnection alot? Could you please try to disconnect the dataconnection during a call?
thanks