Go Back   Android Forums > Android Phones > Samsung Galaxy Nexus

New Forums: Nexus Player | Nexus 9
test: Reply
 
LinkBack Thread Tools
Old February 3rd, 2012, 09:25 PM   #51 (permalink)
Senior Member
 
BubbaNexus's Avatar
 
Join Date: Nov 2011
Posts: 541
 
Device(s): dumped the bionic. now have galaxy nexus!
Carrier: Not Provided

Thanks: 47
Thanked 66 Times in 55 Posts
Default

Quote:
Originally Posted by ThorWantNexus View Post

OMG! take your GN and go screaming into the night!

Advertisements
BubbaNexus is offline  
Reply With Quote
sponsored links
Old February 4th, 2012, 12:35 AM   #52 (permalink)
Senior Member
 
ajdroidx's Avatar
 
Join Date: Oct 2011
Location: Colorado
Gender: Male
Posts: 2,769
 
Device(s): Nexus 5, Galaxy note II (back up)
Carrier: AT&T

Thanks: 691
Thanked 1,077 Times in 628 Posts
Default

Coming soon to the cdma galaxy nexus version 4.0.3 with typical Verizon bloat

I hope not
__________________

Most people run from storms, I run to them (back by popular request )
Flickr Gallery
ajdroidx is offline  
Reply With Quote
Old February 4th, 2012, 06:49 AM   #53 (permalink)
AF Addict
 
AntimonyER's Avatar
 
Join Date: Jun 2010
Location: Statesboro, GA
Posts: 13,642
 
Device(s): Droid DNA, Nexus 7 16GB
Carrier: Verizon

Thanks: 5,041
Thanked 9,353 Times in 5,034 Posts
Default

I don't think we will see bloat on the GNex after getting all the clarifications/statements from Google last night. THey are still owning the software builds.

My only question is, why now? The Nexus S 4G has been out there for months, and was "supported" the entire time until now. The GNex was "supported" for two months. I understand Google's explanation, but nothing has changed, so this should have been the story all along. I still wonder if some sort of breakdown with Verizon has occured to trigger Google re-evaluating its CDMA policy.
AntimonyER is online now  
Reply With Quote
Old February 4th, 2012, 07:15 AM   #54 (permalink)
Member
 
swagner53's Avatar
 
Join Date: Dec 2009
Posts: 291
 
Device(s): Verizon Samsung Galaxy Nexus
Carrier: Not Provided

Thanks: 21
Thanked 62 Times in 38 Posts
Default

Honestly, IMO it is Google's lawyers that forced the change. They have been looking at all of their user agreements and policies and have been very carefully rewriting them all. The privacy policy that was a big stink was nothing new either-- just reworded and clarified and turned 60 documents into 1.
__________________
VZW LG G2
swagner53 is offline  
Reply With Quote
Old February 4th, 2012, 07:24 AM   #55 (permalink)
AF Addict
 
AntimonyER's Avatar
 
Join Date: Jun 2010
Location: Statesboro, GA
Posts: 13,642
 
Device(s): Droid DNA, Nexus 7 16GB
Carrier: Verizon

Thanks: 5,041
Thanked 9,353 Times in 5,034 Posts
Default

Quote:
Originally Posted by swagner53 View Post
Honestly, IMO it is Google's lawyers that forced the change. They have been looking at all of their user agreements and policies and have been very carefully rewriting them all. The privacy policy that was a big stink was nothing new either-- just reworded and clarified and turned 60 documents into 1.
Interesting thought.
AntimonyER is online now  
Reply With Quote
Old February 4th, 2012, 08:24 AM   #56 (permalink)
Senior Member
 
Join Date: Apr 2011
Posts: 985
 
Device(s): LG G2 (vzw) - CleanROM 1.0, Samsung Galaxy Nexus LTE (r), HTC Thunderbolt (r), Motorola Droid 3 (r)
Carrier: Verizon Wireless

Thanks: 66
Thanked 206 Times in 145 Posts
Default

Google Issues Statement Regarding CDMA Nexus Devices – Droid Life

Also, it does mention that "Thankfully Google has assured us that the LTE Galaxy Nexus and all other “Nexus” devices will still receive timely updates, remain unlocked, etc."

Just thought I'd put it up in case people haven't seen it.
__________________
---------------------------------------
Current:
LG G2 (VZW) - XDABBEB's v2.0.0 | Samsung Galaxy Nexus LTE - Stock
Asus Nexus 7 Tablet - Stock
Retired: Motorola Droid 3, HTC Thunderbolt, Samsung Fascinate, Samsung Omnia
CharlzO is offline  
Reply With Quote
Old February 4th, 2012, 08:46 AM   #57 (permalink)
Junior Member
 
Join Date: Dec 2010
Posts: 79
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 2 Times in 2 Posts
Default

This is really interesting and confusing.

I have compiled 4.0.3 without doing anything special, no signing or anything just to see as a test if I was able to do it and a learning experience, and the phone worked fine in terms of making calls and having data. The only thing I was missing was gps and I think camera, since those you do need the proprietary drivers from samsung.

