I've definitely seen this issue on android devices in the past, but I also assume it may no longer be relevant in recent years. We had an app that classified itself as either phone or tablet based on the 7 inch threshold, with different layouts etc, but calculating that from the flash based api was not correct for all devices about 3-4 years ago (even allowing a calculation range for variation :6.9 inches etc)
IIRC this definitely occurred on a 7 inch amazon Kindle device at one point, I can't remember specifics about any others, it was quite some time ago. At the time I made a homemade ANE to deal with it, and it is still in current use in recent builds of the same app. On Mon, Mar 6, 2017 at 8:14 AM, bilbosax <[email protected]> wrote: > Thanks Josh. I have been searching posts and blog articles about the > unreliability of Capabilities.screenDPI, and I realized they were written > way back in 2011. Since I am not finding an ANE that was developed for > this > purpose, I have to assume it is because there is no need for one at this > point. I only have a Galaxy Tab, and iPad, and an iPhone to test with for > my app, so I am grateful for the feedback from someone who has been doing > this for years. It looks like Capabilities is my best option. Let me know > if anyone else has differing opinions than this. > > > > -- > View this message in context: http://apache-flex-users. > 2333346.n4.nabble.com/Screen-DPI-ANE-tp14761p14766.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. >
