Related
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
Ladies and Gents, I present to you; offical VLC Nightlies.
http://nightlies.videolan.org/build/android-v7-neon/
Now, I'm sure some of you already knew this was there. But as of the latest build, it will play 720p files with full DTS support! Make sure Hardware Acceleration is turned on and go to town! Plays flawlessly. 1080p doesn't appear to work, but I'm also installing something right now so I may be hitting the IO barrier of SIO. I'll report back about 1080p after it finishes. If it works then I'm going to uninstall everything else except Super Video (I like popup videos).
There's also a build for Tegra 2, which I haven't tried to see if it works better on our Tegra 3 chips.
EDIT:
1080p is not currently working as far as I can tell. It almost does.
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,
i have tried to moonlight streaming from PC to Androidx86, but its not working, i got message that ROM doesnt support H264, otherwise Games with OpenGL 3.2 and mesa are working.
Is there way how to fix it?
I understand this is quite an old post, however if you check out my fork of moonlight I think I got it to work but am unsure of the preformance of it, feedback would be appreciated https://github.com/foxtrotdragon/moonlight-android-Android-x86/releases
Thanks, there some problem with last Android-x86 release on my Netbook, but will try it, if not write back in 2 days, just remind yourself.
Hmm, error is still the same device or rom dont support h.264 playback..
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.