Run demo test application on Samsung Galaxy S6: run-as: Could not set capabilities: Operation not permitted RRS feed

  • Question

  • Hi !

    I own two devices - one of them is xtreme wonder and another is Samsung Galaxy S6. I have made an example test application using Visual studio, and was able to launch debugger with xtreme wonder. Meanwhile trying same thing (using ARM Debug and ARM64 debug) on Samsung Galaxy S6 and I'm getting following error:

    Microsoft Visual Studio
    Unable to start debugging. Android command 'run-as' failed. Could not set capabilities: Operation not permitted.

    There are two threads currently describing same issue as I do - for example in here:

    and in here:

    Besides proposal of whole phone reset, there are bit confusing messages of whether it's problem of debugger, phone or client software.

    Ok, I think that phone reset is not an option, I think this should be fixed via Samsung phone update.

    Also there are some mentions about incorrect line feeds used on client side, which in a turn can be a bug in visual studio itself.

    Is it possible to analyze deeper this problem, and also contact Samsung on this matter if problem is on Samsung side ?

    The issue on second link was raised one year ago (WOW!) - but since this is not yet fixed, I suspect that this is not classified as bug or bug is present on client software which uses adb debugging system.

    • Moved by Baron Bi Wednesday, August 23, 2017 5:45 AM Third party issues
    Saturday, July 1, 2017 7:54 AM

All replies

  • Cross posted also here:

    Let's see where I can get reply from.

    Sunday, July 2, 2017 8:55 AM
  • Hi Tarmo Pikaro,

    thanks for posting here.

    For this case, you could try to 'initializing' / factory resetting the device using Samsung's Smart Switch.

    Here is a document for you as a reference.

    This forum is about c++ development with Microsoft products. So for this kind of case on next time, I suggest you directly post on Samsung forum for better support.

    Your understanding and cooperation will be grateful.

    Best Regards,
    Sera Yu

    MSDN Community Support<br/> Please remember to click &quot;Mark as Answer&quot; the responses that resolved your issue, and to click &quot;Unmark as Answer&quot; if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact <a href=""></a>.

    • Proposed as answer by Baron Bi Monday, July 17, 2017 9:06 AM
    Monday, July 3, 2017 6:58 AM
  • Hi !

    I have posted same question to Samsung forum here:

    Like you see - there is no reply.

    I have posted also question here:

    They replied that bug was fixed long time ago, but  fix is not available in Samsung firmware.

    I've also contacted Samsung support - they informed that they informed developers, but informing is not the same as fixing - as you probably understand.

    I understand that resetting phone to factory defaults might solve the issue, but main problem is that developers should test against newest firmware, not old one. So there is no point of performing factory resetting.

    Currently I'm thinking about returning phone back to Samsung by 1 year warranty which is still valid.

    Friday, August 11, 2017 1:33 PM