I recently upgraded the rom on my imate pda2k to 1.4 all was fine then during a GPS session the imate hard reset itself.
Since then i cannot connect to any bluetooth devices - i have 2 which used to be detected and worked fine and still do with an old 3870 IPAQ - a Navman GPS reciever and a bluetooth enabled nokia phone.
i have hard reset and rebuilt several times but cannot get the bluetooth detection working.
i have searched lots of forums and have already tried suggestions such as putting phone in flight mode, enabling BT and soft reset, also tried turning off IR
is it possible to downgrade the version of rom back to earlier version ? as that is the only thing i can think of that i have have not tried - and if so - where can i find a copy please
please can anyone help - i am really stuck now
thanks
IMATE Jam
I am using an IMATE Jam phone which also having the same prolem. When I am trying to swith on my Bluetooth it is asking me to swith off the Flight Mode. What is this? How can I Swith off this Flight Mode
Related
since installing radio 1.13 i have not been able to connect to GPRS using wap.voicestream.com. this is after a hard reset with none of the EXT rom tools loaded. i try to connect, and it times out. in 1.12 i would be able to connect once but after connecting to activesync or disconnecting GPRS i was not able to log back in unless i soft reset or turned on flight mode then turned it off. I have 1.40 ROM installed with phone alarm 1.21, pocket plus, and wisbar 2.4.11
UPDATE!!!
ok, i uninstalled pocket contacts 1.1 from www.pocketx.net and installed pocket conctacts PRO 3.0. i also unloaded mort ring. well when i did that i was not only able to connect to gprs, i am now able to RECONNECT when i disconnect! wierd...
What device do you have and what ROM are you running? I'm looking to solve this problem on my PDA2K.
i have the same device and ROM as you do. since i last posted. i am only able to connect to GPRS after a soft reset, not turning on/off flight mode
Downgrading Caller ID to IA_CallerID_1.20_WWE.CAB will fix this problem. It worked on mine at least...
downloading and installing the cab for the caller_id worked for mine as well. i've had no problems with gprs connections since performing the downgrade -- which was a little over a week ago. i think you can find the cab in these forums if you search for it.
i dont have that caller id sodtware installed at all and i still have the gprs reconnect issue
Hello there,
I have recently installed TomTom 3.01 with GPS update 3.07 and now I cannot connect my BT headset Bluetrek G2 anymore. Before the TomTom install everything worked fine.
I can still pair the headset using the setup wizard, but when it comes to finally connect it I get the error message "Failed to connect".
After hard reset and restore of system before TomTom install all works fine again. Seems to me TomTom somehow blocks the headset-profile.
I spent days reading through all the posts here, but couldn't find any answers.
If there's anyone out there who can help, any tips would be greatly appreciated.
Thanx
[/b]
You could try installing bttools.
Thanx for replying. I have installed bttools from this link http://bluetooth.i-networx.de/index_e.html , but it doesn't seem to do anything. It just appears on the today screen, but none of the buttons has any function. My guess is it only works when the MS-Bluetooth stack is installed (like on the Himalaya), which by default isn't installed on the Blue-Angle. But thanks for trying...
Cheers
Hi
Does anyone know how to setup IGuidance to work with WM5? I dont know how to work the BT ports at all. In 2003se, i could use the "scan" for bt data and it'd find the itrek gps unit but now it results in "no gps found". alternatively, what other gps software will work other than tomtom? I dont have tomtom =(
I've got version 2.1 and it seems to work with WM5. I add the gps to the bluetooth and then I create an incoming and outgoing port. I set my gps to port 6. In IGuidance it won't detect the gps but if you manually choose port 6 it will work just fine.
Andy
iGuidance 2.1.3 locks up my Wizard after several minutes. Grrr...
I am having all sorts of trouble with my PDA2K (WM5) and iGuidance. Although I think it has more to do with my bluetooth than anything. When I first started trying to get it to work it gave me coordinates that I was in Africa... Anyway, I think I am going to go back to 2003SE.
I'm having a different problem with iGuidance v2.1.3 on WM5. It installs and runs just fine. I use BT over COM6 and it seems fine. The problem I have is that the coordinates are off. The strange thing is that when I run GPSInfo (a separate app) it shows the correct coordinates - iGudiance thinks they are different and thinks I'm in a different location ( a few miles away).
I gave up on it and decided to go back to 2003SE (iGuidace v2.1 that worked perfectly fine on that configuration a long time ago). I followed teh steps to format/clean hive and did the down grade but am having a different problem. I've seen other people running into similar issues but I've not been able to get around it
"BTTrayCE - bluetooth can no longer be used because the license has expired" - I have tried a number of things using different BT stacks, 2003SE builds, reset (soft+hard) etc. Same problem!!! Argh - I'm stuck. I really miss my GPS!
Hi krille,
I also had similar problems with my SX66 and iGuidance and finally decided to go back to win 2003 because it worked fine with it. In WM5 my BT GPS receiver was never able to make a connection with iGuidance. But now I am having a different problem. I cannot downgrade even though I followed all the instructions correctly posted on the BA_Downgrade page. The upgrade program ( MaUpgradeUt_noID.exe ) does not seem to identify the rom versions and though it gives me a successfully upgraded message nothing had happened. I cannot downgrade now and stuck with WM5. Did any of you experience this when downgrading and can offer me any help.
DEK.
I've been upgrading/downgrading with differnt ROMs without any problems
Make sure to disable activesync on the pc and copy the nbf files as described in http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5. Sometimes the verion info update to/from doesn't show between WM5/2003SE...
What happens when you click Update to continue?
BaUpgradeUt.exe worked
Thanks for your reply. I followed all the steps as described in the link you have sent but MaUpgradeUt_noID.exe did not upgrade (downgrade to 2003SE) though I got a message saying it did. Then I tried the file BaUpgradeUt.exe in PH20B folder and it did work. My device data file says my SX66 is in fact PH20B1 though. I do not know why MaUpgradeUt_noID.exe cannot update my ROM. Anyway I am happy now with my WM2003SE and iGuidance and BT all work faster with ROM update to 1.40. Now I am planing to customize my ExtROM to have all my personal settings and programs so that I want feel bad not having WM2005. Thanks for your willingness to help.
DEK.
Hi i have pda2k ROM 1.40.00 (latest version). Many times when i open bluetooth it says bluetooth cannot open due to insufficient driver memory reset ur device and try again. Can any one help me please.
Thx
Reboot your device, turn bluetooth on, and leave it on.
Hello everybody,
I am using ARHD since v9.x (don't remember the exact versin number) and moved to JB as soons as it was released.
Since ARHD v17.0, I experience bluetooth heratic connectivity to my car phone system.
My OneX and my car are paired but it takes more and more time to have them connected.
In v17.0 it took about 3-5mn to connect, this morning, with v18.1, it took about 20mn...
I tryed the following :
upgraded the firmware to 1.39
"superwiped" and re-installed ARDH 18.1 rom
cleared the bluetooth entries in both the phone and the car configs
No improvement.
Is there an issue in the BT module since v17.0 ?
Does anybody else experience the same issue ?
Well in two words : "help, please !"
Thanks in advance.
No one else ?
Come on guys, no one else experiences the same issue ?
I'll try to investigate further by myself:
Check the car BT system with anoter phone
Check the phone with a BT connection to a PC (I don't have another BT headset)
Install another custom ROM, e.g. cyanogenmod
Revert back to the original HTC ROM
Well, several tests later... Still facing the same issue.
If i erase the BT profile from the car audio system and the phone, then re-associate them together, the connexion occurs within 30sec !!!
then shut off the car and switch it on again... Both the car and the HOX are trying the connect for several minutes.
I will try to reset the phone when the new version of ARHD (18.2) will be released.
Checked BT connexion between HOX and a PC and another phone
-> connection : ok
-> stop / start : ok
No pb found on HOX side
Checked car with 2 differrent phones (wiko cink slim and lg gt505)
Car does not find any of them...
Even when I stopt any BT connection from the car interface, the BT system retart the phone search...
I'll have to call VW...
So, there is no bluetooth issue in ARHD 17.0 .. 18.1
Unfortunatelly, I have an issue with my car
Topic is closed