Quote:
Originally Posted by drellisdee
Stock it was manila/sense 2.0 and the clock didn't behave like that. It does on sense 2.5. Many things are different from stock. Its a microsoft beta 6.5.5 build that you will never see on a stock VZW release with many newer things from other devices. Sense 2.5 takes alot more resources to run that stock sense 2.0 did too.
|
Thanks for this insight. I imagine my issues may be with Sense 2.5 then. The CAB posted earlier eliminated the constant clock update behavior thankfully. THAT was a HUGE annoyance. Why would anyone enjoy that??
Is sense 2.5 required for this microsoft beta 6.5.5?