Quote:
Originally Posted by lllboredlll
It's requires a program to call for it to function. Whether it be thru a driver or a dll, something has to tell WM to connect to the IP and retrieve the information. The radio enables AGPS thru the fix GC developed but WM has to interface from that point on.
|
Well GC's aGPS fix simply imports the SUPL AGPS registry values. However, if no application/driver is looking for those values and thus not acting on them, it won't really do anything.
Here is GC's aGPS fix's _setup.xml (there are no files, only registry values):
<!-- GC Verizon aGPS Provisioning -->
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Software\HTC\SUPL AGPS">
<parm name="EnableAGPS" datatype="integer" value="1"/>
<parm name="EnableGPSSmartMode" datatype="integer" value="1"/>
<parm name="EnablePDEIPFromNV" datatype="integer" value="0"/>
<parm name="NumberFixes" datatype="integer" value="999999999"/>
<parm name="QoSAccuracy" datatype="integer" value="50"/>
<parm name="QosPerformance" datatype="integer" value="89"/>
<parm name="TimeBetweenFixes" datatype="integer" value="1"/>
<parm name="ServerIP" datatype="string" value="66.174.95.132"/>
<parm name="ServerPort" datatype="integer" value="8888"/>
<parm name="GPSMode" datatype="integer" value="2"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
<!-- End GC Verizon aGPS Provisioning -->
So here's some really good situations to consider:
Are Sprint TPs flashed to VZW ROMs able to use aGPS? If yes, that means that drivers included with the VZW ROM are aGPS capable. If not, then the ROM is missing something.
Are VZW TPs flashed with the Sprint Radio ROM and Bored's GPS fix (modded Sprint PRI) able to use aGPS. If yes, that means that the VZW radio is incapable of aGPS while the Sprint Radio is.