[android-developers] Re: adb logcat -f out.log doesn't work?

2008-04-03 Thread Raja Nagendra Kumar

Not sure if this the way filters should behave. By default only the
those which match filter should be displayed. In you approach two
filters are used one to completely stop all the message and other for
application logs.

I think by default *:s should have been applied when a filter spec is
provided!!

Digit, thank you for the solution.. my logs are neat and helathy now..

Regards,
Nagendra

On Mar 28, 11:43 pm, Digit <[EMAIL PROTECTED]> wrote:
> the syntax is   : or *:, where  is a single letter
> describing the logging level (s=silent, e=error, w=warnings, i=informative,
> d=debug, v=verbose)
> the syntax :* is not supported.
>
> try doing the following:
>
> adb logcat '*:s APP_TAG:v'
>
> this should ensure that only traces from your apps are displayed
>
> On Fri, Mar 28, 2008 at 3:36 AM, Raja Nagendra Kumar <
>
>
>
> [EMAIL PROTECTED]> wrote:
>
> > I have stated both emulator and attached to loc console using the
> > following
>
> > emulator -logcat APP_TAG:*
>
> > and
>
> > adb logcat APP_TAG:*
>
> > However I am seeing apptag logs and also system logs such as the
> > below..
>
> > Regards,
> > Nagendra
>
> > lgConsole
> > exec
> > D/        (  519): zip_openZipFile(/system/app/GTalkSettings.apk)
> > D/        (  519): zip_openZipFile(/system/app/Home.apk)
> > D/        (  519): zip_openZipFile(/system/app/GoogleApps.apk)
> > D/        (  519): zip_openZipFile(/system/app/Maps.apk)
> > D/        (  519): zip_openZipFile(/system/app/Phone.apk)
> > D/        (  519): zip_openZipFile(/system/app/ImProvider.apk)
> > D/        (  519): zip_openZipFile(/system/app/gtalkservice.apk)
> > D/PackageManager(  519): Scanning app dir /data/app
> > D/        (  519): zip_openZipFile(/data/app/ApiDemos.apk)
> > W/PackageManager(  519): Not granting permission
> > android.permission.RUN_INSTRUMENTATION to package
> > com.google.android.samples
> > W/PackageManager(  519): Granting new permission
> > android.permission.WRITE_CONTACTS to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.READ_CONTACTS to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.ADD_SYSTEM_SERVICE to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.SYSTEM_ALERT_WINDOW to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.WRITE_CONTACTS to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.WRITE_SETTINGS to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.BROADCAST_STICKY to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.READ_CONTACTS to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.CALL_PHONE to android.server.PackageManagerService
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.INTERNAL_SYSTEM_WINDOW to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.WRITE_SETTINGS to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.BROADCAST_STICKY to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.RECEIVE_BOOT_COMPLETED to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > com.google.android.gtalkservice.permission.GTALK_SERVICE to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.CALL_PHONE to android.server.PackageManagerService
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.ACCESS_LOCATION to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > com.google.android.maps.permission.READ_MY_MAPS to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > com.google.android.maps.permission.WRITE_MY_MAPS to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.ACCESS_CELL_ID to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.ACCESS_ASSISTED_GPS to
> > [EMAIL PROTECTED]
> > W/PackageManager(  519): Granting new permission
> > android.permission.ACCESS_GPS to android.server.PackageManagerService
> > [EMAIL PROTECTED]
> > D/        (  519): removing file '/data/system/packages-backup.xml'
> > D/        (  519):  unable to unlink '/data/system/packages-
> > backup.xml' (errno=2)
> > I/dalvikvm-heap(  519): GC! (4302ms since last GC)
> > I/dalvikvm-heap(  519): GC old usage 59.0%; now 0.881MB used / 1.763MB
> > soft max (2.062MB real max)
> > I/dalvikvm-heap(  519): GC freed 11180 objects / 634488 bytes in 101ms
> > I/ServiceManager(  502): ServiceManager: addService(package, 0x138b0)
>
> > On Mar 27, 10:33 pm, "Megha Joshi

[android-developers] Re: adb logcat -f out.log doesn't work?

