I have the mx player pro. recently acquired the LG G Pad 8.0 x. I could not get the mx player to play my gopro 4 silver videos at 2.7k 30p (protune turned on) using hw or hw+. the software decoder is not able to playback without serious lag. I searched the forum for LG G pad but didn't find any hits regarding this. hoping there could be a workaround or updates to allow hw or hw+ playback.
rcboosted said:
I have the mx player pro. recently acquired the LG G Pad 8.0 x. I could not get the mx player to play my gopro 4 silver videos at 2.7k 30p (protune turned on) using hw or hw+. the software decoder is not able to playback without serious lag. I searched the forum for LG G pad but didn't find any hits regarding this. hoping there could be a workaround or updates to allow hw or hw+ playback.
Click to expand...
Click to collapse
It means your device doesn't support hardware acceleration for that profile. Can you collect the bugreport immediately after playing the video that has issues & share here..?
Sent from my SM-G900H using Tapatalk
ktsamy said:
It means your device doesn't support hardware acceleration for that profile. Can you collect the bugreport immediately after playing the video that has issues & share here..?
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. Attached is the bug report. I played the video using software decoder, then tried to switch to HW, it tells me HW decoder is not supported, and I pulled the report right after.
rcboosted said:
Thank you for the reply. Attached is the bug report. I played the video using software decoder, then tried to switch to HW, it tells me HW decoder is not supported, and I pulled the report right after.
Click to expand...
Click to collapse
Your logs are insufficient. It only contains the logs when MX Player has closed the video.
Kindly save the bug report as soon as you open the video in HW/HW+ decoder.
Sent from my SM-G900H using Tapatalk
double post...
ktsamy said:
Your logs are insufficient. It only contains the logs when MX Player has closed the video.
Kindly save the bug report as soon as you open the video in HW/HW+ decoder.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Ok I did it again, I guess I didn't do it right. I opened the file, clicked on HW+, clicked off the prompt, ran the report. I did it both for HW and HW+
Just wondering if the new logs I pulled are sufficient.
rcboosted said:
Just wondering if the new logs I pulled are sufficient.
Click to expand...
Click to collapse
It's still same.
Sent from my SM-G900H using Tapatalk
ktsamy said:
It's still same.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
I'm not sure what I'm doing wrong. I open mx player, open the video, it starts to play in sw, i switch to hw, it immediately gave me the error message, I click away(I have to) I open the menu to create the bug report. is there any step that I missed? what else can I do to get you an usable report?
rcboosted said:
I'm not sure what I'm doing wrong. I open mx player, open the video, it starts to play in sw, i switch to hw, it immediately gave me the error message, I click away(I have to) I open the menu to create the bug report. is there any step that I missed? what else can I do to get you an usable report?
Click to expand...
Click to collapse
The method is right. It seems that either your system uses low log buffer or any other process is generating more logs. Logs in android memory is limited. So, when the buffer overflows it will erase old logs in order to make space for new logs.
In Developer Options, Increase the Log Buffer Size to Max value. In my device it's 16M. Then repeat the same procedure you have used earlier to collect the bug report. It may be helpful.
I will check it. If it's not yet complete, only option is connect to PC & collect the logs through ADB.
ktsamy said:
The method is right. It seems that either your system uses low log buffer or any other process is generating more logs. Logs in android memory is limited. So, when the buffer overflows it will erase old logs in order to make space for new logs.
In Developer Options, Increase the Log Buffer Size to Max value. In my device it's 16M. Then repeat the same procedure you have used earlier to collect the bug report. It may be helpful.
I will check it. If it's not yet complete, only option is connect to PC & collect the logs through ADB.
Click to expand...
Click to collapse
I turned on developer options and changed the log buffer size to 16M as you have then ran the report. The size is still very small, not sure if that's an indication of anything. Ran it twice.
rcboosted said:
I turned on developer options and changed the log buffer size to 16M as you have then ran the report. The size is still very small, not sure if that's an indication of anything. Ran it twice.
Click to expand...
Click to collapse
The current report has enough logs. But, the playback has failed with a uncommon error code (9001). The error code is not defined in standard android mediaplayer api. Probably the ROM developer or OEM might have defined the custom error. So, It's very hard to identify the exact reason.
For me it looks like, the profile is not supported by the Hardware Decoders.
As I have pointed in many other places, without hardware acceleration, playback may laggy depends upon the video parameters.
Sent from my SM-G900H using Tapatalk
ktsamy said:
The current report has enough logs. But, the playback has failed with a uncommon error code (9001). The error code is not defined in standard android mediaplayer api. Probably the ROM developer or OEM might have defined the custom error. So, It's very hard to identify the exact reason.
For me it looks like, the profile is not supported by the Hardware Decoders.
As I have pointed in many other places, without hardware acceleration, playback may laggy depends upon the video parameters.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
That's unfortunate. Since you don't have the definition of these uncommon error code, is there anything that can be done to get the code and possible get a profile to work?
rcboosted said:
That's unfortunate. Since you don't have the definition of these uncommon error code, is there anything that can be done to get the code and possible get a profile to work?
Click to expand...
Click to collapse
Try contacting LG about this. They could release an update to patch this. http://www.lg.com/us/support-mobile/lg-LGV521WG
Related
Hi,
with WiMo i was able to play podcasts (h264/aac, 368x208, ~200kBit/s) somewhat smooth with TCMP. With android i get - well - with some luck a frame per minute. I would have said its because of a incomplete/non-optimized GPU-Driver but Youtube (SD) plays fine so for me this looks more like a codec/app-issue. Has anyone already looked for a solution? Any tips on codecs/apps that should work?
SD works, yes. HD/HQ youtube does not however, and I think it's related to a scaling issue.
We're not done with the port... I think this is a pretty minor bug considering the other major ones we have out there....
arrrghhh said:
SD works, yes. HD/HQ youtube does not however, and I think it's related to a scaling issue.
Click to expand...
Click to collapse
...hm… for me exactly this looked like a codec-thing… i dont know the mobile side but for pc i remember something like VP6 for SD and X264 for HD on Youtube. But thanks for the tip, i'll look into this direction too.
arrrghhh said:
We're not done with the port...
Click to expand...
Click to collapse
…and it will never be completely done - otherwise there would be no need for our lovely legacy-forums here
arrrghhh said:
I think this is a pretty minor bug considering the other major ones we have out there....
Click to expand...
Click to collapse
As you already said in another thread: Everyone has his own priorities
Just see this thread as my notepad - i collect my results/ideas here, if someone has made own tests he can add his results and if someone wants to have a look on his own he knows what has been tried already…
B2T: With the described movie i have about 10-20% free CPU-cycles so this should not be the bottleneck. hw3d has no effect (guess this doesnt really affect 2d acceleration). Changing from fullscreen/stretched to original size showed also no difference
adlerweb said:
Just see this thread as my notepad - i collect my results/ideas here, if someone has made own tests he can add his results and if someone wants to have a look on his own he knows what has been tried already…
B2T: With the described movie i have about 10-20% free CPU-cycles so this should not be the bottleneck. hw3d has no effect (guess this doesnt really affect 2d acceleration). Changing from fullscreen/stretched to original size showed also no difference
Click to expand...
Click to collapse
Not a bad idea, I'd like to see this bug squashed.
I've heard it was a scaling issue - have you tried different resolutions? I know someone tried the native resolution of our RHOD, but that didn't work either... I guess I'd be surprised if it is codec, as you can get frozen frames on YouTube HQ and audio plays just fine. I am by no means an expert here tho .
arrrghhh said:
Not a bad idea, I'd like to see this bug squashed.
I've heard it was a scaling issue - have you tried different resolutions? I know someone tried the native resolution of our RHOD, but that didn't work either... I guess I'd be surprised if it is codec, as you can get frozen frames on YouTube HQ and audio plays just fine. I am by no means an expert here tho .
Click to expand...
Click to collapse
I am no expert either but would not the codec be contained in the software such as Utube. And the Multimedia architecture would mostly bypass the Processor. So the problem to me would seem to be routing and timing issue. Thus the beggining frames play but stop due to the loss of coordination.
BigOnes69 said:
I am no expert either but would not the codec be contained in the software such as Utube. And the Multimedia architecture would mostly bypass the Processor. So the problem to me would seem to be routing and timing issue. Thus the beggining frames play but stop due to the loss of coordination.
Click to expand...
Click to collapse
I don't even get any frames to play at the beginning.
It starts with a black screen with audio...
If I skip ahead, I can randomly get freezes of images, but that's about it.
arrrghhh said:
I don't even get any frames to play at the beginning.
It starts with a black screen with audio...
If I skip ahead, I can randomly get freezes of images, but that's about it.
Click to expand...
Click to collapse
What you say supports what I am saying about routing and timing. I am thinking in general terms not specifics and I am no expert.
BigOnes69 said:
What you say supports what I am saying about routing and timing. I am thinking in general terms not specifics and I am no expert.
Click to expand...
Click to collapse
I would think its the processors job to coordinate the frame of reference for the timing. The actual MMS stuff would use that frame of reference to process the video according to the codec provided in the software. The routing and or timing could be screwed because HTC needs a way to get around patent laws. The could have done something as simple as changed polarity or phase or something more complicated as recode with another chip. The audio would works because its simple to process. Our drivers are not doing what needs to be done to process the information. It would have nothing to do with the codec which is contained in the software. Like I said I am guessing.
BigOnes69 said:
I would think its the processors job to coordinate the frame of reference for the timing. The actual MMS stuff would use that frame of reference to process the video according to the codec provided in the software. The routing and or timing could be screwed because HTC needs a way to get around patent laws. The could have done something as simple as changed polarity or phase or something more complicated as recode with another chip. The audio would works because its simple to process. Our drivers are not doing what needs to be done to process the information. It would have nothing to do with the codec which is contained in the software. Like I said I am guessing.
Click to expand...
Click to collapse
Then again the Architecture in our older phones might not be fast enough to process the HQ resolutions.
No, this isn't a question of processing power, it's a matter of having the right codecs installed. I've seen Youtube HQ working on my phone before, running one of tiad8's FroyoX builds with camera kernel, months ago.
The behavior you see where you can skip around and see one good frame, but otherwise nothing, is caused by the actual encoding of the video, and the current codec lacking support for it. (The difference between B frames, I frames, and P frames, if you care to look that up...)
highlandsun said:
No, this isn't a question of processing power, it's a matter of having the right codecs installed. I've seen Youtube HQ working on my phone before, running one of tiad8's FroyoX builds with camera kernel, months ago.
The behavior you see where you can skip around and see one good frame, but otherwise nothing, is caused by the actual encoding of the video, and the current codec lacking support for it. (The difference between B frames, I frames, and P frames, if you care to look that up...)
Click to expand...
Click to collapse
Interesting.
So what do we need to do to get the codec support? I'm assuming the kernel clocks are finally right as well...
found it.
http://www.youtube.com/watch?v=mYW1DIi4ZzY
yankees2450 said:
found it.
http://www.youtube.com/watch?v=mYW1DIi4ZzY
Click to expand...
Click to collapse
That is based off of Tiads cut and paste Blazn if I am correct which was good for video playback but everything else was buggy. This proves HQ can work on our phones.
My question here is wouldnt the Codec that was required by the utube app. be contained within that app. or if it was not when it tried to play back and the codec was missing you would get nothing or a reference to download the required codec such as happens with other operating systems.
Or if the codec is contained in our current version intact. Then it is not referencing the codec properly which goes back to what I originally said about timing and the coordination with the MMS architecture on the phone. It looks as though Tiad had found the proper channeling. Did he leave anyone any information about this before he left this forumn?
BigOnes69 said:
That is based off of Tiads cut and paste Blazn if I am correct which was good for video playback but everything else was buggy. This proves HQ can work on our phones.
My question here is wouldnt the Codec that was required by the utube app. be contained within that app. or if it was not when it tried to play back and the codec was missing you would get nothing or a reference to download the required codec such as happens with other operating systems.
Or if the codec is contained in our current version intact. Then it is not referencing the codec properly which goes back to what I originally said about timing and the coordination with the MMS architecture on the phone. It looks as though Tiad had found the proper channeling. Did he leave anyone any information about this before he left this forumn?
Click to expand...
Click to collapse
He never gave anyone anything useful from his builds.
He was just slapping stuff together, and would see what stuck to the wall.
I heard people had issues with his builds on HQ youtube, and I even tested his junk and wasn't able to get HQ to work... so I think it's just more BS from him.
yankees2450 said:
another junk from tiad8
could this be true?
http://www.neopeek.com/viewtopic.php?f=84&t=6544
Click to expand...
Click to collapse
There's a reason he's banned here. Let's not repost more of his crap here, thanks.
arrrghhh said:
I've heard it was a scaling issue - have you tried different resolutions?
Click to expand...
Click to collapse
Well... Most of my podcast have different resolutions and none worked so far. Also should scaling not be disabled when the Player is set to "original size"?
BigOnes69 said:
I am no expert either but would not the codec be contained in the software such as Utube.
Click to expand...
Click to collapse
I dont know for youtube but most 3rd party video-players i've seen say that supported codecs are device dependent so i guess they are in the rootfs, not the app.
BigOnes69 said:
because HTC needs a way to get around patent laws
Click to expand...
Click to collapse
OK, maybe, but afair do most companys not charge people/companys for playback - only encoding… And "free" codecs like theora or webm would not be affected
BigOnes69 said:
Then again the Architecture in our older phones might not be fast enough to process the HQ resolutions.
Click to expand...
Click to collapse
As said: 20% cpu left and works on Wimo -
I've managed to get "working" video with ffmpeg's default avi-output (think it was divx/mp3) but colors where disorted. My android died yesterday and i had no time to reinstall so i could not test further atm.
adlerweb said:
OK, maybe, but afair do most companys not charge people/companys for playback - only encoding… And "free" codecs like theora or webm would not be affected
Click to expand...
Click to collapse
I think I remember reading the issue the with getting decent video playback wit the MSM GPU is is getting information on the hardware. The codec used to play HQ video on Windows mobile comes from HTC and is written specifically for the MSM7x chipset using proprietary information - information which is not available to everyone, or can only become available for a price and an NDA.
Perhaps there is binary blob that can be used?
toadlife said:
I think I remember reading the issue the with getting decent video playback wit the MSM GPU is is getting information on the hardware. The codec used to play HQ video on Windows mobile comes from HTC and is written specifically for the MSM7x chipset using proprietary information - information which is not available to everyone, or can only become available for a price and an NDA.
Perhaps there is binary blob that can be used?
Click to expand...
Click to collapse
Perhaps a binary blob could be dug up, but we couldn't use it in the AOSP builds. Only custom builds would be able to use it, or individuals will just have to integrate it themselves.
arrrghhh said:
Perhaps a binary blob could be dug up, but we couldn't use it in the AOSP builds. Only custom builds would be able to use it, or individuals will just have to integrate it themselves.
Click to expand...
Click to collapse
That would be fine with me.
toadlife said:
That would be fine with me.
Click to expand...
Click to collapse
Ok... My point is, source is preferred.
If we can't get source, so be it - but a proprietary blob does very little good in the scope of this type of project. I want everyone to have the best Android experience possible, I don't want just a few builds working correctly and others borked. That sucks.
Anyone got the new Netflix app to work on their TP2?
Sent from my TP2 using XDA App
so far i have working audio in the app however no video =(
nasapunk88 said:
so far i have working audio in the app however no video =(
Click to expand...
Click to collapse
Same here, even with highlandsun's video codecs it seems we can't play the video.
rpierce99 said:
Same here, even with highlandsun's video codecs it seems we can't play the video.
Click to expand...
Click to collapse
Probably due to same issue with HQ Youtube videos huh?
How can I bypass the "This device is not supported by Netflix" that I get when clicking on a title on my Instant Queue, so I can see if it is working or if it just audio only. Is there a way to spoof the app into thinking I am on a supported phone? If so, please tell me how to do it. Thanks.
There is an apk that will not check for device compatiblity but yeah no video. For me it plays audio and then it kicks out back to the queue. I wish it worked. Anything we can do?
Can't tell anything without knowing what codec / format Netflix is using in this app. I'm sure they're using H.264, but if it's not H.264 Baseline Profile then our phone hardware can't decode it. And if it's larger than 640x360 resolution, our current codec can't handle it.
I don't have a Netflix account so I haven't tried to see what formats they're using.
The current codec we have is written in C++ with threads. I'd say that's at least a 10% performance hit right there; if it was written well, in straight C, it would probably have achieved the 800x480 that Qualcomm's original spec claimed.
Netflix released an updated app today with support for more devices. I get the main screen, then loading, then the playback screen and nothing .... black screen. Nerts.
Carld256 said:
Netflix released an updated app today with support for more devices. I get the main screen, then loading, then the playback screen and nothing .... black screen. Nerts.
Click to expand...
Click to collapse
I'm not sure what 'nerts' are, but the new video playback libs might be necessary... Anyone with those new libs given this new app a shot?
arrrghhh said:
I'm not sure what 'nerts' are, but the new video playback libs might be necessary... Anyone with those new libs given this new app a shot?
Click to expand...
Click to collapse
nerts = nuts = really mild profanity
I actually have the new libs installed already. I'm running a RHOD500 with the latest kernel, overclocked to 710 Mhz, in case that matters.
Carld256 said:
nerts = nuts = really mild profanity
I actually have the new libs installed already. I'm running a RHOD500 with the latest kernel, overclocked to 710 Mhz, in case that matters.
Click to expand...
Click to collapse
So HQ YouTube works?
Why not just say 'nuts'?
arrrghhh said:
So HQ YouTube works?
Why not just say 'nuts'?
Click to expand...
Click to collapse
HQ YouTube works more or less. There's a little stutter sometimes, and some HQ videos start and then stop after 5 or 10 seconds, and some others play just fine. Oh, and the libs fixed video playback of the mp4 movies I already had on my device.
Weird thing is, YouTube under WinMo refuses to play HQ videos at all.
Nerts is funnier.
Carld256 said:
HQ YouTube works more or less. There's a little stutter sometimes, and some HQ videos start and then stop after 5 or 10 seconds, and some others play just fine. Oh, and the libs fixed video playback of the mp4 movies I already had on my device.
Weird thing is, YouTube under WinMo refuses to play HQ videos at all.
Click to expand...
Click to collapse
IIRC, WinMo plays HQ YouToobs flawlessly.
Carld256 said:
Nerts is funnier.
Click to expand...
Click to collapse
If you say so, lol.
arrrghhh said:
IIRC, WinMo plays HQ YouToobs flawlessly.
Click to expand...
Click to collapse
It used to. Some time back YouTube changed something, and now HQ videos play without sound (I was thinking they didn't play at all). Supposedly you can fix this by changing your network to "media," but I don't have that option any more since I upgraded to 6.5.
Carld256 said:
It used to. Some time back YouTube changed something, and now HQ videos play without sound (I was thinking they didn't play at all). Supposedly you can fix this by changing your network to "media," but I don't have that option any more since I upgraded to 6.5.
Click to expand...
Click to collapse
I just rebooted to see. Worked fine for me, I'm on 6.5 - but I used Opera... I don't know if there's some app that I should be using, perhaps it wasn't truly HQ.
Either way, if it used to then there shouldn't be anything limiting the hardware. Seems hyc went thru all that pretty thoroughly tho.
arrrghhh said:
I just rebooted to see. Worked fine for me, I'm on 6.5 - but I used Opera... I don't know if there's some app that I should be using, perhaps it wasn't truly HQ.
Either way, if it used to then there shouldn't be anything limiting the hardware. Seems hyc went thru all that pretty thoroughly tho.
Click to expand...
Click to collapse
I'm using Dot's latest rom dated 04-23-11 and it does play HQ youtube flawlesly, unlike NRG's which for some reason have a little choppy sound while the video plays, or it could just be my old tilt2
arrrghhh said:
I just rebooted to see. Worked fine for me, I'm on 6.5 - but I used Opera... I don't know if there's some app that I should be using, perhaps it wasn't truly HQ.
Either way, if it used to then there shouldn't be anything limiting the hardware. Seems hyc went thru all that pretty thoroughly tho.
Click to expand...
Click to collapse
I was using the HTC YouTube app. I tried it on two different 6.5 TP2s and they both do the same thing, HQ video plays, but no sound.
And your right. I know the hardware is capable, just somewhere along the way something in the software got screwed up on YouTube's end or mine.
Anybody try changing the build.prop to HTC vision or desire z or any of the phones that works with Netflix that's how we have it working already in my section
Sent from my LG-P999 using XDA App
I don't think the new version checks to see what model you're running.
The new Netflix app has a LOT of compatibility issues.
They still can't get it working on most Huawei S7 ROMs, and that device can do 720p easily.
Credit to styckx for starting the previous one.
STOCK ROM ONLY
Report bugs and/or solutions.
Google's Play Music - Audio stutters when sleeping and playing .flac music files. (Pre-existing from KRT160)
AOSP Browser - Force closes when attempting to open incognito tab. (Pre-existing from KRT160)
Hi,
is the settings UI bug fixed (tablet instead of phone UI)?
thx
odoggy said:
Hi,
is the settings UI bug fixed (tablet instead of phone UI)?
thx
Click to expand...
Click to collapse
Nope...
BT headset audio extremely loud by default. Gets hinky as you try and lower it (raising it seems to work fine).
Only one device to test it with so far (LG TONE 730).
Works fine with HTC One and Nexus 10 on 4.3.
Sent from my Nexus 10 using Tapatalk 4
DevilMR said:
AOSP Browser - Force closes when attempting to open incognito tab. (Pre-existing from KRT160)
Click to expand...
Click to collapse
Confirmed
Sent from my Nexus 10 using Tapatalk 4
FLAC Files Distorted
FLAC files keep skipping and are coming out very distorted on 4.4, did a full restore to both builds of 4.4 and the issue still stands with play music and even winamp. Is there any solution to this?
Exchange email will not sync after initial setup. Same issue on my N4 running 4.4 KRT16S.
HillsRider said:
Exchange email will not sync after initial setup. Same issue on my N4 running 4.4 KRT16S.
Click to expand...
Click to collapse
Known issue with Kitkat
http://forum.xda-developers.com/showthread.php?t=2512237
Sent from my Nexus 10 using xda app-developers app
unome1233 said:
FLAC files keep skipping and are coming out very distorted on 4.4, did a full restore to both builds of 4.4 and the issue still stands with play music and even winamp. Is there any solution to this?
Click to expand...
Click to collapse
I am currently using Poweramp to play FLAC files, no skip or stuttering. Works OK when sleeping also.
Getting parse Error when trying to install apks outside of the market, no matter what apk. Unknown soures enabled of ourse.
Stock KRTS16, BL Unlocked, rooted.
Nevermind, looks resolved, no idea what I did to resolve it though...
The OTA Kitkat update appears to have broken video streaming playback (on my local network). For whatever reason, it's now very choppy and it is impossible to watch anything.
Anyone else having the same experience?
Might be just me, but when sending an email via the stock email app it will only give you the option of attaching either a picture or video? You can "share" a file via email and it will attach okay, but if you are say, replying to an email and need to attach a PDF there is no option to attach anything other than picture or video? Used to be just "attach file" did it not?
I was browsing using opera. After a crash, I did try using chrome. It crashed then and the device rebooted.
Did exeperience this once till now.
Is anyone else having issues with the screen timeout? I have mine set to 1 minute and my screen never turns off.
Hi,
Whenever i try to stream ANY video (doesn't matter if it's YouTube or not), it randomly pauses every 10-20 seconds.
This is very frustrating.
Lenovo IdeaTab S6000-F
Please help!
David
ViolentRockstar said:
Whenever i try to stream ANY video (doesn't matter if it's YouTube or not), it randomly pauses every 10-20 seconds.
Click to expand...
Click to collapse
This is normal behaviour when your internet speed is not sufficient to load all data in the required time, it's called buffering.
orville87 said:
This is normal behaviour when your internet speed is not sufficient to load all data in the required time, it's called buffering.
Click to expand...
Click to collapse
Hi,
I'm sure that that is not the problem.
I know what buffering is etc. (i'm not a noob with this stuff ).
The thing is that, even though the video is buffered completely, it just pauses. It doesn't matter how long i let it buffer.
Thanks for responding tho
PS: My internet speed is sufficient (35-40 mbps).
ViolentRockstar said:
Hi,
I'm sure that that is not the problem.
I know what buffering is etc. (i'm not a noob with this stuff ).
The thing is that, even though the video is buffered completely, it just pauses. It doesn't matter how long i let it buffer.
Thanks for responding tho
Click to expand...
Click to collapse
Hmm, maybe you could install the MX Player codecs, which solve some strange video decoding bugs. Otherwise you can try to upload a log file, so others can help you with this issue.
orville87 said:
Hmm, maybe you could install the MX Player codecs, which solve some strange video decoding bugs. Otherwise you can try to upload a log file, so others can help you with this issue.
Click to expand...
Click to collapse
The codex didn't fix it (i'm afraid it only worsened).
I'll try to upload the logs, but you'll need to refresh my memory .
Thanks for responding!
ViolentRockstar said:
The codex didn't fix it (i'm afraid it only worsened).
I'll try to upload the logs, but you'll need to refresh my memory .
Thanks for responding!
Click to expand...
Click to collapse
Here you go
How to logcat
orville87 said:
Here you go
How to logcat
Click to expand...
Click to collapse
Thanks,
alogcat only creates empty logs however...
Any tips?
ViolentRockstar said:
Thanks,
alogcat only creates empty logs however...
Any tips?
Click to expand...
Click to collapse
Hmm, no, sorry
orville87 said:
Hmm, no, sorry
Click to expand...
Click to collapse
I guess i'm stuck then
ViolentRockstar said:
I guess i'm stuck then
Click to expand...
Click to collapse
I personally use CatLog instead of aLogcat. Maybe it will help.
orville87 said:
I personally use CatLog instead of aLogcat. Maybe it will help.
Click to expand...
Click to collapse
That worked!
Thanks!
Here's the log
ViolentRockstar said:
That worked!
Thanks!
Here's the log
Click to expand...
Click to collapse
Hmm, there is a strange line in your log:
04-15 14:54:43.698 E/MtkOmxVdec(142): MtkOmxVdec::GetConfig Unknown config index: 0x0700000F
I searched the web for it and one solution seems to be installing the latest VLC Player for Android as the problem seems to be a broken/missing video codec. But I am wondering how this could be the problem as you have been able to play the video file (although with random pauses).
orville87 said:
Hmm, there is a strange line in your log:
04-15 14:54:43.698 E/MtkOmxVdec(142): MtkOmxVdec::GetConfig Unknown config index: 0x0700000F
I searched the web for it and one solution seems to be installing the latest VLC Player for Android as the problem seems to be a broken/missing video codec. But I am wondering how this could be the problem as you have been able to play the video file (although with random pauses).
Click to expand...
Click to collapse
Yeah,
Installing the 'VLC for android' app didn't work unfortunately.
Thanks for spending so much time on this problem
ViolentRockstar said:
Yeah,
Installing the 'VLC for android' app didn't work unfortunately.
Thanks for spending so much time on this problem
Click to expand...
Click to collapse
Hmm, VLC was my best bet I hope, somebody else with more experience in Android is able to help you :good:
Hi I have the same problem with pausing youtube and this is not the internet, I made a log from catlog and there is an hwcomposer v1.0 timed out. Anybody knows how can I solve this problem?
Video randomly pause issue
I am using LG G3 Cat 6 F460-L having marshmallow, while playing any video on facebook ,youtube, dailymotion it randomly pauses either i use LTE or WIFI.
Also tried:
VLC
MX player
MX Player codecs
Clear Cache
Enable/Disable Airplane Mode.
All Apps are up to date.
But not fixed yet.
I appreciate if any one suggest some solution.Thanks.
I'm hoping someone could help me with a video problem I'm having. I use my Touchpad mostly as a wall mounted tablet to display a security camera. I'm currently using the Evervolv 7.1.2 Android Nougat Rom which I love and it works so smooth! However, when using the Wyze Labs app that goes with my cameras and also when trying the Tiny Cam Pro app, when trying to enable Hardware Decoder in the apps for video, it fails. It forces me to use the software decoder instead, which works, but is laggy and stutters at times.
I also tried the LineageOS 14.1 Android Nougat 7.1.2 by invisiblek Rom and had the exact same issue.
HOWEVER.... When using the Dirty Unicorns v8.1 Android Oreo by Flintman Rom, the hardware decoder works in both apps with that Rom, but the Touchpad doesn't run nearly as quick and smooth for me as it does with Evervolv 7.1.2
Does anyone have any idea on how to get the hardware decoder to work in either 7.1.2 Rom.
By the way, I'm also using the Max Extreme optimize 1782 if that makes any difference.
mlfc52 said:
I'm hoping someone could help me with a video problem I'm having. I use my Touchpad mostly as a wall mounted tablet to display a security camera. I'm currently using the Evervolv 7.1.2 Android Nougat Rom which I love and it works so smooth! However, when using the Wyze Labs app that goes with my cameras and also when trying the Tiny Cam Pro app, when trying to enable Hardware Decoder in the apps for video, it fails. It forces me to use the software decoder instead, which works, but is laggy and stutters at times.
I also tried the LineageOS 14.1 Android Nougat 7.1.2 by invisiblek Rom and had the exact same issue.
HOWEVER.... When using the Dirty Unicorns v8.1 Android Oreo by Flintman Rom, the hardware decoder works in both apps with that Rom, but the Touchpad doesn't run nearly as quick and smooth for me as it does with Evervolv 7.1.2
Does anyone have any idea on how to get the hardware decoder to work in either 7.1.2 Rom.
By the way, I'm also using the Max Extreme optimize 1782 if that makes any difference.
Click to expand...
Click to collapse
I can not test those Apps as I do not have any way to connect to any security cameras. I do know that the Tablet's video recording capabilities is better with Oreo and Pie.
It maybe the Kernel or the Android ROMs for those version. Did you try setting the Tablet as posted on this guide:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
You mentioned the use of MaXtreme, but did you flash Oreo or Pie using ROM Reducer and also the 1836 Speed?
All ROMs have the same settings applied at the Kernel level and should perform very similar.
HP_TOUCHPAD said:
I can not test those Apps as I do not have any way to connect to any security cameras. I do know that the Tablet's video recording capabilities is better with Oreo and Pie.
It maybe the Kernel or the Android ROMs for those version. Did you try setting the Tablet as posted on this guide:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
You mentioned the use of MaXtreme, but did you flash Oreo or Pie using ROM Reducer and also the 1836 Speed?
All ROMs have the same settings applied at the Kernel level and should perform very similar.
Click to expand...
Click to collapse
I think it may have something to do with the MaXtreme. I tried several ROMs over the weekend in all sorts of combos, some with the ROM reducer and also with the 1836 speed. Anyway, last night I tried one more time with the DU 13 Pie ROM and the hardware decoder worked with both apps. However, after I got it running, I flashed the MAX_1836_CPU_Universal_Optimize_Swap Zip that goes with that ROM and the Hardware decoder stopped working again on both apps. After a quick dirty flash of the ROM without the MaX_1836 , HW Decoder came back. I haven't tried Rom Reducer yet on this ROM, but I may just leave it as is since I'm really only using this particular tablet as a wall mounted display, so as long as it works to display the cameras reliably, I don't need the tablet do work well with anything else.
Thanks for the reply!
mlfc52 said:
I think it may have something to do with the MaXtreme.
All the optimized Kernels improve the CPU frequency ( overclock ) with the most fastest possible settings. But it does not disable or remove any features.
I tried several ROMs over the weekend in all sorts of combos, some with the ROM reducer and also with the 1836 speed. Anyway, last night I tried one more time with the DU 13 Pie ROM and the hardware decoder worked with both apps. However, after I got it running, I flashed the MAX_1836_CPU_Universal_Optimize_Swap Zip that goes with that ROM and the Hardware decoder stopped working again on both apps. After a quick dirty flash of the ROM without the MaX_1836 , HW Decoder came back. I haven't tried Rom Reducer yet on this ROM, but I may just leave it as is since I'm really only using this particular tablet as a wall mounted display, so as long as it works to display the cameras reliably, I don't need the tablet do work well with anything else.
It is great to know that is working one way or the other and that is what's so great about the Tablet, many different options available that still makes it usable!
Thanks for the reply!
Click to expand...
Click to collapse
Out of curiosity I installed the Tiny Cam App using Evervolv 7.1.2 ( ROM Reducer) with MaXtreme 1836.
Attached are the screenshot that shows H.264/H.265 decoder is available . I do not know why it does not work for you, but it should work for everyone.
Click HERE for the Installation Guide
Also I use Evervolv 7.1.2 with the same set up to record and playback video in 2592x1944 resolution over WiFi.
Click HERE for the WiFi endoscope post
HP_TOUCHPAD said:
Out of curiosity I installed the Tiny Cam App using Evervolv 7.1.2 ( ROM Reducer) with MaXtreme 1836.
Attached are the screenshot that shows H.264/H.265 decoder is available . I do not know why it does not work for you, but it should work for everyone.
Click HERE for the Installation Guide
Also I use Evervolv 7.1.2 with the same set up to record and playback video in 2592x1944 resolution over WiFi.
Click HERE for the WiFi endoscope post
Click to expand...
Click to collapse
The decoder shows as available however, when I enabled either Hardware or Hardware+ and then connect to a live camera stream, a message pops up that says something like "Hardware Decoder H264 has failed, Switching to Software decoder" Then the camera video plays using the software decoder. That works. but lags 15 seconds and skips. In the Wyze app which is by the camera manufacturer, Enable Hardware decoder is an option in the app account menu. When enabled, the camera does connect, but the video is just a black screen along with the counting bitrate. It does play with hardware decoder switched off. With the Wyze app, lot's of Android devices, especially older devices need the hardware decoder because without it, the live video lags like 20 seconds and stutters. There were tons of complaints on the Wyze forums for a while when Wyze temporarily removed the hardware decoder option due to some change in Android about a year ago.
mlfc52 said:
The decoder shows as available however, when I enabled either Hardware or Hardware+ and then connect to a live camera stream, a message pops up that says something like "Hardware Decoder H264 has failed, Switching to Software decoder" Then the camera video plays using the software decoder. That works. but lags 15 seconds and skips. In the Wyze app which is by the camera manufacturer, Enable Hardware decoder is an option in the app account menu. When enabled, the camera does connect, but the video is just a black screen along with the counting bitrate. It does play with hardware decoder switched off. With the Wyze app, lot's of Android devices, especially older devices need the hardware decoder because without it, the live video lags like 20 seconds and stutters. There were tons of complaints on the Wyze forums for a while when Wyze temporarily removed the hardware decoder option due to some change in Android about a year ago.
Click to expand...
Click to collapse
In Hardware Decoder the GPU will be doing the work, in Software it will be the CPU. The codec is very important when it comes to playback.
I have found the MX Player App is the best to play videos. I downloaded a video to test from this site:
https://www.appsloveworld.com/sample-hd-video-download/
Tested on Evervolv 7.1.2 and Pie with the same results, the attached screenshots are of 7.1.2. In both Tablets the MaXtreme is use as it provides the fastest CPU.
Not all videos, or streams are encoded the same or using a codec that will work using the GPU ( Hardware plus decoder ). It gets complicated and specially on this old device.
If the wrong encoding option is selected then it will not play, but software using the CPU will work. Using the highest CPU frequency the Tablet can handle should help with software decoder.