Quote:
Originally Posted by klurf8881
theres a RUMOR this week, but i doubt that. But i also wouldnt guess too long. It could, as mentioned before, be one simple little coding error they can fix easily. One single character or bit off could cause huge errors. No one knows right now really.
im current running n2o's 2.16 rom and 1.40 radio and have no DSOD/freezing issues at all. So far my interpretation of the error of freezing going from evdo to 1x and back or into roaming is the 1.47 radio's fault. Ive had no problems with 1.40 (ive tested it in low signal areas and manually changed in settings to roam back and forth and no freezes). Im not a huge bluetooth user but i havent noticed any disconnects, but i also never had problems with bluetooth in the original ROM so maybe i just got lucky. I did notice the dpad issue once but a few click of the pad unlocked it- it wasn't very serious. The new ROM definitely seems to runs quicker and cure RAM issues slightly- it has its benefits.
|
I also am running the 2.16 ROM with the 1.40 radio, and I haven't locked up once. I've not yet seen the dpad issue. In about two days time I've had one disconnect of my headset from the Mogul. It was while the Mogul was idle and unused this morning. It was easily remedied by turning BT off then on from the Mogul. That is a whole lot better than things used to be. I also think the device is a little snappier with the new ROM. However, last night while using Opera Mobile with only one extra tab opened, I got some memory errors stating I needed to close down some apps. The list showed several phone instances open, along with a messaging instance, activesync, and of course Opera. However, when I went into the settings/memory to close apps, only Opera and Activesync showed up in the list. This happened a couple of different times to me while browsing. Could this be another bug?