Question for those familiar with the AOSP

[Asterdroid]

Let me apologize if this has been posted before, but....

Read the first two lines in the below link. I'm not even going to speculate on what this means for us Verizon peeps, but I'm a bit concerned. Any ideas?

Building for devices | Android Open Source

 

[kvlt]

Let me apologize if this has been posted before, but....

Read the first two lines in the below link. I'm not even going to speculate on what this means for us Verizon peeps, but I'm a bit concerned. Any ideas?

Building for devices | Android Open Source

That is interesting, hoping we dont get shafted... :-\

 

[hyperdude]

"The only supported phone with the current release..."

Just means they're releasing the GSM model's source first. JBQ and other Googlers have said that once they are ready to push ICS onto the Nexus S that they'll add it to the build files.
So my guess is that Samsung and Verizon (and Google?) are either still working on the LTE version's code, or they're just not releasing the source until it (finally) hits shelves.

 

[Phil Nickinson]

It means the AOSP code they just dropped is "targeted" at the GSM version of the Galaxy Nexus, which should be of no surprise to anyone. The Verizon version will be separate (and likely not posted in AOSP?) since it's the Verizon version. Doesn't mean there's not a Verizon version.

 

[Asterdroid]

Thanks Phil.

 

[jerrod6]

Doesn't mean there is not a Verizon version but may mean that the Verizon version is LOCKED and cannot be used by developers and will not get updates from Google which means we will get 2 updates and then have to get a new phone FROM THEM to get the latest operating system from Google. Last week someone rooted the Nexus...Maybe Verizon is updating and testing their programs to keep the phone LOCKED DOWN and that's why there are rumors of a delay. Only my thoughts.

I am just a regular user and most likely will never root but since I have been a Verizon customer since before the name of the company was Verizon( think Bell of Pa, then Bell Atlantic) I don't trust them do to the right thing for anyone but themselves.

Still I am going to buy the Nexus they sell.

 

[MMcCraryNJ]

Doesn't mean there is not a Verizon version but may mean that the Verizon version is LOCKED and cannot be used by developers and will not get updates from Google which means we will get 2 updates and then have to get a new phone FROM THEM to get the latest operating system from Google. Last week someone rooted the Nexus...Maybe Verizon is updating and testing their programs to keep the phone LOCKED DOWN and that's why there are rumors of a delay. Only my thoughts.

I am just a regular user and most likely will never root but since I have been a Verizon customer since before the name of the company was Verizon( think Bell of Pa, then Bell Atlantic) I don't trust them do to the right thing for anyone but themselves.

Still I am going to buy the Nexus they sell.

If the phone was called the "Droid Prime" or "Samsung Prime" or "Galaxy Prime", I might be more willing to agree with you.

This is a Nexus device, lest we forget.

 

[tntdroid]

It wont be locked down. Wouldn't be a nexus then.

Sent from my DROIDX using Tapatalk

 

[kidserious]

Even if it wasn't a nexus device, Samsung doesn't allow their bootloaders to be locked. Not by Verizon, not by anyone. Try and find me one Samsung device, through any carrier, that has a locked bootloader. You won't find one. That, and the fact that samsung's hardware (not build quality, their hardware) is a step or two ahead of other oems, is why they rock! Why else do you think Google chose them two years in a row?

meh

 

[MMcCraryNJ]

Even if it wasn't a nexus device, Samsung doesn't allow their bootloaders to be locked. Not by Verizon, not by anyone. Try and find me one Samsung device, through any carrier, that has a locked bootloader. You won't find one. That, and the fact that samsung's hardware (not build quality, their hardware) is a step or two ahead of other oems, is why they rock! Why else do you think Google chose them two years in a row?

meh

Agree with you on build quality and general overall awesomeness of the hardware.

But, sadly...the Samsung Galaxy Tab 10.1 has a locked bootloader. I have a Tab. However, it is a bit complicated. The first round of releases in June/July, most of them have unlocked bootloaders (mine included...my bootloader is unlocked). If you accept an OTA or get one manufactured after July, then you get a locked bootloader. Samsung WILL lock your unlocked bootloader, at least on the Tab 10.1, via their OTA updates. Basically if you were to buy a Tab right now, it will most likely have it locked down.

