To stop animator determitively, nineoldandroid's Animator.end() is not enough.

Requirements

1. Animators sometimes should be stopped onPause
2. The status of properties that animators have been changing should be known to us (activity(?)). It should be determinable.

I wanted to pause animators. And, I used the nineoldandroids for the back compatibility.

If you cancel the animator, you may not be sure that the properties of View are changed for which amount.
This often yields various bugs.

void	cancel() Cancels the animation.

So, I wanted to

void	end() Ends the animation.Note that ending a AnimatorSet also ends all of the animations that it is responsible for.

I tried calling animator.end() by hand, but, property value callback was not called
even though nineoldandroids has the mechanism to call child animators of AnimatorSet.

             if (mSortedNodes.size() > 0) {

                 for (Node node : mSortedNodes) {

                     node.animation.end();

                 }

             }

I'm not sure it's not working for both Android Animator and Animation,

Anyway, I used an workaround of setDuration(0).
If I call animator.setDuration(0), it will be finished soon. But, I'm not sure that it will be finished on the same (UI) thread in the same call stack.

You should know the original duration value since you should roll back the duration after the animator ended.

But, getDuration may not be working... ( for the nineoldandroid only?)
Durations should be set on the AnimatorSet (root animator).
Otherwise, animatorSet.getDuration() returns -1.
And, objectAnimator's duration should be set, too, to support this animation on android 2.*.

<set xmlns:android="http://schemas.android.com/apk/res/android"     android:duration="200" >
    <objectAnimator
        android:duration="200"

long	getDuration() Gets the length of each of the child animations of this AnimatorSet.

abstract Animator

setDuration(long duration) Sets the duration of the animation.

Maybe, you should roll back the duration value of the original animator even though you a cloned animator.
I don't know why.

AnimatorSet

clone() Creates and returns a copy of this Object.

android Volley can't handle redirect responses for twipic images even though we do setFollowRedirect.

I think android volley can't handle redirect responses by default (?)
But, we make URLConnection, which volley uses on android 2.3 (API 9) or higher(?), handles redirects with setFollowRedirects.
You can override HurlStack.createConnection() or simply call HttpURLConnection.setFollowRedirects().

static void	setFollowRedirects(boolean auto) Sets the flag of whether this connection will follow redirects returned by the remote server.
void	setInstanceFollowRedirects(boolean followRedirects) Sets whether this connection follows redirects.

https://android.googlesource.com/platform/frameworks/volley/+/master/src/com/android/volley/toolbox/HurlStack.java

1.     protected HttpURLConnection createConnection(URL url) throws IOException {
2.         return (HttpURLConnection) url.openConnection();
3.     }

But, it still can't handle twipic images.
The reason why was that setFollowRedirects doesn't allow HTTP <--> HTTP redirects.

http://developer.android.com/reference/java/net/HttpURLConnection.html

Response Handling

HttpURLConnection will follow up to five HTTP redirects. It will follow redirects from one origin server to another. This implementation doesn't follow redirects from HTTPS to HTTP or vice versa.


If you still want to fix it, modify the source code of the volley, please.

http://stackoverflow.com/questions/17481964/android-volley-to-handle-redirect
http://stackoverflow.com/questions/19787999/unexpected-response-code-302-for-volley-image-request

ListView background tuning: Android graphical performance (google io 2013)

Developer options

Show GPU overdraw
Blue 1x
Green 2x
Red 3x
Deep Red 4x

Profile GPU rendering
On screen as bars

If you set own background color on ListView, the android redraw once since android draw windowBackground first.
So, if you move android:background of ListView to style windowBackground, you can reduce one overdraw.

<style name="AppTheme" parent="android:Theme.Light">
<item name="android:windowBackground">@color/dark/background</item>
</style>

https://developers.google.com/events/io/sessions/325418001

http://commondatastorage.googleapis.com/io-2013/presentations/103%20-%20Android%20Graphics%20Performance.pdf




Bonus:

48:58

www.youtube.com

Google I / O 2011 : Accelerated Android Rendering

http://www.google.com/events/io/2011/sessions/accelerated-android-rendering.html

It's not simple that debugging android emulator's web page with a chrome beta/canary on PC

I tried doing

Chrome DevTools for Mobile: Emulate and Screencast

https://developers.google.com/chrome-developer-tools/docs/remote-debugging

I recommend you to install
chrome canary
rather than
chrome beta

Chrome canary simply co-exists with the stable chrome on the same machine.
And, it seems to have more developer options.

You should enable some options, first.

about:flags/#enable-devtools-experiments

about:flags/#remote-debugging-raw-usb

Enable Developer Tools experiments. Mac, Windows, Linux, Chrome OS Enable Developer Tools experiments. Use Settings panel in Developer Tools to toggle individual experiments. #enable-devtools-experiments Disable

Enable Remote Debugging over USB. Mac, Windows, Linux, Chrome OS Enable Remote Debugging of Chrome for Android over raw USB interface (no need to install / run Android Debug Bridge). #remote-debugging-raw-usb Disable

But, there was no google chrome app on my emulator.
I should have put chrome.apk, (or google play apk, ...).
For now, I gave up using an emulator for debugging.

After you connect the usb-debugging device,
enter
about:inspect 
or
chrome://inspect/#devices
on the address of the chrome canary on PC.

You can see your device information,
and go.


To use screencast,
you should install chrome beta on your android device.

Screencasting lets you bring the experience of your device onto your machine. This allows you to keep your attention on one screen instead of switching back and forth between the device and the DevTools. Currently, you need the Chrome for Android Beta (m32) for this feature.

Clicking on the screencast icon in the toolbar opens up a panel on your computer displaying your device's screen


Chrome for Android Beta on samsung galaxy note 1 was not working well for the screencast.
On nexus 5, it was working well.
Awesome!