Is it possible to replace the menu button with the ICS Task Manager/Multitasker? like in the galaxy Nexus? I think even the icon looks similar in a way to a list of apps. This would be useful especially since ICS deals with this perfectly by showing a menu button when it doesn't detect it as a hardware button.
What do you guys think about this idea?
Why not just hold the home button to bring up recent apps..
Sent from my GT-N7000 using xda premium
joshnichols189 said:
Why not just hold the home button to bring up recent apps..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Cuase holding the home button for 1 or 2 seconds its not better than just pressing the menu button.
pachi72 said:
Cuase holding the home button for 1 or 2 seconds its not better than just pressing the menu button.
Click to expand...
Click to collapse
Agree. Home buttons degrade and break.
pachi72 said:
Cuase holding the home button for 1 or 2 seconds its not better than just pressing the menu button.
Click to expand...
Click to collapse
VTEChump said:
Agree. Home buttons degrade and break.
Click to expand...
Click to collapse
Yep, and because given the choice, I'm sure most will opt to use it this way. the menu button is getting deprecated as a hardware button and being implemented more and more inside applications.
Hopefully some more ICS ROM devs will see this and review this suggestion. I would love to know what they have to say about it.
I wouldnt mind a widget to do it either. That shouldnt be to hard to do.
moyajaya said:
Is it possible to replace the menu button with the ICS Task Manager/Multitasker? like in the galaxy Nexus? I think even the icon looks similar in a way to a list of apps. This would be useful especially since ICS deals with this perfectly by showing a menu button when it doesn't detect it as a hardware button.
What do you guys think about this idea?
Click to expand...
Click to collapse
+1.
Regards.
This was the first thing I wanted to do after installing ICS. The capacative buttons are mapped in /system/usr/keylayout/melfas-touchkey.kl;
Code:
key 158 BACK WAKE
key 139 MENU WAKE
I'm just not sure what to replace 'MENU' with. 'TASK'?
Hate to double post but I thought I'd share what I've discovered.
I tried replacing 'MENU' with 'APP_SWITCH' in melfas-touchkey.kl and sec_touchkey.kl and got the menu button to act just like the recents button, however there was then no way to access the menu
I had a brief look at the android source code and it looks like the value that decides to show the action overflow button in the toolbar is set depending whether the on screen buttons are being used. Not at all sure about that though and I've seen the new HTC one phones have a hardware recents button replacing the menu so it can't be impossible.
bootlessjam said:
Hate to double post but I thought I'd share what I've discovered.
I tried replacing 'MENU' with 'APP_SWITCH' in melfas-touchkey.kl and sec_touchkey.kl and got the menu button to act just like the recents button, however there was then no way to access the menu
I had a brief look at the android source code and it looks like the value that decides to show the action overflow button in the toolbar is set depending whether the on screen buttons are being used. Not at all sure about that though and I've seen the new HTC one phones have a hardware recents button replacing the menu so it can't be impossible.
Click to expand...
Click to collapse
Thank you for trying this and letting us know about the results. I was thinking if all fails maybe the search option that appears when you click and hold the menu button could be replaced with the menu?
Clicking the Old menu button = New app switcher
Holding the old menu button = Menu
how about that? I think most apps include a search icon if/when they include search functionality.
Had a brainwave today and got it 90% there. I decompiled framework-res.apk and enabled the navigation bar AND resized it to 0. This means the action overflow button shows up in apps without the galaxy nexus-like software keys getting in the way. I then remapped the menu key and it is working like a charm
Of course then there is the little issue of bringing up the menu when using a pre honeycomb app. The simplest solution for me was to use the pen's button+swipe up gesture. This isn't ideal and doesn't even work for people using CM9 or stock ICS.
Here is the modified framework-res for the Team Rocket ROM v1.5:
dl.dropbox dot com/u/2340506/navbarhidden.zip
These forums don't trust me with links
Install with CWM recovery. Don't use it on any other ROM! I can't even guarantee it'll work on every team rocket rom. I'm too lazy to load every ICS ROM but if you post your framework-res.apk I can edit it for you.
After you can remap the hardware keys in /system/usr/keylayout/melfas-touchkey.kl and /system/usr/keylayout/sec_touchkey.kl like I mentioned earlier with Root Explorer or ES File Explorer. I have it set up to mimic the HTC one phones and the galaxy nexus's layout, since I keep the key lights off.
Hopefully this is useful to people. A better way to access the menu on old apps should be easier to do once people start tinkering with the HTC one phones.
bootlessjam said:
Had a brainwave today and got it 90% there. I decompiled framework-res.apk and enabled the navigation bar AND resized it to 0. This means the action overflow button shows up in apps without the galaxy nexus-like software keys getting in the way. I then remapped the menu key and it is working like a charm
Of course then there is the little issue of bringing up the menu when using a pre honeycomb app. The simplest solution for me was to use the pen's button+swipe up gesture. This isn't ideal and doesn't even work for people using CM9 or stock ICS.
Here is the modified framework-res for the Team Rocket ROM v1.5:
dl.dropbox dot com/u/2340506/navbarhidden.zip
These forums don't trust me with links
Install with CWM recovery. Don't use it on any other ROM! I can't even guarantee it'll work on every team rocket rom. I'm too lazy to load every ICS ROM but if you post your framework-res.apk I can edit it for you.
After you can remap the hardware keys in /system/usr/keylayout/melfas-touchkey.kl and /system/usr/keylayout/sec_touchkey.kl like I mentioned earlier with Root Explorer or ES File Explorer. I have it set up to mimic the HTC one phones and the galaxy nexus's layout, since I keep the key lights off.
Hopefully this is useful to people. A better way to access the menu on old apps should be easier to do once people start tinkering with the HTC one phones.
Click to expand...
Click to collapse
Great finds! Thumbs up!
Thank you for your efforts!
I would love to try those but I moved back to Gingerbread for the time being. ICS in the note is far from being a daily driver for me. A lots of bugs and battery drains compared to Gingerbread. Hopefully this will change quickly. I trust the dev community and i'm sure they'll beat samsung in having stable ICS releases...
Back to ICS. Using ICS Stunner 4.3 ROM with the new LP5 kernel and modem. This setup is simply stunning. Best ROM I've tried so far.
Back to subject, how can the process go for AOSP ROMs? Like this one I'm using...
Anyone found any other way around this? Thanks !
Sent from my GT-N7000 using Tapatalk 2 Beta-5
moyajaya said:
Back to ICS. Using ICS Stunner 4.3 ROM with the new LP5 kernel and modem. This setup is simply stunning. Best ROM I've tried so far.
Back to subject, how can the process go for AOSP ROMs? Like this one I'm using...
Anyone found any other way around this? Thanks !
Sent from my GT-N7000 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1450138
I looked into doing the same thing as you did only because I love the tablet layout and holding the home button doesn't bring it up.
In order to get what you and a few others would want on select roms, the source for the framework would have to be adjusted as said in the thread, meaning each dev would have to implement this independently.
The second thing is alread mentioned in this thread, which is changing the key layout.
You can hope that the dev has no issues with inserting it into their build.
NOT changing the source but editing the key layout will only bring up the a Gingerbread styled task switcher. I've tried ;_;
I personally might I add, would just love the same hold the home button functionality while in tablet mode.
evilisto said:
1) change source code related to APP_SWITCH keycode.
platform/frameworks/base/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
from :
Code:
} else if (keyCode == KeyEvent.KEYCODE_APP_SWITCH) {
if (down && repeatCount == 0) {
showOrHideRecentAppsDialog(RECENT_APPS_BEHAVIOR_SHOW_OR_DISMISS);
}
return -1;
}
to :
Code:
} else if (keyCode == KeyEvent.KEYCODE_APP_SWITCH) {
if (down && repeatCount == 0 && !keyguardOn) {
try {
mStatusBarService.toggleRecentApps();
} catch (RemoteException e) {
Slog.e(TAG, "RemoteException when showing recent apps", e);
}
}
return -1;
}
2) edit your keylayout files..
/system/usr/keylayout/
for example, if you want to use search key to recent apps on nexus s...
cypress-touchkey.kl
Code:
key 139 MENU VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 217 APP_SWITCH VIRTUAL
and mxt224_ts_input.kl (it would be better to edit both files..)
Code:
key 158 BACK WAKE
key 139 MENU WAKE
key 217 APP_SWITCH WAKE
key 102 HOME WAKE
Click to expand...
Click to collapse
Related
Since the vibrant doesn't have a secondary input like most android devices, it's even more vital that we have unfettered access to the keyboard and its soft arrow keys. Unfortunately long pressing the menu button in some applications (notably the browser) brings up SEARCH rather than the keyboard by itself. That means no arrow keys for text selection or link highlighting.
This has been discussed previously in general at http://forum.xda-developers.com/showthread.php?t=776792
How difficult would it be to remap the long press of the menu key to bring up the keyboard by itself?
After researching it some on my own, it looks like I need to come up with a way to call showSoftInput() from one of the softkeys. It'd be ideal if I could get that to happen on menu long press, but if that's too far buried in proprietary configuration I'd settle for replacing the google voice search app mapped to the Search button long press.
Anyone have any tips on mapping system functions to a hardware key normally used for app launching? The lack of any keyboard in the browser is seriously inhibiting my ability to use this phone.
Dxtop pro does this, and long press back is tasks
Sent from my SGH-T959 using XDA App
fit333 said:
Dxtop pro does this, and long press back is tasks
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
yeah, buth then you have to use dxtop. *non fan of dxtop*
fit333 said:
Dxtop pro does this, and long press back is tasks
Click to expand...
Click to collapse
dxtop takes over the long press of buttons only in the home screen context, and it doesn't use any of them to launch the keyboard. Plus there's no way to configure any of it so it's not really the same at all.
What I'm looking for is to alter one of the long press actions in a system-wide way to launch the soft keyboard.
cbisquit said:
After researching it some on my own, it looks like I need to come up with a way to call showSoftInput() from one of the softkeys. It'd be ideal if I could get that to happen on menu long press, but if that's too far buried in proprietary configuration I'd settle for replacing the google voice search app mapped to the Search button long press.
Anyone have any tips on mapping system functions to a hardware key normally used for app launching? The lack of any keyboard in the browser is seriously inhibiting my ability to use this phone.
Click to expand...
Click to collapse
Have you tried emailing Anderweb? ADW launcher intercepts the home button. You might be able to do something similar. It might only work on the home screen though, as his app is running there. For a system wide thing you might need to mod the underlying OS files, framework maybe? I'm not sure where that stuff launches. You could try asking one of the Cyanogen devs, they might have found it. They add stuff to the power button long press menu at least.
Certain apps (Visual Task Switcher and Itching Thumb) remap the search and home buttons to open themselves. I imagine this same idea could be used for the menu button, but I've never seen it.
I don't always complain, but when I do, I #BlameWes
some success...
Well I got a little app to work at opening the keyboard on long press of the SEARCH key. I don't want to override the home function, which is what ADW for instance does. The only other button that has an available intent as far as I can tell is search. This is my first java anything, so I wouldn't expect much out of it (it may not even work on anyone's phone but mine) but maybe someone with better android chops can use it as a proof-of-concept for what I was thinking. Install it and when you long press the search key you can choose "Search for Keyboard!"
One pretty major caveat... the swype soft cursor doesn't act anything like I'd wanted when I was envisioning this. There's no "execute" button that works like a click, so while you can use the soft arrows to select links it's not gonna do you much good. Also there's no way to effectively use "select text" in the browser. Concept 2, if I ever get around to it, would probably be more like a replacement touchpad area below the current application window.
i would like to see an app to remap long press menu on my i9000, anyone has success? thx
Another reason to ditch Samsung firmware and use AOSP-based ROMs, like CyanogenMod or MIUI.
FYI, nearly every "ROM" made for Galaxy S phones are Samsung firmware. They're not built from source like ROMs for other decent Android phones, they are just original Samsung builds being modified like nuts. And they use the same Samsung framework (though usually customized for themes and removing of annoyances like battery-full popup), and usually still include most of Samsung's stupid fixes that make their Galaxy S system software the most different in structure compared to any other Android system.
By using AOSP firmware like CyanogenMod and MIUI, these problems (like menu-button keyboard binding getting screwed up by Samsung) don't exist, because they were never present in official Android release. When problems do come up for AOSP, they get fixed quick because the source code is actually available.
Summarized process of development:
Samsung-based ROMs: What's broken or runs like ****? Try to fix it. Hack hack hack, hope it works, if it fails try again. Submit to XDA
CyanogenMod (in general): If there is a problem, try to fix it. Write code, build, test. Make sure it works before putting it in "stable" branch. After that think of brand new useful feature to implement, code it, bug test a lot, request it to be used in official releases or just make your own CyanogenMod-based ROM with your own enhancements, like BiffMod for the HTC Dream.
Btw, the reason why Samsung put this keybind is because the original international Galaxy S doesn't have a dedicated search key, so they set the search function up with the menu button. Our problem is that Samsung was a lazyass and forgot to change back that binding to the original for the Vibrant, which does have a dedicated search button and doesn't need the menu binding to search.
But aosp roms have other problems like poor 3d performance and no gps/compass. If the issues get worked out, I suspect many devs will be switching to aosp builds.
Any apps to make it open something else?
Thanks.
there are plenty
quicksettings
quickdesk
handcent sms
are a few off the top of my head
i used to have a bunch more, but i have since uninstalled after trying nearly all the apps i want to try
(these will allow you to launch them by long press. i dont know if you can replace the short press)
Pretty sure short press is not easily changed. With froyo though longpress opens Google voice commands.
Sent from my SAMSUNG-SGH-I897 using XDA App
Nice.
Thank you.
id be interested in a kernel or rom that would allow this to be changed. long press on menu opens search so why a seperate key that can be usefull as something else? can any of those apps change the short press? ive only seen long press on search and on home.
I use visual task switcher and assigned the long press of the search key to bring up a list of currently running apps. Pretty handy.
I installed "screen lock" and assigned it to screen lock to take some stress off the power button.
I don't remember where, but I found a post somewhere on how to change it, short press on mine opens camera.
Button Shortcut in the market.
Sent from my Captivate.
Dani897 said:
id be interested in a kernel or rom that would allow this to be changed. long press on menu opens search so why a seperate key that can be usefull as something else? can any of those apps change the short press? ive only seen long press on search and on home.
Click to expand...
Click to collapse
AReynante said:
I don't remember where, but I found a post somewhere on how to change it, short press on mine opens camera.
Click to expand...
Click to collapse
wow, this is an old thread, for those interested dragon remaps the key as camera launch.
can be done in button remapper. also touch jestures can be mapped as keys in galay tuner.
for people who want to get custom and dont see the otions they want in button remapper, i think the key table is in /system/usr/keylayout/s3c-keypad.kl
this is good for fixing i9000 roms (partially) when no kernel is available for those who want to try samsung gingerbread
I like the long press for google voice search. Thanks for the idea.
If you end up flashing a ROM, CM7 has a way to change the search key in the settings menu
I took a look at the system/usr/keylayout/s3c-keypad.kl file but I'm having trouble figuring it out. Anyone know how to get more info on it? Would love to map QuickDesk to it
Dani897 said:
wow, this is an old thread, for those interested dragon remaps the key as camera launch.
can be done in button remapper. also touch jestures can be mapped as keys in galay tuner.
for people who want to get custom and dont see the otions they want in button remapper, i think the key table is in /system/usr/keylayout/s3c-keypad.kl
this is good for fixing i9000 roms (partially) when no kernel is available for those who want to try samsung gingerbread
Click to expand...
Click to collapse
OK.. I have the issue, seems quite random with the Search button. Am wondering if it is related to moisture from my palm (right-handed)... not sure. Will have to try the rice trick.
Have also taken a look at the remapping option, but don't seem to have write permissions to any of the files, much less, what values to place in the file(s).
Any assistance would be appreciated on teh edit option.
BTW: Captivate with CM7.1 (and a functional GPS after a number of patch/fixes applied)
cm7 has this option.
I'm an amateur at all this I've managed to get my nook color rooted, and I've installed a few apps. I've tried softkeys, but I'm not 100% happy with the result. First it wouldn't start on its own after a reboot. I reconfigured it following some directions form another user, and it starts now, but it's still too "busy", with bars and buttons popping up all over.
ALL I WANT is an app or some way to configure a "back" button and "menu" button in the lower black bar where the clock, bettery meter, etc are? Any ideas?
Either that, or is there a way to turn off ALL THE OTHER FUNCTIONS AND DISPLAYS of softkeys EXCEPT the ability to go "back" when pressing the physical "N"/home button, which is how I have it now.
In the end, I don't want any "back" or "menu" buttons on the actual viewable screen except the lower black bar.
THANKS a million!!!!!!!!!!!!!!
not quite what you asked for but i remapped my volume keys for menu and back. works great for my needs. i control volume with a widget now.
hxxp://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
hope this solves your frustrations with hotkeys.
nookcolor
zeam launcher
Well, if all you want is a back button on the notification bar..... you have one. Not talking about the back button that appears on there either. Just swipe left on the notification bar and it should always work as a back button.
Other than that, there's an app you can try called Button Savior you can get from the Market. It has a small launcher button that appears on the edge of the screen. You can move it around a limited range as you see fit. It's not as complicated or as "busy" as Softkeys.
If you find the visible button not to your liking, you can try this modded version of Button Savior. The button is invisible. You can see where the button actually lies by switching to the Sense UI theme. Then back to the default or Froyo theme to make it invisible once more. The modded version of Button Savior can be found here:
http://forum.xda-developers.com/showthread.php?t=897253
I suggest you try the Market version of Button Savior first.
I'm going to second Button Savior. It hasn't let me down once
Sent from my LogicPD Zoom2 using XDA App
g-costanza said:
I'm an amateur at all this I've managed to get my nook color rooted, and I've installed a few apps. I've tried softkeys, but I'm not 100% happy with the result. First it wouldn't start on its own after a reboot. I reconfigured it following some directions form another user, and it starts now, but it's still too "busy", with bars and buttons popping up all over.
Click to expand...
Click to collapse
You don't have Softkeys set up properly..
http://nookdevs.com/NookColor_Default_Launcher
I understand what you are looking for. I would like the same thing, but I do not believe there is anything out there for us..
I may end up remapping the volume keys myself.
spikey911 said:
I understand what you are looking for. I would like the same thing, but I do not believe there is anything out there for us..
I may end up remapping the volume keys myself.
Click to expand...
Click to collapse
With SoftKeys you can put the menu and back buttons in the notification area, since ver. 1.0.8 I believe. Then, disable the popper, and you are good to go.
Just wondering if people have done it and didn't like it, or vice-versa. It does seem bad for the hardware, but I can't stand softkeys/button saviour.
If you're using nookie Froyo, you can try the MENU/BACK soft buttons in the status bar mod, instead of remapping the vol+/- buttons. I've been using it since it came out, and can confim it works for nookie Froyo 6.7. Here's the link to the original thread: http://forum.xda-developers.com/showthread.php?t=932631
It does have it's issues, mainly with the stock browser, and causing it to FC. Other than that I have not noticed any other problems.
If you are interested in useing the mod, but don't know how to install it, let me know. I'll pm you or post instructions.
I absolutely recommend remapping the volume buttons. Softkeys is nice, but kind of a pain sometimes. For instance, when I would view pictures in the XDA APP, I would have to restart the app instead of backing out, for some reason softkeys wouldnt let me back out of the picture viewer. It's just much easier to have the menu and back buttons always available than rely on software. I installed volume volume control if I need to adjust volume for some reason.
Is there an app that puts volume in the status bar that anyone knows of?
buffnutz1 said:
Just wondering if people have done it and didn't like it, or vice-versa. It does seem bad for the hardware, but I can't stand softkeys/button saviour.
Click to expand...
Click to collapse
Yup... I've got a Pandigital Novel(white v2) w/custom fw and it'd be essentially useless w/o re-mapping the vol keys to menu and back along with soft-keys in the notification bar...
NC has one up on the WPDN though, it has the n home key plus the 2 vol keys and volume can be controlled through setting or a quick-settings app anyways or by adding soft-keys... still no substitue for physical keys or capacitive screen keys though, unfortunately... (spoilt by gtab with the full complement...)
-------------
buffnutz1 said:
I'm sure you guys know where I'm screwing up. After I adb pull, I only get this
/system/usr/keylayout/twl4030-keypad.kl -> ./twl4030-keypad.kl
/system/usr/keylayout/qwerty.kl -> ./qwerty.kl
/system/usr/keylayout/AVRCP.kl -> ./AVRCP.kl
but it says to edit " 'TWL4030_Keypad.kl' and 'omap_twl4030keypad.kl' "with your text editor of choice; I used vi, always a safe choice.
I don't have the omap. what should I do?
Click to expand...
Click to collapse
Just modify the qwerty.kl in the place of omap. That's what I did and things are working fine.
--ex
Love my remapped buttons and i saved the originals so i can go back anytime i wish.
buffnutz1 said:
Is there an app that puts volume in the status bar that anyone knows of?
Click to expand...
Click to collapse
I am on the stock 1.1 rooted and have mapped my volume buttons - I have tried the other ones, and I MUCH prefer having hard buttons.
I downloaded a volume app "Volume Master Free". It has about 5 different volume controls, but I only use the system volume and the media volume controls.
I use Zeam as home screen; and I put a shortcut to Volume Master on the bottom right of my Zeam shortcut bar. It works very well. I do need to go to the home screen to change volume; but I can tap on the notification bar and toggle mute, so that works for me.
Yes, it makes a huge difference on the stock rom and froyo -- though honeycomb's soft buttons eliminate the need to do so.
Can't recommend remapping the keys enough. On froyo it makes a huge difference in functionality on. The device, life is a pain without it.
how do you remap the vol buttons? i would love to do it
TweetyBear said:
how do you remap the vol buttons? i would love to do it
Click to expand...
Click to collapse
Go here for instructions:
http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
--ex
I remapped.
I also recommend remapping your volume buttons. It's handy having tactile buttons for the back and menu functions.
What really sold me on remapping was that I didn't like to have a Softkeys button floating on the home screen. Without a floating button, I would have to double tap the hardware "N" button to bring up the Softkeys interface, then hit "menu" or "back." If I have to double tap a hardware button to use "menu" or "back," I might as well just remap those functions to the volume buttons and use a single tap.
evilxenu said:
Go here for instructions:
http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
--ex
Click to expand...
Click to collapse
thanks. will attempt over the weekend
can remapping the volume buttons be done when running cm7 nightlies off SD ?
I didn't find a definitive answer
I ran with the CM7 softkeys, Button Savior, remapped volume keys and I just finally settled on zMooth.
So I have a general disdain for capacative buttons. I had planned to go into build.prop and add
qemu.hw.mainkeys=0
Click to expand...
Click to collapse
as well as go into /system/usr/keylayout/Generic.kl and comment out keys 158 and 172 (Back and Home respectively). This would disable the hardware buttons and enable software buttons. The problem is that every time I reboot, the system automatically restores the original versions of both files. Does anyone know how I could prevent this apparent safety function? It's proving far more of an annoyance than a benefit.
rougegoat said:
So I have a general disdain for capacative buttons. I had planned to go into build.prop and add
as well as go into /system/usr/keylayout/Generic.kl and comment out keys 158 and 172 (Back and Home respectively). This would disable the hardware buttons and enable software buttons. The problem is that every time I reboot, the system automatically restores the original versions of both files. Does anyone know how I could prevent this apparent safety function? It's proving far more of an annoyance than a benefit.
Click to expand...
Click to collapse
not until we have s-off. The emmc checks files against its last known configuration and discards any changes. Its been that way since the evo3d. its the same reason supercid wont stick also.
Well that's extremely disappointing. The buttons on here are driving me mad. Who thought it was a good idea to have the home button do three things not one of which is go directly to the homescreen? I was really hoping to get around them.
Any word on the S-Off progress?
rougegoat said:
Well that's extremely disappointing. The buttons on here are driving me mad. Who thought it was a good idea to have the home button do three things not one of which is go directly to the homescreen? I was really hoping to get around them.
Any word on the S-Off progress?
Click to expand...
Click to collapse
My home button goes to the home screen maybe you're holding your lips wrong
Sent from my rooted unlocked rommed HTC One, on the Sprint network.
benmatlock said:
My home button goes to the home screen maybe you're holding your lips wrong
Sent from my rooted unlocked rommed HTC One, on the Sprint network.
Click to expand...
Click to collapse
One press goes to whatever page of the launcher was last in use(not always a Homescreen, most often app drawer)
Double press goes to multi-task
Long press goes to Google Now.
There is no "always go directly to the homescreen" action associated with the home button.
rougegoat said:
One press goes to whatever page of the launcher was last in use(not always a Homescreen, most often app drawer)
Double press goes to multi-task
Long press goes to Google Now.
There is no "always go directly to the homescreen" action associated with the home button.
Click to expand...
Click to collapse
I find a 2nd press of home brings me all the way back home when app drawer, or non home blink feed was previously used...
tmuka said:
I find a 2nd press of home brings me all the way back home when app drawer, or non home blink feed was previously used...
Click to expand...
Click to collapse
So now you have two very different functions tied to the same action for a total of four actions associated with the Home button, none of which is "go directly to the Homescreen". What you present here is "Go to last page used in the launcher, then go to the default homescreen."
rougegoat said:
So now you have two very different functions tied to the same action for a total of four actions associated with the Home button, none of which is "go directly to the Homescreen". What you present here is "Go to last page used in the launcher, then go to the default homescreen."
Click to expand...
Click to collapse
Yeah, sorry, i realize i didn't answer your question. I hope you find the low level solution you're searching for, and that my tip helps you in the short term.
rougegoat said:
So I have a general disdain for capacative buttons. I had planned to go into build.prop and add
as well as go into /system/usr/keylayout/Generic.kl and comment out keys 158 and 172 (Back and Home respectively). This would disable the hardware buttons and enable software buttons. The problem is that every time I reboot, the system automatically restores the original versions of both files. Does anyone know how I could prevent this apparent safety function? It's proving far more of an annoyance than a benefit.
Click to expand...
Click to collapse
try flashing viper's zip here is the link
http://forum.xda-developers.com/showthread.php?t=2236849
HTC ONE
luisrod03 said:
try flashing viper's zip here is the link
http://forum.xda-developers.com/showthread.php?t=2236849
HTC ONE
Click to expand...
Click to collapse
No dice. The files are editable but have no impact.
Is there now any way to disable the hardware keys? I only want to have software keys (paranoid android 4.4 rc1)
Gesendet von meinem Nokia 3310 LTE