Ok so I installed CWM and rooted. Then I tried Rom Toolbox Lite (as I had done before on my Skyrocket)
I was trying to lower the density a bit. I went to 260(original 320) and now it won't let me go over 280.
Anyone know of another app that can adjust LCD density?
nest75068 said:
Ok so I installed CWM and rooted. Then I tried Rom Toolbox Lite (as I had done before on my Skyrocket)
I was trying to lower the density a bit. I went to 260(original 320) and now it won't let me go over 280.
Anyone know of another app that can adjust LCD density?
Click to expand...
Click to collapse
Just use a root explorer and manually edit the build.prop file. I use ES file Explorer and its built in file editor.
Posted by Mr. Z's Galaxy S3.
zanderman112 said:
Just use a root explorer and manually edit the build.prop file. I use ES file Explorer and its built in file editor.
Posted by Mr. Z's Galaxy S3.
Click to expand...
Click to collapse
Well did that, and now phone won't boot up. Going to reflash stock rom.
Reflash of stock rom fixed the boot and lcd issue and all my apps were still there which was even better
Related
i was just wondering if anyone knows a way to manually install more fonts on the vibrant.
I was wondering the same thing
Search for "FlipFont" in the market.
zinite said:
Search for "FlipFont" in the market.
Click to expand...
Click to collapse
appreciate it. will give it a shot. hopefully it works for non-root.
What if you want to use a font that flipfonts hasn't offered?
EDIT: NM got it, an app for Root users called Type Fresh can backup/ restore system fonts, and can install new fonts with proper permissions. Any TTF font file works, but picking ones that are designed for on screen viewing is best.
sent from my Samsung Vibrant
The_Chrome_Coyote said:
What if you want to use a font that flipfonts hasn't offered?
EDIT: NM got it, an app for Root users called Type Fresh can backup/ restore system fonts, and can install new fonts with proper permissions. Any TTF font file works, but picking ones that are designed for on screen viewing is best.
sent from my Samsung Vibrant
Click to expand...
Click to collapse
thanks! zinite and the chrome coyote
EDIT: i tried the app. i got to the point where i restart the phone but the new fonts do not apply. have you or anyone got this to work right on the vibrant yet? (the chrome coyote)
I tried it as well and also had no success. Font would not apply.
At least you Vibrant users got some "starter fonts" out of the box.
Captivates don't come with any besides the default.
I highly recommend the Helvetica Neue from the Market, btw, especially if you were fond of the Zune interface.
DJ! said:
thanks! zinite and the chrome coyote
EDIT: i tried the app. i got to the point where i restart the phone but the new fonts do not apply. have you or anyone got this to work right on the vibrant yet? (the chrome coyote)
Click to expand...
Click to collapse
creator2456 said:
I tried it as well and also had no success. Font would not apply.
Click to expand...
Click to collapse
Yes. I ran into this problem as well. You need to go to Settings and return your fonts to "Default" and reboot before you will see the changes.
The app works by replacing the default fonts, if the phone is already using a flipfont font then it wont work
The_Chrome_Coyote said:
Yes. I ran into this problem as well. You need to go to Settings and return your fonts to "Default" and reboot before you will see the changes.
The app works by replacing the default fonts, if the phone is already using a flipfont font then it wont work
Click to expand...
Click to collapse
I'll give that a try as it seems like a very reasonable reason why it wasn't working. Thanks for that.
Try my guide: http://www.xxthe3dmanxx.com/AndroidFonts/androidfont.html
It was written for the Moto Cliq but might work on the vibrant.
the3dman13 said:
Try my guide: http://www.xxthe3dmanxx.com/AndroidFonts/androidfont.html
It was written for the Moto Cliq but might work on the vibrant.
Click to expand...
Click to collapse
Just tried it. Did not work. Not sure if I did anything wrong, but I followed directions properly. Phone would not boot past initial Samsung Vibrant screen. Luckily I was able to ADB the .backup out and replace the original.
I just recently put this in the sticky in the general section. I listed the directory where to put the font, reboot, go to the settings and select the font, phone should reboot with the new font added.
I would LOVE IF you could test the directory for me. I bought helvatica through the system, do I think it's correct.
creator2456 said:
Just tried it. Did not work. Not sure if I did anything wrong, but I followed directions properly. Phone would not boot past initial Samsung Vibrant screen. Luckily I was able to ADB the .backup out and replace the original.
Click to expand...
Click to collapse
You need to adjust the permissions of the renamed font files to match the stock fonts or else you'll boot loop
sent from my Samsung Vibrant
The_Chrome_Coyote said:
You need to adjust the permissions of the renamed font files to match the stock fonts or else you'll boot loop
sent from my Samsung Vibrant
Click to expand...
Click to collapse
Ok...I followed the directions and did as they said. So, how does one go about doing this?
I use Root Explorer, as its one of the easiest ways to move system files around your phone.
To save you time looking in /system/fonts the permissions are:
User: Read-Yes, Write-Yes, Execute-No
Group: Read-Yes, Write-Yes, Execute-Yes
Others: Read-Yes, Write-No, Execute-Yes
Using Root explorer, you can navigate to your renamed DroidSans.ttf and DroidSans-Bold.ttf files, long press on them and select "permissions", then make sure the permissions match the stock font's listed above.
I cant express how effective the Type Fresh App was in doing this for me, and saves me a whole ton of hassle renaming everything. Plus its free.
The_Chrome_Coyote said:
I use Root Explorer, as its one of the easiest ways to move system files around your phone.
To save you time looking in /system/fonts the permissions are:
User: Read-Yes, Write-Yes, Execute-No
Group: Read-Yes, Write-Yes, Execute-Yes
Others: Read-Yes, Write-No, Execute-Yes
Using Root explorer, you can navigate to your renamed DroidSans.ttf and DroidSans-Bold.ttf files, long press on them and select "permissions", then make sure the permissions match the stock font's listed above.
I cant express how effective the Type Fresh App was in doing this for me, and saves me a whole ton of hassle renaming everything. Plus its free.
Click to expand...
Click to collapse
Thanks for that. Guess I'll give it a go again later today. I'll try Type Fresh again first, then move to doing it manually.
International Fonts
For more fonts and also international fonts, I did a tutorial on a Moto Droid couple months back, it should be exactly the same for "ROOTED" Samsung Vibrant:
http://nexusonehacks.net/android-hacks/droid-hack-how-to-install-thai-font-on-droid/
What I would like to know is how to write the AKP for flipfonts.
I wanted to pull one of the APKs from the Apps directory, but it seems to to work. I also tried making a backup of the APK with titanium backup, but the zip is empty. It seems the files are protected in some way.
I just wanted to take a look at the structure of the apk so I can use it as a template to create custom font APKs to side load.
If anyone can manage to make a backup of one of the flipfont APKs please explain how you did so.
I installed thai fonts by update.zip no root required.
hello all. first i just want to apologize if this is in the wrong section. i recently purchased the streak and upgraded to stephen hyde's 2.2. i am not really digging the adw launcher and am not happy at all with the resolution. other than that, 2.2 is still awesome. i was wondering if anyone can help me out on trying the make the resolution better so that everything is a little bit bigger. the widgets and the items in the notification bar are so tiny on this monster screen. thanks in advance everyone!
LCD density
You need to be rooted and amend the /system/build.prop file. It will have a line referring to lcd density = 140, change that to 160 (stock) or anything up to 240.
I amend mine using root explorer which is very useful or there are apps in the market to change LCD density I believe.
gingernator007 said:
You need to be rooted and amend the /system/build.prop file. It will have a line referring to lcd density = 140, change that to 160 (stock) or anything up to 240.
I amend mine using root explorer which is very useful or there are apps in the market to change LCD density I believe.
Click to expand...
Click to collapse
thank you gingernator! i tried the methods you mentioned and was unsuccessful. i used astro file manager and got to the build.prop file, but was unable to save when i changed the 140 to 160. i tried the other method where i got root explorer and still wasnt able to make any changes to the build.prop file. i also tried several apps from the market place and one of the seemed to work, but ended up bricking the phone. luckily i was able to get it up and running again, but am scared to mess with the lcd density so i guess ill just leave it. thanks for your help though.
Please keep any questions regarding Stevens 2.2 in the Stevens 2.2 thread please
Thank you
i am on rooted stock ATT 2.2 firmware. I have busybox installed. Tried LCD density changer app from market but everytime i try to adjust the setting, the phone freezes and the only way to start back is by removing the battery. phone starts back up fine at 160 dpi again.
i have tried 180, 200, and 220 all with same results. any ideas what the problem is?
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
MySeLfPT said:
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
Click to expand...
Click to collapse
yeh, i saw that manual method but was afraid to try because i wasn't sure i'd be able to easily recover if there was a problem.
fortunately, i found a different app on the market "LCDDensity!" that works just fine. There is no preview and you have to reboot to make the change, but it does a fast reboot and it works flawlessly.
Thanks for the Help!
mongofrye said:
yeh, i saw that manual method but was afraid to try because i wasn't sure i'd be able to easily recover if there was a problem.
fortunately, i found a different app on the market "LCDDensity!" that works just fine. There is no preview and you have to reboot to make the change, but it does a fast reboot and it works flawlessly.
Thanks for the Help!
Click to expand...
Click to collapse
Tried it n it worked but after a full reboot, it reverts back to normal 160 density
MySeLfPT said:
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
Click to expand...
Click to collapse
I cant seem to find this line in my build.prop
im using AWS 345 build rooted and Ive done this before with previous phone so im familiar with it but ive looked at least 5 times for that line but its nowhere to be found..
is there any other way???
ducehlmg said:
Tried it n it worked but after a full reboot, it reverts back to normal 160 density
I cant seem to find this line in my build.prop
im using AWS 345 build rooted and Ive done this before with previous phone so im familiar with it but ive looked at least 5 times for that line but its nowhere to be found..
is there any other way???
Click to expand...
Click to collapse
If the line doesn't exist, just add it. For some reason many of the stock Streak build.prop's don't have it in there. But, just add it and then you can tweak to your heart's content. That's what I did, and I'm on LCD=200 now.
mellojoe said:
If the line doesn't exist, just add it. For some reason many of the stock Streak build.prop's don't have it in there. But, just add it and then you can tweak to your heart's content. That's what I did, and I'm on LCD=200 now.
Click to expand...
Click to collapse
yea i figured that out but thanks for the tip... i set mine to 190 & i also grabbed ur wallpaper from the Screenshot thread.. so thanks for that too
MySeLfPT said:
If you are using a rooted phone browser to build.prop, mount it R/W (root explorer e.g), and edit it.
You should be able to change it there manually.
In the /system/build.prop file, add this:
ro.sf.lcd_density=XXX (where XXX is the density number you want 160/240/etc)
Save, restart your phone and there you go.
Click to expand...
Click to collapse
What did you use to edit the file?
mid_life_crisis said:
What did you use to edit the file?
Click to expand...
Click to collapse
Root Explorer. That's what I use. It is a paid app, but the best file explorer I've found. I'm a big fan.
mellojoe said:
If the line doesn't exist, just add it. For some reason many of the stock Streak build.prop's don't have it in there. But, just add it and then you can tweak to your heart's content. That's what I did, and I'm on LCD=200 now.
Click to expand...
Click to collapse
Worked for me. On 345 with density=180! Thanks mellojoe!
Try font changer if you don't want to meddle with build.prop.
I have two phones, a Huawei m860 and an m835. They are both basically the same phone, except the m835 has a smaller screen.
I have a CM 7.1 ROM that runs great on the m860 with the larger screen, but is out of scale on the m835 with the smaller screen.
I edited the BUILD.PROP file and changed the LCD.SCREEN.DENSITY from 160 to 120. But when I inject the edited file back into the zip file, ROM Manager says the ROM is bad and refuses to flash it.
Anyone know how to properly recompile the ROM with the edited BUILD.PROP file, so that I can flash it?
You can use an app to change the screen density.
Can you elaborate a little? What app?
1. You can use LCDDensity
2. Or if you don't want to have an app running in the background, you can simply install ES File Explorer and (as you know) go to /system/build.prop and change the density and reboot. This is permanent or until you change it back or flashing the/a ROM again.
Thanks, I was able to edit the /system/build.prop file after flashing the ROM, and that did the trick once I rebooted.
Now though, I've discovered that the screen does not change orientations when I turn the phone as it should. Any have any ideas how to fix that?
-TheGE128
Hi,
Is there any mod to set pixel density to 320.
I have X920D and I run Virtuous Rom
I tried through pixel density apps in play store but with no luck.
You need a kernel that enables /system writing while booted then you can use one of the apps.
Sent from my HTC6435LVW using xda app-developers app
kdahri said:
Hi,
Is there any mod to set pixel density to 320.
I have X920D and I run Virtuous Rom
I tried through pixel density apps in play store but with no luck.
Click to expand...
Click to collapse
1. Boot into recovery
2. adb pull /system/build.prop
3. open build.prop in a text editor and edit the line that says "ro.sf.lcd_density=480" to say "ro.sf.lcd_density=320"
4. save the file
5. adb push build.prop /system/
6. reboot
EDIT: If you use anything between 320 and 480, it will work, but you are going to have issues with market apps not showing up. I personally prefer 400 DPI, but it mucks my market up. Not worth it to me.
BotsOne said:
1. Boot into recovery
2. adb pull /system/build.prop
3. open build.prop in a text editor and edit the line that says "ro.sf.lcd_density=480" to say "ro.sf.lcd_density=320"
4. save the file
5. adb push build.prop /system/
6. reboot
EDIT: If you use anything between 320 and 480, it will work, but you are going to have issues with market apps not showing up. I personally prefer 400 DPI, but it mucks my market up. Not worth it to me.
Click to expand...
Click to collapse
This ^
Also if you have a kernel which enables write-to-system, you can use Solid Explorer to go into /System and directly edit the build.prop and save it.
Though I believe if you switch from 480 to 320, it stops sense launcher from working. Which is why I use nova prime.
sense does not work with 320, you need an senseless rom
thank you all that was helpfull
Sense does work down to about 370, and you can use LCD Density Modder Pro to download a modified version of the play store that thinks you're running 320.