Database Users

how to change lcd density?

any idea how to change lcd density as this app is not working (matt 1.6b)
http://forum.xda-developers.com/showthread.php?t=765639
thx

get a file manager with root access (open root explorer) and enter /system category and tap on it.
tap the button at the top of the screen that says "mount R/W".
now long press on your build.prop and select Open In Text Editor.
now search the line with the lcd sensity. you have to edit the number after the "=".
example:
ro.sf.lcd_density=161

chugga said:
get a file manager with root access (open root explorer) and enter /system category and tap on it.
tap the button at the top of the screen that says "mount R/W".
now long press on your build.prop and select Open In Text Editor.
now search the line with the lcd sensity. you have to edit the number after the "=".
example:
ro.sf.lcd_density=161
Click to expand...
Click to collapse
Whilst it's great that you're actually helping people in order to get your 10 posts, please do it on the newer threads rather than ones from August 2010, and the off-topic forums are also great for getting 10 posts.

/system/build.prop tweaks

I'm not responsible to any damage which is caused by applying any modification listed below to your phone.
Backup
If you made mistake to this file, you phone will not boot in gui, so you should always backup the file before you make any change to it. Just use any file manager to copy the file to your sd card or your pc.
Restore
If you have a Linux machine you can mount the /system partition while plugging in with the purple screen (vol up + vol down + power).
Easiest way: get Ubuntu, put your phone in purple screen, plug in with USB, you will see the system partition at your Ubuntu desktop.
The hard way: if the /system partition is no accessible under purple screen mode (such as in the latest 528 rom), you can use adb push the backup file back, search the web for details about how to use adb.
I'm digging the build.prop, some apps can do some of these tweaks for you, but I prefer typing myself. You need to reboot the phone to take effect.
1. windowsmgr.max_events_per_sec=75
add this new line to make UI more responsive, the bigger the value the more responsive, I've tried 90, too fast, fall back to 75, still quite fast
2. ro.config.hw_menu_unlockscreen=false
change value from "false" to "true" to enable menu key unlocking screen
3. ro.sf.lcd_density=240
change to 225 to increase the resolution of display, as a result, the size of icon on home page and fonts of list (of file manager or contact) become smaller, the smaller the value the smaller size of icon and fonts
4. dalvik.vm.heapsize=24m
increase the value to 32m~48m to increase stability and performance, tested but doesn't see much effect so far

all so if you tried games like nova or brother in arms that have black screen or graphic probs do this they now all work
go to /system/build.prop and edit it to this then close and turn the phone off / on do a build.prop DO A BUILD.PROP BACKUP FIRST ALLWAYS A MUST BEFOR PLAYING AROUND.
once the phone is on go to settings about phone model number and it will say Desire HD.
Then download games for the htc desire hd and it works.
if you want it back to standed just replace it with the backup

i think the suggestions are great!
big thx!!!

thanks for the share

Do I just change the name, where it says build.prop now?

sorry there are still some games that wont work like brother in arms 2 and modern combat black pegasus but all the others work like
splinter cell
sandstorm
n.o.v.a.
and so on

your phone hast to be rooted and use root explorer and go to
/system/build.prop and open and edit the text then reboot your phone

backed up the build.prop and made the changes. On restart it hangs on boot screen (huawei name and logo) I have to remove the battery to switch off. tried connecting to the PC to restore build.prop but it doesnt load the phone memory. Only launches the mobile partner autostart. Also tried updating by adding update.zip to sd card but says signature verification failed. Tried lading general update from huaweidevice.com onto dload directory on sd card, Just shows purple screen on booting with power, vol up and down. Please advice.

adrdsouza said:
backed up the build.prop and made the changes. On restart it hangs on boot screen (huawei name and logo) I have to remove the battery to switch off. tried connecting to the PC to restore build.prop but it doesnt load the phone memory. Only launches the mobile partner autostart. Also tried updating by adding update.zip to sd card but says signature verification failed. Tried lading general update from huaweidevice.com onto dload directory on sd card, Just shows purple screen on booting with power, vol up and down. Please advice.
Click to expand...
Click to collapse
If you have a Linux machine you can mount the /system partition while plugging in with the purple screen (vol up + vol down + power).
Easiest way: get Ubuntu, put your phone in purple screen, plug in with USB, you will see the system partition at your Ubuntu desktop.

