Adding res-notlong-port-xhdpi" and other related xhdpi folders to android -> images folder does not work as the image is not taken from those folders.
As per the Android Developer website, I tried to create a 640 x 960 resolution avd to test this issue for xhdpi.
To test:
1. Create an AVD for 640 x 960 resolution for titanium to run on. (This link explains the resolution needed for different densities:
http://developer.android.com/guide/practices/screens_support.html)
*You might have to edit the already created AVD to appropriate resolution since Titanium creates a new AVD by itself (unless there is another way)*
2. Create any default app with res-long-port-xhdpi, res-long-land-xhdpi, res-notlong-port-xhdpi, res-notlong-land-xhdpi folders under android and add differen images to these folder to differentiate easily. (See Screenshot for the folder structure)
3. Run the app with the desired AVD. The starting screen image that appears is not of xhdpi but of mdpi folder.
Please clarify about this issue.
*Note: You would also need to set the tool-api-level and some other properties as below since the xhdpi has been added to android after api level 8.*
{noformat}
http://schemas.android.com/apk/res/android">
8
{noformat}
Escalating because two of our consulting engagements are asking for this.
The "xhdpi" qualifier is actuallly controlled by the screen's density, not it's size (ex: 640x960). You can configure the density of the emulator by editing the AVD. Under the "Hardware:" options change "Abstracted LCD density" to 320. This should cause Android to select the xhdpi images instead.
A good reference on the various qualifiers: http://developer.android.com/guide/practices/screens_support.html#qualifiers
Tested and verified this. The xhdpi folder does get detected on changing the dpi to 320.
Re-opening to edit...
Closing ticket as invalid with reference to the previous comments.