yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] trifthen:
Ok, so earlier in your log, I see this:

2011-12-05 10:29:52 : Info : Detected bad RIL Client - ghost LoS.
2011-12-05 10:29:52 : Warning : ghost LoS confirmed.
2011-12-05 10:29:52 : Warning : Attempt #1 to kill radio daemon...
2011-12-05 10:30:02 : Warning : Attempt #2 to kill radio daemon...
2011-12-05 10:30:12 : Error : RILD restart failed. Rebooting.
2011-12-05 10:31:22 : Info : LoSD Starting

Was that before the ghost LoS you saw that didn't reboot? If you can get it, could you go to the /data/local/LoSD directory and see if there are any timestamped directories? There should be at least one. In those, there will be a radio.log and connectivity.log. I need both of those. I may need more, but I've found those are generally enough.

If it didn't reboot, the next time this happens, could you open a terminal and:

su
bugreport > /sdcard/los.log

Zip that up and put it somewhere (It's pretty big)... :)

Thanks!
[Samsung Epic 4G Touch] greatlakesghost:
Must have been after. I just read a text from my wife and looked and saw I was full blown Los so I quick got on my work computer to see the specific commands I need in terminal to get the logs as my phone didn't restart. So I will look again and see what I have and send you everything I can. Tia

Edit: here are the other logs, I must have overlooked them earlier sorry.

http://db.tt/m6QSi4jL

http://db.tt/sEdbwWhY

http://db.tt/ovkw6lvG

http://db.tt/hV1FhBYi

Sorry the paste in app is kinda week and not user friendly imo so I did it with drop box because of ease of use for me. Let me know if you need anything else. :)

sent from my drama free epic touch 4geez
[Samsung Epic 4G Touch] -viperboy-:
Yeah, sometimes it will say connecting, that is part of a ghost LoS from my research.

You can also modify the logme script I wrote for my LoSChecker and include that with your script as well so people only have to type su then logme in terminal and it will gather the info you need. Again, modify to your liking :)
[Samsung Epic 4G Touch] trifthen:
These are great, thanks! It's pretty clear from this that what you had was full LoS, and not ghost LoS. The log was wrong, but that's because I have it checking for ghost LoS first, which has many of the same log errors. Based on this, I changed the order of the checks.

Now, if you don't have full LoS, next it will check for ghost LoS. Saying you have ghost LoS when you have no radio at all, is just a plan old lie. :)

Now I just need you to go back in time, and get logs for when it didn't find the problem. ;)
[Samsung Epic 4G Touch] greatlakesghost:
lol ok tell me how and I will lol

Glad I was able to help in some way, if you need me to do anything else or test anything absolutely feel free to hit me up. The sooner we can get a grip on this the better. Thanks for your efforts, I truly appreciate them.

sent from my drama free epic touch 4geez
[Samsung Epic 4G Touch] trifthen:
Bumped to version 0.9.0. Updated OP and Changelog with new information and links. From the changelog:

Version 0.9.0

Added non-LoS check for transient CONNECTING status.

Now check for ghost LoS *after* standard LoS.

Calling LoSD with 'dump' now dumps and tarballs all debugging logs.

So, there's your logme, Viper... kinda. I figured, I already have a function that dumps the logs in the utility, so why not use it? I also made it easier by taking the dumped logs and creating a tar archive that's 10x smaller than the log files themselves. It'll make it easier for users to send full debugging logs to make this work better.

Again, to get logs, simply get a root shell and type 'LoSD dump' and you'll not only get a directory of logs for what your phone was doing at the time, but a zipped archive ready for me to look at. :)
[Samsung Epic 4G Touch] rast4man:
Download link is dead, any mirrors? Could someone put it up on their Dropbox for me please? TIA

Regards,

rast4man
[Samsung Epic 4G Touch] mikel719:
Worked for me 3 minutes ago.

Sent from my epic touch B=====D {()} (o)(o)
[Samsung Epic 4G Touch] trifthen:
I just clicked it and it prompted a download. It's a zip file, though. If you're downloading on your phone, it won't download unless you've done a few extra steps, or use something other than the stock browser.
[Samsung Epic 4G Touch] mikel719:
Use dolphin hd browser on your phone.

Sent from my epic touch B=====D {()} (o)(o)
[Samsung Epic 4G Touch] rast4man:
Yeah I finally got it. For whatever reason it was putting an http:// in front of the httpS:// anyways I got it and going to flash Venums ROM then flash this over it. Thanks for the replies.

Regards,

