Database Develop

YouTube no longer working properly... More like a slideshow?

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?

[Q] Slowdowns and freezes due to dhd_dpc/ksoftirqd

Hi all
On my european Samsung Galaxy I9000 (Switzerland, unbranded) running PDA:XFJP7/PHONE:XXJPP/CSC:XXJP7 after a random length of usage the system suddenly is extremely slow (any kind of input takes ~5 seconds until response) or even becomes completely unresponsive.
It also happens with USB connected, so I could check via ADB shell with top who's fault it is. The kernel process "dhd_dpc" is blocking the CPU. It seems wifi related (which I have activated). Checking in with dmesg there's a nonstop spam of "dhdsdio_htclk: HT Avail request error: -35".
It happened on all kinds of Froyo releases. I tried pretty much all official and leaked firmwares, as well as various ROMs and other customizations. It doesn't require an actual usage of wifi. Often it happens when I try to get the phone out of standby and then I just can't unlock it anymore because it doesn't take inputs anymore.
I now downgraded to an Eclair version (PDA:XWJM8/PHONE:XXJM4/CSC:XXJM1) and with it the problem is kinda the same but not exactly. On Eclair the process ksoftirqd/0 jumps to insanely high CPU usage but the system is a bit more responsive than the Froyo issue. There are two messages that appear over and over in dmesg "BUG eth0 code -19 qlen 5" and "dhd_start_xmit: xmit rejected due to dhd bus down status". On Eclair I also am able to "fix" the issue by turning WiFi off and on a few times. I was unable to do that on Froyo.
So I guess my question is... Is my phone broken? There's times when it works for a few hours no problem... Sometimes it just takes 20 minutes.
Thanks for reading and for any input. I'm kinda lost...
Psyraven

Touch screen problem on 4.2 roms?

Hello all,
I was wondering if anyone else is exhibiting this issue. Every once in a while when I try to tap on something, it doesn't register the first tap. As soon as I tap on it again it works. It doesn't happen all the time, but it happens randomly about 5 times a day. Not a big deal but it bothers me when it happens. I've tried ARHD 10.3 and sentinel 1.10 roms and they both exhibit this issue, which makes me think this is a problem with 4.2 roms since I don't recall this happening with 4.12 roms. I was able to replicate this by going to the home screen and holding the home button for a second as if you were trying to bring up the menu button, then immediately tap on anything. If you have the same problem then you will see that it doesn't register the first tap. If it doesn't then I guess it's an isolated issue with my setup. Can you guys check if you have the same issue? Thanks in advance!
Sent from my HTC One
Sent from my HTC One

Hrodriguez77 said:
Hello all,
I was wondering if anyone else is exhibiting this issue. Every once in a while when I try to tap on something, it doesn't register the first tap. As soon as I tap on it again it works. It doesn't happen all the time, but it happens randomly about 5 times a day. Not a big deal but it bothers me when it happens. I've tried ARHD 10.3 and sentinel 1.10 roms and they both exhibit this issue, which makes me think this is a problem with 4.2 roms since I don't recall this happening with 4.12 roms. I was able to replicate this by going to the home screen and holding the home button for a second as if you were trying to bring up the menu button, then immediately tap on anything. If you have the same problem then you will see that it doesn't register the first tap. If it doesn't then I guess it's an isolated issue with my setup. Can you guys check if you have the same issue? Thanks in advance!
Sent from my HTC One
Sent from my HTC One
Click to expand...
Click to collapse
There is a firmware package from 2.17.401.1 RUU available here http://forum.xda-developers.com/showpost.php?p=39225672&postcount=2
This update includes updated touch screen drivers which should sort out your problem.
However in order to flash this package you need to s-off your device so you may wish to stay as you are and live with it.

rider5512 said:
There is a firmware package from 2.17.401.1 RUU available here http://forum.xda-developers.com/showpost.php?p=39225672&postcount=2
This update includes updated touch screen drivers which should sort out your problem.
However in order to flash this package you need to s-off your device so you may wish to stay as you are and live with it.
Click to expand...
Click to collapse
Sorry if I wasn't too specific, but I'm s-off and I'm also on the newest firmware. I don't think the firmware is the issue because I was exhibiting this problem when I flashed ARHD 10.0, and this was before I flashed the newest firmware...which makes me believe it must be with roms based on 4.2.2. Anyone else seeing this issue?

Which sibuti
It's something I can live with, definitely not something I would want to downgrade to 4.1.2 roms for. I just want to see if maybe this is related to 4.2.2 roms. Thanks for the advice, unfortunately since I'm on the latest firmware, I don't think that is the issue. Am I alone with this issue here?

Hrodriguez77 said:
It's something I can live with, definitely not something I would want to downgrade to 4.1.2 roms for. I just want to see if maybe this is related to 4.2.2 roms. Thanks for the advice, unfortunately since I'm on the latest firmware, I don't think that is the issue. Am I alone with this issue here?
Click to expand...
Click to collapse
I don't think that this is a 4.2.2 issue as most people, myself included, found the touch screen to be more responsive after flashing the latest firmware.

It definitely is more responsive besides this one problem. Did you try that test I suggested to see if it happens to you? Holding the home button while on the home screen then try tapping on something? I'd like to know if anyone else can repeat this.
Sent from my HTC One

