yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] trifthen:
I'm currently testing a couple tweaks that will help eliminate false positives. But one weird thing I've seen in my logs is this:

12-20 22:19:51.685 3544 3565 E bm : radio is down and orca is up - ERROR STATE
12-20 22:35:40.160 3544 3565 E bm : radio is down and orca is up - ERROR STATE
12-20 22:46:13.325 3544 3565 E bm : radio is down and orca is up - ERROR STATE

Googling for any of this is completely empty. Nothing on whatever is entering the 'bm' log messages. Nothing on 'orca is up' in reference to android. It seems like some made-up error. But my last ghost LoS that LoSD didn't catch had those above errors, and they are timestamped about half an hour before my wife said she tried to call and text me.

So I'm going to test this for a couple days to make sure it seems sane. Otherwise, the checker is more careful at checking the RILJ daemon, which seems to be the cause of most of my false positives. I may have a way to check the CDMA service too, but I'll hold off on that if this doesn't work.

Just keeping you guys informed, since EK02 still has LoS issues. Just not as often, it seems.
[Samsung Epic 4G Touch] dragonOL2:
Can definitely vouch for this. I got about 6 separate LoS instances in the span of about 4 hours a few days ago. Granted, for 2 of those hours I was sitting in an IMAX theater with horrible reception, but the rest were the garden variety LoS that triggered the LoSD to take action. Thanks for the good work!
[Samsung Epic 4G Touch] trifthen:
Version 1.2.0

Added debug log level.

Moved several informative messages to debugging only.

Debugging is now disabled by default.

Tweaked RILJ error detection for RIL_REQUEST_CDMA_GET_SYSTEMPROPERTIES.

Can now ignore false positive ghost LoS caused by phone calls.

Phone call and Airplane mode now checked before anything else.

CONNECTING status no longer skips LoS check.

Added ghost LoS check for CDMA 'Unknown data error' messages.

Lots of changes in this release, folks. :) Far less false positives than before. I've been digging through my logs with debugging and log dumps enabled (have over 20) looking for things to check for or ignore.
[Samsung Epic 4G Touch] slick4mitch:
This is awesone work and all but doesn't the new radios deal with this LOS problem?
[Samsung Epic 4G Touch] trifthen:
That's actually not the case. I'm running the EK02 modem and EK02 kernel, and an EK02-based ROM. I thought I wouldn't need this anymore, but poof, LoS. Now, I tend to get ghost LoS instead of full, but I have gotten regular LoS a couple times. It happens less often, but it happens.

For me, it happened with stock EG30, even though a lot of people claimed up and down that it never happened unless you used a custom kernel. I was completely stock at the time.

I haven't tried EL13 or EL26 yet, but I'm trying to stay relatively close to official so I can make sure LoSD is actually fixing something. Until the next OTA update, nobody should be running anything higher than EK02. And that means LoS, at least for me, so I assume at least one other person out there is having the same problems.

Maybe it's just the Chicago area that sucks. Maybe it's the fact I go from the train to a high-rise with several signal deadzones in-between, but the fact is the radio gets confused and stops connecting to towers. While it does this, it says "CONNECTING" for hours on end, even after several modem restarts. That's why I added the feature for LoSD to reboot if several restarts don't fix the radio.

The problem with ghost LoS is you don't know you have it until someone tells you they tried to call you, or you can't send a text message. It looks like they nearly got rid of full LoS, but ghost LoS is all too real. I get one about every other day. Until that stops, I'll keep tweaking this, because I can't afford to have my signal die; I have a job that needs to contact me in emergencies.

If you're fixed with the new modems, I'm totally glad for you and wish I had your luck. :)
[Samsung Epic 4G Touch] buggerritt:
Well, a good lot of us are and we don't get LOS anymore. We actually haven't since the EL13 dropped. Now, we're on EL26, the second update that doesn't have that horrible CIQ crap included. After all the hype about CIQ, nobody should be running any build previous to EL13 unless they enjoy performance loss, battery drain, and having their privacy illegally violated.
[Samsung Epic 4G Touch] trifthen:
Or you can just run an EK02 that removed ciq, which was basically all of them. I know ciq is bad, but that hasn't been an issue for a long time.

Like I said, for people who want to stay relatively stock, EL13 and EL26 are not an option. Considering the EG31 mess, just jumping on the latest leak isn't always a good idea. I totally get you, and if they would get off their butts and do a freaking OTA already I'd be on a repack immediately.
[Samsung Epic 4G Touch] buggerritt:
I don't know what mess you are referring to. EL13 was gorgeous. The only thing that had any problem with it was setting a lockscreen wallpaper was stretched and the scrolling wallpaper in TW was not working.

