-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v21.0 causing infinite Guru Meditation crash loop #6012
Comments
It should be present by default; the only thing that could possibly have caused it to not be shown on your device is if somebody messed with NewPipe's settings on your phones. It's possible to add it again by going to "Settings > Content > Content of main page," pressing on the plus button, and choosing "Default Kiosk." Regarding the infinite loop, this could be related to #5977; do you live in the EU? If so, can you see if the problem is fixed in the APK provided here? Also, can you try downgrading to 0.20.11 and see if the issue is present there? |
Also, to clear up a misunderstanding you seem to have, 0.21 is indeed a beta release, but so is every previous single release of NewPipe. That's why it's 0.21 with a zero. |
Ok, re: Beta. I was not aware of the numbering convention. Trending: I am the only user of my phone so I don't think anyone changed my settings but it is definitely possible that I changed something without realizing it. EU: No, I am not in the EU but now that you mention it I do use a VPN and use EU servers as part of my "rotation". I am pretty sure I have had the problem while using non-EU servers (Canada, US, etc.) but will need to investigate this. It didn't occur to me that this could be a problem so I did not try disabling the VPN. I will also downgrade to 0.20.11 as you suggested and test it in conjunction with the VPN tests. Thanks for the suggestions. I will report what I find. |
@OldGuyInTheClub Can you also capture logs with a computer with ADB and developer options in your phone settings? |
Thanks for the step-by-step instructions. I had not heard of ADB. If the problem persists after the prior tips on location/downgrading, etc. I will see if I can capture some logs. |
@OldGuyInTheClub Please try to capture logs from 0.21.0 version. |
Update: Completely uninstalled v21.0 via help from the IRC channel. Installed v20.11: No crashes over the past couple of days. Works with the VPN reenabled, as well and I have access to comments and other features. I use Newpipe intensively mostly on weekends so these are preliminary observations. If v20.11 continues like this, I am in good shape. |
V.20.11 has worked well for me. This solves my problem. Thanks for the help. |
Even if 0.20.11 works, changes in YouTube will eventually break it and you will have to update to a later version, so I believe this issue should stay open. |
Ok. I'll try the latest version and see if any of the prior troubleshooting steps like full deleting/installing make a difference. Always a chance something is amiss with my phone. |
For reference, v21.1 has the same issue on my phone:
Both times I was not actively using the app but had it open in the background. When I went into the app, it crashed and required reboot. Force Stop did not work. |
We cannot solve this issue until you can capture logs and send the logs. Can you please try to get logs? Thanks! |
I'll try to implement ADB and report back. |
Unfortunately, adb devices returns a blank line. Additionally, my phone goes into an infinite "USB debugging connected: Tap to turn off in settings" and "File transfer: Tap to change USB options" loop. Keeps beeping and putting up notifications. Maybe this is related to the underlying problem with Newpipe v21.x. Probably something wrong with my phone and not Newpipe. |
You can have some problem with drivers on your computer, especially on Windows (I had this problem). If you are on this system, try opening the Device Manager (right-click on the Start menu). If there is a problem with an unknown USB Driver which isn't another driver than what you think be your phone, try updating the non-working driver with the USB MTP Device (you need to search in the list of drivers, USB drivers). You can find more on the Internet. |
I am on a Mac. I found some threads and got drivers/software from LG's site but the software requires Catalina (10.15) and I am on Mojave (10.14.6). Sorry but this is at the limits of my abilities. I'll use v20.11 as long as it lasts and hope for the best with future Newpipe releases. Thank you for the help. |
Oh ok, I'm sorry. However, can you reproduce the bug with the 0.21.2 version in development (#6052)? |
Sure. I will give it a try and report back. |
v0.21.2 development also crashed but I think I may be seeing a pattern for at least some of the crashes. Cellular reception in/near my house isn't great although I am supposedly in a strong coverage area. I use wifi in the house but when I leave, there can be a gap between when wifi cuts off and the cellular data network cuts in. On some of those occasions (but not all), I've noticed Newpipe v0.21.x crashing. Again, it doesn't happen all of the time which makes systematic checking difficult. I can't guarantee that this is the cause of all the crashes, either but there is a correlation worth noting. Because of spotty cellular data service (US Sprint in limbo to T-Mobile but still a Sprint SIM card), I keep "Cellular data always active" enabled in Developer Options, otherwise I can be without cellular data for long stretches when wifi disconnects. Even then I periodically need to go in and out of airplane mode to force reconnection. Could this flaky connection be an issue with v0.21.x but not with earlier versions? I will try disabling "Cellular data always active" and see what happens but wanted to mention the possibility. Update: Inclined to think there's something wrong with my phone since I am the only one experiencing this. Reverted to v20.11 |
A couple of weeks ago my cell ISP pushed an update that improved a lot of connection problems with their data network. This is across all applications, not just NewPipe. I tried v21.8 and it has been stable for over a week. Per a prior comment, I think this issue is phone related due to the unstable connection and not a problem with the NewPipe app. |
Great that you found out the problem 👍 I think we can close the issue if there are no further problems regarding this topic. |
Checklist
Steps to reproduce the bug
Actual behaviour
LG V20: Android 8.0.0
Updated Newpipe per a Newpipe notification about ten days ago. System has been unstable ever since.
After a few minutes of use, I will get the "Guru Meditation" error page for ~2 seconds, it will disappear, and then reappear in an endless loop on top of any other applications. The only solution is a full reboot of the phone. I can try it again and the error will come back but the time to get to the error will vary from one to many minutes.
Expected behavior
Newpipe has been very stable up to this point and I simply accept new updates. But, upon checking it seems 21.0 is in beta?
https://newpipe.net/blog/pinned/release/newpipe-0.21.0-released/ indicates it is a full release but
https://github.com/TeamNewPipe/NewPipe says the latest is still in beta and to file a bug report if there are problems, hence this message.
Additional observations:
The Newpipe icon will blink on the top icon panel of the phone as the error comes and goes.
On the lock screen, the Newpipe ribbon is gray and the hourglass indication appears.
I no longer have a Trending icon as shown in
https://github.com/TeamNewPipe/NewPipe/blob/dev/fastlane/metadata/android/en-US/images/phoneScreenshots/shot_01.png
I can't find any way to break out of the loop other than rebooting the phone. e.g. Closing all running apps does not stop the Newpipe error loop
Steps I have taken:
I can downgrade to any recommended version. So long as I can watch videos and access playlists, I can live without comments and other features.
Thanks,
The Old Guy in the Club
Screenshots/Screen recordings
Can't capture anything due to infinite Guru Meditation loop.
Logs
Don't see any applicable logs but I don't know where to look, either. Again, infinite loop makes this hard to pin down.
Device info
The text was updated successfully, but these errors were encountered: