HatOnCat - Wow! Someone got it working? That's amazing! Great Job!!!

I've got a Sprint PPC-6601 and a 1GHz 12" PowerBook. I haven't tried any of the patching that folks have posted about on these forums. Not because I'm not capable, but because I haven't purchased a bluetooth headset yet, and I didn't want to kill my precious, expensive phone.

If I can really use my Powerbook occasionally with these instructions... well, that would kick butt! (Pardon my excitement please!)

I take it no matter what you did, you couldn't get this to work without patching the phone? I'm still a touch nervous about the 3500 patch, after all the comments in that thread. But I'll do some more reading. Voice Command is probably more important to me than tethering, so...

Once again, great job and thanks for the posts!!!

That's great you got it working.

But just few comments. Build 3500 has an issue with Sleep that the headset takes a long time to wake up. It also has an issue that randomly you can get Memory error (I think it depends on what other software you have running). It would be great if you could get this working with Build 3100.

Also installing build 3100 followed by 3500 makes no sense. Every file 3100 installs is replaced by 3500. Every registry change in 3100 is replaced by 3500.

Try HatOnCat's instructions with 3100 first (it's more stable).

P.S. Recommend staying away from Motorola headsets and Jabra 250. Not that they are bad headsets. They are just more unpredictable with these phones. Sony and Plantronics.

Ok didn't know 3100 would not work. My QA department always teases us with the saying "now *WE* know" .

Just be aware with 3500 the memory error may sneak up on you and is slow to reconnect to headset from sleep.

I'm wondering if the thread on the back log of Events is what is eventually messing up some folks BT. And Maybe the hard reset is what is clearing them out. Then they queue up again and break the BT Stack again.

mswlogo - you have a private message.

Just got done with several hours of research. It's my day off, and I was looking for something interesting to do... so learning more about these patches, etc. has kept me out of trouble. (AKA shopping at Fry's, etc. )

Some things I've learned...

1) To backup your phone, just use Activesync's function under Tools! I thought I was gonna have to go drag files by hand or something... not a preferred solution.

2) Applying the patch simply means moving one of the CAB files to the PPC, opening it, and extacting the files to their default locations. Sounds simple enough that *I* can do it.

3) Hard Resets will set the device to it's "like new" state. Excellent in case I make a mistake. And a hard reset is just holding the power button and resetting the device if I understand correctly. I can always RTFM.

4) There are some extremely knowledgable computer people on this forum putting a LOT of time into answering questions and trying to make ALL our devices run for the better. For that, you have my thanks and respect!

I'm running a backup of my PPC-6601 to a folder in My Documents right now. Then I'll backup my primary hard drive's data to my external enclosure drive and know EVERYTHING is about as safe as it can be. My thought is to patch with the 3500 ver B file, and see if I can get tethering working with my 12" Powerbook. That would be VERY cool.

My thanks to HatOnCat, mswlogo, Ehud, and others for your dedication and support of this great device. PDAPhoneHome has become a daily read for me, and you gentlemen are the reason.

