Running CM 5071
For some reason YouTube doesn't seem to work right.
Sometimes it freezes and force closes when I try and play a video... and if it DOES load up without a freeze/force close I will hear the audio just fine but the picture will stay frozen. It just wont move, If I skip ahead it will show that frame, the audio will still keep going but the picture will still remain frozen... what could I possibly try to fix this?
Any ideas on this?
Same problem.
One of 2 things happens:
1. video plays but is stuck on the first frame, sound continues
seeking in the video will change the frame it is stuck on
2. you get an error: 'sorry, this video cannot be played'
Hitting 'ok' here will actually cause a force close, or the phone will become so lethargic that a battery pull is necessary
3. you are greeted with a black screen and the only response from the phone is the haptic feedback on the back/menu/home/search buttons.
The buttons are illuminated, screen is not.
This was happening with Froyo, and now CM 5.0.7
I went back to CM because of this problem, and it seems to have persisted.
Someone has GOT to know something....
Thank you. You have described our problem so much better than me, hopefully someone knows of a fix.
I'm guessing this has something to do with FroYo.
Before you upgraded to FroYo, did you at any point install the "Always HQ" YouTube hack? I was wondering if that had anything to do with that, maybe pushing the original YouTube APK will fix it.
lance713 said:
Thank you. You have described our problem so much better than me, hopefully someone knows of a fix.
I'm guessing this has something to do with FroYo.
Before you upgraded to FroYo, did you at any point install the "Always HQ" YouTube hack? I was wondering if that had anything to do with that, maybe pushing the original YouTube APK will fix it.
Click to expand...
Click to collapse
No.. but my limited knowledge of java is not helping me.
I am trying to figure out what is going wrong... there is a lot of 'not so nice looking' stuff in the logs.
What I have tried:
CM 5.0.6, CM 5.0.7
Wipes of davlik, cache, data, etc.
fix_permissions
'Fix apk UID mismatch' in recovery
Nothing has changed.
Stuff worthy of noting.. there are a LOT of these interesting lines in the logs:
05-27 06:50:45.408 W/ResourceType( 113): Resources don't contain package for resource number 0x7f050000
05-27 06:50:45.408 W/ResourceType( 113): Resources don't contain package for resource number 0x7f020005
The 'resource number' at the end is often repeated and there are about 30 or so lines.
I suspect the froyo update has left something behind that has to go away...
Still looking
do me a favor, use skyfire and try to watch a video. For me it always gets stuck on 25%, I wonder if it's related.
Edit: seems like this is also a problem with videos loaded on the sd. Tried watching a tv show I downloaded. Black screen, lights lit, force close.
video I recorded.. Full audio, frame freezes. Seek freezes a new frame.
Camera in video mode is causing a hard crash on mine.
When I change to video mode the phone locks up for 10 seconds with no response and then reboots.
I am guessing that's the watchdog in the kernel kicking in and rebooting it.
Overall not a good sign.
I am " bumping" this post because I am experiencing the SAME THING EXACTLY!!!
I performed all the same steps as the previous posters.
I was on Froyo... and it happened then. Then I did a Nandroid restore back to CM 5.0.7 and still the same problem exists.
I cannot play ANY video files... Youtube, TV.com, camera recorded videos.
I do hear the audio.
This is so aggravating. Everything else is running fine. But for me this is a big issues.
Thanks for any input, help, or advice!
Found something in a Google search, but it was posted to the cyanogen forums, which have been down all day.
The Google cache of it does not have the information.
The topic has the title '[Solution] Nexus One Won't Play Any Videos after Froyo'
Looks like someone @ cyanogen figured it out but we can't get at the forum to see the fix.
Here is some more information from the logs:
05-27 14:43:13.597 W/QCvdec ( 99): get_parameter: unknown param 0ff7a347
05-27 14:43:13.697 W/QCvdec ( 99): H264_Utils::check_header
05-27 14:43:13.697 W/QCvdec ( 99): check_header: start code 26
05-27 14:43:13.707 W/QCvdec ( 99): H264_Utils::check_header
05-27 14:43:13.707 W/QCvdec ( 99): check_header: start code 8
05-27 14:43:13.707 W/QCvdec ( 99): vdec_open
05-27 14:43:13.707 E/QCvdec ( 99): adsp: cannot open '/dev/vdec', fd: -1 (Out of memory)
05-27 14:43:13.707 W/QCvdec ( 99): Adsp Open Failed
05-27 14:43:13.707 W/QCvdec ( 99): adsp_close: adsp_module is not initialized
05-27 14:43:13.707 W/QCvdec ( 99): FA: Setting Tail to NULL
05-27 14:43:13.707 W/QCvdec ( 99): ERROR!!! vdec_open failed
05-27 14:43:13.707 W/QCvdec ( 99): Native decoder creation failed
05-27 14:43:13.707 W/QCvdec ( 99): ETB in Invalid State
Click to expand...
Click to collapse
I am showing plenty of free memory so I wonder if that device actually exists (/dev/vdec)
I can't get the file explorer running in DDMS for some reason... and I just don't know squat about this kind of debugger.
I am a gdb fan myself
But I keep poking around......
Solution found!
It's the radio!
Get the older radio from here:
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Call me crazy... but it works now.
I flashed:
32.26.00.24U_4.04.00.03_2 download MD5: c55116d119e9e30cffc86875dce1a560
camera works, phone works, youtube works....
Also I am on T-Mo.. no idea if this makes a difference but just in case.
videos work again after flashing the old radio! Thank you for finding the fix.
this is not just froyo, because this happened to me 2 weeks ago and my youtube app STILL does not work. i am still on 2.1 and there are other posts about this exact issue, but no fix has ever been found. i think it just is something on googles end, cause i did not do anything and suddenly my youtube started doing this. the video freezes but the audio continues.
RogerPodacter said:
this is not just froyo, because this happened to me 2 weeks ago and my youtube app STILL does not work. i am still on 2.1 and there are other posts about this exact issue, but no fix has ever been found. i think it just is something on googles end, cause i did not do anything and suddenly my youtube started doing this. the video freezes but the audio continues.
Click to expand...
Click to collapse
All of the symptoms I had seemed related to video.
Youtube did not work, recording video caused the phone to reboot, and so forth.
Does your camera record video?
One thing I noted only hours after I installed froyo over CM was that some streaming apps force closed..
Then the next day I noticed the youtube problem.
Then today is when I noticed the camera problem because I don't shoot video with the phone and the still camera still functioned normally.
I was running stock, then I went to CM, then to froyo and back again.
What is stumping me is what the radio had to do with this?
I don't know enough about the internals to come up with that.
Sorry I wish I had more for you
Nope I can still record video just fine. No reboots here. It's only with the YouTube app which doesn't work anymore.
Have the same problem.
CM to FROYO, with new RADIO, back to 5.0.7 and Youtube or camera viedo does not work.
Will try downgrade RADIO image.
will use this one:
32.26.00.24U_4.04.00.03_2
I can also confirm that downgrading the radio allows the youtube videos to work again. Whew!
Maybe that's why the official froyo release is taking so long -- because the new radio trashes youtube?
I have been having a persisting force close issue that I initially thought was linked to Greenify. "Unfortunately, Context Service has stopped" after every call I made or received, and upon booting the phone. Trial and error have caused me to find the only thing that allows me to run Xposed without any issue is having 7 or less modules enabled. I can switch between modules. For instance, I had Xposed Torch enabled and things were fine with 7 modules. I installed Xtoast, rebooted, and instant error/FC. Repeats no matter how many times I reboot. I uninstall Xposed Torch, which was just working perfectly fine, and leave XToast installed. Reboot and no error. Rebooted over and over to ensure, no error. Switched a few modules around to ensure, and it seems to not matter what modules I have installed. I have no issues whatsoever running Xposed as long as I only have seven modules installed, but if I go to install an 8th, no matter what it is, I immediately get Context Service force closes. I have not found anything on here about a definitive amount of modules you can install, so I can only hope someone has a clue what could be going on. Normally I'd look to the Logcat, but it doesn't seem to be a specific module causing this. I'd really appreciate any help any of you might have. Xposed has a lot more to offer for me than you can cram in seven modules.
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
GermainZ said:
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
Click to expand...
Click to collapse
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
wrongway213 said:
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
Click to expand...
Click to collapse
Enable 7+ modules so that the issue will be reproduced on next boot.
Reboot and start the logcat while the device is booting.
Wait till you see the FC and stop the logcat.
Upload the logcat.
Thanks for your reply. I just figured out the problem, thankfully.. I was preparing to do what you said, and I for some reason thought to reinstall Busybox before installing an eighth module and rebooting. My Busybox install must have been faulty. After reinstalling it said I had just reinstalled the same version as previously installed, but now I am back to nine modules and no problems.
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
wrongway213 said:
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
Click to expand...
Click to collapse
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
GermainZ said:
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
Click to expand...
Click to collapse
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
F/C All devices
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
wrongway213 said:
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
Click to expand...
Click to collapse
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
jon3640 said:
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
Click to expand...
Click to collapse
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
GermainZ said:
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
Click to expand...
Click to collapse
problem came back again for no reason, only 6 mods enabled and all have been stable for days... restart phone because i was getting a crazy mms wakelock in bbs. here's the logcat with the "unfortunately, context service has stopped" both from just automatically happening and i triggered it by having my girlfriend call me. i then disabled xposed, restarted and no problems, so i took a logcat of that to show how my phone runs normally in case you need it. let me know if you do and i will upload that as well.. if you can find anything in here i will greatly appreciate it. i can't even use xposed at this point, i'm worried i'm either damaging my phone or possibly missing calls/texts/notifications. thanks for your time in advance.
It's an ANR (Application Not Responding) error, so I'm guessing your phone kinda hangs for a bit before showing you the dialog?
It doesn't seem to be related to Xposed at all, though. It's Samsung's "Context service" (com.samsung.android.providers.context), so I'd personally try checking for a system update before anything else. You're likely to get more help in the S5 section (since the problem isn't related to Xposed), through it looks like no one else has this problem.
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled? That's why I assumed it was xpoaed related to begin with. Do I need to Odin back to stock? I don't want to damage my phone but I don't know anything about that error or if it could he damaging.. Sorry for the text wall. Thanks for being so helpful.
Sent from my SM-G900V using XDA Free mobile app
wrongway213 said:
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled?
Click to expand...
Click to collapse
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
wrongway213 said:
Do I need to Odin back to stock?
Click to expand...
Click to collapse
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
wrongway213 said:
I don't want to damage my phone but I don't know anything about that error or if it could he damaging..
Click to expand...
Click to collapse
It's mostly just annoying, there should be no permanent damage of any kind.
GermainZ said:
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
It's mostly just annoying, there should be no permanent damage of any kind.
Click to expand...
Click to collapse
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
wrongway213 said:
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
Click to expand...
Click to collapse
I didn't see anything related to S Health, but it might've related to the secure storage (though I'm not sure if that's a stock Samsung thing or if it's activated by the user).
Specs:
Rom: ARHD 91.1
Kernel: Elemental X 20.2
Xposed 3.0 A4, FrameWork v67
So recently I have been using Netflix to watch shows on my phone, and maybe after around 15-20 minutes into a show, the phone will freeze up. A small percentage of the time it will unfreeze and I can go to homescreen, but otherwise I would have to do a hard reboot.
It was a crazy guess, but when I disable all Xposed Mods, Netflix would work without a problem.
I tried going through each of my modules to figure out the problem one, but it would literally take hours....
If I took the Xposed Log from the framework would that potentially tell me which module is causing the error even after the reboot? or how would i go about this?
If I can provide logs would anyone be able to see quickly which mod causes the crash?
Thanks.
Would really like to know what this line means in Logcat. I had a random reboot running HDS9 with Franco kernel 42 and supersu 2.68 so I looked at my Logcat. I have attached my Logcat. I can't seem to attach it from my phone.
Uploaded my one from yesterday as my current Logcat is too big to upload.
The line that repeats constantly, like 4-5 times or more per second, is
[time stamp] 11220 11220 W ResourceType: for resource 0x0103020, entryindex(518) is beyond entrycount(1)
Another one that comes up whenever I touch the screen is
[time stamp] 898 1356 E PowerHAL: touch_boost: failed to send: no such file or directory
Note that neither of these seem to cause issues but I'd like to know what causes them so when I look at my Logcat it's not thousands of entries for one thing.
I do not know about first one but second touch boost thing is not important, I remember it was a side effect of PowerHal touch boost thing in custom kernels(something with franco I think). Anycase Franco also confirmed it nothing can be done for that at the moment.