Related
I have a very strange problem and i would like to know if anyone has the same or its just me.
Firt of all i have Qtek 9090 ROM:1.22.00wwe,radio:1.08.00,Extended Rom:1.22.167WWE.
When i try to start bt i get an error message saying that"bt failed to start due to limited memory for the driver.You have to restart your device in order to begin using bt"
I restart the device and everything ok.But if i turn on wifi open a few progs then turn power off(to ppc) when i turn ppc on i get the same message.
NOTE:No programmes installed.Clean device.The problem was the same even before upgrating radio version to 1.08.00.I have bt version 1.0.0 build 3500
but no change to the problem even with build 3900. :x
I have the same problem - you'll get used to it
PEACE AND B WILD
Hi,
I also have the same problem, I am not sure if it is 108 or 3900.
Simple
At least im not the only one.I am starting to think that it's a hardware problem .But what really makes me mad is that i payed 950euros to have this problem :evil: My previous S100 worked like a charm :roll:
Hi,
I just upgraded to 1.40 rom and noticed that once I turn off wireless from the wireless manager, i can;t turn wireless back on until I reset the device. Is anyone else having this issue?
Thanks,
Skumky
Yes and no.
I've experienced the same problem, but I've also had it with 1.12, 1.22, 1.31 and 1.33 too so I'd comfortably say it's not specifically related to 1.40.
I've also had this problem with the following radios: 1.02, 1.06.02, 1.08, 1.10 and 1.12. (I like to upgrade hehe)
Sorry that wasn't much help, but really just trying to say I think it's more a bug with the operating system itself and not a specific version. Perhaps combination of software affects it and thus you've never had it before. I don't know :-(
I have also upgraded to 1.40 and the wi-fo worls perfectly. I dont face your issue.
I have also upgraded to 1.40 and the wi-fo worls perfectly. I dont face your issue.
I've experienced this with the 1.40 and 1.12 radio.
No problems to report here about the WiFi-module. Works fine. Is it related to the security-level that you run on your WiFi-network? I use an 64-bit WEP-encrypted protocol, and leech on open networks , so more then 64-bit it won't get. Maybe an increased security-protocol causes the system to hang?
No problems here. I did have that problem in an earlier rom combination however.
1.40 WIFI
I had the same problem, so I ran the WLANPatch.CAB from the Cingular update. This cured the problem, so I put it in my extended ROM and did hard reset but the problem came back. As a temporary solution I just rerun WLANPatch.CAB after Hard Reset and no problems so far..
I have that problem all the time. When my wireless manager reads "not connected to network" before I turn it on, it usually works, but after I've turned it on and off again it says "wireless off" instead, and then there's often no way to get it to work again.
I have a feeling this is caused by Omega One Battery Pack's custom "ok" button - I guess it closes the app in an incorrect way. What I usually do is tapping Start->Today instead of "ok" to exit the wireless manager after I've turned wireless on or off. This seems to solve the problem most of the time.
same problem here as well. Was trying for the last hour to turn wifi on, no go. Did a soft reset and wifi was already enabled when it startled back up. This has happened to me with previous roms as well. Guess its a "feature" of the phone.
SBP Pocket Plus will cause this also (customized close)
Has anyone tried my suggestion? Make a habit of just tapping "start :arrow: today" instead of "ok" each time you use the wireless manager and the problem should occur a lot less. If it does occur, the only way out seems to be a soft reset.
Also, does anyone know of a more structural way of actually solving the problem instead of working around it like I do?
Yeah. Don't turn it off!
Don't Turn it Off..
The only problem with that is that when you drive down the road, it tries to connect to everyone's wireless network and keeps popping up those ' Do you want to connect to John's' network' boxes...
Exactly! That's the fun part! And around 70 % of those networks, at least here in Norway, are totally unprotected! :twisted:
Ah!... so now I understand what "free internet" means in those Norweigen commercials :wink:
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.
Have a weird problem and wanted to see if anyone knows a fix.
I have siemens sx66 running wm2003
When using the phone through out the day the phone part of it stops making and recieving calls, even a reset wont fix the issue, after about 5 mins it will reconnect to the network and start to work fine, this happens about 5 times a day. It is not a reception issue since the phone worked fine in my house for the last year, it just started happening.
I upgraded to Helmi AKU3.2 1.3.2b windows mobile 5 and it seems to be more stable. Now when i lose the connection with the network a softreset will allow it to reconnect back to the network. One time when it disconnected i went into device information and for radio rom it said NONE, could this have something to do with the problem, is the phone deleting the radio rom or not seeing it sometimes?
Update:
To try to fix this issue I first smacked it a couple of times, this did nothing to resolve the problem, I then took the entire phone apart to see if there was anything broken, after noticing nothing I smacked the phone a couple of more times. After putting the phone back together the issue is still there.
doing a soft reset when "Radio: NONE" pops up seems to be the only solution.
btw, have you upgraded to Radio 1.15.00?
Hi all.
I'm facing the same issue.
Since I upgraded to Helmi's AKU3.2-1.3.1 I noticed, that the Radio Stack suddenly is lost. You will get no error message. Switching the BA on you will note that the Radio Icon has an "!". Soft resetting will not work. But strange enough, if putting th BA into craddle (or using an USB cable for syncing/charging) and then soft resetting will work, the radio unit is re-enabled again.
I'm now on AKU 3.2-1.3.2 and the issue still exists.
Unfortunately you cannot reproduce this behaviour. Sometimes it happens, but you can be happy and the BA is working for day's without any trouble.
Beside this: the BT stack performance is the worsest I ever met. Just noise, jitter and a very short range using my Headset (Plantronics M2500)
I will try AKU 2.6 this weekend hoping it will be more stable.
yes upgraded to radio rom 1.15 from 1.13 hoping it would fix the issue. Do you guys think the issue is hardware or software?
dr.x
You may want to downgrade from 1.15. There have been several reports in different posts that 1.15 presents several random problems. I installed it for about 2 weeks, but then my phone started making sounds like screetching metal, which led me to believe that I had a loose wire on the speaker or something like that. Then, I remembered about some people complaining about this Radio, so I decided to downgrade. Have not had that problem again. Moreover, I seemed to have weird reception problems in areas where I normally had good signal as well.
All in all, my bets are towards the Radio rather than the BA itself. So, downgrade your Radio and stop hitting your BA before I have to call "BA Services" for domestic violence :wink:
Hope this helps!
dr.x said:
yes upgraded to radio rom 1.15 from 1.13 hoping it would fix the issue. Do you guys think the issue is hardware or software?
Click to expand...
Click to collapse
Hi.
I upgraded to Radio ROM 1.15.00 long time ago und as it worked fine.
As I mentioned before, i faced the problems with disappearing Radio Unit first after I upgraded to AKU 3.2-1.3.1
So I suppose, it will have to do with this ROM Version (AKU 3.2-x.x.x)
Regards
Chuck
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