rast4man
[Samsung Epic 4G Touch] tracerit:
gonna try this out.
[Samsung Epic 4G Touch] todivefor:
I might be missing something, but I think the "LoSD dump" is not working. I installed this and tried the command to see if it would work. I went to /local/data/LoSD and the timestamp for the dumped files was there. I looked at them and all 4 logs were empty but showed sizes of 3.6MB, 2.72K, 126.3K, and 140.17K. The logs.tar.gz showed 558.49K. When I tried emailing this to myself, nothing was sent. I extracted it to SDCard. That worked, but the directory was empty. What am I missing?
[Samsung Epic 4G Touch] trifthen:
How are you trying to view the files, exactly?

They're just text files, but Android is running on top of a UNIX, which means it's using only a newline to separate lines, instead of newline+carriage return on Windows, or just a carriage return on Macs. You can't view these properly in notepad or the Apple equivalent. Unless your android is really messed up, there's no way it dumped 5MB of empty (just spaces?) logs. :)

If it created the timestamped directory, and the dump is 500+k, that's about right for a log dump tarball. You can view the inside of the tarball if you un-tar it, or view it in 7-zip or the Mac equivalent. You can't just open the file itself. If you have access to a UNIX system, you can:

tar -xzf logs.tar.gz

And you'll get the same directory you saw on your phone, full of the same log files. Alternatively, you can view these on your phone with more or cat:

cat LoSD.log
more bugreport.log

For example.
[Samsung Epic 4G Touch] todivefor:
Thanks for your help. I was able to verify the data is there, I just don't understand why I am having trouble accessing it. I tried emailing the tarball and everytime I received it, there was no attachment. I tried viewing each of the logs in the timestamped directory with text view, no data. In each case, I was doing this through "Root Explorer." I have logs from an earlier date and could view them with no problem. I moved the tarball to sdcard and uploaded. Extracted and could read with no problem. I moved the logs from the time stamped directory to the sdcard and could view there with no problem (with root explorer). So it seems I have problems from /data/local (but only sometimes), but not sdcard. Unless someone has an explanation for this, I am going to write it off as a mystery that I can work around.
[Samsung Epic 4G Touch] trifthen:
Weird. You might want to try changing your LOGPATH to /sdcard/LoSD or something if you keep having random trouble. If anything, it'll make the logs easier to pull later.
[Samsung Epic 4G Touch] zzelinka:
For a mobile download link...

http://db.tt/wEZ0LVrB
[Samsung Epic 4G Touch] greatlakesghost:
OK had another episode today but I am running a different yet same setup. I on the venum rom which is basically caulkins 2.0.1 I believe with outlaw kernel. I here is today's logs-

http://db.tt/AAdAfvYw

Let me know if you need anything else. Thanks again!
[Samsung Epic 4G Touch] trifthen:
2011-12-06 16:37:56 : Info : Radio appears normal - no LoS.
2011-12-06 16:39:57 : Info : Confirmed radio unavailable.
2011-12-06 16:39:57 : Warning : full LoS confirmed.
2011-12-06 16:39:57 : Warning : Attempt #1 to kill radio daemon...
2011-12-06 16:40:07 : Warning : Attempt #2 to kill radio daemon...
2011-12-06 16:40:27 : Info : LoSD Starting

I... don't know what of make of this. It clearly saw the LoS, and was in the process of fixing it, and then... it restarts? But it only shows that "LoSD Starting" line if some other process starts it, or if you started it from the command line.

Did you call 'LoSD' by itself at the command line without also adding 'dump' as an option? If the second radio restart attempt at 16:40:07 failed, it would have restarted the phone 10 seconds later. You might have acted too fast and did a log dump, but you didn't give many details. Also, the 'dump' option only works in 0.9.0 and above. If you try to use it before that, it'll just start another copy of LoSD.

Maybe I'll add a check so it won't start another daemon if a daemon is already running.
[Samsung Epic 4G Touch] greatlakesghost:
Sorry. I was in a rush at work at that moment. I did nothing. I actually watch my phone go into a full blown los this time as I was at work trying to get on xda, and had 2 bars but nothing was happening and as it sat there and dwellers first 3g disappeared then about 5 seconds later got the old circle with line through it. So I hopped on my work computer just to double check about last night's revision and then rebooted my phone so I could upload logs to dropbox (not allowed any downloads or uploads on work computers at work), uploaded and posted it. Anything else I could of or should have done? I just want ti get you as much info as possible and since these last two combos of roms and kernels is giving me fits it is providing that opportunity.
[Samsung Epic 4G Touch] trifthen:
Wait... I can't tell what you're trying to say.

