Changing an apk's Virtual Keypad Size? - Kindle Fire Themes and Apps

Hello! I've been reading around these forums for awhile, since i got my kindle for Christmas, and the information and support I've gotten from here has been astoundingly extensive, but now i need help with something specific.
I've gotten PSX4DROID working on my barebonesCM7 build but the virtual keypad displayed onscreen is too small for me to operate comfortably. Is there a way for me to change some settings in the programs code to, say, add another sizing option? One twice as large, but following the same emulation and placement parameters, and without breaking the program?
Actually all the buttons on my kindle are too small as I'm very big and tall, and have large fingers. I'd like to be able to do the equivalent of decreasing my screen resolution, or just increase the buttons real estate on screen in any way possible. but my main question is still whether or not i can do it to an apk at all, since i'll need that information in the future for other onscreen key generating programs.
Thanks in advance, guys! Seriously, this site is the best!

You could try reducing the screen DPI that might make them bigger.
http://forum.xda-developers.com/showthread.php?p=8184409

Related

Morphgear DPad with Visible Buttons in Landscape!!! (For HD2)

Ok so I posted some bit's of this already but I have refined the original "Proof of concept" design to something a bit more useable.
It annoyed me that I could not see the buttons in Landscape mode but I could see the sides of the screen when it is set to Autoscale. This set me to try and make a pad that would fit into the tiny slivers of screen left in landscape mode with "Autoscale" set.
This pad needs to be used in "AutoScale" mode on a WVGA screen such as an HD or HD2 This setting leaves a slither of screen each side of the screen that I have used to show the button placement. Don't get me wrong, you can't fit a Dpad in that area BUT you can easily mark top and bottom left of it and that's a start.
I find that my thumb is a bit lazy and I struggle a bit to use a square DPad, because of this I have squished it a bit to a more suitable rectangular shape, have a go and tell me if it's no good - If you imagine that the visible "strip" at the side is 1/4 of the DPads width then you should get it pretty easily. Please take a look at the attached picture though, I have made this pad a slightly odd shape because I find that I use left and right a cack load more than I use up and down. It may not be great for all games but I have found that it suits my thumb better than a standard equal layout. If you hate it then try using my original pad found here: http://forum.xda-developers.com/showthread.php?p=6339454#post6339454
Other than this the Start (ST) Select (SE), A, B, R1 and R2 buttons are all visible at the edge of the screen!
Currently the GBA pad is the only one I have done but I could easily modify this concept to cover all of the different systems - The only reason I haven't is that I only really play GBA games on my phone.
There is a readme included but I'd like some feedback so please bring it on!
Hey man, good job. I like the v1 rather than this, i find it harder to hit the up arrow with the new one, but it's not the reason why i'm wiriting this.
Both your pads makes the game laggy when i tap the white (unassigned) space. Other pads I've tried never did that. Any idea how to selve this? Or am i the only one experiencing this lag?
is multitouch available for morphgear?
Phenomenon said:
is multitouch available for morphgear?
Click to expand...
Click to collapse
It sure is you just need to download the tweaked version by blutz
xZdenis said:
Hey man, good job. I like the v1 rather than this, i find it harder to hit the up arrow with the new one, but it's not the reason why i'm wiriting this.
Both your pads makes the game laggy when i tap the white (unassigned) space. Other pads I've tried never did that. Any idea how to selve this? Or am i the only one experiencing this lag?
Click to expand...
Click to collapse
Hi I find that they all lag a bit, it seems to be the way that the Multitouch is implemented (I don't think it's Blutz, rather the original Morphgear crew), I find that when I have 2 buttons pressed all is fine but if I press NE and A (so 3 buttons reported to Morphgear) it lags until I release all buttons. This is just my laymans observation.
I could try producing an ultra light version to see if that helps... I think my skin is >2mb
Could you give me some examples of ones that don't cause it and I'll have a look, I wouldn't be overly surprised to find it was something I had done wrong. What we really need is the capacity to set white = NULL!

Gesture Input Method / Keyboard

