Android :: WVGA Emulator Causes My App To Run In Compatibility Mode
Jun 29, 2010
Sometimes when I run a FWVGA or WVGA emulator it causes my app to run in compatibility mode (small inner rectangle instead of full screen / MDPI instead of HDPI). If I delete the emulator and recreate another one this usually solves the problem. My app can support HDPI, MDPI, and LDPI screens. My Android Manifest Support Screens says Small Screens = true Normal Screens = true Large Screens = false Resize able = true Any Density = true, Usually the front page looks like this: http://4.bp.blogspot.com/_hmNcPpDB070/TCmGaxEdS-I/AAAAAAAAAEQ/g0tlmQu. But when it screws up it looks like this: http://2.bp.blogspot.com/_hmNcPpDB070/TCmGvlOUqtI/AEY/mLUVGxN. Does anyone know what causes this or if there is a solution? It's not a major problem, just annoying.
View 3 Replies
Oct 7, 2009
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 Related
Oct 29, 2009
I 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?
View 2 Replies
View Related
Jun 2, 2010
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 Related
Jul 22, 2010
The 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 Related
May 3, 2010
I just published my first application to the market, but I just found out that android.telephony.gsm.smsmanager was depreciated as of Android 1.6. My application depends on sending SMS messages, so it cannot not work in 1.6 or newer. I built the project against 1.5, but I only have a device with 1.5 to test on. Since I built on 1.5, am I fine in terms of newer OSes, or will users get force closes? Is there a way to send/receive SMS messages in the emulator?
View 1 Replies
View Related
Oct 28, 2010
Is it possible to run the emulator without GUI showing? I want to continually run test of my app on server that does not allow opening GUI.
View 2 Replies
View Related
Apr 6, 2009
Is the actual version of the emulator able to reproduce the sleep mode? (Android 1.1 SDK r_1)
View 3 Replies
View Related
Apr 11, 2010
This is probably a pretty easy to answer question, but I can't find the solution myself after a couple hours of searching the documentation and Google.I set the orientation of my Android app to landscape in the AndroidManifest.xml file: android:screenOrientation="landscape"
However, when I run the app in the simulator, it appears sideways and in portrait mode. How can I switch the emulator to landscape mode on a mac? It's running the 1.6 SDK.
View 3 Replies
View Related
Apr 30, 2010
In android emulator, I am in landscape mode and double click the text edit panel. the softkeyboard does not show up. However, it works in portrait mode.
I have check some of posts on line. They said because of hardkeyboard is available in landscape mode. If that so, how can i disable the hardkeyboard. Or is there any setting reason for this problem?
View 1 Replies
View Related
Jul 9, 2010
I have an android application that parses some HTML, downloads an image, and displays it. I'm using an AsyncTask to do the HTML parsing and image downloading, but that shouldn't be relevant. I never have a problem when I'm on WiFi on my phone, when I'm using the Eclipse debugger on my phone, or when I'm using the emulator. When I have my phone on the cell network (even with pretty good reception), the image sometimes fails to display. I'm having a hard time figuring out what is wrong, since the problem cannot be reproduced in the debugger. Does anyone have any idea what could be wrong?
Update: I have narrowed it down to the image downloading function. This way my original code:.......................
View 1 Replies
View Related
Aug 13, 2009
Since I only have access to the emulators, I don't know if the problem can be reproduced on real phones. I'm using setCurrentTab on a TabHost to dynamically select a tab. When I am in portrait mode, it works, but as soon as I change to landscape (ctrl + f12), it doesn't work anymore. It doesn't send an exception, it just doesn't do anything. If I switch back to portrait (ctrl + f12), it doesn't work either. That means it just works when I first am in portrait mode. As soon as I change, it stops working. In order to make it work again, I need to close the application and reopen it.
The TabHost is from the current activity, which is a TabActivity.
Can you check if this happens to you too (emulator)?
View 2 Replies
View Related
Nov 14, 2010
Swype WVGA 2.10.52.13753.apk - English and Deutsch language
View 8 Replies
View Related
Jan 7, 2010
I 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?
View 2 Replies
View Related
Feb 20, 2010
This 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?
View 5 Replies
View Related
Sep 15, 2009
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 Related
Mar 24, 2010
I'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:..................
View 1 Replies
View Related
Oct 15, 2009
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 Related
Oct 31, 2009
What are the 4x1 app widget sizes for WVGA and FWVGA in both portrait and landscape?
View 9 Replies
View Related
May 9, 2010
I'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?
View 3 Replies
View Related
Apr 30, 2010
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 Related
Jun 1, 2010
On 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 Related
Apr 17, 2010
I'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 Related
Jun 25, 2012
I 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 Related
Feb 16, 2013
i want to resize this lockscreen mod to wvga from 720p /1080p,
[URL]
How do i do it?
View 3 Replies
View Related
Nov 21, 2009
<supports-screens android:anyDensity="false" android:largeScreens="false" android:normalScreens="true" android:smallScreens="false" android:resizeable="false"></supports- screens>
first of all what is the resizeable attribute? It does not seem to be documented. This is working almost 90% for my game except when testing in WVGA screen resolution, all my images are scaled incorrectly, it is longer vertically than horizontally. I was expecting the screen compatibility to maintain aspect ratios as that of HVGA.
Also in my layout I have a scrollview and it is designed in such a way that in HVGA when it is not scrolled down, the items are hidden away, however now in WVGA those things are shown. If the aspect ratio of HVGA is maintained I won't have this issue. How can I make sure the aspect ratio is maintained? Also in my layout I am positioning some items using pixel positions. Should I convert these to dpi? How do I calculate what dpi they should be?
View 9 Replies
View Related
Oct 12, 2009
What is the recommended approach to have currently shipping 1.5-SDK compliant apps to start offering 1.6 features (such as TTL) in the Market? Can we just publish 2 versions of the same package name each compiled with a different SDK level (will the Market automatically push out only the right version of the app) or do we have to use different package name and assume that the user will find a way to understand the version of the OS he has. A public statement to the developper community would be more than welcomed here!
View 5 Replies
View Related
Apr 21, 2010
I've found again my DevPhone1 (aka G1) on a shelf and though that this time I should really give it a try and create an app for it. But I've really lost touch with the Android world and now I don't know where to start really. There have been many SDK releases lately for many new and better devices. Which one of these can I use with G1? What is the most recent one which can be used on that hardware (although with reduced performance) but which will enable development for rather modern Android releases as well. The firmware update received today, while recharging the phone, is 1.6. Can I go higher with some R&D build?
View 3 Replies
View Related
Jan 24, 2010
i want to develop an application on android,webos,wince. how to develop application that should run on all paltform with developing each paltform
View 2 Replies
View Related
Jan 26, 2010
I can run my application on 1.5, 1.6 and 2.0 emulator and on a 1.5 device without any problems. But some of my users are reporting force close and strange menu entries (see the attachment) using 1.6 and higher version devices.
This screen should look like this:
http://www.taypo.com/blog/WindowsLiveWriter/TurkceKlavye0.7_6F1/settings_0.7_2.png
And the code that generates this screen is:
<?xml version="1.0" encoding="utf-8"?>
<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android">
<PreferenceCategory android:title="@string/general_settings">
<CheckBoxPreference android:title="@string/haptic_feedback" android:defaultValue="true"android:summary="@string/haptic_feedback_summary" android:key="vibrate"/>
<CheckBoxPreference android:title="@string/sound_feedback" android:defaultValue="false" android:summary="@string/sound_feedback_summary" android:key="sound" />
<CheckBoxPreference android:title="@string/auto_caps" android:defaultValue="true"
android:summary="@string/auto_caps_summary" android:key="auto_caps" />
</PreferenceCategory>
<PreferenceCategory android:title="@string/layout_settings">
<ListPreference android:title="@string/keyboard_layout" android:defaultValue="TRQ" android:key="kbd_layout" android:entries="@array/layout_names" android:entryValues="@array/layout_values" />
</PreferenceCategory>
</PreferenceScreen>
View 1 Replies
View Related