As for staying stock, EL13 and EL26 are "stock" they just aren't official OTA builds. Removing CIQ was never complete with EK02. Fuctionality of CIQ was removed but, some files were left behind. Removing them would result in the OS not booting. That hardly sounds like a good thing. It was all we could get at the time but now we don't have to deal with it anymore. Sprint has ordered it to be off of their system for all future builds.

OTA builds in the past have been known to have bugs and some have even bricked phones.

If people want to be on the old redundant official build, that's their prerogative but, to say that no-one should be on the latest is misinformation and may scare users from trying out the newer and far superior builds. With CWM, Odin, Mobile Odin, and $2 USB jigs available, you can always flash back to stock or any other ROM/kernel/modem/mod/theme. There is nothing to fear.
[Samsung Epic 4G Touch] trifthen:
I meant EG31, which many people were stuck with until someone leaked the EG30 modem. For a while, people were scared they might not be able to use newer modems because previous versions were patches instead of a full modem. Because of that, there are still people who won't run something unless there is an OTA. I don't agree or disagree with this, but it happens.

As long as people continue to download this, I will continue to maintain it. I'm not here to judge, but provide a fix for people who want it, regardless of their reasons.

If you don't need it, that's fine, but please stop trolling my thread to tell me to stop helping people. This conversation is over.
[Samsung Epic 4G Touch] slick4mitch:
This ... +1 ... but keep the good work on the LoS front ... I, for one, havent gotten any since I moved to EL13 :)

Not trolling by the way.
[Samsung Epic 4G Touch] buggerritt:
I didn't tell you or even ask you to stop maintaining what you are doing. I merely corrected you for what you said, "Until the next OTA update, nobody should be running anything higher than EK02.", which IS judging and misinforming. I did not attack you or your work. I offered what is called

constructive

criticism.

