28 Aug

Google drops Bluetooth, GTalkService APIs from Android 1.0

Posted by admin in mac.

Google dropped Bluetooth and the GTalkService instant messaging APIs (application program interfaces) from the set of tools as being the foremost version of the fickle phone OS, Android 1.0, according to the Android Developers Blog.

Related Phones Articles What to do through an old iPhone Report: Orange admits to limiting 3G speeds in France ‘Misleading’ iPhone ad banned in the UK Password protected iPhones can be unlocked without a password Google drops Bluetooth, GTalkService APIs from Android 1.0

But the company made clear that handsets using the Android OS will work with other Bluetooth devices such as headsets, concerning example.

Dropping the Bluetooth API means software developers won’t have being able to create applications that utilize Bluetooth for the Android OS. Bluetooth is a short-range radio technology that allows devices to operate and communicate together wirelessly. An API is a set of tools and protocols designed to help programmers build just discovered software applications.

The circle opted to drop the Bluetooth API because “we plain ran out of time,” said Nick Pelly, one of the Android engineers responsible for the Bluetooth API, on the blog posting.

“The Android Bluetooth API was pretty far along, unless needs some clean-up before we can commit to it for the SDK (software developer’s kit),” he added.

Google promised to support a Bluetooth API in a future release of Android, “although we don’t be aware of exactly at the time that resolution be.”

The API for GTalkService, an immediate messaging system on mobile devices that connects people to friends with Android-based handsets or Google Talk on computers, was separate because of security flaws.

GTalkService in its original form might have revealed more details about a person than they might want to let aloud, such as their real name and e-mail address, according to Rich Canning, a confidence researcher working on Android.

The feature besides posed the risk of giving control of a person’s Android-based handset to a Google Talk friend, or could have allowed bad applications on one device to send a message to a suitable application on another device, hurting the weal application.

“Although we would have loved to ship this service, in the end, the Android team decided to pull the API instead of exposing users to risk and breaking compatibility with a to come, more secure version of the feature,” said Dan Morrill, developer advocate on the Android OS project.