You had LoS, but you had two bars?? I'm having a hard time parsing that paragraph. :)

It's just that the log you sent is just the LoSD log, which describes what LoSD is trying to do, not what it encountered. I need the contents of the timestamped directory it created when it sensed LoS. Or, if it's not sensing the LoS, you need to go to a terminal or adb shell and type 'LoSD dump' without the quotes and send me the logs.tar.gz in /data/local/LoSD. LoSD.log is useful, but doesn't describe the LoS itself.

What I don't understand about the LoSD.log you sent, is how it said "LoSD starting" right after it said "Warning : Attempt #2 to kill radio daemon..." It should have looked like this:

2011-12-06 09:21:59 : Info : Radio appears normal - no LoS.
2011-12-06 09:28:40 : Info : Detected bad RIL Client - ghost LoS.
2011-12-06 09:28:41 : Warning : ghost LoS confirmed.
2011-12-06 09:28:41 : Warning : Attempt #1 to kill radio daemon...
2011-12-06 09:28:51 : Warning : Attempt #2 to kill radio daemon...
2011-12-06 09:29:01 : Error : RILD restart failed. Rebooting.
2011-12-06 09:29:31 : Info : LoSD Starting
2011-12-06 09:31:31 : Info : Radio appears normal - no LoS.

Notice that your log says, "Warning : full LoS confirmed." at around 4:40pm. It then tries twice to restart the radio, and normally if it can't, it reboots. But notice your log is missing "Error : RILD restart failed. Rebooting." So either something else rebooted the phone before LoSD could, or some mysterious service killed LoSD itself before it could start the reboot. But if that second option happened, why did LoSD restart?

So that leaves the first option: something rebooted your phone before LoSD could log "Error : RILD restart failed. Rebooting." Then after the phone rebooted, it restarted LoSD, so then you get the "Info: LoSD Starting." line.

It saw your LoS. It was restarting the radio. It tries to do that twice, and waits ten seconds after each try so the radio can restart. That's 20 seconds after it notices, and it only runs every two minutes while the phone is awake. If its in deep sleep, it runs less often due to how Android works. So you could have been full LoS for around 2-3 minutes before it got to the point LoSD started a reboot.

You said you rebooted your phone, but you didn't say when. If you did it after 16:40:07, but before 16:40:27, you didn't let LoSD finish. If you didn't do it... someone or something killed LoSD and then restarted it. I have no clue what would do that other than a reboot. :(
[Samsung Epic 4G Touch] dtarr:
trifthen, just want to send a big "THANKS" for creating and maintaining the LOS Daemon script. It's made my phone almost reliable using Calkulin's 1.5a ROM. The phone hardware is fantastic and so is the custom ROM but the LOS issue is a killer.

I'm sticking with this solution until EK02 is a solid fix.
[Samsung Epic 4G Touch] rksand:
Just to report, I had this running on odexed Blazer ROM for two days, and today started having strange issues. Wifi would not stay connected and my notification led turned on despite it being turned off. Toggling it did not fix it. The problem persisted through reboots. Removing the Damon seems to have solved the problem.
[Samsung Epic 4G Touch] jefbal99:
THis is working great on my phone, are you interested in the logs?
[Samsung Epic 4G Touch] trifthen:
This is what you would call a "known" issue. :) The problem is that killing the radio sometimes... makes the phone freak out in weird ways. It restarts the radio, but in doing so, other stuff gets kinda wonky. I've had the same occasional problem with the notification light after the radio is restarted, though I haven't seen issues with WiFi personally.

I don't know why it's doing that, so I can't fix it. Nothing really shows up in the logs either. I've been planning to add an option to limit the number of radio restarts. So, for example if it's already restarted the radio twice, and now it has to do it a third time, the chances of things getting buggy are pretty high. In that case, it would reboot instead of restart the radio. I'm thinking a default of 3 is fair, and the user can lower that with LOSD.ini.

It's good to know that it's not just a theory though. I only had my own experience on this particular side-effect, so now that I know it's not just me, I'll work the radio restart limit into LoSD. I'll also make sure you can set that limit to 0, so it just reboots instead of trying to restart the daemon. The default will be 3. My personal preference would probably be 1 or even 0.

