[Q] cm nightly 54 hw video decodeing?? - G Tablet Q&A, Help & Troubleshooting

I was reading the latest changelog for cm7 because the nightly went from 42 to 54 and found this! Is this hw video decoding??
Change-Id:
I987d1fd17462fd41655b193a8cb03709a7d85e8e
Owner
Project CyanogenMod/android_device_advent_vega
Branch gingerbread
Topic
Uploaded Apr 23, 2011 5:27 AM
Updated Apr 23, 2011 2:03 PM
Status Merged
Permalink
Vega : Enable HW Video Decoding
Enable OMX and Opencore prop pulls
Enable TARGET_OVERLAY_ALWAYS_DETERMINES_FORMAT
Enable TARGET_USE_SOFTWARE_AUDIO_AAC
Change-Id: I987d1fd17462fd41655b193a8cb03709a7d85e8e

Where are you seeing these changes ?
I can only see harmony related changes here:
http://cm-nightlies.appspot.com/?device=harmony
Code:
cm_harmony_full-54.zip
Revert "ignore sf error" (android_frameworks_base)
Correct changelog for bad English translation :( (android_vendor_cyanogen)
Changelog revision (android_vendor_cyanogen)
CHANGELOG (android_vendor_cyanogen)
Traditional Chinese: update translation (android_packages_apps_CMParts)
stagefright: Remove extra parenthesis in makefile (android_frameworks_base)
libutils: Fix an improper const-cast in RefBase (android_frameworks_base)
Updated Italian translations (android_packages_apps_CMParts)
Create tablet overlay and set encore to use it (android_vendor_cyanogen)
add csr_tegra support to bluetooth stack (android_external_bluetooth_bluez)
Revert "The ActivityThread will restart a stopped activity before sending onActivityResult" (android_frameworks_base)
harmony: set TARGET_USE_SOFTWARE_AUDIO_AAC in BoardConfig (android_device_harmony)
harmony: set TARGET_OVERLAY_ALWAYS_DETERMINES_FORMAT (android_device_harmony)
Fixes issue #3404 (http://code.google.com/p/cyanogenmod/issues/detail?id=3404) where many applications such as SMS, Contacts, etc would FC if the user changes their locale to Arabic (or any locale that doesn't use the English numeral system) (android_packages_apps_Email)
Convert bearing/heading from 10 bit value to degrees on locapi 20000 (android_hardware_qcom_gps)
Fix for issue 3551 (android_packages_inputmethods_LatinIME)
media: stagefright: Implement TARGET_USE_SOFTWARE_AUDIO_AAC in OMXCodec (android_frameworks_base)
harmony: update extract/setup for Stage Fright (android_device_harmony)
webkit: fix text wrapping (android_frameworks_base)
stagefright: allow targets to pass real dimensions to the decoder (android_frameworks_base)
Check BOARD_VOLD_EMMC_SHARES_DEV_MAJOR to share volumes to get the correct partition number for the volume. (android_system_vold)

Where did you find hw fixes? Its not in the changelog im seeing.
b3ltazar said:
I was reading the latest changelog for cm7 because the nightly went from 42 to 54 and found this! Is this hw video decoding??
Change-Id:
I987d1fd17462fd41655b193a8cb03709a7d85e8e
Owner
Project CyanogenMod/android_device_advent_vega
Branch gingerbread
Topic
Uploaded Apr 23, 2011 5:27 AM
Updated Apr 23, 2011 2:03 PM
Status Merged
Permalink
Vega : Enable HW Video Decoding
Enable OMX and Opencore prop pulls
Enable TARGET_OVERLAY_ALWAYS_DETERMINES_FORMAT
Enable TARGET_USE_SOFTWARE_AUDIO_AAC
Change-Id: I987d1fd17462fd41655b193a8cb03709a7d85e8e
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA Premium App

juanaraya92679 said:
Where did you find hw fixes? Its not in the changelog im seeing.
Click to expand...
Click to collapse
Here
Not sure how that relates to the latest nightly though.

It can be just one change from many step required to make this work.
Sent from my Nexus S using Tapatalk

All I know is that vids that didnt play before are playing now. A whole lot smoother too.

drx69 said:
All I know is that vids that didnt play before are playing now. A whole lot smoother too.
Click to expand...
Click to collapse
Can you take screenshots with this build? Either via ddms on the desktop, or screenshot ER?
Because not being able to take screenshots (as of the previous nightly) is what drove me to Vegantab (which I like, but I could go back )

drx69 said:
All I know is that vids that didnt play before are playing now. A whole lot smoother too.
Click to expand...
Click to collapse
How's youtube? Can it play HQ vids now?

I can confirm video playback from YouTube without stuttering. I played HD video from both the website (Dolphin and Stock Browser) and the YouTube App. I played the VEVO version of a few songs, and they all played flawlessly.
I am running Pershoot's Overclock Kernel, but all seems fine.
Here is a video link for documentation:
http://www.youtube.com/watch?v=iIk2WnS_lAk

This is indeed an incredible development! I can't wait for it to be refined and eventually baked into all the gingerbread roms. I know there are many of us holding off on jumping from froyo until hardware acceleration is enabled.

How about hardware decoding of local AVI's and wmv's? any tests?
thanks in advance.

pagantek said:
How about hardware decoding of local AVI's and wmv's? any tests?
thanks in advance.
Click to expand...
Click to collapse
no dice yet.
Observed speedups might be due to changes in the streaming libraries or flash handling or something.
Setting up hardware acceleration on video players (moboplayer and rockplayer) still fails.
Also graphics related benchmarks results didn't improve from the earlier rest of the CM7 releases.

video is better here... vplayer wouldnt play vids before, now after this update it plays all my movies perfectly!! i know for a fact they wouldnt play before the update, it was just freezing my gtab yesterday!

I just tried to move from Clem+Calkulin1.5 to the CM7 55 - Videos which works fine on Calkulin (h264 main @3.1 1024x600) plays much slower and sometimes hw decoder dies.

Well, from my personal experience.. this enables HW decoding got the default Android supported video formats... so no HD... only MP4...

crutzulee said:
This is indeed an incredible development! I can't wait for it to be refined and eventually baked into all the gingerbread roms. I know there are many of us holding off on jumping from froyo until hardware acceleration is enabled.
Click to expand...
Click to collapse
My thoughts exactly.
I threw on a Gingerbread rom just after I got my Gtab.
Then I tried a Froyo ROM just for the heck of it.
Until Nvidia drivers are a part of GB, I'll be sticking with Froyo.

strudel.chris said:
My thoughts exactly.
I threw on a Gingerbread rom just after I got my Gtab.
Then I tried a Froyo ROM just for the heck of it.
Until Nvidia drivers are a part of GB, I'll be sticking with Froyo.
Click to expand...
Click to collapse
+1
but in all honesty, CM 7.0.2 is MUCH better than the nightlies 54 and below. Its actually usable now. Coming from Vegan 5.1.1, I dont feel compelled to go back to froyo after flashing CM7 now. With pershoots OC kernel, this will definitely be my daily driver moving forward, and its only going to be get better over time! All of the tegra games run butter smooth, HQ (720p) flash works fine, and .3GP works with much more to follow.

How are videoconferencing apps? Camera and video? tempted t flash back to cm7 from vegan 5.1. 1. I love the cm7 honeycomb theme.
Sent from my SPH-D700 using XDA Premium App

Related

[MOD] NeXuS HaZ 720p @29fps and 480p @ 30fps. UPDATE (12/29)

Finally 720p encoding for nexus one
I LOVE ANDROID
Thanks to
My Parents, Cyanogen, maxisma, Wysie_Soh, barakinflorida coolbho3k and more for their support, teaching inspiration and work
Requirements- >CM5.0.8test3
Froyo Done thx to cyanogen
U need the new froyo radio
Here u go, this time its a full CM6 RC1 build, i didnt have time to make it incremental, will do an incremental update sometime tomorrow
http://www.megaupload.com/?d=6WOYHP85
Incremental update. Flash on top of cm6. Thx maxisma I was too lazy if u get fc after flahing these then wipe camera data, thx for the info everyone
Here they are!
For 8 MB/s SDs: http://www.megaupload.com/?d=RUO7BCOC (not signed turn of signature checking)
For 6 MB/s SDs: http://www.megaupload.com/?d=AX38PJ55 (its with kerneln i think itdoesnt need to be really updated, if u still want u can post in thread
Your phone should have a high speed sdcard able to bear the load of the high fps otherwise the video recording will stop for some ms and resume. I am yet to tweak bitrate etc for these settings
#AndroidWinsAgain
#iPonySUX
To come
better audio
Working on them now
Latest Video sample 1 http://www.youtube.com/watch?v=h-eyr3T5W9A
Latest Video sample 2 http://www.youtube.com/watch?v=hzxVlhNnC18
Be sure to watch it in HD
Changelog
12/29
New 8mbps incremental (not signed)
10/29
remove the limit for 8k devices which was set to 24
10/27
Increased FPS
Increased quality of video
5/8
fix pixelation
fix green issue (enom)
3/8
test version out for froyo
6/15
Allocate 15mb to camera (thx coolbho3k)
CAP bitrates
i guess the first stable one with best video quality
6/14
Fix blank 480p
6/13
Increased Bitrate
Allocated more RAM to Camera thx Coolbho3k
June 10
New Camera App by Wysie_Soh (Thx Bro)
Increased Bitrate to 10mbps if anyone can reach it
Source is up at github. www.github.com/charansingh
THANKS!! Does it work with FroYo?
awesome! same as above froyo capable????
when I looked at the download it says CM 5.0.8 and I think it has the same radio as Froyo, so it should work, right? I will test it anyway and report back..
Will this MOD work with any kernel??!
Re: 720p Recording for Nexus one
Downloading it for froyo now. Will report back
-------------------------------------
Sent via the XDA Tapatalk App
Awesome!
I can't wait for the updates to come (FPS, audio quality).
Edit: I don't know if there's an easier way but this is what I did:
1) nandroid
2) wipe
3) flashed pauls FroYo WITH radio HERE
4) wipe
5) flashed cyans 5.0.8t3 HERE
6) flashed the 720p update zip
dont flash on froyo, files are different for it
absolutely wonderful! thank you
"Holy **** 720p" Best video quality title
Lost my usb cable so cant view videos on my computer yet, but i'm currently recording a **** load to view them later.
Thanks OP!
Did you modify anything in the kernel or just in the Camera app? Send me a patch and I'll get it into CM if you want.
charnsingh_online said:
dont flash on froyo, files are different for it
Click to expand...
Click to collapse
And, lo, there was much weeping and gnashing of teeth ='(
Great name for the settings, lol.
Re: 720p Recording for Nexus one
Just tried with froyo. Does not work
-------------------------------------
Sent via the XDA Tapatalk App
Is this 1280x720?
anybody wanna host a sample? I WANNA SEE!!!
spr33 said:
Is this 1280x720?
Click to expand...
Click to collapse
Yes, it's true 720p.
can't wait for FroYo!!
confirmed this don't work with Froyo..
FINAL F*&*&-LY
Dosent work with froyo, hoping and praying for it soon!!
cyanogen said:
Did you modify anything in the kernel or just in the Camera app? Send me a patch and I'll get it into CM if you want.
Click to expand...
Click to collapse
I modded camera driver passion properties and camera for fun. I am working to add 480p profile too with medium tag. No laptop right now. Will report back

