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
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 RelatedI am a fresh developer on Googles Android Platform - my HTC Desire arrived last week. Now i need a way to sign in to my existing application (Java, currently running on jetty). The server Application is developed using spring security 3.0.2
In my case, i want to support the following: If a user has set up his Android phone with a googlemail/google-Account (and most users do) i want to use this account credentials to automagically log in to my server app.
Is there any Android framework supporting that use-case? Or are there any alternatives? I read: http code.google.com intl/de-DE/apis/accounts/docs/OpenID.html
How we do sign in with an app on google AppEnging is described here: http://blog.notdot.net/2010/05/Authenticating-against-App-Engine-from-an-Android-app
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?
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?
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 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 RelatedWhat are the 4x1 app widget sizes for WVGA and FWVGA in both portrait and landscape?
View 9 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 RelatedI have see some apps in Android that use some packages:
import android.net.http.EventHandler; import android.net.http.Headers; import android.net.http.RequestQueue; So some packages do not support the current version of SDK. Where can I find it? Would u tell me about it?
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 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?
How can I localize my application to support some Right to Left languages? How can I localize my application to support Hebrew? Arabic? and other languages?
View 1 Replies View RelatedI currently have an app on the market that supports Android 1.5 (SDK level 3) and up. It also takes advantage of several features that are only present in Android 2.0 (SDK level 5) and up. I do this using Reflection.
I read a post on the Android Developer Blog that talks about how to support these new features while using no Reflection, which would be amazing. http://android-developers.blogspot.com/2010/07/how-to-have-your-cupcake-and-eat-it-too.html <uses-sdk android:minSdkVersion="3" android:targetSdkVersion="5" />
I have tested this out and while it works there is one huge downfall. Currently if I try to add a SDK level 5 class, but I don't know that it's a SDK level 5 class, there is no worries. Eclipse isnt going to find the class and I'm not going to be able to add it.
Using Google's recommended method does allow me to add the classes and gives me no notification that this code is targeted just to SDK level 5 users. This opens up too big of a possibility of adding in code that would break some users without knowing.
Does anyone know of any plugins, options, etc that would warn me at the places I have targeted SDK level 5 to keep this from happening?
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 RelatedWhen we try to implement orientation in AP layer, we can set "android:screenOrientation" parameter in AndroidManifest.xml file or call "setRequestOrientation()" method of Activity class. But if I want to porting android in new HW device, how can I do? Do I need to modify the graphic driver, or just add configuration in program. (Actually I do some experiments but my AP cannot rotate) Besides, can every experts tell me when I set the "android:screenOrientation" parameter, which process will read this configuration, pass to where and which process will do the rotation?
View 2 Replies View RelatedI am new to Android. Can any one please tell me the phone models which support RTSP video(H.264) streaming?
View 1 Replies View RelatedI was hesitatnt to download it, but I love tabbed browsing so i figured I'd give it a shot. Well i love the browser itself, but I tried downloading a ringtone from myxer.com and it says it cant finish downloading because i need to clear space on my phone. But i have space and i tried using the stock browser and it worked fine.
View 1 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 RelatedAbout Donut and Eclair as follows. When are Donut and Eclair released? What is the main features of Donut and Eclair?
View 2 Replies View RelatedWill donut be available for the mytouch 3g or just the g1?
View 2 Replies View RelatedApp is called Tasker. It should be visible in all Donut+ devices but it's only actually visible in Eclair+ devices. Tested on my G1, reported by other users (devices unknown).
Manifest:
<uses-sdk android:minSdkVersion="4" android:targetSdkVersion="4" />
A dump from the compiled apk confirms that.
Here's the top of my Ant output:
Buildfile: build.xml [setup] Android SDK Tools Revision 6 [setup] Project Target: Android 1.6 [setup] API level: 4 [setup] Importing rules file: platforms/android-1.6/ant/ ant_rules_r2.xml
Copy protect is set to off.
And the app works fine when installed on a Donut device outside the market.
I noticed that appbrain also reports it as 2.0 and higher: http://www.appbrain.com/app/net.dinglisch.android.taskerm
O2 forum has launched a Poll regarding the Galaxy i7500, pls cast your vote O2 Forum :: View topic - Samsung no longer supporting Android on Galaxy
View 3 Replies View RelatedIn the Supporting Multiple Screens document in the Android Dev Guide, some example screen configurations are given. One of them states that the small-ldpi designation is given to QVGA (240x320) screens with a physical size of 2.6"-3.0". According to this DPI calculator, a 2.8" QVGA display equates to 143 dpi. However, further down the page the document explicitly states that all screens over 140 dpi are considered "medium" density.
So which is it, ldpi or mdpi? Is this a mistake? Does anyone know what the HTC Tattoo or similar device actually reports? I don't have access to any devices like this.
Also, with the recent publishing of this document, I'm glad to see we finally have an explicit statement of the exact DPI ranges of the three density categories. But why haven't we been given the same for the small, medium, and large screen size categories? I'd like to know the exact ranges for all these.
i want to resize this lockscreen mod to wvga from 720p /1080p,
[URL]
How do i do it?