Quote:
Originally Posted by ChrisCicc
I use S2U2 2.04, works great. no battery drain (and i've used the versions that drained like crazy). That was the build he had published for about six months straight, he's got some work to do on these latest builds tho IMHO. The only problem is an occaisonal landscape glitch in 2.04, but that does not hamper functionality in a way.
|
Hmm... ok, maybe I'll give S2U2 another shot. I remember someone posting a set of "ideal" settings for S2U2 a while back, that conserved power and whatnot.
Quote:
For your others:
activesync opening randomly
This happens when there are errors on the sync. I've seen it, then I've seen it go away when the errors clear out. Make sure you aren't trying to sync to things that your server can't handle (like text messages and google). Also make sure you aren't in an area that drops signal frequently.
|
I haven't seen any errors reported. I'm just doing a standard server sync. But I'll check to make sure I'm not dropping signal.
Quote:
soft keys getting renamed but not remapped
have not seen this, might be a conflict with third-party mods/apps you are using
|
I haven't installed any 3rd party apps--I run my ROMs very clean. A soft reset fixed this issue, but it was driving me bonkers for a while. I wonder if it'll start happening again.
Quote:
and locking/unlocking problems while using 6.5's locking capabilities
it sucks, namely because of the delay in the lock screen showing when the phone is turned on, and the manila pages working on occasion when the phone should be locked. A_C had both these problems in early versions of S2U2, he figured them out, shame MS couldn't LOL
|
Yeah, seriously. I'd much rather use OS functionality than an additional application, but it looks like MS may have dropped the ball.
cflynt: I dunno if you're referring to me, but I've already flashed this ROM and am having these issues. I'm trying to figure out if they're unique to me, or if it's a result of Manila 2.5, which is still beta (more or less) and as such could be causing bugs. The former would mean I may need to hard reset/reflash; the latter means I need to accept that no M2.5 ROM is going to satisfy my needs for stability. I love M2.5's contact management, but I put stability above everything else: generally a persistent glitch or a bug will be enough to make me abandon a particular ROM. (You may argue that this means I shouldn't flash at all, but many custom ROMs--MM, MM+Silence, and indagroove--offer ROMs that are frankly more stable than stock.)