Will this affect the launch?

[redraider1]

How does the delay of the 1.5 GHz OMAP4 affect the Nexus Prime launch? | Android and Me

Wonder if this will push the launch date back?

 

[The_Chief]

Well, with 1GHz DUAL-CORE I'll still enjoy sporting this beast... IF they'll just release it.

 

[Sandroidfan]

I heard that OMAP 4460 already started sampling in the first half of year. Maybe Samsung already placed huge chunk of its order for Prime phones, so there are not so many left for Archos tablet. Also it's possible that Sammy will use Exynos instead as some rumors said recently. I'm still skeptical on it but Note is also using Exynos with LTE. Anyway I'm not too worried on it.

 

[vandyman]

Sorry, I don't believe the story. TI may allready have a deal with Samsung and will keep their promise. If that is the cpu of choice for the Prime.

It's all BS untill we see it via FCC........

 

[redraider1]

Sorry, I don't believe the story. TI may allready have a deal with Samsung and will keep their promise. If that is the cpu of choice for the Prime.

It's all BS untill we see it via FCC........

Guess we will see. Doesn't matter what deal they have if they can't make enough in time ala original incredible with amoled screen. Just saying.

 

[redraider1]

I heard that OMAP 4460 already started sampling in the first half of year. Maybe Samsung already placed huge chunk of its order for Prime phones, so there are not so many left for Archos tablet. Also it's possible that Sammy will use Exynos instead as some rumors said recently. I'm still skeptical on it but Note is also using Exynos with LTE. Anyway I'm not too worried on it.

Pretty sure LTE and exynos don't work together atleast not yet.

 

[The_Chief]

I read that Sammy got Eynos to work with LTE on the Note. If that's true, then we're in for potential wonder phone!

 

[redraider1]

I read that Sammy got Eynos to work with LTE on the Note. If that's true, then we're in for potential wonder phone!

But if ics is developed around the omap i cant see them using exynos for the nexus.

 

[vandyman]

Guess we will see. Doesn't matter what deal they have if they can't make enough in time ala original incredible with amoled screen. Just saying.

Please understand that TI my have more then enough chips for the prime.
TI may not want to take on anymore contracts for other products because of the demand they are allready committed to.

 

[The_Chief]

But if ics is developed around the omap i cant see them using exynos for the nexus.

Why on EARTH would a developer create a "revolutionary" operating system and base it on a single chipset? That would severely limit its application. Seems to me that Google would want to make sure that as many manufacturers as possible could get on board with ICS, regardless of the processor they use.

 

[vandyman]

Reference.

 

[redraider1]

Why on EARTH would a developer create a "revolutionary" operating system and base it on a single chipset? That would severely limit its application. Seems to me that Google would want to make sure that as many manufacturers as possible could get on board with ICS, regardless of the processor they use.

Just because the developed it on one chip doesnt mean it wont work on others. Just saying. If it was tested on more than one there would be multiple nexus phones each year. Google gives the OS to manufacturers to work with it to best work with what chip the companies use.

 

[The_Chief]

I see no reason from the reference to believe that ICS was written specifically for the OMAP. Sure, the OMAP supports a lot of the hardware features that ICS will support software-wise... but to assume that ICS was designed for that particular chip seems a stretch to me. Maybe I'm just missing something here.

EDIT: Now will manufacturers possibly "tweak" ICS code to optimize performance with their chipsets? Sure, I'll buy that one...

 

[redraider1]

I see no reason from the reference to believe that ICS was written specifically for the OMAP. Sure, the OMAP supports a lot of the hardware features that ICS will support software-wise... but to assume that ICS was designed for that particular chip seems a stretch to me. Maybe I'm just missing something here.

EDIT: Now will manufacturers possibly "tweak" ICS code to optimize performance with their chipsets? Sure, I'll buy that one...

I never said specifically for the omap just that is what they developed it on.

 

[jinwons]

Both OMAP4 and Exynos are Cortex A9 based ARM SoC processor but they differ in GPU and some other design details. So it won't be that big deal to port ICS to Exynos. Gingerbread debuted with Hummingbird AP in Nexus S but it was ported to Snapdragon, Exynos, OMAP4 eventually. Whether ICS comes out with OMAP4 or Exynos, it will be soon ported to other ARM processor, especially Qualcomm. I don't think AP things will affect ICS/Prime launch schedule.

 

