I was browsing through the market and found a keyboard I'd never seen before, even thought it's apparently been around for quite a while. It's called Full Keyboard (http://www.appbrain.com/app/full-keyboard/com.hmw.android.fullkeyboard). What makes it so special is that it includes a directional keypad, complete with Home and End keys, a Camera key and a whole keyboard with nothing but control keys. Since I'm (currently) running TnT Lite I installed it using the "copy from /data/app to /system/app" trick and am finding it incredibly helpful in the terminal emulator and ConnectBot.
Related
I would like KforTP integrated onto my Fuze keyboard, but only for the shortcut keys on the bottom, while leaving every other key alone. This would most likely involve changing the keyboard input ROM or something. I'm not sure what to do, but if anyone could make a cab adjusting those 4 keys, that would be very helpful so people who don't use the shortcut keys on the bottom don't have to activate/unactivate KforTP every time a game emulator is used. Information would also be helpful too, thanks
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.
I've searched around and was amazed that nobody else mentioned this problem before.
I've only just received my Xperia X1 recently and love everything about it except its keyboard. I've used many phones with a hardware keyboard before, and they all have the standard navigation keys/buttons, like the UP, Down, Left and Right keys.
On the Xperia X1 however, it doesn't have that. But there're 4 keys that actually look similar to the navigation keys layout on a typical keyboard. It's the 8, 0, * and # keys. I'm trying to figure out how to map the navigational functions onto those keys......but can't figure out how.
I could use AEButton Plus but I'm looking for something easier, that doesn't use as much memory as AEButton Plus does.
I'm looking for something similar to the X1BC tweak, which basically uses the "TAB" key and assigns Control functions onto it, so that you can use CTRL+C or CTRL+V etc. Again, this is one of the annoying problems using this keyboard, you would think you can use control copy and paste easily but none of the keys on the keyboard does that, that's why X1BC is a tweak that changes the TAB key on the keyboard to use as the Control function as well.......and that's what i'm looking for, a tweak similar to this but for navigational functions instead.
chaoscreater said:
I've searched around and was amazed that nobody else mentioned this problem before.
I've only just received my Xperia X1 recently and love everything about it except its keyboard. I've used many phones with a hardware keyboard before, and they all have the standard navigation keys/buttons, like the UP, Down, Left and Right keys.
On the Xperia X1 however, it doesn't have that. But there're 4 keys that actually look similar to the navigation keys layout on a typical keyboard. It's the 8, 0, * and # keys. I'm trying to figure out how to map the navigational functions onto those keys......but can't figure out how.
I could use AEButton Plus but I'm looking for something easier, that doesn't use as much memory as AEButton Plus does.
I'm looking for something similar to the X1BC tweak, which basically uses the "TAB" key and assigns Control functions onto it, so that you can use CTRL+C or CTRL+V etc. Again, this is one of the annoying problems using this keyboard, you would think you can use control copy and paste easily but none of the keys on the keyboard does that, that's why X1BC is a tweak that changes the TAB key on the keyboard to use as the Control function as well.......and that's what i'm looking for, a tweak similar to this but for navigational functions instead.
Click to expand...
Click to collapse
fingerkeyboard though that might be what you don't want (due to memory consumption)
didn't find anything else yet, don't have much time right now...
thanks for the suggestion, but i don't want touch typing. I wanna use the navigational keys on the hardware keyboard....
After downloading and playing with a basic vt100 terminal emulator I soon noticed that there is no ctrl key on the hardware keyboard. In order to get a ctrl-c, for example, I have to press and release the volume lowering button to get "ctrl" and then the "c". This is very awkard. Especially with the keyboard fully extended! I later downloaded the hackers keyboard which has a ctrl key but it was not working at the time and I have reported it as a bug. Regardless, I would like the option to use the hwkb to do this. Perhaps this is premature as we don't have root yet, but is there a way to define say alt-shift, or the "ok" key or what ever to be ctrl. Also, while it is nice to have a fifth row of keys with numbers, I would think that these keys should have other functions too. Whatever one likes, i.e. alt 1 for F1 and so forth.
It is possible, there are apps in the Market, or you could hard code it into a ROM, but all of this requires root to my best knowledge, unless we have that I do not believe it is possible, but would be great if root wasn't needed, so if someone knows more hopefully they can let you know, but that's what I know.
search for Button Remapper, it is also on XDA: http://forum.xda-developers.com/showthread.php?t=850464
mscion said:
After downloading and playing with a basic vt100 terminal emulator I soon noticed that there is no ctrl key on the hardware keyboard. In order to get a ctrl-c, for example, I have to press and release the volume lowering button to get "ctrl" and then the "c". This is very awkard. Especially with the keyboard fully extended! I later downloaded the hackers keyboard which has a ctrl key but it was not working at the time and I have reported it as a bug. Regardless, I would like the option to use the hwkb to do this. Perhaps this is premature as we don't have root yet, but is there a way to define say alt-shift, or the "ok" key or what ever to be ctrl. Also, while it is nice to have a fifth row of keys with numbers, I would think that these keys should have other functions too. Whatever one likes, i.e. alt 1 for F1 and for forth.
Click to expand...
Click to collapse
I have the Official HP TouchPad Wireless Keyboard and I'm running cm9 0.6
Some keys on the Keyboard are non functional with ICS. For example
Brightness Control
Back and Forward Music
Notification Key
Card View Key (Could be used as home button)
Virtual Keyboard Toggle Key
and some others I cant think of
My point is, how can I make these keys functional to actually work
and
Is there any way someone could probably develop a driver that can be flashed via Clockwork Mod Recovery as a ZIP?
It would be a great help to us TouchPad Users running CM9 ICS
BUMP!
Sent from my Galaxy Nexus using xda premium
I'm actually very curious about this as well, I own the HP touchpad keyboard too and I really like it, it works really well on WebOS but when it came to android, many of the buttons don't work and it would be really great if these buttons could be remapped in some form or another.
Yeah, I would be interested in this too.
Some of the keys are easily fixable by editing /system/usr/keylayout/qwerty.kl - such as the media back/forward buttons. There's a keytest app out there which will capture keystrokes and spit out the numerical codes. You can then edit these codes in together with the desired commands into the kl file.
Other keys (keyboard toggle, brightness toggle etc...), however, do not trigger numerical keycodes at all when pressed; they seem to be using some WebOS specific command, or the Android driver simply is not written to recognise these codes. It looks like the driver would need to be modified for those keys to work - but I am no expert.
I'll try and post an edited kl file with all the keys which are recognised working later.
I have no idea on Android inputs work, but in Linux/X server there was a command line command that allowed you to directly capture keystrokes/events from a keyboard. Does android use X?
Just so you know, this thread will probably get moved, but I thought I would provide a link before it does.
http://forum.xda-developers.com/showthread.php?t=1379863
I havent applied this to CM9, but I would imagine that it shouldn't be too different.
Bump
Bump
Bump
Try using this app:
External Keyboard Helper
https://play.google.com/store/apps/...id.hwkeyboardhelperdemo&feature=search_result
You can use it to remap keys into android. Please report back if it works, as I want to buy a keyboard for my tablet, but dont want to deal with useless keys
I did find this review in the UK that mentions this app does help remap and get those uesless keys working:
http://www.amazon.co.uk/product-reviews/B0058CZX70?pageNumber=2
Quote:
This high quality Bluetooth keyboard measures 28.5cm by 13cm and weighs about 360g, including the two AA batteries that are supplied with it: slightly longer than my tablet is wide, but still small and light enough to carry round.
It is solidly made, matt black metal rather than plastic, with a stylish curving shape firmly supported on rubber feet - no wobble even on slightly uneven surfaces. The slope is perfect for fast typing. The keys are low profile and short-travel, full size, responsive and quiet. No sign that any of them is likey to come loose. There is no numeric keypad, but there is a row of function keys at the top to control the tablet - search, brightness, volume, on/off etc. Battery life is claimed to be about six months as the keyboard powers down when not in use and comes back to life as soon as you press a key.
The keyboard paired with my Sony S and with my Galaxy (both Android devices) without fuss and worked immediately, although three or four key mappings needed adjusting to match the GB layout. For this the External Keyboard Helper app is highly recommended - you just press "autodetect keyboard" and everything comes right.
As other reviewers have mentioned, there is no on/off indicator. The light next to the on/off switch on the underside of the keyboard seems to show that the device is visible for pairing, rather than that it is on. Again, the External Keyboard Helper is useful here because it flashes up a discreet message when a keyboard is not detected. I only found the lack of a light a problem on one occasion - the second time I used it. The batteries supplied were flat, so nothing worked. Fortunately, before hurling it at the wall, I remembered the old principle "check the simplest explanation first".
The lack of a caps lock light I did not find a problem - this probably depends on your style of typing.
Excellent value for money.