bug hunting

[Guest fards]

Please note that this is what I've found out so far, I'm still fairly new to android, but I've learnt quite a bit, if you know more then please add to the thread!

(I'll also edit this so its clearer at some point)

If you're having issues with your streak (or other android) then there's a few places you can look to see what's happening.

You've probably read about "use logcat" or "share your logs" ]

adb logcat > whatever.txt

is useful, but a bit cumbersome

there's a few other spots as well that are actually more useful.

data/tombstones contains crash data, lots of crash data. these seem to be saved when an aop crashes out without showing the force close box.

The files inside it are saved with time and date info, they are plain text files, so can be opened with root explorer (view as text)

these files have loads of info in them, usually there's time info at the top, with what application has crashed, after that there's a memory dump, near the start of the memory with often what's caused the issue.

data/systemlog also contains the main log files for

gpslog - fairly self explanatory, logs when the gps is on or off.

Lifetimelog - the overall statistics for the streak including how many major crashes (OOPS??) there's been

reload.log - I Suspect its the boot date/time stamp- mine then shows as "unknown" I presume if there's a reason for a reboot it will show here

wakelock.log - this is what keeps the streak awake, its not as useful as it sounds, but its not too bad a start to see why you're battery life is struggling. (its also too big for root explorer to handle)

Inside the /data/systemlog/ folder theres two other folders:

kwakelog - Which always seems to be empty

wakelog - Where all the goodies are found!

inside wakelog there are further folders based on date/time

opening one of these folders will give you three more logs, these are the really useful ones.

main.log - its similar to what you get with logcat but even more detail !

radio.log - this is everything that goes on with the mobile data - network - and sms stuff - there's lots of data, most of it meaningless, but it does show any errors

sys.log - this is a fun one, its basically a complete system dump, everything that's running..

there's lots of info to look through in all those, but most of the time you should be able to see what's causing an issue if there is one, by using them

Edited February 21, 2011 by fards

[Guest popetodd]

You're fairly new to Android? You could have fooled me! :D

Thanks for all the log locations, that is some very useful information.

Edited February 21, 2011 by popetodd

[Guest fards]

android yes, linux no..

android code still looks like an explosion in a spaghetti factory ..

[Guest anthscorner]

Thanks for the heads up Fards.

I've just started using logcat in terminal;

su

logcat -f "filename" -v long

I then try the app causing the problem, wait for the FC and then go back to terminal; ctril <C> to stop.

I have noticed this records everything but the file can grow in size very quickly (hence testing against app for fcs)

Thanks,

Anthony.

[Guest popetodd]

Any idea what /sdcard/snapshots is all about?

It's taking up a sh**load of space and has files dating back to last year in it.

Edited February 22, 2011 by popetodd

[Guest CodaWolf]

android yes, linux no..

android code still looks like an explosion in a spaghetti factory ..

And Linux doesn't? :huh:

[Guest fards]

Any idea what /sdcard/snapshots is all about?

It's taking up a sh**load of space and has files dating back to last year in it.

It's profiling I think, can disable it using the init script, it is disabled in the streak droid roms.

I presumed it would flush after some time but it never appears to

http://hi-android.info/src/com/android/int...ation.java.html

http://www.eclipse.org/tptp/home/documents...AndroidTPTP.pdf