BUT...the locked bootloader means nothing in the case of Samsung hardware. You can still flash ROMs and Kernels via either CWM or ODIN (a Samsung flashing tool). There are some things you cannot use...I don't believe you can use fastboot and I know you can't use NVFLASH (a cmd prompt tool for flashing things on Tegra 2 devices). But 99.9 percent of anything you want to do on a Samsung device, you can do so even with a locked bootloader.

 

[kidserious]

Agree with you on build quality and general overall awesomeness of the hardware.

But, sadly...the Samsung Galaxy Tab 10.1 has a locked bootloader. I have a Tab. However, it is a bit complicated. The first round of releases in June/July, most of them have unlocked bootloaders (mine included...my bootloader is unlocked). If you accept an OTA or get one manufactured after July, then you get a locked bootloader. Samsung WILL lock your unlocked bootloader, at least on the Tab 10.1, via their OTA updates. Basically if you were to buy a Tab right now, it will most likely have it locked down.

BUT...the locked bootloader means nothing in the case of Samsung hardware. You can still flash ROMs and Kernels via either CWM or ODIN (a Samsung flashing tool). There are some things you cannot use...I don't believe you can use fastboot and I know you can't use NVFLASH (a cmd prompt tool for flashing things on Tegra 2 devices). But 99.9 percent of anything you want to do on a Samsung device, you can do so even with a locked bootloader.

Well, I am typing this particular comment on my 10.1 LTE tab, which does in fact have an unlocked bootloader. I bought this on august 21st. and it was unlocked. In order to use ODIN, you need access to the bootloaders. If it was locked, there would be no download (odin) mode. Many times, when a samsung device becomes hard bricked, it is because you either flashed the wrong bootloaders or you corrupted your bootloaders during a flash. Either way, if you have access to the bootloaders in anyway, then the bootloader is open. You may be talking about another type of locked, but it has no bearing on anything really. My point is, if you can access/flash boot.bin and sbl.bin, and/or a custom kernel, then as far as anyone is concerned you have an open device. You may be technically right but you see my point.

Meh

 

[MMcCraryNJ]

Well, I am typing this particular comment on my 10.1 LTE tab, which does in fact have an unlocked bootloader. I bought this on august 21st. and it was unlocked. In order to use ODIN, you need access to the bootloaders. If it was locked, there would be no download (odin) mode. Many times, when a samsung device becomes hard bricked, it is because you either flashed the wrong bootloaders or you corrupted your bootloaders during a flash. Either way, if you have access to the bootloaders in anyway, then the bootloader is open. You may be talking about another type of locked, but it has no bearing on anything really. My point is, if you can access/flash boot.bin and sbl.bin, and/or a custom kernel, then as far as anyone is concerned you have an open device. You may be technically right but you see my point.

Meh

All I know is, on unlocked Tabs (Wifi Tabs, I have no idea about anything LTE-related), you will see the infamous unlocked padlock upon bootup if your bootloader is indeed unlocked.

If you have one and then accept an OTA by Samsung, before anything happens, a screen comes up that says "Securing bootloader". After your Tab reboots from this, it then installs the update. Once you reboot, the padlock icon is gone, and certain developers on XDA have confirmed that the bootloader is indeed encrypted after this happens, and there is even a small effort ongoing to trying to figure out what encryption method Samsung is using.

However, even with a locked bootloader, you can still root, install clockwork, and use ODIN if you want to. You can flash ROMs and Kernels through CWM. The one thing the people with locked bootloaders have noticed is that you cannot use nvflash as it errors out. If you still have the unlocked bootloader, you can use nvflash all you want.

The one thing I KNOW you cannot do with a locked bootloader Tab is install Ubuntu. You need nvflash for that.

Again, this is for the Wifi Tab. The LTE Tab could be different. Take it for what it is worth, but Samsung is definitely locking down bootloaders (or attempting to at least). You do not need an unlocked bootloader to use ODIN.