• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

***Official Galaxy Nexus Pre-Release speculation thread**

Status
Not open for further replies.
Didn't the guy on Google+ from Chicago that got a hands on preview from a friend say that the phone was running on Verizon's network? Why would this be so if the phone was not coming to Verizon?
 
So how long will it be before the Nexus is revealed as a 4430 also? :eek:

Before drawing and quartering me, I'd just point out that it wouldn't be the first time that a BIOS or sysinfo reporting tool misidentified a CPU. If a unique chip ID wasn't recognized for some reason, it could've said Well it's definitely in the OMAP4 family but it's faster than the official 1.0GHz 4430, so let's assume it's the 4460!

The bottom line question is: How likely is it that Motorola and Samsung would both release 1.2GHz processors in the same family at the same time, but one of them's a 4430 and the other's a 4460? I'd say possible but unlikely. :confused:
 
i dont know why i bother even reading these comments, no real useful information about the device, only speculations of rumors where its going..... i agree with OTD its real easy to start rumors, funny thing is though, as i post this 6 more posts will appear before me once i hit Post Quick Reply



haha i was right! 6!!
 
AntimonyER said:
Yeah I am halfway tempted to take a trip over to the RAZR forums to see how they are taking the news of the 4430...
Click to expand...


Not too well. I went from an advocate to an adversary. IMO, Motorola are deceptive twits and screwing consumers over if a 4430.

Added: The gpu will scale up, but the 4430 has to work harder than the 4460 to get to 1.2ghz. This means more heat and less battery life, with a FIXED battery? Nuts.
 
jasaero said:
I was referring more to R&D to get to the initial maps you are referring to I suppose, but you could be correct.

Just seems in the PC world that a lot of times you only have one or two die designs/maps for a CPU or GPU and then they pump them out and bin them and enable or disable this or that to get a plethora of models. Actually remember early AMD processors you could jump circuits on the packaging to get new features only intended for higher models if you got a lower model chip. It seems I have read different overall maps if you will were only developed for quite a bit different die sizes where you might be able to fit a good bit more dies on a waffer? That sound normal? I don't know and it's possible 4460 is enough extra circuits to justify another die based on this thinking for all I know.
Click to expand...

First, complexity. These beasties are SoC packages - system on (a) chip.

Compared to the PC world, that's taking a number of chips, glue logic, motherboard piece(s) - and putting that all on to one - single - chip.

And the idea of jumping circuits in nanometer design - not something I'd like to expect. On-chip wiring today vs a decade ago is like comparing angel hair to a oak trunk. (I exaggerate, but only slightly. We started calling the thick to thin oxide wiring comparisons "bamboo" and that was years ago.)

It's not about number of transistors.

It's about cookie cutting.

If you want a higher yield per wafer, you have 4 choices:


  • shink the dice, shrink the chips by going from 65 nm manufacturing process to 45 nm to 32 to 28 to 17 to ... the limits of our machinery technology
  • increase the wafer size
  • increase your manufacturing quality to have less loss during production
  • combination of above
 
rushmore said:
Not too well. I went from an advocate to an adversary. IMO, Motorola are deceptive twits and screwing consumers over if a 4430.
Click to expand...

This is a statement about a company that is recycling a name and slapping Droid in front of it rather than use any creativity and give it a good name. (Not that HTC is doing any better with the name Rezound) but still. :(
 
VoidedSaint said:
i dont know why i bother even reading these comments, no real useful information about the device, only speculations of rumors where its going..... i agree with OTD its real easy to start rumors, funny thing is though, as i post this 6 more posts will appear before me once i hit Post Quick Reply



haha i was right! 6!!
Click to expand...

That's one of the main reasons I stay away from this thread, I have but 10 posts in this thread (maybe)........plus, too many posts to read to keep up with this Monster Thread........Darn you Steven for starting this.......lol
 
EarlyMon said:
Obsolete? Ok...

And where are you getting USELESS from?

You honestly believe that anyone would be so stupid as to not build their revision to support the actual hardware existing on the phone?

I'm going to disagree.

If you find that onscreen buttons obsolesces capacitive button for user-friendliness or something - sure, ok, that's an opinion and those are never wrong by definition.

But - onscreen buttons when not needed with capacitive buttons already there? I don't see that happening.
Click to expand...

I'm not worried about the buttons becoming obsolete, because surely the software can recognize whether or not the phone has physical buttons. What I think is more of a point is that Google/Sammy stated 720p was the default resolution for 4.0. I don't know what effect rescaling the UI for older (read: RAZR)/other phones will have in terms of performance.
 
EarlyMon said:
And the idea of jumping circuits in nanometer design - not something I'd like to expect. On-chip wiring today vs a decade ago is like comparing angel hair to a oak trunk. (I exaggerate, but only slightly. We started calling the thick to thin oxide wiring comparisons "bamboo" and that was years ago.)
Click to expand...

Weren't you telling us about FPGA's before? And hell, couldn't a simple microcode update change a chip from one type to another? I think that's what Intel's doing w/their latest adventures with customer unlockable/upgradeable CPUs.

Edit: Oops, ARM doesn't use microcode. :confused:
 
dmiller2007 said:
You're just now learning of Motorola's evil intentions? :p
Click to expand...


Pay back will be after the glowing reviews when users have used the device for a few weeks. I expect heat related and battery life issues. Seems no way around it. People should hold off until then to see.
 
Steven58 said:
Welp, I sent a long list of ideas for our next chat party off to Rob and Phases. Phases said they were good and he liked them.. Our next part is going to be even BETTER!!

Can anyone say "YaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaY!!!!!!!??????????"
Click to expand...

ANOTHER ONE??? :eek:

Heck, Steven, I couldn't keep up with the last one! You guys have fun, we'll be right here :)
 