Certainly some of you have more computer experience than I do, as I have a two-year technical degree in Computer Information Management Systems, a four-year degree in Business Administration - Management Information Systems, and spent 5 1/2 years doing systems support for Boeing before my layoff and eventual move to management elsewhere. But I love computers (I have 5 or so), electronics (got Logitech 680's for my media room for Christmas), music, movies, and keeping up to date with such toys. I can only presume others of you do as well, and it's a pleasure to communicate with you.

Sincerely,

Merk Man

More from my end...

Having always had trouble configuring my PPC-6601 with my PowerBook, I decided to make some changes. I shortened my computer name, and the shared bluetooth name for my PC. Then I went through HatOnCat's instructions, ignoring steps 0 - 4. (It took me QUITE a while to find the BT Serial Utility, but once I did it was quick work to get it set up per his instructions.)

Once steps 5-8 were complete, I started a ping of www.yahoo.com. I left this run in the background, and disabled my Airport Extreme Network card. Once this was done, my ping was obviously affected. Then I connected the Apple to the PPC-6601 using the Dial Up Networking in OS X. It connected, and for about 30 seconds my laptop was able to ping Yahoo as before, with decent connect times. I used Safari to surf to Apple.com from Yahoo (My Startup Page), and it began to download the front page. However, I got a disconnect message on the PPC-6601. Checking on the Mac, I could not pull up any other web pages. So I told DUN on OS X to close the connection and quit the ping with Terminal Services.

So, it is possible to connect to the Sprint service using DUN and a PPC-6601, even with the "stock" Bluetooth stack. The question is, does the "modified" stack allow that connection to remain active for longer? Is it a problem with some sort of setting on my phone? Do I need to ping something else with Terminal Services? Whatever the case, I'm reassured by the fact that I made SOMETHING happen today... and that is a good start.

Gotcha. So I've skipped a key part, except...

There are occasional problems with the 3500 patch, such as memory errors, bluetooth connections in and out of sleep mode, and longer than usual reconnect times with devices.

All that said, it does sound like Sprint devices have fewer of these problems than VX ones. And if I understand correctly the problems with MS Voice Command have been solved with the 3500 B2 patch.

Kinda thinking I may wait for my new bluetooth headset to arrive before I go ahead and install 3500 over my existing device files. So I have a clear picture of how the headset works with the phone BEFORE I start making changes on my own.

But thanks again HOC. Your work is greatly appreciated!!!

MM

Working great here, thanks hat. Great work.

Now if we could only figure out USB tethering....

See my post on the long patch thread with "updates available".

There is a later 3500 patch I uploaded last night.

You CAN get memory errors with 3500 Build (whether you install 3100 first or not). I can create a memory error at will and I so happened to have 3100 build first. 3100 has nothing to do with it.

The latest patch is very close to what a new PDA2K ROM would put on your phone. And they do not install 3100 first. The ROM includes a sequence of patches.

I believe I described what causes the memory errors in the long patch thread.

I believe the latest patch fixes the delayed connects from sleep.
And I think you can avoid the memory errors (read the other thread).

Got BT DUN working tonight on my 12" pb with the latest 3500 patch only. After the soft reset I tried to turn on the CDMA modem and then the BT modem and got the driver memory error. Soft reset, turned on BT first this time then the CDMA modem and VOILA! No problems here so far although I can't seem to use BT to browse my BT shared folder on the pb from the pda any more.

NOT LIKE I CARE!!! HAHAHAHA

Sadly, the connection is clearly capped by the BT throughput but this is better than no dial-up at all. Big ups to HATONCAT and MSWLOGO.

PS. I did this all on an XV6600.

Well, I broke down and set it up.

First, I tried installing the 3500 "c" on my phone. That caused corruption with the "today" screen, so I did a hard reset, installed the bluetooth firmware with the bluetooth and phone radio off, renamed my phone, re-installed all my apps, resynced the phone to the PC, and finally tried the phone with my PowerBook.

I was getting some silly unavailable error, and that's when I realized I hadn't turned back on the telephone radio (turned off flight mode), even though the bluetooth stack was on and working fine.

Long story long, I've been able to surf the web from my Powerbook for the past 16+ minutes and it seems to work pretty well. Thanks everyone for ALL your help getting this working!

Next step... will the Logitech Bluetooth Mobile Headset work?

__________________
Cingular 8525 with Black 3.0.1 ROM (WM6)
Paired: Sony MEX-BT2500 (car stereo w/ audio streaming, it's AWESOME!), i.Trek GPS w/ i.Guidence software, a few PC's

PS... yes speeds are slow, and faster would be nice. But if this is all I can do while travelling, it's better than nothing. Not sure if those "speed test" web sites work on Safari, but I'm thinking I'll give that a try and see what it says.

Addon: Ok, so I ran Speed Test at bandwidthplace.com. I chose other, then Wireless G3 as my connection type, and ran the test.

Personal test results

Speed

425.3 kilobits per second
Communications 425.3 kilobits per second
Storage 51.9 kilobytes per second
1MB file download 19.7 seconds
Subjective rating Not bad

Not sure how this really stacks up, but it seems a touch faster today since moving my laptop and cell away from my computer desk. I've had the occasional dropped call while at that desk, and I wonder if my Logitech Dinovo bluetooth dongle or other computer equipment might not be a cause of signal issues. But in any event, that's what I come up with.

__________________
Cingular 8525 with Black 3.0.1 ROM (WM6)
Paired: Sony MEX-BT2500 (car stereo w/ audio streaming, it's AWESOME!), i.Trek GPS w/ i.Guidence software, a few PC's

The best speed test is to download and upload a file.

I did the 3500.c update on my xv last night as well & saw the same today screen 'corrpution'. So then I wondered about it a little more. So I did NOT do a hard reset, but instead clicked into the corresponding apps underlying the corrupted screen areas (I had 3 apps). After that, everything repainted w/o a problem (so far).

So it make me wonder that the BT stack upgrade changed the screen paint location(s) (e.g., reloacted stack/heap space I'd guess?) just enough to need the repaint.

But everything appears to be ok & that was w/o a hard reset & reinstall, etc.

Oh yea. And my BT interactions (limited so far to Nextlink AX a littel last night tho) appear to be fine.

Setup everything like you said but used this modem driver: Verzion Support (PC5220). Seems to work pretty well.

<--- Anxiously waits to hear if the driver makes a difference in speed.

__________________
Cingular 8525 with Black 3.0.1 ROM (WM6)
Paired: Sony MEX-BT2500 (car stereo w/ audio streaming, it's AWESOME!), i.Trek GPS w/ i.Guidence software, a few PC's

Well,

I have the verizon XV6600 without camera. I am connecting via BT to the internet with my 12" PowerBook OSX 10.3.7 and NO BT stack updates or patches.

Speeds seem to be as fast as my former Nokia 6820 EDGE connection via BT. I ported a line from ATT to VZW on Friday. I waitied after the 6600 became available through business channels to make sure it didn't seem to be as much of a lemon as my Treo 600, which has a screen die every 2 months (I am on my 5th Treo 600 since July 2004 so I passed it on down as our spare phone).

I was surprised that I didn't need to put in my user ID as phonenumber@vzw3g.com or the password "vzw" like with other dial up connections, and so it took me a full day to figure this part out. Once I got Bluetooth Serial Utility to create a DUN connection to the Pocket_PC that I named VZWBT, and went to network system preference, all I had to do was have it dial #777 (without user name or PW), select the aussie cdmaone script and leave the rest of the settings blank (except I gave it a name).

With ATT I had to enter *99# into the phone number, and leave the user name and PW blank as well.

This is only a backup emergency dial up for when wifi isn't available, and I can still fall back on my Treo600 and "wireless modem" software if I don't mind carryng a USB cable around. Interestingly, when I connect my Zire 72 to the 6600 via BT to download email and surf, it seems much faster - certainly faster than using the previous Nokia 6820 with the palm zire.

People look at me wierd when I tell them my Zire is connected to the internet using my PPC phone

QUESTION: How do I get the PPC to NOT ask me if it is okay to dial out or not? I have the 6600 and powerbook and zire all paired, but there doesn't seem to be something that tells the PPC that the other 2 can be trusted.

__________________
Larry Ganz
http://www.jesusreigns.org
John 3:16

Anyone try this using the ipaq 6315?I have a 12in.ibook running panther and would love to use it as a modem.I would appreciate any suggestions-thanks!-fabbi =)

This is a public response to a PM I got from another mac user, xmit, that I think will be helpful to all, and it was too big to use as a reply to a PM

Hmmmm... I decided to walk through this myself, and open the apps and control panels as I go along, to see my settings and to document what happens and what my thoughts are, like a "log file" to sort out what is happening.

First I made sure I was paired with the XV6600 in bluetooth preferences, and it is, but it is paired as a "computer" not as a phone.

Then I went to Applications/Utilities and opened bluetooth serial utility. I had previously created a new bluetooth serial port in the bluetooth serial utility which I called VZWBT, with direction set to "out", Authentication on encryption off, port type is "modem"... Whoooaaa!

As I was reading my settings from BT serial utility for this reply, and before I clicked on edit to read the settings, it had listed "Pocket PCce" under the Device column, and then when I closed the settings the device DISAPPEARED and I when I tried I couldn't connect with internet connect, just like you. I figured I might have to recreate the port so the device shows up? I thought the key to it not working is that if bluetooth serial utility loses the device name that it is using for Dial up networking, then you stop being able to dial out. That wasn't it, as you'll see later.

I have all three windows open now, BT serial utility, Internet connect, and network control panel, and I decided to see if re-creating a new BT serial port fixes this issue.

However, since I couldn't connect to the internet, the next thing I tried was to see if I could even browse the XV6600 from the Mac, in case my partnershp was messed up. "Browse Device" was unable to validate the XV6600 or find it, as I realized because the XV6600 was asleep - the bluetooth bug was probably stopping it from waking and connecting to the 6600. This confirmed one of my suspicions that not only will BT lose connection to a headset when the phone is asleep, but it will do so with a PC as well. For example, when you have a call come in while you are wearing a BT headset, you have to answer the call with the phone, not the headset button, until the XV6600 re-establishes the connection. Keeping this in mind, after I had the XV6600 awake for a few seconds, I was able to browse it's contents and retrieve files from the XV6600, so I decided to dial out again, using the VZWBT port I had previously created. That gave me a modem error.

I then chose to create a new port, leaving the old one in place, but I named it BT6600 this time. I set it as outgoing, require authentication and show in network preferences, port type modem, then last I went to the "select device" button while the XV6600 was still awake. There it listed my Pocket_PC in the list of devices on the left and I clicked on it. Then it showed all the services in pocket_pc on the the right, and I selected dial-up networking, and clicked okay.

Then I closed system preferences and then re-opened up the network control panel in system preferences. It said "new port BT6600 detected". I selected okay, then went to the "show" drop down menu and selected BT6600. Then I set up the PPP and Modem tabs as I did before. On the PPP tab I named it VZWBT and left the account name, password, telephone number and alternate number all blank. Then I chose PPP options on that page made sure "send ppp echo packets" was turned off. I left the TCP/IP tab alone. I left the proxies tab alone. In the modem tab I chose modem as "au cdmaOne C413S by Sony", enabled error correction, turned off wait for dialing tone, told it to use tone dialing with sound off, and then clickeed the apply now button. The show in modem menu was already selected for me.

Went back to "Internet connect" in the applicationsd folder, and the rest that follows is using only internet connect, which now has both VZWBT listed and BT6600 listed as connections (which should be configured the same). I clicked on BT6600, and everything was blank, being that it was new to internet connect. I clicked on "show modem status in menu bar" so I could access it when I needed to dial out more easily. In the "configuration" drop-down menu I chose "edit configurations". VZW was already in my list, so I didn't have to click on the "+" key to add VZW. For those having to add this setting, everything was left blank and I didn't change it. I chose okay. Then I entered the phone number #777 for the BT6600 internet connect settings, but left name and password blank.

Next I made sure the XV6600 wasn't asleep, so when I hit connect I should not have issues, but I got modem error. So, I tried the old VZWBT connection, and connected to the internet! What?!?!?! This hadn't worked the last time I tried. That was the whole resason for making a new port! I clicked disconnect and tried again with VZWBT, but only the first try had worked. The second try was a bust, again.

This reminded me of the issue I have with my Palm Zire 72, where after I connect the first time then I cannot connect again without a soft reset of the XV6600. So, I soft reset the XV6600 and tried to dial out again with VZWBT. Same modem error, and I saw the "headset" icon come up in place of the 1X icon on the 6600 screen. Weird. Same thing each time I tried to connect. Modem error.

I decided to see if browsing the device is what made it work the last time, since the reset didn't make the difference. So I browsed the device and then tried to connect to the internet while I had the file directory in front of me. Modem error. Tried to download a file with browse device, then tried to connect - modem error. Browsed the device then closed the browse window, then tried to connect and modem error. Tried all kinds of combinations without a difference.

On a lark I tried the BT6600 again, which had never worked, and got connected to internet no problem!!! Twilite Zone Music started to play. Then I clicked disconnect BT6600 in internet connect, and tried to connect again. This time it said "internet connect could not negotiate a connection with the remote ppp server" it was NOT another modem error. I waited a few seconds and tried to have BT6600 connect a third time. Same "could not negotiate" error. Without a soft reset, went back to VZWBT and clicked connect. Didnt work, so it wasn't an issue of having to switch ports each time I dialed out.

So, again, neither VZWBT and BT6600 will connect. Decided to soft reset the XV6600 again. The question I asked myself is, since BT6600 worked the last time, do I now try VZWBT? I waited 10 seconds after the 6600 was done rebooting. Choose to dial out with VZWBT, clicked connect, Modem error. Switched internet connect to BT6600, and connected with no problem!!!! This makes no sense!

So, I am going to leave both serial ports, VZWBT and BT6600, and when I want to dial out I will soft reset first, then try both of them till I get one that works.

Will the ROM update fix this issue? I don't know - I don't want to do the ROM update on my Mac with virtual PC. Each of our two PC laptops only have one USB port, and I have heard of people doing the upgrade having a port lock-up and having to switch ports, which I can't do.

I am as baffled as you are, xmit.

Larry

__________________
Larry Ganz
http://www.jesusreigns.org
John 3:16

Here are instructions for an alternate way to make Mac DUN work, that I haven't tried.

I DO NOT TAKE CREDIT FOR THIS. Another user on these forums or Howardforums.com came up with it so I saved the info in case I ever needed it, and I will post his name for credit when I find the source.

Download the zip file, and it will have 3 files, one for wmodem mac dialer software and one for verizon wireless modem drivers, and a pdf instruction file that I made from his website.

The .zip is 420K in size.

Attached Files

second method bt dun 6600.zip (417.8 KB, 222 views)

__________________
Larry Ganz
http://www.jesusreigns.org
John 3:16

FYI - just now decided to test a connection without a reset, after doing all the above.

BT6600 gave me a modem error even though last time it was the one that worked, but the original VZWBT connection worked.

This time, instead of disconnecting on the mac side, i clicked the icon on the 6600 to show the hidden connection box and clicked disconnect there. Re-tried a connection with VZWBT and it worked without error. Disconnected from the XV6600 side again, and tried it a third time, no problem connecting with VZWBT.

This time I disconnected from the mac side (the button in internet connect). Tried to connect a 4th time in a row and had no modem error, but could not negotiate a connection with VZWBT. Switched to BT6600 and tried to connect, got modem error. Back to VZWBT, still no modem error, but could not negotiate a connection.

Time to soft reset XV6600.

After the reset tried BT6600 and it woked just fine.

I could go on and on, but my plan is the same as above - to just soft reset the phone when I want to make a internet DUN connection, and to use whichever of the two bluetooth ports that works the first time I try to connect....

__________________
Larry Ganz
http://www.jesusreigns.org
John 3:16