• 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.
nj02vette said:
I'd prefer a delayed phone that works, as opposed to having a phone that can't keep a call.

But that's just me. :D

Seriously though, too many people I know have issues with AT&T, so not going down that route at all. Sprint right now would be my #2 carrier choice.
Click to expand...

You expect an awful lot from a smartphone... Call quality? YOu would think it was supposed to be a phone or something... oh... wait...
 
nj02vette said:
Possibly because Samsung is the cause of the delay? Just some food for thought.
Click to expand...


I'm not sure why Verizon wouldn't speak about their own products though. Both companies have officially announced the device, yet only one is admitting to a delay. Regardless of who is responsible for the delay, it makes no sense that Verizon is not saying anything.
 
Highwayman said:
Not picking on you Sox... Am I missing something in this article, or is there no supporting documentation for the assertion? :)
Click to expand...
The Phandroid article is just a bit off in at least two parts:

1. It says 9th instead of 8th.

2. The Business Insider article said that Samsung are the ones that confirmed the Dec. 8th date, not Verizon.
 
This is from Phil Nickinson over at AC:

Jesus H. OK. This isn't that difficult.

That's from a Business Insider post that attributes ... no one. Nada. And carries even less information than an incorrect Best Buy flyer.

We're not doing a front-page story on it because it's not worth my time -- or yours. But for what it's worth, I did just speak with Samsung Corporate PR, which "has no official word."

And you're right. Samsung won't be the one to announce the date. Verizon will. (Maybe both simultaneously, but you know what I mean.)
Click to expand...
I agree with him 100%. as I said in my previous post just a minute ago.

no official source
no official delay.
 
Badget78 said:
This is from Phil Nickinson over at AC:

I agree with him 100%. as I said in my previous post just a minute ago.

no official source
no official delay.
Click to expand...
Yeah, I thought it very odd that the Bus. Insider would quote someone from Samsung as confirming the Dec. 8th date and not Verizon. That would be like Samsung stepping on Verizon's toes.

Verizon will be the ones to announce an official date, nobody else.
 
Badget78 said:
This is from Phil Nickinson over at AC:

I agree with him 100%. as I said in my previous post just a minute ago.

no official source
no official delay.
Click to expand...

Yeah, so in other words another total BS article. I knew it. The lack of a screenshot or any hard evidence was a dead giveaway that it was bunk.
 
Here's a size comparison. I'm not sure BB know's what she's getting into. :p
 

Attachments

  • phones.jpg
    phones.jpg
    180.1 KB · Views: 143
Ringhale said:
Well sorry but since you guys have to play by the rules now things are going to be a little different... BTW hows that 6-5 record feeling

GO BLUE!!
Click to expand...
Noooooooo...hit the thanks button by accident ..but in reality, how's it going to feel losing to the same team...your biggest rival,like 8 times in a row, even in our worse season in years. Really? Gotta be a little hard talking smack after years of but whippings, blue alright, sad and blue, and black and blue. And don't give a damn bout you. OH...........
 
nj02vette said:
On paper, you'd expect the exact opposite. LTE radio and Blur must be the culprits.

EarlyMon is really the expert on the S3, but I believe Qualcomm also packages the 4G radio on the SoC rather than a separate chip. The S3 also can run it's dual cores independantly, something the Cortex A9 can't do.
Click to expand...

They package the modem/controllers on the S3, but the actual radios (of all kinds) are on separate chips.

In the case of my phone, the WiMAX/4G radio is still that 65 nm Sequans, so it's still a hog. (My battery life brags are without 4G, rarely have access to it.)

Without a proper teardown on the Rezound (the only one I've seen still had the RF shielding over the main components, so no way to get part numbers) or a schematic, no way to tell what the LTE or other radios are.

And speaking of RF - an SoC is enough of a nightmare to manage for its own RF with various multi-speed buses - so imagine how much worse that would be if you added the radios into that same chip.

The OMAP4 in Nexus is really something at managing the internal clock speeds to maintain data integrity - can't praise that enough.

The S3 was originally marked as the 8260/8660 where the first had only the GSM modem/controller and the second had that plus the CDMA one. People constantly kept reading that as radios and then causing a negative perception that someone was holding out on them for world-phone capabilities. I'm not 100% sure, but I think that's why they re-named it to the S3 and then took down the sub-model explanations from their public site (last I checked).

And a little PS on anything S3 or Snapdragon - it's not really A8 based (I used to make that same mistake). Snapdragon is to Cortex as AMD is to Intel - they can run the same commands, but just as an AMD is not a version of an Intel, so a Snapdragon is not a version of an A8 Cortex.

~~~~~~~~~

If anyone cares, here's a pretty good teardown of the RAZR (not as good as others they've done, but pretty good) -

