Android :: Application Widget Sizes For WVGA And FWVGA
Oct 31, 2009What are the 4x1 app widget sizes for WVGA and FWVGA in both portrait and landscape?
View 9 RepliesWhat are the 4x1 app widget sizes for WVGA and FWVGA in both portrait and landscape?
View 9 RepliesThis seems like a simple problem to me, but I can't figure it out. I have a fullscreen layout that displays differently if the screen is taller (854 instead of 800 pixels). I've tried putting the xml into layout-notlong-hdpiand layout-long-dpi respectively, but both my WVGA and FWVGA emulators go for the "long" version (as described in the doc).
Is there any way to distinguish between the two besides using the deprecated -800x480/-854x480 qualifiers?
I want to create an app widget that could take up a different number of "cells" on the home screen, but I don't think that the app widget framework easily supports this. I know that an app widget can have a configuration screen, and I'd like the user to be able select a sort of small, medium, or large size for the widget as part of my configuration activity. Unfortunately, I don't think that this is possible, correct? Based on the minWidth and minHeight properties, the Launcher app will assign a number of cells that I can't configure at run time.
For instance, if I want a weather widget that has a current, hourly and weekly format that take up 1, 2, and 4 cells respectively, I can't do this at run time. Instead, I believe my only option is to export 3 different widgets and have them all listed in the widget picker dialog as something like "Weather - current conditions", "Weather - hourly forcast", and "Weather - week long forcast".
I have been able to scale-up my application in WVGA skins pretty easily for my app.But in WVGA mode the widget seem to be not working as desired.Sometimes the widget just gives the message "No more room in the Home Screen" even though there is space.Some times it takes up the whole screen without considering the size mentioned in the configuration files.And even strangely sometimes it hust gives me the desired behaviour.Are there are any know issues for the WVGA mode as far as widgets are concerned.
View 2 Replies View RelatedWhat I'm trying to do is have a clock widget of different sizes (i.e. 2x2, 3x3, 4x4 etc) in one apk and a configuration activity to be able to select which size to add. From what I've learned from documentation:
Widget size is specified in <appwidget-provider> tag in respective xml file
Also in that file I set up the configuration activity for that provider
So it seems that size is a property of AppWidgetProvider and I'll need to somehow create another provider from the code in configuration Activity of the first one. I have read this and this. First one explains how to put multiple wigets in one apk, but it's not clear how to select between them in runtime. Second one is about changing layouts, but not size.
I have noticed that when I install some widgets I can later choose from different widget sizes while adding widget. How can I implement that feature in my widget?
View 2 Replies View RelatedI want to develop an application for a tablet of 480*800 screen pixels. I had developed an application for normal mobiles, but now this screen size is large than normal size. what precaution should I take while developing the application? Because device is not available right now so I must have to work on the project using emulator.
View 2 Replies View RelatedI've been reviewing the Supporting Multiple Screens documentation on the Android and I just need some additional clarification...
It's my understanding that designing three unique interfaces (ldpi, mdpi, and hdpi) would be the best way to go about supporting all the potential android screens with minimal scaling/distortion.
Yes, I know there are similar questions posted, however... If I create an image for the benchmark mdpi (let's say my image is 300x210, just for example) how to I determine what size I will need to recreate that image at ldpi & hdpi? This post as well as a google search leads me to believe that ldpi is just 75% of the mdpi image, and the hdpi is 150% of the mdpi image. Is this accurate?
Where can I find a list of how much space my apps are taking up? I'd like to see how much more memory I have on my phone and on my SD card. Do the apps store on the phone or the memory card?
View 1 Replies View RelatedMy android application is running good on emulators form 1.5v to 2.2v
when i installed .apk file on SAMSUNG GALAXY-3 v2.1 screen sizes are not matching.But
the same .apk file supporting the UI on SAMSUNG v1.5
I want to run my application on any screen sizes.
Swype WVGA 2.10.52.13753.apk - English and Deutsch language
View 8 Replies View RelatedI wrote a reading software. I implemented the page turning effect when user tap the screen to turn to next/pre page. The display is ok on G1 (320X200 size) but it can not works well on Droid(480*854 size), the font looks a litter fuzzy, not clear as G1. I explain my codes for page turning:
1) create a canvas A
2) create bitmap.
3) set bitmap on canvas A
4) draw the new page content on canvas A
5) the current showing page has been saved in bitmap before since we do from step 1) to setp 4),
6) In order to implement the turning effect of scrolling from left to right, I draw the old bitmap part and draw the new bitmap part until the whole new bitmap has been drawn. all of bitmaps are drawing by canvas.drawBitmap() in onDraw() function.
7) when step 6) is done, it means the new page has been shown on screen, and the bitmap has been saved to use in next page turning.
The above is the whole actions for my page turning. On G1, no problem. But on Droid phone, the font is not clear, I tried if I directly draw text by canvas in OnDraw() not through bitmap, It is ok, but it can not implement the page turning effect that I need. I don't know why, could you please help me to take a look and tell me where is wrong or miss some steps?
Are there any apps in the DONUT sdk that has support for the WVGA (looking just not for resized or compatibility mode, but having the proper assets to support 240dpi WVGA) Just looking around, dialer look awkward, so does few others ..
View 5 Replies View RelatedI'm developing an Activity with a simple LinearLayout with a button. When I try the activity on my hardware (WVGA 480x800 screen) the activity only fills the standard size (480x320) while the OS itself fills the whole screen.
What could be the issue.
CODE:..................
We have ported Android on our Development Board and are able to do the Web Browsing . We have 2 WVGA screens on our Development Board . We wanted to know if it possible for us to use the second screen when using the web browser to display large web pages . (Usually we scroll down , but we want to display it on the 2nd screen as much as possible. Any hints or suggestion in this regard would be really appreciated.
View 2 Replies View RelatedI been working on default skin before, if i change my skin to WVGA , my layout displays only in a portion of the skin and the rest of screen is black.
although, i can see android's home screen in full view. do i need to change my skin settings or my layout itself?
I read about in the google documents that the 3 folders corresponds to different screen types and that android would select the image from different folders automatically according to the screen type. I read that WVGA will load from drawable-hdpi and HVGA will load from drawable-mdpi. When I tested with 2 emulators both running 2.1, each with HVGA and WVGA. It turns out that they are both reading the image in mdpi. If I deleted the image in mdpi then they read from hdpi. Can someone answer why emulator with WVGA is reading from drawable- mdpi?
View 4 Replies View RelatedThe problem I am having is that when I run a FWVGA or WVGA sized emulator it sometimes runs at a MDPI size instead of HDPI. Here is an example with pictures. I create the AVD with the proper hw.lcd.density setting and screen size and it randomly does this. There doesn't seem to be a pattern. I used to be able to just delete the AVD and create it over again and it would fix itself for a while but now it's getting worse.
View 1 Replies View RelatedI'm designing an HTML page for display in Android browsers. Consider this simple example page:
<html>
<head><title>Simple!</title>
</head>
<body>
<p><img src="http://sstatic.net/so/img/logo.png"></p>
</body>
</html>
It looks just fine on the standard HVGA phones (320x480), but on HDPI WVGA sizes (480x800 or 480x854) the built-in browser automatically scales the image up; it looks ugly.
I've read that I should be able to use this tag to force the browser to stop scaling my page:
<meta name="viewport" content="width=device-width; initial-scale=1.0; maximum-scale=1.0; minimum-scale=1.0; user-scalable=0;" />
... but all that does is disable user scaling (the zoom buttons disappear); it doesn't actually prevent the browser from scaling my image. Adjusting the scale factors (setting them all to 2.0 or 0.5) has no effect at all.
How can I force the WVGA browser to stop scaling my images?
I took a WVGA quality video and uploaded it to youtube. The video looks great on the phone but looks crappy on youtube. What am I doing wrong?
View 4 Replies View RelatedOn my htc desire, all of the apps are blurry, they are not WVGA resolution as you would expect from a $390 phone!
View 15 Replies View RelatedI've noticed that all of the official literature regarding the Incredible describes the screen as WVGA OLED -not AMOLED. Can a screen be OLED without AM (active matrix) technology - and if so, what will the difference be between the Incredible's screen and the N1's AMOLED display?
View 8 Replies View RelatedI had previously used a wvga device and backed everything up on titanium backup. No I have anew qhd device, can I restore the alls and they will function normally? or will there be graphical errors?
View 2 Replies View Relatedi want to resize this lockscreen mod to wvga from 720p /1080p,
[URL]
How do i do it?
I've got a quick question about screen size support. Currently, I've got an application that is rockin' along just fine on 1.5 and 1.6. Today the client called and says they want to run on Droid. While I've downloaded the 2.0 SDK, I'm a little wary of compiling against it. Will it break 1.5 and 1.6 compatilbility? How will the "medium" phones (G1, MyTouch) know to use those layouts?
View 3 Replies View RelatedG1, Dream, Magic, Hero, Galaxy and more to come... Does anybody have a rundown of their screen sizes (and of some of the devices to come out)?
View 2 Replies View RelatedHello, I would like to ask what settings are necessary for my application to be available on all screen sizes: Is it enough to compile it using SDK 1.6 (but target is set to 1.5 and API level to 3) or maybe I have to set target to 1.6 and API level to 4?
View 4 Replies View Relatedsupporting multiple screens (sizes and resolutions). I´ve searched not only this forum but many different websites and the android documentation but I´m probably doing a small mistake so things are not working properly.
Well, my main layout was designed with a HVGA screen, and it works great. When I try the same app on a WVGA, FWVGA, WQVGA or FWQVGA, I always get an unused space in the end of the layout because the screen ´s "heightnes" is proportionally bigger than HVGA´s.
So I consulted the documentation and decided to give a try on resource qualifiers, so I then created a nonsense UI and placed it on layout- large, created a new AVD using the WVGA skin and launched the app. Well, all I got was my old and not well stretched layout. The same happened to a FWVGA AVD.
This is the first problem. The second is: medium high density medium size screens and medium density large screens have the same resolution: how can I create a layout that is loaded for both, but not for (for example) medium size medium density or small size medium density screens?
I have a widget in my app (in single choice mode) and the list is longer than the screen so it requires scrolling. There is a lot of space above and below the text so I think that space could be reduced (and the font size) so that everything fit without scrolling. I haven't been able to figure out how to reduce that space.
I'm also trying to get a single checkbox below that list and i tried making 2 listviews on top of each other on the linear layout but it didn't work.