Lcd_density - LG Optimus 2x

Hi,
Has any of you tried to change lcd density in build.prop?
Sent from my LG-P990 using XDA App

Tried it myself after successful root.
Setting it to 210 really sharpens things up.
Sent from my LG-P990 using XDA App

lower density is nice but it does give u problems with some programs

tried with lcd density changer from marked... dosen't work ??

dk_iceman said:
tried with lcd density changer from marked... dosen't work ??
Click to expand...
Click to collapse
Didn't know about that app, changed via Root Explorer.
About some apps having problems with lower density, as far as I can see it will just make them "smaller". I still like it better with low (210) lcd_density.

Aduck79 said:
Didn't know about that app, changed via Root Explorer.
About some apps having problems with lower density, as far as I can see it will just make them "smaller". I still like it better with low (210) lcd_density.
Click to expand...
Click to collapse
would you post a guide on how to do it with root explorer

dk_iceman said:
would you post a guide on how to do it with root explorer
Click to expand...
Click to collapse
Use this on your own risk
Quite easy:
1. Root your phone using Superoneclick
2. Install and start Root Explorer
3. Go into /system and tap "Mount R/W"
4. Long press build.prop and tap "Open in Text Editor"
5. Change ro.sf.lcd_density from 240 to 210 or lower (the lower the more zoomed out)
6. Save & Exit
7. Tap "Mount R/O"
8. Reboot phone

Aduck79 said:
Use this on your own risk
Quite easy:
1. Root your phone using Superoneclick
2. Install and start Root Explorer
3. Go into /system and tap "Mount R/W"
4. Long press build.prop and tap "Open in Text Editor"
5. Change ro.sf.lcd_density from 240 to 210 or lower (the lower the more zoomed out)
6. Save & Exit
7. Tap "Mount R/O"
8. Reboot phone
Click to expand...
Click to collapse
That was easy enough... thans
mine was rooted already

Just curious, why u want to have lower density.
Will it make text or image less sharp and nice?

Well, I don't think that it actually gets sharper, but since you zoom out it looks like it, and you can have more Widgets and shortcuts on the homescreens. This can be achieved by using eg. Launcher pro by adding an extra row and column.
Sent from my LG Optimus 2X using XDA App

Uhm, crap!
I did "mount -o remount, rw /system" edited density in /system/build.prop and then "mount -o remount, ro /system" and rebooted now it keeps looping on the bootscreen, now and then it boots to the homescreen for maybe 2 sec then back to bootloop.
Any ideas?

beejizzle said:
Uhm, crap!
I did "mount -o remount, rw /system" edited density in /system/build.prop and then "mount -o remount, ro /system" and rebooted now it keeps looping on the bootscreen, now and then it boots to the homescreen for maybe 2 sec then back to bootloop.
Any ideas?
Click to expand...
Click to collapse
Hard reset (Power + volume down)
Sent from my LG-P990 using XDA App

domi007 said:
Hard reset (Power + volume down)
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Yeah, I noticed that later. Thank you

Related

Changing the LCD Density Post Install?