Thank you..a mate uses linux so went over and it worked like a charm. I hadn't put the 'm' at the end in 'dalvik.vm.heapsize=24m' but it is sorted now. Thanks again.

Hi there.Is there any value in build.prop file to decrease the time that the screen rotates?I measure that the default time is about 1sec.I want it 500ms or lower.

ive root and root explorer, but when i try to edit the build.prob it says that its read only rom .
whats the problem?
sry for my bad english

In the top right hand corner there is a button which says 'mount r/w' press it and your filesystem will be read/write. Then make the changes to build.prop then press the button again then reboot.

volume headphones?
Where can I find the file corresponding to the volume of the sound through headphones? A similar problem occurred on the ZTE, but was repaired in the new ROM.

Piron said:
Where can I find the file corresponding to the volume of the sound through headphones? A similar problem occurred on the ZTE, but was repaired in the new ROM.
Click to expand...
Click to collapse
/system/etc/hwVolumeFactor.cfg

iamelton said:
/system/etc/hwVolumeFactor.cfg
Click to expand...
Click to collapse
I found the compination of speaker=80 and wired_headset=80 pretty cool.Has anyone found a better setting?

headphone volume
80 is too much. For me the best settings are:
- speaker 75 (default)
- Headphones 70 (higher values ​​will cause the overload of sound)
With this setup is really cool .

Swype
The original ROM is installed Swype keyboard, but not in the Polish language. It is not possible to uninstall Swype and you can not install a new keyboard. Despite the ROOT system does not allow the removal of the keyboard ("cust/hw/ideos_x5/app / "). Does anyone know how to remove the keyboard, or where to replace your dictionary?

adrdsouza said:
Thank you..a mate uses linux so went over and it worked like a charm. I hadn't put the 'm' at the end in 'dalvik.vm.heapsize=24m' but it is sorted now. Thanks again.
Click to expand...
Click to collapse
unfortunately I've got the same problem with you, I changed a file's name in the system/ directory now the phone bricks. I mounted it on mu ubuntu laptop and found that file but it says I have no permission to change it back...what should do now?
edit: never mind, I got it solved with sudo. I am a stupid linux noobie.

I just opened the file, but there's no "windowsmgr.max_events_per_sec" in it, i found the rest (2-4), does someone know why?
Edit: after applying the B160 ROM, i found this line, works great

[GUIDE] How to enable Swiftkey on Kindle Fire

