I'm following along with the tutorial provided by the Android Developers official site and using the help files in Android Studio, but I'm finding out of date screenshots and feeling very confused and a little frustrated.
I have a Pixel 2 connected via usb.
I've enabled developer mode on the device.
I've got it not sleeping when connected via USB.
I've enabled USB debugging in the Developer Options on the phone.
...I just need to figure out how to get my Mac to see it via Android Studio.
The tutorial alludes to a configuration screen that I don't see in studio. I see something similar but the device drop down is disabled.
Hit the sync button,
Wait for downloads(don't stop the hidden downloads)
Restart if necessary, wait for the first invocation to complete work.
Then enjoy your first app.
Happy coding :)
answer: hit the sync button (elephant/mouse looking icon with a diagonal arrow), wait for downloads, don't stop the hidden downloads, then restart if necessary, wait for first invocation to complete, ...then it will (hopefully) work.
Got myself a Xiaomi Pocophone F1.
However, I cannot compile android application on the phone, because it won't let me.
It seems I must specify explicitly the source of the installation media and Delphi is not on the list :)
So, does anybody know perhaps what I must do to get the compiler working ?
USB debugging is on and developer options are visible.
Thank you all for suggestions.
The issue on that particular phone is that you have to (in developer options under debugging) enable "Install via USB" and "USB debugging - security settings").
It is not as simple as it sounds because you have to create an account on their site (https://account.xiaomi.com/) first. Creating the account for this particular options implies that you can not change the phone's region any more. Why they chose to do this,I do not know.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
While I allow USB debugging, tap on OK button, Messaging has comes
because an app is obscuring a permissions request, Settings can't
verify your response
The error is coming in allowing USB debugging.
Go to Settings -> Apps -> Special Access -> Draw Over Other Apps
See which apps have permission to draw over other apps, and turn them off one by one until the problem goes away.
I had the same with my tablet. I restarted tablet and it worked.
Turn off shortcut ball (or) assistive ball and then try it will work
Model : Oppo
I found a post on XDA Forum that solved that problem. Here it is:
I solved this as follows:
- Go to Settings > Apps > Settings icon (at the bottom).
- Then Advanced > Special access > Draw over the other apps.
- At the top right, in the scrolling menu, choose "Show system processes".
- Select "Floating dock" and disable "Permit drawing over other apps".
May be DevMike trick is working but I solved this by uncheck the option of verify apps over USB.
Setting > Developer options > verify apps over USB & uncheck the verify apps over USB.
Note:
This setting specifies whether your device should allow Google to inspect apps installed over USB for possible harmful behavior.
In order to install apps over USB you must also have USB debugging enabled and compatible software (such as the ADB tool supplied by Google to developers, though other software can also take advantage of this ability) on the connected computer.
App developers may want to have this service disabled in order to speed up the process of loading their app onto their device for testing. If you are installing apps that you did not develop yourself over USB, it is recommended that you enable this.
This setting has no effect on apps that are installed on the device itself, either from the Play store or from other sources.
The best way is to put Android OS in Safe-mode.
For Samsung phones:
Hold the power button until three buttons will appear on the screen.
Hold the power-off button on the screen for a couple of seconds while the safe-mode prompt appears.
This will restart your phone to a safe-mode.
After you're done, you can bring the phone to normal operation by choosing the safe-mode prompt from the notifications.
I had to turn off navigation gestures under the action and gestures settings.
Go to Settings → Apps → Special Access → Draw Over Other Apps
turn off YouTube.
Another cause is the Smart Pixels battery saving feature that is present on some custom Android ROMs; ie Resurrection Remix. Disabling Smart Pixels will solve the problem.
In Resurrection Remix the setting is in Settings > Resurrection Tools > Interface > Smart Pixels > Enable Smart Pixels.
Note:This setting is Disabled by default.
Ok, disable Smart Pixels in Resurrection Remix ROM settings. This answer is ONLY for those running R.R. with Smart Pixels enabled. This setting is not an app, so it doesn't show up under the "Display Over Other Apps" listing in settings. Credit to Jebtrix
Simple answer is to please restart your device or mobile
it will work...
Enter into the safe mode and try connecting it. It works!
How to enter safe mode?
Power off your device.
Power on the device and press and hold the volume down key the moment you see the boot animation, until it boots up.
You could able to see safe mode in left right corner.
Try connecting now.
It will work.
Restart device to exit safe mode.
P.S: entering into safe mode might be different for some devices. Try Googling for your device model, if it doesn't work!
I fixed the issue by uninstalling an App named "Mobile Go"
it was having permission of running on top of screen, i think it's related to capture screen.
Regarding your permission issue on your phone, the problem may be caused by an app called "File manager" Either you can uninstall it, or if you want to keep it, go in "Settings -> Applications -> Settings -> Draw over other apps" and set the value to "No" for "File manager". If you don't find still...Go to settings and search 'draw over other apps'. Restart the device. worked for me!
Turning off Assistive/Quick/Shortcut ball did the trick for me.
Also, try revoking the Debugging Permissions from Developer Options under USB debugging, and setting connection mode to Media Transfer.
Installing PdaNet+ App and Driver might help too.
Opting for onscreen buttons instead of navigational gestures worked for me.
#Terry Carmen's answer is acceptable for me, the problem is occuring with Mobile Go app, revoking the access permission to Draw over the apps solved!
In my case probably messenger bubble was source of problem. After cloase messenger app it was ok.
for me I had to turn off Edge Gestures on the Accessibility Services!
The problem is that you have the DU Recorder app running. You can see the orange camera icon in the left side of picture you attached. What you need to do is to close the app. You can do it by dragging the camera icon to the X.
It's obvious that the problem is due to some running app is preventing you from getting permission.
Combinating the answers above from Terry Carmen and Andrew,
JUST TURN OFF ALL APPS AND TRY AGAIN
and it will work.
Lock and Unlock your device. That's all you need to do.
Be aware that Google is telling that not all cables are able to use MTP transfer.
If you are displayed wrong icons at the beginning it might be that the USB cable needs to be different and most likely unique to the device or at least have transfer capability.
Be aware if MTP does not work, your cable might be wrong.
I have a situation:
1. Samsung 7 has a strange bug in my app.
2. This device is 10000 miles away from me.
What are the opportunities for debugging this device remotely.
When tester on the other side can do everything.
I tried adb tcpip <port>
but device ip can be only local(192.168.....)
The rude way is to get Android Studio there and install team viewer on the phone. It's not working every time.
And when we have 1 hour intersection it's difficult to support.
Is there any other way?
Have your user enable Developer Options on the device. You should already know how to do that.
See whether the device has Take Bug Report and/or Bug Report Shortcut settings. If you enabled Bug Report Shortcut a Take Bug Report option will appear when pressing/holding the power button.
Instruct your user to take a bug report -- either through Developer Options, or from the power menu -- as soon as your app crashes.
As for the APK you send to your user, make sure debugging is enabled, so you get all your log messages. If you obfuscate the APK, be sure you keep your mapping files handy.
If you have some idea of where the bug is happening, an option could be to set up something like http://www.acra.ch/ and send your tester a new apk.
This way when the bug is provoked, given you set up useful log events, you will receive information about the crash or bug. ACRA lets you include the LogCat as well, which is pretty useful.
There are several options:
-Build APK and send it to the phone. Install and check/try again.
-Create Android Virtual Device identical to the model located remotely, install Samsung Android firmware.
There is no clear solution about debugging out of local network.
You could try something like LogmeIn for Android - this way both devices will be in the same network.
Once done, just do usual adb connect ipadress If t refuses to do so first, try enabling ADB over WiFi option
I've searched online about getting crash logs from android and/or ios devices but could not find anything. I am testing an external app atm and have solid steps to reproduce a crash. Though, I can get a crash log/dump for the developer by using Eclipse... any guides on how to do so? Thanks.
To be able to see log calls and other info, you have to enable Debug Mode in your device.
You also need a specific driver to use your device with ADT. If you don't have that driver you can download a generic one from google in SDK Manager > Extras.
But be aware that "commercial" apps (downloaded from Google Play) are not debuggable,
or at least should not be.
First install the driver software for your mobile. Enable your debugging mode in your mobile. Go to DDMS->windows->show view click device. Here u can able to know wether ur device is connected or not.