View Single Post
  #299 (permalink)  
Old 11-16-2011, 10:52 AM
arrrghhh's Avatar
arrrghhh
Testing Extraordinaire
Offline
 
Join Date: Mar 2007
Posts: 3,604
Reputation: 7360
arrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the community
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only

Quote:
Originally Posted by [ACL] View Post
The logs posted by trevoroni show almost nothing. Only thing we know the cpu is crunching away at something. once the cpu is pegged, all hell breaks loose and people start blaming anything.
That's really the whole issue people. The logs posted show NOTHING useful, other than the processor is pegged by "something".

GetLogs is a great app (see the Logs topic on the wiki), and I recommend everyone use it if they want to pull logs. It shows processes in top, and has corresponding logs from the kernel - so in theory lines can be matched up, because again in this case just a logcat with no timestamps is useless.
Reply With Quote