[MOD] LCD Density - Higher Resolution Screen

Search This thread

minotauri

Senior Member
Jun 18, 2008
632
175
Seattle, WA
www.antdroid.net
Sorry for floodin the thread with such a massive post but maybe it will help others. But I still want to know how to add adfree into visionary.sh so I don't have to start that up every time to0. If anyone want to throw me the command you used, I will guinea pig it into the script I just created and post it for the for everyone as well.

It's off topic but at least it will be out in the open cause I didn't see it anywhere. I know how to search...

Thank you all!

I thought I got adfree working in visionary, but I cant get it to work.

the code should be as simple as
Code:
cp /data/local/tmp/hosts /system/etc/
busybox killall system_server

but it doesnt write to system/etc with visionary.sh, but I can get it to work with terminal and using gscript. will continue to work on it.
 

Shambala001

Senior Member
Aug 29, 2009
117
0
Tampa
www.kilowattlaser.com
I have LCD Density working just fine but Adfree seems to only work at random times, most of the time though it does not function. Is there a way to revert back to the stock density without rebooting?
 
I have LCD Density working just fine but Adfree seems to only work at random times, most of the time though it does not function. Is there a way to revert back to the stock density without rebooting?

Adb shell
Su
Mount -o remount,rw /dev/block/mmcblk0p25 /system
Mount -o remount,rw /dev/block/mmcblk0p25 /data
Setprop qemu.sf.lcd_density 240
Busybox killall system_server


Sent from my T-Mobile G2 using XDA App
 

ihateusernames

Senior Member
Aug 21, 2009
304
44
This is basically taken from the LCD Density Changer app and applied to visionary.sh

You can increase the density (sort of like monitor resolution) on your screen by simply changing the build.prop file. Unfortunately, since we have temp-root only, it'll revert back. The LCD Density Changer - Free app lets you modify it without editing the build.prop and uses a hot boot to apply changes...

I wanted to automate it into startup with Visionary so here's what you can put into your visionary.sh file:

Code:
su
mount -o remount,rw /dev/block/mmcblkp025 /system
mount -o remount,rw /dev/block/mmcblkp025 /data
setprop qemu.sf.lcd_density XXX #change XXX to 200, 190, etc
busybox killall system_server

I use "200" for the XXX density. Some people below mention 190 as their favorite number to use.

note: killall command will do a hot reboot of your system.


all the credit goes to appelflap and jdsemler who found these things.

update 10/30:
added mounting to read/write for /system and /data to the script for users who did not have it already in their script. also some people prefer using 190 as oppose to 200.



Sent from my T-Mobile G2 using XDA App
 

V1R3Z

Senior Member
Mar 19, 2009
50
1
ok for everyone not knowing how to get this done:

#1 - have adb working and properly installed
go here for drivers for windows

#2 - copy the script posted on the first post of this thread:

su
mount -o remount,rw /dev/block/mmcblkp025 /system
mount -o remount,rw /dev/block/mmcblkp025 /data
setprop qemu.sf.lcd_density XXX
busybox killall system_server

#3 - paste it into notepad and change the XXX to ither 190 or 200 or some say 205 try 190 to start then move up so for now lets say you change XXX to 190

#4 - go to save as... select from the drop down menu at the bottom that says "txt file" change that to "any file" then change the file name to visionary.sh and click save to save it to your desktop or were ever u want

#5 - make sure you have visionary installed from the market and your phone is temp rooted and you select the run on boot option in the visionary app

#6 - on ur computer open up the command prompt and type in "adb push " with a space ater push and drag the visionay.sh file u just saved into the command prompt then type another space and type "/data/local/" then press enter so ur command prompt should look like:

C:\Users\Me>adb push C:\Users\Me\Desktop\visionary.sh /data/local/
(press enter)
and it should say that you copied the file over
23 KB/s (166 bytes in 0.007s)

then reboot ur phone and wait a few extra minutes and tada it should be all smaller and like when you raise the resolution on your pc

