Bluetooth Manager ? - JASJAR, XDA Exec, MDA Pro General

Good evening all,
Has anybody else noticed a missing peice of software ???
I'm running my Exec on the latest 02 rom (1.13.188 WWE) and its running great but, when I tried to explore a freinds nokia I noticed that the Blutooth Manager wasn't there... :?: I didn't recall seeing manager there beforehand as I had picked up my Exec on the Saturday and flashed the new rom upgrade on the Sunday... :shock:
Can anybody give me a lil bit of help on this please...??
Thanx
The magman

the magman said:
Good evening all,
Has anybody else noticed a missing peice of software ???
I'm running my Exec on the latest 02 rom (1.13.188 WWE) and its running great but, when I tried to explore a freinds nokia I noticed that the Blutooth Manager wasn't there... :?: I didn't recall seeing manager there beforehand as I had picked up my Exec on the Saturday and flashed the new rom upgrade on the Sunday... :shock:
Can anybody give me a lil bit of help on this please...??
Thanx
The magman
Click to expand...
Click to collapse
Bluetooth Manager was a WM2003SE thing. It was "simplified" in WM5 (which is what the Exec runs) by putting everything under Bluetooth Settings.

Thanx for that Ineedtoy,
do you know if there is anyway to emulate that feature....? it came in quite handy sometimes...
Thanx
The magman

I guess that depends what you want to do. Is there something in BT Manager that you can't do in the Communication Manager (icon in bottom systray on Today page) and BT Settings?

Good evening Ineedtoys,
With wm2005 you have to option to connect to any bluetooth device just as you could with the earlier models but now, unless i'm missing it...
You no longer have the ability to explore those devices now as u could before...?
It is/was a very handy feature for certain circumstances..
thanx the magman

Ah, right. When you connect to a device from the Devices tab it automatically lists all the services available as tickboxes, you then just tick the ones you want to use in that profile. You can change them at anytime afterwards by tapping and holding on the device name and selecting Edit (even when not connected).
Is that what you want to do?

I know what magman is talking about. Under the Broadcom 3900 stack on my old 2i, there was an option of opening an Explorer style window detailing the files held on the destination device in order to search for a particular file. That doesn't seem possible on the Exec's MS stack - not that I can see, anyway.
If anyone knows of a way to do this on the Exec, please let us know.
Cheers
Ant

Related

GlobalSat SD-501 GPS will not work with S100, please help me