So I don't understand their technical answer. According to them if I were to build AOSP for my cdma phone it should not have worked in terms of making calls and getting data?
ghosthunter is offline  
Reply With Quote
Old February 4th, 2012, 09:24 AM   #58 (permalink)
Senior Member
 
Join Date: Apr 2011
Posts: 985
 
Device(s): LG G2 (vzw) - CleanROM 1.0, Samsung Galaxy Nexus LTE (r), HTC Thunderbolt (r), Motorola Droid 3 (r)
Carrier: Verizon Wireless

Thanks: 66
Thanked 206 Times in 145 Posts
Default

I'm thinking maybe other CDMA-based phones moving forward, they might not work, and that maybe it's device-specific, and a crap-shoot as to how it works for people trying? I would imagine devs will always find a way though
CharlzO is offline  
Reply With Quote
Old February 6th, 2012, 06:53 AM   #59 (permalink)
Senior Member
 
esmith818's Avatar
 
Join Date: Nov 2009
Location: NC
Posts: 691
 
Device(s): HTC Rezound returned Galaxy Nexus LTE retired X2 & OG
Carrier: Not Provided

Thanks: 268
Thanked 319 Times in 149 Posts
Default

I thought AndroidUser00110001's comment in this post was the best explanation of Friday's news:
Quote:
On this subject, what Google is saying is kind of the opposite of what is going on.

In Dan Morrill's post he states:

For various technical reasons, recent CDMA Android devices implement core telephony functionality in .apk files provided in binary form by the carriers. To function correctly, these .apk files must be signed by the so-called “platform” key. However, when an individual creates a custom build from the AOSP source code, they don’t use the same signing key as these CDMA flies were signed with.
The result is that these files don’t work properly, and pure AOSP builds running on these devices can’t place calls, access mobile data, and so on. Because we aim to make sure that we are as clear as possible about the degree of support that devices have, we updated the docs over at source.android.com to reflect this reality."

First paragraph true.
Second paragraph not so true. the word "pure" is the key word. If he means that just leaving the source code alone than that is correct. However, up until today Google did provide most of the basic propitiatory files for CDMA model phones on their device driver page. I would say since they did provide the basic files it can be considered "pure" build. When you extract the drivers it places them in the source folder. Now they don't even provide those files any more which kind of contradicts "We will still make available as many as possible of the closed-source binaries for these devices" He states this the same day they pull the files.

(emphasis added)Also, when you download the source there are some scripts that will pull the files from your phone and place them into the source. I guess it is kind of a tool in the source that is not documented in the instructions. These files are signed by what Google calls “platform” and states that the files do not work properly and calls, data and so on will not work. That is not true and that is how there are custom ROMs (Like CodeName < a plug here) that can make calls, transfer data and so on.

When the files that are needed are pulled from phone they still retain that platform key. When they are built into the ROM from the source the signature is not touched and remains the same platform key while other non-propitiatory files are signed with the public key. There are no conflicts and everything works. If you use the Verizon framework files then Verizon apps like their NFL app will work on AOSP builds too.


So I don't see how any of what he said makes sense since depending on what tools and files you used from Google that most, if not everything will work.

There are times that the signature will make a difference but I can not think of a way how it does in this case. One way it would make a difference is if Verizon updated one of their apk files through market, you may get a signature mismatch error but they would never update one of the propitiatory files through market but would issue it through an OTA update.

All they did today was take the drivers down from device page, left the scripts to pull the drivers from phone in place and make everyone confused.
CDMA providers can sign the files with same key to make things easier but they choose not to or have not decided yet.

Google could have said just screw supporting CDMA devices since they dropped the Nexus S 4G too or there is something going in the background that has not come yet.

It's just a word game for now and they will still push updates (hopefully) for the Galaxy Nexus LTE although they may come later than the GSM version. It has been the case for any Nexus device that was a bit different than source. The Nexus S 4G is just officially getting ICS from Google over a month that the GSM version got it and the same holds true to the Nexus One when Vodafone altered it a bit.

The only thing that makes an Android phone a developer device is that it provides support with AOSP other than that, you can build an app on any phone, even the most locked down Moto phone So they can state the the LTE Galaxy Nexus is a developer phone but all they are doing there is watering down the meaning of a truly pure developer phone and Google experience phone that actually meant something until now.

They should have not called the LTE version a Nexus phone and made it a Droid in the terms that the original Droid was. Sort of an unofficial developer phone that was unlocked and can run AOSP with a few extra files.

This was coming before today. It's why I believe the Google logo never appeared on the back of the LTE edition and why some Verizon apps were allowed on it. Only time that has happened with a Nexus phone.

Sorry for the longest post...
I just hope this wasn't in response to the issue several of us have been having with the mic cutting out on calls, but I'm hopeful that is not the case per his 2nd to last paragraph which certainly makes valid points.
esmith818 is offline  
Reply With Quote
Old February 6th, 2012, 08:25 AM   #60 (permalink)
Senior Member
 
