Hi all,
I tried to use the blueooth for the first time in ages and I get an error message saying the license has expired, then the bluetooth is turned off automatically.
I found some earlier articles about this problem, and they suggested a solution was to install the widcomm bluetooth driver, which the author posted as an attachment. I installed this and reset the device, but when I click on the bluetooth icon I just get the same error message as before.
In case my customised ExtROM was the problem, I installed the standard O2 1.11.169 ExtROM, but the problem is still there. This is wierd because I have used bluetooth under that ExtROM version successfully in the past!
Can anyone help me???
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:
After upgrading to 1.40, connecting to GPRS is hit or miss. When the problem occures it is normaly after the GPRS connection has been disconnected for a while, then when connecting again, I get the error "Cannot Connect". The only way out of this is to soft reset or turn ON then OFF "flight mode" (restart radio). The real problem in troubleshooting this issue is, I can not make it happen on a consistant basis, in fact, I can not duplicate it at all (it happens when it wants to). If you also have this issue, please offer any info you have on WHEN it happens or sequence of events that makes it happen.
Problem: "Cannot Connect" error when connecting to GPRS (all connection settings are correct).
When: ?????
Work around: restart radio
Note: This is not the same problem as "red phone button disconnects GPRS" ("Flags2") as discussed in http://forum.xda-developers.com/viewtopic.php?t=21972&sid=ff63b7f3db5fceffff1cd54fe61ffd27
the same for me!!
don't know why!!!
Does it seem to happen after a couple of hours after a soft reset?
Also, I have noticed turning flight mode ON then OFF only works for the next connection, after that I get the "Cannot Connect" error. A soft reset may work for several connect/disconnect cycles before it craps out.
Please post when it happens for you.
Got the same for a while now. Started to occur indeed after installing 1.40. My use is quite simple: an hour in the morning and an hour in the evening; in the evening it won't connect; soft reset and the thing goes again.
Did not found a woraround yet but will keep trying and share it with you if so.
XdaIIi - Cannot Connect GPRS
My XdaIIi is also giving the same problem. Turning Flight mode on/off gives some relief; buy only temporary. Compared to soft rest, this is far better. Why O2 is not providing any solution.
nraj
India
Norwegian devices with the 1.40 ROM is also having this problem!
Oystein
This seems to be the fix!!!!
efjay
Posted: Thu Jun 16, 2005 08:17
--------------------------------------------------------------------------------
I posted this before, I had the same problem with GPRS not reconnecting. Now i am able to use GPRS without any problem. My solution was to downgrade my caller id version to 1.20 build 17957. When i first upgraded to AKU_RC 20 was when i first had the problem, tried the later version RC21 and still didnt work. I tried this several times, only the caller id version being changed produced the problem. Try that and see if it works for you
_________________
Rom version 1.40 WWE
Radio 1.12
Ext Rom 1.40.147 (Cooked)
ftp://xda:[email protected]/BlueAngel/CAB_Files/Caller ID/IA_CallerID_1.20_WWE.CAB
Thanks to efjay!!!!!!!!!!!
What is the best way to update the Caller_ID cab? When I update, it tells me that it is available in ROM. Can it be done without doing a hard reset i.e. re-installing all over again?
You have to move the following files from \windows directory to a temporary location before installing the cab.
CallerID.dll
DisplayCID.dll
IA_CID_StartUp.exe
IA_CID_StartUp.lnk (From /windows/startup)
IACIDSync.dll
iacontacts.dll
After re-installation, change all the dll files in the temporary location to txt file. Softreset. You can then delete these files in temporary location.
Hope this help.
Chris,
I tried what you suggested but I still get the message re file windows/ai???.dll is in ROM. I do not have any of these dlls in the windows directory or at startup.
Please let me know if you have other ideas. Thanks.
SK
You have to use gsfinder or resco explorer to see all system files.
Anybody else try this or the people who did it before today, Is it still working? I have the same issue. I just applied this fix, but it is too early to tell if it did anything...
thanks for the replies
It worked for me! Thanks very much to everybody who helped to discover and post this fix. It saved me from having to downgrade my entire rom, because I was cheesed off with having to do flight mode off/on every time I wanted to connect to the internet via cellular line, which I do often, because I've got an old Genie SIM with free WAP (not GPRS).
I found the instructions easy to follow, and I didn't even need to use gsfinder or resco explorer - I just set File Explorer to Show All Files.
Cheers,
John
_____________________
I-mate PDA2k Model No PH20B
Rom 1.40.00 WWE from club-imate
Radio 1.12.00
Protocol 1337.42
ExtROM 1.40.176 WWE
BT Build 3990
Network: O2 UK
From with files in ROM
Next time install safemode, then install your updates in safemode.
Cheers!
This fix has worked great for me (xda IIi ROM 1.11.00 Radio 1.00.00 ExtROM 1.11.923). When prompted that certain files are in ROM or in use, simply changing the file name of the files in question did the trick. For the first time in a very long time of using the XDA II and now the XDA IIi, I can reconnect to GPRS without a hitch.
Same Problem Here. I am going to try the Fix now
Moving to caller id version to 1.20 build 17957 worked great for me. No more GPRS cut outs at all.
Working Good Here. even the Wifi reconnects very very Nice THank you
Problem solved!!, This upgrade works great, thanks!!!
beware newbie detected >>> so
i keep having problems with bluetooth on my spv m2000 actualy with 1.31 original rom. an error message appears from time to time and says:"the bluetooth radio failed to turn ON due to insufficient driver memory aviable. You must perform a normal reset before you can turn ON the bluetooth radio". when i bought this unit it had same problem same stuois message. i thought that if i put original rom 1.31 i can solve it. but as you see same problem. what shall i do ?
Unfortunately I think you are out of luck.. this appears to be a common and unsolved problem. Check out the wiki sire for the blue angel rom upgrades for some possible worl arounds. however none have worked for me. We all need a new bt stack for these devices...
so what the reall problem is ?
so what the reall problem is ? bad unit or ban software ?
half the problem solved ?????
i managed to get rid of the error "bluetooth radio failed to turn ON due to insufficient driver memory ". i deactivated all bluetooth services to gain more memory except HANDS-FREE service. so bluetooth is now activated
Now spv 2000 is not detecting the headset, a plantronics 2500 ( works fine with hp6340)
what to do now?
My thoughts are that its primarrily a software integration issue. Pehaps some conflicts with files in main and/or extended ROM...
Interesting idea to deactivate the services... how did you do that?
Regards
chris
cbrow51 said:
My thoughts are that its primarrily a software integration issue. Pehaps some conflicts with files in main and/or extended ROM...
Interesting idea to deactivate the services... how did you do that?
Regards
chris
Click to expand...
Click to collapse
so >> go to bluetooth settings >>> setings tab >>> service settings, take each one in particular, leave enabled only what you need
Hey All-
Rather then adding to the large Helmi thread, I figured it would be best to start my own...
In short today I upgraded from TuMa v1.3 to Helmi's new ROM: Helmi_BA_WM2k5_AKU_2.3_32mb_v1.rar
Everything went fine during the upgrade, I set the Operator Code to T%CID? which was retrieved by using GetDeviceData.exe and the upgrade went smoothly... but now the phone functionality doesn't work at all. I've tried with two different SIM's, one being a T-Mobile and the other a Cingular. Both just show no service when inserted, although if I place those SIM's into other phones everything works properly without issue and I get 'full bars' (I have another Cingular 8125 and a T-Mobile SDA).
Here is what I have done so far:
- Reupgraded the Radio to the latest rev 1.15
- Recreated the nk.nbf again with retyping the operator code
- Reupgraded to the ROM to Helmi's
- Reunlocked SIM with xdadev_all_unlock-v1.5.exe
... and still no phone service.
Any suggestions on how to get the phone functionality to work properly? Its pretty much useless right now...
Thanks!
tempie23
I'm not sure that T%CID is right for an operator code... I know for O2 UK it's O2___001 and I'm sure a T-Mobile code isT-MOB101, both of these are 8 digits... check you're devicedata output again and use the setoperator.bat to set it properly, then try again
It's all good clean fun
spkr4thdd
I have the same operator code T%CID? but only on WM5. When i use 2003SE it is DANGA001.
tempie23
I had such error on TuMa 1.4 but reinstalling the ROM helped for a while. Then I tried helmi's ROM and the problem gone. But a couple of days ago it appeared once and reflashing did not help. What I done is downgraded to 2003SE, did a hardreset and reinserted SIM. The phone came back to work. Then installed helmi's ROM again. Now it is working for a day without any trouble, HOPE it's gone forever.
Tried a few things...
I tried downgrading and then reupgrading, but it still is stuck. No phone service. Interestingly enough the LED for the phone doesn't even come on anymore.
Interestingly enough when I select the phone settings from the upper menu I'm getting a Popup message stating "The phone is not ready. Wait 15 Seconds and try again." Obviously waiting 15 seconds does nothing...
Any other ideas?
Thanks!
tempie23
sometimes (happened to me) the operator info corrupts when upgrading to WM5
copy the files attached to the update directory and run 'MaUpgradeUt_noID.exe'
spkr4thdd said:
I'm not sure that T%CID is right for an operator code... I know for O2 UK it's O2___001 and I'm sure a T-Mobile code isT-MOB101, both of these are 8 digits... check you're devicedata output again and use the setoperator.bat to set it properly, then try again
It's all good clean fun
Click to expand...
Click to collapse
No it is not, it sounds like he has the same SX 66 that I have.
The ID is = AT%CID?
I posted this in this thead Here
read my above post, it can happen to anyone when upgrading to any wm5, mine happened the very first time i upgraded (TuMa 1.3), i dont know how it happens, but it seems to be permanent even with further reflashes (haven't tried 2k3)
NO Service
Midget_1990 said:
read my above post, it can happen to anyone when upgrading to any wm5, mine happened the very first time i upgraded (TuMa 1.3), i dont know how it happens, but it seems to be permanent even with further reflashes (haven't tried 2k3)
Click to expand...
Click to collapse
HI.
Sorry for my post, but I did not "get" how to fix the "NO Service" error:
This is what I've done today with Helmi_BA_WM2k5_AKU3.5_v1.4.CF2 by baniaczek:
Hi all.
Today finally spent some time, trying to upgrade my Qtek 9090.
Everything went fine:
1st) Did a SD backup of my current settings;
2nd) Updated ROM with SetOperator to my Operator (got from getdevice.txt);
2nd) Updated without problems;
Then used the Qtek by 5 minutes (inclusively i did a phone call), after that could no longer get the "phone" working - exactly when I received a call, the phone "gone out" and never more. After several soft resets and hard resets the phone was always with "no service" message (but strangely, I could go to settings phone, and look for "the broadcasting" networks).
I swaped the SIM to another phone and it was working, never the less I got another working sim, but the problem continues (btw, I always have the PinCode disabled, and I remember now that I forgot to test enabling PinCode request!!!).
Then, just in case I downgraded the phone to W2003SE, again, and everything was working fine.
My radio was 1.12. So upgraded radio to 1.15, and started over again but with no sucess.
When I downgraded once again, the Qtek works fine with either RADIO versions or sims.
Has anyone got this "nice feature"?????
Is there any overcame solution? (My only missing test is to enable Pincode, and test if it works?)
tks for any help
I'm having the same issue here as well, tried the comm manger on and off and disable and enable it. Still makes no difference, someone please help me out, I can't get anyone to help me
Hi People, I've been away from PDA's for while, realized the error of my ways and picked-up o2 Stellar at the weekend, the 2nd one in week. Before doing anything I installed WIN 6.1,everything appeared to working fine, until I tried to transfer files from my N95 to the stellar via bluetooth, every time I tried I got the same error 'unable to connect, I can pair with any phone tried 4 different phones today and I can send from my phone to another but can't receive files. I have double checked all my settings they seem to OK so I'm at a loss. Before I take it back for a 3rd has anyone else here had the same problem or know what I'm doing wrong.
Any help and advice would be much appreciated.
ROM details as follows
ROM Version 3.29.206.0.WWE
05/09/08
Radio Verson 25.83.40.02W
BlueTooth Verson 2.0/2.0+EDR
Windows Mobile 6.1 Pro.
plaver said:
Hi People, I've been away from PDA's for while, realized the error of my ways and picked-up o2 Stellar at the weekend, the 2nd one in week. Before doing anything I installed WIN 6.1,everything appeared to working fine, until I tried to transfer files from my N95 to the stellar via bluetooth, every time I tried I got the same error 'unable to connect, I can pair with any phone tried 4 different phones today and I can send from my phone to another but can't receive files. I have double checked all my settings they seem to OK so I'm at a loss. Before I take it back for a 3rd has anyone else here had the same problem or know what I'm doing wrong.
Any help and advice would be much appreciated.
ROM details as follows
ROM Version 3.29.206.0.WWE
05/09/08
Radio Verson 25.83.40.02W
BlueTooth Verson 2.0/2.0+EDR
Windows Mobile 6.1 Pro.
Click to expand...
Click to collapse
I had a similar problem with a bluetooth dongle.
Start/Settings/Connections/Beam/Recieve all incoming beams. Make sure BT filesharing is turned on the phone (if you fileshare), also make visible. BT can be spotty sometimes and these settings can be reset to default if the phone is reset.
nufsaid said:
I had a similar problem with a bluetooth dongle.
Start/Settings/Connections/Beam/Recieve all incoming beams. Make sure BT filesharing is turned on the phone (if you fileshare), also make visible. BT can be spotty sometimes and these settings can be reset to default if the phone is reset.
Click to expand...
Click to collapse
I forgot the setting 'Receive all incoming beams' now that has been set, everything is OK. Thanks
Had the same problem. Set to visible, receive all incoming beams etc. but I could only send, not receive. I solved the problem by activating Bluetooth Explorer and Activate File sharing. Strange since I didn't have this problem with WM 6.0 and BT Explorer deactivated.