I used to have a control that could manually select profiles; Car, Home, Work etc. It also switched to Car automatically when the carkit was connected. Maybe it wa in WM2003 or WM5. But I can't find it in any WM6, 6.5 ROMs.
Can someone post the cab for it plz?
Thanks.
the lack of profiles in windows mobile is annoying. any crappy 10 year old nokia phone has several customizable profiles, wm still doesn't. while i haven't thought about it in ages, i have to admit, if anybody has a nice app for that, i would use it as well, especially if it supports hardware changes like you say. different profiles for car kit, charger, BT handsfree... would be nice.
That's odd that no WM had it - maybe it was bundled in an Operator customisation then (e.g. Orange or O2)...trouble is I've blown all my old ROMs away!!
Anyone up for building a neat Applet then?
Have you all tried something like SPB Phone Suite? I think this comes with this option.
Related
It is from an HP 6315 from 3/31/05
http://h18007.www1.hp.com/support/files/HandheldiPAQ/us/download/22539.html
I would love to see if we could get this stack and the settings on our XDAII and other HTC devices,,, THAT would be cool.
Bluetooth build 1.0.0.3701:
Corrects inaccurate display of headset icon when a call is in progress.
Adds a check to determine if Bluetooth stack is initialized before accepting messages from phone.
Adds a user interface (UI) change to enable a connected headset to automatically disconnect before attempting to connect to a different headset when the user chooses to connect to a second headset.
Corrects check for invalid device name.
Corrects issue where handheld could not reconnect to remote device after a page timeout.
Corrects Object push profile update so it sends all files.
Updates FTP connection wizard to correct service discovery issue.
Corrects issue with call waiting for incoming call handling while dialing out.
Corrects issue with headset connection icon so it is correctly displayed after power cycling.
Corrects audio to make it compatible with an in-car solution.
Corrects audio issue where the right channel for a headset was unavailable for playing audio and during calls.
Corrects issue where the LED and network status were not properly synchronized.
Corrects issue where the user could not send multimedia messaging (MMS) message.
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
2. This is not a HTC device, so I doubt the tools developed here will work on it.
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Well, even though I don't want to stop progress because I would like to have the ROM taken apart for my own personal reasons, the 6315 was actually made by Compal. Bad move on the part of HP in my opinion. However, the bluetooth stack that was taken from an iMate JAM worked on the 6315 and that is how most survived until the update was released. So it very well could work on the HTC's. On a side note, if someone could point me in the right direction, I will take the ROM apart, just don't know where to start.
mamaich said:
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Click to expand...
Click to collapse
Oops....my bad....excuses!
no htc dont make ALL hp's pda's the H5400's was oem'd from LG
and even if the ipaq in question is made by HTC then that dont garentee that the xda tools work as they are not made by HTC
I can tell you now that the XDA tools do not work on that ROM as it stands. However, looking through the HEX, it is laid out a little differently than the XDA ROM's but have some of the same portions, just in different locations. Now if I knew more about what I was looking at, I could take it apart for you. The 6315 uses Widcomm BT and like I stated before the BT drivers ripped from a JAM worked great on the 6315 so I have a feeling the 6315 drivers will work on the XDA's.
I can also tell anyone looking at it that in the first header of the ROM the letters are shifted 13 characters. So when you see RAT it equals ENG and so on. It looks like they don't do that for very long though.
BT
HappyGoat said:
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
Click to expand...
Click to collapse
BT 3900 and 3500 do not support Hands Free Profile or even Headset Profile on my XDAII.. This is important so people can use Caller ID on a BT device and OR a Car Kit with the Hands Free Profile....
Switching stacks is a pain in the but...
Even so, the only OS that even slightly works with Hands Free on the Himalaya, is 2.20 translated but even that has bugs that makes it very frustrating. The 2005 did have a fully functional BT, even having separate serial ports for each BT device, (like GPS), but the other bugs and the limited memory left over from the useless and unerasable Extended ROM from the other OS made it no good..
With this new ROM, I may be tempted to buy the HP again.. When I first bought one, it was DAM slow and the BT SUCKED!!!
Maybe now it is usable.
I love my Himalaya and it's 128 of built in..
http://www.expansys.com/product.asp?code=PDA2&asource=IMATE
http://www.expansys-usa.com/product.asp?code=PDA2&asource=IMATE
I will just have to keep waiting for one of the above unless someone finds a fix for the BT Hands Free.
I have a BlueAngel / SX66 on Cingular. I have been through every ROM upgrade you can imagine, all with the hopes that SOME DAY the bluetooth will work properly. More specifically, I have a stick BMW and it's impossible for me to talk on this thing and drive at the same time, not to mention really unsafe, but I absolutely need to talk in the car because I'm on the move a lot. There is a bluetooth headset interface in the car that I know is pretty damn good because it works so beautifully with Motorola devices (specifically the somewhat ancient V600 I have). My SX66 can barely get through 3 seconds of being connected to it before it just goes haywire and drops the connection, locks up my stereo, etc. It's a disaster. So every time a new ROM comes out I sit for hours upgrading just hoping that maybe this time it will work. I've tried a Motorola HS810, HS850, a Logitech Mobile Freedom, a Jabra BT800, and an Ericsson HBH600. Not one of them can consistently hold a connection without it dropping here and there and me having to go to the Bluetooth manager and "reconnect". These are all reputable headsets that work flawlessly with other devices.
Conclusion: The MS bluetooth stack is pathetic.
Problem: I want my SX66 to work with JUST ONE bluetooth device flawlessly. It doesn't need to be the car necessarily, but that would be really sweet if it did. I have recently upgraded to WM5 in another feeble attempt, but alas WM5 doesn't appear to be compatible with GoodLink, the messaging sync software that I'm tied to that makes me use this god awful device (I won't use a Treo because the Palm UI is garbage and it has its own host of problems I've seen). I'm going to have to downgrade back to 1.40 to get GoodLink to work again because its pretty vital to me.
Question: Does anyone know how to get Bluetooth to work consistently with any headset, paired with an SX66? I seriously have sank like $400 just in headsets trying to get this piece of crap to work. If there are any stack upgrades, firmware flashes, etc. WHATEVER I'm willing to try anything. This is the only Windows based device available on the market that is compatible with GoodLink and has a qwerty keyboard that's easy to use.
FYI, the BA uses the Broadcom/Widcomm BT stack, unless you've upgraded it to WM5.
Ok. After searching through the forums, and trying various things, I've finally given up...
The goal: To enable bluetooth DUN for WM6.
According to Microsoft, this feature was originally removed due to the thought that their 'Connection Sharing' feature was superior. Unfortunately, my TomTom 910 will ONLY connect via DUN. So, obviously I would like that 'feature' back!
Do any of the chefs out there have access to this feature, and can create a CAB to enable it on my 8525??
This would REALLY be appreciated. I'm sure I'm not the only one out here who misses this feature.
thanks.
I'm with you
Me too
I'm in the same boat. 8525 and 910. Would love a fix.
Kevin
Considering how the change was made to WM6, it is probably unlikely anyone would be able to bring back without issues. I think it is time TomTom start supporting WM6.
Not very hopeful
I asked this same question on the general forum just a couple of days ago.
http://forum.xda-developers.com/showthread.php?t=309996
Unfortunately, from Menneysys' answer it looks like Ipsi2000 is correct.
I think the options for us TomTom 910 users are:
1. Use duplicate sim and keep another phone in the car to connecto to TomTom
2. Pray and wait that one of the operators releases (or one of the chefs gets hold of) a version of WM6 for the Hermes with DUN back in there (since it will be an option at each operator's discretion)
3. Hope that TomTom upgrades the firmware to support BlueTooth PAN over ICS (That will happen just after hell freezes over. We'll probably have to buy the TomTom 920 or something...)
4. Flash our Hermes back to a pre AKU 3 WM5 ROM (Nooooooooooo!)
cuccureddu said:
I asked this same question on the general forum just a couple of days ago.
...
I think the options for us TomTom 910 users are:
...
2. Pray and wait that one of the operators releases (or one of the chefs gets hold of) a version of WM6 for the Hermes with DUN back in there (since it will be an option at each operator's discretion)
...
Click to expand...
Click to collapse
I also miss DUN thingy (I have M$ BT stack on my toshiba with completely crippled/non functional PAN and don't really feel like experimenting with Widcomm BT stack right now). So, no GPRS/EDGE internet connection for me - I kind of got used to it with my old P910...
There is an idea though - I did a little digging in the BT services branch of WM6 registry and I've got an impression that DUN functionality is still there it's just has to be enabled via registry (dunno why I got so sure though). What you can try is to ask somebody with pre-AKU 3 wm5 device to dump the registry for you and compare Bluetooth branch (the part where it lists services) with your WM6 device.
It's just a hunch - if what you are saying about operators enabling DUN BT service at their discretion is true, then this trick could actually work out.
i have a spare hermes [Tmobile VarioII variant], i can dump you a copy of the registry just after a HR is you would like?
i can dump it via registry workshop if thats best for you?
Acuum2 said:
i have a spare hermes [Tmobile VarioII variant], i can dump you a copy of the registry just after a HR is you would like?
i can dump it via registry workshop if thats best for you?
Click to expand...
Click to collapse
Yup, sounds great. If you can do just HKLM branch that should be enough. I have WM6 black - we can compare BT parts se if we can try to enable DUN back.
The worst part is that, according with MS blog, they DIDN'T remove BT DUN, they give it to the operators, and they can choose to add or not BT DUN to their ROM.
Just isn't in DEFAULT rom, is an option
So, somewere, the MS BT DUN should be available!
I love how because you use it, it automatically makes Bluetooth PAN useless.
It isn't.
It is MILES better than ****ty Bluetooth DUN. I use TomTom on an ancient Ipaq PDA, and even that supports PAN. Not only does it support it, its miles miles more stable. It doesn't require you to dial-up every time you go through a tunnel, or under a bridge, it just works.
I vote NO to bluetooth DUN (unless it can run alongside PAN)
Its TomTom you should be angry at, not MS or the operators!
I know, my car is miles away from my feet, but sometimes I need to go were only feet are allowed
The problem isn't what is better but why they removed BT DUN instead of leaving it..
I am a bad, bad, bad boy, but I believe there is some marketing strategy behind, like AS4.5 NEEDED for WM6 not working with outloook 2002, with NT...
al3xxx said:
Yup, sounds great. If you can do just HKLM branch that should be enough. I have WM6 black - we can compare BT parts se if we can try to enable DUN back.
Click to expand...
Click to collapse
al3xxx
Here you go,
sorry did the entire thing...
well i added the WM DUN reg keys to my Elf WM06 and its not enabled the DUN service... (not surprised, if it were that simple it would have been figured out weeks ago... So what's next?)
Microsoft saying they give the DUN to the operators sounds fishy. Let's face it, Microsoft would prefer everyone uses PAN (considering it provides all the features available in DUN and plus more). They basically said to the operators we will support PAN, however if you wish you can implement DUN but you will have support it yourself and any issues that may crop up due this implementation. Most operators would not want the additional support or issues that may come up due to them providing a deprecated function. PAN is the replacement for DUN and there is very little we could do about it.
Software vendors need to adopt PAN or it may not work with WM6.
clublander said:
I love how because you use it, it automatically makes Bluetooth PAN useless.
It isn't.
...
I vote NO to bluetooth DUN (unless it can run alongside PAN)
Its TomTom you should be angry at, not MS or the operators!
Click to expand...
Click to collapse
Yeah not MS, what made winxp BT stack PAN absolutely NOT working - tried bunch of BT devices with it - neither one was recognized as PAN capable... See if PAN on the phone (and PC) was working for me whan I was set in front of the fact that there is the ONLY choice MS gives me if I want to use my phone as wireless modem i wouldn't really get the DUN back...
al3xxx said:
Yeah not MS, what made winxp BT stack PAN absolutely NOT working - tried bunch of BT devices with it - neither one was recognized as PAN capable... See if PAN on the phone (and PC) was working for me whan I was set in front of the fact that there is the ONLY choice MS gives me if I want to use my phone as wireless modem i wouldn't really get the DUN back...
Click to expand...
Click to collapse
Thats funny, I use my WM6 device with XP with no troubles.
I suggest you need computer lessons.
To re-iterate, TomTom is going to have to update THEIR Bluetooth stack, unfortunately. PAN is almost identical to DUN, it just has an interface on the phone now, whereas you had to do it all from your PC before. If you don't believe me that it's virtually identical, look in your WM6 registry. The PAN service is STILL CALLED "DIAL UP NETWORKING" in the registry. Furthermore, if you recall, when you pair your phone to your pc, the phone offers DUN as a service!! Do you see PAN in that service list? No... because it's DUN!! Same thing, folks.
All MS was shooting for was the ability to make it easier to dial up to the internet through the phone, not to mention, add the functionality to become a Network node. It's the same thing as buying a new pc these days that doesn't come with a dial up modem. Why not? Because it comes with a network adapter.
TomTom is going to have to update their stack to recognize this service.. not the other way around.
Stpete111,
I emailed Tom Tom about this today, and their attitude is as follows:
I told them I have a M3100 that their attitude was - we don't no support phones with WM 5 OR 6 especially NOT this device! But get this, they DO support the O2 XDA Mini S....so I don't think they understand that they are already supporting a WM5 device....
Anyway, there was no indication that they intend to change this, and I suspect that they won't.
So I suspect you'll have four choices:
1) Live without any phone when using you're TTG - not an option if you've already subscribed to one of their services.
2) Go back to WM5 - where it will work - far from ideal.
3) Get a spare phone that will work, and a duplicate sim - not that easy...
Or finally, 4) Invest in a device that's more current that WILL support WM6 devices.
Anyway, that's my thoughts - I've yet to make up my mind. But I'm not holding out any hope of TT changing their minds!!
Matt
Here's an update:
I have spoken with TomTom regarding this issue, and this is what I have found out. It's not really good news.
TomTom is phasing out the cell phone connection to their GPS units. All future units do NOT use cell phones to access traffic and weather info. They will ONLY use FM antenna for their data.
So, TomTom probably won't be updating their Bluetooth stack for us current-generation GPS owners. Their next generation ships in July.
Ideally, (for me at least), I would like to have BOTH DUN and PAN services on WM6. That way, for "older" devices, we still have connectivity, while at the same time, future devices can use PAN.
(just my .02c)
Has anyone tried Garmin products? I have tried two Garmin units but NOT with Bluetooth, so I don't know anything about their BT functionality. I DO know however that I much prefer the Garmin devices to TomTom's. Not trying to spark a debate here over which is better... but perhaps checking out Garmin's capabilities is a 5th option?
Hi,
I am look ing for a SIMPLE today plugin to fast switch on/off BT. I have tried a dozen but none of them seem to work. Strange. I used to have a HTC Universal (WM 6.1.) and there the BatteryStatus (name of the program) worked like a charm (even the last version homescreen_plusplus doesn't work on the rhodium) I tried exe versions (like BtOnOff.exe)and cabs (like BlueTogglerSetup). So I am starting to think I am missing sth. Anybody a suggestion?
Oh yeah, the indicators do switch on of these plugins (when i switch on BT trough settings-connections) so they detect the state of BT but are not able to switching on them selfs?
Help welcome!
thx in advance
greetz
Kjoere
(damn, i am missing my solid universal!)
Read the very first post in this forum! The very first paragraph. The search function works well ;-)
Pro2 use a different bluetooth stack than all previous models. Currently I have not seen other BT toggles that is working, but I expect they will come later.
I have CommManager assigned to the send button, so it is no big issue for me.
The biggest issue is, that the BT headset controls are hardcoded to WMP/HTCPlayer, so I can not use my favorite mediaplayer.
thx
thx, yeah I searched and read about the BT problems.
I just wanted to check in to see if there was sth new going on this front.
I hope you didn't mind too much.
In the mean time I assigned comm manager to a soft key in combination with 2 today screens it is feasable, but definitely not sth I want as a final result.
greetz,
Kjoere
I am wondering if it's possible to schedule to turn Bluetooth on and off at specific times of the day, automatically on our Rhodium
Does anyone know of this is possible?
It's not a freebie, but I use SpbPhoneSuite to provide different "profiles". These can be used to turn on/off bluetooth and can also be configured to activate based on time or other triggers (e.g. during an appointment, when cradled, etc.).
As this is primarily a Today Plugin, I've used "Second Today", which gives me a separate today screen (aside from TouchFlo) which I use to access PhoneSuite and change profile if I need to do it manually.
I had a licence for PhoneSuite from my previous phone, so I didn't care about the cost.
Ed
I found G-Profiler. Free and alot of config.
BUT... The Bluetooth part dont work.
I've found the reg key for BT on the Rodium:
HKLM\system\state\hardware\
bluetooth=8 is the value for off
bluetooth=9 is the value for on
I havn't found the place to put that value in G-Profiler.
But it's possible to call a prg instead. Mortscript to change this reg-value?
Is this the easiest way? I've had this problem in other prg aswell, so i'd like to know.
Thanks for your replt, however I read that HTC switched from the WM BT-stack, to the WidComm BT-stack and SPB Suite will no longer control BT as we would expect.
Any other ideas?
eepyaich said:
It's not a freebie, but I use SpbPhoneSuite to provide different "profiles". These can be used to turn on/off bluetooth and can also be configured to activate based on time or other triggers (e.g. during an appointment, when cradled, etc.).
As this is primarily a Today Plugin, I've used "Second Today", which gives me a separate today screen (aside from TouchFlo) which I use to access PhoneSuite and change profile if I need to do it manually.
I had a licence for PhoneSuite from my previous phone, so I didn't care about the cost.
Ed
Click to expand...
Click to collapse
phoneweaver
With SBSH Phoneweaver, Profiling works fine with Bluetooth. Make sure that you use version 1.4.2 (the issue with the BT Stack has been solved in this version)
http://www.sbsh.net/products/windows_mobile_pocket_pc/phoneweaver
mail_e36 said:
Thanks for your replt, however I read that HTC switched from the WM BT-stack, to the WidComm BT-stack and SPB Suite will no longer control BT as we would expect.
Any other ideas?
Click to expand...
Click to collapse
Ahhh - I'd seen the Bluetooth option, but not actually tried to use it in anger.
D'oh!
Phoneweaver looks as though it might also do the trick, though...