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!
I noticed that the nook color has a gingerbread update but the famed Samsung 7 inch tab (wifi only) p1010 doesn't.
I know this was shot down in the Q&A before but I am curious as to why given the fact that the nook color has the same PowerVR SGX530 graphics chip.
I do know the nook color runs either OMAP3621 or OMAP3622 system on a chip
and the P1010 runs the OMAP3630 system on a chip but both have that same PowerVR SGX530 graphics chip. All of the listed OMAP SOC models have the same ARMv7 Cortex-A8.
So this begs the question, what is preventing the gingerbread port? Any dev's want to chime in?
Thanks for any time & effort reading or replying.
c0le
I have also learned that the droid x phone runs the same OMAP SOC and it too has the gingerbread update.
*bump*
No reply from the dev's? Am I to assume it is just laziness?
Any idea why a nook color build wouldn't work on this model? How about one of the phone builds? isn't it the same SOC minus the cell modem and possibly Sim port?
The whole idea of system on a chip is to integrate everything.
i am not a dev but i was also thinking the same... can you post this in the galaxy tab dev/question/general tab section... it might get the attention this topic deserves in the appropriate forum
Thanks for the suggestion. I have made such a post here:
http://forum.xda-developers.com/showthread.php?p=19639386#post19639386
Hello all!
I guess this should be in the development thread, anyways.
Regarding to this: https://en.wikipedia.org/wiki/Tegra
@Tegra 250 AP20H (Ventana)
Is the most confusing part of SoC types....
Is there a different build of the Ventana between manufacturers? :0
The Optimus 2x uses the wolfson DAC WM8990 chip, while the Atrix 4G uses the WM8903 according to some rumors, is this true? Plus the dac is in the SoC, not externally...
Any body can clarify this please?
(Dont want to buy a 400 bux teardown document of the tegra 2)
Thanks!
Any response/help is appreciated!
Anyone know which NFC chip the Xperia Tablet Z uses? I've found references to an NXP 44701, but can't find a data sheet or anything else on that part. I also find it curious that many of the NXP parts begin with letters, not numbers.
I'd like to know what the chip's part number is, and how it is interfaced to the main CPU. It does not appear to be USB. Anyone know?
Thanks!
I wonder that as well.. nobody knows?
Hi,
the number 44701 clearly indicates a PN544. Where 44 is the short code for PN544 and 701 is chip revision information.
Regarding its connection to the application processor: The chip should support HSU (High Speed UART), SPI and I2C. For NFC chips on Android this is typically I2C due to the existing kernel drivers (cf. https://github.com/sonyxperiadev/kernel/blob/yuga-aosp/drivers/nfc/ for Xperia kernel).
br,
Michael
I've read that the snapdragon 400 chip natively support GPS.
Is it possible to active it in a custom rom ?
doud1357 said:
I've read that the snapdragon 400 chip natively support GPS.
Is it possible to active it in a custom rom ?
Click to expand...
Click to collapse
No, while the processor chip may have support for GPS, the watch does not have the required sensors needed to get a GPS lock and to feed data to the processor.
If the sensor was actually in the device? Certainly there would be a way to enable it with a custom ROM, but that still dictates that the sensor would need to be built into it.
doud1357 said:
I've read that the snapdragon 400 chip natively support GPS.
Is it possible to active it in a custom rom ?
Click to expand...
Click to collapse
It means it natively has support for a GPS, it doesn't mean it has one embedded within the Snapdragon 400 SoC.
How about a portable gps reciever it's small and you can take with you. I have a nexus 6 and a LG G not GPS when I go for a run I have to take my phone to track my run could there be a way to bluetooth a GPS reciever to work with G watch. Like the way some people use there tablets and GPS same Idea?
What about Wi-Fi?
Many sites I follow are currently suggesting that the smartwatches powered by the Snapdragon 400 might have built in Wi-Fi antennas. The LG G Watch has a Snapdragon 400 APQ8026 but this SoC doesn't seem to have it. Can anyone confirm this?
matteo.gee said:
Many sites I follow are currently suggesting that the smartwatches powered by the Snapdragon 400 might have built in Wi-Fi antennas. The LG G Watch has a Snapdragon 400 APQ8026 but this SoC doesn't seem to have it. Can anyone confirm this?
Click to expand...
Click to collapse
When I looked at the teardown, the radio chipset is solely BT 4.0 :\ no wifi hardware in sight. However while the SoC supports it, without the hardware, that support is useless. Sorry to say
I read the watches have wifi but no antennas. Is it that they actually have the needed hardware but lack the circuitry for an antenna? Maybe a hardmod? Or no?
player911 said:
I read the watches have wifi but no antennas. Is it that they actually have the needed hardware but lack the circuitry for an antenna? Maybe a hardmod? Or no?
Click to expand...
Click to collapse
No. What you are reading is that they have the hardware to SUPPORT a wifi module (Some do actually only lack the antenna, however those will also lack drivers since the OEMs are not likely to make them). Not that there is one built into the SoC. As with the GPS above, even though your SoC supports something, doesn't mean it already has the hardware needed built into it.
@LittleLX: I actually attempted this and attempted to sideload a Bluetooth GPS receiver app to the watch, unfortunately because almost all of them use the Android ActionBar, it refused to start up. Android Wear is restricting applications to the swipe to dismiss action and forbidding the actionbar on versions of Android with Swipe to Dismiss on. That said, there is definitely room for this type of application to be developed for Android Wear, I had sideloaded CF.Lumen and ES File Manager, and while CF.Lumen doesn't open because of it's ActionBar, I had put together a tasker app factory app to attempt to play around and trigger (I had manually installed the CF.Lumen driver) it, it did show that it would work if I had been able to set up location services inside the app (choose the location for the automatic dimming..)
So Android Wear has potential to be a very powerful and extensible platform, developers just aren't interested in it yet it seems. We as a people seem to be stuck looking at a smartwatch as a watch rather than a wrist computer.