View Single Post
  #3108 (permalink)  
Old 04-22-2010, 02:09 AM
IsLNdbOi's Avatar
IsLNdbOi
Regular 'Geeker
Offline
 
Join Date: Oct 2006
Posts: 493
Reputation: 105
IsLNdbOi is keeping up the good workIsLNdbOi is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: ║MightyROM.com║ ║Windows Phone®║ ║Sense UI 2.5║

Quote:
Originally Posted by mrmediaguy View Post
I was actually really optimistic about that fix since I've been running it for a few days with no issues -- but *just now* I had my first SOD on the new HTCServices cab. Sadness. (I guess "sleep of death" is a bit of a misnomer because in this case I just left things alone for a few minutes and it turned on just fine when I picked it up again.) Not saying the Ziggy fix doesn't work -- but there might be more than one cause of the screen not turning on.

Tangentially, has anyone tried the new Mr. X ROM that allegedly fixes memory leak (or perhaps better said, poor memory allocation) issues? I'm not running anything on top of the current MightyROM except for Cookie's Home Tab, but I notice my memory dwindling throughout the day until I'm at about 85% to 89% used. Wondering if anyone has tried Mr. X and seen different behavior?
I thought the HTC services cab fixed the SOD problem since I hadn't experienced it for at least a week, but I did experience it again today.


Quote:
Originally Posted by IsLNdbOi View Post
I've been using the latest version of this ROM since Mike made it available on his site.

I've been experiencing four problems.

The first one is that sometimes I can't get the screen to turn on (either by pressing the power button or sliding the keyboard open). After a couple of minutes it finally does come on.

The second one is that alarms keep going off on their set time even though I've turned them off.

The third one is that the clock on the home screen freezes. If I haven't turned the screen on in a measurable amount of time then turn it on, the clock's time is what it was before I turned the screen off then it quickly catches up. This is something that happened all the time on my original Touch / Vogue.

The fourth one is that bluetooth devices I've paired and set to automatically connect sometimes won't connect unless I first disable bluetooth, soft reset then enable bluetooth again.

These paired devices are set to "Connections Authorized" in the bluetooth settings (tab that shows paired devices, tap and hold device then tap on "Properties").
I still haven't found solutions to these other problems, though others have said that number three is unavoidable. I experienced this problem with the original Sprint Touch / Vogue as well, but never did with the first Touch Pro..

Last edited by IsLNdbOi; 04-22-2010 at 02:12 AM.