search

ghbolivar / android-on-freerunner

Automatically exported from code.google.com/p/android-on-freerunner
0 stars 0 forks source link

broken terminal emulator #55

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. go to dev tools, and select Terminal Emulator
2. type something
3. press enter. it doesn't seem to allow a carriage return.

What is the expected output? What do you see instead?
well...for a working enter button. it's as if the key isn't being passed.

What version of the product are you using? On what operating system?
this has seemed to be an issue for me with all builds that I have tried.
including older panicking and koolu builds, if I remember correctly.

Please provide any additional information below.
is anyone else having this problem?

Original issue reported on code.google.com by michaelt...@gmail.com on 22 Oct 2009 at 5:25

GoogleCodeExporter commented 9 years ago 
Yep, same thing here.

Also, preferences seems to be broken.  When I choose different font size and/or
colors, the settings are neither applied nor remembered.

This worked for me before with some of the koolu or panicking builds.

Original comment by alex.shu...@gmail.com on 22 Oct 2009 at 5:55

GoogleCodeExporter commented 9 years ago 
I can confirm the enter issue.

Original comment by larlin...@gmail.com on 22 Oct 2009 at 6:06

GoogleCodeExporter commented 9 years ago 
Confirmed on latest weekly. 2009, week 43

Original comment by bowdr...@gmail.com on 22 Oct 2009 at 4:33

GoogleCodeExporter commented 9 years ago 
after install alternate keyboard (ruKeyboard). on this keyboard enter works, so 
that
might be keboard issue

Original comment by icuk...@gmail.com on 27 Oct 2009 at 1:54

GoogleCodeExporter commented 9 years ago 
I have russian ( russiankeyboard.apk ) installed, but can only type symbols and
nothing happend when press enter. it doesn't seem not accepted a carriage 
return.
( To icukeng )Which apk you use?

Original comment by Alexandr...@gmail.com on 27 Oct 2009 at 2:29

GoogleCodeExporter commented 9 years ago 
also rom 2009-44
http://4pda.ru/forum/index.php?showtopic=134073

Original comment by icuk...@gmail.com on 31 Oct 2009 at 7:40

GoogleCodeExporter commented 9 years ago 
I can confirm this on 0.1.1 and weekly build 2009-48

Original comment by madzare...@gmail.com on 10 Dec 2009 at 7:45

GoogleCodeExporter commented 9 years ago 
ruKeyboard.apk really solve a problem, al least for current release.

Original comment by Alexandr...@gmail.com on 11 Dec 2009 at 6:44

Attachments:

GoogleCodeExporter commented 9 years ago 
I have the same problem, very annoying. Is it too hard to fix standard keyboard?

Original comment by ilya.pla...@gmail.com on 19 Jan 2010 at 8:04

GoogleCodeExporter commented 9 years ago 
Problem still exists for Release candidate 1 for 0.2.0.

Original comment by Neuman....@gmail.com on 5 Feb 2010 at 2:19

GoogleCodeExporter commented 9 years ago 
As a workaround, I use Connectbot and a "local" connection.
http://code.google.com/p/connectbot/

Original comment by kewlcat...@gmail.com on 5 Feb 2010 at 5:07

GoogleCodeExporter commented 9 years ago 
Same problem.

Original comment by jasons...@gmail.com on 19 Mar 2010 at 2:47

GoogleCodeExporter commented 9 years ago 
anyone knows how to fix this?

Original comment by hariseld...@gmail.com on 12 May 2010 at 9:30

GoogleCodeExporter commented 9 years ago 
The source file you should look into is Term.java. It contains the code for the 
behaviour of the virtual keyboard in the terminal. Take a look at the byte 
value passed on to doEsc and see if it is parsed correctly.

Insert your logging statements there and build the directory again. That should 
give you a starting point.

Original comment by niels.he...@gmail.com on 17 Aug 2010 at 9:29