Please see the condensed list below for details of some changes found in this CE07 update for the SCH-i770.
The latest Microsoft AKU Update 1.5.1.
Enhanced zoom for Internet Explorer
Slight UI Modifications.
Various additional improvements to improve handset function.
Open Standalone LBS Supported and Performance Enhanced. (This may Support 3rd Party Applications)
MMS Over GPRS Supported. (GSM Mode)
Softswitch For GSM (Allows handset to select correct network overseas)
Multiple Qualcomm Patches Applied to Improve Phone Performance.
VZ Access Manager Supports Bluetooth Connection (SPP).
So, when you click on the VISTA link, it does not look like they have the vista software there.. I'm downloading the XP one right now.
hmmm- looks like the vista instructions are cut and paste from the xp instructions and then edited- but they left in one reference to active sync instead of wmdc. and the have the wrong link for the file...
Actually, the same package works on either Vista or XP. When you run it it must detect what your OS is, because it comes up and says connect your device using Activesync when I run it on XP, and it said connect using Mobile device Manager when I ran it from Vista/Win7
Having said that... I upgraded using XP, so if Vista hoses your device, don't yell at me.
Open Standalone LBS Supported and Performance Enhanced. (This may Support 3rd Party Applications)
So anyone know what this means, exactly?
I think I will give this a day or two before I start doing anything. I won't be in town starting tomorrow and I really don't want to be without a phone on the off chance that something goes haywire.
I think I will give this a day or two before I start doing anything. I won't be in town starting tomorrow and I really don't want to be without a phone on the off chance that something goes haywire.
Please let me know how things go.
I'm about to run the update but in a nutshell that means gps is "unlocked"
LBS= location based services.
open standalone means it will work without verizon's assisted gps (AGPS) servers. VZNAV uses agps servers to get faster fixes and to work in gps trouble spots like inside buildings and in cities.
looks like com9 is the deal- that looks like what google maps needs too.
set to allow windows to manage gets you nada. If I set to com9 at least I get "seeking gps satellites" with a pile of numbers in brackets- I'm thinking the numbers are the gps sats that it thinks should be in view.
seems to take an awfull long time to be getting a lock- but without assisted GPS I think that is going to be par for the course. Hopefully subsequent locks will be much quicker.
But even without that at least googlemaps is doing the cell tower approximation thing that it didn't do before- so at least you get in the ball park quickly.
Actually, the same package works on either Vista or XP. When you run it it must detect what your OS is, because it comes up and says connect your device using Activesync when I run it on XP, and it said connect using Mobile device Manager when I ran it from Vista/Win7
Having said that... I upgraded using XP, so if Vista hoses your device, don't yell at me.
just to confirm it works fine- the first splash screen that you have to agree to actually says something like "requirements: win xp spX or Vista pc"
what's interesting is some serial number or something has been changed someplace.
I have good mobile messaging- it backs up to the sd card so it doesn't need to download all the configuration info again from the server. It locks the backup on the card to the device so you can't steal a card to get someone elses data.
when i try to restore it complains:
"The serial number on the memory card: MEID15 digit id number ending in 7) does not match the serial number on the handheld: MEID(same exact 15 digit number except last digit is now 6)"
help me out but isn't MEID like the new and improved ESN? did the update change the saga's ESN or maybe just the way the info gets passed to other programs is slightly off?
I need to blow away my good mobile messaging on the server and start from scratch becasue it thinks my account is installed on another mobile device (the other check digit...)
I wonder if exchange active sync is going to behave similarly.
the MEID is differnt but it's not a different check digit. The problem is the old firmware was reporting the check digit so 14 digit MEID with 1 check digit- total of 15 digits.
NEW firware is apparently only reporting 14 digit MEID sans check digit.
(sorry i got confused becasue the last digit of my 14 digit MEID is 6 and with the checkdigit it's it ends in 67)
anyone remember the code to punch in the dialer to get the phone info- I'd like to see what the phone iteself says the check digit should be.
it's **772
and it reports the MEID in hex- whereas good is doing it in decimal. I tried an online converter but i came up with something all together different....