android-8.0-oreo

问题 I am currently working on transitioning an application to Android O, and I am currently working on notification channels. I have made different channels with different importance levels and since the application has a foreground service that has to run at all times until we transition to a new architecture (more push oriented), I thought about putting that notification in a channel that has its importance set as IMPORTANCE_MIN , so that it is there, but it doesn't bother the user, and doesn't

问题 I am currently working on transitioning an application to Android O, and I am currently working on notification channels. I have made different channels with different importance levels and since the application has a foreground service that has to run at all times until we transition to a new architecture (more push oriented), I thought about putting that notification in a channel that has its importance set as IMPORTANCE_MIN , so that it is there, but it doesn't bother the user, and doesn't

问题 I am currently working on transitioning an application to Android O, and I am currently working on notification channels. I have made different channels with different importance levels and since the application has a foreground service that has to run at all times until we transition to a new architecture (more push oriented), I thought about putting that notification in a channel that has its importance set as IMPORTANCE_MIN , so that it is there, but it doesn't bother the user, and doesn't

问题 I read in the docs that Context.startForegroundService() has an implicit promise that the started service will call startForeground() . However, since Android O is coming out with changes to background and foreground services, are there any other performance improvements that it has compared to using the older startService() method, or is it just best practice going forward? 回答1: It's about neither performance improvements, nor benefits, nor best practice. Starting from API 26, system just

问题 I created an app initially using Pie sdk And it worked on Pie devices Now I want it to run on Nougat and Oreo as well How to do it I am attaching the log as well as the app level Gradle after changing the sdk version to 26 APP LEVEL GRADLE apply plugin: 'com.android.application' apply plugin: 'com.google.gms.google-services' android { compileSdkVersion 26 defaultConfig { applicationId "com.divyateja.waviour" minSdkVersion 15 targetSdkVersion 26 versionCode 1 versionName "1.0"

问题 I find myself confused with the new background limitations and am just looking for some clarity here... With the app in the foreground OR in the background with a foreground service running, background services are good to go. I got this. With the app in the background and without a foreground service, the background service is stopped by the system. I'm cool with this as well. My question: The app can still obtain limited location updates per hour but how ? Where do you create the request so

问题 I am currently using the startWakefulService function which is crashing in Oreo. I realise I either have to switch to startForegroundService() and use a foreground service, or switch to JobIntentService but based on my code below I am not sure what to do. (Sorry I am an android novice). Any points in the right direction will be greatly appreciated. public class GcmBroadcastReceiver extends WakefulBroadcastReceiver { @Override public void onReceive(Context context, Intent intent) { //

问题 I have FileObserver in my application, now it runs on the background and if new file registered - instantiate uploading of it to some server in foreground service. In Android O we should use FirebaseJob Dispatcher to do some job in background, but how could we apply it for FileObserver ? Is there any way to analyze data in background? Or maybe it's fail to use FileObserver since now? 回答1: but how could we apply it for FileObserver? You can't. Is there any way to analyze data in background?

问题 In my application, I can receive android.intent.action.PHONE_STATE but can't receive Intent.ACTION_NEW_OUTGOING_CALL on android O . If I use android N or android M everything work fine. I have register first broadcast in AndroidManifest file and second in foreground service , but none of them can receive Intent.ACTION_NEW_OUTGOING_CALL , only can receive android.intent.action.PHONE_STATE . If anyone know how to fix it, please post your answer, thanks in advance. 回答1: But I am still confused,

问题 In my application, I can receive android.intent.action.PHONE_STATE but can't receive Intent.ACTION_NEW_OUTGOING_CALL on android O . If I use android N or android M everything work fine. I have register first broadcast in AndroidManifest file and second in foreground service , but none of them can receive Intent.ACTION_NEW_OUTGOING_CALL , only can receive android.intent.action.PHONE_STATE . If anyone know how to fix it, please post your answer, thanks in advance. 回答1: But I am still confused,