1) If putting in my new sim after my at&t one was in, it first asks me for my pin.  This was given to me when i bought it, so i enter it and then it goes to touch calibration. 
2) after I do touch calibration, it goes to the start up tutorial which tells you how to navigate the phone.
3) when i finish that, it displays the message “new sim card inserted.  copy sim card contacts to phone address book?”  to which i answer no.
4) then if i try to make a call, right after i dial, it gives me the error message “service unavailable”

the same stuff happens if i use my at&t sim except i don’t have to enter a pin at the beginning.  also, when i use the new sim, about a minute after finishing the tutorial i get the error message “sim not provisioned MM #2“

I have installed LG PC Suite 3 & 4 and I am not able to connect phone with either .. using Blutooth or USB cable connection.

In ver. 3, using Bluetooth, I get reponses from phone asking if I want to connect to the PC / PC Suite, enter the code I entered in PC Suite and the phone then asks again and then the PC Suite says Pairing has failed. I installed USB driver from within a folder in Prgram Files / LG PC Suite 3, seen it listed in Device Manager, but no solution. There is no Connection Selection in CF360′s Connectivity for PC Suite, just, mass storage and music sync and data transfer. I did see music sync and the player program in PC Suite showed the phone was connected, but no files / data / anything showed.

In ver 4, using Bluetooth, I get an error that it can not get the IEMI#.

I am able to copy contacts, and almost anything it seems, from phone to pc using my bluetooth and mass storage, but my geek side wants to be able to use PC Suite. – - MikeG0103

I have installed LG PC Suite 3 & 4 and I am not able to connect phone with either .. using Blutooth or USB cable connection.

In ver. 3, using Bluetooth, I get reponses from phone asking if I want to connect to the PC / PC Suite, enter the code I entered in PC Suite and the phone then asks again and then the PC Suite says Pairing has failed. I installed USB driver from within a folder in Prgram Files / LG PC Suite 3, seen it listed in Device Manager, but no solution. There is no Connection Selection in CF360′s Connectivity for PC Suite, just, mass storage and music sync and data transfer. I did see music sync and the player program in PC Suite showed the phone was connected, but no files / data / anything showed.

In ver 4, using Bluetooth, I get an error that it can not get the IEMI#.

I am able to copy contacts, and almost anything it seems, from phone to pc using my bluetooth and mass storage, but my geek side wants to be able to use PC Suite. – - MikeG0103

I have installed LG PC Suite 3 & 4 and I am not able to connect phone with either .. using Blutooth or USB cable connection.

In ver. 3, using Bluetooth, I get reponses from phone asking if I want to connect to the PC / PC Suite, enter the code I entered in PC Suite and the phone then asks again and then the PC Suite says Pairing has failed. I installed USB driver from within a folder in Prgram Files / LG PC Suite 3, seen it listed in Device Manager, but no solution. There is no Connection Selection in CF360′s Connectivity for PC Suite, just, mass storage and music sync and data transfer. I did see music sync and the player program in PC Suite showed the phone was connected, but no files / data / anything showed.

In ver 4, using Bluetooth, I get an error that it can not get the IEMI#.

I am able to copy contacts, and almost anything it seems, from phone to pc using my bluetooth and mass storage, but my geek side wants to be able to use PC Suite. – - MikeG0103

So it’s been a fun day of armchair code forensics and legal analysis on the web after Florian Mueller published a piece this morning alleging Google directly copied somewhere between 37 and 44 Java source files in Android. That’s of course a major accusation, seeing as Oracle is currently suing Google for patent and copyright infringement related to Java, and it prompted some extremely harsh technical rebuttals, like this one from ZDNet and this one from Ars Technica. The objections in short: the files in question are test files, aren’t important, probably don’t ship with Android, and everyone is making a hullabaloo over nothing.

We’ll just say this straight out: from a technical perspective, these objections are completely valid. The files in question do appear to be test files, some of them were removed, and there’s simply no way of knowing if any of them ended up in a shipping Android handset. But — and this is a big but — that’s just the technical story. From a legal perspective, it seems very likely that these files create increased copyright liability for Google, because the state of our current copyright law doesn’t make exceptions for how source code trees work, or whether or not a script pasted in a different license, or whether these files made it into handsets. The single most relevant legal question is whether or not copying and distributing these files was authorized by Oracle, and the answer clearly appears to be “nope” — even if Oracle licensed the code under the GPL. Why? Because somewhere along the line, Google took Oracle’s code, replaced the GPL language with the incompatible Apache Open Source License, and distributed the code under that license publicly. That’s all it takes — if Google violated the GPL by changing the license, it also infringed Oracle’s underlying copyright. It doesn’t matter if a Google employee, a script, a robot, or Eric Schmidt’s cat made the change — once you’ve created or distributed an unauthorized copy, you’re liable for infringement.*

Why does this matter? Because we’re hearing that Oracle is dead-set on winning this case and eventually extracting a per-handset royalty on every Android handset shipped. In that context, “those files aren’t important!” isn’t a winning or persuasive argument — and the more these little infringements add up, the worse things look for Google. Whether or not these files are a “smoking gun” isn’t the issue — it’s whether Android infringes Oracle’s patents and copyrights, since the consequences either way will be monumental and far-reaching. Ultimately, though, the only person who can resolve all of this for certain is a judge — and it’s going to take a lot more time and research to get there.

–
*They’re not directly comparable, but think about the Psystar case for a second. Even though Psystar desperately wanted to argue that Apple’s OS X license agreement was invalid, the judge never got there — he simply ruled Psystar wasn’t authorized to copy and distribute OS X, and swung the hammer. It really is that simple sometimes.

Android source code, Java, and copyright infringement: what’s going on? originally appeared on Engadget on Fri, 21 Jan 2011 19:15:00 EST. Please see our terms for use of feeds.

Permalink

Read the rest here:
Easy Way To Unlock Centennial Wireless Blackberry 8100 | Cellular …

We’ve already established that the Nexus S is almost certainly a Samsung — but what else do we know about it? Well, a quick search for pictures taken with a Nexus S on Flickr and Picasa produced some 5 megapixel results, believe it or not, and some of those users’ albums had been using a Samsung handset with model number GT-i9020 just a few days earlier. If we had to guess, a recent firmware update changed the EXIF identifier for these shots from the code to the actual retail name — Nexus S, that is — which explains the switchover. We’ve got both an FCC filing and a Wi-Fi Alliance certification for the i9020, and it’s definitely a smartphone with 802.11 b / g / n (single-band, unfortunately) and AWS 3G, a radio choice that ties it in nicely with T-Mobile as the Best Buy leak would have us believe.

Interestingly, a little digging reveals that all of these shots on photo sharing sites are coming from Google employees and families of Google employees — and Sammy’s i9000 series is closely tied to the Galaxy S line, which makes sense considering how much the Nexus S seems to look like a Galaxy S. Oh, and if that wasn’t enough, the FCC label documentation for the i9020 lines up perfectly with the leaked picture. So yeah, it’s all kind of coming together — all we need now, Google, is an official Gingerbread and hardware announce. Let’s do this thing.

Google Nexus S is the Samsung GT-i9020? originally appeared on Engadget on Thu, 11 Nov 2010 13:56:00 EST. Please see our terms for use of feeds.

Permalink

Tried many times calling ATT support, LG Manufacture support (as per ATT support recommendation), still i am not able to get the subsidy unlock code for my LG incite, with no luck.

Their response - LG Incite – not eligible to get unlock code

But i do see in various forums, people getting the code from ATT.  Any other alternatives to get the unlock code.