Hrodriguez77 said:
Hello all,
I was wondering if anyone else is exhibiting this issue. Every once in a while when I try to tap on something, it doesn't register the first tap. As soon as I tap on it again it works. It doesn't happen all the time, but it happens randomly about 5 times a day. Not a big deal but it bothers me when it happens. I've tried ARHD 10.3 and sentinel 1.10 roms and they both exhibit this issue, which makes me think this is a problem with 4.2 roms since I don't recall this happening with 4.12 roms. I was able to replicate this by going to the home screen and holding the home button for a second as if you were trying to bring up the menu button, then immediately tap on anything. If you have the same problem then you will see that it doesn't register the first tap. If it doesn't then I guess it's an isolated issue with my setup. Can you guys check if you have the same issue? Thanks in advance!
Sent from my HTC One
Sent from my HTC One
Click to expand...
Click to collapse
It doesn't register the tap because it is waiting for you to press the home button again to bring up multitasking. I also get the tap issue in the situation which you described, however it doesn't affect me

Ok thanks for your help, I'll live with it
Sent from my HTC One

Hrodriguez77 said:
Hello all,
I was wondering if anyone else is exhibiting this issue. Every once in a while when I try to tap on something, it doesn't register the first tap. As soon as I tap on it again it works. It doesn't happen all the time, but it happens randomly about 5 times a day. Not a big deal but it bothers me when it happens. I've tried ARHD 10.3 and sentinel 1.10 roms and they both exhibit this issue, which makes me think this is a problem with 4.2 roms since I don't recall this happening with 4.12 roms. I was able to replicate this by going to the home screen and holding the home button for a second as if you were trying to bring up the menu button, then immediately tap on anything. If you have the same problem then you will see that it doesn't register the first tap. If it doesn't then I guess it's an isolated issue with my setup. Can you guys check if you have the same issue? Thanks in advance!
Sent from my HTC One
Sent from my HTC One
Click to expand...
Click to collapse
I've noticed this too completely stock odexed 2.17 with firmware.

Is it on the stock 4.1.2 rom?
Sent from my HTC One

I don't think it's the new firmware since I noticed it happening before I updated it.
Sent from my HTC One

Touch disable after ROM......
Hello friends .
I have a device 7 " A13 cortex A8 processor with a 1.2 model for touch screen GSL2682 chip , this chip is on the edge of the flat cable that goes to the screen , I opened the unit to be able to identify him because no ROM tested works TS on my device , I currently have a JB 4.2.2 ROM and only the wi - fi and camera function , G- sensor and TS no .
I tried this driver across the web and have not found the driver for the touch ... you have something to tell us about ?
Thanks again .
This is my lsmod now
C : \ android- sdk \ sdk \ platform -tools > adb devices
List of devices attached
200804118822c70 device
C : \ android- sdk \ sdk \ platform -tools > adb shell
root @ android :/ # lsmod
lsmod
8188eu 767 523 0 - Live 0x00000000
8192cu 666 125 0 - Live 0x00000000
device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
ASIX 24601 0 - Live 0x00000000
sun5i_csi0 33355 0 - Live 0x00000000
gc0308 18608 1 - Live 0x00000000
61054 1 camera sun5i_csi0 , Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0 , Live 0x00000000
videobuf_core 20242 2 sun5i_csi0 , videobuf_dma_contig , Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 199911 69 - Live 0x00000000
ump 34161 17 mali , Live 0x00000000
nand 225000 8 - Live 0x00000000
root @ android :/ #

[Q] XT1072 is slow

Hello folks.
I couldn't manage to find any other suitable title for my thread because thats it. My phone is damn slow.
I bought it on expansys month ago already and returned it because it wasn't what I expected - slow, unresponsive, wifi problems, battery problems. I got new one like a week ago and it was same "crap".
So I decide to root it and flash custom ROM - CM 12.1 for THEA. Worked like a charm for a day (or less) but okay. Yesterday I started experiencing problems. All of sudden phone restarted and when it booted up, started to boot again - bootloop I guess.
Somehow I managed to get it working. "Apps X out of Y are updating", when it finished after like 2 reboots it worked.
But later in the day "Auto Rotate" didn't work anymore (gyro out or something), people couldn't reach me, I couldn't reach them (had to call like 3 times to make it work) and its slow.
I reinstalled ROM today and wont install any application for now to see how long will it work normal.
Its strange that this is second model that I got and its still laggy. Could it be in my google account something terribly wrong? Only apps that are essential to me were installed (like 25-30), only official.
Anyone have a slightest idea of what is going on?
Thanks

the moto e 2015 is the same, very laggy device. i think alot of it is because of the memory leak 5.0.2 has. try to use xposed lollipop and the memory leak module.

Somehow I can't install Xposed (tried "xposed-sdk22-arm-xxxxxx.zip"). Therefore no modules work.
Whats the point of "Android is starting. Optimizing app x of y" ? I get this every restart...

Xposed will work on 5.0.2. If your on 5.1 search xda for the alpha xposed for lollipop 5.1. Works fine here.

Yeah found it. Installed "Lollipop Memory Leak" module. Next few days will tell if phone is worth keeping.
Anyway this question its still hot, why "Android is starting. Optimizing app x of y" pops up after restart? I get feeling something is wrong all the time.

Mine is very slow too. Pretty annoying actually. And when I watch videos on Instagram or Facebook, the sound and video is never in sync.

I put xposed with the lollipop mem leak module on my rooted xt 1072 and also gravity box and I think things like sluggishness and overall speed has improved.

Yes this phone is so slow it's painful. I got this phone because my nexus 6 is in for repair and as soon as it's back I'm returning this poor excuse for a phone. I wasn't expecting flagship performance but my god this thing is so so slow, and I get a horrible hiss when I'm make or recieve a call.

Logcat - Entryindex is beyond type entrycount

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.