android-3.0-honeycomb

Android 3.0 statusbar & targetSdkVersion in manifest, menu button

一曲冷凌霜 提交于 2019-12-12 03:19:33
问题 I needed to dim Honeycomb's status bar on some screens of my app, so I used the View.setSystemUiVisibility(int) method. But in order for it to work I've changed the targetSdkVersion attribute to 11 in my manifest. Now everything works perfectly, but the "menu" button in the status bar has disappeared so I can't access some options. How do I show it while keeping targetSdkVersion=11? 回答1: How do I show it while keeping targetSdkVersion=11? You don't. Your menu will appear in your action bar.

Android proxy wifi vs mobile [closed]

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-12 02:50:15
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 11 months ago . I know it is a mess when it comes to proxy support in Android and a lot of frustration too. I read most of posts on SO and I am still confused. I would like to support both Wifi proxy and mobile proxy and I know that there has been some changes in proxy support prior to honeycomb and post honeycomb. I also

Android 3.x emulator app launcher not working

≯℡__Kan透↙ 提交于 2019-12-12 02:46:34
问题 I'm trying to check how a web page is displayed in the Android emulator browser, but seems that I'm out of luck today. I just installed the new API 13 AVD, launched it with WXGA resolution and realised that it was unusable (it hanged). Then I edited the configuration and now it is only 640x480. The GUI has changed a little, but still it hangs when I try to open the applications launcher (to find the browser icon). Only the notifications slider works, but is really slow. How can I open the

Why isn't graphics acceleration turned on by default in Honeycomb?

北城余情 提交于 2019-12-11 23:52:39
问题 Why isn't graphics acceleration turned on by default in Honeycomb? Are there any situations when it's better to leave it disabled? 回答1: It is not turned on by default for compatibility reasons. Not 100% of the Canvas API is supported when turned on (although the missing parts are very few and rarely used) and there might be bugs in the new implementation. There are also new constraints (for instance if you try to draw a bitmap larger than the maximum OpenGL texture size, it will fail.) The

How can text selection be disabled in Android 3.0 Honeycomb?

不想你离开。 提交于 2019-12-11 15:25:37
问题 This simple test page has the snippet that typically suppresses text selection on Android, iOS, Chrome, Safari and Firefox: .unselectable { -moz-user-select: none; -webkit-user-select: none; } I have a lot of test devices and I've been able to confirm that this suppresses text selection on the Android 2.X devices, but fails to do so on a Xoom running Android 3.0 Honeycomb. So: Is this a Honeycomb-specific problem or a Xoom-specific problem? Is there a hack for a fix now or a fix coming down

Why do I keep getting exception when re-using bitmaps?

南楼画角 提交于 2019-12-11 15:00:05
问题 background starting from API 11, you can re-use bitmaps when you decode new ones, so that the decoder won't need to re-create totally new large objects. this is done using something like this code (taken from this tutorial) : mCurrentBitmap = Bitmap.createBitmap(imageWidth,imageHeight,Bitmap.Config.ARGB_8888); bitmapOptions.inJustDecodeBounds = false; bitmapOptions.inBitmap = mCurrentBitmap; bitmapOptions.inSampleSize = 1; mCurrentBitmap = BitmapFactory.decodeResource(getResources()

Hardware acceleration flag

泪湿孤枕 提交于 2019-12-11 10:53:02
问题 I'm building an app which will run from Android version 2.2 (Froyo) onwards. I have already built an app with 2.2 for playing videos and in the same app I want to run on Android version 3 (Honeycomb). And here my problem starts with hardware_ accelerated flag. This flag is available from Honeycomb 3 onwards, but not below Honeycomb. I want to ship one common app with Froyo, but as I'm trying my app in Honeycomb, video is not shown. It's clearly because of the hardware_ accelerated flag. I can

Android Fragments API doesn't show background 9patch image correctly

梦想与她 提交于 2019-12-11 03:37:20
问题 I'm porting an existing android app to honeycomb and the fragments API and compatibility library. I'm using the same layout, but I'm loading it into a fragment. The background is a 9patch image, but it now only covers the top left quarter of the screen. The rest of the background is white. If I change the background to a hex color, it covers the entire screen. This has never happened before switching to fragments and the layout did not change. I'm somewhat new to Android and very new to

How to add an outer shadow for a rounded-corners drawable?

牧云@^-^@ 提交于 2019-12-11 01:22:39
问题 I'm using this RoundedCorners library (based on Romain Guy's post) which allows to set both outline border and a rounded rectangular image to an imageView . I need to add an outer shadow (meaning it's outside of the image being shown) to the image that is shown (say ,to direction south-east) . I've decided that since the border is the larger part of what is shown, I would add the shadow to it instead of to the image, using the next extra code in RoundedDrawable : mBorderPaint.setShadowLayer

Android Honeycomb, get instance of Fragments?

余生颓废 提交于 2019-12-10 23:44:02
问题 I have a PreferenceActivity that loads two Fragments via the xml file for the headers. I don't seem to be able to set a tag or an ID. or a tag for the fragments in the header xml (that is loaded using loadHeaderFromResource(); Since I don't instantiate it myself I have no ID. or reference to get hold of it. What do I do? 回答1: I don't think preference fragments loaded via XML are given a tag, and AFAIK they don't have a known ID, so the only way to do this may be to (1) maintain a separate