Whenever I run my emulator for the first time, it shows up but doesnt start my app and I find no device in DDMS view UNTIL I reset the ADB. It happens always FOR THE FIRST TIME. But after I reset the ADB it works from then on.
Uninstall and reinstall Android on your system.
Related
When I try to run my application via Android Studio on a virtual device, or a physical device, my Kotlin app runs the first time, but afterwards I need to disconnect my device each time I want to publish it again.
When I click on "Run App" it just says "Install" an the bottom. When I click it, it says "Launching App". I've had this problem for some time now, and I hope somebody knows the solution for this.
I've tried rebooting and turning USB-debugging off and on. Both work the first time install, just like disconnecting and reconnecting the device. After that however, again it keeps getting stuck on "Installing".
On a virtual device u could try to Open AVD Manager and then click on Wipe Data from dropDown list in actions column
The next command enables phone call recording in OnePlus phones (may be others too):
adb shell settings put global op_voice_recording_supported_by_mcc 1
But after reboot its effect is disabled. My phone is OnePlus 6T.
How to make this setting persistent?
jOnePlus Tools is an answer. This application sets settings up on every reboot.
https://forum.xda-developers.com/oneplus-5/themes/app-enable-call-recording-boot-t3634292
This link has other root-required methods you might want to try.
Unfortunately, I am also trying to find a way without root. As the setting automatically turns off, sometimes before reboot, when you have an active some-country sim card, my hypothesis is that there is a "checking" program going on under the hood. If there is an adb command to turn off that "checking", the result should be permanent.
I also have a 6T, and what I could see about what causes recording to be disabled, is any application installation made by PlayStore.
If you keep the automatic update function of the applications deactivated, the recording remains activated, but anytime you do any installation on the PlayStore, the recording will be disabled and you will need to enable it with the command again.
I am developing an app for Android on my HTC Desire HD; at times during the App development the app crashes due to some reason or the other.
But once it crashes, it won't start in any case and the only solution is to restart my device.
I have tried to run it again using Ctrl+f11
I have even tried uninstalling the app from the device uninstaller.
Even uninstalled it using adb uninstall 'com.example.www' with a successful uninstallation.
It does not show any kind of log messages in logcat, just that killProcess, pid=xxxx
Can you please provide a solution to this; as my device takes 5 mins to reboot and as the app gets complicated, its crashes even more.
Thanks in Advance.
You can see all running processes which you can debug in DDMS perspective in Eclipse:
Check if your application is runing,if it is you can stop it by clicking the stop button near the screenshot one.
Or you can use the process id to kill the process in the shell if you have a SU rights:
adb shell
su
pkill #pid
At this moment, this error started with IDEA 11. I still did not find the right pattern but if a device or emulator are idle for a specific period of time (not long) and if I then try to push the project to a device/emulator and to attach a debugger, first appears a message that IDEA is trying to connect to ADB (a several message windows) and then the upload starts, the apps gets uploaded, then it fails with error:
Launching application: com.xxx/com.xxx.sMain.
DEVICE SHELL COMMAND: am start -D -n "com.xxx/com.xxx.Main"
I/O Error: Connection refused
The only solution is to close both emulator and IDEA or to disconnect a real device from USB cable.
Any ideas why this is happening? As I said it happened with both device and emulator so I cannot tell that it's up to a device/emulator.
EDIT
I tried restarting ADB via shell, it did not help either. This does not happen when I simply run the project, but only when I press debug.
EDIT 2 (18May)
I've noticed that this is happening when two IDEA's screens are opened in the same time. For example, I open another project and choose to open it in new window. I first run the app in window 1, and then in window 2, but then the popup "Trying to attach to ADB" keeps opening and closing. I see that memory increases for a couple of MB as each time a new popup is created. this leads to IDEA stop responding and I have to kill it.
I think this is a new bug.
I am trying to use Logcat to help diagnose my android issues. I frequently have a phone plugged in AND an emulator running. Sometimes I debug on the emulator, sometimes I debug on the phone, or maybe even a third device.
Logcat does not continue to show messages after a device is switched. How can I specify what Logcat does or force it to resume logging without restarting eclipse?
Insight appreciated
I've noticed this at times. Usually one of two things does the trick. First, open the Devices view, verify that the new device is showing, and then switch back to Logcat. That seems to kick Logcat into action again.
If that doesn't work, then in the Devices view menu, select "Restart ADB" (I think that's what it's called; I don't have it open at the moment).
If even that doesn't work, then kill and restart the ADB server from the command line and repeat the above.
If you are using Eclipse, switch to the DDMS perspective.
There, logcat will be showing the log of the selected device in the devices View
(Window -> Open perspective -> Other -> DDMS)
You coupld use the CLI for ADB and reattach the debug process to your switched device. Then Logcat will pick the debug msgs from that connected device. Whatever device is actively connected to ADB will output through Logcat