Been browsing this group, found some great answers on here, but none have helped me with my problem.
We have a new ( less than 1 month old) dji device, called a smart controller, it’s basically an android tablet, it’s built into our drone remote controller.
A few days ago it came up wirh an error message duijg # Flight, which was basically a memory overflow.
So we suspect the internal memory has been filled by the local cache files.
The issue is that this has now stopped the device even starting up.
We have tried installing drivers on our pc, including the firmware update application from dji, but this just fails every time we try it.
Today we have been following advice on here, and using Rhe ADB program on our pc, we do at least get a connection to the device.
However we can’t do anything withnht program.
Each time we try any command we get this message
Device unauthorised
This adb server $adb_vendor_keys is not set.
We have tried deleting the public key, on the pc, and creating a new one, but we can’t write that new key to the device.
We are not programmers and don’t know code, so we are doing all this on our pc in a command line prompt.
Before we give up and send it back to China, anyone got any ideas on what we might be able to do?
Thanks in advance.
Without being able the use the physical device. I do not believe there is anything that you can do. Generally speaking the error you are seeing is caused due to a permission prompt that would appear on the device authorizing your computer to interact with it.
If you could get the device to display and disable and re-enable usb debugging a security prompt should display when you connect it to your PC. Without that option I would recommend sending it back
Related
I am communicating via desktop to a Samsung Android phone. OS is latest. I have done "Allow always" on the same desktop I use every day for authorization of the key for secure debugging. But to my surprise, I keep getting pop-up authorization message on the phone after a few days. I do not want to kill-server all the time to make it work or anything. However, I have restarted the phone as well. My USB cable is perfect. Why is the certificate getting revoked and I have to authorize again after a few days?
Thanks
There a wide variety of possible issues with ADB authorization. You might have multiple Android SDK installs on your path, you might have bad permissions in your ~./android folder. There's a ton of answers here that might give you some ideas of where to look from the problem ADB Android Device Unauthorized
Also instead of killing the server you might be able to turn USB debugging on and off to circumvent this issue as well (though this is still tedious)
Persistent error on Samsung Galaxy Note 5
this is a weird issue that i am having for almost a year now, i'll try to be brief.
background story (What i think happened)
I own a Chinese aftermarket car infotainment system, running android 4.4. So, being the obsolete piece of **** that it is, i started digging around, and found out that it has something called Device link or something along those lines.
you have to download an app called EasyConnection from the play store, enable developer mode, and enable usb debugging, i know that's not the safest thing to do with Chinese stuff, but that's the only option i have at my disposal, so i have to manage.
anyway, it worked flawlessly for a year or so, then suddenly it refused to connect, with an endless connecting message. and my phone started giving me the Attention message, this was a year ago, and never worked since.
Attention
The connected device is unable to access data on this device. Reconnect the USB cable and try again.
Android File Transfer or Samsung Smart Switch must be installed on Mac OS X devices. To download Android File Transfer, go to https://www.android.com/filetransfer, or to download Samsung Smart Switch, go to https://www.samsung.com/smartswitch.
Phone behavior
Since then, whenever i connect my phone to my PC, either running windows or linux, it displays the Attention message. i can access files on my phone no problem, and it is not driver related, as this happens regardless of what driver is installed, or in the case of linux, no driver is required.
Android development
Now, a couple of months back, i decided to dabble in android development , as i have a couple of sysadmin years under my belt, and a beginner level knowledge of a couple of programming languages, so i thought android development would be fun, but here is the problem.
While my device is hooked up to android studio, i get this aforementioned error on random long intervals, but i am able to run my apps from android studio to my phone no problem. So i started to link everything together, and thought to seek help here on reddit after some fruitless internet diving.
note
I did a factory reset for my phone a month or so ago, so the only step remaining in my mind right now is to re-flash the stock firmware (i'm on stock for security reasons), but i am reluctant to do so because of the hassle of re-configuring my device again.
I'm hoping to accomplish the following :
Resolve the cause of the error.
See if my car system works with my phone after the error is resolved
Any help would be greatly appreciated.
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
My phone cannot connect to the android ADB but I need to check its logs since it seems to be getting unique errors from an app I made. aLogcat app is outdated and getting "bug reports" from developer options is unreadable for me.
Is there any way for me to get a logcat report of my app while I'm running an application on it?
Edit: I use a droid Mini phone and it won't connect to eclipse. After installing the specific driver for the device it worked.
First of all, consider making ADB work for your device. Provided this is totally impossible, consider using ACRA. If you don't want to integrate fully with it, check their logcat collection code.
I have a game built on Unity running in an android device. In theory it should be possible to step through the unity code by attaching to AndroidPlayer at runtime.
Well I followed the rules on how to do this.
1) Created development build with script debugging enabled.
2) run the app with script debugging on wifi that has the player.
Initially it worked. Then perhaps a change or two in my network, and I no longer see AndroidPlayer as an option in MonoIDE to attach to. Its vanished and for several days now I am not able to debug. Not only that but i really don't know where to check this. I yanked out the ethernet cable so device and Mac are both on same wifi running on single subnet. Nothing seems to help. But what really dissappoints me is there is really nothing to check in Unity when this type of thing happens. It just try to attach to proess. Hope AndroidPlayer process is there and if its not. Tough luck.
PS: I should add I am on Unity Pro 4.2.04f. It worked fine, then who knows what and it stopped finding the AndroidPlayer. What a mess!
PS: Things I have tried. Pinging to ip address, and telneting to port (successfully to ip:5555)
Note: This is not the Android Debugger I am talking about but a player that needs to be running in the app, and visible to MonoIDE in order to debug.
What I am really trying to understand is what are my options when I cannot see AndroidPlayer as an process to attach to?How does one debug this problem? Are there things in the logg if AndroidPlayer is sucessfully running? How could monodebug not see it? How do I know it it is or is not running on the devices.
Thanks
Have you looked at the IP address of the Android device and attempted to ping it? I find that, here in the UK, our BT provided "home hub" will often, randomly, stop routing traffic between devices on the same network.
I find that if I can't debug (and I believe Unity 4.2 still used wifi debugging) then I usually can't print either and it's because the router has stopped routing traffic.
A quick reboot of the router usually fixes it.
PS Just read about the ping being successful. Have you downloaded and run "wireshark" to see what network traffic is happening? At least that will show you what is happening on the network layer.
Other thought, any sort of firewall running on the debugging machine?
Try to:
1) Disable antivirus
2) Disable firewall
3) Deinstall Xamarin (in case when you use VS for debugging)
That did help me when I had the same problem