|
|
10/05/2009, 12:07 PM
#34
 Originally Posted by jhoff80
Okay one thing about the AFLT mode... that might be bad to enable, actually. The Pre already uses an tower-assisted type mode in software, based on Google stuff I believe. That's why some applications can get an instant 'fix' on your position and then ask you if you want a more detailed position, making AFLT redundant, and no better of a failsafe since the Pre already does similar BEFORE everything else.
I really wouldn't worry about it.
It may be that WebOS accesses the AFLT mode directly, but I suspect what happens is that it's using the aGPS information to "guestimate" a fix before it gets a real one from the towers.
aGPS and AFTL is somewhat similar because you're getting location information from the towers, just the aGPS info you get is more geared towards how to find sats, but that still gives you a rough position (as your location on the planet is one of two keys to finding the sats, that and the current time).
I can't see any harm in enabling AFLT. It'll only work if the towers support it and nothing else works, providing a fall back method. If you're concerned though, just leave it disabled, there was no point in enabling it on the 800w as the drivers didn't support it, so we left it disabled there. But even if Palm doesn't support AFLT currently, they may add support in the future.
Originally Posted by SiniStereO
Out of curiosity, care to speculate as to why Palm didn't enable these options at the factory?
It's really hard to tell. With the 800w my guess was that since it was originally a Verizon device, it was very likely that the block never got removed when Sprint picked it up. With the Pre, that's obviously not the case (plus there isn't the limitation of needing the time off the network).
There could be a couple of reasons:
- Sprint wanted it locked down.
- It was setup this way to encourage providers such as Verizon to pick it up.
- Palm always intended to unlock it down the road.
- It got overlooked.
Originally Posted by willsurg
Hey how did you guys get tech support to release the SPC/MSL code. I tried saying I needed to do a factory reset and was told that web doctor does not require that information and that I should try that program first. anyone please help!!
Last time I called in I just told the rep that I wanted my MSL code. I told him that they give out the code when the phone is provisioned, so he should have no problem giving it to me. He didn't.
Originally Posted by dragbug
Just curious but is it possible that at some point, these options can be done without rooting and using the tools mentioned? First, I don't want to get into the whole rooting. I've used linux distros so I am somewhat familiar with it I just don't want to do it on the phone. Secondly, I don't have a 32bit OS to run the drivers so I can't do squat anyway.
Unfortunately you cannot do this without rooting your phone.
Originally Posted by gbp
ebagg333
Should I choose "Charge Only" when connected to Pre using the cable.
And what version of the PALM SDK you used ?
Yup, I used Charge Only. I used the latest version of the SDK. You can also use novaterm instead of the command line (though looks like you're already past that  ).
Originally Posted by gbp
hmm
I am getting the following error
C:\Program Files\Palm\SDK\bin>novacom -t open tty://
root@castle:/# mpt 0d
mpt 0d
novacomd socket was closed prematurely
novacom: unexpected EOF from server
The data port is dead on the phone. Novacom won't run.
I will have to reset the phone to run the novacom.
I will try using it as USB drive.
You turned on developer mode, yes?
From another thread:
Originally Posted by dianehelen
The permision, and/or socket closing issues I was having, could they be caused or at least aggrivated by my Novaterm Lan2 connection attempting to start? I noticed it trying to come up on my system tray, but with limited connectivity. ONce I disabled this, the socket did not seem to keep disconnecting in my cmd window??
|
|
|
