Winstron, a Chinese company, is showing their Android phone at CES:

The GW4 is reportedly currently using Linux right now, but should be running Android within a few months.

More info at ZapNat.

Simon Judge points to the LiPS and Androis/OHA Faq, which outlines the similarities (unity) and differences (open vs. ad-hoc standards) between the Linux Phone Standards, and the Open Handset Alliance.

The Open Handset Alliance, a group of more than 30 technology and mobile companies, is developing Android: the first complete, open, and free mobile platform. On Monday 17th December we’ll be hosting Dick Wall from Google’s HQ in California for a special session about the platform. Dick will provide a technical overview of the Android architecture with an emphasis on developing real-world applications.

You will need a wireless enabled laptop to take part in this event. Refreshments will be provided, but places are strictly limited.

Reserve your seat here.

Resco MobileForms Toolkit 2008 was released today, optimized for .NET Compact Framework 3.5 and featuring a slew of new controls and features:

Bratislava, Slovakia — December 10, 2007 — Resco, a leading provider of advanced developer components and tools for mobile devices, has today released Resco MobileForms Toolkit 2008 optimized for Microsoft Visual Studio 2008 and the .NET Compact Framework 3.5.

See the company’s press release for more info.

The Boy Genius reports that Verizon just announced they are planning on using Android:

Resistance is futile, or so it seems, as everyone looks to be jumping on Google’s new Android mobile handset operating platform. The newest convert to the ways of Google is Verizon. The company has just announced that they will plan on using Android in one form or another…

It all stems from a BusinessWeek article titled Verizon Embraces Google’s Android:

In yet another sudden shift, Verizon Wireless plans to support Google’s (GOOG) new software platform for cell phones and other mobile devices. Verizon Wireless had been one of several large cellular carriers withholding support from the Android initiative Google launched in early November.

But given the stunning U-turn Verizon Wireless made Nov. 27, announcing plans to allow a broader range of devices and services on its network, Chief Executive Officer Lowell McAdam says it now makes sense to get behind Android. “We’re planning on using Android,” McAdam tells BusinessWeek. “Android is an enabler of what we do.”

Welcome to the Party…

Nokia issued a press release unveiling the new device management features of its Intellisync Mobile Suite:

Nokia Intellisync Device Management delivers single service-optimized device management platform that seamlessly combines OMA DM and Nokia Intellisync Mobile Suite device management technologies

New York, NY - Nokia unveils today the newest device management features of Nokia Intellisync Mobile Suite. The next generation release offers single platform to manage both OMA DM compatible mobile devices as well as devices running Nokia Intellisync Mobile Suite client. This technology approach provides flexibility to support a wide variety of mobile devices and operating systems with advanced device management functionalities such as device configuration, application management, asset collection, help desk, theft-loss protection and recovery…

Mobility Site has the skinny.

Techworld posted a mildly interesting article on Google’s Android getting positive early reviews from mobile developers.

After downloading and examining Google’s Android software development kit, some software developers gave the platform favourable initial reviews and praised it as a breath of fresh air for an industry that has long been characterised by closed devices and software.

The article goes on quoting various developers and designers praising Android for its openness, potential, DIY approach, etc.

Just like most superficial tech article, it concludes with a few paragraphs outlining some of the potential problems Android may face, according to their experts. From carrier and enterprise acceptance to Google’s ability to monetise the platform.

Simon Judge is attempting to understand how Google Maps Mobile cell ID-based location actually works:

Hence, my best guess at how this all works is…

App sends IMEI and Cellid (if available) to Google
If IMEI is for operator with location service agreement then get position
else if Cellid available then look it up in Google cellid/position database
else tell the user their phone isn’t supported

He also notes that Java ME, in most cases, is unable to reliably retrieve a cell ID.