![]() Mod names are formatted a bit more nicely (e.g.Added actions and shortcuts to increase and decrease priority.Added menu action to refresh load order.Details window width automatically adjusts to the content width.Actions like "show details" or "open folder" now work with multiple selected mods. ![]() Added menu action to open the mod folder directly.Create Mods and DLC directories if they don't exist.Creates Documents/The Witcher 3 directory if it does not exist instead of closing silently.Added a lockfile, so a warning is displayed when more than one instance of the program is opened simultaneously.Additions to ttings are written properly.When there's a config.ini in the current directory, use that path for storing the config files, otherwise store configs in the user documents.Custom ordering for the tree widget so it sorts correctly when ordering by numeric columns.Selected mods stay selected when the list refreshes.Fixed the crashing issue that appeared when trying to disable mods."Change priority" dialogs now have the previous value already filled in.Added search functionality (case-insensitive).Added Installation of mods by drag-and-drop.So I pulled the last playlist from my app database, and started over again with creating the playlist and adjusting track and position to last played from inside OnPrepare call and return. This recreates the service ( OnCreate is hit). User clicks the play icon on notification. But notification somehow sticks around (which it should'nt? But it happens to me). Service is shut down at some point by android system. To resume playing, I manually set the position inside OnPrepare call, by pulling the last track and position from my app database. But the position and the item played is reset. The MediaManager queue will have the playlist. At this point, the MediaManager state is still valid. Later, user decides to click the notification play icon, while another app is in Foreground. User calls MediaManager.Stop() from the app. Not sure if these scenarios are valid if everything is done correctly. This created couple of scenarios that I had to deal with. The android system will decide when it should reclaim memory for service and execute its OnDestroy. The notification stays along with the service. The call to StopSelf() no longer immediately shuts down the service.The notification is expected to stay, and user will have the choice to swipe it out or resume playing. OnCancelled is not called anymore ins API 30 on Media Browser Service.This is explained in a comment on ExoPlayer project. The reason for this issue is API changes in version 30. But can't post the solution here, since my code is intermingled with this library code. Relevant code added to the default blank app is in below two lines, result is shown in screenshot above. The repository is just a basic single page Xamarin.Forms app created with visual studio 2019. Please find sample repository here to reproduce this issue. The notification should disappear as soon as Stop() is called or when app is swiped out. I tried to debug the issue spending most of the time today, but its beyond me. As a result the foreground notification stays along with the foreground media browser service. So, the MediaBrowserService implementation never gets to hit its OnDestroy block in this case. I noted that the media browser service never stops after Stop() call as asserted in this line. I also tried to remove the notification manually by using NotificationManager.ClearAll() but don't have any effect. I started to have this issue since Android update. Not sure if this is a new normal behaviors for Android 11. Ironically, clicking the play icon on the orphaned notification restarts the song again from the first song of the playlist and it works as if the app was relaunched. by force stopping (killing) the app from installed apps => app => settings in android.The only way to make the notification go away is as follows. Even after the app is swiped away with android task switcher, the notification stays. The song stops, but the notification stays with play icon as shown on screenshot below. The notification won't go away when () is called. Samsung S10+ running Android 11 □ Bug Report
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |