Related
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.
I'm having a problem when someone calls, I can't hear them but they can hear me. Once I soft reset, everything's peachy. Just today I used my phone (pda2k with i-mate 1.40 rom) several times. Everything was fine. I turned the flight mode a couple times today. Then, I turned on flight mode, let the phone sit for a while and had an incoming call...I couldn't hear them. I told them to call back in 5 minutes. I tried calling another number but couldn't hear anything, did a reset and everything was fine.
This has happened before and after the 1.40 upgrade. Anyone have any reason why?? I've tried turning the flight mode off and back on, but that didn't help either.
Thanks,
Tom
This is an known issue in 1.40 ROMs, and currently there is no solution.
Dont blame ROM 1.40 because you also face this problem when using ROM 1.31
No solution so far but a trick's available here: http://forum.xda-developers.com/posting.php?mode=reply&t=22239
Solution
Delete Run_BTTrayCE_10.lnk from your Windows\Startup folder and soft reset. Now you wont have the BT icon on the tray bar, but you wont have the no sound problem. If you still need bluetooth you can start it from the Windows directory as BTTrayCE.lnk.
Have fun.
I don't know if this can help to solve the problem but I wanted to mention that I never had this problems when I was using vodafone, but after I changed the sim card this probleme occured
Solution
The Solution is TURN ON your BLUETOOTH and then TURN OFF your bluetooth.
Re: Solution
asim_ag said:
The Solution is TURN ON your BLUETOOTH and then TURN OFF your bluetooth.
Click to expand...
Click to collapse
Unfortunately for me this actually triggers the no sound issue! My device is fine until the first time I use bluetooth then I can almost 100% guarantee that the next call will be silent.
As stated before with the 1.40.00 rom, this issue is certainly linked to the Bluetooth driver, perhaps on use it is switching audio to their driver for headset use and not restoring it?
Are you using sbp Plus, because this application has issue with bluetooth. Try to close all application not to minimize them when you are done with it. Use PocketNav or Magic Button for that.
Re: Solution
ThExSenatoR said:
Delete Run_BTTrayCE_10.lnk from your Windows\Startup folder and soft reset. Now you wont have the BT icon on the tray bar, but you wont have the no sound problem. If you still need bluetooth you can start it from the Windows directory as BTTrayCE.lnk.
Have fun.
Click to expand...
Click to collapse
Can you tell me if the BT has to be started like you described when you use Tom Tom? Normaly Tom Tom starts the BT automaticaly when it starts. Thanxx
hi
I get this problem a lot when I've had the phone on silent or vibrate and then change it back. I think it mainly happens when I receive a call after this rather than make an outgoing one but after the 1st call even outgoing ones have no sound.
It sounds daft but after a couple of months where I reset whenever it happened I just by chance hit the volume slider & sure enough the in call volume was turned right down. It's worth checking as it's an easy fix for me!!
Kill process
The solution for the problem could be to not run the BT driver. Anyway it's possible to delete from startup the dirver and to run when it need (for GPS or headset...).. But is there a way to kill the BT process without reset the machine (that without BT in the startup does't run the driver) whit a simple "TAP" ?
Thanx... M.
I hope I put my Reply on the right forum, but however...
I recently bought a QTEK9090 via Ebay and also I have the "I can't hear incoming calls..." problem.
Radio 1.06.02 and ROM 1.22.ooWWE. I understand from the postings in this forum that only a few (approx 10 to 15) have a problem and the rest of the world does NOT.
Strange but due to this I am really thinking to replace it by a P910I, as a phone should be able to pick-up calls. I haven't decided because the 9090 is a great machine.
Doesn't anybody have a clue, even not the manufacturer ??
Hi,
i had the same problem. Than i followed the advice above from someone deleting the autostart BT and using the btray.lnk instead. Absolutely fine since then.
greetings
Using the XDA IIs.
Until we get a proper fix, I am using the manual Run_BTTray method to turn on the BT if I need to use my headset.
So what I do is, (a) normally, no BT tray, (b) to use my BT headset, use Run_BTTray to turn on BT tray, (c) use ATBluetooth to actually turn on and off the BT radio, and finally (d) soft-reset to remove the BT Tray when I'm done.
I know it sounds complicated, but is ok after I assign the commands to my buttons (XDA IIs, plenty of buttons!).
What about the pda2k UniDirectional Patch.sa.cab available on the clubimate site.
I had this problem with ROM 1.40 as well as with the previous ROM. I have installed this patch. I have not had this unidirectional problem since then but I am not sure if this will work in the longer term as I have installed the upgraded ROM and the patch only a few days from now.
Love to hear comments of other members who have tried this patch.
Kind Regards
srmz said:
What about the pda2k UniDirectional Patch.sa.cab available on the clubimate site.
I had this problem with ROM 1.40 as well as with the previous ROM. I have installed this patch. I have not had this unidirectional problem since then but I am not sure if this will work in the longer term as I have installed the upgraded ROM and the patch only a few days from now.
Love to hear comments of other members who have tried this patch.
Kind Regards
Click to expand...
Click to collapse
The patch works.... atleast I didnt get the no voice problem after the patch (touch wood :twisted: )
So, I've been searching, and this may be covered, but I seem to have the problem in REVERSE. I can hear the other party when using my BT headset, but they can't hear me! On one call, it'll work, then on another, it won't, and then it'll stop working. I have ROM v.1.40.00 and Radio 1.13.00 I don't know what I could do to fix this problem...
Any suggestion would be appreciated...Although I'm not keen about removing the BT tray from the startup, only to soft reset just to remove it...
Thanks,
Q
does this problem remains in the WM5 ?
I wouldn't know...I'm still on WM2003SE....BTW, I have a Siemens SX66.... Anyone? Please?
Hello everybody.
i'm very interesting to upgrade my M2000 to WM2005.
I've read many post on the forum.
The main issue seems to be the Bluetooth power off by itself
after 10 min of standby device.
As far as i know, on WM2003SE, there was a problem with "no sound"
communication when receiving a phone call. The only solution was
to let the bluetooth always On.
If i upgrade to WM2005, due to the bluetooth "auto-shutdown" problem,
does the "no sound" problem will come back again ?
With the latests patchs, WM2005 can be really used as a normal device ?
(phone calls, speed of WM2005)
Many thanks.
you can always edit the registry to leave BT on permanantly and can alkways downgrade if your not happy,
ive been usin WM5 for past 2 weeks and have encountered no problems on it so far *touchwood*
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