This past March, i noticed that if an app supports the softkeys, the grinder tends to make it go wacko. Specifically, I had made AVK_SOFT1 act as CLR and AVK_SOFT2 act as SELECT, and when i'd run the Grinder on the app in the emulator and the handset simultaneously, it'd work fine in the emulator but it'd exit the app on the handset and party all over the handset menus.

After a little investigation, i realized that the emulator was receiving AVK_LEFT and AVK_RIGHT, but the handset was receiving AVK_SOFT1 and AVK_SOFT2. I thought it might be a bug in the VX4400, but if i didn't use the Grinder then it wasn't a problem. (Mashing left/right buttons on the handset doesn't do it.)

So then, I suspected it was the Grinder but didn't have time to investigate further, and just removed softkey support from the app. (I mentioned this in
thread 1410.) Anyway, recently i knew another programmer who was writing some menuing code that supported the softkeys, so i asked him to check it out and sure enough the same problem happened to him with his code.

Has anyone else run into this and come up with a solution? I'm sure that NSTL would not fail the app if this issue were properly documented since the app by itself works correctly on the handset. However, it'd be nice if the Grinder worked correctly.

Last time I ran the Grinder on an app that had AVK_SOFT1=CLR, the phone exited the app and sent a garbled SMS to Aaron B. at Qualcomm. So Aaron, if you read this, that was the Grinder, not me. :p