Occasionally when I try to turn on my Bluetooth I get an error saying :
"The bluetooth radio failed to turn on due to insufficient driver memory available. You must perform a normal reset before you can turn on the bluetooth radio."
If I do a reset it's fine, but it's a bit annoying.
Any idea why this happens or what I can do to stop it ?
It's a bug in the current firmware of the device, should be corrected in the next release. There have been discussions of a new version in Beta which you "may" be able to obtain from a BT repair centre
ozymandias, you wouldn't happen to be running spb pocket plus, would you?
yes
think that's ur problem. Check out this thread (especially near the end of the thread):
http://forum.xda-developers.com/viewtopic.php?t=16146&highlight=
Related
I have a qtek 2020 with v1.52 rom. I downloaded the new Italian rom (1.72.04ITA) from www.windowsmobile.it and I tried to upgrade it.
After erasing internal rom the upgrade process stopped with a fault message:
Error 112: ce rom update error
Now the display is dark. I can read “serial” or “USB” on it.
What’s happened?
I tried again 10 times but nothing.
It seems that connection between pc and qtek wasn’t correctly established. This because the little activesync icon (bottom right) is now always gray, never green.
Help me please!
Hm...
When OS is not started, PC ActiveSync cannot connect to your device, i think this is indeed...
But open Windows Task Manager and kill process wcescomm.exe (this is that tray icon of ActiveSync) and try to run update again...
HTH
> open Windows Task Manager and kill process
> wcescomm.exe and try to run update again
I tried but nothing.
I also tried to execute XDAtools but I recieved the following message:
Cannot execute the remote communication program.
Please make sure that USB/Serial cable is properly connected.
What can I do?
Does your device changes the screen from "Serial... blablabla..." to "USB... blablabla..." when you put it into cradle?
If so, what update writes when you try to run it (after putting device into cradle and killing activesync)?
> Does your device changes the screen from
> "Serial... blablabla..." to "USB... blablabla..."
> when you put it into cradle?
Exactly
> If so, what update writes when you try to run it
> (after putting device into cradle and killing ActiveSync)?
I can read following messages:
* Message 1 *
Cheking info on your pocket pc. Please don’t disconnect.
-----------------------------
* Message 2 *
Your pocket pc software is about to be update from:
Device CE image version: (now this is blank, the first time I attempted the upgrade was 1.52.00ITA)
Device CE extended image version: (now is blank, first time was 1.52.93)
Device Radio image version: (now is blank, first time was 1.06.1)
To
CE image version : 1.72.04
Extended image version: 1.72.128
Radio image version: 1.14.00
-----------------------------
* Message 3 *
The current software is being erased
Stage1: erasing ROM. Please wait
(But bar will stay at 0%)
-----------------------------
* Message 4 *
(After 2 minutes)
Error 112: ce rom update error
Any ideas?
Stupid question, but do you have pluged charger to cradle? I assume that so...
On other hand, I searched through this forum and found this links:
http://forum.xda-developers.com/viewtopic.php?t=10333
http://forum.xda-developers.com/viewtopic.php?t=8835
HTH
I tried, but nothing.
Anyway thank you for your reply
Hm... I was solving this issue yesterday and try to download update again (some corruption may come when update is downloaded) and flash it again...
I did it. I downloaded and tried also other international rom version, but nothing to do.
I’m going to call the costumer service ...
This is strange... :evil:
Unhappy, we are so far from each other... I want to help you...
Do you by chance have your cradle plugged into a USB hub? There have been many reports of problems in this configuration.
If so, try it with the QTek cradle plugged directly into the computer.
If not, a call to the service center may well be in order.
> we are so far from each other...
> I want to help you
You are very kind. But I live in Rome ...
> have your cradle plugged into a USB hub?
No, it is plugged directly into pc
Service center seems to be the only chance
:roll:
Me too..
Hi!
Just experienced the exact same thing :-(
I hate it!
I has done it one time before, and then I had to send it in to be repared. I dont know what they do, but I got it back working again.
But now when I saw the new official 1.72 rom, I wanted to give it another try.... but... now its dead again, doing the exact same thing as yours...
any news?
Regards
Peter.
You are very unlucky.
Today I’m going to call service center.
I hope they’ll solve problems quickly.
I’ll tell you what’s goin’ on.
Working!
hey!
I actually got it back to life!!
I took a different PC, connected my qtek and just started the upgraded again, even though the activesync wasnt connected. It started to upgrade, and my Qtek is now back to normal with 1.72!
Try if you can, with af different PC...
Today my service center replyied to my email regarding this, sayning that they couldnt help my, and there was no guarantee since i tryied to upgrade my self :-(
So, good thing i did it my self
I was thinking about it because I had some problems with usb ports on my pc. So this morning I tried the upgrade from another pc and ... YEEEAH.
I make it !!!
Now qtek 2020 works again !!!
Yeah!
Congratulations!
Good thing we have this forum
Experienced any problems with the upgrade yet?
yes.
still problems with bluetooth connection: no signal available from gps reciever. :shock:
problem solved by downloading bluetooth tools from:
http://bluetooth.i-networx.de/index_e.html :idea:
now it works fine.
bye
hi,
i just received my o2 xda 2, i decided to upgrade to 1.60 when i saw 1.72 it's out:
1st quest:
where could i find 1.72?
Does the qtek one works with my xda?
thnx
ciao mario!!come ti va col gps BT e tomtom3?
Hi!
I would definetly not try to do any upgrade as long as the upgrade isnt directly comming from your service center. All the XDA upgrades I tryied on my Qtek didnt work at all...!
Be carefull!
Hi all,
I have a strange problem: bluetooth manager works fine after a soft reset. I can my PPC the whole day and it will always start normally (read: the screen that shows BT shortcuts shows up). The problem occurs when I turn off the phone over night (flight mode). The next day I can't get the BT manager to show the shortcuts screen - BT can be switched on and off but neither the BT manager or the BT settings screen will show up (there is no error message!!!). After I do a soft reset everything starts working...
Has anyone come across this kind of a problem in the past? I couldn't find anything using search on this forum...
My device info is (DutchRetail ROM):
ROM: 1.40.00 WWE
Radio: 1.13.00
Ext ROM: 1.40.556 WWE
I have tried uninstalling almost all extra software that I have installed after a hard reset but the issue is still here.
Thanks for all suggestions on what else I can try.
Hi Poga,
Yep, I get exactly the same problem :-(
AndrewB
ROM (i-Mate) 1.40.00 WWE
Radio 1.12.00
ExtROM 1.40.176
Hi Poga,
Yep, I get exactly the same problem :-(
AndrewB
ROM (i-Mate) 1.40.00 WWE
Radio 1.12.00
ExtROM 1.40.176
Do either of you have Goodlink software on your device?
same problem no goodlink
Same problem but no goodlink software
I also get another funny problem where sometimes I go to connect to my bluetooth access point from my phone and it just has the little pie icon saying it's doing something, then it stops and it hasn't connected (the connection icon stays the same) and I can't make any sort of connection. It then does this everytime I try to connect.
I don't know how i fix it, but I combination of many soft resets various flight mode turn ons and fiddling it eventually works. It's very frustrating and it's happened on every software version. Right now i"m running 2.04.00. I have a CDMA from Telecom NZ running radio HA_01_151 right now (but I've tried other radios).
Somebody else had this problem I noticed but nobody replied to his posts.
I've got the same problem I hope someday that someone makes a fix for it. I run the XDA IIs BlueAngel 1.40.00 Asian O2 ROM WWE. =/.
Same problem here - only solution I had was to go into settings/memory and then stop all programs running - then the bluetooth manager appears without the need for a softboot..
Pain in the arse. :!:
poga said:
Hi all,
I have a strange problem: bluetooth manager works fine after a soft reset. I can my PPC the whole day and it will always start normally (read: the screen that shows BT shortcuts shows up). The problem occurs when I turn off the phone over night (flight mode). The next day I can't get the BT manager to show the shortcuts screen - BT can be switched on and off but neither the BT manager or the BT settings screen will show up (there is no error message!!!). After I do a soft reset everything starts working...
Has anyone come across this kind of a problem in the past? I couldn't find anything using search on this forum...
My device info is (DutchRetail ROM):
ROM: 1.40.00 WWE
Radio: 1.13.00
Ext ROM: 1.40.556 WWE
I have tried uninstalling almost all extra software that I have installed after a hard reset but the issue is still here.
Thanks for all suggestions on what else I can try.
Click to expand...
Click to collapse
cw6447 said:
Do either of you have Goodlink software on your device?
Click to expand...
Click to collapse
I do and I have the same problem. I've been suspecting that it may have something to do with that because when I reset and I can start the manager just fine before I start Goodlink, but after I start goodlink it's a pain. Once, I tried to start BT manager then it didnt... i forgot all about it then suddenly some 11 hours later it just popped up by itself. Goodlink had been running continuously.
Any ideas???
I sometimes have the same effect.
What I usually do to resolve it (without soft reset):
- I installed PocketNav (kills programs which run in the background)
- I select 'Close all but Ative' in PocketNav
Then the Bluetooth Manager works again.
Hope it helps.
A
This is due to memory limitation in WM2003SE. When it finds that the memory is not sufficient it wont run Bluetooth Manager or Wifi. I had this problem a lot until i have shifted to WM5 which has more than 100 mb when the device starts. I guess that is why M$ has built WM5 for that reason and also for persisten storage of course.
The "memory limitation" is indirectly the problem. The Goodlink, which is more than three times the memory hog as any other 3rd party app out there, is the direct problem. I could write a college discertation on the amount of bugs in this awful software. And yes, it is good for push email...but at the expense of everything else that is good about these multimedia devices we own. The typical "close-when-you-tap-the-X" software utilities don't shut down Goodlink on my device even though they successfully shut down every other software I own (over 40 titles). So I have to use MemMaid to kill its process. But Goodlink will restore itself in a matter of minutes as it ventures out to the server looking to synch mail, calendar, contacts. If there was ever a reason to bring back public hangings, it would be for the Goodlink windows OS development team.
I don't really see any issues with Goodlink eating my memory. Then again, I've converted from a strictly fun user to a strictly business user so the whole gaming and multimedia thing doesn't quite do it for me anymore.
Steiner,
I tried PocketNav to see if it would truly close GoodApp.exe. Although it does seem to shut the application down, the 6+MB exe still is open in memory. Using MemMaid it shows that it never really closes.
I also didn't have the Goodlink software installed . My solution to the problem was: I installed the Sprite Backup software and set it to automatically restart my PPC @ 6 am after creating a backup. So in a way, this problem was very benifical to me - I now have a fresh backup of all the software every morning and the device reboots every morning without my intervention (no BT errors, no WiFi errors, etc).
poga said:
I also didn't have the Goodlink software installed . My solution to the problem was: I installed the Sprite Backup software and set it to automatically restart my PPC @ 6 am after creating a backup. So in a way, this problem was very benifical to me - I now have a fresh backup of all the software every morning and the device reboots every morning without my intervention (no BT errors, no WiFi errors, etc).
Click to expand...
Click to collapse
Good idea!!! :lol:
Hi,
I have just hard reset my xda zinc. The bluetooth works after sometime I got this error:
"The Bluetooth Radio failed to turn ON due to insufficient driver memory available. You must perform a normal reset before you can turn ON the Bluetooth Radio."
I've already soft reset a couple of time and I've search for solution on existing thread but none is related or even close to this one. Please advice.
prob solved
sorry, it's my fault i've deleted the BTTrayCE in the startup.
Okay, I've searched alot to get this thing solved. When I try to update my rom, the update starts normally, but then my telephone screen turns black, my gets disconnected, windows tells me it has found new hardware. The update failes and returns error 260 (connection lost). When I soft-reset the telephone afterwards, it returns to it's old shape.
Info about my telephone.
Rom: 1.93.404.1 NLD
Radio: 1.0025.05
PC: Windows XP SP 3, Active Sync 4.5
I tried to update with this rom: RUU_Diamond_HTC_NLD_2.03.404.3_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
I also tried to update to Hard-SPL but that gave me the same error.
PLease guys does anyone of you know how to fix this? (personally I think it's windows xp which is screwing up).
Thanks in advance, I appreciate all help.
Yours, Martijn.
Even the tiniest tip may help (A)
I had the same trouble with that rom, I tried from internal memory and it worked. Search the wiki I am sure the info is there.
"ERROR [260] : UPDATE ERROR
This error occurs when there is an "open port error" before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again."
This is what the WIKI tells me. But I have tried that. How did you manage to perform the update on the internal storage? Because I tried that with hard-spl but it wouldn't work.
Besides I only have .exe files for the Hard-Spl and the official rom from HTC.
Thanks for your reply though.
EDIT PART, just read this on another thread in the wiki:
ERROR 260 (Update Error):
"Your phone is not connected to ActiveSync. Check your connection or restart the phone. Also make sure in ActiveSync that "Allow USB connections" is checked (under File->Connection Settings). If this still doesn't help, then remove the memory card and SIM card before flashing."
I'm going to try this now, if it worked, I'll let you know
Just found out I have a CDMA version or something, I'll try google for the problem now.
Get the rom image from your temp directory and look here, found in the wiki
http://wiki.xda-developers.com/index.php?pagename=Diamond_FlashfIS
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
dickenz said:
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
Click to expand...
Click to collapse
It looks alot like your problem yes. But last time the hardware installed correctly, then the patch I found for CDMA models on ppcgeeks failed, and my telephone got bricked. So I'll need to get that fixed first. After that I'll sure think twice before I try another rom update :/
Thanks for all the help though, and I have to advice everyone to not use the hard-spl for cmda users from ppcgeeks unless you're 100% sure it fits your model!
Hi i am new on this forum ,i have a qtek 9090 unlocked bought on ebay
it runs windows 2003 and when i try to upgrade to wm6 ,the process starts and and it goes into USB V2.08 and pc makes a usb has been removed sound and the installer gives me a error msg
ERROR 120:COUNTRY ID: ERROR
and when i do a soft reset it comes up with a new installtion of (wm2003 which i hate)
this is getting to my head as i need to upgrade my PDA
can anyone help me
send me some links with the correct software and stuff please
you need to put the device in bootloader mode before connecting it to the pc by pressing reset+power+record and use the MAupgradeut_noID instead of the BAupgradeut to upgrade your device. if you don't have the MAupgrade tool present, you can download it from this post of mine:
http://forum.xda-developers.com/showpost.php?p=3768875&postcount=3
by doing these 2 points, you can avoid all error 101, 110 and 120
windows 6 for qtek 9090
does anyone have links to the new wm6 for qtek 9090
try this: http://forum.xda-developers.com/showthread.php?t=482997
No service
upgrade done and the phone worked for about 3 days now is says no service and wont pick a network
first make sure you didn't soft-reset the device the wrong way, meaning restarting the device by releasing the battery lock, because restarting it like that generally starts the device w/o radio, meaning no phone function. to avoid that, simply soft reset again by pressing the actual hardware reset pin.
in second thought, you might wanna post the values shown in the boot screen, maybe another radio rom might do the trick.
if neither of that worked, maybe you should try another sim card or a different location for testing network coverage just to figure out, if it might have something to do with a network failure.
if still however nothing worked, which i wouldn't hope, it still could be a bug with the particular rom and you might try another rom.
and at last, if that didn't help, you might have a broken radio receiver and as a harware fault would require you to repair or replace the device, but that is rather unlikely, so you are probably lucky and can fix it yourself.
please post back if and when you figured out, what the problem was, so we can all profit and learn off it.
with best regards,
Chef_Tony