billnapier
Member
Registered: Feb 2002
Location:
Posts: 7 |
GSM Lib reserved function calls
Well, I used the debugger to figure that one out. I know how to trigger the Phone to ring (by going into ringer preferences and selecting a new ringer), soI would bring up that screen and set a breakpoint in the debugger. Then I would step through in the debugger until I heard my phone vibrate. I would go back through and look at the instructions executed and looked for ones that were System Calls that weren't documented. I saw two functions called, one that took 3 args and one that only took 1. So I built an application that had some buttons on it that just triggered those function calls (and a slider to vary the values of the one with 3 args, since the first one is always a reference to the library). From there it was just trial and error to see what the system call did.
A (kinda) simple way to figure out what all the reserved calls did would be to completly disassemble the applications on your VisorPhone (which I haven't been able to sucessfully do yet) and see how many arguments are passed to each of these reserved functions, and then try them out to see what they do. WARNING: don't break your visor or visor phone doing this. It should be pretty safe (Since the application is calling it), but I make no garuntees. Do this at your own risk. Heck, I may even do it myself sometime.
b
|