The short answer is “yes”. The Honeycomb emulator performance will be improved in future release of the development tools. For right now, you should start by increasing the amount of device RAM used by the emulator. The default is 256Mb but 1Gb is probably more reasonable. [Update (April 9 2012) — The latest developer tools … Read more
You could use the online IDE. It’s the Mozilla project that started out as Bespin a few years ago. I’ve been playing with it for a while, and I am quite impressed with how well it works. And it hooks right into github. There are even ways of running it in offline mode.
Whenever you are creating/starting ActionMode Create by mMode = startActionMode(….); To Dismiss it use following Syntax if (mMode != null) { mMode.finish(); }
Drawable d=getResources().getDrawable(R.drawable.background_image_name); getActionBar().setBackgroundDrawable(d); The above code sets the background image for the action bar. Hope it helps.
Not had a chance to check it yet but API 11 introduced the following public dimens: notification_large_icon_height notification_large_icon_width Should be able to use those to scale your image before setting it on the notification.
Thank you @Amir for point out the log. Discovered a line: decoder->decode returned false This seems to be a common problem. Doing a search I found a solution. My previous code: URLConnection conn = url.openConnection(); conn.connect(); inputStream = conn.getInputStream(); bufferedInputStream = new BufferedInputStream(inputStream); bmp = BitmapFactory.decodeStream(bufferedInputStream); Code which is working: HttpGet httpRequest = null; try … Read more
I found the most effective fix for this, first mentioned here, was to set a transparent background color after the layout has been inflated: webView.setBackgroundColor(Color.argb(1, 0, 0, 0)); Yes, it’s a total hack, but it’s the only solution I’ve found to work well without disabling hardware acceleration. Note that this does not work through setting … Read more
Currently the minimum limit is 2048px (i.e. the hardware must support textures at least 2048×2048.) In ICS we will introduce a new API on the Canvas class that will give you this information: Canvas.getMaximumBitmapWidth() and Canvas.getMaximumBitmapHeight().
New version of Support Library v4 (or Android 4.2, ofcourse) resolve this problem much simply. For do this, simply do constructor of your custom FragmentPagerAdapter like this: public CustomFragmentPagerAdapter(android.support.v4.app.Fragment fragment) { super(fragment.getChildFragmentManager()); // write your code here } This work because new Android version approve using nested Fragments
By default Android will retain the fragment objects. In your code you are setting the homeFragment in your onCreate function. That is why it is allways some homeFragment or fl what ever that you set in onCreate. Because whenever you rotate, the onCreate will execute and set your fragment object to the first one So … Read more