[cereal killer]

Both OMAP4 and Exynos are Cortex A9 based ARM SoC processor but they differ in GPU and some other design details. So it won't be that big deal to port ICS to Exynos. Gingerbread debuted with Hummingbird AP in Nexus S but it was ported to Snapdragon, Exynos, OMAP4 eventually. Whether ICS comes out with OMAP4 or Exynos, it will be soon ported to other ARM processor, especially Qualcomm. I don't think AP things will affect ICS/Prime launch schedule.

+1

 

[moondrius]

I am sure that Samsung has the processors already if they planned on putting them in the Prime. Archos might not be able to get them because I am sure Samsung buys a hell of a lot more then Archos and the stock was sold to Samsung for the simple fact that they are buying in a much larger quantity.

 

[The_Chief]

Whatever the processor: I think it's a foregone conclusion that the phones - at least the first round of builds - are already finished. Just waiting on FCC, ICS flash, box, ship and sell.

So you could have a point that OMAPs were bought out by Sammy for this phone. That would be good... really, really good.

 

[kyler13]

Reference.

Slightly off topic, but after clicking on the OMAP5 link....

 

[The_Chief]

I must admit: a bit of a step up from the OG Droid...

 

[Don S]

I see no reason from the reference to believe that ICS was written specifically for the OMAP. ....

I don't think it was specifically written for OMAP, but many many articles and rumors have pegged the OMAP platform as the one Google is using to build ICS. Here is one of many ...

 

[The_Chief]

Well folks, I'm man enough to admit when I'm wrong... shocked, stunned and amazed, but wrong...

Just baffles me that Google would write an OS and then have to tweak it for each and every manufacturer out there, depending on the processor that they use; but I guess they can do that if they wanna.

I stand corrected

 

[nj02vette]

Well folks, I'm man enough to admit when I'm wrong... shocked, stunned and amazed, but wrong...

Just baffles me that Google would write an OS and then have to tweak it for each and every manufacturer out there, depending on the processor that they use; but I guess they can do that if they wanna.

I stand corrected

Google isn't doing this because they "wanna". It's pretty much the only way to effectively do this. Keep in mind, that Google doesn't provide end user support (except on Nexus devices). All support comes from each phone manufacturer/carrier. As such, Google is in no position to support all the extra features that each handset mfr may use.

Google picks a platform to develop thier latest release. Then they release the source to manufacturers. Each mfr is free to modify the source to support thier differentiating features, and throw in whatever carrier bloat they may be under contract for.

For example, a phone may have an HDMI port that wasn't part of the Nexus device. That requires a driver for a HDMI chip installed. The mfr is responsible for making sure that hardware/software works properly.

As for the OMAP vs Exynos vs Snapdragon, et al......it's really minor. For the most part, they are all ARM based, so compiling for each architectures is really no big deal. The only customization would be the various drivers required for all the other functions loaded on the SoC. When you have the source, compiling for the other architectures is a minor effort at best. What takes more time is replacing launchers, adding extra features and testing everything. That's where the bulk of the time comes from.

If Google were the true end product producer, they'd either have to limit hardware selection, or test a bazillion different configurations. MS does this with Windows, and the industry definately notes how inefficient that system is. No company wants to start a new venture by hiring 50,000 software test engineers to design and develop for all possible configurations. You either limit your options, or you deal the the incredibly long update cycles and manpower investment that goes along with it.

In contrast, Apple has only thier limited ecosystem to develop for since they are in control of everything (hardware/software).

MS, with WinMo7, is also in full software control, but they do that by limiting hardware selection. Right now, every single WinMo7 device is Snapdragon based, and can only use a limited selection of i/o chips. As a result, all WinMo7 devices are basically the same.

 

[vandyman]

It looks like Samsung made LTE and Exynos to play well together.(1.5ghz)

But will ICS run on it?

 

[anexanhume]

Slightly off topic, but after clicking on the OMAP5 link....

And it doesn't even have a Rogue 6xx GPU from ImgTec