Keyboard skipping keys a "known" issue with EB13?

Search This thread
By:
Advanced…
qbking77

qbking77

Senior Member
Dec 2, 2010
2,768
5,369
Chicago
Okay, so i called a sprint store today and talked to a rep named Ozzie. I told him, "My samsung epic's physical keyboard skips keys when I type on it every once in a while." His response was, "oh well the froyo they released has a great deal of bugs involved such as the camera and sd card." I asked him if the keyboard skipping keys was a common problem with the update and he told me, "yes that is very common." He told me to wait for the "new" update that is supposed to be coming out within the next week (yeah, right). I didn't realize eb13 caused this issue...

UPDATE: Talked to a sprint rep through chat and this is what he said,

17:41:52 : Tim: Initial Question/Comment: I received the eb13 froyo update for my Samsung Epic and now my physical keyboard skips keys every once in a while. I press on the key and it still skips. I was told by a sprint rep that it was a known bug with eb13 and it should be fixed with another update coming soon.

17:41:57 : You are number (2) in queue.

17:42:02 : Please wait and the next available account specialist will be with you shortly.

17:42:07 : You are next in queue...

17:42:12 : Jonas S has joined this session!

17:42:12 : Connected with Jonas S. Your Reference Number for this chat session is 2290211.

17:42:12 : Thank you for contacting Sprint. My name is Jonas S.

17:42:20 : Tim : Hi

17:42:39 : Jonas S: Hi.

17:45:19 : Jonas S: I understand your concern that you are not able to use froyo update with you EPIC, I apologize to inform you that this is a know issue and most of our customers have this issue with epic but you don't worry our technicians are working over this and soon this will be fixed

17:45:51 : Tim : Really? And what if this issue is not fixed?

17:47:24 : Jonas S: Actually due to some issues froyo has been removed from our server and we are diligently working on this, I will provide you a link where you can view this once it is available

17:48:27 : Tim : Okay. So what if the release they come up with next doesn't fix the issue? Will I be able to get a new phone that doesn't have this problem? (Since it is a known issue that sprint caused)

17:50:09 : Jonas S: I certainly understand your point but the new update will fix the issue you will not need to change the phone. I understand how it feels to pay for something that does not work up to your expectations. I re apologize for that

17:50:36 : Tim : Okay. So the update will fix the issue?

17:52:34 : Jonas S: Yes, be assured this will fix the issue, most of our customers using epic are facing this issue so we have been working over this and soon we will come up with new update

17:54:01 : Tim : Okay thanks for your help

17:54:14 : Tim : one more thing

17:54:18 : Tim : any eta on the update?

17:54:24 : Jonas S: You're welcome and thank you for you understanding in this regard.

17:54:24 : Jonas S: Sure

17:56:24 : Jonas S: Please let me know your second concern

17:56:40 : Tim : what do you mean?

17:57:19 : Jonas S: Oh, got it, you meant is there any expected time when this will be available, right?

17:57:24 : Tim : yes.

17:58:49 : Jonas S: I don't want to provide you incorrect or false information, as of now we do not have any expected date, you can view the link below and once it is available it will be updated there

17:59:23 : Tim : Alright thanks

17:59:29 : Jonas S: http://shop.sprint.com/en/software_downloads/pda_smartphone/index.shtml

17:59:59 : Jonas S: You're welcome

18:00:09 : Jonas S: Is there anything else I can help you with?

18:00:28 : Tim : Nope thats all. Thanks Jonas

18:01:03 : Tim : wait

18:01:14 : Jonas S: Sure

18:01:19 : Tim : Is there a reason the epic isn't on that link?

18:02:29 : Jonas S: Yes, once the updated version of friyo is available, this phone will be there

18:02:40 : Tim : Alright, thanks again. Bye

18:03:19 : Jonas S: You're welcome, thank you for your time with us and have a great weekend

18:04:23 : Jonas S: It’s been my pleasure to serve you. Please don't hesitate to chat again at sprint.com.
 
Last edited:
styckx

styckx

Senior Member
Sep 15, 2010
2,844
1,466
47
Keys skipping was on di18 also, just very very very less common. The nearly one skipped key a sentence crap started on dk28, eb13 is improved to about one skipped key every 2-3 sentences.

Sent from my SPH-D700 using Tapatalk
 
Y

yogi2010

