-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working properly with TimVision #125
Comments
I've noted that temporarely disabling SuperSU brings the same results as using RootCloack: you don't get the warning message from the TimVision app, but still no drm contents can be displayed. The only way to restore TimVision to its full functionality is to unroot the device for good, then root it again later. There must be a way to trick the app... |
Hello again, I've got my hands on a rooted apk of an old version of TimVision app. On a rooted tablet with SuperSu enabled and running the rooted app doesn't show a warning message (so it not detects root) but still can't show any drm contents. The news is this rooted app gives you an explanation why it can't display drm contents, showing this message on the media player: com.discretix.drmdlc.api.exceptions.DrmClientInitFailureException: Failed to initialize DRM Client Could this be useful to bypass the root check? |
This is a logcat made while running TimVision on a Cyanogenmod with Xposed and RootCloack active: alogcat.2016-10-30-14-21-18+0100.txt I really hope this will help you solve the problem |
@Ric-82 I'm not sure how you got that logcat, but that doesn't actually include any information. Remember to enable rootcloak logging and try again. |
I've got it with aLogcat (https://play.google.com/store/apps/details?id=org.jtb.alogcat&hl=en). I'll try with the rootcloack logging as soon as possible. I'll let you know. Thank you for your time |
Ok, this is the log file: |
Unfortunately, that log file doesn't have any helpful information. We've had people with issues where the app would be okay with hiding root, but can't play back DRM content, and that's probably not something that the app can deal with. |
I see, and still the issue has to have something to do with root because, if I get rid of SuperSU completely, drm contents are delivered as usual on the very same device. I feared that could be some sort of check at a kernel level, but I've managed to install TimVision on a stock rom with unlocked bootloader, dm-verity disabled and data encryption removed: it works fine without root. It works under Remix OS too, so I don't think the issue is kernel related or even build.prop related. If you want to inspect this issue any further, I'll be glad to help you with additional logs, tests and whatever could prove useful. Thank you |
Just one more thing, as a side note: I've found this old video on youtube: https://www.youtube.com/watch?v=kBB7jc8UCv4 It shows an older version of TimVision working on a rooted Nexus 5 thanks to Cydia Substrate + SELinux Mode Changer + RootCloak Plus (Cydia). I cannot test this method, because Cydia Substrate supports ARM only, and I have an Intel-Based tablets running Android on x86. But dig into that method could be a starting point to come out with a possible workaround. |
According to this post on http://forum.zidoo.tv/index.php?threads/timvision.2052/#post-11747 It seems TimVision is sensitive to the privilege (it searchs for user-level privilege, for what I can understand). Any idea how to try and fake user-level privilege on a rooted device and/or custom rom? |
any news? |
Using RootCloak, TimVision app (https://play.google.com/store/apps/details?id=it.telecomitalia.cubovision) doesn't show the warning message at launch that states that your device is rooted, and that's good. The problem is that the app still acts as if it detects root, since no drm protected contents can be displayed.
So, RootCloack hides something to the app, but not the whole thing since the app still acts as if it detects root (you can normally use the app on a rooted device without any tricks, but you can only see trailers and free live tv streams. The same happens with RootCloak).
Can you try and research the cause of this behaviour?
(Just to be clear: before rooting my device, I was able to watch drm protected contents, so the drm keys must to be still there, even after the rooting procedure...)
The text was updated successfully, but these errors were encountered: