RemoteView | Android 悬浮窗，视频通话缩放最小 | Android library

It creates a new Media Player because the class is recreated or re-executed. This clears all the variables and re-defines them. This makes the issue in your case.

1. Just create a class name anything like MediaPlayerHelper.java

2. Create a variable of MediaPlayer which is public and static. Like this:

You need to use two distinct, up-to-date PendingIntent objects, wrapped around different Intent objects (e.g., ones with differing extras).

For "distinct", you need the IDs of the PendingIntent objects to be different. The ID is the second parameter to the PendingIntent.getBroadcast() call.

For "up-to-date", you need to update any existing PendingIntent that your code might have created previously. For that, pass PendingIntent.FLAG_UPDATE_CURRENT as the fourth parameter to the PendingIntent.getBroadcast() call.

In order flutter widgets to work there should be a flutter virtual machine working. In remote view there is no such possibility because it is run by the Android system and it does not know about flutter. Moreover even not all the android native widgets can be rendered as remote view.

There are some options you can do here though:

• If your flutter vm is active you can rasterise the flutter widget and show it in the ImageView inside the remote view. It won't be interactive though. You can combine it with some android native buttons.
• Use service with ui - in theory it can render flutter view but it is hard to achieve since it is hardly possible to show fragment outside of activity.
• Make all the logic needed in flutter and via platform channels pass the data to and from the native implementation. Platform channels only work when the main thread of the app works.
• Implement all the stuff as android navite and don't bother with flutter because flutter is meant for cross platform and all the previous stuff would not work on iOs hence the point of flutter is absent in this case.

You are correct, appWidgetManager.updateAppWidget() should be called just once.

You need to apply all changes to the same RemoteViews instance, so it should be:

In you NotificationBuilder you need to set notification category to NotificationCompat.CATEGORY_CALL and style to NotificationCompat.BigTextStyle() like this

I have found the solution : it was in styles.xml (V31) : I introduced this item

As per the documentation, not all layouts and widgets are supported by RemoteViews. Your AppCompatTextView is causing the issue. Replace it with a simple TextView.

Also,

Beware that the background color for the notification can vary across different devices and versions. So you should always apply support library styles such as TextAppearance_Compat_Notification for the text and TextAppearance_Compat_Notification_Title for the title in your custom layout. These styles adapt to the color variations so you don't end up with black-on-black or white-on-white text.

Documentation:

• https://developer.android.com/training/notify-user/build-notification
• https://developer.android.com/reference/android/widget/RemoteViews

Turns out that is Android 12 bug. It was fixed in Android 12L.

https://issuetracker.google.com/issues/205749786

If an app is killed by e.g. the user force-stopping, all of the services, activities, notifications, and PendingIntents from the app are cancelled. You'll only have an opportunity to recover the next time your app runs (from activity launching, receiving broadcast, etc).

This is why the system warns the user that apps may not behave properly if force-stopped.