It's pretty simple:
- there is no guarantee that a phone that supports "armeabi" will support the ARMv6 instruction extensions,
the baseline defined in docs/CPU-ARCH-ABIS.TXT
- Market and the Package Manager will filter applications based on the ABI they support. i.e. an application
that only contains "armeabi-v7a" shared library will not be listed by Market on "armeabi" devices. Also,
you won't be able to install such an application (even with 'adb install <file>').
- the difference between armv5te and armv6 are not sufficient to justify a new officially-supported ABI
- if you want to use these, nevertheless, you should target "armeabi", then perform runtime feature
detection to ensure that the device your program runs on supports them, otherwise provide alternative
paths for the devices that don't, even if it means slower performance.
The same is true for NEON instruction support with "armeabi-v7a" (some ARMv7-based Android devices
do not / will not support NEON at all, so make sure your app works without them).
Hope this helps.