[TIP] CM10 - What to Do if Your Physical Keyboard Shift or Capslock Keys Don't Work i

[brandontowey]

EDIT - so seems this isn't working. Sigh, thought this was the end of this particular problem. I'll keep researching and post if I find something.

Found this on the Droid 4 forum (link below). So I always had an issue with not being able use symbols, capitalize stuff, etc. when using Chrome, Naked Browser, whatever. Figured it was a software issue but finally decided to Google it and the fix is easy:

-Settings
-Language/Input
- AOSP Settings
- Language
- Uncheck 'Use System Language'
- Scroll down, uncheck English
- Scroll Down to No Language - QWERTY (seriously, says that), check

Should be good to go. Not sure if it works on stock but worth a shot. I hated having to use my on screen keyboard for passwords and crap.

Soure: http://www.droidforums.net/forum/dr...shift-key-not-working-most-punctuation-4.html

 

[arrrghhh]

Ah, I did always wonder why some text fields seemed to be created differently than others...

Input field racism I tell you!

Nice find, thanks

Edit - just tried it, perhaps I need to restart... I still need to hold shift in order to get special characters to appear in fields on Chrome...

 

[brandontowey]

Yea, still having issues myself. Seems to work in the url field but not in password fields, etc. I'll see if I can find anything else in the link or online.

Sent from my XT897 using Tapatalk 2

 

[arrrghhh]

Yea, still having issues myself. Seems to work in the url field but not in password fields, etc. I'll see if I can find anything else in the link or online.

Sent from my XT897 using Tapatalk 2

Bummer, I was hoping I did something wrong, lol.

I'm trying to remember what apps were misbehaving here as well... there were a few, which probably just used webUI frontends for their app instead of making true context-aware Android fields.

 

[brandontowey]

I know it works in Words with Friends, text messaging and most other apps (can't remember any not working) and seems to be only in the browser. Really annoying but holding the shift key is better than before where I just opened up Swype.

Sent from my XT897 using Tapatalk 2

 

[arrrghhh]

I know it works in Words with Friends, text messaging and most other apps (can't remember any not working) and seems to be only in the browser. Really annoying but holding the shift key is better than before where I just opened up Swype.

Sent from my XT897 using Tapatalk 2

Oh holding shift in the browser always worked for me... I was always able to put in the special characters holding shift, even before this mod.

Still, it's confusing why different text fields receive different treatment...

 

[brandontowey]

It never even occured to me to hold the shift key down, honestly. I just dealt with it. I don't really know the inner workings of android well enough to say why it doesn't work but I think it's weird that it works in mobile apps like USAA and Ebay, which I always thought just took the website and displayed it in a better format than a browser.

Sent from my XT897 using Tapatalk 2

 

[GoodWiesKapot]

Hi,

First of a i'm not sure if this is the right place to ask this question, but it is hardware keyboard related. So if it is misplaced please forgive me!

How do you disable the special characters that are typed when you quickly double press for example the letter e. example: I want to type steel, but i end up with stél.

 

[mrvek]

Settings - Advanced - multipress. Two options, you pick one. The multipress interval let's you disable the feature completely.

 

[GoodWiesKapot]

Settings - Advanced - multipress. Two options, you pick one. The multipress interval let's you disable the feature completely.

Wow thanx a lot, didn't expect it would be so simple.

 

[brandontowey]

Still, it's confusing why different text fields receive different treatment...

So I was messing around a bit and it seems I don't need to hold the shift key to get a special character, just press the character key right after the shift key. I ridiculously quick press that requires two hands anyways. So maybe the browsers aren't correctly interperting the 'hold' the shift key normally sends (I know very little about coding so hopefully this makes sense) and releasing it way too soon? I think I've exhausted Google search options as of now.