Bluetooth scanner? - General Topics

Is there any Bluetooth scanner like Mobiluck but designed specificaly for HTC devices (particulary Magician). I would like to run a program which would scan for other BT devices in his range and just make log about devices which are found and when they were. I used Mobiluck on my Nokia 3650 (Symbian6) and it was working fine, but now on my Compact with Bluesoleil stack, it just don't wanna run!?
Thanks

hhmm are you trying to run symbian programs on a pocketpc ?

hhmmm no i am trying to find a program which is written for PPC but will do what mobiluck used to do.. so.. is there any?

Related

Idea: WM2005 Bluetooth stack on Magician ???

Hi guys, just a crazy idea.
I loaded my old XDA II with the WM2005 ROM that is floating around in the XDA forum.
First of all I can confirm all the bugs and problems people face with this obvious BETA build of WM2005 on the XDA II, but…
I found the improved MS Bluetooth stack quite interesting.
So here’s an idea:
Would it be possible to extract all WM2005 BT parts (files and registry entries) form the XDA II and place them onto the Magician.
Obviously the XDA II is using a different BT chip, as the Magician, but I found in the registry of the XDA II
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\HCI
the bthcsr.dll
and in the Magician registry
the bthusb.dll instead.
And we know from the exercise with the Bluesoil stack that the Magician uses some kind of USB BT chip.
So I believe these are the driver dll’s for the different BT chips, so by keeping the bthusb.dll on the Magician the WM2005 stack may accepts it.
So here’s the problem:
I managed to export all WM2005 BT registry entries I found, but I got stuck by copying the bt*.* files (dll, etc.) of the XDA II, as they are obviously in the ROM and Resco File Explores can’t copy them.
Even if we manage to get the files, I believe we face the same problem how to override and load them into the Magician.
Maybe by copying them into a different path then \Windows, a directory in the RAM and set the pointers in the registry to this location.
I know it’s probably a hopeless project, but maybe some of you are mad enough and have some ideas and ways of doing it ;-)
I’m happy to help with everything, getting the stuff of my WM2005 XDA II, so let me know if you have some ideas.
Torsten
Can you tell us please, if there is any new features in BT stack? Any voice dial support?
BT profiles I found in WM2005
Hi, had a quick look through the WM2005 registry and found the following BT profiles:
- Serial Port
- Dial Up Networking
- Headset
- Hands Free
- Input Device (probably Keyboard etc.)
- Active Sync
YES!!! I wish we could!
:idea: :idea: :idea:
Lets see a cab file include the reg and the dll files with the new features 8)
torklemm,
can u dump the rom and upload it to xda ftp?!
Ecactly my problem, never did that 'dump rom' excercise, and I'm not to deep into that Hex code hacking to do it myself, so if anyone else can get us a dump of that WM2005 Rom so that we can try to integrate the required dll files and registry entries into the Magician, that would help.
Ahmmm
guys...
why dont u try the bluetooth stack provided by widcomm instead... it has more features than the 2005 microsoft stack as well, u'll save hell a lot of time and energy extracting only the blutooth stack from the package and am using the widcomm stack currently... it works like a charm... though mine is a himalaya but i've upgraded to win2003se
ROM Version : 2.06,00WWE
Radio Version :1.14.00
ExtROM Version : 2.06.00a
See if u like it... u'll find the widcomm stack on this forum itself, in the Himalaya Upgrading section... but this stack doesnt work with the radio and rom version that himalaya provides... i actually upgraded to the new OS version mainly for the widcomm stack and ofcourse why would i mind a landscape view
adios
always
mOrph
mi amigo
I have tried installing the latest widcomm drivers... well not just the latest one.. all of them.. but it always gives an error about the lack of memory even tho there are lots of memory to spear.... so no one till now could figure out how to make it work on the imate jam...

Attn Widcomm & A2DP-users:a new, GREAT hack for all A2DP (Hi-Fi stereo headset) users

