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.
Related
As I go through yet another build.prop market fix, I can't help but wonder: is there a build.prop market fix (or any kind of fix) that gives you the best of both worlds (all 2.x and 3.x apps are visible in the market, working Flash Player, runs 3.x apps and maybe even Netflix)? If not, anything close to it (I can live without running 3.x apps)?
P.S. - If possible, I prefer to stick with Froyo/2.2 since the display quality and video playback & hardware acceleration performance has been superior to 2.3.x and 3.x ROMs in my experiences so far.
HTC Vision gets Netflix good for GB. I also don't notice anything missing from the market. Guess you could use vegan 5.1.1 and throw in the Netflix patch and then mod build.prop and see what happens. Breaks YouTube app by the by but browser viewing still works peachy.
You can't run 3.0 (Honeycomb) code on 2.3 (Gingerbread) or 2.2 (Froyo).
No build.prop will ever give you that.
The build.prop is the properties of your build....ie what OS, manufacturer, some basic settings and such. Edits of it may allow you to see certain things in the Market but seeing them doesn't mean they will install or run.
If you want Netflix (and now Hulu Plus), CM7.03 stable is your best option. It also sees nearly everything that will function on the tablet in the Market.
I miss nothing from VEGAn5.1.1 now that I'm on CM7.03. I've gained a ton (better stability, WiFi location services, better market (no fixes needed) access, Netflix, etc...
I keep hearing CM 7.0.3 is the best option. It still doesn't have native Nvidia drivers, correct?
DiGiTY said:
I keep hearing CM 7.0.3 is the best option. It still doesn't have native Nvidia drivers, correct?
Click to expand...
Click to collapse
That's correct, but they did add in some hardware acceleration code of their own to improve video playback. It's not perfect, but most videos seem to work pretty well for me.
Mantara said:
HTC Vision gets Netflix good for GB. I also don't notice anything missing from the market. Guess you could use vegan 5.1.1 and throw in the Netflix patch and then mod build.prop and see what happens. Breaks YouTube app by the by but browser viewing still works peachy.
Click to expand...
Click to collapse
Worked like a charm... except [modded/patched] Netflix doesn't play video for me (it looks like its going to play, shows play/pause and seek control but goes back to the main screen almost immediately). No biggie, I rarely watch Netflix anyway.
I see everything in the market and all the T/HD games actually run. Thanks!
You can clear app data for netflix from manage apps then fix permissions with cwm. This fixes a lot of Netflix issues (chipmunk, slo-mo, bad banding)
DiGiTY said:
Worked like a charm... except [modded/patched] Netflix doesn't play video for me (it looks like its going to play, shows play/pause and seek control but goes back to the main screen almost immediately). No biggie, I rarely watch Netflix anyway.
I see everything in the market and all the T/HD games actually run. Thanks!
Click to expand...
Click to collapse
Did you just change the device to HTC Vision? Or did you copy a complete build.prop from somewhere? Link?
Thank you!
I just changed it to HTC Vision in build.prop. Netflix also works now (from the Market).
Hi there.
Anybody know if there is a way to enable/patch the rom so the hw acceleration would be possible.
i play the mkv files with mx video player and i see that there is only the sw possible.
anybody have any idea?
Such a thing does not yet exist for any AOSP based ROMs.
as a matter of fact it does exist in one GB rom ...
AdyScorpiusMIUI-GB[2.3.7][DARK][SMOOTH & CRISP][MIUI-GB]
http://forum.xda-developers.com/showthread.php?t=1488399
wini77 said:
as a matter of fact it does exist in one GB rom ...
AdyScorpiusMIUI-GB[2.3.7][DARK][SMOOTH & CRISP][MIUI-GB]
http://forum.xda-developers.com/showthread.php?t=1488399
Click to expand...
Click to collapse
Whilst I see that it is listed as a feature of that ROM, I'd personally like to call bull<insert profanity> on any HW acceleration of video playback claims.
oinkylicious said:
Whilst I see that it is listed as a feature of that ROM, I'd personally like to call bull<insert profanity> on any HW acceleration of video playback claims.
Click to expand...
Click to collapse
well i have tried the AdyScorpiusMIUI-GB yesterday and the videos with 1080p 30fps played smoothly with normal frame rate.
p.s. i have noticed that the new Miui Special Edition v7 has HW acceleration too.
I'll give it a try today...
Hi All,
I've been trying to figure out how to get my CM7 NT to stream Netflix in the HD quality of the stock Nook ROM.
I've tried several edits to the build.prop (ro.product.____ and ro.build.___), to no avail.
Are there any specific lines in the current CM7 Internal build.prop that prevent Netflix from streaming in HD, like how the NT comes originally? Or is it some other issue with the CM7 build? Has anybody on CM7 gotten this to work?
Many thanks in advance.
Unless there's been a development I'm not aware of as of right now, you can't, it has to do with the fact that hardware acceleration isn't fully supported in non Stock ROMs. In addition the stock app is believed to be coded differently for the hardware.
DemonicPhantasm said:
Unless there's been a development I'm not aware of as of right now, you can't, it has to do with the fact that hardware acceleration isn't fully supported in non Stock ROMs. In addition the stock app is believed to be coded differently for the hardware.
Click to expand...
Click to collapse
I wish that part about the stock app was true, but the stock app works identically to the version that you get in the Google Play store. Reinstalling the stock version on CM7 via Titanium Backup gets you the same low-quality video and delayed audio that you'd get on the downloaded app.
But hardware acceleration will be here, it's just taking a little while. We're very fortunate to have Rebellos, a recognized XDA developer, joining the new-kernel project. He says he plans to start contributing to the project in about a week.
Mike_IronFist said:
But hardware acceleration will be here, it's just taking a little while. We're very fortunate to have Rebellos, a recognized XDA developer, joining the new-kernel project. He says he plans to start contributing to the project in about a week.
Click to expand...
Click to collapse
Ah, so it's a hardware acceleration issue then, rather than Netflix<-> build.prop device incompatibility? I thought that was done and fixed in the latest CM7 release?
Also stoked to have Rebellos on board.
i thought cm7 had full HW acceleration- and from using it vs using the rooted nook tablet it DOES play movies Better (i can play/stream a bluray.mp4 file on CM7 Fine, it stutters and hangs using the rooted nook(mx video player streaming over my wireless network for both examples) , it is CM9 that is having problem with the ducati timer conflict with backlight timer....the issue is the hd version of netflix if i remember correctly required the locked bootchain blah blah to get the hd version. not sure if that version will run on cm7 i just installed netflix from googlestore and use that.
chaqfoistylo said:
Ah, so it's a hardware acceleration issue then, rather than Netflix<-> build.prop device incompatibility? I thought that was done and fixed in the latest CM7 release?
Click to expand...
Click to collapse
lenardo said:
i thought cm7 had full HW acceleration- and from using it vs using the rooted nook tablet it DOES play movies Better (i can play/stream a bluray.mp4 file on CM7 Fine, it stutters and hangs using the rooted nook(mx video player streaming over my wireless network for both examples) , it is CM9 that is having problem with the ducati timer conflict with backlight timer....the issue is the hd version of netflix if i remember correctly required the locked bootchain blah blah to get the hd version. not sure if that version will run on cm7 i just installed netflix from googlestore and use that.
Click to expand...
Click to collapse
If that were true, I think we'd already have hardware acceleration in CM9. After all, it would mean that source code for a hardware-accelerated graphics driver on the Nook Tablet was available. The whole reason Rebellos is joining the project is because we lack said source code.
Celtic did fix a video performance bug in CM7, but as far as I know it was mainly related to video playback and decoding, not graphics drivers. I might be wrong about that (I'm not a developer myself, I just follow it closely) but that's what the situation looks like right now.
Like I said, there's no difference between the Google Play downloadable Netflix app and the one that comes with your Nook Tablet. The key difference is the underlying firmware - stock, for some reason, gets HD-quality and synced up sound while CM7 gets low-quality and delayed sound. I've been following this one issue closely since it's my one pet peeve with the custom firmware we've got available. Hopefully, though, the devs will sort it out. They all seem like competent and talented folks.
the problem is 99.9% of the universe apparently for cm9(ICS) uses gptimer 11 for ducati...and the backlight some other timer
the nook tablet -currently- HAS to run the backlight on.....gptimer 11, the devs- i believe- have found a ducati on a different timer and they are working on adapting it to run on the nook tablet, once that is fixed- the cm9 devs will progress faster
Hello XDA, I am user of Moto E and I frequently jump from ROMs to test the stability, performance and bugs of all ROMs I can try.
I watch a lot of TV Series and one of the newer trends is HEVC aka h265 aka x265. This codec enables use to watch HD videos in half the size without losing much quality.
Coming to point, as we know that Moto E as well as Moto G 2014 does not natively supports HEVC playback but all custom ROMs(I really mean all) based on Android Lollipop or above, can play 720p HD HEVC videos smoothly on our device.
It was all going good until 12th May.
I was using Mokee ROM, build 11 May 2016. Then I installed the OTA for 12 May. And bam, HEVC playback is screwed now.
At first I thought this problem was exclusive to Mokee ROM but turns out ALL the ROMs built after 12 May 2016 have this bug.
I have tested and confirmed that the bug exists on: Cyanogenmod 13, Mokee 6.0.1, Resurrection Remix 5.5.9, AOSP CAF, Krexus.
It is a systemwide problem, not just of a media player.
So, I request the devs to have a look at commits made on or before 12th May that affect video playback. or are related to it.
If this is not fixed then many of us will not be using newer builds.
I have attached a screenshot of the problem. To reproduce this bug, just play any hevc video and you will notice a green colored overlapping.
Ptmaroct said:
Hello XDA, I am user of Moto E and I frequently jump from ROMs to test the stability, performance and bugs of all ROMs I can try.
I watch a lot of TV Series and one of the newer trends is HEVC aka h265 aka x265. This codec enables use to watch HD videos in half the size without losing much quality.
Coming to point, as we know that Moto E as well as Moto G 2014 does not natively supports HEVC playback but all custom ROMs(I really mean all) based on Android Lollipop or above, can play 720p HD HEVC videos smoothly on our device.
It was all going good until 12th May.
I was using Mokee ROM, build 11 May 2016. Then I installed the OTA for 12 May. And bam, HEVC playback is screwed now.
At first I thought this problem was exclusive to Mokee ROM but turns out ALL the ROMs built after 12 May 2016 have this bug.
I have tested and confirmed that the bug exists on: Cyanogenmod 13, Mokee 6.0.1, Resurrection Remix 5.5.9, AOSP CAF, Krexus.
It is a systemwide problem, not just of a media player.
So, I request the devs to have a look at commits made on or before 12th May that affect video playback. or are related to it.
If this is not fixed then many of us will not be using newer builds.
I have attached a screenshot of the problem. To reproduce this bug, just play any hevc video and you will notice a green colored overlapping.
Click to expand...
Click to collapse
1080p video working fine here
Sent from my Moto E using Tapatalk
Abhimanyu Shekhawat 121 said:
1080p video working fine here
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
I was talking about HEVC codec. Not about h264 or mkv in general.
HEVC uses h265 which is a newer codec.
Download any 720p h265 based video and you will see the bug in playback.
Ptmaroct said:
I was talking about HEVC codec. Not about h264 or mkv in general.
HEVC uses h265 which is a newer codec.
Download any 720p h265 based video and you will see the bug in playback.
Click to expand...
Click to collapse
Ok
Sent from my Moto E using Tapatalk
I can verify this issue.
piku 123 said:
I can verify this issue.
Click to expand...
Click to collapse
You are also facing this issue? Any luck with newer builds?
Ptmaroct said:
You are also facing this issue? Any luck with newer builds?
Click to expand...
Click to collapse
I was facing this issue with mokee.
I went back to RR 5.6.7 build.
720P HD HEVC videos lag a bit..while playing in Orion rom.
akshay 33333 said:
720P HD HEVC videos lag a bit..while playing in Orion rom.
Click to expand...
Click to collapse
Our phone is not powerful enough to play 720p hevc videos smoothly.
piku 123 said:
I was facing this issue with mokee.
I went back to RR 5.6.7 build.
Click to expand...
Click to collapse
That's what I did. As we know that Resurrection 5.6.7 is not latest, it was build before 12th may hence it has no playback issue.
akshay 33333 said:
720P HD HEVC videos lag a bit..while playing in Orion rom.
Click to expand...
Click to collapse
Try any old build of april of Mokee or CM or any. HEVC playback was worse before, they did some upgrade and frame drops were heavily reduced. But on near 12th may there was a commit to main source which completely broke the playback.
piku 123 said:
Our phone is not powerful enough to play 720p hevc videos smoothly.
Click to expand...
Click to collapse
Our phone does not natively support HEVC videos but custom roms have kernel enhancements and/or changes in framework_av which made playback possible.
Bug Reporting Process
@piku 123 - Thanks for bringing this to my attention. I don't browse the condor forums regularly, so I don't see these reports unless I'm told about them.
I don't have my condor on me, but I was able to reproduce this issue with HEVC playback on the latest nightly for otus, and can confirm that this issue is not present on the older snapshot build. Since this issue is easily and consistently reproducible, and would have had a clear last known good and first known bad date, this would be classified as a nightly regression. Nightly regressions are reproducible issues that worked properly on a specific recent nightly and no longer work on the current nightly. The proper way to report nightly regressions is on JIRA.
I understand that the JIRA bug reporting process takes a little time, as you need to be clear and specific about the nature of the issue. However, reporting it through JIRA would ensure that the all the relevant developers are made aware of the issue in a timely manner, have proper descriptions of issues, and specific last known good dates. It also allows tracking the progress of the issue and follow up. Due to the nature of Android's version control (a bunch of separate git repos), it can become difficult to reproduce a month old build. The sooner an issue is reported on JIRA, the easier it would be to debug.
With regards to this issue with HEVC, since I am now already aware of the issue and working on it, it probably isn't necessary to create a JIRA ticket. However, for future reference, please report new nightly regressions on JIRA.
Yes, I was facing this issue on 9 may cm13 build. And great to see that squid2 was read this thread and will fix this issue.
Sent from my Moto E using XDA Labs
squid2 said:
@piku 123 - Thanks for bringing this to my attention. I don't browse the condor forums regularly, so I don't see these reports unless I'm told about them.
I don't have my condor on me, but I was able to reproduce this issue with HEVC playback on the latest nightly for otus, and can confirm that this issue is not present on the older snapshot build. Since this issue is easily and consistently reproducible, and would have had a clear last known good and first known bad date, this would be classified as a nightly regression. Nightly regressions are reproducible issues that worked properly on a specific recent nightly and no longer work on the current nightly. The proper way to report nightly regressions is on JIRA.
I understand that the JIRA bug reporting process takes a little time, as you need to be clear and specific about the nature of the issue. However, reporting it through JIRA would ensure that the all the relevant developers are made aware of the issue in a timely manner, have proper descriptions of issues, and specific last known good dates. It also allows tracking the progress of the issue and follow up. Due to the nature of Android's version control (a bunch of separate git repos), it can become difficult to reproduce a month old build. The sooner an issue is reported on JIRA, the easier it would be to debug.
With regards to this issue with HEVC, since I am now already aware of the issue and working on it, it probably isn't necessary to create a JIRA ticket. However, for future reference, please report new nightly regressions on JIRA.
Click to expand...
Click to collapse
Thank you so much sir
I know that my way of reporting isn't the best example but I tried. I created an account on JIRA and even searched for existing tickets for the same issue. I did not post because of lack of proper knowledge. Now that you are aware of this bug, I hope you will fix it sooner or later.
@Ptmaroct how you play hevc videos i tried its laggy here and it plays only on sw decoder,hw decoder its not supported....
vinay001 said:
@Ptmaroct how you play hevc videos i tried its laggy here and it plays only on sw decoder,hw decoder its not supported....
Click to expand...
Click to collapse
MX player or gallery supports HEVC with HW.Moto E can play upto 720p(TV series Episodes).
What ROM are you using?
@piku 123 this file doesn't play smoothly on Mx player or Bs player it plays only on sw decoder when we switch to hw decoder says Hw is not supported i tried HW+ too
bw its 720p Hevc file....
vinay001 said:
@piku 123 this file doesn't play smoothly on Mx player or Bs player it plays only on sw decoder when we switch to hw decoder says Hw is not supported i tried HW+ too
bw its 720p Hevc file....
Click to expand...
Click to collapse
That is a AC3 file our device can't do both hevc and 5.1 decoding .
Most HEVC are hit and miss but 720p hevc tv series plays properly in our devices.
piku 123 said:
That is a AC3 file our device can't do both hevc and 5.1 decoding .
Most HEVC are hit and miss but 720p hevc tv series plays properly in our devices.
Click to expand...
Click to collapse
The best example of supported HEVC videos are 720p Tv Series episodes from encoders like Shaanig or PSARips.
hello to all, greetings from Spain, I open this issue because since last Friday I am the new owner of lg v30, but I have a problem that I do not like at all, and I would like to know if the same thing happens to you too
on YouTube, I've put some videos of these shows to see the screen and others, and I noticed that the videos in 1080p60 are pretty lag, and quite annoying frame losses, like stoppages, (in one of Youtube videos, a demo of LG, a red car comes out, and happens to be next to the camera and the next frame is already 2 meters, I do not know if I explain) and I'm quite fussy about this issue, what I put the same video to 1080p also in a leeco le pro 3, and it looks fluidisimo, perfect .... why can this be? Someone else happens?
I do not know if you can put links, if you can please tell me and I'll post the video so you can try it if you can see it well
Another question, does your phone heat up? is that I notice it hotter than the leeco, as soon as I put some video like this 1080p60 gets tempered by the area of the camera, I do not know if that is normal or not
Thank you very much and hopefully answer
Happens to me too. I also tested this on a Galaxy S8 and it has identically bad performance. It probably also happens on the Note 8. 1080p30 HDR runs fine though. I didn't notice any heating - maybe just slightly warm but could as well be from my hands. Was the other phone you tested HDR capable?
I don't know if I can help you at all, but perhaps if you fill in some blanks, others might.
1) What model phone do you own and what firmware are you on (stock, stock rooted, custom ROM, etc)? You can check your firmware under Settings.
2) Can you link us to a video that's giving you problems?
Mejilan said:
I don't know if I can help you at all, but perhaps if you fill in some blanks, others might.
1) What model phone do you own and what firmware are you on (stock, stock rooted, custom ROM, etc)? You can check your firmware under Settings.
2) Can you link us to a video that's giving you problems?
Click to expand...
Click to collapse
hello, thank you very much for answering
1) my phone is lg v30 h930, stock, just removed from the box without touching anything, and the software version is V21w-EUR-XX
2) this problem happens to me in all the videos that I play on YouTube 1080p60 HDR (if I put the same video in 720p60 HDR the problem improves a lot, it becomes almost imperceptible) but the problem is that youtube does not give the option to deactivate the hdr, so if the video has that option, it activates it
I give you some examples of the videos that I have tried and they are very annoying ( It does not let me put links because I have less than 10 messages, I put the description of the youtube thumbnail, the first videos come out )
on youtube put "lg oled demo ", and play the first video, which shows a teapot in the thumbnail, and the video that shows a butterfly in the thumbnail, both are 4k Hdr 60fps
the phone I have it all activated, the HDR, I have not activated any energy savings, this all to the maximum ... I do not know what can happen, I do not know if it is the snapdragon 835 problem that can not with so much demand .... Do you think that could be why?
I have a pocophone f1 my brother, and the same video runs smoothly, very very fluid, but does not allow HDR, but I do not want hdr only make it look fluid
I've also noticed a bit of lag in chrome, in firefox it's better to scroll
Do you think it will be solved in any way? is that if I'm not return it and buy another phone thinking, something like pocophone because they do not have that kind of budget : llorando:
thank you very much and I hope response
I just tested that first video you suggested (the one with the teapot thumbnail) and I had absolutely no issues with playback. No stutter or lag with either the video or audio.
It's perfectly smooth, and really a lovely video.
I'm not an expert on HDR (since I don't use this device to watch movies or TV shows via Netflix or any other service), but as far as I can tell, the HDR triggered properly.
I have HDR turned on Settings, of course, and it's my understanding that you can tell when HDR turns on (when you rotate to Landscape) because the white Youtube pause/play buttons (amongst others) get very bright compared to Portrait view (which is supposed to disable HDR).
I also have never had any issues with Chrome. But I don't use FireFox, so I can't really compare the two.
I'm using an American open market US998 LG V30 on stock 20D (an old firmware from around June/July 2018), rooted.
I plan on updating my phone to the newest stock firmware one of these days, but haven't gotten around to it.
I have no idea what's going on with your phone. I understand it's new.
Maybe try checking to see if there's an OTA firmware update ready for you to install? (You might be running system software even older than mine, with a flawed HDR implementation).
Maybe there are some bloatware apps that came with your phone that are impacting performance.
Perhaps a factory reset could help?
I'm sorry I can't be of more help.
Que tengas buena suerte.
When i Am on STOCK ROM there is stutter and lag..
Install A CUSTOM ROM (tested on dot os) The colors still look vivid and plays smooth!! Absolutely no lag
I have had this issue since I first took my V30 out the box. Have the latest update for stock ROM/ VS996/Verizon. I gave up trying to troubleshoot this issue.
im using vanced as default YouTube app. it has an option to enable VP9 codec, that'll make your playback smoother even at 1440p60fps. But it kill HDR (but the color still the same tho). Shame, that V30 couldn't play HDR, because this phone is one of YouTube Signature Devices https://devicereport.youtube.com/phones/lg_v30.
Update: When I play that "lg oled demo" video, it doesn't stutter, I don't notice any of them. But when play "peru hdr" it stutter a lot. I'm using H932 latest stock. Try to activate that VP9 codec if you don't want HDR after all. Also, I don't use Chrome anymore, I disable it and using others. try Kiwi or Brave both are chromium based if you prefer chrome-like interface. If Firefox feels better so stick with it.
Just turn off hdr in display settings, every lg v30 has this problem. I think it's because hw decoder cannot keep up so this problem applies to every snapdragon 835 phone. Hw is capable of 1080p30fps HDR in vp9, 1080p60fps HDR is on the limit and can drop frames. HDR is gimmick for me, it is not well implemented. The quality is much worse than normal videos. For me bigger problem is that oled screen cannot reproduce dark colors because of low uniformity when pixels are barerly turned on and very slow response time in that matter too but that's for another topic.