Well, the odd thing is that I've only ever seen this issue on CyanogenMod. It works fine on stock.
Sigh, how would I even contact Google anyway?
Also, I don't see what you mean about the ALT Lock being part of the Blur framework... in ClockworkModRecovery, if I go to Keytest, it shows as "Key: 125", it's obviously picked up just like any other key on the device.
Last edited by drfsupercenter; 09-15-2011 at 07:42 PM.
There is no way to map a function to that key in AOSP. I don't know the details, I'm not a developer, but the devs told me that the blur framework has to be used to map the ALT lock key. If you want more details, ask Revnumbers or one of the other devs. The ALT lock not working isn't a big deal anyways, because hitting ALT twice does the same thing as the ALT lock. (Forgot to mention this before)
As far as how to contact Google, maybe start here:
(I just did a Google search for android support)
I had this exact same issue when i first flashed cyanogen. I was obviously frustrated because it takes a few minutes to go from Liberty .9 on the Monster kernal to froyo (bootlooped after sbfin) then install the OTA and finally install cyanogen. Because of this i decided to search for a few days for a remedy before sbfin yet again and flashing another rom (steel looks intriguing) so all my efforts weren't wasted. However this morning ( approximately 36-48 hours after flashing c7), without me having to do anything, when i went into market to try again everything downloaded without a problem. I am sorry i cannot be of more help ( would love to give back to the community which has been so kind to me), but i figured the least i could do is share my story. Best of luck to you and hopefully you find a solution or luck prevails as in my case.