Mahalo's Avatar
 
Join Date: Apr 2010
Location: Tampa, Florida
Posts: 520
 
Device(s): Galaxy Nexus
Carrier: Not Provided

Thanks: 190
Thanked 242 Times in 111 Posts
Default

MEh, I'm rooted and Rommed... I'll get my updates from devs before they are released anyway (in most cases.)
__________________
"We are a democracy of readers and we should keep it that way." -- Ray Bradbury
Mahalo is offline  
Reply With Quote
sponsored links
Old February 6th, 2012, 11:14 AM   #61 (permalink)
AF Addict
 
AntimonyER's Avatar
 
Join Date: Jun 2010
Location: Statesboro, GA
Posts: 13,642
 
Device(s): Droid DNA, Nexus 7 16GB
Carrier: Verizon

Thanks: 5,041
Thanked 9,353 Times in 5,034 Posts
Default

The biggest concern of mine is not the fate of my dear GNex, but the chances of ever getting another, as I am stuck with Verizon. It seems that at least until CDMA has been completely phased out, VZW will not see another Nexus.
AntimonyER is online now  
Reply With Quote
Old February 6th, 2012, 02:33 PM   #62 (permalink)
 
Join Date: Jan 2012
Posts: 53
 
Device(s): Big Red Galaxy nexus
Carrier: Not Provided

Thanks: 1
Thanked 7 Times in 6 Posts
Default

There will be a new nexus on verizon man people go crazy over something like this lol. And you wonder why government don't tell us about anilens hahaha.
butternutz is offline  
Reply With Quote
Old February 6th, 2012, 02:34 PM   #63 (permalink)
Senior Member
 
Join Date: May 2010
Posts: 3,335
 
Device(s): Moto X, Nexus 7
Carrier: Not Provided

Thanks: 89
Thanked 1,543 Times in 794 Posts
Default

Quote:
Originally Posted by AntimonyER View Post
The biggest concern of mine is not the fate of my dear GNex, but the chances of ever getting another, as I am stuck with Verizon. It seems that at least until CDMA has been completely phased out, VZW will not see another Nexus.
All it would take is to do what Apple did: install a dual band chipset, one that integrates pentaband GSM, with CDMA.

Unfortunately, the fact that there is almost no overlap in LTE frequencies means that someone is going to have to come up with a hell of a chip to have a "global" LTE phone. So the problem may be getting worse, not better.
binary visions is offline  
Reply With Quote
Old February 7th, 2012, 06:26 AM   #64 (permalink)
AF Addict
 
AntimonyER's Avatar
 
Join Date: Jun 2010
Location: Statesboro, GA
Posts: 13,642
 
Device(s): Droid DNA, Nexus 7 16GB
Carrier: Verizon

Thanks: 5,041
Thanked 9,353 Times in 5,034 Posts
Default

Quote:
Originally Posted by binary visions View Post
All it would take is to do what Apple did: install a dual band chipset, one that integrates pentaband GSM, with CDMA.

Unfortunately, the fact that there is almost no overlap in LTE frequencies means that someone is going to have to come up with a hell of a chip to have a "global" LTE phone. So the problem may be getting worse, not better.
Well the key isn't so much the frequency differences, as the LTE protocols enforced by the FCC. It is much closer to a GSM environment than a CDMA environment, and so having a fully supported device on Verizon once they switch over to LTE doesn't require Google getting the proprietary binaries like it does for CDMA. Which is what Google has been saying is the problem all along.
AntimonyER is online now  
Reply With Quote
The Following User Says Thank You to AntimonyER For This Useful Post:
binary visions (February 7th, 2012)
Old February 7th, 2012, 06:48 AM   #65 (permalink)
Senior Member
 
Join Date: May 2010
Posts: 3,335
 
Device(s): Moto X, Nexus 7
Carrier: Not Provided

Thanks: 89
Thanked 1,543 Times in 794 Posts
Default

Gotcha. I was under the assumption that Google was only going to support one chipset/driver set as the pure developer phone, and that any other versions were sort of secondary to the primary "developer phone."
binary visions is offline  
Reply With Quote
Old February 7th, 2012, 09:36 AM   #66 (permalink)
Member
 
Ed5275's Avatar
 
Join Date: Jul 2010
Location: Harrisburg, PA
Posts: 152
 
Device(s): Galaxy Nexus
Carrier: Verizon

Thanks: 12
Thanked 91 Times in 33 Posts
Default

Oh I think we all know what time it is...RAMPAGE!!!
Ed5275 is offline  
Reply With Quote
Reply

Galaxy Nexus
Current Rating:
Rate this Phone:

The Galaxy Nexus is the third official phone contracted by Google and the first phone to come with Android 4.0 Ice Cream Sandwich. Specs include a 1.2GHz dual-core processor, 1GB of RAM, 16/32GB of internal storage, a 4.65 inch 720p HD Super AMOLED... Read More



Go Back   Android Forums > Android Phones > Samsung Galaxy Nexus
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 04:51 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.