I have been experiencing a problem.
I'm trying to authorize my rooted android device (Asus Zenfone GO) for ADB.
Developer options are on and USB debug, as well. Unfortunately, if I plug the phone and start the ADB server on my pc, instead of showing the authorization popup on the phone, the following message is shown "Unfortunately, System UI has stopped." and the user interface crashes.
Any ideas about how to solve the problem?
Thank you very much!
Related
My device is connected using adb tcpip and the Logcat is not showing Log.i(TAG, "message"). Running abd logcat does not show the Log.i(TAG, "message") either. When using emulators or USB-connected devices, it is working fine. Any solution for this?
On your Android device, in Settings->System->Developer Settings, there is an option (off by default) that says "Enable Wi-Fi Verbose Logging."
Also restart your phone after changing the phone setting, if not working. Make sure to select the correct device used for debugging in logcat window.
also,
In the Device's Developer OptionS: make sure Logger Buffer sizes is NOT set to off
I would set it to the highest if your device can handle it.
What worked for me is this...
Activate "Enable Wi-Fi Verbose Logging" on your android Device
Add "ADB Wifi" to android studio
Run the app on your phone using cable (and make sure logs show)
Connect the phone using ADB, then remove the cable from phone.
Please note that: Step 3 might seem useless but it seems important because it acts as a way to authorize your phone to send logs when you go wireless. There after remove the cable, the logs will show.
com.android.ddmlib.AdbCommandRejectedException: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Error while Installing APK
When you first connect a phone to a new computer via USB Debugging, it will pop up a confirmation dialog ont he phone asking if you want to let this device debug. You need to click ok (you may need to toggle USB debugging on and off again to see the dialog again).
Yes, you are right but I got "Because an app is obscuring a permission request, Settings can't verify your response" error when I try to press "OK" in USB debugging popup menu in my phone....
Soluction:
I got this solution,https://www.reddit.com/r/GalaxyS8/comments/81r7xl/because_an_app_is_obscuring_a_permission_request/
What I do:
I uninstall night mode app from my mobile and now I am able to press ok button without any error.., and then app are installed in my mobile phone from Android Studio.
I am writing an app and just last night I wanted to try it on my device. So, I enabled USB debugging on my device, connected it to my machine and issued
react-native run-android
This installed and run my app on device just as expected. All good...
But, this morning, I tried opening the same app I installed last night as explained above, by finding the app on my device and tapping on it. I get error "Hot loading isn't working because it cannot connect to the development server."
OK, I disabled hot reloading on my device and run app again. This time app showed on device without error but my app should show one image from my resource folder and it is not although it was showing it last night.
So, I shaked device to show dev menu and tap on Reload to reload my app and then I get error "Could not connect to development server."
Why am I getting these errors out of a sudden?
The only difference btw me running my app last night and this morning is that last night, I had enabled USB debugging, was connected to my laptop through USB cable, and was starting the app through the terminal.
That deployed my app to device and from that point, I would expect that once the app is deployed, it does not care any more about whether packager is running or USB debugging is enabled. It should just run.
I am trying out this adb shell procedure to store all my android apps to the SD Card on my new samsung galaxy tab 4.i have tried the following shell command on my laptop while staying connected with my tab via usb cable and it showed me an error.i am attaching the screenshot here.it keeps on saying "Device Unauthorized".how can i resolve this?
Your device is unauthorized. This means that you either have USB debugging off, or the adb server has messed up.
If you have the USB debugging on, try to revoke the USB debugging and restart the adb server, as suggested in
https://stackoverflow.com/a/25546300/3970830
After connecting the device, you have to accept the connection in the dialog on the device screen.
The error message is giving you the solution. Check your device for a confirmation dialog. It should be asking you to authorize the computer to connect, or something to that effect.
I am having trouble running my application on a particular phone. It runs correctly on a different phone and on an emulator. I have the standard unauthorized issue coming up in my ADB logs:
PropertyFetcher: AdbCommandRejectedException getting properties for device [My Device's ID]: device unauthorized. Please check the confirmation dialog on your device.
When I try to run the application anyway on the phone in question, it is able to target the phone and runs the app, but immediately hits a null pointer (that isn't present when running on the other phone or the emulator).
Before you insta-lock this question, I've tried everything in all of the duplicate questions. Specifically
I have set the target to show chooser dialog
I have reset the ADB server
I have revoked and re-accepted permissions, and tried changing the USB type
I have confirmed that Enable ADB Integration is checked
None of which worked.
Furthermore, the same phone was working earlier (not sure what changed), so it's not a bad USB cord.
The phone is a new Nexus 6, and the old phone that works correctly is a Samsung Galaxy S4.
Running adb devices in the android studio terminal shows:
List of devices attached
[My Device's ID] device
Which implies (?) that it is in fact authorized.
You have missed the Fingerprint Certificate Authorization popup in your phone when you connected it. To solve disconnect and plug-in again.Wait for some seconds and a confirmation popup will appear. Click OK.