Obviously, people appreciate your work and I wouldn't want you to stop helping people. But, your attitude, at this moment, is leaving me with ill regard. Maybe, you haven't had your first cup of coffee or your gf didn't talk nice to you this am. I'll assume you're a better person on most days and leave it at that.
[Samsung Epic 4G Touch] trifthen:
Cool. I like hearing that. Unfortunately I heard the same thing with EK02. :(

And just to clarify because apparently I got misinterpreted somehow, I wasn't implying nobody should ever upgrade to leaks. Not everyone downloads the latest and greatest. For folks who want to stick to semi-official builds and treat the leaks like they don't exist because they might not be stable, there isn't really an option, unfortunately.

I mean... not to denigrate EL26 or anything, but we still don't know what it actually does. They changed the phone icon and the calling screen is different. Great. But what else does it do? Nobody knows because it's a leak. We're just guessing whether or not it's safe. There could be some horrible bug we don't know about, and EL30 will be out today. Until an OTA, upgrading carries a small degree of risk.

People who don't want to take that risk, however small, still need this if EL13 and beyond really fix the problem. That's all I'm saying.
[Samsung Epic 4G Touch] Just_s:
FWIW, I had 2 LoS on EK02 (zero when paired w/ stock kernel) over several weeks. Zero LoS on EL13 over 3+ weeks with any kernel. Zero LoS so far on EL26, day 5 both Rogue kernels tried. Incredible GPS improvement on EL26 btw. That was my biggest issue with the phone and it seems to be resolved (within the confines of Samsung's horrible GPS structure that is. It'll never be great on this phone but at least it's around 50% as good as HTC now.)

Definitely appreciate the work you, viperboy and kai did on this, and I think anyone who decides not to move past EK02 can definitely use it, but I haven't used it since EG31 with the results noted above.
[Samsung Epic 4G Touch] buggerritt:
After reading your pm, I realize I thanked you by mistake.
[Samsung Epic 4G Touch] JohnCorleone:
You definitely have a point about not knowing what exactly was supposed to be fixed/changed in the leaks. Some people report better data speeds and others worse. It would be nice if we got some sort of changelog. I will say this though, we don't have tons of LOS posts anymore. That shouldn't discourage you from updating the script though. There are probably plenty of people that only feel comfortable on official builds. I have never had a LOS so I can't say that the issue is totally fixed but I have had excellent results on EL13 and so far on EL26.
[Samsung Epic 4G Touch] trifthen:
Yeah. Downloads are 10x less than the last version. I'd say that is a good sign. I wonder how many leaks there will be before the next OTA.
[Samsung Epic 4G Touch] lunchboxVA:
...so i have a question i may have to drop back to EG30 because my wifi speeds are like .76Mbps on EL26 and were like 13+Mbps on EG30...i just need some clarification on

"WARNING! Do not wipe anything before or after install of this utility! It is not a ROM. You will be left with an unbootable system" ....

does that mean i have to uninstall LosD before flashing new roms and kernals?
[Samsung Epic 4G Touch] trifthen:
No. I put that warning there so nobody tries installing this like a ROM. If you install a ROM, you'll have to re-flash LoSD, but that's all.

Concerning your speeds, I never clocked that high on EG30. In fact, aside from LoS improvement with each release, I haven't noticed much difference at all. Are you sure about EG30 being that much faster than the newer modems even after a PRL and profile update?
[Samsung Epic 4G Touch] lunchboxVA:
u know now i honestly dont know...when i flashed back to EG30 i got this great boost of speed on speedtest reading at 9Mbps on WIFI but the more i ran it it dropped down to .89Mbps...for some reason when i was on EG30 before flashing any modem i was able to consistantly hit such high numbers
[Samsung Epic 4G Touch] Bear Knuckles:
I have been having issues with people receiving my texts for a couple of weeks now. Updating prl and profile does nothing. Went to sprint store where they implied it was the apparently fault. I told them I used the apparently for months with night issues. Then they tried to imply that I might have rooted my phone and messed it up. They finally tried a "soft reset" from their side which fixed the issue for an hour and then I got the same issue again.

I am flashing this and hoping it helps.

Sent from my Epic Deuce
[Samsung Epic 4G Touch] todivefor:
It appears you have a problem correctly detecting when airplane mode is on. I went through the day without a problem. At night I turned on AP mode. Had detections of radio unavailable followed by full Los. 2 attempts, then reboot. LoSD 1.2.0, calk 2.7 rom, Rogue stock EL26 kernel, EK02 modem.
[Samsung Epic 4G Touch] trifthen:
If you happen to have a log dump for this, I'd love to see it. I've tested airplane mode several times and dumpsys always showed it pretty clearly.
[Samsung Epic 4G Touch] Bear Knuckles:
How do I know if this is working?

Sent from my Epic Deuce
[Samsung Epic 4G Touch] todivefor:
Here you go. Not from last night, but today.
[Samsung Epic 4G Touch] trifthen:
Interesting. It would seem that something Calkulin did something to his ROM, or else the EL26 kernel/firmware completely changes the location dumpsys. Check out what my phone says at the very end of 'dumpsys location':

WifiScanFrequency 86400000
WifiEnabled 1
WaitingForWifiScan 0
LastNetworkQueryTime 44136229
LastSuccessfulNetworkQueryTime 44136539
Enabled 1
AirplaneMode 0
DisabledForAirplaneMode 0

If I turn off network location, 'Enabled' is set to 0. If I turn off Wifi, 'WifiEnabled' is set to 0, and so on. But the sections are still there. Your logs don't have any of this anywhere. The string AirplaneMode doesn't even exist at all.

Can someone who isn't running Calkulin's ROM, but is running EL13, EL26, or EL29, run 'dumpsys location' in an adb shell or su terminal? This block should be at the very end of that output. If not, I need to come up with a different way of detecting airplane mode in newer firmwares.
[Samsung Epic 4G Touch] dragonOL2:
Anyone still running the daemon on EL26 or EL29? Any positive instances of LoS detected? Just wondering...
[Samsung Epic 4G Touch] greatlakesghost:
Pm sent with dumpsys location log.
[Samsung Epic 4G Touch] trifthen:
Updated OP with new update.

Version 1.3.0

Improved CDMA connection FAILED detection.

Added second Airplane mode check for EL13, EL26, EL29 firmwares.

Also as a side note, I saw this in my logs during the CDMA testing:

01-13 13:30:40.539 D/CDMA ( 3070): [CdmaDataConnectionTracker] setState: FAILED
01-13 13:45:40.790 D/CDMA ( 3070): [CdmaDataConnectionTracker] setState: FAILED
01-13 14:00:40.564 D/CDMA ( 3070): [CdmaDataConnectionTracker] setState: FAILED
01-13 14:15:40.589 D/CDMA ( 3070): [CdmaDataConnectionTracker] setState: FAILED
01-13 14:30:40.870 D/CDMA ( 3070): [CdmaDataConnectionTracker] setState: FAILED
01-13 14:45:40.835 D/CDMA ( 3070): [CdmaDataConnectionTracker] setState: FAILED

Notice the 15-minute interval? I'm not sure what's causing that, but it looks suspiciously like Juice Defender's default data wake interval. If that's it, repeatedly toggling data on the older, unstable radios will probably eventually cause them to ghost, or Los. In fact, I've already proven with older versions of LoSD, that after killing or turning the radio on and off a few times, the phone starts acting weird in general, or enters LoS.

So along with this update, I'm going to recommend disabling Juice Defender if you use it. I've disabled it, and I'm going to watch the logs closely.

If you're using a newer ROM using recent EL13, EL26, or EL29 modems, I added a check for a logcat message that gets sent if you enable Airplane Mode. I won't know for sure unless someone sends me an 'LoSD dump' while using airplane mode and one of these newer firmwares. But at the very least, the extra check shouldn't make it worse. :)
[Samsung Epic 4G Touch] todivefor:
1.3.0 fixed my AP mode problem. Running Calk 2.8.1 ROM, EL29 kernel, EK02 modem. LOS has not been much of a problem with this modem, but like LoSD just in case. Thanks.
[Samsung Epic 4G Touch] todivefor:
I spoke too soon. Disregard the LOS at 07:55 on 14th. I think that was real. I was playing around installing LoSD and AP mode about that time and not sure of the circumstances. All the others were with AP mode on. Turned AP mode on about 10:00PM on 14th and turned AP mode off about 6:30AM on 15th. Hope this helps.
[Samsung Epic 4G Touch] brekfist:
Great program. I have had it installed for a month now, every time I use the phone now I can make a phone call. I have seen it reboot twice.

Does LoSD work for Ice cream Sandwich (ICS) ?
[Samsung Epic 4G Touch] daniel4653:
Did you really need to bring this back up ?
[Samsung Epic 4G Touch] CyberpodS2:
Rumpa dump dump completely useless bump...
[Samsung Epic 4G Touch] donsh00tmesanta:
Nice ima keep this around
[Samsung Epic 4G Touch] Censura_Umbra:
This looks useful, would it work on the new jb Roms, or only GB?
[Samsung Epic 4G Touch] Dchibro:
Haha. LOS is back on the JB ROMs, so people are searching for solutions. Although this is just a bandaid, not a fix.
[Samsung Epic 4G Touch] Censura_Umbra:
Well if it works for job, then it may be more like a vaccine. Not only would it automatically help Los, you can set it to auto save logs so even noobs can contribute
[Samsung Epic 4G Touch] Censura_Umbra:
Why did you just bump this
[Samsung Epic 4G Touch] zzelinka:
Bump :)
[Samsung Epic 4G Touch] acejoker25000:
I flashed this with a jb Rom and didn't experience los but didn't run the Rom very long

私は神の罰です。
[Samsung Epic 4G Touch] Censura_Umbra:
Okay, well at least it didn't Bork anything
[Samsung Epic 4G Touch] kathompson2nd:
I don't believe its working for jb. Installed and restarted...I had signal for five minutes and its been twenty with no change or forced restart.
[Samsung Epic 4G Touch] trifthen:
Holy crap, I never saw this thread got necro-bumped. :eek:

I'll start taking a look at it again for JB. It's likely a lot of the logcat messages and other phone status pieces I'm checking have changed, which is unfortunate. I'll need dumps though, since I'm not entirely willing to FUBAR my phone by putting JB on it just yet. ;)

Though on second thought, ICS is much closer to JB than GB is. I bet if I update to ICS at least, it'll be much more likely to work. I still get LoS occasionally due to my building's weird magic field that seems to drive my radio insane occasionally, so testing won't be a problem. I'll warn that LoS seems to be a mostly solved problem. That it's back with JB suggests some Kernel setting got missed, or because we have no JB-native modem. I seem to remember LoS being only from kernel source builds, so it's not entirely surprising it came back. I'll update my band-aid, but I'm guessing it'll be made irrelevant soon enough. At least I hope so.
[Samsung Epic 4G Touch] Censura_Umbra:
Thank you. I'm interested in the easy logging and the possible band aid effect. (Though I don't think it is a typical Los. As mine only happened due to the phone.apk)

