Just made my first android app.
I'm really confused about one thing. How to rightly simulate different android mobile screens with the android sdk.
Im trying to simulate the HTC Desire screen. But ive problems getting my app looking the same in simulated screen (avd) as it does on a real htc desire.
This is the example i am using:
I've got a Samsung Galaxy S phone, and my friend has got a HTC Desire.
When i install my app wht the default HVGA-avd on my pc , it shows exactly as on my samsung galaxy-phone. But the app doesnt show the same on the android-avd compared to the real htc desire phone.
Ive attached in this post 2 links to screendumps, that shows the app on avd(htc desire simulator) and the app on a real htc desire phone.
- link: home.c2i.net/hkhan/real_htc.jpg : this is a screendump with the app running on a real htc desire phone.
- link: home.c2i.net/hkhan/avd_htc.jpg : this is a screendump with the app running on the avd.
In the AVD (htc desire spec) the whole app-screen gets showed, with the button numbers from 1 to 9. But when i run the app on a real htc desire: Only the numbers up to 6 get shown, as in the picture. I dont see what im doing wrong....i need to get the avd similar to the real thing, or else i would not be able to test my app properly.
Ive got my friend to send me his htc-desire specs. this is what we get when he run the app 'tDpiInfo' on our mobiles. Both the htc desire and samsung has got the same specs as following:
Density:1.5
Density dpi:240dpi
Screen layout size=Normal
Aspect Ratio: long WQVGA,WVGA,FWVGA
Height px: 800px
Width pixels 480px
Click to expand...
Click to collapse
The only difference between the galaxy and desire i get is:
Desire:
Xdpi: 254 dpi
Ydpi: 254 dpi
screen size: 3.7"
Galaxy:
Xdpi: 234 dpi
Ydpi: 236 dpi
Screen size: 3.7"
Click to expand...
Click to collapse
I have set my pc monitor resolution to
Screen resolution: 1366x768
Screen: 15,6" widescreen
Click to expand...
Click to collapse
I have set the Android AVD for htc desire with the following:
-WVGA800(480x800) AND HIGH DENSITY(240)
-scale density to real size with: screen size 3.7"
-monitor dpi 100 (screen size 15,6" and Resolution 1366 x 768 for my dell studio 1555)
-scale 0,40.
Click to expand...
Click to collapse
Any suggestions and help will be very very appriciated. thanx.
Did you check Android Development and Hacking and then the subforum Android Software Development?
Seems to be the best place to search for, or ask, a question like this one. Your question has nothing to do with this Desire subforum
Related
hey guys i was wondering if there is any way (or maybe app? ) to change the display settings on hd2 or android in general
i searched some other threads but somehow nobody knows how it goes^^
Try lcd density changer. I found a few in appbrain market, finally found one that works on my hd2, check your default before changing anything though, the first one i tried for some reason when i rebooted my screen was black, like i could touch things and feel the haptic but no screen. I had to clean install my android rom. I think the hd2 is default 240 and i went to 220 and it was cool. Some apps dont scale right but others are fine, and the font is much crisper imo
Sent from my HTC HD2 using XDA App
LCD density changer doesn't seem to change contrast/saturation but only pixel density/resolution.
Is there a way to change dispaly contrast or saturation?
Been looking for this too..
The Desire HD should* have the same screen as the hd2, am i right?
why is it that the colors are a bit more saturated in the desire hd? it must be a software issue, no?
saintnickxiii said:
Been looking for this too..
The Desire HD should* have the same screen as the hd2, am i right?
why is it that the colors are a bit more saturated in the desire hd? it must be a software issue, no?
Click to expand...
Click to collapse
The Desire HD uses an S-LCD were as the HD2 has a normal LCD
I am Korean. I am not well English...
well.. my hd2 is nand miui 1.2.11 Ver.
I see color banding by widget and pictur
e and back ground and etc..
but my friend is color banding no!!
Why!!? help me..
Sent from my HTC HD2 using XDA App
ysm213 said:
I am Korean. I am not well English...
well.. my hd2 is nand miui 1.2.11 Ver.
I see color banding by widget and pictur
e and back ground and etc..
but my friend is color banding no!!
Why!!? help me..
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Different ROMs use different graphics.
Colour banding happens because the screen of the HD2 is 16 million colours instead of 32 million colours. To see this effect on your home computer, change the monitor settings to 16m from 32m.
If you have an image that changes colour progressively then banding is going to happen i'm afraid. The only way to avoid banding is to use images with block colours.
If, however, you are both using the same phone and same ROM, then I am lost as to the reason you've both experiencing different visual effects.
It could also be that your screen is starting to break down, if u see colour distortion also in official wm6.5 ROMs i would return it for repair.
Bot me and my brother had the same problem, colours fading away or not looking correct, HTC does np in fixing it (atleast here), got our screens replaced within 3 weeks
Thank you i will go to a/s center..
without pay..?
Sent from my HTC HD2 using XDA App
actually the HD2 screen is TFT capacitive touchscreen, 65K colors not 16million
and 32 million colors screen ? is something like this exist ???
for example HTC Desire HD or iPhone 4 got 16M colors
dkl_uk said:
Different ROMs use different graphics.
Colour banding happens because the screen of the HD2 is 16 million colours instead of 32 million colours. To see this effect on your home computer, change the monitor settings to 16m from 32m.
If you have an image that changes colour progressively then banding is going to happen i'm afraid. The only way to avoid banding is to use images with block colours.
If, however, you are both using the same phone and same ROM, then I am lost as to the reason you've both experiencing different visual effects.
Click to expand...
Click to collapse
rikardo1979 said:
actually the HD2 screen is TFT capacitive touchscreen, 65K colors not 16million
and 32 million colors screen ? is something like this exist ???
for example HTC Desire HD or iPhone 4 got 16M colors
Click to expand...
Click to collapse
Oh well, I was still right then, 65k colours would certainly cause banding.
ysm213 said:
Thank you i will go to a/s center..
without pay..?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I don't think its a hardware problem... its just that the hd2 only has 65,000 colors while other android phones have 16million, so unless you use a launcher that gets rid of the banding, you will see banding. The HD2 wasn't meant to run android... it doesn't have the colors to support what the OS wants to display.
I think launcher pro will get rid of banding.... it all depends on what launcher you're using.
Does your friend that doesn't have banding have a HD2? What launcher is he using?
My launcher is default miui launcher..
Sent from my HTC HD2 using XDA App
So what does this do....
http://forum.xda-developers.com/attachment.php?attachmentid=549635&stc=1&d=1300874955
With AWD Launcher i now get a screen with 6 x 6 (columns,rows). I finally get to use the big screen on the Desire HD.
Compatability?
Well i have no idea what sense would do and themes may have issue alone with some apps.
i know that Camera360 Ultimate don't like this until you run in hardware compatibility mode.
But ill never go back to ro.sf.lcd_density=240
This command is in the build.prop file located in the system folder. I recommend 'Root Explorer' for editing. And its all done at your own risk, always backup
FYI, i even did this to my Desire, not HD, and its just brilliant.
I also run at 200dpi, I find if you take it any lower that compatibility starts to become an issue and some games don't look nice in 70% screen usage. Personally I use ES File Explorer to do the editing of build.prop
wont sense be incompatible with this dpi setting?
that screen is so cluttered. I like mine to be open with everything big, easy to see and press. Plus the app drawer is where I keep most my apps
reminds me of an iphone
smurcoch said:
wont sense be incompatible with this dpi setting?
that screen is so cluttered. I like mine to be open with everything big, easy to see and press. Plus the app drawer is where I keep most my apps
reminds me of an iphone
Click to expand...
Click to collapse
yes, thank christ don't run sense it slows dhd down uneccessarily.
to see the difference heres two images first at 240 then at 200
Uploaded with ImageShack.us
I'm running CleanDHD which comes with 190 DPI, and i love it. My screen is way bigger now!
Have found three small glitches, but apps and games runs perfectly.
Confirm that troubles occurs with Camera360 but it's usable. Another application having problems with DPI=190 is CalWidget... it just displays an exception instead of my agenda....
naboleo said:
Confirm that troubles occurs with Camera360 but it's usable. Another application having problems with DPI=190 is CalWidget... it just displays an exception instead of my agenda....
Click to expand...
Click to collapse
can you send the Camera360 dev an email explaining what happens. i don't think that they understood what i was on about
Could you also test wide screen shots with zoom, full zoom or half zoom. I found that it crashes the app at dpi 240 or 200 for me.
cheers,
To save editing the build.prop you can download lcd density changer from the market. A bit easier I find.
I found that sense worked at 190dpi with a glitch on the lockscreen.
Sent from my HTC Desire HD using XDA Premium App
twiztedvvv said:
To save editing the build.prop you can download lcd density changer from the market. A bit easier I find.
I found that sense worked at 190dpi with a glitch on the lockscreen.
Sent from my HTC Desire HD using XDA Premium App
Click to expand...
Click to collapse
LOL!!!!!!! yeah that is a bit easier
Trust me to go and find the hard way of do it
mrjonnyrock said:
can you send the Camera360 dev an email explaining what happens. i don't think that they understood what i was on about
Could you also test wide screen shots with zoom, full zoom or half zoom. I found that it crashes the app at dpi 240 or 200 for me.
cheers,
Click to expand...
Click to collapse
Can you PM the dev's email ? Didnt find it, and user forum seems to be about feature requests and votes... Will try those setting
Confirmed also for notification glitch ... See screen captures
twiztedvvv said:
To save editing the build.prop you can download lcd density changer from the market. A bit easier I find.
I found that sense worked at 190dpi with a glitch on the lockscreen.
Sent from my HTC Desire HD using XDA Premium App
Click to expand...
Click to collapse
the problem with LCD density changer
is that the change doesn't survive reboots, where as changing build.prop does.
I may have missed something but can't get Camera360 crash...
2 other app that are not perfect :
- the stock dialer is too small the dialer part
- freecell has problems too
ghostofcain said:
the problem with LCD density changer
is that the change doesn't survive reboots, where as changing build.prop does.
Click to expand...
Click to collapse
I have LCD Density changer 5.3 and works perfect for me. Even with a reboot.
I don't see myself going above 180dpi anymore, I just love the screen estate I get with this. Also looks much cleaner.
This is with dpi on 170 and I'm thinking of going lower, the keyboard stays the same size so I go nothing got lose
I installed virtuous unity and I notice that in the phone application I can see the first 6 contacts over the virtual keyboard.
With standard sense for desire z (virtuous sense) I can only see my first 3-4 contacts.
This because virtuous unity is ported from a device with more resolution (I think) but the effect is great!
I hate the standard sense because I can't set the text size.
Large text is good for people that have vision problems, but I don't have, and I would like a rom with "less zoom" to see more objects in my screen.
I switch continuously from sense and cm7, I love cm7 and AOSP for the text size
PS: Spare parts have an options to resize the text, but don't work with all the sense applications. I hate the space waste of senseee!!! but I love sense services and beauty
Try LCD Density Changer from the market.
Sent from my Desire Z running @ 2GHZ
Search around for an app called propmoder
Sent from my HTC Vision using XDA App
xT4Z1N4TRx said:
Try LCD Density Changer from the market.
Sent from my Desire Z running @ 2GHZ
Click to expand...
Click to collapse
LCD density don't works on sense (brakes all the sense applications..)
im not quite sure but i think u can try this app, i had it sometime ago and i think it has the dpi change option
http://www.mediafire.../?61dsjqqfl6qg6
nonione said:
im not quite sure but i think u can try this app, i had it sometime ago and i think it has the dpi change option
http://www.mediafire.../?61dsjqqfl6qg6
Click to expand...
Click to collapse
I don't need a dpi changer.. change dpi in sense roms don't works.
I would love a sense rom with the text dimension and proportions of sense 3.0 ported from other bigger screen terminal.
I think that in bigger screen terminale htc makes smaller proportions in sense..
So an htc HD2 sense rom ported to htc desire z would be great (I think)
Someone can confirm?
Hi, i'm planning to buy the S4 this weekend..
I see i allready can root the device.. Is it also possible to change to 240dpi? Or is it to early
Greetings
I tried to switch to 240 dpi, but got ui errors after a reboot?
probably, but not for a little while. wait until all the hacks are released, and enjoy it for awhile first. lol
240 dpi is optimal for s3 , as s4 comes with 4xx dpi by default, id suggest you to change it to 320 dpi which would be optimal
I read somewhere that the S4 comes at 320dpi just like the S3.
type R-blood
Hi bala-gamer is it you who did the 240/180dpi modded apps for SGS3? If so I cant wait to do it for SGS4 I was very satisfied with your work and with the amount information displayed on SGS3 HD display on 240dpi...
You can always use another launcher which works on 240 dpi and use an others keyboard i guess .
No I tried all of the "best" launchers on SGS3 and ended with touch wiz...and bala modified problematic apps to work...
Help me to understand what is the discussion here.
DPI? Isn't that a print value?
BoneXDA said:
Help me to understand what is the discussion here.
DPI? Isn't that a print value?
Click to expand...
Click to collapse
DPI = printing
PPI = displaying
DPI=PPI moreless
but both means same = resolution of viewing doesn't matter the way
Actionx1 said:
I read somewhere that the S4 comes at 320dpi just like the S3.
type R-blood
Click to expand...
Click to collapse
I don't think there is even a hint of truth to that. Its like 441 dpi
Provide a link if you've got one. . .
sharkeecz said:
DPI = printing
PPI = displaying
DPI=PPI moreless
but both means same = resolution of viewing doesn't matter the way
Click to expand...
Click to collapse
But what is the point of changing it?
Icons and everything are displayed smaller so there will fit more info on the screen.
rauschkugl said:
Icons and everything are displayed smaller so there will fit more info on the screen.
Click to expand...
Click to collapse
yes, this is the reason for somebody who need it
I have tried
LCD Density Modder Pro - hangs on boot
A build.prop editor - boots fine, but dpi looks exactly the same. When I go back into the app, it says 480 dpi... as if I didn't change it
Xposed - hangs on boot
Anything that works?
3473 said:
I have tried
LCD Density Modder Pro - hangs on boot
A build.prop editor - boots fine, but dpi looks exactly the same. When I go back into the app, it says 480 dpi... as if I didn't change it
Xposed - hangs on boot
Anything that works?
Click to expand...
Click to collapse
same here, any infos?
ah ok i've got it.
my problem was that i added a line on the end of the build.prop -> i had to edit the one that was already there.
I used rom toolbox from the play store and changed mine to 320dpi and it's worked fine for the last 24hrs...
Sent from my GT-I9505 using xda premium
jongilluley said:
I used rom toolbox from the play store and changed mine to 320dpi and it's worked fine for the last 24hrs...
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
what line did you change?
zincsnow said:
what line did you change?
Click to expand...
Click to collapse
Within rom toolbox go to build prop editor and click the search icon and enter lcd. It should return a few lines but one will be lcd. Density at 420. Just click that one and change to 320 and reboot...
Need to be rooted as well.
Sent from my GT-I9505 using xda premium
rauschkugl said:
Icons and everything are displayed smaller so there will fit more info on the screen.
Click to expand...
Click to collapse
So how does going from a pixel density of 441 pixels per inch to fewer PPI (I've seem people talking about 240, 320, etc.) make things take up less room?
If an icon was 441 pixels wide, it'd take up an inch of screen space at native resolution. Change screen to 240 pixels per inch, and now that same icon takes up almost two inches.
Wouldn't you want to change to some number bigger than 441 pixels per inch to fit more on the screen? What am I missing?