Group items tagged

Getting Started Welcome to Training for Android developers. Here you'll find sets of lessons within classes that describe how to accomplish a specific task with code samples you can re-use in your app. Classes are organized into several groups you can see at the top-level of the left navigation. This first group, Getting Started, teaches you the bare essentials for Android app development. If you're a new Android app developer, you should complete each of these classes in order:

I am just getting started with Android development and I have created a nice little widget that displays some info on my home screen. However, I now want to implement a Button on my widget that updates the info in my widget TextView.

Solved - I can confirm that an Activity is NOT needed if you want create a Button to update an Android AppWidget. I have been able to implement my AppWidgetProvider class such that it registers an android.appwidget.action.APPWIDGET_UPDATE intent-filter with the Broadcast receiver in the AndroidManifest.xml, which then fires the onUpdate event in the AppWidgetProvider class (which in turn then runs the UpdateService).

The UpdateService in my AppWidgetProvider class then uses onHandleIntent to run a private buildUpdate method - which registers the onClick event with a call to setOnClickPendingIntent as follows:

Additionally, you can feel free to use the Search bar selection mechanism as a replacement for tabs since it’s really just a fast pivot on a data set. If you have more than 3 data sets, tabs become problematic since no more than 3 can be onscreen at once. For example, look at how we implemented the Profile switching mechanism below:

The good news for developers is you get this highly functional contacts feature for free if users choose to sync contact information into your app

The good news for developers is you get this highly functional contacts feature for free if users choose to sync contact information into your app. QuickContact for Android provides instant access to a contact's information and communication modes.

I am just making some AppWidget and I want to pass some Strings through UpdateView to an Activity. But the Bundle is null. I try this: -Widget.java                       Intent defineIntent = new Intent(context, Visor.class);                        defineIntent.putExtra ("org.rss.androides.post2","artist");                        PendingIntent pendingIntent = PendingIntent.getActivity(context, 0, defineIntent, 0);                        updateViews.setOnClickPendingIntent (R.id.widget, pendingIntent); -Viewer.java           Bundle b = intent.getExtras();                 if (b == null) {                     finish();                     return;                 } b is always null.

Remember that PendingIntents aren't keyed using extras: http://groups.google.com/group/android-developers/msg/b296f43ae70c4587 You could hack the extras through by mangling them into Uri parameters, or if you're using a ContentProvider, just point to a specific row.

Or use PendingIntent.FLAG_UPDATE_CURRENT; just be careful that each active instance has its own unique Intent.

手势相对于无趣的触摸和点击来说，给用户带来了的动态感。但是，缺乏一致性，操作的不易发觉，加上极易触发的不可恢复的操作，使得整个系统的可用性遭到损害。  我们迫切的需要回到基本原则，为这些系统开发可用性指南，这份指南应该基于交互设计的坚实原则，而不是某个公司在人机交互指导中的奇思，或者一些开发者的妙想

简单的宣称你的用户界面“有趣”和“自然”并不能证明你的界面可用，当你的用户使用软件时，对于如何操作茫然无措，并不是什么好玩的事情

1.Android 许多重要的功能是不可见的，除非你长按界面上的某东西，我经常对此感到懊恼

Android 的某些功能着实让人喜爱，而另一些尚需改进。我们觉得 Google 应该改进的一个地方就是 Android 的待机锁定屏幕的可用性。Android 的优秀的小工具框架能让它在一瞥之间提供不少信息。现在的这个空旷的锁定屏幕一定可以得到增强（这对于平板电脑来说非常合适），而多亏了一些应用程序，Android 可以做到这一点

Since: API Level 3

Constants for supporting speech recognition through starting an Intent

Authentication with App Engine, regardless of where you're doing it, is a three-stage process: Obtain an authentication token. This can be done with ClientLogin for installed apps, for example, or with AuthSub for a webapp. When logging in directly to an application, this is the part of the login process where your user sees a Google signin screen. Take that authentication token, and use it to obtain an authentication cookie. Use that authentication cookie in all subsequent requests.

<uses-permission android:name="android.permission.GET_ACCOUNTS"></uses-permission> <uses-permission android:name="android.permission.USE_CREDENTIALS"></uses-permission> <uses-permission android:name="android.permission.INTERNET"></uses-permission>

Create a new file (as root) sudo gedit /etc/udev/rules.d/50-android.rules with the following content SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666" Make sure that the text after {idVendor} is the same as the device id found when using the lsusb command. Save and exit the editor To make execution of the rule possible, perform a chmod sudo chmod a+rx /etc/udev/rules.d/50-android.rules To make the rule active, restart udev sudo /etc/init.d/udev restart

You can perform a check, to see that the Android Dev Phone is shared with Ubuntu, by opening a Terminal (inside Ubuntu. Open a VMWare Remote Console to make use of the Ubuntu) and type the following command lsusb A list of USB devices will be shown. For example: Bus 002 Device 001: ID ld6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 0bb4:0c02 High Tech Computer Corp. Bus 001 Device 001: ID ld6b:0002 Linux Foundation 2.0 root hub

A facility for the application to tell the system about something it wants to be doing in the background

A facility for an application to expose some of its functionality to other applications.

Spinner s2 = (Spinner) findViewById(R.id.spinner2);Cursor cur = managedQuery(People.CONTENT_URI, PROJECTION, null, null);     SimpleCursorAdapter adapter2 = new SimpleCursorAdapter(this,    android.R.layout.simple_spinner_item, // Use a template                                          // that displays a                                          // text view    cur, // Give the cursor to the list adatper    new String[] {People.NAME}, // Map the NAME column in the                                         // people database to...    new int[] {android.R.id.text1}); // The "text1" view defined in                                     // the XML template                                         adapter2.setDropDownViewResource(android.R.layout.simple_spinner_dropdown_item);s2.setAdapter(adapter2);

魅族M9具体参数曝光： 1GHz三星S5PC110处理器 带有HDMI输出接口 三围59.5 mm x 113 mm x 11mm 三种制式：WCDMA, CDMA, TD-SCDMA 3.6英寸触摸屏幕，720×480分辨率 512MB ROM 512MB RAM Android 2.1 Eclair系统 micro SD/TF扩展 500万像素摄像头 蓝牙/WiFi/GPS/电视输出（HDMI 1.3） 1350毫安电池 价格方面，不送耳机的话大概在255欧元左右，带耳机和8GB内置存储的是290欧元，预计将在今年夏天上市。

Sunil回信了。 Hi Luke, Rest assured the apps are fine. We are migrating people over the new system and will let you know when it's complete. Showing false does not impact your earnings or account. 他只字未提Superdroid的事件。

http://groups.google.co.nz/group/android-developers/browse_thread/thr... 这个有个账号做adsense网页的，账号被封 又打开的，半年前的事情。 在android developer人多些

The question is: How do I reference the Android default icons? In XML this would be: android:icon="@android:drawable/ic_menu_info_details

android.R.drawable.ic_menu_info_details

Creating objects ahead of time is an important optimization. Views are redrawn very frequently, and many drawing objects require expensive initialization. Creating drawing objects within your onDraw() method significantly reduces performance and can make your UI appear sluggish.

If your view doesn't need special control over its size, you only need to override one method: onSizeChanged().