Attn Widcomm & A2DP-users:a new, GREAT hack for all A2DP (Hi-Fi stereo headset) users
Many Dell Axim x50(v) (those that upgraded to WM5) and x51(v) users have noticed the device’s using the Microsoft Bluetooth stack, with all its problems and shortcomings. The situation wasn’t changed much by the AKU2.3-based ROM upgrades, which were only released for the x51(v) series – it only added non-full (for example, it just refuses to work with the Plantronics Pulsar 590A – this has also been reported by Solsie) A2DP support.
The lack of proper, compatible-with-all-headphones A2DP support in the new ROM versions made a lot of Dell Axim users stick with the well-known Widcomm hack to use their stereo BT headphones with their PDA's.
In June, mikelspikel and beemer, the main leaders of the Widcomm project, have released BTSpeedSwitcher, which fixed the problem of the stalling sound transfer between the PDA and the headphones. (For geeks / hackers, here are the Registry values this utility modifies.)
Up to now, it was the only solution for the problem plaguing almost all WM2003(SE) devices (and the WM5 Dells with the Widcomm hack): the sound would just stop after some dozen minutes, which can only be fixed by reconnecting the headset from Bluetooth Manager, after restarting the Bluetooth unit.
Now, mikelspikel has just come up with a much easier and, what is more important, generic hack that seems to be compatible with more models than the speed switcher hack (more on this later):
All you need to do is setting the DWORD Registry value HKEY_LOCAL_MACHINE\ SOFTWARE\Widcomm \BtConfig\ SerialTransport\ FlowControl to 0 (from the default 1). (You can, alternatively, import this registry file if you prefer importing pre-made registry files instead of manually editing the Registry.)
This hack, so far, has proved to be, generally, considerably better on two of my test devices (my old iPAQ h2210 with the HP 1.6 upgrade and the Fujitsu-Siemens Pocket Loox 720 with the PDA2k BT upgrade – please see this article for more info on these upgrades) than the BT speed hack (which doesn’t do anything on these two models, it seems).
Also, I’ve thoroughly tested the new hack with my Dell Axim x51v and found it to be perfect.
Make sure you give it a try! Also, if you have a different model, let the others know how it works.
Note that the hack (as with BTSpeedSwitcher) only works with Widcomm BT stacks. There is no point in trying to apply it on MS BT-stack based devices (to, for example, fix the Pulsar 590 problem).
A chart showing all the results of my tests can be found here
Note that, with the iPAQ h2210, you'll still need to reconnect in about every half an hour (after that time, it just starts to awfully skip). Still, it's much better than the default, hack-less, completely useless case.
Also note that I’ve also elaborated on the HP iPAQ hx4700 + Motorola HT820 combo in the chart as well (which don’t seem to like each other) in the last row.
Menneisyys, do u know if i can try the widcomm hack in my hp 6828?
Is it a Widcomm-based device? If it is, then, yes.
Menneisyys, thanks for your reply. I do not know if it's widcomm based device (or how do i check it?). hp 6828 is manufactured by Quanta similar to Atom and uses MS BT stack.
kjskho1 said:
Menneisyys, thanks for your reply. I do not know if it's widcomm based device (or how do i check it?). hp 6828 is manufactured by Quanta similar to Atom and uses MS BT stack.
Click to expand...
Click to collapse
Then, the hack won't work.
However, I've just published a new article on my latest hacks (including MS-related ones) - don't forget to check out http://forum.xda-developers.com/showthread.php?t=280454
ok, thanks! checking ur link... sad to say if i need to stick with MS BT stack, it sucks...

wm6 standard questions

hey guys (and girls where aplicable),
i got a question (a sorta dumb one). If a smartphone lik the iPAQ 514 Voice Messenger or the HTC Vox have windows mobile 6 standard does that mean they run regular windows mobile programs or smartphone versions? See the Cheeta/treo 750 has windows mobile standard ed. and is called a smartphone but it uses regular PPC programs, the other two mentioned before have the same wm6 but no touch screen. so i was wondering if that made a diference in the phones capabilities to use PPC Progs? I appreciate any answers as i am greatly puzzled and intregued buy this.
With WM6 they dispensed with the term "smartphone" in favour of WM 6 Standard. Too many non Windows Mobile phones were being called "smart phones" as well as PPC phones.
WM Standard has no support for touch screens and many PPC apps will not run on it.
WM Pro has touchscreens.
understanding versions...
so lemmie go over this... a ppc with a touch screen is said to run WM6 pro, a ppc without a touch screen is said to run wm6 standard the "smartphone" version. so what of the vox? it has all the capabilities of a full sized PPC without the touch screen so where would it and the ipaq 514 fit in? Because correct me if i'm wrong but dont they offer features like MS Office editing and production verus the others whose ability is limited to viewing or is it the WM6 platform that actually enables this?
You're right, its just a functionality of WM6. Any smartphone (i.e. non-Touch screen device) running WM6 has those same office capabilities and will be running WM6 Standard, not Professional.
As far as I know the two WM6 are one same core of the same OS but..
In the PPC version there is more advanced setup in the menus wich setup is locked in the Srtandard by default.
For example in the Standard there is no way to change the IP of the wi-fi manually.
And in the pocket pc there is some dll's, responsible for touchscreen operation .
yes but....
i do believe you might be correct on everything but the I.P setup for standard. i have an sda running wm6 and i can manually setup my wifi and change certain settings in the network config. Also the HP ipaq 514 that i've been researching also has the same features. see my big thing is i love he compact size of the smart phone but need the capabilities of the PPC. It wold be great if i could get the best of both. i know the O2 XDA stealth has that exact combo but they are hard to find and kinda pricey for thier age.
There are separate SDKs for Standard and Pro, so I think the differences run a little deeper.
well what to do?
well i guess my final questions then wuld be what kind of phone are:-
1/ O2's xda stealth
2/ HP's Ipaq 514