hope that helps someone
 

minotauri

Senior Member
Jun 18, 2008
632
175
Seattle, WA
www.antdroid.net
ok for everyone not knowing how to get this done:

#1 - have adb working and properly installed
go here for drivers for windows

#2 - copy the script posted on the first post of this thread:

su
mount -o remount,rw /dev/block/mmcblkp025 /system
mount -o remount,rw /dev/block/mmcblkp025 /data
setprop qemu.sf.lcd_density XXX
busybox killall system_server

#3 - paste it into notepad and change the XXX to ither 190 or 200 or some say 205 try 190 to start then move up so for now lets say you change XXX to 190

#4 - go to save as... select from the drop down menu at the bottom that says "txt file" change that to "any file" then change the file name to visionary.sh and click save to save it to your desktop or were ever u want

#5 - make sure you have visionary installed from the market and your phone is temp rooted and you select the run on boot option in the visionary app

#6 - on ur computer open up the command prompt and type in "adb push " with a space ater push and drag the visionay.sh file u just saved into the command prompt then type another space and type "/data/local/" then press enter so ur command prompt should look like:

C:\Users\Me>adb push C:\Users\Me\Desktop\visionary.sh /data/local/
(press enter)
and it should say that you copied the file over
23 KB/s (166 bytes in 0.007s)

then reboot ur phone and wait a few extra minutes and tada it should be all smaller and like when you raise the resolution on your pc

hope that helps someone

thanks. this should help people. i'll put it in the OP.

I couldn't get it to work until I ran it like this as well. Very strange.

i have noticed that the phone is very finicky with running scripts. i dont know why, but i sometimes have to delete and re-type things in over again to get it to work. i'm not sure if editing it in wordpad/notepad in win7 works half the time when switching over to android/unix. i have better luck typing the commands in root explorer.
 

V1R3Z

Senior Member
Mar 19, 2009
50
1
i also seem to be running into a bit of trouble too.

when i run the visionary.sh with just the LCD density script it works perfect every time BUT when i add anything else to that script such as overclocking it breaks it... ive tried putting the OC before and after the mounting of system and data... after the mounting of system and data and even after the system killall and i cant get BOTH to work... im not an ADB genius lol so maybe some one can help us with how the script should be ordered idk...

or were just going to have to use gscript and make it run the scripts for us at boot...
 

V1R3Z

Senior Member
Mar 19, 2009
50
1
OK so i did what philosophics said at the end of post #12 and it worked for me too

very wierd i reall dont need to edit the overclock script/kernel i want to leave it at 1ghz not 1.4ghz so normaly i would only need to add this line o the visionary.sh file:

insmod /data/local/vision_oc.ko

but it some how breaks it and nothing works BUT

if you put

insmod /data/local/vision_oc.ko pll2_l_val=53

into the script then it works just fine with boh OC and LCD density mod...

its just like post 12 said a the end... tthe only thing i changed was the 74 at the end for 53 cuz i dont want to kill my battery running it at 1.4ghz

so at the end my visionary.sh file is:

su
insmod /data/local/vision_oc.ko pll2_l_val=53
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
setprop qemu.sf.lcd_density 205
busybox killall system_server

but i should be working with:

su
insmod /data/local/vision_oc.ko
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
setprop qemu.sf.lcd_density 205
busybox killall system_server

sorry its getting a little of topic i just wonder if we can find out why its doing that....
 
This is for implementing adfree android into the script
the code should be as simple as
Code:
cp /data/local/tmp/hosts /system/etc/
busybox killall system_server

I just tried to run this in a shell and it says no such file or directory. Maybe this is the reason why it's not working?

I'm really sorry for making this go off topic so much. this is where the conversation is taking place though. Really don't understand why a thread hasn't been opened up about the visionary.sh

