Related
Hey there,
Was doing alot of research online about the graphic chipset from ATI on Athena but not even ATi has any infomation on their Webby.
Anyone know the specs of this w2284 chipset? Would really like to have more information on the chipset.....
Cheers
i agree with you, i tried to find info on the chipset to but i couldn't so i was like fu*k it and bought it anyways
Interesting thing, I was looking for Intel® PXA270 and found out all things are over to Marvell. Pretty confusing but ATI is just part of that chip, not a special chip
I saw some posts at the Coreplayer (comercial version of TCPMP) forum that ATI has refused to make the specs of that chip available to the Coreplayer developers, effectively crippling the chip for being used my alternative media players.
that very intersting, will i think we all need to find a player that ati likes
ATI W2284 not only for processing video and graphics, but also for handling the camera. Particularly, calculating autofocus algorithms and settings of automatic white balance are done with the help of this graphic subsystem
hmm... i think tt is known.... But if i m not wrong my old blueangel also uses ATI chipset...
problem is like example nVidia's Goforce 5500 is known to have a clock speed of 150 to 200 mhz....
how much is ATI's W2284??? Secondly does it have hardware encoding N decoding of H.264 videos??
Blah blah blah... Lots of qns left unanswered.
Anyone knows??
Cheers....
bLiTz^ said:
hmm... i think tt is known.... But if i m not wrong my old blueangel also uses ATI chipset...
problem is like example nVidia's Goforce 5500 is known to have a clock speed of 150 to 200 mhz....
how much is ATI's W2284??? Secondly does it have hardware encoding N decoding of H.264 videos??
Blah blah blah... Lots of qns left unanswered.
Anyone knows??
Cheers....
Click to expand...
Click to collapse
Read here:
http://ati.amd.com/products/handheld/imageonfaq.html
http://ati.amd.com/products/imageon2282/index.html
and here:
http://ati.amd.com/products/handheld/products.html
Not very definitive I know, but never really found much else about them since last year and I believe ATI is remaining tight lipped for a reason...also not releasing info to Corecodec so they can support the chipset properly.
Notice also in the 3rd link, 2282 is listed,......but where is the mention of 2284?
I give up with ATI/AMD/Imageon....Imagine if we could get the best out of it via hardware decoding...how sweet that would be.
Just have to settle for using the Imageon driver for now, as it still yields visually better results thatn Rawframe buffer mode or direct draw and outperforms both in benchmarks fo speed.
Sorry can't help any more than that. Good luck on finding anything else useful.
no probs mackaby007......
Hmm i wonder...... mayb W2284 is actually a Modified Imageon W2282...
W2282 supports 3MP Cam.....
bLiTz^ said:
no probs mackaby007......
Hmm i wonder...... mayb W2284 is actually a Modified Imageon W2282...
W2282 supports 3MP Cam.....
Click to expand...
Click to collapse
That's what I thought too.
Ive noticed a real delay between image and sound when playing some games.
Games in question are FIFA 2002 from EA Sports and also Smart Tennis from SIMBSOFT.
Did anybody noticed something similar??
Any news? I'm waiting for optimized Ati W2284 driver for HTC Athena... May be it will be supported in CorePlayer...
Any news? I'm waiting for optimized Ati W2284 driver for HTC Athena... May be it will be supported in CorePlayer...
up )
bLiTz^ said:
Hey there,
Was doing alot of research online about the graphic chipset from ATI on Athena but not even ATi has any infomation on their Webby.
Anyone know the specs of this w2284 chipset? Would really like to have more information on the chipset.....
Cheers
Click to expand...
Click to collapse
Hey, thinks for your work.I'm sorry I don't konw how to help you.But i think it maybe like qualcomm 7200's graphics chip.because the first ppc phone base on qualcomm 7200 is kaiser/TyTN II has the same problem as our 7500 at first.but someone solved it by modfy the 7201a driver for diamond for it.and the 7200 is the first product after ati sold the handheld products to qualcomm.so i think they maybe a little like.
i'm sorry for my poor english!
Came across this website:
http://htcclassaction.org/
Looks like it is specific to the MSM7200 and MSM7500 chipsets not sure the Athena should be included in the list or not since I am not sure what we are running.
Good read anyway and hopefully they will come up with a fix.
Athena's could well benefit from all of this.
marka2k said:
Came across this website:
http://htcclassaction.org/
Looks like it is specific to the MSM7200 and MSM7500 chipsets not sure the Athena should be included in the list or not since I am not sure what we are running.
Good read anyway and hopefully they will come up with a fix.
Click to expand...
Click to collapse
Well I'm trying to get the project leaders to include the Athena and TyTN I device too as the Qualcomm MSM 7200 has ATI and Imageon hardware in it and driver support has never been forthcoming for these devices either.
Granted the Athena and TyTN I are no handheld 3D games devices (as the Kaiser has the potential to be), but they certainly would be much better at handling native VGA H.264 encoded movies/clips if driver support was given.
Who knows where this will lead, but hopefully it will lead to a set of accessible drivers that our very own xda-developers can hack and tweak to perfection.
I was surfing around wmpoweruser.com and saw this article: http://wmpoweruser.com/?p=2252. It says that Pharos will release this PDA in the Q1 of 2009 and it will rival the HTC Touch HD.
In fact, the specs of the phone are very similar to the HD, but what calls my attention is one really interesting fact: the Pharos phone uses the very same processor as the Touch HD (Qualcomm MSM 7201A 528MHz).
I would like to ask the experts: if the Pharos payed for the video drivers to use hardware acceleration, will it be easy or, at least, possible to import them to Touch HD and we´ll finally have decent video playback?
Thanks!
I think if the drivers for WM existed we would have them by now. I think the GPU is broken and simply doesnt work properly in the Qualcomm CPU or Qualcomm themselves cant get it to work properly, thats why there is only partial support for all its functions.
HTC Touch HD/Diamond/Touch Pro all three of them have video drivers but they are used only with inbuilt players(WMP and video player in gallery). What we need now is to Coreplayer use those DS filters or gain access straight to QTv 'chip' and they said that they finally came to terms with qualcomm about it and now they can start working on it. So one of the upcoming updates(which one I don't know) should finally end this problem but I don't know when it will come.
Here you have link to the topic regarding QTv situation.
The simple test is whether ANY devices on any platform that use the CPU have decent video performance. If not then its clearly a problem with the CPU itself, rather than just the phone manufacturers being cheap.
Qualcomm has other, cheaper CPUs that are just as fast in general terms, but without the GPU, so why fit a CPU with a GPU if your not going to use it?
Sure the HTC Album App can play some files with acceleration, but that is not offering full QTv support and is not providing us with everything the GPU is capable of in theory.
In my view the GPU is broken (or qualcomms implementation is) and therefore writing drivers to fully utilise it is very difficult, which is why there are no fully featured drivers.
Acceleration clearly works - you can play 800*480 high bitrate files in h264 via wmp, but they're a slideshow through other players.
Yes, but its only partial, its not accelerating everything it should. I still say such drivers do not exist, even at qualcomm. Their recent request for windows mobile driver specialists and developers speaks volumes.
It wouldn't be the first time a technology company has launched a broken product on the unsuspecting world, or talked up a product when it really isnt capable of what they claim.
Back to this Traveler 137, it does have impressive specs, looks, gps, and best of all 3G for us T-Mobile USA users! It just won some innovation awards at CES: http://www.pcworld.com/article/1563...ne_offers_navigation_no_network_required.html
I still think that the drivers are here but I think that winmo itself can be blamed for the situation too(using drivers by the system). WinMo should be rewritten for the multimedia so it would bring some universal standards for all video solutions that SoC has to offer. Something like openCL but for mobiles.
The fact that they are looking for programmers and enginners is a good thing and it means that they want to improve the way their products handle wm but it doesn't mean that they don't have people now.
Until somebody gives me concrete proof that the drivers arent there I won't change my opinion. And please don't start talking about GPU problem(which problem I think lies in faulty use or implementation of drivers and that HTC can be blamed cause they take full responsibility of how they configure the device and not SoC maker). I'm only talking here about video acceleration.
Its just that ive seen the same thing happen before, and its usually graphics drivers or memory controllers that suffer. Almost every graphical device we have has some element of broken hardware in it that requires a work around. It may not be the GPU itself, but the interconnect to the CPU, or the way the CPU and GPU interact is just not optimal. Either way something is not right as it is right now.
I very much doubt that there is a driver sitting on a PC in Qualcomm labs that will fix all the issues. I dont believe that no one has been bothered to buy it or that Qualcomm has priced it so high that it wont be used, that makes no sense at all.
HTC are not responsible for the poor driver performance, in fact they have clearly done their own work to work around the issue. What they are responsible for is using the chipset in the first place.
Im waiting to see exactly what Coreplayer ends up like after their improved QTv suport is out. Im willing to bet that it wont make a great deal of difference to anything but H.264 that is already accelerated by the HD native player, but not by Coreplayer currently.
rovex, you might have a point here btw...
I know that the Touch HD runs H264's inloop deblocker in hardware for example. Switching it on or off has no effect on CPU. For pure software decoders it has about 15-25% effect.
Since you can't really apply that specific acceleration to other types of video, it will be interesting to see what other media will be sped up by implementing QTV.
To all guys who know what they're talking about:
I've heard that the DHD (as most Android phones) does not support hardware acceleration in videoplayback at all (The only phone that has it is the SGS...?).
If that's true it is logical, that 720p does not run on it.
But I think in some HTC apps and also in some games, the GPU must be use due to the performance.
Will there be any possibility to test whether the DHD is using the Adreno GPU or not?
Because if hardware acceleration is not enabled, with hardware acceleration my baby could run Sense 3.0 smoothly, couldn't it?
imo at the moment it's not possible, because it's not
perfectly smooth. And I hate that
Gingerbread do not support hardware acceleration. Honeycomb does. Lets hope for Ice Cream Sandwich!!!
http://code.google.com/p/android/issues/detail?id=6914
After looking through engadgets live blog there was no mention of hardware acceleration being added to android 4.0. With that being said that was my hopes of 4.0 bringing true smoothness that both ios and WP7 have been having all along. Now i know there is 3d animation ( i may be wrong ) but i know that isn't the full acceleration. Question asked does it have it?
Yes, Android 4.0 features 2D Hardware Acceleration (as originally added in Honeycomb), with some improvements.
Additionally, applications can take advantage of the GPU (Photos, Video & Gallery, for example) for on-the-fly transform effects. For example, if you perform edits in Gallery to a photo, it's actually loaded as a texture in OpenGL, and the "effects", or transforms, are applied leveraging the GPU to vastly improve performance.
Likewise, the panoramic "stitching" is GPU accelerated, and video capture (compression) and streaming (transformations, such as silly faces) are GPU accelerated.
It remains to be seen if the GPU is being used for other aspects of the OS, for example, being leveraged by the browser to assist in webpage rendering, etc. However, even as it is right now, it's a massive step up in quality and performance, and should facilitate wonderful UI/UX experiences for ICS even on older devices, like the Evo, Nexus One, Droid X, etc.
Shidell said:
It remains to be seen if the GPU is being used for other aspects of the OS, for example, being leveraged by the browser to assist in webpage rendering, etc. However, even as it is right now, it's a massive step up in quality and performance, and should facilitate wonderful UI/UX experiences for ICS even on older devices, like the Evo, Nexus One, Droid X, etc.
Click to expand...
Click to collapse
Oh really! Are we to believe that somehow the Evo's GPU will be ICS supported for hardware acceleration? Will that require a HTC-specific ICS update, or is it workable for AOSP before HTC codes in their hardware acceleration?
thegregbradley said:
Oh really! Are we to believe that somehow the Evo's GPU will be ICS supported for hardware acceleration? Will that require a HTC-specific ICS update, or is it workable for AOSP before HTC codes in their hardware acceleration?
Click to expand...
Click to collapse
Well, it isn't really a device-specific feature.
Hardware acceleration in the UI is akin to playing a 2D game, like Angry Birds. The system is actually leveraging OpenGL to handle 'displaying', or 'rendering', the game. Likewise, the UI is 'displayed', or 'rendered', the same way.
The way this relates to Android 4.0 is like this: Hardware acceleration was added to Android in Honeycomb (3.0), and in order to take advantage of it, requires a GPU that is capable of supporting OpenGL 2.0 with drivers that are compatible with OpenGL 2.0. If you have a capable GPU with capable drivers, the OS will use the GPU to render the UI, and voila, hardware acceleration.
If any of those components are not available (or perhaps not working correctly), Android defaults to "software acceleration", which is what has always been present in Android for phones. 1.0 all the way through 2.3.7 all use software acceleration. That is, all of the UI elements are rendered by the CPU.
You've probably experienced lag thanks to this--scroll through your contacts list quickly, flip between full home screens, or load up an intensive Live Wallpaper and open your Launcher and try scrolling--you'll probably find slowdown, if not stuttering in places. This is because the CPU is doing the heavy lifting not only for the OS, but also to render the display.
By alleviating this pressure on the CPU, we free up the phone to do work it's better at handling--running the OS. Additionally, because GPUs are actually designed for rendering, they are far, far more efficient at doing so than the CPU. The result? A massive overhead reduction overall on Android on devices, that means improved performance across the board as well as a much more pleasing user experience.
This is fantastic news for devices new and old; but a real treat for those of us with older phones, as the reduced CPU overhead coupled with GPU acceleration should mean noticeable performance improvements, as well as a drastic reduction in stuttering, lag, jittery-ness in the UI, etc.
Best of all, it should be very simple to implement. Most hardware supports OpenGL 2.0 (our Evos do, for example), and most drivers for that hardware also support OpenGL 2.0 (as our Evos do), so it should really be as easy as building Android 4.0 with the appropriate drivers, and then experience the bliss of a hardware-accelerated Android for the first time.
(Note that this explanation doesn't touch on using the GPU for additional benefit, like editting photos, videos, offloading work from the CPU as I touched on above, etc.)
man that was a bunch of good info i needed +1 will be glad when our evos have that much needed acceleration
Dude Shidell thank you so much for that in depth explanation! You covered everything I could have possibly wondered about, haha. A king amongst men, and a god amongst kings, you are.
Thanks alot shidell that really helps me out alot. I just have one question, did anyone here about usb host, on 4.0?
Sent from my PC36100 using XDA App
BmW13294 said:
Thanks alot shidell that really helps me out alot. I just have one question, did anyone here about usb host, on 4.0?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yeah i read that the galaxy nexus was having a usb 2.0? i will check some images to see if its true
Naturally, Ice Cream Sandwich is onboard, with Google finally revealing the version number as 4.0. Other specs include an HD Super AMOLED display (1,280 x 720), a 1.2GHz dual-core processor, 5 megapixel rear camera (with LED flash), a 1.3 megapixel front-facing cam, 1080p video recording and playback, a newfangled panorama mode, a 3.5mm headphone jack and Bluetooth 3.0. You'll also find USB 2.0(right there), 802.11a/b/g/n WiFi, an embedded NFC module, accelerometer, compass, gyro, proximity sensor and even a barometer -- yeah, a barometer. Finishing things out, there's 1GB of RAM, 16 or 32GB of internal storage space and a 1,750mAh battery. info gathered from Engadget listing all the galaxy nexus specs
Happy to share information.
BmW13294 said:
Thanks alot shidell that really helps me out alot. I just have one question, did anyone here about usb host, on 4.0?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yeah, Android 4.0 builds upon the USB Host support that was integrated in Honeycomb, which means it has native support for a variety of USB devices. Granted, I don't know the depth of devices or support, but it is present.
Nice explanation shi.