Trying to run the Dalvik Debug Monitor and can't seem to get it figured... currently my CMD box shows what is written below and my phone shows offline.
09:34:53 E/adb:
09:34:53 E/adb: This application has requested the Runtime to terminate it in an
unusual way.
09:34:53 E/adb: Please contact the application's support team for more informati
on.
09:34:58 W/DeviceMonitor: Failed to connect to client '1629': An existing connec
tion was forcibly closed by the remote host
09:34:58 E/DeviceMonitor: Adb connection Error:An existing connection was forcib
ly closed by the remote host
09:34:59 E/DeviceMonitor: Connection attempts: 1
09:35:01 E/DeviceMonitor: Connection attempts: 2
09:35:03 E/DeviceMonitor: Connection attempts: 3
09:35:05 E/DeviceMonitor: Connection attempts: 4
09:35:07 E/DeviceMonitor: Connection attempts: 5
09:35:09 E/DeviceMonitor: Connection attempts: 6
09:35:11 E/DeviceMonitor: Connection attempts: 7
09:35:13 E/DeviceMonitor: Connection attempts: 8
09:35:15 E/DeviceMonitor: Connection attempts: 9
09:35:17 E/DeviceMonitor: Connection attempts: 10
09:35:19 E/DeviceMonitor: Connection attempts: 11
09:35:26 E/adb:
09:35:26 E/adb: This application has requested the Runtime to terminate it in an
unusual way.
09:35:26 E/adb: Please contact the application's support team for more informati
on.
09:35:31 W/DeviceMonitor: Failed to connect to client '1551': timeout
09:35:32 E/DeviceMonitor: Adb connection Error:An existing connection was forcib
ly closed by the remote host
09:35:32 E/EventLog: An existing connection was forcibly closed by the remote ho
st
java.io.IOException: An existing connection was forcibly closed by the remote ho
st
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(Unknown Source)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
at sun.nio.ch.IOUtil.read(Unknown Source)
at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
at com.android.ddmlib.AdbHelper.read(AdbHelper.java:640)
at com.android.ddmlib.AdbHelper.read(AdbHelper.java:616)
at com.android.ddmlib.AdbHelper.readAdbResponse(AdbHelper.java:216)
at com.android.ddmlib.AdbHelper.setDevice(AdbHelper.java:734)
at com.android.ddmlib.AdbHelper.runLogService(AdbHelper.java:469)
at com.android.ddmlib.AdbHelper.runEventLogService(AdbHelper.java:445)
at com.android.ddmlib.Device.runEventLogService(Device.java:290)
at com.android.ddmuilib.log.event.EventLogPanel$8.run(EventLogPanel.java
:454)
09:35:32 W/DeviceMonitor: Failed to connect to client '1580': An existing connec
tion was forcibly closed by the remote host
09:35:33 E/DeviceMonitor: Connection attempts: 1
09:35:33 W/DeviceMonitor: Failed to connect to client '1620': Connection refused
: connect
09:35:34 W/DeviceMonitor: Failed to connect to client '1629': Connection refused
: connect
09:35:35 E/DeviceMonitor: Connection attempts: 2
09:35:37 E/DeviceMonitor: Connection attempts: 3
09:35:39 E/DeviceMonitor: Connection attempts: 4
09:35:41 E/DeviceMonitor: Connection attempts: 5
09:35:43 E/DeviceMonitor: Connection attempts: 6
09:35:45 E/DeviceMonitor: Connection attempts: 7
09:35:47 E/DeviceMonitor: Connection attempts: 8
09:35:49 E/DeviceMonitor: Connection attempts: 9
09:35:51 E/DeviceMonitor: Connection attempts: 10
09:35:53 E/DeviceMonitor: Connection attempts: 11
09:37:04 E/DDMS: device offline
com.android.ddmlib.AdbCommandRejectedException: device offline
at com.android.ddmlib.AdbHelper.setDevice(AdbHelper.java:736)
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:373)
at com.android.ddmlib.Device.executeShellCommand(Device.java:276)
at com.android.ddmuilib.SysinfoPanel.loadFromDevice(SysinfoPanel.java:15
9)
at com.android.ddmuilib.SysinfoPanel.deviceSelected(SysinfoPanel.java:12
6)
at com.android.ddmuilib.SelectionDependentPanel.deviceSelected(Selection
DependentPanel.java:52)
at com.android.ddms.UIThread.selectionChanged(UIThread.java:1680)
at com.android.ddmuilib.DevicePanel.notifyListeners(DevicePanel.java:752
)
at com.android.ddmuilib.DevicePanel.notifyListeners(DevicePanel.java:740
)
at com.android.ddmuilib.DevicePanel.access$1100(DevicePanel.java:56)
at com.android.ddmuilib.DevicePanel$1.widgetSelected(DevicePanel.java:35
7)
at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at com.android.ddms.UIThread.runUI(UIThread.java:497)
at com.android.ddms.Main.main(Main.java:103)
09:37:12 W/ddms: Unable to get frame buffer: device offline
09:37:14 W/ddms: Unable to get frame buffer: device offline
09:37:31 E/DDMS: device offline
com.android.ddmlib.AdbCommandRejectedException: device offline
at com.android.ddmlib.AdbHelper.setDevice(AdbHelper.java:736)
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:373)
at com.android.ddmlib.Device.executeShellCommand(Device.java:276)
at com.android.ddmuilib.SysinfoPanel.loadFromDevice(SysinfoPanel.java:15
9)
at com.android.ddmuilib.SysinfoPanel.access$300(SysinfoPanel.java:54)
at com.android.ddmuilib.SysinfoPanel$3.widgetSelected(SysinfoPanel.java:
274)
at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at com.android.ddms.UIThread.runUI(UIThread.java:497)
at com.android.ddms.Main.main(Main.java:103)
09:37:40 E/DeviceMonitor: Adb connection Error:An existing connection was forcib
ly closed by the remote host
09:37:40 W/ddms: 'adb kill-server' failed -- run manually if necessary
09:37:41 E/DeviceMonitor: Connection attempts: 1
Click to expand...
Click to collapse
perhaps try the last piece of advice it provides,
adb kill-server and then ./ddms which should auto start the adb server again.
if you're on windows, might give it a reboot.
sometimes it can be odd when plugging/unplugging phones, etc.
also, if you're using eclipse for application development (your logcat of errors shows eclispe, eclipse will sometimes initiate an adb connection and prevent another instance of adb from establishing a connection .. this is usually the issue that i run into!
Thanks, ill try this when I get home from work. Hopefully this will solve it.. new PC problems always suck
I caused water damag to my Laptop for about 2-3 seconds. Although it is booting now after about 2 days to dry.. too nervous to play with it yet. (Hopefully I get lucky)
Supra RCMix Shooter
Related
I've got ADB 1.0.26 running on my Windows 7 x64 and Eclipse SDK 3.6.2 with ADT 10.0.1 SDK tools r10, and I've got all the Android SDK versions installed.
When I connect my phone to the computer in debug mode, and type `adb devices` into the command prompt, my phone shows up. It's an Inspire 4G. I can `adb shell` into the device and `ls`, so I'm assuming that the adb/driver/phone part of the chain is working properly.
Now, if I connect my phone and go into Eclipse, I get:
[2011-03-28 17:46:33 - DeviceMonitor]Adb connection Error:An existing connection was forcibly closed by the remote host
[2011-03-28 17:46:34 - DeviceMonitor]Connection attempts: 1
[2011-03-28 17:46:36 - DeviceMonitor]Connection attempts: 2
Click to expand...
Click to collapse
[...etc...]
[2011-03-28 17:47:53 - DeviceMonitor]Connection attempts: 10
[2011-03-28 17:46:54 - DeviceMonitor]Connection attempts: 11
[2011-03-28 17:47:00 - adb]
[2011-03-28 17:47:00 - adb]This application has requested the Runtime to terminate it in an unusual way.
[2011-03-28 17:47:00 - adb]Please contact the application's support team for more information.
[2011-03-28 17:47:04 - DeviceMonitor]Adb connection Error:An existing connection was forcibly closed by the remote host
[2011-03-28 17:47:05 - DeviceMonitor]Connection attempts: 1
[2011-03-28 17:47:07 - DeviceMonitor]Connection attempts: 2
Click to expand...
Click to collapse
etc, etc... This loops forever.
It doesn't matter if I start Eclipse and then connect the phone, or if I connect the phone and then start Eclipse.
I don't think it should matter, but my phone is an Inspire 4G which is rooted and running Revolution 4G 3.2
As suggested somewhere else, I've tried resetting ADB in DDMS but that has no effect.
i have the same problem... can anyone help me please?
This happens to me too sometimes.
To solve this I have to this:
- close the IDE (in your case Eclipse... )
- open up cmd, and type: adb kill-server
- Start Eclipse and it should work again
http://code.google.com/p/android/issues/detail?id=12141
Hello, there.
I installed void #e a while ago on my O1, everything went smoothly until I had to setup a VPN with L2TP/IPsec.
After poking around with adb logcat, I found that the bundled kernel (mik_os's one) missed support for NETKEY sockets, IPSec over IPv4 and PPP altogether, so I rebuilt the kernel from source adding all missing options to .config.
I flashed the new kernel, boot it and tried to start the VPN, but it failed again.
This time - however - racoon was able to set up an IPsec security association with the remote host, but pppd complained about missing PPP support in kernel:
Code:
I/racoon ( 4330): ISAKMP-SA established <scrubbed>[500]-<scrubbed>[500] spi:<scrubbed>
I/racoon ( 4330): initiate new phase 2 negotiation: <scrubbed>[500]<=><scrubbed>[500]
I/racoon ( 4330): IPsec-SA established: ESP/Transport <scrubbed>[0]-><scrubbed>[0] spi=<scrubbed>(0x<scrubbed>)
I/racoon ( 4330): IPsec-SA established: ESP/Transport <scrubbed>[500]-><scrubbed>[500] spi=<scrubbed>(0x<scrubbed>)
I/mtpd ( 4532): Tunnel established
D/mtpd ( 4532): Received ICRP (remote_session = 65060) -> Sending ICCN
D/mtpd ( 4532): Received ACK
I/mtpd ( 4532): Session established
I/mtpd ( 4532): Creating PPPoX socket
I/mtpd ( 4532): Starting pppd (pppox = 13)
I/mtpd ( 4532): Pppd started (pid = 4533)
I/pppd ( 4533): Using PPPoX (socket = 13)
E/pppd ( 4533): This system lacks kernel support for PPP. This could be because
E/pppd ( 4533): the PPP kernel module could not be loaded, or because PPP was not
E/pppd ( 4533): included in the kernel configuration. If PPP was included as a
E/pppd ( 4533): module, try `/sbin/modprobe -v ppp'. If that fails, check that
E/pppd ( 4533): ppp.o exists in /lib/modules/`uname -r`/net.
E/pppd ( 4533): See README.linux file in the ppp distribution for more details.
I/mtpd ( 4532): Received signal 17
I/mtpd ( 4532): Pppd is terminated (status = 4)
D/mtpd ( 4532): Sending STOPCCN
I/mtpd ( 4532): Mtpd is terminated (status = 36)
I double-checked /proc/conf.gz and sure enough it contains all ppp options:
Code:
# zcat /proc/config.gz | grep PPP
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_MPPE=y
CONFIG_PPPOE=y
CONFIG_PPPOL2TP=y
CONFIG_PPPOLAC=y
CONFIG_PPPOPNS=y
I noticed in mik_os's sources that LG also set CONFIG_ANDROID_PARANOID_NETWORK to y, while in mik_os's build it is set to n.
Does anyone know if they are related and/or if I'm running into another issue (permissions, maybe)?
Thanks in advance
Sure enough, it was CONFIG_ANDROID_PARANOID_NETWORK.
For future reference, if this option is undefined AID_NET_ADMIN and AID_NET_RAW have no special meaning for the kernel (iow, CAP_NET_ADMIN and CAP_NET_RAW are not granted to non-root processes belonging to those special groups).
Moreover, network access restrictions are completely ignored, so any application can create sockets and/or access the bluetooth stack even if its manifest does not specify the relevant permissions.
I upgraded to ADT 14 for ICS and it sucks, and it sucks bad. The upgrades are nice, but now ADB (at least logcat) doesn't work at ALL.
Code:
[2011-10-20 19:36:46 - adb]
[2011-10-20 19:36:46 - adb]This application has requested the Runtime to terminate it in an unusual way.
[2011-10-20 19:36:46 - adb]Please contact the application's support team for more information.
[2011-10-20 19:36:54 - DeviceMonitor]Adb connection Error:An existing connection was forcibly closed by the remote host
[2011-10-20 19:36:54 - Unexpected error while launching logcat. Try reselecting the device.]An existing connection was forcibly closed by the remote host
java.io.IOException: An existing connection was forcibly closed by the remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(Unknown Source)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
at sun.nio.ch.IOUtil.read(Unknown Source)
at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:395)
at com.android.ddmlib.Device.executeShellCommand(Device.java:319)
at com.android.ddmuilib.logcat.LogCatReceiver$1.run(LogCatReceiver.java:100)
at java.lang.Thread.run(Unknown Source)
[2011-10-20 19:36:55 - DeviceMonitor]Connection attempts: 1
[2011-10-20 19:36:57 - DeviceMonitor]Connection attempts: 2
[2011-10-20 19:36:59 - DeviceMonitor]Connection attempts: 3
[2011-10-20 19:37:01 - DeviceMonitor]Connection attempts: 4
[2011-10-20 19:37:03 - DeviceMonitor]Connection attempts: 5
[2011-10-20 19:37:05 - DeviceMonitor]Connection attempts: 6
[2011-10-20 19:37:07 - DeviceMonitor]Connection attempts: 7
[2011-10-20 19:37:09 - DeviceMonitor]Connection attempts: 8
[2011-10-20 19:37:11 - DeviceMonitor]Connection attempts: 9
[2011-10-20 19:37:13 - DeviceMonitor]Connection attempts: 10
[2011-10-20 19:37:15 - DeviceMonitor]Connection attempts: 11
Is what I get anytime ADB connects. IT prints out about 100 lines then dies. MAkes it impossible to test any apps.
I don't know how much longer I can use the patch ADB version on the google code page (Not sure of hte link right off hand)... anyone know how to fix this?
Hi, same problem here. Debugging on a Galaxy Tab 10.1 is now impossible since logcat isn't working.
I've had CM7 running on my TouchPad for quite some time now, and all of sudden, after rebooting it, it will no longer complete the boot process. Keeps hanging on the boot animation.
I rebooted to recovery and wiped system, cache and dalvik and reflashed CM7 and Google Apps. Keeps hanging at the exact same place:
There is no more logging entries generated after this:
W/BluetoothHeadset( 249): Proxy not attached to service
W/BluetoothHeadset( 249): Proxy not attached to service
E/wpa_supplicant( 453): wpa_driver_priv_driver_cmd failed (-1): GETPOWER
D/WifiStateTracker( 249): DHCP request started
I/bluedroid( 249): Starting bluetoothd deamon
D/WifiStateTracker( 249): DHCP succeeded with lease: 86400
V/WifiStateTracker( 249): IP configuration: ipaddr 192.168.1.123 gateway 192.168.1.1 netmask 255.255.255.0 dns1 192.168
.1.1 dns2 0.0.0.0 DHCP server 192.168.1.1 lease 86400 seconds
E/BluetoothEventLoop.cpp( 249): event_filter: Received signal org.freedesktop.DBus:NameAcquired from /org/freedesktop/D
Bus
D/BluetoothHidService.cpp( 249): hid_event_filter...
D/BluetoothService( 249): found 3 bonded devices
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
D/BluetoothService( 249): Bluetooth state 11 -> 12
Anyone have any idea how I can resolve this? How do I turn off bluetooth via ADB?
Obviously, wiping data will resolve the issue, but I would rather not do that (although I do have all of my apps backed up via TB)
Turge said:
I've had CM7 running on my TouchPad for quite some time now, and all of sudden, after rebooting it, it will no longer complete the boot process. Keeps hanging on the boot animation.
I rebooted to recovery and wiped system, cache and dalvik and reflashed CM7 and Google Apps. Keeps hanging at the exact same place:
There is no more logging entries generated after this:
W/BluetoothHeadset( 249): Proxy not attached to service
W/BluetoothHeadset( 249): Proxy not attached to service
E/wpa_supplicant( 453): wpa_driver_priv_driver_cmd failed (-1): GETPOWER
D/WifiStateTracker( 249): DHCP request started
I/bluedroid( 249): Starting bluetoothd deamon
D/WifiStateTracker( 249): DHCP succeeded with lease: 86400
V/WifiStateTracker( 249): IP configuration: ipaddr 192.168.1.123 gateway 192.168.1.1 netmask 255.255.255.0 dns1 192.168
.1.1 dns2 0.0.0.0 DHCP server 192.168.1.1 lease 86400 seconds
E/BluetoothEventLoop.cpp( 249): event_filter: Received signal org.freedesktop.DBus:NameAcquired from /org/freedesktop/D
Bus
D/BluetoothHidService.cpp( 249): hid_event_filter...
D/BluetoothService( 249): found 3 bonded devices
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
I/BluetoothDeviceProfileState( 249): Entering ACL Connected state with: -1
D/BluetoothService( 249): Bluetooth state 11 -> 12
Anyone have any idea how I can resolve this? How do I turn off bluetooth via ADB?
Obviously, wiping data will resolve the issue, but I would rather not do that (although I do have all of my apps backed up via TB)
Click to expand...
Click to collapse
Yep, you need to do a full wipe and reflash. Happened to me and its annoying, but im trying to minimize the number of apps i install and am currently staying away from restoring apps from TiBu. Havnt had a problem for the last few days...
jackdonogy said:
Yep, you need to do a full wipe and reflash. Happened to me and its annoying, but im trying to minimize the number of apps i install and am currently staying away from restoring apps from TiBu. Havnt had a problem for the last few days...
Click to expand...
Click to collapse
Do you know if it was the same problem? Were you able to take a look at logcat?
Hi,
I am having issues with the Facebook application not letting me log in..
I am having this issue on both Oneplus 3 and a Oneplus 5.
On the logcat i get the the error:
Code:
09-19 14:36:16.343 9693-13345/? W/fb4a.BlueServiceQueue: Exception during service
com.facebook.tigon.tigonutils.TigonErrorException: TigonError(2): TigonLigerErrorDomain(2) AsyncSocketException: connect failed, type = Socket not open, errno = 111 (Connection refused)
at X.1e9.onError(:416738)
at com.facebook.tigon.tigonapi.TigonCallbacksIntegerBufferJavaHelper.onError(:417283)
at com.facebook.common.jniexecutors.NativeRunnable.run(Native Method)
at com.facebook.common.jniexecutors.PooledNativeRunnable.run(:308022)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at X.1Zd.run(:401648)
at java.lang.Thread.run(Thread.java:764)
Things I have already tried:
Delete app data and cache
Reinstall application
Factory reset device
If i use a proxy (using mitmproxy) it will go through and i get to the screen which says:
Is there anyway i can debug or fix this issue.
"We're sorry, we can't set up English (United Kingdom) at the moment"
Thanks