Senior Member
Dec 22, 2010
2,120
319
Los Angeles, CA
I agre that this issue is worse on DK28 and EB13 than on DI18..... (I'm on EB13 right now, and made several 'mistakes' just typing this!) kind of unaceptable for such an expensive phone.... but oh well. I hope the next update fixes it, but I'm not holding my breath after all that has happened recently.
 
J

JPhantom95

Senior Member
Dec 23, 2010
150
26
Turning off Swype helped my issue but did not fix it completely and I still fail the "qaol" test.
 
S

Sesquipedalian

Senior Member
Apr 23, 2007
145
57
Nashville, TN
I skip letters almost every other word. It's next to impossible to use the physical keyboard on EB13. Double letters (like tt in letters) will always skip the second one.

I returned my phone once for skipping, and the second one was just as bad or worse than the first one. DK28 was worse than DI18, and EB13 makes using the physical keyboard pointless.

So frustrating. I otherwise love the phone!

Also, turning of Swype doesn't help at all. Even removing the apk doesn't help. Using touchpal prediction for the hardware keyboard fixed the problem in a way, but it's annoying it a whole new way.
 
Y

yogi2010

Senior Member
Dec 22, 2010
2,120
319
Los Angeles, CA
since the problem seems to vary by OS, it should be software-related.... that's the good news, I suppose. I wish I knew what was involved in fixing it, and hopefully the next update will fix it.... but I'm not counting on it. but yeah, DI18 seems the best for typing.
 
Last edited:
B

badasscat

Senior Member
Aug 11, 2009
139
14
I didn't have this problem *at all* on DI18. It started for me on DK28. Definitely software-related.

I do believe it is some service or app interfering with the keyboard. I do have days when I have no skipping at all, even now. But I don't know what I do to enable that. I am one of those people that randomly force closes various things when my phone gets frustratingly slow, so I think there's something that I occasionally shut off that does it, but it probably automatically comes back.
 
S

Sesquipedalian

Senior Member
Apr 23, 2007
145
57
Nashville, TN
Some people have hypothesized that it's related to the long key press opening a selection of extended characters. It seems plausible, but I haven't the faintest idea how to remove that feature. I've never used it, and doubt I ever will.
 
Top Nurse

Top Nurse

Senior Member
Sep 20, 2010
1,077
62
Palm Bay, FL
I think this is related more to the size of the fingers and the speed of the brain more than a problem with the hardware or software.
 
Top Nurse

Top Nurse

Senior Member
Sep 20, 2010
1,077
62
Palm Bay, FL
styckx said:
1/10

Try harder
Click to expand...
Click to collapse

I happen to have big fingers. It is also a known fact that the brain runs faster than the fingers. So skipped keys (or added ones) are a known problem since the days of the first typewriters. Unless you guys can somehow separate the keyboard from the phone so as to perform some scientific testing, I will go with my previous statement. :)
 
qbking77

qbking77

Senior Member
Dec 2, 2010
2,768
5,369
Chicago
Top Nurse said:
I happen to have big fingers. It is also a known fact that the brain runs faster than the fingers. So skipped keys (or added ones) are a known problem since the days of the first typewriters. Unless you guys can somehow separate the keyboard from the phone so as to perform some scientific testing, I will go with my previous statement. :)
Click to expand...
Click to collapse

The arrogance.......

Sent from my SPH-D700 using XDA App
 
C

cheapfx

Senior Member
Jan 1, 2011
55
3
Kinda related. Do you guys have the problem when you slide out the keyboard to do a quick "just type" search that it ALWAYS fails to register the first key press? When my phone is sleeping and I kick open the keyboard to search in google it never fails that first letter is always gone.

Sent from my SPH-D700 using XDA App
 
F

formula84

Senior Member
Aug 17, 2007
2,194
390
Philadelphia - HTC One (m7)
cheapfx said:
Kinda related. Do you guys have the problem when you slide out the keyboard to do a quick "just type" search that it ALWAYS fails to register the first key press? When my phone is sleeping and I kick open the keyboard to search in google it never fails that first letter is always gone.

Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse

Yes LWAYS (just switched to ladscape) lol, sometimes it puts in a letter of it choice without even touching the keyboard.
 
You must log in or register to reply here.

Similar threads

F
EB13 Releases from Samsung Website (download)
Replies
374
Views
58K
Y
yogi2010
sonarchist
  • Sticky
Damaged microSD Card...(this is how I recovered my Data)
Replies
143
Views
518K
M
mody737
A
EB13 Bugs (And Some Fixes)
Replies
294
Views
40K
J
Jedi2155
incisivekeith
Update: List available now of issues in Froyo (EB13) for Devs and SamsungJohn
Replies
217
Views
36K
T
twolostminds
O
EC05 update.zip *Direct Google download!* (For both DI18 and EB13)
Replies
195
Views
39K
N
notsosmrtgeek

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 6
    M
    mkasick
    Folks, it's another kernel bug.

    If you open a shell ("adb shell", ConnectBot Local, etc.) and check the output of dmesg after typing on the keyboard a bit, you'll see debug output from the kernel keyboard driver. For example, after typing "hello", dmesg reports:
    Code: 
    <3>[31195.737437] [key_press] keycode=26
<3>[31195.838771] [key_release] keycode=26
<3>[31196.057429] [key_press] keycode=13
<3>[31196.159085] [key_release] keycode=13
<3>[31196.479541] [key_press] keycode=29
<3>[31196.580948] [key_release] keycode=29
<3>[31196.627761] [key_press] keycode=29
<3>[31196.729424] [key_release] keycode=29
<3>[31196.955957] [key_press] keycode=19
<3>[31197.057527] [key_release] keycode=19
    A "key_press" event happens when you push the key down, a "key_release" event happens when you let go. The numbers in the brackets are timestamps, the number of seconds since boot at which the event happend.

    Now, notice how at least a 1/10th of a second (100 ms) passes between each key_press and its corresponding key_release? That's bad, that's about the same time order as human muscle reaction. It should be 10-30ms-ish at most, and even that is quite long.

    Point is, if you can press a letter twice is less than 1/10th of a second (like "ll" in "hello"), the kernel will count it as a single "key press" because of the lag in reading release events.

    I took a cursory look at the kernel keyboard driver (which is an absolute mess). I think I might've located something that explains that amount of lag. I'll prepare a patch tomorrow morning and test, and if I can get it to reduce that lag I'll post it to the development forum.

    Edit: This only applies to twice-pressed letters (e.g., "ll"), pressing different letters should still come through, although perhaps not in the correct order. In any event, the twice-pressed problem is the only one I can replicate in ConnectBot, leading me to think that any other hardware keypress problems (particularly those present in DI18) might be happening at the IME level which ConnectBot avoids. On the other hand, I thumb-type rather slowly.
    View

New posts