The Screen unlocks in the "slide to unlock" mode, by just a press of the "= " button. Is it a bug or a feature...? its sort of buggy for me because screen unlocks itself in my pocket. Any one please check and see if its a one-off case of my phone or general???
jy0thish said:
The Screen unlocks in the "slide to unlock" mode, by just a press of the "= " button. Is it a bug or a feature...? its sort of buggy for me because screen unlocks itself in my pocket. Any one please check and see if its a one-off case of my phone or general???
Click to expand...
Click to collapse
its a feature, you can disable it in the build.prop file, i cant remember the line sorry.
Yes It's a feature in ICS as you can slide notification bar down in locking screen.
There is these three different ways to unlock: notification bar, "settings" button and slidelock.
Thanks. But how do I disable it?
Sent from my U8800 using XDA
Use a file manager with root access, go to /system/build.prop and open it with a text editor. I recommend ES file explorer and then es text editor it comes with.
Find the line:
Code:
ro.config.hw_menu_unlockscreen=true
and change it to:
Code:
ro.config.hw_menu_unlockscreen=false
Reboot and it should no longer unlock with menu key. You can also edit it before installing latest aurora rom by editing build.prop with wordpad in windows or gedit in linux.
Sorry. I couldnt find the above lines inside build.prop.
Sent from my U8800 using XDA
Related
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.
This Guide Will Disable Hardware Keys (Home, Menu, Back, Search) Light and make it disabled completely so we can use the on screen button like nexus phone in AOSP based ROM (AOKP/PACMAN/Codefirex)
NOTE: Don't Try This in CM Based Rom because CM don't have any on-screen button mod
For Disable The Hardware Keys Light :
Add The Following code to /system/etc/init.d/90userinit
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
and reboot
For Disable The Hardware Keys Function Completely
Navigate to /system/usr/keylayout/synaptics-rmi-touchscreen.kl (maybe it's touchscreen dependent mine is synaptic,i can't try for other)
For atmel is atmel-touchscreen.kl, for elan is elan-touchscreen.kl
Open it as text editor and delete all content of it and save and reboot
To Restore the Hardware Keys Light and Function
Just Copy and Paste the Backup File to the destination (/system/etc/init.d, /system/usr/keylayout)
NOTE: Don't Forget to Backup The ROM,default 90userinit, default touchscreen layout .kl before trying...
Hi hdorius,
maybe it's just typos, but, it will not work the way you describe it.
You have to remove ">" from the chmod command line and change 755 to 644.
BTW: for CM based ROMs, there is a tweak, too (using the file "brightness" etc.),
but it's more easy to just use the app "Keyboard Backlight Controller" from the market.
Cheers, Magpie
hdorius said:
This Guide Will Disable Hardware Keys (Home, Menu, Back, Search) Light and make it disabled completely so we can use the on screen button like nexus phone in AOSP based ROM (AOKP/PACMAN/Codefirex)
NOTE: Don't Try This in CM Based Rom because CM don't have any on-screen button mod
For Disable The Hardware Keys Light :
Add The Following code to /system/etc/init.d/90userinit
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
and reboot
For Disable The Hardware Keys Function Completely
Navigate to /system/usr/keylayout/synaptics-rmi-touchscreen.kl (maybe it's touchscreen dependent mine is synaptic,i can't try for other)
For atmel is atmel-touchscreen.kl, for elan is elan-touchscreen.kl
Open it as text editor and delete all content of it and save and reboot
To Restore the Hardware Keys Light and Function
Just Copy and Paste the Backup File to the destination (/system/etc/init.d, /system/usr/keylayout)
NOTE: Don't Forget to Backup The ROM,default 90userinit, default touchscreen layout .kl before trying...
Click to expand...
Click to collapse
In Viper DHD you have this on Viper tweaks cheers
Sent from my HTC Desire HD using xda premium
aljazirrr said:
In Viper DHD you have this on Viper tweaks cheers
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Yuhuuu...is viperdhd an AOSP ROM?
Sent from my HTC Desire HD using Tapatalk 2
Magpie42 said:
Hi hdorius,
maybe it's just typos, but, it will not work the way you describe it.
You have to remove ">" from the chmod command line and change 755 to 644.
BTW: for CM based ROMs, there is a tweak, too (using the file "brightness" etc.),
but it's more easy to just use the app "Keyboard Backlight Controller" from the market.
Cheers, Magpie
Click to expand...
Click to collapse
I've tested myself and worked before I posted it and yes the cm have that tweaks,but I doesn't work for me when I set,btw thx
Sent from my HTC Desire HD using Tapatalk 2
hdorius said:
I've tested myself and worked before I posted it
Click to expand...
Click to collapse
So you have no clue at all what theses commands do?!
Sorry, but if you don't know what things do, you should not recommend them.
Your `chmod 755 > /sys/class/leds/button-backlight/max_brightness` will not change the mode of the file as needed,
but overwrite the 0, you previously wrote into "max_brightness", making the first command completely superfluous.
It ends up in a completely empty "max_brightness" file - if we think positive, assuming best case.
In worst case, STDERR has previously been redirected to STDOUT and your command will even result in a "max_brightness" file containing this:
Code:
chmod 755
Usage: chmod [OPTION] <MODE> <FILE>
-R, --recursive change files and directories recursively
--help display this help and exit
The effect of this - or empty - content is in fact unpredictable and only depends on the robustness of the routine, which evaluates the content of "max_brightness".
In your case, you may have been on the lucky side, cause the routine in your ROM seems to return a 0 in case of failure,
setting the value for brightness to 0 - so your "testing success" is nothing less than just sheer coincidence.
A less robust implementation may just crash, leaving your phone unbootable, in a boot loop or s/th even worse.
Cheers, Magpie
increase the hardware button britness on JB 4.2.1
Magpie42 said:
So you have no clue at all what theses commands do?!
Sorry, but if you don't know what things do, you should not recommend them.
Your `chmod 755 > /sys/class/leds/button-backlight/max_brightness` will not change the mode of the file as needed,
but overwrite the 0, you previously wrote into "max_brightness", making the first command completely superfluous.
It ends up in a completely empty "max_brightness" file - if we think positive, assuming best case.
In worst case, STDERR has previously been redirected to STDOUT and your command will even result in a "max_brightness" file containing this:
Code:
chmod 755
Usage: chmod [OPTION] <MODE> <FILE>
-R, --recursive change files and directories recursively
--help display this help and exit
The effect of this - or empty - content is in fact unpredictable and only depends on the robustness of the routine, which evaluates the content of "max_brightness".
In your case, you may have been on the lucky side, cause the routine in your ROM seems to return a 0 in case of failure,
setting the value for brightness to 0 - so your "testing success" is nothing less than just sheer coincidence.
A less robust implementation may just crash, leaving your phone unbootable, in a boot loop or s/th even worse.
Cheers, Magpie
Click to expand...
Click to collapse
Hi Guys,
can someone please help me and suggest me a way to increase the britness of the hardware button on my ZOPO 980 who is running JB 4.2.1
I have tried to edit the build.prop but did not find any line to modify , and I would guess this is not the right way.
thanks
Good
Sent from my KM-S220 using xda app-developers app
Thanks a lot
Works great on my d2vzw. I used option one and made the 644 changes that magpie suggested in second post
Sent from my SCH-I535 using Tapatalk
Thanks!
Great guide worked perfect on my htc amaze 4g
Thanks!
Viper DHD 3.0.1
in viperdhd this options is available in venom tweaks, version 3.0.1 is the latest and most stable version with complete sense 4.1 UI. I suggest you to try it once.
Nice guide, can I try this on nameless ROM, 5.0.2
total mess . anything related to disabling keylight and disable keys won't work for me . i am having note n7000 . first i enabled navigation bar and tried everything what was mentioned above , even i did tried replacing 755 with 644 and removing > but didnt work anything
ankitrajj said:
total mess . anything related to disabling keylight and disable keys won't work for me . i am having note n7000 . first i enabled navigation bar and tried everything what was mentioned above , even i did tried replacing 755 with 644 and removing > but didnt work anything
Click to expand...
Click to collapse
Maybe it don't compatible with samsung phone, i just tested it on my desire hd,sorry..
I am using micromax nitro A311 and its navigation key light is turned off, can anyone tell me how to enable the light of navigation keys?
hdorius said:
This Guide Will Disable Hardware Keys (Home, Menu, Back, Search) Light and make it disabled completely so we can use the on screen button like nexus phone in AOSP based ROM (AOKP/PACMAN/Codefirex)
NOTE: Don't Try This in CM Based Rom because CM don't have any on-screen button mod
For Disable The Hardware Keys Light :
Add The Following code to /system/etc/init.d/90userinit
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
and reboot
For Disable The Hardware Keys Function Completely
Navigate to /system/usr/keylayout/synaptics-rmi-touchscreen.kl (maybe it's touchscreen dependent mine is synaptic,i can't try for other)
For atmel is atmel-touchscreen.kl, for elan is elan-touchscreen.kl
Open it as text editor and delete all content of it and save and reboot
To Restore the Hardware Keys Light and Function
Just Copy and Paste the Backup File to the destination (/system/etc/init.d, /system/usr/keylayout)
NOTE: Don't Forget to Backup The ROM,default 90userinit, default touchscreen layout .kl before trying...
Click to expand...
Click to collapse
Brother can you help me up enabling button light in samsung exynos 7580 as button light feature is disabled in the RR sources.
Please it would be a great help to me struggling from months for the fix .
With this procedure you will be able to disable the capacitive buttons and enable the real android onscreen buttons, NOT PIE.
This has been tested in a Tab Pro 8.4 with the latest CM build. If you follow the instructions correctly you shouldn't have any issues, however make a backup just in case. If anyone wants to try it with a stock rom please let me know if it works.
Requisites: Root access and a root explorer.
1. With your preferred root explorer open your build prop and add the following line all the way to the end:
qemu.hw.mainkeys=0
Save and exit.
2. Navigate to system/usr/keylayout and open sec_touchkey.kl as text.
You should have two lines. Add a # at the beginning of each line as follows:
#key 158 BACK
#key 254 APP_SWITCH
Save and exit.
3. Exit the file explorer and go to settings, buttons and turn off the buttons light.
4. Reboot and voila!!!
I hope this helps.
I'm wondering if someone got the chance to test this and if it work for everybody else as it works for me.
I managed to get the soft keys showing via step 1.
However, I do not find a file called sec_touchkey.kl in step 2.
Any advice?
I have atmel_mkt_ts.kl, gpio_keys.kl and synaptics_rmi4_i2c.kl instead.
uPDATE - managed to do step 2 by editing generic.kl instead
All works great now!
It works fine in portrait but broken in landscape. Keys dont show up at all. Any fix for this?
burshturs said:
I'm wondering if someone got the chance to test this and if it work for everybody else as it works for me.
Click to expand...
Click to collapse
I have the same problem with stock ROM.
aeron16 said:
I managed to get the soft keys showing via step 1.
However, I do not find a file called sec_touchkey.kl in step 2.
Any advice?
I have atmel_mkt_ts.kl, gpio_keys.kl and synaptics_rmi4_i2c.kl instead.
uPDATE - managed to do step 2 by editing generic.kl instead
All works great now!
Click to expand...
Click to collapse
Are you trying it in stock or CM?
Hi am using Stock
Hi guys i tried on CM 11 and i dont find #key 254 APP_SWITCH , i rebooted my TAB and Hardware button still works , and appear Software button too , any clue?
Works like a sharme on cm11. The only thing is that the file isn't named 'sec_touchkey.kl' but 'sec_touchscreen.kl' (newest nightly 9-9-2014)
Thanks, works great for me on cm11, too
Works like a charm.
But it's annoying to do this every time I flash a new nightly - so I made a recovery zip-file that does the trick in recovery. Just flash it after you flashed a new ROM.
It's tested on CM11. The script is quite generic and maybe also works on other ROMs.
It first deletes the line with qemu.hw.mainkeys in build.prop if there is one (to avoid duplicates) and then inserts the command at the end of the file.
After that it removes all "#" in front of key assignment in sec_touchscreen.kl (again to avoid duplicates) and then adds "# " in front of every key assignment in this file.
@burshturs: Feel free to post this zip in the OP, if you want to.
The code of the shellscript, if someone is interested:
Code:
#!/sbin/sh
sed -i '/qemu\.hw\.mainkeys/d' /system/build.prop
echo "qemu.hw.mainkeys=0" >> /system/build.prop
sed -i 's/\# *key/key/gI' /system/usr/keylayout/sec_touchscreen.kl
sed -i 's/key/\# key/gI' /system/usr/keylayout/sec_touchscreen.kl
Good stuff. Thank you ! So I guess the way to undo the process I is simply to flash a CM update?
Just flash the ROM again without reset and everything will be as before. Or edit the files as described in the OP and revert the changes.
Nice!
I tried this om my sm-t520 and it works.
I did not phase out the Samsung bar, because in portait mode the bar is gone.
Is there a solution for the Andoid bar in portrait mode?
Sorry if this sounds like a dumb question but you said to open the build prop and add that line to the bottom and my question is where, exactly? I'm using solid explorer and am in the system root folder but to which file do I add that line? Is it in system>usr>keylayout>Generic.kl like I navigated to to disable the capacitive buttons?
I found how to do that in another post and then enabled Pie, but I'd rather have the normal buttons instead.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
@baldwyn: build.prop is a file in /system.
Does anybody know the key for the home-button? I have already disabled #172 but that's not working.
petty500 said:
Nice!
I tried this om my sm-t520 and it works.
I did not phase out the Samsung bar, because in portait mode the bar is gone.
Is there a solution for the Andoid bar in portrait mode?
Click to expand...
Click to collapse
You can use this app instead of the build.prop edit. That works just great, The Pro version even allows many customizations incl. behaviour like auto hide or not or custom icons. Important - it works both portrait and landscape,
https://play.google.com/store/apps/details?id=com.mrbimc.udn.lite&hl=de
Working in CM12?
hypophysis said:
Works like a charm.
But it's annoying to do this every time I flash a new nightly - so I made a recovery zip-file that does the trick in recovery. Just flash it after you flashed a new ROM.
It's tested on CM11. The script is quite generic and maybe also works on other ROMs.
It first deletes the line with qemu.hw.mainkeys in build.prop if there is one (to avoid duplicates) and then inserts the command at the end of the file.
After that it removes all "#" in front of key assignment in sec_touchscreen.kl (again to avoid duplicates) and then adds "# " in front of every key assignment in this file.
@burshturs: Feel free to post this zip in the OP, if you want to.
The code of the shellscript, if someone is interested:
Code:
#!/sbin/sh
sed -i '/qemu\.hw\.mainkeys/d' /system/build.prop
echo "qemu.hw.mainkeys=0" >> /system/build.prop
sed -i 's/\# *key/key/gI' /system/usr/keylayout/sec_touchscreen.kl
sed -i 's/key/\# key/gI' /system/usr/keylayout/sec_touchscreen.kl
Click to expand...
Click to collapse
Has anyone tried this in CM12? Or perhaps CM12 has a built-in setting that accomplishes the same thing?
Thanks,
Ron
kingofcomedy said:
Click to expand...
Click to collapse
Thank you for this. With this setting are the capacitive buttons disabled? I would prefer that they were.
Sent from my SM-T320 using Tapatalk
Any chance anyone has found settings or an app to get the lockscreen to rotate into landscape mode?
Sent from my [device_name] using XDA-Developers Legacy app
nivag1710 said:
Any chance anyone has found settings or an app to get the lockscreen to rotate into landscape mode?
Click to expand...
Click to collapse
If you have root access enabled you can enable lock screen rotation with any file manager like ES File Explorer or FX Explorer. First grant root permissions to enable access to root partition. Then head to the root partition and open the system folder. In system open build.prop file (all the way at the bottom) using any of the recommended file editors.
Directory path: /system/build.prop
Once in build.prop, hit the edit option, scroll all the way to the bottom, create a new line and add this string:
lockscreen.rot_override=true
Hit save and exit edit mode and reboot device. If it hangs on boot logo screen, just force reboot and it should take.
Syndrome666 said:
If you have root access enabled you can enable lock screen rotation with any file manager like ES File Explorer or FX Explorer. First grant root permissions to enable access to root partition. Then head to the root partition and open the system folder. In system open build.prop file (all the way at the bottom) using any of the recommended file editors.
Directory path: /system/build.prop
Once in build.prop, hit the edit option, scroll all the way to the bottom, create a new line and add this string:
lockscreen.rot_override=true
Hit save and exit edit mode and reboot device. If it hangs on boot logo screen, just force reboot and it should take.
Click to expand...
Click to collapse
I figured you can do it with root, but I haven't tried it. I found that lack of bloat didn't compel me to root the phone yet.
Sent from my [device_name] using XDA-Developers Legacy app
You can probably, root, add that string to build.prop, reboot to make sure it's working properly, and then unroot. Haven't tried that myself as I need root enabled at all times, adaway, ampere (battery meter) and some custom features require it to be activated.
OP status for the first time
I just found out you can snooze it just before typing this sentence lol. But is there a way to disable the notification permanently without root?
I don't expect it to survive a reboot but if there is a way I would imagine it being achieved via ADB?
Not a big deal anymore since I just found out you can snooze it for 2 hours but hey might as well finish what I started. If you were wondering my concern is burn in but I think the icons on the status bar move? I would rest better knowing it's not there anyway.
Thanks, I appreciate it.
EDIT: Nevermind I think I did it.
System/System app settings
Then disable "Show update notifications"
EDIT 2: It did not work:laugh:
- With root I used this solution:
Edit the file: system/build.prop
copy / paste the line that contains the version number.
Example: ro.build.version.incremental=V14.3.11.0.PFJMIXM
I have put a "#" for memo and changed v10 to v14 :
Code:
# ro.build.version.incremental=V10.3.11.0.PFJMIXM
ro.build.version.incremental=V14.3.11.0.PFJMIXM
- Without root It may also be possible (to check) to modify this file with XiaomiADBFastbootTools (with the small embedded file manager).
Do I need an unlocked bootloader or root access to use XiaomiADBFastbootTools?
The Flasher, Wiper and Camera2 modules require an unlocked bootloader but everything else works without rooting or unlocking.
Click to expand...
Click to collapse