SOTI Pulse Logo

Disable USB-Debugging Samsung Galaxy Tab Active 3 Enterprise Edition

Solved
AB
Alexander Behmer
CHRIST Juweliere und Uhrmacher seit 1863 GmbH

Hello,

We are currently trying to implement a mobile register on our Galaxy Tab Active 3 Enteprise Edition.

For this we need to deactivate USB-Debugging and adb functionality.

Normally i wouldn't see the problem in this since there is a feature control option for USB-Debugging to enable or disable this.

But for us it is already disabled in the profile but it is still enabled anyways.
If I disable it manually it works but after a restart it enables itself automatically.

Is there a way to permanently disable the usb-debugging?

thanks for the help

kind regards Alex

android usb-debugging
a year ago
Android
ANSWERS
RC
Raymond Chan Diamond Contributor
a year ago

Hi Alexander,

What you said is abnormal.   Do you have the same consistent behavior for multiple Galaxy Tab Active 3 devices?  Or just in some, which might have been used as test devices for development purposes, and possibily have Developer's option enabled manually in device's Settings and some ADB command(s) sent to the device before?

Maybe you should test again with a newly factory reset device, enrolled and deployed with your profile with youor mentioned feature-control option enabled.  If the same problem is still found, there might be some bugs/ incompatability in the device firmware.

AB
Alexander Behmer
a year ago

Hi Raymond,

yes it seems consistent over every tablet i try.
I have the same issue on a Samsung Galaxy Tab Active 5 Enterprise Edition. So the newest of this series.

I just enrolled one freshly after a factory reset and it has the same issue.

An unenrolled device does not have this issue though.

AB
Alexander Behmer
a year ago

After a bit more testing we identified the Problem.

If we have a Lockdown mode policy enabled it seems that the debugging mode is on in the background. Maybe it doesn't work but our register App regocnizes it as active.

If we disable the lockdown mode it works fine. The different lockdown modes don't affect the problem.

The Problem persists even with the newest agent and the newest Server Version as we tested it with out soti Partner.

MD
Matt Dermody Diamond Contributor
a year ago

I believe the Feature Control Profile is only active when the device is in User mode and not Admin mode. Typically when the device is in lockdown mode it is also in User mode and the Feature Control configurations will be active during that time. If you are exiting lockdown to verify if a Feature Control is applied try just disabling the kiosk while leaving the device in User mode. 

Solution
TK
Thorsten Konrad
7 months ago

Hallo Herr Behmer, ich bin gerade zufällig auf Ihren Post gestoßen. Ich bin ein Partner von SOTI mit dem Schwerpunkt MDM, AutoID und Mobility-Lösungen und bei SOTI vor allem mit SNAP unterwegs. In dem neu angekündigten Versions-Release wird SOTI komplett neue Möglichkeiten zum Umgang mit der Lockdown Funktionalität anbieten. Sind Sie hierzu schon im Bilde? Wenn Sie Informationen dazu möchten, stehe ich Ihnen gerne für einen Austausch zur Verfügung! 

RC
Raymond Chan Diamond Contributor
a year ago

Whether or not your register app "recognizes" USB debugging as "active" is not important.  To confirm if there is any loophole, do a test to have ADB port connected and see if any ADB command shell can send any command successfully to the device.

E
ENMod
a year ago

Thanks for posting on SOTI pulse. Thanks Raymond for responding to the post, your expertise and willingness to help are greatly appreciated!


Has your query been resolved? If not, or if you have any additional concerns, please don't hesitate to reach out. We are dedicated to providing assistance and support.


Also, if this post has helped you in solving your query, I would request you to mark the particular comment as "is solution", so that others may benefit from this information.

Technical Support, SOTI | Call Us | SOTI.net | Discussion Forum | Log a Case Online

Similar Discussions