New Verizon GPS Fix

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

  1. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    It's probably best to wait unless you have a pretty good idea how to use the software tools required. This is very difficult stuff to explain especially when we aren't really sure of any of it.

    And just to be sure you understand that I am not trying to keep anyone from contributing to the process, it's just that the software was designed to be used by engineers and technicians and it's not a simple thing to explain how to safely use it to play around with the guts of your phone.

    If you have QXDM loaded then there is a User Guide in the help tab that you can start with.
    It will make your head spin...then fall off...it's very painful!:laugh2:
    But you can learn a great deal about how to use it from studying the guide and exploring the GUI.

    Basically, what we are looking for in the logs are the sequences of messages that show what the phone is doing when it tries to get a GPS fix and trying to understand what it is asking for or telling us about the NVM configuration by the errors displayed as well as the other feedback messages. So ultimately we would expect to see it perform all the steps and contact the PDE server, get the data then use that to calculate a position fix.

    When that happens you will know about it...:2cool:
  2. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    Well...you asked what we are looking for...


    From bberryhill0's latest logs sent:

    MSG Global Positioning System/Medium 21:02:30.971 uapdms.c 01218 Handling SS event 0...
    MSG Global Positioning System/Medium 21:02:30.971 uapdms.c 01224 SS event mask 0x4000000...
    MSG Global Positioning System/Medium 21:02:30.971 uapdms.c 01228 hdr_hybrid 1
    MSG Global Positioning System/Medium 21:02:30.971 uapdms.c 01270 CM_SS_BASE_STATION_PARMS_CHGD_MASK set by CM
    MSG Legacy/Medium 21:02:30.971 mot_rsl_atcmif.c 00649 =RSL= cmss_event = 0
    MSG Global Positioning System/High 21:02:30.971 pdsmtask.c 02454 =PDSM= Received Base Station Info 2
    MSG Global Positioning System/Medium 21:02:30.971 seedposssinfo.c 00312 =PDSM_STDBG= sid 1610 wk 1534 ms 507750971
    MSG Global Positioning System/High 21:02:30.972 pdsmtask.c 02476 =PDSM_STDBG= BS Info:sid 1610
    MSG Global Positioning System/High 21:02:30.972 pdsmtask.c 02484 =PDSM_STDBG= bslat [0.25 S] 637168
    MSG Global Positioning System/High 21:02:30.972 pdsmtask.c 02486 =PDSM_STDBG= bslat [deg 10^6] 44247776
    MSG Global Positioning System/High 21:02:30.972 pdsmtask.c 02488 =PDSM_STDBG= bslat [rad 10^6] 772269
    MSG Global Positioning System/High 21:02:30.972 pdsmtask.c 02491 =PDSM_STDBG= bslong[0.25 S] -1749500
    MSG Global Positioning System/High 21:02:30.972 pdsmtask.c 02493 =PDSM_STDBG= bslong [deg 10^3] -121493
    MSG Global Positioning System/High 21:02:30.972 pdsmtask.c 02495 =PDSM_STDBG= bslong [rad 10^3] -2120
    MSG Global Positioning System/High 21:02:30.972 pdsmtask.c 02498 =PDSM_STDBG= nsrhwin 12

    MSG Legacy/Medium 21:02:30.972 mot_rsl_atcmif.c 01193 =RSL= CM_SS_EVENT_SRV_CHANGED
    MSG Legacy/Medium 21:02:30.972 mot_rsl_eri.c 00247 =RSL= 1X : sys_mode(2) srv_status(2) roam_status(0)
    MSG Legacy/Medium 21:02:30.972 mot_rsl_eri.c 00248 =RSL= EV : hdr_hybrid(1) hdr_srv_status(4) hdr_roam_status(0)
    MSG Legacy/High 21:02:30.972 mot_rsl_eri.c 00249 =RSL= roam_status = 0, sid = 1610, prev_sid = 1610
    MSG Legacy/High 21:02:30.972 mot_rsl_eri.c 00942 =RSL= reg_status = 6
    MSG Legacy/Medium 21:02:30.972 mot_rsl_eri.c 00266 =RSL= checking 1X
    MSG Legacy/High 21:02:30.972 mot_rsl_eri.c 00307 =RSL= current_creg = 1, roam_status = 0
    MSG Legacy/High 21:02:30.972 mot_rsl_eri.c 00325 =RSL= sid found. index=0
    MSG Legacy/Medium 21:02:30.972 mot_rsl_eri.c 00349 =RSL= Home. cur_sid == home_sid : 1610. Checking PRL match


    Tell me that doesn't look an awful lot like position data!!!!!!!!!!!!!!!!!!!!!!

    Not sure what this means but I certainly haven't seen anything like that yet in any of my logs!

    WOOOOOOOOOOOOOOOOOOT!!!!!!!!!!!!!!!!!!!!!!!!!!!

    And a note regarding these logs...the above messages represent less than 2 milliseconds of realtime activity...that's a measure of how hard it can be to find what we need in the logs.
  3. poboy975

    poboy975 New Member

    Joined:
    Mar 11, 2008
    Messages:
    50
    Likes Received:
    0
    hey ok so I think I've gotten a log to run. I'm including a .zip with a txt file and an isf file. I got 3 or 4 different purple errors including the sm standalone mode not enabled.

    Attached Files:

  4. merkel04

    merkel04 New Member

    Joined:
    Aug 1, 2008
    Messages:
    76
    Likes Received:
    0
    44.247776, -121.493

    looks like the correct coords
  5. merkel04

    merkel04 New Member

    Joined:
    Aug 1, 2008
    Messages:
    76
    Likes Received:
    0
    I guess bslong and bslat is probably base station long and lat?

    So is that the location info of the tower the cell was connected to during the logging?
  6. PacoJr67

    PacoJr67 Active Member

    Joined:
    Mar 6, 2007
    Messages:
    13,359
    Likes Received:
    0
    my guess would be that is the GPS data that the phone was receiving, if it were tower data there would most likely be multiples because CDMA phones don just connectto one tower at a time. But then I could be wrong
  7. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    Apparently it is seed position data from the base station. It went on later to have the same errors about the standalone fallback session being active and never got a fix. What is significant is that I have never seen that occur before and it seems to indicate that something in the NVM is enabled that is not on mine.
    Now we need to go through and see what that might be or how to further configure the NVM.
    It's still the kind of changes that we are looking for to isolate the required NVM items and so is progress!
  8. poboy975

    poboy975 New Member

    Joined:
    Mar 11, 2008
    Messages:
    50
    Likes Received:
    0
    hi so I've been reading through the qxdm user manual, and looking at the nv browser. why is it that some of the items you guys have changes in the excell file I cant see. comes back item inactive. how did you activate them? I havent been able to find an answer googling.
  9. Q9Nap

    Q9Nap Member

    Joined:
    Feb 8, 2009
    Messages:
    173
    Likes Received:
    0
    Highlight the item you want to change and click 'read' (it's a good idea to record your default value in case you want to change it back later) then double click on the value to edit, leaving the '0x' part alone where applicable. Once you've entered the new value, click 'write'. Finally, click 'read' again to make sure the value stuck.
  10. poboy975

    poboy975 New Member

    Joined:
    Mar 11, 2008
    Messages:
    50
    Likes Received:
    0
    ok thanks I got that to work. some of the items come back parameter bad when I try to read them. any ideas? and what would happen if I change a 0 to a 1 in some of these? what are chances of bricking?
  11. Q9Nap

    Q9Nap Member

    Joined:
    Feb 8, 2009
    Messages:
    173
    Likes Received:
    0
    Not sure about the 'parameter bad' items...it may mean that these are not used/referenced with this chipset (?)
    As far as changing values from 0 to 1, I'm assuming you're referring specifically to boolean value items as there are decimal and hex values also, which are obviously more complex. Not likely that you'd brick the phone by turning a boolean value on or off, but you should still be careful and keep notes of what is changed and from what to what in case you want to change it back.
    Most likely the worst-case scenario would be having to manually place the Q in bootloader mode and reflash.
  12. merkel04

    merkel04 New Member

    Joined:
    Aug 1, 2008
    Messages:
    76
    Likes Received:
    0
    Just to confirm, the following error is the one giving you the problems at this point?


    MSG Global Positioning System/Medium03:11:16.054 pdsmpd.c 01832 =PDSM_STDBG= SM - standalone fallback session active

    MSG Global Positioning System/Medium03:11:16.054 pdsmpd.c 01848 =PDSM_STDBG= SM - MSB/Std not allowed when std fallback fix session is on hold/active

    MSG Global Positioning System/Error03:11:16.055 pdsmpd.c 02075 =PDSM= pd cmd err, cmd = 0, err = 14, client = 3491

    MSG Global Positioning System/Medium03:11:18.584 pdsmpd.c 01832 =PDSM_STDBG= SM - standalone fallback session active

    MSG Global Positioning System/Medium03:11:18.584 pdsmpd.c 01848 =PDSM_STDBG= SM - MSB/Std not allowed when std fallback fix session is on hold/active

    MSG Global Positioning System/Error03:11:18.584 pdsmpd.c 02075 =PDSM= pd cmd err, cmd = 0, err = 14, client = 3491

    MSG Global Positioning System/Medium03:11:21.132 pdsmpd.c 01832 =PDSM_STDBG= SM - standalone fallback session active

    MSG Global Positioning System/Medium03:11:21.132 pdsmpd.c 01848 =PDSM_STDBG= SM - MSB/Std not allowed when std fallback fix session is on hold/active

    MSG Global Positioning System/Error03:11:21.132 pdsmpd.c 02075 =PDSM= pd cmd err, cmd = 0, err = 14, client = 3491
  13. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    Parameter bad errors usually indicate a protected item and/or that the syntax of the request command was improper. Sometimes these items can be read by first inputting the SPC in the command buffer at the bottom, which will then allow the item to be read. They can also often be read with RadioComm which uses a different command format and has different security protocols.

    QXDM is Qualcom proprietary software and RadioComm is Motorola proprietary software.
    This is the case for many Security items and data authentication items, but I haven't gotten that message for any of the GPS items and I have at least tried to read them all, if not actually edited them.

    The bottom line is that when discussing these things it's always better if you list exactly which items you are referring to and their default value etc.

    Also remember that once an item is written to it becomes active and the only way we know to make it inactive again is to reflash the phone and start over.
    That is why I have been working with Q9Nap and Aixelsyd to use there freshly flashed units as testbeds and to avoid writing to any items that we're not sure about in order to find out which items are required.
    This is why testing and logging must be done very carefully so that we can derive good information from the results, otherwise we may miss critical feedback from the logs.

    One more helpful hint for anyone who posts a log file.

    Please rename the file with a clearly identifying name so that it's easier for me to keep them organized. The default naming structure is fairly inscrutable and I have a huge collection of them(almost a GB now) and it's getting ridiculous...thanks!
  14. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    Yes that is correct, except on my configuration I don't get the error any longer because the fallback session doesn't remain active after it's terminated.

    That is what we want to isolate in the NV configuration, amoungst other things.
  15. merkel04

    merkel04 New Member

    Joined:
    Aug 1, 2008
    Messages:
    76
    Likes Received:
    0
    Is there anyway for GPS to take the new nv values without restarting the phone?
  16. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    Well, as soon as they are written with QXDM they are set in theNVM but are not acknowledged by the OS it seems until after a reboot. You can immediately verify that the values have changed by rereading the item after writing...always a good idea anyways, but you can also do so by reading a service programming with QPST and check the values in the gpsOne tab. You will see that they reflect the edits without a reboot but the changes don't have their full effect until you reboot.

    Short answer...always reboot before logging any changes made.
  17. bberryhill0

    bberryhill0 Active Member

    Joined:
    Feb 14, 2009
    Messages:
    2,215
    Likes Received:
    1
    I didn't think to reboot for my last log. I will have to do another one. I am starting to recognize some things in the logs. Keep posting interesting snippits.
  18. merkel04

    merkel04 New Member

    Joined:
    Aug 1, 2008
    Messages:
    76
    Likes Received:
    0
    -------------------------
    MSG Global Positioning System/Medium 09:22:13.294 pdsmtask.c 03507 NO AA data generated by PE
    MSG Global Positioning System/Medium 09:22:16.294 pdsmtask.c 03993 =PDSM= pe response timer expired
    MSG Global Positioning System/High 09:22:16.294 pdsmtask.c 03349 =PDSM_STDBG= timeout Tf1-x
    MSG Global Positioning System/High 09:22:16.294 pdsmtask.c 03389 =PDSM= PE Response timeout
    MSG Global Positioning System/Error 09:22:16.294 pdsmpd.c 06362 =PDSM= PE Response timeout
    MSG Global Positioning System/High 09:22:16.294 pdsmnmea.c 02039 =PDSM= nmea:NmeaDataUpdate
    MSG Global Positioning System/High 09:22:16.295 pdsmpd.c 12895 =PDSM= op Complete,status=12,substate=2
    MSG Global Positioning System/High 09:22:16.296 pdsmpd.c 13174 =PDSM= Fix operation completed...
    MSG Global Positioning System/High 09:22:16.296 pdsmpd.c 13230 =PDSM= err_c(A)=0,err_c(B)=1,total=2
    MSG Global Positioning System/Medium 09:22:16.296 lcsagent.c 00172 V1V2 disabled, bypassing lcs_agent_handle_lr_resp
    MSG Global Positioning System/Error 09:22:16.296 pdsmpd.c 13282 =PDSM= Error_cnt >= threshold..Exit sess
    MSG Global Positioning System/Medium 09:22:16.296 pdsmpd.c 13283 =PDSM= last_error=2, err_type=0
    MSG Global Positioning System/Error 09:22:16.296 pdsmpd.c 01245 =PDSM= Abort and notify, error=12 type=0
    -----------------------------

    Seems like no matter what I do I get the above error sequence. Does anyone know the solution to get rid of the above? I have gone through several fresh flashes and different NVM configs I have found throughout this thread, and throughout the conversation BBhill posted between Call Zealot and him. Log attached if interested.

    Currently I am using a fresh Gen to USCC flash, data working, with the following NVM edits:

    Desc............. : NV# : Status : Value

    GPSOne Lock....: 452 : Active : 0
    PDE Address.....: 401 : Active : 0xD8C68B5C
    PDE Port..........: 426 : Active : 0x000022b9
    Dynamic Mode..:3756: Active : 3
    Vx LCS Agent...:1993: Active : 0
    Throttling........:3358: Active : 0
    Chain Config....:1032: Active : 0x03
    Vx Trusted......:1994: Active : 10
    Position Report.:3293: Active : 0

    Attached Files:

  19. merkel04

    merkel04 New Member

    Joined:
    Aug 1, 2008
    Messages:
    76
    Likes Received:
    0
    MSG Global Positioning System/Medium 11:16:40.855 pdsmpd.c 05071 =PDSM= start pe response timer 3000


    after looking further, I see that in the message log. I'm assuming the PE response timer is set at 3000. The timeout occurs 3 seconds after this timer starts.
  20. CellZealot

    CellZealot New Member

    Joined:
    Jan 3, 2009
    Messages:
    915
    Likes Received:
    0
    Good feedback thanks. It's looking like the TRM edits may be key.

    Also try writing 400 to 0 if you haven't yet.

Share This Page