Pages

24 Sep 2014

Show unused resources in Android Studio

Today when I was reading about how to decrease size of an APK file, I discovered a functionality that I have been looking for in Android Studio, it's how to show unused resources. This functionality becomes extremely helpful when you want to optimize your APK file before release, and I believe the smaller your APK file the more download your app will get.

Enough rambling, this is how you get it:
Analyze -> Inspect code...
Then in  Inspection windows (View -> Tool Windows -> Inspection), under Android Lint, you will find an entry named "Unused resources", click on it and you would get something like:



Oh, just one more note, I'm using Android Studio Beta 0.8.11 (Updated from Canary Channel)
Yeah, that's it.

Happy coding ;)

10 Jul 2014

ImageView.setImageBitmap and other ImageView's set image methods

Have you ever stumbled in a case that you use ImageView.setImageResource(R.drawable.your_image) and your image is displayed totally fine in all devices, then you want to make your ImageView more dynamic by put your image into a server, then use something (like Volley, UniversalImageLoader...) to load the image as a Bitmap, then use ImageView.setImageBitmap(your_bitmap) to display your image but it's displayed fine in all devices anymore?!

I got myself into that case today, after using ImageView.setImageBitmap(), my image is displayed too big in some devices and too small in some others. It took me an hour debugging and reading the ImaveView's source code and still couldn't figure out why but reminded me about Android's DisplayMetrics.
As we are developing Android and iOS versions parallel, both share the same resources, and I put all Android's image resources into drawable-xhdpi (as you may know, Android's xhdpi and iOS's retina have the same density), so when I use ImageView.setImageResource(), it displays my images pretty well on all current popular devices (exclude tablets), but why not ImageView.setImageBitmap()?!

The reason is ImageView.setImageResource() cares about device's density, but setImageBitmap() doens't seem to, I think it probably uses some default settings. So to fix it, just use Bitmap.setDensity() with an appropriate density from DensityMetrics. For example, in my case, I would use:

 bitmap.setDensity(DisplayMetrics.DENSITY_XHIGH);


That's it ;-)
Happy coding, guys!

8 Jun 2014

9GAG - TV's iPhone app like animation on Android

I'm always a huge fan of http://9gag.com, and recently, they released a version of http://9gag.tv for iPhone with very cool animation. When I saw it, it aroused my curious, so I tried to implement it on Android, and here is what I've got :)



You can grab the source code here: https://github.com/mrleolink/9GAGTVAnimation

A side note: This is just a simple implementation I have made in a few hours, I tried to reuse views for cards bust just in a very simple way. I believe that this sample can be improved to hook with a custom Adapter to create a completed widget for Android, but I don't have enough of time at the moment, so if any of you have time to implement it, feel free to give me a pull request.

20 May 2014

Android Canvas's clipping functions doensn't work?

I was working on an Android's custom view to show a volume bar with an overlay gradient, it looks somewhat like to this:


My approach was calculate small volume bars's RectF then use Canvas's clipRect to clip the canvas, then draw the gradient and gray part on it. Everything worked well with Nexus 5 and Galaxy S2 LTE, but not with a NTTdocomo Android phone (all of them were 4.0 up).

At first I thought the divider between volume bars was too small but after double checked, it wasn't the reason. Then it took me 2 hours for many checks (Android API Samples) and searches, it's only because of something called Hardware Acceleration, as written in the developer page:

Hardware acceleration is enabled by default if your Target API level is >=14

 So, Hardware Acceleration must be enabled by default on all of my devices, then I tried to turn it off by putting this line into the Activity which contains my custom view:

android:hardwareAccelerated="false"

And it worked!!!

So all the blames should go to the Hardware Acceleration, but why did it still work with Hardware Acceleration ON on two other devices ?!
It's a question that I haven't but need to figure out later!

P/S: The more I work with Android, the more I see this sentence of a random guy on StackOverflow is very true:

Everything is so random with Android!

Hope this help someone out there to not waste 2 hours at work like I did lol, happy coding guys!

UPDATE: I just found this today (20140728) http://developer.android.com/guide/topics/graphics/hardware-accel.html. There is a table about Unsupported Drawing Operations, so you guys can take a look then enable/disable hardware acceleration to match your needs.

14 Mar 2014

Android - LinearGradient comprehension

Today I read about Property Animation, and I got into following snippet somehow.

