Discussion in 'Android Devices' started by GomerBoy, Jul 11, 2011.
What do you guys think?
No because i dont have that problem.
i think it will not.
Did the patch from XDA not solve your problem?
I don't know I did not try it yet, I was just curious if Gingerbread would fix the keyboard skipping.
Did you at least get your phone rooted and a kernel flashed?
I guess it will all depend on whether Samsung deems it at something that needs fixing, and how long it takes for the gingerbread update to come out. I would personally just try the patch, and not wait on Samsung/Sprint to put out the update...
I'm hoping it does fix it, as I haven't rooted my phone or anything yet, and won't unless gingerbread doesn't fix the laundrylist of problems that spawned on my phone with the sprint OTA FROYO update (the samesung download prior to being forced into the OTA worked flawlessly)...
If gingerbread limp-wrists my phone I'm going to just root.
So you're saying there are "fixes" available to those who have rooted? So that I can use my physical keyboard and have it detect every keypress?
I think the point is you shouldn't have to root your phone to fix a simple issue such as this. And just because it doesn't affect you, doesn't mean it doesn't exist. If it doesn't affect you and isn't a concern, why bother to post?
I agree with you in that you shouldn't have to root in order to resolve the problem. Still, wish in one hand... I guess if it is a critical item in your overall satisfaction of the phone, I would take the necessary steps to rectify it.
With any luck, we will be able to tell if Samsung addressed the problem within the next couple of weeks...
I'm rooted so it doesn't bother me personally, but I work with a technically declined bunch. They just want their phone to work, and rooting isn't an option. And a flagship type phone having undergone a few updates and still having this sporadic issue is a bit unacceptable. Add the gps issues to it, and I get to hear complaints quite a bit. I hear the iphone talk, but I always ask them why they keep bugging me for keyboarded phones. Frickin' lemmings just have no clue. Will probably be all for nothing anyway if/when we jump ship to tmob. But then we lose 4" screens and 5 row keyboards...blah.
I can only imagine your pains and struggles then... There really isn't any excuse, though, from either Sprint or Samsung. Unfortunately, although a great phone overall, the Epic was never really treated as a flagship phone by either.
Hopefully, you don't go the T-Mobile route, in case of the AT&T buyout occurring.
actually...will be saving $500/mo over Sprint, and we'll be grandfathered into t-mobile's current rate plan structure should the merger go through. Plus, coverage should improve after the merger. There's already talk of towers from both working for both. So who knows. $6k a year is nothing to sneeze at.
Grandfathered in wouldn't be a bad option, along with improved coverage. Being that both are GSM, I can't see it being much of a stuggle to get the two systems to comply with one another.
Wait, you said you are rooted? I'll assume it is on your personal phone.
You do realize that only a small portion of Epic 4G owners have this problem with their Epic, right?
Samsung and Sprint made the decision to focus on more pressing matters, such as fixing GPS malfunctions and releasing 2.2. Now that most of the bugs have been worked out of the Epic, they have time to focus on these trivial issues.
Ugh... this has been one of the most frustrating electronic devices I've ever owned. Such great potential, and overall a great phone, but these bugs since Froyo are ruining the phone for me. I decided that I was not going to root my phone, when I got it. Sure, Samsung and Sprint should be able to stay on top of things, so when Froyo took so long to come out, and it eventually did come out, I started doubting that I should have any faith in them. It took forever, and then after I got a good version of Froyo installed from the samsung website, Sprint pushed the OTA and it totally ruined my phone.
So then I noticed that GB was going to be coming out and they were already testing and it didn't seem like a very long wait, so, again I figured I could give them a chance to fix it... but the longer I have to wait and the longer I have to use a buggy device... the more my patience wears thin.
I might as well just root and fix the problems and continue the cycle of tinkering with every electronic device I ever get...
My work and personal phone are one and the same. I have quite a few phones I can use in a pinch, but I've rarely been out of commission from flashing issues for more than an hour. Keeping the latest syndicate and bonsai rom on the card, I'm usually just a 3x wipe and flash away from being up and running if a nandroid restore doesn't do the trick.
That is incorrect, I have tried MANY different epics and all of them have this issue. My guess is that Samsung refuses to acknowledge the issue even though it is so widespread.
When people come into a thread about an issue they don't have and voice their negative opinion, I usually find it easier to just dismiss them because what they offer up is usually a) wrong b) pointless or c) both a & b. Usually not worth replying to.
My phone got real buggy after Froyo and I finally took it to Sprint. The tech said there was major problems with the Froyo OTA. After a quick reflash, my phone is awesome. I highly recommend an official Sprint reflash.
Is your phone rooted? My phone has been buggy since the Froyo update. Did the official Sprint reflash take long or erase any of your data/config?
My solution to the keyboard skipping problem is just to type a little bit slower.
If I go to fast, the phone drops characters and I have to go back and fix them, which takes more time than just slowing down slightly.
It doesn't take much, and it seems to work.
Not rooted. It took them about 15 minutes and all data/apps was wiped. Had to start over with configing everything but it was well worth it. I use MyBackupPro to put the apps back on and that works pretty well.
I didn't know this was a known issue. I thought it was just me typing poorly.
It happens all the time for me, when using the slide-out keyboard, I'll be typing away and then look back and half the words are missing letters. I do have to frequently go back and correct my typing.
So, this fixed the stupid problem with the screen icons disappearing when you open and close the keyboard slide? How about the keyboard skipping letters?
Meanwhile, back at the XDA patch, can someone possibly link to it?