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.
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!
Installing Mods on a Defy MB525:
A Guide for the Laymen MacOS User
Read In Rich Text:
https://docs.google.com/document/d/15XYKWyjvfHr4pAV5Wtxlt_4KsM-ykmQ4pvLhOt_mzlM/edit
This began as a personal list/guide for myself since much of the info was scattered across the XDA forum and some other websites. I'm still tweaking the guide on my laptop but if anyone thinks this is useful I'd be more than willing to update it here.
I just have some questions listed below as well as a general wonder if anything I'm doing isn't that efficient. Cheers.
I. Questions:
I.A. What Apps should I use on an unrooted Defy for backup?
I.B. Which SBF do I have? (Out-of-the-box)
http://sbf.droid-developers.org/umts_jordan/list.php
I.C. Is there a way to batch restore APKs on Mac like the Windows APK Batch Installer?
http://forum.xda-developers.com/showthread.php?p=23291051
http://www.droidsector.com/blog/2010/06/23/easy-way-to-install-apk-files-using-android-sdk-for-mac/
I.D. Is it necessary to know what color the lens is? Is knowing the camera module enough?
In the Beginning…
II. Rootin'
II.A. Prepping for Unrooted Flashin'
II.A.1. Copy down your SBF info (See I.A.)
II.A.2. Find out which Defy you have:CatLog
II.A.3. Android Development Bridge (ADB is found in the Android SDK)
Download Android SDK http://developer.android.com/sdk/index.html
Drag her into a location such as Applications/Android (The location is of your choice) & unzip. Open the newly unzipped folder "android-sdk-macos" then open "tools."
In Terminal drag and drop "android" located in tools so the command looks like:
$YOURPATH/android-sdk-macosx/tools/
We will write a shortcut so that ADB can be accessed anywhere. In terminal enter:
$ open ~/.bash_profile
.bash_profile should have been opened in a Text editor. At the bottom enter the following(Remember to replace "$PATHto/xxxx" with a drag and drop of the directory):
export PATH=$PATHto/platform-tools:$PATHto/platform:$PATHto/tools=$PATH
i.e.
export PATH=/Users/BobDole/Android/android-sdk-macosx/platform-tools:/Users/BobDole/Android/android-sdk-macosx/platform:/Users/BobDole/Android/android-sdk-macosx/tools=$PATH
Save the file and jump back into Terminal. Reload the sucker:
$ source ~/.bash_profile
In Terminal open up the SDK by typing:
$ android
Press enter. this will launch the SDK Android Manager. Find the folder named, "Tools;" tick it and click the install button.
Sources: http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
II.A.4. Create a folder on your Mac to organize all your Android files. i.e.
/Users/BobDole/Documents/MotoDefy/
II.A.5. If you have been using your Defy, you will probably want to save your text messages, phone calls, photos etc. Make , non-root Apps and do a manual backup:
SMS Backup
Call Logs Backup & Restore
Source: http://wiki.cyanogenmod.com/wiki/Mo...efore_you_do_anything_.E2.80.94_Make_a_backup
II.A.6. Getroot (Contains):
busybox, copy_rootfile.sh, getroot.sh, rage.bin, su, SuperUser.apk
II.A.7. Your MOD (and any extra files)
II.B. Backup (Unrooted)
II.B.1. Optional: Preform SMS Backup & Call Logs Backup
II.B.2. Duplicate entire SDcard via mounting on a Mac.
i. Plug Defy into a Mac
ii. Defy will now have a new notification at the top, open it and select Memory Card Access.
iii. Right click (or option + mouse-click) and select duplicate.
iv. Relabel as you like and put her into you android folder for safe keeping.
Source: https://motorola-global-en-uk.custh.../defy---transfer-files-from-phone-to-computer
II.C. Rooting
II.C.1. Mount SDcard (if not already mounted) See II.B.2.i.
II.C.2. Extract Getroot.zip and drag unzipped contents onto SDcard. Once done, Eject SDcard.
II.C.3. Change Defy's USB connection to "None."
II.C.4. Go to settings - Apps - Development - USB debugging. Turn this on.
II.C.5. In terminal launch adb:
$ adb shell
Launch getroot.sh by typing:
$ sh $SDcardNAME/Getroot/getroot.sh
Re-enter ADB:
$ adb shell
"$" should now be "#." Time to copy some files including the recovery tool (up next):
# sh #SDcardNAME/Getroot/copy_rootfile.sh
Reboot!
# reboot
This should have Clockwork Recovery load on reboot. Continue to II.B. Flashing to add ROMs and Mods like CM7.
Flash Some Color
III. Flashing
III. A. Prepping for Rooted Flashin
All You Need:
Titanium Backup https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
Your ROMs & MODs
Place them on your SDcard in an easy to find place. (Refer to II.B.2. i - ii for Mounting SDcard instructions) I'd suggest placing them at the root unless you plan on keeping them, in which case I'd place them in a folder designated for ROMs and Mods, i.e.
/SDcard/mods
The Mods and ROMs can be removed after flashing them but you may wish to keep them in a folder for quick flashing between ROMs.
III. B. Backup (Rooted)
III. B. 1. Titanium Backup
Open 'er and in the upper right corner select Batch Backup/Restore - All button, the paper with a check mark onto. (See Image 1.)
Under Backup, find Backup all user apps + system data and press RUN. (See Image 2.)
"Pause active apps" should be ticked.
Press Select all.
Press the green check in the upper right corner to begin backup.
III. B. 2. "Nandroid" Backup - via Clockwork Recovery
Reboot your Defy
Upon reboot when the phone flashes the Blue LED, press Volume Down to load the Bootmenu.
Using the volume buttons to navigate; press the power button to select Recovery > Backup and restore > Backup (All). This will take a few minutes (depending on how much is on the phone and SDcard.
Reboot after backup unless you're installing ROMs/mods.
Sources: http://wiki.cyanogenmod.com/wiki/Motorola_Defy:_bootmenu
III. B. Flash! Installing ROMs & Mods
III.B.1.
Go to Bootmenu
Recovery > Backup and restore
Wipe data/factory reset
When done, Wipe cache partition
When done, Instal zip from SDcard >Choose Zip from sdcard>Your ROM/mod .zip
When finished with all the installs select Go Back and reboot the phone.
Source: http://wiki.cyanogenmod.com/wiki/Motorola_Defy:_Full_Update_Guide#Flashing_CyanogenMod
|||. Reverting to Stock SBF
All You Need:
Windows PC **(Most Likely needed as Mac OS & Defy don't seem to get along via USB during sbf_flash's execution.)
Your Defy's Stock SBF (refer to the notes you took for it in II.A.1):
http://sbf.droid-developers.org/umts_jordan/list.php
IV. Apps of Interest
As of 2012-10
Here's the few essential and near-perfect apps:
AdAway
Blocks a great number of ads in and out of Apps. You can also customize which URLs to allow or not (white listed).
SwiftKey
I don't use too many of the type-saving features (which really are great) but the amount of slight adjustments like key height in Landscape gives the text half an inch of space! That and it's seamless (so far).
Apex Launcher
It's hard to find a smooth Launcher. Apex isn't perfect but it's the closest I've come to finding one with the most space-saving, shortcut-creating, quick-loading, customizing-featured launcher.
Turntable FM
Want continuos music… with no ads? Interested in discovering new artists or songs every time you jump on? Turntable FM has "rooms" which are entirely dj'd by it's users. If there's an open spot feel free to jump on and upload your own tunes! Just make sure you stick with the style or else you'll get "booed" off. It's a great lil' music app I've run on my laptop's browser for a good year now. It can be tempting to take part in the community but even just being a listener and grad a song here and there makes this app so great.
Tasks
Need a quick and easy To-Do list? Hook this batboy up to your Google account and have them sync back and forth. It'll only take 15seconds to add a new "task," and if you put the widget on the desktop, it only take one second to mark completed. This also allows for different lists, notes, due dates and reminders (reminders are only on the app, not on Google's.)
Solid Explorer
The only file browser you'll need. can be very simple but offers so much for such a clean app? I'll take two! Oh and you can swipe between two "windows" and drag and drop!
Honorable Mention:
Photoshop Express
Manually adjust the exposure, saturation, tint, "Black & White," contrast and brightness. Crop, straighten, rotate and flip. The basic adjustments to make your image pop. If you want auto settings like InstantHipster, I mean Instagram, try Streamzoo. Lot's of great auto settings but also offer some manual adjustments. This is the closest app I have found to manipulate photos the way I do… which isn't as close as I'd like but the closest yet.
Currents
I haven't spent much time finding a good RSS reader but Currents works just fine for me so I haven't done too much searching. Plus she's pretty minimal and to the point.
V. Notes & Terms
Terminal Commands
($ represents the username you see, merely a place holder for each line of commands you will type into Terminal. Wait for $ or # to appear before entering new commands.)
Device Identification
SOC or BAYER Camera Module?
a. Install CatLog
b. Open & your camera app.
c. Open Catlog and "Search Logs for SOC, BAYER or Camera
d. If nothing is found try reopening the camera app and repeat these steps.
Model Number MB525 or MB526?
a. Open settings > About Phone > Model No.
b. MB525 is a Defy. MB526 is Defy+.
Manufacturing date: Late January or Later are Red?
a. Look at your battery.
b. There's a Thread about what each letter/number means.
SBF info?
Rooting
Android Rooting is the process of devices running the Android mobile operating system to attain privileged control (known as "root access") within Android's subsystem. http://en.wikipedia.org/wiki/Rooting_(Android_OS)
A few have asked so...
To easily set a custom lcd screen setting...
download an app, or
create a file called local.prop containing the line below and save it in /data.
change the number in the line below to suit.
a setting of 320 made everything nice and big for my eyes.
Stock setting in Slimkat is 245.
this setting will over-ride the rom default, without changing the original files.
the below command will copy it there, then reboot to apply changes:
adb push /yourpath/to/local.prop /data
qemu.sf.lcd_density=320
Yep we know, this is nothing new and there are already hundreds of threads detailing this.
Thread closed.
First of all you need root and init d support.
Second i will not take responsibility if something happens to you're phone.
I tried screen shift for a long time, but it kept disabling the set at boot and i got sick of it. Now im using 1600x900 with 360dpi with init d script and could not be happier that it works perfectly.
1. Download the file.
2. Open your preferred file manager with root priviliges.
3. Browse to your download folder and search the file.
4. Remove the txt extension from the file by renaming it.
4. Open the file with text editor and change the resolution and dpi to what you want.
5. Copy or cut the file into /etc/init.d
6. Reboot your phone and boom! You have you're desired resolution and dpi set at boot.
Stock 1900x1080 480dpi file attached.
You can change the values with text editor if you wan't different resolution and dpi.
1600x900 360dpi setting file also included.
Eh?
Code:
adb shell wm density “INSERT_DPI” && adb reboot
SpiritBreak3r said:
Eh?
Code:
adb shell wm density “INSERT_DPI” && adb reboot
Click to expand...
Click to collapse
What about the resolution?
I think that that only changes dpi.
I want more performance with lower res.
Fatsodonkey said:
What about the resolution?
I think that that only changes dpi.
I want more performance with lower res.
Click to expand...
Click to collapse
Code:
wm size "resolution"
wm size reset
wm density "DPI"
wm density reset
Does that also work with every boot?
I thought earlier that it just changed the value and after boot it would not stick.
Maybe i should not make guides since im a bit nooby with this. I just thought that it would make life easier for people like me.
I will just add the adb commands to it and call it a day.