Database Users

[Q] Answer call with home button

Can you answer calls with the home button in cm9 ? I can't find the option.
Or in some other ics rom ?
Or an app?
Anyone?

m__w said:
Can you answer calls with the home button in cm9 ? I can't find the option.
Or in some other ics rom ?
Or an app?
Anyone?
Click to expand...
Click to collapse
try menu >settings >call settings > tick answering key

xsenman said:
try menu >settings >call settings > tick answering key
Click to expand...
Click to collapse
Hi, I can't seem to find that in ics, maybe your thinking of gb?
I also tried open up the contacts/phone app and then press menu, but I didn't find it there either.

Hey
This would be a nice feature!

m__w said:
Hi, I can't seem to find that in ics, maybe your thinking of gb?
I also tried open up the contacts/phone app and then press menu, but I didn't find it there either.
Click to expand...
Click to collapse
yup, I was referencing it from GB...unless the CM9 developers would include it in their future releases the only other option would be to flash GB settings , if you badly need this feature.

Im missing that feature also badly on my GT9100 S2. Isn’t there any other way to get this work, than to wait for the developers to notice that this feature is missing for Samsung Users. There must be hundred thousands of them.

If the code was pulled from the open commits from CM and brunched into a working build, it would be located in Settings/Accessibility. At least, it is on my cm9 rom I made for the HTC Rezound.

IAmTheOneTheyCallNeo said:
If the code was pulled from the open commits from CM and brunched into a working build, it would be located in Settings/Accessibility. At least, it is on my cm9 rom I made for the HTC Rezound.
Click to expand...
Click to collapse
Ok, I don't know exactly how complicated that would be, but I think it's a little bit out of my league.

xsenman said:
the only other option would be to flash GB settings.
Click to expand...
Click to collapse
Is there like a settings.zip, that i just extract from the rom file, and then flash it in recovery ? or is it more complicated than that ?
edit: could I just swap the "settings.apk" in system\app directory in the rom file, using 7zip as extractor ?

m__w said:
edit: could I just swap the "settings.apk" in system\app directory in the rom file, using 7zip as extractor ?
Click to expand...
Click to collapse
you should use root explorer to do this , first do a nandroid backup in CWM ( in case it fails you can restore in CWM) when you want to try, Note the permissions of current settings.apk, rename current as .bak, copy paste new settings.apk, fix permissions and exit using exit menu ( not back button) and reboot

m__w said:
Ok, I don't know exactly how complicated that would be, but I think it's a little bit out of my league.
Click to expand...
Click to collapse
No problem. Do any of you know someone who can compile cm9 for this device? I can tell them how to pull the open commit from Cyanogenmod Gerrit code review's open commits.. Did it myself today for this "Home to answer calls" option. Let me know
For the one that can do it, give them this:
It's a two part commit. This one will go in Frameworks/Base:
git fetch http://r.cyanogenmod.com/CyanogenMod/android_frameworks_base refs/changes/56/20756/1 && git cherry-pick FETCH_HEAD
and this one will go in packages/apps/Settings:
git fetch http://r.cyanogenmod.com/CyanogenMod/android_packages_apps_Settings refs/changes/57/20757/2 && git cherry-pick FETCH_HEAD
Build the rom with those two cherry picks and you have yourself the "home key to answer calls" option.
-Neo
Sent from my Rezound using xda premium

[MOD][KRT16M/KOT49E/KOT49H] NavBar dpi modification | Multiple sizes!

