System apps behave differently when they are compiled with Eclipse and when they are compied as part of the AOSP

33 views
Skip to first unread message

Android007

unread,
May 22, 2013, 8:30:00 AM5/22/13
to android-...@googlegroups.com
Hi,
I don't understand why, but when I compile my app as part of the AOSP (in /packages/apps ) and run it on the compiled emulator, it uses the mdpi folders when searching for resources - and it makes no difference whether the emulator has its density at 320.

However when I compile it  with Eclipse, I get the right behaviour (resources are taken on the same emulator from the xhdpi folder).

What causes this behaviour?

Thanks
Reply all
Reply to author
Forward
0 new messages