Database Info

Resolution on vegan beta 5.1

Is there a way to change/increase resolution of tablet running the vegan 5.1?
I love the high resolution which comes with the gingerbread build?
Sent from my PC36100 using XDA App

Try LCD densitychanger from the market. Its free and doesnt survive a reboot, There is a paid version that will make it permanent. You can do a search of this forum and the instructions for changing it permanently manually are around.

rob_z11 said:
Is there a way to change/increase resolution of tablet running the vegan 5.1?
I love the high resolution which comes with the gingerbread build?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
{from a secret bunker somewhere in the canadian rockies}in /system/build.prop there's a line that says ro.sf.lcd_density=xxx the default android density is 160. The actual pixel density of the gtablet is ~120. Since xxx is really only a UI scaling factor relative to 160, you should get reasonable results with a number between 120 and 160... 120 will make things smaller. 140 seems about right to me.
If you use RootExplorer, navigate to /system, mount it as r/w, select build.prop and open in text editor... edit the line, save your changes, and mount the directory as r/o... and reboot.
If you don't use RootExplorer, edit the file elsewhere and push it back using adb.

bittrix said:
{from a secret bunker somewhere in the canadian rockies}in /system/build.prop there's a line that says ro.sf.lcd_density=xxx the default android density is 160. The actual pixel density of the gtablet is ~120. Since xxx is really only a UI scaling factor relative to 160, you should get reasonable results with a number between 120 and 160... 120 will make things smaller. 140 seems about right to me.
If you use RootExplorer, navigate to /system, mount it as r/w, select build.prop and open in text editor... edit the line, save your changes, and mount the directory as r/o... and reboot.
If you don't use RootExplorer, edit the file elsewhere and push it back using adb.
Click to expand...
Click to collapse
Thank you both for your help, and I think 120 is too small, and 140 did the trick for me which is the nice combination of the workspace and not too much strain on eyes.
I am sorry to report you Bittrix, but down in Florida temperature is gong to hit 60 and may be 68 tomorrow, so enjoy the cold weather in Canadian rockies

I use 120 for my tablet on all roms. I used 140 for awhile when starting to use lcd density, but eventually went to 120 because of app issues. 120 and 160 seem to nativly supported in android, and numbers in between its hit or miss as to whether they would work or not, even with compatibility turned on. (Some would only take up 3/4 of the screen instead of full or not open at all)

My build.prop does not have a line ro.sf.lcd_density=xxx and am running the latest Vegan build...
Any ideas?
EDIT: Added the line and no issues - just dont like it that small.. reverted back. Thanks
bittrix said:
{from a secret bunker somewhere in the canadian rockies}in /system/build.prop there's a line that says ro.sf.lcd_density=xxx the default android density is 160. The actual pixel density of the gtablet is ~120. Since xxx is really only a UI scaling factor relative to 160, you should get reasonable results with a number between 120 and 160... 120 will make things smaller. 140 seems about right to me.
If you use RootExplorer, navigate to /system, mount it as r/w, select build.prop and open in text editor... edit the line, save your changes, and mount the directory as r/o... and reboot.
If you don't use RootExplorer, edit the file elsewhere and push it back using adb.
Click to expand...
Click to collapse

Moved to general

[Q] Hold Back to Kill/Best Method for changing DPI

Double whammy question. Is there any way to enable hold back button to kill current app on any rom? I know that it's on most AOSP roms and Viper rom but I'm running King Cobra and miss it coming from AOKP. I would just use viper rom as it's the better rom between the two imo but currently changing the dpi causes system ui to fc and I need my 200 dpi, 320 seems huge and ridiculously wasteful after being on 200 for so long. On Viper it's 320 or nothing, no 241,240,200 or 192 (tablet mode) just 320. I usually just use root explorer and edit the build prop but that kills system ui. Unfortunately so does the app "lcd modifier pro" I know they all essentially do the exact same thing but maybe there's an app out there unbeknownst to me that tricks the system into thinking the density has been unchanged while actually allowing you to change the resolution. Any feedback is appreciated.

TW ROM that works with 240 LCD Density

Are there any TW roms that work well with LCD density set at 240? Specially the dialer. Thanks

