When our favorite gadgets have limitations, we love to find, exploit and whine about them. Today, HTC explains the 30FPS limitation on the EVO 4G – more specifically, the 30FPS limitation on the HDMI out. Apparently, the frame rate cap is a hardware issue, but we’re also learning that it is imposed by the EVO 4G software itself. Double caps! But why would HTC place a limitation on both the hardware and the software?
Android Guys decided to get in touch with the manufacturer for an explanation for this blasphemy, this outrage!
We were advised that the frame rate cap is hardware related, although the cap itself is imposed by the EVO’s software. The reason for the limitation is directly related to the EVO’s HDMI port, which, we were told, requires a sizable portion of the Snapdragon processor’s output in order to operate. Subsequently, a limit needs to be placed on the amount of the processor’s output that is allocated to the display.
Ah, well there you have it. The explanation is that the Snapdragon processor, powerful as it is, still needs to allocate its resources to other functions so that the phone still performs satisfactorily. It makes good sense and should quell any bitterness that the most picky of users might have had about this particular issue.
However, can we really consider this an HDMI limitation? Most TV sets display videos at 24FPS or 30FPS and will even cut down frame rates when displaying video from a source that is going at a higher rate. HTC EVO 4G users were still getting annoyed when scrolling through pictures, web pages and home screens where the issue is really noticeable. To them, I say: seriously, guys? Seriously?! You have a phone so capable, with a screen so huge, with 4G connectivity where it’s available — and the one thing you want to complain about is the not-so-smooth scrolling of screens when you connect the HDMI port to another monitor or display? Yikes.
Now that that’s all sorted, your next biggest decision is: black or white?
Don’t forget to check out our Sprint HTC EVO 4G review here!
[Via: Android Guys]