Naw. If it's working right, the logs won't help me. So far the logs I've seen when it's working properly are exactly what I expect. If you think it's working great, I suggest you set DUMPLOGS=0 in your LoSD.ini so it stops dumping logs for you. :)
[Samsung Epic 4G Touch] trifthen:
Well, I've upgraded to the EK02 modem and the Rogue 1.1.1 repacked EK02 kernel. While developing LoSD, I tended to get at least one ghost LoS per day. I'll keep LoSD installed and see if EK02 helps at all.

If it does, I'll discontinue, but at least maintain this in case anyone wants it. If not, well, we'll see. Either way, I'm going to add the stuff I've mentioned so far in the last few posts. Look for something tonight or tomorrow.
[Samsung Epic 4G Touch] greatlakesghost:
I am testing the ek02 modem as well in one of my setups that was giving me complete los fits so we shall see how it goes today. Thanks for you and vipers effort with this.
[Samsung Epic 4G Touch] 1lazysheep:
upgraded to EK02 modem last night and got LoS within an hour. what do you make of this?
[Samsung Epic 4G Touch] trifthen:
Looks like it caught a possible ghost LoS. If you happen to have the radio.log available, I'd love to see that.

On another note, I just found a better and safer way to restart the radio.

setprop ctl.stop ril-daemon
setprop ctl.start ril-daemon

This actually uses the system, so it may reduce the side-effects, such as stuck notification lights or possibly glitchy WiFi after restarting the radio. I'll leave the old restart in, but only if the daemon won't respond to the setprop method.
[Samsung Epic 4G Touch] 1lazysheep:
i'm not sure what to do with the code you provided. i'm not a dev :)

so i just got another Data Roaming warning and LoSD recorded another ghost LoS a few minutes ago. the radio log is included
[Samsung Epic 4G Touch] trifthen:
Lots of changes in this version. Updated OP and download link.

Version 1.0.0

Log dumping is now disabled by default.

Now uses 'setprop ctl.stop/ctl.start' to try restarting RILD nicely.

Does a quick check to prevent multiple running copies.

Added a radio restart limit to avoid glitchy post-fix systems.

Clear radio log in case of false positive ghost LoS.

I noticed that the normal check I use for ghost LoS can be caused by an incoming phone call. So, now the active phone call check will clear the radio log if you're in a phone call. The rest is pretty straight-forward.

If you want to re-enable log dumps, set DUMPLOGS=1 in your LoSD.ini.

Enjoy!
[Samsung Epic 4G Touch] dtarr:
Running Rogue 1.1.3 and EK02 kernel I got a full LOS overnight. The LoSD wasn't installed so unfortunately no log files. I just re-installed LoSD and we'll see what happens. Bummer....

Thanks again trifthen for what might turn out to be long term fix... One very minor suggestion for the script: Only post to the log on state change. I don't think we need postings every 2mins (or whatever the interval is) only when something new happens.
[Samsung Epic 4G Touch] trifthen:
It already does that. Just put DEBUG=0 in your LoSD.ini configuration file.
[Samsung Epic 4G Touch] trifthen:
I just got a chance to look at this log. It confirms what I just fixed with the 1.0.0 version, actually.

It turns out that one of the ghost LoS checks actually gets triggered at the very beginning of a phone call. Version 0.9.0 and older would leave the radio alone as long as you were on the phone, but as soon as you hung up, it would restart the radio.

Beginning with version 1.0.0, it will now see that you're on a phone call, and clear the radio log so LoSD doesn't re-detect the ghost LoS and needlessly restart your radio. So Mr. Lazy Sheep, if you upgrade to the newest version, scenarios like this will be handled properly.

This goes for everyone! Less radio restarts are good!
[Samsung Epic 4G Touch] 1lazysheep:
thank you. upgrading now...
[Samsung Epic 4G Touch] greatlakesghost:
OK I just checked my logs, forgot to upgrade to 1.0 sorry, but I was amazed when I saw 11dumps in there. You want any or all of them before I go flashing your new one?
[Samsung Epic 4G Touch] ravizzle:
The link for download doesn't work. Please update.

Thanks for the mod in advance. Los is killing me!

Sent from my Galaxy S2
[Samsung Epic 4G Touch] narucii:
Am I missing something ? I can't find the path to the log file. I did the losd dump but still cant find it.
[Samsung Epic 4G Touch] greatlakesghost:
/data/local/LoSD
[Samsung Epic 4G Touch] narucii:
It doesnt have any file in there.
[Samsung Epic 4G Touch] greatlakesghost:
Try running the script again
[Samsung Epic 4G Touch] narucii:
I did
[Samsung Epic 4G Touch] greatlakesghost:
Well if it didn't take I would try running his uninstall script and redownload the install script and try it again. Probably a bad down load.
[Samsung Epic 4G Touch] trifthen:
Bad news, folks. It's not time to put this away just yet. I'm on a full EK02 system, including modem, and not only did I get a full LoS, but no method I tried would return connectivity.

