Re: *Updated Oct 10th* NFSFAN's Custom WM6.5 ROMs
So I think I'm about to flash back to stock to test a few things out, then decide whether to call this a phone related problem. I'm still seeing some things that I'm pretty sure aren't ROM related (though not positive), but figured I'd throw one more post here just to see if anyone else has seeing anything like it.
The biggest one now is keyboard failure. It's still somewhat intermittent, and I've never been able to isolate it to any app or tweak. At first I thought it was the classic word completion, but I haven't installed that since my last flash, and it's again. Thought it might be S2U2, but doesn't seem to be. Basically, when I open the keyboard, the light comes on, screen rotates, but no response from keys. After the 10 second timeout, the backlight goes out and won't respond to any keypresses either. In the past couple of weeks, soft resetting, or popping the battery for a few usually fixed it. However, it's been dead for 24+ hours now despite reboots, and a power down (for flight home). I'm rather hoping it will go non-responsive after going back to stock so I can take it in.
So I think I'm about to flash back to stock to test a few things out, then decide whether to call this a phone related problem. I'm still seeing some things that I'm pretty sure aren't ROM related (though not positive), but figured I'd throw one more post here just to see if anyone else has seeing anything like it.
The biggest one now is keyboard failure. It's still somewhat intermittent, and I've never been able to isolate it to any app or tweak. At first I thought it was the classic word completion, but I haven't installed that since my last flash, and it's again. Thought it might be S2U2, but doesn't seem to be. Basically, when I open the keyboard, the light comes on, screen rotates, but no response from keys. After the 10 second timeout, the backlight goes out and won't respond to any keypresses either. In the past couple of weeks, soft resetting, or popping the battery for a few usually fixed it. However, it's been dead for 24+ hours now despite reboots, and a power down (for flight home). I'm rather hoping it will go non-responsive after going back to stock so I can take it in.