Hi All,
I currently own a viewsonic vpad 10s tablet. It's currently on 1024x600.. is it possible to have a software hack or other to change the resolution to 1280x like the xoom?
The short answer is no.
The longer answer is...kind of.
https://market.android.com/details?id=com.beansoft.lcd_density_changer&feature=search_result
BK553 said:
The longer answer is...kind of.
https://market.android.com/details?id=com.beansoft.lcd_density_changer&feature=search_result
Click to expand...
Click to collapse
OK, and now the even longer answer.
There is no way to increase the resolution to 1280 x 800. Our display is an AU OPTRONICS B101AW06. Look it up on the net & you'll find max resolution is 1024 x 600. What BK553 is speaking about is a change in text DPI. You can see this in Windows where you can change the DPI. Manufacturers normally set the DPI to give the user the best readability but not necessarily the highest DPI. If you change the DPI, text & icons will become smaller (or larger depending on if you increase or decrease the DPI). To see what effect LCDDensity Changer may have, see the attached picture. Icons are smaller & text is smaller, giving the illusion of higher resolution. Notice how the backbround is the same while the text & icons are smaller.
Again, you can not change the resolution...videos, pictures etc will always displayed at a max resolution of 1024 x 600.
By the way, check this post http://forum.xda-developers.com/showthread.php?t=864338&highlight=lcd and you will see that atleast in Dec 2010 there used to be a field in build.prop that you could change to change the DPI. I looked for it in mine (I'm running Calkulin+Clemsyn Combo v6) and that field no longer appears.
hatorihanzo said:
Hi All,
I currently own a viewsonic vpad 10s tablet. It's currently on 1024x600.. is it possible to have a software hack or other to change the resolution to 1280x like the xoom?
Click to expand...
Click to collapse
I use blade and spare parts to tweak the dpi. don't think you can get up to 1280 with any software though.
hi guys..
i have seen a few posts on the SGS side of things about resizing the dialer / camera etc... correctly when the LCD denisty is changed to a lower than standard figure..
is there a way of these apps "ignoring" the LCD density values set in the build.prop files?
just thinking.....
ta
nutmegy said:
hi guys..
i have seen a few posts on the SGS side of things about resizing the dialer / camera etc... correctly when the LCD denisty is changed to a lower than standard figure..
is there a way of these apps "ignoring" the LCD density values set in the build.prop files?
just thinking.....
ta
Click to expand...
Click to collapse
This ROM has a modified camera app for 200 dpi: http://forum.xda-developers.com/showthread.php?t=1149713
Just extract it from SkyROM and replace yours via adb or root explorer...
please help me i changed my s2 density to 200 now its not booting please super please help.
Indirect deserves a salute for rooting the NT
http://forum.xda-developers.com/showthread.php?t=1354487
Still running a Nook Color with a dpi of 240 in build.prop, I would very much
get any reports on the following
1. Can the same be done on the NT without too many side affects?
2. Has anyone installed skype and tested the built in Mic?
How about a response as to a rooted Nook Tablet with a higher (240) dpi setting?
speaking completely out of curiosity, how can you display a higher dpi onscreen (if I'm understanding what you're asking), if the display is only capable of 169 dpi?
maybe I'm oversimplifying the question and am not understanding you.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
after doing some searching, are you referring to actual font size?
Android allows different dp settings independent of the hardware dpi for UI design. Details in below link,
http://developer.android.com/guide/practices/screens_support.html
Density-independent pixel (dp)
A virtual pixel unit that you should use when defining UI layout, to express layout dimensions or position in a density-independent way.
The density-independent pixel is equivalent to one physical pixel on a 160 dpi screen, which is the baseline density assumed by the system for a "medium" density screen. At runtime, the system transparently handles any scaling of the dp units, as necessary, based on the actual density of the screen in use. The conversion of dp units to screen pixels is simple: px = dp * (dpi / 160). For example, on a 240 dpi screen, 1 dp equals 1.5 physical pixels. You should always use dp units when defining your application's UI, to ensure proper display of your UI on screens with different densities.
e.mote said:
Android allows different dp settings independent of the hardware dpi for UI design. Details in below link,
The density-independent pixel is equivalent to one physical pixel on a 160 dpi screen, which is the baseline density assumed by the system for a "medium" density screen. At runtime, the system transparently handles any scaling of the dp units, as necessary, based on the actual density of the screen in use.
Click to expand...
Click to collapse
I understand the advantage to a developer laying out UI that needs to run on different display resolutions, but I don't see an advantage for an end-user. Why would you set your dpi to 240 if you can only display 169 dpi on the device? Won't the tablet simply downsize bit-mapped images when they're actually displayed?
Honest question--I'm probably not understanding something here--and I'm certainly not trying to rile anyone. Thanks!
Per above equation, setting your device's dpi setting to 240 would allow the app to be 150% in size. This aids in legibility, at cost of more screen space.
If you have an NC, you can see this firsthand by adjusting abovesaid dpi setting in build.prop up or down.
e.mote said:
Per above equation, setting your device's dpi setting to 240 would allow the app to be 150% in size. This aids in legibility, at cost of more screen space.
Click to expand...
Click to collapse
Ah, cool. Thanks for the info!
All I wanted to know was if the build.prop can be edited on a rooted NT as I have done on the NC.
Also, I will try once more. Did anyone use the Microphone with skype or some other chat app?
Hi, all!
I have JXD s7100B and when I changed custom bootscreen (only the last one. I can't find others to change them ), because there was a circle on the boot image, I've noticed that the image is deformed - when turned to lanscape mode it is "squished" verticaly. After that I've noticed the same with the icons on the launcher - however I rotate the screen shorter side is squished. I have an idea that maybe display is not WVGA (800x480pix) like it's set (and sold) but a WVGA NTSC (854x480) so I would like to change 800 to 854 somehow but leave 480 and dpi. I've searched forum and net and 90% of posts are changing dpi with LCD Resolution app or by editing build.prop but nothing I found says anyting about what I want to do. I found some resolutions in /system/bin/set_display_mode.sh but I've decided to ask first if someone knows what I should do. Can you help me? Can I change one dimension with some app or by editing some file?
I just thought I would give everyone a warning about changing LCD density with "adb shell wm density XXX"
(only applies to us non-rooted users -- rooted users can edit build.prop on the fly)
If you change the density, and then decide to check out the other resolutions like 720p and 1080p, it will fully erase your set density and return to stock resolution, even if you change the resolution back to stock (WQHD)
I myself didnt know this. I thought it would keep the resolution and recalculate the density, or reduce / increase the density based on the difference between WQHD. This is not the case.
So for those who set a custom density, DONT CHANGE RESOLUTION!