UPDATE: updated instructions for Swiftkey X version 2.2.0.35 (released 11/18/2011) and later.
UPDATE 2: added known values for some other keyboard apps.
UPDATE 3: added warning, split the copying and chown/chmod step into two separate steps.
These instructions assume:
You've already rooted your KF and have ADB access.
You have the adb.exe debug shell installed. This is included with some rooting kits, or you can install the Android SDK (software development kit) from Google and get ADB straight from the source. The examples assume you have a directory called "C:\Android" where adb.exe is installed but yours may be installed elsewhere.
You've got some way of installing the Swiftkey X app, either by installing Android Market or by sideloading the apk.
You're using the purchased version of Swiftkey X (not the tablet version, not any beta or free version that might be out there).
You've got a SQLite editing software (or can use "sqlite3" itself); the instructions below use the free SQLite Database Browser 2.0 which can be downloaded from Sourceforge; just Google for "sqlite browser" (sorry as a n00b I can't post links).
WARNING: use these instructions at your own risk! Modifying, removing or incorrectly setting the permissions on the settings database can result in a non-booting device!
ALTERNATIVELY, you can use various Android apps to edit the database on the device without using ADB, and skip many of the steps below. Posts further down this thread has some recommendations for such apps. Two caveats if using such an app: make sure it doesn't alter the settings.db file ownership or permissions, and be very cateful when modifying the database entry, as there is a tendency for the keyboard or cut-and-paste to "helpfully" insert spaces or change capitalization.
If you try and install Swiftkey as you normally would, you'll get stuck at installation's step 2, which requires you to enable Swiftkey as an input method by redirecting you to the device's input method settings window; in the case of the KF, the option to enable alternate keyboard has been omitted, but as others (thanks PSXtreme and mfisch) have found it's possible to get around this problem and successfully install an alternate keyboard.
Connect the KF to your computer via USB.
When the Kindle tells you that USB storage is enabled, press the "Disconnect" button to disable it (having the USB storage mounted will prevent us from using ADB to copy to the sdcard directory).
Open an ADB shell and use it to make a backup copy of the settings database file (settings.db), and then to a directory where you can edit it (we'll use /mnt/sdcard/Download here) (stuff you need to enter below is in boldface):
C:\android>adb shell
$ su
# cd /data/data/com.android.providers.settings/databases
# cp settings.db settings.db.bak
# cp settings.db /mnt/sdcard/Download​
Now enable USB storage by tapping on the KF's top notification bar and then on "USB is Connected / Select to copy files..."
Open the SQLite Browser, and then open the settings.db file you copied by navigating to the mounted USB drive (e.g. D:\Download\settings.db).
Click on SQLite Browser's "Browse Data" tab, and then "secure" from the droplist of tables. Find the row with the entry named "enabled_input_methods" (it's number 19, ID 21 in my file); you may need to widen the columns to see the full name.
Double-click on the entry's "value"; this will open an "Edit database cell" dialog.
The default value of the entry should be "com.android.inputmethod.latin/.LatinIME"; regardless, you want to add ":com.touchtype.swiftkey/.KeyboardService" to it (the ":" is a separator), e.g. changing the value to "com.android.inputmethod.latin/.LatinIME:com.touchtype.swiftkey/.KeyboardService". (Note: if you're installing a different keyboard program, you'll substitute a different value; I found the correct value for mine by downloading the settings.db file from another Android device with Swiftkey already installed.)
UPDATE: for Swiftkey X versions 2.2.0.35 (released 11/18/2011) and later, the value to be added is ":com.touchtype.swiftkey/com.touchtype.KeyboardService", so the resulting enabled_input_methods value is: "com.android.inputmethod.latin/.LatinIME:com.touchtype.swiftkey/com.touchtype.KeyboardService"
UPDATE 2: here's a list of known values for various keyboard apps:
Swiftkey (paid version): com.touchtype.swiftkey/com.touchtype.KeyboardService
Swiftkey Tablet (paid version): com.touchtype.swiftkey.tablet.full/com.touchtype.KeyboardService
Swype: com.swype.android.inputmethod/.SwypeInputMethod
SymbolsKeyboard & TextArt Pro: com.mobisters.textart.pro/.AsciiTextArtKeyboardPro
SlideIT: com.dasur.slideit/.SlideITIME
Graffiti Pro: com.access_company.graffiti_pro/.Graffiti
FlexT9: com.nuance.flext9.input/.IME
Beansoft Thumb Keyboard: com.beansoft.keyboardplus/.LatinIME
Hacker's Keyboard: org.pocketworkstation.pckeyboard/.LatinIME
Simeji: com.adamrocker.android.input.simeji/.OpenWnnSimeji
After you've changed the entry and double-checked you got it right, hit the "Apply Changes" button, close the dialog, and save your changes to the settings.db file. You can now close the SQLite Browser.
Disable USB storage again by hitting the "Disconnect" button on the KF.
Back in the ADB shell, copy the modified settings.db file back to its original location:
# cp /mnt/sdcard/Download/settings.db .​
Still in the ADB shell, fix the file owner and permissions (IMPORTANT! skipping this step can prevent your KF from booting properly!):
# chown system.system settings.*
# chmod 660 settings.*
# ls -l
-rw-rw---- system system 22528 2011-11-17 21:04 settings.db
-rw-rw---- system system 22528 2011-11-17 17:30 settings.db.bak​(The last command just confirms your handywork.)
Reboot the Android device using the ADB "reboot" command:
# reboot​
Once rebooted, you can proceed with the Swiftkey installation. When you reach step 2 of the installation and it directs you to the KF input settings window, you can return from settings window and if you've correctly modified the settings it won't complain that you haven't enabled Swiftkey, and you can go on with the rest of the installation process.
After finishing the install, long-press on a text field to bring up the "Select input method" pop-up menu, which will allow you to switch between the Kindle keyboard and Swiftkey X.
Voila!

I love Swiftkey on my phone but damn this looks so complicated. Thanks though for getting it to work on our devices.

Sooner or later someone will write a script or an app to make it easy.

