spakanati123

@ragner seems my demo branch is old and with the updated one it's working fine. I can see API diff to register android layout in the commit: https://github.com/gearvrf/GearVRf-Demos/commit/51c5d35a528dfa7bf53cd796f2d308f4d6d846aa#diff-7bcfc0e30ec452a2b0ad5aefb0c6b022

@ragner when i am checking the **gvr-videoplayer** demo app the cursor not working with remote controller only in player screen when playing video(galley scene no issue) but it's working fine...

@liaxim any update on this..? i wonder like the basic functionality(protected content playback) not available yet. It's an obstacle for many streaming vendors to switch to GearVR framework.

@Shyri you can lower the security level to L3 but it's not recommended when security is a concern. DefaultDrmSessionManager drmSessionManager = buildDrmSessionManager(); drmSessionManager.setPropertyString("securityLevel", "L3");

@liaxim is this feature added to your near roadmap..?

@liaxim @rahul27 @NolaDonato @bohuang3d

@bohuang3d : Playback fails on both GearVR and DayDream . GearVr framework passing the SurfaceTexture as a surface to Player(here it's Exo) which does not support the protected content playback....

@bohuang3d Thanks for the update. It seems your proposed workaround introduces non-secure codec, which in turn uses non-secure buffers while rendering. Lowering security to L3 also uses the non-secure buffers...