When I figure it out, I'll create the thread with instructions and possible options and/or various choices cause I understand that not everyone wants their device running at 1.42Ghz (It is pretty stable though and I'm almost positive my battery lasts longer due to underclocking the cpu for screen off) so a varity is needed.

Back to the subject, /data/local/tmp is EMPTY! WHY? This doesn't seem normal.

Just ran adfree and decided to try symlinking /data/data/hosts and nothing changed. Really don't know where to find /hosts so I'm running blind here.

If anyone has any insight on this, please help me out so I can get this topic somewhere else. The way I see it is the conversation is here right now so let's solve it and then create a thread when we have something working.

Again, I apologize...
 

minotauri

Senior Member
Jun 18, 2008
632
175
Seattle, WA
www.antdroid.net
This is for implementing adfree android into the script
Just ran adfree and decided to try symlinking /data/data/hosts and nothing changed. Really don't know where to find /hosts so I'm running blind here.

If anyone has any insight on this, please help me out so I can get this topic somewhere else. The way I see it is the conversation is here right now so let's solve it and then create a thread when we have something working.

Again, I apologize...

Yea this is getting off topic but it's ok. Maybe we should start a new thread?

Anyway, when AdFree is run and installed, it modifies /system/etc/hosts file. I forgot to mention, that after running AdFree, I make a copy of hosts to /data/local/tmp so that it'll remain there after rebooting. My attempt is to copy this file to /system/etc/ at boot up and then do the hot boot to try to implement it, but it doesn't work.
 

LxDroid

Senior Member
Sep 13, 2010
58
3
Any ideas on how to fix the few apps that don't load full screen?


Sent from my T-Mobile G2 using XDA App
 
This question is actually on topic!

Is there a command we can implement into the script that will make all apps utilize all of the screen real estate? After reboot everything reverts (OBVIOUSLY) and it's stating to get a little annoying to uninstall and reinstall all apps that don't stretch.

SPARE PARTS DOESN'T WORK FOR ME!
 
Last edited:

Shambala001

Senior Member
Aug 29, 2009
117
0
Tampa
www.kilowattlaser.com
This question is actually on topic!

Is there a command we can implement into the script that will make all apps utilize all of the screen real estate? After reboot everything reverts (OBVIOUSLY) and it's stating to get a little annoying to uninstall and reinstall all apps that don't stretch.

SPARE PARTS DOESN'T WORK FOR ME!

Are you saying that if you reinstall an app that previously did not resize, upon reinstall it now resizes?
 

minotauri

Senior Member
Jun 18, 2008
632
175
Seattle, WA
www.antdroid.net
here's what AdFree looks like for me at 190 density.
 