Interesting timing. A new version of Swiftkey X was released this morning that changed the input methods path; I've updated the instructions above.
If you updated Swiftkey and found it no longer working, as I did, all you need to do is edit the settings.db file using the procedures described above, and reboot the device, after which you can select Swiftkey X as an input method again.

Can you unroot after completing this guide and still keep Swiftkey? Or, in other words, can I temporarily root my KF just to install Swiftkey?
Thanks!

vtluu, why not the tablet version of Swiftkey?

scrotty, yes you can unroot your KF after--I've done that so I can play Amazon videos--and Swiftkey will keep working just fine.
Why not the tablet version? The mobile phone version just happens to be what I have purchased. I might eventually get the tablet version but I find the phone version works pretty well, and in landscape mode the keyboard isn't too wide for my thumbs and I don't find myself needing a split keyboard.

vtluu said:
scrotty, yes you can unroot your KF after--I've done that so I can play Amazon videos--and Swiftkey will keep working just fine.
Click to expand...
Click to collapse
Cool. I decided to use Voodoo OTA RootKeeper for now, but it's good to know a full unroot is viable.
vtluu said:
Why not the tablet version? The mobile phone version just happens to be what I have purchased. I might eventually get the tablet version but I find the phone version works pretty well, and in landscape mode the keyboard isn't too wide for my thumbs and I don't find myself needing a split keyboard.
Click to expand...
Click to collapse
That's exactly what I was hoping to hear!
Thanks!

This works great.
Maybe a list of what should be added for different keyboards in the first post?

Excellent! Waiting on my KF, was hoping someone would have SwiftKey working. Thank you!
//Tapatalk//

