I have been dealing with this error for a week when I`m trying to emulate my app using virtual device in android studio.
Adb rejected shell command (getprop) closed
I have tried updating SDK according to the device, restarting it but none of those helped at all. I searched but did not find any answers that deals with this specific error.
Some clue would mean great help. Thanks.
( A humble request, if you do not like the question please downvote but still do not use abusive words )
Related
After noticing that Logcat messages were not showing up in Android Studio, I tried every solution out there, and nothing worked. I eventually tried the command adb devices and sure enough my device was there, but as soon as I tried adb logcat it returned "logcat read failure".
Developer settings are turned on, and so it debugging. I'm on a rooted phone running 7.0 Nougat, with an open bootloader.
Could it be that I'm rooted and it somehow messed up some permissions? I've never encountered this issue before, even on a rooted phone.
Logcat works when using an emulator.
I was facing the same issue as yours. Then I asked the developer of the ROM if he is facing the same issue. The developer said that it is working fine for him. So I flashed the ROM again and noticed that logcat was properly working. So it was clear that the problem was due to some apps or changes that I did on the ROM.
After debugging , I found that it was ARISE Sound System that was the root cause of this problem for me.
So if your are using ARISE Sound System dirty flash the ROM to remove it and check if this solves the problem for you. For now I am only using Viper4Android.
Did you try to use alogcat ROOT app. Is it work on the device? App link
So, post here right answer because I spent a such many time to solve this.
Ok, when in Android Studio I start debug an app on real Smart TV device I saw in logcat nothing. When I ran "logcat" on device directly I got "logcat read failure"
A year before I removed "logd" from "system/bin" and this was a problem.. but I forgot about it. Even if I've copied it back it doesn't work. Because SELinuxe Security Context
Solution: give the logd it's context back with a chcon util.
More details you can find here: https://forum.xda-developers.com/t/guide-how-to-restore-logd-to-your-device-fix-adb-logcat-read-failure-or-empty-logs.3512946/#post-69930494
I am not able to install the ADB drivers/Oem drivers for my one plus one.
I have tried the following three methods given by the link and restarted my system
http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
PLEASE HELP
I should have posted this much earlier
This was a bug in OPO android lollipop. Many devices(NOT on all ) were not able to connect to the windows using drivers. This was already fixed in marshmallow.
For more details refer:
http://www.idigitaltimes.com/downgrade-oneplus-one-cm12-cm11-fix-lollipop-bugs-manual-process-guide-437875
This question already has answers here:
Cannot create or edit Android Virtual Devices (AVD) from Eclipse, ADT 22.6
(14 answers)
Closed 8 years ago.
Trying to create a new AVD specifically for Android 2.3.3 Gingerbread.
I've cloned a device based on the 3.7" FWVGA slider as indicated by this image
This shows up in the "Device Definitions" tab
When I get to the "Create new Android Virtual Device (AVD)" window, I believe I have properly filled in the form as shown here
However, when I go to click "OK", which is a live button and not grayed out, there is no response at all from Eclipse. The application doesn't freeze or anything it just does not allow me to finish creating the new AVD. These specs were as indicated by my class but any advice that could help rectify the situation would be greatly appreciated while I await a response from my professor.
This is a bug in 22.6. We're preparing a 22.6.1 update that will fix this.
I think you can use the standalone AVD Manager, running tools/android avd from a shell to create one.
Don't mark this as a duplicate. Let me explain what's wrong and tell you what I've done. So here's my problem. When I open Android Studio, it gives me an error like so:
So then I went to my windows firewall settings. Here is what I have:
As you can see, Firewall is off. Then, I went to my antivirus security program and turned the settings off there:
As you can see here too, I disabled Smart Firewall. Then, I opened Android Studio again. I got the same error here too.
I pressed the OK button and moved on. Then, Android Studio loaded up and everything. After that, ADB started loading. This is where the real error occurs.
I have also tried it with Eclipse, but it also says ADB not responding. For the past month or so, Android Studio has been working fine. I have never gotten these error or warning messages with Android Studio before, so this is rather new to me.
Here is what I have tried:
In cmd, adb kill-server then I pressed the restart button on the ADB not responding message
Restarting computer
Turning USB Debugging on and off on my Nexus 5
So, I really can't find a solution to this. Any help regarding this problem would be extremely appreciated.
Sometimes it just gets into a mess. Close your ide then Go to processes and terminate all adb processes.
Then when you open up android studio it should kick off adb again fresh (or you could run something like 'adb devices' from command prompt before opening the ide if you're worried it gets in to a bad state while the ide is waiting for it to initialize)
If none of that works you could also reboot your device. I've very rarely found it necessary, but it has helped me in the past
Kill processes bas_deamon & bas_helper Then press restart for ADB and it will work.... this what I do in WIndows 7 when I face this issue.
You may want to make sure your phone is unplugged. When it is plugged in, I have noticed this happening and the solution for me (which may be Mac specific) is to unplug my phone from the computer.
I had the same error messages, but a different problem.
Port 5037 was not in use, but still adb couldn't start.
So after hours of trying I finally realized, that it was an installed VPN-client (Checkpoint Endpoint Security). Even though there was no connection (and I even killed the process) the connection didn't work. After uninstalling everything worked like a charm.
Maybe it helps someone who reads this question, because everywhere else you just read about the blocking port. And in addition, while the client was installed some other TCP-based Frameworks and even Windows-Remotedesktop stopped working too.
This happened to me as well. I solve it by terminating all process that is using port "5037" which is, by default, the port used by adb.
Sir,
Actually Sometimes our parent control software interfere with it. but after turning off its real time protection , we got this error. so basically you need to check the whether we are using 32 bit Android Studio or 64 bit. just try to av same bit operating system as of Android Studio , u ll get this error removed after that. :)
For Windows: add a system variable as following and then restart your Computer then try again - it will be OK
ANDROID_ADB_SERVER_PORT
10501
I had the same problem on Mac OS X. After some research I've found a bad entry in my /etc/hosts file for my localhost (192.168.99.100 localhost).
I removed the bad line and left the line 127.0.0.1 localhost for ipv4 and some entries for ipv6 in.
After a reboot the Android Studio was able to communicate with adb and found my connected Android device again.
Hey Everyone,
I have had this working before, but all of the sudden it stopped working, I have reinstalled the drivers, restarted the adb server, restarted the phone and computer a few times, and it just won't work. The thing that is weird about it is that I had it working before, and it just stopped working, if I never had it working before, then I would assume I just didn't have something installed correctly, but it must be if it worked before. Any ideas for anything I can do to fix this, I am getting tired of using the crappy emulator :p
Thanks,
WWaldo
Edit: Editing the edit, because I am dumb and forgot I had the copy mode on...no new info on the issue then :(
It can be many things:
bad device drivers: try removing all usb drivers for the device and start from scratch
bad mb drivers preventing the recognition of any usb: look into the device manager for trouble
as EboMike said, bad cable: do you hear the sound when the device is plugged in?
phone not in debug mode: adb requires usb debug mode. Check the phone settings
bad ROM: you mention "the rom I am running": flash another one and check