android-compatibility

App name in launcher is taken from main Activity label insead of from intent label

北战南征 提交于 2020-06-09 05:26:08
问题 I've set intent filter label as per and per and per official docs: The icon and label that are set in a component's are shown to the user whenever that component is presented as an option to fulfill an intent. By default, this icon is inherited from whichever icon is declared for the parent component (either the or element), but you might want to change the icon for an intent filter if it provides a unique action that you'd like to better indicate in the chooser dialog. For more information,

App name in launcher is taken from main Activity label insead of from intent label

馋奶兔 提交于 2020-06-09 05:24:27
问题 I've set intent filter label as per and per and per official docs: The icon and label that are set in a component's are shown to the user whenever that component is presented as an option to fulfill an intent. By default, this icon is inherited from whichever icon is declared for the parent component (either the or element), but you might want to change the icon for an intent filter if it provides a unique action that you'd like to better indicate in the chooser dialog. For more information,

Change Google Places picker Action bar color

杀马特。学长 韩版系。学妹 提交于 2020-01-17 13:09:45
问题 Good morning, i am quite new in Android and i have a problem setting the color of the built-in action bar in Google Places Picker. The documentation of this one clearly says that the action bar color inherits the matherial theme style of the project. The problem is that i have Theme.AppCompat.Light.NoActionBar and the color of this style isn't passed to the Google Place Picker because it uses only the colors of material themes. I would like to ask if it's somehow possible to replace Theme

Is checking SDK_INT enough or is lazy loading needed for using newer android APIs ? Why?

南笙酒味 提交于 2020-01-09 11:26:12
问题 Code such as : if (android.os.Build.VERSION.SDK_INT >= Build.VERSION_CODES.GINGERBREAD) ed.apply(); else ed.commit(); produces a warning in Froyo : 04-27 03:40:35.025: W/dalvikvm(3138): VFY: unable to resolve interface method 219: Landroid/content/SharedPreferences$Editor;.apply ()V But I understand that in older devices this would be a RuntimeError which would abort the application (see here and here). So is this way of conditionally calling new API (methods) safe in API 8 (Froyo) and above

Is checking SDK_INT enough or is lazy loading needed for using newer android APIs ? Why?

半世苍凉 提交于 2020-01-09 11:25:28
问题 Code such as : if (android.os.Build.VERSION.SDK_INT >= Build.VERSION_CODES.GINGERBREAD) ed.apply(); else ed.commit(); produces a warning in Froyo : 04-27 03:40:35.025: W/dalvikvm(3138): VFY: unable to resolve interface method 219: Landroid/content/SharedPreferences$Editor;.apply ()V But I understand that in older devices this would be a RuntimeError which would abort the application (see here and here). So is this way of conditionally calling new API (methods) safe in API 8 (Froyo) and above

Android accessibility service backwards compatibility and jelly bean

不想你离开。 提交于 2020-01-03 02:19:07
问题 I've got an app that uses the accessibility service to monitor for events. It's always worked fine in versions of android up to ICS, but with Jelly bean I'm not having much luck. As the documents mention I've added android:permission="android.permission.BIND_ACCESSIBILITY_SERVICE" to my service in the manifest file. This causes the app to work fine using the declarative xml method for the xml. The problem is on backwards compatibility. For versions such as gingerbread I'm now getting the

My App isn't Compatible with Nexus 7 on Google Playstore

不羁岁月 提交于 2020-01-01 09:44:34
问题 Hii i have submitted an app to playstore but it isn't compatible with Nexus here is my Manifest My App is on List of supported Devices in the Google Play and when i check the same in the nexus device it is not at all visible on Search <uses-sdk android:minSdkVersion="14" android:targetSdkVersion="14"/> <supports-screens android:anyDensity="true" android:largeScreens="true" android:normalScreens="true" android:resizeable="true" android:smallScreens="true" android:xlargeScreens="true" /> <uses

Gradle conflict when using admob 15.0.0 with the lastest support library

只愿长相守 提交于 2020-01-01 09:17:26
问题 I am using 'com.google.android.gms:play-services-ads:12.0.1'. and android support version 27.1.1. when I try to upgrade my ads library to the latest (15.0.0) I get an error saying that I must use the same version specification. See image below. Is there a way to use the latest version for both the supportLibraries and the play-services-ads ? Note that this problem does not exist when i use the play-services-ads version 12.0.1 回答1: You can try overriding the conflicted support library by

How to get “?android:attr/actionBarSize” with Compatibility Library

扶醉桌前 提交于 2020-01-01 04:58:08
问题 I'm trying to use Fragments and ActionBar in a Android 2.2 project. There is some error when using "?android:attr/actionBarSize", how to get and set that value correctly? Example: <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:orientation="horizontal" android:layout_width="match_parent" android:layout_height="match_parent" android:id="@+id/frags"> <fragment class="com.example.android.hcgallery.TitlesFragment" android:id="@+id/frag_title" android:visibility=

ObjectAnimator in API Level < 11

瘦欲@ 提交于 2019-12-31 17:50:18
问题 So I'm getting really frustrated with android and the fact half the stuff doesn't work when you roll back the API Level past 11. Why isn't it easy and well done like iOS?! The Problem I am using ObjectAnimators to animate the transitioning between Fragments . They work fine in anything with API Level 11 and above. As soon as I change the build target to less than 11 I get problems with it saying it can't found the resource identifiers for attributes such as propertyName and valueType in the