Has any one taken this ROM appart yet? It has uptated BT. - Upgrading, Modifying and Unlocking

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.

Related

Bluetooth Headphones Problem

I have an O2 XDA Mini S and have just purchased a pair of Motorola HT820 Bluetooth headphones. I have paired the two; however, I only get the Hands Free service (which works) but NO Wireless Audio. I have not installed any other software / drives and I am using WMP 10 Mobile to play the music.
Any help with this problem would be very much appreciated.
Thanks, Harold Clements
...Ok, I have been on this for about 4 hours now and I am starting to get a bit annoyed.
I clicked on Motorola HT820 and then went ‘Refresh’ and up popped ‘Headset’ so I ticked that and saved. I then clicked (and held) on Motorola HT820. The options that I get are Edit – Delete – Set as Hands Free. I think I should also have ‘Set as Wireless Stereo’ or something, but I don’t.
Please, has anyone any ideas?
Thanks, Harold Clements
Wirless Audio Hacks
I really could do with someone’s help!
I have read about the ‘hacks’ (zoad2p.cab, Tornado asdp, AKU2.6) but I am unsure:
a) if this is a solution to for problem / PDA.
b) what a hack is and why is it needed?
Please can someone help!
I don't know wich kind of PDA you have, as you can see everyone here calls their PDAs by their HTC's code name (mine is a universal), go to look the pictures of all the PDAs, find yours and search directly inside there, it will be much easier for you to find an answer.
One simple comment, your PDA has to have the Bluetooth high quality audio (is called be some PDAs in this way), see if your PDA does contain such feature, you have to activate it if you want to hear stereo audio, generally when you pair your phones for the first time, your PDA will show you the option already ticked, if you haven't see it, chances are that something is missing in your bluetooth profiles, go to your PDA's specific part of this forum and read, with patience and some luck, I'm sure you'll find whatever you need to get your PDA's stereo audio to work.
Most of the cases, are just the lack of the profiles or even installing another BT stack.
good luck
Thanks...
Thank you very much for your advice / reply, it was very much appreciated. It seems that my PDA is a Wizard. I will indeed search that part of this forum.
Thanks again,
Harold Clements
I don't think your phone supports A2DP profile. Correct me if I'm wrong.
Neither do i know if his phone supports it, I use to have an Ipaq 6340, it suppose that it didn't supported A2DP but with an BT stack extracted from another PDA (don't remember wich one) it worked, it didn't worked very well, it dropped audio more or less each 30 seconds for 2 seconds, someone said at that time that was processor lack of power -I didn't agree with this-, but I did no further investigation.
As far as I've understood, the main bottleneck for stereo profiles (or any deamanding profile in BT) is the radio, of course, if We don't have access to the manufacturers good information, good tools, much time and even more will is very hard to find a solution to anything, most of us do not spend lots of time with this things -it's not easy for anyone with a "normal" life-, and I'm not complaining!
It's just fine for me, the whole thing it's quite enjoyable like this, some more time spent in this way and it would become a second work.
So, may us have fun and keep an excellent forum up.
haroldjclements said:
I have an O2 XDA Mini S and have just purchased a pair of Motorola HT820 Bluetooth headphones. I have paired the two; however, I only get the Hands Free service (which works) but NO Wireless Audio. I have not installed any other software / drives and I am using WMP 10 Mobile to play the music.
Any help with this problem would be very much appreciated.
Thanks, Harold Clements
Click to expand...
Click to collapse
on the front page not 2 rows (at the moment) below this thread in really big bold letters
MOTO HT820 SKIPPING SOLVED! NEW FIRMWARE INSIDE!
which covers the issues and varioius fixes (if any) for most phones.
To be truthful, I know very little about what I am trying to do. All I know is that I can’t get the music side of the Motorola headset working.
As I said in my previous post: I have an O2 XDA Mini S (Wizard) and have just purchased a pair of Motorola HT820 Bluetooth headphones. The two paired but I only get the Hands Free service but NO Wireless Audio. I clicked on Motorola HT820 and then went ‘Refresh’ and up popped ‘Headset’ so I ticked that and saved. I then clicked (and held) on Motorola HT820. The options that I get are Edit – Delete – Set as Hands Free. I think It should also have ‘Set as Wireless Stereo’ but It don’t.
I have read about the ‘hacks’ (zoad2p.cab, Tornado asdp, AKU2.6) but I am a) unsure if this is a solution to my problem, and b) what a hack is and why is it needed?
I just really want to know how to fix my problem.
Thanks for your help,
Harold Clements
a hack is getting a device which dont support a feature to do it anyway
if htc dident make your device to support a2dp == bluetooth stereo
you maybe be able to get it to do it anyway using a hack
if any hacks works for your device
as it differs
bluetooth support is never support for all profiles bluetooth have
plus there are bluetooth version 1 - 1.1 - 1.2 and 2.0
haroldjclements said:
To be truthful, I know very little about what I am trying to do. All I know is that I can’t get the music side of the Motorola headset working.
As I said in my previous post: I have an O2 XDA Mini S (Wizard) and have just purchased a pair of Motorola HT820 Bluetooth headphones. The two paired but I only get the Hands Free service but NO Wireless Audio. I clicked on Motorola HT820 and then went ‘Refresh’ and up popped ‘Headset’ so I ticked that and saved. I then clicked (and held) on Motorola HT820. The options that I get are Edit – Delete – Set as Hands Free. I think It should also have ‘Set as Wireless Stereo’ but It don’t.
I have read about the ‘hacks’ (zoad2p.cab, Tornado asdp, AKU2.6) but I am a) unsure if this is a solution to my problem, and b) what a hack is and why is it needed?
I just really want to know how to fix my problem.
Thanks for your help,
Harold Clements
Click to expand...
Click to collapse
The zoia a2dp hack (zoa2dp.cap) is what you need, it will give you "Set as wireless stereo" but be prepared for pretty bad skipping, that has not yet been solved for all of wizards.
Also if you flash to a custom rom (Like Molski's 2.26 it'll have the patch automatically.)

