Wakelock and Vibrate permission on Android?

[datvm]

Per documentation:

[assembly: UsesPermission(Manifest.Permission.WakeLock)]

//Required so that the plugin can reschedule notifications upon a reboot
[assembly: UsesPermission(Manifest.Permission.ReceiveBootCompleted)]
[assembly: UsesPermission(Manifest.Permission.Vibrate)]
[assembly: UsesPermission("android.permission.POST_NOTIFICATIONS")]

//Optional (only for Calendar and alarm clock apps)
[assembly: UsesPermission("android.permission.USE_EXACT_ALARM")]
[assembly: UsesPermission("android.permission.SCHEDULE_EXACT_ALARM")]

Is there any reason why Wakelock and Vibrate are needed? The only usage I can see is here and I assume it's deprecated. Should the doc be updated there?

[thudugala]

@datvm

// Required so that the plugin can schedule
[assembly: UsesPermission(Manifest.Permission.WakeLock)]

[assembly: UsesPermission(Manifest.Permission.Vibrate)] is needed as Minimum permissions (

Plugin.LocalNotification/Source/Plugin.LocalNotification/AndroidOption/NotificationChannelRequest.cs

Line 64 in a757eac

public long[] VibrationPattern { get; set; } = [];

)

[datvm]

Darn I didn't know WakeLock is needed for the scheduling, no wonder I didn't see any scheduled notification on Android (works great on iOS btw). As for Vibrate, do I need that even if I don't use or care if it vibrates or not?