Windows Mobile 6.5 cannot browse WSP webpage after installing the official QQ version!

Solved!

Once again, I realized the joy of success. Find yourself useful!

 

Problem description:

During project development, QQ 2008 official version of Windows Mobile was found. On Windows Mobile 6.5, QQ's built-in browser cannot be used to access QQ's WAP website.

Phenomenon shows, click QQ nine palace lattice hyperlink http://3g.qq.com, display blank page.

 

However, if the same cab package is installed on the machine of wm6.1, both the toshba g900 and the palm tero can work normally.

The same cab package is installed on the Samsung i329 machine of wm6.5.

 

Analysis:

1. It may be caused by different user agents of the device.

After using the uaprof/user agent of palm tero, the problem still exists.

This may be excluded.

 

2. Use the netlog packet capture tool to analyze the HTTP interaction between wm6.1 and wm6.5 in normal conditions.

I found that wm6.1 can jump to the http://info13.3g.qq.com/g/s in 10 seconds after get to WML page? Aid = index & s_it = 2 & g_from = 3 gindex & SID = 00 & G_F = 1283

Wm6.5 does not jump in case of exceptions. Will only stay on the first WML page, and this page only has something like ontimer = "http://info13.3g.qq.com/g/s? Aid = index & s_it = 2 & g_from = 3 gindex & SID = 00 & G_F = 1283.

 

So the problem is locked on the WML jump.

 

3. WML redirection is a render issue of WML. There are two possibilities: Microsoft wm6.5, and wm6.5. According to vendor, HTC's wm6.5 device is capable of running. It may be the current specific wm6.5 device (of course not an HTC device !) .

To verify, use the device emulator of wm6.5 to simulate access to the Internet through ActiveSync on the PC (see the previous article ). Verify the problem. It was found that the wm6.5 simulator had such a problem.

 

4. to further verify the wm6.5 problem, use Microsoft SDK sample minipie for debugging and verification. The problem persists. Therefore, it can be determined that the QQ browser uses the minipie sample to change. The difference between locking wm6.5 and wm6.1 causes this problem.

 

5. Export the palm registry and wm6.5 registry for comparison. The problem is verified. In the past, Microsoft replaced wmlview. dll with the new wmlview7.dll in wm6.5. The two DLL files coexist. However, it seems that wmlview. dll is not very useful.

 

Then, hey... Two days .... It proves Microsoft's wmlview7.dll jump bug. Microsoft may think that few websites use WSP now. So...

 

Should I report this question to Microsoft? Which one can help me?

 

In addition, if you use Google wmlview, I hope this article will be useful to you! Haha, I didn't have any useful results when I googled wmlview.