Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 5 subscribers
  • Views 12628 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

App protection failure on lollipop 5.1

st
Hi, Your software ( sophos mobile security, version : 5.0.1515 (12) ) is running on an Android smartphone. It was working under Android KitKat with dalvik. As i tried an alternative runtime environment ( ART ), app protection stopped working. Now my phone is upgraded to lollipop 5.1 and the app protection component of the antivirus is not working. A password is set in the app protection component. But no more password is requested when i use an application protected by app protection. Do you plan to fix it? Yours sincerely
:1021385


This thread was automatically locked due to age.
  • 0

    Hello,

    changing the runtime environment is currently not supported. 

    There are currently no plans to change this.

    Regards
    Thomas

    :1021386
  • 0 in reply to ThomasBrand

    I am stunned with this answer, we have several Nexus 9 (LTE) tablets running on Android 5.1.1 (build: LMY48I). In the SMC application it shows 8 protected apps. Lock all aps or change password is not working. The new Android OS is based on ART. So imo Sophos needs to bring out an application update to support their user base.

    Cheers Luc

  • 0

    This has also happened to me since the Stagefright issue patch applied to them by a recent update by Google to my Nexus 5 and Nexus 6 phones. Also note that both of these phones worked when they were using ART runtime before the patch.

    ART is a feature of Android lollipop that replaced Dalvik entirely. It cannot be turned off. I'm note sure the Sophos response is valid because of this.

  • 0
    Please excuse this issue. The Stagefright patch has disabled this feature. You will see an update soon, which re-enables it after the user confirms, we can access "runtime data" as Google calls it