Hey guys,
So just a little background: Running PA 2.53 on Trinity 63
The problem: Sometimes I'll try and play a video, on youtube, locally, basically anywhere and the phone just won't. It'll sit there loading then when I hit back the app FCs. A restart will fix the issue until I run into it again, at which point I have to reboot again.
Extra: This isn't exclusive to my configuration. I've had the same issue since I got the phone (before root and rom). The issue persisted on PA with the included kernel as it does with the Trinity kernel. I like PA though and would like to stick with that. I don't know if this is related, but when this happens my face unlock also stops working (loads for a second then flips to the pattern grid)
So, folks, has anyone heard of anything like this? I don't think it's a hardware issue since a restart usually clears it up, but it's really frustrating (and embarassing when I want to show someone a video I literally just took) Any suggestions on how to fix it?
I had the same issue. Uninstalling VLC beta solved it. I don't know if you have a third app video player installed, but you might want to try that.
Sent from my Galaxy Nexus using xda app-developers app
Only QuickPic. I just uninstalled it now and am seeing if it makes any difference, doubt it will since it's not a video player with its own codecs like VLC.
Bump, other opinions?
I have found a similar issue on another site that outlines the exact problem I'm having, seems many are having them since Jelly Bean. Factory Resets don't help.
http://androidforums.com/samsung-galaxy-nexus/592669-video-player-youtube-problems-jelly-bean.html
bump bump.
Related
Hello, I was just wondering whether anybody else had this problem. Whenever I play Netflix on a tw based rom, the picture freezes about thirty minutes in, even over multiple episodes, the back button becomes useless, the touchscreen becomes useless, and the only way to fix it is to press home and kill Netflix. This doesn't happen in CyanogenMod, but I really want to know why this happens.
Sent From The Best Phone of 2011
Been using Netflix since day 1 and never had that problem.how many other apps are you running?
Btw, shouldn't this be in apps?
Sent from my SGH-T989
None. I think it might just be an isolated case. When I flashed CM7 the problem went away. I guess I'm just going to have to keep wondering. And thanks for moving my post.
Sent From The Best Phone of 2011
Hello, this is my dad's phone and I'm used to Samsung so everything is a bit different. I've been searching for a fix for hours but nothing seems to work, I have the latest version of YouTube and I simply can't play YouTube videos from both the app and browser. It will play for around 4 seconds, stop and start over like 3 seconds later to do the exact same thing. I had this issue with other videos as well but fixed that by using a different video player. I hope someone can help me.
Thanks, Johan.
Fixed it using a bit of common sense, can't believe I didn't see that earlier.
Mods can close this now if they want to.
It came back for some reason, can anyone help?
I've experienced this issue before, but I've LGNPST'd a few times since for various reasons, not because of this, and it seems to clear it up each time. Youtube is fine, I have yet to have an issue with that, but when I'm running an internet browser and choose to play a video where it does not request me to pick a player, the clip will play for a few seconds, then the screen goes black but is backlit. Now if I touch the screen, the clip is view-able again for a few seconds and then will go back to the black backlit screen. Clip isn't pausing, just the image is cutting.
Currently I'm running stock JB (not a ROM), rooted and unlocked running TWRP 2.4.4 with CM 10.1 on my storage. It seems that I notice this only after rooting\unlocking or after a ROM gets installed even if I flash back to stock.
Has anyone else experienced this? Can anyone offer suggestions? If I can provide more info, let me know.
latrotoxin1986 said:
I've experienced this issue before, but I've LGNPST'd a few times since for various reasons, not because of this, and it seems to clear it up each time. Youtube is fine, I have yet to have an issue with that, but when I'm running an internet browser and choose to play a video where it does not request me to pick a player, the clip will play for a few seconds, then the screen goes black but is backlit. Now if I touch the screen, the clip is view-able again for a few seconds and then will go back to the black backlit screen. Clip isn't pausing, just the image is cutting.
Currently I'm running stock JB (not a ROM), rooted and unlocked running TWRP 2.4.4 with CM 10.1 on my storage. It seems that I notice this only after rooting\unlocking or after a ROM gets installed even if I flash back to stock.
Has anyone else experienced this? Can anyone offer suggestions? If I can provide more info, let me know.
Click to expand...
Click to collapse
I experienced this too.
I just decided not to use chrome and use the default browser, it work's perfectly fine there.
I'll give that a shot. Hadn't really considered it might just be a chrome issue...
Sent from my LG-LS970 using xda app-developers app
I had the same problem until I read some where here to check disable hw overlays under developer options. It works just doesn't stick after reboot.
Sent from my AT100 using Tapatalk HD
I am experiencing what seems to be a reproducible phone crash while casting Google Play Music to my TV. If the phone goes to sleep while casting and I wake it, hitting volume down or up buttons while on the lock screen crashes the phone. I couldn't replicate the crash while casting YouTube, only Google Play Music. Also, no crashing when adjusting song volume from lock screen while not casting. When the phone crashes it goes straight to the boot animation, no splash screen shown, and gets stuck there. I have to force shutdown to get it to turn off.
Phone is s-off, rooted, running latest stock.
Anyone with a Chromecast willing to replicate this crash? Any ideas what's going on?
Thanks.
xenakis said:
I am experiencing what seems to be a reproducible phone crash while casting Google Play Music to my TV. If the phone goes to sleep while casting and I wake it, hitting volume down or up buttons while on the lock screen crashes the phone. I couldn't replicate the crash while casting YouTube, only Google Play Music. Also, no crashing when adjusting song volume from lock screen while not casting. When the phone crashes it goes straight to the boot animation, no splash screen shown, and gets stuck there. I have to force shutdown to get it to turn off.
Phone is s-off, rooted, running latest stock.
Anyone with a Chromecast willing to replicate this crash? Any ideas what's going on?
Thanks.
Click to expand...
Click to collapse
Yep. I've had it happen to me as well. I've never really tried to see what the issue may be though.
Its happening to me too. Are you using xposed mod to wake with volume button? I am and I'm thinking that might be the cause. I'll try it a little later and report back.
Edit. That's not the cause. I turned off that mod and it still happens.
No xposed mod or anything else. All I'm doing is trying to adjust the volume of the song that is playing, which one should be able to do while casting, and the whole phone crashes. Is this an HTC problem or Google problem? midnight assassin, what ROM are you running?
midnight assassin said:
Its happening to me too. Are you using xposed mod to wake with volume button? I am and I'm thinking that might be the cause. I'll try it a little later and report back.
Edit. That's not the cause. I turned off that mod and it still happens.
Click to expand...
Click to collapse
I am experienced the same issue last night while using Netflix. I tried adjusting the volume while using my chromecast and then my phone reboots into the HTC one screen. I have to hold the power button until it hard reboots.
Sent from my One using Tapatalk
I get this same issue on Verizon HTC One, although it seems the phone doesn't need to be actually asleep, and it will reboot itself - does not need a hard reset from me.
Non Rooted HTC One
I am also having the same issues when trying to change the volume of Play while the screen is off. I have a non rooted Verizon HTC One.
exact same issue with me when using volume rocker after phone goes to sleep while casting Play Music. I am using ATT phone rooted, s-off, running latest ARHD 31.6 rom. this seems to be an issue with chromecast as it only happens when casting.
Thanks for reporting. I'm trying to figure out if the problem is on Google's end or HTC's. My Nexus 7 doesn't have this problem while casting.
I emailed HTC support about it, with a link to this thread. I'll post back if I get a reply.
I've noticed the same issue. I'm running InsertCoin 6.0-5. It took two reboots before I figured out why my phone kept crashing. I've been using my Chromecast for a while, and I only recently went back to a Sense rom. I was running CM 10.2 until recently, and I can't recall having this issue on that rom, but I can't say for certain. I'm sort of glad to see that I'm not the only one having a problem.
Edit: Oh, and I just noticed this is the Verizon forum (came across this thread via Google). I have an AT&T HTC One.
It's still good to know that the problem is not carrier specific.
I did heard back from HTC and they just punted saying that it's a third party app, not their problem, and suggested uninstalling and reinstalling the app, which doesn't fix anything.
Anyone know how to report this to Google?
Sent from my HTC6500LVW using xda app-developers app
xenakis said:
It's still good to know that the problem is not carrier specific.
I did heard back from HTC and they just punted saying that it's a third party app, not their problem, and suggested uninstalling and reinstalling the app, which doesn't fix anything.
Click to expand...
Click to collapse
Typical manufacturer BS. If your OS crashes because of a third party app, then there's something wrong with your OS. A properly designed OS should be incapable of crashing because of a third party app. Never mind the third party in question in this case is Google... If it only crashes under HTC's spin of Android, then HTC broke something and needs to fix it.
I'm tempted to wait until the "sense-ified" release of KitKat comes out to see if that fixes the issue, since I'm waiting on HTC to fix the stupid purple hue low-light camera issue as well.
I have this very same problem, except i dont have to force shutdown. It just reboots sense (takes about 10 seconds) and then all is fine.
I'm rocking a stock (android 4.3) international simlock free unit.
Not rooted, no s-off, no nothing. Fresh out of the box.
Im still having this same problem on my HTC one X running ViperX 4.07. Has anyone found a solution yet?
I've recently experienced a similar issue when casting from the GP Music app to my Sonos speakers. When trying to adjust the volume from within the GP Music app, it causes the phone to reboot. I have an HTC One still running 4.3 (my carrier in the UK dragging their feet a bit!). I was wondering (hoping) whether this is still an issue with 4.4?
Sometimes when I launch Super Hexagon, the game runs terribly slow. It feels like it's running at 15-20 FPS instead of 60 FPS. The weird part is that this lag persists after I exit the game. The whole system becomes super slow with choppy animations.
I've tried killing the app and even clearing the data, but the only thing that seems to fix this is a reboot. I can reproduce this behavior after rebooting again. It usually happens on the 2nd or 3rd time I launch the app, but sometimes it can take up to 10 times of closing and launching. Holding the tablet vertically seems to trigger it faster (although I'm not completely sure if it's related yet).
I'm running completely stock KOT49H and version 1.0.5 of Super Hexagon.
I haven't been able to reproduce this on my Nexus 4 or my old Nexus 7 (2012).
Can anyone else confirm that this happens on their Nexus 7 (2013)? I'm just wondering if it's a bug/compatibility issue or if it's a problem with my device
Just a quick update: Tried changing to ART with and flashing the latest franco kernel (just to experiment), and it still happens in the exact same way
Eregoth said:
Just a quick update: Tried changing to ART with and flashing the latest franco kernel (just to experiment), and it still happens in the exact same way
Click to expand...
Click to collapse
I know this is a late response but I had the same thing happen to me twice tonight and I found your thread while googling for the issue myself.
Force closing the app doesn't help. It seems I have to reboot to fix it.
Have you by any chance figured out a fix? I'm running a 2013 n7 completely stock
chiefz0r said:
I know this is a late response but I had the same thing happen to me twice tonight and I found your thread while googling for the issue myself.
Force closing the app doesn't help. It seems I have to reboot to fix it.
Have you by any chance figured out a fix? I'm running a 2013 n7 completely stock
Click to expand...
Click to collapse
Haven't found a fix yet
It's clearly a software issue though, either with the game or the latest N7 2013 build. Maybe someone who's more skilled could check the debug log (or something) to figure out the cause.
Hey
EDIT:
to fix this problem, open your favorite file explorer..
navigate through android/data/(superhexagon package file name)
go to settings.dat
change vsync from 1 to 0
NsZebra said:
EDIT:
to fix this problem, open your favorite file explorer..
navigate through android/data/(superhexagon package file name)
go to settings.dat
change vsync from 1 to 0
Click to expand...
Click to collapse
Just tried this and it happend again (on the first try). Rebooted and triggered it again after launching the app 3 times.
Eregoth said:
Sometimes when I launch Super Hexagon, the game runs terribly slow. It feels like it's running at 15-20 FPS instead of 60 FPS. The weird part is that this lag persists after I exit the game. The whole system becomes super slow with choppy animations.
I've tried killing the app and even clearing the data, but the only thing that seems to fix this is a reboot. I can reproduce this behavior after rebooting again. It usually happens on the 2nd or 3rd time I launch the app, but sometimes it can take up to 10 times of closing and launching. Holding the tablet vertically seems to trigger it faster (although I'm not completely sure if it's related yet).
I'm running completely stock KOT49H and version 1.0.5 of Super Hexagon.
I haven't been able to reproduce this on my Nexus 4 or my old Nexus 7 (2012).
Can anyone else confirm that this happens on their Nexus 7 (2013)? I'm just wondering if it's a bug/compatibility issue or if it's a problem with my device
Click to expand...
Click to collapse
I confirm, the only solution is to reboot... Very annoying if it happens while you break a record
Wow, I am astonished by Google. It has been over a year now and this problem STILL exists, I am having the exact same problem as described in the OP with several apps. How come this problem gets so little attention? Should be well known by now.
All those fancy design changes but who cares about actual system stability.
^What apps? I've never had this problem and this is my first time reading about it.
It's up to the app developer to keep their **** updated to work well with new versions of android. Nothing to do with google.
yosmokinman said:
^What apps? I've never had this problem and this is my first time reading about it.
It's up to the app developer to keep their **** updated to work well with new versions of android. Nothing to do with google.
Click to expand...
Click to collapse
No way apps are supposed or even able to mess with the whole system like that and this bug doesn't happen on other devices like nexus 5 with the same apps so it's obviously just the device. I mean did you even read the thread you ignorant prick? The thread creator said too that he can't reproduce it with other devices such as Nexus 4 or Nexus 7 2012.