|
||||
One week later, my Mogul is still working fine running 2.16 ROM using Effcomm instead of Comm Manager. Alarms, d-pad, Bluetooth, everything working properly with this solution. Still have occasional low-memory sluggishness, but if I just remember to soft-reset it at night when putting it on cradle, that seems to usually take care of free RAM through the next day. And the occasional Oxios bitch-slap helps a lot and is no real inconvenience at all.
Seriously, this really seems to have "cured" my Mogul. I was unable to use the 2.16 ROM until I tried this. Just pretend the Comm Manager doesn't exist. Your results may vary, but life is looking pretty rosy in this little corner of Moguldom. Last edited by veblen64; 11-19-2007 at 03:01 AM. |
|
||||
Ok. I think I have the down and dirty. I traveled 10 hours over the weekend through all kinds of roaming, no signal, negotiated towers, etc (went to watch FSU beat Maryland - GO NOLES! - ). What I found with all my playing around is that the thing that makes the most difference is keeping the phone on the Sprint network and with a solid signal. This testing was extremely extensive and I am quite sure that this is the biggest factor. I used EFFComm most of the time and still had challenges. I did, however, seem to have more difficulty when I used Comm Manager. I was using bluetooth for tethering, GPS, and audio using a Plantronics headset. I, really, ran the thing through the ringer and I think the bottom line is to tread water until the new ROM comes out.
matt
__________________
........ and the moral of the story is: "you can't have a drink on the house"
|
|
||||
Update:
I took my Mogul on a long trip out of town, and was in and out of Spring coverage, and finally did experience a lot of problems with system lockups and d-pad lockups and Bluetooth funkiness. When I stay in town, the Mogul is pretty reliable with this configuration, but I need more than that from a PPC. |
|
||||
Quote:
|
|
|
|