android-3.0-honeycomb

My app has several fragments and activities. Over the course of the main parent activity's lifecycle, the app presents information/options to the user in other activities. The documentation for Fragments has the following stipulation for commit(): Caution: You can commit a transaction using commit() only prior to the activity saving its state (when the user leaves the activity). If you attempt to commit after that point, an exception will be thrown. This is because the state after the commit can be lost if the activity needs to be restored. For situations in which its okay that you lose the

I'm trying to update location data to a web database using BroadcastReceiver and Service . However I am having difficulties making it to work with Android 3.2 on a Galaxy Tab 7.0 Plus. The same application is working very well on a Android 2.3.6 Galaxy Note, but it doesn't run on the tablet. In fact, I add the RECEIVE_BOOT intent action to my receiver, but it never gets instantiated, that is, o nReceive() never gets called after boot completes. I wonder if there are any updates to the system that cause this action. Here is my xml and receiver classes: AndroidManifest.xml <manifest xmlns

I know that before API 10 of Android, it was important to call recycle() for Bitmap s that aren't used anymore, since the actual raw data is stored in the native memory. However, as of API 11, Bitmap s are stored in the heap, so my question is: Is it still needed to call recycle() on Bitmap s if the API is large enough (at least 11)? What does it do if I call it on such API? s0nicYouth Official documentation tells that recycle() now is an advanced call so if you want to free your bitmap you can just write something like bitmap = null and GC will take care of everything else. 来源： https:/

I'm implementing n-layer PreferenceActivities 1st layer PreferenceActivity is loaded from preference-headers. First header creates fragment of settings which is a PreferenceFragment. Second is a browser activity (2nd is an example from developer.android.com) which opens specified Url. The third one I want to be a next level of PreferenceAtivity that also will be loaded from preference-headers. First two work fine but 3rd is crashing an app with the exception: "android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=com.mycompany.myapp

My manifest setup: targetSdkVersion=11 I have Activity with theme set to android:style/Theme.Holo.NoActionBar or android:style/Theme.NoTitleBar Desired result: app that doesn't show top bar (action bar or title bar), and has menu. I want almost full screen (video player or image viewer) possibly with dimmed status bar. Problem is that in such combination, there's no way to push menu button, because there's no Menu button shown. If targetSdkVersion is <11, then there's legacy Menu button at bottom bar, which I would expect to be there if I choose to hide Action bar. There's no hardware menu

Am getting Error inflating fragment error while running calling an Activity which having fragments. CheckList is Activity which contains listview and Description fragments. and its xml code is: <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:orientation="horizontal" android:layout_width="match_parent" android:layout_height="match_parent"> <fragment class="com.uday.honeytest.CheckList$listview" android:id="@+id/titles" android:layout_weight="1" android:layout_width="0px" android:layout_height="match_parent" /> <fragment class="com.uday.honeytest.CheckList