Guest The PocketTV Team Posted May 19, 2003 Report Posted May 19, 2003 Apparently QueryPerformanceCounter is broken on the SPV. It returns incorrect timing information (i.e. bad time conversion from internal clock). QueryPerformanceCounter works properly on the other Smartphone that we have tried (Red-e). The less accurate GetTickCount seems to work properly on the SPV.
Guest neurons Posted June 14, 2003 Report Posted June 14, 2003 its broken on my SPV, i've written a small code profiler which inserts a small code stub at the beginning of a routine, it appears that if the call returns immediately (ie just open/close brace) QueryPerformanceCounter returns the stop time as being less than the start time. This only appears to happen when the profiled call takes less than 40ish microseconds. anything above that and it seems to work pretty much ok. /2ob
Guest The PocketTV Team Posted June 14, 2003 Report Posted June 14, 2003 According to our observations, it returns timing information that does not ellaps at the correct rate. I.e. if you call the routine at one second intervals, the timing information returned by the routine will not indicate an interval of one second. i.e. if we use the QueryPerformanceCounter to play video, the video will play play at the wrong speed on the SPV. The problem is specific to the SPV. It works fine on other Smartphones and on Pocket PCs. It is very possible that the problem is only with certain firmware versions of the SPV.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now