android-7.0-nougat

I have this warning message in Samsung S8+ Android 7: APP_NAME does not support the current Display size setting and may behave unexpectedly. What it means and how can I remove it? Thank you Solved by adding in supports-screens android:xlargeScreens="true" and removing: android:requiresSmallestWidthDp="600" So you need to create different folders and maintain all xml in those folders. The following is a list of resource directories in an application that provides different layout designs for different screen sizes and different bitmap drawables for medium, high, and extra high density screens.

How can we give separate layout or separate activity for Multiple window ? eg. I have checked below things with help of android developer site <activity android:name="com.configure.it.MyScreen"> <layout android:defaultHeight="400dp" android:defaultWidth="200dp" android:gravity="top|end" android:minimalSize="300dp" /> </activity> by declaring above things it affect how an activity behaves in multi-window mode. But how can I show different layout if my particular screen is activated on Multiple-Window ? From the Android Developer link . To make changes in UI or separate layout which should be

As per the documentation in Language and Locale there have been improvements to Resource-Resolution Strategy from Android 7.0(API level 24) which is easy to understand with the following table: Improved Resource-Resolution strategy As per my requirements, I want my app's default langauge to be en_US. So, I am not providing separate resources for en_US. I also have en_GB resources present separately. Now, as per the resolution strategy, if my device's language is en_US then the order in which it should look for resources is en_US -> en -> en_GB -> default which means for all locales of en, in

I have an existing app that makes use of ViewPager and PagerTabStrip and this has been working for a long time with various releases of the Android SDK and the com.android.support:appcompat-v7 library. I've just bumped up the compile and target SDK versions of my app from 23 to 24 and the com.android.support:appcompat-v7 library version from 23.4.0 to 24.0.0 ... and I now see that the PagerTabStrip is totally missing from the ViewPager . (Not just missing titles in the PagerTabStrip ... the PagerTabStrip is totally missing from the ViewPager when the views are rendered.) This is how I'm

I am using the below snippet to generate notifications in my android app. private void sendNotification(String contentText, String message) { Intent resultIntent = new Intent(this, MainActivity.class); resultIntent.putExtra("clear","clear"); resultIntent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK); PendingIntent piResult = PendingIntent.getActivity(this, 0, resultIntent,0); NotificationCompat.Builder builder=new NotificationCompat.Builder(this) .setSmallIcon(R.drawable.icon) .setColor(ContextCompat.getColor(getApplicationContext(),R.color.red)) .setContentTitle(

I'm catching this fatal exception when I try to pass an Serializable inside an Intent bundle, and I think is related with the nougat shortcuts that I'm trying to implement. here the exception: 12-16 16:17:32.972 20461-20461/***.****.******.debug E/AndroidRuntime: FATAL EXCEPTION: main Process: ***.****.******.debug, PID: 20461 java.lang.IllegalArgumentException: Bad value in PersistableBundle key=shortcutId value=***.****.******.common.cta.CtaAccountSectionModel@1fb70dc at android.os.PersistableBundle.<init>(PersistableBundle.java:124) at android.os.PersistableBundle.<init>(PersistableBundle

According to Google's introduction , starting with Android N, the Android API is supposed to support Java streams. However, using the Android N preview SDK, I am unable to use any of the Stream APIs in my project (which is configured with Android N as minimum, target and build SDK version). The java.util.stream package seems to be missing, as are the stream() methods of all collection implementations I've tried. Are the necessary classes not yet included in the current preview release of the SDK? It's not yet in the current preview, but it has already been merged into the AOSP Git master. See