Thanks for sending it. I uploaded it to my website. Here's the link for anyone else who would like to give it a try. I will post results when I try it out.
Before this CAB file:
I connected my Thinkpad T40 to my h6315 via Bluetooth and tried to surf the internet with Tmobile Internet and it would only load about three or four pages before it just timed out all the time.
After this CAB file:
I connected my TP T40 and surfed about 10 websites so far with no timeouts.
It's way too early for me to draw any conclusions and I don't understand why the Asset Viewer isn't showing the updated version. Maybe the reg file mswlogo removed from the CAB is what updated the version info in the reg viewer???
I will test the h6315 tonight with my Bluetooth headset when I get home, but so far it looks to be an improvement, at least for me. YMMV
This looks great. I have been trying to make this Bluetooth dialup work for ages - BUT - how is it going to interact with any ROM upgrades T-Mobile / HP eventually get round to providing. Is it easily removable before installing an upgrade or does it overwrite files?
Thanks for any info.
You obviously know what you are doing. Is there any way of dialing up via IRDA to GPRS? Would it be faster or slower than Bluetooth?
IRDA is incredibly slow. I don't know all the technical details for why that is, but it chugs. Use Bluetooth or a USB cable if you don't want to wait forever for every page to load. I have a 38% signal to Tmobile right now in my office and I'm surfing on my laptop at a respectable speed. It feels about the same as when I had my Sony Ericsson T610 paired via bluetooth. This is the first time I've been able to surf via bluetooth since I got my h6315.... so WOOHOO!
This is basically a CAB file that overwites a bunch of files on your PDA, so my guess is that as long as the files that would potentially be updated in an HP/Tmo patch are newer versions, it shouldn't be a problem. But I am not going to stand behind that promise. I'm willing to risk it, if it means I can actually use Bluetooth on my h6315 with my Thinkpad.
The worst that happens is you have to hard reset to apply whatever patch HP/Tmo potentially release. Frankly, I've lost most of my hope that they will ever get their heads out of their butts and get a patch out. HP treats the h6315 like an ugly redheaded stepchild and Tmobile engineers are utterly incompetent. Talk to them about topics like DHCP or proxies sometime and you'll see what I mean.
That's great it's working and thanks for putting it up on your web site.
To check version of bluetooth.
Go into The Radio Manager Icon in your system tray.
Then Go To BlueTooth Settings
Then Go To About Tab
Then Click Details.
You will see BTTrayCe.exe is still 1400 which is the only file I did not overwrite because of HP's custom Radio Manager. Your Asset Manager might be reporting that version. The Details will show the version of a bunch of Bluetooth DLL's (i.e. stack and drivers).
As far as upgrades in the future go.
It's hard to say what you will have to do.
But what will always work is hard reset and then apply patch. If it's ROM update you will essentially be doing a hard reset anyway.
What you have to be careful of is your future backups may pickup these RAM updates. And if you restore it to a newer ROM (in the futire) it may basically apply this "old patch" again and you won't want it to.
Some backup programs give you more control than others.
So Allways keep Active Sync up to date as you go because for most people that is your most critical data.
Looks like you might be right. When I click about it says v1.0.0 3000. So the Asset Viewer must be pulling from the radio manager executable. No biggie.
FYI: I've now been surfing on my Thinkpad via bluetooth for over an hour with no disconnects or lockups and I only have a 38% signal to Tmobile in my office according to IP Dashboard.
Last edited by Paladin27 : 12-29-2004 at 03:25 PM.
By the way this is the behavior I saw with this patch using HS820
If the Headset and phone were all paired up and working and with in range everything is fine.
If Phone is turned off or turns off by itself. The Bluetooth light stops blinking on both units.
If a call comes in Bluetooth lights come back on and it almost immediately rings in the headset (this would not happen before the patch).
How ever if the headset is turned off manually and back on it will not automatically reconnect. Toggling Bluetooth radio seems to help it along. Likewise if it goes out of range for a while. It will not reconnect automatically. I think the phone polls it periodically while it is asleep. If this polling stops the links it broken.
My HBH-300 (although really fussy and I could not get to work on the H6315 patch or no patch). On my PPC-6601 with patch 3100 it stayed locked on and would automatically reconnect under a wide range of situations like I decribed above. I think I may get my HBH-300 exchanged because it is known to pair with H6315 and LG-325 which I cannot seem todo. But once paired it seems to behave well.
I'll try this patch with my Plantronics M3000 tonight when I get home. Under the old driver version, once my Ipaq went into standby, I could not revive the bluetooth pairing to the M3000 until I did a soft reset on the 6315. Hopefully I will experience a similiar improvement in performance as you have mswlogo! Good job on extracting this update!
Well, I am about in tears.... HAPPY tears. I just left my Ipaq paired to my Plantronics M3000 bluetooth headset for the past hour and called it intermittently from my other phone and ***SHOCK*** the phone woke up, bluetooth came on, and the headset let me answer the FREAKING call. I remember the days of working bluetooth before my H6315 and it's so convienant I had almost forgotten.
No thanks to HP and Tmobile... I think we finally have a solution to our bluetooth woes on the h6315. THANK YOU mswlogo! You are my hero!
mswlogo - Thank you for emailing me last night. I was so excited when I installed the 3100 patch and BANG! it went to sleep and woke up still connected to my HS820. I even got up in the middle of the night and tried it. (im a geek)
I tried it out today - Sadly im having serious problems
I applied the patch without doing a hard reset and I can hear excellent through the headset but people cannot hear me. There is no return audio at all.
I also then applied the patch after a hard reset and still no luck.
Im wondering if you tested the calls to other people?
What could I be doing wrong?
How ever if the headset is turned off manually and back on it will not automatically reconnect. Toggling Bluetooth radio seems to help it along. Likewise if it goes out of range for a while. It will not reconnect automatically. I think the phone polls it periodically while it is asleep. If this polling stops the links it broken.
>Mswlogo,
Thanks for the patch...still testing it.
This is THE problem I am facing. I was hoping that the patch would resolve this.
I tested calling people. I don't like that HS820 headset. The friend I borrowed the phone from had a cheap $30 head set. It was the smallest I've seen and it worked pretty damn good. I did not test sleep with this headset though.
Suggestions:
Try a different headset (could be different firmware levels around).
Try comparing hardware revs with others (I know there is multiple versions of the phone).
Search for WaveDev on all forum for a post I did. You can try that hack.
That's all I can think of at the moment. Zillions of variables.
So far taken and made a few calls. No issues. The only problem is still the out of range issue when the SW on the ipaq seems to hang and I have to toggle on/off the BT to get the link to the headset connected again. I tend to leave my ipaq and wander around with the headset in my pocket.
I have tested using a Logitech Freedom headset and a Jabra 250.
Mswlogo,
No worries.. I have decided to get rid of the Jabra 250. I understand that there is a 3500 patch for the imate. Is that the same as the 3100? I am still hoping that the out of range issue is resolved. To me if it works on the XDAII, why not on the ipaq. I am curious to know whether the new XDA IIs faces the same problem as both the IIs and the ipaq uses the widcomm stack.
I'm willing to risk it, if it means I can actually use Bluetooth on my h6315 with my Thinkpad.
Login
Panel