For those concerned about the uselessness of their current buttons:

Controls for system UI visibility

Since the early days of Android, the system has managed a UI component known as the status bar, which resides at the top of handset devices to deliver information such as the carrier signal, time, notifications, and so on. Android 3.0 added the system bar for tablet devices, which resides at the bottom of the screen to provide system navigation controls (Home, Back, and so forth) and also an interface for elements traditionally provided by the status bar. In Android 4.0, the system provides a new type of system UI called the navigation bar. You might consider the navigation bar a re-tuned version of the system bar designed for handsets—it provides navigation controls for devices that don’t have hardware counterparts for navigating the system, but it leaves out the system bar's notification UI and setting controls. As such, a device that provides the navigation bar also has the status bar at the top.

To this day, you can hide the status bar on handsets using the FLAG_FULLSCREEN flag. In Android 4.0, the APIs that control the system bar’s visibility have been updated to better reflect the behavior of both the system bar and navigation bar:

The SYSTEM_UI_FLAG_LOW_PROFILE flag replaces the STATUS_BAR_HIDDEN flag. When set, this flag enables “low profile" mode for the system bar or navigation bar. Navigation buttons dim and other elements in the system bar also hide. Enabling this is useful for creating more immersive games without distraction for the system navigation buttons.
The SYSTEM_UI_FLAG_VISIBLE flag replaces the STATUS_BAR_VISIBLE flag to request the system bar or navigation bar be visible.
The SYSTEM_UI_FLAG_HIDE_NAVIGATION is a new flag that requests the navigation bar hide completely. Be aware that this works only for the navigation bar used by some handsets (it does not hide the system bar on tablets). The navigation bar returns to view as soon as the system receives user input. As such, this mode is useful primarily for video playback or other cases in which the whole screen is needed but user input is not required.
You can set each of these flags for the system bar and navigation bar by calling setSystemUiVisibility() on any view in your activity. The window manager combines (OR-together) all flags from all views in your window and apply them to the system UI as long as your window has input focus. When your window loses input focus (the user navigates away from your app, or a dialog appears), your flags cease to have effect. Similarly, if you remove those views from the view hierarchy their flags no longer apply.
Click to expand...

The new APIs allow for you to hide the navigation bar completely (I believe these were present in honeycomb too EDIT: jk you can't hide it on tablets).

It shouldn't be too hard to write an application (perhaps locked into the System) that continuously hides the virtual buttons (navigation bar).

Also, the menu button will still act like a menu button. Newer apps should use "ActionBar", which will be accessible by the menu button (I believe...)
Options menu button

Beginning with Android 4.0, you'll notice that handsets no longer require a Menu hardware button. However, there's no need for you to worry about this if your existing application provides an options menu and expects there to be a Menu button. To ensure that existing apps continue to work as they expect, the system provides an on-screen Menu button for apps that were designed for older versions of Android.

For the best user experience, new and updated apps should instead use the ActionBar to provide access to menu items and set targetSdkVersion to "14" to take advantage of the latest framework default behaviors.
Click to expand...
 
rushmore said:
Pay back will be after the glowing reviews when users have used the device for a few weeks. I expect heat related and battery life issues. Seems no way around it. People should hold off until then to see.
Click to expand...

Probably. Is 1.2 overclocked or just as fast as it comes stable? I'm not as up to date on the processors. I skipped those (dozens of) pages
 
dmiller2007 said:
Didn't the event go pretty smoothly in honk Kong without mentioning a carrier? If a carrier was the issue, don't you think they could have just changed the script at CTIA to not include the mention of a carrier?
Click to expand...


The whole presentation would have to be reworked. Those things are rehearsed and changes have a ripple effect whether large or small.

They just dont go on stage and wing it :)
 
Travillion said:
I'm not worried about the buttons becoming obsolete, because surely the software can recognize whether or not the phone has physical buttons. What I think is more of a point is that Google/Sammy stated 720p was the default resolution for 4.0. I don't know what effect rescaling the UI for older (read: RAZR)/other phones will have in terms of performance.
Click to expand...

Page subject to change as things update, so for now, please see -

Android Developers Blog

Answer: not so much of a problem.
 
BabyBlues said:
This is a statement about a company that is recycling a name and slapping Droid in front of it rather than use any creativity and give it a good name. (Not that HTC is doing any better with the name Rezound) but still. :(
Click to expand...

I'm totally not getting where the Moto hate is coming from. The Honda Civic is now on its 9th generation, but I don't see anybody complaining that they've been re-using the same name for the last 28yrs.

Do you seriously think the RAZR isn't a large improvement over Bionic?
 
dmiller2007 said:
Probably. Is 1.2 overclocked or just as fast as it comes stable? I'm not as up to date on the processors. I skipped those (dozens of) pages
Click to expand...


Same thing really. The point is the chip has to work harder to get to the same speed as the 4460. Result is more heat and power consumption..... In a 7.1mm body and fixed battery. This chip decision could bite Moto on the a$$.
 
Status
Not open for further replies.
Back
Top Bottom