keyboard
Now on the terminal i cant get a keyboard at all HELP ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: keyboard
more information ,like ROOTFS? rocco scaccia wrote: > Now on the terminal i cant get a keyboard at all HELP > > > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: keyboard
try follow step: cd /tmp mkdir matchbox-keyboard cd matchbox-keyboard wget http://www.ginguppin.de/files/keyboard-ipk.tar.bz2 <this is important tar -jxf keyboard-ipk.tar.bz2 opkg remove -force-depends multitap-pad opkg install matchbox-keyboard-inputmethod*.ipk opkg install matchbox-keyboard-im*.ipk opkg install matchbox-keyboard-applet*.ipk cd .. rm -rf matchbox-keyboard maybe the keyboard you want rocco scaccia wrote: > I inputed the opkg remove -force-depends multitap-pad > opkg install matchbox-keyboard-inputmethod > opkg install matchbox-keyboard-im > opkg install matchbox-keyboard-applet > > It now comes back as NOT INSTALLED. > > > I have no keyboard at all on the terminal section i cant input anything at > all > > Rocky > > > --- On Fri, 7/25/08, xiangfu <[EMAIL PROTECTED]> wrote: > > >> From: xiangfu <[EMAIL PROTECTED]> >> Subject: Re: keyboard >> To: [EMAIL PROTECTED] >> Cc: "Support for Openmoko Device Owners" >> Date: Friday, July 25, 2008, 8:28 PM >> more information ,like ROOTFS? >> >> rocco scaccia wrote: >> >>> Now on the terminal i cant get a keyboard at all HELP >>> >>> >>> >>> >>> ___ >>> support mailing list >>> support@lists.openmoko.org >>> https://lists.openmoko.org/mailman/listinfo/support >>> >>> > > > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: keyboard
you can ssh to your FR from your PC, then you can install the keyboard. then you have the "/" key :-) rocco scaccia wrote: > I understand that but I have no keyboard and I have no way at all to input > anything or USB coneectivity to my pc > > this all happened when i found out that the factory fresh phone had no / key. > > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: keyboard
rocco scaccia wrote: > I tried to ping the phone but the pc cant find it. > > Is there a way to reset the fireware. > > you can download[1] new kernel and rootfs and use "dfu-util"[2] download then to your FR, it is something like reset the fireware. 1. enter DFU-MODE ( hold AUX then hold POWER release AUX after 1 sec, hold POWER until the screen show UBOOT) 2. in your PC use "dfu-util -a kernel -R -D ./kernel" "dfu-util -a rootfs -R -D ./rootfs*" then you can start you phone. plug it to your PC. at PC: 1. "ifconfig usb0 192.168.0.200" 2. "ssh [EMAIL PROTECTED]" 3. then your get a shell. do what you want do. [1] http://buildhost.openmoko.org/daily/freerunner/200807/ [2] http://wiki.openmoko.org/wiki/Dfu-util hope this can help you. :-) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: keyboard
Am Mo 28. Juli 2008 schrieb xiangfu: > at PC: > 1. "ifconfig usb0 192.168.0.200" > 2. "ssh [EMAIL PROTECTED]" > 3. then your get a shell. do what you want do. Actually >>> /sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0 /sbin/route add -host 192.168.0.202/32 dev usb0 ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [EMAIL PROTECTED] <<< ssh to [EMAIL PROTECTED] probably will give you a shell login to host PC, that's not what you want! /jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: keyboard
Joerg Reisenweber wrote: > Am Mo 28. Juli 2008 schrieb xiangfu: > >> at PC: >> 1. "ifconfig usb0 192.168.0.200" >> 2. "ssh [EMAIL PROTECTED]" >> 3. then your get a shell. do what you want do. >> > > Actually > > /sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0 > /sbin/route add -host 192.168.0.202/32 dev usb0 > ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [EMAIL > PROTECTED] > <<< > > ssh to [EMAIL PROTECTED] probably will give you a > sorry ! type the wrong IP address. > shell login to host PC, that's not what you want! > > /jOERG > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: keyboard
Am Mo 28. Juli 2008 schrieb xiangfu: > Joerg Reisenweber wrote: > > Am Mo 28. Juli 2008 schrieb xiangfu: > > > >> at PC: > >> 1. "ifconfig usb0 192.168.0.200" > >> 2. "ssh [EMAIL PROTECTED]" > >> 3. then your get a shell. do what you want do. > >> > > > > Actually > > > > /sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0 > > /sbin/route add -host 192.168.0.202/32 dev usb0 > > ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [EMAIL PROTECTED] > > <<< > > > > ssh to [EMAIL PROTECTED] probably will give you a > > > sorry ! type the wrong IP address. > > shell login to host PC, that's not what you want! > > > > /jOERG NP :-) I'm hired to catch errors ;-) /jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: keyboard
you can download new kernel and rootfs from [1] and use "dfu-util"[2] download them to your FR, it is something like reset the fireware. step: 1. Download new kernel, rootfs and dfu-util 2. enter DFU-MODE ( hold AUX button then hold POWER button release AUX after 1 second, hold POWER button until the screen show UBOOT) 3. connect your FR and PC with usb cable. 4. then you can use dfu-util to download kernel and rootfs to your FreeRunner, the dfu-util command will find FR automatic .(make sure there only FR connect with your PC , no other USB device ) "dfu-util -a kernel -R -D ./kernel" "dfu-util -a rootfs -R -D ./rootfs*" then you can start you phone. plug it to your PC. at PC: 1. "ifconfig usb0 192.168.0.200" 2. "ssh [EMAIL PROTECTED]" 3. then your get a shell. do what you want do. [1] http://buildhost.openmoko.org/daily/freerunner/200807/ rootfs: http://buildhost.openmoko.org/daily/freerunner/200807/20080720/Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-20080720-om-gta02.rootfs.jffs2 kernel: http://buildhost.openmoko.org/daily/freerunner/200807/20080728/uImage-om-gta02-latest.bin [2] http://wiki.openmoko.org/wiki/Dfu-util hope this can help you. :-) rocco scaccia wrote: > I tried what you wrote. I will keep trying but im not as advanced as you and > the other users. > > I will need you to please spell it out to the point where your trying to > teach a child. Everything painfully explained. I am very sorry that I havent > been a sharp student. > > Thank you > Rocky > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Keyboard guid
Hi there, I am sure this has been announced before, but I am sure I am not the only one who only stumbled into it by accident after hours of experimentation and reading bug reports and heated debates. So I will just increase its pagerank a bit. There are two guides on how to use the new om2008.8 keyboard! http://wiki.openmoko.org/wiki/Om2008.8_Keyboard http://wiki.openmoko.org/wiki/Om_2008.8_Guide * how to switch between layouts (small, caps, numeric, special characters) * how to do backspace * how to turn it on and off Even though one of the guides is linked directly from http://wiki.openmoko.org/wiki/Om2008.8, I think it needs a more prominent spot and a better catch phrase*. For some reason I did read the installation instructions, but did not even notice this important link. I think I am not the only one. So that means I am probably stupid, but so are most people; this will be a fun challenge for the usability team. * : e.g. right after "install" in the "Download" subsection (I would also switch these titles by the way; "Install" is the real main message here and you'll need to "download" before you can do that) have a "Get started" subsection. That should have a text like: "You'll probably want to learn about the new keyboard.". Sjors ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
SHR - Keyboard
Is there a way to make the keyboard pop up on demand, say for the terminal? -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Finger-based keyboard
Hello all, it's my first post here, so I take the chance tell you that this project rocks! given this, I'd like to know if there is, somewhere, a finger-based (qwerty) keyboard that can be easily used, for example to send sms or write urls. I've found this [1] page which presents something as I whish, but could not find any more link to it. The matchbox is finger-unusable, and sometimes you just don't have the stylus around. thanks, leonardo. [1] http://openmoko.togaware.com/survivor/Keyboard.html -- http://leonardo.lilik.it Key fingerprint = 2C20 A587 05AC 42E5 1292 D0D4 3EED CFB5 52FD AD1E ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard guide
> http://wiki.openmoko.org/wiki/Om2008.8_Keyboard > http://wiki.openmoko.org/wiki/Om_2008.8_Guide Alright, that typo in the subject completely ruined the pagerank :-) Sjors ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard guid
Sjors Provoost wrote: > Hi there, > > I am sure this has been announced before, but I am sure I am not the > only one who only stumbled into it by accident after hours of > experimentation and reading bug reports and heated debates. So I will > just increase its pagerank a bit. > > There are two guides on how to use the new om2008.8 keyboard! > > http://wiki.openmoko.org/wiki/Om2008.8_Keyboard > http://wiki.openmoko.org/wiki/Om_2008.8_Guide > > * how to switch between layouts (small, caps, numeric, special characters) > * how to do backspace > * how to turn it on and off > > Even though one of the guides is linked directly from > http://wiki.openmoko.org/wiki/Om2008.8, I think it needs a more > prominent spot and a better catch phrase*. For some reason I did read > the installation instructions, but did not even notice this important > link. I think I am not the only one. So that means I am probably > stupid, but so are most people; this will be a fun challenge for the > usability team. > > * : e.g. right after "install" in the "Download" subsection (I would > also switch these titles by the way; "Install" is the real main > message here and you'll need to "download" before you can do that) > have a "Get started" subsection. That should have a text like: "You'll > probably want to learn about the new keyboard.". > > Sjors > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > > Hehe, thanks for that. I have been using the keyboard for a day while mumbling about the lack of a delete key. :-) I shall go RTFM. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard guide
On Sun, Aug 10, 2008 at 4:23 AM, Sjors Provoost <[EMAIL PROTECTED]> wrote: >> http://wiki.openmoko.org/wiki/Om2008.8_Keyboard >> http://wiki.openmoko.org/wiki/Om_2008.8_Guide Wow. This information needs to be featured PROMINENTLY, both in the software itself and in the getting started section of the wiki. It negates virtually all of my complaints about the new keyboard. The biggest one that remains is that this functionality is virtually impossible to discover on your own. Adding some visual cues to indicate this exists will do wonders to improve the out of box experience with it. I was extremely frustrated with the keyboard when I first tried it, and I know I am not alone in this. -- -Regards- -Quentin Hartman- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard guid
No your not stupid and you didn't overlook it the first time you read it :P I just added the Guide last night ;) I love this whole wiki thing. I've been going around fixing anything I could find and adding what I know to help others out. -- View this message in context: http://n2.nabble.com/Keyboard-guid-tp683937p684780.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard guid
Fantastic. This is the type of stuff we need and can build on. Mike ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
XFCE matchbox keyboard
Anyone know how to make the toggle keyboard in XFCE embed instead of being a resizable application window? It makes it hard to use when it gets lowered and/or is overlapped by or overlaps other windows. -Tom ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Illume keyboard Disappeared
after running a few while , maybe after suspends , Illume keyboard does not appear and standard om2008 keyboard appear , any one has any idea ? -- Armin ranjbar , System Administrator ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Intermittant bluetooth keyboard
I set up my bluetooth keyboard on my openmoko phone using the 'new' (In other words, not hidd, but still dbus) input interface, and it only works like 10% of the time. That means when I turn it on it should connect and start working. Unfortunately, it only works about 25% of the time, and I have to switch it off and on frequenly in order to get it to finally connect. I get this output from hcidump -V when it doesn't work: > HCI Event: Connect Request (0x04) plen 10 bdaddr 00:0A:DF:00:24:59 class 0x002540 type ACL < HCI Command: Accept Connection Request (0x01|0x0009) plen 7 bdaddr 00:0A:DF:00:24:59 role 0x00 Role: Master > HCI Event: Command Status (0x0f) plen 4 Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1 > HCI Event: Connect Complete (0x03) plen 11 status 0x22 handle 42 bdaddr 00:0A:DF:00:24:59 type ACL encrypt 0x00 Error: LMP Response Timeout The difference in time between 'Accept Connection Request' and 'LMP Response Timeout' is about 3 seconds. I was under the impression that LMP negociation was supposed to time out after 30 seconds? Is there something I'm doing wrong? Am I not interprating this correctly? If it does work I get something like this: > HCI Event: Connect Request (0x04) plen 10 bdaddr 00:0A:DF:00:24:59 class 0x002540 type ACL < HCI Command: Accept Connection Request (0x01|0x0009) plen 7 bdaddr 00:0A:DF:00:24:59 role 0x00 Role: Master > HCI Event: Command Status (0x0f) plen 4 Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1 > HCI Event: Link Key Request (0x17) plen 6 bdaddr 00:0A:DF:00:24:59 . . . (And then link key request reply and so on it does its negociation and there you have it) -- Daniel Benoy http://daniel.benoy.name ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SHR - Keyboard
On Tue, 16 Dec 2008 15:28:09 -0500 Paul babbled: > Is there a way to make the keyboard pop up on demand, say for the terminal? yes. the terminal can put a property on its window stating what the state of the keyboard for that window should be :) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SHR - Keyboard
On Tue, Dec 16, 2008 at 8:28 PM, Paul wrote: > Is there a way to make the keyboard pop up on demand, say for the terminal? Or did you just mean: press the tiny little mark at centre top of the screen. A curtain 1/3 the size of the screen will wander down. At its top right corner is the word "qwerty". if you press that a keyboard will appear. Later you can repeat to make the keyboard disappear. The keyboard has a sign in some oriental language at its top right which causes changes in it. Basically 3 possibles, of which the third can be quite useful if you can get it to respond. It has the habit of enlarging its characters when they are pressed which may be helpful when trying to use fingers to type on it but slows it. It also at times develops a habit known as predictive. I have actually been shown how this can be made to work on a mobile phone where it may have some value. Compared with ordinary "tab completion" in linux commands it is not even a starter, and again is a distraction.. clare (who really likes the matchbox keyboard - remember that?. It is used in the new "hackable"; and with apologies to Rasterman; but I do feel strongly on these points.) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SHR - Keyboard
On Thursday 18 December 2008, clare johnstone wrote: > On Tue, Dec 16, 2008 at 8:28 PM, Paul wrote: > > Is there a way to make the keyboard pop up on demand, say for the > > terminal? > > Or did you just mean: press the tiny little mark at centre top of the > screen. A curtain 1/3 the size of the screen will wander down. At its top > right corner is the word "qwerty". if you press that a keyboard will > appear. > Later you can repeat to make the keyboard disappear. Yes, it is now frustratingly longwinded. The keyboard icon on the matchbox panel is much better in my opinion. Even better would be a keyboard icon that brought up the default keyboard if tapped, but if held would pop up a list of available keyboards or layouts. > The keyboard has a sign in some oriental language at its top right > which causes changes in it. Basically 3 possibles, of which the third > can be quite useful if you can get it to respond. It is "ABC" with the characters overlapping slightly. It needn't be 3 choices either - you can add or remove keyboard layouts as you wish. You could remove all but the terminal layout if that's the only one you want. People have produced alternative layouts better suited to other languages too. The top left lets you pick the dictionary to be used for the corrective input, so you could have multiple languages available. > It has the habit of enlarging its characters > when they are pressed which may be helpful when trying to use fingers > to type on it but slows it. It can be a little distracting, but it doesn't seem to compromise performance. It seems to keep up with ~4 characters per second - as fast as I can hit characters in short bursts anyway. Sometimes I get characters from a long way from where I tapped, but I suspect that's the touchscreen driver causing problems since I have the same problem with the matchbox keyboard. > It also at times develops a habit known as predictive. Corrective would be more accurate, and whether it is enabled depends on the keyboard layout. The icon in the top left will give you the full list of potentially matching words, with the exact string you entered always at the top. The quality of correction is heavily dependant on the dictionary, at least out of the box. The default english dictionary works well, but some have reported problems with german for example. To some extent this should be offset if you persevere as it adds spellings and word frequencies to your personal dictionary, > I have actually been shown how this can be made to work on a mobile > phone where it may have some value. Agreed. With the corrective layout I can enter text reasonably reliably one handed while walking. I wouldn't have a hope of doing this with the terminal layout, or with the matchbox keyboard. > Compared with ordinary "tab completion" in linux commands it is not > even a starter, and again is a distraction.. But for linux commands surely you would use the terminal layout, which doesn't have the corrective feature enabled, and use tab completion. > clare (who really likes the matchbox keyboard - remember that?. It is > used in the new "hackable"; > and with apologies to Rasterman; but I do feel strongly on these points.) Input method preferences are highly personal. Happily we have a choice of input methods, and Rasterman included the facility to use them. If you install the matchbox keyboard, or any other for that matter, it should appear in the list of selectable keyboards in the illume config (spanner icon). I suspect part of the reason people tend to dislike the qtopia and default illume keyboards is that by default they don't do what we expect, and it isn't obvious what they are doing. The matchbox keyboard is just an onscreen representation of a familiar keyboard, and behaves as we expect. It doesn't require any extra knowledge to get it to do what we want. The same could be said of the illume terminal layout, but that isn't the default. The qtopia and illume keyboards try to be better, as does the iPhone keyboard, but all require a bit of hidden knowledge to get them to work. Once you know their secrets they are as good as or better than the matchbox keyboard, but if you don't know the secrets then they are incredibly frustrating. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SHR - Keyboard
Al thank you for the detailed reply; very encouraging. regards, clare On Thu, Dec 18, 2008 at 2:49 PM, Al Johnson wrote: > On Thursday 18 December 2008, clare johnstone wrote: >> On Tue, Dec 16, 2008 at 8:28 PM, Paul wrote: >> > Is there a way to make the keyboard pop up on demand, say for the >> > terminal? >> >> Or did you just mean: press the tiny little mark at centre top of the >> screen. A curtain 1/3 the size of the screen will wander down. At its top >> right corner is the word "qwerty". if you press that a keyboard will >> appear. >> Later you can repeat to make the keyboard disappear. > > Yes, it is now frustratingly longwinded. The keyboard icon on the matchbox > panel is much better in my opinion. Even better would be a keyboard icon that > brought up the default keyboard if tapped, but if held would pop up a list of > available keyboards or layouts. > >> The keyboard has a sign in some oriental language at its top right >> which causes changes in it. Basically 3 possibles, of which the third >> can be quite useful if you can get it to respond. > > It is "ABC" with the characters overlapping slightly. It needn't be 3 choices > either - you can add or remove keyboard layouts as you wish. You could remove > all but the terminal layout if that's the only one you want. People have > produced alternative layouts better suited to other languages too. > > The top left lets you pick the dictionary to be used for the corrective input, > so you could have multiple languages available. > >> It has the habit of enlarging its characters >> when they are pressed which may be helpful when trying to use fingers >> to type on it but slows it. > > It can be a little distracting, but it doesn't seem to compromise performance. > It seems to keep up with ~4 characters per second - as fast as I can hit > characters in short bursts anyway. Sometimes I get characters from a long way > from where I tapped, but I suspect that's the touchscreen driver causing > problems since I have the same problem with the matchbox keyboard. > >> It also at times develops a habit known as predictive. > > Corrective would be more accurate, and whether it is enabled depends on the > keyboard layout. The icon in the top left will give you the full list of > potentially matching words, with the exact string you entered always at the > top. > > The quality of correction is heavily dependant on the dictionary, at least out > of the box. The default english dictionary works well, but some have reported > problems with german for example. To some extent this should be offset if you > persevere as it adds spellings and word frequencies to your personal > dictionary, > >> I have actually been shown how this can be made to work on a mobile >> phone where it may have some value. > > Agreed. With the corrective layout I can enter text reasonably reliably one > handed while walking. I wouldn't have a hope of doing this with the terminal > layout, or with the matchbox keyboard. > >> Compared with ordinary "tab completion" in linux commands it is not >> even a starter, and again is a distraction.. > > But for linux commands surely you would use the terminal layout, which doesn't > have the corrective feature enabled, and use tab completion. > >> clare (who really likes the matchbox keyboard - remember that?. It is >> used in the new "hackable"; >> and with apologies to Rasterman; but I do feel strongly on these points.) > > Input method preferences are highly personal. Happily we have a choice of > input methods, and Rasterman included the facility to use them. If you > install the matchbox keyboard, or any other for that matter, it should appear > in the list of selectable keyboards in the illume config (spanner icon). > > I suspect part of the reason people tend to dislike the qtopia and default > illume keyboards is that by default they don't do what we expect, and it > isn't obvious what they are doing. The matchbox keyboard is just an onscreen > representation of a familiar keyboard, and behaves as we expect. It doesn't > require any extra knowledge to get it to do what we want. The same could be > said of the illume terminal layout, but that isn't the default. > > The qtopia and illume keyboards try to be better, as does the iPhone keyboard, > but all require a bit of hidden knowledge to get them to work. Once you know > their secrets they are as good as or better than the matchbox keyboard, but > if you don't know the secrets then they are incredibly frustrating. > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SHR - Keyboard
On Thu, 18 Dec 2008 14:49:50 + Al Johnson babbled: > On Thursday 18 December 2008, clare johnstone wrote: > > On Tue, Dec 16, 2008 at 8:28 PM, Paul wrote: > > > Is there a way to make the keyboard pop up on demand, say for the > > > terminal? > > > > Or did you just mean: press the tiny little mark at centre top of the > > screen. A curtain 1/3 the size of the screen will wander down. At its top > > right corner is the word "qwerty". if you press that a keyboard will > > appear. > > Later you can repeat to make the keyboard disappear. > > Yes, it is now frustratingly longwinded. The keyboard icon on the matchbox it's that way because slowly i'm expecting toolkits to be able to auto-popup or apps - it's still there, but i moved it away to make more room on the top bar for other things. it's laid out by theme so it can be changed - but the default is aimed more at the "state of things how they should be right now" > panel is much better in my opinion. Even better would be a keyboard icon that > brought up the default keyboard if tapped, but if held would pop up a list of > available keyboards or layouts. that can be done - though it duplicates the layout selector on the kbd itself > > The keyboard has a sign in some oriental language at its top right > > which causes changes in it. Basically 3 possibles, of which the third > > can be quite useful if you can get it to respond. > > It is "ABC" with the characters overlapping slightly. It needn't be 3 choices > either - you can add or remove keyboard layouts as you wish. You could remove > all but the terminal layout if that's the only one you want. People have > produced alternative layouts better suited to other languages too. > > The top left lets you pick the dictionary to be used for the corrective > input, so you could have multiple languages available. > > > It has the habit of enlarging its characters > > when they are pressed which may be helpful when trying to use fingers > > to type on it but slows it. > > It can be a little distracting, but it doesn't seem to compromise > performance. It seems to keep up with ~4 characters per second - as fast as I > can hit characters in short bursts anyway. Sometimes I get characters from a > long way from where I tapped, but I suspect that's the touchscreen driver > causing problems since I have the same problem with the matchbox keyboard. if you happen to have both fingers pressed at once (as you haven't released 1 before pressing the other) this will happen. this is just unfortunately part of life with a single-touch resistive touchsrceen. (i can come up with hackish workarounds like extrapolating sudden moves to be a new press somewhere else in the tslib driver... but now you're in magic voodoo land and really.. you just should have multitouch). > > It also at times develops a habit known as predictive. > > Corrective would be more accurate, and whether it is enabled depends on the > keyboard layout. The icon in the top left will give you the full list of > potentially matching words, with the exact string you entered always at the > top. > > The quality of correction is heavily dependant on the dictionary, at least > out of the box. The default english dictionary works well, but some have > reported problems with german for example. To some extent this should be > offset if you persevere as it adds spellings and word frequencies to your > personal dictionary, yeah. dictionary quality is the issue. remember i only test with the english one and its decent - once you use it for writing messages/notes for a while (in english) it learns your patterns pretty well and accuracy improves significantly. (some words for some reason are not in there - like 'hello' as i always start my tests with bashing away 'hello world' :)) indeed it is corrective - NOT predictive. it is only intended to be corrective. i don't think predictive WITH fuzzy matching is a good idea as it blows out the potential list of "matches". also it is NOT intended for a terminal - the terminal layout is for that. so you cant compare to tab completion - it is nothing like it. tab completion has knowledge of the context (current directory and file system) whereas the keyboard has no clue about the context. it's trying its best using a dictionary for your language - assuming you are typing regular "english text" (or another language) like writing notes or emails or sms's. that is precisely why a terminal layout exists to add all the extra keys you'll want for using a terminal etc. > > I have actually been shown how this can be made to work on a mobile > > phone wher
Re: SHR - Keyboard
On Thursday 18 December 2008, Carsten Haitzler wrote: > On Thu, 18 Dec 2008 14:49:50 + Al Johnson > > > babbled: > > On Thursday 18 December 2008, clare johnstone wrote: > > > On Tue, Dec 16, 2008 at 8:28 PM, Paul wrote: > > > > Is there a way to make the keyboard pop up on demand, say for the > > > > terminal? > > > > > > Or did you just mean: press the tiny little mark at centre top of the > > > screen. A curtain 1/3 the size of the screen will wander down. At its > > > top right corner is the word "qwerty". if you press that a keyboard > > > will appear. > > > Later you can repeat to make the keyboard disappear. > > > > Yes, it is now frustratingly longwinded. The keyboard icon on the > > matchbox > > it's that way because slowly i'm expecting toolkits to be able to > auto-popup or apps - it's still there, but i moved it away to make more > room on the top bar for other things. it's laid out by theme so it can be > changed - but the default is aimed more at the "state of things how they > should be right now" I'm finding that I have to manually pull up the keyboard more often now than I used to, not less. Rather like the original keyboard discussion I agree with the theory, but in practise things aren't there yet. > > panel is much better in my opinion. Even better would be a keyboard icon > > that brought up the default keyboard if tapped, but if held would pop up > > a list of available keyboards or layouts. > > that can be done - though it duplicates the layout selector on the kbd > itself If the 'correct' layout would appear automatically every time it wouldn't be an issue. Until that happens the duplication allows manual selection of the 'correct' keyboard for the situation with a tap-hold-drag rather than tap (bring up keyboard) tap (bring up layout selection) scroll (as it seems to add scroll bars whether needed or not) tap (to select layout). There is of course the argument that if you make the keyboard too easy nobody will ever fix the apps ;-) > > It can be a little distracting, but it doesn't seem to compromapp-emulation/emul-linux-x86-java-1.5.0.17ise > > performance. It seems to keep up with ~4 characters per second - as fast > > as I can hit characters in short bursts anyway. Sometimes I get > > characters from a long way from where I tapped, but I suspect that's the > > touchscreen driver causing problems since I have the same problem with > > the matchbox keyboard. > > if you happen to have both fingers pressed at once (as you haven't released > 1 before pressing the other) this will happen. this is just unfortunately > part of life with a single-touch resistive touchsrceen. (i can come up with > hackish workarounds like extrapolating sudden moves to be a new press > somewhere else in the tslib driver... but now you're in magic voodoo land > and really.. you just should have multitouch). This is with a single finger or stylus, and a definite release before the next tap. This sort of operation works without problem on a Psion 5, another device with a resistive touchscreen and still my reference device in many respects. > > I suspect part of the reason people tend to dislike the qtopia and > > default illume keyboards is that by default they don't do what we expect, > > and it isn't obvious what they are doing. The matchbox keyboard is just > > an onscreen representation of a familiar keyboard, and behaves as we > > expect. It doesn't require any extra knowledge to get it to do what we > > want. The same could be said of the illume terminal layout, but that > > isn't the default. > > also one could argue that the invers could be the case. i am trying to > answer and sms and do nothing but yell at this tiny pokey keyboard i can > barely hit with a finger - and the device has no place for a stylus (and > the one that comes with it is so huge i wouldn't be seen dead carrying it). > :) you can't win. you make lot A happy, then lot B unhappy. thats why there > are multiple layouts to at least give the options to both. the default lean > is towards using it as a PHONE - not as a terminal. i would assume the > nerds have enough braincells to rub together to switch layout :) I never said it was easy ;-) The corrective keyboard and the alternate keyboard layouts are hugely better than the matchbox keyboard, but there is a barrier to entry that the matchbox keyboard doesn't have. The matchbox keyboard is intuitive but ultimately limited as an input method as you say. The challenge is to lower the initial barrier for the illume keyboard so that more people get to see the advantages on the other side rather than giving up and ditching it for the matchbox one, only to run into its limitations at a later date. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SHR - Keyboard
On Fri, 19 Dec 2008 02:09:52 +, Al Johnson wrote: > On Thursday 18 December 2008, Carsten Haitzler wrote: >> On Thu, 18 Dec 2008 14:49:50 + Al Johnson >> >> >> babbled: >> > On Thursday 18 December 2008, clare johnstone wrote: >> > > On Tue, Dec 16, 2008 at 8:28 PM, Paul wrote: >> > > > Is there a way to make the keyboard pop up on demand, say for the >> > > > terminal? >> > > >> > > Or did you just mean: press the tiny little mark at centre top of > the >> > > screen. A curtain 1/3 the size of the screen will wander down. At > its >> > > top right corner is the word "qwerty". if you press that a keyboard >> > > will appear. >> > > Later you can repeat to make the keyboard disappear. >> > >> > Yes, it is now frustratingly longwinded. The keyboard icon on the >> > matchbox >> >> it's that way because slowly i'm expecting toolkits to be able to >> auto-popup or apps - it's still there, but i moved it away to make more >> room on the top bar for other things. it's laid out by theme so it can > be >> changed - but the default is aimed more at the "state of things how they >> should be right now" > > I'm finding that I have to manually pull up the keyboard more often now > than I > used to, not less. Rather like the original keyboard discussion I agree > with > the theory, but in practise things aren't there yet. We're doing more manual keyboard work simply because we're testing SHR instead of 2008.x, so we don't have Qtopia apps triggering keyboard. In this case that's not at all the keyboard's fault. I've seen quite a bit more auto-keyboard action the past few days, as well. :) >> > panel is much better in my opinion. Even better would be a keyboard > icon >> > that brought up the default keyboard if tapped, but if held would pop > up >> > a list of available keyboards or layouts. >> >> that can be done - though it duplicates the layout selector on the kbd >> itself > > If the 'correct' layout would appear automatically every time it wouldn't > be > an issue. Until that happens the duplication allows manual selection of > the 'correct' keyboard for the situation with a tap-hold-drag rather than > tap > (bring up keyboard) tap (bring up layout selection) scroll (as it seems to > add scroll bars whether needed or not) tap (to select layout). There is of > course the argument that if you make the keyboard too easy nobody will > ever > fix the apps ;-) The heart of it - fix the apps. Or perhaps word it as "enhance the apps". In the meantime, I simply did: "cd /usr/lib/enlightenment/modules/illume/keyboards; mv Default.kbd Alpha.kbd; mv Terminal.kbd Default.kbd" and called it done. When I pop up the keyboard manually or it triggers auto, I get the full terminal layout, which I'm far happier with as default. >> > It can be a little distracting, but it doesn't seem to > compromapp-emulation/emul-linux-x86-java-1.5.0.17ise >> > performance. It seems to keep up with ~4 characters per second - as > fast >> > as I can hit characters in short bursts anyway. Sometimes I get >> > characters from a long way from where I tapped, but I suspect that's > the >> > touchscreen driver causing problems since I have the same problem with >> > the matchbox keyboard. >> >> if you happen to have both fingers pressed at once (as you haven't > released >> 1 before pressing the other) this will happen. this is just > unfortunately >> part of life with a single-touch resistive touchsrceen. (i can come up > with >> hackish workarounds like extrapolating sudden moves to be a new press >> somewhere else in the tslib driver... but now you're in magic voodoo > land >> and really.. you just should have multitouch). > > This is with a single finger or stylus, and a definite release before the > next > tap. This sort of operation works without problem on a Psion 5, another > device with a resistive touchscreen and still my reference device in many > respects. I saw the same thing until quite recently. I'm presuming that this is the result of Tick's touchscreen jitter work. I used to fire up sketchbook and tap rapidly around the keyboard area (or any other area, closer to the edge the more pronounced) and get intermittent taps registering as far away as the center of the screen. Today I tried that and got one mis-registered tap like that where before I'd have had about 20. Playing with sketchboo
Re: SHR - Keyboard
On Fri, Dec 19, 2008 at 5:34 AM, Joel Newkirk wrote: > The heart of it - fix the apps. Or perhaps word it as "enhance the apps". > In the meantime, I simply did: "cd > /usr/lib/enlightenment/modules/illume/keyboards; mv Default.kbd Alpha.kbd; > mv Terminal.kbd Default.kbd" and called it done. When I pop up the > keyboard manually or it triggers auto, I get the full terminal layout, > which I'm far happier with as default. Maybe you did something else as well.? I have set up SHR on the card, which is much better as it has its kernel and modules ready installed. I followed the above simple instruction. It is an improvement, as I can now quickly select "Default" instead of "Terminal" which was previously hidden under a black bar and very unresponsive. "Numbers" are under there now. It can be got, by touching along the top edge of the Black bar, (as I found I had to do before to get Terminal). I would like to mention now that the keyboard is easier to read than matchbox due to the relatively larger font of the letters. It is also vastly improved by being white instead of black as it was at one time, (I couldn't see where I was with the stylus.) > >>> > I suspect part of the reason people tend to dislike the qtopia and >>> > default illume keyboards is that by default they don't do what we >> expect, There is a difference with Qtopia predictions they are not so in your face and they dont seem to matter. If you just type you get there. >>> barely hit with a finger - and the device has no place for a stylus (and >>> the one that comes with it is so huge i wouldn't be seen dead carrying >> it). yes I agree, my stylus made of wire and a toothpick is on a cord through the hole in the case which has saved it many times. >> the default lean >>> is towards using it as a PHONE - not as a terminal. i would assume the >>> nerds have enough braincells to rub together to switch layout :) I would assume they are even lazier than others as they know it doesn't need to be so difficult. However I was fascinated on trying a picture of a new moon to get a message "Suspending your Computer". At last somebody thinks it is a computer :) > IMHO the only thing the matchboxkeyboard has over the Illume - with Terminal > as default - is that it takes > up a bit less room. Disagree, I still dont like the letters jumping up. is there a way to turn that off? Just "bold" them? cheers, clare ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Qtopia and keyboard
Hi to everybody, I have a problem with qtopia keyboard. I open the web browser and try to open the gmail app. So when I go to put my password the keyboard disapeares... Any idea??? Many thanks -- Marc Rios Nota: http://www.gnu.org/philosophy/no-word-attachments.es.html ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
illume-Keyboard lowercase?
Hi! I'm trying to get my Neo running with shr. Whenever I'm trying to type in my password (consisting of upper and lowercase letters) I can use the "shift" key on the "Terminal" keyboard, but a lowercase letter is sent. How do I get uppercase letters? Bye, Nils ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
phone as usb keyboard
I don't want to plug a keyboard into the phone, I want to plug the phone into a laptop and use the phone as a 2nd keyboard. assuming it is, the goal is to use a web cam as a bar code scanner, app on phone uses scan data to generate "keyboard" clicks that get send to the laptop. (no, we can't just run the software on the laptop. all we can do is hook up an external HID like device.) Is this doable? Carl K ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Finger-based keyboard
leonardo wrote: > Hello all, One more thing.. I use Freerunner with 2007.2 bye, leonardo. -- http://leonardo.lilik.it Key fingerprint = 2C20 A587 05AC 42E5 1292 D0D4 3EED CFB5 52FD AD1E ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Finger-based keyboard
leonardo wrote: > given this, I'd like to know if there is, somewhere, a finger-based > (qwerty) keyboard that can be easily used, for example to send sms or > write urls. I've found this [1] page which presents something as I > whish, but could not find any more link to it. The matchbox is > finger-unusable, and sometimes you just don't have the stylus around. Hi leonardo, I was looking for that keyboard too and I found it. It's the old (GTK 2007) openmoko-keyboard that is available on svn archives. I've not tried it on my FR (I've mostly used qtopia) but it runs on my PC. For more informations and instructions for getting it refer to this [1] old community thread. Bye! [1] http://tinyurl.com/5oejft -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Finger-based keyboard
Am Mo 28. Juli 2008 schrieb Marco Trevisan (Treviño): > leonardo wrote: > > given this, I'd like to know if there is, somewhere, a finger-based > > (qwerty) keyboard that can be easily used, for example to send sms or > > write urls. I've found this [1] page which presents something as I > > whish, but could not find any more link to it. The matchbox is > > finger-unusable, and sometimes you just don't have the stylus around. > > Hi leonardo, I was looking for that keyboard too and I found it. It's > the old (GTK 2007) openmoko-keyboard that is available on svn archives. > > I've not tried it on my FR (I've mostly used qtopia) but it runs on my > PC. For more informations and instructions for getting it refer to this > [1] old community thread. > > Bye! > > [1] http://tinyurl.com/5oejft PLEASE don't use tiny-urls and the like, they are very volatile and don't tell true destination. Some months in the future this post is worthless with broken tiny-url. :-( [1]: <http://thread.gmane.org/gmane.comp.handhelds.openmoko.community/16811/focus=17273> /jOERG signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Finger-based keyboard
On Mon, Jul 28, 2008 at 4:55 AM, Joerg Reisenweber <[EMAIL PROTECTED]> wrote: > Am Mo 28. Juli 2008 schrieb Marco Trevisan (Treviño): > > leonardo wrote: > > > given this, I'd like to know if there is, somewhere, a finger-based > > > (qwerty) keyboard that can be easily used, for example to send sms or > > > write urls. I've found this [1] page which presents something as I > > > whish, but could not find any more link to it. The matchbox is > > > finger-unusable, and sometimes you just don't have the stylus around. > > > > Hi leonardo, I was looking for that keyboard too and I found it. It's > > the old (GTK 2007) openmoko-keyboard that is available on svn archives. > > > > I've not tried it on my FR (I've mostly used qtopia) but it runs on my > > PC. For more informations and instructions for getting it refer to this > > [1] old community thread. > > > > Bye! > > > > [1] http://tinyurl.com/5oejft > > PLEASE don't use tiny-urls and the like, they are very volatile and don't > tell > true destination. > Some months in the future this post is worthless with broken tiny-url. :-( > > [1]: > < > http://thread.gmane.org/gmane.comp.handhelds.openmoko.community/16811/focus=17273 > > I can only support this. Tinyurl is a really terrible thing - especially where is no 160 signs short message limit... ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Finger-based keyboard
Marco Trevisan (Treviño) wrote: > leonardo wrote: > > given this, I'd like to know if there is, somewhere, a finger-based >> (qwerty) keyboard that can be easily used, for example to send sms or >> write urls. I've found this [1] page which presents something as I >> whish, but could not find any more link to it. The matchbox is >> finger-unusable, and sometimes you just don't have the stylus around. > > Hi leonardo, I was looking for that keyboard too and I found it. It's > the old (GTK 2007) openmoko-keyboard that is available on svn archives. > thanks! ciao, leonardo. -- http://leonardo.lilik.it Key fingerprint = 2C20 A587 05AC 42E5 1292 D0D4 3EED CFB5 52FD AD1E ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume keyboard Disappeared
I myself asked this question recently.(Please search the mailing list before posting) http://n2.nabble.com/preserving-illume-keyboard-on-update-tp778734p778734.html link Armin ranjbar wrote: > > after running a few while , maybe after suspends , Illume keyboard does > not appear and standard om2008 keyboard appear , any one has any idea ? > > > -- > Armin ranjbar , System Administrator > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > -- View this message in context: http://n2.nabble.com/Illume-keyboard-Disappeared-tp784751p785127.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume keyboard Disappeared
VictorSigma wrote: Armin ranjbar wrote: > > after running a few while , maybe after suspends , Illume keyboard does > > not appear and standard om2008 keyboard appear , any one has any idea ? > > > I myself asked this question recently.(Please search the mailing list before > posting) > http://n2.nabble.com/preserving-illume-keyboard-on-update-tp778734p778734.html > > link > > > But that thread has no answer either... Anyone know how to enable a full keyboard with the new update? -- Alex ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume keyboard Disappeared
On Tue, 26 Aug 2008 16:00:08 -0400 Alex Fitzpatrick <[EMAIL PROTECTED]> babbled: > VictorSigma wrote: > > Armin ranjbar wrote: > > > > after running a few while , maybe after suspends , Illume keyboard does > > > not appear and standard om2008 keyboard appear , any one has any idea ? > > > > > > I myself asked this question recently.(Please search the mailing list before > > posting) > > http://n2.nabble.com/preserving-illume-keyboard-on-update-tp778734p778734.html > > > > link > > > > > > > But that thread has no answer either... Anyone know how to enable a full > keyboard with the new update? as best i know there is no way to turn qpe's keyboard off. until that happens there will always be fighting between illume's own keyboard and qpe's (As the vkbd system is generic allowing for any keyboard window - and illume just creates one of its own that gets picked up by the generic system). -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume keyboard Disappeared
On Wed, 27 Aug 2008 09:28:55 +1000, Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > On Tue, 26 Aug 2008 16:00:08 -0400 Alex Fitzpatrick > as best i know there is no way to turn qpe's keyboard off. until that > happens > there will always be fighting between illume's own keyboard and qpe's (As > the > vkbd system is generic allowing for any keyboard window - and illume just > creates one of its own that gets picked up by the generic system). > > -- > Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> Right now, that's an IMMENSE irritation for me. (and to judge by mailinglist traffic, for many many others as well) I had xterm running today, typing on the 'full qwerty' keyboard, and while I was staring at the screen that keyboard went away and the 'letters only' one appeared, and the only way I could get cursor keys back was to reboot the goddammed thing. I dare anyone to try editing a file with that useless excuse for a keyboard. It may be good for text messaging and naming entries in Contacts, but even there it has shortcomings, mostly caused by the dictionary interaction. The predictive error introduction and the need to switch keyboards for punctuation and numbers means it takes a painfully long time to type something like 'ip r d default via 192.168.0.201'. If the damned thing would just stay shut off when disabled it'd be acceptable. I've been seriously considering flashing to a different OS just because of the keyboard. Any OS that intermittently removes cursor keys requiring reboot to restore them is broken. j PS - I realize this and similar posts are mostly 'preaching to the choir'. Since a polling mechanism isn't readily available, would it be useful to start a 'qtopia keyboard vote' thread where people can be encouraged to post a simple 'make it die' or 'I love it' or whatever as a vote? Clearly someone controlling such decisions at Openmoko is insufficiently aware of the general loathing within the community toward that keyboard. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume keyboard Disappeared
On Wed, Aug 27, 2008 at 2:14 AM, Joel Newkirk <[EMAIL PROTECTED]> wrote: > On Wed, 27 Aug 2008 09:28:55 +1000, Carsten Haitzler (The Rasterman) > <[EMAIL PROTECTED]> wrote: >> On Tue, 26 Aug 2008 16:00:08 -0400 Alex Fitzpatrick Clearly > someone controlling such decisions at Openmoko is insufficiently aware of > the general loathing within the community toward that keyboard. How the hell can they be unaware after a hundred mails all saying the same? I have not read one mail from a user that said he found this keyboard useful in the state it is right now. Everybody who has the phone at this stage NEEDS to enter funky words in his terminal. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume keyboard Disappeared
I like qtopia's keyboard, but ONLY for text messaging. I can use that one w/ my fingers, which makes sending texts, while driving, easy. I cannot use the illume keyboard with my thumbs. Ultimately, I would like qtopia's to show up ONLY when sending a message, and illume to show up every where else. That's just my preference, but if I can figure that out I'd be a happy panda. . . .shawn Yorick Moko wrote: > On Wed, Aug 27, 2008 at 2:14 AM, Joel Newkirk <[EMAIL PROTECTED]> wrote: >> On Wed, 27 Aug 2008 09:28:55 +1000, Carsten Haitzler (The Rasterman) >> <[EMAIL PROTECTED]> wrote: >>> On Tue, 26 Aug 2008 16:00:08 -0400 Alex Fitzpatrick > Clearly >> someone controlling such decisions at Openmoko is insufficiently aware of >> the general loathing within the community toward that keyboard. > > > How the hell can they be unaware after a hundred mails all saying the same? > I have not read one mail from a user that said he found this keyboard > useful in the state it is right now. Everybody who has the phone at > this stage NEEDS to enter funky words in his terminal. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Intermittant bluetooth keyboard - more
Oops, I said 10% and then I said 25% :p Needless to say it's an annoyingly low percentage of the time that it all works smoothly. -- Daniel Benoy http://daniel.benoy.name ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
keyboard - gaming, virtual gamepad
Hello I do see options for number/default and terminal for keyboard. Is there an option for "Gamepad" keyboard ? A C B Up arrow D Down Arrow Left Arrow E Right Arrow -- Ritesh Khadgaray Ph: +919970164885 Desktop LinuX N Stuff, RHCE Software Maintenance Engineer, Pune, Red Hat ॐ मणि पद्मे हूँ Eat Right, Exercise, Die Anyway. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Intermittant bluetooth keyboard
I completely drained the battery in my keyboard and now it's working every time. I wish that there was some way to change this LMP timeout though. Try as I might I couldn't find it. On Monday 08 September 2008 13:23:15 Daniel Benoy wrote: > I set up my bluetooth keyboard on my openmoko phone using the 'new' (In other > words, not hidd, but still dbus) input interface, and it only works like 10% > of the time. That means when I turn it on it should connect and start > working. Unfortunately, it only works about 25% of the time, and I have to > switch it off and on frequenly in order to get it to finally connect. I get > this output from hcidump -V when it doesn't work: > > > HCI Event: Connect Request (0x04) plen 10 > bdaddr 00:0A:DF:00:24:59 class 0x002540 type ACL > < HCI Command: Accept Connection Request (0x01|0x0009) plen 7 > bdaddr 00:0A:DF:00:24:59 role 0x00 > Role: Master > > HCI Event: Command Status (0x0f) plen 4 > Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1 > > HCI Event: Connect Complete (0x03) plen 11 > status 0x22 handle 42 bdaddr 00:0A:DF:00:24:59 type ACL encrypt 0x00 > Error: LMP Response Timeout > > The difference in time between 'Accept Connection Request' and 'LMP Response > Timeout' is about 3 seconds. I was under the impression that LMP negociation > was supposed to time out after 30 seconds? > > Is there something I'm doing wrong? Am I not interprating this correctly? > > If it does work I get something like this: > > > HCI Event: Connect Request (0x04) plen 10 > bdaddr 00:0A:DF:00:24:59 class 0x002540 type ACL > < HCI Command: Accept Connection Request (0x01|0x0009) plen 7 > bdaddr 00:0A:DF:00:24:59 role 0x00 > Role: Master > > HCI Event: Command Status (0x0f) plen 4 > Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1 > > HCI Event: Link Key Request (0x17) plen 6 > bdaddr 00:0A:DF:00:24:59 > > . > . > . > > (And then link key request reply and so on it does its negociation and there > you have it) -- Daniel Benoy http://daniel.benoy.name ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qtopia and keyboard
Marc Rios wrote: > Hi to everybody, > > I have a problem with qtopia keyboard. I open the web browser and try to > open the gmail app. So when I go to put my password the keyboard > disapeares... Any idea??? I think this is a bug in web kit. -- Lorn 'ljp' Potter Software Engineer, Systems Group, Qt Software, Nokia Pty Ltd ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qtopia and keyboard
You can use the method "Keyboard" so you can hide and show it from the options menu as a workaround. A small, annoying bug. On Sun, Jan 4, 2009 at 11:00 PM, Lorn Potter wrote: > Marc Rios wrote: > > Hi to everybody, > > > > I have a problem with qtopia keyboard. I open the web browser and try to > > open the gmail app. So when I go to put my password the keyboard > > disapeares... Any idea??? > > I think this is a bug in web kit. > > -- > Lorn 'ljp' Potter > Software Engineer, Systems Group, Qt Software, Nokia Pty Ltd > > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- - Atilla Filiz Eindhoven University of Technology Embedded Systems, Master's Programme ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qtopia and keyboard
How can I do this??? Thanks in advance -- Marc Rios Nota: http://www.gnu.org/philosophy/no-word-attachments.es.html On Sun, Jan 4, 2009 at 11:26 PM, Atilla Filiz wrote: > You can use the method "Keyboard" so you can hide and show it from the > options menu as a workaround. A small, annoying bug. > > > On Sun, Jan 4, 2009 at 11:00 PM, Lorn Potter wrote: > >> Marc Rios wrote: >> > Hi to everybody, >> > >> > I have a problem with qtopia keyboard. I open the web browser and try to >> > open the gmail app. So when I go to put my password the keyboard >> > disapeares... Any idea??? >> >> I think this is a bug in web kit. >> >> -- >> Lorn 'ljp' Potter >> Software Engineer, Systems Group, Qt Software, Nokia Pty Ltd >> >> >> >> ___ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> > > > > -- > - > Atilla Filiz > Eindhoven University of Technology > Embedded Systems, Master's Programme > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qtopia and keyboard
Go to somewhere where keyboard is activated(browser should be just fine). Tap Options>change input method Repeat this until you see "hide keyboard" or "show keyboard" option. Now you can hide and show it at will. On Mon, Jan 5, 2009 at 12:41 AM, Marc Rios wrote: > How can I do this??? > > Thanks in advance > -- > Marc Rios > > Nota: http://www.gnu.org/philosophy/no-word-attachments.es.html > > > On Sun, Jan 4, 2009 at 11:26 PM, Atilla Filiz wrote: > >> You can use the method "Keyboard" so you can hide and show it from the >> options menu as a workaround. A small, annoying bug. >> >> >> On Sun, Jan 4, 2009 at 11:00 PM, Lorn Potter wrote: >> >>> Marc Rios wrote: >>> > Hi to everybody, >>> > >>> > I have a problem with qtopia keyboard. I open the web browser and try >>> to >>> > open the gmail app. So when I go to put my password the keyboard >>> > disapeares... Any idea??? >>> >>> I think this is a bug in web kit. >>> >>> -- >>> Lorn 'ljp' Potter >>> Software Engineer, Systems Group, Qt Software, Nokia Pty Ltd >>> >>> >>> >>> ___ >>> support mailing list >>> support@lists.openmoko.org >>> https://lists.openmoko.org/mailman/listinfo/support >>> >> >> >> >> -- >> - >> Atilla Filiz >> Eindhoven University of Technology >> Embedded Systems, Master's Programme >> >> >> ___ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> >> > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > -- - Atilla Filiz Eindhoven University of Technology Embedded Systems, Master's Programme ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: illume-Keyboard lowercase?
On Thursday 08 October 2009, Nils Bokermann wrote: > Hi! > > I'm trying to get my Neo running with shr. Whenever I'm trying to type > in my password (consisting of upper and lowercase letters) I can use the > "shift" key on the "Terminal" keyboard, but a lowercase letter is sent. > > How do I get uppercase letters? Shift key gives upper case for me in shr unstable for every use I've tried. What exactly are you trying to do? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: illume-Keyboard lowercase?
Al Johnson wrote: > On Thursday 08 October 2009, Nils Bokermann wrote: >> Hi! Hi! >> >> I'm trying to get my Neo running with shr. Whenever I'm trying to type >> in my password (consisting of upper and lowercase letters) I can use the >> "shift" key on the "Terminal" keyboard, but a lowercase letter is sent. >> >> How do I get uppercase letters? > > Shift key gives upper case for me in shr unstable for every use I've tried. > What exactly are you trying to do? I'm trying to get my password typed in (which consists of lower-case and upper case letters...) What I experience (even in the terminal-application) is: I *can* use the shift-key and an uppercase-letter is shown as I type on the keyboard, but on the terminal-screen, a lowercase letter is written. Installed is: e-wm-theme-illume - 0.16.999.050+svnr41040-r5.5 e-wm-config-illume-shr - 1.1-41040-gitr187+ee8d21beae597778056fa83168f9aa571720821b-r6 - e-wm-config-illume - 0.16.999.050+svnr41040-r5.5 e-wm-theme-illume-shr - 1.1-41040-gitr187+ee8d21beae597778056fa83168f9aa571720821b-r6 - Did I install (or delete) something wrong? Bye, Nils ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: illume-Keyboard lowercase?
2009/10/12 Nils Bokermann : > Al Johnson wrote: >> On Thursday 08 October 2009, Nils Bokermann wrote: >>> Hi! > > Hi! > >>> >>> I'm trying to get my Neo running with shr. Whenever I'm trying to type >>> in my password (consisting of upper and lowercase letters) I can use the >>> "shift" key on the "Terminal" keyboard, but a lowercase letter is sent. >>> >>> How do I get uppercase letters? >> >> Shift key gives upper case for me in shr unstable for every use I've tried. >> What exactly are you trying to do? > > I'm trying to get my password typed in (which consists of lower-case and > upper case letters...) > > What I experience (even in the terminal-application) is: > I *can* use the shift-key and an uppercase-letter is shown as I type on the > keyboard, but on the terminal-screen, a lowercase letter is written. For the terminal: has someone (or something) changed the conversion handling for input? When you type "stty -a", do you see a "-iuclc" in the params or just a "iuclc"? For the latter case, you can fix that with "stty -iuclc". ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: illume-Keyboard lowercase?
Joachim Ott wrote: > 2009/10/12 Nils Bokermann : >> Al Johnson wrote: >>> On Thursday 08 October 2009, Nils Bokermann wrote: >>>> Hi! >> Hi! >> >>>> I'm trying to get my Neo running with shr. Whenever I'm trying to type >>>> in my password (consisting of upper and lowercase letters) I can use the >>>> "shift" key on the "Terminal" keyboard, but a lowercase letter is sent. >>>> >>>> How do I get uppercase letters? >>> Shift key gives upper case for me in shr unstable for every use I've tried. >>> What exactly are you trying to do? >> I'm trying to get my password typed in (which consists of lower-case and >> upper case letters...) >> >> What I experience (even in the terminal-application) is: >> I *can* use the shift-key and an uppercase-letter is shown as I type on the >> keyboard, but on the terminal-screen, a lowercase letter is written. > > For the terminal: has someone (or something) changed the conversion > handling for input? When you type "stty -a", do you see a "-iuclc" in > the params or just a "iuclc"? For the latter case, you can fix that > with "stty -iuclc". > Hi Joachim, its not only the terminal. And for sake of completness: the terminal is set -iuclc. Thanks, Nils ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: illume-Keyboard lowercase?
On Mon, 12 Oct 2009 15:19:47 +0200 Nils Bokermann said: > Joachim Ott wrote: > > 2009/10/12 Nils Bokermann : > >> Al Johnson wrote: > >>> On Thursday 08 October 2009, Nils Bokermann wrote: > >>>> Hi! > >> Hi! > >> > >>>> I'm trying to get my Neo running with shr. Whenever I'm trying to type > >>>> in my password (consisting of upper and lowercase letters) I can use the > >>>> "shift" key on the "Terminal" keyboard, but a lowercase letter is sent. > >>>> > >>>> How do I get uppercase letters? > >>> Shift key gives upper case for me in shr unstable for every use I've > >>> tried. What exactly are you trying to do? > >> I'm trying to get my password typed in (which consists of lower-case and > >> upper case letters...) > >> > >> What I experience (even in the terminal-application) is: > >> I *can* use the shift-key and an uppercase-letter is shown as I type on the > >> keyboard, but on the terminal-screen, a lowercase letter is written. > > > > For the terminal: has someone (or something) changed the conversion > > handling for input? When you type "stty -a", do you see a "-iuclc" in > > the params or just a "iuclc"? For the latter case, you can fix that > > with "stty -iuclc". > > > > Hi Joachim, > > its not only the terminal. And for sake of completness: the terminal is > set -iuclc. calitals (shift) works in illume upstream, in xephyr and as people say - works on their gta02's with shr. i tested it and it works here. chances are u are missing keymaps for x that indicate "shift + a == A". literally these keymaps define such behavior and illume is just sending fake shifts+ a's to x via the x test extension. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alternate Keyboard(s) on 2008.8 - I have the full terminal keyboard
I don't really understand why, but sometimes I get the predictive text (limited keys) and sometimes I get the full keyboard (choice of three). I used ASU 200080806, then opkg update..etc. Ole Kliemann wrote: > There is only one possible solution. There must be easy customizable > keyboard files so that everybody is able to use the keyboard he likes. > Besides there must be an option to switch between different keyboards. > It's a simple idea: one tool for one job. > > The predictive text with the right dictionary can be very powerful when > writing SMS. You don't really need to aim for the letters, just hit > somewhere close to them. > > Still the Qtopia keyboard like it comes with Om2008.8 now is pretty > flawed lacking punctation signs. You have to switch two layouts further > to find a comma or period. Despite the fact that there is a lot of space > left on the alphabet keyboard. > > And certainly for everything except SMS and maybe sometimes writing > notes the layout alone is a disaster; not to mention the predictive > text. > > As I understand, there has been a long discussion about why not using > the illume keyboard. I have not completely followed that discussion and > I do not claim to have an understanding for the problems of development > that may be connected to this issue. > > But I'd like to stress at this point that I believe the customizability > of input methods - i.e. the possibility of individually communicating > with the device - is a kind of freedom that many people are seeking with > the FR. > > Ole > > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: phone as usb keyboard
On Wed, Jul 16, 2008 at 10:19 AM, Carl Karsten <[EMAIL PROTECTED]> wrote: > I don't want to plug a keyboard into the phone, I want to plug the phone into > a > laptop and use the phone as a 2nd keyboard. > > assuming it is, the goal is to use a web cam as a bar code scanner, app on > phone > uses scan data to generate "keyboard" clicks that get send to the laptop. > > (no, we can't just run the software on the laptop. all we can do is hook up > an > external HID like device.) > > Is this doable? > Yes, in theory. You'd first need to set the moko into USB-endpoint (instead of USB-host) mode, and you'd need to write some mad kernel hax that make it show up as a keyboard, and you'd need to expose the mad kernel hax to userland on the moko so your barcode scanner can send data. ..it's really a whole lot simpler just to use TCP. Why can't you run software on the laptop? Some sort of locked down corporate situation? -Nick ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: phone as usb keyboard
On Wednesday 16 July 2008, Nick Guenther wrote: > On Wed, Jul 16, 2008 at 10:19 AM, Carl Karsten <[EMAIL PROTECTED]> wrote: > > I don't want to plug a keyboard into the phone, I want to plug the phone > > into a laptop and use the phone as a 2nd keyboard. > > > > assuming it is, the goal is to use a web cam as a bar code scanner, app > > on phone uses scan data to generate "keyboard" clicks that get send to > > the laptop. > > > > (no, we can't just run the software on the laptop. all we can do is hook > > up an external HID like device.) > > > > Is this doable? > > Yes, in theory. You'd first need to set the moko into USB-endpoint > (instead of USB-host) mode, and you'd need to write some mad kernel > hax that make it show up as a keyboard, and you'd need to expose the > mad kernel hax to userland on the moko so your barcode scanner can > send data. > ..it's really a whole lot simpler just to use TCP. > > Why can't you run software on the laptop? Some sort of locked down > corporate situation? As you say, being a USB HID should be possible if you write a new USB Gadget driver. However in the proposed scenario we need to attach to a webcam, presumably also by USB. In this case we need to be both host and client which AFAIK is impossible under USB. I thought USB barcode scanners could behave as an HID anyway? If you really need to do something custom with the barcode data you could use a serial barcode scanner with a USB-capable microcontroller for a fraction of the price anyway - these often provide the HID stack as example code. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Alternate Keyboard(s) on 2008.8
Is is possible to install a different keyboard on 2008.8? If not, I'd like to see that as a feature Real Soon Now. I find the stock keyboard to be almost totally unusable due to the predictive text feature. Even if the predictive stuff was removed, it would still be less usable for me than the matchbox qwerty keyboard, which had important keys like ctrl, dash, period and return all on the same page. I will be using the phone with a stylus for most interaction, so I don't need a finger-friendly keyboard. It might be nice to occasionally have one, but it's a *very* low priority for me. I will primarily type in the terminal, the "notes" app, and the browser: unix commands, URLs, and notes like book titles, author names, part numbers and the like. In other words, almost nothing I type will benefit from predictive input (in fact it would be a distinct annoyance). -- Dirk ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
2008.8 Turn off keyboard 'guessing'??
Ok, I'm starting to figure out the new keyboard a little, now I can backspace and 'forwardspace'. But right now I'm wanting to type an URL in to the web browser, that doesn't seem to be possible with the predictive behavior. I'd like to turn that off, is there a way to do that? If I get the terminal installed too I would think it would also be unworkable with prediction. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
preserving illume keyboard on update
I currently have the 20080823 openmoko-qtopia-x11-image-om-gta02.jffs2 image flashed on my freerunner and it is working great. The problem is that it originally comes with the illume keyboard pre-installed but whenever I 'opkg update' the keyboard is changed to the qtopia version. Is there anyway to preserve the illume keyboard or reinstall it after the update? thanks -- View this message in context: http://n2.nabble.com/preserving-illume-keyboard-on-update-tp778734p778734.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[OM2008.9] HID keyboard layout configuration
Hi, I'm trying to use a non-qwerty HID keyboard (more precisely an azerty Logitech), and I haven't been able to find out if the Xglamo keyboard can be set to azerty. I'm not even sure there's a configuration file. Any suggestion? Has somebody already tried this? Note: BTW, the hid keyboard doesn't work well in the console. I can switch to tty1 but then lots of keys don't work and I'm stuck :) -- MiKael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
German layout for usb keyboard?
Hi there! I just got my mini-usb-keyboard for my freerunner, and I'm very happy that it works "out of the box" - mostly, that is: How do I set a german layout for the keyboard under X? Normally, I would have done it by editing the xorg.conf, but since I can't find it, there has got to be another way, right? Any help would be very much appreciated :) Regards, Konstantin ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Illume keyboard breaks on om2008.12
Hi there, according to this [1], I just: 1 .- opkg install libevas-saver-png edje-utils cpp cpp-symlinks libembryo-tests 2 .- cd /usr/share/enlightenment/data/themes 3 .- edje_decc illume.edj 4 .- cd illume 5 .- vi freerunner.edc (to edit a copule of lines, but "freerunner.sh") 6 .- sh build.sh 7 .- mv illume.edj ../illume.edj 8 .- /etc/init.d/xserver-nodm restart 9 .- sed -i -e s,asu,illume, /etc/enlightenment/default_profile 10.- /etc/init.d/xserver-nodm restart and I would get the illume keybord. Setp 5 is not necessary 'couse you can use illume.edj instead which does not need to be edited. Well, it works, but then it fails. Enlightenment start (splash screen shows up) and you get the illume keyboard, but then I get: "Enlightenment error" "This is very bad. Enlightenment SIGABRt'd" =-O "Theres is no meant to happen and it is likely a sign of a bug on Enlightenment or the libraries it relies on. You can gob attach to this process to try debug it or you could exit, or you just hit restart to try and get your desktop back to the way it was." "Please compile everything with -g in your CFLAGS" I know I can compile using -g, but you might have some other options. (sure I would update the wiki :-) ) [1] http://wiki.openmoko.org/wiki/Keyboard_Toggle Cheers, Kosa - Un mundo mejor es posible - ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Keyboard not working on latest ASU
After `opkg update ; opkg upgrade' on my FR using ASU this morning, the onscreen keyboard is broken. It is still displayed and when striking a key the letter is raised but nothing more; the input is not working. Also the `drag-up-gesture' for switching the layout to numbers is not working. Problem resides when reflashing with: http://buildhost.openmoko.org/daily/freerunner/200807/20080718/uImage-om-gta02-latest.bin http://buildhost.openmoko.org/daily/freerunner/200807/20080718/openmoko-qtopia-x11-image-om-gta02.jffs2 pgp4HqmHdWfKD.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Qtopia: customize keyboard, select input language
With ASU you can use your own layout for the onscreen keyboard. It's a simple text file .kbd you can customize. Is there something similar with Qtopia? The full keyboard has too small buttons to be used with fingers. The predicative keyboard is not working very good. I want English as language displayed, but German as input-language. I have chosen as language U.S. English but checked the `use for input' box for German. Still the predicative keyboard seems only to use English. Thanks in advance for any hints. Ole pgpI2fC4wtSho.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
qtopia: keys missing for predictive keyboard?
Hi! >From what I have seen, the predictive keyboard of qtopia for the freerunner is IMO by far the best typing solution for text messages. But is it just me or are there some keys missing for touchscreen? I have not found a possibility to erase letters or to enter special keys etc. -- [EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alternate Keyboard(s) on 2008.8
+1 This sums my feelings up exactly Dirk Bergstrom wrote: > Is is possible to install a different keyboard on 2008.8? If not, I'd > like to see that as a feature Real Soon Now. > > I find the stock keyboard to be almost totally unusable due to the > predictive text feature. Even if the predictive stuff was removed, it > would still be less usable for me than the matchbox qwerty keyboard, > which had important keys like ctrl, dash, period and return all on the > same page. > > I will be using the phone with a stylus for most interaction, so I don't > need a finger-friendly keyboard. It might be nice to occasionally have > one, but it's a *very* low priority for me. > > I will primarily type in the terminal, the "notes" app, and the browser: > unix commands, URLs, and notes like book titles, author names, part > numbers and the like. In other words, almost nothing I type will > benefit from predictive input (in fact it would be a distinct annoyance). > > -- > Dirk > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alternate Keyboard(s) on 2008.8
+100 On Fri, Aug 8, 2008 at 10:22 PM, Dale Maggee <[EMAIL PROTECTED]> wrote: > +1 > > This sums my feelings up exactly > > Dirk Bergstrom wrote: >> Is is possible to install a different keyboard on 2008.8? If not, I'd >> like to see that as a feature Real Soon Now. >> >> I find the stock keyboard to be almost totally unusable due to the >> predictive text feature. Even if the predictive stuff was removed, it >> would still be less usable for me than the matchbox qwerty keyboard, >> which had important keys like ctrl, dash, period and return all on the >> same page. >> >> I will be using the phone with a stylus for most interaction, so I don't >> need a finger-friendly keyboard. It might be nice to occasionally have >> one, but it's a *very* low priority for me. >> >> I will primarily type in the terminal, the "notes" app, and the browser: >> unix commands, URLs, and notes like book titles, author names, part >> numbers and the like. In other words, almost nothing I type will >> benefit from predictive input (in fact it would be a distinct annoyance). >> >> -- >> Dirk >> >> ___ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> >> > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alternate Keyboard(s) on 2008.8
On Sat, Aug 09, 2008 at 06:22 (+1000), Dale Maggee wrote: > +1 +1 The present keyboard is nice for showing off and pleasing the eye but to it's only useful in specific situations like writing sms, not for generic operation on a linux system. As this is not an iPhone I'd prefer to have a fully functional keyboard. /Ben ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alternate Keyboard(s) on 2008.8
Could we please also get a qwerty keyboard on the GTA01? I don't have a GTA02. I complained when it was changed, but it didn't seem to matter to the people making the general releases. And when given the choice of a qwerty keyboard, shouldn't international characters be of some priority? Peter Yorick Moko wrote: > +100 > > On Fri, Aug 8, 2008 at 10:22 PM, Dale Maggee <[EMAIL PROTECTED]> wrote: > >> +1 >> >> This sums my feelings up exactly >> >> Dirk Bergstrom wrote: >> >>> Is is possible to install a different keyboard on 2008.8? If not, I'd >>> like to see that as a feature Real Soon Now. >>> >>> I find the stock keyboard to be almost totally unusable due to the >>> predictive text feature. Even if the predictive stuff was removed, it >>> would still be less usable for me than the matchbox qwerty keyboard, >>> which had important keys like ctrl, dash, period and return all on the >>> same page. >>> >>> I will be using the phone with a stylus for most interaction, so I don't >>> need a finger-friendly keyboard. It might be nice to occasionally have >>> one, but it's a *very* low priority for me. >>> >>> I will primarily type in the terminal, the "notes" app, and the browser: >>> unix commands, URLs, and notes like book titles, author names, part >>> numbers and the like. In other words, almost nothing I type will >>> benefit from predictive input (in fact it would be a distinct annoyance). >>> >>> -- >>> Dirk >>> >>> ___ >>> support mailing list >>> support@lists.openmoko.org >>> https://lists.openmoko.org/mailman/listinfo/support >>> >>> >>> >> ___ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> >> > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alternate Keyboard(s) on 2008.8
There is only one possible solution. There must be easy customizable keyboard files so that everybody is able to use the keyboard he likes. Besides there must be an option to switch between different keyboards. It's a simple idea: one tool for one job. The predictive text with the right dictionary can be very powerful when writing SMS. You don't really need to aim for the letters, just hit somewhere close to them. Still the Qtopia keyboard like it comes with Om2008.8 now is pretty flawed lacking punctation signs. You have to switch two layouts further to find a comma or period. Despite the fact that there is a lot of space left on the alphabet keyboard. And certainly for everything except SMS and maybe sometimes writing notes the layout alone is a disaster; not to mention the predictive text. As I understand, there has been a long discussion about why not using the illume keyboard. I have not completely followed that discussion and I do not claim to have an understanding for the problems of development that may be connected to this issue. But I'd like to stress at this point that I believe the customizability of input methods - i.e. the possibility of individually communicating with the device - is a kind of freedom that many people are seeking with the FR. Ole pgpKupNw21yrF.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alternate Keyboard(s) on 2008.8
Dirk Bergstrom wrote: > Is is possible to install a different keyboard on 2008.8? If not, I'd > like to see that as a feature Real Soon Now. > > I find the stock keyboard to be almost totally unusable due to the > predictive text feature. Even if the predictive stuff was removed, it > would still be less usable for me than the matchbox qwerty keyboard, > which had important keys like ctrl, dash, period and return all on the > same page. > > I will be using the phone with a stylus for most interaction, so I don't > need a finger-friendly keyboard. It might be nice to occasionally have > one, but it's a *very* low priority for me. > > I will primarily type in the terminal, the "notes" app, and the browser: > unix commands, URLs, and notes like book titles, author names, part > numbers and the like. In other words, almost nothing I type will > benefit from predictive input (in fact it would be a distinct annoyance). > > -- > Dirk > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > > I think the stock keyboard (once got my head round it, I rather liked its novel approach) would be good for sms, but I would love to see the matchbox keyboard added as part of the stock keyboard options, ie swipe through upper case, numerals, special chars and then get the matchbox keyboard (or similar) for when it is needed. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Alternate Keyboard(s) on 2008.8
Peter there is a good keyboard in the Milestone 2. If using it you need to press the little triangle to get home then the terminal icon then qwerty(top left) then the icon top right of the keyboard which offers "full-qwerty", at this point you have all the characters you need, no prediction and somewhere to type them. The letters jumping up is distracting, and the black background, though elegant, makes the stylus hard to see in poor light. Nonetheless the FSO is so good that I am now preferring it. Another couple of Milestones and it will be really nice. At that point apparently there are plans to clutter it with changes. (See thread in Community list "FSO: is zhone here to stay?" ) FSO is apparently only semi-official. Debian also has a good keyboard named xvkbd which has all you want, has facilities for a number of changes including charactersets at user level. Debian I think will be good for GTA01 after it gets a few more changes. I use it now as a dual boot alongside FSO, have not yet added phone capability. clare. On Fri, Aug 8, 2008 at 9:11 PM, Peter Rasmussen <[EMAIL PROTECTED]> wrote: > Could we please also get a qwerty keyboard on the GTA01? I don't have a > GTA02. > I complained when it was changed, but it didn't seem to matter to the > people making the general releases. > And when given the choice of a qwerty keyboard, shouldn't international > characters be of some priority? > > Peter > > Yorick Moko wrote: >> +100 >> >> On Fri, Aug 8, 2008 at 10:22 PM, Dale Maggee <[EMAIL PROTECTED]> wrote: >> >>> +1 >>> >>> This sums my feelings up exactly >>> >>> Dirk Bergstrom wrote: >>> >>>> Is is possible to install a different keyboard on 2008.8? If not, I'd >>>> like to see that as a feature Real Soon Now. >>>> >>>> I find the stock keyboard to be almost totally unusable due to the >>>> predictive text feature. Even if the predictive stuff was removed, it >>>> would still be less usable for me than the matchbox qwerty keyboard, >>>> which had important keys like ctrl, dash, period and return all on the >>>> same page. >>>> >>>> I will be using the phone with a stylus for most interaction, so I don't >>>> need a finger-friendly keyboard. It might be nice to occasionally have >>>> one, but it's a *very* low priority for me. >>>> >>>> I will primarily type in the terminal, the "notes" app, and the browser: >>>> unix commands, URLs, and notes like book titles, author names, part >>>> numbers and the like. In other words, almost nothing I type will >>>> benefit from predictive input (in fact it would be a distinct annoyance). >>>> >>>> -- >>>> Dirk >>>> >>>> ___ >>>> support mailing list >>>> support@lists.openmoko.org >>>> https://lists.openmoko.org/mailman/listinfo/support >>>> >>>> >>>> >>> ___ >>> support mailing list >>> support@lists.openmoko.org >>> https://lists.openmoko.org/mailman/listinfo/support >>> >>> >> >> ___ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: 2008.8 Turn off keyboard 'guessing'??
On Sun, Aug 10, 2008 at 11:51:09AM -0600, B wrote: > Ok, I'm starting to figure out the new keyboard a little, now I can > backspace and 'forwardspace'. But right now I'm wanting to type an URL > in to the web browser, that doesn't seem to be possible with the > predictive behavior. I'd like to turn that off, is there a way to do > that? If I get the terminal installed too I would think it would also > be unworkable with prediction. AFAIK you can't turn it off completely, but you can override it for single letters by holding the letter for more than 1 or 2 seconds: http://wiki.openmoko.org/wiki/Om2008.8_Keyboard#Keyboard_Zoom This wasn't really mentioned in the wiki before, so I added a hint on this here: http://wiki.openmoko.org/wiki/Om_2008.8_Guide HTH, Thomas ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: preserving illume keyboard on update
VictorSigma wrote: > I currently have the 20080823 openmoko-qtopia-x11-image-om-gta02.jffs2 image > flashed on my freerunner and it is working great. The problem is that it > originally comes with the illume keyboard pre-installed but whenever I 'opkg > update' the keyboard is changed to the qtopia version. Is there anyway to > preserve the illume keyboard or reinstall it after the update? > > thanks rasterman explained this already. qpe (the monolithic binary blob that makes phone calls) is hardcoded to start up its own keyboard. If qpe registers its keyboard first, then you don't get the illume one anymore. I think the fix is to break disable the qpe keyboard somehow. I've tried breaking it's config file, but that crashes qpe, breaking phone calls... I got a bit further than that, and think I found the code (51% sure...) that turns the qpe keyboard on, but now I don't have time to deal with it anymore. If you time to mess with it, consider rebuilding qpe with this patch removed: http://git.openmoko.org/?p=qtopia.git;a=commit;h=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04 the diff: http://git.openmoko.org/?p=qtopia.git;a=blobdiff;f=src/server/phone/serverinterface/phonelauncher/phonelauncher_illume.cpp;h=405a0b654e9c34a390d18e3466242de5de1cc53d;hp=623258b15a27a969dd8a0926884792936f41103b;hb=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04;hpb=38d2a3923ef46b12279901e5a5dc4c84aeae5d6e A better approach would add a config option to turn qpe's keyboard off. The long-term goal is to replace it with the illume one, but OM will be supporting the qpe keyboard in the near-term... -Rusty ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: preserving illume keyboard on update
There is a script on the wiki which enables you to install the full qwerty keyboard, unfortunately the last file gives a 404, which makes it rather useless. Is there a way, other then recompiling it, to get the good keyboard back? How does one get a dictionary for their own language, anyway? Or how do you get an Azerty keyboard? /Met vriendelijke groeten,/ *Jelle De Loecker* Kipdola Studios - Tomberg Russell Sears schreef: VictorSigma wrote: I currently have the 20080823 openmoko-qtopia-x11-image-om-gta02.jffs2 image flashed on my freerunner and it is working great. The problem is that it originally comes with the illume keyboard pre-installed but whenever I 'opkg update' the keyboard is changed to the qtopia version. Is there anyway to preserve the illume keyboard or reinstall it after the update? thanks rasterman explained this already. qpe (the monolithic binary blob that makes phone calls) is hardcoded to start up its own keyboard. If qpe registers its keyboard first, then you don't get the illume one anymore. I think the fix is to break disable the qpe keyboard somehow. I've tried breaking it's config file, but that crashes qpe, breaking phone calls... I got a bit further than that, and think I found the code (51% sure...) that turns the qpe keyboard on, but now I don't have time to deal with it anymore. If you time to mess with it, consider rebuilding qpe with this patch removed: http://git.openmoko.org/?p=qtopia.git;a=commit;h=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04 the diff: http://git.openmoko.org/?p=qtopia.git;a=blobdiff;f=src/server/phone/serverinterface/phonelauncher/phonelauncher_illume.cpp;h=405a0b654e9c34a390d18e3466242de5de1cc53d;hp=623258b15a27a969dd8a0926884792936f41103b;hb=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04;hpb=38d2a3923ef46b12279901e5a5dc4c84aeae5d6e A better approach would add a config option to turn qpe's keyboard off. The long-term goal is to replace it with the illume one, but OM will be supporting the qpe keyboard in the near-term... -Rusty ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: preserving illume keyboard on update
On Sun, 24 Aug 2008 01:53:47 +0200 Jelle De Loecker <[EMAIL PROTECTED]> babbled: the whole keyboard thing is a mess right now. illume has one - that seemingly people want. qpe has one that om wants. illume provides a gui config to turn it's keyboard on and off or launch a 3rd party vkbd app and use that. this gui is turned off by om and pretty much permanently inaccessible. qpe doesn't provide any way to say "yes" or "no" to getting its keyboard up. so basically qpe is playing the game of "take my keyboard or dont use qpe" right now, and illume is playing the game of "do what you want - i have config for that", but that game is pretty much inaccessible. there is a dbus call you can use to fiddle with some config but that incantation needs a dbus session key (so you'll need to steal it from a running session or do this with a terminal on the FR itself), but this still will only affect illume and do nothing about qpe. this all needs to be resolved and so it'll be a mess until it's cleared up. the wiki is not really correct - it's well behind any development and it's not really understanding how the keyboard works, but that has been changing rapidly. > There is a script on the wiki which enables you to install the full > qwerty keyboard, unfortunately the last file gives a 404, which makes it > rather useless. > > Is there a way, other then recompiling it, to get the good keyboard back? > > How does one get a dictionary for their own language, anyway? Or how do > you get an Azerty keyboard? > > /Met vriendelijke groeten,/ > > *Jelle De Loecker* > Kipdola Studios - Tomberg > > > > Russell Sears schreef: > > VictorSigma wrote: > > > >> I currently have the 20080823 openmoko-qtopia-x11-image-om-gta02.jffs2 > >> image flashed on my freerunner and it is working great. The problem is > >> that it originally comes with the illume keyboard pre-installed but > >> whenever I 'opkg update' the keyboard is changed to the qtopia version. Is > >> there anyway to preserve the illume keyboard or reinstall it after the > >> update? > >> > >> thanks > >> > > > > rasterman explained this already. qpe (the monolithic binary blob that > > makes phone calls) is hardcoded to start up its own keyboard. If qpe > > registers its keyboard first, then you don't get the illume one anymore. > > > > I think the fix is to break disable the qpe keyboard somehow. I've > > tried breaking it's config file, but that crashes qpe, breaking phone > > calls... I got a bit further than that, and think I found the code (51% > > sure...) that turns the qpe keyboard on, but now I don't have time to > > deal with it anymore. > > > > If you time to mess with it, consider rebuilding qpe with this patch > > removed: > > > > http://git.openmoko.org/?p=qtopia.git;a=commit;h=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04 > > > > the diff: > > > > http://git.openmoko.org/?p=qtopia.git;a=blobdiff;f=src/server/phone/serverinterface/phonelauncher/phonelauncher_illume.cpp;h=405a0b654e9c34a390d18e3466242de5de1cc53d;hp=623258b15a27a969dd8a0926884792936f41103b;hb=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04;hpb=38d2a3923ef46b12279901e5a5dc4c84aeae5d6e > > > > A better approach would add a config option to turn qpe's keyboard off. > > The long-term goal is to replace it with the illume one, but OM will be > > supporting the qpe keyboard in the near-term... > > > > -Rusty > > > > ___ > > support mailing list > > support@lists.openmoko.org > > https://lists.openmoko.org/mailman/listinfo/support > > > -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: preserving illume keyboard on update
Interesting! But "who" is openmoko? What group of persons decide this? And surely they must know about this? If not, and you want me to vent my frustration with the qpe keyboard somewhere else, just give me an address! I've made a list! :) I just hope this doesn't turn into something like the "gimp-in-one-window" struggle... Here's hoping for a good solution! Carsten Haitzler (The Rasterman) schreef: > On Sun, 24 Aug 2008 01:53:47 +0200 Jelle De Loecker <[EMAIL PROTECTED]> > babbled: > > the whole keyboard thing is a mess right now. illume has one - that seemingly > people want. qpe has one that om wants. illume provides a gui config to turn > it's keyboard on and off or launch a 3rd party vkbd app and use that. this gui > is turned off by om and pretty much permanently inaccessible. qpe doesn't > provide any way to say "yes" or "no" to getting its keyboard up. so basically > qpe is playing the game of "take my keyboard or dont use qpe" right now, and > illume is playing the game of "do what you want - i have config for that", but > that game is pretty much inaccessible. > > there is a dbus call you can use to fiddle with some config but that > incantation needs a dbus session key (so you'll need to steal it from a > running > session or do this with a terminal on the FR itself), but this still will only > affect illume and do nothing about qpe. > > this all needs to be resolved and so it'll be a mess until it's cleared up. > the > wiki is not really correct - it's well behind any development and it's not > really understanding how the keyboard works, but that has been changing > rapidly ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: preserving illume keyboard on update
On Mon, 25 Aug 2008 15:36:12 +0200 Jelle De Loecker <[EMAIL PROTECTED]> babbled: > Interesting! > But "who" is openmoko? What group of persons decide this? And surely > they must know about this? this has been beaten to death on the community list already :) i am just trying to give people what they are saying they want - as best i can. > If not, and you want me to vent my frustration with the qpe keyboard > somewhere else, just give me an address! > I've made a list! :) hahahahaha! :) seriously - right now asu is still young. it wont be perfect. it's missing a lot. i have actually now got FSO building myself and am already sending patches to mickey for the FSO build that does use the illume keyboard. i intend to continue to support FSO over the long term and have a reasonable go at the gui end of things there while mickey & gang really hammer at the back end. > I just hope this doesn't turn into something like the > "gimp-in-one-window" struggle... > > Here's hoping for a good solution! if you ask me... try FSO. the phone bits are not that mature - but it's definitely got a future going for it. :) > Carsten Haitzler (The Rasterman) schreef: > > On Sun, 24 Aug 2008 01:53:47 +0200 Jelle De Loecker <[EMAIL PROTECTED]> > > babbled: > > > > the whole keyboard thing is a mess right now. illume has one - that > > seemingly people want. qpe has one that om wants. illume provides a gui > > config to turn it's keyboard on and off or launch a 3rd party vkbd app and > > use that. this gui is turned off by om and pretty much permanently > > inaccessible. qpe doesn't provide any way to say "yes" or "no" to getting > > its keyboard up. so basically qpe is playing the game of "take my keyboard > > or dont use qpe" right now, and illume is playing the game of "do what you > > want - i have config for that", but that game is pretty much inaccessible. > > > > there is a dbus call you can use to fiddle with some config but that > > incantation needs a dbus session key (so you'll need to steal it from a > > running session or do this with a terminal on the FR itself), but this > > still will only affect illume and do nothing about qpe. > > > > this all needs to be resolved and so it'll be a mess until it's cleared up. > > the wiki is not really correct - it's well behind any development and it's > > not really understanding how the keyboard works, but that has been changing > > rapidly > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Debian-how to login without keyboard?
Hi there I have just installed debian in the sd card doing the partitions and copying a kernel and the "http://rabenfrost.net/debian/debian-armel-xfce.tar.bz2"; file and everything is running smooth until the gdm login prompt arise. There is any way, via ssh to make it autologin? or I have to do a vnc session to enter xfce? I'm a little bit ashamed , but I have no idea to where to begin. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Change keyboard language on-the-fly
Hi Is there any way to change keyboard language on-the-fly for the Qtopia predictive keyboard? I know that you can change the language in: /opt/Qtopia/etc/default/Trolltech/locale.conf if the languages are in: /opt/Qtopia/etc/dict/ But that won't do anything before the phone has been rebooted... So is it possible to force it to reload the cache? -- View this message in context: http://n2.nabble.com/Change-keyboard-language-on-the-fly-tp1082783p1082783.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: German layout for usb keyboard?
2008/12/15 Konstantin > Hi there! > > I just got my mini-usb-keyboard for my freerunner, and I'm very happy that > it > works "out of the box" - mostly, that is: How do I set a german layout for > the > keyboard under X? Normally, I would have done it by editing the xorg.conf, > but > since I can't find it, there has got to be another way, right? > Any help would be very much appreciated :) At least you can use xmodmap to change from default US to DE. Depending on your distribution you might have other tools to change the layout. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume keyboard breaks on om2008.12
uff -- to avoid people asking over and over again I've put a little hint into wiki page which seems everyone manage to find http://wiki.openmoko.org/wiki/Keyboard_Toggle#In_base-image_.28testing.29 actually section is Englightments segfaults with Illume theme too often? feel free to extend/correct -- .-. =-- /v\ = Keep in touch// \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User^^-^^[17] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
Am Samstag 19 Juli 2008 15:43:54 schrieb Ole Kliemann: > After `opkg update ; opkg upgrade' on my FR using ASU this morning, the > onscreen keyboard is broken. It is still displayed and when striking a > key the letter is raised but nothing more; the input is not working. > Also the `drag-up-gesture' for switching the layout to numbers is not > working. the input works, but is not displayed directly. If you use the stroke for space or return you can see it. but i could not switch the layout between letters and numbers. As a workaround I did: svn checkout http://svn.projects.openmoko.org/svnroot/illume scp illume/keyboards/* [EMAIL PROTECTED]:/usr/lib/enlightenment/modules/illume/keyboards/ then on the fr: cd /usr/lib/enlightenment/modules/illume/keyboards/ rm Default.kbd Numbers.kbd /etc/init.d/xserver-nodm restart this gives you a full qwerty-keyboard with arrow keys ;) Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Sat, Jul 19, 2008 at 01:43:54PM +, Ole Kliemann wrote: > After `opkg update ; opkg upgrade' on my FR using ASU this morning, the > onscreen keyboard is broken. It is still displayed and when striking a > key the letter is raised but nothing more; the input is not working. > Also the `drag-up-gesture' for switching the layout to numbers is not > working. > > Problem resides when reflashing with: > > http://buildhost.openmoko.org/daily/freerunner/200807/20080718/uImage-om-gta02-latest.bin > http://buildhost.openmoko.org/daily/freerunner/200807/20080718/openmoko-qtopia-x11-image-om-gta02.jffs2 The problem does not appear on: http://buildhost.openmoko.org/daily/freerunner/200807/20080715/openmoko-qtopia-x11-image-om-gta02.jffs2 pgpboPnocpvsi.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Sat, Jul 19, 2008 at 02:44:49PM +0200, Michael Münch wrote: > Am Samstag 19 Juli 2008 15:43:54 schrieb Ole Kliemann: > > After `opkg update ; opkg upgrade' on my FR using ASU this morning, the > > onscreen keyboard is broken. It is still displayed and when striking a > > key the letter is raised but nothing more; the input is not working. > > Also the `drag-up-gesture' for switching the layout to numbers is not > > working. > > the input works, but is not displayed directly. If you use the stroke for > space or return you can see it. but i could not switch the layout between > letters and numbers. > > As a workaround I did: > svn checkout http://svn.projects.openmoko.org/svnroot/illume > scp illume/keyboards/* > [EMAIL PROTECTED]:/usr/lib/enlightenment/modules/illume/keyboards/ > then on the fr: > cd /usr/lib/enlightenment/modules/illume/keyboards/ > rm Default.kbd Numbers.kbd > /etc/init.d/xserver-nodm restart > > this gives you a full qwerty-keyboard with arrow keys ;) > > Michael Thanks! Works fine! :) Ole pgploWxL4uZnl.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Sat, 19 Jul 2008 13:43:54 + Ole Kliemann <[EMAIL PROTECTED]> babbled: > After `opkg update ; opkg upgrade' on my FR using ASU this morning, the > onscreen keyboard is broken. It is still displayed and when striking a > key the letter is raised but nothing more; the input is not working. > Also the `drag-up-gesture' for switching the layout to numbers is not > working. > > Problem resides when reflashing with: > > http://buildhost.openmoko.org/daily/freerunner/200807/20080718/uImage-om-gta02-latest.bin > http://buildhost.openmoko.org/daily/freerunner/200807/20080718/openmoko-qtopia-x11-image-om-gta02.jffs2 i'm in the middle of a full kbd rewrite... it's all functional now... with latest svn (rev151) for sure, but dictionary lookup is not working (havent done that yet). -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Qtopia: customize keyboard, select input language
On Mon, Jul 21, 2008 at 03:41:19PM +, Ole Kliemann wrote: > I want English as > language displayed, but German as input-language. I have chosen as > language U.S. English but checked the `use for input' box for German. > Still the predicative keyboard seems only to use English. Workaround for this is: cd /opt/Qtopia/etc/dict mv en_US _en_US ln -s de en_US Ole pgpf5cFwrbzw7.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Tue, Jul 22, 2008 at 04:29:39AM +1000, Carsten Haitzler wrote: > i'm in the middle of a full kbd rewrite... it's all functional now... with > latest svn (rev151) for sure, but dictionary lookup is not working (havent > done > that yet). Was working well at one point. Could change the keyboards with menu and my own layout was working. Thumbs up for the customizable .kbd files. Especially that you can change the size of the keys. These are the things I got an FR for. :) But right now[1], I don't get a keyboard at all. [1] http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2 illume is rev152 in this image. Ole pgpKtXsfobAYM.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
Hello, On Wed, Jul 23, 2008 at 2:13 PM, Ole Kliemann <[EMAIL PROTECTED]> wrote: > But right now[1], I don't get a keyboard at all. > > [1] > http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2 >illume is rev152 in this image. I can confirm this - I just did an 'opkg upgrade -force-overwrite' even after I was warned. And no the keyboard never shows up (test with PIN code dialog, contacts application). Is there a way to "roll back" to a known working version? -- Regards, Torfinn Ingolfsen ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Wed, 23 Jul 2008 13:07:22 +0200 "Torfinn Ingolfsen" <[EMAIL PROTECTED]> babbled: > Hello, > > On Wed, Jul 23, 2008 at 2:13 PM, Ole Kliemann > <[EMAIL PROTECTED]> wrote: > > But right now[1], I don't get a keyboard at all. > > > > [1] > > http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2 > > illume is rev152 in this image. > > I can confirm this - I just did an 'opkg upgrade -force-overwrite' > even after I was warned. And no the keyboard never shows up (test with > PIN code dialog, contacts application). > Is there a way to "roll back" to a known working version? and it will continue to be there/not there between svn versions. qtopia has its own vkbd and illume has one - they conflict and right now i can only turn off the illume one in code. so depending what svnrev u get it may or may not be enabled or conflict etc. etc. - u'll have to wait for dust to settle. -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Wed, Jul 23, 2008 at 01:07:22PM +0200, Torfinn Ingolfsen wrote: > Hello, > > On Wed, Jul 23, 2008 at 2:13 PM, Ole Kliemann > <[EMAIL PROTECTED]> wrote: > > But right now[1], I don't get a keyboard at all. > > > > [1] > > http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2 > >illume is rev152 in this image. > > I can confirm this - I just did an 'opkg upgrade -force-overwrite' > even after I was warned. And no the keyboard never shows up (test with > PIN code dialog, contacts application). > Is there a way to "roll back" to a known working version? I guess the problem is with illume. I think rev151 worked. I don't know if there are still binaries (e.g. an ipkg) to find for this rev. You could check out rev151 from svn and compile yourself, I guess. But probably this will be fixed pretty soon. It was working just yesterday or so. Ole pgpzp2NX1YJWQ.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Wed, Jul 23, 2008 at 10:28:08PM +1000, Carsten Haitzler wrote: > On Wed, 23 Jul 2008 13:07:22 +0200 "Torfinn Ingolfsen" <[EMAIL PROTECTED]> > babbled: > > > Hello, > > > > On Wed, Jul 23, 2008 at 2:13 PM, Ole Kliemann > > <[EMAIL PROTECTED]> wrote: > > > But right now[1], I don't get a keyboard at all. > > > > > > [1] > > > http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2 > > > illume is rev152 in this image. > > > > I can confirm this - I just did an 'opkg upgrade -force-overwrite' > > even after I was warned. And no the keyboard never shows up (test with > > PIN code dialog, contacts application). > > Is there a way to "roll back" to a known working version? > > and it will continue to be there/not there between svn versions. qtopia has > its > own vkbd and illume has one - they conflict and right now i can only turn off > the illume one in code. so depending what svnrev u get it may or may not be > enabled or conflict etc. etc. - u'll have to wait for dust to settle. I see. Sitting tight... :) pgpRHLAohdjEp.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
Hi, On Wed, Jul 23, 2008 at 2:28 PM, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote: > and it will continue to be there/not there between svn versions. qtopia has > its > own vkbd and illume has one - they conflict and right now i can only turn off > the illume one in code. so depending what svnrev u get it may or may not be > enabled or conflict etc. etc. - u'll have to wait for dust to settle. In the future, could it be possible to have a configurable keyboard? - I install three keyboards I like (or all available keyboards) - I configure somewhere (a .conf file in /etc maybe?) which keyboard I prefer, this is the keyboard that appears whenever a keyboard i needed Additionally, all keyboards have a way to switch to another keyboard (menu?, extra key?) so that I can switch whenever I want, even in mid sentence. Anyway, that would be my wish. -- Torfinn -- mvh Torfinn ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Wed, Jul 23, 2008 at 01:07:22PM +0200, Torfinn Ingolfsen wrote: > Hello, > > On Wed, Jul 23, 2008 at 2:13 PM, Ole Kliemann > <[EMAIL PROTECTED]> wrote: > > But right now[1], I don't get a keyboard at all. > > > > [1] > > http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2 > >illume is rev152 in this image. > > I can confirm this - I just did an 'opkg upgrade -force-overwrite' > even after I was warned. And no the keyboard never shows up (test with > PIN code dialog, contacts application). > Is there a way to "roll back" to a known working version? Backup your data and flash this one: http://buildhost.openmoko.org/daily/freerunner/200807/20080721/openmoko-qtopia-x11-image-om-gta02.jffs2 It works for me so far. Ole pgpGgjNorEJvH.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Wed, Jul 23, 2008 at 03:50:44PM +0200, Torfinn Ingolfsen wrote: > Hi, > > On Wed, Jul 23, 2008 at 2:28 PM, The Rasterman Carsten Haitzler > <[EMAIL PROTECTED]> wrote: > > and it will continue to be there/not there between svn versions. qtopia has > > its > > own vkbd and illume has one - they conflict and right now i can only turn > > off > > the illume one in code. so depending what svnrev u get it may or may not be > > enabled or conflict etc. etc. - u'll have to wait for dust to settle. > > In the future, could it be possible to have a configurable keyboard? > - I install three keyboards I like (or all available keyboards) > - I configure somewhere (a .conf file in /etc maybe?) which keyboard I > prefer, this is the keyboard that appears whenever a keyboard i needed > Additionally, all keyboards have a way to switch to another keyboard > (menu?, extra key?) so that I can switch whenever I want, even in mid > sentence. Try the image I posted. You can change the keyboard via menu. Look into /usr/lib/enlightenment/modules/illume/keyboards/ Check out the .kbd files. It's pretty easy to modify them/make your own. Ole pgpHMfupzEfx4.pgp Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Wed, 23 Jul 2008 15:50:44 +0200 "Torfinn Ingolfsen" <[EMAIL PROTECTED]> babbled: > Hi, > > On Wed, Jul 23, 2008 at 2:28 PM, The Rasterman Carsten Haitzler > <[EMAIL PROTECTED]> wrote: > > and it will continue to be there/not there between svn versions. qtopia has > > its own vkbd and illume has one - they conflict and right now i can only > > turn off the illume one in code. so depending what svnrev u get it may or > > may not be enabled or conflict etc. etc. - u'll have to wait for dust to > > settle. > > In the future, could it be possible to have a configurable keyboard? > - I install three keyboards I like (or all available keyboards) > - I configure somewhere (a .conf file in /etc maybe?) which keyboard I > prefer, this is the keyboard that appears whenever a keyboard i needed > Additionally, all keyboards have a way to switch to another keyboard > (menu?, extra key?) so that I can switch whenever I want, even in mid > sentence. yes. configuring which keyboard comes up is on my todo list. it's almost there - i am adding in config fields and then e will handle executing the keyboard 0 if it needs executing, or be able to use its internal one (its not a separate process, so it comes with less overhead), or have no keyboard at all... thats my plan anyway... -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia: keys missing for predictive keyboard?
Joerg Lippmann wrote: > Hi! > > From what I have seen, the predictive keyboard of qtopia for the freerunner > is IMO by far the best typing solution for text messages. > > But is it just me or are there some keys missing for touchscreen? I have not > found a possibility to erase letters or to enter special keys etc. > I'll trade you info: to erase a letter you sweep your finger leftwards just below the keyboard. A "slight" sweep does that; a longer sweep erases the current word. Now my turn to ask: I used Qtopia and the predictive kb for a while and then it got back-burnered. I just flashed it again and I'm in the opposite position from you. How do you *accept* the word that's showing and move on to the next one? Thx. b. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia: keys missing for predictive keyboard?
On Wed, Jul 23, 2008 at 03:40:04PM -0400, Brian Capouch wrote: > I'll trade you info: to erase a letter you sweep your finger leftwards > just below the keyboard. A "slight" sweep does that; a longer sweep > erases the current word. > > Now my turn to ask: I used Qtopia and the predictive kb for a while and > then it got back-burnered. I just flashed it again and I'm in the > opposite position from you. How do you *accept* the word that's showing > and move on to the next one? Sweep your finger rightwards? ;-) Regards, Thomas ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: qtopia: keys missing for predictive keyboard?
You should be able to select it from the list that pops up above the keyboard (and bellow the message). It puts the space in for you. To select it, just press down on it. Does anyone know put a space or newline into the message? -SR On Wed, Jul 23, 2008 at 4:19 PM, Thomas B. <[EMAIL PROTECTED]> wrote: > On Wed, Jul 23, 2008 at 03:40:04PM -0400, Brian Capouch wrote: > > I'll trade you info: to erase a letter you sweep your finger leftwards > > just below the keyboard. A "slight" sweep does that; a longer sweep > > erases the current word. > > > > Now my turn to ask: I used Qtopia and the predictive kb for a while and > > then it got back-burnered. I just flashed it again and I'm in the > > opposite position from you. How do you *accept* the word that's showing > > and move on to the next one? > > Sweep your finger rightwards? ;-) > > Regards, > Thomas > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