I need to change my LCD density on my phone (NAND / Warm Donut), but I do not want to reinstall the whole system...is there a way to change the LCD density without formatting/reinstalling Android?
Also what is the best NBH resolution and density combination to use?...I tried 120 density on 240x320 NBH file, but it is 'too big'...I have to scroll down to see stuff. 110 was perfect it seemed for 240x320 except that it left some black space on the edges at times.
Thanks,
-C
su
mount /system -o rw,remount
edit ro.sf.lcd_density in /system/build.prop
mount /system -o ro,remount
then reboot
I am a Windows user. How do I do it in Windows or in the phone. Also my phone is not "rooted" (whatever that means)
crobs808 said:
I am a Windows user. How do I do it in Windows or in the phone. Also my phone is not "rooted" (whatever that means)
Click to expand...
Click to collapse
Our phones are rooted, period.
You have to use adb to do it from windows or linux, or be comfy using vi on the phone (ha.)
so you'd do the remount stuff mentioned above, then
Code:
adb pull /system/build.prop/ro.sf.lcd_density c:\mydata\ro.sf.lcd_density
*edit the pulled file*
adb push c:\mydata\ro.sf.lcd_density /system/build.prop/
mrkite38 said:
Our phones are rooted, period.
You have to use adb to do it from windows or linux, or be comfy using vi on the phone (ha.)
so you'd do the remount stuff mentioned above, then
Code:
adb pull /system/build.prop/ro.sf.lcd_density c:\mydata\ro.sf.lcd_density
*edit the pulled file*
adb push c:\mydata\ro.sf.lcd_density /system/build.prop/
Click to expand...
Click to collapse
Ok thanks...now, what is the best NBH resolution and density value combination to use for the Vogue?
open a terminal "better terminal emulator" on your phone
type
su
mount /system -o rw,remount
Click to expand...
Click to collapse
use astro to browse and edit /system/build.prop
look for the line ro.sf.lcd_density=120
change it to whatever you like save changes.
makes filesystem read only
Code:
mount /system -o ro,remount
restart phone
seriously read Tatnai's FAQ (apparently yours isn't the easiest if it didn't work on your own Vogue) and stop making these useless threads.
berardi said:
seriously read Tatnai's FAQ (apparently yours isn't the easiest if it didn't work on your own Vogue) and stop making these useless threads.
Click to expand...
Click to collapse
Huh? I didn't incorporate anything about LCD density into my tutorial on purpose...my tutorial is about how to install Android via the NAND method...has nothing to do with density tweaking, and I never intended it to.
Also "stop making threads"...? What is this forum for then, because I only post a thread when the search or FAQs do not cover something. Isn't that the point of a forum?
myn said:
Change LCD Density to 110
Change LCD Density to 160
Click to expand...
Click to collapse
If you want any other density edit the build.prop within these files - look for lcd density and change it to what you want. Go into your boot up menu and do "install update"
Do a little reading like everyone else does, studies show it is good for your brain.
if using 320x480, you should use lcd.density of 160.
if using 240x320, most people use something between 110 and 120. I like 110, things are a little smaller, easier to see in messaging, and the eclair dialer and wysie's dialer fit the screen. others like 120, because supposedly it is a little "crisper"; try for yourself. I've played around with 113, 115, -> basically everything between 120 and 110.
if using 320x428 (does anyone use this anymore???) use 160 (I think, I can't even remember anymore).
there is a full discussion of other benefits of different resolutions in the FAQ thread. also, you might want to take a look at the market FAQ post, as it applies.
berardi said:
If you want any other density edit the build.prop within these files - look for lcd density and change it to what you want. Go into your boot up menu and do "install update"
Do a little reading like everyone else does, studies show it is good for your brain.
Click to expand...
Click to collapse
ha...you like following me around the board and insulting me. you have done this now on three threads where i simply ask a question on how to do something, then you state that my post is 'useless'. that really lends itself to good discussion. please re-evaluate why you post things because you are definitely not doing it to help me or answer the original question.
p.s. - i did read the forum and search before i posted. all the instructions so far were how to do it on Linux or how to do it using ADB, neither of which I have at my disposal. The other posters in this thread helped, which I had already stated (post #5 on pg.1) before you even posted, so there was no reason for you to post all all, except to get your insult in I guess. Stop following me around the forum. Now.
crobs808 said:
ha...you like following me around the board and insulting me. you have done this now on three threads where i simply ask a question on how to do something, then you state that my post is 'useless'. that really lends itself to good discussion. please re-evaluate why you post things because you are definitely not doing it to help me or answer the original question.
p.s. - i did read the forum and search before i posted. all the instructions so far were how to do it on Linux or how to do it using ADB, neither of which I have at my disposal. The other posters in this thread helped, which I had already stated (post #5 on pg.1) before you even posted, so there was no reason for you to post all all, except to get your insult in I guess. Stop following me around the forum. Now.
Click to expand...
Click to collapse
It is my opinion man, can't we all post our own opinions wherever we want? these were your words afterall..
As for you reading the forum and not finding the answers, well apparently you can't read very well. Trust me I am FAR from a coder / developer / hacker - I learned how to do it simply by reading other posts. If you do a little reading you can get far.
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
tmcfarland said:
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
Click to expand...
Click to collapse
Are you using one of those files I linked to? I found it easiest to do it in windows on a pc. If so, open up the .tar file and look for build.prop - open that and make the change. Close the file and it should allow you to save changes. Put that on an sd card in your phone reboot and install update and you should be good.
berardi said:
Are you using one of those files I linked to? I found it easiest to do it in windows on a pc. If so, open up the .tar file and look for build.prop - open that and make the change. Close the file and it should allow you to save changes. Put that on an sd card in your phone reboot and install update and you should be good.
Click to expand...
Click to collapse
That did the trick ... many thanks!
crobs808 said:
I need to change my LCD density on my phone (NAND / Warm Donut), but I do not want to reinstall the whole system...is there a way to change the LCD density without formatting/reinstalling Android?
Also what is the best NBH resolution and density combination to use?...I tried 120 density on 240x320 NBH file, but it is 'too big'...I have to scroll down to see stuff. 110 was perfect it seemed for 240x320 except that it left some black space on the edges at times.
Thanks,
-C
Click to expand...
Click to collapse
Either use an androidupdate.tar, or, if you need to do it on your phone:
Open BetterTerminal.
1. Type 'su', enter.
2. Type 'mount -o remount,rw /system', enter.
3. Type 'vi /system/build.prop'.
4. Scroll down to the build.prop section. Put the cursor where you want to modify.
5. Hit 'i' to go into edit/insert mode.
6. Hit backspace to delete the comment "#" of the line you want..
7. Add a # to the old density line. You can safely use the dpad to move in edit mode.
8. Hit escape (Hold Center Button and type '1'), to leave edit/insert mode.
9. Type ':wq', then enter, to write and quit.
10. Power down (the proper way, hold red button, hit power off....).
You can always hit escape (Center-1), then ':q<enter>' to quit without saving if you mess up. Then start over.
I just did this, so it works.
Vi has two modes, edit mode, and command mode. If you don't know what mode you're in, always just hit ESC (Hold center button, type the number '1') to return you to command mode.
BetterTerminal is kinda screwy, the cursor covers the letter before it, so you have to keep that in mind.
Personally, I prefer 120, it's nice and clear. It originally was changed from 120 to 110 because Google Maps would freeze on the 3.4.0? update and a density of 120, however 4.0.0+ seems to fix that. I don't know why Myn doesn't go back.... Google maps works perfectly fine for me now on 120.
jnadke said:
Either use an androidupdate.tar, or, if you need to do it on your phone:
Open BetterTerminal.
1. Type 'su', enter.
2. Type 'remount -o remount,rw /system', enter.
3. Type 'vi /system/build.prop'.
4. Scroll down to the build.prop section. Put the cursor where you want to modify.
5. Hit 'i' to go into edit/insert mode.
6. Hit backspace to delete the comment "#" of the line you want..
7. Add a # to the old density line. You can safely use the dpad to move in edit mode.
8. Hit escape (Hold Center Button and type '1'), to leave edit/insert mode.
9. Type ':wq', then enter, to write and quit.
You can always hit escape (Center-1), then ':q<enter>' to quit without saving if you mess up. Then start over.
I just did this, so it works.
Vi has two modes, edit mode, and command mode. If you don't know what mode you're in, always just hit ESC (Hold center button, type the number '1') to return you to command mode.
BetterTerminal is kinda screwy, the cursor covers the letter before it, so you have to keep that in mind.
Personally, I prefer 120, it's nice and clear. It originally was changed from 120 to 110 because Google Maps would freeze on the 3.4.0 update and a density of 120, however 3.4.1+ seems to fix that. I don't know why Myn doesn't go back....
Click to expand...
Click to collapse
Man you are a vi hacker!!
The only reason I am using 110 (soon to be 113) is because the eclair dialers cut off the top of the numbers with 120. Some themes however don't have the eclair dialer so 120 is completely perfect for it.
This process of changing density will become inherently easier come the next release of Warm Donut . More to come as I make more progress.. I will leave it at that.
myn said:
Man you are a vi hacker!!
The only reason I am using 110 (soon to be 113) is because the eclair dialers cut off the top of the numbers with 120. Some themes however don't have the eclair dialer so 120 is completely perfect for it.
This process of changing density will become inherently easier come the next release of Warm Donut . More to come as I make more progress.. I will leave it at that.
Click to expand...
Click to collapse
Astro wouldn't save the changes to build.prop Even after su/remount (That's because only BetterTerminal gets su privileges, not Astro)
Yeah, I've learned to love vi, mainly because searching is similar to sed, unlike that stupid emacs.
I actually use 123, I'm greedy
the 1, 2, 3 don't bother me in the least, you can still press them and I rarely dial numbers manually
tmcfarland said:
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
Click to expand...
Click to collapse
Ditto - I tried doing it this way after reading a post on page like 153 (or there abouts) on the main Myn Warm Donut thread to no avail. Definitely doesn't work.

Change Screen Resolution on legend ???

is it possible to change the resolution of htc legend..........i tried lcd density but no use ...i am using azure cyanogen mod 6.....
i tried to edit the build pro..but no use
some one help me.......
Change Your Screen Resolution on HTC Evo 4g
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
@TheGrammarFreak
What is the resoultion of your screen now?
qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
I dunno how I'd work it out, sorry.
Ah...
I think I've found the first of many flaws with this, and it was mentioned in the EVO 4G post. Some apps ignore this and use the old resolution, and thus don't fill the screen (see attachment)
As you can the the status bar goes a lot wider than the app. The status bar is the full width of the screen.
Other problems arise too, a reinstall of the app doesn't help, and some apps just end up completely screwed...
qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Cool, thanks grandioso
On a slightly different note I've found that changing the value to 130, and using the 5 icon rows feature of launcher pro, is quite nice.
grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Thanks for clearing that .
There are some problems, but if you want to try it out, you can flash the update.zip I've just made.
160lcd.zip takes you back to default and 120lcd.zip makes your screen resolution higher.
@Briix
Can you make update for 130, like TheGrammarFreak suggested
I'd make one but I'm currently struggling to sign my .zip
EDIT:
Done it, just testing then I'll upload. I also notice that ROM Manager is one of the apps that ends up being screwed by this mod...
EDIT 2:
Wow, lots of edits. Anyhoo, 130lcd right here:
really nice
TheGrammarFreak said:
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
Click to expand...
Click to collapse
thanks man its working...........
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Explicitly my zip? Or any of the zip's in this thread?
No wipe is needed.
Also, this method is inherently flawed. Some apps just don't use the edited resolution. Unless a way can be found to force these apps to scale up then there will always be ugly moments.
One of the things that I've found to not work is the HTC-IME mod. So is it worth it? That for you to decide... Lol
Sent from my Legend using XDA App
I mean yours or Briix' - are there any others ?
I don't want to edit the file manually if I don't have to
grandioso said:
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Click to expand...
Click to collapse
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
whitetigerdk said:
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
Click to expand...
Click to collapse
I'd love to, but I can't at the moment, I'm at school and didn't bring my laptop. Unless someone beats me to it I'll make one in about an hour and a half; when I'm home.
I did try 140 myself but I didn't think it was worth it. I use 5 icon rows in launcher pro and the widgets started overlapping again. Like they did in the default resolution.
Sent from my Legend using XDA App
I'll wait..
Would be great though if WF & Clock Widget (The Sense look Clock) would adapt to new screen and fill it out..
Totally sweet indeed..
Yeah, if I knew more about android I'd look into forcing apps to scale up. I'm not sure if it's even possible, but hey.
Sent from my Legend using XDA App

Camera Application without shutter sound.

here is the LG Optimus Black ArcCamera.apk without shutter sound and focus sound at all.
NOTE: you can`t enable/disable it....it`s disable by default.
I installed the app, and the sound still wasn't disabled.
rimatox said:
I installed the app, and the sound still wasn't disabled.
Click to expand...
Click to collapse
strange. since I have no shutter sound anymore...
I guess you thought about uninstalling the original ArcCamera.apk before installing this version right?
keep me on current.
how did you install the camera? i tried to run it and it failed to install......
I've already uninstall my stock camera using titanium backup....
i04055 said:
how did you install the camera? i tried to run it and it failed to install......
I've already uninstall my stock camera using titanium backup....
Click to expand...
Click to collapse
running adb shell type this command:
type "su" and press enter
type "mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system"
type "chmod 777 /system/app"
type "exit" and "exit" again
with a file manager go on /system/app and delete ArcCamera.apk
after that in adb run command: "adb push ArcCamera.apk /system/app
it`s going to autoinstall. enjoy
P.S. let me know if the shutter sound is disabled indeed, I`m pretty sure it is but someone said it isn`t though
I install the apk using root explorer...
-mount /system/app ro r/w
-copy ArcCamera.apk from sdcard to /system/app
-change permission ArcCamera.apk same as other apk in the folder
-restart my phone
was that the same? but nothing happened...
Try and go to /system/app/ArcCamera.apk. click on it and go to application manager and then click install.
Sent from my LG-P970 using XDA App
spyb0y said:
strange. since I have no shutter sound anymore...
I guess you thought about uninstalling the original ArcCamera.apk before installing this version right?
keep me on current.
Click to expand...
Click to collapse
No, I did not think of that... but anyway now I have and I can't get Adb Shell to work on my computer, I need to use Terminal Emulator on my phone :/ could you make a tutorial for that?
rimatox said:
No, I did not think of that... but anyway now I have and I can't get Adb Shell to work on my computer, I need to use Terminal Emulator on my phone :/ could you make a tutorial for that?
Click to expand...
Click to collapse
open emulator and:
type "su" (it will ask you for root permisions, you`ll say yes. if doesn`t ask you it will simply announce you that emulator has been granted super user permision and terminal might get stuck - in this case close terminal, open again and type "su" it will work this time)
type "mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system"
type "chmod 777 /system/app"
exit emulator.
next go to /system/app folder and remove original ArcCamera.apk (long press on it -> Edit -> Delete), after you`ve done this, copy the modified ArcCamera.apk in /system/app, click on it and install it. I hope you will succeed.
After I've done that and try to install modded ArcCamera.apk I get this message "Program not installed"
rimatox said:
After I've done that and try to install modded ArcCamera.apk I get this message "Program not installed"
Click to expand...
Click to collapse
my bad man....are you using stock ROM or NOVA ROM?
if you are using stock ROM than instead of ext4 in the command line you need to use ext3. sorry
now when I try to install it it says "Analyzingerror" :s
rimatox said:
now when I try to install it it says "Analyzingerror" :s
Click to expand...
Click to collapse
i don`t know why are you having this kind of trouble installing the application, for me worked very very easy. wait for others to test it and let`s see if others are having same troubles as you have...
I don't know, but it seem doesn't work for me as well....
hectorrent said:
I did it and the phone doesn't sound the main noise, but the previous little shrill sounds yet
Click to expand...
Click to collapse
yeah i did not remove the focus sound...
so application works.
@hectorrent
how did you install it?
spyb0y said:
yeah i did not remove the focus sound...
so application works.
Click to expand...
Click to collapse
Can you remove the focus sound too? It will be perfect
sent from Optimus Prime
val5 said:
Can you remove the focus sound too? It will be perfect
sent from Optimus Prime
Click to expand...
Click to collapse
I will do it tomorow night.
spyb0y said:
I will do it tomorow night.
Click to expand...
Click to collapse
is it up yet?
val5 said:
is it up yet?
Click to expand...
Click to collapse
yes it is but I did not have time to upload it....i`ll post it tonight. sorry!
EDIT: IT IS ON THE FIRST POST!

Tips - use G button as camera button / lock screen (change key binding)

I found it in a chinese forum (bbs.gfan.com/android-2014369-1-1.html)
I'm sure most people found the G button useless, so it would be nice to change that. The following is my experience with it:
The position of the G button make it perfectly useful as lock/unlock button, you can use it to shutdown as well, but cannot use it to switch on the phone, I guess it is electrically hardwired to the power button at the top.
Not too bad for camera, long press it will launch the camera app, but it don't have 2 levels so press it once and it will start auto-focus and take picture immediately, similar to touch and release shutter button in camera app, which mean you can't "dis-engage" a failed focus attempt.
here is the method:
1. make sure you have root and r/w to system partition
2. the file in question is "TWL4030_Keypad.kl", it's in /system/usr/keylayout/
3. before making any changes, copy the file to SDcard as a backup
4. open the file with any text editor, scroll down to 3rd line from the bottom, it should be "key 95 GESTURE"
5. if you want to use it as camera button, change it to "key 95 CAMERA WAKE_DROPPED"
if you want to use it as power/lock button, change it to "key 95 POWER WAKE_DROPPED"
6. save the changes, reboot to see the changes.
Very good.
In fact, I may even use this on nova.
the method is work.
after edit file it create backup file which is name "TWL4030_Keypad.kl.bak"
It works! Great!
worked perfectly thx!
thank u..
this work
hey, i was followed this method but my Optimus Black can't use it .. when i push my Gesture it can't go to camera .. somebody help me ??
My phone still on Original ROM.
After modify to Power/Lock mode, it's work.
but into Shutter mode, doesn't work.
Any idea?
SnoopyZ
digezter said:
hey, i was followed this method but my Optimus Black can't use it .. when i push my Gesture it can't go to camera .. somebody help me ??
Click to expand...
Click to collapse
did u reboot after making the changes?
digezter said:
hey, i was followed this method but my Optimus Black can't use it .. when i push my Gesture it can't go to camera .. somebody help me ??
Click to expand...
Click to collapse
notice you need to long press to start the Camera App. (you should feel the phone vibrate)
or just start the camera app, then press the G button to take a picture to see if it works.
It should be a pretty straight forward modification.
Could it be
"key 95 RECOVERY WAKE_DROPPED" ???
wow, very nice
Very nice. Thanks.
To all who could not manage get it to work: You must take care of file attributes after modyfing the file content ( otherwise it won't work ). It must be CHMOD 644.
( I use SD Maid for this )
It doesn't work for me, i am using pays ROM. Can someone upload the file? Thank u!
Enviado desde mi LG-P970 usando Tapatalk
"key 95 HEADSETHOOK WAKE"
to use headset button
I tried modifying the file and saving it ... but the it always comes up as an error and doesn't allow me to save it... any solutions???
you need to have your phone "root" AND mount system partition as read and write
fjsw said:
you need to have your phone "root" AND mount system partition as read and write
Click to expand...
Click to collapse
Hey my phone is rooted, how do I mount system partition a read and write ? Sorry I'm a noob
if you use ES File Explorer, goto setting, select 2 checkboxs "Root Explorer" and "Mount File System"
if you use root explorer, change directory to /system, then press "Mount R/W" button
yabgo said:
"key 95 HEADSETHOOK WAKE"
to use headset button
Click to expand...
Click to collapse
Sorry to ask but: what is the "headset button" and what is it good for?
Thanks,
Kusie

Request-flashable jellybean boot animation

I tried to copy the jb boot animation on my ics rom but got an error. I know that others would like have it too both on ics and other job roms. thanks in advance..
Sent from my Nexus S using xda app-developers app
darius0519 said:
I tried to copy the jb boot animation on my ics rom but got an error. I know that others would like have it too both on ics and other job roms. thanks in advance..
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Already done it mate, here you go:
http://forum.xda-developers.com/showthread.php?t=1773329
If you're looking to integrate this into your ROM, just drop it into /system/media (without unzipping it)
Hope this helps.
Tried to copy but got an error. Is there anything I missed? Thanks
Sent from my Nexus S using xda app-developers app
darius0519 said:
Tried to copy but got an error. Is there anything I missed? Thanks
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Your file manager needs to have root access. This looks like it should work, if not try Root Explorer, which whilst it is paid for, is well worth the money and you'd be amazed at how often it comes in handy.
You must make the /system directory read/write. You can do this is ES File Explorer (assuming you have root) by hitting the menu button, click on "Settings", and scroll to the very bottom. The second option from the bottom is "Mount File System", and the subtext shows this is to "Mount / , /system as writable." Check this option, then try copying your file.
MercilessLTD said:
You must make the /system directory read/write. You can do this is ES File Explorer (assuming you have root) by hitting the menu button, click on "Settings", and scroll to the very bottom. The second option from the bottom is "Mount File System", and the subtext shows this is to "Mount / , /system as writable." Check this option, then try copying your file.
Click to expand...
Click to collapse
Thanks it worked!!
Sent from my Nexus S using xda app-developers app
No problem. Glad to hear it worked.
If you don't want to mess with /system/media and possibly lose the boot animation that is baked in your rom, drop the bootanimation.zip in /data/local and fix permissions.
sent from the man behind the mask.....

Categories

Resources