android-8.0-oreo

Android O HIDL not available

徘徊边缘 提交于 2019-12-05 07:24:33
I have problem with Android O HIDL. The failure log shows it can't find out the service. However I can see it by adb shell ps -A | grep fingerprint system 18758 1 17408 3276 pipe_wait 7c79e93e08 R android.hardware.biometrics.fingerprint@2.1-service` Could anyone give me a hint how to solve the problem? I checked https://source.android.com/devices/architecture/hidl/ but could not get the solution. Error log: 08-21 06:00:35.864 1890 2264 V FingerprintService: mDeamon was null, reconnect to fingerprint 08-21 06:00:35.864 1890 2264 I system_server: Looking for service android.hardware.biometrics

How to detect a Notification Channel is blocked by user in Android 8.0

人盡茶涼 提交于 2019-12-05 06:31:13
Is there any callback my application receives when user blocks a Notification Channel created by my application OR it can be detected later ? No, there is no such listener provided by the APIs. You will have to check each time before you make a notification. From the developer document To find out if a user blocked a notification channel, you can call getImportance(). If the notification channel is blocked, getImportance() returns IMPORTANCE_NONE. rockgecko Starting from Android P, there is a system broadcast for this: https://developer.android.com/reference/android/app/NotificationManager

Same ANDROID_ID in Oreo

一世执手 提交于 2019-12-05 03:55:05
As per Android 8.0 Behavior Changes , For apps installed on a device running Android 8.0, the value of ANDROID_ID is now scoped per app signing key, as well as per user. The value of ANDROID_ID is unique for each combination of app-signing key, user, and device. As a result, apps with different signing keys running on the same device no longer see the same Android ID (even for the same user). To test above changes, I made two test APK and found below behavior (tested on Nexus 5X, OS 8.0.0): In case when targetSdkVersion 26, compileSdkVersion 26, buildToolsVersion 26.0.0, The two different apk

Correct way to create Notification Channels from Android O Api

﹥>﹥吖頭↗ 提交于 2019-12-05 03:38:31
The notification channels which introduced from Android O (API 26) version.I read about it from the following links: Managing notification channels Google Sample for Creating Channel Questions: If I have multiple numbers of notification then Is it a good idea to create notification channels when the application starts and keep it at ApplicationScope ? public void addNotificationChannels(Context context) { List<NotificationChannel> channels = new ArrayList<>(); channels.add("channel_1"); channels.add("channel_2"); . . channels.add("channel_7"); NotificationManager notificationManager =

Font in XML with Android O

非 Y 不嫁゛ 提交于 2019-12-05 03:19:54
Android O give font directory with new android-studio version 3.0 but when in drop font-file in font directory and run project it give me a error in font file in font directory. Error:Execution failed for task ':app:mergeDebugResources'. /home/ttuser4/Downloads/fontPractice/app/src/main/res/font/Dancing_Script.ttf: Error: The file name must end with .xml I also got the similar issue. To fix that i followed the below steps. Updated Android Studio to latest canary build. Change distributionUrl in project-dir/gradle/gradle-wrapper.properties to latest gradle distribution url(You can get the

Android Notification Not Showing On API 26

坚强是说给别人听的谎言 提交于 2019-12-05 03:09:51
I recently updated my app to API 26, and notifications are no longer working, without even changing the code. val notification = NotificationCompat.Builder(this) .setSmallIcon(R.drawable.ic_notification) .setContentTitle("Title") .setContentText("Text") .build() (getSystemService(Context.NOTIFICATION_SERVICE) as NotificationManager).notify(1, notification) Why isn't it working? Was there some change to the API that I'm not aware of? From the documentation : Android O introduces notification channels to provide a unified system to help users manage notifications. When you target Android O, you

No response received in startscan method at WifiManager in Android 8 Oreo

旧时模样 提交于 2019-12-05 01:30:18
问题 According to official Android documentation, the method startScan at WifiManager is deprecated in API level P. However I am trying to use this method in API level 26 (previous to P) without success. I have developped an app which requires the scanning of the WiFi networks, if the user agree with the required permissions, and this behaviour is paramount for the appropriate functioning of the app. However I do not receive any response when calling the startScan method. ¿Can anyone help me to

JobScheduler behaviour on Android O

跟風遠走 提交于 2019-12-04 18:04:15
According to the documentation , as of Android O services will be stopped several minutes after the app is no longer in the foreground. The documentation suggests most services can be replaced with JobScheduler jobs. My question is - do jobs have any kind of special behavior as well, or do they behave the same as services pre-Android O? Can they live "forever" (as long as the system doesn't need the memory, of course), or do the system also kills them off at the end of a certain window? CommonsWare Can they live "forever" (as long as the system doesn't need the memory, of course), or do the

Notification android on foreground not displayed (Oreo)

丶灬走出姿态 提交于 2019-12-04 17:53:46
I'm trying to display an notification with firebase when the app is in the foreground . The onMessageReceived method is called when I push the notification from the server, but the notification is not displayed . Here my code : public class MyFirebaseMessagingService extends FirebaseMessagingService { @Override public void onMessageReceived(final RemoteMessage remoteMessage) { Timber.d("FCM-From: " + remoteMessage.getFrom()); new Handler(Looper.getMainLooper()).post(new Runnable() { public void run() { if (remoteMessage.getNotification() != null) { Timber.d("FCM-Message Notification Body: " +

Oreo (API 26) - drawOverlay + draw over status bar

ぃ、小莉子 提交于 2019-12-04 16:25:47
问题 In android oreo, I can't use WindowManager.LayoutParams.TYPE_SYSTEM_ERROR anymore and must use WindowManager.LayoutParams.TYPE_APPLICATION_OVERLAY instead. The drawback is, that this mode does not draw over the statusbar. Is there anyway to achieve the old behaviour and be able to draw over the statusbar as well? I've a sidebar app and until now, I allowed the user to have trigger areas on top of the screen as well, which does not work anymore now, because the status bar is overlapping the