2008-03-28 Thread Digit
the syntax is   : or *:, where  is a single letter
describing the logging level (s=silent, e=error, w=warnings, i=informative,
d=debug, v=verbose)
the syntax :* is not supported.

try doing the following:

adb logcat '*:s APP_TAG:v'

this should ensure that only traces from your apps are displayed

On Fri, Mar 28, 2008 at 3:36 AM, Raja Nagendra Kumar <
[EMAIL PROTECTED]> wrote:

>
> I have stated both emulator and attached to loc console using the
> following
>
> emulator -logcat APP_TAG:*
>
> and
>
> adb logcat APP_TAG:*
>
> However I am seeing apptag logs and also system logs such as the
> below..
>
> Regards,
> Nagendra
>
> lgConsole
> exec
> D/(  519): zip_openZipFile(/system/app/GTalkSettings.apk)
> D/(  519): zip_openZipFile(/system/app/Home.apk)
> D/(  519): zip_openZipFile(/system/app/GoogleApps.apk)
> D/(  519): zip_openZipFile(/system/app/Maps.apk)
> D/(  519): zip_openZipFile(/system/app/Phone.apk)
> D/(  519): zip_openZipFile(/system/app/ImProvider.apk)
> D/(  519): zip_openZipFile(/system/app/gtalkservice.apk)
> D/PackageManager(  519): Scanning app dir /data/app
> D/(  519): zip_openZipFile(/data/app/ApiDemos.apk)
> W/PackageManager(  519): Not granting permission
> android.permission.RUN_INSTRUMENTATION to package
> com.google.android.samples
> W/PackageManager(  519): Granting new permission
> android.permission.WRITE_CONTACTS to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.READ_CONTACTS to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.ADD_SYSTEM_SERVICE to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.SYSTEM_ALERT_WINDOW to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.WRITE_CONTACTS to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.WRITE_SETTINGS to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.BROADCAST_STICKY to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.READ_CONTACTS to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.CALL_PHONE to android.server.PackageManagerService
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.INTERNAL_SYSTEM_WINDOW to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.WRITE_SETTINGS to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.BROADCAST_STICKY to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.RECEIVE_BOOT_COMPLETED to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> com.google.android.gtalkservice.permission.GTALK_SERVICE to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.CALL_PHONE to android.server.PackageManagerService
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.ACCESS_LOCATION to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> com.google.android.maps.permission.READ_MY_MAPS to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> com.google.android.maps.permission.WRITE_MY_MAPS to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.ACCESS_CELL_ID to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.ACCESS_ASSISTED_GPS to
> [EMAIL PROTECTED]
> W/PackageManager(  519): Granting new permission
> android.permission.ACCESS_GPS to android.server.PackageManagerService
> [EMAIL PROTECTED]
> D/(  519): removing file '/data/system/packages-backup.xml'
> D/(  519):  unable to unlink '/data/system/packages-
> backup.xml' (errno=2)
> I/dalvikvm-heap(  519): GC! (4302ms since last GC)
> I/dalvikvm-heap(  519): GC old usage 59.0%; now 0.881MB used / 1.763MB
> soft max (2.062MB real max)
> I/dalvikvm-heap(  519): GC freed 11180 objects / 634488 bytes in 101ms
> I/ServiceManager(  502): ServiceManager: addService(package, 0x138b0)
>
> On Mar 27, 10:33 pm, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
> >   Hi,
> >
> >  The filters do work as expected. Could you please give an example of
> the
> > logcat command that you used, expected output and the actual output that
> you
> > received?
> >
> >  Thanks,
> >  Megha
> >
> > On Wed, Mar 26, 2008 at 6:24 AM, Raja Nagendra Kumar <
> >
> >
> >
> > [EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> >
> > > May be there are big issues in the arguments checking in sdk tools.
> >
> > > adb logcat APP_FILTER_TAG or
> > > emulator  -logcat APP_FILTER_TAG does not seem to work as expected. I
> > > am still seeing all the log messages which are of different tag than
> > > APP_FILTER_TAG.
> >
> > > R

[android-developers] Re: adb logcat -f out.log doesn't work?

2008-03-28 Thread Raja Nagendra Kumar

I have stated both emulator and attached to loc console using the
following

emulator -logcat APP_TAG:*

and

adb logcat APP_TAG:*

However I am seeing apptag logs and also system logs such as the
below..

Regards,
Nagendra

lgConsole
exec
D/(  519): zip_openZipFile(/system/app/GTalkSettings.apk)
D/(  519): zip_openZipFile(/system/app/Home.apk)
D/(  519): zip_openZipFile(/system/app/GoogleApps.apk)
D/(  519): zip_openZipFile(/system/app/Maps.apk)
D/(  519): zip_openZipFile(/system/app/Phone.apk)
D/(  519): zip_openZipFile(/system/app/ImProvider.apk)
D/(  519): zip_openZipFile(/system/app/gtalkservice.apk)
D/PackageManager(  519): Scanning app dir /data/app
D/(  519): zip_openZipFile(/data/app/ApiDemos.apk)
W/PackageManager(  519): Not granting permission
android.permission.RUN_INSTRUMENTATION to package
com.google.android.samples
W/PackageManager(  519): Granting new permission
android.permission.WRITE_CONTACTS to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.READ_CONTACTS to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.ADD_SYSTEM_SERVICE to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.SYSTEM_ALERT_WINDOW to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.WRITE_CONTACTS to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.WRITE_SETTINGS to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.BROADCAST_STICKY to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.READ_CONTACTS to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.CALL_PHONE to android.server.PackageManagerService
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.INTERNAL_SYSTEM_WINDOW to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.WRITE_SETTINGS to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.BROADCAST_STICKY to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.RECEIVE_BOOT_COMPLETED to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
com.google.android.gtalkservice.permission.GTALK_SERVICE to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.CALL_PHONE to android.server.PackageManagerService
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.ACCESS_LOCATION to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
com.google.android.maps.permission.READ_MY_MAPS to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
com.google.android.maps.permission.WRITE_MY_MAPS to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.ACCESS_CELL_ID to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.ACCESS_ASSISTED_GPS to
[EMAIL PROTECTED]
W/PackageManager(  519): Granting new permission
android.permission.ACCESS_GPS to android.server.PackageManagerService
[EMAIL PROTECTED]
D/(  519): removing file '/data/system/packages-backup.xml'
D/(  519):  unable to unlink '/data/system/packages-
backup.xml' (errno=2)
I/dalvikvm-heap(  519): GC! (4302ms since last GC)
I/dalvikvm-heap(  519): GC old usage 59.0%; now 0.881MB used / 1.763MB
soft max (2.062MB real max)
I/dalvikvm-heap(  519): GC freed 11180 objects / 634488 bytes in 101ms
I/ServiceManager(  502): ServiceManager: addService(package, 0x138b0)

On Mar 27, 10:33 pm, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
>   Hi,
>
>  The filters do work as expected. Could you please give an example of the
> logcat command that you used, expected output and the actual output that you
> received?
>
>  Thanks,
>  Megha
>
> On Wed, Mar 26, 2008 at 6:24 AM, Raja Nagendra Kumar <
>
>
>
> [EMAIL PROTECTED]> wrote:
>
> > Hi,
>
> > May be there are big issues in the arguments checking in sdk tools.
>
> > adb logcat APP_FILTER_TAG or
> > emulator  -logcat APP_FILTER_TAG does not seem to work as expected. I
> > am still seeing all the log messages which are of different tag than
> > APP_FILTER_TAG.
>
> > Regards,
> > Raja Nagendra Kumar,
> > C.T.O
> >www.tejasoft.com
>
> > On Mar 26, 6:23 am, Diego Torres Milano <[EMAIL PROTECTED]> wrote:
> > > I was tempted to tell you that in your case '-f out.log' is
> > > interpreted by adb as a filter, but if you invoke
>
> > > $ adb logcat -f '*'
>
> > > you'll obtain
>
> > > "couldn't open output file: Is a directory"
>
> > > so, it's not a filter expression really.
> > > adb is not parsing its command line correctly.
>
> > > On Mar 24, 1:55 pm, [EMAIL PROTECTED] wrote:> I tried to use
> > "adb logcat -f " to redirect the log message
> > > > to a log file. Then I don't need to watch logs

[android-developers] Re: adb logcat -f out.log doesn't work?

2008-03-27 Thread Megha Joshi
  Hi,

 The filters do work as expected. Could you please give an example of the
logcat command that you used, expected output and the actual output that you
received?

 Thanks,
 Megha

On Wed, Mar 26, 2008 at 6:24 AM, Raja Nagendra Kumar <
[EMAIL PROTECTED]> wrote:

>
> Hi,
>
> May be there are big issues in the arguments checking in sdk tools.
>
> adb logcat APP_FILTER_TAG or
> emulator  -logcat APP_FILTER_TAG does not seem to work as expected. I
> am still seeing all the log messages which are of different tag than
> APP_FILTER_TAG.
>
> Regards,
> Raja Nagendra Kumar,
> C.T.O
> www.tejasoft.com
>
> On Mar 26, 6:23 am, Diego Torres Milano <[EMAIL PROTECTED]> wrote:
> > I was tempted to tell you that in your case '-f out.log' is
> > interpreted by adb as a filter, but if you invoke
> >
> > $ adb logcat -f '*'
> >
> > you'll obtain
> >
> > "couldn't open output file: Is a directory"
> >
> > so, it's not a filter expression really.
> > adb is not parsing its command line correctly.
> >
> > On Mar 24, 1:55 pm, [EMAIL PROTECTED] wrote:> I tried to use
> "adb logcat -f " to redirect the log message
> > > to a log file. Then I don't need to watch logs in windows cmd window.
> > > Is that correct to use like "adb logcat -f out.log"? There is no
> > > out.log file created in the same directory.
> > > Or I tried the wrong direction?
> >
> > > Thanks!
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---



[android-developers] Re: adb logcat -f out.log doesn't work?

2008-03-26 Thread Raja Nagendra Kumar

Hi,

May be there are big issues in the arguments checking in sdk tools.

adb logcat APP_FILTER_TAG or
emulator  -logcat APP_FILTER_TAG does not seem to work as expected. I
am still seeing all the log messages which are of different tag than
APP_FILTER_TAG.

Regards,
Raja Nagendra Kumar,
C.T.O
www.tejasoft.com

On Mar 26, 6:23 am, Diego Torres Milano <[EMAIL PROTECTED]> wrote:
> I was tempted to tell you that in your case '-f out.log' is
> interpreted by adb as a filter, but if you invoke
>
> $ adb logcat -f '*'
>
> you'll obtain
>
> "couldn't open output file: Is a directory"
>
> so, it's not a filter expression really.
> adb is not parsing its command line correctly.
>
> On Mar 24, 1:55 pm, [EMAIL PROTECTED] wrote:> I tried to use "adb logcat -f 
> " to redirect the log message
> > to a log file. Then I don't need to watch logs in windows cmd window.
> > Is that correct to use like "adb logcat -f out.log"? There is no
> > out.log file created in the same directory.
> > Or I tried the wrong direction?
>
> > Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---



[android-developers] Re: adb logcat -f out.log doesn't work?

2008-03-25 Thread Diego Torres Milano

I was tempted to tell you that in your case '-f out.log' is
interpreted by adb as a filter, but if you invoke

$ adb logcat -f '*'

you'll obtain

"couldn't open output file: Is a directory"

so, it's not a filter expression really.
adb is not parsing its command line correctly.



On Mar 24, 1:55 pm, [EMAIL PROTECTED] wrote:
> I tried to use "adb logcat -f " to redirect the log message
> to a log file. Then I don't need to watch logs in windows cmd window.
> Is that correct to use like "adb logcat -f out.log"? There is no
> out.log file created in the same directory.
> Or I tried the wrong direction?
>
> Thanks!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---



[android-developers] Re: adb logcat -f out.log doesn't work?

2008-03-25 Thread Megha Joshi
 You could use the standard unix redirection :

 adb logcat > out.log



On Mon, Mar 24, 2008 at 5:55 AM, <[EMAIL PROTECTED]> wrote:

>
> I tried to use "adb logcat -f " to redirect the log message
> to a log file. Then I don't need to watch logs in windows cmd window.
> Is that correct to use like "adb logcat -f out.log"? There is no
> out.log file created in the same directory.
> Or I tried the wrong direction?
>
> Thanks!
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---