• 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 10
Video stuttering in Kodi 15 for Amlogic SOCs
#46
He probably means that it's not working mediacodec/libstagefright enabled and amlcodec disabled.
If amlcodec is enabled, it's tried first, so if it works, the other 2 are not used at all.

But if amlcodec is working, I don't get what's his issue, unless he just blindly disabled amlcodec due to other posts/threads....
Reply
#47
...
Reply
#48
I guess so, lol
Reply
#49
We're getting some similar reports here:
http://minixforum.com/threads/kodi-15-0-...ased.6855/

Users claim that it works OK on older Gotham releases.

Hope this info helps, thanks.
Reply
#50
Ha Ha, round and round in circles.

The best troubleshooting procedure is just to enable each decoder one at a time and leave the rest disabled. Then connect a keyboard and pullup the OSD Codec window with the "O" key

If Hardware acceleration is working:

amcodec = am-h264, am-mpeg2, am-h265 etc
libstagefright = stf-h264, stf-mpeg2 .....
mediacodec = amc-h264, amc-h265....

Reply
#51
(2015-08-03, 11:20)wrxtasy Wrote: Ha Ha, round and round in circles.

The best troubleshooting procedure is just to enable each decoder one at a time and leave the rest disabled. Then connect a keyboard and pullup the OSD Codec window with the "O" key

If Hardware acceleration is working:

amcodec = am-h264, am-mpeg2, am-h265 etc
libstagefright = stf-h264, stf-mpeg2 .....
mediacodec = amc-h264, amc-h265....

Thanks for the tip. I tried enabling each codec independently, including disabling them all. The result was that the OSD showed the same indication for what I assume is the decoder: dc:ff-h264 regardless of the enabled codec.

If I read this right, none of the decoders are being enabled since the OSD shows the same value for 'dc' when all decoders are disabled.

Regards
Reply
#52
The difference is from this commit:
https://github.com/xbmc/xbmc/commit/8684...e754cea214

Reverting it should fix this problem?
Reply
#53
(2015-08-04, 05:19)minixhk Wrote: The difference is from this commit:
https://github.com/xbmc/xbmc/commit/8684...e754cea214

Reverting it should fix this problem?

No, sorry. The problem is firmware with incorrect permission. Letting Kodi (or any app) have root when it doesn't really need it is a security risk, and correcting permissions is not Kodi's job.

In other words, this was deliberately done to force companies to finally fix the real problem, with the incorrect firmware permissions.
Reply
#54
(2015-08-04, 05:51)Ned Scott Wrote:
(2015-08-04, 05:19)minixhk Wrote: The difference is from this commit:
https://github.com/xbmc/xbmc/commit/8684...e754cea214

Reverting it should fix this problem?

No, sorry. The problem is firmware with incorrect permission. Letting Kodi (or any app) have root when it doesn't really need it is a security risk, and correcting permissions is not Kodi's job.

In other words, this was deliberately done to force companies to finally fix the real problem, with the incorrect firmware permissions.

Noted.
Reply
#55
(2015-08-04, 05:51)Ned Scott Wrote:
(2015-08-04, 05:19)minixhk Wrote: The difference is from this commit:
https://github.com/xbmc/xbmc/commit/8684...e754cea214

Reverting it should fix this problem?

No, sorry. The problem is firmware with incorrect permission. Letting Kodi (or any app) have root when it doesn't really need it is a security risk, and correcting permissions is not Kodi's job.

In other words, this was deliberately done to force companies to finally fix the real problem, with the incorrect firmware permissions.

But it used to work before without root access.
MINIX firmware doesn't come with root privileges...
Reply
#56
let's wait for koying to comment on this. iirc it used to work by "accident" but unsure.
Since he has a Minix device(s) he should be able to see what is happening.
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply
#57
Does Minix have issues? As it is indeed my reference device, I'm pretty sure the permissions are right...

I don't see anything related in the Minix thread:
"Lower framerate" is just unrelated to video, so much that we removed its display because it confused users.
SMB with username rather than email address is just... the way it is. I'm not gonna spend hours looking into that (I didn't even know you *could* use the email address previously).
Reply
#58
(2015-08-04, 09:58)Koying Wrote: Does Minix have issues? As it is indeed my reference device, I'm pretty sure the permissions are right...
Permission are correct on my HardKernel C1 (S805) add well, so having none of these issues.

(2015-08-04, 05:51)Ned Scott Wrote:
(2015-08-04, 05:19)minixhk Wrote: The difference is from this commit:
https://github.com/xbmc/xbmc/commit/8684...e754cea214

Reverting it should fix this problem?

No, sorry. The problem is firmware with incorrect permission. Letting Kodi (or any app) have root when it doesn't really need it is a security risk, and correcting permissions is not Kodi's job.

In other words, this was deliberately done to force companies to finally fix the real problem, with the incorrect firmware permissions.
HINT:
Those with incorrect Firmware permissions and a Rooted device would logically try the "su chmod 666" commands outlined in Red in the Github commit above using an Android Terminal App.

BUT these permission will be lost on every reboot. So this thread comes into play as a workaround for those with poor Firmware to Autoset these permissions again on every reboot:
http://forum.kodi.tv/showthread.php?tid=229310

I do totally agree with Ned & Koying, its up to the Android Firmware devs of each device to get these permissions correct in the first place.
Buy a cheap AMlogic device - get no support and this is the mess you end up with.
You get what you pay for in the end.

Reply
#59
Since my non-rooted MX2 worked with Helix, is it really necessary that the 15.x aml_permissions() check for RW access? Would RO access be sufficient?

The reason I ask is that on a non-rooted MX2 running 14.2, wouldn't the files be RO anyway and the chmod calls in aml_permissions() fail?



Thanks for the interesting discussion.
Reply
#60
Just wanted to add another datapoint:

I installed SPMC from the playstore and it correctly loaded the HW acceleration codec for my chipset. Everything plays smooth and CPU load is < 30%/per

Good job Koying. Whatever you did for SPMC to enable HW acceleration for AmLogic devices, is it possible to get that rolled in to the Isengard branch? Note also that this MX2 is not rooted.

PS:

One issue: The video is not scaled properly (zoomed upper-left), but at least the HW acceleration is working. Now to figure this out!

Regards
Reply
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 10

Logout Mark Read Team Forum Stats Members Help
Video stuttering in Kodi 15 for Amlogic SOCs1