M mistermentality Active Member Licensed User Longtime User Apr 26, 2011 #1 Logcat read - invalid argument error. Cannot read any errors I've had this error before and its gone away but this time it will not go at all, I have an app which has for some reason despite no changes decided to crash so I try to connect via usb lead by clicking connect in the log section of the ide but while it says Logcat is connected to my device the next line always says invalid argument. I have tried restarting Windows, testing different source code, using the wireless bridge, but nothing seems to resolve the issue. Any ideas what causes this? Dave Edit: Restarting phone solved it until I run any b4a app then the logcat error starts again Last edited: Apr 26, 2011
Logcat read - invalid argument error. Cannot read any errors I've had this error before and its gone away but this time it will not go at all, I have an app which has for some reason despite no changes decided to crash so I try to connect via usb lead by clicking connect in the log section of the ide but while it says Logcat is connected to my device the next line always says invalid argument. I have tried restarting Windows, testing different source code, using the wireless bridge, but nothing seems to resolve the issue. Any ideas what causes this? Dave Edit: Restarting phone solved it until I run any b4a app then the logcat error starts again
Erel B4X founder Staff member Licensed User Longtime User Apr 26, 2011 #2 Where so you see the invalid argument message? Upvote 0
M mistermentality Active Member Licensed User Longtime User Apr 26, 2011 #3 The error appears in the ide display area for the logs section (where the logs tab is) when I click connect if I try via usb. If I connect via the wireless bridge I get no such error but I get no error log at all even though in the app, to debug it, I have it logging different events. So at the moment I am unable to debug my apps and really need to solve why it happens. I can reboot my phone but then as soon as I try and connect via usb the same thing happens again. Edit: would it have anything to do with this issue at http://code.google.com/p/android/issues/detail?id=5745 as I would guess there is a lot of data. Dave Last edited: Apr 26, 2011 Upvote 0
The error appears in the ide display area for the logs section (where the logs tab is) when I click connect if I try via usb. If I connect via the wireless bridge I get no such error but I get no error log at all even though in the app, to debug it, I have it logging different events. So at the moment I am unable to debug my apps and really need to solve why it happens. I can reboot my phone but then as soon as I try and connect via usb the same thing happens again. Edit: would it have anything to do with this issue at http://code.google.com/p/android/issues/detail?id=5745 as I would guess there is a lot of data. Dave
Erel B4X founder Staff member Licensed User Longtime User Apr 26, 2011 #4 Seems related to the issue in the link. Did you try to kill ADB server (Tools - Restart ADB server)? You can also try calling: adb logcat -c adb is located in Android SDK folder (under tools). Upvote 0
Seems related to the issue in the link. Did you try to kill ADB server (Tools - Restart ADB server)? You can also try calling: adb logcat -c adb is located in Android SDK folder (under tools).
M mistermentality Active Member Licensed User Longtime User Apr 26, 2011 #5 I cleared logcat as you suggested and it worked for about two minutes before erroring again, long enough to figure out the error causing my app to crash. Still getting the logcat error but can at least now do logcat -c. Thanks Dave Upvote 0
I cleared logcat as you suggested and it worked for about two minutes before erroring again, long enough to figure out the error causing my app to crash. Still getting the logcat error but can at least now do logcat -c. Thanks Dave