3Sixty.2 RockfordFosgate and Acer n310 Problem

I have the Sound processor from RockfordFosgate wchith communicates over Bluetooth with WM5/6/6.1 PDAs for now i can communicate over BT with my HTC Wizard but when I try to start the software on Acer n310 (WM5, or 6.1) then i get error:
TypeLoadException
at MyProject.Program.Main()
does anyone know what can be done?
I called RockfordFosgate but they dont know anything about solution and say Acer n310 may not be supported, but it has same CPU as the supported E-Ten G500+.
xequtor said:
I have the Sound processor from RockfordFosgate wchith communicates over Bluetooth with WM5/6/6.1 PDAs for now i can communicate over BT with my HTC Wizard but when I try to start the software on Acer n310 (WM5, or 6.1) then i get error:
TypeLoadException
at MyProject.Program.Main()
does anyone know what can be done?
I called RockfordFosgate but they dont know anything about solution and say Acer n310 may not be supported, but it has same CPU as the supported E-Ten G500+.
Click to expand...
Click to collapse
Go through the basic requirements for some of the programs... For instance, does it require CompactFramework 3.5? Is your BT connection established? Just go through them and see if you are missing something...
yes .NET 3.5 is installed BT is working and I did pair with the device.
I will re flash my PDA and try again but don't think this will help.
3Sixty.2 for PDA requires Microsoft BT stack, I use WM6.1 and I think it has MS BT stack.
ok, i know now what the problem is, the Acer n300 uses Broadcomm BT stack and this app needs MS BT stack. Now I have to find out how to install MS BT stack and even don't know if its possible

change Bluetooth stack on cotulla powered device

Hello,
did anyone successfully install a different bluetooth stack on a cotulla rom ?
i tried bluesoleil (but i only have a pretty old version). i also tried the toshiba stack (also pretty old version, build for 2003).
both work fine on 2003SE - but none of them work on cotulla rom.
anyone successfully did this ? or what about widcomm/broadcom ? what's so special about the magician bluetooth - i've never seen a widcomm version for magician - but for almost every other HTC device.
(i need a better stack than MS - since MS does not support BT LAN access, neither PAN (client))
In reality it's not easy to change BT Stack on Windows Mobile device...
Now my roms are using MS BT Stack...
I have some research and maybe some future versions will have BroadComm stack...but not sure...
Hello Cotulla,
nice to see you're answering about the bluetooth issue ;-)
broadcomm/widcomm stack would be great off course!
... in the meanwhile: as far i know, no broadcomm exists for magician - not even for the old ROMs - i never understood why (different BT hardware i guess ?).
but
- toshiba and
- bluesoleil exists for the old ROMs
they work - if you disable the microsoft drivers (cause it's not possible that both drivers use the same hardware - i guess).
bluesoleil: comes with a tool to disable the MS stack.
toshiba: you have to do it manually by taking off bticon.dll from HKLM/services.
so i have a question:
"taking off bticon.dll" from HKLM/services" is for 2003SE -> what is to do in WM6 to disable the MS-stack ?
maybe the toshiba/bluesoleil would even work ? did anybody tried before ?
or is this bull**** ? i heard of different "driver-models" between CE 3/4 and CE 5 - so is it even possible to use drivers from CE 3/4 on CE 5 ? i don't know! but i'm sure, you know ! ;-)
thank you cotulla for your great work! i'm wondering how you managed to get that much knowledge about this device! great!

Categories

Resources