This mod will make your navigation bar smaller. It is compatible with ONLY stock ROM, do not use this with a custom ROM! And always double check that you have a matching build number, such as KOT49E, before proceeding.
Root and recovery needed.
Recovery flash method:
Files:
Compatible with stock KOT49H ROM:
20 dpi: http://www.mediafire.com/download/9xtg49orau98u81/KOT49H_20dpi_flashable.zip
24 dpi: http://www.mediafire.com/download/ua8jd88ll1rz87b/KOT49H_24dpi_flashable.zip
26 dpi: http://www.mediafire.com/download/yeok7afeb5k37uh/KOT49H_26dpi_flashable.zip
28 dpi: http://www.mediafire.com/download/fj51gmlrybi8oac/KOT49H_28dpi_flashable.zip
30 dpi: http://www.mediafire.com/download/mdshzwa3q6tawtx/KOT49H_30dpi_flashable.zip
36 dpi: http://www.mediafire.com/download/2c7cpjgk3ueilu0/KOT49H_36dpi_flashable.zip
40 dpi: http://www.mediafire.com/download/rv0n9o02h4xi2u7/KOT49H_40dpi_flashable.zip
48 dpi: http://www.mediafire.com/download/ji05m55i65t1y0a/KOT49H_48dpi_flashable.zip - back to stock
Compatible with stock KOT49E ROM:
20 dpi: http://www.mediafire.com/download/m3cysam0pkz5j4n/KOT49E_20dpi_flashable.zip
24 dpi: http://www.mediafire.com/download/y9in2y4uv9jmrf4/KOT49E_24dpi_flashable.zip
26 dpi: http://www.mediafire.com/download/6cm3fu3bdveu15e/KOT49E_26dpi_flashable.zip
28 dpi: http://www.mediafire.com/download/1g9mo53zvxqlazr/KOT49E_28dpi_flashable_v2.zip
30 dpi: http://www.mediafire.com/download/qedonvtjy2bbid1/KOT49E_30dpi_flashable.zip
36 dpi: http://www.mediafire.com/download/yauecgoaz2v0567/KOT49E_36dpi_flashable.zip
40 dpi: http://www.mediafire.com/download/g9b7xmat6dd4ock/KOT49E_40dpi_flashable_v2.zip
48 dpi: http://www.mediafire.com/download/66n9u3hevuj4v7t/KOT49E_48dpi_flashable.zip - back to stock
Click to expand...
Click to collapse
Installation instructions:
- Download the file into your phone
- Go to recovery, flash the file
- Wipe cache and dalvik cache
- Reboot
Click to expand...
Click to collapse
Manual method:
Files:
Compatible with stock KRT16M ROM:
36 dpi: http://www.mediafire.com/?ddrk111b1jjcb8j
Compatible with stock KOT49E ROM:
26 dpi: http://www.mediafire.com/download/37eyz1d59bd4nud/KOT49E 26dpi.zip
30 dpi: http://www.mediafire.com/download/dyxolnb33212e87/KOT49E 30dpi.zip
36 dpi: http://www.mediafire.com/download/s220a94cwpnqd3w/KOT49E 36dpi.zip
Click to expand...
Click to collapse
Installation instructions:
- Download and unzip the file
- Dump files to /sdcard/
- Go to recovery, mount data and system
- ADB Shell:
Code:
cp /sdcard/framework-res.apk /system/framework/
cp /sdcard/SystemUI.apk /system/priv-app/
- Wipe cache and dalvik cache
- Reboot
Click to expand...
Click to collapse
Or you can install with flashable zip packaged by mercuriox85: http://forum.xda-developers.com/showpost.php?p=47495075&postcount=4
Disclaimer: I am not responsible for lost data, bricked phones, non-booting systems, angry girlfriends, world war III... It is recommended to make a Nandroid first.

Can be installed using TWRP file manager too.

CAn I push manually with root explore?

flashable zips
https://www.dropbox.com/s/g7ehdlpikxxxvf5/navigation_bar_28dpi_4.4.zip
https://www.dropbox.com/s/beyvorqo1jajtzm/navigation_bar_32dpi_4.4.zip
https://www.dropbox.com/s/8dby6jg1wy0n20h/navigation_bar_36dpi_4.4.zip
https://www.dropbox.com/s/96smacmar05wj0f/navigation_bar_restore_factory_4.4.zip

