08-09-2012 03:05 AM
2,584 ... 6768697071 ...
tools
  1. sjsharksfan's Avatar
    That did absolutely nothing for me.

    Sent from my SPH-D710 using Tapatalk 2
    Really? You still get LOS as much as you do without it?

    I can see a noticeable difference when I use it.. its supposed to help your phone stay connected to the closest tower to where you are.. I live pretty much directly in the middle of 3 towers. Without the app, I will bounce between the three towers periodically, but with the app, my phone stays connected to the one that's closest, by 30 ft..

    I guess YMMV..

    sj

    Sent with my Epic 4G Touch on CM9-8/03 @ 128 dpi using Tap@Talk Pro v2.2.4
    08-04-2012 11:00 PM
  2. anakin_sw's Avatar
    Really? You still get LOS as much as you do without it?

    I can see a noticeable difference when I use it.. its supposed to help your phone stay connected to the closest tower to where you are.. I live pretty much directly in the middle of 3 towers. Without the app, I will bounce between the three towers periodically, but with the app, my phone stays connected to the one that's closest, by 30 ft..

    I guess YMMV..

    sj

    Sent with my Epic 4G Touch on CM9-8/03 @ 128 dpi using Tap@Talk Pro v2.2.4
    I tried this app and it did nothing for me. I also have an AirRave femtocell and signal is perfect in my place and I still experience LOS.
    Downtown Taco and sjsharksfan like this.
    08-04-2012 11:04 PM
  3. dabora3003's Avatar
    To save some time, the answer to the next stupid question is to bash your face against a table until you either have the answer or the foresight to get onto a ROM that you can handle. Way too many people are being outmatched by this build and patience is required for us as a group to figure out these things. Please, if you're going to post a problem, at least list your phone's configuration: ROM build, gapps version, modem and if you used Titanium Backup. This will help in troubleshooting and for statistical aggregation.
    Agreed very much, but chill. Newbies are people too. I'm a total newbie but I can still help with testing if people are patient when I don't quite understand something. Don't make Paul come back for the umpteenth time and slap us into shape. I'd like this thread to stay open.
    Downtown Taco likes this.
    08-04-2012 11:04 PM
  4. MicrosoftBug's Avatar
    Anyone having LoS may want to take a look at this: http://forum.xda-developers.com/show....php?t=1374560

    Sent from my SPH-D710 using Xparent Red Tapatalk 2
    08-04-2012 11:48 PM
  5. anakin_sw's Avatar
    Anyone having LoS may want to take a look at this: [MOD] LoSD - LoS Repair Daemon v1.3.0 [Updated 2012-01-13] - xda-developers

    Sent from my SPH-D710 using Xparent Red Tapatalk 2
    Sadly, I tried that and didn't notice any difference. Got LOS within minutes...
    08-04-2012 11:57 PM
  6. JayWill's Avatar
    Anyone having LoS may want to take a look at this: [MOD] LoSD - LoS Repair Daemon v1.3.0 [Updated 2012-01-13] - xda-developers

    Sent from my SPH-D710 using Xparent Red Tapatalk 2
    The thing is, that is a bandaid. There was a time when LOS couldn't be fixed by anyone but Samsung, which they did in the EK02 update. Nobody could figure it out, or why it happened more frequently on kernels built from the EG30 source code. So Viperboy came up with a script that would restart the radio daemon upon a LOS event, and this guy picked the project up until LOS because a dinosaur and everyone moved on to greener pastures.

    This LOS is not happening on the stock system. It's happening on AOSP code and kernel created in the fashion of Dr. Frankenstein. The LoS Daemon is nice if you have no alternatives, but people running this ROM are testers, not end users, and end users should be sticking with known working and stable daily drivers and staying away from cutting edge software. Running a LOS script doesn't help test and fix the issue, which should be the primary goal.

    My 2 bits on the matter FWIW.

    By the way, I'll say it again ... the LOS issue (and probably the battery drain issues too) is VERY LIKELY related to the kernel. You're probably witnessing first hand why AOSP developers hate CDMA devices.
    Paul627g and Downtown Taco like this.
    08-05-2012 12:01 AM
  7. thenameisnigel's Avatar
    Kies air & Sprint TV confirmed working.


    Sent from my SPH-D710 using Tapatalk 2
    08-05-2012 12:09 AM
  8. firegoblin's Avatar
    Just installed his using the instructions in the op and now my phone can't obtain root access? Tried everything I can think of to fix it. Any ideas

    Sent from my SPH-D710 using Android Central Forums
    08-05-2012 12:09 AM
  9. thenameisnigel's Avatar
    Just installed his using the instructions in the op and now my phone can't obtain root access? Tried everything I can think of to fix it. Any ideas

    Sent from my SPH-D710 using Android Central Forums
    Flash ChainFires version of Superuser in CWM baked into the ROM.

    Read my previous post: http://forums.androidcentral.com/sho....php?p=2044207

    Sent from my SPH-D710 using Tapatalk 2
    firegoblin likes this.
    08-05-2012 12:11 AM
  10. Downtown Taco's Avatar
    I tried this app and it did nothing for me. I also have an AirRave femtocell and signal is perfect in my place and I still experience LOS.
    Ditto on the femtocell. Still getting LOS.

    Sent from my SPH-D710 using Tapatalk 2
    anakin_sw likes this.
    08-05-2012 12:15 AM
  11. firegoblin's Avatar
    Flash ChainFires version of Superuser in CWM baked into the ROM.

    Read my previous post: http://forums.androidcentral.com/sho....php?p=2044207

    Sent from my SPH-D710 using Tapatalk 2
    Worked perfect thank you

    Sent from my SPH-D710 using Android Central Forums
    oskee likes this.
    08-05-2012 12:56 AM
  12. censura_umbra's Avatar
    The thing is, that is a bandaid. There was a time when LOS couldn't be fixed by anyone but Samsung, which they did in the EK02 update. Nobody could figure it out, or why it happened more frequently on kernels built from the EG30 source code. So Viperboy came up with a script that would restart the radio daemon upon a LOS event, and this guy picked the project up until LOS because a dinosaur and everyone moved on to greener pastures.

    This LOS is not happening on the stock system. It's happening on AOSP code and kernel created in the fashion of Dr. Frankenstein. The LoS Daemon is nice if you have no alternatives, but people running this ROM are testers, not end users, and end users should be sticking with known working and stable daily drivers and staying away from cutting edge software. Running a LOS script doesn't help test and fix the issue, which should be the primary goal.

    My 2 bits on the matter FWIW.

    By the way, I'll say it again ... the LOS issue (and probably the battery drain issues too) is VERY LIKELY related to the kernel. You're probably witnessing first hand why AOSP developers hate CDMA devices.
    Did you read the thread???

    The script does many helpful things.

    A) it will monitor your Los status and fix it for you, so you hopefully won't miss much.
    B) it can auto-save logs every time this happens.

    Soooo basically testers can test it longer, AND it is easy to pull the logs
    08-05-2012 01:10 AM
  13. JayWill's Avatar
    Did you read the thread???

    The script does many helpful things.

    A) it will monitor your Los status and fix it for you, so you hopefully won't miss much.
    B) it can auto-save logs every time this happens.

    Soooo basically testers can test it longer, AND it is easy to pull the logs
    Yeah I read every post, many many months ago. I guess my point was probably not made well. I'll leave it at that. If people find value in using it when running this ROM then all the power to them.

    Sent from my SPH-D710 using Tapatalk 2
    08-05-2012 01:24 AM
  14. censura_umbra's Avatar
    Yeah I read every post, many many months ago. I guess my point was probably not made well. I'll leave it at that. If people find value in using it when running this ROM then all the power to them.

    Sent from my SPH-D710 using Tapatalk 2
    I meant, even just the OP would have told that info.

    Do I think that the mod will work? No, because it is made for GB and no one has mentioned any success with it.

    Would something designed for JB like this work? Yes, absolutely.

    -----------


    I just downloaded DKs Beta 4 (btw, 4Shared is terrible) but it was only 45,000 KB... That seems WAY too small to be a ROM, did I get a bad download?

    Okay, redownloading, it Says 150mb this time, but it is still downloading just as fast....but it seems to fully download this time
    08-05-2012 01:30 AM
  15. JayWill's Avatar
    I meant, even just the OP would have told that info.

    Do I think that the mod will work? No, because it is made for GB and no one has mentioned any success with it.

    Would something designed for JB like this work? Yes, absolutely.
    The thing is, the logs are meant to report why when a LOS event occurred, the LoSD daemon didn't catch it. It really wasn't designed to discover the reason LOS was happening in the first place. This script (and the work Viperboy did prior to it) got really good at identifying what was taking place when a LOS event occurred, but not why.
    censura_umbra likes this.
    08-05-2012 02:15 AM
  16. darkleo's Avatar
    hey,
    i don't know what's wrong, but i'm following the procedure correctly and still the installation is getting aborted. its giving an error of status 7. could anyone help me out.

    thanks in advance.

    peace.
    08-05-2012 03:02 AM
  17. sjsharksfan's Avatar
    hey,
    i don't know what's wrong, but i'm following the procedure correctly and still the installation is getting aborted. its giving an error of status 7. could anyone help me out.

    thanks in advance.

    peace.
    Make sure to use the correct recovery and maybe download the rom again.. did you verify the md5 sum?

    sj

    Sent with my Epic 4G Touch on CM9-8/04 @ 128 dpi using Tap@Talk Pro v2.2.4
    08-05-2012 03:08 AM
  18. sonic7z's Avatar
    I'm unable to download/update anything on the Play Store on Beta 4. I can DL and install apps from third party sources. Is this normal?
    08-05-2012 03:17 AM
  19. Jocelyn84's Avatar
    Make sure to use the correct recovery and maybe download the rom again.. did you verify the md5 sum?

    sj

    Sent with my Epic 4G Touch on CM9-8/04 @ 128 dpi using Tap@Talk Pro v2.2.4
    Where's the md5? I don't see one

    Sent from my Samsung Epic 4G Touch using Tapatalk
    08-05-2012 03:44 AM
  20. sjsharksfan's Avatar
    Where's the md5? I don't see one

    Sent from my Samsung Epic 4G Touch using Tapatalk
    Hmm, you're right.. I didn't even notice that.. maybe op can post it..

    I didn't flash this build yet so I haven't needed to check md5 yet,.

    sj

    Sent with my Epic 4G Touch on CM9-8/04 @ 128 dpi using Tap@Talk Pro v2.2.4
    08-05-2012 04:07 AM
  21. censura_umbra's Avatar
    Hmm, you're right.. I didn't even notice that.. maybe op can post it..

    I didn't flash this build yet so I haven't needed to check md5 yet,.

    sj

    Sent with my Epic 4G Touch on CM9-8/04 @ 128 dpi using Tap@Talk Pro v2.2.4
    check the size. the first time i downloaded it, it was 40 mb, it should be 150mb
    08-05-2012 04:09 AM
  22. darkleo's Avatar
    the size is 150 MB, i've downloaded the ROM a couple of times already, still the same. i'm using the EL29 recovery.
    08-05-2012 04:20 AM
  23. land2634's Avatar
    I meant, even just the OP would have told that info.

    Do I think that the mod will work? No, because it is made for GB and no one has mentioned any success with it.

    Would something designed for JB like this work? Yes, absolutely.
    I don't post much, but felt the need to chime in here. I think what was meant is that even if this were for JB, it wouldn't be fixing the problem. The script was never intended to fix any of it. From my understanding, and if I remember correctly from when I first started using the device almost a year ago, the script was intended to, upon detecting LOS, restart the radio on the device. It doesn't prevent such an event from happening, it simply gives a reboot/refresh when it detects an event related to LOS. This could be oversimplified, but it is my understanding from what I remember.
    08-05-2012 04:31 AM
  24. censura_umbra's Avatar
    The thing is, the logs are meant to report why when a LOS event occurred, the LoSD daemon didn't catch it. It really wasn't designed to discover the reason LOS was happening in the first place. This script (and the work Viperboy did prior to it) got really good at identifying what was taking place when a LOS event occurred, but not why.
    Ohhh okay, So what do you suggest to capture WHY in our logs?


    Also, I've been hearing good things from some people about the latest beta, so I'm going to try some testing.

    Here are my steps:

    I started on Cm9. I am Mobile Odining back to Gingerbread, stock, + Root and Mbile Odin Injected. Had Mobile Odin Wipe Data / cache / Dalvik (never done that before...So hope Mobile Odin didn't mess up. (just checked, it didn't.)

    So on boot, I am instantly connected to 4g (hmmm forgot what Touchwiz was like lol)

    I am back on EL29.
    2.3.6
    FG20
    EL29

    I am going to get a GPS lock, then bypass Sprint Proxy
    (Forgot, my phone is a refurb and can never get a GPS lock, or update PRL/Profile idk why)

    Rebooted after removed Sprint Proxy, Now to ODIN

    Flashed Stock EL26 Kernel with CWM.
    Formatted all a few times
    Installed beta 4, no Gapps
    Wiped again...
    confused why I see CM9 boot screen.......
    4.1.1
    FG20
    DK Beta 4

    I tried a few fixes that were mentioned here these are the results:

    First, no changes, just the no GAPPS:
    when I click the screen off, it flickers. No wake yet. Call works right after boot. Will wait for a while.
    Turned 4G on, called again, it froze. Rebooted, call worked, 4G on, Call worked again. Wait a few minutes. Called again about 20 mins after, still worked. Installed CPU spy, unplugged phone. Will check Deep Sleep, still no Wake locks.

    Since the first reboot. No issues. Granted, without GApps, I'm not doing much with it. I will go to bed and leave it off the charger to see what happens. Will test more tomorrow.

    okay, now it says it is going to deep sleep, then I turn the screen off an I get wake locks every 5 seconds! Pulling logs, patience.
    Still to do:

    LoS test:
    Turn off Network locations
    Don't use wifi or 4G(4g seems fine)
    Try the scripts
    Try original Gapps
    Try DK gapps/ Lowridder


    Test Deep Sleep/wake lock:
    Max Processes = 1
    Turn off notification light.
    Turn off auto sync?

    Battery Life:
    Undervolt to 800?
    08-05-2012 04:34 AM
  25. censura_umbra's Avatar
    the size is 150 MB, i've downloaded the ROM a couple of times already, still the same. i'm using the EL29 recovery.
    Use Stock EL26 CWM recovery, works fine for me
    08-05-2012 04:36 AM
2,584 ... 6768697071 ...
LINK TO POST COPIED TO CLIPBOARD