App crash SystemUI because of Tubular notification
Checklist
- [x] I am able to reproduce the bug with the latest version.
- [x] I am not able to reproduce the bug with the latest version of vanilla NewPipe.
- [x] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
- [x] I have read the FAQ and my problem isn't listed.
- [x] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- [x] This issue contains only one bug.
- [x] I have read and understood the vanilla NewPipe contribution guidelines.
Affected version
0.27.7
Steps to reproduce the bug
1.click tô play THE vídeo THE interface on Nokia cellphones crash totally ,have tô testar the cellphone
Expected behavior
No response
Actual behavior
No response
Screenshots/Recordings
No response
Logs
No response
Affected Android/Custom ROM version
No response
Affected device model
No response
Additional information
No response
I appear to have also be experiencing the issue, though since OP has not provided much details, I can't be sure, though the symptoms appear the same. Specifically SystemUI crashes while a video is loading, for me in some cases this appears to make tubular not able to load the video, causing a crash loop requiring the device to be rebooted, in others there is a singular crash during which tubular does manage to load the video, thus allowing the device to be used without rebooting. I have tested NewPipe and I have not been able to experience the issue, though I havent tried that hard, since the issue is rather common on Tubular.
I'm using:
- tubular 0.27.7
- a motorola e22
- android 12L, seemingly close to but not quite AOSP? the build number (if it gives any info) is
SOV32.121-56-47(which does not match the build number conventions used by android so idk, the Baseband version isMOLY.LR12A.R3.MP.V222.P32,MOLY.LR12A.MP.V222.P32)
The SystemUI crashlog
FATAL EXCEPTION: SysUiBg
Process: com.android.systemui, PID: 17115
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.media.MediaMetadata.getString(java.lang.String)' on a null object reference
at com.android.systemui.media.MediaDataManager.loadMediaDataInBg(MediaDataManager.kt:577)
at com.android.systemui.media.MediaDataManager.access$loadMediaDataInBg(MediaDataManager.kt:105)
at com.android.systemui.media.MediaDataManager$loadMediaData$1.run(MediaDataManager.kt:345)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.os.HandlerThread.run(HandlerThread.java:67)
~~This issue, at least on my device, appears to be fixed on androids side by 55e80e8 (5 years ago btw)~~
edit: ~~before that commit there was a separate check above where the exception happens? I'm not sure if thats the case then or maybe the OEM tried to "fix" the same issue by removing the check??~~ this commit is also from before android 12 so nope
a workaround on the user end is to disable the "Tubular notification" notification category (Settings>Apps>Tubular>Notifications, set the toggle next to "Tubular notification" to off).
@MinekPo1 Is disabling Tubular notification category completely solve the problem? If yes, probably there is a bug in notification system
@MinekPo1 Is disabling Tubular notification category completely solve the problem? If yes, probably there is a bug in notification system
i have not experienced this issue since I disabled those notifications, yes.