LOS alogcat logs, kmsg logs and bug reports

DarkPhoenix

Senior Member
Sep 6, 2007
534
68
0
Lebanon, TN
I have started having the LOS issue since rooting on the 10-2. I have had alogcat running in the background while waiting for a LOS instance to occur. I have the alogcat buffer set to radio. I don't know if it's of any use to anyone but I am attaching it anyway. I am also going to attach a log with the buffer set to events and main to try to get as much information as possible when a LOS instance occurs. I am not a developer and I don't know much about this stuff but I want to contribute to figuring it out if at all possible. Let me know if there is anything else I can do to help. Thanks.


Post #2 alogcat logs

Post #3 ksmg pastebin links

Post #4 reserved for bugreport.txt


Edit:

Just fyi I've had my phone since release day, rooted using Heimdall in Ubuntu with Zedomax v3 and currently running Midnight rom v2.

PRL 60681

Not sure if this will matter or not if they release future versions of the E4gt, Hardware version D710.10.

Edit #2

I will try to add the logs/kmsg output pastebin links to the appropriate post at the beginning of the thread with the original posters name as they are added to the thread.

To get the kmsg output on a rooted phone use terminal emulator, type "su", press enter and allow super user privileges. Then type the command "cat /proc/kmsg".

For a non rooted phone use the guide below from frifox.

Hook up to your PC in debugging mode, have adb at the ready, and do:

"adb shell cat /proc/kmsg > out.txt"

Then pastebin the context of the .txt.

Thanks to K0nane, mkasick and frifox for their input.
 
Last edited:

DarkPhoenix

Senior Member
Sep 6, 2007
534
68
0
Lebanon, TN
Alogcat buffer logs

10-9-11 Alogcat radio buffer log
http://pastebin.com/Ng3JPNnd

10-9-11 Alogcat event buffer log
http://pastebin.com/SEb66mtR

10-9-11 Alogcat main buffer log
http://pastebin.com/sVYkRdg2

10-6-11 Alogcat main buffer log from firemedic624
This log is for a LOS instance after LCD Resolution restarted the phone. http://pastebin.com/SiPxteRZ

10-6-11 Alogcat event buffer log from firemedic624
This log is for a LOS instance after LCD Resolution restarted the phone. http://pastebin.com/gCYzeXzh

10-5-11 Alogcat event buffer log from firemedic624
http://pastebin.com/c07Vakc6

10-4-11 Alogcat radio buffer log from firemedic624
http://pastebin.com/8QbeAeHQ
 
Last edited:
  • Like
Reactions: Itchiee

DarkPhoenix

Senior Member
Sep 6, 2007
534
68
0
Lebanon, TN
Kmsg Logs and Interrupt Logs

10-10-11 Interrupts log on Zedomax v3 from jirafabo
http://pastebin.com/PFF9UWWi

10-9-11 Kmsg from firemedic624
http://pastebin.com/0Zh7yPrX

10-6-11 Kmsg from jirafabo
http://pastebin.com/Xr4dF8nx

10-6-11 Kmsg from firemedic624
This LOS occurred after LCD Resolution restarted the phone.
http://pastebin.com/zdsz8FwX

10-5-11 #2 Kmsg from firemedic624
http://pastebin.com/9qMUMmG8

10-5-11 #1 Kmsg from firemedic624
http://pastebin.com/B7wQsGf2

10-4-11 Kmsg from dts_stretch
http://pastebin.com/4HQTMH2C
 
Last edited:

DarkPhoenix

Senior Member
Sep 6, 2007
534
68
0
Lebanon, TN
Bug reports

10-7-11 bugreport by frifox

10-5-11 bugreport by firemedic624

10-10-11 bugreport immediately after LOS by frifox

10-10-11 bugreport 5 minutes after LOS by frifox

10-11-11 bugreport noLOS by frifox
 

Attachments

Last edited:

k0nane

Inactive Recognized Developer
Feb 7, 2008
3,991
3,783
0
127.0.0.1
www.k0nane.info
Thanks for getting some data! It's high time someone did so.

A kmsg would be incredibly helpful to go along with this. For future reference, you may wish to paste to pastebin.com for readability and to save space.
 

DarkPhoenix

Senior Member
Sep 6, 2007
534
68
0
Lebanon, TN
Thanks for getting some data! It's high time someone did so.

A kmsg would be incredibly helpful to go along with this. For future reference, you may wish to paste to pastebin.com for readability and to save space.
OK I will do that. How do I go about getting a kmsg?

Sent from my SPH-D710 using xda premium
 

jirafabo

Senior Member
Dec 4, 2007
766
71
0
Orlando
This, on a rooted phone.

Hook up to your PC in debugging mode, have adb at the ready, and do:

adb shell cat /proc/kmsg > out.txt

...right after an LOS incident. Then pastebin the context of the .txt.
Tried it without a LOS incident, just to practice... The out.txt gets output to the same folder as ADB correct?

Found it and it just said this..

"cat: can't open '/proc/kmsg': Permission denied"

logcat printed out fine.....
 
Last edited:

dtm_stretch

Senior Member
Dec 22, 2010
477
163
0
Albany
Tried it without a LOS incident, just to practice... The out.txt gets output to the same folder as ADB correct?

Found it and it just said this..

"cat: can't open '/proc/kmsg': Permission denied"

I'm gonna jump in the irc and learn this real quick...
Make sure you give super user rights. after adb shell type su and then acknowledge on your phone.
 
  • Like
