[Non-Touchscreen Windows Mobile Other] TimelesslyPrecise:
Okay,

You know what is weird gahbmwm5? Is that mostly the problem, for me the phone keyboard locking itself up isn’t during heavy use… or while in the middle of using it.. (Ok maybe once, that I can think of)

Don’t go beating up your phone or anything! :D If you like the SAC4 don’t look for the issues you don’t often have! :D maybe you use your phone more than I, keeping it attent and active.

In most cases, if I am trying to receive a call… If the phone rings, and I don’t get to it within three rings or so, the keyboard will lock up and lock you out. In this case, I have been next to the phone for three hours, and it hasn’t rung; and now someone is calling. Usually I am reading something, too tuned in to reach and get the phone immediately; if I stall out for a minute it might lock up. (Though I can’t say that completely, because sometimes when I rush to the phone as quick as I can, it still is already locked..) Stumper.. Either way, it’s hard to reproduce the error. Happens when I’m least concerned, and always when it’s important. Lol

Today, I woke up to my phone on the charger, having a solid shiny Green light. Couldn’t push a button. I hadn’t tried to call it to test, but looking at my Google Voice account; I had missed about 3 texts, and 2 phone calls…. None of which had even shown up on my phone. (And looking at the logs now, still aren’t there.)

This tells me we may have a few other variables… (1. possibly the phone doesn’t manage power operations very well. 2. Maybe the phone did the keyboard lock up, and after so long it jut froze the whole system.) (In that case, was it before the phone was done charging completely, or was it after the keyboard locked up? Was it the charging, was it the keyboard?)

(I have two different spaces I charge the phone, and it has locked up on both of them, and without being on either.)

So anyway,

I have a very strange suspicion about a few things..

First, of a more universal concern…. The Radio version of the phone.. (i617UCHJ1 is what I have)

I believe there may be something in the radio version, which isn’t handled properly with the Wm6.5 pda portion of rom software..?? (maybe)

Another though; was there something straight up added to the stock ATT 6.1 rom, to assist with the kernel processes? something not standard in our current rom we are just overlooking.. an intermediate dll, exe?

Guys, What version of Radio are you using? (in Settings\About\ ”Radio Version”)

Onto MY next steps,

I am about to throw the ATT 6.1 Rom back on, and do a dump..

Dermann.. I would like to ask, in regards to the dump, I intend to use XDA-Developer tools to dump an .nbf file. Do you know of any other program I should be using to dump a rom?

I did a dump of SAC4 last night, but I came up with an .nbf of about 30mb’s??? Now, I don’t know, but that seems a bit small. I know it is just the phone portion being dumped, but still that seems a bit small?

Okay, on the way to replace. I will leave it on here today and tomorrow, see how and if I can get it to freeze up or lock up on me.. I don’t recall having the issue with 6.1, so I will see what I can do..

(Dermm, I’ll get an export of the 6.1 Reg Hives, stock)

Is there anything else I should grab from it while I have it loaded… any specific .dll’s, or .xml.

(I noticed the mort’s you have, looks very clean. i kind of think there should be a way for us to edit some of those values and cook them into the rom somehow..)

One thing I did notice, and I personally thought concerning… the HTC-Reset mod is added.

I tried this with my 6.1, and I didn’t like its behavior. Though, it works and is effective… When you actually click the Reboot option, notice how ‘Hard’ it shuts down. It’s almost, to me, like holding in the power button for 4 seconds on a PC with 6 hard drives in a RAID-0… in most cases, not too safe.. :P

I don’t know why, but on my 6.1, I had uninstalled the HTC-Reboot patch dll and exe. To me, it seems like just a bit safer to just do a Power Off, and let windows shut everything down the way it wants. This may be a second suspicion of mine, but since it is not an active process, only when called, it couldn’t have anything to do with the keyboard acting up.

Okay, to Recap.

•	What are each of our Radio Versions’?

•	I’m going to load up 6.1, grab a dump, and reg hives.. maybe there is something I can compare between the two..

•	Derm, we’ll wait and see if py8 says anything about the keyboard issue…

(if I recall correctly, I used a chinese rom before all this, and I don’t recall any keyboard lockups…) though it was really freaky with the language of things.

Well, chat with you all soon. Off to commit 6.1