Not setprop, not killall, nothing. Only a reboot worked. I can confirm the radio was listed as unavailable the entire time, so LoSD would have fixed it. Maybe we'll have better luck with EL13, but I'm not ready to move to that firmware until it's official.

Just a heads up. If any dev wants to shove this into their ROM, go ahead. It seems to consistently catch both ghost and regular LoS now, and I've disabled default log dumping. Feel free to customize.
[Samsung Epic 4G Touch] narucii:
Since I installed this, my phone reboot at least serveral time a day. It doesn't work for me.
[Samsung Epic 4G Touch] rbaucom:
Hi apparently I was not the only person experiencing reboots, I downloaded Calk's latest (as of two days ago), did a backup of current system with CWM backup Which was full stock with CWM added on via full automated script. Full wipe with his included wipe zip file from clockwork mod, then installed his rom. Reboot/Launch of his Rom, to verify that it was a good install. rebooted into CWM recovery flashed your deamon file and back to reboot into system. From there I was: wow nice and shiny and fast! Then I experienced 6 reboots, before I went back to stock.

Yes I did full wipe, no did not restore anything from backup. Not complaining, just informing.

I would be using the phone and next would be looking at the white galaxy startup logo.
[Samsung Epic 4G Touch] todivefor:
Trifthen, keep at it. I have the same experience. I have tried multiple kernels with Viper ROM, and have found the best results with EK02 stock (with minor changes ie. no ciq, and init.d support). I still get a couple LOSes a day in low signal areas. The 2 attempts to fix usually don't work, but the reboot does. Keep up the good work. This doesn't seem to be going away.
[Samsung Epic 4G Touch] trifthen:
Weird. I've noticed in low signal areas, or in areas where it might roam frequently, it gets a lot of errors that are the same ones it checks for ghost LoS. It should only restart the radio, unless that doesn't fix the problem. It only reboots if:

1. It needs to restart the radio more than four times since the last reboot.

2. Restarting the radio twice in a row doesn't fix the detected LoS.

There might be something in that ROM that's confusing the detection, too. I think I added a 'Requirements' section in the OP, but you can only use this if you have busybox, an init.d compatible kernel, and root. If any of those three is missing, I can't vouch for how it'll react. But any non-stock ROM here should have all that, so I don't know.

I am looking into trying to narrow down the ghost LoS situations, so it's not restarting the radio needlessly. Old versions of this had a bug that improperly detected phone calls, so it would reboot in the middle of one. The current 1.0 release is probably the most conservative so far.

That said, it restarted my radio four times in the last three hours and then rebooted because it detected ghost almost every time it checked. Something -viperboy- said about the new EK02 radio makes me wonder... he said the radio restarted itself to fix his LoS, and I had that happen to me while on the train to work this morning. I was using the phone just fine, and boom, what looked like a soft boot following a radio restart, but LoSD didn't do it. In fact, it was still running in the background and saying the radio was fine.

But it was after this EK02 self-restart that LoSD started detecting ghost LoS almost constantly. So I'm thinking there's some flaw in the EK02 restart that doesn't bring everything up properly, and the logs start filling up with RILJ (the error I got) generic failure messages. I've re-enabled log dumps on my phone to investigate this further.
[Samsung Epic 4G Touch] dragonOL2:
This is EXACTLY what happened to me yesterday; in an area with low reception / high susceptibility to roaming, I got lots of errors and the LoSD restarted the RIL until finally the restart number grew to a point that it just rebooted the phone (as you designed it, I believe). So thanks for the work; glad I held on to the script after upgrading to EK02 (both kernel as well as modem)

How did you go about doing this? I'd like to do the same to investigate my own dumps and I know log dumping isn't enabled by default with your latest and greatest version of the script. Thanks for the help...
[Samsung Epic 4G Touch] todivefor:
Put DUMPLOGS=1 in file LoSD.ini in /data/local/LoSD directory.
[Samsung Epic 4G Touch] todivefor:
I have noticed something new recently. Out of the blue, I will get the 3 beeps and message, "data roaming." However it is not roaming. This is happening at home where I have a strong signal. When I look it is not roaming. If I look in the LoSD.log, it shows, "Confirmed ghost LoS." Does the LoSD reset cause that roaming message or does the roaming cause LoSD to do the reset?