Attachments

  • device.jpg
    device.jpg
    21.8 KB · Views: 336

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    You can increase the density (sort of like changing monitor resolution) on your screen by simply changing the build.prop file. This gives you more viewing area on your screen. The build.prop file contains many user variables that are editable and one of them is the LCD Density. The lower the number, the higher the resolution. The default value is 240, but by simply changing it to 200, you can increase the resolution and see more emails in your email app, more app listings in the market, more room for widget alignment, crisper graphics, and much more!

    UPDATE 03/25/2011: ADDED SCREENSHOTS! (finally)



    PERMANENT ROOT SOLUTION:

    now that we can do perm root, you can permanently change this by modifying your build.prop file located /system/build.prop. look for ro.sf.lcd_density and modify the number and save and reboot.

    Recommended value is 200, though many users like 190. If you are unsure what you like, please try TEST MODE shown below!

    Please be sure to download Spare Parts from the Market, and disable Compatibility Mode in the app. This will fix many, many apps from not displaying full-screen, however there are some apps that will not re-size.

    This works really well if you pair it with something like Launcher Pro or ADW.Launcher, where you have control over rows/columns and resizing widgets.


    Easiest Method -- Go to Market and download one of the LCD Density apps. Search "LCD Density."


    Phone-Only Method:

    You can use Root Explorer, or any text editor like notepad++ or text edit.

    1. Open a File Manager and locate /system/build.prop
    2. Make sure "/system" is mounted as R/W (in Root Explorer, click the Mount R/W button at the top.)
    2A. MAKE A BACKUP!
    3. Open and Edit the file.
    4. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
    5. Save the file.
    6. Exit and Reboot!

    If you use a separate text editor, just copy the file to your SDCard, edit it there, and move it back and overwrite the original. I recommend backing up the original just-in-case. :)


    ADB Method:

    at the cmd prompt:

    1. adb pull /system/build.prop
    2. Go to SDK / Tools folder and open build.prop in a text editor (recommend WORDPAD for Windows).
    3. Find ro.sf.lcd_density=240 and change it to desired value (recommend 200 or 190 for G2).
    4. Save & Exit
    5. go back to cmd prompt and type: adb shell mount -o remount,rw /dev/block/mmcblk0p25 /system
    6. type: adb push build.prop /system/
    7. exit and reboot phone!


    [Test Mode]

    If you just want to play around with the setting for test, you can do something similar to the temp-root method shown below.

    Open Terminal Emulator from your phone or use adb shell from your computer:
    type: setprop qemu.sf.lcd_density 200 (or 190,etc)
    press enter.
    type: busybox killall system_server
    press enter.
    it will reboot quickly with your new display. Just reboot and it'll go back to stock. Once you find something you like, you can edit the real build.prop file. :)


    ---------------------------------

    [original mod / pre-perm-root]


    Below is for use with Visionary temp-root app.

    This is basically taken from the LCD Density Changer app and applied to visionary.sh

    You can increase the density (sort of like monitor resolution) on your screen by simply changing the build.prop file. Unfortunately, since we have temp-root only, it'll revert back. The LCD Density Changer - Free app lets you modify it without editing the build.prop and uses a hot boot to apply changes...

    I wanted to automate it into startup with Visionary so here's what you can put into your visionary.sh file without even having the app:

    Code:
    setprop qemu.sf.lcd_density XXX #change XXX to 200, 190, etc
    busybox killall system_server

    Example Visionary.sh script is found on Post 51. This script also contains commands for Ad Block and Overclocking which can be found in separate threads on the forum.

    I use "200" for the XXX density. Some people below mention 190 as their favorite number to use. 240 is the default!

    note #1: killall command will do a hot reboot of your system.

    note #2: you do not need to download the app to do this. you just need visionary app from Modaco/Paul O'Brien, which is on the market.

    Here are some written instructions from V1R3Z on Page 3 of this thread if you do not know how to create and push visionary.sh to your device:
    http://xdaforums.com/showpost.php?p=8962877&postcount=27


    update 10/30:
    added mounting to read/write for /system and /data to the script for users who did not have it already in their script. also some people prefer using 190 as oppose to 200.

    update 11/02:
    removed mounting for the /data folder as it is unneccessary. make sure you use a proper text editor and save in a format the phone can read. it's probably a better idea to make the script on the phone than in windows.



    credit goes to appelflap and jdsemler who found these things.
    1
    While I edit the build.prop sometimes too, why don't you just use LCD Density from Market? There is a free version, which does this in a graphical interface.
    1
    http://jamespickens.me/cloud/snap20110218_224457.png

    Any idea what is going on?

    Sent from my HTC Vision using XDA App

    You have to download "Spare Parts" from the Market, and uncheck "Compatibility Mode". This fixes the size issue of most apps. Good luck ;)


    Sent from the Heavens
    1
    I am now but this was a long time ago and have changed roms altogether since then. the market is real funny/finiky sometimes and I believe there is something apon start up that checks things like do you have internet and what device you have and then is stored to your account, if you go to the playstore from pc it should show the devices linked to your account. sometimes when I change roms it thinks I have a completley diferent phone, my guess is it thinks you have a different device right now. try restoring a recent nandroid if you have one or try flashing gapps without a wipe over current setup

    Sent from my HTC Vision using xda premium