Motorola Droid RAZR Teardown - Page 3 - iFixit

I was very surprised to find that the full memory package was not a single MCP by Samsung, but rather that plus a Toshiba chip - so I may have to eat crow on the idea that the Gnex will use a single MCP for memory. (Well, that - or Samsung kept those to themselves, we'll soon see I think.)

Hope this helps! :)
 
MMcCraryNJ said:
Not that i don't believe you, but do you have a link or anything to back that up? The last I heard the only device in the source right now is the HSPA+ model.

EDIT: http://source.android.com/source/building-devices.html

"The only supported phone with the current release is the GSM/HSPA+ Galaxy Nexus, a.k.a. "maguro". GSM/HSPA+ Galaxy Nexus is currently the recommended device to use with the Android Open-Source Project."

Directly from the Android Source page.
Click to expand...


it took me forever to find this but this is where I got the info from. I re-read it and saw the end where he says its his speculation but he did say the source will be there even if it is not fully supported on the future builds, much like the NS4G and NS dont always get the updates together. but being the source is there that lends hope that it won't be all that difficult to compile using the old source files and patching a GSM update.

https://groups.google.com/forum/#!topic/android-building/qzSxFEqWvNg http://
 
If the GNex is not on VZW by the eighth or we don't have a concrete date soon I am done.

I will get one unlocked for AT&T. T-MO or Sprint. Or wait until they are released for one of those carriers.

Why? I truely feel VZW has kept us in the dark for selfish reasons. If they continue to do so adios.

This is America and the customer is ALWAYS right (yeah right) but seriously as I stated on Facebook, we pay premium prices for service and devices so we should get premium treatment. (Asbestos suit is on let the flaming begin!)
 
EarlyMon said:
They package the modem/controllers on the S3, but the actual radios (of all kinds) are on separate chips.

In the case of my phone, the WiMAX/4G radio is still that 65 nm Sequans, so it's still a hog. (My battery life brags are without 4G, rarely have access to it.)

Without a proper teardown on the Rezound (the only one I've seen still had the RF shielding over the main components, so no way to get part numbers) or a schematic, no way to tell what the LTE or other radios are.

And speaking of RF - an SoC is enough of a nightmare to manage for its own RF with various multi-speed buses - so imagine how much worse that would be if you added the radios into that same chip.

The OMAP4 in Nexus is really something at managing the internal clock speeds to maintain data integrity - can't praise that enough.

The S3 was originally marked as the 8260/8660 where the first had only the GSM modem/controller and the second had that plus the CDMA one. People constantly kept reading that as radios and then causing a negative perception that someone was holding out on them for world-phone capabilities. I'm not 100% sure, but I think that's why they re-named it to the S3 and then took down the sub-model explanations from their public site (last I checked).

And a little PS on anything S3 or Snapdragon - it's not really A8 based (I used to make that same mistake). Snapdragon is to Cortex as AMD is to Intel - they can run the same commands, but just as an AMD is not a version of an Intel, so a Snapdragon is not a version of an A8 Cortex.

~~~~~~~~~

If anyone cares, here's a pretty good teardown of the RAZR (not as good as others they've done, but pretty good) -

Motorola Droid RAZR Teardown - Page 3 - iFixit

I was very surprised to find that the full memory package was not a single MCP by Samsung, but rather that plus a Toshiba chip - so I may have to eat crow on the idea that the Gnex will use a single MCP for memory. (Well, that - or Samsung kept those to themselves, we'll soon see I think.)

Hope this helps! :)
Click to expand...

This is some good stuff. I need to come here during the evening shift more often.
 
nexusprimepls said:
I wish I had an answer for you, but all I know is I barely used my RAZR the last two days, and have went in to work with a 100% charge, and have had to charge it by 2:00 both days. That is fact, anything else I would have to say would be speculation.
Click to expand...


Hmmm. I've been unplugging at 9am and generally by 7pm or so am down to 20%ish. I have a bunch of apps notifying, but I usually pull back the frequency.

That being said, I have the power saver screen setting on, as the display seems to suck up most of my battery usage.

Did you set the moto apps you're not using to autokill with task manager?
 
nj02vette said:
I'd prefer a delayed phone that works, as opposed to having a phone that can't keep a call.

But that's just me. :D

Seriously though, too many people I know have issues with AT&T, so not going down that route at all. Sprint right now would be my #2 carrier choice.
Click to expand...

Think it depends where you're located. I had ATT before and never had a problem. I get dropped calls all the time on verizon. On top of that I get no signal at work while ATT gets 3 bars. So based on my experience Verizon's network is just marketing bs.
 
Status
Not open for further replies.
Back
Top Bottom