android-3.0-honeycomb

I'm trying to implement a CalendarView , it takes an absurd amount of time (about 10 seconds) to appear on screen and it only loads the month and weekday headers, it does not display any calendar content. Using the same code from this video but not seeing the same result. I'm trying to launch it in a dialog: CalendarView calendarView = new CalendarView(this); dialog.setContentView(calendarView); but when I tried to embed it in an activity it took the screen the same amount of time to load and similarly failed to display correctly. The tracing helped reveal that GregorianCalendar was being

I have a ListView that normally is the singleChoice choiceMode . When the user long presses on an item, I want to enter an action mode that allows selecting multiple items so they can perform an action on any selected items. I am able to configure the ListView so that it is in singleChoice mode and the user is able to select list items to display a details fragment next to it and have the list item itself shown in its activated state. I am also able to configure the ListView so that it is in the multipleChoiceModal choiceMode and performing a long press on an item starts the action mode and

I am trying to get my app to be backward compatible so i need to show the menu button since we used the menu button in our app on previous versions. So I was reading and it says that if your target is 11 (3.0) than you don't get the menu button but it your target is 10 they you do. But the issue is I am using fragments so my target has to be 11. Any thoughts. Ordinary options menus will appear regardless of Android version. If you have: android:targetSdkVersion="11" then the options menu will appear in the action bar on Android 3.0+ devices. All items in the options menu will be available when

I have created an AppWidget for Honeycomb which is working well, except that when first installed, it does not show up in the Widgets menu so it can not be added to a home screen. Rebooting the device will allow it to show up, or during development, sending it twice from Eclipse will cause it to show up. Any ideas? Thanks! Appearently EboMike was right, setting android:installLocation="internalOnly" did fix the issue. Without specifying an install location, it should have defaulted to internalOnly, but did not seem to for me. Perhaps something changed in Honeycomb? Also, even with internalOnly

I want to develop an android application using Honey Comb 3.0 in which I want to display a list , clicking on any item in a list should display another list beside that list item in the form of Fragment. Can any one provide me sample code in sorting out this issue? Thanks in Advance, Ollie C Have a look at these two blog posts from Google's Reto Meier: http://blog.radioactiveyak.com/2011/02/android-app-surgery-earthquake-redux.html http://blog.radioactiveyak.com/2011/02/strategies-for-honeycomb-and-backwards.html He has lots of code examples in there for handling fragments. 来源： https:/