TextView tv = (TextView) rootView.findViewById(R.id.textview);
tv.setText("I'm Leo");
tv.setWidth(150);
tv.setBackgroundColor(Color.BLACK);
LinearGradient linearGradient = new LinearGradient(0, 0, 150, 0,
        new int[]{
                Color.BLACK,
                Color.WHITE,
                Color.BLACK
        },
        new float[]{
                0,
                0.5f,
                1
        },
        Shader.TileMode.CLAMP);   
tv.getPaint().setShader(linearGradient);



At first, I couldn't figure out how does LinearGradient really work, especially the part position, why when:

new float[]{
        0,
        0.5f,
        1
},

is used, it gives a result like above picture?!

After an hour of trial-and-error, I realized that:
- The first number 0 means where the first Color.BLACK begins
- The second one, 0.5f means 50% of the width (0 to 150), so the Color.WHITE begins at where X = 75 (relatively with the TextView). And the TextView turns from Color.BLACK(X=0) to Color.WHITE(X=75)  within the part from X=0 to X=75
- Same things happen between the second one and the third one, TextView turns from Color.WHITE(X=75) to Color.BLACK(X=150) within the part from X=75 to X=150

Well, that's how the gradient is rendered as a great above picture, and if you work some more to integrate LinearGradient with Property Animation, you will get a great effect ;)

20 Feb 2014

Alternative to Intent.FLAG_ACTIVITY_CLEAR_TASK

I want to use Intent.FLAG_ACTIVITY_CLEAR_TASK to start my app from a notification on Android's status bar like it's restarted, but as you may know, Intent.FLAG_ACTIVITY_CLEAR_TASK requires Android API 11, so I found an alternative for it. Basically, just replace:

intent.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TASK);
PendingIntent contentIntent = PendingIntent.getActivity(this, REQUEST_CODE, intent, PendingIntent.FLAG_UPDATE_CURRENT);

with

ComponentName cn = intent.getComponent();
Intent restartIntent = IntentCompat.makeRestartActivityTask(cn);
PendingIntent contentIntent = PendingIntent.getActivity(this, REQUEST_CODE, restartIntent, PendingIntent.FLAG_UPDATE_CURRENT);

And it works as expected ;)

5 Feb 2014

A hack to catch soft keyboard show/hide event on Android

Today at work, I got this problem: catching event when soft keyboard comes up/down (or show/hide) ?!

At first, I thought it would be easy to resolve, but after a while of googling, I realized that there is no official event or listener in Android API for that, but I did find some workarounds like:
http://stackoverflow.com/questions/4312319/howto-capture-the-virtual-keyboard-show-hide-event-in-android
http://stackoverflow.com/questions/3793093/android-edittext-soft-keyboard-show-hide-event

Well, there are some workarounds that were already posted but they are incomplete (some work on 4.0.4 but not 2.3, some don't work all the time), but at least they are still useful, they gave me an idea to make this "complete" workaround (well, at least it works like a charm in my case for now, I tested on both Android 2.3 and 4.0.4), so I would like to share it here, hope it helps someone out there ;)

Usage: just use following LinearLayout overridden class as the main layout(and of course, use "match_parent" for its layout_width and layout_height) of the activity where you want to catch soft keyboard show/hide events, then setOnSoftKeyboardVisibilityChangeListener for your main layout. Finally, you need this line in your <activity> tag (in manifest.xml) where SoftKeyboardHandledLinearLayout is used:

android:windowSoftInputMode="adjustResize"

Take a look at following code to get a better idea of how to implement this hack.

19 Jan 2014

WRAP_CONTENT doesn't work with ViewPager?!

Lately, I have been working on an Android project, and when I was making a tutorial activity for it, I got into a problem with ViewPager.

I wanted to use ViewPager and ViewPagerIndicator to show content of the tutorial activity, the ViewPager had a rounded corner background, and each page of it contains an ImageView which is a part of the tutorial. And the problem is although I set layout_width for the ViewPager as wrap_content but it always acts like match_parent?!

After googling for a while, I saw some guys got into the same problem, for example: http://stackoverflow.com/questions/8394681/android-i-am-unable-to-have-viewpager-wrap-content. They proposed some solutions but none of them matches my need, but this anwser gave me an idea.

Because the rounded corner background and all image on pages of the ViewPager have the same size, and as the answer says, it's possible to set a fixed size for the ViewPager, so the solution for my case is just set size of the ViewPager as size of the rounded corner background.

Check out following gist to get a clearer idea about it.