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.
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.
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
Hi.
Using Servers Ultimate to start a new NFS server on my Android device - Z ultra rooted.
I have firewall turned off both on the server and client.
First I replaced the "linker" file due to google disabling of pie
error: only position independent executables (PIE) are supported.
NFS server is able to being executed now.
192.168.1.84 = server
192.168.1.90 = client
When active I can see my client in the Server ultimate log on the android when searching the network with yast: 192.168.1.90 - New request...
But the server (android phone) says, this version (3) not handled: min=2 max=2...**
What does this mean?
I have NFS server working on Windows 7 and FreeNAS and client working on Suse so this issue is isolated to android. Not my network or my client.
Having the option to choose and setup NFS servers in the Servers ultimate app must mean its possible to use NFS on android?
Servers ultimate log:
2015-10-24 05:31:29 [testing] - Port map handler: PMAP_CALLIT called...
2015-10-24 05:31:29 [testing] - 192.168.1.90 - New request...
**2015-10-24 05:31:28 [testing] - this version (3) not handled: min=2 max=2...**
2015-10-24 05:31:28 [testing] - 192.168.1.90 - New request...
2015-10-24 05:31:24 [testing] - Port map handler: PMAP_CALLIT called...
2015-10-24 05:31:24 [testing] - 192.168.1.90 - New request...
**2015-10-24 05:31:24 [testing] - this version (3) not handled: min=2 max=2...**
2015-10-24 05:31:24 [testing] - 192.168.1.90 - New request...
2015-10-24 05:31:03 [testing] - Listening for connections...
2015-10-24 05:31:03 [testing] - Registering prog 100005 vers 1 prot 17 port 2049...
2015-10-24 05:31:03 [testing] - Registering prog 100003 vers 2 prot 17 port 2049...
2015-10-24 05:31:00 [testing] - Registering prog 100000 vers 2 prot 17 port 1111...
2015-10-24 05:31:00 [testing] - Port mapper started...
2015-10-24 05:31:00 [testing] - Forwarding ports done. Exit code: 0 - Returned: ""
2015-10-24 05:31:00 [testing] - Applying forwarding rules (root, 111)...
2015-10-24 05:31:00 [testing] - Preparing.
2015-10-24 05:31:00 [testing] - Server started
2015-10-24 05:31:00 [testing] - Starting server
2015-10-24 05:31:00 [testing] - Request has been send to servers pack
Limitation of the Android software
I found that on my Ubuntu desktop, I could only user version 2 of the NFS protocol with Servers Ultimate.
If it helps, the command I've used is:
sudo mount -o soft,intr,rsize=32768,wsize=32768,vers=2 192.168.2.55:/mnt/usb_storage/USB_DISK0/250gb/ /data/stuff/NFS
However, the rsize and wsize are arbitrary at the moment since version 2 of NFS has a maximum of 8192\
Anyway, hope that helps!
device is:
ST70208-1
Android Version: 4.1.1
Kernel Version: 3.0.8+
Build: ST70208-1_20130808_INT
aka Trekstor Surftab Ventos 7.0 HD
As Chrome crashes at start even after factory reset and all known measures did not help,
i installed root/su/bussybox/ssh-server and did a logcat.
...
/ActivityManager( 3603): Start proc com.android.chrome:sandboxed_process0 for service com.android.chrome/org.chromium.content.app.SandboxedProcessService0: pid=24769 uid=99001 gids={}
I/LibraryLoader(24750): loading: chromeview
E/Main (24750): Failed to load native library.
E/Main (24750): org.chromium.content.common.ProcessInitException
E/Main (24750): at org.chromium.content.app.LibraryLoader.loadNow(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation.loadLibraryNow(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation.access$400(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation$2.run(Unknown Source)
E/Main (24750): at android.os.Handler.handleCallback(Handler.java:615)
E/Main (24750): at android.os.Handler.dispatchMessage(Handler.java:92)
E/Main (24750): at android.os.Looper.loop(Looper.java:137)
E/Main (24750): at android.os.HandlerThread.run(HandlerThread.java:60)
E/Main (24750): Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1891]: 2487 could not load needed library 'libjnigraphics.so' for 'libchromeview.so' (load_library[1093]: Library 'libjnigraphics.so' not found)
E/Main (24750): at java.lang.Runtime.loadLibrary(Runtime.java:370)
E/Main (24750): at java.lang.System.loadLibrary(System.java:535)
E/Main (24750): ... 8 more
E/Trace (24769): error opening trace file: No such file or directory (2)
D/OpenGLRenderer(24750): Enabling debug mode 0
I/SandboxedProcessService(24769): Creating new SandboxedProcessService pid=24769
I/LibraryLoader(24769): loading: chromeview
E/SandboxedProcessService(24769): Failed to load native library, exiting sandboxed process
E/SandboxedProcessService(24769): org.chromium.content.common.ProcessInitException
E/SandboxedProcessService(24769): at org.chromium.content.app.LibraryLoader.loadNow(Unknown Source)
E/SandboxedProcessService(24769): at org.chromium.content.app.SandboxedProcessService$2.run(Unknown Source)
E/SandboxedProcessService(24769): at java.lang.Thread.run(Thread.java:856)
E/SandboxedProcessService(24769): Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1891]: 2487 could not load needed library 'libjnigraphics.so' for 'libchromeview.so' (load_library[1093]: Library 'libjnigraphics.so' not found)
E/SandboxedProcessService(24769): at java.lang.Runtime.loadLibrary(Runtime.java:370)
E/SandboxedProcessService(24769): at java.lang.System.loadLibrary(System.java:535)
E/SandboxedProcessService(24769): ... 3 more
..
"ls -al" in /system/lib showed amongst others 4 suspicious shared native libraries:
-rw------- 1 0 0 59996 Mar 17 18:50 libjnigraphics.so
-rw------- 1 0 0 10017928 Mar 17 18:18 libmsrmsdk.so
-rw------- 1 0 0 8577120 Mar 17 18:50 libreader.so
-rw------- 1 0 0 135864 Mar 17 18:51 librss.so
all other libs here look like that:
-rw-r--r-- 1 0 0 31363328 Aug 1 2008 libchromeview.so
The 4 suspects have a date 03/17/2016 and no read permission for group/other but the rest all are 8/1/2008 and have the permissions.
I did "chmod 644" to them.
But i had to remount /system as readwrite.
Seams it is normaly readonly!
And i had to do "su"!
How/Who can change anything here in /system/lib?
Chrom still crashes but logcat shows it is not because it does not find the libjnigraphics.so.
Now it crashes with a dump.
I think it is because libchromeview.so loads the dependency libjnigraphics.so,
but that is an newer version than that it was linked against.
After i left the device in the morning on the day this **** happend, it was working ok.
In the evening (my wife had used it) there was tones of error msg at starting of many apps (Contacts, Playstore, ...).
So i did a factory reset, but the Chrome problem persists (Google+ and Maps where *****y too but worked after update).
I did not switch of auto update.
So i think some update messed it up, or my wife had switched it hard off during something important/longer lasting, as it was not responsive to her.
But how can a normal apk do something to /system?!
Any ideas why Chrome still uses these old native shared libraries?
Please can somebody who is having the same device, send me a "ls -al" of /system/lib.
Any ideas how to fix Chrome (PlayStore)?
Greetings
Michael
PS: This was the 3rd factory reset i had to make because some update managed to screwed it. But the two before worked, ok.
The stock "firmware" of this device looks as if it was the 5th test build a new greenhorn system builder.
And ADB does not work. The device announces itself only in recovery mode to USB (of course "USB debugging" is on).