Related
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!
Click to expand...
Click to collapse
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!
Click to expand...
Click to collapse
[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://forum.xda-developers.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.
Hey, I gave this a shot but didn't notice a difference. Do you run any other commands in you visionary script? Do you put this at the end?
Update
Checked my build.prop, still set to 240. Never used the setprop command, but notice the property in build.prop doesn't have qemu.
Sent from my T-Mobile G2 using XDA App
I find 190 to work best.
mckinlk said:
Hey, I gave this a shot but didn't notice a difference. Do you run any other commands in you visionary script? Do you put this at the end?
Update
Checked my build.prop, still set to 240. Never used the setprop command, but notice the property in build.prop doesn't have qemu.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Hi - It doesnt modify the build.prop at all actually. I also have some other commands in my script to control adfree and setcpu, but perhaps adding these commands at the beginning will help:
Code:
su
mount -o remount,rw /dev/block/mmcblkp025 /system
mount -o remount,rw /dev/block/mmcblkp025 /data
Very nice. I just added a gscript to run it. It works like a champ.
Slows down g2 when uninstalled everything was back to normal.
Sent from my T-Mobile G2 using XDA App
I added the r/w to the /data and removed a line that killed the launcher after uninstalling bloatware. One of those steps did the trick. I love it at 190. I was so frustrated with how the resolution was better than the G1 but didn't really give me the impression with everything blown up.
Thanks for the details.
Sent from my T-Mobile G2 using XDA App
mckinlk said:
I added the r/w to the /data and removed a line that killed the launcher after uninstalling bloatware. One of those steps did the trick. I love it at 190. I was so frustrated with how the resolution was better than the G1 but didn't really give me the impression with everything blown up.
Thanks for the details.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Cool. I'll update the OP with the read-write commands.
Love the mod, thanks for the tip
any idea why after the hot reboot it causes sim checker light to email my location as if someone stole my phone and put in there sim?
Noticed the stolen report too with the kill launcher command. Must mess with the sim card negotiation and trigger something.
Sent from my T-Mobile G2 using XDA App
Forgive the noobisness, but are the icons in the app drawer supposed to look like complete ass with it set @ 190?
Trial and error results
That's what I noticed as well. ADW looks like crap and that's no lie. Some things aren't using the entire screen anymore.
One thing I've learned when it comes to having Android on the HD2 with a lcd_density of 180 is that you have to unmark compatability mode within spare parts. Since we g2 users don't have that app, we're kinda stuck.
BUT WAIT! Spare parts is on the market. Install it and then do an adb shell...
su
busybox killall system_server
AND IT DIDN'T WORK!!!
So I guess I'm gonna have to try a different density other than 190...
UPDATE:
changing the density to 200 made ADW look fantastic. Some apps still don't use the entire screen. Maybe rebooting entirely will help and actually adding these lines to visionary.sh instead of just running the commands through a shell...
UPDATE2:
Rebooting did nothing. Spare parts doesn't do anything so my question would be How do we get all apps to span across all of the screen?
My example is Weather and Toggle Widget with the Weather Forecast Add-on, the weather animation uses only half of the screen...
minotauri said:
I also have some other commands in my script to control adfree and setcpu
Click to expand...
Click to collapse
Off topic, I know but what are the commands you use for them?
This would help out a great deal!
UPDATE3:
Something went fishy. visionary.sh doesn't seem to want to work. This is what I have,
su
mount -o remount,rw /dev/block/mmcblk0p25 /system
mount -o remount,rw /dev/block/mmcblk0p25 /data
insmod /data/local/vision_oc.ko pll2_l_val=74
setprop qemu.sf.lcd_density 200
busybox killall system_server
Click to expand...
Click to collapse
Basically, it's everything in the OP with the addition of the oc command.
It was working just fine in the beginning but now it doesn't do the hot reboot unless I manually type killall system_server in adb shell or terminal emulator but oc goes through no problems either way...
I would like some clarification on something...
Is it mmcblk0p25 or mmcblkp025 cause 0p25 is what I did and it worked...
FINAL UPDATE:
So I'm really not sure what I did but with a lot of trail and error, I was able to come up with a working script...
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
Click to expand...
Click to collapse
don't edit it in anyway or it won't work. I don't know why...
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!
Launcherpro @ 200 looks amazing. Will keep it like that, it's like a whole new phone.
edit: thinking it's just a stock launcher problem with rendering, cause stock launcher looked like crap @ 200 too
Can someone post a couple of screen shots?
I'm using launcher pro @ 205. Looks amazing, everything aligned. I think you also need to play with your desktop columns and rows. I'm using 5x6 and manually resized widgets.
Thanks a ton to the OP. I absolutely LOVE high resolutions. Im using a density of 190 on ADW, and it looks fantastic! For some strange reason 200 and 210 were crashing the phone, 190 is running smoothly with no problems/glitches.
Sent from my overclocked T-Mobile G2 using XDA App.
Launcher Pro @ 190. This works great. Thank you.
Sent from my T-Mobile G2 using Tapatalk
I use launcher pro. but I know adw works too because I used that in the past with cyanogenmod on nexus one. you will want to change to column and row settings to full optimize the new screen density.
Sent from my T-Mobile G2 using XDA App
I can't get it to work I pushed the script and it was successful I can see it in terminal but it's not setting my density.
PlatinumMOTO said:
I can't get it to work I pushed the script and it was successful I can see it in terminal but it's not setting my density.
Click to expand...
Click to collapse
Reboot device and run visionary...
DooMKernel v10 with FW:4.0.A.2.368 on rogers xperia arc (bootloader unlocked)
I'm trying to use a custom script to set voltage, cpu governor, and schedule
I tried to copy the script to the sd card, then copy to /etc/init.d/, set permission to 777 in root explorer, NO EFFECT ON REBOOT..
Then I tried to use adb push to directly push the script into /etc/init.d/, and use chmod 777 command to set permission in adb shell, still NO EFFECT ON REBOOT..
If however I execute the script directly with root explorer everything works...
I've attached the script I used. Can anyone help me to autorun this on boot? Thx!!
zeronk said:
DooMKernel v10 with FW:4.0.A.2.368 on rogers xperia arc (bootloader unlocked)
I'm trying to use a custom script to set voltage, cpu governor, and schedule
I tried to copy the script to the sd card, then copy to /etc/init.d/, set permission to 777 in root explorer, NO EFFECT ON REBOOT..
Then I tried to use adb push to directly push the script into /etc/init.d/, and use chmod 777 command to set permission in adb shell, still NO EFFECT ON REBOOT..
If however I execute the script directly with root explorer everything works...
I've attached the script I used. Can anyone help me to autorun this on boot? Thx!!
Click to expand...
Click to collapse
Nice script.
It can't help you, but look at it:
http://forum.xda-developers.com/showthread.php?t=486486
You can use this for autostart and if you have trouble, simply remove SD card before start the phone:
http://forum.xda-developers.com/showthread.php?t=1011266
I am using the rom IML74K Android 4.0.3 Build 8 from bigxie and franco.Kernel #13.
I think the rom and kernel suppose to support init.d scripts. And I can found the script in etc/init.d named 97schedmc.
I wanna the hotplug function, so I put a file named 98hotplug(I don't know how to named the script), but I found it would not work. The parameter would not change after restart the device. Even I excute it(rename to sh file) in RootExplor, the parameter did not changed.
I try to run or sh the command in adb shell, it works fine, and the parameter changed.
I thinks it is relate to the access right issue, but I don't know how to fix it.
Could any one can help me?
Thanks for the guy who reply me.
you most chmod the files. Just sticking them it won't allow them to run.
I am not such understand... What should I do then?
chmod them?
755 works.
Hi,
Like this:
For 755,right permissions for scripts in Init.d folder,a good link i think: http://www.elated.com/articles/understanding-permissions/
Do not create a sh. file,for example in Root Eplorer,go to system/etc/init.d and menu/New file then put your script with #!/system/bin/sh first then space then enter.
Or on your pc take a init.d file in a rom,erase the script,copy yours with the correct script,reput in your phone,set the correct permissions then reboot.
Are you really sure your rom/kernel suppot Init.d ?
Just one question,I do not use this combo...
Hoping this helps
Permissions are set correctly, the kernel (faux123) supports init.d scripts, and the script works when run from terminal, but it still does not run on boot.
Thanks for your reply and great help!
I am sure the kernel support the init.d, but I not sure the rom, is it necessary both of them to support init.d?
What is your combo??
Hi,
To monkeyzou,yes i use the same kernel wich support Init.d script,but i use aokp rom,the rom you are using seems not support Init.d (it is not specified?),but in any case the Franco kernel support it,and it create the necessary lines in "init.rc" for activate the init.d support+the init.d file+the correct permissions,all automatically when you flash the kernel...
So i don't now what is wrong
Are you sure you set the right permissions for your file script in init.d?Are you sure your script is written correctly?
Can you share it?
After that my knowledges stop there,sorry...
init.d support only needs to be in the kernel ramdisk. As for rom support, that only goes as far as needing the directory. Note that some of the kernels out there are anykernel format and therefore would not support init.d scripts.
I was trying to do the exact same thing and couldn't make it work either. Eventually I just used Script Manager (on market) and let it run the script at boot.
Here is my script:
Code:
#!/system/xbin/bash
echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled
Re,
To monkeyzou can you test this script at the bottom of my message?
Remove the .txt and copy it to your init.d folder then set the right permissions for it as i have shown above.
Or test another script where you could see a change?
At the end are you sure your script don't work?
After reboot with the script go to /sys/module/dsscomp/parameters/hotplug_enabled and see if the value is set to 1,if yes it's ok,if no (so set to 0),i don't know more...
ctbear said:
I was trying to do the exact same thing and couldn't make it work either. Eventually I just used Script Manager (on market) and let it run the script at boot.
Here is my script:
Code:
#!/system/xbin/bash
echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled
Click to expand...
Click to collapse
Hi,
Test the script i've posted above:
#!/system/bin/sh
echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled
Click to expand...
Click to collapse
I hope that helps
viking37 said:
Hi,
Test the script i've posted above:
I hope that helps
Click to expand...
Click to collapse
Thanks. Unfortunately it still didn't work, but I've found a workaround (looks stupid, but somehow works):
Basically I have a script file at the root of storage, and it contains just the echo line. My init script will just run that /sdcard script and it works fine.
viking37 said:
Re,
To monkeyzou can you test this script at the bottom of my message?
Remove the .txt and copy it to your init.d folder then set the right permissions for it as i have shown above.
Or test another script where you could see a change?
At the end are you sure your script don't work?
After reboot with the script go to /sys/module/dsscomp/parameters/hotplug_enabled and see if the value is set to 1,if yes it's ok,if no (so set to 0),i don't know more...
Click to expand...
Click to collapse
Tried this script and it works
I have a shell command that I manually type in terminal everytime my phone starts up. How can I make it automatically execute @ each boot? I've seen init.d scripts, but I'm currently on ICS and I don't believe the kernel I am on supports init.d scripts yet. Any other way without using an external app?
thanks..
Check my thread out in here,
http://forum.xda-developers.com/showthread.php?t=1610741
You can run any scripts during the boot.
Hey guys, ive modified the services.odex file from the ODEXED ROM of the ICS Official Rom, it makes the launcher hard to kill, it means no more launcher redraws. Use it in conjunction with the V6 supercharger script. All you need to do is copy it to system/framework and apply permissions
screenshots for proof at the bottom
THIS IS NOT MY OWN WORK, i'm just sharing my pre-made file to make it easier for you
you need:
busybox
root access
script manager
terminal emulator
1. copy the services.odex file to your internal memory
2. backup current services.odex (found in system/framework)
3. copy modded services.odex to /system/framework/
4. in a terminal emulator type:
su (for root privilleges) thanks mharckk
cd /system/framework
chown 0.0 services.odex
chmod 644 services.odex
5. run the official v6 supercharger script from here http://forum.xda-developers.com/showthread.php?t=991276
6. wipe dalvik cache and reboot
please say thanks to zeppelinrox http://forum.xda-developers.com/member.php?u=3357461
Can you post any screenshot?
Why do you need a Screenshot?
This is not a new Launcher
Gesendet von meinem LT26i
thanks!! I was too lazy to modify the odex file :laugh::victory:
have anyone tried this yet? Any issues?
can anyone show how to install (detailed) and how to use it (recommended choice)
and also the effect (for xperia s stock launcher)
PrimeDeluxe said:
Why do you need a Screenshot?
This is not a new Launcher
Gesendet von meinem LT26i
Click to expand...
Click to collapse
Ah Really?
But I don't know about this Launcher =w='
sorry.
Hatsunumike said:
Ah Really?
But I don't know about this Launcher =w='
sorry.
Click to expand...
Click to collapse
Simply speaking, that's a script that make launcher isn't redrawed any more and may be faster, smoother,...
Sent from my LT26i using Tapatalk 2
i dont know but when i run the command
chown 0.0 services.odex
i get permission denied
edit: anyway i will try to install the supercharged
I can't do it with kao9, right?
if I want to make it Die-Hard or bulletproof which lines should be modified in the smali file?
I tried to follow the zeppelinrox's tutorial from his supercharger thread but the lines are completely different from what he has mentioned and in your smali file!
.line 13663
const/4 v10, 0x1(0x6) Note that this is for Die-Hard Launcher! To BulletProof it, make it 0x0, HTK 0x2
Click to expand...
Click to collapse
mharckk said:
i dont know but when i run the command
chown 0.0 services.odex
i get permission denied
edit: anyway i will try to install the supercharged
Click to expand...
Click to collapse
sorry guys, before you do chown 0.0 services.odex you need to type in su, which gives you root privilleges. how silly of me
Stero! said:
I can't do it with kao9, right?
Click to expand...
Click to collapse
you can!
diimaan said:
if I want to make it Die-Hard or bulletproof which lines should be modified in the smali file?
I tried to follow the zeppelinrox's tutorial from his supercharger thread but the lines are completely different from what he has mentioned and in your smali file!
Click to expand...
Click to collapse
I changed the value to 0x2 to make it hard to kill
I will post a screenshot soon
Oh well! can you make it a die hard launcher too then? It always worked better than the HTK for me otherwise I can follow the screenshot too...
i alaready installed this yesterday and it was perfect. now i will try to run the die-hard battery script.thanks.
Tutorial
Dude...can u make it easyer for us?please make a full tutorial with full download links.not sending us to another forum....etc etc..
the full tutorial is on the original thread, so basically u need are these:
1. services.odex (from this thread)
2. supercharger script ( i used update9rc9)
3. script manager or terminal emulator (play store download),
4. supercharger starter kit (just in case bootlop run this first then run the script again) make sure u have backup of your rom
instructions:
1.install script manager or terminal emulator
2. download services.odex, V6_SuperCharger_for_Android-Update9_RC9.sh.pdf, SuperCharger_Starter_Kit_RC7.zip and paste in /sdcard.
3. copy services.odex and paste in /system/framework
4. fix permissions( rw-r--r)
5. run terminal emulator type "su" (without the "")
6. type cd /system/framework
7. type chown 0.0 services.odex
8. type chmod 644 services.odex
9. type sh /sdcard/V6*
10. read and follow the instructions
11. reboot and wipe dalvik cache (anyway its automatic when u choose option 32)
well the odex file only is enough to get a HTK launcher (50% supercharged). I don't think it's a good idea to mess with the ram values with the supercharger script, because the current minfrees are good enough and ICS doesn't need a forced memory management (we got 1gb of ram anyway)
also the best way is to push the file using adb, I tried to replace it in ES File Explorer but it rebooted and ended up in a bootloop.
I booted in recovery and pushed the file again using adb and after that it worked fine.
just my experience/opinion.
SnowOokami said:
well the odex file only is enough to get a HTK launcher (50% supercharged). I don't think it's a good idea to mess with the ram values with the supercharger script, because the current minfrees are good enough and ICS doesn't need a forced memory management (we got 1gb of ram anyway)
also the best way is to push the file using adb, I tried to replace it in ES File Explorer but it rebooted and ended up in a bootloop.
I booted in recovery and pushed the file again using adb and after that it worked fine.
just my experience/opinion.
Click to expand...
Click to collapse
you need to apply the correct permissions
mharckk said:
i alaready installed this yesterday and it was perfect. now i will try to run the die-hard battery script.thanks.
Click to expand...
Click to collapse
We can follow this guide http://forum.xda-developers.com/showpost.php?p=11803458&postcount=10 for the battery or...?
Stero! said:
We can follow this guide http://forum.xda-developers.com/showpost.php?p=11803458&postcount=10 for the battery or...?
Click to expand...
Click to collapse
xperia s has a built-in battery.