Guest cepr Posted November 30, 2009 Report Share Posted November 30, 2009 Hello guys, I have a Deutsch T-Mobile Pulse, and I use it to develop applications using the SDK. adb is working fine (adb shell, adb install, adb ... is working), but logcat is dumb. When I launch logcat, no log is displayed at all. I have an official device (non-rooted), with rom U8220V100R001DEUC85B116SP01. Thanks you and best regards, -Cedric Link to comment Share on other sites More sharing options...
Guest Paul Posted November 30, 2009 Report Share Posted November 30, 2009 Same problem here... P Link to comment Share on other sites More sharing options...
Guest martinbrook Posted November 30, 2009 Report Share Posted November 30, 2009 Same problem here... P Will have a look here. I did get a device id from my kernel at the weekend instead of the usual ??????????? Link to comment Share on other sites More sharing options...
Guest martinbrook Posted November 30, 2009 Report Share Posted November 30, 2009 Will have a look here. I did get a device id from my kernel at the weekend instead of the usual ??????????? logcat working on the new kernel both on the device from adb shell and from the host adb logcat. Had to clear the buffers first with adb logcat -c As specified here :- > Yes it is a reproducible case. Exact content of the log change but it > always finish by "logcat read: Invalid argument" and I need to restart > the mobile to be able to read any log again. > It seems that something is getting twisted up in the logging. This really seems like a bug, but there is a quick workaround: run "adb logcat -c" once to clear the log, then "adb logcat" will work again until the log fills up. Florian Martin standing on the shoulders of giants Link to comment Share on other sites More sharing options...
Guest deardan Posted December 2, 2009 Report Share Posted December 2, 2009 (edited) Hi Cedric You may try follow means: adb shell echo 1 > /sys/kernel/logger/log_main/enable // ** '1' is enable log_main, echo 2 >/sys/kernel/logger/log_main/priority // ** '2' is the log level, you can get the level number from the android source code. Edited December 2, 2009 by deardan Link to comment Share on other sites More sharing options...
Guest Timmmm Posted December 2, 2009 Report Share Posted December 2, 2009 I did get a device id from my kernel at the weekend instead of the usual ??????????? Ah, fantastic. That's been pissing me off for a while (it breaks adb in eclipse). Link to comment Share on other sites More sharing options...
Guest Timmmm Posted December 15, 2009 Report Share Posted December 15, 2009 adb shell echo 1 > /sys/kernel/logger/log_main/enable // ** '1' is enable log_main, echo 2 >/sys/kernel/logger/log_main/priority // ** '2' is the log level, you can get the level number from the android source code. Ah, I also needed to do this. Thanks. Link to comment Share on other sites More sharing options...
Guest Tamas_ Posted February 7, 2011 Report Share Posted February 7, 2011 Hi Cedric You may try follow means: adb shell echo 1 > /sys/kernel/logger/log_main/enable // ** '1' is enable log_main, echo 2 >/sys/kernel/logger/log_main/priority // ** '2' is the log level, you can get the level number from the android source code. works like it should. thanks! :P Link to comment Share on other sites More sharing options...
Guest c51greedo Posted June 15, 2011 Report Share Posted June 15, 2011 Thanks a lot it is ok with these two shell commands !! ;) Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now