This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
The Gizmodo shots look photoshopped. Also in the Gizmodo article it mentions that the device is using a Snapdragon. Last I heard this thing was using a T.I. OMAP 3630 @ 7xx Mhz.
That thing in the picture DWARFS the EVO in size. The EVO 4G is 4.8 inches top to bottm. The Droid is 4.5" top to bottom. This between 7 and 8 inches judging from the photograph.
I saw that video and also linked the 3D gears .apk that was used. I also contacted the gentleman responsible for bringing GLX gears to the Android which was used in that video. Turns out that after speaking with him that the devices used in those tests were no locked to V-Sync. Which in english means they ran balls out. They were also running at stock speeds. IF the OMAP 3430 in the video were OC'd to run at the same speed as the OMAP 3630 the framerates would have been very comparable. The biggest bonus the OMAP 3630 will offer is power savings over the current 3430 in the Droid due to its' smaller manufacturing process and newer power savings schemes. Otherwise the base performance will be nearly identical to an equally clocked 3430.
Another note is that they also use the same GPU. So there will be little to any difference in performance there as well. The big difference will be the HD recording and HDMI out which is supported by the OMAP 3630 SoC.
I saw that video and also linked the 3D gears .apk that was used. I also contacted the gentleman responsible for bringing GLX gears to the Android which was used in that video. Turns out that after speaking with him that the devices used in those tests were no locked to V-Sync. Which in english means they ran balls out. They were also running at stock speeds. IF the OMAP 3430 in the video were OC'd to run at the same speed as the OMAP 3630 the framerates would have been very comparable. The biggest bonus the OMAP 3630 will offer is power savings over the current 3430 in the Droid due to its' smaller manufacturing process and newer power savings schemes. Otherwise the base performance will be nearly identical to an equally clocked 3430.
Another note is that they also use the same GPU. So there will be little to any difference in performance there as well. The big difference will be the HD recording and HDMI out which is supported by the OMAP 3630 SoC.
But CPU speeds have nothing to do with fps results in a purely GPU hardware accelerated benchmark. I think the GPU in the 3630 is clocked higher too, which would explain the higher benchmarks, but I cannot find a reliable source anywhere.
I saw that video and also linked the 3D gears .apk that was used. I also contacted the gentleman responsible for bringing GLX gears to the Android which was used in that video. Turns out that after speaking with him that the devices used in those tests were no locked to V-Sync. Which in english means they ran balls out. They were also running at stock speeds. IF the OMAP 3430 in the video were OC'd to run at the same speed as the OMAP 3630 the framerates would have been very comparable. The biggest bonus the OMAP 3630 will offer is power savings over the current 3430 in the Droid due to its' smaller manufacturing process and newer power savings schemes. Otherwise the base performance will be nearly identical to an equally clocked 3430.
Another note is that they also use the same GPU. So there will be little to any difference in performance there as well. The big difference will be the HD recording and HDMI out which is supported by the OMAP 3630 SoC.
But CPU speeds have nothing to do with fps results in a purely GPU hardware accelerated benchmark. I think the GPU in the 3630 is clocked higher too, which would explain the higher benchmarks, but I cannot find a reliable source anywhere.
That isn't necessarily true. The GPU speeds can be effected as pointed out in another post in this forum. Turns out that if the code is written improperly the GPU and in turn whatever is being displayed will run at a higher rate. Although it was also pointed out that this causes some INSANE heat really quick. I would love to link the post but I don't remember which it is.
Ah, I think you're referring to SkullOne's overclocking post from a while back. He makes some good points, but there are some I don't necessarily agree with. Regardless, I'm hoping this new chipset has atleast a 300+ mhz clocked GPU, the 200 Mhz one on the Droid is barely cutting it with the high res screen.