[mod][how to][ics & jb]disable capacitive buttons - Nexus S General

I've seen some interest on the forums in how to do this. So here is a guide.
NOTE: This mod will render the capacitive buttons(hardware buttons) on your Nexus s completely inoperable. Use this mod only if you are using a custom ICS OR JB ROM with navigation bar(on screen buttons) enabled, or some other way to navigate your phone.
First, make sure that you are completely satisfied with the operation of the navigation bar & are certain that you have no need for the capacitive buttons.
DISCLAIMER: This mod involves editing system files. Use at your own risk. This mod will not magically make the navigation bar appear on roms that do not already have it enabled. This mod only disables the capacitive buttons. Instructions on how to disable the backlights for these buttons will be at the bottom of this post.
UPDATE : Just flash these zips.
To disable capacitive keys
http://db.tt/AyJLDkg1
To restore capacitive keys
http://db.tt/PhxFyBb3
And an init.d script for BLD to turn the backlights off (to the best of your BLD supported kernels ability anyway)
http://db.tt/BRpy78Cz
NOTE : Success will vary with BLD according to the capabilities of your chosen kernel. Some kernels are really good with bld responsiveness, others aren't. This has nothing to do with my script. And remember that you can't just choose a kernel based on how well it handles backlight settings. It's gotta run your whole phone too.
For those who want to do it manually.
1; Using Root Explorer (from market) go to system/usr/keylayout.
2; Mount system as r/w.
3; Long press on the file called mtx224_ts_input.kl.
4; Select 'open in text editor'. Scroll down and you will see these 4 lines:
key 158 BACK WAKE
key 139 MENU WAKE
key 217 SEARCH WAKE
key 102 HOME WAKE
5; Delete these 4 lines. Or alternately, just delete the lines for the buttons you want disabled.)
6; Press menu, save & exit. (Root Explorer will automatically create a backup of this file. It will be called mtx224_ts_input.kl.bk)
7; Now, make the same edits to the 4 lines in the file called cypress-touchkey.kl and save & exit.
8; Reboot.
Now you have no capacitive buttons(or only the ones you left intact in step 5 & 7).
Now, the backlights are still working. To disable these, flash a kernel that has backlight dimmer support(BLD) (I use GladOs) and use NStools(from market). Set BLD to on. And delay to 0. Done. No buttons & no backlight.
NOTE: BLN will still work even with BLD on.
To undo this mod you can either restore the original .kl file using the backup that Root Explorer automatically created. Just delete the modified .kl file and rename the .kl.bk file by just removing the .bk from the end of the file name. And reboot.
Alternately, you can just flash your ROM straight over the top. (of course, that means you'll have to flash your kernel & any other mods again too)

Followed this to the letter and my buttons still work... Any thoughts?

dchoward1977 said:
Followed this to the letter and my buttons still work... Any thoughts?
Click to expand...
Click to collapse
Hmm... are you sure you rebooted after making the edits? Which rom are you using. I've tested with AOKP build 27. And cm9 with evilisto's mod and both work fine. Are the button functions still working or just the backlights? If it's just backlights, make sure you set nstools to run on boot. If it's function that's still working, check the edited .kl file and make sure the edit stuck. If you are sure you've folowed to the letter and button 'functions' are still working it may be necessary to make the same edits in cypress-touchkey.kl as well. This wasn't necessary for me but it may be with your rom.
Sent on neXus from somehere. Could be anywhere.

Awesome mod! I needed to also delete in cypress-touchkey.kl. Great job!

stu5797 said:
Awesome mod! I needed to also delete in cypress-touchkey.kl. Great job!
Click to expand...
Click to collapse
Glad it worked for you, although the cypress touchkey edit really shouldn't have been necessary, since that file only sets the function of those keys, not the status. Which rom are you using, so I can test some more? And thanks for the feedback.
Sent on neXus from somehere. Could be anywhere.

I m using aokp milestone 4. I have to set my bld at 500ms with matrix v17 because if i set it to 0 it does not work correctly. Wish i could set it to 0. Any ideas to completely get rid of those lights?

I also had success deleting the lines from cypress touch key.kl. Thanks a bunch.
Sent from my Nexus S using xda premium

stu5797 said:
I m using aokp milestone 4. I have to set my bld at 500ms with matrix v17 because if i set it to 0 it does not work correctly. Wish i could set it to 0. Any ideas to completely get rid of those lights?
Click to expand...
Click to collapse
Milestone 4 is basically the same as build 27. Which is what I'm using. I have no problems with bld set to zero. As for disabling the lights, someone would have to write a boot script I think. I have no idea how. So if anyone wants to give this a go.....
Sent on neXus from somehere. Could be anywhere.

Heres a flashable zip for disabling the capacitive keys.. It just includes the mxt224_ts_input.kl and cypress-touchkey.kl, modded for no capacitive funciton.
View attachment 957555

Please make restore zip , tnx
Sent from my Nexus S using xda premium

Thanks Swamp Goblin. Wish I knew how to do that. Got any tricks for the backlights?
Sent on neXus from somewhere. Could be anywhere.

If i install this mod i cant set bld off/on :S
Sent from my Nexus S using xda premium

dinos3 said:
If i install this mod i cant set bld off/on :S
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I just tried it. Works fine. Reflash your kernel.
Sent on neXus from somewhere. Could be anywhere.

I try this but For me not work ;S
Sent from my Nexus S using xda premium

dinos3 said:
Please make restore zip , tnx
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Here you go
Restore_capacitive_keys_NS
---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------
stumpy352 said:
Thanks Swamp Goblin. Wish I knew how to do that. Got any tricks for the backlights?
Sent on neXus from somewhere. Could be anywhere.
Click to expand...
Click to collapse
I might be able to figure out where to disable it.. I'll try tonight
This button mod and completely disabled lights would be perfect, thanks for the mod

That would extremely helpful!

Guys the backlight of the buttons on my i9023 are really really weak.. is there any way to make them brighter?
Sent from my Nexus S using xda premium

swamp goblin said:
Here you go
Restore_capacitive_keys_NS
---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------
I might be able to figure out where to disable it.. I'll try tonight
This button mod and completely disabled lights would be perfect, thanks for the mod
Click to expand...
Click to collapse
No probs. Thanks for making it a zip, although i've added it into
my rom now so only one flash reqd.
thegtfusion said:
Guys the backlight of the buttons on my i9023 are really really weak.. is there any way to make them brighter?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
We're trying to disable them, but I suppose the method used, when we work it out might give you a starting point.
Sent on neXus from somewhere. Could be anywhere.

thegtfusion said:
Guys the backlight of the buttons on my i9023 are really really weak.. is there any way to make them brighter?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
This may be related to hardware.. My dad's ns4g has super dim backlights, and mine are insanely bright.. But if we figure out how to disable them there may be a way to maybe bump up the brightness a bit without breaking them haha

I was just reading an article for LEDs hack.apk. Supposedly gives you control on/off for button bl. The dev says nexus s will never be supported because the button bl & screen bl are powered together. If that was the case, bld wouldn't work without affecting the screen. Evilisto made a reference to arrays.xml in framework res. Maybe the answer is here. I don't have a pc so I can't decompile it and have a look. Any takers?
Sent on neXus from somewhere. Could be anywhere.

Related

[GUIDE] remap capacitive buttons

I know a lot of people out there are doing this already, but it didn't seem like there was a guide or anything out there for the NS. So, here we go.
(Please, make sure you know what you're doing BEFORE you apply this modification. I can't be responsible if you somehow manage to brick, or make brick-like your phone while following this guide.)
-You can do this using either adb, Terminal, or apps like Root Explorer. Since I'm trying to make this as easy as possible, I'll explain how to do this using the "File Manager" app, which can be installed via Market for FREE.
First, you need a rooted phone. If your phone is not rooted, there is extensive existing literature on how to get this done. (It's awfully easy on our Nexus S )
Run File Manager, hit Menu > More > Settings, scroll way~~ down, and make sure that "Root Explorer" and "Mount System Folders" are checked.
Navigate your way to
/system/usr/keylayout
(you'll have to move Up a step or two to find 'system' folder at root level.)
[BACKUP THE ORIGNIAL FILE WE'RE ABOUT TO MODIFY]
Long-press the file 'cypress-touchkey.kl'
Select 'Copy'
Hit 'Paste', on the upper left corner of app.
You'll be asked to rename the file. Rename it to something reasonable. (like, cypress-touchkey.kl.bakup)
Hit 'Ok'
Make sure the file you just created exists.
[START MODIFICATION]
Long-press 'cypress-touchkey.kl' (again)
Hit 'Permissions'
Make sure that ALL THREE boxed under "Write" are checked, and hit OK.
Hit 'cypress-touchkey.kl' (yet, again)
Select Text > Text Editor
Here, you'll see something like,
Code:
key 139 MENU VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 217 SEARCH VIRTUAL
as you've guessed, the first part,
Code:
key ###
is telling which key this command (event) is for.
So we can intuitively tell that the number for our capacitive 'Back' button is probably 158.
the next section, 'MENU, HOME, BACK, SEARCH' tells Android what these buttons should actually do.
And a pretty good list of what an Android CAN do on a key-press is listed here: http://goo.gl/vrCvJ
From the list, lookup anything that starts with KEYCODE_ and you'll find a pretty good description of what that command ('event') makes Android do.
Just add this keycode, WITHOUT the KEYCODE_ part of the code, to where the current cypress-touchkey.kl reads 'MENU, HOME, BACK, SEARCH' (according to what you want which button to do, that is)
So, for example, I've remapped my 'Search' button to bring up the App Switcher (Recent Apps). (Long-pressing the Home button just didn't cut it for me )
So, my 'cypress-touchkey.kl' looks like this:
Code:
key 139 MENU VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 217 APP_SWITCH VIRTUAL
Now, save your modified 'cypress-touchkey.kl' by selecting,
Menu > Save, and the exit by selecting Menu > Exit.
To be safe, let's set the permissions back to what they were.
From the File Manager App, long-press 'cypress-touchkey.kl' > Permissions,
and un-check the lower two check-boxes under the 'Write' column, and hit "OK"
Now, reboot your phone, and see if all went well
I actually tried this mod on a ICS rom, expecting the ICS app switcher to pop up, but somehow, the APP_SWITCH event seems to bring out the GB Recent App thingy.
Functionally, it still works pretty well for me. But if there's anyone out there who has any information on how to bring out the all-new ICS App switcher with a key-event, I'd really appreciate it
Hope this makes someone's life easier!
Thanks for the post.
I've tried to remap my search key as you described, but the APP_SWITCH command doesn't seem to work? Nothing happens for me. When I switch the value back to "search" that command works again, so I know the have edited the file correctly.
Any ideas? Does the kernel/rom affect this? I'm running oxygen + franco kernel.
Thanks!
Edit: Spelling.
Thanks for this, will definitely try out soon!
Follow the leader @corythug
Any idea what the app switch command is on ICS
Sent from my Nexus S 4G using xda premium
The ICS app-switch is, in my opinion, the best way to use search button key on Nexus S with ICS rom.
Hope someone will be able to find the correct command ot for that and someother creates a flashable zip to do the mod easily from recovery
Is there any way to remap the longpress on capacitive buttons?
Sent from my Google Nexus S using XDA App
cahir_cz said:
Is there any way to remap the longpress on capacitive buttons?
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
That's what were trying to figure out
Sent from my Nexus S 4G using xda premium
Thanks for the guide, I'll try it soon. My last few phones were from HTC and I love (or rather am so accustomed to) their button layout.
Sent from my Nexus S 4G using XDA App
Zorrich said:
Thanks for the post.
I've tried to remap my search key as you described, but the APP_SWITCH command doesn't seem to work? Nothing happens for me. When I switch the value back to "search" that command works again, so I know the have edited the file correctly.
Any ideas? Does the kernel/rom affect this? I'm running oxygen + franco kernel.
Thanks!
Edit: Spelling.
Click to expand...
Click to collapse
I don't think neither rom nor kernel should affect how this trick works ... unless maybe the rom dev. explicitly made changes to how the key events work ... which is highly unlikely ;;;;
are you sure you changed ONLY the key-event part? (HOME, BACK, etc.)
you shouldn't change the number that comes after the 'key' part of the script.
... I can't seem to think of any other reason this wouldn't work for you. :'(
Tried this, doesnt work on my kellmsking miui 2.8.1 with francos kernel :/ Changing the file does not change the button behaviour
olorin86 said:
I don't think neither rom nor kernel should affect how this trick works ... unless maybe the rom dev. explicitly made changes to how the key events work ... which is highly unlikely ;;;;
are you sure you changed ONLY the key-event part? (HOME, BACK, etc.)
you shouldn't change the number that comes after the 'key' part of the script.
... I can't seem to think of any other reason this wouldn't work for you. :'(
Click to expand...
Click to collapse
Yes, I've only changed the key-event to APP_SWITCH. Actually, I even tried copy/pasting your code into the file, still didn't work.
Thanks anyways. At least I now know how to do it, just have to figure out why it doesn't work, haha.
When using this the old recent apps comr up, meh.
Sent from my Nexus S using Tapatalk
we need to find the correct keyword for triggering the new ics app switch and it will be great
Anyone got a configuration to recommend to complement the ICS on screen buttons?
brrip said:
Anyone got a configuration to recommend to complement the ICS on screen buttons?
Click to expand...
Click to collapse
I tried logcat to see what happens when it's brought up but i'm not a dev, I know some code buy don't have a computer to try and implement for testing
Sent from my Nexus S 4G using xda premium
I tried alogcat from the market. It didn't show anything of worth after a key press.
Sent from my Nexus S 4G using xda premium
any news about that?
provolinoo said:
any news about that?
Click to expand...
Click to collapse
+1!!!
Sent from my Nexus S
Would be pretty sweet idd
Greenthy said:
Would be pretty sweet idd
Click to expand...
Click to collapse
Agreed, would love to get this working on ICS.

[MOD][REQUEST] Disable Capacitive Buttons

I am currently running AOKP on my Tmobile version and enabled the onscreen navigation bar. Id like to know if we have a script that disables the capacitive buttons yet on this device, and if not, a request for a dev to make one. Thank you.
I haven't been able to disable them, but if you just want to have the capacitive buttons not light up snag "Screen Filter" as it lets you turn off the button lights (set it to 100% if you don't want to dim your screen). I also used "Auto Start (no root)" to have it start at boot.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Dandude159 said:
I am currently running AOKP on my Tmobile version and enabled the onscreen navigation bar. Id like to know if we have a script that disables the capacitive buttons yet on this device, and if not, a request for a dev to make one. Thank you.
Click to expand...
Click to collapse
What do you mean disable those buttons? Disable actions when pressing them?
So you have a huge useless bezel at the bottom of your screen?
Simple Line changes in the key map.
Sent from my SPH-L710 using Tapatalk 2
nabbed said:
What do you mean disable those buttons? Disable actions when pressing them?
So you have a huge useless bezel at the bottom of your screen?
Click to expand...
Click to collapse
Well mostly disable the light. I want to use the on screen navigation keys in AOKP as a substitute.
Dandude159 said:
Well mostly disable the light. I want to use the on screen navigation keys in AOKP as a substitute.
Click to expand...
Click to collapse
Are you for real?
I don't mean to be a **** but come on!
Settings/Display/Touch Key Light Duration/Always Off.
LOL i bet a lot of people didn't know that (including me).... i mean i've been to that setting before to see how long the lights could be "on" for. but never noticed there was a "always off" option
nabbed said:
Are you for real?
I don't mean to be a **** but come on!
Settings/Display/Touch Key Light Duration/Always Off.
Click to expand...
Click to collapse
Please don't be rude, especially because you are wrong. This option is only available in the stock touchwiz based rom. I am on AOKP.
Dandude159 said:
Please don't be rude, especially because you are wrong. This option is only available in the stock touchwiz based rom. I am on AOKP.
Click to expand...
Click to collapse
Sry. Reading comprehension was subpar on my part.
This is actually a very useful tool if available. On my Asus Transformer Prime, there is a lock setting that disables the capacitive buttons while you watch a movie or play a game. I know the OP wants to disable the capacitive buttons for the purpose of replacing it with the AOKP onscreen buttons, but I would like to have that ability just to disable it so that I don't accidentally press on those buttons while playing game or watching video. Like a quick setting from the notification bar to lock it would be perfect!
Ill be subscribing to this thread for when we get a daily driver AOSP rom on Verizon. I too would like to disable the capacitive buttons and have on-screen navigation buttons instead. I find the capacitive buttons are too hard to press when I want to and too easy to accidentally press when I don't want to.
Sent from my SCH-I535 using xda premium
So, I don't know how to actually disable the button function (I'm running task's AOKP rom) and I didn't like using that Screen Filter app to keep the backlight off since it keeps it in the notification bar.
However, it is pretty easy to keep just the backlight off. Go into Settings>Display>Custom Backlight Settings. Check the "Use custom" option and go into "Edit other levels...".
Change the value for all the different levels from 1 to 0. Reboot and enjoy!
clark44 said:
Simple Line changes in the key map.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Do you happen to know what or where this line of code is so that we may modify it...?
Thanks,

[MOD] Navigation Bar for CM10

Flashing this will enable navigation bar, and disable capacitive touch buttons on Nexus S.
Make sure to set the Backlight Dimmer delay to 0 using the NSTools, so the capacitive touch buttons don't light up.
If you are using the navigation bar, I recommend setting the LCD density to 200 or 190. Edit it with Rom toolbox, or
navigate to /system/build.prop/ro.sf.lcd_density=200 edit it with text editor and reboot.
Always do a backup before flashing. It should work for any JB rom.
To disable navigation bar, reflash the rom, restore the backup or flash disable nav bars.
You are doing this at your own risk.
Its based on Brainmaster's tweaks for android, all thanks goes to him.
Added files, they set dpi to 190 or 200 or disable Nav bars.
Screenshots please.
Gesendet von meinem Nexus S mit Tapatalk 2
AzN MusiQ said:
Screenshots please.
Gesendet von meinem Nexus S mit Tapatalk 2
Click to expand...
Click to collapse
You get these three buttons on bottom of your screen.
http://cdn3.digitaltrends.com/wp-co.../samsung-galaxy-nexus-review-home-buttons.jpg
Or you can just add
qemu.hw.mainkeys=0
To your build.prop and reboot. It works with every ROM I think. To disable, just set it back to =1.
Sent from my Nexus S using xda premium
But that won't disable the capacitive buttons
Sent from my Nexus S using xda app-developers app
Does DPI of 200 break the play store? I'm at 210 and its breaking some installs
tehkraft said:
Does DPI of 200 break the play store? I'm at 210 and its breaking some installs
Click to expand...
Click to collapse
First time I went from 240 to 200, I wiped googleplay, everything else worked okay, as far as I remember.
If you get FC's wipe that app.
If BLD is set to zero, this will just turn off the backlight right, but they will still work when pressed. Is there a way to disable them for real otherwise what's the point of the nav bars, right?
Sent using the xda mobile app
apatal said:
If BLD is set to zero, this will just turn off the backlight right, but they will still work when pressed. Is there a way to disable them for real otherwise what's the point of the nav bars, right?
Sent using the xda mobile app
Click to expand...
Click to collapse
They are disabled...
Serris said:
They are disabled...
Click to expand...
Click to collapse
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
apatal said:
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
Click to expand...
Click to collapse
Yes you are correct, I used NSTools, and set it to 0, I assumed its the same with CM settings, I will try to fix it. Thanks
EDIT: OK no go, CMsettings work like that, if its set to BLD 0 its always on, NSTools looks like overrides it.
great! this is working just great. really thanks! but i don't see any problem by leaving screen density to 240 though. been opened all apps installed on my ns
quick edit: i am using CM 10 nightly
What's about the menu button? Is it build in the apps? Can I configured them?
Gesendet von meinem Nexus S mit Tapatalk 2
AzN MusiQ said:
What's about the menu button? Is it build in the apps? Can I configured them?
Gesendet von meinem Nexus S mit Tapatalk 2
Click to expand...
Click to collapse
Yes you can see the three dots in the navigation bar, and in aplications
Serris said:
Yes you are correct, I used NSTools, and set it to 0, I assumed its the same with CM settings, I will try to fix it. Thanks
EDIT: OK no go, CMsettings work like that, if its set to BLD 0 its always on, NSTools looks like overrides it.
Click to expand...
Click to collapse
I'm using a script it works like a charm with 0 if you don't use bln.
Sent from my Nexus S using xda premium
BenHeng said:
I'm using a script it works like a charm with 0 if you don't use bln.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
So all you have to do, is disable BLN, and put below code(script) in init.d?
Code:
echo 1 > /sys/devices/virtual/misc/backlightdimmer/enabled
echo 0 > /sys/devices/virtual/misc/backlightdimmer/delay
Works for me at least
Sent from my Nexus S using xda premium
Tried the mod last night and it works! Unfortunately, my fingers are already too big for the default PDI, and reducing it to 200 won't really help me very much. Thanks for sharing this anyway. I'm sure some users have been looking for this.
Sent using the xda mobile app
apatal said:
Oh OK. So the zip turns then off already. Question though, in the BLD settings, setting it to zero turns off BLD meaning the buttons are always lighted up. I set it to 1 to turn it off almost immediately.
Sent using the xda mobile app
Click to expand...
Click to collapse
in order to turn off capacitive buttons follow these:
1. using root browser lit go to system.
2.then "usr" then " keylayout"
3. open sec_touchscree.kl > open as > text file > rb text editor
4. insert "#" in front of lines u want to make them stop working.
like
#key 158 BACK virtual
will make back button stop working.

Flashlight with volume up on regular S4?

So I switched from the active back to the original s4 and the option I miss the most is the flashlight option by pressing the volume up button on lock. Does anyone know of a way to do this with an app or other hack?
Sent from my SGH-I337 using xda app-developers app
mattpayne92 said:
So I switched from the active back to the original s4 and the option I miss the most is the flashlight option by pressing the volume up button on lock. Does anyone know of a way to do this with an app or other hack?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
There is a thread about this in the Apps section already.
I am also interested in this. The one thread I found was the one we're you have to download nova or apex launchers but that's not working. Any other way to do this without rooting?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
mattpayne92 said:
So I switched from the active back to the original s4 and the option I miss the most is the flashlight option by pressing the volume up button on lock. Does anyone know of a way to do this with an app or other hack?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You switched back too? I thought you were happy with your active? I switched back to the s4 today too, I missed the better camera and amount of accessories, plus my active had horrible.call quality (not sure of I had a bad one or what)
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Solange82200 said:
You switched back too? I thought you were happy with your active? I switched back to the s4 today too, I missed the better camera and amount of accessories, plus my active had horrible.call quality (not sure of I had a bad one or what)
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I loved the active but I'm with you on accessories. I bought a fairly nice case and there's so many more options for the future. Plus, if I ever want to replace the housing of the device, or even just change the color of the battery door, it'll be much simpler with the original S4. Also I don't think the Active will ever have the ROM and modifications support the S4 has even when/if they eventually get a custom recovery.
mattpayne92 said:
So I switched from the active back to the original s4 and the option I miss the most is the flashlight option by pressing the volume up button on lock. Does anyone know of a way to do this with an app or other hack?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i've used the nottach xposed mod on three different roms. works great!
mixlex said:
i've used the nottach xposed mod on three different roms. works great!
Click to expand...
Click to collapse
I'm on stock TW with Nottach and it doesn't seem to work for me (and a lot of other people). I've tried the shortcut option and the Nottach way (which basically is the same) and neither seem to work.
on any rom except mint jelly all mods have to be done through the xposed installer or nothing will work.you have to place the nottach Xposed apk on your sd card (or on phone storage i suppose) then you have to install with an app called xposed installer which you can get from the xposed thread. install the framework thru the xposed installer. After installing hit the module button top right and check the xposed module apk..All mods are done from there or nothing works. also when changing colors make sure the switch top right on the color choosing screen is turned on or again nothing works. give it one more try..
---------- Post added at 04:42 PM ---------- Previous post was at 03:57 PM ----------
mattpayne92 said:
I'm on stock TW with Nottach and it doesn't seem to work for me (and a lot of other people). I've tried the shortcut option and the Nottach way (which basically is the same) and neither seem to work.
Click to expand...
Click to collapse
https://github.com/rovo89/XposedInstaller.This is the link to the installer you need to get it to work. All mods done thru this app if not on mint jelly rom.
drsiddiqui1 said:
I am also interested in this. The one thread I found was the one we're you have to download nova or apex launchers but that's not working. Any other way to do this without rooting?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Don't get me wrong, I would love to do this as a flashable MOD for my DeOdexed stock (1st Gen P-Rom) without having to install anything else and I encourage anyone that can do it. I just pointed out the other thread in the APPs section so people interested can see if there is any further information in that thread that they might want to check out.
I think the "X-Posed" Mod and Nottach's contribution is awesome and potentially one of the best things that can happen for this phone, but just a simple MOD for the torch to work via volume keys sure would be nice.
mixlex said:
on any rom except mint jelly all mods have to be done through the xposed installer or nothing will work.you have to place the nottach Xposed apk on your sd card (or on phone storage i suppose) then you have to install with an app called xposed installer which you can get from the xposed thread. install the framework thru the xposed installer. After installing hit the module button top right and check the xposed module apk..All mods are done from there or nothing works. also when changing colors make sure the switch top right on the color choosing screen is turned on or again nothing works. give it one more try..
---------- Post added at 04:42 PM ---------- Previous post was at 03:57 PM ----------
https://github.com/rovo89/XposedInstaller.This is the link to the installer you need to get it to work. All mods done thru this app if not on mint jelly rom.
Click to expand...
Click to collapse
I have xposedinstaller and use nottach for more than trying to get the torch to work and nottach works fine. For some reason it just doesnt work for torch
Sent from my SGH-I337 using xda app-developers app
seems a little buggy on the torch..This is what works for me. With screen off, power button on,power button off, then volume up. Then it works, pretty much have to do it every time but at least it works that way for me. Also the setting for long press of brightness icon seems to work all of the time. Hope this works for you.
mixlex said:
With screen off, power button on,power button off, then volume up.
Click to expand...
Click to collapse
Doesn't work for me. Neither does switching music tracks with the volume keys. Anything involving volume keys just won't work using Xposed for me. :'( But the brightness shortcut works fine, I just wish the actual button hotspot was a little larger; I generally have to be sure to touch the very center of the icon for it to work.
Right now I'm just using Flashlight LED Genius, which turns on the torch on the lock screen when you shake it. Seems to work pretty well. And gives me some exercise!
johnus said:
Doesn't work for me. Neither does switching music tracks with the volume keys. Anything involving volume keys just won't work using Xposed for me. :'( But the brightness shortcut works fine, I just wish the actual button hotspot was a little larger; I generally have to be sure to touch the very center of the icon for it to work.
Right now I'm just using Flashlight LED Genius, which turns on the torch on the lock screen when you shake it. Seems to work pretty well. And gives me some exercise!
Click to expand...
Click to collapse
i have the same problem...
mattpayne92 said:
So I switched from the active back to the original s4 and the option I miss the most is the flashlight option by pressing the volume up button on lock. Does anyone know of a way to do this with an app or other hack?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
HEY! this rom has an add on for EXACTLY what you want. idk if you can use it on ur stock one but go to add on section
it works PERFECTLY (well, on that rom at least)
http://forum.xda-developers.com/showthread.php?t=2313469

[REQ] Remove 3 Dot Overflow in 4.3 Roms

Hi everyone,
Since I use a menu button in my navbar, I was wondering if there was a mod, that I could flash to remove the 3 dot menu. If there are none, I am willing to do it myself and have tried the following methods but they don't work for me. So if anyone knows of a mod or a guide, that would be great:
http://forum.xda-developers.com/showthread.php?t=2297692
The above link was the only one I could find, the rest mostly relate to HTC One threads.
Rom: Vanir Nighlty, Android 4.3 (AOSP Base)
EDIT 1: Here are the steps I tried:
To remove 3-dot menu:
Decompile your framework-res.apk
Go to values folder
Open bools.xml
Search for
<bool name="config_showNavigationBar">true</bool>
and change it to
<bool name="config_showNavigationBar">false</bool>
Recompile your framework-res.apk
I also made sure to sign the apk and zipalign it before putting it in a flashable zip
One thing I also tried, it was a long shot & it didn't work but I decompiled the framework of an MIUI rom since they have it enabled, and tried taking a few things from there but it didn't work
EDIT 2: I have already tried editing the build prop with a line from a HTC thread but it didn't work (phone wouldn't turn on)
Also, if anyone knows where menu-related stuff is within framework res that would be great because that would be a good place to test. (That's if the solution lies within framework res)
EDIT 3: Update: AOKP unofficial 14th September (4.3) still has the bug
Updated post with screenshots
I'm using Full screen toggle apk and LMT pie for navigation on stock 4.3 rooted and working well. See here http://forum.xda-developers.com/showthread.php?t=1497558
Melt1down said:
I'm using Full screen toggle apk and LMT pie for navigation on stock 4.3 rooted and working well. See here http://forum.xda-developers.com/showthread.php?t=1497558
Click to expand...
Click to collapse
I think you have misunderstood me. I mean the 3 dot menu in apps
bump
anyone??
22sl22 said:
bump
anyone??
Click to expand...
Click to collapse
Checking to see what I can do now
Sent from my Nexus 4 using XDA Premium 4 mobile app
melbourne408 said:
Checking to see what I can do now
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, much appreciated
Sent from my Nexus 4 using xda app-developers app
Bump, anyone?
Sent from my Nexus 4 using xda app-developers app
bump
bump too ...
as a start ... http://forum.xda-developers.com/showthread.php?t=1645052
http://mobility.forumsee.com/a/m/s/...hree-dot-menu-and-remap-multitask-button.html
xanthrax said:
bump too ...
as a start ... http://forum.xda-developers.com/showthread.php?t=1645052
http://mobility.forumsee.com/a/m/s/...hree-dot-menu-and-remap-multitask-button.html
Click to expand...
Click to collapse
Thanks xanthrax but I already tried that a while ago, I edited the build prop and my phone wouldn't turn on, so the search continues.....
Correct me if I'm wrong but I believe that the overflow menus you are referring to is coded into the app and not really dependent on anything else. Meaning that it is part of the app itself and not something the OS shows. Isn't that what Google's android interface guidelines suggests?
Sent from my Nexus 7 using Tapatalk 4
PMentior said:
Correct me if I'm wrong but I believe that the overflow menus you are referring to is coded into the app and not really dependent on anything else. Meaning that it is part of the app itself and not something the OS shows. Isn't that what Google's android interface guidelines suggests?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'm not a dev or app developer so I can't really comment on that. But I do know that some roms do have this feature on 4.3, it's just that it it doesn't work.
So im pretty sure the answer lies within the rom itself, not the apps maybe. Although im not even sure if the solution lies within framework res, it could be system ui or even at source, in git, which would make it out of my hands
I know that there are roms that can add the menus button permanently to the nav bar (PA can do this) but I have never seen one get rid of the menu overflow button within any apps themselves. Even back to 4.2 roms I never saw that type of behavior.
In fact now that I think about it when I still had my GS3 which has a physical menu button there still was the menu overflow button in some apps because that is what Google's app guidelines say to do.
Edit - I think what you are seeing about the htc one is about removing the black onscreen nav bar that shows up in apps that don't use the menu overflow button on app because the htc one has hardware keys but not a menu key.
Sent from my Nexus 4 using Tapatalk 4
PMentior said:
I know that there are roms that can add the menus button permanently to the nav bar (PA can do this) but I have never seen one get rid of the menu overflow button within any apps themselves. Even back to 4.2 roms I never saw that type of behavior.
In fact now that I think about it when I still had my GS3 which has a physical menu button there still was the menu overflow button in some apps because that is what Google's app guidelines say to do.
Edit - I think what you are seeing about the htc one is about removing the black onscreen nav bar that shows up in apps that don't use the menu overflow button on app because the htc one has hardware keys but not a menu key.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
There are roms on 4.2 that can remove the 3 dot menu because I used them. All roms (Or at least most) on 4.2 based off AOKP have the feature, i used to use Rootbox rom on 4.2.2 and Xylon rom and the feature worked perfectly. But if you look now on 4.3 AOKP builds, it just doesn't work for some reason
bump, updated first post
Bump
PMentior said:
Correct me if I'm wrong but I believe that the overflow menus you are referring to is coded into the app and not really dependent on anything else. Meaning that it is part of the app itself and not something the OS shows. Isn't that what Google's android interface guidelines suggests?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
The apps seem to know if the phone has a menu button or not.
Just throwing this out there but PAC has the overflow menu disabled by default!
If there was a way to port this to other roms I would be ecstatic!
But alas I do not know how to cherry pick commits and I have no idea where the commit is in PAC's GIT
You find me that commit and I might be able to add it and build it with a friend of mines help.

Categories

Resources