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.
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?
This kinda blows my mind.
Why doesn't Samsung's Email apk scale with higher DPI settings? I mean they are planning for future ICS phones with higher rez screens, and Galaxy Nexus is made by them (higher rez screen with ICS)..
Why the hell when I set the DPI to 210 or 220 in build.prop, the TW launcher, Email and even clock app don't scale?
Anybody knows any tricks of making at least Email scale nicely?
Can any dev explain the phenomena that I experience with Navigon when altering the Interface DPI with Paranoid Android? Not that they have to, I'm just curious.
If I set the DPI lower than 320, Navigon blows the interface up to freakish levels. Setting Navigon's per-app DPI back to 320 only makes it worse.
To get Navigon to display properly (and like stock 320 DPI), I have to set it to 160 DPI. With the XPosed framework, I can set the DPI back to 320 to remove the graphical glitch and set the app to view as it was before I changed the UI's DPI.
If I want the interface shrunk to match the rest of my UI, which I have at 190 DPI, I have to manually edit to properties.conf file to set the DPI to 100.
If no one can answer, hopefully this will help others who might have experienced this with other apps.
if I manually set dpi value to less than 289, the phone UI will switch to tablet mode.
is there any way to prevent this and run a lower dpi, say 200-250?
Stock is 480 and smallest is 330 for reference.