[Q] USB Debugging issue

R

redders6600

Member

May 14, 2010

18

1

• Feb 20, 2014

• #1

I have a 2013 Nexus 7, running clearnrom 2.6 and the kernel that comes along with that.

Very irritatingly I have constant spam in my logcat when I plug it in to my PC.

I *do* get most of the debugging information, but messages like these are constantly being thrown in (about once a second), which is irritating, but also causes the chrome adb extension to crash/disconnect frequently:

Code:

02-20 13:32:53.316: E/UsbDebuggingManager(611): java.io.IOException: Connection refused
02-20 13:32:53.316: E/UsbDebuggingManager(611): 	at android.net.LocalSocketImpl.connectLocal(Native Method)
02-20 13:32:53.316: E/UsbDebuggingManager(611): 	at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:287)
02-20 13:32:53.316: E/UsbDebuggingManager(611): 	at android.net.LocalSocket.connect(LocalSocket.java:130)
02-20 13:32:53.316: E/UsbDebuggingManager(611): 	at com.android.server.usb.UsbDebuggingManager.listenToSocket(UsbDebuggingManager.java:75)
02-20 13:32:53.316: E/UsbDebuggingManager(611): 	at com.android.server.usb.UsbDebuggingManager.run(UsbDebuggingManager.java:111)
02-20 13:32:53.316: E/UsbDebuggingManager(611): 	at java.lang.Thread.run(Thread.java:841)

Has anyone else had this issue?

I thought it might be an issue with the kernel, or with my PC, but I've tried it on two separate PCs (one Linux, one windows) and with the ElementalX 2.6 kernel but no joy.

Help/thoughts appreciated.

 

R

redders6600

Member

May 14, 2010

18

1

• Feb 22, 2014

• #2

Given the lack of replies - I guess people don't know.

Could someone who has eclipse set up plug their nexus 7 in and check the logcat to see whether they get similar output?

Especially helpful if you are running cleanrom.

Thanks

 

R

redders6600

Member

May 14, 2010

18

1

• Feb 24, 2014

• #3

Does nobody have eclipse set up?

 

R

redders6600

Member

May 14, 2010

18

1

• Feb 26, 2014

• #4

Can anyone help with this? All I need is for someone to plug in their Nexus 7 and tell me if they get errors in the console..

 

Scott

Retired Recognized Developer

Feb 20, 2007

29,245

66,273

Fargo

www.scottcrosler.com

OnePlus 8T

Samsung Galaxy S21 Ultra

• Feb 27, 2014

• #5

Yep sure do.


Just got a new device yesterday and it is giving same message. Stock, un-rooted.


Now please dont spam my thread with these questions

 

• 

Reactions: redders6600

R

redders6600

Member

May 14, 2010

18

1

• Feb 27, 2014

• #6

Thanks! Sorry for the spam... Any idea what could be causing this then?

I thought it would have been a ROM or kernel thing but if you are getting the same fully stock then clearly not...

Sent from my Nexus 7 using Tapatalk

 

Scott

Retired Recognized Developer

Feb 20, 2007

29,245

66,273

Fargo

www.scottcrosler.com

OnePlus 8T

Samsung Galaxy S21 Ultra

• Feb 28, 2014

• #7

redders6600 said:

Thanks! Sorry for the spam... Any idea what could be causing this then?

I thought it would have been a ROM or kernel thing but if you are getting the same fully stock then clearly not...

Sent from my Nexus 7 using Tapatalk

Click to expand...

Click to collapse

Yeah, I am not sure but I got some ideas...

I would look at replacing the ADBD binary and also unsecure the boot.img.


That's totally random guessing... But that's what I would try first.

You should be able to fastboot flash my boot.img as it already has this done.

Once again thats a random guess.

 

Scott

Retired Recognized Developer

Feb 20, 2007

29,245

66,273

Fargo

www.scottcrosler.com

OnePlus 8T

Samsung Galaxy S21 Ultra

• Mar 1, 2014

• #8

Did you try? Any updates?

 

R

redders6600

Member

May 14, 2010

18

1

• Mar 3, 2014

• #9

scrosler said:

Did you try? Any updates?

Click to expand...

Click to collapse

Sorry, was busy over the weekend, going to try now.

 

R

redders6600

Member

May 14, 2010

18

1

• Mar 3, 2014

• #10

redders6600 said:

Sorry, was busy over the weekend, going to try now.

Click to expand...

Click to collapse

Didn't get very far

I don't know where your insecure boot.img is located..

 

R

redders6600

Member

May 14, 2010

18

1

• Mar 21, 2014

• #11

Bump

 

Scott

Retired Recognized Developer

Feb 20, 2007

29,245

66,273

Fargo

www.scottcrosler.com

OnePlus 8T

Samsung Galaxy S21 Ultra

• Mar 29, 2014

• #12

It looks like this issue may be fixed in Android 4.4.3.

It just said a USB Debugging security fix.

Here is a link with the info: http://www.androidheadlines.com/2014/03/leak-new-android-4-4-3-kit-kat-update-details.html

 

Last edited: Mar 29, 2014

• 

Reactions: redders6600 and LinearEquation

LinearEquation

Senior Member

Aug 26, 2013

1,765

436

Midwest

• Mar 30, 2014

• #13

scrosler said:

It looks like this issue may be fixed in Android 4.4.3.

It just said a USB Debugging security fix.

Here is a link with the info: http://www.androidheadlines.com/2014/03/leak-new-android-4-4-3-kit-kat-update-details.html

Click to expand...

Click to collapse

Good read, thanks.

Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

 

Miche1asso

Senior Member

Apr 11, 2012

680

500

Treviso

• Dec 23, 2014

• #14

I just had the same issue on my Xperia M2 with Kitkat 4.4.4. I disabled and enabled the USB Debug in develop setting and it seems to have disappeared. Now NFC is spamming the logcat, but that is usual...