Talk:Patch webOS Roam Control

From WebOS Internals

Revision as of 17:22, 16 October 2009 by T3rmin (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Would it be possible to add a "Roam Only" function to the menu bar along with wi-fi, bluetooth, etc? As it is now, it's somewhat cumbersome to turn on.

Any headway into with 1.2? With this feature not working, I am back to being tethered to the wall in my low sprint service area....


We've been having reception issues with the Pres at work. The roam-only patch seems to pretty much resolve things. But it occurred to me that's kind of a heavy-handed approach.

Isn't the real problem that the Pre's roaming algorithm gives far too much weight to Sprint towers? I mean it *will* roam with the default settings, but only as a *very* *last* *resort*. It seems like in some cases, roam-only could actually impair your reception (if you're right on top of a Sprint tower). It's not that we don't want to use Sprint towers -- there just aren't enough of them and we want the best signal possible.

Also, as I understand, it costs Sprint more when we're on other company's towers. I'm sympathetic to that, especially because more cost to them equals higher prices for us in the long run.

So how 'bout it, has anyone poking through the code seen anything that might indicate we can alter the phone's affinity for Sprint towers versus non-Sprint towers? Then the phone could pick the tower with the best signal indiscriminately. --T3rmin 17:22, 16 October 2009 (UTC)

Personal tools
Google AdSense