Hello fellow users from XDA,
I have a Galaxy S i9000 with a broken back button. That makes navigating pretty painful. In the rom called Slim Bean 4.2.2 Build 2 there are more options in the Hardware Keys section (including remapping the back button to, for example, the home button). I don't really like the ROM to be honest. My queston was, if there was a possibility to bring that to a different ROM (by flashing a ZIP-archive for example).
Greetings.
Rom developers generally do not respond to feature requests. You are better off trying to code it yourself.
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.
Details of the device
I'm using the latest CM11 version from Novafusion.
Problem and steps I've taken
Currently I've got a problem where the home button intermittently activates on its own (but only long-presses, so if I disable long-press in the OS, it'll be fine for normal operation), without any interference. The side effect (which is my main issue) of this is that it means my phone's screen effectively turns on by itself 24/7, which is obviously bad for many, many reasons.
I'm asking whether there's anyway I can disable the home button? I've tried Android-HomeKey-Locker (can't link it, but the Google Play version of the thing on GitHub) but it hasn't done anything.
I'm aware I can turn on the software buttons, but they don't deactivate the physical buttons: and I only want to disable home anyway.
So my question is, is there any way of doing this? I can take the back and menu keys if needed.
Side note
Is it possible in anyway to bind long-press back to home? I asked this for CM12 a while back (and I've since downgraded), but is this possible with Cyanogen, as I've been able to do it with Carbon ROM on 4.4.4.
Hi! I currently use this app on CM 12.1 to enable softkeys and disable hardware keys:
https//play.google.com/ store/apps/details?id=net.alviano.android.softbuttons&hl=en
sorry for my bad english
Hi
Try disable the home button by following this. it worked for me
http://forum.xda-developers.com/showthread.php?t=2032117
Hey everyone,
Thanks for the help. Someone on reddit gave me a working solution by using Xposed Additions to remap the buttons how I wanted them to.
Running Miui on my new Xiaomi Mi5, there was a really nifty feature where you could "soft touch" the home button to use is as the "home" button (instead of having to "click" it down).
It was a very useful thing! Is there a way of restoring this functionality in CM 13? I've worked out how to swap the back and menu buttons already, but haven't been able to find anything about this.
cangurob said:
Running Miui on my new Xiaomi Mi5, there was a really nifty feature where you could "soft touch" the home button to use is as the "home" button (instead of having to "click" it down).
It was a very useful thing! Is there a way of restoring this functionality in CM 13? I've worked out how to swap the back and menu buttons already, but haven't been able to find anything about this.
Click to expand...
Click to collapse
There are plenty of answers about this. It can be implemented only when kernel sources will be released.
Some new about it?
It's the only feature that I miss on my CM on Mi5.
Man, so glad to see this question here.
I'm sick of seeing the same ol' question being asked everywhere in the CM thread, spamming all around it.
Let the devs to their work. It's being developed here, so when it fully works will be added to the build. For now, it's GREAT to have official CM for our device. I'm keeping MIUI until it's good to go and to switch, BUT... I'm waiting
I would like soft home button as well.
Hope good devs will make it work one day
As a temporary solution, you can use this:
http://forum.xda-developers.com/android/apps-games/app-fingerprint-to-unlock-t3466549
Download fingerprint quick action in google play
The cyanogenmod maintainers for mi 5 are working on it
Hi,
I've bought several Android devices and since 2014 I really hate how the multitasking button replaced the menu button.
I just want to bring the menu button back and bring the multitasking section by long-pressing the home button, I really don't care about the Google Search functions.
The problem is, the phones I bought don't have any on-screen buttons and I really don't want to add a bottom panel for that.
I also know that GravityBox may be the Xposed module which can do that, but since it mostly applies to AOSP-based ROMs, I'm affraid of having conflicts with my phones' stock ROMs (Zenfone Selfie -ZE551KL- on Marshmallow).
Some apps that I found in the internet are quite old -pre 2014-, making them surely unsuitable for Android Lollipop and above.
So the question is: Is there any Xposed module -or even an app !- that can remap the bottom hardware buttons without conflicts ?
Have you tried out Xposed Additions?
Hi there, first of all I would like to thank you for checking the thread.
I require help with my Business Studies Project. I have to select a business or a company or anyone that makes a successful product and write an essay on why it's successful, make analysis on it; get some secondary research so I thought what better way to do it than start a thread on the XDA. I would really appreciate it if you guys could comment down below mentioning the things you really enjoy about RR OS and what is your favourite feature and if you would recommend it.
Thanks once again.
Help!!!
I installed the resurrection remix rom on my Galaxy S5, and I enabled the soft keys, how do I disable the hard keys? the capacitve buttons, are very annoying when you have soft keys enabled
RomBetaTester said:
I installed the resurrection remix rom on my Galaxy S5, and I enabled the soft keys, how do I disable the hard keys? the capacitve buttons, are very annoying when you have soft keys enabled
Click to expand...
Click to collapse
Go to settings - configuration - buttons
I really enjoy how customizable this rom is. I enjoy the fingerprint working I cant get that to work on most touchwiz based roms which is a shame.
I like the customization menu in settings and substratum theme engine.
Did it work?