New Verizon GPS Fix

Discussion in 'Moto Q Hacks' started by wnrussell, Dec 22, 2008.

  1. Aixelsyd

    Aixelsyd Active Member

    Joined:
    Jan 25, 2009
    Messages:
    1,406
    Likes Received:
    0

    With that said would you want me to do that edit to mine and run another log? I have not yet done the TRM edits to my device as of yet per our other discussions on this.

    However all other edits are done that have been posted to date so far, along with any others we did while going over this on gtalk. Juts let me know and I can do another run after making those changes and see what we get.
  2. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    May as well give it a shot.
  3. Aixelsyd

    Aixelsyd Active Member

    Joined:
    Jan 25, 2009
    Messages:
    1,406
    Likes Received:
    0
    Will do bud a bit later. After running the log I'll get that over to ya also then labeled so you know what it is.
  4. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    Well...I sort of fell off the wagon...and I made a bunch of edits that emulate the configuration of non smartphone Motorolas with Telus firmware that GPS functions work for Java apps.
    The location agent is enabled now and you can see the results in the initialization sequence below.
    Lots more things appear to happen correctly but I still ultimately timeout with no fix.
    But the stand alone fallback error is definitely not occuring.
    Note the location agent acknowledges the request for trusted access and receives a "true" response from the PDE server.

    I don't think the TRM edits are required as I undid them on mine without affecting the latest results.


    EVENT EVENT_T_HDR_SLP_RTC_MSG_TX 12:06:38.685 Nak <--- STREAM2
    EVENT EVENT_T_HDR_AMP_RXATI_MTCH 12:06:38.952 fnc:hdramp_match_receive_ati_address FALSE caller:CCMAC
    EVENT EVENT_T_HDR_AMP_RXATI_MTCH 12:06:38.952 fnc:hdramp_match_receive_ati_address FALSE caller:CCMAC
    EVENT EVENT_T_HDR_AMP_RXATI_MTCH 12:06:38.952 fnc:hdramp_match_receive_ati_address FALSE caller:CCMAC
    EVENT EVENT_T_HDR_AMP_RXATI_MTCH 12:06:38.952 fnc:hdramp_match_receive_ati_address FALSE caller:CCMAC
    EVENT EVENT_T_HDR_AMP_RXATI_MTCH 12:06:38.952 fnc:hdramp_match_receive_ati_address FALSE caller:CCMAC
    EVENT EVENT_T_HDR_OVHD_QC_MSG_RX 12:06:38.953 received Quick Config message
    EVENT EVENT_T_HDR_IND_IGND_STATE 12:06:38.953 CCMAC_SLEEP_CAPSULE_DONE for:IDLE state:INACTIVE wrong state
    EVENT EVENT_T_HDR_IND 12:06:39.005 LMAC <--- CCMAC_END_OF_SYNC_CAPSULE (N/A)
    EVENT EVENT_T_HDR_OVHD_M_IGN_RED 12:06:39.006 SectorParameters already stored
    EVENT EVENT_T_HDR_IND_IGND_STATE 12:06:39.006 CCMAC_END_OF_SYNC_CAPSULE for:IDLE state:INACTIVE wrong state
    EVENT EVENT_GPS_PD_SESSION_START 12:06:39.331 start_src: MOBILE_INITIATED op_mode: MS_BASED session_type: GET_NEW_POS privacy: NONE data_dl_type: PERIODIC transport_type: IP num_fixes: 51711 fix_period: 2000 prq: 16 threshold: 50
    EVENT EVENT_T_HDR_IND 12:06:39.380 LMAC <--- CCMAC_END_OF_SYNC_CAPSULE (N/A)
    EVENT EVENT_T_HDR_OVHD_QC_MSG_RX 12:06:39.380 received Quick Config message
    EVENT EVENT_T_HDR_IND_IGND_STATE 12:06:39.381 CCMAC_END_OF_SYNC_CAPSULE for:IDLE state:INACTIVE wrong state
    EVENT EVENT_GPS_DATA_DOWNLOAD_START 12:06:39.385 data_type: LOC_EPH, sv_mask: 0xffffffff
    MSG Position Engine/Medium 12:06:39.382 cd_decode.c 01942 SVs with eph: 19
    MSG Global Positioning System/Medium 12:06:39.382 pdsmpd.c 03122 =PDSM_STDBG= << pe_stat.eph_dload 0 eph_validity 1 meas_aa 1
    MSG Position Engine/Medium 12:06:39.382 cd_getpt.c 02011 NAV: Standalone flag 0
    MSG Position Engine/High 12:06:39.383 pepdsm.c 04825 NavDataCheck: No MS location, Fail 1
    MSG Position Engine/Medium 12:06:39.383 cd_decode.c 01942 SVs with eph: 19
    MSG Global Positioning System/Medium 12:06:39.383 pdsmpd.c 03157 =PDSM_STDBG= >> pe_stat.eph_dload 0 eph_validity 0 meas_aa 1
    MSG Global Positioning System/High 12:06:39.383 pdsmpd.c 03165 =PDSM= LR_U=10000000m,Eph=0(Y=1),ALM(Y=1)=1
    MSG Global Positioning System/High 12:06:39.383 pdsmpd.c 03309 =PDSM= Process Fix request from Client
    MSG Global Positioning System/Medium 12:06:39.385 pdsmpd.c 03635 =PDSM= Process MS based only session ..
    MSG Global Positioning System/High 12:06:39.385 pdsmpd.c 03653 =PDSM= Dload data for MS-based only
    MSG Global Positioning System/High 12:06:39.385 pdsmpd.c 03689 =PDSM= Dload data,req=65544,resp=1024
    MSG Global Positioning System/High 12:06:39.385 pdsmpd.c 05956 =PDSM= New ses,substate=3
    MSG Global Positioning System/Medium 12:06:39.385 pdsmsm.c 00383 =PDSM_STDBG= SM - Smart Mode not allowed when V1/V2 is enabled
    MSG Global Positioning System/High 12:06:39.385 pdsmpd.c 05995 =PDSM= New session initiated
    MSG Global Positioning System/High 12:06:39.385 pdsmpd.c 06019 =PDSM= Need to check with LCS Agent
    MSG Global Positioning System/Medium 12:06:39.385 pdsmpd.c 06028 =PDSM= Active client=2, for fix
    MSG Global Positioning System/High 12:06:39.385 lcsagent.c 01166 Req for Auth from PDSM,n=999999999,type=1,mode=2
    DIAG TX Extensible Parameter Retrieval Request 12:06:30.265 Length: 0005
    MSG Global Positioning System/High 12:06:39.385 lcsagent.c 01187 Trusted MO request, return true
    MSG Global Positioning System/High 12:06:39.385 pdsmpd.c 05540 =PDSM= Use trusted PDE adrs,ip=-658076836,port=8889
    MSG Global Positioning System/Medium 12:06:39.385 pdsmpd.c 06096 =PDSM= LCS agent allowed the session

    MSG Global Positioning System/High 12:06:39.385 pdsmpd.c 06247 =PDSM= PDE needs to be contacted,open con
    MSG Global Positioning System/High 12:06:39.385 pdsmpd.c 05821 =PDSM= MSBased download, check if throttling is required
    MSG Global Positioning System/Medium 12:06:39.385 pdsmpd.c 06260 =PDSM= No throttling necessary...
    MSG Global Positioning System/High 12:06:39.385 pdsmpde.c 00446 =PDSM= Wait for disconnect...
    MSG Global Positioning System/High 12:06:39.385 pdsmpd.c 09519 =PDSM= Trigger CDMA Srch to start PPM
    MSG GPS Searcher/Medium 12:06:39.385 srchppm.c 05941 Got START_PPM
    MSG GPS Searcher/Medium 12:06:39.385 srchppm.c 05297 PPM scheduled to start on TC/PC
    MSG GPS Searcher/Medium 12:06:39.385 srchppm.c 05435 Go to PC state to run PPMs
    MSG GPS Searcher/Medium 12:06:39.386 srchgps.c 11220 GPS friendly wakeup
    MSG Searcher/High 12:06:39.386 srchint.c 00715 Requested 1x rude wakeup. srch_state=7
    LOG System Arbitration Module 12:06:39.386 Length: 0023
    MSG Legacy/Medium 12:06:39.386 sam.c 01165 Lock denied: M=0, D=280, LO=2
    LOG System Arbitration Module 12:06:39.386 Length: 0023
    MSG Legacy/High 12:06:39.386 srchzz_is2000_sm.c 01103 Can't get lock for rude wakeup, wait for notify
  5. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    And the following is the recurring error sequence that I get consistently now.



    MSG 1xEV-DO Protocol/Medium 12:07:10.953 hdrovhd.c 03374 QC. SecID24:74242 CCode:36 SSig:3 ASig:1 Users:3
    MSG Global Positioning System/Medium 12:07:10.955 pdsmtask.c 03993 =PDSM= pe response timer expired
    MSG Global Positioning System/High 12:07:10.955 pdsmtask.c 03349 =PDSM_STDBG= timeout Tf1-x
    MSG Global Positioning System/High 12:07:10.955 pdsmtask.c 03389 =PDSM= PE Response timeout
    MSG Global Positioning System/Error 12:07:10.955 pdsmpd.c 06362 =PDSM= PE Response timeout
    LOG Internal - GPS Position Engine Info 12:07:10.955 Length: 0506
    LOG GPS PE Position Report 12:07:10.956 Length: 0090
    LOG Internal - GPS PE Position Report Extended12:07:10.956 Length: 0420
    LOG GPS Position Engine Full, Version 2 12:07:10.956 Length: 0506
    MSG Global Positioning System/High 12:07:10.956 pdsmnmea.c 02039 =PDSM= nmea:NmeaDataUpdate
    MSG Global Positioning System/High 12:07:10.958 pdsmpd.c 12895 =PDSM= op Complete,status=12,substate=2
    MSG Global Positioning System/High 12:07:10.958 pdsmpd.c 13174 =PDSM= Fix operation completed...
    MSG Legacy/High 12:07:10.958 mot_lbs.c 01065 =MOT_LBS= PD Event = 0x01000000
    MSG Global Positioning System/High 12:07:10.958 pdsmpd.c 13230 =PDSM= err_c(A)=0,err_c(B)=1,total=1
    MSG Global Positioning System/Medium 12:07:10.958 lcsagent.c 00176 LCS agent handling LR resp,index=-1
    MSG Global Positioning System/Error 12:07:10.958 pdsmpd.c 13282 =PDSM= Error_cnt >= threshold..Exit sess
    MSG Global Positioning System/Medium 12:07:10.958 pdsmpd.c 13283 =PDSM= last_error=2, err_type=0
    MSG Global Positioning System/Error 12:07:10.958 pdsmpd.c 01245 =PDSM= Abort and notify, error=12 type=0
    MSG Global Positioning System/High 12:07:10.958 pdsmpd.c 07149 =PDSM= nmea:pDSM_PD_EVENT_END - pd_event:12
    MSG Legacy/High 12:07:10.958 mot_lbs.c 01065 =MOT_LBS= PD Event = 0x00000010
    MSG Legacy/High 12:07:10.958 mot_lbs.c 01902 =MOT_LBS= PD Event End Error: Fix ID = 1, Err = 1460
    DIAG TX Extensible Parameter Retrieval Request 12:07:01.842 Length: 0005
    MSG Global Positioning System/High 12:07:10.959 pdsmpd.c 04247 =PDSM= Ending Session Fix..
    MSG Legacy/High 12:07:10.959 mot_lbs.c 01065 =MOT_LBS= PD Event = 0x00000008
    MSG Position Engine/Medium 12:07:10.959 pepdsm.c 05266 AlmFlashTime 928462438: wk 1535, ms 94438605
    LOG 1xEV-DO Data Rate Control Channel - ARQ Buffer, Version 212:07:10.959 Length: 0104
    LOG 1xEV-DO Reverse Activity Bits Buffer 12:07:10.959 Length: 0012
    MSG Position Engine/Medium 12:07:10.960 pepdsm.c 05116 EphFlashTime 928498022: wk 1535, ms 130022467
    MSG Position Engine/Medium 12:07:10.960 pepdsm.c 05142 SV 3 UpdateTime 928498027
    MSG Position Engine/Error 12:07:10.961 pepdsm.c 05156 Ephemeris will not be saved for more than 16 Svs
    MSG Searcher/Searcher 4 12:07:10.975 srch4drv.c 02385 Started search for HDR_S on HPQ0 with 7 tasks
  6. Aixelsyd

    Aixelsyd Active Member

    Joined:
    Jan 25, 2009
    Messages:
    1,406
    Likes Received:
    0
    Anything you need me to edit and try to see if I can come up with the same results on my end bud. Just let me know the details and I'll get on it as time permits me to
  7. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    The last log you sent still seems like the logging view config is not getting everything.
    I know we went over that already but I still don't understand why your logss look so different than mine. Yours still do have the recurring stand alone fallback session active error.

    I will post the new edits I used to get these results, they are mostly a whole series of items activated with 0 values as well as setting the location agent to 01 instead of 00 and leaving the trusted app settings at 10.
  8. Aixelsyd

    Aixelsyd Active Member

    Joined:
    Jan 25, 2009
    Messages:
    1,406
    Likes Received:
    0
    Sounds good bud. I'll keep an eye out for them and then move forward from there. This time tho I'm going to take Q9Naps *.xls and start a new column and go back over each and every edit to make sure they are set exactly the same one my deivce. So then when I send the log I'll attach it so you can see exactly what settings are there so we are on the same page. That way if I still have the issue we can decide what to do/try. Worse case if you want me to I'll reflash and start it over. I do have the the QPST SP backup from the the first night right before we started this, so it's a matter of 20 mins to reflash no biggie to me. I'd rather see us on the same page then not getting the same results.
  9. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0

    Attached Files:

  10. Aixelsyd

    Aixelsyd Active Member

    Joined:
    Jan 25, 2009
    Messages:
    1,406
    Likes Received:
    0
    I won't have time tonight bud but I will compare your spreadsheet to the settings on my phone and set them to be the same if I see any difference. If I don't find anything off the only other thing I can think of is for me to reflash this bad boy again and reactivate it. To then start fresh with the edits and see if we get closer to having the same results in our logs.
  11. poboy975

    poboy975 New Member

    Joined:
    Mar 11, 2008
    Messages:
    50
    Likes Received:
    0
    hello, ok I've been following the edits here, and I ran through the xls file cellzealot uploaded. I have mad all the same edits except for one, which was different in my default NV Item 650 default is 0 and inactive, the mod is 0 and active, my default was active and value 0x8A...I left that one alone. I ran a log view and ran google maps, it tried to get a fix with no luck, I'm including a copy of the xls file with my default marked, and a txt file of my log and also an item save isf.

    Attached Files:

  12. hachu

    hachu New Member

    Joined:
    Feb 4, 2009
    Messages:
    234
    Likes Received:
    0
    Hey, so I was reading the NV Item config list.
    I'm guessing the Mod Value is the value you're inserting into the phone right?

    I got a few questions?
    1) Why is the LO Calibration Offset being changed to 0x0028?
    2) Why is the PCS RF Delay being changed? Has this affected anything?
    3) Have you or anybody else checked to see what happens if Dynamic Mode is set to other values? If so, what kind of stuff changed? Can you try 4? If you try 4, let me know if the V1/V2 smart messages disappear.
    4) Likewise, GPS Recieve Chain Configuration? Other values tried? This seems like it may need more investigation.
    5) What is #1624 and #1713?

    Based off the recent log from outside, can you check what the value for NV Item 32, 33, 176, and 177 are? (They were mentioned in the log as being loaded)

    In the recent 2 logs including the log from outside, there's something wrong. What happened to all the AA Data GPS searcher messages? It seems to imply that some settings were applied that caused satellite search jobs to not get set up and run.
    Look in past logs for the text "SRCH_START", "GPS got RF lock", and especially NEW_PK_FOUND.
    Those are things we definitely need to investigate. Could people who are trying these mods try them individually and see what mod caused those to disappear?
    An old log that had them was "Q9c_Generic_Current" and "TRM_EQS_Test".

    Thanks!
  13. poboy975

    poboy975 New Member

    Joined:
    Mar 11, 2008
    Messages:
    50
    Likes Received:
    0
    hello, ok so I've tried a few things. I looked at my nv items
    32 = nam=0, min1[0]=0x0031A00D,min1[1]=0x0031A00D
    33 = nam=0, min2[0]=0x00C9,min2[1]=0x00C9
    176 = nam=0, imsi_mcc=0x00D1
    177 = nam=0, imsi_11_12=0x63
    1624 = 0x14EC
    1713 = 0x152D

    I tried nv item 3756 dynamic mode as value 4, no change in log. tried as value 1, no change in log. returned to 3. changed 1992 lcs agent value to 0 and got a significantly different log. much bigger much faster, no more smartmode errors. I've saved the isf and uploaded to rapidshare, its about 4 megs unzipped.
    http://rapidshare.com/files/243216175/QXDM_NV_Item_Poboy975-6-10-09-1993-0.zip.html

    edit ok made another change and got this:
    MSG Global Positioning System/Medium 04:11:49.746 uapdms.c 01218 Handling SS event 0...
    MSG Global Positioning System/Medium 04:11:49.746 uapdms.c 01224 SS event mask 0x4000000...
    MSG Global Positioning System/Medium 04:11:49.746 uapdms.c 01228 hdr_hybrid 1
    MSG Global Positioning System/Medium 04:11:49.746 uapdms.c 01270 CM_SS_BASE_STATION_PARMS_CHGD_MASK set by CM
    MSG Global Positioning System/High 04:11:49.748 pdsmtask.c 02454 =PDSM= Received Base Station Info 2
    MSG Global Positioning System/Medium 04:11:49.748 seedposssinfo.c 00312 =PDSM_STDBG= sid 20 wk 1535 ms 360709748
    MSG Global Positioning System/High 04:11:49.748 pdsmtask.c 02476 =PDSM_STDBG= BS Info:sid 20
    MSG Global Positioning System/High 04:11:49.748 pdsmtask.c 02484 =PDSM_STDBG= bslat [0.25 S] 0
    MSG Global Positioning System/High 04:11:49.748 pdsmtask.c 02486 =PDSM_STDBG= bslat [deg 10^6] 0
    MSG Global Positioning System/High 04:11:49.748 pdsmtask.c 02488 =PDSM_STDBG= bslat [rad 10^6] 0
    MSG Global Positioning System/High 04:11:49.748 pdsmtask.c 02491 =PDSM_STDBG= bslong[0.25 S] 0
    MSG Global Positioning System/High 04:11:49.748 pdsmtask.c 02493 =PDSM_STDBG= bslong [deg 10^3] 0
    MSG Global Positioning System/High 04:11:49.748 pdsmtask.c 02495 =PDSM_STDBG= bslong [rad 10^3] 0
    MSG Global Positioning System/High 04:11:49.748 pdsmtask.c 02498 =PDSM_STDBG= nsrhwin 9

    MSG Global Positioning System/Medium 04:11:49.786 tlm.c 01466 Got event from pdsm_comm_task
    MSG Global Positioning System/High 04:11:49.786 pdsmtask.c 02539 =PDSM= PDSM event mask=16
    MSG Global Positioning System/Medium 04:11:49.786 pdsmtask.c 01282 =PDSM= PTLM State=1
    MSG Global Positioning System/High 04:11:49.786 pdsmpd.c 12895 =PDSM= op Complete,status=7,substate=3
    MSG Global Positioning System/High 04:11:49.786 pdsmpd.c 09574 =PDSM= Trigger CDMA Srch to end PPM
    MSG GPS Searcher/Medium 04:11:49.786 srchppm.c 05959 Got END_PPM
    MSG GPS Searcher/High 04:11:49.786 srchppm.c 05700 PPM session end requested
    MSG GPS Searcher/Medium 04:11:49.786 srchppm.c 00868 Sent retry sleep request to MC
    MSG Global Positioning System/Medium 04:11:49.787 pdsmsm.c 00406 =PDSM_STDBG= SM - NV allows Smart MSB
    MSG Global Positioning System/Error 04:11:49.787 pdsmpd.c 12999 =PDSM= Error in Dload operation
    MSG Global Positioning System/Medium 04:11:49.787 pdsmsm.c 00406 =PDSM_STDBG= SM - NV allows Smart MSB
    MSG Global Positioning System/Medium 04:11:49.787 pdsmpd.c 13075 =PDSM_STDBG= SM - case_begin: NavData DL failure when Smart MSB is allowed. fallback to Demod
    MSG Global Positioning System/Medium 04:11:49.787 pdsmpd.c 13096 =PDSM_STDBG= SM - Data socket is closed so fallback to Demod right away.
    MSG Global Positioning System/Medium 04:11:49.792 pdsmsm.c 00262 =PDSM_STDBG= SM - dbg: fallback_mode 0x2
    MSG Global Positioning System/Medium 04:11:49.792 pdsmlog.c 00570 =PDSM_STDBG= SM - event: std fallback begin
    MSG Global Positioning System/High 04:11:49.792 pdsmpd.c 13109 =PDSM= Pending fix request,proceed
    MSG Global Positioning System/Medium 04:11:49.792 pdsmsm.c 00406 =PDSM_STDBG= SM - NV allows Smart MSB
    MSG Global Positioning System/Medium 04:11:49.792 pdsmpd.c 12748 =PDSM_STDBG= SM - Need Demodulation Session for Standalone
    MSG Global Positioning System/Medium 04:11:49.792 pdsmdemod.c 00551 =PDSM_STDBG= SM - Demod success criteria check is NOT required
    MSG Global Positioning System/High 04:11:49.793 pdsmdemod.c 00559 =PDSM_STDBG= Init. Demodulation Session...
    MSG Global Positioning System/High 04:11:49.793 pdsmdemod.c 00563 =PDSM_STDBG= Demod Sess State PDSM_SESSION_STATE_DEMOD_ENTRY
    MSG Global Positioning System/High 04:11:49.793 pdsmpd.c 10260 =PDSM= PDSM initializing GSC...
  14. hachu

    hachu New Member

    Joined:
    Feb 4, 2009
    Messages:
    234
    Likes Received:
    0
    That log you just added in the edited message. What did you change to get it? (It's not necessarily a good or bad thing because enabling/disabling it can cause a different feature to not get run)

    Basically, that block in bold is the location information for Cell Tower #20. Apparently it's all zeros. So obviously, no trilateration could be performed using it.
  15. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    Ok, after all the experimental edits I had done, I definitely broke something by activating items that were then preventing the default OS selections from working.
    I set everything back to default values as per Hachu's suggestion and started getting the simultaneous mode error again despite that item and value being properly set in QXDM.

    Given that and the fact that I couldn't properly evaluate what the individual items were doing I decided to reflash and start over from scratch. I also didn't use QPST to do the service programming because that would have written to the gpsOne tab whatever was in the saved service programming. Instead I used RSD General to write the NAM, PRL and MIP individually, without writing anything to the gpsOne settings at all.

    I now have a completely untouched stock configuration to start with and can redo the edits and monitor the changes in a more detailed and clinical manner than I have thus far, given everything we have learned thus far and my own ability to interpret the logs having seen the behavior with the various edits applied.

    I believe the data above is the seed position data and is for SID 20 not tower 20'

    I am not certain of which item controls that showing up but I will be able to isolate it now that I have a clean config.

    I will activate again tonight and post more detailed results.
  16. Aixelsyd

    Aixelsyd Active Member

    Joined:
    Jan 25, 2009
    Messages:
    1,406
    Likes Received:
    0
    With that all said bud would you prefer I not go threw and do all the edits you put in your posted spreadsheet? Makes no difference to me either way I guess seeing as I have a SP backup right after activation prior to doing any edits with QXDM the first night we went over it all. So even if I do hose things up I can just reflash quick and use my current/original SP backup I had and start from square one on whatever edits you would like tested.
  17. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    Hold off now that I have a fresh confiig to look at myself and can see any changes as they happen.
  18. Aixelsyd

    Aixelsyd Active Member

    Joined:
    Jan 25, 2009
    Messages:
    1,406
    Likes Received:
    0
    Sounds good bud as I was going to have some free time to work on it tonight if you wanted me to. i'll just hold up until I hear otherwise and what you'd like done/tested in specific.
  19. poboy975

    poboy975 New Member

    Joined:
    Mar 11, 2008
    Messages:
    50
    Likes Received:
    0
    hello, ok so what does this mean?
    MSG GPS Searcher Debug/Custom 02:43:18.101 gpssrch_metajob.c 00539 REFPOS: 0x 16fc (CDMAcx8)
    MSG GPS Searcher Debug/Custom 02:43:18.101 gpssrch_metajob.c 00550 SV 9 Code Phase 75 ms + 0 GCx1
    MSG GPS Searcher Debug/Custom 02:43:18.101 gpssrch_warm_metajob.c 02526 Sv 9 using Cold Start
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00539 REFPOS: 0x 16fc (CDMAcx8)
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00550 SV 25 Code Phase 75 ms + 0 GCx1
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_warm_metajob.c 02526 Sv 25 using Cold Start
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00539 REFPOS: 0x 16fc (CDMAcx8)
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00550 SV 8 Code Phase 75 ms + 0 GCx1
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_warm_metajob.c 02526 Sv 8 using Cold Start
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00539 REFPOS: 0x 16fc (CDMAcx8)
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00550 SV 27 Code Phase 75 ms + 0 GCx1
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_warm_metajob.c 02526 Sv 27 using Cold Start
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00539 REFPOS: 0x 16fc (CDMAcx8)
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00550 SV 16 Code Phase 75 ms + 0 GCx1
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_warm_metajob.c 02526 Sv 16 using Cold Start
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00539 REFPOS: 0x 16fc (CDMAcx8)
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00550 SV 30 Code Phase 75 ms + 0 GCx1
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_warm_metajob.c 02526 Sv 30 using Cold Start
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00539 REFPOS: 0x 16fc (CDMAcx8)
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_metajob.c 00550 SV 28 Code Phase 75 ms + 0 GCx1
    MSG GPS Searcher Debug/Custom 02:43:18.102 gpssrch_warm_metajob.c 02526 Sv 28 using Cold Start


    they are debug custom...are they errors? things wrong?
  20. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    I believe those are the requests for ephemeris data for each Sv that is showing as available with data. I think it is using Cold Start because it has no position data to start with. They aren't errors, just the messages about the performance of various functions required to get a fix. If successful, you would see them come back with actual live satellite data. There are huge areas of repetitious cycles in a typical log where the GPS searcher/slicer makes these request without getting anything back

Share This Page