Anyone have the value for the Tablet version of swiftkey? It isn't the same as the phone version and I can't install the Tablet version on my phone to check it(it won't let me). Any help is appreciated.

Just figured out the value for Swiftkey X Tablet (v 2.1.0.223):
com.touchtype.swiftkey.tablet.full/.KeyboardService
Not sure (didn't test yet), but it's probably com.touchtype.swiftkey.tablet.full/com.touchtype.KeyboardService for the newer version [EDIT: confirmed by scrotty]

Nice work! Swiftkey is my favorite!!

brian112358 said:
Not sure (didn't test yet), but it's probably com.touchtype.swiftkey.tablet.full/com.touchtype.KeyboardService for the newer version
Click to expand...
Click to collapse
Confirmed. I just purchased Swiftkey Tablet X v2.2.0.38 through the Marketplace and used the value you hazarded above successfully. Yay!

By the way, with Swiftkey Tablet X, I did not get the number pad in the middle when in landscape mode.
On a hunch, I figured that this was due to the KF's resolution. So I installed the free LCD Resolution app from the Marketplace and set the pixel density from 160 (KF default) to 155. That was sufficient to get the number pad to appear.
WARNING: I tried to set the density to 159 at one point (just to set if I could get it as close to 160 as possible). That value seemed to prevent the KF from restarting (stuck forever at "Kindle Fire")! Thankfully, I had not selected the "apply setting on boot" option in the resolution app and so a simple reboot restored to the default 160 pixel density and the KF started properly. Whew!

I'm waiting for a easier way to do it with out risking so much cause knowing me I would mess up something. Keep of the good work
Sent from my Kindle Fire using Tapatalk

Updated: added values for various other keyboards, copied from Swype keyboard thread.

Any ideas if something similar would work on the Nook Tablet?

Very usefull, thank you bro!

downsay said:
Any ideas if something similar would work on the Nook Tablet?
Click to expand...
Click to collapse
If the NT has the same limitation (i.e. no UI to allow alternate keyboard) I would imagine the same procedure could work, yes. That assumes B&N hasn't screwed around with the text input field code to prevent you from selecting between enabled keyboards (via long-press on text intput field).
Only one way to find out... good luck!

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 ?

[*GUIDE*] Bypassing that seemingly unsurmountable Google Sign-In

Alright all you legacy device lovers, lol, go get your HTC Mytouch 3G devices (probably all sapphire devices, haven't tried on others) that are stuck on that annoyingly persistent Google Sign-In screen outta of the junk drawer and get ready to get some use out of it. I've really only seen a few solutions, touching the four corners, lol, really? never seen that work but its everywhere so it must have at some point, and some other vague or ineffective methods. I have done this over and over just to make sure it wasn't some sorta fluke or lucky button press. That being said i no longer have the devices cause i was unlocking it for a friend that used too many wrong pin codes, so if you see some mistakes, plz let me know.
But first, let me cover my a**, lol
I AM NOT RESPONSIBLE FOR ANY BRICK, BROKEN, EXPLODING, OR TRANSFORMING DEVICES.
USE THIS GUIDE AT YOUR OWN RISK. YOU ARE HENCEFORTH INFORMED.
LMAO, Alright now that's over with. I can say that, although seemingly complicated, if you mess this up then you should have left it in the junk drawer cause its pretty hard to mess it up. I will also include the steps taken to get custom recovery and cm6 on the device as well. The main thing is getting the right files.
It was running Android 1.6.
View attachment 2167592
These are the files you will need:
1.Rom Manager 2.5.0.4
2.Universal AndRoot 1.5.3
3.Root Explorer
4.Terminal Emulator
5.My html hack.View attachment html_hack.zipl
6.Cyanogenmod 6.1
7.Gapps zip
Put all these files at the root of your sdcard, extract html_hack.zip to the root of the sdcard and insert into phone..Also add at least one picture to the DCIM/Camera folder.
Alright, Now that you have the files lets start the fun stuff.
1. Of course power device on normally.
2. Once at the "Click the Android to start" screen, Press Emergency Dialer in the bottom left.
3. Dial the Test Screen Dialer Code. "*#*#4636#*#*".
4. Touch Phone Information at the top.
5. Press the Menu button when the Phone Info screen pops up and touch View Sim Address Book.
6. If you have contacts stored on your SIM Card, just touch any of them. If not add one by pressing menu i think.
7.When the edit contact screen comes up, click the image at the top left that is the image for the contact
8.The gallery will come up, press the menu button and touch Capture Image.
9.When the camera app opens, click the gallery shortcut in the top right corner.
10, Long press on any of the images in your gallery and touch Share on the right.
11.Press Messaging from the list that pops up.
12. In the Recipient field press any random 10 digit number and in the text field enter "Google.com"
13. Hit send, of course it will not send and give you some network unavailable message. now click "Google.com" in the message you just attempted to send, which will bring you to the Browser.
14. long press the menu button, and in the text field type "content://com.android.htmlfileprovider/sdcard/html_hack.html"
15. Now click the Root explorer link and it'll show a warning about unknown sources, click Settings.
16. Touch the Unknown Sources checkbox and while you are there click Development and enable USB Debugging.
17. click back to the web browser and click Root Explorer again and Install.
18. Once installed open Root Explorer.
19. Browse to your sdcard and click the Universal Androot file and install.
20. Once installed open the app, make sure android 1.5/1.6 Superuser is selected and click the Root button.
21. Now click back till you get to the browser again and install Root Explorer again and open.
22. This time though you should see the superuser dialog pop up. Of course click Allow.
23. Again browse to your sdcard and install Terminal Emulator, and open it. Allow superuser.
24. Alright now for the awesome part, in terminal emulator type:
Code:
su
am start -a android.intent.MAIN -n com.android.settings/.Settings
Which should open the settings menu.
25. Now navigate to the Wireless menu and enable WIFI and select a WIFI connection.
Thats the bypass. alot of steps right, lol, but it works.
26. Now press the back button all the way back to the "Click the Android to start" screen and procede with activation.
alright Now you are in your phone.
27. Go to the stock Market app and download Busybox by Stephen and install the app. Install busybox from the app.
28. Now go back to root explorer and browse to the sdcard and install Rom Manager. Open it and Allow superuser.
29. now click Install Clockworkmod Recovery and select the appropriate device. This will probably kick you back to the home screen.
30. Open Rom Manager again and reboot into recovery.
31. From CWM Recovery select install zip from sdcard and select the Cyanogenmod 6 zip file. Let this complete then reboot. This will of course take a while.
32. Once booted back up click the android then skip and skip. Then confirm the location stuff.
33. Open Rom Manager again and reboot into recovery and pick install zip from sdcard and select the gapps zip and install.
34 Once it's finished, reboot and you are all set. Root, Busybox, CWM Recovery and cm6 with google apps is yours. Congrats.
Buddhaja