Our device has the ability to record up to 720p video, but is bottlenecked by an outdated compression method. This post is to start an OFFICIAL Petition for HTC to offer us an update that will allow us to gain full access to this feature. We are only asking that our EVO's be given the ability to compress HD content properly.
I believe the issue will be solvable when the PacketVideo library within Android is replaced by something like CoreCodec, rumored for sometime AFTER 2.2 release, but,
I remember the petition way back in the day when HTC was using the Qualcomm 7200/7201 chipset in all their devices (Touch Pro, Diamond, etc.), but didn't include any type of video drivers on the device. The GPU was capable (for its time). Sad to say, a petition was created, but nothing ever came out of that.
HTC Engineer: Sir, Android forums dot com user YouNoAsian has made an "official" demand on the Internet in the form of a forums post.
HTC Space Captain: An OFFICIAL petition you say?! DAMN YOUUUUUUUUUUUUUUUUU! We have no choice but to acquiesce. He did call it an "official petition." MAKE THE CHANGES AT ONCE!
Last edited by tardmobile; June 24th, 2010 at 12:46 PM.
The Following 8 Users Say Thank You to tardmobile For This Useful Post:
I remember the petition way back in the day when HTC was using the Qualcomm 7200/7201 chipset in all their devices (Touch Pro, Diamond, etc.), but didn't include any type of video drivers on the device. The GPU was capable (for its time). Sad to say, a petition was created, but nothing ever came out of that.
Even after they promised, several times, that the update was "out next month", years later and still no changes
Re: Official: Petition for .H264 update on HTC EVO
I think it is more to do with 65nm chips in such a small form factor not being able to handle it. Pick your poison: low frame rate, bit rate, or lower resolution.
I think it is more to do with 65nm chips in such a small form factor not being able to handle it. Pick your poison: low frame rate, bit rate, or lower resolution.
"Beer", it's what's for dinner.
Fab size only has an indirect influence on power. Going down to a small fab size doesn't, in itself increase the computing power of any given semiconductor. What it does allow for is a decrease in power consumption, and thus heat. With less heat, one is able to clock a processor faster without overheating problems.
So, not withstanding the internal design differences between the Snapdragon, the new 1 Ghz TI OMAP, Samsung Hummingbird, and the Apple A4, they are all ARM A7 chips running at 1Ghz. So while the other chips are rumored to be faster than the snapdragon, fabrication size isn't the power-limiting feature here.
HTC Engineer: Sir, Android forums dot com user YouNoAsian has made an "official" demand on the Internet in the form of a forums post.
HTC Space Captain: An OFFICIAL petition you say?! DAMN YOUUUUUUUUUUUUUUUUU! We have no choice but to acquiesce. He did call it an "official petition." MAKE THE CHANGES AT ONCE!
LOL... Even though my sarcasm meter is flying off the charts. I need my(I mean our )demands met...lol
I believe the issue will be solvable when the PacketVideo library within Android is replaced by something like CoreCodec, rumored for sometime AFTER 2.2 release, but,
SURE.
I've seen you tout corecodec repeatedly in this forum, and I finally have to make a response. Coming from WinMo, counting on CoreCodec for anything is a losing proposition. To this day the best WinMo video player is arguably TCPMP, the original product from before CoreCodec was CoreCodec, back in like 2004. Given that they had a platform that was obviously amenable to good video and wide codec support, they failed to bring to market a product that truly beat that now six year old product; all CorePlayers, while shinier, never approached the compatibility and quality of the original TCPMP.
If they are starting their android odyssey out by saying that some fundamental flaw prevents them from even releasing a FIRST product ... you might as well write them off from any consideration until they actually show us something.
ide rather have ogg... and not have to worry about royalties in 5 years
Unfortunately, 95% of the users probably don't understand the implications of what you just said. And, I want to agree with you.
However, something tells me Google and/or the hardware manufacturers (whoever ends up footing the bill) will have the resources to pay the royalties. Thomson is pushing pretty hard to have H.264 go mainstream. Apple is furthering Thomson's cause.
It's inclusion goes against the idea of Linux and open standards but (in my humble opinion) is a necessary evil for the Android OS based on how the market is shaping up.
Is there way for developers to get into the code and change the codec like they change the roms? I'm surprised this it not done yet. That would be awesome addition.
What exactly is the deal with the video? I thought it was just a decreased bitrate/increased compression. But I don't really know. Sure I'm in on any petition to improve the video quality. Brand new phone with plenty of horse power, 8mp camera and it's thoroughly bested by the iPhone and older Android phones, etc. It might be better to gather all the facts and capabilities and mull over the best possible and reasonable response from HTC and then run an email request campaign to let HTC know what we don't like, what we'd like and how many people think this is important. Cause, yeah, a single forum thread by people who have already shelled out their money for the phone probably isn't going to have Sprint and HTC shaking in their panties. But if we can suggest something reasonable to include in an upcoming patch that would be awesome.
Trust in the LORD with all your heart and lean not on your own understanding; in all your ways acknowledge Him, and He will make your paths straight. Proverbs 3:5-6
When Sprint announced their first ever 4G handset at CTIA in March 2010, they dropped a bombshell on the mobile world. The HTC Evo 4G is a device that introduces a lot of firsts when compared to other North American handsets. This is the first Andr... Read More