However jb runs well on our phones. Only the Los is a real issue. You should try it out. Once all Los is fixed it will be my daily
[Samsung Epic 4G Touch] manufan721:
Only downside is phone will continuously reboot if it cant strengthen signal...lol, this includes airplane mode...at least it did for me and one other person

If at first you don't succeed, read the op......
[Samsung Epic 4G Touch] Censura_Umbra:
Yeah, but Los isn't that bad on jb. Just like once an hour.

And if it is auto fixed, then I won't have to check constantly to make sure there is no los
[Samsung Epic 4G Touch] trifthen:
OP updated with newer version.

Version 1.3.1

Added third Airplane mode check for ICS firmwares.

Third firmware check also works on phones with disabled logcat.

This should at least keep your phone from rebooting when in airplane mode, unless they changed the location of where that's reported again in JB. Seriously, why can't they just have a status check in the same place in the logs? What does moving it actually accomplish?

Surprisingly the connectivity and ghost LoS checks that were already built for GB still looked valid for ICS after a few manual checks, so JB should be OK. If this doesn't work, it's because there's a LoS it's missing. If it *does* work, but is rebooting your phone too often, you should increase the RESTART_LIMIT setting from the default of 3. I put that in there because RILD in the early GB roms would get really flaky after being restarted so many times, and it was better to reboot after two or three radio restarts. It's likely newer radios are more stable, so you can probably bump that setting up safely.

