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.
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.
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
I edited the build.prob file change lcd density to 720. now I can't access phone
If you know how to use adb, and have USB Debugging or a custom recovery set up, you might be able to pull the build.prop, edit it on your computer, push it back, change permissions, and reboot to resolve. You aren't able to access your apps or anything like that, I suppose?
es0tericcha0s said:
If you know how to use adb, and have USB Debugging or a custom recovery set up, you might be able to pull the build.prop, edit it on your computer, push it back, change permissions, and reboot to resolve. You aren't able to access your apps or anything like that, I suppose?
Click to expand...
Click to collapse
Am try to that, using DroidExplorer but after editng the build.prop the changes are not being saved. I thing usb debugging mode is disabled and I cant access anything in my phone. my device doesnt show in" fastboot devices"command when I use the ADB
fastboot devices only works in fastboot/bootloader mode and adb works when booted (with USB Debugging enabled) or via most custom recoveries. Did you install a custom recovery or just root? If just root, it might just be easier to return the device to stock and reroot.
3CPO_R2D2 said:
I edited the build.prob file change lcd density to 720. now I can't access phone
Click to expand...
Click to collapse
If you are running any custom rom..extract that zip...copy that build.prop to sd card...now using Root Explorer on your phone copy it and head on to /system...delete the build.prop and paste the new one..and Reboot.
P.S.:Remember to Mount R/W before pasting it.
theprakhar said:
If you are running any custom rom..extract that zip...copy that build.prop to sd card...now using Root Explorer on your phone copy it and head on to /system...delete the build.prop and paste the new one..and Reboot.
P.S.:Remember to Mount R/W before pasting it.
Click to expand...
Click to collapse
Don't think he can use his phone well enough to make that work. according to the way the pictures look, which is why I didn't suggest that one. All apps are going to be like that and it's not something you can scroll around in like you would if you zoomed in on the browser or something similar.
es0tericcha0s said:
Don't think he can use his phone well enough to make that work. according to the way the pictures look, which is why I didn't suggest that one. All apps are going to be like that and it's not something you can scroll around in like you would if you zoomed in on the browser or something similar.
Click to expand...
Click to collapse
Opz..my bad...i forgot that this is only his problem......yup...but still one other option left...he can install the zip of the rom which he is currently using WITHOUT formatting or wiping...just over-writing...It might work..
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)
i installed build prop editor and i saw the option change pixel density
i changed it to 360 and i rebooted the phone and when it rebooted i get force closes and i cant do anything on my phone now...
Any help???Any fix without loosing my apps? cuz i dont want to loose my apps... i have some important things in there...
@gabiabrudan7: you only may reduce dpi, lower 320! So try to restore the old build.prop: if there's a bak-file, you can rename it in TWRP's file manager - otherwise use ADB (if there's access from PC) to move build.prop to PC, change it with an editor, which stores in UNIX-format and move back.
rp158 said:
@gabiabrudan7: you only may reduce dpi, lower 320! So try to restore the old build.prop: if there's a bak-file, you can rename it in TWRP's file manager - otherwise use ADB (if there's access from PC) to move build.prop to PC, change it with an editor, which stores in UNIX-format and move back.
Click to expand...
Click to collapse
thanks for the reply but i already fixed it ... i flashed lollipop mirror and i have no problem now!
thanks anyway!