Rom Kitchen Issues
 

I figured we needed a topic for this by now, but i do have one particular issue i'm curious about at the moment. I used the kitchen to build the ROM and now when i have the phone off the hard keys all wake it up. Is this a registry setting that is missing or something? I don't want to find out i've called people and left them a 10 minute message while i was singing in my car or something =)

What happens when you go to Settings...Buttons...Lock (tab at the very bottom) and select "When device is off: Lock all buttons except power button"

I just noticed this was not selected by default on Colonel's custom ROM and I"m wondering if it has something do to with people's battery drain issues.

Aieee! Crapola! That's not set in the Hemli 3.3 Rom either - completely forgot about that setting - my phone's been on in the holster way more then normal - THANKS!

Are you guys sure that the stock Sprint CE ROM has that setting pre-set? I think it's actually a cab in the extrom that does that (I don't have the stock extrom handy to check but I seem to remember a cab file that did nothing but set that particular reg entry). I agree, it's a crucial setting, especially once you've gotten used to it as the default behavior!

There is a cab in the ExtRom called buttonlock, but I ran the ExtRom after I updated my latest rom and when haus brought this up I checked and it was not selected. It is, however, in my newest rom. :wink:

Excellent, that fixed my issue and probably helped a lot of others. Thanks haus!

Hmmm... that's odd. OK I'm still on AKU2.2 so maybe someone can double-check that this is still the correct registry value to modify the button lock. I just opened up the buttonlock cab and this is the only thing it adds to the registry:

[HKEY_LOCAL_MACHINE\HARDWARE\OEM\KEYBD]
"KeyLock"=dword:00000001

It does it via xml, so if the registry value itself hasn't changed in 3.x I wonder if for some reason the xml file isn't being parsed correctly when installing that cab.

Can someone running 3.3 test this? Look in the registry for that value, change it to 0 and then look in the buttons applet to see if it's been changed to "Do not lock buttons" (might require a soft reset first).

If the buttons applet doesn't change then there are two possible reasons. Either:

1. The value and/or key to control this setting is different
or
2. The setting isn't controlled by the registry anymore.

You could check #1 by dumping the registry then changing the setting in the buttons applet and then dumping again and doing a diff on the files.

Hope it's not #2, as that would be a regression back to the way WM 2003SE did it (I spent hours looking for this setting in the registry on my PPC6600 and discovered it didn't exist. It must have been set inside the button driver or something).

OK well hopefully it's just something easy. :)

Yes it still contols it. dword to 1 for on.

Did you view this with Cab Manager? I just opened up buttonlock.sa.cab and it only shows a version registry entry. It adds 5 files and has a setup dll though. Maybe that is why it wasn't turning on for me.

I tried installing the win phone profile program and it seems to have messed up my bluetooth. I uninstalled it, but I am still having a problem. My bluelight is blinking as if bluetooth is on, even though the comm manager shows blue tooth off. The comm manager seems to be having problems turniing bluetooth on and off. Anybody have any ideas how to fix this short of a hard reset? I have hardreset 7 times today playing with cooked roms, and don't feel like suffering through another setup.

Thanks.

Yeah, HTC is weird with their cab files. There are actually a whole bunch of ways to add registry entries with a cab file and HTC usually uses either the platformxxx.reg file or the CM_Entries.xml file (I don't think they've ever used both in one cab... you can look at the file sizes to see which one has "stuff" in it... the other one will just be a few bytes in size).

So using WinCE Cab Manager, just look at the "Files" section. You can extract them and then view them, or save yourself a step by right clicking on whichever file and choosing view (and then choose to view with notepad) and you will see the structure. The platformxxx.reg files are naturally easier to parse, but it's still fairly easy to understand the xml file as well.

Hope that helps.