
Originally Posted by
midiology
Ok to all the folks that have a new phone or have hard reset the phone,, these settings will absolutely not get your browser past the provisioning state,, if your browser is trying to set up vision services and hangs,, it is because of this.. ill try to explain..
You see I reset the phone when I got it.. like a moron.. and after resetting it I never could get the browser to come up again,, it kept trying to update my account...
so here is what the deal is,, and how I think I got it back...
your browser doesnt know if you have your ppp settings installed or not..
it basically uses a policy,,
when the phone is new,, or reset,, when you open the browser it opens up a hidden NAI application in the background to provision your Sprint vision account,,, once the vision is updated,, it writes to the browser policy telling it it is complete,, then the browser will boot on its own without checking your vision data service... but this will not work on cricket since it is not on sprints vision service...
Sooooooooo... if this is your case... then following the steps Ive provided,,, start from the beginning,, but this time start clean,, go into qpst and clear all account info and ip address`s from M.IP and PPP config... then start from the very beginning and add it all back in,,,
then when completed , go to phone,, do the ##brew# enter spc
then youll see a bunch of little icons,, tap each one once while looking at the bottom of the screen,,, look until you see something that just says browser,, double click on this icon,, it may try to bring up your browser,, once you do this, back out and go back to brew and look for the icon that says sde_app there are a couple that say sde,, but use the one that says SDE_APP,, double tap on this it should bring up a list of like Start sde:addr start sde:mailto etc..
click on start sde:http and then I think you click browse,, the browser may or may not come up when you click this,, but i did this and after exiting brew it no longer tried to verify account,, it just brought the browser up properly like it should,, I dont know if it was a coincidence or what but it got it back..