You can try Galaxy Mod, http://forum.xda-developers.com/showthread.php?t=1953008
--------------------------------------
Multi-DPI support
--------------------------------------
This ROM has been modified to support different DPI settings, however don't expect it to be at the level of Paranoid Android. I still have yet to figure out per-app DPI, but as of right now you should not get any force closes or unexpected behavior when changing the DPI. There may be graphical glitches. Be careful, in my testing the phone would NOT boot with a DPI lower than 165. To be safe, I would suggest using a DPI of 180-220 if you plan on changing it. Make sure you do not set the DPI above the max which is 320. Doing so would result in a non-booting device.
To change the DPI open the build.prop using an app like Build.prop Editor and edit the following:
Code:
ro.sf.lcd_density=320
Change "320" to whatever value you want, but be careful. Reboot the device when you have made the changes.
Do not post a bug report if you changed the DPI. Some apps may not work with well with a DPI lower than 320.
Click to expand...
Click to collapse

[Q] Change device resolution? (not DPI)

Not sure if this is the correct forum, so please move it if need be
I am looking to change the resolution of a tablet, but so it is persitent (I am currently in a position to change the firmware, so maybe a build prop setting or init.rc?)
I can change the resolution using "am display-size widthxheight" but this does not persist through a reboot.
Is there a way to set it at firmware level?
I have tried various DPI settings, but I know it must be a resolution change, as I need to be able ot set it specifically to 1280x720.
Not sure what the original resolution is, but changing the DPI lower or higher does not change the fact I cannot view a 1280x720 image, at 100%, without scrolling.
Might it be the case I need to make a system app to run the "am display-size" command on boot?

mr_pablo said:
Not sure if this is the correct forum, so please move it if need be
I am looking to change the resolution of a tablet, but so it is persitent (I am currently in a position to change the firmware, so maybe a build prop setting or init.rc?)
I can change the resolution using "am display-size widthxheight" but this does not persist through a reboot.
Is there a way to set it at firmware level?
I have tried various DPI settings, but I know it must be a resolution change, as I need to be able ot set it specifically to 1280x720.
Not sure what the original resolution is, but changing the DPI lower or higher does not change the fact I cannot view a 1280x720 image, at 100%, without scrolling.
Might it be the case I need to make a system app to run the "am display-size" command on boot?
Click to expand...
Click to collapse
its not recommended to change your resolution, i have bricked my galaxy tab before and was luckily able to recover it. what device do you have? hopefully its a first party like samsung otherwise Chinese tablets you shouldn't mess with them, the chip-set is not open source so its easy to brick.

helped
this thread helped me alot

[TUTORIAL] How to increase Screen Density/DPI value of any Android Device

The phones keep becoming inferior with every superior model getting launched. Some users might not want to buy a new phone just yet. You might want to get the most out of your device while it lasts. To compensate for the continously increasing screen sizes and resolutions in the newer phones, we can change the Screen Density of our devices in order to utilize our screens more efficiently.
Most manufacturers stick to the standard DPI of 240 on the large screened phones like Samsung Galaxy S II or HTC Desire HD, so it might be too big to really make efficient use of the Android device.
Still, there is hope. Just make sure that you are rooted and equipped with Root Explorer or a free app like ES File Explorer in order to access the Root owned partition of the device.
Method:
1. Open Root Explorer
2. Go to /system
3. Click on Mount RW (It shall appear aa Mount RO)
4. Look for build.prop. Long press on the file and press Open file in Editor
5. Scroll down to ro.sf.lcd_density=240
6. Change the value to anywhere between 180 and 240. The lower the value, the higher density your screen will have.
7. Click on the Menu button , and Save and Exit.
8. Reboot.
You should now have a phone with the same screen size but alot more density, slightly smaller text and more space to use applications on.
This guide can be used on all Android phone, even the smaller MDPI and LDPI phones to make your screen to appear bigger and more useful . However, you will have to tinker with the value unless you find one that suits you best.
If some applications cannot span properly to the new screen size, download Spare Parts from the market, uncheck Compatibility Mode in the options, and reboot.
Some launchers may act wierd , however most do look good with a higher density look!
Do press the Thanks button if this guide has helped!

Reserved.

I am using 160. With this value you don't have problems with play store.

Bighardy said:
I am using 160. With this value you don't have problems with play store.
Click to expand...
Click to collapse
What issues did you experience with play store before?

When I used different values between 160 and 240, i. e. 180 or 200, I had compatibility problems with play store. New program version weren't shown as update, and if I searched for apps the message Not compatible with this device appeared. With 160 no problems with unhacked play store.