pretty sure 1.6 donut made it possible for apps to work on any screen size. but, idk if that applys in this situation. Also i dont think google is that dumb to release a a major phone with no compatible apps
Yeah, and I doubt it will be very hard (depends on the app and how its layed out, really), but it's definitely something to take into consideration when you realize this is the first (and only, so far) non-HVGA Android device.
The 1.6 docs talk about a compatibility mode for apps hard coded to the old (medium) resolution. Some API changes in 1.6 were specifically for smaller resolution support as well as larger (netbook) support. As long as the apps don't use any unsupported library calls I believe they should "just work". They may not entirely full up the screen with content but they should mostly work.
Originally Posted by jtc082488
pretty sure 1.6 donut made it possible for apps to work on any screen size. but, idk if that applys in this situation. Also i dont think google is that dumb to release a a major phone with no compatible apps
The Android 1.6 SDK includes these emulator skins:
* QVGA (240x320, low density, small screen)
* HVGA (320x480, medium density, normal screen)
* WVGA800 (480x800, high density, normal screen)
* WVGA854 (480x854 high density, normal screen)
The leaked specs for the STD list the resolution as 854x480. The 1.6 SDK and emulator will already support the screen resolution of the STD.
Originally Posted by space1701
The 1.6 docs talk about a compatibility mode for apps hard coded to the old (medium) resolution. Some API changes in 1.6 were specifically for smaller resolution support as well as larger (netbook) support. As long as the apps don't use any unsupported library calls I believe they should "just work". They may not entirely full up the screen with content but they should mostly work.
The leaked specs for the STD list the resolution as 854x480. The 1.6 SDK and emulator will already support the screen resolution of the STD.
That's good to hear. Hopefully dev's realize this phone is coming out, so they can prepare their apps. All the secrecy could harm app development. Though realistically I doubt that'll be a problem.
:groan: Android is resolution independent. VERY VERY VERY few apps will simply "not work" due to a different resolution. The existing Android devices out already have different resolutions.
API changes are made to be minimal to avoid incompatibilities. Android 2.0 will run 1.6 apps just like Vista runs XP apps.
:groan: Android is resolution independent. VERY VERY VERY few apps will simply "not work" due to a different resolution. The existing Android devices out already have different resolutions.
API changes are made to be minimal to avoid incompatibilities. Android 2.0 will run 1.6 apps just like Vista runs XP apps.
Well, I'm not too familiar with the way Android handles different resolutions, but I'd be surprised if it can natively stretch apps to fit correctly. But hey, who knows. And AFAIK all released Android devices use HVGA. The HTC Tattoo is QVGA, but that isn't out yet.
i think if there isnt an official announcement THIS WEEK then our hopes of October 30th are simply not true.
hurry up and announce the phone already! and give us some official info!!
I disagree, as will many of the people here. But this has already been discussed so so so many times at this point that it's not worth bringing up anymore. Don't take that the wrong way, I'm just trying to avoid the catastrophe that was the last STD pre-release thread.
A slice of bread will always land peanut butter side down. If, by chance, you put peanut butter on both sides of the slice, it will float forever.
Well, I'm not too familiar with the way Android handles different resolutions, but I'd be surprised if it can natively stretch apps to fit correctly. But hey, who knows. And AFAIK all released Android devices use HVGA. The HTC Tattoo is QVGA, but that isn't out yet.
Why would you be surprised if it can stretch apps? I can resize firefox to any resolution... The app is drawn on screen using layouts, just like with any desktop application. The OS handles the calls to drawLayout() to handle different resolutions. It's not like all Android applications use absolute layouts. And if app developers do... they deserve to have their applications not work.
Think about how a program would have to be written and then you'll realize that res independence is fairly obvious in most all cases.
Motorola A855 Sholes/Tao/Droid Pre-Release Thread 2 (Off topic Posts=BAN No Warnings)
Originally Posted by iamrobk
Bookmarks