BLUETOOTH STACK - please please help me

I have read every post about MS bluetooth stack vs widcomm etc....
I know someone can build a cab file that will uninstall the MS one and replace with the newest widcomm stack.
I LOVE my universal but I carry TWO phones with me because the universal's connection via bluetooth is not PERFECT for phone calls like the blackberry (oh i fking hate the blackberry for everything else).
I REALLY REALLY REALLY want to use only my Universal but the static on bluetooth KILLS me because I am on the phone 10 hours a day.
PLEASE please help me. Fish
This file fix Blue Tooth
Bluetooth stack
I would second Fish's comments about the Univerasl and the Bluetooth stack. I have bluetooth in my car and it is great WHEN it works. When it doesn't work it takes a lot of tinkering to get the car to recognize the phone again. I'm of course not sure if the issue is on the Universal side, but Bluetooth turns it self off, so there is some kind of problem. I have tried different radios, currently 1.13 (tried 1.14 as well, but went back). I'm very interested in finding a solution (not using two phones), can you please provide some detail on what the CAB file does to Bluetooth?
Thanks,
Sven
Logout. said:
This file fix Blue Tooth
Click to expand...
Click to collapse
What exactly does this file fix/change ?
I've just installed the WM6 crossbow helmi_c version
do I still need this file ?
This is a Stack changer to change from MS BT stack to Cambridge Silicon Radio BT stack. Originally developed for Dell AXIM (about what I've found). Seems to work fine there, but need to uninstall/reinstall after every soft-reset because of a volume lock bug.
http://www.pocketpcmag.com/blogs/index.php?blog=3&p=392&more=1
http://www.aximsite.com/boards/showthread.php?t=108767&page=1
UPDATE
Do not install this patch yet. It is over a year old.
Follow the development/information on Widcomm BT Stack instead. Following links
http://forum.xda-developers.com/showthread.php?t=279236
http://forum.xda-developers.com/showthread.php?t=285419
http://forum.xda-developers.com/showthread.php?t=285696
http://forum.xda-developers.com/showthread.php?p=1073003
SO this is a different BT stack then the original MS and the widecomm ?
Daelyn said:
UPDATE
Do not install this patch yet. It is over a year old.
Follow the development/information on Widcomm BT Stack instead. Following links
http://forum.xda-developers.com/showthread.php?t=279236
http://forum.xda-developers.com/showthread.php?t=285419
http://forum.xda-developers.com/showthread.php?t=285696
http://forum.xda-developers.com/showthread.php?p=1073003
Click to expand...
Click to collapse
True
reading the posts in the forum he linked:
12-12-05, 09:57 PM
I'd rather go with the widecomm BT
I installed the Hermes Widcomm BT stack on my Universal. Sound is great, but the rest is troublesome. We need a developer to fix the code for us so it works on the UNiversal .
Check my thread in UNiversal/accessories. Or move that thread over here please!
Daelyn said:
http://forum.xda-developers.com/showthread.php?t=285419&page=20
Tried out BT Stack change for Hermes patch/program.
TEST RESULTS ON UNIVERSAL WITH WM6 (Midget aka Helmi unreleased)
Sound IS great. But other than that, this program does not work very well on my device. Of course this is designed for Hermes but I gave it a shot.
Issues:
1:
Screen flickers (only when this BT is turned on).
Flickers really bad and unable to use device.
Fix: set the device to standby (power button) and wake it up again. Flickering gone
2:
Once BT is deactivated for a few minutes I can't start it again.
Fix: No fix found yet. Only a Soft-reset and directly activate BT works.
3:
I can't use my GSM/UMTS connection anymore. Trying endlessly. Even after soft-reset's I can't connect. WiFi works fine though.
Fix: No fix found yet.
4:
Unable to uninstall this program. Tried several times. I get to the "Soft Reset Device Yes/Cancel". I soft reset, program still there and working.
5:
Hard-Reset, complete setup with WAP, MMS, MAIL etc.
Installed Widcomm BT Stack again.
Soft-reset:
Screen flickering (fix)
No 3G/UMTS connection avalible anymore. Even when BT stack is completly shut down.
We need a specific one for our Universal. Who's up to fixing this for us?
KEEPING this post updated.
EDIT 06: 18:40 @ 21/01/07
Click to expand...
Click to collapse
Quoted from my A2DP/AVRCP thread in accessories.
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
xixfishxix said:
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
Click to expand...
Click to collapse
try this link
it may help
http://www.pocketpctweaks.com/pocketpc_tweaks/increase_bluetooth_volume
frz
Thanks for the info
I changed the channel in the registry of the device to channel 5 as suggested on that webpage. It was the same quality. I then tried a few other channels and the same results - connection quality still staticy.
Thank you very much for trying to help me though. Fish
xixfishxix said:
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
Click to expand...
Click to collapse
I'm also worried with the same issue, because I've exactly the same problem. But I don't think only altering of BT stack should fix the problem. My understanding is, something is also to be done in radio (rom) side itself. Because I was using a different radio rom last year at about May or June and my BT headset worked perfect. But I can't remember now about what build that was, because later on I've updated my radio to few other releases.
Radio rom has NOTHING to do with the Bluetooth or Wifi - It's ONLY the firmware for the GSM chip.
xixfishxix said:
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
Click to expand...
Click to collapse
We know the MS BT stack is crappy. I found out today that Helmi_c is developing one. But, still, this thread should be more about how to resolve the BT stack change (or just shut it until our friend Helmi_c finishes his school stuff and gets back to being the ROM-N3rd in need of more RAM that we all love so much) than bringing up more issues about the MS BT stack.
Thanks.
guys,tried almost all roms on my universal,some of them works a few days,after 3 months i flashed with the good old official rom,better and stable than all
anyway,the only reason for this waste of time was this a2dp issue,being not able to listen music to my motorokr(tested with 2 laptops and 2 htc,working great)
so i think is just some kind of incompatibility motorokr-universal(yes,i try all the a2dp hacks/registry editing found here

Bluetooth DUN (dial up networking) for WM6

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?

Bluetooth pairing process is different, 6.0 vs. 6.1

The device is Holux GPSlim 236. The phone is Hermes. The phone will pair without question on a 6.0 rom, does not matter who cooked it.
It will specifically not pair with 6.1 roms.
I can see the device when scanning for bluetooth devices, i can choose it, it asks me for passcode, but will not accept the "0000" as the passcode. (tried hardware and software keyboards). IF i type in a passcode OTHER than "0000", it appears to pair, i can see the spp slave service and select it, but once the gps software tries to talk with it, it asks to pair again.
Something is definitely different in the pairing process between 6.0 and 6.1.
Any suggestions are greatly appreciated.
Also see thread about it here from the Himelaya:
http://forum.xda-developers.com/showthread.php?t=378103
Thanks,
Rock
Did you select it as a serial port? You have to do this after you pair the device with the phone!
I am not familar with gps units, does it have a pairing mode like a headset? I know with my Plantronics headset, if I let my phone discover it without the headset being in pairing mode, the phone says it pairs with it, but it really doesn't, so I put it in pair mode then turn on bluetooth on my phone and pair up as normal(0000 passkey) and all works fine.
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
Bluetooth Pairing with 6.1
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
I had issues with the same device on some roms. I eventually changed BT drivers from WM6 and all went back to normal.
On some WM6.1 roms things went OK though.
Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
crusti said:
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
Click to expand...
Click to collapse
ummm no, dont move my thread thanks. you can start one over there if you would like.
crusti said:
mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out
Click to expand...
Click to collapse
You are not the only one
I reverted back to the 6.0 and it pairs without issue. I am thinking that alot of these cookers do not pay much attention to the development of bluetooth in some of their roms. Its not like I changed something on the GPS, so something must have happened with the software.... Still investigating. I hope it works on schaps new rom.
miffymiffy said:
Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
Click to expand...
Click to collapse
this method paired my jabra automatically, it didnt even ask if i wanted to do it auto, i juck clicked "pair" and there it was.
When pairing the holux 236 on the other hand, it would ask for a passcode, then reject it if you put in the correct code of "0000". If you canceled it, it would appear in the connected devices list!!, but still ask to pair once the gps application tries to connect. VERY jacked up.
Hissing Syd said:
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
Click to expand...
Click to collapse
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
rock99rock said:
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
Click to expand...
Click to collapse
No, there was no mention of if it could be disabled.
Wam7 said:
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
Click to expand...
Click to collapse
Wam, which rom are you using now that it works with? id like to download and try it. The 5 or so ive tried did not work.
I power cycle the device without any change in pairing succession.
Thanks!
BTW: Other users experiencing differences between 6.0 and 6.1
http://forum.xda-developers.com/showthread.php?t=391488
http://forum.xda-developers.com/showthread.php?p=2240665

Bluetooth A2DP on my Tilt2: WORTHLESS AS $H!T

Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!
e-thug said:
Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!
Click to expand...
Click to collapse
Hmmmm .... I don't believe you ever stated what type of headset you are trying to get working here? I find your problem to be very strange, even though WinMo does seem to be lacking in a lot of different areas, audio streaming via bluetooth stereo headset is definitely not a problem I have encountered. It even streams flawlessly through my 5.1 hooked to my pc via a crappy 8 buck bt dongle and still sounds excellent. Have you considered that the problem may lie with your bt headset itself?
Also, when you say that you installed latest "release" from AT&T (from a thread on this site), what exactly do you mean? I am running the "unofficial" leaked rom from AT&T on mine and I just paired my Motorola S9 stereo headset and it is playing great for me. You also may want to try using some different software, give S2P (Slide 2 Play) a try and see if you have different results. That's what I am using right now, but I have used TCPMP to play a few xVids through my headset and have had no problems.
The problem is not in the head unit. 25 other phones can't all be wrong. I have no problem using my bluetooth headset. That is probably why you don't see the problem. Anything more complex than a headset will not work with this release. The problem lies within the phone as soon as it displays a notification (which, of course I cannot disable) which reads, "The connected Bluetooth headset does not support volume adjustment from the device. Adjust volume on the headset itself."
That message is the kiss of death. So basically any Bluetooth head unit will not work with this phone? Sounds like shoddy programming to me. Yes, I am using the "leaked" release. I really don't think this release will ever see the light of day. Its horrible! You cannot disable notifications (I don't need to know when my text messages were sent successfully), and it looks like whenever I get a system notification, any program I am using crashes immediately. Like I said before, as soon as I get a notification, I lose the Bluetooth connection (which is like a split second before the notification comes up). I highly doubt this "leaked" copy will ever see the light of day, officially (unless AT&T and HTC do absolutely zero testing on it).
A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset
My Tilt 2 works absolutely fine with all my BT devices, including 2 Motorola headphone sets and my Sony Xplod head unit in my truck.
e-thug said:
A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset
Click to expand...
Click to collapse
I was mis-understanding you about the head unit, I did think you were talking about a headset. Sorry bout that, my Mustang doesn't have built-in BT so I have to use a Motorokr t505 for those chores. It works well but it does give me the same message that you are getting about "volume can't be cotrolled etc" but I can dismiss it and carry on without any problems.
but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
Click to expand...
Click to collapse
Since you don't need your phone for calls, just get Sirius or XM. Ya know, considering you only stream music through the phone..
Did you try the BT headset or head unit with the original stock ROM before you flashed the "leaked official" ROM?
Seems like you might have a couple random issues, with the BT issues and the system notifications crashing programs. I haven't flashed the leaked ROM, but I do know that many random issues with cooked ROMs can often be cleared up by running Task29, which completely wipes the phone memory before you flash a new ROM. I think you will need to HardSPL before you run Task29. Might be worth a try, sometimes fragments of the old ROM interfere with the new one, and cause some bugs.
Bluetooth protocols can be implemented differently by different manufacturers.
I know of many people including myself who have NO PROBLEM with the tilt 2 and different Bluetooth products INCLUDING car radios.
I am using the "new" AT&T ROM and have no difficulties.
Clearly your pissed but your subject is wrong. I would suggest changing to "Worthless as $HIT to ME"
I think my problem is that I am getting notifications which seem to be killing my connection. Is there a way to turn all notifications OFF? The only ones I care about are missed calls, incoming SMS and maybe a birthday. I would like to try to kill the notifications first because I think this may solve my problem
You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/06/24/enable-or-disable-the-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/06/24/tweak-and-configure-how-notifications-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.
redpoint73 said:
You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/...he-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/...cations-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.
Click to expand...
Click to collapse
Thanks I will try these out and report back
For the record my head unit is a JVC KD-BT11 and I have never had any kind of problem pairing any other phone
Somebody else just posted a very similar issue, and found the app hAndyUtils to be helpful:
http://forum.xda-developers.com/showthread.php?t=741311
I think hAndyUtils might just be a app-based way to make the reg edits I posted earlier. But give it a try.
I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack. (Just as an aside, on all my past phones, there were people bemoaning the the fact that it had MS, and trying to replace it with the Widcomm, so I am getting a real chuckle out of folks complaining about the Widcomm and wishing for MS )
In any case, the utilities (Blue music toggle etc...) that used to work for me to toggle between streaming in stereo and plain phone qulity no longer work. However, all my stereo headsets (I own three different brands/pairs) all work perfectly with the Tilt 2. And stay connected and streaming all day.
By the way, coming on a forum that is full of people helping each other and using profanity, anger and threats, is not the most conducive way to get your questions answered. The odds are that the problem you are having is already solved somewhere among the 6+ million posts in this forum. I do not know where or I would post it for you, but it is probably out there. Good luck. And if you find it, please post the link to the answer back here so that other serchers will find it too.
maybe it can come from the phone itself
i had a rhodium for almost a year and never got my motorola headset ht820 to work well enough for me to use it... (more skips than music...cant move my head without a skip)
i flashed to a NRG rom before trying my headset...i tried eveything as far as ref setting, different radios...even flashed my ht820...
no improvement...
then my phone fell in water not so long ago...got another rhodium same model (european)...and it worked perfect out the box on stock rom i can go in a different room than my device and still hear music with no skips...and it still does with nrg rom and latest radio...
so my guess is maybe some actual devices have bad bluetooth hardware ???
I have the Motorola S9 and the HT820 and both work absolutely fine on my Tilt 2.
yatrg said:
I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack.
Click to expand...
Click to collapse
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?
e-thug said:
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?
Click to expand...
Click to collapse
Did you ever try the solution in this thread? It fixed a lot of issues people were having with bluetooth car kits. Maybe it will work for you: http://forum.xda-developers.com/showthread.php?t=591322
The solution source is here: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
And here is the solution. You need a registry editor to do this:
1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2
2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change (or add if not there) DisableReopenAudio to 0 (default is 1)
3. Reboot device
You may also want to do the A2DP quality registry edit: Add a DWORD value of LineSpeed to HKLM\Software\WIDCOMM\Plugin\AV\ with a value of 320.
Give it a try, it may work for you.
I will give this a try and report back. Thank you very much for the response!
No luck. And my bdaddr keeps resetting to a binary value when I reset the phone

Categories

Resources