Hope this helps. I just installed LoSD myself because it's been a while since I've actually needed it, and I'd like to see how it operates these days. I'll keep an eye on my logs, which I just bloated by setting DEBUG=1. Hooray?
[Samsung Epic 4G Touch] Censura_Umbra:
Hoorayy thank for this, hope it helps
[Samsung Epic 4G Touch] AdhvanIt:
Anyone else have any issues with getting cm10 a2.3 to boot when flash this over it? I get stuck at sgs2 splash.

Adb doesn't connect that early in boot process, otherwise I'd throw in a log cat too...

Sent from another Galaxy [S2]
[Samsung Epic 4G Touch] trifthen:
That's odd. Does that have a kernel with init.d support and busybox? Most of the devs I've seen install those, but you never know. I'll see if I can look into it when I have time this weekend.
[Samsung Epic 4G Touch] AdhvanIt:
I can't imagine it would come without busybox, but I have no idea on the init.d support..

Sent from another Galaxy [S2]
[Samsung Epic 4G Touch] element1966:
That's been a question of mine as well. How do we check to see if the kernel we are running supports init.d?
[Samsung Epic 4G Touch] gershee:
nice update! any reports of how this works on jb? (or if it boots :D)
[Samsung Epic 4G Touch] Custodian:
This chit doesn't work on CM10. Thanks for the time spent working on this chit. Hope you continue to contribute more to the community.
[Samsung Epic 4G Touch] dougiefresh36:
If the ROM's kernel doesnt support init.d, is there a way to run it with SManager?
[Samsung Epic 4G Touch] yinyang37:
I put in on JB ROM on ET4G, it wouldn't boot. Stuck on Samsung screen. So without wiping anything I just reflashed my ROM and back to normal. Hope this helps. Thanks for your hard work!
[Samsung Epic 4G Touch] jayslim1983:
i had the same issue with CM10 would not boot im the el26 had no los all yesterday when i flashed woke up this morning and los every 4-6 mins thanks in advance i know your going to figure it out
[Samsung Epic 4G Touch] rast4man:
Glad to see this back in action. I used it when you first released it and it helped out a ton since I was in a partial dead-zone. Subscribed!

Regards,

rast4man

Sent from my rooted LG burner phone.
[Nexus One Q&A, Help & Troubleshooting] JeepFreak:
I'm running a kanged CM7.2 nightly (currently 7.2.0.RC0) and I am trying to use the notification power button widget to keep the phone in 2G mode while I listen to internet radio. The problem is, when in 2G mode, it's constantly switching between GPRS and Edge, therefor momentarily breaking the connection.

I tried to find some documentation on the "Network modes" and "Mobildata auto 2G/3G" (both in CM Settings -> Interface -> Notification power widget -> Widget buttons), but couldn't find anything. How can I stop it from switching back and forth?

Much thanks,

Billy
[Nexus One Q&A, Help & Troubleshooting] bassmadrigal:
My understanding is that GPRS is 1G where EDGE is 2G. If you are switching to GPRS, then that means the 2G signal is too low. I doubt 1G is capable of streaming the audio, which is most likely what caused your problems.
[Wildfire General] ukdevil:
can any one help me plz. For the last two weeks I've had this problem when ever I try to update an app via market it downloads fine then when installing it errors out and I get an "update unsuccessfull" message.

What can i do to fix this ?

Can you help me out ?

Thank you all

Sent from my HTC Frying Pan
[Wildfire General] Scratch0805:
Uninstall the app first, then redownload from the market.

Inconvenient I know but it should work, has your market updated either by you or itself before the problem began?
[Wildfire General] ukdevil:
No market is same version i hate the newer version so not updated. You know of a good data saver for the apps so o don't have to reinput all settings and what not

Sent from my HTC Frying Pan