Hello. I have a problem: I installed the newest The FroyoMOD. Now, when my phone is in horizontal position button "volume up" turns volume... down. In vertical position everything works fine.
I thought, that this might be useful - I switched in file qwerty.kl volume down button with search button, but problem has performed before this.
I did 3xWIPE - It didn't help.
If you find any mistakes in my post - I'm really sorry. English is not my native language.
In horizontal mode the vol.up and down switches. This is normal.
Thank you for your reply, but in horizontal mode Volume Up button turns volume down, Volume Down button turns volume down too so in this mode I can't turn volume up or zoom in camera mode.
As FroyoMOD was based on CM6 for Milestone, I guess this behaviour is controlled by the ro.config.volume_keys_rotation property that I introduced in the past.
See http://android.doshaska.net/cm6prop
You can change it if you edit the /system/build.prop file and set the property value to 0.
(In more recent CM7/CM9/CM10 roms, I've changed it to use persistent property instead of read-only property - persist.sys.volbtn_orient_swap. So in newer roms it's determined by what the user has set in /data/property. So in case of CM7/9/10, what is in build.prop file is just the default value, overridden by the user selected value. In the case of CM7, the property value can be set in Settings>CyanogenMod>Input>Swap volume buttons in landscape. In CM9/10, the corresponding GUI for this option has not been implemented yet - setprop on command line can be used there).
It's interesting. Did you tried any other rom? I recommend FuFu's Fast and Light if you'd like to stick to Froyo or any of kabaldan's CM.
If it persists in another rom, the chances are great it is a hardware failure.
Kabaldan has the proper answer.
Thank you guys, especcialy for you @kabaldan, I set "ro.config.volume_keys_rotation=1" to 0, rebooted phone and everything looks fine. Again, thank you so much
Related
I have tried searching for the answer to this so please do not ridicule me if i missed it!
Is there a way of stopping the screen from being so dim when i press the power button to wake up device if it is locked.
I always lock the device when i am not using it and will quite often press the power button quickly to turn off the display. When i come to use the phone etc i press the power button to get the screen back then press unlock at the bottom of the screen then the unlock half way up the screen, phone unlocked. BUT when the power button is pressed to turn the screen on and the phone is still locked the screen is so dim i cannot see it in bright daylight. Is there a way of making the screen brighter so i can unlock it?
David
simple answer YES!
The registry key here controls the backlight lock level:
HKCU\ControlPanel\Backlight\LockLevel
There REG_DWORD Key called LockLevel can be set between 0-10 (0=0%, 10=100% locklevel backlight brightness)
The system defaults this setting to 0, hence the dim lock display.
I have found however that the value does not stick after a soft reset/reboot, and goes back to default, so i have set a startup .lnk file that runs a reg script to set this value silently on boot for me.... you can do this yourself using the latest taskmanager 2.9 from here: http://www.dotfred.net/TaskMgr.htm (/silent command line parameter was only added in v2.9 so i can run a reg script without the prompts!)
I like to have a bright pin/unlock screen as i like to use the screen as a torch/light by just pressing the power button!!
Enjoy.
Thanks!!
Thanks for the answer to that. I too have been having the same problem, and it has bugged the hell out of me, especially on those bright summer days .
Thanks heaps for that!!!
Sorry for the delay, but many thanks for the answer! Damned annoying that was.
Regards
David
How do i make this .lnk file? What should it say? Where do i put it? etc etc. Sorry for the question but not done any of this before. The reg edit was easy enough but now i am lost.
Cheers
David
Locklevel startup value
_DrG_ said:
simple answer YES!
The registry key here controls the backlight lock level:
HKCU\ControlPanel\Backlight\LockLevel
There REG_DWORD Key called LockLevel can be set between 0-10 (0=0%, 10=100% locklevel backlight brightness)
The system defaults this setting to 0, hence the dim lock display.
I have found however that the value does not stick after a soft reset/reboot, and goes back to default, so i have set a startup .lnk file that runs a reg script to set this value silently on boot for me.... you can do this yourself using the latest taskmanager 2.9 from here: http://www.dotfred.net/TaskMgr.htm (/silent command line parameter was only added in v2.9 so i can run a reg script without the prompts!)
I like to have a bright pin/unlock screen as i like to use the screen as a torch/light by just pressing the power button!!
Enjoy.
Click to expand...
Click to collapse
I also would like to do this, but havent figured out how to create a command line with TaskMgr that will execute at startup - would you share how it is done?
Also, when I set locklevel to any number other than 1, no dimming occurs when I lock my Tilt. I experimented because I thought I'd like a little dimming but not as much as the default - but it seems like it's all or nothing.
I hate the way the Kaiser and/or WM6 insists on spoonfeeding some settings to us, no matter how much we would like to permanently alter them!
peanutome said:
How do i make this .lnk file? What should it say? Where do i put it? etc etc. Sorry for the question but not done any of this before. The reg edit was easy enough but now i am lost.
Cheers
David[/QUOTe
my thoughts exactly..more instructions for this guy too please
Click to expand...
Click to collapse
BUMP - Anyone know how and what to do to make this .lnk file and then how to use it?
David
strange thing. When I adjust this value it messes with my backlight timeout. I normally have this set to 30secs, i.e. the screen goes dimmer after 30 secs. When I adjust the lockout value as described it goes dim after 5-10 seconds. am I doing this right? I wasn't sure if I had adjusted the value correctly.
M
I have searched all over can someone tell me how to get the \silent to work I have taskmanager v2.9 spent the last 2 hours trying to get this to work please give a bother some help
I think the answer is here...well, not an answer but at least an app that claims to do what you're looking for.
This answer may be too basic, but have you tried changing the registry edit and then NOT doing a soft reset, but instead doing a full power off/on? Some registry entries WON'T stick with a soft-reset, but will with a power cycle. The power cycle gives the OS a heads up that it's being turned off and writes things more permanently...
pkley said:
This answer may be too basic, but have you tried changing the registry edit and then NOT doing a soft reset, but instead doing a full power off/on? Some registry entries WON'T stick with a soft-reset, but will with a power cycle. The power cycle gives the OS a heads up that it's being turned off and writes things more permanently...
Click to expand...
Click to collapse
I always power cycle after a reg change (It forces a registry write and a SR doesn't) but it doesn't matter...this reg change doesn't stick after a power cycle for some reason.
EDIT:
BTW, I loaded BrightLock and it works perfectly.
Excellent seems to do what i needed!!! Cheers
David
Fitipaldi1 said:
I think the answer is here...well, not an answer but at least an app that claims to do what you're looking for.
Click to expand...
Click to collapse
snowgum said:
strange thing. When I adjust this value it messes with my backlight timeout. I normally have this set to 30secs, i.e. the screen goes dimmer after 30 secs. When I adjust the lockout value as described it goes dim after 5-10 seconds. am I doing this right? I wasn't sure if I had adjusted the value correctly.
M
Click to expand...
Click to collapse
I am experiencing a similar issue. My normal backlight on battery power is set to 1 minute, but after installing brightlock, it keeps changing to 10 seconds. I really like what brightlock does for me, but not at the cost of dimming the screen when I am trying to read something. Is there a configuration I am missing?
I think I got rid of this annoying “dim” problem without .lnk file and scripting.
See my next post.
Is there a way of stopping the screen from being so dim when i press the power button
I think I got rid of this annoying “dim” problem without .lnk file and scripting.
What I did is the following:
1. Downloaded and installed Taskmanager 2.9 from: http://www.dotfred.net/TaskMgr.htm
2. Opened Taskmanager and went to Regedit
3. Deleted LockLevel folder from HKCU\ControlPanel\Backlight\LockLevel
4. Saved
5. Rebooted the phone.
After rebooting, system recreates LockLevel folder, however, “dim” problem is gone.
Unit still dims the screen, but pressing any key triggers the bright display.
Suggestion: Export registry and backup your device before playing with Regedit.
can some one please re-post brightlock? mediafire link seems to be done and this is doing me nutter
I've got a script launched through a gscript bookmark on my home screen that remaps the volume keys as Back/Home -- and a script that switches it back to the normal volume control. Basic structure is identical to the Ad-Hoc WiFi fix.
Unlike the Ad-Hoc wifi fix that is immediately useable, the remapped hardware buttons require a reboot to go into effect.
Is there any way for this to take place WITHOUT requiring a reboot?
no even if you just use root explorer to change the key layout (easiest way)
you still have to reboot.
To disable the capacitive button lights on the Bionic, edit this file to be 0. It's originally at 255.
/sys/devices/platform/leds-cpcap-kpb/leds/button-backlight/brightness
Keep in mind if you use ES Text Editor it messes up the permissions. You'll have to set it back to rw-r--r--. (Evidently this is optional. It works fine without resetting the permissions)
Can anyone make a script that enables and disables this? Or a widget? I'm not a programmer, just an enthusiast. Also, there is a "maxbrightness" file in there that is r--r--r-- so I'd rather be modifying that one, but I am just happy this brightness file works for now, so I'm not going to mess with it.
Looks like it resets to 255 on boot. I guess I will figure out how to make scripts if nobody responds. It's way past my bed time now that I stumbled onto this.
Edit: To get it to stick (except for boot), after changing brightness to 0, I just changed the permissions on the brightness file to r--r--r-- so nothing can write to it. I wonder if I can get used to never having any backlights. It's not like the buttons move around. They're in the same position they've been in the last 3 months.
Edit: Tasker can run Terminal command lines, so I have made some homescreen shortcuts for shutting off and turning on the lights. For terminal commands, you type:
echo "0" > /sys/devices/platform/leds-cpcap-kpb/leds/button-backlight/brightness
and that writes a 0 to the file, shutting off the lights.
I'm finding it gets turned on by more than just rebooting. There are several events that turn the lights back on, so unless you want Tasker to run the script every 30 minutes or something, you can just make a shortcut to the task on your homescreen and just shut them off when they're annoying you.
The volume buttons can be remapped to other buttons by editing the file /system/usr/keylayout/sec_key.kl. The problem is changing this file requires a reboot to take affect.
I wrote a daemon to allow on the fly remapping. It works by using uinput subsystem to create a virtual keyboard, listening to the real keyboard /dev/input/event1, and sending the mapped keys to the virutal keyboard whenever a key is pressed.
In order to use it, you need to edit the file /system/usr/keylayout/sec_key.kl, removing (or commenting out with #) the first two lines, and reboot. After this step, the volume buttons are ignored. Now run the daemon (as root). The default configuration is to send SPACE/SHIFT+SPACE for VOL-/+ to firefox and the default browser, down/up arrow to tapatalk, and VOL-/+ to everything else.
The daemon opens a named pipe on /app-cache/.uinput-virtual-keyboard-fifo and can be configured using this pipe.
For example, the command
echo profile com.sec.android.app.ve 231 44
Will map the keys in the video editor to CALL (open phone) and Z.
The daemon is at http://my.svgalib.org/android/pgdn
Source at http://my.svgalib.org/android/pgdn.c
Comments are welcome.
You, dear sir, are a genious.
Really appreciate your effort. Works like a charm.
Sent from my GT-N7000 using XDA App
Can you provide for a key remap for the stock camera application? Volume up capture picture, volume down focus mode?
Thank you!
Sent from my GT-N7000 using xda premium
The file with the meaning of the keys is /system/usr/keylayout/Vendor_04E8_Product_7021.kl according to it FOCUS is 211 and CAMERA is 212. Unfortunately, FOCUS appears to do nothing, so if you run the command
Code:
echo profile com.sec.android.app.camera 211 212 > /app-cache/.uinput-virtual-keyboard-fifo
The VOL+ button will take a picture, but the VOL- button does nothing.
(There is currently no configuration file, so this command needs to run everytime the daemon is started).
MatanZ said:
The volume buttons can be remapped to other buttons by editing the file /system/usr/keylayout/sec_key.kl. The problem is changing this file requires a reboot to take affect.
I wrote a daemon to allow on the fly remapping. It works by using uinput subsystem to create a virtual keyboard, listening to the real keyboard /dev/input/event1, and sending the mapped keys to the virutal keyboard whenever a key is pressed.
In order to use it, you need to edit the file /system/usr/keylayout/sec_key.kl, removing (or commenting out with #) the first two lines, and reboot. After this step, the volume buttons are ignored. Now run the daemon (as root). The default configuration is to send SPACE/SHIFT+SPACE for VOL-/+ to firefox and the default browser, down/up arrow to tapatalk, and VOL-/+ to everything else.
The daemon opens a named pipe on /app-cache/.uinput-virtual-keyboard-fifo and can be configured using this pipe.
For example, the command
echo profile com.sec.android.app.ve 231 44
Will map the keys in the video editor to CALL (open phone) and Z.
The daemon is at http://my.svgalib.org/android/pgdn
Source at http://my.svgalib.org/android/pgdn.c
Comments are welcome.
Click to expand...
Click to collapse
Thanks for the information !..great work. Can you provide how to remap the power button for taking pictures with the camera (sorely missed especially for this device due to its size; touchscreen very awkward esp. for 1-handed shots and have been asking a lot for this even tried to do this myself based on SGS2 hacked camera but got nowhere)
Thanks !
You can try with this (untested) daemon which allows for mapping all four hardware buttons:
http://my.svgalib.org/android/pgdn4
You need to disable the buttons by also removing the 102 and 116 lines from the file /system/usr/keylayout/sec_key.kl and rebooting. By default home and power map to home and power on all applications except for camera, where power, vol+ and vol- map to camera button (take a picture).
I've tried to map the volume buttons 4cm down on the left side.
Wont work. Then i tried for another 2 hours to map them to the right side of my note. (under the on/off button).
Didn't work too...
What am i doing wrong? Do i need a screwdriver to execute the script and the buttons?
What i have done as a temporary measure is edit the
/system/usr/keylayout/sec_key.kl
so that i can use volume down button to start camera as well as take pics
Could someone explain in more detail how to run a daemon? Thanks.
[Edit] Solved. I used Script manager to run it as "is executable" as root and at boot up. But I have to copy it to the internal memory to run it, otherwise, "permission denied".
Thanks. really like it but few issues noted
1. For the camera mod as suggested in post 6 - The home button does not work after the daemon is run. Long press works however.
2. The daemon needs to be in internal memory for it to work with script manager. If in sd card it shows permission denied.
Also since its in internal memory, it gets deleted every time at boot and hence have to copy it there every time after boot.
Is there any other app to run the daemon from sdcard ?
Thanks
drgopoos said:
Thanks. really like it but few issues noted
1. For the camera mod as suggested in post 6 - The home button does not work after the daemon is run. Long press works however.
2. The daemon needs to be in internal memory for it to work with script manager. If in sd card it shows permission denied.
Also since its in internal memory, it gets deleted every time at boot and hence have to copy it there every time after boot.
Is there any other app to run the daemon from sdcard ?
Thanks
Click to expand...
Click to collapse
I put the file under /system, and it won't be deleted every time it bootup.
wonghyf said:
I put the file under /system, and it won't be deleted every time it bootup.
Click to expand...
Click to collapse
how about the home button not working ?
has that happened ?
drgopoos said:
how about the home button not working ?
has that happened ?
Click to expand...
Click to collapse
It's working for me.
wonghyf said:
It's working for me.
Click to expand...
Click to collapse
After running the script my home button does not work . Long press works.
Will try to redo everything once more i guess.
wonghyf said:
I put the file under /system, and it won't be deleted every time it bootup.
Click to expand...
Click to collapse
I think the best partition is /data. This partition is ext4, so supports executable, symlinks, etc. And is mounted rw, so it does not need to be remounted for every change.
If you want to make the daemon suid root, it has to be on /system, since /data is by default mounted with option nosuid.
MatanZ said:
You can try with this (untested) daemon which allows for mapping all four hardware buttons:
http://my.svgalib.org/android/pgdn4
You need to disable the buttons by also removing the 102 and 116 lines from the file /system/usr/keylayout/sec_key.kl and rebooting. By default home and power map to home and power on all applications except for camera, where power, vol+ and vol- map to camera button (take a picture).
Click to expand...
Click to collapse
Thanks ! works like a charm ! (finally camera with power button to take picture on note..so many camera mods but no one doing this mod which was so easily available on sgs, sgs2), Thanks !
Can someone post a modded camera apk to take pics with volume or power button?
This mod is awesome!
Thanks!!!!!
Sent from my GT-N7000 using xda premium
Surprised to that this was popping up in battery stat to use some battery....
@Taptalk-GalaxyNote
should be possible to input the passw with the volume control?
my email forces me to lock with strong password. Should be possible to start and script with a remapped button, producing to input the password stored on it and unlock screen?
Thanks a lot.
To enable soft keys, or onscreen buttons, on any rooted ROM based on Android 4.0 ICS or later, simply add the following to the build.prop file: "qemu.hw.mainkeys" and set the value to zero ("0"). The line will look like this in the text file: "qemu.hw.mainkeys=0". Next, reboot your device and upon start up, a row of onscreen buttons will be at the bottom of your screen. Keep in mind that this will not disable the hardware buttons or disable the backlight, please search for another tutorial for that. Also, the buttons will obviously take up screen space so some things may look a little different or be covered up. If you would like to disable the soft keys, change the value of the line to one ("1") in the build.prop file. Be sure that the hardware buttons are enabled, and then reboot.