Database Users

LCD Density changer - Not saving after reboot

Hi all,
Just wondered if anyone had any joy with the LCD Density changer remembering your updated density after a reboot.
If I re-power the device, it always returns to the stock 240 despite me clicking "Save" at 180.
It's getting slightly frustrating as the reason I paid for the app was to avoid having to re-do it everytime.
Anyone had any success getting it to remember? I rooted via Z4root, so I'm not sure if it's related to this method of rooting?
Thanks in advance.
If not, can someone tell me a step by step guide on how to hard-edit the density? - Thanks!

You have to go to settings and select "Save density as system density", then go back and save again on main screen.
You see a message saying it was saved as system settings and well keep after reboot or something similar.
all the best,
Joao.

awsome
I just did the exact same thing, also using z4root Only I also pressed the physical menu button while inside the lcd density changer app --> settings --> set saved density as system density ..or something like that (I don't have my tab with me atm). I hope this was helpful

Cheers guys - sorted at last. Much appreciated.
Hope the Galaxy Tab gets some love with some custom ROMs soon. Seems the Advent Vega is getting all the attention at the moment when I feel that the Samsung, with a few tweaks and bloatware gone - could be even more impressive than it is now!
Cheers all!

also, be sure to choose the permanent root option in z4root, or else your root will disappear on reboot

Any good screenshots where you guys take advantage of a higher density on the tab? (Sorry if OT)

Mate - just edit the build.props file in the system folder using root explorer or whatever
I have mine set for 200 and theres no need to muck about with apps of any kind... literally, just change 2 letters and youre good to go:
1. Download and install Root Explorer from Android Market.
There are other file managers for root users available, but this is one I use and what the rest of this tutorial is based on.
2. Open Root Explorer on your Tab, scroll to the bottom, and tap the system folder.
3. Tap the Mount R/W button at the top of the screen to gain read-write access to the files.
4. Long press on the build.prop item in the list.
5. Select Open in Text Editor from the pop-up menu that will appear.
6. Locate the line that reads ro.sf.lcd_density = 240. Delete “240″ and input another value in its place.
7. Tap the Menu button on the Tab.
8. Tap Save & Exit from the toolbar that will appear on the bottom of the screen. A backup of the original build.prop will be created automatically.
9. Tap the Mount R/O button at the top of the screen to return to the previous read-only state.
10. Exit Root Explorer and reboot the Tab to see the changes.
11. Repeat steps 2-10 as needed. Set the density to 240 to go back to the stock DPI.

AmeriCanAndroid screen size issue

so i just flashed the AmeriCanAndroid rom and everything is running smoothly. the only issue is that the screen is very small. like the notification bar is so small i can hardly see it. the lock screen is a little bigger then a US stamp. i searched the original thread but there are over 1500 pages and the search function yeilded no results . so how do i fix the screen size?

The very first page of ACA thread says
"-Starting with 080111 and later, users can edit /sdcard/android/startup.txt prior to booting to adjust LCD_DENSITY, GPS_ZONE, and DATA_SIZE (data.img)
(ie: the default lcd_density of ACA is 167. Edit the lcd_density= value to 240 to get standard sized icons and fonts)"
The part you're looking for is to change the value to 240.
I do agree, its a plague to look through that thread and search ain't no help if you don't search right

RE: Wrong Section
Hi...please put this in the questions and answers section...iron fist will be on you ...here are some solutions I found by simply using the search:
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!
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!
hope this helps you out

Or if that doesn't work, go to spare parts and uncheck "compatibility mode" then reboot phone

Pansi SMS screen size issue
I am using american android 2.3.7.
I have installed Pansi SMS application for messaging but some how it is not coming on the fullscreen of HD2. It is just capturing upper middle part of the screen Neither am i able to open the settings of Pansi SMS. Even the windows key is not working to open its setting.
How can i resolve this.
Is there any other SMS app as good as PANSI ?

Free 50 GB Box Account HELP

I followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?

yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?

bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.

bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.

ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.

This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.

be careful, backup buid.prop and restore it after creating Box account.

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse

I am having no luck finding a way to get root access from a computer.

deleted post
user error

The tumbleweeds are big around here

There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/

But is there an app to copy my file over from my computer?

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug

I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.

yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.

jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...

its taking forever to install SDK

This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.

yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?

How to turn the Droid X into wifi mini tab without crippling your cell radio.

How to turn the Droid X into wifi mini tab without crippling your cell radio.
Requires Root
This write up is to guide people who have moved on to other phones but what to use their good old Droid X for a wifi device. Many people have just frozen or uninstalled the dialer and messaging apps, but this is going to an unnecessary extreme. Other people have used airplane mode, but this is a pain because it also disables your bluetooth and wifi. Sure you can toggle them back on, but this doesn't persist after a reboot. This fix allows you to use airplane mode to disable the cell radio, but not the wifi or bluetooth. The extra benefit is that you still have a fully functional phone if you ever need it as a backup.
Step 1. Download a File Manager from the market that allows browsing as root. I recommend ES File Explorer because its free and has a search function.
Step 2. Open the file manager and go to its settings. Find any settings that allow you to browse as root, navigate to the root of the filesystem, and mount the filesystem as rw (Read & Write). If you get a Superuser prompt, click allow.
Step 3. Navigate to the root of the filesystem. If you see folders like "etc" and "system", you are there.
Step 4. Use the search function to find settings.db. On ES, make sure you are searching the current folder and have the filter set to all files. Enter settings.db as the file name.
Step 5. Copy the settings.db file to your sd card. Note the directory you found it in. Usually /data/data/com.android.providers.settings/databases.
Step 6. Download SQLite Manager from the market. Open and navigate to /sd card and find your copy of settings.db. Click on it.
Step 7. Click on "system" and then long press on the line that says "airplane_mode_radios". Click on update row and edit the value so that it only has the word "cell" in it.
Step 8. Back out to update the file. Re-open it in SQLite Manager and verify your changes. If your changes did not stick, keep trying.
Step 9. Copy the settings.db that you edited on your sd card back to the folder you originally found it in. When prompted to overwrite, allow it.
Step 10. Reboot and turn your wifi on and activate airplane mode. You wifi should stay on. Reboot. Your wifi should come back up right away but airplane mode should still be active.
Edited example settings.db from .605 stock in a zip file. This is not flashable in CWM Recovery! You can use this but it will probably change a bunch of settings back to what they are when you first set the phone up. Better to sbf and then apply this right away before changing any settings.

I just use the app Airplane Mode Wifi which disables data and cell but keeps wifi and bluetooth active.

Lock screen rotation?

Any chance anyone has found settings or an app to get the lockscreen to rotate into landscape mode?
Sent from my [device_name] using XDA-Developers Legacy app

nivag1710 said:
Any chance anyone has found settings or an app to get the lockscreen to rotate into landscape mode?
Click to expand...
Click to collapse
If you have root access enabled you can enable lock screen rotation with any file manager like ES File Explorer or FX Explorer. First grant root permissions to enable access to root partition. Then head to the root partition and open the system folder. In system open build.prop file (all the way at the bottom) using any of the recommended file editors.
Directory path: /system/build.prop
Once in build.prop, hit the edit option, scroll all the way to the bottom, create a new line and add this string:
lockscreen.rot_override=true
Hit save and exit edit mode and reboot device. If it hangs on boot logo screen, just force reboot and it should take.

Syndrome666 said:
If you have root access enabled you can enable lock screen rotation with any file manager like ES File Explorer or FX Explorer. First grant root permissions to enable access to root partition. Then head to the root partition and open the system folder. In system open build.prop file (all the way at the bottom) using any of the recommended file editors.
Directory path: /system/build.prop
Once in build.prop, hit the edit option, scroll all the way to the bottom, create a new line and add this string:
lockscreen.rot_override=true
Hit save and exit edit mode and reboot device. If it hangs on boot logo screen, just force reboot and it should take.
Click to expand...
Click to collapse
I figured you can do it with root, but I haven't tried it. I found that lack of bloat didn't compel me to root the phone yet.
Sent from my [device_name] using XDA-Developers Legacy app

You can probably, root, add that string to build.prop, reboot to make sure it's working properly, and then unroot. Haven't tried that myself as I need root enabled at all times, adaway, ampere (battery meter) and some custom features require it to be activated.