On Mon, Jan 11, 2016 at 12:21 PM, Michael Zanetti <[email protected]> wrote: > > > On 11.01.2016 12:07, Thomas Voß wrote: >> On Mon, Jan 11, 2016 at 10:32 AM, Michi Henning >> <[email protected]> wrote: >>>> >>>> Would this get your hardware stuff enabled here then? If so, the check >>>> is not good enough. >>> >>> Right. So much for that. >>> >>>>> But it turns out that the point may well be moot. I re-enabled concurrent >>>>> extraction for audio and video files on my Chromebook, just to see how >>>>> it’ll go. Turns out that codecs get stuck and just hang on my Chromebook >>>>> when more than one runs at a time, so we can’t enable concurrent >>>>> extraction on Arm anyway for the time being. >>>> >>>> Wasn't the idea to enable concurrent extraction for when we are using >>>> the software codecs? >>> >>> What I was trying to do was turn on concurrent extraction on Arm, but >>> *only* if we are not on a phone. Turns out that concurrent extraction is >>> broken on Arm in general, not just on the phone, so the point is moot now. >>> I’ll leave it as for the time the being, which is to run only one gstreamer >>> pipeline at a time on Arm, which is the only thing that works. >> >> Just try to exec getprop. It is only available on systems that are >> running an Android container. > > That's not working when confined, is it? >
I'm not sure, but just trying to stat it might be possible. And that call failing or succeeding should be good enough, too. Cheers, Thomas >> >> Cheers, >> >> Thomas >> >> >>> >>> Michi. >>> -- >>> Mailing list: https://launchpad.net/~ubuntu-phone >>> Post to : [email protected] >>> Unsubscribe : https://launchpad.net/~ubuntu-phone >>> More help : https://help.launchpad.net/ListHelp >> > -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
