View Single Post
  #1232 (permalink)  
Old 02-25-2010, 07:14 PM
makkonen's Avatar
makkonen
TouchPro Android Guy
Offline
Threadstarter
 
Join Date: May 2007
Posts: 585
Reputation: 3280
makkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Linux/Android on CDMA Touch Pro (RAPH800)

Quote:
Originally Posted by peterm20 View Post
Wouldn't it be the keyboard map files in the XDAndroid system.sqsh that would make the keyboard go funky? I don't think they've changed since December at least that is what is reported when I do a 'ls -a'
I don't know what it would be. The keyboard files did change a bit probably around december/january -- but I can't think why that change, or anything to do with the keyboard mapping in android, would cause the keyboard to work at boot, and then stop working. That sounds like something unrelated to keymaps. Possibly some sort of keyboard handler in Android, though I don't think such a thing exists...

From what everyone's saying, it sounds like it's NOT an issue at the kernel level, since from the command line it hasn't stopped working. (For those testing that: the kernel will throw a hung_task_timeout error and some other data every few minutes, but I don't think that should stop you from being able to keep typing.)

Edit: I don't know what was going on when I read through those posts before, but I take it back. Clearly my reading comprehension was suffering. So, it... does sound like it's at the kernel level? But is weirdly intermittent? I don't really know what to make of it. I really want to say 'hardware failure' and stop thinking about it, but that's probably a dodge. Very strange that a large majority of people haven't reported anything like this.

Last edited by makkonen; 02-25-2010 at 07:18 PM.
Reply With Quote
This post has been thanked 2 times.