Reactions: jirafabo

jirafabo

Senior Member
Dec 4, 2007
766
71
0
Orlando
Make sure you give super user rights. after adb shell type su and then acknowledge on your phone.
thanks good sir. yeah i tried that too, but i didn't acknowledge on phone, i already have so wasn't asked too. trying again, here's my results, tried two different commands....
\

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Bo>cd..

C:\Users>cd..

C:\>cd androidsdk/tools

C:\AndroidSDK\tools>adb shell
$ su
su
# adb shell cat /proc/kmsg > out.txt
adb shell cat /proc/kmsg > out.txt
adb: not found
# cat /proc/kmsg > kmsg2.txt
cat /proc/kmsg > kmsg2.txt
cannot create kmsg2.txt: read-only file system
#
 
Last edited:

dtm_stretch

Senior Member
Dec 22, 2010
477
163
0
Albany
thanks good sir. yeah i tried that too, but i didn't acknowledge on phone, i already have so wasn't asked too. trying again, here's my results, tried two different commands....
\

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Bo>cd..

C:\Users>cd..

C:\>cd androidsdk/tools

C:\AndroidSDK\tools>adb shell
$ su
su
# adb shell cat /proc/kmsg > out.txt
adb shell cat /proc/kmsg > out.txt
adb: not found
# cat /proc/kmsg > kmsg2.txt
cat /proc/kmsg > kmsg2.txt
cannot create kmsg2.txt: read-only file system
#
after you have granted su just type

cat /proc/kmsg then just right click>select all>paste in paste bin

for some reason creating the .txt is causing the error
 
  • Like
Reactions: jirafabo

jirafabo

Senior Member
Dec 4, 2007
766
71
0
Orlando
after you have granted su just type

cat /proc/kmsg then just right click>select all>paste in paste bin

for some reason creating the .txt is causing the error
That worked. Weird that it won't write the file now, as it did for logcat and it actually did earlier but with an error written in the txt file. Oh well, this way worked.

I'll share my kmsg in the morning when I wake up with my LOS.
 
  • Like
Reactions: dtm_stretch

eagercrow

Senior Member
Mar 19, 2007
434
45
0
Great minds think alike!

Here is my post in that other thread:
My tasker profile to capture logs of LOS
Profile: LoS Reboot (11) ***name of profile***
Priority: 10 CoolDown: 0 ***gave it top priority, so it runs above everything else***
Event: Variable Set [ Variable:%CELLSRV Value:noservice ] ***profile runs when only when service drops out, thinking about duplicating this to another profile except for service in an "unknown" state***
Enter: Los Report And Reboot (10) ***name of task***
A1: Wait [MS:0 Seconds:20 Minutes:0 Hours:0 Days:0] ***wait 20sec after seeing no service, to allow for boot up, switch from roam to home or home to roam, ect...basically filters any "blips" out***
A2: Stop [With Error:Off] Stop [ %CELLSRV !~ unknown ] ***If I have cell service after 20sec this tells the whole thing to cancel***
A3: Airplane Mode [Set:On] ***switch airplane mode on because sometimes airplane cycle this fixes it***
A4: Wait [MS:0 Seconds:5 Minutes:0 Hours:0 Days:0] ***wait 5 sec for airplane mode to kick on***
A5: Airplane Mode [Set:Off] ***cycle airplane mode off***
A6: Wait [MS:0 Seconds:5 Minutes:0 Hours:0 Days:0] ***wait 5sec for mode to settle***
A7: Stop [With Error:Off] Stop [ %CELLSRV !~ noservice ] ***if I have cell service process is cancelled***
A8: Run Shell [Command:bugreport -d > /sdcard/losbug_$(date +%y-%m-%d_%H-%M-%S).txt Timeout (Seconds):0 Use Root:On] ***saves text file of bug report, this is a large file too. 3-5mb from what I've seen***
A9: Run Shell [Command:cat /proc/kmsg > /sdcard/loskmsg_$(date +%y-%m-%d_%H-%M-%S).txt Timeout (Seconds):0 Use Root:On] ***k0nane suggested this might be helpful in another thread***
A10: Wait [MS:0 Seconds:10 Minutes:0 Hours:0 Days:0] ***I have it wait because sometimes those reports take a little while to dump***
A11: Say [Text:Lost signal Engine:Voice:com.samsung.SMT:eng-USA-f01 Stream:3 Pitch:10 Speed:5 Continue Task Immediately:On] ***some people prefer a popup, I thought this was kinda cool. lol***
A12: Reboot [Type:Normal] ***reboot so I get service back and don't miss 15 calls***
Another thing I haven't posted here and I don't think I need to. I have another bootup profile set to run logcat -c that way the log is clear and fresh on every boot.

I don't know what I can do with these logs, but I'm hoping that devs can use them and fix our problem. Or at the very least figure out what is going on. I haven't had a damn LOS since running this...dammit! lol. But when I do I will post all logs to pastebin.com. We should maybe create another thread that consists purely of pastebin.com links regarding LOS
 
Last edited:

DarkPhoenix

Senior Member
Sep 6, 2007
534
68
0
Lebanon, TN
That's not a bad idea. I tried running bugreport -d > /sdcard/bugreport.txt but when I open it the text inside says that the file is to large.

Also added a few more logs to the 2nd and 3rd posts.
Sent from my SPH-D710 using xda premium