![]() |
||||||||||||
|
FAQ: Frequent asked questions This section describe the most common asked questions about the issues:
Witch phones or PPC's are affected by the issue? The following known phones and PPC's are affected by the issue:
How can I get rid of the issues? To get rid of the issues is by letting HTC know this is not normal for a decent phone and state that thousends of other users are experiencing the same problem. Also as for a reply! If you don't know how to contact HTC, please go to the how to contacts HTC question. Why is it that the camera has such a slow refresh rate? This is all due to the lack of video driver support. It seems that the hardware is not properly rendered. Qualcomm has build in the Qcamera function in this chipset. Which seems not to be enabled by HTC on these devices. With this feature enabled it will give a better performance in regards to frame rate when using the camera. Temporary solution: turn the phone off by pressing the power button, wait 2 secons, and turn it on again (turn on/off by pressing the sleep button on the side of the phone (TYTNII)) users reported a gain in FPS from 3 till over 20! even in dark surroundings! Why does flipping from portrait to landscape take so long? This problem is also related to the video drivers. It seems that 2d rendering is also significantly impaired. How can it be that there is such a bad video playback? This item is described in the problem section very well, please go to the problems section and read it. It is also illustrated with You Tube movies to show you the difference. Is there a way to solve the video playback? Solving this problem without help from HTC seems to be very difficult. Off course there are ways to manipulate this issue. One thing you can do is convert a movie on your computer to a size around 320x240. This will take a lot less space and with a player like coreplayer it should be possible to play movies. However, keep in mind you loose lots of quality when you want to play this file on another screen. it seems that coreplayer is working on a fix for the video issue and will intergrate it in their core player version 1,2 wich should be released any moment. Also complaining to HTC may work. update: try the new corecodec, it seems to work quite well according to some users! Can I play games on these devices? Yes and no, if you want to play solitaire or bubblebreaker it shouldn't be a problem. But keep in mind if you want to play games wich requires 3d drawing this is not going to work on the devices with a QualcommMSM7200 chipset. This is because the lack of a proper hardware driver supporting OpenGL ES How can I contact HTC about this issue? You can find a list of all their regional phone numbers here: http://www.htc.com/support/care_hotline.htm Does all these complaints really work? What started as a group of enthusiast people, soon grew into thousands of people complaining to HTC. HTC is just now starting to say the are aware of the problem. So yes, we need to continue and find even more support in drawing attention to our cause. The last few weeks has shown an explosive growth of unhappy and disgruntled people. Hopefully this is just the tip of the iceberg and many more people will help draw attention to the problem so that HTC will stand up, take notice and offer a solution. What about making a driver myself? Feel free to do that, many people are really looking forward to see a driver. If you want to make some money with it you can have a look here. At the moment of writing this there is raised over 4000$ for the person making a proper video driver. Why is my phone is really slow when I end my call (tytnII)? This is because the fact you've got a devicelock enabled, something seems to go wrong and it's just a little bug. You can simply eliminate this bug by putting of the devicelock on your TyTNII. Why are people fading out when I’m on speaker (tytnII)? This is still a pretty strange thing on the kaiser, some people think it is because the phone doens't support a full duplex mode. If this is true then hopefully it can be fixed with a firmware upgrade.
|
|
||||||||||