[Q] CM7: Netflix Streaming in HD?

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

HDMI out on Task650 4.1

Sorry if this is old news, but I finally got HDMI out working on Task650's 9.8.2012 build for the SGSII. I used a Samsung HDTV adaptor from Amazon and ktoon's FluxiXX kernel. In xxTweaker, I set the I/O Scheduler to bfq and the Exynos Sensor HAL to proprietary. I also set the CPU governor on performance. Videos on my external sdcard were occasionally choppy, but videos on the internal sdcard ran fine.
Also, I had to select the video file and play it through the stock player. MXPlayer, my normal video player, did not work.
I'm going to order the cable then this week. I haven't seen this posted before so yay for me. Lol good post man
Sent from my SGH-I777 using xda premium
Thanks, I hope it works for you. I'm trying to get my posts up so I can thank Task publicly for his ROM!
FYI, this is only partial functionality - hwaccel video playback works, but the UI is not mirrored AND also in the case of hwaccel video, only the video itself shows and NOT any UI overlays.
Entropy512 said:
FYI, this is only partial functionality - hwaccel video playback works, but the UI is not mirrored AND also in the case of hwaccel video, only the video itself shows and NOT any UI overlays.
Click to expand...
Click to collapse
All true, but for those out of town trips at the Holiday Inn, at least you get to watch your movies...
Still not working, Having a powerfull device with AOKP 9/28 and not able to play games in HDMI with my SONY Bravia. huh !

Video playback bug in all custom ROMs. Attention of devs required.

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.

Hardware Decoder help?

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.

Categories

Resources