Hi guys!
Just learned of this forum, it might be my last chance.
I bought the GlobalSat SD-501 GPS secure digital receiver in Hong Kong. It was a big gamble and it turned out to a headache.
After installing the thing you are supposed to be able to see which comport it has received using the nifty utility "GPSInfo" from GlobalSat.
It is supposed to identify itself as COMX: MANF-0501-CARDID or something similar.
... but after loading the program I see the following:
COM1: Serial
COM2: Serial_Cmd
COM3: IrCOMM
COM4: BTIBserial
COM5: BTOBserial
COM9: Serial_Data
That is, nothing that resembles anything what I want. I tried to force select one of the following ports but of course that didn't work. There are also 3 different drivers to test, the one supplied on the cd and two on the developers site, found here:
http://www.globalsat.com.tw/english/download.php?level_id=3
I have tried all three drivers with no effect. I have also tried soft resetting after install and even a hard reset to see if that would solve any issues.Along with the drivers there is also a program called COMKiller that disables comports (after surfing found out that most IPAQ's tie up all comports leaving nothing for the GPS), I tried this as well with no success.
The LED on the GPS is supposed to blink when it has your location fixed, the device actually does that after a while so it seems to have a working hardware anyway - it just won't talk to the phone.
From looking at other forums it seems as this device work for people running the S2020 (the Himalaya) so maybe there is hope.
In summary this is what I have tried:
1. Tried all three drivers available from maker.
2. Soft resetting.
3. Hard resetting.
4. Upgraded ROM to the version described below.
5. Disabled IR (incoming beam).
This is what I have:
Qtek S100
ROM: 1.06.00 WWE
ROM date 01/06/05
Radio version: 1.05.00
Protocol version: 1337.39
ExtROM version: 1.06.115 WWE
Model NO.: PM10A
Maybe there is something in the driver that is trying to access the S100 in the wrong way, maybe it is trying to force select a busy comport. I don't know. Please you kind devs and others, can you maybe take a look at this?
best regards
Kristian
I querried this forum about this about a month ago and had no luck.
I have an o2 mini. When i plug the sd501 into the mini The light doesnt come on. My friend has JAM. When I plug it into the jam the light comes on but still i have not been able to get it to work,
If you find a solution please post
Could any of you smart devs please take a look at this, I would be eternally grateful!
/Kris
Krillo said:
Could any of you smart devs please take a look at this, I would be eternally grateful!
/Kris
Click to expand...
Click to collapse
Hi Kris,
did you already try on the forums you can find at www.pocketgps.co.uk ???
IMHO that is the best-gps-experts website; if nobody can help you there, you can put your receiver in the recycle bin
Sorry I cannot help you some more
Hi,
yes I have posted in that forum too - awaiting response. But I am sure this is solvable, it's not rocket science. Well, for me it might be but I know there are some seriously smart people here eager to give support
/Kris
being a bit a GPS expert myself as well as an S100 owner I have not found a solution so far to get this combo to work, which I guess is not that bad at the end of the day considering you lose the SD slot for storage unlike with say a Bluetooth GPS. I will certainly revisit when they send me the SD-502 with its 512mb RAM, small helix antenna and SIRFIII chipset for testing in a few weeks ;-)
GpsPassion -> Do you have some kind of relation with GlobalSat? If so, have you had any comments from them if they will try to make this combo to work or not?
I mean, I like the device and it would suit my needs quite well - and I bought mine so I must decide if I should sell it or if there might bew a solution sometime. Do you have any contacts?`
best regards
Kristian
Hello Sd 501 "victims",
searching through the net I ended up at this thread. I also would like to run my sd-501 with my magigian. Is there really no solution to that problem?
Stefan
hi
the drivers arent installed properly you should have on there manufactors card under the com ports. reinstall the drivers andf it will work are you using the disk that came with it as the drivers you down load dont seem to work.
kevin
Nice to see an old thread coming back to life. I for one never managed to get the 501 to work on an S100 and the 502 is following the same fate, looks like some SDIO issues at HTC...http://www.gpspassion.com/fr/news.asp?id=410
just signed up today and this is my first post! anyway i am having the same problem. i have been trying to get the globalsat sd-502 to talk to my Qtek s110 without any joy depsite expansys saying it is compatible.
i have tried the drivers supplied and those on the globalsat website. it cannot see any com ports other than those mentioned earlier in this thread.
i do know from a local guy who tried to help me out that he managed to get it working with his xdaii which was not comaptible but he failed to help me out on with the qtek. i think this is one that globalsat will need to look at.
its a shame because it locks on to satellites just as quick as my globalsat bt-338 but wont suck the battery dry as quickly the bluetooth does. i will be interested to here if someone comes up with a solution.
tebs said:
just signed up today and this is my first post! anyway i am having the same problem. i have been trying to get the globalsat sd-502 to talk to my Qtek s110 without any joy depsite expansys saying it is compatible.
i have tried the drivers supplied and those on the globalsat website. it cannot see any com ports other than those mentioned earlier in this thread.
i do know from a local guy who tried to help me out that he managed to get it working with his xdaii which was not comaptible but he failed to help me out on with the qtek. i think this is one that globalsat will need to look at.
its a shame because it locks on to satellites just as quick as my globalsat bt-338 but wont suck the battery dry as quickly the bluetooth does. i will be interested to here if someone comes up with a solution.
Click to expand...
Click to collapse
Sorry to hear about your problems - but, what software are you trying? A good freebie is VisualGPS CE, and does work with the SD-501 (i use said GPS reciever with my Blue Angel).
But unfortunatly, I think this problem is purely a HTC problem, not global sat. Remember, they made thier device compatible to the BSquare SDIO Now protocalls - if HTC decides not to follow that , then it is not GS's fault (though, it is odd that they would support the SDIO on devices like the II, IIs, III, but not on other devices..)
Divine im using tom tom 5 but as far as gps programs ive used both gpsinfo and winfast as someone on the pocketgps site suggested. yeh it probably is something that htc need to look at.
thanks to a bit of browsing on here ive downloaded a trial verison of phone alarm which allows me to use a single press of tghe tom tom icon to activate the bluetooth and tom tom in one go. exiting tom tom switches the bluetooth off and the phone so i can power the device down. this will keep me happy till someone comes up with a solution.i am going to return the sd-502 to expansys and ask them to remove the qteks110 compatiblity reference on their site

Could you guys please comment about my problem?

Hi All,
I seem to be having Bluetooth problems with my dutch t-mobile mda compact:
I am using a simple bluetooth headset - it's got no brand name - but I know it works fine beacuse before getting the mda compact I have used it with my Nokia 6310i and it works fine.
Anyhow, I pair the headset with my mda with no problem and it may work all day long without any problem - but... if for instance I leave the room with my headset - leaving the phone behind - which essentially disconnects the BT headset and the phone - when I come back the phone doesn't recognize the headset no matter what I do. The headset icon on the top of the phone disappears and oesn't come back. I reset the phone, I cliick on the headset answer button, I turn on and off the bluetooth on the phone, I switch on and off the headset - nothing helps!
The only solution that I found working is to delete the headset from the bluetooth devices in the mda and then rediscover the headset which works like a charm. All goes back to normal unitl the next time that it loses connection. I think the phone also sometimes loses connection when I am not using the headset for a long time (and hour or so)...
What can I do?? this is really driving me crazy. I have no problems when using the same headset with my nokia 6310i - but hey, I want to use the MDA!!!
My device: MDA COMPACT - T-Mobile Netherlands
Rom - 1.01.00 WWE
Radio - 1.00.10
Protocol - 1337.36
Ext Rom - 1.01.124 WWE
Thanks you guys for helping me
Ciao,
Lisa
hey Lisa..
i've noticed ur device informations are the following:
My device: MDA COMPACT - T-Mobile Netherlands
Rom - 1.01.00 WWE
Radio - 1.00.10
Protocol - 1337.36
Ext Rom - 1.01.124 WWE
they are too old :wink:
I have not experienced a problem like urs before,but i recommend u to upgrade ur device(the latest ROM version is 1.12.00,as much as i know :wink: ),u can find it in the ftp server,wich u can access from the wiki page(top left of ur page)...
if ur new to PDAs,then u have to know that ur device is a Magician,so search the ftp in the Magician folder :wink:
if u don't know how to upgrade ur device,u just have to ask,i will guide ur to the steps with pleasure
hope i've helped...
RAGO :lol:
Thanks Rago.
I was kind of wondering which one of the ROMs I should pick? When logging on to the FTP directory - there are lot's of shipped Magician Roms... Many show 112 - but which one should I take?
Is there any issue with the new Roms? Bluetooth problems?
Regards,
Lisa
hi lisa
best available workaround is to buy zenduris pocket zenphone software (do a search here at xda-developers). this program enables the headset profile permanently so your mda will be able to re-connect with your headset again, when you are back in the room.
cheers, lutz
Hi Lutz,
Thanks again for helping me
So you are using the word "workaround" - is this a known problem or it this just a problem with my device?
Am I to assume that there is a problem with the BT can can only be worked around and not solved permanently?
Does any of the new Roms solve this?
Bye,
Lisa
hi lisa
well there may be a rom that acts different but i won't force you to flash your device certain times with all the risks just to find out that it doesn't work! zenduris pocket zenphone really fixes the issue permanently and is definitely the best way to do it. i myself use the german o2 xda mini rom and it works well with my parrot ck3100 and reconnects with it the way it should while all the other (german) rom versions did not. but i guess you won't flash your device with a german rom, right...
cheers, lutz

BTW-CE 1.4.2.02 trouble adapting to XDA2i

Hi all,
i hope someone can help me with this, i got hold of an updated pocket pc bluetooth stack that i would like to get working correctly on my XDA2i Alpine. It's version BTW-CE 1.4.2.02 which is a massive upgrade from the 1.0 version on the Alpine. It adds a lot of new functionality etc.
It was originally for a Dell Axim but it should work fine on the Alpine, it's an updated stack of what is already there. I installed it on my XDA2i as per the instructions in the file, but did not update the registry keys. I no longer had any sound on the XDA2i at all but the bluetooth seemed to work pretty ok! :?
Then i removed all my old bluetooth keys from the registry and updated with the new registry settings included in the setup. I had full sound and functionality back then, but it could not load the bluetooth driver! It must be possible to have my extra bluetooth functionality with full normal sound by installing this package correctly but i need someone who knows more about it than me please?
File missing
I attached the bluetooth stack that i need help with to my post above so others can see and use it. Now it seems to be missing, did someone take it down? I can upload it to the ftp if i get access, thanks.
EDIT : Now it's there, must have been an issue with my browser!
what extra function you looking for in this stack indeed ?

Remote SIM Access Profile (rSAP) working on Orange SPV M3100!!

I've been looking around these forums for a while now trying to find a solution to the Orange/rSAP issue, and have finally found a solution...
I've basically just combined the instructions from various posts about various things to make this work, so i'll include all the info i found and try to credit people where necessary - apologies in advance if i've forgotten any, but i looked through so many threads and pages it was unbelievable!
Anyway, this is basically a step by step for getting your Orange SPV M3100 (and probably any Hermes/TyTn variance that has had remote SIM access removed by the provider) to work with a rSAP enabled accessory (the VW Passatt Bluetooth Premium kit in my case).
First, you need to change the TyTn's bluetooth identity to be a phone, or the rSAP accessory will not recognise it (funnily enough, bluetooth rSAP car kits don't look for pocket PCs). Here's how:
Download PHM RegEdit - it is important to use this exact program as due to Orange's stupid application locking it is the only registry editor i have found that can be installed.
Next, edit the following value:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SY S]
"COD"=dword:52020C (hex)
Bear in mind the new dword is a Hex value, so be sure to select "Hexadecimal" from the Base menu.
For reference (in case something messes up), heres the original value (the Pocket PC identifier):
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SY S]
"COD"=dword:1048852 (decimal)
Next, soft reset. For some reason i had to restart, change the value again (as it had reset itself), backup the registry and soft reset again for the change to take effect. God knows why, couldnt be arsed to figure it out.
Once this is done, you need to unlock and mount the phone's ROM. The easiest way i've found to do this is using the Fit4Cat Hermes Tweaker. The download will most likely require a forum signup, but its free so what the hey...
Use the hermes tweaker to unlock and mount the ROM, save and restart.
When the TyTn has restarted, if its worked you will see an Extended ROM volume in file explorer.
These files need to go in there helmi_c's SAP Test cab (you will need to unRAR first).
This was taken from the following thread: Helmi BA WM2k5 AKU3.2 Beta (v.1.3 Beta)
Cheers for that, helmi! You are a genius
After that, restart. If you do NOT have a new application in your Programs directory called SAPSettings, go into your Extended ROM and install helmi's btsap_test.cab file manually, then restart.
You should now have SAPSettings working fully:- just go into the app, click the enable button and away you go!
I hope this works for everyone, its worked on the 3 M3100s and the O2 XDA Exec ive tried it on so far with no problems so hopfully all is good.
Please post up your results here - itd be good to know the outcome
Cheers,
-JD-
Thank you
At last - I too am trawlling through these forums trying to put together a SAP package for the M3100.
Just one thing for the amateur here - how do you "unRAR" a file???
Thank you
p.s. I dont suppose you know if this will work on aC600 too??? I'll try it when I get a moment..
Better get a CIngular ROM and u hv built in SAP app
hdubli said:
Better get a CIngular ROM and u hv built in SAP app
Click to expand...
Click to collapse
That may be, but not if your pocket pc is company owned.
I should think that a lot of people wanting rSAP will have businessmobiles and probably business phone contracts too. Installing non-orange ROMs on an orange business contract pocket pc is NOT a good idea...hence this way around.
Theres always a reason
p4uly said:
At last - I too am trawlling through these forums trying to put together a SAP package for the M3100.
Just one thing for the amateur here - how do you "unRAR" a file???
Thank you
p.s. I dont suppose you know if this will work on aC600 too??? I'll try it when I get a moment..
Click to expand...
Click to collapse
To unRAR....get a copy of winRAR to unarchive the package
and i should thing the aC600 would work too as long as its on a WM5 Orange ROM.
Cheers,
-JD-
Same Problem with my VPA3 compact III and FWD Audio com
Hi all,
i´ve the same problem.
My CarKit "FWD audio com" won´t connect via SAP with my HERM200 Vodafone 1606 VPA 3 compact III. It always connect via 4 Char Code for talking. SAP Code (16 Char´s) won´t ask and so i´m not able to use the SAP-functions
I tried like the instruction from above.
At first I had the unrar-Problem with "helmi_c´s SAP Test cab".
Everytime you save it to disk, it´s not able to unpack.
If you don´t save it to disk and if you installed WINRAR, just
OPEN it und unpack it via WINRAR to HD ! Now it works.
Back to my Handy and the instruction
I was able to install everything, but if I start Install of "helmi_c´s SAP Test cab" in the Extended ROM there will be a message, that I don´t have rights to install !
I don´t know if the instruction will fix my problem nether the File is for my Fone, but I´ll try.
Does anybody can help me and answer why my phone won´t install "helmi_c´s SAP Test cab" ?
Can Cingular, which I don´t understand, help me ?
Fone: HERM200 Vodafone 1605 VPA compact III
Fone-ROM: 1.20.162.3
Car Kit: fwd audio com
I have a T-Mobile Vario II, and am looking into buying the Sony-Ericsson HCB-700 carcit. I have SAP settings in my programs, will it work ??
Scholle2 said:
Hi all,
i´ve the same problem.
My CarKit "FWD audio com" won´t connect via SAP with my HERM200 Vodafone 1606 VPA 3 compact III. It always connect via 4 Char Code for talking. SAP Code (16 Char´s) won´t ask and so i´m not able to use the SAP-functions
I tried like the instruction from above.
At first I had the unrar-Problem with "helmi_c´s SAP Test cab".
Everytime you save it to disk, it´s not able to unpack.
If you don´t save it to disk and if you installed WINRAR, just
OPEN it und unpack it via WINRAR to HD ! Now it works.
Back to my Handy and the instruction
I was able to install everything, but if I start Install of "helmi_c´s SAP Test cab" in the Extended ROM there will be a message, that I don´t have rights to install !
I don´t know if the instruction will fix my problem nether the File is for my Fone, but I´ll try.
Does anybody can help me and answer why my phone won´t install "helmi_c´s SAP Test cab" ?
Can Cingular, which I don´t understand, help me ?
Fone: HERM200 Vodafone 1605 VPA compact III
Fone-ROM: 1.20.162.3
Car Kit: fwd audio com
Click to expand...
Click to collapse
Did you install the Fit4Cat tweaker? Have a play with the options in it - from what i can remember, theres an some options about being able to install non-signed apps and rights.
If that doesn't work ill have a look for you.
Churchill said:
I have a T-Mobile Vario II, and am looking into buying the Sony-Ericsson HCB-700 carcit. I have SAP settings in my programs, will it work ??
Click to expand...
Click to collapse
Depends entirely upon whether the HCB-700 uses rSAP or HFP (hands free profile) to connect to your vario....
If it uses rSAP then chances are it will work, but without having used your exact kit i can't say for definite i'm afraid.
-JD-
Thanx for the info
OK - I have tried to load the fit4cat tweaker to the c600 - it doesnt work - neither does my regedit software - so it requires more cunning.
With the M3100 I could not load the PHMRegedit - instead i used Vidya which seems to have worked.
The car kit I am trying to pair with is a mercedes MHI - it has worked with my Nokia 6230i up until now.
The regedit doesnt have a HEX function but converting 52 02 0C into DEC I get 5374476 - however looking at the original post it could be 5202C - which means 335916.
I have tried 335916 - and at first the car kit sees it - dials the long number in-order to pair with the phone - but then dies. after a few attempts the car kit stops to see the phone.
I have asked some colleagues to try this with their Bluetooth Passats - I will report back on this later.
Also I will now go and try 5374476.
With helmis test CAB - I only got on cab file after un-rar'ing it. is that OK? also is it the latest version of the file?
Thanks
p4uly said:
OK - I have tried to load the fit4cat tweaker to the c600 - it doesnt work - neither does my regedit software - so it requires more cunning.
With the M3100 I could not load the PHMRegedit - instead i used Vidya which seems to have worked.
The car kit I am trying to pair with is a mercedes MHI - it has worked with my Nokia 6230i up until now.
The regedit doesnt have a HEX function but converting 52 02 0C into DEC I get 5374476 - however looking at the original post it could be 5202C - which means 335916.
I have tried 335916 - and at first the car kit sees it - dials the long number in-order to pair with the phone - but then dies. after a few attempts the car kit stops to see the phone.
I have asked some colleagues to try this with their Bluetooth Passats - I will report back on this later.
Also I will now go and try 5374476.
With helmis test CAB - I only got on cab file after un-rar'ing it. is that OK? also is it the latest version of the file?
Thanks
Click to expand...
Click to collapse
The reason you wont be able to get PHMRegedit and Fit4Cat to work is the fact that you're on a c600 rather than an M3100....
Anyway...the dec you're looking for is (as you stated you were going to test) 5374476 so that one should work...
What you need to do now is have a forum search for unlocking the Extended ROM on the c600 and the follow the instructions from there.
You should get a .cab file and a folder from the unRAR...
Yes this is the latest version of the file and works fine
-JD-
Testing
Right - have tried with both DEC values for the bluetooth and they both seem to work. Good so far.
Further Good News - It works with the Passat Car Kit - excellent
However when it comes to pairing with the Mercedes device (essentially a bluetooth dongle that plugs into where the phone cradle normally goes) the phone does not respond to the Car Kit when it dials the pairing number.
So I guess I'll post this on Helmis thread and see if there are any more tweaks...
where can you get a cingullar ROM from? has it been tried on a Hermes 100?
any luck
did you have any luck finding out how to pair with the mercedes bluetooth dongle. I can get Comand to see the device but it does not pair.
Mercedes Car Kit Not Working
Sorry - the Mercedes MHI (European variant) does not want to pair!!
I have tried my phone - with the tweaks in a VW passatt Bluetooth car - and it works.
I have tried my phone with a BMW I drive - and it is fine.
It also works with the Audi Bluetooth and a Nokia and Parrott Bluetooth kit.
So Mercedes have done something very odd with their kit....
And whats more infuriating is that there seems to be no way of asking mercedes techncial questions without the answer "that phone is not shown as compatible in the list".
Currently I am using the phone in speaker phone mode and have a pay as you go sim in the car kit for outgoing calls.
Apparently the U.S. Version of the MHI dongle is different - but I have not found anyone out there who has tried this threads update on a U.S module.
Oh well - here's hoping Orange release a ROM update tht comes out to update the phone in the future.
thanks for your reply
Doing the same with my T-Mobile phone and using a pay as you go sim in the car.
Really annoying.
I can't get it to work with the new Audi system. Have an Audi Allroad manufactured 10/06 with the new PT4 telephone system and a HTC Tytn.
Pairing it with the handsfree profile works and I can make calls and access the contacts in the Tytn.
Pairing it with the SAP profile also works but I do not get any network and can´t access the contacts in the Tytn. Tried changing [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS]
"COD"=dword:52020C (hex) but I get the same results. Have not tried the other tweak since I already have "SAP Settings" under programs.
Any ideas about what to do?
UPDATE: Tried manual network selection from the car and was very surprised when my network "Vodafone Sweden" showed up as available and some other networks as not available. When I choose "Vodafone Sweden" it tries to connect and then says "Network error". Could it be a problem with SAP and Vodafone Sweden? Will try my wifes sim when she comes home.
please has anyone found a solution to pairing with a Mercedes device?
Sorry
Sorry - No..
Although your phone says it has SAP already the file atached on the first page of this thread is an upgrade to the Bluetooth Stack - so please try with the file (you can always remove it if it doesnt work).
Hopefully that should then work.
Are there any particular functions you want to use via SAP that you cannot do with Headset Profile??
When I tried another sim (Telia) it worked! Talked to Telenor/vodafone and they said I should ask the car or telephone manufacturer what type of sim I should have, Telenor/vodafone has several different sims.
I want to use SAP to get use of the outside antenna for better reception an no "radiation" (don´t know the word) inside the car. I also want to use the separate bluetooth handset that can´t be used when using handsfree profile.
Do you think the other bluetooth stack can help me get the contacts in the Audi phone?
Update: tried to install BTSAP_Test.cab manually but it says that installation failed since it doesn´t have enough authority in the system. Have mounted and unlocked extended rom with Fit4cat Hermes Tweaker and soft boot but it doesn´t work.

WM5 Bluetooth stack and DialUp Networking (DUN)

I'm at my wits end with my T-Mobile MDA (aka HTC Wizard) and my new 2007 Acura RDX. The car can connect to the Internet via a Bluetooth phone to send/receive diagnostic messages to Acura, but I'm pretty sure the MS Bluetooth stack is disconnecting during the setup. I'm able to pair the HTC Wizard just fine with the car, and the handsfree functionality for sending/receiving voice calls works perfectly using the JETWare mobile Bluetooth extension on the phone. I've tried doing some basic registry tweaks in the HKLM\Software\Microsoft\Bluetooth keys, but nothing helped. I can use my Sony Ericsson T68i phone just fine with this troublesome feature, but I really don't want to start using my old phone again. Any thoughts on what might be fubared with the DUN connectivity? I'm using the same dial strings too that work just fine on my laptop with the MDA (*99#) on T-Mobile's network. Thanks in advance for suggestions...
While I don't have specific info on your car, you may want to give a try to the
1, Widcomm BT stack (instead of the MS one)
2, AKU3 and BT PAN if your car also supports PAN and not just DUN.
Please check out http://forum.xda-developers.com/showthread.php?t=282780 on the latter q.
Thanks for the reply. I've had older Pocket PC/Windows CE devices that used Widcomm, but I was under the impression that the MS Bluetooth stack was baked into the device ROM. Do I have to reflash the HTC Wizard ROM to get the Widcomm BT stack?
RE: option #2, I'm nearly certain that the car does not support PAN, but I'll dig around and see what I can find.
Thanks again.
Hmm... I just found this wiki page:
http://maemo.org/maemowiki/BluetoothDUN
which mentions Bluetooth DUN problems on the Samsung SGH-X820, which I believe is using WM5 or similar variant. At any rate, it mentions a "receive all" flag, and I'd love to know if there's a registry setting in WM5 that's related to this suggestion.
flashfreaker said:
Thanks for the reply. I've had older Pocket PC/Windows CE devices that used Widcomm, but I was under the impression that the MS Bluetooth stack was baked into the device ROM. Do I have to reflash the HTC Wizard ROM to get the Widcomm BT stack?
.
Click to expand...
Click to collapse
nope, just install the Widcomm BT stack, not even a hard reset is needed - see the sticky thread.
Thanks again for the prompt reply. I followed the How To here:
http://forum.xda-developers.com/showthread.php?t=285696
and I also used SolSie's installation guide here to fill in some gaps:
http://solsie.com/?p=82
I used the CAB file here:
http://btfix.thcgirls.com/BroadcomBluetoothStackX51V05.zip
Bluetooth functionality seems to working ok, but I don't see Dialup Networking as a service now on my HTC Wizard. Do I need to upgrade the AKU ROM? I'm using the summer 06 ROM update from T-Mobile USA right now. Thanks in advance for any suggestions.
flashfreaker said:
Bluetooth functionality seems to working ok, but I don't see Dialup Networking as a service now on my HTC Wizard. Do I need to upgrade the AKU ROM? I'm using the summer 06 ROM update from T-Mobile USA right now. Thanks in advance for any suggestions.
Click to expand...
Click to collapse
You're right - just tested this on my Wizard. No DUN service is visible- actually, HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Services doesn't contain any DUN service listed.
I'll tomorrow check this on my other 1.7 WM5 Widcomm-based Pocket PC's (hx4700, x51v) to see whether you can import this functionality in any way. My WM2003 iPAQ 2210 and WM2003SE PL720 lists this service; from the former (I only have this here at home in addition to my Wizard; the rest are all at work) a direct HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Services\ and [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB] didn't work though.
From what I've read on other sporadic posts, it seems that the Windows Mobile registry has a setting for enabling a "receive all" parameter for Bluetooth that fixes DUN problems. I'm sure there's a bit of a security risk in that, but I'm willing to try anything at this point.
You mean the standard BT / IrDA receive all? It's not dangerous at all - and, for that matter, it doesn't even add much to the overall power consumption, contrary the popular belief (see my related power consumption measurements)
Thanks for the reply. I read your post(s) on power consumption--excellent stuff. I can see options for IR ("Receive all incoming connections"), but not for Bluetooth, other than the discoverable option. Is there some registry parameter? That's what I'm looking--if DUN is failing during a PPP connection because a some weird rejection command, I'd like to see if there's anything I can try out to work around that.
The "Recieve incoming beams / Recieve Incoming Connections" in the IR menu in also responsible for BT file recieves. In addition to enabling the BT discoverable option, you need this to be turned on to accept file tranfers. I'm not sure about how this is going to effect DUN, but give it a shot.
This is prolly what you might have read in one of those posts that you mentioned.
BTW, the DUN service will not be offered even with the Beam Receive option enabled.
This may mean, currently, unless someone invents a way to access DUN under Widcomm, it's impossible to use Widcomm-based WM5 PPC PE devices as external dial-up modems.
Hm...
I know this is kinda off topic of DUN, but using the Axim Widcomm stack on my 8125, I loose all sound from the speaker.... anyone else encounter this?
Yes I have this problem too, can be solved just by calling someone... but then there are other problems...
1)Memory leak after turning off Bluetooth.
2)Only solution is to leave it on, but there are other issues here, for me, so far, it is my Wizard hangs(require soft reset button) or the sound of the speakers dissappears and gets redirected to the phone speaker only... after about a days use..
Hm.... well.... suck. I wish someone released a custom ROM without the MS stack
pball3485 said:
Hm.... well.... suck. I wish someone released a custom ROM without the MS stack
Click to expand...
Click to collapse
but from the axim site, you can actually remove the MS stack..

Categories

Resources