I've done a cursory search looking for something like this but have been unable to find something...
Does anyone know if there is an app/keyboard replacement which has a screen much like the gesture search screen, allowing a person to draw individual letters and have them placed into the input box? Yes, it has shades of Graffiti (from the-company-which-shall-not-be-named), but would make typing while the unit is in a car dock, or just when standard keyboards are a pain in the ass, much easier.
I can't believe something doesn't already exist, so I turn to all of you.
Help me, XDA, you're my only hope.
+++++++++++
N1, CM6
+++++++++++
Well, it would appear something kind of comes close ... graffiti or stroke keyboard work, tiny input area. But MobileWriter looks to be very much along the lines of what I had envisioned, but does anyone know of something with the same sized writing area which doesn't cost 5 bucks?
I'll get mobilewriter if nothing turns up, but hey...free is cheaper than 5
Thanks!
Graffiti has been ported to Android. Search for it in the Market.
The input box is still quite small. I'm thinking of something where one could essentially be inputting with one hand (using the thumb of the hand holding the device) without even needing to look at it, so a large forgiving graffiti area would be best. Thanks for the tip though.

[App] Thumb Keyboard v1.5.1

Note (nov 30, 2010): By now there are two versions: a lite version, published here (free) and a full version (paid) on the market. The full version will be continuously updated with new features, layouts, styles and more. The lite version will get no more updates.
(feb. 16, 2011) New thread for the full (paid-for) version created here: http://forum.xda-developers.com/showthread.php?t=948179 . Please post your requests, questions, comments etc in that thread. Thanks
------ initial announcement ----------
New thumb keyboard for easy thumb typing. The idea is simple. I've split the keyboard in two halfs, took them apart and placed them above each other (see screenshots). Result: much wider keys...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Somehow the brains does the remapping remarkably well. Left/right to up/down doesn't seem a problem. The result is that the keys can be defined with a greater width and that for thumb typing the phone can be hold in much more natural way.
Press-and-hold the keyboard icon for switching between layouts, settings and selecting another input method:
I'm very curious what other users think about this concept... Also I'm very interested in getting feedback on the usability of this concept.
Site
App blog: http://thumbkeyboard.blogspot.com/
Little FAQ
Q: I don't see the keyboard after installing it
A: The procedure of selecting the keyboard is described in the screen you see right after you have installed the keyboard. It's described in the section "Selecting the Keyboard". You can consult this info at any given time by tapping on the Thumb Keyboard app in your app drawer.
Basically the procedure is as follows: go to the Android keyboard settings menu by selecting "Settings" or "Preferences" in your app drawer and then "Keyboard ...". In this menu check "Thumb Keyboard". Now, when you want to edit something and your normal keyboard pops up, long tap in the edit field and select "Thumb Keyboard" from the "Input Method" menu.
Q: How can I switch to another layout or set up my preferences for the keyboard
A: Also described in the info screen under the header "Setting up the Keyboard". Anyway... long press on the keyboard icon in the left corner at the bottom of the keyboard to access the settings menu and to switch layouts.
Q: I can't download the file that is attached to this post.
If you try to download it from your Android phone keep in mind that not all browsers support downloading apk files directly. You can either try another browser, use a download helper or download it from your pc/mac
Q: Will this keyboard help me to find answers to some urgent existential questions?
A: No. But you can always read a good philosophy book and make notes with this keyboard.
Q: Huh?
A: kidding
Changelog
v1.5.1 * missing accented characters added * solved spacing issues in the accented character popup keyboards * added a numpad popup keyboard (press and hold [email protected]) * Some additions to the help/info screen"
v1.5 * New Style * International (accented) characters * Popup Smiley Keyboard * Option to mark keyboard blocks with different colors * Numbers on the compact keyboard * Checkerboard Vibrate Pattern * option to set vibration strength * etc (Compatible with Android 1.6 and higher)
(Users who already downloaded the 1.5 version are adviced to download the (new) attached version again)
v1.4.1: Small update: * added a extra, redundant "g" to the "asdf" row to address more typing habits. * made the keyboard suitable for all possible screen densities
v1.4: *finally adapted the landscape keyboards for thumbtyping (see screenshot) *added new portrait layouts with a squeezed q for better accessibility of the t (see screenshot) *changed the layout of the symbol/num keyboards
v1.3: Added help info + caught a bug or two
v1.2.1: = 1.2 + little bug fixed (and . added to the first symbol screen)
v1.2: Changed the behavior of the Shift-key: *Double tap on Shift key to turn on/off Caps Lock * auto capitalize after period (can be turned off in preferences)
v1.1:
New additional small layout
QWERZ keyboard layouts (Big and Small)
(1 Gesture added) Swipe back for backspace
Sound bug fixed
Remember: long press menu icon for options and settings
v 1.0 release
Distribution
I will not allow any distribution of this keyboard without a explicit permission by me.
Full Version
The full version (with text prediction, themes, tablet layouts, resizable height, sound selection, auto quick fix, etc. etc.) is available on the Android Market and on AndroidPIT (paypal)
Like the concept. It is almost like my left and right thumb knew which keyboard to use. Maybe you can try changing one of the space keys for special characters or hard press on letters for special characters. I like the idea although I have to trade it for screen real-estate. Not bad, indeed a lot of work need to be done but I'm definitly keeping my eyes on the this. Thank you.
I'm an idoit I just notice the special character key is next the "g".
Sent from my T-Mobile G2 using XDA App
niscrome said:
Like the concept. It is almost like my left and right thumb knew which keyboard to use. Maybe you can try changing one of the space keys for special characters or hard press on letters for special characters. I like the idea although I have to trade it for screen real-estate. Not bad, indeed a lot of work need to be done but I'm definitly keeping my eyes on the this. Thank you.
Click to expand...
Click to collapse
thanks for your feedback. I've changed the layout a bit (concept remains the same). After some testing and some feedback from others I decided to place the spacebar, backspace key etc on the default location.. The result is much better.
this new version looks better!
i will try it very soon but is very unlikely for it to replace swype or swiftkey.
still, as soon as i try it i can give you some more feedback (will be about portuguese writing, i'm afraid)
Im testing this keyboard right now.
I just found a few bugs.
1. When starting writing caps lock is on and doesnt go off after the first letter.
2. Every time i use backspace it erases two lettrrs instead of one.
3. It may be me but im missing so much more lettrrs.
i believe most of my writting is done with one hand.
edit:
i gave up writing in my nexus. its too hard for me
i'm sorry and i hope you dont get mad at me but i'm not very confident in this keyboard. at least i tried it. hope you understand. stil... good luck
Sent from my Nexus One using XDA App
nutweevil said:
Im testing this keyboard right now.
I just found a few bugs.
1. When starting writing caps lock is on and doesnt go off after the first letter.
2. Every time i use backspace it erases two lettrrs instead of one.
3. It may be me but im missing so much more lettrrs.
i believe most of my writting is done with one hand.
edit:
i gave up writing in my nexus. its too hard for me
i'm sorry and i hope you dont get mad at me but i'm not very confident in this keyboard. at least i tried it. hope you understand. stil... good luck
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Don't get me wrong. I write this stuff because I need it myself and I share it because, you know, maybe others can use it too. So how can I be mad... I myself like and use this keyboard very much.
As for the bugs you reported. Yes, I can reproduce them and fix them asap.
BTW what makes this keyboard hard to use for you, the bugs or the layout
What does it look like in landscape orientation?
Edit fixed backspace bug. Shift key functionality is under review and reconstruction.
my biggest problem with the keyboard is that i'm missing too many letters. its like i was trying to say. i dont know why but i believe i dont miss as many with other keyboards, or they correct me, i dont know :\
the keyboard layout seamed like a really good idea but first i noticed i'm not using that much the two hands to write in my everyday writing. neither swiftkey, neither swype need two hands so i guess that may be my second problem. i dont get extra speed for using two hands with either of these two keyboards i'm used to.
Also, i believe you're taking too much of useful space for the keyboard. 2/3 of the screen is too much i think. maybe a solution with less used space? Another thing: at first i did understand the idea: get bigger and better letters. but now you have reduced the size of them again and they are just in a different position than the regular keyboards. why dont you try a little bigger than atm? you can remove the arrows and redistribute the numbers in the left overs. i will try to make a draw of my idea.
the two small bugs i reported are less of it
why dont you try to implement Dvorak keyboard. That keyboard was designed to increase the speed writing and the letters position was carefully selected. Also, it already has many languages configuration already selected so it would be only needed to change this configuration for each language.
more about it: http://en.wikipedia.org/wiki/Dvorak_Simplified_Keyboard
vezquex said:
What does it look like in landscape orientation?
Click to expand...
Click to collapse
i would have to say... it looks bad in my opinion it needs some reorganization in this landscape orientation
nutweevil said:
my biggest problem with the keyboard is that i'm missing too many letters. its like i was trying to say. i dont know why but i believe i dont miss as many with other keyboards, or they correct me, i dont know :\
the keyboard layout seamed like a really good idea but first i noticed i'm not using that much the two hands to write in my everyday writing. neither swiftkey, neither swype need two hands so i guess that may be my second problem. i dont get extra speed for using two hands with either of these two keyboards i'm used to.
Also, i believe you're taking too much of useful space for the keyboard. 2/3 of the screen is too much i think. maybe a solution with less used space? Another thing: at first i did understand the idea: get bigger and better letters. but now you have reduced the size of them again and they are just in a different position than the regular keyboards. why dont you try a little bigger than atm? you can remove the arrows and redistribute the numbers in the left overs. i will try to make a draw of my idea.
the two small bugs i reported are less of it
why dont you try to implement Dvorak keyboard. That keyboard was designed to increase the speed writing and the letters position was carefully selected. Also, it already has many languages configuration already selected so it would be only needed to change this configuration for each language.
more about it: http://en.wikipedia.org/wiki/Dvorak_Simplified_Keyboard
Click to expand...
Click to collapse
You noticed that you don't thumb type, it that case I understand all of your points. I designed the keyboard for use with two hands. The keys are wider (maybe as wide as in portrait mode and the height is, I think enough. So yes there is a big difference: look at the first row (qwert) and the 4th (yuiop) and picture them as 1 row, then you see what I mean.
Nevertheless, thanks for your comments. I'll see if I can use it.
Dvorak is a great keyboard layout btw, but a solution to a different problem.
i understood in the process that in order to help you, or in order to try to help you i need to use both thumbs. i'm doing it now.
its indeed easy to see that your keyboard is wider than default by looking at the qwert-yuiop.
i still believe the arrows arent needed. we have a finger to select where we want the cursor or a trackball... so... its just space used in my opinion.
i also believe that the shift isnt at the best spot. why do you require shift at such a great position? It isnt used that much.
the "?" should be near the "enter key". maybe instead of the backspace? i would place backspace in the "3" area, in top the the "op". maybe a little bigger than the others?
isnt the "t" too fair away from the left thumb?
nutweevil said:
i understood in the process that in order to help you, or in order to try to help you i need to use both thumbs. i'm doing it now.
its indeed easy to see that your keyboard is wider than default by looking at the qwert-yuiop.
i still believe the arrows arent needed. we have a finger to select where we want the cursor or a trackball... so... its just space used in my opinion.
i also believe that the shift isnt at the best spot. why do you require shift at such a great position? It isnt used that much.
the "?" should be near the "enter key". maybe instead of the backspace? i would place backspace in the "3" area, in top the the "op". maybe a little bigger than the others?
isnt the "t" too fair away from the left thumb?
what do you think? any valid thoughts now?
Click to expand...
Click to collapse
Yep, very valid thoughts Like this feedback. I have to say that some of your points crossed my mind when designing the keyboard.
Some points I want to address:
First, I think the shift key and backspace key are on the wright position because one expect those keys there while typing. I did some tests with some fluent thumbtypers with a previous version in which I moved the backspace to another position and they all, without exception were a bit disoriented. I think the same will be the case with the shift key.
Concerning the postion keys: I don't think they are a waste of space, but I really like more feedback on this. To go to a exact position by touching the location is not that easy is my experience. (For example: misspelling the word imagene and then going back to the e is much easier by pressing 3 times the left key than to select that position with a finger)
Thanks for your feedback.
EDIT: your point about the "t" being too far from the edge is a very good point. But then again it's better than in the landscape scenario.
Pure genius ! I am surprised no one has thought of this before. Just a questions
Is there a way to turn off the clicking noises ? My phone is on silent and I don't see anything wrong in the Sounds menu but yet the noises are there
MeOverTrance said:
Is there a way to turn off the clicking noises ? My phone is on silent and I don't see anything wrong in the Sounds menu but yet the noises are there
Click to expand...
Click to collapse
(Press-and-hold the keyboard icon for settings and fast selecting another keyboard)
here you have the option to turn it off but actually the keys keep making the sound =P
@appelflap
have you noticed you have 5-4-3 letters in the top left and 5-5-4 letters in the right bottom? what if you removed one line and got that "shift-z-x-c" in the same line as "y-u-i-o-p"? to extra "help", you could change the color of the keys. This way it would be a suggestion of which thumb (left or right) to be used.
i keep my idea: the arrows arent that great =P by removing those you could try this, i believe.
I love the idea but I really don't understand the point of it in it's current configuration. The keys seem to be the exact same size to me except they've been moved around. I mean, the keyboard isn't THAT small to begin with so unless the new configuration makes them bigger the only thing that seems to be accomplish is making my hold my thumbs in staggered positions... I don't see the benefit in that. (Maybe because I'm on an evo with a larger screen and therefore with a larger keyboard to begin with?)
I'm not going to refund since I want to see where this goes but I don't think it'll be my every-day keyboard for now. Good job though!
nolageek said:
I love the idea but I really don't understand the point of it in it's current configuration.
Click to expand...
Click to collapse
So you like the concept but you don't like the way it is implemented in the current configuration. That is something you must elaborate on, because it looks you have a interesting, implicit (not tacit) intuition.
The keys seem to be the exact same size to me except they've been moved around. I mean, the keyboard isn't THAT small to begin with so unless the new configuration makes them bigger the only thing that seems to be accomplish is making my hold my thumbs in staggered positions... I don't see the benefit in that. (Maybe because I'm on an evo with a larger screen and therefore with a larger keyboard to begin with?)
Click to expand...
Click to collapse
The keys are much wider. Just take the "qwert" of the first row and the "yuiop" of the fourth and picture them together in one row. The reason you think they aren't that much bigger is maybe because in comparisson to regular keyboard the height is smaller. The result is square keys with a simular height and width.
(I had to reduce the height because of the fact that I had to introduce more rows)
With regular keyboards I concluded that much of my typing errors were caused by hitting adjacent keys on a same row. That's what this layout is supposed to prevent and in my opinion it does a good job in that. The reducing of the height has no influence on the amount of errors I make. (I always thought that the extra height on regular keyboards was mere a suggestive thing)
In the end, what I'm trying to accomplish (and this is the most ambitious part), is to make blind thumb typing possible. I think with this layout that must be possible, only thing I have to introduce for this is a way to give thumbs some feedback so they can return to a fixed, initial position from where they can start of.. (like with a normal keyboard with markers on the "j" and "f")
I'm not going to refund since I want to see where this goes but I don't think it'll be my every-day keyboard for now. Good job though!
Click to expand...
Click to collapse
I hope you didn't feel obliged to donate. But thanks, also for your feedback. And please let me know if you have any suggestions, request etc. I hope with the comments and "thumb on" experience of users I can make this keyboard better.
nutweevil said:
(Press-and-hold the keyboard icon for settings and fast selecting another keyboard)
here you have the option to turn it off but actually the keys keep making the sound =P
Click to expand...
Click to collapse
****, you're right! In theory it worked remarkably well Expect a little bug fix real soon.
@appelflap
have you noticed you have 5-4-3 letters in the top left and 5-5-4 letters in the right bottom? what if you removed one line and got that "shift-z-x-c" in the same line as "y-u-i-o-p"? to extra "help", you could change the color of the keys. This way it would be a suggestion of which thumb (left or right) to be used.
Click to expand...
Click to collapse
What a great idea!!! Really, brilliant. Thanks, I will definitely implement this idea.
i keep my idea: the arrows arent that great =P by removing those you could try this, i believe.
Click to expand...
Click to collapse
I guess that everyone has his own preference in this respect. My plan is to make the non-qwerty characters configurable. (But maybe I sacrifice those keys when moving the upper keyblock one row down)
MeOverTrance said:
Pure genius ! I am surprised no one has thought of this before. Just a questions
Is there a way to turn off the clicking noises ? My phone is on silent and I don't see anything wrong in the Sounds menu but yet the noises are there
Click to expand...
Click to collapse
tapping-and-holding the keyboard icon will bring you to a setting menu in which you can not turn off the sounds (Kidding, It's a bug, but there you should have the possibility to turn off the sound)

My problems with touchscreen in general

Hi,
I would like to propose an idea, which so far is unavailable in the market, but nevertheless I see potential for development.
It stems from my frustration of using touchscreen.....whether it be handphone, or 7", or 10", I always have the problem of typing at speed, and always needing to correct as there is no standard keyboard. Yes, due to my past usage, the standard keyboard size is impt for a ease of use.
So I am suggesting:
a. a small pull-out keyboard, which can easily extend to the size of a standard keyboard. the touch and feel of "click" is needed, and impt, just like playing piano vs playing on a keyboard....u really cannot feel where to press without the demarcating separation between each keys. yes, typing at speed definitely means typing by feeling, and COMPLETELY NOT LOOKING AT THE KB AT ALL. Touchscreen cannot do that.
b. 10" is just nice for reading, esp if it matches the standard A4 size, as I have lots of ebook with that size. and gesture like zooming and pulling up is impt, so a touchscreen without the need of keyboard. Luckily u have that with Android, as I attached the keyboard to my development Android tablet (blizzard from Technexion) and the KB does not appear on touchscreen at all.
Frankly the finger is really BAD for pointing....scrolling up yes, but often, instead of scrolling up, it selected the item which my finger landed on. Whereas when I connect the moue to the tablet, put the mouse over a list, i can select by clicking, and yet scrolling up/down by the scrolling ball. Finger alone is really bad for telling the difference.
My 2cts ideas, please comment.
Peter Teoh

[Q] what is most responsible for IME cursor precision?

Hi there, not sure what is the confluence of factors....
But I find it horribly nasty in Lollipop with the google keyboard to place my cursor by tapping text I am editing. It just doesn't go where my thumb and eye thinks it should. It is getting more and more annoying.
I used Smart Keyboard Pro in KitKat, and it had a "calibration" subroutine that I thought was responsible for hitting the actual keys, but do you think it also helped text entry selection?
Do IME rules govern the text cursor placement? I am now used to the google keyboard layout but find the precision horrid.
Thanks for any thoughts on subject.
Hah. Just tested Smart Keyboard Pro again... after calibrating. It feels like I can enter text again right away. It was very buggy during the Android version bump, but updates have made it work great again!
Now just another layout reconditioning....d'oh
nednednerb said:
Do IME rules govern the text cursor placement?
Click to expand...
Click to collapse
Nope. All an IME can do is read what is in the text field (for correction) and what type of text field it is (plaintext, password, username, number-only, etc) through the system (not the text field itself), and tell the system to input keystrokes (it doesn't input them itself).
It has no direct contact with the text field itself.
A keyboard app is really just a UI and sometimes also a text corrector.
Hmmm. I wonder about how Smart Keyboard Pro works its "calibration"... and then I wonder why without fail, switching keyboard is letting me navigate the text field better.
Something in the story you give is missing perhaps. Text correction for instance indicates going "into" the text field...
I notice the little handle to drag the cursor also feels way less buggy. I was having trouble even grabbing the handle in Google Keyboard. It also looks like a different handle.
Maybe things have changed from KitKat to Lollipop....perhaps somehow related to not being able to use any alternative IME if the default IME was removed. I saw others complaining about that. Some input method functions that were "deeper than the IME apk" are now placed differently...
I am not a dev though and wouldn't know where to begin to look in version manifest to see this described.
It makes sense a keyboard app dev would try to make entry work better if they COULD somehow fool the screen to better "read my mind" which is totally the aim of Smart Keyboard Pro's calibration function.
Not saying you're wrong exactly, but curious because I'm always learning and enjoy understanding and my test has seemed to work in my favour!
nednednerb said:
Hmmm. I wonder about how Smart Keyboard Pro works its "calibration"... and then I wonder why without fail, switching keyboard is letting me navigate the text field better.
Something in the story you give is missing perhaps. Text correction for instance indicates going "into" the text field...
I notice the little handle to drag the cursor also feels way less buggy. I was having trouble even grabbing the handle in Google Keyboard. It also looks like a different handle.
Maybe things have changed from KitKat to Lollipop....perhaps somehow related to not being able to use any alternative IME if the default IME was removed. I saw others complaining about that. Some input method functions that were "deeper than the IME apk" are now placed differently...
I am not a dev though and wouldn't know where to begin to look in version manifest to see this described.
It makes sense a keyboard app dev would try to make entry work better if they COULD somehow fool the screen to better "read my mind" which is totally the aim of Smart Keyboard Pro's calibration function.
Not saying you're wrong exactly, but curious because I'm always learning and enjoy understanding and my test has seemed to work in my favour!
Click to expand...
Click to collapse
The only thing a keyboard app can "calibrate for accuracy" is on the keyboard view itself, not the text field. Both the text cursor and text field are 100% handled by the system and in some cases the app you're typing in, never the IME application.
Okay, thanks.. hmm. What kind of system features may be responsible for precision?
There are "responsiveness" differences between kernels and ROM combos... but assuming I like my ROM and kernel, what kind of potential tweaks to settings might make the touch screen more snappy and stable for text editing?
I notice thermal throttling when using phone when charging definitely worsens ability to type. Way more lag.. for example, cursor will jump around. Key presses will hang.
Thank you @Lethargy for your time spent thinking.
nednednerb said:
Okay, thanks.. hmm. What kind of system features may be responsible for precision?
Click to expand...
Click to collapse
I don't know what you mean here. It uses InputMethodManager/InputMethodService, and text fields are managed by TextView.
nednednerb said:
There are "responsiveness" differences between kernels and ROM combos... but assuming I like my ROM and kernel, what kind of potential tweaks to settings might make the touch screen more snappy and stable for text editing?
Click to expand...
Click to collapse
ROMs have no influence unless one has a terribly written feature which lags the entire thing. Kernels don't affect anything themselves either - the kernel settings do, which are also user tunable anyways (default settings on a kernel are usually just what the builder prefers themselves). Neither have anything to do with text cursor placement accuracy, and no ROM should be messing with how the IME works anyways as it'll cause problems for more people than solve.
And there isn't anything you can do to make it more accurate other than physically (via using a stylus or having smaller fingers), since each touch is registered on an individual pixel, not the entire surface area being touched.
nednednerb said:
I notice thermal throttling when using phone when charging definitely worsens ability to type. Way more lag.. for example, cursor will jump around. Key presses will hang.
Click to expand...
Click to collapse
Not necessarily thermal throttle. An IME will run fine on a Nexus 5 even if you underclock to 1GHz. More likely its just your CPU usage being high and the IME isn't as high a priority as what is keeping up lets say 75% of your CPU.
So perhaps I might have less lag if I overclocked a bit? I guess that is obvious...
Do you know of not too invasive methods of altering the IME priority or tweaking the touch responsiveness in general?
Also, I am being more careful about my large thumb's "one pixel" touch point, and I am noticing an improvement already.... although I had already switched back to the 3rd party keyboard which seemed to help right away with input accuracy.
I also found a google android issue with 51 stars regarding generally buggy input issues in the Nexus 5 on Lollipop... so I am not too crazy about noting my issue perhaps!
Thanks for your help in understanding IME, @Lethargy.
nednednerb said:
So perhaps I might have less lag if I overclocked a bit? I guess that is obvious...
Do you know of not too invasive methods of altering the IME priority or tweaking the touch responsiveness in general?
Also, I am being more careful about my large thumb's "one pixel" touch point, and I am noticing an improvement already.... although I had already switched back to the 3rd party keyboard which seemed to help right away with input accuracy.
I also found a google android issue with 51 stars regarding generally buggy input issues in the Nexus 5 on Lollipop... so I am not too crazy about noting my issue perhaps!
Thanks for your help in understanding IME, @Lethargy.
Click to expand...
Click to collapse
Overclocking might not help that much, and I don't know of an easy way to force priority.
I don't have such issues with any sort of IME, so it's likely a per-user issue rather than affecting everybody. I also use the AOSP and Google keyboard.

Categories

Resources