6/29/11 Update: Add keycodes for EF02's "" and "Sym". Thanks EvilDennisR for providing the new keycodes, eyecannon for confirmation.
5/5/11 Update: Fix handling of ENTER key in fix_dead patch, i.e., make non-printable and emit carriage return. Thanks xbj9000 & Fnorder for pointing out this bug.
1/13/11 Update: Add key_logic patch from git to make ConnectBot use the correct hardware keymap, eliminating the need for the previous '_' & '-' swap workaround. Add fix_dead patch to fully implement combining accent (dead key) support. See note about combining accents on the Epic below.
12/20/10 Update: Add keep local connection patch. Add Tab, Home, End, Page Up/Down keys. Add partial support for Swype's edit keyboard.
12/1/10 Update: Fix use of arrow keys for moving the selection cursor when copying text.
Attached is a build of ConnectBot v1.7.1 modified to better support the Epic's keyboard. Also attached are the source patches against the v1.7.1 sources.
Changes are:
Make "" an alternate dpad-center (one press emits Ctrl, two presses emit Esc).
Make "Sym" emit Tab.
Make ".com" (Fn+"Sym") emit '`' (backtick, the only missing printable ASCII character).
Make arrow keys able to move the copy selection cursor.
Make "" and Enter (to support Swype's edit keyboard) select the copy region.
Make Fn+Left emit Home, Fn+Right emit End, Fn+Up emit Page Up, and Fn+Down emit Page Down.
Enable Tab key in Swype & other virutal keyboards.
Enable Home, End, & Cursor Jump in Swype's edit keyboard. Cursor Jump makes the arrows emit Home, End, Page Up/Down.
Workaround to make Fn+W emit '-' (hyphen/minus) and Fn+E emit '_' (underscore).
Make ConnectBot use the correct hardware keymap for the Epic, fixes the swapping of '-' & '_' and other subtle keymap bugs.
Although the hardware-keyboard changes are specific to supporting the Epic, this build should run fine on other devices--I don't think the keymaps conflict.
About the workaround: in regular ConnectBot v1.7.1, Fn+W emits '_' (underscore) while Fn+E emits '-' (hyphen/minus), which is backwards compared to other applications. I'm not sure why this is, as the key character map appears to be correct from what I can tell. This bug is due to ConnectBot's previous method of decoding key characters where it assumes the hardware keymap is the first one specified in the Android properties database (hw.keyboards.0.devname), which it is not on the Epic. A fixed method of decoding key characters was comitted to ConnectBot's github repo last month in a patch that also partially (brokenly) implements support for combining accents. I've added this patch and another to this release to fix both the swap bug and fully implement support for combining accents.
Note on combining accents: The standard Epic keymap does not include support for combining accents (dead keys). I've posted a modified keymap to add these. See the thread for details.
I've also added a patch to reenable the use of arrow keys (on both hardware and virtual keyboards) to move the selection cursor when copying text. You may use either "" (hardware keyboard) or Enter (both hardware & Swype's edit) to select where the start and end the copy region.
Unfortunately Swype's Select All, Select Text, Cut, Copy, and Paste keys do nothing in ConnectBot as they do not emit keycodes, but copy & paste support is availble via the menu, arrow, and Enter keys. Also, Swype's Page Up/Down keys simply generate 5xUp/Down arrows. Cursor Jump+Up/Down may be used a real Page Up/Down instead.
Enjoy!
Mirror links (does not require forum login):
connectbot-1.7.1-epic-6.apk
connectbot_create_outdir.diff
connectbot_fix_copy.diff
connectbot_keep_local.diff
connectbot_key_logic.diff
connectbot_fix_dead.diff
connectbot_epic_keymap.diff
connectbot_swype_keymap.diff
very nice, thanks much for this.
5 bucks someone makes a comment about how this is in dev and not in the themes and apps board tho
shabbypenguin said:
5 bucks someone makes a comment about how this is in dev and not in the themes and apps board tho
Click to expand...
Click to collapse
Crud, I figured I made a mistake somehwere.
I don't believe I can move the thread myself, would the powers-that-be mind placing this in the appropraite location? Thanks!
Thanks
Wrong forum or not, this is perfect, I was going to change my system keylayout to accomplish this before, but this is a much better solution.
Amazing, thanks for this! ConnectBot was near-perfect for my needs, you just pushed it over the finish line
Haven't tried it yet, but I was just about ready to do keymappings identical to yours at the android layer... I like your solution a lot better, though, thank you!
Thx for this op!!!
Sorry, but im just about a month into the "rooting scene" and am not yet familiar with what this is, can someone please explain?
Sent from my SPH-D700 using XDA App
this will allow you to change what keys do what, it is a very handy app
Will it prevent the Epic from missing keystrokes???
JungleJiujitsu said:
Sorry, but im just about a month into the "rooting scene" and am not yet familiar with what this is, can someone please explain?
Click to expand...
Click to collapse
ConnectBot is an open-source terminal emulator and SSH client for Android. If you're a Windows user, think of it as a combination of the "Command Prompt" and PuTTY programs, but for your phone.
The Epic is an important device for ConnectBot users as it's one of the few programs that really requires (or at least benefits from) a hardware keyboard. Unfortunately, the Epic keyboard, while very good compared to the Droid (and I'd argue the G2 also) is missing a few keys important for ConnectBot, but has other extra keys that are unused. So this is a modified version of the program to better support the Epic's keyboard, making ConnectBot much more convenient to use.
In general ConnectBot is not a particularly important program for "rooting" (although root makes it vastly more useful locally). As suggested earler, this thread should really belong in the Themes & Apps forum.
That said, I imagine ConnectBot is a somewhat popular program among Epic owners as its (near) requirement of a hardware keyboard makes the Epic a much more suitable device to use with it than the Evo, and so those folks interested in using it are more likely to purchase an Epic.
This is awesome. Thanks a lot! Now ConnectBot is pretty much perfect.
shabbypenguin said:
this will allow you to change what keys do what, it is a very handy app
Click to expand...
Click to collapse
So is it like what someone posted a few weeks back on how they changed the smiley face key to place an @ symbol instead, but only now with this app I can change it to whatever I want?... TIA
JungleJiujitsu said:
So is it like what someone posted a few weeks back on how they changed the smiley face key to place an @ symbol instead, but only now with this app I can change it to whatever I want?... TIA
Click to expand...
Click to collapse
shabbypenguin is incorrect. ConnectBot has nothing to do with altering keyboard mapping for the entire system. I just posted a modified version of ConnectBot that has altered keybindings internally.
As a terminal emulator, it is unusual compared to most Android applications in that much of the hardware keyboard support is implemented internally (from the keycode level up) instead of using standard input widgets.
Sorry for the confusion.
Awesome work. Is there a Ctrl shortcut on the regular build? I got stuck the other day because I couldn't Ctrl+C out of an app.
Sent from my SPH-D700
Forcystos said:
Is there a Ctrl shortcut on the regular build? I got stuck the other day because I couldn't Ctrl+C out of an app.
Click to expand...
Click to collapse
Not on the hardware keyboard. But if you tap the screen an icon "Ctrl" and "Esc" appear that you can tap.
Awesome, muchas gracias. Can we donate?
I'm curious... does this version still disconnect in local mode when a call comes in? I like Connectbot, but being disconnected while editing my script locally with vi editor, was something that irritates me with the version I tried from the Market.
After researching the bug, the only fix I saw was a different source tree with a fix included.
If this fix is included, it would finally replace the Android Terminal for me.
Thanks for working on this for the Epic, by the way!
Sent from my SPH-D700 using Tapatalk
DRockstar said:
I'm curious... does this version still disconnect in local mode when a call comes in?
Click to expand...
Click to collapse
The update I just posted fixes this now. Somehow I never managed to run into this, but I was able to reproduce the problem and it's pretty annoying. Thanks for pointing out the patch.
Alt key?
I cannot for the life of me figure or find out how to use the Alt key w/my Epic. What am I missing? It must be supported....
Let me start by saying I tried searching for a solution to this, asked a few people, no avail, so I am posting here hoping somebody has done something along the lines of what I am trying to do. I am having a little trouble with my jog tabs on my lock screen, the left one to be exact. Normally text pops up with "Unlock" or "Answer" when a call is coming in. Since changing my animation to the Bounce Animation found HERE the text has stopped showing. The jog bar does change to the correct color when sliding but no text. I looked through a whole Vanilla Rom of CM6.1 to look for a png that has the text but no luck. My guess it is controlled by XML, any idea on where the correct XML is that would need editing, and how?
Thanks in advance
Since upgrading to Gingerbread I have been aware of the new text selection features, i.e. dragging the little pin to move the cursor. What I can't get right though is selecting text.
Previously I could double-tap and drag in order to highlight words, which made sense, but now whenever I double-tap anything, I get the "Cut" and "Copy" menu before I can even start to drag. The two separate pins don't ever appear that way.
The only way I can seem to make it work is by holding on a word, picking "Select word" and then dragging the two pins when they appear, which seems a little drawn out compared to before.
Anyone any clues? Have the gestures changed? Am I doing something wrong or is this just the way it works now? Wondering if someone with a Nexus S or other custom Gingerbread ROMs can also confirm.
I don't know in which apps you have tried this, but the way it works in the browser and gmail (checked right now) is that you:
1.Tap and hold to go into text-selection mode
2.Drag your finger over the text you want to copy
3.Adjust with arrows as you see fit
4.Click on the selected text to copy it
5.Profit
SBS_ said:
I don't know in which apps you have tried this, but the way it works in the browser and gmail (checked right now) is that you:
1.Tap and hold to go into text-selection mode
2.Drag your finger over the text you want to copy
3.Adjust with arrows as you see fit
4.Click on the selected text to copy it
5.Profit
Click to expand...
Click to collapse
Ah ha, I see, that seems to work for reading emails and web pages. I was more meaning inside text-entry boxes like in the SMS app, Google Talk, etc.
Sorry for the long post.
Aright so here is the deal. We are making MattedGreens into an apk for theme chooser. We have great looking buttons. But for some reason, every time I change the buttons out, root explorer stops writing on them. At first I though It was because they were just to dark. So I switched it up. No luck. Then I figured I would try a plain white button. Again, only root explorer wont display text on them. I have tried making the 9patch huge, and also tiny. Nothing works. I then tried using the stock buttons. Which work normally, but as soon as I put them in my apk and install, root explorer wont display text on them. The specific buttons are the mount r/o(r/w) and when you click menu>>multiselect. So I figured I would pull Androdian and try those buttons. No luck still.
Does anyone have any ideas? Why it works for every other theme, and for stock, but not when packed in my theme? This is really frustrating me. Any suggestions are appreciated
I should also add this happens to the send button in mms as well. But the 9patch is the exact same!
Hello, people, i have a few questions to you :
1. I want to change the picture, which appears when i shut down Nook using "Power Menu" and software button "Power Off". It was told to me, that this picture resides in folder /res/drawable-mdpi/(cold_boot_screen.png) in framework-res.apk, but i cannot find such a file - cold_boot_screen.png ?
2. I want to change the loading picture, when NST is starting - where to locate it ?
3. I want to change the picture for charging of e-reader, where to find it ?
(i can't remember if there is a difference in pictures when charging thru usb or thru charger ?
4. I want to change the pic/screensaver for standard unlock screen , where is it ?
I will be very grateful for your assistance !
gsms said:
Hello, people, i have a few questions to you :
1. I want to change the picture, which appears when i shut down Nook using "Power Menu" and software button "Power Off". It was told to me, that this picture resides in folder /res/drawable-mdpi/(cold_boot_screen.png) in framework-res.apk, but i cannot find such a file - cold_boot_screen.png ?
2. I want to change the loading picture, when NST is starting - where to locate it ?
3. I want to change the picture for charging of e-reader, where to find it ?
(i can't remember if there is a difference in pictures when charging thru usb or thru charger ?
4. I want to change the pic/screensaver for standard unlock screen , where is it ?
I will be very grateful for your assistance !
Click to expand...
Click to collapse
All of these task require a rooted NST. Have you rooted your Nook yet? If you have, search the Nook Touch General and Nook Touch Android Development forums. There are detailed instructions in those forums for what you want to do.
I never actually power off my Glow Plus, so I can't say that the screen annoys.
The same goes for the power off charge screens.
The suspend screen was screwed up and I fixed both the mechanism and the images.
I've forgotten by now what exactly my complaint was.
The power off charge icons are stored in the boot image under /res/image/charger.
I normally just hit the power button briefly to put the Glow Plus in suspend mode.
Even if I forget to do that the power consumption does not seem to be large.
With occasional syncing, I hardly have to explicitly charge the battery.
I'm sure I posted it somewhere here, but I made a patch to fix the rotation of the suspend images
It's available under the mergesmali page in my signature as nook45patch.zip
You just modify and replace (using adb, apktool, mergesmali, apktool, adb) android.policy.jar
I still can not find the location of these 2 pictures in NST...
Any help will be highly appreciated !
I've never seen anything like that. Is it the original 4.5 software?
That says ReLaunch in the top left. Presumably you have replaced the standard launcher with ReLaunch and those are the default images for ReLauch, NOT the proper Nook screens.