So I'm fairly certain that the "protected" attribute that a developer can include in a compiled APK is causing the problem I have been witnessing on my Velocity 1.1 Ally where my Online Banking app does not show up in the Market, and is shows as "Incompatible" from the market website where it is clearly approved for Android 2.1 and 2.2 APIs. As I have been researching this a fairly common problem with custom ROMs on ANY Android phone, there is a fingerprint that each ROM uses to access that market that must be approved by Google to be able to access / install the above mentioned "protected" apps. The fix that I've seen is tricking the market into thinking that you have an approved ROM. This is done by editing the line: "ro.build.fingerprint=**ROM specific text here**" from the file: "/system/build.prop" to match from a known correctly working ROM. I know I didn't have this issue on Velocity 1.0 so could I have a Velocity 1.0 (ZVD/ZVE should work also as they are obviously approved ROMs) user post or PM this line from their build.prop file to see this is really is the case? Probably have to have root to access this file if I had to guess.