ANDROID OPERATING SYSTEM

Google Android OS, Apps, Projects, Widgets & Phones

Archive for March, 2009

Top Global Android Gateway platform integrates 3G radio together with WiFi and Bluetooth for connectivity to multiple Bluetooth phones and WiFi devices.

See the original post: 
Top Global Announces Google Android Gateway Development to Extend …

If Google’s Android OS is to gain momentum in the non-smartphone products, it may not be long before it reaches entirely into the desktop markets, and possibly even servers (as it is Linux-based). And given the relative sizes of the two …

Continued here: 
HP and Asustek testing Google's Android OS for sub-$500 netbooks

Google Apps users: SMS Backup works for your email accounts too. Locale. Locale has a lot of options to change everything from Display to Wireless settings. There are several applications that allow easy profile settings but most are a manual … Several client applications that support us do allow this feature however not our Android app . so your statement that we’re reducing the resolution is incorrect. Big thanks to Android And Me for the mention in the article! …

Go here to see the original: 
10 Of The Best Free Applications For Android | Android and Me

DOOM on Google Android G1 – Game Review

Posted by shinobiwan23 March - 30 - 2009 - Monday ADD COMMENTS

Port of Doom over to the Android G1 by Google. It (was) free to download from the android market. You can save your games as well. Check out androidandme.com for info on the effort to get Quake 2 onto Android.

http://www.youtube.com/v/HIN2LZNBZAY?f=videos&app=youtube_gdata

Excerpt from:
DOOM on Google Android G1 – Game Review

Developer News

Posted by Dan Morrill March - 30 - 2009 - Monday ADD COMMENTS

For no particular reason other than to celebrate this particular Monday, I wanted to update developers on two Android-related news items. If you’re a developer who will be in the San Francisco Bay Area at the end of May, I hope you’ll join us at the 2009 Google I/O developer conference . You might have already seen the sessions we had listed for Android, but today I’m quite pleased to let you know that we’ve added a few more Android-related sessions. You can find the full list plus abstracts on the Google I/O site, but here are the titles: Turbo-Charge Your UI: How to Make Your Android UI Fast and Efficient Pixel-Perfect Code: How to Marry Interaction and Visual Design the Android Way Supporting Multiple Devices with One Binary Debugging Arts of the Ninja Masters Coding for Life—Battery Life, That Is Writing Real-Time Games for Android Android Lightning Talks These sessions don’t even include the “fireside chat” with the Core Technical Team that we have planned. We’re working on still more sessions too; keep an ear to the ground on this blog and the Google I/O site for the latest info. I’m pretty excited about how the Android sessions for Google I/O are coming together. I think it’s going to be a great event, and I hope to meet many of you there. The other topic I want to mention is that our partners at HTC have uploaded a new system image for Android Dev Phone 1 owners. This new image is mostly the same as the one we mentioned earlier this month, but adds voice dialing. Note that not all features will work correctly in all countries, such as voice dialing and Google Voice Search which currently only work well for US English. Additionally, there are some features that we aren’t able to make available at all in some countries. For instance, this build can’t currently include Google Latitude due to privacy standards in some regions. We’ll always keep the ADP1 builds as full-featured as we can, but it’s important to remember that these devices are primarily intended for development, and won’t necessarily have all the features included on mainstream builds. I hope this news is useful to you. As always, happy coding!

See original here: 
Developer News

Sharing and reusing layouts is very easy with Android thanks to the tag, sometimes even too easy and you might end up with user interfaces that contain a large number of views, some of which are rarely used. Thankfully, Android offers a very special widget called ViewStub , which brings you all the benefits of the without polluting your user interface with rarely used views. A ViewStub is a dumb and lightweight view. It has no dimension, it does not draw anything and does not participate in the layout in any way. This means a ViewStub is very cheap to inflate and very cheap to keep in a view hierarchy. A ViewStub can be best described as a lazy include . The layout referenced by a ViewStub is inflated and added to the user interface only when you decide so. The following screenshot comes from the Shelves application. The main purpose of the activity shown in the screenshot is to present the user with a browsable list of books: The same activity is also used when the user adds or imports new books. During such an operation, Shelves shows extra bits of user interface. The screenshot below shows the progress bar and cancel button that appear at the bottom of the screen during an import: Because importing books is not a common operation, at least when compared to browsing the list of books, the import panel is originally represented by a ViewStub : When the user initiates the import process, the ViewStub is inflated and replaced by the content of the layout file it references: To use a ViewStub all you need is to specify an android:id attribute, to later inflate the stub, and an android:layout attribute, to reference what layout file to include and inflate. A stub lets you use a third attribute, android:inflatedId , which can be used to override the id of the root of the included file. Finally, the layout parameters specified on the stub will be applied to the roof of the included layout. Here is an example: When you are ready to inflate the stub, simply invoke the inflate() method. You can also simply change the visibility of the stub to VISIBLE or INVISIBLE and the stub will inflate. Note however that the inflate() method has the benefit of returning the root View of the inflate layout: ((ViewStub) findViewById(R.id.stub_import)).setVisibility(View.VISIBLE); // or View importPanel = ((ViewStub) findViewById(R.id.stub_import)).inflate(); It is very important to remember that after the stub is inflated, the stub is removed from the view hierarchy. As such, it is unnecessary to keep a long-lived reference, for instance in an class instance field, to a ViewStub . A ViewStub is a great compromise between ease of programming and efficiency. Instead of inflating views manually and adding them at runtime to your view hierarchy, simply use a ViewStub . It’s cheap and easy. The only drawback of ViewStub is that it currently does not support the tag . Happy coding!

More:
Android Layout Tricks #3: Optimize with stubs

As the HTC Magic passes through FCC filters, CPS is there to catch all the nitty gritty details. Head over to CellPhoneSignal.com to check out the full article: www.cellphonesignal.com

http://www.youtube.com/v/XACs7n2qASk&f=videos&app=youtube_gdata

Original post: 
T-Mobile G2 – HTC Magic from CellPhoneSignal

Although there is an incredible amount of hype surrounding Google’s open-source operating system, Android, we are yet to see any addition to the HTC G1 device. The follow up to this handset, the HTC Magic, is due out next month, but other than that, fans of the OS have been left wanting more. When are we going to see all these promised Android phones from the big guns?  According to Unwired View , Orange France has at least six Android phones in their 2009 line-up, to include a rather awful pink HTC Hero (looks very T-Mobile G1-esque to us) and a bunch of others from Sony Ericsson, LG, Samsung and Motorola. They cite French mobile news site Mobinaute, who apparently got it from someone deep within Orange France. Of course, Orange UK is denying everything, including any kind of roadmap for either France or UK HQ.

See the original post here: 
Orange France rumoured to have six Android powered handsets