I was playing around yesterday with BT PAN on the PPC 6800, and was able to get the wireless internet working on my laptop over Bluetooth. However, while I was in the middle of a data session my phone suddenly did a soft reboot and ever since that reboot I have been unable to access Vision services, getting an Error Code 67 Registration failure when attempting to connect. After about 6 calls to Sprint Customer Service/Technical Support they are now telling me, after reprovisioning the device, reconfiguring the IP address / password information, that I will have to do a hard reset on my phone and make sure to copy the pim.vol file to the storage card so that I do not loose any "settings". Not only does this prevent me from accessing internet, but in order to stop the beeping and vibrating I had to disable almost all sounds, notifications, and reminders coming from the phone.
Does anyone know of any other way to get my phone working as it should without doing a hard reset? I have the unlock code at hand avail as necessary.
have you tried deleting both Sprint connections & then adding them manually? tried initiating an over the air provisioning through the phone settings menu? or tried changing your Vision password from their website?
HA! this same thing happened to me a couple days ago when i was trying to get an ad hoc network setup on the Mogul to allow the ipod touch to use it for internet access.
i kept fooling around and fooling around and a day or so later i got this error you have. popup after popup! it was insane! i then did the iota and it could not connect to vision since i was having issues dialing #777, so then i ended up having the popup about the 67 error and a 1012 error about data provisioning. i went up to the top of the tech tree at sprint
and the only thing they could do was remove the data package off the account and reapply to see if that would work. i told him no and to have a good day and hung up.
basically you are going to have to do a hard reset. thats what i did last night (used clear storage) and am reinstalling as we speak. i needed to anyway because i like to spring clean this thing every few months. im now afraid to re try the ipod touch adhoc setting for fear this will happen again.
but yeah it was insane... i could barely use the phone due to the popups poping up every few seconds! it was insane!!!
i deleted all those settings and even went into the ##data and restored the data profile.. nothing! i had sprint PUSH (basically the equivalent of shoving it down the phones "throat") the data profile and it would not take it. its the phone thats the issue, not anything on sprints end.... hard reset is in order.....
Try starting to Internet Sharing app, click "Connect" and immediately, before it can connection, click "Disconnect". That has fixed it for me in the past.
Try starting to Internet Sharing app, click "Connect" and immediately, before it can connection, click "Disconnect". That has fixed it for me in the past.
The thread also explains a newer method of Ad Hoc WiFi Internet sharing, written with the HTC Mogul in mind.
Thanks! I recycled the Internet Connection Sharing for both Sprint PCS and Phone as Modem and it fixed the problem, saving me from having to do a hard reset on my device.
Marctronix, this happens because of a .dll Sprint injects into the Internet Sharing process, as a poor mans way to prevent Sprint users from tethering.
Before, to use the Internet Sharing application, users would start an Internet connection via another means (ie starting Internet Explorer) before starting the Internet Sharing application.
The problem would occur if the phone got reset/restarted or the Internet Sharing app got terminated before the "disconnect" properly processed, which caused this error 67 bug.
The link provided above gives information on how to remove this injection so you can connect using the Internet Sharing application directly, and not have to deal with error 67 because of this issue again.
taly,thx for responding. im going to use your usb adhoc option.. your explanation makes sense because i was testing the other method several times and then this bugg popped up. thank you.