mercuriox85 said:
flashable zips
https://www.dropbox.com/s/g7ehdlpikxxxvf5/navigation_bar_28dpi_4.4.zip
https://www.dropbox.com/s/beyvorqo1jajtzm/navigation_bar_32dpi_4.4.zip
https://www.dropbox.com/s/8dby6jg1wy0n20h/navigation_bar_36dpi_4.4.zip
https://www.dropbox.com/s/96smacmar05wj0f/navigation_bar_restore_factory_4.4.zip
Click to expand...
Click to collapse
Invalid link.

motoxxxx said:
Invalid link.
Click to expand...
Click to collapse
now working links

mercuriox85 said:
now working links
Click to expand...
Click to collapse
Thanks!
---------- Post added at 12:09 PM ---------- Previous post was at 11:27 AM ----------
Having issue. Every time I press and hold powder button, I get reboot. Any fix?

That has nothing to do with this mod. It is a safety feature, to allow you to reset your device even if it is completely frozen.

Thanks! Working fine

jkoljo said:
cut.
Click to expand...
Click to collapse
you can add zip files to first post

motoxxxx said:
Having issue. Every time I press and hold powder button, I get reboot. Any fix?
Click to expand...
Click to collapse
That's normal behaviour, it's effectively the replacement for a battery pull.

noodles2k said:
That's normal behaviour, it's effectively the replacement for a battery pull.
Click to expand...
Click to collapse
Usually when I press and hold the powder button its give me the option to powder/reboot/airplane mode. But every time I do that its just reboot.

motoxxxx said:
Usually when I press and hold the powder button its give me the option to powder/reboot/airplane mode. But every time I do that its just reboot.
Click to expand...
Click to collapse
Ah, got you. This shouldn't affect the power button/menu as they're different files. Which rom are you using? And are you using Dalvik or Art runtime?

noodles2k said:
Ah, got you. This shouldn't affect the power button/menu as they're different files. Which rom are you using? And are you using Dalvik or Art runtime?
Click to expand...
Click to collapse
I'm running on deodex KANGAKAT rom and Dalvik.

motoxxxx said:
CAn I push manually with root explore?
Click to expand...
Click to collapse
I wouldn't try it. I have messed with framework on a different phone in root explorer and it locked up on me and I had to reflash a backup because it wouldn't boot.

Will anyone mirror the flashable zip please? My phone freezes on dropbox for some reason?

mercuriox85 said:
you can add zip files to first post
Click to expand...
Click to collapse
Done, makes things easier for beginners

tried flashing 36dpi nav bar and it failed on TWRP
Sent from my Nexus 5 using Tapatalk

Also tried 36dpi with twrp and got stuck in boot animation bootloop

Is it possible to change the height of the navbar to 0 dpi?
I want to use UDN instead of the stock navbar but keep the menu button in the top bar.
Tried to change the framework.res myself but failed by compiling it.
Any help is appreciated.

[HOW TO] Disable Capacitive Buttons and Enable REAL android onscreen buttons

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

Xiaomi Piston v3 keys

Just a quick info for people with Xiaomi Piston v3 headset, nothing new either:
As root you can assign all three keys in the file
Code:
/system/usr/keylayout/msm8226-tapan9302-snd-card_Button_Jack.kl
Buttons in order top->bottom when you wear the headset
Upper button: Keycode 115
Middle button: Keycode 226
Lower button: Keycode 217
(at least on Cyanogenmod 13)
For example:
Code:
key 226 HEADSETHOOK
key 115 VOLUME_UP
key 217 VOLUME_DOWN
You can get some inspiration on what actions are available in the "Generic.kl" file in the same folder
Todo: Write a little script in /persist so it stays accross system updates.

so how i'm supposed to enable those actions? please explain the process step by step
Thank you

