android-8.0-oreo

Notification Badges in Android O

╄→гoц情女王★ 提交于 2021-02-18 12:00:11
问题 Im testing with Google Nexus 5x with Android Oreo SDK.I cant find Notification Badges in App icon in Homescreen,even i got notification from App And app shortcut is not showing Number.The following is snippet: final NotificationManager mNotific=(NotificationManager)getSystemService(Context.NOTIFICATION_SERVICE); CharSequence name="Ragav"; String desc="this is notific"; int imp=NotificationManager.IMPORTANCE_HIGH; final String ChannelID="my_channel_01"; NotificationChannel mChannel=new

Notification Badges in Android O

安稳与你 提交于 2021-02-18 12:00:06
问题 Im testing with Google Nexus 5x with Android Oreo SDK.I cant find Notification Badges in App icon in Homescreen,even i got notification from App And app shortcut is not showing Number.The following is snippet: final NotificationManager mNotific=(NotificationManager)getSystemService(Context.NOTIFICATION_SERVICE); CharSequence name="Ragav"; String desc="this is notific"; int imp=NotificationManager.IMPORTANCE_HIGH; final String ChannelID="my_channel_01"; NotificationChannel mChannel=new

Getting error “file name must end with .xml” while using the “android:fontFamily” of Android O?

自闭症网瘾萝莉.ら 提交于 2021-02-17 21:15:11
问题 Android O introduces a new feature, Fonts in XML, which lets you use fonts as resources. And I am creating the font folder in resource file as it provided by Android developer, but the problem is that I am getting error that file name must end with .xml while using the font folder which is provided in Android O release. Please check the below layout for it. <TextView android:id="@+id/txtMsgCount" android:layout_width="wrap_content" android:layout_height="16dp" android:background="@drawable

Native Crash tgkill+8 for MediaPlayer (Samsung Oreo 8.0)

会有一股神秘感。 提交于 2021-02-11 12:55:53
问题 We are seeing a weird tgkill native crash for all kinds of Samsung devices with Android Oreo 8.0. #00 pc 000000000006b818 /system/lib64/libc.so (tgkill+8) #01 pc 000000000001df10 /system/lib64/libc.so (abort+88) #02 pc 0000000000007f44 /system/lib64/liblog.so (__android_log_assert+304) #03 pc 0000000000015a94 /system/lib64/libutils.so (_ZN7android6Looper4wakeEv+192) #04 pc 0000000000695368 /system/framework/arm64/boot-framework.oat (android.os.Binder.restoreCallingIdentity [DEDUPED]+152) #05

Notification channel error

陌路散爱 提交于 2021-02-10 14:14:24
问题 I have an app which will recieve FCM notifications.App was recieved notifications on os below Android oreo devices. But notificatons are not recieving in android oreo device.Instead of notification it gets toast "developer warning for package failed to post notification on channel null". I searched and understand that Notification channels are required.But I dont know where it is to be added.Please give me guidance.The toast is appearing on 8.0 emulator.In real device nothing is coming. 回答1:

Notification channel error

可紊 提交于 2021-02-10 14:10:39
问题 I have an app which will recieve FCM notifications.App was recieved notifications on os below Android oreo devices. But notificatons are not recieving in android oreo device.Instead of notification it gets toast "developer warning for package failed to post notification on channel null". I searched and understand that Notification channels are required.But I dont know where it is to be added.Please give me guidance.The toast is appearing on 8.0 emulator.In real device nothing is coming. 回答1:

Android-O launch on secondary display

十年热恋 提交于 2021-02-07 14:29:18
问题 The new ActivityOptions setLaunchDisplayId (int launchDisplayId) function in Android-O seems to always crash my app when I try to launch an activity intent. Both when I launch activities from my own app and when I try to launch other apps i.e. Chrome Canary. Does anyone know if this is a general problem with the new API's or am I missing something: A small snippet of my code is below: options.setLaunchDisplayId(1); startActivity(intent, options); NOTE I was testing with 'simulate a second

Android-O launch on secondary display

岁酱吖の 提交于 2021-02-07 14:26:59
问题 The new ActivityOptions setLaunchDisplayId (int launchDisplayId) function in Android-O seems to always crash my app when I try to launch an activity intent. Both when I launch activities from my own app and when I try to launch other apps i.e. Chrome Canary. Does anyone know if this is a general problem with the new API's or am I missing something: A small snippet of my code is below: options.setLaunchDisplayId(1); startActivity(intent, options); NOTE I was testing with 'simulate a second

Opening android application has delay after clicking on OneSignal notification in android 8

こ雲淡風輕ζ 提交于 2021-02-07 14:22:41
问题 I've added oneSignal library to my android project. Everything goes right except when i click on the received notification from one signal server. it takes about one or two minute to open my android app on my device, but emulator works fine. My device is Galaxy s7 with android 8 and emulator uses android 5. I guess my android version is the issue. maybe new features on android 8 does not allow app to open immediately. Any idea? 回答1: Finally, after a lot of searching, I found the cause.

Opening android application has delay after clicking on OneSignal notification in android 8

本秂侑毒 提交于 2021-02-07 14:21:10
问题 I've added oneSignal library to my android project. Everything goes right except when i click on the received notification from one signal server. it takes about one or two minute to open my android app on my device, but emulator works fine. My device is Galaxy s7 with android 8 and emulator uses android 5. I guess my android version is the issue. maybe new features on android 8 does not allow app to open immediately. Any idea? 回答1: Finally, after a lot of searching, I found the cause.