Monday, March 31, 2014

This example show how to send command from Android to Arduino Esplora board, in USB Host Mode, to control the LED and Screen of Arduino Esplora. When user toggle the LED by clicking on the button, or change the screen color by slideing the bars, the commands will be add in a command queue, and then send to Arduino in background.

Tuesday, March 25, 2014

This example show how to update content of popup window using Java code at run-time, instead of hard-coded in XML. The TextView (textOut) of Popup Window will be set according to another EditText (textIn) on main layout, before the Popup Window shown.

Monday, March 24, 2014

Previous examples show how to diaply animated GIF using decodeStream(InputStream) and decodeByteArray(InputStream) loaded with a preset resource, /res/drawable/android_er.gif. This example show how to define resource with android:src in XML, and retrieve in custom view.

Tuesday, March 18, 2014

Android Wear extends the Android platform to a new generation of wearable devices. The Android Wear Developer Preview is available now, to let you create wearable experiences for your existing Android apps and see how they will appear on square and round Android wearables. Later this year, the Android Wear SDK will be launched, enabling even more customized experiences.

In the coming months we’ll be launching new APIs and features for Android wearables to create even more unique experiences for the wrist:

The Android Wear Developer Preview provides tools and APIs that allow you to enhance your app notifications to provide an optimized user experience on Android Wear.

With the Android Wear Developer Preview, you can:

Run the Android Wear platform in the Android emulator.

Connect your Android device to the emulator and view notifications from the device as cards on Android Wear.

Try new APIs in the preview support library that enhance your app's notifications with features such as voice replies and notification pages.

Caution: The current Android Wear Developer Preview is intended for development and testing purposes only, not for production apps. Google may change this Developer Preview significantly prior to the official release of the Android Wear SDK. You may not publicly distribute or ship any application using this Developer Preview, as this Developer Preview will no longer be supported after the official SDK is released (which will cause applications based only on the Developer Preview to break).

A number of enhancements have been added to Android and iOS SDKs to help developers save time, increase flexibility, and capture new opportunities.

Full support for device identifiersIn order to give users better control and to provide you with a simple, standard system to continue to monetize your apps, full support for anonymous device identifiers is introduced within the new iOS and Android SDKs. These identifiers help marketers better reach and engage with the types of users most valuable to them while helping developers improve monetization through higher CPMs and fill rates.Seamless auto-updates for AndroidThe Google Mobile Ads SDK is now fully integrated with Google Play Services so you can take full advantage of features and capabilities in each new release of Google Play services, without needing to update your APK. Monetize your appsThe Google Mobile Ads SDK fully supports AdMob and DoubleClick for Publishers. Connect with even more advertisers with ad network optimization - now fully supporting JavaScript based ad network tags via the iOS and Android SDKs.

Now that Google Mobile Ads is supported in Google Play services. The standalone AdMob SDK will be deprecated on 1 August, 2014. Play services supports Advertising ID, and provides seamless updates to Android users.On 1 August, the Play Store will stop accepting new or updated apps that use the standalone Google AdMob SDK. The standalone SDK does not use the Advertising ID, and will therefore be affected by the Google Play Ad Policy. Google Play services still supports devices that don't have the Google Play store installed on it. The only difference is that devices without the Play Store will not receive automatic updates.

Sunday, March 16, 2014

The motion aftereffect (MAE) is a visual illusion experienced after viewing a moving visual stimulus for a time (tens of milliseconds to minutes) with stationary eyes, and then fixating a stationary stimulus. The stationary stimulus appears to move in the opposite direction to the original (physically moving) stimulus. The motion aftereffect is believed to be the result of motion adaptation. ~ Wikipedia.

To see the illusions: Run the app on Android Tablet, and stare to the center of the image. After around one minute, look away (for example look to a face or to your hands). For few seconds everything you see will appear to distort. Or touch the motion picture on screen, it will stop and change to another ImageView.

Friday, March 14, 2014

Last post "Simple SurfaceView example" draw bitmap in surfaceCreated() callback. In this step, a customized Thread, MyThread, is implemented to draw the bitmap running across screen in background thread.