{ "id": "120476", "key": "TIMOB-15437", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": { "id": "11", "description": "Is not a bug in our product", "name": "Not Our Bug" }, "resolutiondate": "2013-10-09T22:00:33.000+0000", "created": "2013-09-26T07:54:03.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "android" ], "versions": [], "issuelinks": [], "assignee": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-29T20:59:49.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "I'm testing a simple titanium app on an android avd obtained from a Xperia Z device definition (similar to samsung s4).\r\n\r\nThe app works but I got a wrong value for Titanium.Platform.displayCaps.dpi\r\n\r\nThe app report a wrong value for Titanium.Platform.displayCaps.dpi = 320 (avd has a dpi of 480).\r\n\r\nIf can help finding a solution the Ti.Platform.displayCaps.platformWidth correctly report 1080.\r\n\r\nAttached AVD config", "attachment": [ { "id": "42779", "filename": "Schermata 2013-09-25 alle 10.22.40.png", "author": { "name": "ftaioli", "key": "ftaioli", "displayName": "Fabiano Taioli (vista)", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-09-26T07:54:03.000+0000", "size": 78581, "mimeType": "image/png" } ], "flagged": false, "summary": "Android: Titanium.Platform.displayCaps.dpi incorrect for Samsung S4 / Sony Experia Z emulator", "creator": { "name": "ftaioli", "key": "ftaioli", "displayName": "Fabiano Taioli (vista)", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "ftaioli", "key": "ftaioli", "displayName": "Fabiano Taioli (vista)", "active": true, "timeZone": "America/Los_Angeles" }, "environment": "osx", "comment": { "comments": [ { "id": "273757", "author": { "name": "jbuckley", "key": "jbuckley", "displayName": "Jamie Buckley", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~morahman] He isn't using the actual device, he is using an AVD simulator based on the device, you should be able to create a custom simulator based on this to test.", "updateAuthor": { "name": "jbuckley", "key": "jbuckley", "displayName": "Jamie Buckley", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-10-03T17:50:27.000+0000", "updated": "2013-10-03T17:50:27.000+0000" }, { "id": "274262", "author": { "name": "tlsg", "key": "tlsg", "displayName": "Tommy Leung", "active": true, "timeZone": "America/New_York" }, "body": "This is a problem on the emulators only. It seems to work fine on the actual device.\r\nGoogling indicates this is a problem on native applications as well and is a problem with the emulator.", "updateAuthor": { "name": "tlsg", "key": "tlsg", "displayName": "Tommy Leung", "active": true, "timeZone": "America/New_York" }, "created": "2013-10-08T21:46:24.000+0000", "updated": "2013-10-09T01:07:50.000+0000" }, { "id": "274348", "author": { "name": "ftaioli", "key": "ftaioli", "displayName": "Fabiano Taioli (vista)", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I have no the real device to test but may be really an emulator issue.\r\n\r\nI was able to force the right DPI values on emulator with this commands:\r\n\r\n> adb shell setprop qemu.sf.lcd_density 480\r\n> adb shell stop\r\n> adb shell start", "updateAuthor": { "name": "ftaioli", "key": "ftaioli", "displayName": "Fabiano Taioli (vista)", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-10-09T11:09:03.000+0000", "updated": "2013-10-09T11:09:03.000+0000" }, { "id": "274358", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "From the comments, it _sounds_ as if this is an emulator bug, not an issue with the Titanium platform. [~tlsg] do you have any links?\n\nOtherwise, can you please provide the following:\n\n# Steps you used to create the emulator.\n# Sample app you used to test the theory\n# Actual vs. expected results (I'm assuming alert of Titanium.Platform.displayCaps.dpi displays 320,nut browsing the info of the AVD displays 480)", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-10-09T13:05:14.000+0000", "updated": "2013-10-09T13:05:14.000+0000" }, { "id": "274489", "author": { "name": "tlsg", "key": "tlsg", "displayName": "Tommy Leung", "active": true, "timeZone": "America/New_York" }, "body": "This is SO for the commands Fabino found: http://stackoverflow.com/questions/12919341/any-suggestions-on-getting-xxhdpi-working-in-the-android-emulator\r\n\r\nThis is one of the many places developers were complaining about the wrong dpi: http://www.basic4ppc.com/android/forum/threads/density-for-1080x1920-is-not-correct.29686/\r\n\r\nAnd looking at the code for Ti, the reported dpi is indeed just calling the same underlying android function \"context.getResources().getDisplayMetrics().density\" so it would make sense that this is an emulator problem.", "updateAuthor": { "name": "tlsg", "key": "tlsg", "displayName": "Tommy Leung", "active": true, "timeZone": "America/New_York" }, "created": "2013-10-09T21:56:45.000+0000", "updated": "2013-10-09T21:56:45.000+0000" }, { "id": "274490", "author": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Based on comments, this appears to not be our bug. Resolving as such.", "updateAuthor": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-10-09T22:00:33.000+0000", "updated": "2013-10-09T22:00:33.000+0000" }, { "id": "416248", "author": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "body": "Closing ticket as it has been established that the issue is not our bug.", "updateAuthor": { "name": "lmorris", "key": "lmorris", "displayName": "Lee Morris", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2017-03-29T20:59:49.000+0000", "updated": "2017-03-29T20:59:49.000+0000" } ], "maxResults": 8, "total": 8, "startAt": 0 } } }