Link on step 3.
I think the caching changes and stutter are chain/device dependent.
I have never had an issue with stuttering in FEL on any CE nightly so it is not something I worry about. No issue for me on any of the nightlies that cpm build was based on.
I have exact cache settings in that post
Okay, a wrong choice of words. It technically supports it, but is not usable as playback is interrupted in the first 10 to 20 seconds, and that is if you are lucky. It has been like that for over a year and I even installed the latest nightly to check the state of FEL playback just to be sure in my response, and, unsurprisingly, it is still exactly the same.
hm, I was under impression that it was already working fine since a couple of months. I think someone mentioned that you would need to use maven’s build from kodinerds repo. But maybe that’s a false info.
No, it’s not false info, I got it with Maven’s nightly build, and never tried any other. Used it for several days without any problem for testing purpose. Never tried it again after @cpm published his builds.
Now I use only official nightlies and @cpm build, and got rid of Kodi on Android…
Can be installed over the current one, then reboot.
This release is only work for self compiled CPM builds.
This release does not work with the CPM A5 build.
For the CPM A5 build, please use this release.
Enjoy! 
This looks great - too bad we can’t have it 
Will this build after A5 be shared with all forum members. I know about the conflict with CPM. Some developments are shared here that cannot be used by forum members. Can those who have this compilation after A5 share it?
No shares anymore from cpm.
I know about that. But you still release a development for a skin that is for a build after A5. So you and someone else have this build. Play it for the rest of the forum members too…
Only if you pay for it 
Don’t worry, the newest CPM builds will be eventually shared outside of his private github soon(ish).
I suspect that CPM privately shared a build with @jamal2367 with an agreement that jamal2367 would not share it further.
Basically, it seems at this point we’ll need another member to set-up a build environment, mirror the official CE repos, applies CPM’s patches on top, build and then share. This will last until CE either merges CPM changes or makes a breaking commit or CPM decides to share builds again.
thanks , I prefer this one 
You made me feel better 
May we not wait long
I can’t say anything about this, but your assumption could be true.
Cheers!!
cpm has made some commits today, cleaning up and reworking some recent changes.
And it seems to be in more ‘finished’ state than a couple days before with temp commits.
In theory I can share my build(s) based on these changes after some tests and without any support of course.
I hope that he would be ok with this.
The question is whether he wants his work to be made available by others for download. If we do something wrong, it could mean that he gives it up completely.
Difficult situation… 
yeap, that’s my only doubt. On the other hand, considering that he left the repo public, It would be strange to be against the build, otherwise what’s the point of it, just to tease?))
I think it’s okay to share a build if you compile it yourself. After all, the code is publicly available. But we don’t know how cpm will react to it.
There is a reason why he deleted his builds on GitHub.
Hmm. 
About | FAQ | Terms of Service | Privacy Policy | Legal Notice
