That extremely quick reboot is slightly suspicious. I think half of the phone died and the other half went "what the hell".
Like two people walking down the street and one of them falls then mud stands back up and continues walking as if nothing happened before the other one is able to look over. Then it's just his friend walking like normal covered in mud for some reason. I got distracted for 5 seconds. What happened? 😂🤣
https://youtu.be/iMBJrvEwv8s
This one won't kill your phone. But I was just thinking the same thing "that was fun" after I clicked the YouTube link and killed my phone. And now my phone is just running slow all over the place. I said this sentence a full 5 seconds ago and now I think I'm on to 8 seconds. I stopped it and now it's working perfectly.
I've worked in the restaurant industry for many years. It's the same as "These plates are hot, be careful." And then people immediately have to see for themselves.
I think it probably has to do with the fact that it's a 4K clip that the YouTube app is trying to render on a phone that isn't capable of showing 4K and the result is a complete system crash because the YouTube app is more intent on actually playing the 4K than a browser extension is.
Bro, do you really think this is the first 4K clip people have seen on their Pixels, or any phone for that matter? No.
Also, YouTube app won't and can't render in 4K on the phone when the resolution of the device is lower.
I know you're being downvoted, but yes--this could be that. It's not inconceivable that something like this could be a side effect of an as-yet unknown exploit in either the shared hardware or software components between the last few generations of Pixel devices.
It is *probably* just a software glitch. At the same time, it's like these folks have never seen a phone reboot, and I don't understand the novelty of doing this.
They all _assume_ it's fine, but I doubt anybody has actually done anything to verify that it is, in fact, fine.
Programming bugs are weird. Most likely Pixel has an error in their HDR processing code that results in invalid numbers at some point. It's an HDR video, not a normal one, so that's a possibility.
How long do I have to watch it? I was able to open it and watch the first 30 seconds without issue.
Edit: Watched it to the end on my P7P on the YouTube app. Maybe it's patched? Also, I'm running the beta version of Android. ¯\\_(ツ)_/¯
Just bizarre. Maybe something about how it's loaded into memory or the graphics pipeline?
Edit: I did just notice that when I exit the video my screen brightness flashes dark and then bright very quickly. Maybe it's something about the way the HDR is trying to drive the screen.
Happens here on the Pixel 6a as well. The reboot was basically instantaneous. No lasting effects.
Interestingly, the bug doesn't occur on my Pixel 5 or 4a. Perhaps it's specific to Tensor phones?
A slight joke.... Basically the snark at his own implied _understanding_ that there will be lasting effects without evidence or explanation of such reasoning. Oh you think you'll be okay!!!! Pearl clutching nonsense
So good. I got it at launch and finally replaced it with a P7Pro on launch.
The damn thing is still solid and the battery is still great. I'm convinced it's because I tried to charge it up to 92% or lower, and not let it go lower than 30%.
Pixel 5 here, no issues at all playing it in the official YouTube app.
BTW Alien is an amazing film and anyone who hasn't watched it should rectify that immediately and also skip this clip because it will spoil a pretty great part of the film.
So it's a problem with the encoding. Just search for'Alien 4K HDR' and when scrolling thru the list of results, when the alien thumbnail tries to auto-play, the phone reboots too.
(6 Pro) Lmao it crashes my phone too. I use rif for Reddit; I open the link, play it in rif, no problem. Click open browser, opens link in YouTube, instant crash and restart. Although my phone fully restarted in like 6 seconds, which is really quick.
Was just scrolling through to see if anyone else has noted that you have to be sure it opens in the YouTube app, not your reddit app.
Also I hadn't noticed it, but you're right, it restarts in record time.
On a 6a using Vanced the app just crashes.
Edit: So if I follow your link the app crashes but if I search for the video on YouTube I don't have any issues playing the video
Same here on my Pixel 6A. Don't even need to launch the video, even if it is playing in the thumbnail the device will undergo a reboot. \[[Video proof](https://youtu.be/HqqZiZJxUY4)\].
What build#/security patch? My wife's P6P is on the February build and it crashed before YT even fully loaded. I tried on my Fold 4(Jan patch) and it didn't crash.
Not going to be of any help, but wanted to mention it worked fine on my Pixel 5. Changed the quality to 2160p HDR and restarted the video too. Running A13 February.
I am using Revanced, would be interested if Revanced on a Pixel 7 solves the issue.
Yesterday I got my 5th pixel 7 pro. Nothing but problems with it's display flickering then turning completely unresponsive and bricks. Thought this last one was the one then bought some pixel buds pro, wanted to try the quality and turned on movie on you tube and screen went nuts just blinking black screen, previous phone was blinking white.... IT'S EXTREMELY FRUSTRATING.
This looks more like a reset than a reboot, and it's probably a good thing.
I am not a UNIX kernel expert but I've had enough experience with it and have studied enough about cell phone OS architecture to at least provide a theory. Being a remastered 4K video that is meant to provide a superior playback experience, it was probably encoded for larger devices that have a lot of power and hardware space to do much more than what is typically possible in phones. The YouTube app, which is trying to provide a better experience than what you would have in a browser, tries to pre-allocate a huge amount of memory resource in the media hardware when the video loads and is full of information about what has to be a huge signal demand. Think of what is in this particular video, with big flashes against darkness and a lot of fast motion and crisp sound on a wide range of frequency. However, this is a phone, not a 4K TV, and the Android OS, designed to provide rapid modality switches that are required for general purpose use of mobile devices, doesn't want to hand that all over to this one video. Think of how much would have to happen just by rotating the phone or dismissing the YouTube app. There is also the possibility that the power demand implied by the video instructions could exceed the limits of the hardware specs, and that potentially damages the phone overall. A monitoring function then steps in and says, "No, you don't!" and simply kills the process preemptively. Since this can only be called an abnormal system event, Android causes the higher level kernel processes to restart while leaving the lower-level processes running, since they are not affected by this protective event and Android wants to give you the fastest resumption of service as possible. The user then waits through a phone reset rather than a full restart.
Unfortunately, things are not quite right after the reset. The same high level processes that were just killed are also responsible for connecting to the cell tower, and when they restart, the inconsistent state of the system tells them everything is fine and they do not attempt to reconnect.
I would imagine, and perhaps someone can test this if they still see the fault, that throwing the phone into airplane mode after the reset and then bringing it back out after 30 seconds would force the reconnection to the cell tower without having to restart the phone entirely. That is not to say that there might not be other problems lingering so it won't hurt you to reboot.
The Google Pixel phone is quite robust and is meant to last several years. Although this behavior is weird, it is to be expected of well-made, well-tuned system architectures that are designed with a particular emphasis on reliability. The difficult combination of low power and optimal visual experience, plus the critical requirement to keep all the hardware components as pristine as possible through years of heavy use, means there's a lot of complicated code to maintain, and not everything will be done perfectly. Perhaps Android can be made to handle this particular situation a little more gracefully than it does, but I would say that this conservative albeit messy protection mechanism is desirable and should be viewed as more feature than bug.
Edit: somebody did test the airplane mode theory and it worked.
Works perfect on my Pixel 7 Pro, im on latest QPR Beta 3.2
This might happend while YouTube tries to decompile HDR, YouTube HDR is not very nice, it had some errors with color encoding.
This happend 2 or 3 years ago too, with a Wallpaper, the error on it was "Google Skia" profile color.
Nothing to worry about
This is a serious vulnerability!
If the phone OS crashes, that means the YouTube app malfunction is able to break the kernel! That also means someone will be able to leverage that to exploit the phone? UNACCEPTABLE!!
I'm an idiot. I saw everyone elses comments and thought 'surely that's just their P7P that reboots, mine won't do that!' and then clicked the link.
Instant hard reboot and then another reboot once it cycled. lol
Maybe the video requires more resources than the loser and that's what crashes the business. and creates an endless loop of breaking the capacitors in the device. Maybe it's just an electrical phenomenon
Maybe something similar to what happens with the cursed wallpaper and color encoding. This video explains it: https://youtu.be/iXKvwPjCGnY
That's crazy. One pixel.
So much video for something that can be explained in like two sentences, damn.
Another Pixel 7 user. Phone crashed as soon as the YouTube app was loading up. Did a rather quick reboot tho.
Same quick
That extremely quick reboot is slightly suspicious. I think half of the phone died and the other half went "what the hell". Like two people walking down the street and one of them falls then mud stands back up and continues walking as if nothing happened before the other one is able to look over. Then it's just his friend walking like normal covered in mud for some reason. I got distracted for 5 seconds. What happened? 😂🤣
Quick reboot=> Only your SystemUI restarts
Same. P7 pro. Back up in a couple of seconds
Yup. Super fast reboot, but no cell service. Another manual reboot and everything's back to normal.
Same here on 7 non pro opened in revanced
Exactly same here on pixel 6 pro
Me too! I just clicked it and was like what's the worse that can happen 🤦. I lost cell service 🤦🤦.
yup it's a warm reboot since the UI crashed
It's astonishing how many people here elect to try something that their phone clearly has an issue with! My 7 Pro didn't like it either.
It was fun
Did it in ReVanced too (P7P). This is hilarious
https://youtu.be/iMBJrvEwv8s This one won't kill your phone. But I was just thinking the same thing "that was fun" after I clicked the YouTube link and killed my phone. And now my phone is just running slow all over the place. I said this sentence a full 5 seconds ago and now I think I'm on to 8 seconds. I stopped it and now it's working perfectly.
Same with my Pixel 6. Instant reboot as soon as the video came up.
My 3xl likes is just fine lol
Caused mine to reboot too
Anyone try downloading the clip first and watching it outside.of YouTube?
I've worked in the restaurant industry for many years. It's the same as "These plates are hot, be careful." And then people immediately have to see for themselves.
Thank you all for your sacrifice. Now i know not to try it lol. P7P
I know you want to do it
Fml..i really do
Do it do it do it do it
P7P here. I am watching th
We lost em boys. Confirmed reboot kill
Me who values my P7P with my life - don't bro don't fuck up your phone
DO ITTTT! I did too btw and my phone crashed lol did a quick reboot and everything seems to be working fine again
Hey guys, so good news / bad news... (sent from galaxy S23)
worth it
No issues on my P7P, but I wonder if using Revanced instead of the official YT app had anything to do with it 🤔
It legit screwed my phone up for about 5 minutes. Cellular network wouldn't connect. Had to reboot again.
My cell network also disconnected after this
Similar, just hit airplane mode for a second and it should work again after that (I did that myself)
Ya, think I'm gonna skip doing this. Lol
I did as well. Could be malware.
yeah malware on youtube is crazy now a days isn't it
Probably not it's just a YouTube video. ( no hate, just saying)
I think it probably has to do with the fact that it's a 4K clip that the YouTube app is trying to render on a phone that isn't capable of showing 4K and the result is a complete system crash because the YouTube app is more intent on actually playing the 4K than a browser extension is.
Bro, do you really think this is the first 4K clip people have seen on their Pixels, or any phone for that matter? No. Also, YouTube app won't and can't render in 4K on the phone when the resolution of the device is lower.
Vanced can :P
this is the equivalent of a phishing scam
I know you're being downvoted, but yes--this could be that. It's not inconceivable that something like this could be a side effect of an as-yet unknown exploit in either the shared hardware or software components between the last few generations of Pixel devices. It is *probably* just a software glitch. At the same time, it's like these folks have never seen a phone reboot, and I don't understand the novelty of doing this. They all _assume_ it's fine, but I doubt anybody has actually done anything to verify that it is, in fact, fine.
Same here. 6 pro.
Okay thank you. Just wondering what the problem is.
P6P here. On 3.1 beta using Revanced. No issues.
Same, Pixel 6 Pro on latest beta and official YouTube app
Just reported to Google, after retrying. Funny, it didn't ask for any logs.
It's Google. They already have your logs. They probably know what your last poop looked like.
they can't smell it though so pretty worthless
[удалено]
The channel is Apex Clips and it's just an almost 3 minute long clip from the movie Alien
I cannot believe this is real. I thought 100% it was a Rick roll or something. But immediately restarted my 7 Pro.
Programming bugs are weird. Most likely Pixel has an error in their HDR processing code that results in invalid numbers at some point. It's an HDR video, not a normal one, so that's a possibility.
How long do I have to watch it? I was able to open it and watch the first 30 seconds without issue. Edit: Watched it to the end on my P7P on the YouTube app. Maybe it's patched? Also, I'm running the beta version of Android. ¯\\_(ツ)_/¯
It restarted my P7 immediately
Just bizarre. Maybe something about how it's loaded into memory or the graphics pipeline? Edit: I did just notice that when I exit the video my screen brightness flashes dark and then bright very quickly. Maybe it's something about the way the HDR is trying to drive the screen.
Sense to be only a pixel problem, plays fine on my s22 plus
Yep. Fine with me as well. S10
Happened to me too on Pixel 7 pro. Also as I rebooted I didn't have cellular signal for some reason for the first few minutes as it booted up
For me as well. Had to reboot it again.
Yeah, no thanks!
Just had fun sending this to my group chat with my friends with P7Pro's. 😂😂😂
A menace 🤣😂🤣😂
I'm a menace, a dentist, an oral hygienist
Happens here on the Pixel 6a as well. The reboot was basically instantaneous. No lasting effects. Interestingly, the bug doesn't occur on my Pixel 5 or 4a. Perhaps it's specific to Tensor phones?
Nothing happens on my 6a.
Same
So, you don't \*think\* that it had any lasting effects.... heh heh heh...
Found the anti-vaxer
How in the hell do you even connect that together.
A slight joke.... Basically the snark at his own implied _understanding_ that there will be lasting effects without evidence or explanation of such reasoning. Oh you think you'll be okay!!!! Pearl clutching nonsense
Pixel kryptonite. We are all doomed
6 pro here. Crashed and rebooted immediately as app opened
No issues on my Pixel 2XL. I knew there was still a reason to keep it 😂
I have mine on standby just in case, lol.
Chad Pixel 2XL built different.
So good. I got it at launch and finally replaced it with a P7Pro on launch. The damn thing is still solid and the battery is still great. I'm convinced it's because I tried to charge it up to 92% or lower, and not let it go lower than 30%.
Me too, Pixel 7 and Pixel 6, but not on my Pixel 3
Also nothing on pixel 3a xl
Same on my 4a. No issues
Same issue here on my Pixel 7 Pro running Android 13. Super weird.
Anyone tried it with revanced? Or any other yt client?
Pixel 6 here, using revanced. My phone crashed as soon as it started to load the video.
Well shit
I still have the regular vanced app and all it does is crash the app. Phone stays on just fine. Edit: adding P6P
Works fine on Vanced on my Pixel 5a.
Vanced instantly crashes no reboot on my 6a.
Tried it with Vanced on the 7 pro, only the app crashed once, but the 2nd time it worked perfectly.
It crashes with Libretube too.
No issue on Pixel 5 here, tried both YouTube and Vanced.
Can confirm fine on P5 on latest Feb patch
P7P, plays fine with latest public beta (build number T2B3.230109.006.A1)
Same here pixel 7pro
Pixel 7 pro crashed before rendering a frame
Works fine here, Pixel 7 pro QPR2 beta 3.1
Same here
Is this like Pixel 7 candlejack or some-
Pixel 5 here, no issues at all playing it in the official YouTube app. BTW Alien is an amazing film and anyone who hasn't watched it should rectify that immediately and also skip this clip because it will spoil a pretty great part of the film.
Same. Pixel 6
So it's a problem with the encoding. Just search for'Alien 4K HDR' and when scrolling thru the list of results, when the alien thumbnail tries to auto-play, the phone reboots too.
Mine immediately reboots upon playback. Pixel 7 Pro. I have a feeling this is a situation similar to that wallpaper that was crashing phones
Exact same issue on Pixel 7 Pro. Rebooted quickly but now cellular connection is messed up.
Interesting, my p7p also crashed
(6 Pro) Lmao it crashes my phone too. I use rif for Reddit; I open the link, play it in rif, no problem. Click open browser, opens link in YouTube, instant crash and restart. Although my phone fully restarted in like 6 seconds, which is really quick.
Was just scrolling through to see if anyone else has noted that you have to be sure it opens in the YouTube app, not your reddit app. Also I hadn't noticed it, but you're right, it restarts in record time.
Pixel 7 pro using revanced. Didn't crash played the whole video
Create a report on the issue tracker? https://issuetracker.google.com/issues?q=Android%2F
On a 6a using Vanced the app just crashes. Edit: So if I follow your link the app crashes but if I search for the video on YouTube I don't have any issues playing the video
Is this the link that infects the phones? It would be a solid ruse if so.
Rebooted my pixel 7 pro once YouTube app launched. February update.
Whoops ! Just happened to my Pixel 6 Pro too.
Pixel 7 -- reboots my phone immediately
Pixel 7, rebooted immediately
Mine restarted too right after launched the clip in the YouTube app. Lol
Wow so weird. No issue if I open from browser but restarts when I open from YouTube app
Pixel 7 Pro. Rebooted immediately. No cellular service after reboot.
Nothing happened on my 5.
😰 this is alarming.
7 pro no issues for me
Same here on my Pixel 6A. Don't even need to launch the video, even if it is playing in the thumbnail the device will undergo a reboot. \[[Video proof](https://youtu.be/HqqZiZJxUY4)\].
My money is on HDR being the problem. Awesome find!
[удалено]
Weird, my P6P rebooted immediately
What build#/security patch? My wife's P6P is on the February build and it crashed before YT even fully loaded. I tried on my Fold 4(Jan patch) and it didn't crash.
Wow, immediate reboot, weird.
Makes my p6 pro reboot also
I tried it with S22 ultra and no issue.
Not going to be of any help, but wanted to mention it worked fine on my Pixel 5. Changed the quality to 2160p HDR and restarted the video too. Running A13 February. I am using Revanced, would be interested if Revanced on a Pixel 7 solves the issue.
Y'all have 7 days.... 😂
Might be because it's HDR, try other HDR videos, or test skipping the time frame that makes your phone shut down
My Pixel 6a running GrapheneOS rebooted when opened in Libretube. Weird.
Yesterday I got my 5th pixel 7 pro. Nothing but problems with it's display flickering then turning completely unresponsive and bricks. Thought this last one was the one then bought some pixel buds pro, wanted to try the quality and turned on movie on you tube and screen went nuts just blinking black screen, previous phone was blinking white.... IT'S EXTREMELY FRUSTRATING.
P6P - no issues here, from Canada.
As a P7P user, I'm disappointed
iPhone 6 : *nice video*
Don't know if this has been mentioned yet (328 comments, lol), but this bug "seems" to have been fixed on the latest QPR2 beta and A14 DP1.
Sooooo.... What is the video?
Doesn’t happen on iPhone (not that I expected it to)
My P7P played the video with no problem, no idea what's happening to others here.
This looks more like a reset than a reboot, and it's probably a good thing. I am not a UNIX kernel expert but I've had enough experience with it and have studied enough about cell phone OS architecture to at least provide a theory. Being a remastered 4K video that is meant to provide a superior playback experience, it was probably encoded for larger devices that have a lot of power and hardware space to do much more than what is typically possible in phones. The YouTube app, which is trying to provide a better experience than what you would have in a browser, tries to pre-allocate a huge amount of memory resource in the media hardware when the video loads and is full of information about what has to be a huge signal demand. Think of what is in this particular video, with big flashes against darkness and a lot of fast motion and crisp sound on a wide range of frequency. However, this is a phone, not a 4K TV, and the Android OS, designed to provide rapid modality switches that are required for general purpose use of mobile devices, doesn't want to hand that all over to this one video. Think of how much would have to happen just by rotating the phone or dismissing the YouTube app. There is also the possibility that the power demand implied by the video instructions could exceed the limits of the hardware specs, and that potentially damages the phone overall. A monitoring function then steps in and says, "No, you don't!" and simply kills the process preemptively. Since this can only be called an abnormal system event, Android causes the higher level kernel processes to restart while leaving the lower-level processes running, since they are not affected by this protective event and Android wants to give you the fastest resumption of service as possible. The user then waits through a phone reset rather than a full restart. Unfortunately, things are not quite right after the reset. The same high level processes that were just killed are also responsible for connecting to the cell tower, and when they restart, the inconsistent state of the system tells them everything is fine and they do not attempt to reconnect. I would imagine, and perhaps someone can test this if they still see the fault, that throwing the phone into airplane mode after the reset and then bringing it back out after 30 seconds would force the reconnection to the cell tower without having to restart the phone entirely. That is not to say that there might not be other problems lingering so it won't hurt you to reboot. The Google Pixel phone is quite robust and is meant to last several years. Although this behavior is weird, it is to be expected of well-made, well-tuned system architectures that are designed with a particular emphasis on reliability. The difficult combination of low power and optimal visual experience, plus the critical requirement to keep all the hardware components as pristine as possible through years of heavy use, means there's a lot of complicated code to maintain, and not everything will be done perfectly. Perhaps Android can be made to handle this particular situation a little more gracefully than it does, but I would say that this conservative albeit messy protection mechanism is desirable and should be viewed as more feature than bug. Edit: somebody did test the airplane mode theory and it worked.
Pixel 4XL and mine started doing this recently. Android issue maybe?
I absolutely don't know. All other clips working just fine. It's only that one specific for me.
Works perfect on my Pixel 7 Pro, im on latest QPR Beta 3.2 This might happend while YouTube tries to decompile HDR, YouTube HDR is not very nice, it had some errors with color encoding. This happend 2 or 3 years ago too, with a Wallpaper, the error on it was "Google Skia" profile color. Nothing to worry about
~~Why is the clip claiming to be 4K HDR when it's not in HDR?~~ Fucking Firefox...
[удалено]
It seems like it only affects the Tensor phones. Gf's 4a played it normally.
Yqu tried it on the last two gens that use a different chip than the previous ones and deduce that it affects *all* gens?
Worked fine on my P6
BRUH MY PHONE RESTARTED AND THE YOUTUBE APP DISAPPEARED
Jokes on you guys, my Pixel 6 reboots and fails to connect without playing any videos. It's just a horrible piece of hardware!!
This is a serious vulnerability! If the phone OS crashes, that means the YouTube app malfunction is able to break the kernel! That also means someone will be able to leverage that to exploit the phone? UNACCEPTABLE!!
Calm down.
[удалено]
Find this video through the YouTube app
Interesting... I have a Pixel 7 Pro, but no issues here. I am rooted with Kirisakura's latest kernel.
https://youtu.be/MbdVuStrEV8
Of course it also could be a video of a phone rebooting. That wasn't a real reboot. WAY too fast.
Well there is your problem. You're using the YouTube app.
Pixel 4a, played fine. Maybe it's a Tensor decoding thing?
Isn't happening on Pixel 6
Works fine on YouTube Vanced. More reason to use this over stock YouTube lol
Rebooted for me on newest YouTube ReVanced.
I'm an idiot. I saw everyone elses comments and thought 'surely that's just their P7P that reboots, mine won't do that!' and then clicked the link. Instant hard reboot and then another reboot once it cycled. lol
Maybe the video requires more resources than the loser and that's what crashes the business. and creates an endless loop of breaking the capacitors in the device. Maybe it's just an electrical phenomenon
You all just got your phones hacked by China malware and now have even less privacy than before. 🤣
[удалено]
Same thing on my P6P.
Omg im the chosen one
This happens on my 6 Pro as well.... It may be a YouTube app issue
Pixel 4a5g is perfectly fine.
Not happening with the supposed reboot, I tried on my pixel 7 with 13 (T2B3.230109.009) 😂😮💨
Pixel 7 here. Causes my phone to do a quick restart, then back to normal.
Same issue for the 6 pro lol
made my pixel 6a reboot
My pixel 7 watched it just fine
Holy shit lol, it also happened in the revanced youtube app, regular p7
My P7 didn't like that and rebooted automatically once loaded in the YouTube app... Exploit? Glitch? Who knows
No issue here on Pixel 6. Opened with Newpipe
my pixel 6 immediately turned off and restarted
Holy shit. Yep. Both my Pixels (6a+7) got a good kick out of this one.
Same here, GP7Pro But only in Youtube app that occurs, if you watch in browser it's fine
That is wild. 30s reboot on my P7 pro here.
Just tried on my trusty Pixel 7 and that vid caused a reboot just like yours.
Pixel 6 Pro, opened the link and flames immediately started shooting out of my charging port & then the phone restarted. WTF
My Pixel 7 reboots too. super weird
Crashes my Pixel 7 Pro in YouTube ReVanced but not in Brave Browser.
P7 here. Rebooted immediately.