I think it is a no go but I had to write this somewhere even if maybe I am the only one with this kind of problem (googled about that and got no results so far). This make learning difficult, debugging almost impossible on real device. Using the 'normal' chrome dev tools, It seem that I can only see some exceptions (if they raise from my code) and console.log. I have another device, the One+ but with this one, I can't use the dev tools (nuclide inspector) because adb reverse don't work with API 19, and I must keep this device to API level 19. See all available actions: Click the arrow to expand the Library. In the Automator app on your Mac, find an action by doing any of the following. Each action is a single step in a workflow.

until I restart the app by manually killing it's instance (I suspect Samsung modification to be the cause of that behavior). Actions in the Automator Library are grouped into categories by app or type of file or data. If I start the app (not from a previous instance), then the menu is visible, and as soon as I dismiss it, it is back again (infinite loop hideshowhideshow.), and I have to hit the 'recent app' button then come back to the app to make it invisible, but then it is gone forever. I can shake the device but nothing happen (a chance it didn't slip of my hand yet )) I have a Galaxy S6 here at work and I can't bring the menu. Hi, I agree with shaking the device to bring up the dev menu is not efficient.

Adb enabler automator mac