Very odd.. I tried it on my other G2 and it worked flawlessly it rebooted itself and loaded fine.
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!
cp /data/local/tmp/hosts /system/etc/
busybox killall system_server
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 couldn't get it to work until I ran it like this as well. Very strange.su
insmod /data/local/vision_oc.ko pll2_l_val=74
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
setprop qemu.sf.lcd_density 200
busybox killall system_server
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.
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
I couldn't get it to work until I ran it like this as well. Very strange.
the code should be as simple as
Code:cp /data/local/tmp/hosts /system/etc/ busybox killall system_server
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...
Any ideas on how to fix the few apps that don't load full screen?
Sent from my T-Mobile G2 using XDA App
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!
which apps aren't working? i just went through my apps and it looks like everything i use works just fine at "200" density.
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!
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!
setprop qemu.sf.lcd_density XXX #change XXX to 200, 190, etc
busybox killall system_server
http://jamespickens.me/cloud/snap20110218_224457.png
Any idea what is going on?
Sent from my HTC Vision using XDA App