cameravala said:
so how i'm supposed to enable those actions? please explain the process step by step
Thank you
Click to expand...
Click to collapse
Hope this works on your ROM.
First the /system parition needs to be writeable, you need root for that.
In a terminal emulator or in "adb shell" on your PC do:
Code:
mount -o remount,rw /system
Then you can edit it, for example go to the location with a root-explorer and open it from there in a text editor (most comfortable)
or you can transfer it to your PC and edit it there:
On the phone:
Code:
cp /system/usr/keylayout/msm8226-tapan9302-snd-card_Button_Jack.kl /sdcard
Then edit the file that is now in your internal storage that shows up on PCs over usb.
To put it back, on the phone:
Code:
cp /sdcard/msm8226-tapan9302-snd-card_Button_Jack.kl /system/usr/keylayout/msm8226-tapan9302-snd-card_Button_Jack.kl
chmod 644 /system/usr/keylayout/msm8226-tapan9302-snd-card_Button_Jack.kl
You need to reboot it after that. You can ask if you have other questions.

This won't work if your kernel doesn't include this patch: https://github.com/CyanogenMod/andr...mmit/9aecde9a7aaa7362ef7b4c04ad92d3873a90d8eb

fonz93 said:
This won't work if your kernel doesn't include this patch: https://github.com/CyanogenMod/andr...mmit/9aecde9a7aaa7362ef7b4c04ad92d3873a90d8eb
Click to expand...
Click to collapse
Damn, I was hoping this is universal.
Thanks for the clarification

fonz93 said:
This won't work if your kernel doesn't include this patch: https://github.com/CyanogenMod/andr...mmit/9aecde9a7aaa7362ef7b4c04ad92d3873a90d8eb
Click to expand...
Click to collapse
Thanks you guy

Will this work with CM13?

tiagp said:
Will this work with CM13?
Click to expand...
Click to collapse
Yes

I can't find msm8226-tapan9302-snd-card_Button_Jack.kl on root/system/usr/keylayout
Should i make that file named msm8226-tapan9302-snd-card_Button_Jack.kl on that location?
I'm on Cm13 with latest build.

giboto91 said:
I can't find msm8226-tapan9302-snd-card_Button_Jack.kl on root/system/usr/keylayout
Should i make that file named msm8226-tapan9302-snd-card_Button_Jack.kl on that location?
I'm on Cm13 with latest build.
Click to expand...
Click to collapse
Yeah, you'll need to create it in that location. Your keycodes might differ from the OP (mine did) so you might need to use the keytest.apk to make sure your mappings are correct. Other than that, you'll be fine.

Works me perfect
I didn't create the file, instead of that i modified the "Generic.kñ" file and after a fast reboot worked fine
Sent from my Moto G using XDA-Developers mobile app

Double Tap To Wake (K5 Plus)

Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.

Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk

Nikish21 said:
Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Best of luck. :good:

Would it work with los stock kernel?

impulsar said:
Would it work with los stock kernel?
Click to expand...
Click to collapse
No idea. I am using vegito kernel v7

riazul.islam20 said:
No idea. I am using vegito kernel v7
Click to expand...
Click to collapse
Vegito kernel by default supports dt2w right?

impulsar said:
Vegito kernel by default supports dt2w right?
Click to expand...
Click to collapse
Might be. But by default it was inactivated.

Is it possible to add screen of gestures in lenovo vibe k5

Is it possible to lock device by double taping...Just like dt2wake??

jometzz said:
Is it possible to lock device by double taping...Just like dt2wake??
Click to expand...
Click to collapse
Why not?
Just double tap on statue bar

riazul.islam20 said:
Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.
Click to expand...
Click to collapse
It gets reset to 0 on reboot. Why?

afzalsayed96 said:
It gets reset to 0 on reboot. Why?
Click to expand...
Click to collapse
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
#!/system/bin/sh
echo 2 > /sys/android_touch/doubletap2wake
Click to expand...
Click to collapse

Android_touch
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!

Goutham47 said:
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!
Click to expand...
Click to collapse
the same here, please help

Please someone who says the correct way to do the procedure in Rom AOSP or LineageOS in 7.1.2

Someone using dt2w on oreo? Please share info if there's a way to activate it under oreo

nonline said:
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
Click to expand...
Click to collapse
bro...i m getting endless boot animation...what to do...??? plzz help